Related
Hey guys, I'm having a problem.
I've installed the Miui 10 8.7.12 Global Beta and all is well, however i want to install TWRP so I can root and uninstall some Xiaomi apps still on the phone. However whenever I try to install TWRP via fastboot there are a few problems I face.
1) I flash twrp.img and its fine then I do fastboot reboot with volume up + power to go into recovery, but instead of taking me to TWRP, or even the stock recovery it keeps going back into fastboot mode.
2) When I try another method with adb reboot recovery it says device not found
3) If I try and directly go into recovery with fastboot boot twrp.img it restarts the phone and goes into the mi screen and nothing happens from there.
I've tried every possible combination I can think of and made sure I downloaded the proper TWRP from the official website and it still isn't working. Any input?
*EDIT*
I managed to figure it out! SORRY!!! Delete pls!
What was the problem?
how you solved ?
you got the anti rollback ?
You should boot phone with twrp.img like this. Don't reboot.
fastboot boot twrp.img
Then format data.
achfighter said:
You should boot phone with twrp.img like this. Don't reboot.
fastboot boot twrp.img
Then format data.
Click to expand...
Click to collapse
it works! thanks
achfighter said:
You should boot phone with twrp.img like this. Don't reboot.
fastboot boot twrp.img
Then format data.
Click to expand...
Click to collapse
really helpfull i was looking several days and didnt found, thanks
Quote:
Originally Posted by achfighter
You should boot phone with twrp.img like this. Don't reboot.
fastboot boot twrp.img
Then format data.
can i do this method without format data ?
I did it and I just got a: "The system has been destroyed" !!!! ¬_¬ -_-
achfighter said:
You should boot phone with twrp.img like this. Don't reboot.
fastboot boot twrp.img
Then format data.
Click to expand...
Click to collapse
syaren said:
Quote:
Originally Posted by achfighter
You should boot phone with twrp.img like this. Don't reboot.
fastboot boot twrp.img
Then format data.
can i do this method without format data ?
Click to expand...
Click to collapse
If you didn't format data, firmware may reinstall stock recovery after reboot.
Blue line, redline twrp blanck screen
Hi guys after installing miui pro miui 10 Oreo , my twrp become blank screen , i try to install using cmd , and i try to boot using cmd also didn't work , help me this .
I have managed till installing twrp, however it seems like all the downloaded rom files and decrypt.zip are encrypted. I tried to copy 'em to the internal storage again but as I boot to twrp it again goes to encrypted mode. In Twrp, I tried to enable the MTP and copy files directly but it always fails. How do I go from here?? Please help!
Phone : MI mix 2
bootloader : unlocked
Twrp : installed
Twrp variant: Dwight twrp
Rom : Pixel Experience/ RR/ HAVOC etc
Use orange twrp
KaptanHarlock said:
Use orange twrp
Click to expand...
Click to collapse
orange twrp ? could you tell me where can I get it?
My 2 cents:
If you can still boot whatever OS you have right now, back up things you need (including internal storage), then format /data. Reboot into recovery and flash whatever you want, optionally DecScript to switch to unencrypted data after next boot. OrangeFox recovery is not necessary but its UI could be seen as intuitive to some.
AndyYan said:
My 2 cents:
If you can still boot whatever.... .
Click to expand...
Click to collapse
I can boot in Twrp and Miui10 OS too. I want to install custom rom, but the rom.zip files turns out encrypted when booting up in Twrp. while being in Twrp I tried to transfer " unencrypted rom.zip " files in my PC to internal storage to flash it but I can't transfer it even after enabling MTp in Twrp.
How do I install the rom is my problem. Shall I wipe data, cache? and then how?
xdasith said:
I can boot in Twrp and Miui10 OS too. I want to install custom rom, but the rom.zip files turns out encrypted when booting up in Twrp. while being in Twrp I tried to transfer " unencrypted rom.zip " files in my PC to internal storage to flash it but I can't transfer it even after enabling MTp in Twrp.
How do I install the rom is my problem. Shall I wipe data, cache? and then how?
Click to expand...
Click to collapse
So you're seeing the storage as encrypted (garbled content)? I never actually used encrypted data so I don't know for sure, but Wight's TWRP might not be able to decrypt MIUI's /data, so IMO you do need to format (not wipe) /data. You might also need to reboot to recovery once after that, so that the storage is recognized properly by PC.
..d properly by PC.[/QUOTE said:
Thanks. ok I will factory reset the phone reboot to twrp. Im using Mi phone for the first time, so i was scared that might locked the bootloader again. it wont relock the bootloader would it? guess im asking too many stupid questions. I never had to go thru this kinda situation on my samsung devices. Thanks for helping
Click to expand...
Click to collapse
AndyYan said:
So you'... C.
Click to expand...
Click to collapse
still not working. I wonder how people are installing Roms when you are booting in Twrp and finding everything encrypted.
xdasith said:
still not working. I wonder how people are installing Roms when you are booting in Twrp and finding everything encrypted.
Click to expand...
Click to collapse
Boot into TWRP and select Wipe and then Select the Format Data button.
Make sure you're not sliding to factory reset or advance wiping.
NOTE: This will erase all the information from the phone including internal storage. Make a backup prior this process.
After you're done, you can connect the phone to a PC while on TWRP to copy the rom zip files to internal storage and flash them. A backup from TWRP is highly recommended just in case.
xdasith said:
still not working. I wonder how people are installing Roms when you are booting in Twrp and finding everything encrypted.
Click to expand...
Click to collapse
Emphasis on "format (not wipe)"... Lester already made it clear for you.
lester0310 said:
Boot into TWRP and......
Click to expand...
Click to collapse
thanks. I'll do that as soon as I reach home. I'll let you know the progress. I hope everything works well.
AndyYan said:
Emphasis on "format (not wipe)"... Lester already made it clear for you.
Click to expand...
Click to collapse
Ok. Now I got it. I'll do that n will let you know. Thanks again. Can't wait to try the rom. I'll drop some "beer" coins in ROM's donate account soon. Hope the link works.
AndyYan said:
Emphasis on "format (not wipe)"... Lester already made it clear for you.
Click to expand...
Click to collapse
Thanks for the help. I'll drop some beer coins at your rom's Donate link soon
xdasith said:
I have managed till installing twrp..c
Click to expand...
Click to collapse
Hey! It works! I'm enjoying LOS16 on mi mix 2.
My problems :
1. Booting to Recovery Twrp :
only thru fastboot mode > fastboot boot twrp.img, Mi inbuilt recovery prevent me to boot to twrp.
Is there any way to go to twrp by just pressing buttons?
2. Flashing magisk/Universal_Decrypt.Zip Bootloops
xdasith said:
Hey! It works! I'm enjoying LOS16 on mi mix 2.
My problems :
1. Booting to Recovery Twrp :
only thru fastboot mode > fastboot boot twrp.img, Mi inbuilt recovery prevent me to boot to twrp.
Is there any way to go to twrp by just pressing buttons?
2. Flashing magisk/Universal_Decrypt.Zip Bootloops
Click to expand...
Click to collapse
Both work fine on my side so I'm assuming there's still something wrong with your setup, but on the other hand I don't really have a clue...
xdasith said:
Hey! It works! I'm enjoying LOS16 on mi mix 2.
My problems :
1. Booting to Recovery Twrp :
only thru fastboot mode > fastboot boot twrp.img, Mi inbuilt recovery prevent me to boot to twrp.
Is there any way to go to twrp by just pressing buttons?
2. Flashing magisk/Universal_Decrypt.Zip Bootloops
Click to expand...
Click to collapse
1- There are multiples ways to reboot to recovery:
Buttons combination: Turn the phone off and press Power + Volume Down and it will boot to recovery.
Apps (root required): There are multiples apps that has a option to reboot to recovery directly. Search something like advance reboot on Play Store.
adb (USB debugging required): Running the command "adb reboot recovery" from terminal will reboot the phone into recovery.
2- To flash magisk, first flash the rom and gapps and reboot to system, finish the initial setup and then reboot to recovery and flash the magisk zip file. Next reboot will take a few minutes.
Edit: The universal decrypt file is not necessary since the data partition is no longer encrypted.
lester0310 said:
1- There are multiples ways to reboot to recovery:
Buttons combination: Turn the phone off and press Power +...
Edit: The universal decrypt file is not necessary since the data partition is no longer encrypted.
Click to expand...
Click to collapse
Yes i agree. The thing is Mi has its own recovery, thats preventing me from going to twrp directly, (even though) twrp is properly installed. if i press the button combination it will go to the "Miui inbuilt recovery" Not to twrp. so i go the fastboot mode and boot to Twrp recovery thru adb command. If only I could suppress inbuilt recovery and boot to twrp recovery it would be great. Apps like "boot to recovery" only initiate booting in recovery. It fails to choose Twrp because there are two recovery inside.
In my previous devices, honor 8pro n Samsung 8+ this wasnt an issue. But with Mi phone...
Does yours boots to Twrp directly with the button combination?
xdasith said:
Yes i agree. The thing is Mi has its own recovery, thats preventing me from going to twrp directly, (even though) twrp is properly installed. if i press the button combination it will go to the "Miui inbuilt recovery" Not to twrp. so i go the fastboot mode and boot to Twrp recovery thru adb command. If only I could suppress inbuilt recovery and boot to twrp recovery it would be great. Apps like "boot to recovery" only initiate booting in recovery. It fails to choose Twrp because there are two recovery inside.
In my previous devices, honor 8pro n Samsung 8+ this wasnt an issue. But with Mi phone...
Does yours boots to Twrp directly with the button combination?
Click to expand...
Click to collapse
That's means that the TWRP recovery is not installed, there's is just one recovery partition and only one can be installed at the same time.
From fastboot mode run "fastboot flash recovery twrp.img"
That will replace the stock recovery and you will be able to boot to twrp with the button combination and any other app running the reboot recovery command.
lester0310 said:
That's means that the TWRP recovery is not installed, there's is just one recovery partition and only one can be installed at the same time.
From fastboot mode run "fastboot flash recovery twrp.img"
That will replace the stock recovery and you will be able to boot to twrp with the button combination and any other app running the reboot recovery command.
Click to expand...
Click to collapse
I installed Twrp with that command only once. After that, i have been using "fastboot boot twrp.img" only to boot in twrp.
Ok ill try reflashing twrp again with "fastboot flash recovery twrp.img"
xdasith said:
I can boot in Twrp and Miui10 OS too. I want to install custom rom, but the rom.zip files turns out encrypted when booting up in Twrp. while being in Twrp I tried to transfer " unencrypted rom.zip " files in my PC to internal storage to flash it but I can't transfer it even after enabling MTp in Twrp.
How do I install the rom is my problem. Shall I wipe data, cache? and then how?
Click to expand...
Click to collapse
Just remove lockscreen protection before rebooting into recovery. You will be fine. Do this before everytime you want something done in TWRP. You won't have to format DATA partition everytime. TWRP will decrypt with default password and you'll be good. I have moved between MIUI 10 and pie roms without trouble this way.
---------- Post added at 05:32 PM ---------- Previous post was at 05:31 PM ----------
xdasith said:
I installed Twrp with that command only once. After that, i have been using "fastboot boot twrp.img" only to boot in twrp.
Ok ill try reflashing twrp again with "fastboot flash recovery twrp.img"
Click to expand...
Click to collapse
You can just use power + volume up combo to get into TWRP recovery. You don't basically need to fastboot for recovery after it's installed.
I'm not sure which $400 lesson I learned today other than a bundle of humility.
my device is bootloader unlockable.
I'm clearly not properly prepared for this. I flashed the most recent factory android 9 using google's windows batch file. I'm using the latest adb/fastboot as install by Chocolatey. The plan was to flash this v9 base ROM.
installed twrp xda-developers.com /google-pixel-3-unlock-bootloader-root-magisk/
yes: Backup each and every partition from TWRP Recovery
yes, from twrp: Make a full wipe (system, data, cache, dalvik)
yes, from twrp: Flash [ROM][9.0.0_r46] AospExtended ROM V6.7 [OFFICIAL]
for some reason I believed using twrp meant it was installed, so no: Flash TWRP
yes: Reboot to recovery
yes, from twrp: Wipe data (if clean flash or first install)
yes, from twrp: Flash magisk
yes: Reboot to system
uh oh
sleepy robot
"no command"
Power + up
reboot
white screen with google logo briefly appears on screen
sleepy robot
"no command"
power + up
reboot recovery
boot twrp img
all the files I had pushed are gone and no option to push them again
adb sideload twrp img & twrp install zip
Here's where I think it goes very wrong for me
When I go to reboot to system I see B selected. I thought I was working on A.
so I switched to A
reboot
black screen
never flickers, unresponsive to buttons
brick?
That was fun.
For my next $400 how do I ensure everything I need is flashed BOTH to A & B?
So you can get into recovery? Hardly a brick then. Flash an official image in fastboot or recovery
That's my bad for not filling in the timeline better
so I switched to A
reboot
black screen
never flickers, unresponsive to buttons
brick?
Click to expand...
Click to collapse
no, I could get into recovery. After switching to A it is a brick. Doesn't respond to power button, power+up, power+up+down. It is still on as it's warm, but I'm waiting for the battery to die
fastboot is "waiting" for devices
How would I have used google flash-all _before_ installing TWRP to flash-all A and flash-all B? And then TWRP to flash A and flash B with the ROM? Are those the steps I should have followed so that A or B would boot to correct ROM?
nay_ said:
That's my bad for not filling in the timeline better
no, I could get into recovery. After switching to A it is a brick. Doesn't respond to power button, power+up, power+up+down. It is still on as it's warm, but I'm waiting for the battery to die
fastboot is "waiting" for devices
How would I have used google flash-all _before_ installing TWRP to flash-all A and flash-all B? And then TWRP to flash A and flash B with the ROM? Are those the steps I should have followed so that A or B would boot to correct ROM?
Click to expand...
Click to collapse
Hmmm is it recognized by your computer at all under device manager or does it say qcomm 9005 or something along those lines?
If the recovery is functioning, you could sideload an OTA image from Google. That cleans the phone and reflashes everything.
P.S: Chheck my PM
Hi,
I attempted to flash ArrowOS for my Poco F3 2 days ago but I didn't follow the steps correctly. My plan was to unlock bootloader, boot twrp and install ArrowOS. After I tried this, the ArrowOS loadup screen kept on loading for a hour. I rebooted the device and ended up in the ArrowOS recovery. After some times, I tried to flash the MIUI fastboot rom with Mi Flash Tool and I think I chose "clean all and lock." This caused a problem because I became stuck on the fastboot page and when I tried to reboot, it would go to the Poco startup page briefly before jumping back to the fastboot. I've tried to hold the power button and the volume keys but it has no effect. Also, on the Poco page there was no unlocked padlock which was weird because when I first tried to flash ArrowOS I could see the unlocked padlock. When I checked on my computer using Mi Unlock, it showed that my device was unlocked.
I think I did manage to flash fastboot rom for MIUI using XiaomiToolV2 because it said that the installation was complete.
Another problem is that when I boot TWRP with fastboot from my computer, there isn't any internal storage shown after I click the install button. I think this is because I wiped the device with TWRP when I was following various tutorials. When I try to add a file to the internal storage from my computer it shows an empty folder and any files I copy into it isn't shown.
I would be really grateful for any help as I've been trying to fix this problem for 2 days now. Thank you!
I've attached a video of the phone being stuck on fastboot.
12839172398 said:
Hi,
I attempted to flash ArrowOS for my Poco F3 2 days ago but I didn't follow the steps correctly. My plan was to unlock bootloader, boot twrp and install ArrowOS. After I tried this, the ArrowOS loadup screen kept on loading for a hour. I rebooted the device and ended up in the ArrowOS recovery. After some times, I tried to flash the MIUI fastboot rom with Mi Flash Tool and I think I chose "clean all and lock." This caused a problem because I became stuck on the fastboot page and when I tried to reboot, it would go to the Poco startup page briefly before jumping back to the fastboot. I've tried to hold the power button and the volume keys but it has no effect. Also, on the Poco page there was no unlocked padlock which was weird because when I first tried to flash ArrowOS I could see the unlocked padlock. When I checked on my computer using Mi Unlock, it showed that my device was unlocked.
I think I did manage to flash fastboot rom for MIUI using XiaomiToolV2 because it said that the installation was complete.
Another problem is that when I boot TWRP with fastboot from my computer, there isn't any internal storage shown after I click the install button. I think this is because I wiped the device with TWRP when I was following various tutorials. When I try to add a file to the internal storage from my computer it shows an empty folder and any files I copy into it isn't shown.
I would be really grateful for any help as I've been trying to fix this problem for 2 days now. Thank you!
I've attached a video of the phone being stuck on fastboot.
Click to expand...
Click to collapse
Well I don't own that phone but it sounds like you didn't unlock the bootloader properly and your internal storage is encrypted that's why it shows 0 and that's probably why your having problems. Is there an encryption disabler zip? Your supposed to format data and flash an encryption disabler and than magisk v23 on Samsung devices than boot.
Okay, so I've just used the Format Data option in TWRP which says it will remove encryption on internal storage. But this didn't seem to fix any problems
12839172398 said:
Okay, so I've just used the Format Data option in TWRP which says it will remove encryption on internal storage. But this didn't seem to fix any problems
Click to expand...
Click to collapse
Did you flash a disabler zip? Also is your bootloader locked?
No, I haven't flashed a disabler zip. Where would I download that. I found a XDA download called Xposed-Disabler-Recovery.zip, would that be it.
My bootloader was unlocked and the Mi Unlock tool still says that it is unlocked, but I don't see an unlocked padlock on the start up page.
12839172398 said:
Okay, so I've just used the Format Data option in TWRP which says it will remove encryption on internal storage. But this didn't seem to fix any problems
Click to expand...
Click to collapse
Did you follow the directions on Xda
INSTALLATION PROCEDURE:
First installation (Clean flash):
You need adb/fastboot tools.
Download boot, vendor_boot and rom zip:
boot_alioth.img
drive.google.com
vendor_boot_alioth.img
drive.google.com
ArrowOS - Downloads
Reboot in fastboot. Flash boot and vendor_boot:
fastboot flash boot_ab boot_alioth.img
fastboot flash vendor_boot_ab vendor_boot_alioth.img
fastboot --set-active=a
Reboot in ArrowOS Recovery:
fastboot reboot recovery
Make format data (Factory reset -> Format data).
Flash ROM (Apply update -> Apply from ADB):
adb sideload name.zip
If you want install separate gapps on vanilla buildtype, after flash ROM:
Advanced -> Reboot to recovery
Flash gapps (Apply update -> Apply from ADB):
adb sideload name.zip
Follow what show on device, should be ... Step 1/2 -> 2/2, then flashing ended, can reboot device in system. (on command line can show "(~47%) adb: failed to read command: No error", it normal!)
________________________________________
Install Update (dirty flash):
Go in Settings -> System -> Updater
Downlad new build -> Install
12839172398 said:
No, I haven't flashed a disabler zip. Where would I download that. I found a XDA download called Xposed-Disabler-Recovery.zip, would that be it.
My bootloader was unlocked and the Mi Unlock tool still says that it is unlocked, but I don't see an unlocked padlock on the start up page.
Click to expand...
Click to collapse
sounds like you have indeed locked your bootloader. you can check using fastboot cmd 'fastboot oem device-info'
if it's locked, only thing to do i would guess is to try and flash stock rom (not EU custom rom) and hope for the best, then try to unlock your bl again
12839172398 said:
No, I haven't flashed a disabler zip. Where would I download that. I found a XDA download called Xposed-Disabler-Recovery.zip, would that be it.
My bootloader was unlocked and the Mi Unlock tool still says that it is unlocked, but I don't see an unlocked padlock on the start up page.
Click to expand...
Click to collapse
Also twrp instructions
Installation:
1. fastboot boot twrp.img
2. copy that same twrp image to the device
3. go to Advanced > Install Recovery Ramdisk
4. select the image you copied
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
7. reboot to recovery, you should now be able to boot TWRP normally using Power+volume up
repeat step 3 and 4 directly after flashing a new rom, then reboot recovery to flash additional stuff
also, if your bl is indeed locked i for sure recommend you HALT all attempts at flashing twrp or any custom rom. you need to focus on trying to get stock fw back on the device and booting
WOW! Thank you guys so much for your help! My bootloader was indeed unlocked and I proceeded with the steps by Techguy777 and it worked perfectly! I now have ArrowOS booting up and I cannot thank you guys enough. I hope you have a great day!
Also I haven't installed TWRP; Should I install TWRP? Or is ArrowOS Recovery sufficient
12839172398 said:
Also I haven't installed TWRP; Should I install TWRP? Or is ArrowOS Recovery sufficient
Click to expand...
Click to collapse
Just use arrowos recovery... Doesnt really matter unless u switch around several roms
12839172398 said:
WOW! Thank you guys so much for your help! My bootloader was indeed unlocked and I proceeded with the steps by Techguy777 and it worked perfectly! I now have ArrowOS booting up and I cannot thank you guys enough. I hope you have a great day!
Click to expand...
Click to collapse
enjoy the ArrowOS, it is way better than MIUI. I am loving it since i flashed it 2 days ago!
Wow, if you chose flash and lock like you mention in 1st post and somehow your device remained unlocked, you sir are very lucky!! Glad it's all up and running. Fck knows how it stayed unlocked, but thankfully it did
I was on C.62 AA with a working Magisk.
Yesterday I tried to update to C.63 AA with following steps:
1. Disable all Magisk module and reboot.
2. Restore Stock Image from Magisk Manager.
3. Update to C.63 from System Settings menu.
4. Install Magisk to inactive slot, then reboot.
That's it.
After reboot, my OP9P starts, but can't get into lock screen. Instead it only show black screen with a nonstop vibration.
I didn't do backup since I was NOT expecting this to happen.
Now I'm desperate for any help to unbick it or at lease get my files in sdcard back.
I can go into bootloader and fastbootd mode. ANY help would be much appreciated.
dna1982 said:
I was on C.62 AA with a working Magisk.
Yesterday I tried to update to C.63 AA with following steps:
1. Disable all Magisk module and reboot.
2. Restore Stock Image from Magisk Manager.
3. Update to C.63 from System Settings menu.
4. Install Magisk to inactive slot, then reboot.
That's it.
After reboot, my OP9P starts, but can't get into lock screen. Instead it only show black screen with a nonstop vibration.
I didn't do backup since I was NOT expecting this to happen.
Now I'm desperate for any help to unbick it or at lease get my files in sdcard back.
I can go into bootloader and fastbootd mode. ANY help would be much appreciated.
Click to expand...
Click to collapse
Unfortunately the only thing that's going to get device up and going again is msm or factory reset. You could possibly get a boot without wiping if you have untouched boot images of build you were on but then you don't know which side it booted to. I'd factory reset . Or keep device dead. You will still have patched boot.img so just reinstall magisk manager after reset.
mattie_49 said:
Unfortunately the only thing that's going to get device up and going again is msm or factory reset. You could possibly get a boot without wiping if you have untouched boot images of build you were on but then you don't know which side it booted to. I'd factory reset . Or keep device dead. You will still have patched boot.img so just reinstall magisk manager after reset.
Click to expand...
Click to collapse
I do have untouched boot images(C.63 AA) from the other thread.
I did try to "fastboot boot boot.img", result the same -- black screen with a nonstop vibration.
I think something went wrong during the update process.
Maybe flashing a stock rom in fastboot mode will help, but I don't know how and I can't find any info about howto flash OxygenOS 12 in fastboot on OP9P.
what you can try is the c63 full rom via fastbootd with the tool Fastboot Enhance to flash
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
forum.xda-developers.com
but that will be difficult because there is no aa full rom (only india) since the update to c63 was only released globally as an incremental update
ChrisFeiveel84 said:
what you can try is the c63 full rom via fastbootd with the tool Fastboot Enhance to flash
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
forum.xda-developers.com
Click to expand...
Click to collapse
ChrisFeiveel84 said:
but that will be difficult because there is no aa full rom (only india) since the update to c63 was only released globally as an incremental update
Click to expand...
Click to collapse
The Fastboot Enhance Tool you post does look promising.
I guess I will just wait for AA full rom to come out.
Thank you.
dna1982 said:
The Fastboot Enhance Tool you post does look promising.
I guess I will just wait for AA full rom to come out.
Thank you.
Click to expand...
Click to collapse
Last full rom for aa is
C48
I don't think that oneplus will release a full aa again
ChrisFeiveel84 said:
Last full rom for aa is
C48
I don't think that oneplus will release a full aa again
Click to expand...
Click to collapse
I will wait a week or two before flash DA C.63.
dna1982 said:
I do have untouched boot images(C.63 AA) from the other thread.
I did try to "fastboot boot boot.img", result the same -- black screen with a nonstop vibration.
I think something went wrong during the update process.
Maybe flashing a stock rom in fastboot mode will help, but I don't know how and I can't find any info about howto flash OxygenOS 12 in fastboot on OP9P.
Click to expand...
Click to collapse
It's fastboot flash boot boot.img sir.
mattie_49 said:
It's fastboot flash boot boot.img sir.
Click to expand...
Click to collapse
1. "fastboot flash" change partition permanently, while "fastboot boot" change partition temporary.
2. I also tried "fastboot flash", no luck.
dna1982 said:
I will wait a week or two before flash DA C.63.
Click to expand...
Click to collapse
The problem came up when you tried carrying root over. I've had issues as well . Make sure your on 25.2 magisk manager, disable all modules . Only uninstall magisk,restore images,start system update when finished don't reboot. Go into magisk install to inactive slot for ota. And reboot.
Just flash the full DA C.63 over it using FBE. Make sure you go to the partitions screen and search cow and delete all cow partitions before you flash or you will brick. This should at least enable you to get your files backed up so you can MSM.
Before that though, go to fastboot and try fastboot --getvar current-slot to find out what slot you're on. From there do fastboot --set-active=a or --set-active=b, whichever is not active currently. Fastboot reboot and see if your old OTA boots.
EtherealRemnant said:
Just flash the full DA C.63 over it using FBE. Make sure you go to the partitions screen and search cow and delete all cow partitions before you flash or you will brick. This should at least enable you to get your files backed up so you can MSM.
Before that though, go to fastboot and try fastboot --getvar current-slot to find out what slot you're on. From there do fastboot --set-active=a or --set-active=b, whichever is not active currently. Fastboot reboot and see if your old OTA boots.
Click to expand...
Click to collapse
he can also see which slot is active directly with fbe because fbe shows this itself, just like he can change the slot with fbe
dna1982 said:
1. "fastboot flash" change partition permanently, while "fastboot boot" change partition temporary.
2. I also tried "fastboot flash", no luck.
Click to expand...
Click to collapse
fastboot flash only flashes the active slot and does not switch to the inactive slot.. and fastboot boot only boots an image that you have specified
ChrisFeiveel84 said:
he can also see which slot is active directly with fbe because fbe shows this itself, just like he can change the slot with fbe
Click to expand...
Click to collapse
FBE's slot changer doesn't always work in my experience. Both times I tried it for the purposes of changing the slot to boot from, it didn't actually change the slot, but when I switched slots to choose which to install to, that worked correctly. I only tell people to use things I'm confident work correctly and I know fastboot slot switching is one of those things that does.
EtherealRemnant said:
FBE's slot changer doesn't always work in my experience. Both times I tried it for the purposes of changing the slot to boot from, it didn't actually change the slot, but when I switched slots to choose which to install to, that worked correctly. I only tell people to use things I'm confident work correctly and I know fastboot slot switching is one of those things that does.
Click to expand...
Click to collapse
I also noticed that if you change the slot with fbe, the active slot is still displayed in fbe, but if you then reconnect the cell phone to the pc, fbe then shows that it has changed the slot
dna1982 said:
I was on C.62 AA with a working Magisk.
Yesterday I tried to update to C.63 AA with following steps:
1. Disable all Magisk module and reboot.
2. Restore Stock Image from Magisk Manager.
3. Update to C.63 from System Settings menu.
4. Install Magisk to inactive slot, then reboot.
That's it.
After reboot, my OP9P starts, but can't get into lock screen. Instead it only show black screen with a nonstop vibration.
I didn't do backup since I was NOT expecting this to happen.
Now I'm desperate for any help to unbick it or at lease get my files in sdcard back.
I can go into bootloader and fastbootd mode. ANY help would be much appreciated.
Click to expand...
Click to collapse
Is there any update regarding this thread? The same thing happens to me after I update my phone from C.62 DA to C.63 DA my phone is stuck on a black screen and then keeps on vibrating. I am also desperate to at least recover my data.
JeanFlasher said:
Is there any update regarding this thread? The same thing happens to me after I update my phone from C.62 DA to C.63 DA my phone is stuck on a black screen and then keeps on vibrating. I am also desperate to at least recover my data.
Click to expand...
Click to collapse
Sorry to hear that.
But you don't have to wait, since there is DA C.63 full rom.
Just flash it in fastboot mode by using Fastboot Enhance tool.
Good luck and tell us how it goes.
dna1982 said:
Sorry to hear that.
But you don't have to wait, since there is DA C.63 full rom.
Just flash it in fastboot mode by using Fastboot Enhance tool.
Good luck and tell us how it goes.
Click to expand...
Click to collapse
It didn't work for me real bummer. I've tried to do what EtherealRemnant suggested (ie: full flash DA C.63 over it using FBE), still out of luck.
JeanFlasher said:
It didn't work for me real bummer. I've tried to do what ChrisFeiveel84 suggested, still out of luck.
Click to expand...
Click to collapse
Did you follow the steps that @EtherealRemnant post?
And what is the result? We need details to help you.