Database Info

Really screwed up, what to do? CID:BM__001

Ok, so I tried to unlock my bootloader and install a custom rom, of course, somewhere along the way I screwed up and now I don't know what to do. So what I did was I unlocked my bootloader using the HTCDev unlock token, that went fine, then I installed CWM, again, that was fine, then installed superSU and flashed CM10, rebooted, nothing, I realized I had to flash the boot.img from CM so I did that, then that's what when the problems began. The CM boot animation just starts and never ends (i.e. over 15min). So all I can do now is get into bootloader, and from there recovery; although my /sdcard partition seems to be screwed too. Can't 'flash from SDcard' in recovery, I looked at that thread that says to flash a stock recovery to fix this but I can't find a stock recovery or RUU for my CID...
I guess my question is, how can I get my phone booting again? Is it easier to just go straight to S-OFF? Which I don't think I can do with my phone in this state, or just go back to stock? Which I can't find a proper RUU for my phone....
Obviously... any help is greatly appreciated
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT27DWxxxxxx
(bootloader) imei: ----------------------
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4133mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s

stock recovery--
https://www.dropbox.com/sh/yhrq0tia8512rj9/go28kc1NeP/ville_recovery_signed.img
would also fastboot twrp recovery after you are sorted--2.3.3.0 works good
http://techerrata.com/browse/twrp2/ville
you will lose sdcard hope you have a bu and a nandroid on pc--i always keep copies on my pc or you may have to push a rom to sdcard
you need to fastboot stock recovery
then thru command window boot into bootloader and clear storage
reboot into into bootloader and factory reset, that should get your sdcard mountable again
you can use this but use fastboot and not toolkit and fastboot twrp not cwm
http://forum.xda-developers.com/showthread.php?t=1630459

rugmankc said:
stock recovery--
https://www.dropbox.com/sh/yhrq0tia8512rj9/go28kc1NeP/ville_recovery_signed.img
would also fastboot twrp recovery after you are sorted--2.3.3.0 works good
http://techerrata.com/browse/twrp2/ville
you will lose sdcard hope you have a bu and a nandroid on pc--i always keep copies on my pc or you may have to push a rom to sdcard
you need to fastboot stock recovery
then thru command window boot into bootloader and clear storage
reboot into into bootloader and factory reset, that should get your sdcard mountable again
you can use this but use fastboot and not toolkit and fastboot twrp not cwm
http://forum.xda-developers.com/showthread.php?t=1630459
Click to expand...
Click to collapse
thank you sir, questions:
how do I boot into bootloader thru command window? Won't I be still be in bootloader after I fastboot the stock recovery?
Also what should/can I do after? Can I try re-installing CM10 again? I guess that's the only thing I can do since I don't have a RUU that works with my CID...??

i forget how phone reacts after clearing storage, but need to get back to bl or see if you stay there
assume you are familiar with adb/fatsboot, i soon have to call it a nite. someone else may have to chime in
but, basically you need to open command window and change directory to where your adb/fastboot folder is. If using android sdk it is usually in platform tools
take the boot image from the link i provided and put in your fastboot folder on pc
once there you should be able to type adb devices and see that your phone is recognized. then you can type adb reboot bootloader and you should boot into fastboot screen where FASTBOOT is highlighted red
then you can type fastboot devices to again verify your are in fastboot
then type fastboot flash boot boot.img
the boot.img part will be the exact name of the boot image you put into the adb/fastboot folder, the one i gave you the link to.
you can change the name of that image to boot.img or just copy and paste the name as is into the command line instead of boot.img
fastboot twrp the same way if you get sdcard recognized
if you can now mount card you can copy rom to sdcard from pc
you may not have wiped properly when you flashed cm10
wipe all including system 3x from recovery before flashing roms
Awesome has a kernel and system wipe zips you can also use if you want. I wipe all thru recovery first then run the kernel then wipe script then flash rom. wouldn't use them yet.

rugmankc said:
stock recovery--
https://www.dropbox.com/sh/yhrq0tia8512rj9/go28kc1NeP/ville_recovery_signed.img
would also fastboot twrp recovery after you are sorted--2.3.3.0 works good
http://techerrata.com/browse/twrp2/ville
you will lose sdcard hope you have a bu and a nandroid on pc--i always keep copies on my pc or you may have to push a rom to sdcard
you need to fastboot stock recovery
then thru command window boot into bootloader and clear storage
reboot into into bootloader and factory reset, that should get your sdcard mountable again
you can use this but use fastboot and not toolkit and fastboot twrp not cwm
http://forum.xda-developers.com/showthread.php?t=1630459
Click to expand...
Click to collapse
rugmankc said:
i forget how phone reacts after clearing storage, but need to get back to bl or see if you stay there
assume you are familiar with adb/fatsboot, i soon have to call it a nite. someone else may have to chime in
but, basically you need to open command window and change directory to where your adb/fastboot folder is. If using android sdk it is usually in platform tools
take the boot image from the link i provided and put in your fastboot folder on pc
once there you should be able to type adb devices and see that your phone is recognized. then you can type adb reboot bootloader and you should boot into fastboot screen where FASTBOOT is highlighted red
then you can type fastboot devices to again verify your are in fastboot
then type fastboot flash boot boot.img
the boot.img part will be the exact name of the boot image you put into the adb/fastboot folder, the one i gave you the link to.
you can change the name of that image to boot.img or just copy and paste the name as is into the command line instead of boot.img
fastboot twrp the same way if you get sdcard recognized
if you can now mount card you can copy rom to sdcard from pc
you may not have wiped properly when you flashed cm10
wipe all including system 3x from recovery before flashing roms
Awesome has a kernel and system wipe zips you can also use if you want. I wipe all thru recovery first then run the kernel then wipe script then flash rom. wouldn't use them yet.
Click to expand...
Click to collapse
I was just about to reply, I got the TWRP going so I have that recovery on there now and I think my SDcard is working now... so should I wipe and run the kernal and flash rom? what about flashing the boot.img of the new rom? Do I still need to do that?

You'll have to read OP page for flashing instructions for that rom. Some have a boot script you can run as opposed to fastbooting boot image. And if you are .13 hboot or higher you will need to flash boot image. Fastboot is best way. However some are using Flash Image GUI to do that. From Market. For now fastboot it as you are obviously proficient at fastboot.
I would normally wipe all 3x including system/flash rom in recovery(don't boot into OS (System)yet)/boot into bootloader and flash boot image. After flashing boot image in command window type fastboot erase cache. then type fastboot reboot-bootloader. Once back in recovery you can reboot into System (OS).
Usually after rom boots and I set up wifi, I usually reboot to recovery and wipe caches then reboot into rom and continue setup.

rugmankc said:
You'll have to read OP page for flashing instructions for that rom. Some have a boot script you can run as opposed to fastbooting boot image. And if you are .13 hboot or higher you will need to flash boot image. Fastboot is best way. However some are using Flash Image GUI to do that. From Market. For now fastboot it as you are obviously proficient at fastboot.
I would normally wipe all 3x including system/flash rom in recovery(don't boot into OS (System)yet)/boot into bootloader and flash boot image. After flashing boot image in command window type fastboot erase cache. then type fastboot reboot-bootloader. Once back in recovery you can reboot into System (OS).
Usually after rom boots and I set up wifi, I usually reboot to recovery and wipe caches then reboot into rom and continue setup.
Click to expand...
Click to collapse
Ok I've tried all the steps and I can get into recovery and flash roms but any rom I try to flash (and following all wipe and boot.img steps) always results in a bootloop when I first boot the rom... any ideas?? I can reflash different roms but no matter which one I try they end up in bootloops...
Is there a way to go to S-OFF in my state?

pookguy88 said:
Ok I've tried all the steps and I can get into recovery and flash roms but any rom I try to flash (and following all wipe and boot.img steps) always results in a bootloop when I first boot the rom... any ideas?? I can reflash different roms but no matter which one I try they end up in bootloops...
Is there a way to go to S-OFF in my state?
Click to expand...
Click to collapse
Are you sure your flashing the boot img for the ROM you are trying to flash? Use fastboot.
HTC_One_S | S-OFF | Root_Box | Bubba_3.7b_SoftOV

ryanshew said:
Are you sure your flashing the boot img for the ROM you are trying to flash? Use fastboot.
HTC_One_S | S-OFF | Root_Box | Bubba_3.7b_SoftOV
Click to expand...
Click to collapse
Yup.. I always take the boot img out of the ROM zip file itself and fastboot it before I reboot..
I've tried Carbon and CM10 so far... both get stuck in bootloops at boot.. I know the boot.img is being flashed because the fastboot goes through ok and the boot animation for each ROM is different

maybe im repeating some one else but
try it without wiping after the install of rom and boot.img
so, wipe all (data/cache/system/dalvik/unsecure) then factory reset
then flash rom in twrp
then fastboot flash boot boot.img in fastboot usb mode
reboot device.
btw what rom are you flashing?

I am not up on hboots/cid's/etc
but see you have an EU radio
you are version s4 not s3
sorry if that was easily recognized on your 1st post

real187 said:
maybe im repeating some one else but
try it without wiping after the install of rom and boot.img
so, wipe all (data/cache/system/dalvik/unsecure) then factory reset
then flash rom in twrp
then fastboot flash boot boot.img in fastboot usb mode
reboot device.
btw what rom are you flashing?
Click to expand...
Click to collapse
I've been trying CM10 (http://forum.xda-developers.com/showthread.php?t=1799139) nightlies...
So for the wiping part, isn't a factory reset (in TWRP) just a data/cache wipe? what does unsecure do? I haven't done that before..

rugmankc said:
I am not up on hboots/cid's/etc
but see you have an EU radio
you are version s4 not s3
sorry if that was easily recognized on your 1st post
Click to expand...
Click to collapse
yeah, just realized I have a S4... are you sure I have a EU radio though? I got mine from a Canadian (Bell) carrier..

Ok I'm going to try re-locking the bootloader and RUU-ing this:
RUU_Ville_U_BM_1.70.666.1_R_Radio_0.16.31501S.06_3_10.20.31501S.09L_release_255222_signed.exe
hopefully that will work.. downloading it now

pookguy88 said:
yeah, just realized I have a S4... are you sure I have a EU radio though? I got mine from a Canadian (Bell) carrier..
Click to expand...
Click to collapse
.11 was EU I thought--it doesn't matter though
---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------
pookguy88 said:
I've been trying CM10 (http://forum.xda-developers.com/showthread.php?t=1799139) nightlies...
So for the wiping part, isn't a factory reset (in TWRP) just a data/cache wipe? what does unsecure do? I haven't done that before..
Click to expand...
Click to collapse
gfactory reset is your date
dalvik cache and cache are different and don't impact your personal data

pookguy88 said:
Ok I'm going to try re-locking the bootloader and RUU-ing this:
RUU_Ville_U_BM_1.70.666.1_R_Radio_0.16.31501S.06_3_10.20.31501S.09L_release_255222_signed.exe
hopefully that will work.. downloading it now
Click to expand...
Click to collapse
That will not work...you cannot ruu to a lower hboot...you are on the highest hboot, so ruu is not an option for you since there is no bell mobility ruu for jb out yet...your doing something wrong...probably something very simple you are overlooking.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_3.4

ryanshew said:
That will not work...you cannot ruu to a lower hboot...you are on the highest hboot, so ruu is not an option for you since there is no bell mobility ruu for jb out yet...your doing something wrong...probably something very simple you are overlooking.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_3.4
Click to expand...
Click to collapse
@all
is there any way i can get an Europe RUU on this phone? or any custom rom will work on this? if yes then pls inform! if there's a way!
WBR
ReyTech.

screwed up when flashing twrp

Alright so I screwed Up. I got in a rush and followed some guys advice in a thread for a different phone and not sure how to get back on track. Can someone help?
Heres what I did.....
G:\Downloads\oneplus 6 root\android p>fastboot flash recovery twrp-3.2.3-0-enchilada.img
target reported max download size of 536870912 bytes
sending 'recovery' (26744 KB)...
OKAY [ 0.569s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.577s
Click to expand...
Click to collapse
Nothing..... SO I googled and then typed this:
>>fastboot flash boot_b twrp-3.2.3-0-enchilada.img
Phone rebooted and showed twrp, cool. I restarted from there then, sh1t! Now I can't get back to twrp nor the os to follow the correct guide.
I tried holding power for 7 seconds - reboots and shows the red dot with white dots circling eternally
I tried holding volume down + power for 7 seconds - reboots and does the same thing
I tried holding volume up + power for 7 seconds - it goes into this all black recovery mode or something
no recovery mode is seen again yet since my mistake

As far as I know the only TWRP that works for Android p on the OnePlus 6 is bluspark. Try this unbrick thread or try fastboot bluspark.img
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
---------- Post added at 04:45 AM ---------- Previous post was at 04:36 AM ----------
Bluspark
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
Fastboot commands
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page44

dgunn said:
As far as I know the only TWRP that works for Android p on the OnePlus 6 is bluspark. Try this unbrick thread or try fastboot bluspark.img
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
---------- Post added at 04:45 AM ---------- Previous post was at 04:36 AM ----------
Bluspark
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
Fastboot commands
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page44
Click to expand...
Click to collapse
Hey thanks for trying to help me. I somehow just got it into fastboot mode....... Not really sure how, but I tried to follow the guide here to get in to it.
Anyway. I was running android oreo not android p before I tried to flash twrp.. does that make a difference?

So just to be clear you were trying to update TWRP on Oreo and not Android p?
Reason I ask is it says Android p in your original post

dgunn said:
So just to be clear you were trying to update TWRP on Oreo and not Android p?
Reason I ask is it says Android p in your original post
Click to expand...
Click to collapse
Hey! sorry, I made the folder called "Android P" because i will be upgrading to android p lineage os 16. Before I made this mistake, I was running the latest version of android oreo.
GOOD NEWS THOUGH. I somehow got into twrp through fastboot (using bootloader? option). now it keeps booting into twrp. How can I restore stock recovery from here and have a do-over? Thank you!

If you want to restore stock recovery you have to flash the stock image that you are currently on. If you are on the latest Oreo it would be 5.1.11
And I believe you will have to delete the TWRP folder. Not exactly sure when you do that but I read about it somewhere

dgunn said:
If you want to restore stock recovery you have to flash the stock image that you are currently on. If you are on the latest Oreo it would be 5.1.11
And I believe you will have to delete the TWRP folder. Not exactly sure when you do that but I read about it somewhere
Click to expand...
Click to collapse
Ok this is weird..........
I boot into twrp, then I choose; reboot, slot a (instead of default slot b), then the phone boots and it's running android P. what the heck!?
Not sure what happened....... here's the history
1- Android 8
2- Installed Android P dev preview
3- Rolled back to Android 8
4- Installed TWRP, screwed it up
5- Got back to TWRP, chose slot B, now it's booted
6- How is it running Android P

I really just want to get it back to full stock and start over since i screwed up. or even better... just want to fix my screw up the way it's meant to be done right......

Once it screwed up the TWRP it automatically switch slots.
Installed Android p (slot a)
Rolled back (slot b)
TWRP screw up (switched to slot a)
Every time you update it Flags the current slot
---------- Post added at 05:16 AM ---------- Previous post was at 05:15 AM ----------
Boot into recovery and Flash a full stock ROM Oreo

dgunn said:
Once it screwed up the TWRP it automatically switch slots.
Installed Android p (slot a)
Rolled back (slot b)
TWRP screw up (switched to slot a)
Every time you update it Flags the current slot
---------- Post added at 05:16 AM ---------- Previous post was at 05:15 AM ----------
Boot into recovery and Flash a full stock ROM Oreo
Click to expand...
Click to collapse
So is slot A and B only for ROMS and not for recovery?
When I downgraded to 8 from 9, technically 9 was still installed:silly:?

R0ttenB4ndit said:
hey @ajsmsg78. when i do adb devices through usb, it doesn't find it. it will keep booting to the red dot and spinning white dots around it. no recovery option appears on the phone. what mode do I have to be in for the pc to see it at this point?
Click to expand...
Click to collapse
1. Shut off device
2. Unplug any cables or otg connectwd to it.
3. Hold volup while holding power, you should be greeted with fastboot mode and a oneplus logo
4. When you get into the menu do
Code:
fastboot flash boot_x boot.img
Replace _x with _a then _b, to flash it to both slots.
5. By now you should be up and running, to flash twrp you have to
Code:
fastboot boot twrp.img
6. Flash the twrp zip to make it stay.
Reason being that twrp has to be patched to your current boot image, new phones with ab partition tables doesnt have a recovery partition. Thats why we have to boot the twrp img from our pc initially, then use the zip to patch it in permanently.
If you dont have a boot for your oos there is a thread with stock and prepatched twrp boot img's in discussion subforum
I posted this in the other thread before i saw any replies here, if you want to reset to full stock just use the fastboot unbrick bat

I can't boot back into TWRP lol. I also tried changing the slots while in fastboot with PC using
a) fastboot --set-active=a
b) fastboot set_active [a,b]
c) fastboot set_active other
none of them worked. how do you recommend I get back to how twrp and the rom is supposed to be installed? Thank again for the help, big help.
UPDATE: OK I see your previous response, I'll try and report back.

R0ttenB4ndit said:
I can't boot back into TWRP lol. I also tried changing the slots while in fastboot with PC using
a) fastboot --set-active=a
b) fastboot set_active [a,b]
c) fastboot set_active other
none of them worked. how do you recommend I get back to how twrp and the rom is supposed to be installed? Thank again for the help, big help.
Click to expand...
Click to collapse
Well, easiest way is the last mentioned one, its a real simple procedure. Hook up to fastboot, then click the corresponding bat and wait, heres the thread. Then to get twrp running follow my previous posted steps
forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/page57

After installing the zip... should I wipe the cache/dalvik?
Update: the answer is yes, I'm reading. will update soon.

efinityy said:
1. Shut off device
2. Unplug any cables or otg connectwd to it.
3. Hold volup while holding power, you should be greeted with fastboot mode and a oneplus logo
4. When you get into the menu do
Code:
fastboot flash boot_x boot.img
Replace _x with _a then _b, to flash it to both slots.
5. By now you should be up and running, to flash twrp you have to
Code:
fastboot boot twrp.img
6. Flash the twrp zip to make it stay.
Reason being that twrp has to be patched to your current boot image, new phones with ab partition tables doesnt have a recovery partition. Thats why we have to boot the twrp img from our pc initially, then use the zip to patch it in permanently.
If you dont have a boot for your oos there is a thread with stock and prepatched twrp boot img's in discussion subforum
I posted this in the other thread before i saw any replies here, if you want to reset to full stock just use the fastboot unbrick bat
Click to expand...
Click to collapse
Alright, thought I had it............ but no, now it just keeps rebooting into fast mode. Maybe I'm getting ahead of myself here. Sorry....
Here's what I did:
cmd
>>fastboot flash boot_a twrp-3.2.3-0-enchilada.img
>>fastboot flash boot_b twrp-3.2.3-0-enchilada.img
all ok
>>fastboot boot twrp-3.2.3-0-enchilada.img
the phone boots into twrp, cool
cmd again
>>adb push twrp-installer-enchilada-3.2.3-0.zip /sdcard/
then installed twrp-installer-enchilada-3.2.3-0.zip to make it stay
wiped dalvik/cache and it rebooted to twrp again
think I am now in the clear yay (not).
>>adb push lineage-16.0-20180916_111137-UNOFFICIAL-enchilada.zip /sdcard/
then installed lineage-16.0-20180916_111137-UNOFFICIAL-enchilada.zip
success
I reboot but it still goes to twrp
i change slot to b (it was set to A) hoping maybe it'd boot to lineage
phone reboots and now I can't make it go back to twrp. It keep rebooting into fastboot no matter what I do (hard keys reset/options to choose)
stuck again.

When try to mount the twrp image just to boot into it, I get this now:
>>fastboot boot twrp-3.2.3-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.568s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.584s

so @efinityy what's this fastboot unbrick bat you speak of? Is it this one I need: flash-all-partitions-fastboot.bat ?
Thanks again.
Which zip is it that I need?

R0ttenB4ndit said:
so @efinityy what's this fastboot unbrick bat you speak of? Is it this one I need: flash-all-partitions-fastboot.bat ?
Thanks again.
Which zip is it that I need?
Click to expand...
Click to collapse
Exactly, but i dont think its the all partitions one, it says in the thread which one almost always is the necessary one, using the wrong one can make it worse... and the twrp zip you need can be gotten from blu_spark kernel threads download section, you want the twrp v2 for pie, v1 for Oreo.. Scratch that, v2 works for all.
Dont flash the twrp img in boot partition yo ? you want the stock boot image/ kernel there... Twrp will later be merged with your current boot, flashing twrp to boot a or b will make you have no kernel, having no kernel equals having no instructions to get android running, and instead of calling the kernel to boot android it will just call twrp over and over
Why we are installing the zip is because previously we had recovery partition, a dedicated partition made for the recovery, now we don't, the recovery is part of the kernel, and we don't ever wanna lose our kernel because that means the phone doesn't know how to boot itself to a usable state, so that's why we only fastboot BOOT twrpimghere... Then install the twrp zip to to patch out the old recovery, like removing a tumor from a body, then patch that empty place with a bandaid that is twrp, so you have your old kernel, the one that can boot the system, and a fresh bandaid on top of it that is twrp... Sorry for the weird metaphoring, I trying to put a/b partitions and it's functions in condensed text is a challenge, but as soon as you grasp the concept you will understand how to do it flawlessly every time

efinityy said:
Exactly, but i dont think its the all partitions one, it says in the thread which one almost always is the necessary one, using the wrong one can make it worse... and the twrp zip you need can be gotten from blu_spark kernel threads download section, you want the twrp v2 for pie, v1 for oreo
Click to expand...
Click to collapse
In the OP it says:
Now usually the one needed is only the first "flash-all-partitions-fastboot.bat" but if you are badly bricked i recommend to use flash-all-partitions.bat .
Click to expand...
Click to collapse
When you say I want the twrp..... is this something else I need before I run the Stock Fastboot ROM bat file?

which step did I go wrong?
I did Replace _x with _a then _b, to flash it to both slots
I thought it was meaning to flash it to both A and B? What did that mean? Thank you!

Can't install TWRP in Android 9

I was running stock OOS with Android 8.1 with the normal TWRP and Magisk working. When the OOS 9 got out, I installed the full OTA through TWRP (dirty flash) and everything went perfectly, with no problems whatsoever, but I lost TWRP and Magisk, of course.
Now in Android 9 I can't seem to reinstall TWRP (I'm trying with the latest bluespark): I can boot TWRP from fastboot and install Magisk, everything is fine, Magisk works great. However, when I try to install the TWRP zip (through the fastboot loaded TWRP), the phone freezes at the bootloader warning and doesn't boot (and I have to reinstall the full OTA zip to get the phone working again). Or, some other times, it reboots always to the recovery and never to the OS. Any ideas on how to solve this? Thanks in advance.

What version of bluespark are you using ?? v2

Glsoto said:
What version of bluespark are you using ?? v2
Click to expand...
Click to collapse
9.85v2

first fastboot boot twrp.img, the install twrp.zip , reboot recovery and then magisk..

I also tried to fastboot boot blu_spark twrp V2 IMG.... This ended in a black screen. I used the latest official twrp without a problem on pie.

Glsoto said:
first fastboot boot twrp.img, the install twrp.zip , reboot recovery and then magisk..
Click to expand...
Click to collapse
Thanks! Did it in that exact order and now everything works. I was forgetting to reboot the recovery before installing Magisk.

don't flash magisk on the temporary TWRP

Hexyl said:
I also tried to fastboot boot blu_spark twrp V2 IMG.... This ended in a black screen. I used the latest official twrp without a problem on pie.
Click to expand...
Click to collapse
Cuz of kernel panic. When you boot into twrp after fastboot command - unplag your cable from pc when the command is done, then disable mtp, connect to pc and re-enable mtp.
Dont forget to click thanks
And yeah, use blu spark's TWRP, not official one

Came here from google.
Glsoto said:
first fastboot boot twrp.img, the install twrp.zip , reboot recovery and then magisk..
Click to expand...
Click to collapse
This procedure didn't work for me, for some reason "fastboot boot twrp.img" was leading to black screen.
What worked for me was
1) Boot to fastboot
2) fastboot flash twrpXXX.img
3) Without rebooting, select recovery from fastboot's bootloader menu
4) If you are able to boot in twrp this time, then flash blu spark twrp.
5) Reboot
6) Try to reboot in recovery as usual
If all worked well, you should see twrp recovery.
Cheers.

Alekcander said:
Came here from google.
This procedure didn't work for me, for some reason "fastboot boot twrp.img" was leading to black screen.
What worked for me was
1) Boot to fastboot
2) fastboot flash twrpXXX.img
3) Without rebooting, select recovery from fastboot's bootloader menu
4) If you are able to boot in twrp this time, then flash blu spark twrp.
5) Reboot
6) Try to reboot in recovery as usual
If all worked well, you should see twrp recovery.
Cheers.
Click to expand...
Click to collapse
Hi
I have same problem ... after installing twrp i have black scream. twrp doesnt boot
I trying to use this method but cmd give me ]
C:\Android>fastboot flash twrp-3.3.1-x_blu_spark_v9.101_op6.img
unknown partition 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
error: cannot determine image filename for 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
I have restored phone with msn download
OnePlus is again unlocked
I have this problem sins i tried to install magisk and after reboot my op doesn't boot to OS with crash error
any ideas ?

jasiorr said:
Hi
I have same problem ... after installing twrp i have black scream. twrp doesnt boot
I trying to use this method but cmd give me ]
C:\Android>fastboot flash twrp-3.3.1-x_blu_spark_v9.101_op6.img
unknown partition 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
error: cannot determine image filename for 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
I have restored phone with msn download
OnePlus is again unlocked
I have this problem sins i tried to install magisk and after reboot my op doesn't boot to OS with crash error
any ideas ?
Click to expand...
Click to collapse
You need to Fastboot boot twrp. Img

jasiorr said:
Hi
I have same problem ... after installing twrp i have black scream. twrp doesnt boot
I trying to use this method but cmd give me ]
C:\Android>fastboot flash twrp-3.3.1-x_blu_spark_v9.101_op6.img
unknown partition 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
error: cannot determine image filename for 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
I have restored phone with msn download
OnePlus is again unlocked
I have this problem sins i tried to install magisk and after reboot my op doesn't boot to OS with crash error
any ideas ?
Click to expand...
Click to collapse
yldlj said:
You need to Fastboot boot twrp. Img
Click to expand...
Click to collapse
Alekcander said:
Came here from google.
This procedure didn't work for me, for some reason "fastboot boot twrp.img" was leading to black screen.
What worked for me was
1) Boot to fastboot
2) fastboot flash twrpXXX.img
3) Without rebooting, select recovery from fastboot's bootloader menu
4) If you are able to boot in twrp this time, then flash blu spark twrp.
5) Reboot
6) Try to reboot in recovery as usual
If all worked well, you should see twrp recovery.
Cheers.
Click to expand...
Click to collapse
I have the same problem as Alekcander
When I try to use command ,, fastboot boot twrp-xxx.img nothing happens. I mean mobile restart as always but there is only black screen and notification diode shine white ...
Also Alekcander method doesn't work:
C:\Android>fastboot flash twrp-3.3.1-x_blu_spark_v9.101_op6.img
unknown partition 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
error: cannot determine image filename for 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
I tried official twrp and is the same , I tried to disconnect from usb when mobile is restarting also nothing ...
so again ... I have restored phone with msn download -> unlock bootloader...
i have this issue sins i tried to install magisk and after reboot my OP6 doesn't boot to OS and give crash error
any other ideas ?

Solved I have to update system to more recently version. Why twrp doesn't work with oxygen is 5.1.5 ?

Flash TWRP via fastboot android 10

Hello guys, as we known that it is unable to use command in fastboot to boot into TWRP if we are on Android 10 (both OOS and Custom rom) at the moment, so here is the simple command allow us to do that if you want to roll back android 9 or any rom by TWRP
fastboot flash boot_a <twrp name.img>
fastboot flash boot_b <twrp name.img>
fastboot reboot
Your phone will automatically boot into TWRP, so you can flash another rom

Can anyone confirm this works?
I tried something similar when I first installed OOS 10, and I successfully booted TWRP, but I ended up getting a bootloop (stuck at the g.co/ABH warning thing) when I rebooted to system. I don't know if I did something wrong, or flashing twrp to both boot partitions caused it.
I would try again, but I'm on a critical work trip until the end of the month, so my phone's uptime is expected to be 100% until then.

worked for me while anything else didnt

LazerH said:
worked for me while anything else didnt
Click to expand...
Click to collapse
Does it wipe your data?

Didn't work for me. My boot image was patched already this is probably why.

ok, I tried this, but as reported above, now also stuck on this same: "I tried something similar when I first installed OOS 10, and I successfully booted TWRP, but I ended up getting a bootloop (stuck at the g.co/ABH warning thing) when I rebooted to system. I don't know if I did something wrong, or flashing twrp to both boot partitions caused it."
How do I resrore operation for my phone? (help?)

Well, I met this issue before, and ended up with using this method to successfully boot into twrp.
This issue seems to appear on OOS, when I using `fastboot boot xxx.img` on other ROM like omni, I'm able to boot into twrp, thanks!

can someone help me please. my phone is stuck in a fastboot bootloop. everything I try doesn't work.
fastboot boot TWRP.img NOTHING
tried your solution above and still nothing
Still stuck in fastboot this is what I get:
PS C:\Users\Les Brown\Desktop\OnePlus 6> fastboot boot twrp-3.3.1-17-enchilada-Q-mauronofrio.img
downloading 'boot.img'...
OKAY [ 0.617s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.655s

@killathenoob Download DECRYPTED OOS 10.3.0 with this help if you don't really know what to do with this.
For others people (and you if you want to root or just install TWRP after fresh OOS10 Decrypted install) don't forget to OEM unlock before doing anything.
Download this
Copy "twrp-3.3.1-17-enchilada-installer-mauronofrio.zip" into internal storage of your OP6
Power it OFF
Power it ON in fastboot mode
Launch "Boot TWRP.bat"
Connect your OP6 to your PC and wait for TWRP to boot
Install twrp-3.3.1-17-enchilada-installer-mauronofrio.zip
Reboot to recovery and install magisk if you need to.
Source
Hope I helped a bit.

Unable to flash TWRP. Lost Recovery, OS and only have unlocked bootloader.

Hi,
I was on Oxygen OS 10.0.0. Rooted with twrp-3.3.1-4-enchilada and magisk 20.1. (I had used this guide to do it. https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213) Today I downloaded the zip for 10.0.1 from the Oxygen Updater app and tried to flash it like I have done for OOS 9 in the past as usual. I went to recovery (I did not backup), I just wiped my data (not internal storage), cache and system. After that I tried to install the new zip but I got an error. It just said error unable to install. Didn't mention why. I tried flashing the older OOS 10 zip and got the same error.
So I thought I will try flashing on the other slot. I was on slot B. I switched to slot A and got the same error.
So I thought I will try to sideload. When I tried that I got the same error. So I thought I will try to reflash the twrp img itself. I went to fastboot mode and tried runnning this command
fastboot boot twrp-3.3.1-14-enchilada-Q-mauronofrio.img
It showed me this error
Sending 'boot.img' (65536 KB) OKAY [ 1.609s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Now I don't have any recovery at all. I have just the unlocked bootloader and no OS nor recovery. What can I do to flash TWRP again and install either OOS 10.0.1 zip or 10.0.0 zip? Any help will be great.
Thanks

Arnavzz said:
Hi,
I was on Oxygen OS 10.0.0. Rooted with twrp-3.3.1-4-enchilada and magisk 20.1. (I had used this guide to do it. https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213) Today I downloaded the zip for 10.0.1 from the Oxygen Updater app and tried to flash it like I have done for OOS 9 in the past as usual. I went to recovery (I did not backup), I just wiped my data (not internal storage), cache and system. After that I tried to install the new zip but I got an error. It just said error unable to install. Didn't mention why. I tried flashing the older OOS 10 zip and got the same error.
So I thought I will try flashing on the other slot. I was on slot B. I switched to slot A and got the same error.
So I thought I will try to sideload. When I tried that I got the same error. So I thought I will try to reflash the twrp img itself. I went to fastboot mode and tried runnning this command
fastboot boot twrp-3.3.1-14-enchilada-Q-mauronofrio.img
It showed me this error
Sending 'boot.img' (65536 KB) OKAY [ 1.609s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Now I don't have any recovery at all. I have just the unlocked bootloader and no OS nor recovery. What can I do to flash TWRP again and install either OOS 10.0.1 zip or 10.0.0 zip? Any help will be great.
Thanks
Click to expand...
Click to collapse
So basically what happened there is TWRP doesn't boot with the oxygenos 10 bootloader. You will need to use the MSM download tool to unbrick your device.
Sent from my ONEPLUS A6003 using Tapatalk

Kaleshwar said:
So basically what happened there is TWRP doesn't boot with the oxygenos 10 bootloader. You will need to use the MSM download tool to unbrick your device.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
But how is that? I was on stable OOS 10 before rooting following this link https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213. As per this, the first step is to flash twrp and that image did flash back when I did it. Any idea why it doesn't work now?
Also, do you have any links for the MSM download tool and any guide if there is?
Thanks

Arnavzz said:
But how is that? I was on stable OOS 10 before rooting following this link https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213. As per this, the first step is to flash twrp and that image did flash back when I did it. Any idea why it doesn't work now?
Also, do you have any links for the MSM download tool and any guide if there is?
Thanks
Click to expand...
Click to collapse
The problem isn't TWRP it's the bootloader. That's all I know. And for the MSM download tool. See attached link below.
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Sent from my ONEPLUS A6003 using Tapatalk

Do not boot the twrp from fastboot it won't work
Just do
Fastboot flash boot twrp.img
Then reboot the device to twrp it will boot to trwp and then flash the new a10 zip and immediately afterwards flash the twrp zip

chintu1234 said:
Do not boot the twrp from fastboot it won't work
Just do
Fastboot flash boot twrp.img
Then reboot the device to twrp it will boot to trwp and then flash the new a10 zip and immediately afterwards flash the twrp zip
Click to expand...
Click to collapse
This doesn't work. It flashes successfully but when I select Reboot Recovery and press the power button, it boots back to the bootloader.

Maybe wrong twrp img
Try the older 3.3.1-12 twrp.img and then try
Also try the following as well
Fastboot flash boot_a twrp.img
Fastboot flash boot_b twrp.img
And try just reboot not reboot to recovery

Kaleshwar said:
The problem isn't TWRP it's the bootloader. That's all I know. And for the MSM download tool. See attached link below.
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Thanks so much for that! I have been able to recover the phone using MSM download tool. Now will update to 10 using the phones OTA.
However, I have one question, if I update to OOS 10.0.1, do you think this original post on rooting OOS 10, will work for it? https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213 Or do you suggest to not root and wait?

Arnavzz said:
Thanks so much for that! I have been able to recover the phone using MSM download tool. Now will update to 10 using the phones OTA.
However, I have one question, if I update to OOS 10.0.1, do you think this original post on rooting OOS 10, will work for it? https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213 Or do you suggest to not root and wait?
Click to expand...
Click to collapse
You can try it . Looks pretty solid.
Sent from my ONEPLUS A6003 using Tapatalk

Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules first to avoid issues (in TWRP if you cannot boot to system. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242)
Update through local update to 10.3.2 is what I prefer to do. Then I do the following.
Reboot to let phone finish whatever. reboot into bootloader.
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-18-enchilada-Q-mauronofrio.img - ( https://sourceforge.net/projects/ma...3.3.1-18-enchilada-Q-mauronofrio.img/download )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3.2 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP (https://sourceforge.net/projects/ma...-enchilada-installer-mauronofrio.zip/download ) or Blu zip (https://github.com/engstk/android_device_oneplus_enchilada/releases)
5. Reboot to recovery
6. Flash Magisk 20.3 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://mega.nz/#!PO5x1bYA!dKq3pbxUdpb16zhuqM_idqvWNLnsu4Ky4IAmYQiQUDw
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853

I had similar situation last evening.
I made the mistake of having a factory reset on rooted 9.0.8 and then trying to flash the 10.0.1
I got the same error, so I had to connect my mobile to my laptop, fastboot to the newest TWRP, flash the TWRP, flash the 9.0.9, flash the 10.0.1, flash magisk 20.x and then everything was working.

xpakage said:
Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules
Update through local update 10.3 or current ROM
Reboot
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-16-enchilada-Q-mauronofrio.img - ( https://androidfilehost.com/?fid=4349826312261678088 )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP ( https://androidfilehost.com/?fid=4349826312261678087 ) or Blu zip (https://github.com/engstk/op6/releases/download/r112/blu_spark_r112-oos_op6-op6t_0dd5f9228.zip)
5. Reboot to recovery
6. Flash Magisk 20.1 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://drive.google.com/file/d/1w44cUg815g-H1h_6gObUVPLDTc_dtiMX/view
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Click to expand...
Click to collapse
This worked for me.. Finally. PS - I did in a slightly different order. I installed twrp first, booted into twrp, made sure I was in slot A. If I wasnt, I rebooted to recovery. If I still wasnt I set slot to A manually then rebooted to recovery again. Flashed the stock boot img you linked to boot, then rebooted to recovery slot b (same process I did to get to slot a) then flashed the stock boot img to boot again THEN finally installed magisk. Booted to system, where it hanged a bit, rebooted before getting into android, but booted in just fine after that..
For some reason if you don't flash stock img to slot A (and maybe slot B too, I did this for good measure) before installing magisk everything dies a horrible death and breaks, which can't even be recovered from /boot /system backups..
EDIT: Tried to reboot into recovery, which reverted back to stock for some reason after doing the above steps. So I proceeded to install the bluspark recovery, rebooted into recovery, made sure I was in slot b, made a back up of the boot image, then flashed bluspark kernel. Got stuck at the unlocked bootloader screen. Rebooted into recovery, restored my /boot back. Still stuck when I try to boot into system. Fixed it by booting back into recovery in slot A flashing stock boot img, then into slot b stock boot, then magisk, but also installed bluspark kernel here because I had a feeling I would lose twrp from flashing to stock boot img, and that the issue was caused by twrp (both twrp-3.3.1-16-enchilada-installer-mauronofrio and twrp-3.3.1-x_blu_spark_v9.108_op6 have this issue). Guess what? Turns out I was right. Having twrp breaks everything after you install magisk, so you need to flash the stock boot img before flashing magisk for some reason.. and cant install twrp again unless you dont mind bricking your phone.
EDIT2: F2FS works, just boot into recovery via fastboot (this should be slot b), change /data to f2fs, boot back into fastboot then into recovery again by fastboot (slot b again), flash stock boot img > magisk > bluspark kernel > f2fs_fstab.zip > f2fs_optimize.zip > factory reset/wipe (from twrp before rebooting), done just reboot into system. You of course lose twrp because magisk doesnt like twrp on oos 10.x for some reason, and will need to set everything up again to cause of the wipe. If you dont factory reset/wipe from twrp before booting into system your system will crash and reboot every time you boot into android, then have to do all the steps I listed again.
EDIT3: Never mind, I was wrong, f2fs makes almost all your apps and storage unusable. Not sure if it's cause of the rom (OOS10.3.0) or because we have to flash stock boot.img and get rid of twrp before booting into system. Either way, f2fs has never really been stable or fun to get working so better to stick to ext4.. that few percent performance boost isnt worth it.
EDIT4: This is my last update. After experimenting with different things, bricking my phone, restoring it via fastboot rom, many many times, I've verified the simplest and cleanest way to install magisk.. Do note you wont be able to keep twrp.
Method A - If you already have twrp
Boot recovery into slot a, flash your rom's stock boot.img, then boot into your recovery in slot b (dont boot into slot a recovery because slot a wont have twrp anymore), flash your rom's stock boot.img, magisk and (optional) your kernel of choice (or not) in that order, then you can boot boot into system. That's it.
Method B - If you don't have twrp
Boot into fastboot, and from your cmd/terminal run fastboot flash boot yourtwrp.img (I suggest Mauronofrio's twrp-3.3.1-16-enchilada-Q-mauronofrio.img or newer). Use your volume buttons to select boot into recovery. Make sure your active slot is B, (if it isnt, install twrp (bluspark and Mauronofrio's twrp both work great) by zip, then follow the steps above in method A). Once you've verified you're in slot B flash your rom's stock boot.img, magisk and (optional) your kernel of choice (or not) in that order, then you can boot into system. That's it.
Maybe @mauronofrio or @eng.stk can verify why magisk or twrp bricks the system when you install them together on OOS 10.

not working
sir i follow your steps but phone is stuck on boot i have official version a10 10.3.0 update on 25.12.19
pls tell me how i get root access....

gauravkapoor99150 said:
sir i follow your steps but phone is stuck on boot i have official version a10 10.3.0 update on 25.12.19
pls tell me how i get root access....
Click to expand...
Click to collapse
U need to flash the magisk v22 zip file through the .108 TWRP recovery
Sent from my ONEPLUS A6003 using Tapatalk

RASTAVIPER said:
U need to flash the magisk v22 zip file through the .108 TWRP recovery
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
sir can you send me a link

lemon07r said:
Maybe @mauronofrio or @eng.stk can verify why magisk or twrp bricks the system when you install them together on OOS 10.
Click to expand...
Click to collapse
@mauronofrio wrote the following in his TWRP thread a while ago:
So little update, after some tests i'm sure there is a compatibility problem between twrp and magisk, i was able to get only one of them, so actually i don't know how to proceed, i need to understand if it is a twrp problem or a magisk problem, TWRP is in stand-by for now.
There are not problems on Android Pie, if you need of the twrp on android Q just flash in boot partition the Q .img (fastboot flash boot twrp.img) and then reboot from fastboot in recovery. Before publishing the twrp I had not tested magisk and twrp together.
On Android 10 use only magisk 19.4
Click to expand...
Click to collapse

xpakage said:
Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules first to avoid issues (in TWRP if you cannot boot to system. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242)
Update through local update to 10.3.2 is what I prefer to do. Then I do the following.
Reboot to let phone finish whatever. reboot into bootloader.
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-18-enchilada-Q-mauronofrio.img - ( https://sourceforge.net/projects/ma...3.3.1-18-enchilada-Q-mauronofrio.img/download )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3.2 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP (https://sourceforge.net/projects/ma...-enchilada-installer-mauronofrio.zip/download ) or Blu zip (https://github.com/engstk/android_device_oneplus_enchilada/releases)
5. Reboot to recovery
6. Flash Magisk 20.3 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://mega.nz/#!PO5x1bYA!dKq3pbxUdpb16zhuqM_idqvWNLnsu4Ky4IAmYQiQUDw
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Click to expand...
Click to collapse
Basically worked for me, too, with 2 exceptions:
- this tool to remove magisk modules etc. wouldn't be flashed, always ended in an unnamed error; probably the cause for some other problems?
- flashing boot.img (V 10.3.4 from this thread) didn't work for me, I always ended up in twrp's splash screen
- got it solved by dirty flashing the full V 10.3.4 ROM (again from the above thread)
Many thanks once again!