Database Info

[RECOVERY][UNOFFICIAL] TWRP for Xiaomi Redmi 6 (cereus) by TWRPBuilder

TWRP Recovery 3.2.3-0 For Xiaomi Redmi 6 (cereus) by TWRPBuilder
​
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Welcome, all Redmi 6 users, This is Lastest TWRP Recovery For your device By TWRPBuilder Team
CHANGELOG for 3.2.2-0:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
Downloads​Xiaomi Redmi 6 Recovery img
​
Sources:
Code:
[CENTER][URL="https://github.com/TwrpBuilder/android_device_xiaomi_cereus"][COLOR="bule"]Device tree[/COLOR][/URL]
[URL="https://github.com/TeamWin/Team-Win-Recovery-Project"][COLOR="bule"]TeamWin Github
[/COLOR][/URL][/CENTER]
How to install:
You must have fastboot installed on your pc and then:
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
Notes:
You have to disable force encryption in order to access data partition:
- Format data
- Flash Magisk DFE or DisableForceEncryption zip, attached below.
- If you flashed miui global/china you must flash magisk or the DisableForceEncryption zip before rebooting to the system, or recovery will be replaced!
Don't Forget to Hit Thanks :good:
https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253

Screenshots
attached :silly:

and this also

Anyone tried? Does it work?

Works for redmi 6 pro?

i dont get it, i've tried several times to install this twrp.img.
but as soon as i reboot {fastboot boot twrp.img} it just goes into the system, instead of recovery, and then when trying to reboot to recovery its still the xiaomi recovery.
how do i prevent it from constantly replacing the twrp with the standard recovery??
i dont know how to install magisk or the other zip if i even cant get into twrp...

mauritsivs said:
i dont get it, i've tried several times to install this twrp.img.
but as soon as i reboot {fastboot boot twrp.img} it just goes into the system, instead of recovery, and then when trying to reboot to recovery its still the xiaomi recovery.
how do i prevent it from constantly replacing the twrp with the standard recovery??
i dont know how to install magisk or the other zip if i even cant get into twrp...
Click to expand...
Click to collapse
same here: no chance to boot into twrp, even tough flash was successful

webc82 said:
same here: no chance to boot into twrp, even tough flash was successful
Click to expand...
Click to collapse
it actually works. Make sure you keep the vol+ button pressed for a while when you do the fastboot boot command.
It will eventually go to a black screen after the mi logo. now wait about one minute and press the volume buttons and twrp suddenly appears!!.
After installing ROM, it got soft-bricked, Had to wipe cache and dalvik again after rebooting, then it worked.

jackint said:
Works for redmi 6 pro?
Click to expand...
Click to collapse
No, it's different device

1.installed DisableForceEncryption_Treble.zip would restart forever.
2.MTP/ADB sideload don't work
3.everytime reboot show “Android System there's an internal problem with your device.Contact your manufactirer for details."
4. reboot is very solw.

Dachtire said:
1.installed DisableForceEncryption_Treble.zip would restart forever.
2.MTP/ADB sideload don't work
3.everytime reboot show “Android System there's an internal problem with your device.Contact your manufactirer for details."
4. reboot is very solw.
Click to expand...
Click to collapse
I have the same “Android System there's an internal problem with your device.Contact your manufacturer for details." message after installing global rom 9.6.4 and DFE
And i couldnt get my sim card working
has anyone been able to install a working rom on this device?

TWRP is not working.

I flash Magisk successfully and reboot the system normally. when i go back to twrp i don't find mount data. when my flash ROM from micro sd will work? please answer dev @TwrpBuilder

(Rom from Xiaomi.eu)
TWRP is working. But do not install custom rom. (Rom from Xiaomi.eu)

Good news. Now waiting a lineageos rom to leave MIUI.

gogojuy said:
TWRP is working. But do not install custom rom. (Rom from Xiaomi.eu)
Click to expand...
Click to collapse
If flash rom miui stable grobal wil work?

What is Xiaomi's wait time for unlocking BL on this device?

unlock time was 15 days for me...
i succesfully unlocked with no problems.
after flashing TWRP i ran into the same problems like Dachtire:
“Android System there's an internal problem with your device.Contact your manufactirer for details."
Click to expand...
Click to collapse
SIM wasn't working.
after several reflashing attemps i eventually flashed miui_HM6Global_V9.6.4.0.OCGMIFD_fb107cc63b_8.1.zip with success.
i'm experiencing problems with OTA right now... haven't figured out what the problem is.

---------- Post added at 07:38 PM ---------- Previous post was at 07:37 PM ----------
[/COLOR]
snoerme said:
unlock time was 15 days for me...
i succesfully unlocked with no problems.
after flashing TWRP i ran into the same problems like Dachtire:
SIM wasn't working.
after several reflashing attemps i eventually flashed miui_HM6Global_V9.6.4.0.OCGMIFD_fb107cc63b_8.1.zip with success.
i'm experiencing problems with OTA right now... haven't figured out what the problem is.
Click to expand...
Click to collapse
Thx are aware of this, its good information?
https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/

Arround 1 minute on proses unlocking
I got device on 13 pm
Adding mi account on 13.20 pm
Ubl on 15.00 pm

[ROM][9.0_r46][mermaid] SonyAOSP

Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Whats Working:
Probably everything.
Whats not Working:
Everything should work. If you find bug then please report it here: https://github.com/sonyxperiadev/bug_tracker/issues
Steps to flash:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img (WARNING: This will delete all your data on device so have a backup before doing anything)
fastboot flash oem NameOfOEMFile.img
You only need to flash userdata.img when you are going from Stock Firmware to AOSP or when you get issues with future builds.
Downloads:
ROM Dual SIM: Download all the files in that folder
ROM Single SIM: Download all the files in that folder
OEM: OEM Unzip this and flash it as OEM. Instructions above
XDA:DevDB Information
[ROM][9.0_r46][mermaid] SonyAOSP, ROM for the Sony Xperia X10 Plus
Contributors
Haxk20
Source Code: https://android.googlesource.com/platform/manifest
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2019-09-11
Last Updated 2020-01-03

Reserved
NOW: Build for both Dual and Single SIM variants is in to download and test.

Reserved

Help, brothers! Dual sim dont work!!! The network appears and disappears. I bought a phone in Russia. presented to my sister in Belarus. And stumbled upon this problem. Need detailed instructions for flashing the radio module, please!

[email protected] said:
Help, brothers! Dual sim dont work!!! The network appears and disappears. I bought a phone in Russia. presented to my sister in Belarus. And stumbled upon this problem. Need detailed instructions for flashing the radio module, please!
Click to expand...
Click to collapse
Is this issue with the ROM ? Or is the phone running stock firmware ?
If its stock then please move the discussion to questions and answers in 10 Plus forum.
If this is issue with AOSP then please flash stock firmware to check if its working on stock firmware.

I flashed and was able to boot up ok. Initially the phone would only boot up to a blank screen. You could see the volume change when hit vol+ or vol-, the background would remain black. Pulling the SD card and Sim out cause a reboot automatically that seemed to resolve this. The connection to wifi and lte connects and unexpectedly drops. This happens over and over, I cannot make calls or use sms . The browser works fine with the limited LTE time and wifi. There is a vzwinternet apn, I cannot edit them. I wasn't sure if here or where to post. The link to github doest work. The rom is fine otherwise and easily root with magisk 20.1

yitakumini said:
I flashed and was able to boot up ok. Initially the phone would only boot up to a blank screen. You could see the volume change when hit vol+ or vol-, the background would remain black. Pulling the SD card and Sim out cause a reboot automatically that seemed to resolve this. The connection to wifi and lte connects and unexpectedly drops. This happens over and over, I cannot make calls or use sms . The browser works fine with the limited LTE time and wifi. There is a vzwinternet apn, I cannot edit them. I wasn't sure if here or where to post. The link to github doest work. The rom is fine otherwise and easily root with magisk 20.1
Click to expand...
Click to collapse
Link to github is fixed. Thank you for that.
I can say that the ROM worked just fine for me. I switched to different ROM few months ago now and this ROM has no support now. It is very likely you installed wrong OEM image. Please install the latest one for 4.9 kernel.
Because we have started working on 4.14 and well its still in alpha and those 4.14 images there are for us to test it properly.
The WiFi dropping out is known bug and sadly we do not have a fix for it yet.
Please open a bug report on that github repo and explain the issue and post logcat and dmesg files there.
EDIT: Ah my bad. It seems like i already pointed to the correct OEM image. Interesting that calls dont work.

Yo, i've installed the ROM and tried to flash gapps but they didn't install. Is there a way to flash them?

demonic8383 said:
Yo, i've installed the ROM and tried to flash gapps but they didn't install. Is there a way to flash them?
Click to expand...
Click to collapse
You will have to boot TWRP and flash it trough TWRP as AOSP recovery doesnt support flashing openGapps.
Booting up TWRP can be a bit tricky so well good luck.

Haxk20 said:
You will have to boot TWRP and flash it trough TWRP as AOSP recovery doesnt support flashing openGapps.
Booting up TWRP can be a bit tricky so well good luck.
Click to expand...
Click to collapse
Booting into TWRP after the first boot into AOSP is kinda impossible - as far as I know the only way to get TWRP to boot for this device is first to flash the stock ROM -> wait for it to boot completely -> go to bootloader through the ADB command (key combination results in stuck TWRP logo) -> then boot into TWRP. Getting there through the key combination results in black screen. TWRP is in unofficial state - it works only on the stock ROM and only with "fastboot boot twrp.img", it cannot be flashed yet. I'm using this version - https://forum.xda-developers.com/10-plus/development/recovery-twrp-3-3-1-0-unofficial-t3954147
Installing it is possible, however the touchscreen stops working in TWRP when booting the installed version.
Any suggestions on that?

demonic8383 said:
Booting into TWRP after the first boot into AOSP is kinda impossible - as far as I know the only way to get TWRP to boot for this device is first to flash the stock ROM -> wait for it to boot completely -> go to bootloader through the ADB command (key combination results in stuck TWRP logo) -> then boot into TWRP. Getting there through the key combination results in black screen. TWRP is in unofficial state - it works only on the stock ROM and only with "fastboot boot twrp.img", it cannot be flashed yet. I'm using this version - https://forum.xda-developers.com/10-plus/development/recovery-twrp-3-3-1-0-unofficial-t3954147
Installing it is possible, however the touchscreen stops working in TWRP when booting the installed version.
Any suggestions on that?
Click to expand...
Click to collapse
Unfortunately no. SODP does not officially support openGapps and this rom isnt maintained anymore as we are working on 10.
Also twrp for our device will never be flashable image as its useless to do so. We do not have recovery partition and thus have to have recovery in boot image and we build AOSP with stock recovery as its almost impossible to build it with TWRP using AOSP sources. And my guess is that TWRP wont get any better until it supports android 10 which is when we can finally start working on it.
Also on twrp i was able to boot to twrp using this ROM. It was tricky and im guessing the times i did boot it it was just luck.
So so far its a mess.

Haxk20 said:
Unfortunately no. SODP does not officially support openGapps and this rom isnt maintained anymore as we are working on 10.
Also twrp for our device will never be flashable image as its useless to do so. We do not have recovery partition and thus have to have recovery in boot image and we build AOSP with stock recovery as its almost impossible to build it with TWRP using AOSP sources. And my guess is that TWRP wont get any better until it supports android 10 which is when we can finally start working on it.
Also on twrp i was able to boot to twrp using this ROM. It was tricky and im guessing the times i did boot it it was just luck.
So so far its a mess.
Click to expand...
Click to collapse
Damn that's sad, thanks for the info tho

Xperia i4213 problems with sound after flash. No touch sounds. No sound in youtube. The sound appears for 15 seconds after clicking on the flashlight icon. please help fix

My OP 7 PRO(GM21AA) is being completely stuck at Fastboot.

Hey,
It's been always a huge headache since when the Android 10 beta and stables updates are out to root and install twrp. I've tried almost every way possible but every-time, end up being stuck at TWRP or being half way rooted. This time I've tried doing that again :
* I was at OxygenOs Android 10 stable version,
* My bootloader was unlocked as well as OEM unlocking and usb debugging was on,
* I turned my phone into fastboot, and flash the twrp image as:
fastboot flash boot file.img
Then after my phone booted into TWRP since once or twice showing that 0mb internal storage, I flashed the Magisk.zip from adb command, and rebooted it.
Since then, my phone is completely stucked at fastboot, I've tried and followed almost every xda suggestion and everything, I've tried flashing flash.bat file, I've tried flashing stock recovery, In fact I've tried flashing complete fastboot Rom (with all in one app)and it everytime boots me into Fatboot.
Please, help me out guys. I'm stressed out of this problem since yesterday's night.
Let me know your suggestions.

Maybe THIS can help you?

Actually this thread helped me just now in the same situation:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
That thread Jonsat mentioned didn't help me either, at all. Its not very clear that thread, telling in the thread to unbrick a OP7 to look at the thread of the OP6, there send them to OP5 and so on, eventually having to use a short written manual for the OP3 which mentions different versions and so on, its not the best for inexperienced people like me, it just send me on a wild chase downloading drivers and other things that eventually didnt work at all. Maybe I will try to rewrite it, as soon as I have enough experience to do so, i own this device for just a week.

Next time, read before you peform the install steps. It's nowhere like the older devices due to the A/B Recovery.
1. Use MSM Downloader to put you back to stock.
2. Upgrade to Android 10
3. Factory Reset to Clean out your phone (don't forget to unlock bootloader)
4. Initialize phone
5. Boot twrp (specific to Android Q + OP7 Pro)
6. Install TWRP and Magisk from TWRP
7. reboot and enjoy your rooted phone

lloydlim996 said:
Next time, read before you peform the install steps. It's nowhere like the older devices due to the A/B Recovery.
1. Use MSM Downloader to put you back to stock.
2. Upgrade to Android 10
3. Factory Reset to Clean out your phone (don't forget to unlock bootloader)
4. Initialize phone
5. Boot twrp (specific to Android Q + OP7 Pro)
6. Install TWRP and Magisk from TWRP
7. reboot and enjoy your rooted phone
Click to expand...
Click to collapse
What is MSM download tool? I'm going to try using All in One.
On searching for MSM tool, I found https://www.techoxygen.com/msm-download-tool/ is that correct?
Scratch this, MSMdownload is part of zip, I'll read through https://forum.xda-developers.com/showpost.php?p=79972789&postcount=50 and see how it goes

[SOLVED] Installing ANY custom ROM bricks Oneplus 6

Hello!
I'm having quite a hard time figuring out what is happening on my new Oneplus 6.
The first time i flashed LineageOS 16 microg edition it booted but since i tried to restore stock ROM backup with TWRP it all went to hell.
Device immediately bricked, only booting to fastboot.
Had to use msm tool to unbrick. ( the first of so many times.... )
Then updated from settings to latest OOS 9.0.9.
unnlocked bootloader
and flashed again.
NO OS INSTALLED.
phone boots only in fastboot.
can't boot any recovery from fastboot. gives error.
if reboot to recovery blue led and black screen is all that i see.
only fix is msm.
From that point onwards i tried EVERY guide I could find (and recognize as valid of interest) here on xda, youtube, google.
Multiple times per guide.
here's an example of a "last resort" guide from https://forum.xda-developers.com/oneplus-6/how-to/guide-microg-oneplus-6-source-ligthway-t3874469
INSTALLATION TUTORIAL
Italic = recommended, but not mandatory. Do it if something doesn't work properly
0) DON'T RESTORE your apps until everything is set up, otherwise you'll have issues with GCM (getting instant notifications from messaging apps for example)
1) Reboot to blu spark TWRP
2) step deleted
3) Flash OOS
4) Flash TWRP
5) Reboot to recovery
6) Flash OOS
7) Flash TWRP
8) Reboot to recovery
9) Flash your custom ROM + TWRP + reboot to TWRP
10) Flash again your custom ROM + TWRP
11) Reboot to recovery
11 bis) Wipe data ("factory reset")
12) Flash Magisk
13) Reboot to system. It's just to make sure the installation worked.
... more on link
Click to expand...
Click to collapse
Tried also official lineage, SyberiaOS. Different previous version of the two (since I read in the lineage official thread others have this issue)
Basically at the point after flashing any of these roms results immediately in TWRP warning "no os is installed" at reboot attempt with or without re-flashing twrp after.
Then if rebooted just hangs on blue led. can't boot anything.
Meanwhile flashing OTAs + twrp results in bootable system.
Other things that i tried:
before unlocking BL update to latest OTA_34 -> 9.0.9, reboot, install again.
using mauronofrio twrp version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Any ideas?
[SOLUTION]
If you're bricked follow this: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
1 - Have last OOS installed in both slots
- update from settings, local update, latest OTA (Pie) from oneplus support site.​- reboot, let it complete​- apply again​2 - Enable OEM Unlock in Developer options
3 - Boot to Fastboot and unlock bootloader:
Code:
fastboot oem unlock
4 - Once in OOS reboot to fastboot and boot twrp:
Code:
fastboot boot <twrp-img-name>.img
5 - Push twrp + custom rom:
Code:
adb push <custom-rom-name>.zip <twrp-zip-name>.zip /sdcard
6 - Flash twrp in twrp
7 - Reboot to recovery
8 - Wipe system and Data
9 - flash ROM
10 - flash twrp
[IMPORTANT]
11 - Tap Reboot to recovery then if it says No OS installed! tap home button! Don't reboot! reboot = brick = msmdownloadtool
12 - Go in advanced menu and select Fix Recovery Bootloop and swipe
13 - THEN TRY TO MOUNT /system.
IF YOU'RE UNABLE TO MOUNT /system APPLY AGAIN THE FIX AND REPEAT FROM STEP 7​14 - Reboot to recovery
It WILL stil say No OS installed but now you'll be able to reboot to recovery​[/IMPORTANT]
15 - Once in recovery reboot to system.
If you've done everything correctly it won't complain again about no OS being installed and you'll get your rom up and running.​16 - Let it reboot to system and complete first configuration
17 - Now you can reboot and flash every module you like from twrp.
That's it. Hope this'll spare nightmares and storage write life.

This is a bad phone .. I have it too
تم الإرسال من ONEPLUS A6003 باستخدام Tapatalk

But you seem (from post history) to be able to install ROMs :crying:
As most of those who try i guess.
Maybe my phone is somehow damaged

What some guides miss out is that you have to install everything twice. Once on slot A and once on slot B and after each install, verify what slot you are on before reboot and then check what slot you are on after reboot. I ran into issues flashing Havoc OS onto my phone too and figured it out in the end after so many times that I was in fact installing stuff twice on the same slot because it never switched over. I'll run you through the order I did things so hopefully you can follow.
-Use MSM Tool to revert everything back to stock and once the phone is booted, update to 9.0.9 either by downloading the update through the phone or by local upgrade if you have the file to hand. (remember to only have the OOS file present as any other OS in zip form crashes the local updater). You don't need to do this if you are already rocking stock Oxygen OS.
-Once the phone has restarted after the upgrade, let the post update procedure finish before continuing.
-Enter developer mode and enable OEM unlocking, Advanced Restart and USB Debugging. From here, reboot to bootloader.
-Plug your phone into the PC now and assuming you have fastboot setup ready on your PC, type 'fastboot oem unlock' and use the volume keys to select the option to unlock and press the power button to select.
-After the phone has completed it's wipe cycle, re-enable Advanced Restart and USB Debugging. The OEM unlock option should be greyed out as it's already been enabled. Make sure you don't add a pin code or password just yet as you will enable encryption which will make the next steps harder than it should be.
-Boot back to bootloader and type 'fastboot boot twrp.img' (or whatever you named it. Make sure that the image file is in the same folder you initiated cmd or powershell)
-Once booted into TWRP, flash blu_spark TWRP as that supports encryption apparently and is more stable than any other. To make sure that the script executed on both slots, hit reboot and check what slot you are on and tap the button for the other slot. Now reboot back to recovery, check you are on the other slot and flash it again.
-Now flash your 9.0.9 OOS zip followed by TWRP once on slot A and once on slot B while making sure you are on the other slot when doing it a second time. Remember that you have to re-flash TWRP after any flashable file that alters the boot partition before you reboot or you will undo all your work. Just make it habit that you re-flash it every time and you should be good.
-Once OOS and TWRP have been flashed on BOTH slots, reboot back to recovery and do the whole process again with your custom ROM (Remembering to flash TWRP before you reboot and checking which slot you are one before and after each flash).
-Once that has completed, reboot back to recovery and flash Magisk on each slot and GApps or MicroG if your ROM supports it. You don't need to re-flash TWRP after this but I do anyway to keep the habit lol.
-Entirely up to you, but before you reboot to your fresh new OS, you can wipe internal storage ONLY if you want all traces of your previous OS gone, but this will also remove personal files etc. I generally just head into TWRP file manager and delete the Android folder and keep the rest.
If you run into issues like crashes on your new OS, reboot to recovery and do a factory reset, but you will also need to re-flash Magisk again. GApps installs itself to system, so you won't need to re-flash that. MicroG does not and will need setting up again. One thing that took me a while to realise is that if you try rebooting while your USB is plugged into your PC, you will sometimes enter download mode, so only keep it plugged in when you need it for MSM Tool or to transfer files across.
I'm pretty sure I put everything down the way I did it and didn't miss anything, but it is late and I am half asleep. Will check back in the morning and double check with a fresh brain.

Many thanks for your exhaustive reply!
Will follow this tomorrow morning with a fresh brain

Fixed!
Now I'll write a guide for those in the same situation.

franticboe said:
Hello!
I'm having quite a hard time figuring out what is happening on my new Oneplus 6.
The first time i flashed LineageOS 16 microg edition it booted but since i tried to restore stock ROM backup with TWRP it all went to hell.
Device immediately bricked, only booting to fastboot.
Had to use msm tool to unbrick. ( the first of so many times.... )
Then updated from settings to latest OOS 9.0.9.
unnlocked bootloader
and flashed again.
NO OS INSTALLED.
phone boots only in fastboot.
can't boot any recovery from fastboot. gives error.
if reboot to recovery blue led and black screen is all that i see.
only fix is msm.
From that point onwards i tried EVERY guide I could find (and recognize as valid of interest) here on xda, youtube, google.
Multiple times per guide.
here's an example of a "last resort" guide from https://forum.xda-developers.com/oneplus-6/how-to/guide-microg-oneplus-6-source-ligthway-t3874469
Tried also official lineage, SyberiaOS. Different previous version of the two (since I read in the lineage official thread others have this issue)
Basically at the point after flashing any of these roms results immediately in TWRP warning "no os is installed" at reboot attempt with or without re-flashing twrp after.
Then if rebooted just hangs on blue led. can't boot anything.
Meanwhile flashing OTAs + twrp results in bootable system.
Other things that i tried:
before unlocking BL update to latest OTA_34 -> 9.0.9, reboot, install again.
using mauronofrio twrp version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Any ideas?
[SOLUTION]
If you're bricked follow this: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
1 - Have last OOS installed in both slots
- update from settings, local update, latest OTA (Pie) from oneplus support site.​- reboot, let it complete​- apply again​2 - Enable OEM Unlock in Developer options
3 - Boot to Fastboot and unlock bootloader:
Code:
fastboot oem unlock
4 - Once in OOS reboot to fastboot and boot twrp:
Code:
fastboot boot <twrp-img-name>.img
5 - Push twrp + custom rom:
Code:
adb push <custom-rom-name>.zip <twrp-zip-name>.zip /sdcard
6 - Flash twrp in twrp
7 - Reboot to recovery
8 - Wipe system and Data
9 - flash ROM
10 - flash twrp
[IMPORTANT]
11 - Tap Reboot to recovery then if it says No OS installed! tap home button! Don't reboot! reboot = brick = msmdownloadtool
12 - Go in advanced menu and select Fix Recovery Bootloop and swipe
13 - THEN TRY TO MOUNT /system.
IF YOU'RE UNABLE TO MOUNT /system APPLY AGAIN THE FIX AND REPEAT FROM STEP 7​14 - Reboot to recovery
It WILL stil say No OS installed but now you'll be able to reboot to recovery​[/IMPORTANT]
15 - Once in recovery reboot to system.
If you've done everything correctly it won't complain again about no OS being installed and you'll get your rom up and running.​16 - Let it reboot to system and complete first configuration
17 - Now you can reboot and flash every module you like from twrp.
That's it. Hope this'll spare nightmares and storage write life.
Click to expand...
Click to collapse
i tried all the mentioned steps, nothing worked for me. Even i tried all the guides, here on xda and on youtube i am not able to boot my 1+6 it is getting booted to fastboot mode, after installing custom rom. But if i flash only OOS then it boots back properly.
But in case of a custom rom it boots back to fastboot mode, and then in the end msm tool is the last resort to lock bootloader and make it stock.

i tried all the mentioned steps, nothing worked for me. Even i tried all the guides, here on xda and on youtube i am not able to boot my 1+6 it is getting booted to fastboot mode, after installing custom rom. But if i flash only OOS then it boots back properly.
But in case of a custom rom it boots back to fastboot mode, and then in the end msm tool is the last resort to lock bootloader and make it stock.
Click to expand...
Click to collapse
If you are stuck on fastboot try
fastboot set_active other
then try rebooting recovery if fails try
fastboot boot pc-stored-twrp
I found changing the active slot via fastboot may unbrick it without msm. It all depends on what steps you actually take during installation.
For installing LOS try not flashing twrp after installation. Los comes with its own recovery. Anyway if it says no OS installed you HAVE to fix recovery bootloop.

Stuck in a bootloop, please help

Hey,
Quick rundown: Stuck in a bootloop to some sort of empty bootloader screen which has the readout:
"Start/Restart Bootloader/Recovery Mode/Power Off"
"Press volume key to select, and press power key to select"[Regarding above options]
"FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [Gonna leave this out for now]
SECURE BOOT - yes
DEVICE STATE - unlocked" [this line is in red]​
Every choice besides Power Off returns me to the same window. What can I do to recover from this?
Background:
So I was trying to update my OP6 to the current OxygenOS while keeping my root using TWRP and Magisk, which I've done in the past without any issue(i.e. go in recovery flash OS, flash current TWRP, reboot back to recovery, flash current Magisk as I understand it). However this time I was running into an issue flashing the Oxygen update getting an error that said it "failed to map file" for the zip. My first instinct was to update TWRP to see if the newest version didn't run into this issue so I flashed that followed by the current Magisk(no reboot in between). After booting back to standard operations everything seemed fine. I went back into recovery and tried the OS update again, but hit the same issue.
I couldn't find anything specific to OP6 with this issue, but similar questions with other devices suggested clearing the dalvik cache, which I tried to no useful effect. Then I came across this thread (forums.oneplus.com/threads/oxygen-os3-i-have-a-problem-please-help.440587/page-2 too new to hyperlink) and did what I think really messed me up which was boldly follow this guy's advice to do an advanced wipe of everything but internal storage(I also left USB storage intact) from TWRP. This failed to fix the issue with the file mapping error when I subsequently tried to flash the update, though I was able to flash TWRP and Magisk successfully again before rebooting and ending up in this loop.
Any assistance in fixing this or general tips on how to not be foolish when messing around with this stuff is greatly appreciated.

Update:
So I followed the advice gleaned from the resourceful person here(https://forum.xda-developers.com/oneplus-6t/help/bootloader-baseband-versions-blank-t3927565) to try working with the device from my computer with fastboot. At first it would recognize the device as "Android" but be unable to find a driver for it and adb/fastboot both failed to recognize it as a device. After installing MiniTool(more as a way to backup what was on the SD card) the proper device driver also got installed and I was able to access it with fastboot; I ran into similar issues as the linked thread above, solved it by switching to b(still failed) then back to a.
Currently I've got it booted into TWRP and I'm working on getting the current Oxygen .zip copied onto the phone storage but the transfer keeps failing after moving a negligible amount.
Update 2:
Via TWRP was able to sideload the current up-to-date standard OS onto it, however my Google backup seems to have decided to disappear on me and the only OP backup I have is ages old. Anyone have recommendations on data recovery tools?

next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.

NickTheHuy said:
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
Click to expand...
Click to collapse
Good to know, thanks for the info!
I assume that happened when I messed around with advanced wipe, do you know which of the folders I selected that would have been under? And just for future awareness, would that have not occurred had I just used TWRP's standard wipe instead?

You can run a program that will install 9.0.6 from scratch, running a batch file...
Save my life before yesterday....

Your device is bricked
If able to access the TWRP recovery then boot into twrp and try to get all the data stored in your computer.
Then use the Qualcomm flash tool to completely recover from your hard bricked OP6.
from here https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Then its easy, again unlock boot-loader flash TWRP and magisk.