Related
So my OP3 got bricked and I used @Naman Bhalla guide to unbrick my phone using the second method which flashes an old OOS after unbrick. I was successful in unbricking my phone, however once the phone restarts after the unbrick tool it gets stuck in the OOS boot animation (The rotating O animation) and then it reboots and this continues.
I've tried,
1) Sideloading another Stock ROM (OOS 5.0.1.) via stock recovery: Just rebricks my phone
2) Flashing TWRP 3.1.0-0 and tried to install zip for 5.0.1 : TWRP does't recognize phone, (ERROR 7, This ROM is for OnePlus 3, This device is " ") and thus it doesn't flash.
3) Tried upgrading TWRP to 3.2.1. : could'nt do it - Lost recovery, phone just restarts to a black screen with white notification light.
4) Tried flashing OOS 4.5.1 (Nougat) via TWRP 3.1.: Does't boot up. Doesn't even go to the animation and restarts after OnePlus Logo.
Yes, I was stupid enough to not have done a nandroid backup. Desperately need help.
yawarkhalid said:
So my OP3 got bricked and I used @Naman Bhalla guide to unbrick my phone using the second method which flashes an old OOS after unbrick. I was successful in unbricking my phone, however once the phone restarts after the unbrick tool it gets stuck in the OOS boot animation (The rotating O animation) and then it reboots and this continues.
I've tried,
1) Sideloading another Stock ROM (OOS 5.0.1.) via stock recovery: Just rebricks my phone
2) Flashing TWRP 3.1.0-0 and tried to install zip for 5.0.1 : TWRP does't recognize phone, (ERROR 7, This ROM is for OnePlus 3, This device is " ") and thus it doesn't flash.
3) Tried upgrading TWRP to 3.2.1. : could'nt do it - Lost recovery, phone just restarts to a black screen with white notification light.
4) Tried flashing OOS 4.5.1 (Nougat) via TWRP 3.1.: Does't boot up. Doesn't even go to the animation and restarts after OnePlus Logo.
Yes, I was stupid enough to not have done a nandroid backup. Desperately need help.
Click to expand...
Click to collapse
Try with eng.stk's TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Item 5 in the list.
tnsmani said:
Try with eng.stk's TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Item 5 in the list.
Click to expand...
Click to collapse
Gave this a shot. Not booting up again. Goes to blank screen with white notification light.
Update: I've even tried rooting phone and flashing custom rom: Doesn't even go to animation
I've also tried method 1, erased the system via fastboot and reflashed the official OOS 3.1.2. zip file via adb sideload. Still the same result on official zip.
yawarkhalid said:
Update: I've even tried rooting phone and flashing custom rom: Doesn't even go to animation
I've also tried method 1, erased the system via fastboot and reflashed the official OOS 3.1.2. zip file via adb sideload. Still the same result on official zip.
Click to expand...
Click to collapse
If Method 2 doesn't work, Method 1 will definitely not work.
After flashing TWRP, are you able to boot to it (without flashing any ROM)? Flashing OOS or Open Beta will overwrite TWRP. So try this: wipe everything and flash TWRP, boot to TWRP and flash ROM and again TWRP, then flash Magisk and boot to system.
When you get white LED, hold power button for 7 to 10 seconds, it will switch off. Then press power button again and you will boot to the options menu to choose bootloader, recovery etc. You may not have to use Method 2 every time if this works for you.
tnsmani said:
If Method 2 doesn't work, Method 1 will definitely not work.
After flashing TWRP, are you able to boot to it (without flashing any ROM)? Flashing OOS or Open Beta will overwrite TWRP. So try this: wipe everything and flash TWRP, boot to TWRP and flash ROM and again TWRP, then flash Magisk and boot to system.
When you get white LED, hold power button for 7 to 10 seconds, it will switch off. Then press power button again and you will boot to the options menu to choose bootloader, recovery etc. You may not have to use Method 2 every time if this works for you.
Click to expand...
Click to collapse
Hey thanks for the help. Will give this a shot now. Can you tell me what method I should use to flash magisk?
Also, I am able to access TWRP but when flashing a rom via TWRP it gives me error 7 i.e. can't install this since because it is for OnePlus 3 this device is " ". Also, with method 2 I already have a stock rom installed, I've tried wiping system via fastboot and sideloading another ROM too, that doesn't work.
yawarkhalid said:
Hey thanks for the help. Will give this a shot now. Can you tell me what method I should use to flash magisk?
Also, I am able to access TWRP but when flashing a rom via TWRP it gives me error 7 i.e. can't install this since because it is for OnePlus 3 this device is " ". Also, with method 2 I already have a stock rom installed, I've tried wiping system via fastboot and sideloading another ROM too, that doesn't work.
Click to expand...
Click to collapse
Magisk to be flashed through TWRP.
If you know how, remove this first line from the updater script and then flash it: getprop("ro.build.product") == "OnePlus3" || abort("This package is for "OnePlus3" devices; this is a "" + getprop("ro.build.product") + ""."); This is what is preventing TWRP from flashing the ROM. Removing this line will result in no checks for device type while flashing the ROM.
tnsmani said:
Magisk to be flashed through TWRP.
If you know how, remove this first line from the updater script and then flash it: getprop("ro.build.product") == "OnePlus3" || abort("This package is for "OnePlus3" devices; this is a "" + getprop("ro.build.product") + ""."); This is what is preventing TWRP from flashing the ROM. Removing this line will result in no checks for device type while flashing the ROM.
Click to expand...
Click to collapse
Hi, already did that, still is't flashing.
Lastly, I managed to lock my bootloader now somehow by running the 3.0.8 version of the MSMTool. Now I have no working OS, A locked bootloader and no way to flash TWRP. I should should throw my phone in the garbage now. Shouldnt I? :crying:
yawarkhalid said:
Hi, already did that, still is't flashing.
Lastly, I managed to lock my bootloader now somehow by running the 3.0.8 version of the MSMTool. Now I have no working OS, A locked bootloader and no way to flash TWRP. I should should throw my phone in the garbage now. Shouldnt I? :crying:
Click to expand...
Click to collapse
NEVER GIVE UP, atleast not so soon. Contact OnePlus and ask them for a remote session, they may be able to restore it.
Though you are not able to flash TWRP, you can boot TWRP by using the adb command "fastboot boot twrp.img" and then play with it. Place the TWRP within the adb folder while trying this. (Replace twrp.img with the name of your TWRP or rename your TWRP as twrp.img)
Either you have encryption issues or you have a hardware issue if you are not able to flash anything successfully.
This is the end of my knowledge.
Take a look here:
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
or here:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
jeffrey268 said:
Take a look here:
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
or here:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
Click to expand...
Click to collapse
ummm thanks jeffery. But that tool is exactly what i've been using and what isn't working for me in ways i mentioned above. Thanks though.
tnsmani said:
NEVER GIVE UP, atleast not so soon. Contact OnePlus and ask them for a remote session, they may be able to restore it.
Though you are not able to flash TWRP, you can boot TWRP by using the adb command "fastboot boot twrp.img" and then play with it. Place the TWRP within the adb folder while trying this. (Replace twrp.img with the name of your TWRP or rename your TWRP as twrp.img)
Either you have encryption issues or you have a hardware issue if you are not able to flash anything successfully.
This is the end of my knowledge.
Click to expand...
Click to collapse
Gives me the error, "Unlock device to use this command"
I am able to flash rom via MSMTool, it even dash charges and all. But I can't boot into the system. It gets stuck in OOS animation while booting. Been at it for 3 days. Can it really be a hardware issue if my bootloader and recovery both are working?
Lastly, do you have any way I could unlock the bootloader without system permissions?
Putting an end to this madness. after 4 days in front of my laptop. Had a remote session with a OnePlus tech support team. Discarding my phone unfortunately. Thinking of shifting to a Xiaomi Redmi Note 5 Pro since I can't afford a OnePlus 5T anymore. Thanks to everyone who helped. This thread can be closed now.
My bootloader is unlocked.
After installing PIE update to MIUI Global 10.3.1.0 Stable, when I try to boot OrangeFox recovery ver. R9.0-2 for Whyred using fastboot command "fastboot boot recovery.img" in CMD ( the result is shown below), the phone does NOT boot in OrangeFox recovery. It just remain stuck on MI logo after booting ...
C:\platform-tools>fastboot boot recovery.img
Downloading 'boot.img' OKAY [ 0.951s]
booting OKAY [ 0.157s]
Finished. Total time: 1.158s
Kindly advise on how to resolve the issue
Did you temporarily deactivate the Anti-Rollback-Feature with
>fastboot flash antirbpass dummy.img
where you will find the dummy.img in the official download of the Xiaomi firmware before trying to boot into recovery?
This needs to be done in the same fastboot-session that you want to boot into recovery.
NOTE 5 PRO Soft Bricked recovery bootLoop after MIUI Pie 10.3.1 Global Stable update
One more!! Hello i have a note 5 pro, yesterday it received automatic OTA update of miui 10.3.1.0.PEIMIXM with android 9.0, after install it soft bricked saying this miui version cant be installed on this device.
it lets me wipe data, which didnt help, also i connect with mi assistant using my pc suite nothing works, pc suite wont even recognize the phone on windows 10,.
PLEASE HELP! !
Kindly advise on how to resolve the issue[/QUOTE]
JosephusQuint said:
Did you temporarily deactivate the Anti-Rollback-Feature with
>fastboot flash antirbpass dummy.img
where you will find the dummy.img in the official download of the Xiaomi firmware before trying to boot into recovery?
This needs to be done in the same fastboot-session that you want to boot into recovery.
Click to expand...
Click to collapse
Many thanks for the advice. Worked like a charm. :good:
No, I did NOT deactivate the Anti-Rollback-Feature which was causing the problem.
In the past, whenever I installed custom recovery on my device including the first time, I did NOT have to flash dummy.img as my device booted into custom recovery without flashing dummy.img.
P.S.: I used dummy.img from this thread:
Everything About Anti Roll-back [Whyred]
ExoticPoint said:
One more!! Hello i have a note 5 pro, yesterday it received automatic OTA update of miui 10.3.1.0.PEIMIXM with android 9.0, after install it soft bricked saying this miui version cant be installed on this device.
it lets me wipe data, which didnt help, also i connect with mi assistant using my pc suite nothing works, pc suite wont even recognize the phone on windows 10,.
PLEASE HELP! !
Kindly advise on how to resolve the issue
Click to expand...
Click to collapse
ONLY IF you have Unlocked-Bootloader, then you can use this MIUI Flashing Guide- Method 2: Fastboot Update to unbrick your device.
Please carefully chose the firmware version (Global / India) to download the fastboot stock ROM for your device.
Lahoria said:
Many thanks for the advice. Worked like a charm. :good:
No, I did NOT deactivate the Anti-Rollback-Feature which was causing the problem.
In the past, whenever I installed custom recovery on my device including the first time, I did NOT have to flash dummy.img as my device booted into custom recovery without flashing dummy.img.
P.S.: I used dummy.img from this thread:
Everything About Anti Roll-back [Whyred]
Click to expand...
Click to collapse
Great that it solved your problem!
As addendum: The Anti-Rollback (afaik) has to be disabled every single time the recovery is changed/updated. This caught me off guard as I wanted to update TWRP from within the offical TWRP app. This failed and made my recovery unusable (Although I could still normally boot into system).
So let this be a cautionary tale to people.
I can't boot to my custom recovery in my redmi note 5. it is booting to the original recovery. I tried TWRP and REDWOLF recoveries . It will boot in the first time, then I reboot my phone after that when I reboot, it is booting to the original recovery. Same happened when I tried RED WOLf recovery. Pls help me.
Ayyappadas said:
I can't boot to my custom recovery in my redmi note 5. it is booting to the original recovery. I tried TWRP and REDWOLF recoveries . It will boot in the first time, then I reboot my phone after that when I reboot, it is booting to the original recovery. Same happened when I tried RED WOLf recovery. Pls help me.
Click to expand...
Click to collapse
After flash twrp, just flash magisk zip through twrp recovery...
So I've been following DavidRocher's tutorial to install a custom rom (the one that's linked around here the most), I've followed it before installing his RR official rom but as the room started showing a lot of issues, I decided to wipe everything and install something a little more stable such as lineage. I didn't care for Gcam or etc so I wouldn't have minded not having those at all.
However, even after following these steps now once again, even flashing the stock rom as asked for a brand new, clean install, twrp (offain) is hitting me with Error 1s on *any* custom rom that I try installing. I can seemingly flash the stock rom without any issues, but anything else and it's a solid no from TWRP.
Am I missing something?
The error itself is Error applying update: 28 (ErrorCode:: kDownloadOperationExecutionError) Updater process ended with Error: 1 error installing zip file.
I've been wiping, booting, rebooting, re-installing the custom rom, checking the unlocked bootloader and I have had no progress at all. I do not know why this is happening, could anyone please help me?
So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?
JumboTSB said:
So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?
Click to expand...
Click to collapse
Please can you describe exactly the steps that you did from boot to recovery and so?
SubwayChamp said:
Please can you describe exactly the steps that you did from boot to recovery and so?
Click to expand...
Click to collapse
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.
JumboTSB said:
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.
Click to expand...
Click to collapse
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.
SubwayChamp said:
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.
Click to expand...
Click to collapse
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.
JumboTSB said:
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.
Click to expand...
Click to collapse
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.
SubwayChamp said:
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.
Click to expand...
Click to collapse
I guess I'll try it with orange when I have a little more time then.. Spent the last 10-12 hours trying different procedures with twrp and they were pretty fruitless... It's still so weird, I'm definitely not new to flashing roms, I've done it so many times in the past and this is the very first time I get this sort of behavior. I'll update this once I try out OrangeFox.
hi!
your method has always worked for me, but this time I always get error 1.
I tried to install the pixel experience and lineage and nothing works, can you help me?
:good:
Hello,
I have a Poco F3 wanted to install a custom rom (i have bluetooth problem with Miui rom), but, to install TWRP, I made the mistake with this doing :
"fastboot flash recovery MyTWRP_File.img" :/
I read (too late) that ESPECIALLY we should not do this command on recent devices (with A / B partition) like Poco F3. With this device, we had to type this command :
"fasboot boot MyTWRP_File.img".
Result, I am unable to install the Gapps (including pico), I have an error 70 (not enough storage space available on the system partition).
I tried to do a lot of things and tutorials (formatting and reinstalling an official rom with Mi Flash to try to start from zero).
But my problem still persists, I cannot install Gapps because I have error 70.
Does anyone have a solution for me to fix my mistake?
Thanks in advance.
chtivain said:
Hello,
I have a Poco F3 wanted to install a custom rom (i have bluetooth problem with Miui rom), but, to install TWRP, I made the mistake with this doing :
"fastboot flash recovery MyTWRP_File.img" :/
I read (too late) that ESPECIALLY we should not do this command on recent devices (with A / B partition) like Poco F3. With this device, we had to type this command :
"fasboot boot MyTWRP_File.img".
Result, I am unable to install the Gapps (including pico), I have an error 70 (not enough storage space available on the system partition).
I tried to do a lot of things and tutorials (formatting and reinstalling an official rom with Mi Flash to try to start from zero).
But my problem still persists, I cannot install Gapps because I have error 70.
Does anyone have a solution for me to fix my mistake?
Thanks in advance.
Click to expand...
Click to collapse
Did "fastboot flash recovery MyTWRP_File.img" actually flash TWRP onto Recovery?
It's not your fault, because several websites (like Xiaomi.eu) still list this command, which is outdated, and many people get confused why that doesn't work, including me.
What Custom ROM are you using?
Flashing Stock ROM with Mi Flash wipes the entire phone, including Recovery. I don't know why you still get this error.
Are you sure that error is related to this? I think it may be something else... I mean you used Mi Flash.
Hi,
Currently, I am back under the stock rom of the Poco F3 (miui global 12.5.3), which I installed with miflash after doing a full wipe.
Before that, i tried the official roms of Lineage and ArrowOS.
with both rom i had the same problem. An error 70, when I flash the Gapps under their respective reecovery.
I tried with the twrp recovery, but I have the same problem
chtivain said:
Hi,
Currently, I am back under the stock rom of the Poco F3 (miui global 12.5.3), which I installed with miflash after doing a full wipe.
Before that, i tried the official roms of Lineage and ArrowOS.
with both rom i had the same problem. An error 70, when I flash the Gapps under their respective reecovery.
I tried with the twrp recovery, but I have the same problem
Click to expand...
Click to collapse
TWRP allows you to save Recovery log for further analysis. Can you upload it here?
dreamytom said:
TWRP allows you to save Recovery log for further analysis. Can you upload it here?
Click to expand...
Click to collapse
I'll put it tomorow (phone call => need to go to work now :/ ).
Did you solve the Problem? Because i got the Same Problem. No matter how i Install twrp. Using Fastboot Boot twrp.img, or flash Boot twrp.img. System Partition is to small and need to be resized.
Got the same thing, cannot Install GApps, errpr 70. What can I do?
I successfully unlocked my bootloader, then I tried flashing the twrp by following munchy's tutorial from YouTube (as someone recommended here). I also used the twrp recovery file he provided in the description, by using the latest platform tools from the official website. It was going pretty good. I even got the TeamWin logo, and also loaded up the twrp interface, and was able to navigate through it. But the problem was my internal storage wasn't showing up. So I booted back to my system normally to see If I can find a solution. Then I think I tried again after restarting to see if it fixes itself, but the same problem was persisting. The next time when I tried again, I used the latest twrp version which I downloaded from the official twrp website.
But since my 3rd attempt, I am not able to see any TeamWin recovery come up on my phone, when I connect I do the "fastboot boot (twrp filename)" command in cmd. When I do the command, nothing shows up. The device remains in the Fastboot mode, or just turns off. When I switch it back on, It turns on normally and boots into the phone without any issues, and I can use it. I've tried switching back to the original twrp version munchy used in the above linked video, but same result.
What did I do wrong here? How do I make my phone get into the twrp recovery when I enter the fastboot boot (twrp filename) command thru my PC? How do I make my Internal Storage available to view int he TWRP recovery so I can install it from my Downloads folder? I am on MIUI 14.0.4 If that helps. My end goal is to install Magisk.
Any tips/guides/suggestions are appreciated.
Installing TWRP and root does not erase your data.
Remove security from the lock screen. (decryption).Normally the latest TWRP decrypts the data.
Install Platform tools ,put the TWRP in the folder and run the commands from the folder.
TWRP SKK, Use A12 if your system is in A12/A13 if system A13.
Rename it to twrp.img
CMD
fastboot boot twrp.img
Powershell
./fastboot boot twrp.img
Once booted, go to Advanced -> Press "Flash current TWRP"
If offered, both slots.
NOSS8 said:
Installing TWRP and root does not erase your data.
Remove security from the lock screen. (decryption).Normally the latest TWRP decrypts the data.
Install Platform tools ,put the TWRP in the folder and run the commands from the folder.
TWRP SKK, Use A12 if your system is in A12/A13 if system A13.
Rename it to twrp.img
CMD
fastboot boot twrp.img
Powershell
./fastboot boot twrp.img
Once booted, go to Advanced -> Press "Flash current TWRP"
If offered, both slots.
Click to expand...
Click to collapse
Thank you. I had put backed the screen lock after the first 2 attempts because someone said to to that on a YT video after they faced the same problem. Now I tried again by removing the screen lock and the latest twrp for my device also boots up just fine. Now the problem Is I still can't access my internal storage .
Still having removed the screen security?
Which rom(fullname)?
Which TWRP?
Try to mount storage.
NOSS8 said:
Still having removed the screen security?
Which rom(fullname)?
Which TWRP?
Click to expand...
Click to collapse
Yes, I removed the screen security, though I can enter TWRP, I can't read the internal storage. MIUI 14.0.4.
I just watched a YT video where the dude does the following:
-TWRP Recovery
- Wipe
- Format Data
- Types 'yes'
then
-TWRP Recovery
- Reboot
- Recovery
- Do not Install
After coming back to recovery after rebooting, he gets a pop up, which at the swipe says "Swipe to allow for modifications" which he swipes, then now after checking the Internal Storage, It's readable now. Is this a possible solution?
Twrp A13, obviously if you don't want to keep the data.
Twrp/wipe format data type yes/reboot TWRP.
If error red lines, reboot TWRP and repeat the operation.
Sideload roms or use OTG.
NOSS8 said:
Twrp A13, obviously if you don't want to keep the data.
Twrp/wipe format data type yes/reboot TWRP.
If error red lines, reboot TWRP and repeat the operation.
Sideload roms or use OTG.
Click to expand...
Click to collapse
what's twrp A13? Also, I just unlocked my bootloader a few hours ago, so my phone has already done a factory reset and i don't have anything to lose except the Magisk APK and .img file in my phone.
But I have a question, will doing the format data just do a factory reset, or will I lose my ROM? Because I'm not trying to install a custom ROM, I just want to Install Magisk as the end goal with my current ROM.
MIUI 14 Android 13 so use this TWRP
plugged the phone into the PC when it is on the TWRP, you will have access to the internal storage. (works on my 12 pro aves twrp A13 Skk).
twrp-3.7.0_12-v7.5_A13-alioth-skkk.img
I'm using the latest one I could find on the TWRP website for my device. Not aware If it supports Android 13 though as it isn't mentioned on the website. Just asking my prev question, will doing the format data from TWRP just do a factory reset, or do I lose the ROM and will have to install a custom ROM?
second question I forgot to ask in my prev post, after i do the format data and put the Magisk APK and twrp img file again on my device, will my device stay decrypted as I formatted the data, or will the problem persist?
sorry If i sound dumb
zoinksy said:
I'm using the latest one I could find on the TWRP website for my device. Not aware If it supports Android 13 though as it isn't mentioned on the website. Just asking my prev question, will doing the format data from TWRP just do a factory reset, or do I lose the ROM and will have to install a custom ROM?
second question I forgot to ask in my prev post, after i do the format data and put the Magisk APK and twrp img file again on my device, will my device stay decrypted as I formatted the data, or will the problem persist?
sorry If i sound dumb
Click to expand...
Click to collapse
Use this TWRP(officiel).
twrp-3.7.0_12-v7.5_A13-alioth-skkk.img
thank you, this is the one I was looking for. Sorry to bother you again, now I installed the Magisk V26.1 apk from TWRP. And when I boot back to system and try opening the magisk manager, this happens. It says downloading, forever. I think I shouldn't have directly downloaded the latest version. So probably have to downgrade it a bit. For that, what will I have to do?
Can I just hold the Magisk icon, and uninstall it simply like any other app? Or do I have to do it from the TWRP? Also, Is it necessary for me to uninstall it before downgrading, or can I just download the apk of older magisk version and flash it from twrp just like I did previously?
It was on my first post.
Installation
The Magic Mask for Android
topjohnwu.github.io
TWRP + Root
Hi all. Hope you are good and safe from Covid-19. If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP...
forum.xda-developers.com
Try OrangeFox. I never had problems with it. Been using it for half a year and constantly flash new ROM builds as a tester
Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth)
orangefox.download
cyanGalaxy said:
Try OrangeFox. I never had problems with it. Been using it for half a year and constantly flash new ROM builds as a tester
Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth)
orangefox.download
Click to expand...
Click to collapse
Sure, but currently only in A12.
NOSS8 said:
Sure, but currently only in A12.
Click to expand...
Click to collapse
I use ArrowOS 13
cyanGalaxy said:
I use ArrowOS 13
Click to expand...
Click to collapse
I don't doubt it, the Twrp A12 also works for certain operations on an A13 system but for certain Miui roms some bootloop.
NOSS8 said:
I don't doubt it, the Twrp A12 also works for certain operations on an A13 system but for certain Miui roms some bootloop.
Click to expand...
Click to collapse
Hm ok.
Welp for me on AOSP, it works nicely. I flash a new build (or two) every week. Backup/Restore works as should. UI is nice and modern, imo better than TWRP. That's why I'm recommending it.
Haven't heard anyone saying that they can't view Phone storage on OrangeFox.
Hi,
@NOSS8 , I'd like to ask : I've only some hours to wait to unlock the BL. But one question, as it's yet the stock rom (FW V13.0.11.0, A12), wich twrp should I use ? I want to install a A13 rom (that supposes FW V 14.xxx !)
So :
- fastboot boot twrp (but wich one ?? A12 or 13 ?? ; skkk ? Or ?) (+ "flash current twrp" OR "install it in ramdisk"?)
- reboot recovery
- flash FW V14.xxx
- flash rom
- format data
- reboot system
- flash magisk (last version ? Seems to be 'big' changes ?)
- flash what I need (V4A, DFE (??), ....)
What do you think ?
Thanks a lot ! Main question is about what version of twrp.. Help will be very appreciated !
néonaloj said:
Hi,
@NOSS8 , I'd like to ask : I've only some hours to wait to unlock the BL. But one question, as it's yet the stock rom (FW V13.0.11.0, A12), wich twrp should I use ? I want to install a A13 rom (that supposes FW V 14.xxx !)
So :
- fastboot boot twrp (but wich one ?? A12 or 13 ?? ; skkk ? Or ?) (+ "flash current twrp" OR "install it in ramdisk"?)
- reboot recovery
- flash FW V14.xxx
- flash rom
- format data
- reboot system
- flash magisk (last version ? Seems to be 'big' changes ?)
- flash what I need (V4A, DFE (??), ....)
What do you think ?
Thanks a lot ! Main question is about what version of twrp.. Help will be very appreciated !
Click to expand...
Click to collapse
Instead, use Miflash with a Fastboot rom, you can extract the boot img for root.(don't re lock the bootloader).
You can root without TWRP, but according to this thread, if you root you lose the TWRP and vice versa, I don't know if this is still relevant.(I don't have this device).
If you need ,install the TWRP A13 after flashing the A13.
See this thread for instructions
[Recovery] [13] [12] TWRP & OrangeFox
Since recoveries play a crucial role in flashing firmwares, custom ROMs and offline updates, it is of importance to have access to them. This post is about sources and instructions to working versions of recoveries for Alioth. Platform Tools (aka...
forum.xda-developers.com
***Note:
Use the TWRP SKKK.
Advantage with Miflash, the Fastboot roms contain all the imgs.
EDIT:
omitted link
TWRP + Root
Hi all. Hope you are good and safe from Covid-19. If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP...
forum.xda-developers.com
NOSS8 said:
Instead, use Miflash with a Fastboot rom, you can extract the boot img for root.(don't re lock the bootloader).
You can root without TWRP, but according to this thread, if you root you lose the TWRP and vice versa, I don't know if this is still relevant.(I don't have this device).
If you need install the TWRP A13 after flashing the A13.
See this thread for instructions
[Recovery] [13] [12] TWRP & OrangeFox
Since recoveries play a crucial role in flashing firmwares, custom ROMs and offline updates, it is of importance to have access to them. This post is about sources and instructions to working versions of recoveries for Alioth. Platform Tools (aka...
forum.xda-developers.com
***Note:
Use the TWRP SKKK.
Advantage with Miflash, the Fastboot roms contain all the imgs.
Click to expand...
Click to collapse
I'm very greatfull for your quick reply ! Thanks
The device is too a Poco f3, sorry.. This doesn't need to flash magisk for twrp to stick (I had another one I've broken)
But I don't understand what's the advantage to first flash a fastboot rom..? As you say to flash twrp would loose root and vice versa... (I've read the thread you're talking about ofox)
So I wanted to go trough +- the way I mentionned, as A13 as well as ofox 'seems' to work (but I'm carefull with that twrp on stock MIUI A12, and I never used ofox..)
So you do think it's a bad idea ?? The rom I want to flash is crdroid.
I'm more lost now ...
Thanks again !