Question Issue with recovery - Xiaomi Poco X3 Pro

When I boot to recovery I remain stuck on Boot logo of OrangeFox, reboot back to system from TWRP and boot normally from stock recovery image... Any solution to this problem of mine?

Orangefox R11.1 works fine for me... it took a bit longer to boot with the boot screen, but then works like a charm... Did you flash OF via fastboot?

Wraller117 said:
When I boot to recovery I remain stuck on Boot logo of OrangeFox, reboot back to system from TWRP and boot normally from stock recovery image... Any solution to this problem of mine?
Click to expand...
Click to collapse
Maybe the problem is in the orangeFox version !

flash the latest version of ofox through fastboot mode, mine is working well.

I tried already tried flashing different variants of OrangeFox via fastboot it didn't work... But it did work earlier...

in my redmy 7a
I am not able to flash boot.img
Remote: flash write failure
can anyone help me

Wraller117 said:
I tried already tried flashing different variants of OrangeFox via fastboot it didn't work... But it did work earlier...
Click to expand...
Click to collapse
so weird, coz after i unlock my bootloader i flashed ofox directly via fastboot and it worked well.

icodix said:
so weird, coz after i unlock my bootloader i flashed ofox directly via fastboot and it worked well.
Click to expand...
Click to collapse
I won't be here if it wasn't weird...
I was using it just fine till noon but then I flashed another custom ROM using same recovery, but no sooner did I flash a custom ROM and was booting back to flash a custom Kernel, it was then simply stuck on Boot LOGO of OF and booted me back to system from TWRP... Stock is just as useless as Trump. So that's there

Wraller117 said:
I won't be here if it wasn't weird...
I was using it just fine till noon but then I flashed another custom ROM using same recovery, but no sooner did I flash a custom ROM and was booting back to flash a custom Kernel, it was then simply stuck on Boot LOGO of OF and booted me back to system from TWRP... Stock is just as useless as Trump. So that's there
Click to expand...
Click to collapse
Presumably, this "Custom ROM" has a name, and a version number?
BTW: OrangeFox has its own thread: https://forum.xda-developers.com/t/official-recovery-orangefox-recovery-project-r11-1.4362131/

@asif said:
in my redmy 7a
I am not able to flash boot.img
Remote: flash write failure
can anyone help me
Click to expand...
Click to collapse
You are more likely to receive help for your device on it's dedicated/specific forum, nevertheless are you sure your bootloader is unlocked?

Related

Need help with recovery please...

I bought this phone so I can get access to a lot of different roms... I'm trying to install twrp as my recovery or cmw but when I flash it after unlocking the boot loader with cmw it doesn't stay installed and revert back to the original request and the twrp I get an error message in twrp about original recovery and then the phone goes into a boot loop. It has the latest OS version running with April Security fixes... please help
Flash twrp as it is a more versatile and widely supported recovery.
Flash twrp in fastboot mode. After flashing, use the power and volume buttons to boot directly to twrp, do not reboot the phone until after you have entered recovery.
audit13 said:
Flash twrp as it is a more versatile and widely supported recovery.
Flash twrp in fastboot mode. After flashing, use the power and volume buttons to boot directly to twrp, do not reboot the phone until after you have entered recovery.
Click to expand...
Click to collapse
did exactly what you said and im getting thr error / system to prevent the stock rom from replacing twrp...
whats happening
I recommend flashing the latest stock rom to make sure the phone boots properly.Then, I would flash twrp again.
audit13 said:
I recommend flashing the latest stock rom to make sure the phone boots properly.Then, I would flash twrp again.
Click to expand...
Click to collapse
Did that and flashed twrp and I'm still getting the error...
I unlocked boot loader
Flashed twrp
With USB still plugged in I selected recovery from the fastboot menu...
Boots to recovery and still get that error message
Am I doing something wrong
You're flashing 2.8.7 for the hammerhead?
audit13 said:
You're flashing 2.8.7 for the hammerhead?
Click to expand...
Click to collapse
No I'm flashing the latest 3.0.2 version is that the problem?
I would try 2.8.7

Can't install Custom Roms.

Alright, so its without wasting time of people here, I'd just state the summary in points.
I flashed stock rom a.17 - I had custom roms before, I got fed up with them changing every 2 months.
Then everything worked fine until I flashed the boot.img from vishal_android_freak to get recovery.
I got the twrp recovery 2.7.0.0.
I flashed AOSP 6.0.1 through it, it was done very well but the rom stuck on boot animation for more then 30 mins.
I pulled the battery out - now I had TWRP 2.8.4.0
I tried flashing the rom again, it gave /data error.
I flashed stock rom, rooted then tried other methods of getting recovery, I failed everytime (Tried from TWRP app, su dd command, Recovery installer app )
Then I found a CWM boot.img to flash through fastboot.
I did and got CWM.
I flashed AOSP again from it, it stuck on boot animation again.
Then again I flashed stock rom and repeated the process.
This time with CWM, I flashed Stryflex LP Ultimate
It also stuck on boot animations.
Any idea why this happens? How to fix this ****?
Summary: Only stock rom works, not any other rom.
Observer000 said:
Alright, so its without wasting time of people here, I'd just state the summary in points.
I flashed stock rom a.17 - I had custom roms before, I got fed up with them changing every 2 months.
Then everything worked fine until I flashed the boot.img from vishal_android_freak to get recovery.
I got the twrp recovery 2.7.0.0.
I flashed AOSP 6.0.1 through it, it was done very well but the rom stuck on boot animation for more then 30 mins.
I pulled the battery out - now I had TWRP 2.8.4.0
I tried flashing the rom again, it gave /data error.
I flashed stock rom, rooted then tried other methods of getting recovery, I failed everytime (Tried from TWRP app, su dd command, Recovery installer app )
Then I found a CWM boot.img to flash through fastboot.
I did and got CWM.
I flashed AOSP again from it, it stuck on boot animation again.
Then again I flashed stock rom and repeated the process.
This time with CWM, I flashed Stryflex LP Ultimate
It also stuck on boot animations.
Any idea why this happens? How to fix this ****?
Summary: Only stock rom works, not any other rom.
Click to expand...
Click to collapse
I think​, that means bootloader is unlocked again! Recheck bootloader state and always use latest TWRP recovery (v3.0.2 for us).
You can download Xperia L recovery from twrp website and then use your current v2.8.4 one to install that. Or just simply use adb & fastboot in your PC and enter this command:
Code:
fastboot flash boot [I]your recovery image name.img[/I]
. And then flash your desired ROM
Kungfu73 said:
I think​, that means bootloader is unlocked again! Recheck bootloader state and always use latest TWRP recovery (v3.0.2 for us).
You can download Xperia L recovery from twrp website and then use your current v2.8.4 one to install that. Or just simply use adb & fastboot in your PC and enter this command:
Code:
fastboot flash boot [I]your recovery image name.img[/I]
. And then flash your desired ROM
Click to expand...
Click to collapse
Alright, I check bootloader state, it says bootloader unlock done means it's unlocked.
I am going to flash twrp 3.0.2 and will update you soon!
Kungfu73 said:
I think​, that means bootloader is unlocked again! Recheck bootloader state and always use latest TWRP recovery (v3.0.2 for us).
You can download Xperia L recovery from twrp website and then use your current v2.8.4 one to install that. Or just simply use adb & fastboot in your PC and enter this command:
Code:
fastboot flash boot [I]your recovery image name.img[/I]
. And then flash your desired ROM
Click to expand...
Click to collapse
Oh Man, you saved my day! nothing worked but the damnit twrp 3.0.2
For anyone else referring here:
I get hell lot of graphical glitches when I flashed twrp 3.0.2, I just made it to factory reset and click install button although my screen was glitched and I cant even look at it.
JUST IGNORE THE GLITCHES! I wiped dalvik cache after flashing AOSP-RRO, now I'm flashing Lineage OS, thanks a lot! Button pressed.
Observer000 said:
Oh Man, you saved my day! nothing worked but the damnit twrp 3.0.2
For anyone else referring here:
I get hell lot of graphical glitches when I flashed twrp 3.0.2, I just made it to factory reset and click install button although my screen was glitched and I cant even look at it.
JUST IGNORE THE GLITCHES! I wiped dalvik cache after flashing AOSP-RRO, now I'm flashing Lineage OS, thanks a lot! Button pressed.
Click to expand...
Click to collapse
Did TWRP 3.0.2 ultimately work with this?
If worked, I am also curious to know how much space is left there for apps in device memory, since the ROM seems to be Marshmallow based.

flashed twrp and its gone

Guys i faced a wierd problem . I flashed twrp image and then twrp zip and then magisk ..i rebooted and when i tried to boot in recovery . The recovery was gone but magisk is still . What should i doo nowwww ?
What you do now is you
fastboot boot blu_sparktwrp.img
And then in twrp you flash blu_sparktwrp.zip
Reboot to twrp
Flash magisk 17.2.Zip
Done..rebot.
whizeguy said:
What you do now is you
fastboot boot blu_sparktwrp.img
And then in twrp you flash blu_sparktwrp.zip
Reboot to twrp
Flash magisk 17.2.Zip
Done..rebot.
Click to expand...
Click to collapse
It didnt work ....it goes away after a reboot
sanu26661 said:
It didnt work ....it goes away after a reboot
Click to expand...
Click to collapse
It must work. You're basically flashing TWRP temporarily, so when you are in TWRP for the first time, you have to flash the zip file so that it stays installed. Try that again, maybe you did something wrong, but it has to work, you just need the .img that you flash with your PC, and the .zip that you flash using TWRP when you boot into it the first time.
Kluxe Nobody said:
It must work. You're basically flashing TWRP temporarily, so when you are in TWRP for the first time, you have to flash the zip file so that it stays installed. Try that again, maybe you did something wrong, but it has to work, you just need the .img that you flash with your PC, and the .zip that you flash using TWRP when you boot into it the first time.
Click to expand...
Click to collapse
I booted img first then installed zip but when i reboot to recovery thers only stock recovery present ...did like 10 times results are same
the blu_spark twrp? v2?
If twrp isn't sticking, from my experience is to lock bootloader, flash stock OS and start from scratch.....
Do not flash stock with unlocked bootloader

I need Help with Rooting OP6 stable not beta 9.0.2, bootloader is unlocked

So, i have used my whole saturday on unlocking the booloader which was the easiest and quickest and then trying to root, but that has failed every time. I first flashed the stock firmware zip 9.0.2 then I go back I dont reboot and flash the twrp and magisk zip and then it wont boot up,
when I try rebooting after flashing the firmware back to the system it sends me to the firmware,
when I try flashing a new firmware and then boot into fastboot then twrp and flash magisk it wont boot up,
and when I do the same only with twrp it wont neither.
I have tried sevel magisk versions, 17.1,17.2,17.3 none of them worked
as for the twrp blu spark or the one from the twrp website, i was always able to boot into twrp but not really to flash it as that would end in a twrp loop
can PLEASE anyone, someone, with a good heart and patience help me ? im really loosing my ****s over this
:fingers-crossed::fingers-crossed:
Try booting into blu_spark twrp
Installing blu_spark twrp
Rebooting to blu_spark twrp
Install magisk 17.3 or 17.1 (I am using 17.3 because it it beta but less stable.)
Faaris Ansari said:
Try booting into blu_spark twrp
Installing blu_spark twrp
Rebooting to blu_spark twrp
Install magisk 17.3 or 17.1 (I am using 17.3 because it it beta but less stable.)
Click to expand...
Click to collapse
can you provide me with the files ? plus
does it make a difference if I take these twrps compared to the one im using from their website ? because I dont see how this can be the fault ?
galaxyss8 said:
can you provide me with the files ? plus
does it make a difference if I take these twrps compared to the one im using from their website ? because I dont see how this can be the fault ?
Click to expand...
Click to collapse
The normal twrp is known to be buggy on the OnePlus 6 since there was encryption and stuff. Here is the blu_spark twrp IMG to boot:
https://forum.xda-developers.com/devdb/project/dl/?id=30485
And here you need to flash the blu_spark twrp: https://forum.xda-developers.com/devdb/project/dl/?id=30484
Flash that then reboot into recovery again
Then flash magisk
If this doesn't work for you I think there is another way.
Faaris Ansari said:
The normal twrp is known to be buggy on the OnePlus 6 since there was encryption and stuff. Here is the blu_spark twrp IMG to boot:
https://forum.xda-developers.com/devdb/project/dl/?id=30485
And here you need to flash the blu_spark twrp: https://forum.xda-developers.com/devdb/project/dl/?id=30484
Flash that then reboot into recovery again
Then flash magisk
If this doesn't work for you I think there is another way.
Click to expand...
Click to collapse
ive done that now and im waiting again in the; the boot loader is unlocked and software integrety.. winodw
im waiting now for some minutes, i flashed the blu spark zip pressed back went to reboot pressed on reboot to recovery and flashed magisk and then reboot to system, thats where i am now
galaxyss8 said:
ive done that now and im waiting again in the; the boot loader is unlocked and software integrety.. winodw
im waiting now for some minutes, i flashed the blu spark zip pressed back went to reboot pressed on reboot to recovery and flashed magisk and then reboot to system, thats where i am now
Click to expand...
Click to collapse
You might be on the wrong slot. DO you even have a system to boot to? Not sure why you even tyred flashing the 9.0.2 ROM. If I was you I would start over. Use the fastboot ROM to get a clean wiped system booting. After that
fastboot boot bluespark twrp v86. Img
Flash bluespark twrp v86. Zip
Reboot revovery
Flash magisk 17.1
yldlj said:
You might be on the wrong slot. DO you even have a system to boot to? Not sure why you even tyred flashing the 9.0.2 ROM. If I was you I would start over. Use the fastboot ROM to get a clean wiped system booting. After that
fastboot boot bluespark twrp v86. Img
Flash bluespark twrp v86. Zip
Reboot revovery
Flash magisk 17.1
Click to expand...
Click to collapse
I flashed the rom because my phone didn't boot up anymore after either flashing TWRP or magisk.
Why should I use the fastboot room, what is the benefit if I use it.
Is the reboot to recovery necessary ? I feel like that part is actually not working properly ?
galaxyss8 said:
I flashed the rom because my phone didn't boot up anymore after either flashing TWRP or magisk.
Why should I use the fastboot room, what is the benefit if I use it.
Is the reboot to recovery necessary ? I feel like that part is actually not working properly ?
Click to expand...
Click to collapse
Yes the reboot to recovery is the most nessesary part of it as it will change slots.
You can try boot to recovery
Flash oos full rom
Flash bluespark twrp. Zip
Reboot recovery
Flash full ROM again
Flash bluespark twrp. Zip again.
Reboot recovery
Flash magisk.
yldlj said:
Yes the reboot to recovery is the most nessesary part of it as it will change slots.
You can try boot to recovery
Flash oos full rom
Flash bluespark twrp. Zip
Reboot recovery
Flash full ROM again
Flash bluespark twrp. Zip again.
Reboot recovery
Flash magisk.
Click to expand...
Click to collapse
Can you explain how to properly boot back into recovery?
Previously I either just went on the back button and flashed the other Zip's or I went back to the reboot overview and pressed recovery there but that also did not seem to work properly I think.
galaxyss8 said:
Can you explain how to properly boot back into recovery?
Previously I either just went on the back button and flashed the other Zip's or I went back to the reboot overview and pressed recovery there but that also did not seem to work properly I think.
Click to expand...
Click to collapse
Just press back button in Recovery/ reboot / choose recovery.

Problem with flashing custom ROM (error 255)

Hey guys,
after searching through different websites and guides you are my last resort to get a custom ROM running on my Redmi S2.
Everytime i try to flash a custom ROM i get the error 255. Here is what i tried until now (bootloader is unlocked):
- flashing twrp(twrp-3.2.1-0-ysl) to recovery using fastboot
- wiping phone (first wipe to disable encryption since miui puts some kind of password on the hard drive that i dont know, second wipe to ensure partitions are clean for new OS)
- mounting phone to pc to transfer OS image (tried Lineage and Havoc, both modified for S2 (ysl version)) and GApps
- finally, installing OS zip (after which i get error message 255, telling me that twrp wasnt able to install the zip file)
please help me out, ask away if something's not clear
flying_shitnugget said:
Hey guys,
after searching through different websites and guides you are my last resort to get a custom ROM running on my Redmi S2.
Everytime i try to flash a custom ROM i get the error 255. Here is what i tried until now (bootloader is unlocked):
- flashing twrp(twrp-3.2.1-0-ysl) to recovery using fastboot
- wiping phone (first wipe to disable encryption since miui puts some kind of password on the hard drive that i dont know, second wipe to ensure partitions are clean for new OS)
- mounting phone to pc to transfer OS image (tried Lineage and Havoc, both modified for S2 (ysl version)) and GApps
- finally, installing OS zip (after which i get error message 255, telling me that twrp wasnt able to install the zip file)
please help me out, ask away if something's not clear
Click to expand...
Click to collapse
change your recovery..
Baim alif said:
change your recovery..
Click to expand...
Click to collapse
Mind elaborating? What do you mean exactly?
flying_shitnugget said:
Mind elaborating? What do you mean exactly?
Click to expand...
Click to collapse
use this recovery
https://files.orangefox.download/OrangeFox-Stable/ysl/OrangeFox-R10.0-1-Stable-ysl.zip
Baim alif said:
use this recovery
https://files.orangefox.download/OrangeFox-Stable/ysl/OrangeFox-R10.0-1-Stable-ysl.zip
Click to expand...
Click to collapse
so... i first tried taking the recovery.img out of the zip and flashing it via fastboot, didnt worked. after that i tried first flashing my old twrp and then (after wiping) installing the whole zip. the install finished successfully, sayed it will restart to recovery in 5 seconds... aaaand got stuck on the android screen. now it wont boot to recovery at all anymore, unless i flash the old twrp again. suggestions?
flying_shitnugget said:
so... i first tried taking the recovery.img out of the zip and flashing it via fastboot, didnt worked. after that i tried first flashing my old twrp and then (after wiping) installing the whole zip. the install finished successfully, sayed it will restart to recovery in 5 seconds... aaaand got stuck on the android screen. now it wont boot to recovery at all anymore, unless i flash the old twrp again. suggestions?
Click to expand...
Click to collapse
try to boot recovery with power button and volume up
Baim alif said:
try to boot recovery with power button and volume up
Click to expand...
Click to collapse
yes, that's what i did. i also tried booting into from fastboot and still nothing.
flying_shitnugget said:
yes, that's what i did. i also tried booting into from fastboot and still nothing.
Click to expand...
Click to collapse
hmmm... try this bro..
https://androidfilehost.com/?fid=6006931924117927913
flying_shitnugget said:
yes, that's what i did. i also tried booting into from fastboot and still nothing.
Click to expand...
Click to collapse
Try this, you have to flash first this in fastboot https://files.orangefox.download/OrangeFox-Beta/ysl/ the R10.0-1 RC1 .img file
And THEN flash this https://orangefox.download/en/device/ysl once you are in the recovery.
Then it worked for me, finally, hope this helps.
celephrn said:
Try this, you have to flash first this in fastboot https://files.orangefox.download/OrangeFox-Beta/ysl/ the R10.0-1 RC1 .img file
And THEN flash this https://orangefox.download/en/device/ysl once you are in the recovery.
Then it worked for me, finally, hope this helps.
Click to expand...
Click to collapse
so i tried this approach. i first installed how you told me to (orangefox R10.0-1 RC1 .img first), but factory reset nor installing the second recovery img worked because of the encryption miui puts on the phone. So i flashed twrp, wiped memory, flashed first orange fox img and from then installed the second img (as a zip). until here everything worked, orange fox told me that he's going to reboot to new recovery -- and i got stuck on the boot logo again. :c
flying_shitnugget said:
so i tried this approach. i first installed how you told me to (orangefox R10.0-1 RC1 .img first), but factory reset nor installing the second recovery img worked because of the encryption miui puts on the phone. So i flashed twrp, wiped memory, flashed first orange fox img and from then installed the second img (as a zip). until here everything worked, orange fox told me that he's going to reboot to new recovery -- and i got stuck on the boot logo again. :c
Click to expand...
Click to collapse
Did you flash the firmware? https://github.com/XiaomiFirmwareUpdater/firmware_xiaomi_ysl/releases/tag/stable-16.03.2020
Other thing you could try is flash the other .img files from https://files.orangefox.download/OrangeFox-Beta/ysl/ and the flash in there the same .zip file you did as before.
celephrn said:
Did you flash the firmware? https://github.com/XiaomiFirmwareUpdater/firmware_xiaomi_ysl/releases/tag/stable-16.03.2020
Other thing you could try is flash the other .img files from https://files.orangefox.download/OrangeFox-Beta/ysl/ and the flash in there the same .zip file you did as before.
Click to expand...
Click to collapse
im currently on MIUI V.10.3.1.0.OEFMIXM | Stable 654M, is it important to flash newer firmware?
flying_shitnugget said:
im currently on MIUI V.10.3.1.0.OEFMIXM | Stable 654M, is it important to flash newer firmware?
Click to expand...
Click to collapse
Could solve the issue, I'd give it a shot!
celephrn said:
Could solve the issue, I'd give it a shot!
Click to expand...
Click to collapse
i suppose you flash it using MiFlash right? If so, i have a problem with flashing new roms using it because my Mi account isnt allowed to do that, i unlocked the bootloader using a tool (dont know if this has something to do with the custom rom problem)
flying_shitnugget said:
i suppose you flash it using MiFlash right? If so, i have a problem with flashing new roms using it because my Mi account isnt allowed to do that, i unlocked the bootloader using a tool (dont know if this has something to do with the custom rom problem)
Click to expand...
Click to collapse
As long as the bootloader is unlocked it should be fine. And no, you should flash the firmware just as you would flash the rom, i. e. from OrangeFox Recovery.
celephrn said:
As long as the bootloader is unlocked it should be fine. And no, you should flash the firmware just as you would flash the rom, i. e. from OrangeFox Recovery.
Click to expand...
Click to collapse
so i flashed the firmware as you said, now neither orangefox or twrp throw me the error "unable to locate storage device", i cant mount the storage to the pc and cant copy the custom rom stuff as well
celephrn said:
As long as the bootloader is unlocked it should be fine. And no, you should flash the firmware just as you would flash the rom, i. e. from OrangeFox Recovery.
Click to expand...
Click to collapse
UPDATE: i finally ****ing did it. So here are the steps that i took (incase anyone has to go through this **** as well)
1. flash MIUI on mobile device using MiFlash (at least i did this by shorting 2 pins on the back)
2. (VERY IMPORTANT!!!) instantly boot to fastboot using Power button + Volume down. this has to be before android starts setting up the phone
3. flash recovery with the image that celephrn provided in this thread
4.boot to recovery by holding Volume up + Power button
5. install the miui update that celephrn provided in this thread
6. reboot to recovery
7. install orange recovery zip that celephrn provided in this thread (phone reboots to recovery)
8. now you can reboot to system (Do NOT (!!!) set the phone up, just let it work its things until you see the MIUI setup screen)
9. Now, finally you can dirty flash your custom rom (and GApps)
10. after flashing the new rom android will throw you alot of errors so you will have to wipe Dalvik/Cache, System, Data and Internal Storage.
11. now you can flash your Rom clean and you're good to go
(huge thanks to celephrn, helped me out after me struggling for a few good weeks with this damn phone)
Baim alif said:
use this recovery
https://files.orangefox.download/OrangeFox-Stable/ysl/OrangeFox-R10.0-1-Stable-ysl.zip
Click to expand...
Click to collapse
bro please help me i have the same issue error 255 on 3.2.1-0 ysl twrp.please help
Farrellclay said:
bro please help me i have the same issue error 255 on 3.2.1-0 ysl twrp.please help
Click to expand...
Click to collapse
so far, what have you done

Categories

Resources