Database Info

Booting TWRP Advice

HTCDreamOn said:
A word of advice: I strongly recommend temporarily booting any images (be it recoveries or kernels) you are about to flash to your device. This is simply a case of using the command "fastboot boot blahblah.img" whether blahblah.img is a recovery or kernel.
Click to expand...
Click to collapse
We know you can boot to TWRP vice flash to your device by using the command:
Code:
fastboot boot twrp.img
But how do you proceed from here? Are you required to use ADB commands at this point or can you unplug your USB cable and use TWRP as if it was installed, I.E. , back up current ROM, and install new zip.

purplepizza said:
We know you can boot to TWRP vice flash to your device by using the command:
Code:
fastboot boot twrp.img
But how do you proceed from here? Are you required to use ADB commands at this point or can you unplug your USB cable and use TWRP as if it was installed, I.E. , back up current ROM, and install new zip.
Click to expand...
Click to collapse
Sorry if I wasn't clear. Yes you can unplug usb and use as normal, it just means twrp isn't flashed to the device so it won't be there when you reboot.
I just recommend this step because I'm paranoid. Once you've confirmed the image works you should reboot to bootloader and fastboot flash the image, then you'll be able to boot into twrp whenever you want.

HTCDreamOn said:
Sorry if I wasn't clear. Yes you can unplug usb and use as normal, it just means twrp isn't flashed to the device so it won't be there when you reboot.
I just recommend this step because I'm paranoid. Once you've confirmed the image works you should reboot to bootloader and fastboot flash the image, then you'll be able to boot into twrp whenever you want.
Click to expand...
Click to collapse
This is a good step to do, and if the device supports it it should be used... for example the Moto G (if unlocked) fully supports fastboot boot commands, devices like the HTC One M7 do NOT support this anymore...
To the OP, what is really happening here is that TWRP or the boot.img (kernel) is being loaded from USB into RAM and executed normally, instead of the standard /boot partition which is skipped when executing fastboot boot. TWRP (and recovery in general) is really just a specialized micro-sized android distribution and when started via fastboot boot is executed as if it was the boot image. Once the image is transferred into RAM, the boot continues normally per the instructions of TWRP or the boot image, and no further action via USB is required. USB is just the medium to load the image into RAM and nothing more.
fastboot boot - used to manually load a boot image (or recovery) and execute from RAM, it is not flashed to the device, on the next reboot it will return to it's previous state
fastboot flash boot/recovery - used to actually flash the boot image or recovery image to the it's appropriate partition on the device, it does not execute it. On a reboot or factory default this information will stay in the device.

acejavelin said:
This is a good step to do, and if the device supports it it should be used... for example the Moto G (if unlocked) fully supports fastboot boot commands, devices like the HTC One M7 do NOT support this anymore...
To the OP, what is really happening here is that TWRP or the boot.img (kernel) is being loaded from USB into RAM and executed normally, instead of the standard /boot partition which is skipped when executing fastboot boot. TWRP (and recovery in general) is really just a specialized micro-sized android distribution and when started via fastboot boot is executed as if it was the boot image. Once the image is transferred into RAM, the boot continues normally per the instructions of TWRP or the boot image, and no further action via USB is required. USB is just the medium to load the image into RAM and nothing more.
fastboot boot - used to manually load a boot image (or recovery) and execute from RAM, it is not flashed to the device, on the next reboot it will return to it's previous state
fastboot flash boot/recovery - used to actually flash the boot image or recovery image to the it's appropriate partition on the device, it does not execute it. On a reboot or factory default this information will stay in the device.
Click to expand...
Click to collapse
Thanks. So it seems there is no reason to ever flash TWRP unless you don't want the PC dependence to use the TWRP tool.

purplepizza said:
Thanks. So it seems there is no reason to ever flash TWRP unless you don't want the PC dependence to use the TWRP tool.
Click to expand...
Click to collapse
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...

acejavelin said:
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
Click to expand...
Click to collapse
I understand what you are saying. The only flash I planned on was SuperSU. I thought when a system upgrade is available, I could simply use SU to unroot and be ready for the update. Would this work?
If I followed your recommendation, could I feasibly, flash TWRP, then when an upgrade is ready, flash nandroid backup (which I assume removes TWRP) then accept system update, then re-flash TWRP. I could restore apps by using TB. Does this make sense? Or does TWRP remain in place after flashing nandroid backup?

purplepizza said:
I understand what you are saying. The only flash I planned on was SuperSU. I thought when a system upgrade is available, I could simply use SU to unroot and be ready for the update. Would this work?
If I followed your recommendation, could I feasibly, flash TWRP, then when an upgrade is ready, flash nandroid backup (which I assume removes TWRP) then accept system update, then re-flash TWRP. I could restore apps by using TB. Does this make sense? Or does TWRP remain in place after flashing nandroid backup?
Click to expand...
Click to collapse
TWRP remains in place after restoring a nandroid (I think, I haven't installed on my Moto G, but in most devices it doesn't backup/restore recovery), but you can easily restore the original recovery via fastboot.

acejavelin said:
TWRP remains in place after restoring a nandroid (I think, I haven't installed on my Moto G, but in most devices it doesn't backup/restore recovery), but you can easily restore the original recovery via fastboot.
Click to expand...
Click to collapse
Just curious, how did you go from 5.1.1 to 6.0?

purplepizza said:
Just curious, how did you go from 5.1.1 to 6.0?
Click to expand...
Click to collapse
OTA... part of soak test on December 22.

acejavelin said:
OTA... part of soak test on December 22.
Click to expand...
Click to collapse
Hey thanks for helping to answer this, your explanation was much better I thought it had something to do with loading into RAM but wasn't sure. I didn't know some devices don't allow fastboot boot commands though, I've always relied on them. Part of the reason I'm avoiding htc now.
@purplepizza I agree with everything acejavelin has said: essentially you really do want to make sure your have twrp flashed.
To answer your nandroid question: It basically just takes an image of the partitions you choose, usually /system, /data, and /boot (where kernel stuff is) which is the least you need to boot back with all your data. It doesn't backup recovery and when you restore it doesn't write anything to recovery, so yes twrp will still be in place. In general you should only ever flash stuff to the recovery partition whilst in fastboot mode (i.e. using fastboot flash recovery recovery.img), I know on some devices you can flash recoveries as zip files in the recovery itself but you shouldn't.
I've seen quite a few people querying about the 6.0 OTA: in short, I wouldn't worry about it because once they start rolling out, people always catch the OTA and post here on xda. You can flash that and it'll return you to stock 6.0 anyway, at which point you can reroot and everything if you want.

acejavelin said:
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
Click to expand...
Click to collapse
One more question, when making the first nandroid backup. do you just back up system and data or do you include boot as well?

purplepizza said:
One more question, when making the first nandroid backup. do you just back up system and data or do you include boot as well?
Click to expand...
Click to collapse
My opinion is always backup everything, you can always choose what to restore
Sent from my MotoG3 using Tapatalk

acejavelin said:
My opinion is always backup everything, you can always choose what to restore
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
So what is boot? I know I am kind of going back to my previous question, but if I restore boot, is that the boot loader? I would assume this would not commonly need restored?
And I now assume the bootloader is completely independent from recovery.

purplepizza said:
So what is boot? I know I am kind of going back to my previous question, but if I restore boot, is that the boot loader? I would assume this would not commonly need restored?
And I now assume the bootloader is completely independent from recovery.
Click to expand...
Click to collapse
It is not the bootloader... It is the /boot partition of the phone, basically the kernel and RAM disk. If you screw things up and need to restore, you typically want to restore /boot, /system, and /data, and occasionally /cache (if you want to restore to save time and get an exact duplicate of the previous image, otherwise many people skip /cache and let it rebuild on the first boot which takes 10-15 minutes extra).

acejavelin said:
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
Click to expand...
Click to collapse
HTCDreamOn said:
@purplepizza I agree with everything acejavelin has said: essentially you really do want to make sure your have twrp flashed.
Click to expand...
Click to collapse
So I am following your advice. I booted to TWRP, made Nandroid backup.
Rebooted and flashed TWRP, see below:
Code:
sudo fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (7772 KB)...
OKAY [ 10.635s]
writing 'recovery'...
OKAY [ 0.141s]
finished. total time: 10.776s
All seems OK.
Scrolled to recovery, selected recovery. TWRP was there. I then powered down.
After that I held power and volume down, system boots to dead Android with message “No command” Held power then volume up, I see stock boot loader. Is TWRP flashed somewhere or is it gone? So what did I do wrong.

purplepizza said:
So I am following your advice. I booted to TWRP, made Nandroid backup.
Rebooted and flashed TWRP, see below:
Code:
sudo fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (7772 KB)...
OKAY [ 10.635s]
writing 'recovery'...
OKAY [ 0.141s]
finished. total time: 10.776s
All seems OK.
Scrolled to recovery, selected recovery. TWRP was there. I then powered down.
After that I held power and volume down, system boots to dead Android with message “No command” Held power then volume up, I see stock boot loader. Is TWRP flashed somewhere or is it gone? So what did I do wrong.
Click to expand...
Click to collapse
I have no idea, you did it right... selecting recovery from the bootloader should start TWRP, not stock recovery, that should be gone.

acejavelin said:
I have no idea, you did it right... selecting recovery from the bootloader should start TWRP, not stock recovery, that should be gone.
Click to expand...
Click to collapse
Any recommendations how to proceed?

I also need help with my soft bricked moto g3
Moto g3 (xt 1550, Indian dual sim 16 gb version)
I officially upgraded to 6.0.0 via ota and my objective was to root my phone and use xposed modules. I am not interested in any other custom rom (I'd rather keep stock rom just for moto display and ota upgrades) or custom recovery like twrp(I'm afraid it may cause ota upgrades to fail).
I used the method described here in the question- http://android.stackexchange.com/qu...rsu-using-play-store-versus-a-custom-recovery
So I first successfully unlocked my bootloader using the official motorola method.
I then proceeded to use google's backup settings to re-install all the apps that were uninstalled due to unlocking the bootloader. I also put supersu.zip version 2.46 on internal sd card.
I then proceeded to (without rebooting) enter fastboot where i used minimal adb to temporarily boot into twrp version2.8.7 r5 (link - http://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537 ).
Once in twrp, I located and flashed the supersu.zip. It flashed successfully. I procceded to clear dalvik cache and then after clearing cache I tried to reboot my phone using twrp.
However, it did not go beyond the "Warning - Bootloader Unlocked" screen that you get on unlocking a motorola bootloader. I left it for over 10 minutes (usb was still plugged in, I had >80% battery) but it did not proceed.
Long -pressing the power button causes the phone to vibrate and again attempt to boot, stuck at the same initial screen. Adb quite understandably does not work here.
I can press vol down+power and enter fastboot , where adb works fine.
I can enter stock recovery from the fastboot sceen too.
Using adb in fastboot, I am able to boot twrp . In fact, I tried to re-install supersu.zip. I retried version 2.46 and then tried version 2.56. On all occcassions, it was able to successfully flash it, but gets hung on the initial boot screen.
USB Debugging is also enabled, and I have a backp of my sd card data.
I tried taking a backup of the system and apps in twrp (3 gb in total) and tried to reflash it, but it still hangs at the same screen.
Is there any way I can unbrick my device and- (in decreasing order of preference)
1. Keep my stock rom and recovery?
2. Keep stock rom with twrp? (It should not be a problem)
3. Custom rom with custom recovery - perhaps official cm. Least preferred as I want Moto Display and stock/vanilla android.
Also, is SELinux involved anywhere with my phone getting bricked? I also read that a custom kernel is required for rooting 6.0, which I don't have. Supersu Version 2.56 is said to prevent soft bricks if the kernel is incorrect (systemless root), yet even after flashing the newer one it is still bricked. Where am I going wrong? What should I do? Thanks in advance! :good:

purplepizza said:
Any recommendations how to proceed?
Click to expand...
Click to collapse
Try the flash again? Sorry, but I don't really know help... if you are successfully rooted, perhaps try to flash TWRP image with Flashify? (select your file, don't let it auto-grab an image)

acejavelin said:
Try the flash again? Sorry, but I don't really know help... if you are successfully rooted, perhaps try to flash TWRP image with Flashify? (select your file, don't let it auto-grab an image)
Click to expand...
Click to collapse
I have not rooted yet. I guess I can try by booting TWRP then flashing SuperSU.
Can you think of any reasons not to try fastboot again the re-flash TWRP?

Fixing a trashed "A" boot partition

My device is a rooted, TWRP-enabled OnePlus 7 Pro ... GM1917.
Through some failed flash attempts in the past, I hosed my "A" boot partition, meaning that I can't boot into it, nor do any meaningful work in it via TWRP. The data partition is empty and cannot be written to when I boot into TWRP via the "A" partition. My "B" partition is fine, and my device is running fine with that partition active.
Is there any way to get my "A" boot partition back to being properly functional without messing up my current device configuration? For example, one question I have is this: if I format the data partition in TWRP when I'm booted into the "A" partition, will it format the working data partition that I see when I boot into "B", thereby causing me to lose everything that is currently resident on this data partition?
I don't have a good understanding of the A/B boot partition methodology, so any help will be greatly appreciated.
.​

I think you should do a clean factory reset
https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/

sonvotrung said:
I think you should do a clean factory reset
https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/
Click to expand...
Click to collapse
Thank you, and I agree. I tried a few things via fastboot, but they didn't fix the problem.
Playing with TWRP, fastboot, and boot slots has been an over-complicated headache.
In following your link and reading, I see that this is the flash download that I need:
https://otafsg1.h2os.com/patch/amaz...ygen_21.O.16_OTA_016_all_1908281716_b2bb5.zip
I downloaded it. Then, does the following procedure appear to be correct? ...
First, back up everything that's important on my data partition. Then, from my desktop ...
Code:
fastboot --set-active=b
fastboot reboot bootloader
... just to make sure that "B" is indeed currently the active partition, which it should be.
I should then boot back into my system and flash that ROM I downloaded.
I should flash it via Settings->System update->Local upgrade.
After the system reboots and I get it initialized, I should make sure that OEM unlocking is set,
I can then boot back into the bootloader and do the following
Code:
fastboot flashing unlock
Then, after the system reboots again and I make sure my system is set up properly, I should reboot yet again to the boot loader.
I should then run this command:
Code:
fastboot boot twrp-3.3.1-4-guacamole.img
This should bring up TWRP recovery. Inside of TWRP, I should go into Advanced->Sideload, and then from my desktop ...
Code:
adb sideload twrp-installer-3.3.1-4-guacamole.zip
In TWRP, I should go back to sideload and then do the following from my desktop ...
Code:
adb sideload Magisk-v20.1.zip
At this point, I should boot back into my system and get everything restored and set up the way I want.
Does this all look correct?
Thank you again!
.​

Hmmm.. happened to my boot a partition too.. it cant boot because i flashed dm verity or something like that hoping that it would erase the lock pattern before entering and decrypting TWRP. but it failed. Took.me about an hour before i noticed that if i boot my phone to partition B.. its working fine.. when i boot to B.. i have read somewhere that android 10 installs on inactive slot..so i gambled to see if it would.fix my partition A that i think has been corrupted.. and so.it. worked. I lost my root and TWRP BECAuse i rebooted too soon..but hey... Patching my boot img with magisk..gives me a rooted device again...
So,. Im suggesting to flash ANDROID 10 FULL ROM.VIA Local upgrade then reboot.. i think it will be installed to your inactive slot and will fix the corrupt issue.. ehehehehe

santiagoruel13 said:
Hmmm.. happened to my boot a partition too.. it cant boot because i flashed dm verity or something like that hoping that it would erase the lock pattern before entering and decrypting TWRP. but it failed. Took.me about an hour before i noticed that if i boot my phone to partition B.. its working fine.. when i boot to B.. i have read somewhere that android 10 installs on inactive slot..so i gambled to see if it would.fix my partition A that i think has been corrupted.. and so.it. worked. I lost my root and TWRP BECAuse i rebooted too soon..but hey... Patching my boot img with magisk..gives me a rooted device again...
So,. Im suggesting to flash ANDROID 10 FULL ROM.VIA Local upgrade then reboot.. i think it will be installed to your inactive slot and will fix the corrupt issue.. ehehehehe
Click to expand...
Click to collapse
Thank you. Yes, I plan to flash the new 10.0.2 ROM soon, and I am glad to know from your experience that this should indeed solve my problem with the "A" slot.
Regarding dm-verity ... did you ever get that to work? I want to decrypt my phone, but I'm still not confident that dm-verity will work for me.

HippoMan said:
Thank you. Yes, I plan to flash the new 10.0.2 ROM soon, and I am glad to know from your experience that this should indeed solve my problem with the "A" slot.
Regarding dm-verity ... did you ever get that to work? I want to decrypt my phone, but I'm still not confident that dm-verity will work for me.
Click to expand...
Click to collapse
Nope.. i cant seem to make it work.. it just messes up and corrupt my phone partition slot.. dont know why.
It says decrypting phone.. successful.. and then.. it wont boot.

santiagoruel13 said:
Nope.. i cant seem to make it work.. it just messes up and corrupt my phone partition slot.. dont know why.
It says decrypting phone.. successful.. and then.. it wont boot.
Click to expand...
Click to collapse
Thank you. You have saved me a big headache, because now I won't even try to decrypt.
I'll keep investigating decryption, however, and if I can get it to work, I'll let you know
There seem to be a lot of posts in the following thread where people report problems similar to yours, so maybe we just have to wait until there is some sort of enhancement to dm-verity, or perhaps a new method for decrypting.
The thread: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
PS: I just saw this message: https://forum.xda-developers.com/showpost.php?p=80185974&postcount=599
This person first formatted data, then rebooted TWRP, then did a factory reset, and then did the rest of the flashing.
Also, as you can see, the flashing was done twice, with a TWRP reboot in between.
Did you perform that many steps when you tried to decrypt via dm-verity?
.​

Boot to twrp
Format data
Reboot twrp again
Flash A10.01 rom
Flash TWRP
REBOOT TWRP
Flash decrypt via dm verity
REBOOT.. STUCK..

santiagoruel13 said:
Boot to twrp
Format data
Reboot twrp again
Flash A10.01 rom
Flash TWRP
REBOOT TWRP
Flash decrypt via dm verity
REBOOT.. STUCK..
Click to expand...
Click to collapse
In the other message whose link I posted, the writer did repeated flashing and more rebooting, including 3 dm verity flashes.
I think this multiple flashing and rebooting might be necessary because of the A/B slots, but I'm not sure ...
Format data,reboot twrp,factory reset,flash rom ,flash twrp ,flash dm verity.
Reboot again twrp
flash again rom,twrp,dm verity
Reboot twrp
flash gapps(when nedded)magisk(im using 19.4) flash dm verity.
Reboot system.
Click to expand...
Click to collapse
I'll have time to try all this on the weekend.

I fixed the problem via the following steps ...
(1) uninstall all Magisk modules
(2) reboot to System
(3) install the 10.0.2 OOS ROM via System Update->Local upgrade
(4) boot to bootloader
(5) "fastboot boot twrp.img" (version 3.3.1-70)
(6) go into Sideload and flash the twrp 3.3.1-70 installer
(7) reboot recovery
(8) go into Sideload and flash Magisk 20.1
(9) reboot to System
(10) reinstall the xXx-NoLimits ROM (version 9.3) via Magisk
In the process, I ended up with 10.0.2, as well.

OnePlus 6 unable to boot into TWRP -- cannot reinstall OOS. Next steps?

OnePlus 6, Ubuntu 18.04. I think I've basically wiped everything.
I am trying to follow https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 but I can't get either of these to boot:
Code:
fastboot boot TWRP.img
or
Code:
fastboot boot twrp-3.3.1-2-enchelada.img
Doing this gives me the OnePlus logo with "Fastboot Mode" underneath and it hangs.
I've tried
Code:
fastboot --set-active=b
fastboot flash slot_b TWRP.img
and
Code:
fastboot flash slot_b twrp-3.3.1-2-enchilada.img
Rebooting into slot_b recovery gives me the warning about "The boot loader is unlocked and software integrity cannot be guaranteed. ... PRESS POWER KEY TO PAUSE BOOT" and then it hangs.
I am trying to get back to stock OOS so I can try Havoc but I'll settle for the former just to get the phone working.
I have a nandroid backup, I rsynced my /sdcard, and I have a Titanium backup.
I really need some guidance here...

What should I make of
Code:
$fastboot erase recovery
erasing 'recovery'...
FAILED (remote: Check device console.)
iconoclasthero said:
OnePlus 6, Ubuntu 18.04. I think I've basically wiped everything.
I am trying to follow https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 but I can't get either of these to boot:
Code:
fastboot boot TWRP.img
or
Code:
fastboot boot twrp-3.3.1-2-enchelada.img
Doing this gives me the OnePlus logo with "Fastboot Mode" underneath and it hangs.
I've tried
Code:
fastboot --set-active=b
fastboot flash slot_b TWRP.img
and
Code:
fastboot flash slot_b twrp-3.3.1-2-enchilada.img
Rebooting into slot_b recovery gives me the warning about "The boot loader is unlocked and software integrity cannot be guaranteed. ... PRESS POWER KEY TO PAUSE BOOT" and then it hangs.
I am trying to get back to stock OOS so I can try Havoc but I'll settle for the former just to get the phone working.
I have a nandroid backup, I rsynced my /sdcard, and I have a Titanium backup.
I really need some guidance here...
Click to expand...
Click to collapse

What rom was installed last before all this began.

MrSteelX said:
What rom was installed last before all this began.
Click to expand...
Click to collapse
Havoc OS (Havoc-OS-v3.1-20200120-enchilada-Official.zip). The problem was that somehow my pin got corrupted/changed after my first couple of boots into Havoc. That precipitated a big mess.
That said, I switched to my desktop (also running Ubuntu 18.04) and got a new version of the SDK directly from android.com, and replaced the files that came from the repo. That was able to do the formatting and install the stock image so now I just need to go through the procedure again...
I wish I'd had a better sense of what was going on with the partition table/fstab/blkid because I was able to get in with adb shell and I theoretically could have manually formatted...

iconoclasthero said:
OnePlus 6, Ubuntu 18.04. I think I've basically wiped everything.
I am trying to follow https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 but I can't get either of these to boot:
Code:
fastboot boot TWRP.img
or
Code:
fastboot boot twrp-3.3.1-2-enchelada.img
Doing this gives me the OnePlus logo with "Fastboot Mode" underneath and it hangs.
I've tried
Code:
fastboot --set-active=b
fastboot flash slot_b TWRP.img
and
Code:
fastboot flash slot_b twrp-3.3.1-2-enchilada.img
Rebooting into slot_b recovery gives me the warning about "The boot loader is unlocked and software integrity cannot be guaranteed. ... PRESS POWER KEY TO PAUSE BOOT" and then it hangs.
I am trying to get back to stock OOS so I can try Havoc but I'll settle for the former just to get the phone working.
I have a nandroid backup, I rsynced my /sdcard, and I have a Titanium backup.
I really need some guidance here...
Click to expand...
Click to collapse
It looks like you had android 10 and you flashed official twrp, which is android 9 only, which happened to me before. I could recommend using this to flash OOS through fastboot.

[email protected] said:
It looks like you had android 10 and you flashed official twrp, which is android 9 only, which happened to me before. I could recommend using this to flash OOS through fastboot.
Click to expand...
Click to collapse
I haven't checked to see what, if any, recovery is on there now. I'm assuming that the stock one was flashed on when I was able to get 10.3.0-OnePlus6Oxygen_22_OTA_042_all_1912142031_0fb330-FASTBOOT.zip. Now that I've got it working again, how do I put Havoc on it? Isn't that based on Android 10 ... ?
I found this in one of the many tabs I had open from figuring all this out: https://del.dog/pelihovape.txt. I wish it had some version numbers!

iconoclasthero said:
I haven't checked to see what, if any, recovery is on there now. I'm assuming that the stock one was flashed on when I was able to get 10.3.0-OnePlus6Oxygen_22_OTA_042_all_1912142031_0fb330-FASTBOOT.zip. Now that I've got it working again, how do I put Havoc on it? Isn't that based on Android 10 ... ?
I found this in one of the many tabs I had open from figuring all this out: https://del.dog/pelihovape.txt. I wish it had some version numbers!
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815 ?

iconoclasthero said:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815 ?
Click to expand...
Click to collapse
iconoclasthero said:
I haven't checked to see what, if any, recovery is on there now. I'm assuming that the stock one was flashed on when I was able to get 10.3.0-OnePlus6Oxygen_22_OTA_042_all_1912142031_0fb330-FASTBOOT.zip. Now that I've got it working again, how do I put Havoc on it? Isn't that based on Android 10 ... ?
I found this in one of the many tabs I had open from figuring all this out: https://del.dog/pelihovape.txt. I wish it had some version numbers!
Click to expand...
Click to collapse
I was looking around but I could not find what is going on with Havoc OS. I would probably recommended choosing a better maintained ROM with up to date instructions and support. Maybe Pixen or something. I was only able to find this old thread. Maybe you have better luck.
But if you really want Havoc, figure out first if it is androdi 9 or 10. If it is 10, use malfuriono unofficial twrp. If it is 9, you have to downgrade to OOS 9.0.9 first. Also, dirty flashes tend to cause problems, I would not recommended doing that. Make sure you wipe appropriate partitions

Xiaomi Redmi Note 4 (Snapdragon) flashing problem.

Hi guys Zeph here.
I've just rooted my Redmi Note 4 without any problems. I've tried to install several custom ROMs like HAVOC, Pixel, etc using TWRP but it showed some error I don't know. My backup ROM did not install so I've tried to install Global Stable ROMS from Internet but those were shown as corrupt. I've also tried using fastboot, ADB sideloader but same problems are happening. So basically my phone is just a hollow without any OS. Any solutions please because that is my only phone.
Here are some screenshots..

Can you boot up normally?
If not what happens, when you try?

gabtit7 said:
Can you boot up normally?
If not what happens, when you try?
Click to expand...
Click to collapse
Sorry when the backup ROM didn't get installed I had completely wiped all data for sake of installing Global custom ROMs. But it still didn't get installed. So my phone is like DOS without any OS.

Oh. Well thats a problem.
First of all:
Go to https://c.mi.com/oc/miuidownload/detail?device=1700309
dowload the rom (its a zip) and transfer it to your phone
go to twrp
flash it with twrp
reboot to system
Now if (while booting up) it says "The system has been destroyed":
Just keep booting in twrp, back to system, back to fastboot and repeat for some time and multiple times a day. For some reason thats how you call the autorepair to wake up, it will remove the ROM you just installed and probably install a backup one on its own
If this doesnt work too:
I will suppose you have a pc with fastboot & adb drivers available
Since the phone is alr in deep s***, lets try something quite risky
1)
go to twrp > wipe > format data
2)
connect your phone to pc while in fastboot
and execute these commands
fastboot erase system
fastboot erase cust
fastboot erase boot
fastboot erase vendor
CAREFUL: NOW YOUR PHONE IS BRICKED, BUT FIXABLE (probably)
3)
repeat the steps on the top of this message
All this should fix the problem, if not i am sorry but the phone will be unrepairable without any professional technician

Need help restoring my pixel 5

Good morning all I need some help unbricking my pixel 5. I have exhausted all possible avenues that I'm aware of to restore my phone out of bootloop. At the time I messed it up I was attempting to use twrp. In an attempt to fix the phone I tried flashing the system,and boot to no avail repeatedly getting the error "boot.img missing command-line or os version" as well as using the flash all from the stock firmware file. The current active slot is b and the a/b partition thing is new to me so I'm sure somewhere along the way I missed something. Any help is greatly appreciated .

Could you try this fastboot command and see if it works?
fastboot --set-active=a

I did try that however I'm not sure i was doing it correctly is it typed the way you typed it out?

Reboot the phone into the bootloader, look up how to do that if you don't know how, and then manually flash a rom or use the Android Flash Tool. The latter option is recommended if you are a novice.

I wouldn't say I'm novice lol but more out of the game too long either way thank you for your assistance I will try that as soon as I get a chance and report back

UPDATE your advice worked and I was able to reboot properly thank you in a side note is it impossible at this time to install twrp on a pixel 5?

musiv2 said:
UPDATE your advice worked and I was able to reboot properly thank you in a side note is it impossible at this time to install twrp on a pixel 5?
Click to expand...
Click to collapse
Yes. The Pixel series, as with most A/B devices, do not have a bespoke recovery partition. The recovery kernel is compressed into the boot image. TWRP does not support compression in this way so it cannot be used as a replacement for the stock recovery. The only effective way to use TWRP is to live boot the image, use TWRP to do whatever you need to do, without installing it to /boot.
BTW the next time you need to restore your phone you can use the Android Flash Tool.

Ok thank you for the explanation as I stated before I am new to the a/b partitioning way of android life so I have alot to learn

I used twrp in the past( on no A/B devices) but would recommend learning fastboot/adb. First step: always make sure USB debugging is enabled after every flash. This will make it so you can fix a lot of mistakes and recover your device. It's the first thing I do after every boot on a new install.
Here's the commands to flash stock to both slots. NOTE: this is for android 13. 12 and before will be a little different. Bootloader, radio and rom names should be exact to file, this is just for example.
fastboot --slot=all flash bootloader bootloader.img
fastboot reboot bootlaoder
fastboot --slot=all flash radio radio.img
fastboot reboot bootlaoder
fastboot --slot=a --skip-reboot update stock-image.zip
fastboot reboot bootlaoder
fastboot --slot=b --skip-reboot update stock-image.zip
fastboot -w
fastboot reboot
One final note: I put slot a first but I always start with the active slot(it's in the bootloader screen). If you want the android 12 instructions, let me know but it's not much different, you just use the stock recovery.