Related
I tried installing Lineage 14.1 last night, and cannot get past recovery screen now. Not sure what else to do, as I've formatted data and cache both to ext4, and have updated back to TWRP 3.0.3. Any help would be greatly appreciated.
I can still get adb and fastboot to recognize the phone, so that seems to be a good thing. But every time I reboot, I just see the ZTE logo, and then it boots into TWRP.
Format system as ext4 and make sure to be on twrp 3.0.3-1
Just to be sure, but did you flash the Nougat bootstack that was in the release topic?
Twiggy000b said:
Format system as ext4 and make sure to be on twrp 3.0.3-1
Click to expand...
Click to collapse
Thank you. Will I need to completely reinstall the rom and gapps again after updating TWRP? I'll have to get to a computer again and give it a shot.
P.S. Would have quoted your post in the Lineage forum, but lost my old account information and couldn't post under Development. So, out of curiousuty, how much trouble did you have with this?
xtermmin said:
Just to be sure, but did you flash the Nougat bootstack that was in the release topic?
Click to expand...
Click to collapse
I did. But am scared that I may have panicked and reinstalled it again. Hoping that won't cause any more trouble for me. Have had to revert to a backup iPhone, and am hating it. Lol.
Updating TWRP worked.
Setting the ROM up now, just had to get back to a computer and try updating recovery. Thanks for the help.
Hi guys, been using my rooted but otherwise stock OOS rom with TWRP and Magisk for the past few weeks. Today I decided to take the plunge and try either the Lineage OS or Resurrection Remix roms.
I'm using the latest OFFICIAL TWRP.
So I decrypted following the instructions to flash "no-verity-opt-encrypt-5.1.zip", then format data. All went well, so I then sent over the ROMS I wanted to try out. I started with the official ResurrectionRemix. Bootloop. Then the unofficial LineageOS. Bootloop.
Ok, well I guess I'm not gonna get to use any of the cool new OS's for awhile. I'll install the full stock firmware zip so I can have a working phone again. Bootloop.
Now when I say bootloop, the phone is booting to the BootAnimation and just repeating it. It shows the proper boot animation for whatever zip I have installed (resurrection/LOS/OOS), but it stays on there for up to 20 minutes before I have to hard reboot to the recovery again.
I decided to install the stock recovery trying a few methods. I first tried the ALL-IN-ONE tool. It said it flashed the recovery fine, so I booted to the recovery and after staying on a black screen for too long, the language options came up and I sighed a breath of relief. But before I could select English with the volume buttons, it rebooted by itself. It did this again when I manually entered recovery. So I figured maybe the tool flashed the wrong version, so I googled stock recovery for OnePlus 5, I found a few random links for stock recoveries for the OP5 and flashed them, but they more or less do the same thing or not boot at all.
I've tried changing the filesystem for both Data and System using any combinations of EXT4 and F2FS. Everything results in boot animation bootloops.
I have been flashing Roms since the Samsung Galaxy S3 and every phone since and never had any problems.
Currently when trying to install the stock Full OOS official zip with TWRP, the phone won't even go to the boot animation, it only goes to a black screen with the top LED in a light blue color.
I have also tried every version of TWRP there is for the OnePlus 5. Unofficial, Official, 3.1.1-0 and 3.1.1-1.
So I guess my question is....What filesystem is each partition supposed to be on and for which OS?
Lineage based:
System: ?
Data: ?
OOS Based:
System: ?
Data: ?
And any ideas on getting my phone running again?
And anyone have an official confirmed working version of the stock recovery? The one from ALL-IN-ONE TOOL doesn't work for me. It loads the language selection, then the screen goes black with a light blue LED on the top of the phone.
Actually I'm getting that on some roms instead of the bootanimation, like FreedomOOS. What does it mean when you have a black screen and a white LED?
Man, I really thought I was getting somewhere. If I boot into TWRP, change the Data partition to "F2FS", then flash the stock recovery, the stock recovery will boot, however, when inside the stock recovery and I try to flash the stock zip, it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
Ok, I have the official stock recovery from the OnePlus site, but still can't use it. Here is was happens depending on how I left it with TWRP:
System: F2FS
DATA: F2FS
- Stock recovery will load after some time, freeze, then the screen goes black with white LED on top.
System: EXT4
DATA: F2FS
- Stock recovery loads fine, I can go through the settings and install from SD card, but when I do it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
System: EXT4
DATA: F2FS
- If I try to flash stock rom through TWRP, it just boot loops on the animation forever.
I have now also tried flashing the stock boot.img, but no difference.
I have 2 things you can try!
First, replace the bootloader with stock and do a factory reset:
1. flash the stock recovery over
2. then in fastboot mode enter, fastboot oem lock (This forces the phone to wipe cache and data, and also do a complete reset)
Did it work? if yes YAY if not go to Second!
Second if your system.img is ****ed up you have to replace it!
Download the newest version of the stock rom from oneplus link here
Unpack it
research how to use an extractor to convert the system.new.dat to system.img
once thats completed enter fastboot mode and flash the new system.img over with Fastboot flash system system.img
now go into recovery and do a factory reset and wipe cache, and dalvik
Please reply back wether or not this work
"Ihave 2 things you can try! First, replace the bootloader with stock and do a factory reset..."
Is the bootloader simply the boot.img?
After doing the first thing, it simply says that the device is corrupt and will not boot. But it is locked again.
But I will have to unlock it again to do any further flashing.
Hmm, I think I may have gotten it. After unlocking again, flashing the stock recovery and boot.img, then locking again and wiping in the stock recovery, I have finally booted into the stock rom.
I still have no idea what went wrong, and I really want to know, so that in the future I can flash other Roms, like LineageOS.
I mean, I followed the steps exactly.
If it says the device is corrupt it simply means you got something else besides stock rom.
So now unlock it and try the system.img instead
It was because I still had TWRP with the stock rom.
I got it working though, thanks for your help.
Do you have any idea on what might have went wrong when trying to flash the lineageOS based roms and why it got messed up so royally?
Great to hear you fixed it ^_^
Probably some minor bug, if you wanna try installing lineageos again use the 3.1.1 TWRP build that supports backups and do a full backup so you don't have to go thru all this again
---------- Post added at 12:17 AM ---------- Previous post was at 12:13 AM ----------
Not really just try again but remember to use TWRP 3.1.1, as 3.1.0 don't support backup and probably have been part of your problem
If your trying again and gets it successfully installed could you do me a favor and test if Drivedroid works on it? And pm me the result, I'm looking for a rom where Drivedroid will work... Haven't found one so far
You know, I did do a backup with the OFFICIAL TWRP, but it also resulted in a bootloop. I made the backup after decrypting, so I don't know why it bootlopped.
https://forum.xda-developers.com/oneplus-5/development/rom-unified-lineageos-7-1-2-t3635483
Is this the one you tried installing?
I tried like every ROM at one point yesterday, but I think I started with
https://forum.xda-developers.com/oneplus-5/development/rom-resurrection-remix-n-7-1-2-t3636578
Did you remember Gapps?
Also in some cases its better not to root before you have the custom rom running, you usually only need a custom bootloader like TWRP
Yeah, I tried with Gapps, and I never rooted before first trying to boot.
As of yesterday Ressurrection remix, released the first official stable build so try again your should'nt have any problems if you follow the guide 100%
Ever find a solution? I'm stuck here now. Can't get any ROM to boot up, they all get stuck on the boot animation
Bump. I am also stuck in this state
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
I had an older version of twrp so I just updated it to the latest one before attempting this ofc...
I tried flashing the latest RR and AICP and both give me boot loops and I always get this one problem where it says
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
I'm not sure if this has anything to do with the bootloop though...
Going to recovery after seeing the bootloop I always get the "keep system read only?" prompt where i swipe to allow modification but i usually just restore back to my backup from there... i dont think allowing it and trying to boot again will get rid of the bootloop...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
OppaiHeroStar said:
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
Click to expand...
Click to collapse
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
dzidexx said:
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
Click to expand...
Click to collapse
The first 3 steps I've already done that since the beginning
Where can i get the nougat modem/is it possible to update to it? I guess that's the reason every single 7.1 custom rom I tried in the android development section gave me boot loops...
And could you link the 21.11.2017 version of RR? I'm looking at the download links for RR and I dont see one with that exact date
edit-just saw your edit
Custom roms for MM modem works better.
I fully wiped using TWRP, checked everything I possibly could except my micro SD card and I flashed RR-N-v5.8.5-20171121-clark-Final.zip then gapps arm64, 7.1 nano and it's still giving me boot loops. I'm using TWRP 3.2.1-0
im gonna try using gapps arm64 7.1 mini really quick since you said I should use that one and see if it boot loops... - Edit guess I was too optimistic thinking this would fix it
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
dzidexx said:
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
Click to expand...
Click to collapse
changed to 3.1.1-0 and did everything you said, still have boot loop...
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
OppaiHeroStar said:
changed to 3.1.1-0 and did everything you said, still have boot loop...
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
dzidexx said:
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
Click to expand...
Click to collapse
I tried crDroidAndroid-7.1.2-20171119-clark-v3.8.3.zip and it still boot loops :\ I also already tried LineageOS and AICP before we started talking
I went back to my backup and it put me in a bootloop which never happened before but changing cache back to ext4 instead of f2fs fixed it..
OppaiHeroStar said:
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
A little late to chime in and this does not help with your current situation, but here's a little advice. I flash a lot of ROMs (how else am I going to test builds right?). This error happens all the time, BUT if you flash a ROM twice it should not show on the 2nd flash.
So flash order goes:
Wipe/Factory reset
Format data x3 (yes I format my data 3 times for every ROM)
Reboot
Wipe/Factory reset
ROM
ROM again
GAPPS
Wipe caches
Reboot
Do the Initial setup
Reboot before use
OPTIONAL Kernel (if its not already build in)
OPTIONAL Magisk (I never flash Magisk on a clean build but heck I'm expecting a NON boot most of the time anyways)
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
acejavelin said:
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
Click to expand...
Click to collapse
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
OppaiHeroStar said:
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
Click to expand...
Click to collapse
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
acejavelin said:
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
Click to expand...
Click to collapse
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
OppaiHeroStar said:
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
Click to expand...
Click to collapse
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
acejavelin said:
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
Click to expand...
Click to collapse
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
OppaiHeroStar said:
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
Click to expand...
Click to collapse
What custom did you flashed?
dzidexx said:
What custom did you flashed?
Click to expand...
Click to collapse
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
OppaiHeroStar said:
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
Click to expand...
Click to collapse
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
dzidexx said:
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
Click to expand...
Click to collapse
I'm using t-mobile and I've checked the access points, clicking on the one im using and hitting save doesn't fix it. Always getting a notification telling me to sign in to network. Not sure what else I can do. I'll give it a day since I had this kind of problem before when I switched sim cards and data didn't work until the next day
Edit - just went back to stock and my data doesn't work now either... just going to stay at RR now and hope my data fixes itself because my access point settings for tmobile should be correct since I looked it up on the official website..
Firstly, my phone isn't hard-bricked. I'm able to load different versions of the TWRP recovery and access Fastboot without any problems. I'm also pretty comfortable using adb to push, sideload, access fastboot, recovery , etc. so please feel free to throw out any suggestions that might help me resolve my issue. (Note:I'm unable to find the stock recovery on OnePlus's support page anymore, I recall they always had the option to download the stock recovery just below the download option for the stock ROM, so I haven't been able to try sideloading after formatting with the stock recovery.)
My OnePlus 5 was running stock Oreo and I'd been meaning to upgrade to Lineage 16.0 (Pie) or any other Pie ROM really. I booted into TWRP (3.2.3-0 - Oreo firmware) and wiped everything other than USB storage and formatted data too as my previous Oreo installation was encrypted. Then, I downloaded codeworkxx's 9.0.3 firmware for OnePlus 5 and pushed it to my phone using adb. I flashed the firmware successfully, rebooted into Bootloader/fastboot; and flashed the Android Pie version of TWRP recovery ( https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/ ) and was able to successfully boot back into the recovery. Since then, I've tried to flash multiple different Pie ROMs (Pixel Experience, Lineage 16.0, stock OOS official build - 9.0.3 , Beta OOS build OpenBeta26) (clean flashing always) but always ended up with a bootloop with the boot animations in all the ROMs. I've even tried flashing them with Magisk-v18.0 but that doesn't help either. I've waited for 15 min with each boot for the different ROM's (ending up in bootloops) and on rebooting back to TWRP, I've always found that irrespective of ROMs, the only folder that's created in Internal Storage is 'obb' and it is an empty folder. I've even tried sideloading OOS 9.0.3 (official build) via TWRP and that still ends up in a bootloop with the obb folder in Internal Storage being the only thing created. Also, flashing the boot.img recovery in the stock ROM zip files leads to a blank screen with a white LED that tries to install Qualcom drivers, so I just reflashed TWRP and am back to where I started.
That pretty much sums up my problem here. Kindly throw suggestions at me to help fix my problem' I've searched the forums but most of the bootloop issues I've found and read are about unsuccessful firmware flashes (not the case with me as I've explained above) or dirty flashes (again, not the case with me as I always cleanflash).
Thanks!
You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.
Z-Blade said:
You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.
Click to expand...
Click to collapse
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!
BigTurboSkipper said:
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!
Click to expand...
Click to collapse
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
strongst said:
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Click to expand...
Click to collapse
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?
strongst said:
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?
Click to expand...
Click to collapse
I can't recall exactly, but it was most probably OB23/24 (Oreo)
BigTurboSkipper said:
I can't recall exactly, but it was most probably OB23/24 (Oreo)
Click to expand...
Click to collapse
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk
strongst said:
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk
Click to expand...
Click to collapse
Successfully flashed but still results in a bootloop
BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
My only suggestion ...
BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter
BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up
strongst said:
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up
Click to expand...
Click to collapse
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!
BigTurboSkipper said:
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!
Click to expand...
Click to collapse
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?
strongst said:
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?
Click to expand...
Click to collapse
That's exactly what I'm doing. I've tried using codeworkxx 's versions, blu_spark TWRP versions and yours too!
PeterGuru said:
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter
Click to expand...
Click to collapse
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!
BigTurboSkipper said:
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!
Click to expand...
Click to collapse
You need to put your device into MSM Download mode. It's simple. Power off your device. Press and hold the Volume UP key for about 8-10 seconds and, while continuing to hold the Volume UP key, plug in your device to your computer via USB. Open the MSM Tool and press Start.
That's it.
It takes about 3-5 minutes for the tool to complete the unbrick process.
Peter
Thank you! I was able to successfully use the unbrick tool to reset to OOS 4.5.8 Nougat. I'm going to try stepping all the way up to Pie now!
For the past 24+ hours I've been trying to flash a few custom roms on my UNLOCKED BOOTLOADER OP6T, but the phone TURNS OFF a few seconds after the boot sequence/animation.
I've read about the A/B slots and tried the Roms' flashing instructions, along with a few suggestions from others, but I cannot get any Custom Rom on my phone...
Here are the steps I've taken to flash (a few times I tried different things that I'll put in parenthesis). Is there anything ya'll see that I'm doing wrong?:
Starting from OOS 10.3.2 Fastboot Recovery and all required files on an OTG USB Drive
fastboot to TWRP....img
Confirmed I'm on Slot A
Wipe Data/Dalvik
Install OOS...zip (10.3.2)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
(Format Data)
Confirmed I'm on Slot B
Install OOS...zip (10.3.2)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
Confirmed I'm on Slot A
Install Xtended (v8 4/13)
(Wipe Data/Cache)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
Confirmed I'm on Slot B
Install Xtended (v8 4/13)
(Wipe Data/Cache)
Install TWRP...zip (3.3.1.32)
Reboot Recovery
Confirmed I'm on Slot A
Install GAPPS (Arm64 10.0 Nano)
(Format Data)
Reboot System
My Guide for Lineage, however it will work for most AOSP based ROMs.
I assume you arent manually switching slots. Don't, there is no need, in fact dont worry about it. Slots will switch automatically after flashing a ROM when you reboot recovery. There is no cache partition, stop wiping this, its not doing anything. There are two slots, but only one data partition that is shared, there isnt a reason to keep wiping it.
On most instructions adding or removing steps will make things not work. Unfortunately for this device there is a lot of out dated information and information that just doesnt work. My guide has been tested with 10.3.3, and the latest version of LOS, however if you have a T-Mobile 6T you are on your own. (I have a regular 6T)
OhioYJ said:
My Guide for Lineage, however it will work for most AOSP based ROMs.
I assume you arent manually switching slots. Don't, there is no need, in fact dont worry about it. Slots will switch automatically after flashing a ROM when you reboot recovery. There is no cache partition, stop wiping this, its not doing anything. There are two slots, but only one data partition that is shared, there isnt a reason to keep wiping it.
On most instructions adding or removing steps will make things not work. Unfortunately for this device there is a lot of out dated information and information that just doesnt work. My guide has been tested with 10.3.3, and the latest version of LOS, however if you have a T-Mobile 6T you are on your own. (I have a regular 6T)
Click to expand...
Click to collapse
Thanks for the comment! I just followed your guide, but still seeing the boot animation for a few seconds, then the phone vibrates and turns off.
For kicks, I decided to Format Data and I see the boot animation longer, all the way to the end when it's about to start Android, but then it vibrates and shuts off. Strange.
I'm thinking there is something different about my phone... It's a global, unlocked version and I've rooted/flashed hundreds of roms over the years on various devices, so all of this should be a piece of cake................. Thanks!
oooscasianooo said:
Thanks for the comment! I just followed your guide, but still seeing the boot animation for a few seconds, then the phone vibrates and turns off.
For kicks, I decided to Format Data and I see the boot animation longer, all the way to the end when it's about to start Android, but then it vibrates and shuts off. Strange.
I'm thinking there is something different about my phone... It's a global, unlocked version and I've rooted/flashed hundreds of roms over the years on various devices, so all of this should be a piece of cake................. Thanks!
Click to expand...
Click to collapse
Have you tried without Gapps?
After the shutdown go back to twrp and extract the content of /sys/fs/pstore/* and upload the files here.
onliner said:
After the shutdown go back to twrp and extract the content of /sys/fs/pstore/* and upload the files here.
Click to expand...
Click to collapse
Thanks. I actually gave up and setup stock OOS again, so it took a while to get a TWRP backup, etc. etc.
So after the backup, I installed Xtended + TWRP, reboot to recovery, installed Xtended + TWRP, wiped dalvik, and reboot to system.
Boot animation shut down issue as usual.
Afterwards, I copied the pstore folder (attached zip).
Thanks!
onliner said:
After the shutdown go back to twrp and extract the content of /sys/fs/pstore/* and upload the files here.
Click to expand...
Click to collapse
Anything in the logs I can look for?
This is driving me crazy. I flashed MIUI just fine (because it had the .bat file that does everything for you). Essentially it's doing the same thing as flashing OOS & Rom on A/B, right?
Just tried flashing the newest Xtended Rom (May 11th), same issue. Phone vibrates and completely turns off while the boot animation is running.
OhioYJ said:
My Guide for Lineage, however it will work for most AOSP based ROMs.
I assume you arent manually switching slots. Don't, there is no need, in fact dont worry about it. Slots will switch automatically after flashing a ROM when you reboot recovery. There is no cache partition, stop wiping this, its not doing anything. There are two slots, but only one data partition that is shared, there isnt a reason to keep wiping it.
On most instructions adding or removing steps will make things not work. Unfortunately for this device there is a lot of out dated information and information that just doesnt work. My guide has been tested with 10.3.3, and the latest version of LOS, however if you have a T-Mobile 6T you are on your own. (I have a regular 6T)
Click to expand...
Click to collapse
If you have a TMobile 6t I can confirm I have had to manually change the slots during the flashing process to get custom ROMs installed.
mrmcshagbag said:
If you have a TMobile 6t I can confirm I have had to manually change the slots during the flashing process to get custom ROMs installed.
Click to expand...
Click to collapse
I found out that I do have the T-Mobile version that the seller flashed to International Software haha
When I reboot to recovery, I do see that the slots are being changed though.
Would you mind post the exact steps you took to successfully flash a ROM/GAPPS?
oooscasianooo said:
I found out that I do have the T-Mobile version that the seller flashed to International Software haha
When I reboot to recovery, I do see that the slots are being changed though.
Would you mind post the exact steps you took to successfully flash a ROM/GAPPS?
Click to expand...
Click to collapse
Fastboot boot TWRP Marion version
Flash oos
Flash Marion TWRP zip
Check my slot
Reboot recovery
Changed slot since it didn't change
Reboot recovery
Flash oos
Flash Marion TWRP zip
Changed slot
Reboot recovery
Flash custom rom
Flash Marion TWRP zip
Change slot
Reboot recovery
Flash gapps
Flash magisk 20.4
Reboot to system
Those are the steps I had to take before I finally got a custom rom to work. I tried doing the methods posted which would have probably worked if the slots were changing on there own but they weren't for me.
mrmcshagbag said:
Fastboot boot TWRP Marion version
Flash oos
Flash Marion TWRP zip
Check my slot
Reboot recovery
Changed slot since it didn't change
Reboot recovery
Flash oos
Flash Marion TWRP zip
Changed slot
Reboot recovery
Flash custom rom
Flash Marion TWRP zip
Change slot
Reboot recovery
Flash gapps
Flash magisk 20.4
Reboot to system
Those are the steps I had to take before I finally got a custom rom to work. I tried doing the methods posted which would have probably worked if the slots were changing on there own but they weren't for me.
Click to expand...
Click to collapse
Thanks! Do you mean the "mauronofrio" version?
oooscasianooo said:
Thanks! Do you mean the "mauronofrio" version?
Click to expand...
Click to collapse
Yes couldn't remember the exact name but I knew you would be able to find it haha
mrmcshagbag said:
Yes couldn't remember the exact name but I knew you would be able to find it haha
Click to expand...
Click to collapse
hahaha thanks! I was thinking, "is there a T-Mobile version of TWRP?!" haha!