Related
Ok guys, this is a sureshot guide for
PROBLEM
* anyone wanting to decrypt their op3 but stuck at 1+ boot screen(Or not able to boot any custom ROMs.) and only able to restore twrp backups
* After using fastboot format userdata twrp and about phone shows only 32gb phone memory(where the hell is my rest of 32gb )
* Fastboot format userdata resulting in Stuck at boot screen or simply an unbrick trick to return to Stock OOS in unencrypted stage
SOLUTION
1. Use method 2 of Mega unbrick guide to restore your phone to stock partitions found here
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
2. After the flashing is complete do not reboot the phone instead reboot directly into bootloader.
3. In fastboot mode flash modded twrp 3.0.2.22 using command ''fastboot flash recovery recovery.img'' found here
http://forum.xda-developers.com/devdb/project/?id=15934#downloads
4. Reboot directly into twrp and using mtp mode copy latest elemental x kernel or bluspark kernel zip for OOS and SYSTEM supersu.zip into the internal storage. System supersu.zip here OR directly proceed to step 8
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
5. Now flash system supersu.zip and directly after that kernel.zip
6. Now again reboot to recovery directly and from twrp boot into system.
7. After boot up you system should be decrypted. You can check in security settings.
8.Reboot recovery and flash required firmware + modem zip found here
http://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
9.wipe data +cache +dalvik +system
10. Flash any rom of your choice and go flashoholic, use multirom or whatever you want.
Pheww. Thanks.
Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.
Ashtrix said:
Man, Finally the SystemRoot (V4A, MultiROM etc) as we discussed a couple of weeks back with this hassle at the Mega Unbrick and Decrypt guides threads...:highfive:
I saw your post on MultiROM but maybe it got moved I guess...
So are you able to cross flash anything now ?
thanks.
Click to expand...
Click to collapse
anything... even multirom works flawless.
I will give this a try, Or will try to Flash the EX then perform parts of this since they support Kexec, to see what works, I have data and lot of apps working them again is a real pita with my schedule...
Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem
ach3fck said:
Thanks but, this is basically what i have done to decrypt my op3, i just used the CypherOs ROM instead OxygenOs, fastboot format userdata, reboot to recovery, flash rom, flash elementalx, and i didnt flash Supersu(dont know if thats causing my problem, i dont think so), i also did fastboot format userdata without being stuck at boot logo and still no 32gb, dont know whats the problem
Click to expand...
Click to collapse
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.
nikhilsnigam said:
its different fastboot format userdata causes this Dont know why. I suggest method in the OP. Read carefully and follow it.
Click to expand...
Click to collapse
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?
ach3fck said:
Aham, so the format userdata causes it, thanks for that. i want to ask you something, after restoring completely with Msmdownloadtool(method2) can i directly reboot to recovery then sideload CB 3.5.5 and then reboot to fastboot and continue with the tutorial? What im saying is my device is decrypted as long it doesnt boot, am i right?
Click to expand...
Click to collapse
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.
nikhilsnigam said:
Yes you can but you will be encrypted again. so after msm method reboot fastboot and flash modded twrp. reboot recovery flash CB or OOS. flash supersu flash kernel. Agin flash twrp.img from recovery itself and reboot recovery. After that reboot system and you are good to go. Make sure you have enough system space before flashing supersu and kernel. frow twrp file manager delete unneeded system apps 1st. DO NOT REBOOT in between.
Click to expand...
Click to collapse
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?
ach3fck said:
But i need unlocked bootloader to flash twrp, so i guess i need to unlock after i use Msmdownload tool right?
Click to expand...
Click to collapse
your bootloader doesn't get locked
nikhilsnigam said:
your bootloader doesn't get locked
Click to expand...
Click to collapse
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.
ach3fck said:
Sorry to bother you, but i have one more question, i used Msmdownloadtool before, but only in Qualcomm download mode, can i use fastboot or i have to boot to EDL(qualcomm download mode)? And again sorry for taking your time.
Click to expand...
Click to collapse
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.
nikhilsnigam said:
you have to use qualcomm download mode by switching off your phone. pressing vol up button and connecting to usb.
Click to expand...
Click to collapse
Yeah, i know that, thanks a lot, will try later all of this since i have no time now, will report how it went.Thanks!
Not used to giving guides
TWRP Backup - https://forum.xda-developers.com/oneplus-6t/how-to/dp3-twrp-backup-t-mobile-magisk-t3952304
But you need to download the the QB3 update zip and upack the payload.bin with a payload dumper
Make sure your device is on international and unlocked of course
Boot into Twrp recovery and copy the system.img and vendor.img onto device
Flash both images in respective partitions and on both A and B slot
Wipe data after flashing and reboot into bootloader
From directory of the rest of IMG you've extracted you'll want use fastboot and flash:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
Then reboot and done
Don't delete files just yet
Haven't tried but certain you can root this way:
After you've setup your device you can download magisk manager. Select the boot.img on you pc, in your dump folder, and copy it to your device again. In the magisk manager patch the boot image you copied, and copy that onto your PC
Now boot into bootloader and use command
fastboot flash boot magisk_patched.img
Or if that doesn't work try
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
And if device doesn't boot for any reason just flash back the stock boot.img
Enjoy
-About TWRP- (from my knowledge)
DON'T FLASH TWRP
I think recovery is running in boot.img now I'm not sure
But it seems we may need to patch the bootloader to have the recovery in there
Ive unpack both boot IMG from dp3 and Twrp IDK if they're made different but they look different unfortunately I don't understand enough to patch but hopefully that helps idk
So I wouldn't try flashing or booting into recovery it'll just freeze and flashing will mess up the whole device and you'll have to use msmtool again and redo process
ayjays said:
-About TWRP- (from my knowledge)
DON'T FLASH TWRP
I think recovery is running in boot.img now I'm not sure
But it seems we may need to patch the bootloader to have the recovery in there
Ive unpack both boot IMG from dp3 and Twrp IDK if they're made different but they look different unfortunately I don't understand enough to patch but hopefully that helps idk
So I wouldn't try flashing or booting into recovery it'll just freeze and flashing will mess up the whole device and you'll have to use msmtool again and redo process
Click to expand...
Click to collapse
It's not about patching.
Flash stock boot.img to both slots as I'm guessing you aren't sure which one your on.
I'll give u a twrp that works for qb3 also proper instructions.
T-Mobile version downside is we can't flash ota and we can't boot qb3 wth fastboot twrp so flashing the twrp.img now replaces kernel in boot.img.
Thanks, so I'll have to use the "flash recovery Twrp.img" command now?
Or, is it a custom one Twrp only for dp3?
And thank you by the way I'll probably post a guide using a backup from Twrp then
And I'm aware of checking the active slot with a command but I have trouble switching to the opposite after rebooting because of set_active command maybe I'm doing something wrong
ayjays said:
Thanks, so I'll have to use the "flash recovery Twrp.img" command now?
Or, is it a custom one Twrp only for dp3?
And thank you by the way I'll probably post a guide using a backup from Twrp then
Click to expand...
Click to collapse
Our recovery is built in boot.img.
Uploading now
---------- Post added at 10:10 PM ---------- Previous post was at 09:42 PM ----------
Boot to fastboot
fastboot getvar all
See which slot is active.
If it's slot a then this
fastboot flash boot_a qb3-twrp.img
If it's slot b then this
fastboot flash boot_b qb3-twrp.img
Once flashed choose boot recovery and once it boots u can flash stock boot.img back then flash magisk 19.4 while in twrp.
U must use USB drive decryption isn't working yet. Or adb sideload.
I've only tested this on T-Mobile version running qb3.
All credits to @mauronofrio I used his source with some modifications
https://www.androidfilehost.com/?fid=6006931924117924335
ayjays said:
Thanks, so I'll have to use the "flash recovery Twrp.img" command now?
Or, is it a custom one Twrp only for dp3?
And thank you by the way I'll probably post a guide using a backup from Twrp then
And I'm aware of checking the active slot with a command but switching to it after rebooting because I of set_active command maybe I'm doing something wrong
Click to expand...
Click to collapse
Did you try what I posted
twinnfamous said:
It's not about patching.
Flash stock boot.img to both slots as I'm guessing you aren't sure which one your on.
I'll give u a twrp that works for qb3 also proper instructions.
T-Mobile version downside is we can't flash ota and we can't boot qb3 wth fastboot twrp so flashing the twrp.img now replaces kernel in boot.img.
Click to expand...
Click to collapse
twinnfamous said:
Did you try what I posted
Click to expand...
Click to collapse
Not yet, but if you flash the stock boot image after then would there be any point in flashing the patch boot before hand? And, what I was looking for is a more permanent solution. So, that it'll boot and you can go to Twrp whenever without having to use a PC.
If that's the case and it works then nevermind but I remember and if I'm mistaken that, even if you flash the Twrp installer it'll still boot loop after the installation.
If that's still a problem maybe someone more skilled than I, or even you, can patch the stock bootimg themselves. And, eveb get it working for the future time on Q
Maybe unpacking and looking inside the boot.img and Twrp.img, the repacking with the proper adjustments
ayjays said:
Not yet but if you flash the stock boot image after then would there any point in flashing the patch boot before hand. And, what I was looking for is a more permanent solution. So, that it'll boot and you can go to Twrp whenever without having to use a PC.
If that's the case and it works then nevermind but I remember and if I'm mistaken that, even if you flash the Twrp installer it'll still boot loop after the installation.
If that's still a problem maybe someone more skilled than I, or even you, can patch the stock bootimg themselves. And, eveb get it working for the future time on Q
Maybe unpacking and looking inside the boot.img and Twrp.img, the repacking with the proper adjustments
Click to expand...
Click to collapse
I'm aware of the permanent solution your looking for. This is the first step. With magisk installed u can simply use the installer in my android file host by selecting modules push the + sign and find the installer then without rebooting install magisk direct install. Then u can boot to recovery with advanced reboot menu. U can also just do everything in twrp. After u flash twrp.img .
ayjays said:
Not used to giving guides
But you need to download the the QB3 update zip and upack the payload.bin with a payload dumper
Make sure your device is on international and unlocked of course
Boot into Twrp recovery and copy the system.img and vendor.img onto device
Flash both images in respective partitions and on both A and B slot
Wipe data after flashing and reboot into bootloader
From directory of the rest of IMG you've extracted you'll want use fastboot and flash:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
Then reboot and done
Don't delete files just yet
Haven't tried but certain you can root this way:
After you've setup your device you can download magisk manager. Select the boot.img on you pc, in your dump folder, and copy it to your device again. In the magisk manager patch the boot image you copied, and copy that onto your PC
Now boot into bootloader and use command
fastboot flash boot magisk_patched.img
Or if that doesn't work try
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
And if device doesn't boot for any reason just flash back the stock boot.img
Enjoy
Click to expand...
Click to collapse
Just like my guide last month on OnePlus forums as I am jacksummers, even if u do this we still have no calling ability whatsoever. SMS is barely working and it still blows for us. I have been trying everything to get the whole thing to not only flash and install but be able to boot with no hardware mismatch... It won't work unless we can resign the firmware with OnePlus signing keys after changing everything to say "single" still. Since we cannot change the phone. There is still something in the phone that comes back as op6tsingle
fullofhell said:
Just like my guide last month on OnePlus forums as I am jacksummers, even if u do this we still have no calling ability whatsoever. SMS is barely working and it still blows for us. I have been trying everything to get the whole thing to not only flash and install but be able to boot with no hardware mismatch... It won't work unless we can resign the firmware with OnePlus signing keys after changing everything to say "single" still. Since we cannot change the phone. There is still something in the phone that comes back as op6tsingle
Click to expand...
Click to collapse
My phone is off rn but I receive calls and texts and I've been receiving calls on my T-Mobile OnePlus 6t since I flashed it... Make sure you're on international version
the only problems i ran in myself so far are app optimzations and when i'd recieved calls and answer my voice would sound weird to them but id hear them perfectly (not my problem lol jk jk)
ayjays said:
My phone is off rn but I receive calls and texts and I've been receiving calls on my T-Mobile OnePlus 6t since I flashed it... Make sure you're on international version
the only problems i ran in myself so far are app optimzations and when i'd recieved calls and answer my voice would sound weird to them but id hear them perfectly (not my problem lol jk jk)
Click to expand...
Click to collapse
Yeah u need to flash every other partition in the bin dump. If it tells u u cannot bc it's a critical partition then ya can't. Once u do so u will have full function and on calls. It's basically everything in the payload.bin but abl,xbl, hyp, and a few others that tell ya they're critical partitions. Once u do that everything works Perfectly.. my main issue was the call issue u described..but do as I suggest and all will work
​
fullofhell said:
Yeah u need to flash every other partition in the bin dump. If it tells u u cannot bc it's a critical partition then ya can't. Once u do so u will have full function and on calls. It's basically everything in the payload.bin but abl,xbl, hyp, and a few others that tell ya they're critical partitions. Once u do that everything works Perfectly.. my main issue was the call issue u described..but do as I suggest and all will work
Click to expand...
Click to collapse
That's why I said to flash system and vendor in Twrp wipe data then flash the other ones I stated above in fastboot mode everything should be flashed without a problem just follow my guide it's not hard
I'm uploading twrp backup soon with root
DO AT YOUR OWN RISK I WONT BE RESPONSIBLE FOR ANYTHING!!!!!!
EVERYTHING SO FAR WORKS WITH JUST A LIL LAG HERE AND THERE
Tmo oneplus 6t fastboot flash one click Android Q DP3. i test it with and without wiping data. i just put all the files together. just run the flash bat. You need to be on latest beta. i tested myself twice.
root= Download patch q boot.img.
fastboot flash boot img after first boot. then just download canary magisk manager. a quick google search will bring it up
have fun and remember anything goes south you can msm tool back to stock!
flash all: https://drive.google.com/open?id=1D_-B5z-rHGDr6RHjDQA0hz-janrsypdv
patch boot img: https://drive.google.com/open?id=1nbiapy6HZH4VNK4JuEF9KxSIlsBRKgsX
omariscal1019 said:
DO AT YOUR OWN RISK I WONT BE RESPONSIBLE FOR ANYTHING!!!!!!
EVERYTHING SO FAR WORKS WITH JUST A LIL LAG HERE AND THERE
Tmo oneplus 6t fastboot flash one click Android Q DP3. i test it with and without wiping data. i just put all the files together. just run the flash bat. You need to be on latest beta. i tested myself twice.
root= Download patch q boot.img.
fastboot flash boot img after first boot. then just download canary magisk manager. a quick google search will bring it up
have fun and remember anything goes south you can msm tool back to stock!
flash all: https://drive.google.com/open?id=1D_-B5z-rHGDr6RHjDQA0hz-janrsypdv
patch boot img: https://drive.google.com/open?id=1nbiapy6HZH4VNK4JuEF9KxSIlsBRKgsX
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6t/development/dp3-twrp-backup-t-mobile-magisk-t3952304 TWRP backup good job on the not wiping data though
ayjays said:
That's why I said to flash system and vendor in Twrp wipe data then flash the other ones I stated above in fastboot mode everything should be flashed without a problem just follow my guide it's not hard
Click to expand...
Click to collapse
Hi, yes we are saying the same thing.. also note, for me, Calls last for a day, then broken again. Cannot use daily if u need to make phone calls. Testing with TMobile modem.img to see if resolved.
fullofhell said:
Hi, yes we are saying the same thing.. also note, for me, Calls last for a day, then broken again. Cannot use daily if u need to make phone calls. Testing with TMobile modem.img to see if resolved.
Click to expand...
Click to collapse
i made a one click fastboot let me what happens so.ican remove it and add t mo modem
omariscal1019 said:
i made a one click fastboot let me what happens so.ican remove it and add t mo modem
Click to expand...
Click to collapse
Will do buddy. Setting mine up as we speak.. I am down to just my fajita right now, bricked my pixel 3 again as I'm working on an exploit to unlock my locked down version ....
Can you relock bootloader after this? Don't want twrp or root
supaet said:
Can you relock bootloader after this? Don't want twrp or root
Click to expand...
Click to collapse
Not sure try "fastboot oem lock" in the bootloader after
I updated to MIUI 13 from miui.EU and now I can not go back to an older ROM even with full data formatting. I am seemingly stuck on this ROM. I really don't like it. Is there any way to go back?
Flash the older rom using fastboot method and necessary files.
Download the fastboot files from here: https://xiaomifirmwareupdater.com/
look up a "how to unbrick xiaomi" tutorial to learn how to flash a rom via fastboot
I just back to MIUI 12.5 EU from MIUI 13 EU, and I don't have problem
Hpotersept2 said:
Flash the older rom using fastboot method and necessary files.
Download the fastboot files from here: https://xiaomifirmwareupdater.com/
look up a "how to unbrick xiaomi" tutorial to learn how to flash a rom via fastboot
Click to expand...
Click to collapse
Will this work? It gave me an anti roll back notice before
[email protected] said:
I just back to MIUI 12.5 EU from MIUI 13 EU, and I don't have problem
Click to expand...
Click to collapse
I think OrangeFox was my problem I used it on the first install. I went back to TWRP but the damage was done.
Hpotersept2 said:
Flash the older rom using fastboot method and necessary files.
Download the fastboot files from here: https://xiaomifirmwareupdater.com/
look up a "how to unbrick xiaomi" tutorial to learn how to flash a rom via fastboot
Click to expand...
Click to collapse
I tried it. It won't flash.
What if I try a non Mi ROM first? Will that fix it?
Supermatt01 said:
What if I try a non Mi ROM first? Will that fix it?
Click to expand...
Click to collapse
Did you've installed TWRP?
Then factory reset in twrp
Boot TWRP again
format data with yes.
Boot TWRP again
Flash fw and vendor if MIUI or not if oss
Flash rom
Flash magisk or not
Format data again with yes
Boot system
In my opinion this should work with every recovery rom
Laptapper said:
Did you've installed TWRP?
Then factory reset in twrp
Boot TWRP again
format data with yes.
Boot TWRP again
Flash fw and vendor if MIUI or not if oss
Flash rom
Flash magisk or not
Format data again with yes
Boot system
In my opinion this should work with every recovery rom
Click to expand...
Click to collapse
I'll try it that way.
Laptapper said:
Did you've installed TWRP?
Then factory reset in twrp
Boot TWRP again
format data with yes.
Boot TWRP again
Flash fw and vendor if MIUI or not if oss
Flash rom
Flash magisk or not
Format data again with yes
Boot system
In my opinion this should work with every recovery rom
Click to expand...
Click to collapse
I'm trying to find the vendor and fw
Laptapper said:
Did you've installed TWRP?
Then factory reset in twrp
Boot TWRP again
format data with yes.
Boot TWRP again
Flash fw and vendor if MIUI or not if oss
Flash rom
Flash magisk or not
Format data again with yes
Boot system
In my opinion this should work with every recovery rom
Click to expand...
Click to collapse
No good.
Supermatt01 said:
I tried it. It won't flash.
Click to expand...
Click to collapse
Of course it won't, because the flash_all.bat has a couple lines in the beginning that have anti-rollback, you have to modify it with notepad, just open with notepad and delete those lines, then save it and flash normally.
Hpotersept2 said:
Of course it won't, because the flash_all.bat has a couple lines in the beginning that have anti-rollback, you have to modify it with notepad, just open with notepad and delete those lines, then save it and flash normally.
Click to expand...
Click to collapse
Which lines? When I tried that, it would not start.
I did it, it won't work.
I think I fixed it I took the fastboot script out of the miui 13 update and put it in the folder for the miui 12 fastboot. It stared the old boot logo. It is started now. I hope it is stable. Thank you all for the help and suggestions.
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.
I would like to know if someone has managed to root with magisk from CMD without twrp?
You can root with magisk on any miui 14 without using twrp.Just get the boot image from the rom,install magisk apk and patch the boot.img, reboot to fastboot mode ,open cmd and write "fastboot flash boot_ab boot.img" just replace boot.img with the name of your generated magisk boot. The boot image is located in different location according to the rom you are using .Normal miui recovery rom contain file that called payload.bin.You need to download this tool https://github.com/tobyxdd/android-ota-payload-extractor. Follow the instructions in the link and you will get the boot.img .If you using miui.eu rom ,you just need to extract the zip and you will see the boot.img. Also if you want to use Miui 14 global or EEA, you can use the fastboot rom that I created and the zip file contain the boot.img .You can get download link on this thread link https://forum.xda-developers.com/t/fastboot-version-of-miui-14-eea-global-and-older-miui-13.4381953/ .
or965 said:
You can root with magisk on any miui 14 without using twrp.Just get the boot image from the rom,install magisk apk and patch the boot.img, reboot to fastboot mode ,open cmd and write "fastboot flash boot_ab boot.img" just replace boot.img with the name of your generated magisk boot. The boot image is located in different location according to the rom you are using .Normal miui recovery rom contain file that called payload.bin.You need to download this tool https://github.com/tobyxdd/android-ota-payload-extractor. Follow the instructions in the link and you will get the boot.img .If you using miui.eu rom ,you just need to extract the zip and you will see the boot.img. Also if you want to use Miui 14 global or EEA, you can use the fastboot rom that I created and the zip file contain the boot.img .You can get download link on this thread link https://forum.xda-developers.com/t/fastboot-version-of-miui-14-eea-global-and-older-miui-13.4381953/ .
Click to expand...
Click to collapse
ive use your method but my phone still gone to bootloop. im using eu rom currently.
martin132014 said:
ive use your method but my phone still gone to bootloop. im using eu rom currently.
Click to expand...
Click to collapse
What did you do? I wrote several options.
Hey Guys!!!
4 Android 13 we not use Magisk!!! We use Lygisk its a Version direct 4 Android 13 and works great!!!
you can choose witch File you would Patch Boot.img/Recovery.img!! So you can Boot with boot.img normaly into Rooted System!!! And when you Patch the Recovery.img and Flash this, you must start with the Button-Combo that starts Recovery-Mode, so its start the Rooted System, when you start it normaly not over Recovery-Mode the System is Not Rooted!!! Thats the Difference between the 2 Methods,and a Patched Recovery dont set you in Bootloop!!!
Lygisk APK ZIP
System23 said:
Hey Guys!!!
4 Android 13 we not use Magisk!!! We use Lygisk its a Version direct 4 Android 13 and works great!!!
you can choose witch File you would Patch Boot.img/Recovery.img!! So you can Boot with boot.img normaly into Rooted System!!! And when you Patch the Recovery.img and Flash this, you must start with the Button-Combo that starts Recovery-Mode, so its start the Rooted System, when you start it normaly not over Recovery-Mode the System is Not Rooted!!! Thats the Difference between the 2 Methods,and a Patched Recovery dont set you in Bootloop!!!
Lygisk APK ZIP
Click to expand...
Click to collapse
Hi, sorry, but i bit confused about the method here. You mean to just patch either or both. This method is for fastboot or twrp. Sorry if im asking noob question.
or965 said:
What did you do? I wrote several options.
Click to expand...
Click to collapse
I use the method for eu that you posted. First i install magisk 25.2 and then i patch the rom boot.img. I boot to fastboot and flash the patch boot.img using the command. It flash successful then i reboot. But it still bootloop.
And for context, im using Eu weekly rom, not stable and twrp-3.7.0_12-v7.2_A13-venus-skkk.img for recovery. The recovery im using in eu rom forum method for installation.
martin132014 said:
Hi, sorry, but i bit confused about the method here. You mean to just patch either or both. This method is for fastboot or twrp. Sorry if im asking noob question.
Click to expand...
Click to collapse
All good say what you think!! not booth one of them boot.img or recovery.img!! you can flash zip via TWRP than you dont need other steps!!! you can install the Apk and Patch the Boot.img or recovery.img!!! than you can flash it in fastboot, twrp Image or twrp terminal!! choose your method
martin132014 said:
And for context, im using Eu weekly rom, not stable and twrp-3.7.0_12-v7.2_A13-venus-skkk.img for recovery. The recovery im using in eu rom forum method for installation.
Click to expand...
Click to collapse
and what your experience with that!!! Tell me why you like this!!!
System23 said:
All good say what you think!! not booth one of them boot.img or recovery.img!! you can flash zip via TWRP than you dont need other steps!!! you can install the Apk and Patch the Boot.img or recovery.img!!! than you can flash it in fastboot, twrp Image or twrp terminal!! choose your method
Click to expand...
Click to collapse
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
martin132014 said:
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
Click to expand...
Click to collapse
ok a Tip to you!!! when you only Backup Data Partition you can restore it and all Contacts,SMS,Accounts,Apps are availibile again on new ROM!!!
Why you dont use the Magisk.zip and flash it via TWRP after Flash ROM!!! you can rename Magisk.apk to Magisk.zip and flash it!! than you dont need other steps to Root!!! when it dosnt work use the recovery.img to Patch it and try this Method for Rooting, but dont forgett when ya do so you need to try the Buttons-Combo to start in Recovery to boot the System in Root and you have no Recovery-Mode at this Method!!! Also to use Recovery again you must Flash it again via Fastboot!!
And in TWRP use the WIPE Option to make a Factory Reset or WIPE a Single Partition, after some Flashing CROMS its needed to be WIPE the Data Partition!!!
martin132014 said:
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
Click to expand...
Click to collapse
you can ask me what you would i share my Informations with ya!!! when iam not knowing iam googleing it out to find a solution!! the talk we have start are hope helpfully!! when ya have intresst we can stay in kontakt and make what we can, even its public 4 all or PM!!! PS i must not hide my Knowledge, but PM its OK too!!!