Related
So, I wiped all data, system, cache, internal storage using TWRP and then I flash the system.img to System Image and boot.img to Boot into 2 slots (A & B). Consequently, I lose TWRP and root. I have gone back to May Security Patch Nokia 8 TA-1004. I have updated and updated up until October 2018 Patch.
Then, I tried to use "fastboot boot twrp.img", however it doesn't work. It is just stuck to POWERED BY ANDROID LOGO. Flashing twrp will break the wifi and I do not want that. Anybody has solutions for this? I can't get it to boot to TWRP. I use Android stock recovery and apply update in SD Card, not working as well.
I really want to have access root. All because of that stupid random restart occurs in this thread https://forum.xda-developers.com/nokia-8/help/nokia-8-sudden-restart-occurred-randomly-t3852357
Note: During flashing system.img which reverts back to stock one, I didn't use fastboot command. I use TWRP to revert back.
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk
ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk
Click to expand...
Click to collapse
Is this the latest stock boot image (october patch)?
For resolve a lower security than september can't boot to twrp try this method.
Boot to download mode. Then Use command.
Fastboot reboot bootloader => for enter again download mode
Fastboot boot twrp.... It will go to twrp well.
Topogigi said:
Is this the latest stock boot image (october patch)?
Click to expand...
Click to collapse
Um I think cuz Magisk took this backup right during the Install to Second Slot option
ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk
Click to expand...
Click to collapse
This is October patch? If it does, you are a lifesaver.
ValKyre said:
For resolve a lower security than september can't boot to twrp try this method.
Boot to download mode. Then Use command.
Fastboot boot bootloader => for enter again download mode
Fastboot boot twrp.... It will go to twrp well.
Click to expand...
Click to collapse
YOU SIR, ARE ROCK. This is very much working for me. I can boot already to twrp. No longer stuck in POWERED BY ANDROID LOGO.
Although you have mistyped the command. It should be "fastboot reboot bootloader". Anyway, thank you. I have given my thanks to you.
godofknife said:
This is October patch? If it does, you are a lifesaver.
YOU SIR, ARE ROCK. This is very much working for me. I can boot already to twrp. No longer stuck in POWERED BY ANDROID LOGO.
Although you have mistyped the command. It should be "fastboot reboot bootloader". Anyway, thank you. I have given my thanks to you.
Click to expand...
Click to collapse
Yup ... Sorry with my head not remember true command hehe
ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
Click to expand...
Click to collapse
So can i use this img to root with Magisk with patch boot image option? Is this October patch?
Edit: Stuck on Powered by Android logo => not October boot img
Mo4o293 said:
So can i use this img to root with Magisk with patch boot image option? Is this October patch?
Edit: Stuck on Powered by Android logo => not October boot img
Click to expand...
Click to collapse
My bad I guess
ironman38102 said:
Download and extract this stock boot image and you can use it to root through Magisk's patch boot image option.
https://drive.google.com/file/d/11A8-jK0hm4j-ah3HwPpk8i_hwcoIwPBx/view?usp=drivesdk
Click to expand...
Click to collapse
I wonder if some kind soul can offer some wisdom, I unlocked my bootloader and flashed twrp. All fine so far.
I then upgraded to Pie.
I then flashed Magisk.
I was getting some strange Magisk behaviour so uninstalled it but for some reason it did'nt restore stock boot and Play Store was misbehaving.
I then flashed this boot image ^^ and yes, very stupidly, I now have no wifi (my MAC address is screwed).
I can boot to OS but I have no File Manager, nor root and I don't really know what to try from here.
I cant get to recovery (twrp or stock), it just get stuck on the Powered by Android logo.
I have debugging enabled but adb just reports my device as offline.
I cant get in to fastboot mode either.
Really appreciate some help from a kind soul
Ta
Hello i unlocked bootloader and after working so hard i finally booted twrp img to my nokia 8 and from there i cant access to twrp it always opens stock recovery.pls help me.....
I tried 2 to 3 times but i cant access twrp the process was successful but cant access it
I would say if it does not boot to it, its not there. Just flash twrp again. Use the latest from their website to do it.
Hi all, I'd like to share my experiences here about trying to patch boot.img for the Blackview BV6300 Pro which is one of the countless MediaTek Helio P70 (aka MT6771) China phones that can be had for a bit of change at every corner nowadays. It features a fairly non-clutter generic Android 10 ROM.
I bought it because of good feature/price ratio. I also like the fairly idiot-proof MTK Preloader/SP Flash Tool combo and expected no big problems having the phone patched. Apparently that estimate was wrong.
I extracted the boot.img (at exactly 32768k) and started patching it with the latest Magisk Manager (8.0.4). When set to "Stable" the patched result came out less than 12Megs which struck me as very odd, so I did not bother trying to flash that and switched to "beta". Et voila, out came a patched image that appeared to have just the right size.
Unfortunately, after flashing the patched image, the device detected a modified boot signature and flagged "Red State, rebooting in 5s", effectively entering a boot loop. Going back to stock, then unlocking the bootloader with fastboot and reflashing patched boot changed the "Red State" to "Orange State" but the boot loop persisted.
The boot loop message also suggests to either reflash stock or "disable verified boot". Yeah, but... Magisk Manager 8.0.4 seems to have lost the "Advanced Options" menu that had been there in previous versions, allowing users to toggle dmverity while patching boot images... so I wonder how to get around this!? Any suggestions?
Any solution for this, or any suggestions to try??
Have you tried this?
https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
Didgeridoohan said:
Have you tried this?
Click to expand...
Click to collapse
Thanks for your suggestion but it seems like this requires TWRP and, as far as I know, no TWRP recovery is available for the BV6300 Pro.
You have to unlock your bootloader FIRST and not after.Start from scratch and it will work,im sure.Cheers!!!
First make the new,i mean flash fresh firmware blablabla.Extract your firmware,copy boot img to phone,install magisk manager and patch the boot img(im sure you can do it without root(on my Redmi 9 it works),copy patched boot imhg to pc and use adb to flash,but be sure your bootloader is unlocked before.Good luck.
We must unlock the bootloader with fastboot mode or we can do it through developer options??
black_knight_ said:
We must unlock the bootloader with fastboot mode or we can do it through developer options??
Click to expand...
Click to collapse
Fastboot
Bitmixer have you manage to root your phone?
Because i still get a bootloop when flashing the patched boot image...
black_knight_ said:
Bitmixer have you manage to root your phone?
Because i still get a bootloop when flashing the patched boot image...
Click to expand...
Click to collapse
black_knight_ said:
Bitmixer have you manage to root your phone?
Because i still get a bootloop when flashing the patched boot image...
Click to expand...
Click to collapse
Did you flashed vbmeta.img ,thats important.
-CALIBAN666- said:
Did you flashed vbmeta.img ,thats important.
Click to expand...
Click to collapse
DId you mean to follow the guide of : https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/ so we can disable verified boot, because that requires twrp and it is no supported on our device.
Or something else?? And where we find vbmeta.img that disable verified boot?
black_knight_ said:
DId you mean to follow the guide of : https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/ so we can disable verified boot, because that requires twrp and it is no supported on our device.
Or something else?? And where we find vbmeta.img that disable verified boot?
Click to expand...
Click to collapse
Ive flashed vbmeta with adb on my phones,like my Redmi 9,when you dont have vbmeta i think u cant do anything with flashing something,just google for it or look here for it,good luck!!!
OZIP's FOR RMX2001«Android 10»ㅤㅤ ㅤㅤㅤㅤ ㅤㅤㅤㅤㅤㅤㅤ Click Here
«Android 11»*Team Drive Gone Will Find And Update
Need Help?
Contact Me On Telegram
-GROUP LINK-
Awesome!! Can I dirty flash ui2?
Android 11 update (C12 Global) failed, why?
Not flashing ui 2
Ferbir88 said:
Android 11 update (C12 Global) failed, why?
Click to expand...
Click to collapse
it cant be flashed directly u should flash ozip using custom recovery but after flash , flash patched vbmeta too otherwise u got brick for more info ask in ofiicial realme 6 main telegram group
xdriv3r said:
Not flashing ui 2
Click to expand...
Click to collapse
u cant flash it by stock recovery read other comment reply
unique_sandesh said:
it cant be flashed directly u should flash ozip using custom recovery but after flash , flash patched vbmeta too otherwise u got brick for more info ask in ofiicial realme 6 main telegram group
Click to expand...
Click to collapse
I tried not working (bootloop). I lfashed patched vbmeta. I installed it with custom recovery
Ferbir88 said:
I tried not working (bootloop). I lfashed patched vbmeta. I installed it with custom recovery
Click to expand...
Click to collapse
tell meyour all process sir , and they also need format
unique_sandesh said:
unique_sandesh said:
tell meyour all process sir , and they also need format
First, I flashed stock b.53 firmware with SP flashtool and I update with stock recovery to b.65. For the second time I need root the firmware and patch vbmeta, because missing the custom recovery without this step.( orange fox recovery)For the third Time I flash the c.12 firmware with custom recovery, and reboot to bootloader from recovery than I patch c.12 vbmeta. For the last Time I reboot and the end result bootloop.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
unique_sandesh said:
tell meyour all process sir , and they also need format
Click to expand...
Click to collapse
First, I flashed stock b.53 firmware with SP flashtool and I update with stock recovery to b.65. For the second time I need root the firmware and patch vbmeta, because missing the custom recovery without this step.( orange fox recovery)For the third Time I flash the c.12 firmware with custom recovery, and reboot to bootloader from recovery than I patch c.12 vbmeta. For the last Time I reboot and the end result bootloop
ofc it will not boot untill u format data , u need to format data . give these cmd fastboot -w , fastboot erase userdata
unique_sandesh said:
ofc it will not boot untill u format data , u need to format data . give these cmd fastboot -w , fastboot erase userdata
Click to expand...
Click to collapse
Thank you very much now It works, but I want to ask you: Why can not i enter in recovery Mode? I tried the power on and volume down combination, but the phone enter only fastboot mode with "oplus verification failed" message. If I do a factory reset under the Android, the phone load the recovery, until resetting.
Ferbir88 said:
Thank you very much now It works, but I want to ask you: Why can not i enter in recovery Mode? I tried the power on and volume down combination, but the phone enter only fastboot mode with "oplus verification failed" message. If I do a factory reset under the Android, the phone load the recovery, until resetting.
Click to expand...
Click to collapse
from rmui 2.o we only get in fastboot mode. for recovery give this cmd fastboot reboot recovery, , and ignore that oppo verify failed msg
unique_sandesh said:
from rmui 2.o we only get in fastboot mode. for recovery give this cmd fastboot reboot recovery, , and ignore that oppo verify failed msg
Click to expand...
Click to collapse
Thank you very much!
Hello everyone don't know why but i didn't get realme ui 2.0 update I'm stuck on B.65 for RMX2001 and as i recall i once rooted it unlocked bootloader but i relocked it and unrooted it to with all its ROM and Recovery set to default and i exited In-depth test too but i didn't get 2.0 update last updated version is B.65 so i wanna know if i download the file mentioned above and install it will it work.... Please reply
Jegwaar said:
Hello everyone don't know why but i didn't get realme ui 2.0 update I'm stuck on B.65 for RMX2001 and as i recall i once rooted it unlocked bootloader but i relocked it and unrooted it to with all its ROM and Recovery set to default and i exited In-depth test too but i didn't get 2.0 update last updated version is B.65 so i wanna know if i download the file mentioned above and install it will it work.... Please reply
Click to expand...
Click to collapse
were the same situation and i dont know what to do. Please help us.
which is the process 4 install? im on rui 1.0
Kodize said:
which is the process 4 install? im on rui 1.0
Click to expand...
Click to collapse
using custom recovery
Rollback With Custom Recovery
This Method Only For Realme 6/6i(indian)/6s _____________________ RMUI2.0 TO RMUI 1.0____________________________________________ This Method For Downgrading From F2Fs Based Custom Roms ⓿ Flash Latest TWRP (Gofaraway One) ❶ Go to manage partitions And Select...
telegra.ph
Jegwaar said:
Hello everyone don't know why but i didn't get realme ui 2.0 update I'm stuck on B.65 for RMX2001 and as i recall i once rooted it unlocked bootloader but i relocked it and unrooted it to with all its ROM and Recovery set to default and i exited In-depth test too but i didn't get 2.0 update last updated version is B.65 so i wanna know if i download the file mentioned above and install it will it work.... Please reply
Click to expand...
Click to collapse
keep unlockd your bl and use spft for flashing rui 2 make sure you selected download only in spft while flashing here is the latest decrypted firmware link https://t.me/rmx2001_clouds/7
unique_sandesh said:
keep unlockd your bl and use spft for flashing rui 2 make sure you selected download only in spft while flashing here is the latest decrypted firmware link https://t.me/rmx2001_clouds/7
Click to expand...
Click to collapse
Hi guys, did someone do this ? i'm in the same situation after rolling back to B55 using stock recovery, now stuck on B65, no update coming.
Bootloader is unlocked, when i flash a C18 firmware with SPF phone bootloop in fastboot mode.
Only flashing a B65 firmware with SPF to get phone boot corretly.
I just need to known if this method is tested with the given C19 firmware ?
Many thx.
I have eagerly been waiting for the release of a TWRP image or MSM tool for this device, to no avail
I have seen on one of these posts, found here, a potentially working TWRP image.
Currently it is just the twrp.img without any zip
Directly download it here
As said below, this should be flashable within magisk to install
- I have NOT tested this personally
- I am not advising anybody try this image either
- Password decryption appears to not be functional
- This appears to only function on Android 13
sm8450 A13 Kernel Source Compile Issues
2023/02/16 UPDATE!!!! https://github.com/OnePlusOSS/android_kernel_msm-5.10_oneplus_sm8450/issues/4 if u want test it ---> https://github.com/negroni-development/oneplus-sm8450_t_13.0_10pro referenced by X5Pro based severecold's work.(compiles...
forum.xda-developers.com
It should be able to flash into magisk, but there is no guarantee that flashing into rom can enter the system
PlasmaTornado said:
I have eagerly been waiting for the release of a TWRP image or MSM tool for this device, to no avail
I have seen on one of these posts, found here, a potentially working TWRP image.
Currently it is just the twrp.img without any zip
- I have NOT tested this personally
- I am not advising anybody try this image either
- Password decryption appears to not be functional
- This appears to only function on Android 13
sm8450 A13 Kernel Source Compile Issues
2023/02/16 UPDATE!!!! https://github.com/OnePlusOSS/android_kernel_msm-5.10_oneplus_sm8450/issues/4 if u want test it ---> https://github.com/negroni-development/oneplus-sm8450_t_13.0_10pro referenced by X5Pro based severecold's work.(compiles...
forum.xda-developers.com
Click to expand...
Click to collapse
we need testers
TrajanoX3 said:
we need testers
Click to expand...
Click to collapse
Agreed. I'm sure there are some people willing to give it a shot.
I haven't flashed an image since split partitions has existed, which is a fairly long time now
Even with the OP10, I am still unrooted. TWRP provides just that extra bit of security to me
I tested the twrp. I flashed to A then flashed to B . Put phone to fastboot flashed using the fastboot commands
( fastboot flash recovery_a ) then flashed B using commands ( fastboot flash recovery_b ) . From fastboot went to recovery . Booted up twrp recovery . Change language to English ( second from bottom right ) . Completed backup , reboot phone ok . Then went back into fastboot and reboot to twrp recovery. So its seems to be working ok so far.
Canuck Knarf said:
I tested the twrp. I flashed to A then flashed to B . Put phone to fastboot flashed using the fastboot commands
( fastboot flash recovery_a ) then flashed B using commands ( fastboot flash recovery_b ) . From fastboot went to recovery . Booted up twrp recovery . Change language to English ( second from bottom right ) . Completed backup , reboot phone ok . Then went back into fastboot and reboot to twrp recovery. So its seems to be working ok so far.
Click to expand...
Click to collapse
Fantastic! Can you confirm that it can decrypt without any issues?
Its working good
Canuck Knarf said:
I tested the twrp. I flashed to A then flashed to B . Put phone to fastboot flashed using the fastboot commands
( fastboot flash recovery_a ) then flashed B using commands ( fastboot flash recovery_b ) . From fastboot went to recovery . Booted up twrp recovery . Change language to English ( second from bottom right ) . Completed backup , reboot phone ok . Then went back into fastboot and reboot to twrp recovery. So its seems to be working ok so far.
Click to expand...
Click to collapse
we donate screenshot
heres recovery log from TWRP
Canuck Knarf said:
heres recovery log from TWRP
Click to expand...
Click to collapse
Are you using twrp right now?
TrajanoX3 said:
Are you using twrp right now?
Click to expand...
Click to collapse
Yes
Canuck Knarf said:
Yes
Click to expand...
Click to collapse
Can you send us a screenshot of twrp?
Canuck Knarf said:
Sim
Click to expand...
Click to collapse
Thanks for the screenshots, did you flash magisk through twrp?
Canuck Knarf said:
Yes
Click to expand...
Click to collapse
Magisk installation working probably by twrp?
just installed Magisk
TrajanoX3 said:
we donate screenshot
Click to expand...
Click to collapse
then install and flash partition A and then partition B and relapse to recovery?
Yes
fastboot flash recovery_a then fastboot flash recovery_b then reboot to recovery from fastboot . then change language ...cause its in Chinese
Oh and Twrp works with screen password lock so no need to disable it
Canuck Knarf said:
Oh and Twrp works with screen password lock so no need to disable it
Click to expand...
Click to collapse
how do you operate
Beware, this twrp.img is not bootable. Command fastboot boot twrp.img won't work, you will get bootloop into OP logo. Rebooting into fastboot mode and doing fastboot boot stockboot.img will help.
So it means you can only flash it directly. Confirmed by me and three others.
Hello! On the official TWRP website I downloaded the latest version 3.7.0-11 and it turns out that I can't update the weekly ROM because TWRP doesn't show any file. Reading and asking on the internet they gave me a solution but I do not know how safe and reliable it is, they referred me to this link: https://www.123pan.com/s/qHhDVv-nuQJv where they tell me that I have to do, adb, "fastboot boot TWRP.img" with the version (BOOT) 3.7.0_12_Mi11_v7.0_A13-venus-skkk_64135681 .....the question is. How reliable is that file, considering that on the official TWRP website only supports Android 12 and earlier versions? Does anyone with Mi 11 and android 13 TKQ know how to solve this problem? Using ADB Sideload could it be possible to update without losing any data?
Thank you for all!!!
Gor3zno said:
Hello! On the official TWRP website I downloaded the latest version 3.7.0-11 and it turns out that I can't update the weekly ROM because TWRP doesn't show any file. Reading and asking on the internet they gave me a solution but I do not know how safe and reliable it is, they referred me to this link: https://www.123pan.com/s/qHhDVv-nuQJv where they tell me that I have to do, adb, "fastboot boot TWRP.img" with the version (BOOT) 3.7.0_12_Mi11_v7.0_A13-venus-skkk_64135681 .....the question is. How reliable is that file, considering that on the official TWRP website only supports Android 12 and earlier versions? Does anyone with Mi 11 and android 13 TKQ know how to solve this problem? Using ADB Sideload could it be possible to update without losing any data?
Thank you for all!!!
Click to expand...
Click to collapse
If you are on xiaomi.eu_multi_MI11_V14.0.23.1.3.DEV_v14-13.zip
and want to update on the
xiaomi.eu_multi_MI11_V14.0.23.1.9.DEV_v14-13.zip
Start by removing security on the lock screen and reboot then use OTA to download the update and update the phone reboot and the twrp install the rom.
If you want to install the latest TWRP remove security on the lock screen and reboot then flash the TWRP in fastboot mode, assuming it is a TWRP boot.
Command:
fastboot boot twrp.img
powershell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
If REC version
Install with TWRP or fastboot flash recovery_ab twrp.img
Note that the TWRP A13 is already on the rom that you use if weekly A13.
If your system is in A12 use a TWRP A12 to flash A13.
I have Android 13. When I try to download TWRP A13 from https://sourceforge.net/projects/re...wrp-3.7.0_12-v7.0_A13-venus-skkk.img/download I get: 'Software download may not be possible on this device'
When I flash current TWRP I get two sentences, in red (error) 'Unmont data.../.../.twrp'.
Is this command 'fastboot flash recovery_ab twrp.img' new to me, what is the difference with 'fastboot boot twrp.img'?
I don't know what this REC version means?
Gor3zno said:
I have Android 13. When I try to download TWRP A13 from https://sourceforge.net/projects/re...wrp-3.7.0_12-v7.0_A13-venus-skkk.img/download I get: 'Software download may not be possible on this device'
When I flash current TWRP I get two sentences, in red (error) 'Unmont data.../.../.twrp'.
Is this command 'fastboot flash recovery_ab twrp.img' new to me, what is the difference with 'fastboot boot twrp.img'?
I don't know what this REC version means?
Click to expand...
Click to collapse
What is the current TWRP?
If the fastboot boot twrp.img command worked, it's a boot.twrp.
The REC version installs with the TWRP or fastboot flash recovery_ab twrp.img.
To download on Souceforge with the phone.
In the Android browser, press the Menu button and then Settings.
Touch the Advanced options menu.
Touch the User Agent item.
Select the system you want to pass your browser to.
The change is immediate.
What is the version number of your phone?
Go to /settings/my phone/features/model
Example:M2011K2G, M2011K2C
Did you try?
"If you are on xiaomi.eu_multi_MI11_V14.0.23.1.3.DEV_v14-13.zip
and want to update on the
xiaomi.eu_multi_MI11_V14.0.23.1.9.DEV_v14-13.zip
Start by removing security on the lock screen and reboot then use OTA to download the update and update the phone reboot and the twrp install the rom."
I have M2011K2G, xiaomi.eu 14.0.22.12.16 and TWRP 3.7.0-11, the last in the oficial web. Although, according to my research, it seems that this version is not valid for Android 13.
Yes, I removed the fingerprint and the security pattern before.
Gor3zno said:
I have M2011K2G, xiaomi.eu 14.0.22.12.16 and TWRP 3.7.0-11, the last in the oficial web. Although, according to my research, it seems that this version is not valid for Android 13.
Yes, I removed the fingerprint and the security pattern before.
Click to expand...
Click to collapse
Are you sure, I don't see this rom for your device?
https://sourceforge.net/projects/xi...i.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.16.DEV/
You have a Twrp A12 on an A13 system.
Format the data.
Twrp/wipe format data type yes reboot TWRP.
If error, red lines, repeat the operation as many times as necessary and rebbot on the TWRP at each attempt.
Then flash this TWRP
twrp-3.7.0_12-v7.0_A13-venus-skkk.img
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/venus/
and install the rom.
NOSS8 said:
Are you sure, I don't see this rom for your device?
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.16.D
Click to expand...
Click to collapse
Sorry, 22.12.26 is the ROM.
'fastboot flash recovery twrp.img' doesn't work for me, only the boot command.
I didn't try 'fastboot flash recovery_ab twrp.img' but the TWRP I have (3.7.0-11) is apparently not compatible with Android 13 and that's why some say it doesn't work, but I don't understand, it's the latest version on the official TWRP website.
Gor3zno said:
Sorry, 22.12.26 is the ROM.
'fastboot flash recovery twrp.img' doesn't work for me, only the boot command.
I didn't try 'fastboot flash recovery_ab twrp.img' but the TWRP I have (3.7.0-11) is apparently not compatible with Android 13 and that's why some say it doesn't work, but I don't understand, it's the latest version on the official TWRP website.
Click to expand...
Click to collapse
We are talking about these roms, right?
because the TWRP is included in the rom.
https://sourceforge.net/projects/xi...i.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.26.DEV/
NOSS8 said:
We are talking about these roms, right?
because the TWRP is included in the rom.
https://sourceforge.net/projects/xi...i.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.26.DEV/
Click to expand...
Click to collapse
That's strange, when I installed that room, it turns out that the 'main menu' was the normal one, the one that comes without many options.
Gor3zno said:
That's strange, when I installed that room, it turns out that the 'main menu' was the normal one, the one that comes without many options.
Click to expand...
Click to collapse
I have the impression that you are talking to me about the Stock EEA rom for Europe and not the Xiaomi Eu rom custom rom.
NOSS8 said:
Are you sure, I don't see this rom for your device?
https://sourceforge.net/projects/xi...i.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.16.DEV/
You have a Twrp A12 on an A13 system.
Format the data.
Twrp/wipe format data type yes reboot TWRP.
If error, red lines, repeat the operation as many times as necessary and rebbot on the TWRP at each attempt.
Then flash this TWRP
twrp-3.7.0_12-v7.0_A13-venus-skkk.img
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/venus/
and install the rom.
Click to expand...
Click to collapse
So I can't try to flash or boot with A13 version without doing the wioe and without losing all the data?
NOSS8 said:
I have the impression that you are talking to me about the Stock EEA rom for Europe and not the Xiaomi Eu rom custom rom.
Click to expand...
Click to collapse
Ok, now it's clear.
22.12.26 was in Fastboot.zip because no functional TWRP at this time.
try again to install the TWRP A13
twrp-3.7.0_12-v7.0_A13-venus-skkk.img**
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/venus/
This is the official TWRP developed by SKK and uploader by Camerado84
Command:
fastboot boot twrp.img**
powershell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
Try several rebooting each time in Fastboot mode.
If after several attempts 5/6 still the same you will have to:
Format the data.
Twrp/wipe format data type yes reboot TWRP.
If error, red lines, repeat the operation as many times as necessary and reboot on the TWRP at each attempt.
Then flash this TWRP**
Rename it twrp.img**
NOSS8 said:
Ok, now it's clear.
22.12.26 was in Fastboot.zip because no functional TWRP at this time.
try again to install the TWRP A13
twrp-3.7.0_12-v7.0_A13-venus-skkk.img**
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/venus/
This is the official TWRP developed by SKK and uploader by Camerado84
Command:
fastboot boot twrp.img**
powershell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
Try several rebooting each time in Fastboot mode.
If after several attempts 5/6 still the same you will have to:
Format the data.
Twrp/wipe format data type yes reboot TWRP.
If error, red lines, repeat the operation as many times as necessary and reboot on the TWRP at each attempt.
Then flash this TWRP**
Rename it twrp.img**
Click to expand...
Click to collapse
As soon as I have time I'll try it and let you know, thank you
Gor3zno said:
As soon as I have time I'll try it and let you know, thank you
Click to expand...
Click to collapse
To try.
In the Fastboot rom 22.12.26 look in the img folder and replace the recovery.img with the TWRP A13 by renaming it recovery.img.
Important check that the sizes are identical otherwise it will not work.
Then use the Update.bat file.
Then update via OTA.
This will allow you to keep the data.
NOSS8 said:
To try.
In the Fastboot rom 22.12.26 look in the img folder and replace the recovery.img with the TWRP A13 by renaming it recovery.img.
Important check that the sizes are identical otherwise it will not work.
Then use the Update.bat file.
Then update via OTA.
This will allow you to keep the data.
Click to expand...
Click to collapse
There is no recovery.img but the 'boot.img' file happens to weigh exactly the same as the twrpA13skkk file.
Is it possible that boot is the recovery you are referring to?
If so, I should rename the twrpA13skkk.img file to boot.img in this folder.
Although, probably misinformed, I thought that boot is the one in charge of booting the system..... so I'm afraid that changing the file will only boot in TWRP mode without being able to enter system or fastboot.
Gor3zno said:
There is no recovery.img but the 'boot.img' file happens to weigh exactly the same as the twrpA13skkk file.
Is it possible that boot is the recovery you are referring to?
If so, I should rename the twrpA13skkk.img file to boot.img in this folder.
Although, probably misinformed, I thought that boot is the one in charge of booting the system..... so I'm afraid that changing the file will only boot in TWRP mode without being able to enter system or fastboot.
Click to expand...
Click to collapse
Nope, this is a method I used a long time ago and there was a recovery.img.
Stock fastboot rom
NOSS8 said:
Nope, this is a method I used a long time ago and there was a recovery.img.
Click to expand...
Click to collapse
Well, it seems that it is no longer called that.
By installing the twrpA13skkk version you told me, via fastboot, it works perfectly !!!!! I think a lot of people have had the same problem as me because we went to the official TWRP website and the latest version listed there is not compatible with Android 13.
I looked at the cmd command screen and I noticed that after typing 'fastboot boot twr.img' appears writing 'boot.img' so maybe you can change the boot.img file from xiaomi.eu by twrpA13skkk.img (renaming it to boot.img) but as we are not sure we better not move forward on that issue until someone solves that unknown.
If it wasn't for you I wouldn't have found the TWRP version compatible with my device so thank you very much! This is the magic of forums and the internet, now I will be able to help other people thanks to you !!!!!
I have one last doubt, now that I can see the Zip file of the updated Xiaomi eu weekly version, to UPDATE WITHOUT DELETING ANYTHING I simply have to hit 'install' select the ROM and...already?
I ask this because some sites say that you have to do wipe/dalvik and wipe/cache.... in some sites say to do it before installing, in other sites say to do it after installing the ROM, in other sites say to do it before and after and in other sites say that none of this is necessary.
Gor3zno said:
Well, it seems that it is no longer called that.
Click to expand...
Click to collapse
"TWRP website"is obsolete, use my link.
Update via ota then install, the phone reboot on the Twrp and install the rom. No wipe necessary.
Would it be possible to please move this discussion to venus forums? This forum is for alioth, and this discussion could lead to some confusion. Thanks.