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
Related
hi, ive just flashed TWRP onto my lollipop. seemed to be succesful, however when i boot into recovery all i get is the wee android dude lying on his back looking a bit dead! any ideas how to get this working. i just installed lollipop today
If you did 'fastboot flash recovery twrp.img' and not 'fastboot boot twrp.img':
Browse around, I'm pretty sure this has been answered before.
Search topics: install-recovery.sh, recovery-from-boot.p
Boot to Android, then flash again.
Aerowinder said:
Boot to Android, then flash again.
Click to expand...
Click to collapse
Ugh... What are you talking about?
What's happening is that every boot, his install is checking for stock recovery, and every time it doesn't find it, it will reflash it.
well I was using the flash method and it didnt work so i tried yor boot method and i could see teh twrp logo for about 5 seconds then the rebooted. i still get the android dude on his back with red triangle
5.0 will check recovery and overwrite twrp if your not rooted. Download latest SuperSU and place on sd. Boot to boot loader/fastboot. Fastboot flash recovery recovery.IMG. then fastboot boot recovery.IMG. then when twrp boots, flash SuperSU. Reboot
Sent from my Nexus 5 using Tapatalk
MG386 said:
5.0 will check recovery and overwrite twrp if your not rooted. Download latest SuperSU and place on sd. Boot to boot loader/fastboot. Fastboot flash recovery recovery.IMG. then fastboot boot recovery.IMG. then when twrp boots, flash SuperSU. Reboot
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
that worked a treat. is it necessary to flash the MODIFIED BOOT IMAGE?
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.
Hey everyone,
My TWRP has been erased from the phone and all I did was update magisk to the latest version (v 20). I'm on Android Pie, why did that happen? I can boot the phone and everything looks fine, it's just that TWRP is gone.
Should I just install it again ? Will I lose data if I install latest TWRP ?
THanks
Hmm.. i dont know what's happened to yours.. but i also updated my magisk to v20. And all.is well.. when i checked thru it a while ago... I can still boot to twrp..
Are you using the v70 twrp?? Try flashing it again via magisk.. be sure to flash magisk.again after that.. ??
santiagoruel13 said:
Hmm.. i dont know what's happened to yours.. but i also updated my magisk to v20. And all.is well.. when i checked thru it a while ago... I can still boot to twrp..
Are you using the v70 twrp?? Try flashing it again via magisk.. be sure to flash magisk.again after that..
Click to expand...
Click to collapse
No, I was using an old version of TWRP, don't remember what it was exactly, but it wasn't the latest one for sure.
What would be the correct steps to flash TWRP and Magisk so my phone boots up and I don't lose data?
Boot to twrp using fastboot then install twrp and magisk then proceed to reboot to system
Phantom Thief said:
Boot to twrp using fastboot then install twrp and magisk then proceed to reboot to system
Click to expand...
Click to collapse
same here. can't permanetly install twrp as recovery
Same here... I tried to install TWRP again and, at a certain point, phone couldn't even boot. I had to fastboot boot img, flash installer and then magisk 19.3. Now it all works
I was already on 3.3.1-70 ofc
Jack_Sparrow_ said:
Same here... I tried to install TWRP again and, at a certain point, phone couldn't even boot. I had to fastboot boot img, flash installer and then magisk 19.3. Now it all works
I was already on 3.3.1-70 ofc
Click to expand...
Click to collapse
which twrp version u use?
lee0525 said:
which twrp version u use?
Click to expand...
Click to collapse
Not the bluspark, the other one
I got the same issue, twrp is gone after update magisk to v20
what is the right way to install twrp from magisk v20?
I downloaded twrp .70
tnx
mikek753 said:
I got the same issue, twrp is gone after update magisk to v20
what is the right way to install twrp from magisk v20?
I downloaded twrp .70
tnx
Click to expand...
Click to collapse
looks like there is an issue with the latest magisk update. We'll have to wait for an update to the magisk or twrp so TWRP can stick
To fix it i booted into twrp then installed the last rom i was using (pie) then flashed twrp.zip, rebooted into recovery then installed magisk 19.4. you'll have to re-install your modules and re enable your apps that used root.
so since I'm using PIE 9.5.13. Just install the full zip of 9.5.13 through local storage > And then flash twrp and then magisk through twrp? Will there be data loss?
I got twrp back, in magisk by install twrp.
magic download I run flash the twrp and recovery is back
there was no any data loss in my case
For those have the same issue, here is the solution without flashing a new ROM.
https://github.com/topjohnwu/Magisk/issues/1920
from bootloader mode execute
fastboot flash boot boot.img (the stock boot.img)
boot twrp image (I used .70 unified)
fastboot boot twrp.img
flash twrp-installer.zip
flash magisk.zip (I flashed 19.4)
Enjoyyyyy
PS: you can get your corresponding stock boot.img from
https://www.oneplus7tips.com/category/oneplus-7-pro/kernels/
lee0525 said:
For those have the same issue, here is the solution without flashing a new ROM.
https://github.com/topjohnwu/Magisk/issues/1920
from bootloader mode execute
fastboot flash boot boot.img (the stock boot.img)
boot twrp image (I used .70 unified)
fastboot boot twrp.img
flash twrp-installer.zip
flash magisk.zip (I flashed 19.4)
Enjoyyyyy
PS: you can get your corresponding stock boot.img from
https://www.oneplus7tips.com/category/oneplus-7-pro/kernels/
Click to expand...
Click to collapse
Thank you.....
New to the OP7 Pro and this post saved me... I got my device last week and Magisk v20 was current and removed TWRP.... There is a Magisk 21 update is that safe or just say right here?
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
I patched twrp img with magisk and then ran fastboot flash boot "patched file" in fastboot mode. Now, whenever and however I start my system I get only the twrp menu. My device is Lenovo tab 4 8(tb-8504f)
Re-flash tablet's Stock ROM to get rid off of all modifications you applied so far.
re flash the ROM. dont flash the magisk or twrp after it. you will be saved.
you can use twrp via adb boot twrpxx.img So flashing it not needed.
Magisk installation has now become trickier simply flashing via recovery won't work
jwoegerbauer said:
Re-flash tablet's Stock ROM to get rid off of all modifications you applied so far.
Click to expand...
Click to collapse
hello thanks for replying. Could you provide me with the official rom. I've found one but not sure how reliable it is. I also in the twrp menu installed the patched twrp image from sd card to boot. After rebooting I again get the twrp menu but the file is not being show in sdcard anymore.
suraj123 said:
re flash the ROM. dont flash the magisk or twrp after it. you will be saved.
you can use twrp via adb boot twrpxx.img So flashing it not needed.
Magisk installation has now become trickier simply flashing via recovery won't work
Click to expand...
Click to collapse
I also in the twrp menu installed the patched twrp image from sd card to boot. After rebooting I again get the twrp menu but the file is not being show in sdcard anymore. Does this include what you've refused me to do so? And can u pls provide me the official link?