Related
My Moto G5 plus keeps booting to TWRP. No matter what ROM I install. What do I do?
What did you do to get here? Were you on stock before? Did you we Data? You haven't really given any information...
Mikeandrd2292 said:
My Moto G5 plus keeps booting to TWRP. No matter what ROM I install. What do I do?
Click to expand...
Click to collapse
Booting into TWRP or into the bootloader?
If the Bootloader, that's a simple fix... If TWRP you probably flashed it to the boot partition instead of recovery partition, but flashing a ROM should fix it as it over-writes that partition anyway.
Guess if that doesn't help we need more info...
Mikeandrd2292 said:
My Moto G5 plus keeps booting to TWRP. No matter what ROM I install. What do I do?
Click to expand...
Click to collapse
1) never be in a hurry here... we help when we can...
2) search the forum: other people reported this problem an found a solution.
Sorry. I posted this right before I fell asleep. I updated my phone and it booted into TWRP. Now it just keeps booting into TWRP. Every ROM I flash, it does the same thing.
Updated from what to what?
Karlinski said:
Updated from what to what?
Click to expand...
Click to collapse
I restored my backup and there was a security update so I updated it and that's when all this happened.
So, you took a stock OTA Update on a rooted build, it sounds like. I believe you need to follow the steps to root again, and you should be good.
Karlinski said:
So, you took a stock OTA Update on a rooted build, it sounds like. I believe you need to follow the steps to root again, and you should be good.
Click to expand...
Click to collapse
The backup I restored was already rooted though :/
EDIT: I misread what you said. Yeah, I flashed a stock OTA update. But the problem is, I can't get into the system to root it again. It just keeps going to TWRP.
Mikeandrd2292 said:
The backup I restored was already rooted though :/
EDIT: I misread what you said. Yeah, I flashed a stock OTA update. But the problem is, I can't get into the system to root it again. It just keeps going to TWRP.
Click to expand...
Click to collapse
This procedure is for the G4, but the Factory ROM structure is the same for both the G4 and G5+:
https://forum.xda-developers.com/showpost.php?p=68948997&postcount=1
You can get the factory ROM here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Read through everything, and make sure it makes sense. I used this to remove TWRP from a G4.
Mikeandrd2292 said:
The backup I restored was already rooted though :/
EDIT: I misread what you said. Yeah, I flashed a stock OTA update. But the problem is, I can't get into the system to root it again. It just keeps going to TWRP.
Click to expand...
Click to collapse
In TWRP wipe caches and reboot... Should be fine.
acejavelin said:
In TWRP wipe caches and reboot... Should be fine.
Click to expand...
Click to collapse
That did nothing. I tried installing a new ROM and it restarted TWRP in the middle of installing.
Mikeandrd2292 said:
That did nothing. I tried installing a new ROM and it restarted TWRP in the middle of installing.
Click to expand...
Click to collapse
Wiping caches was only to get rid of the OTA file... the OTA zip file is stored in cache, removing it should have allowed the phone to boot normally, if not there is a bigger problem.
Start fresh... Flash latest TWRP, copy a new ROM and Gapps to device, wipe everything except internal/external storage, and flash clean... If it fails, or restarts in the middle of installing, you have more serious problems... likely a partition or hardware issue.
same thing happened to me, I just started over and flashed a stock image, install twrp, update to latest ota, then rooted with magisk. pretty easy with drtechie's moto g5 plus toolkit v1.1.0
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..
Hi, I'm new to rooting. A week ago or so I installed Pixel Experience Rom to my device but didn't liked it to much and my phone was constantly freezing for a second or so. I decided to go back to Oxygen OS with android 9 but keep the TWRP as my recovery and root my phone with Magisk.
Anyways today I got this notification saying that after phone downloads and install the software update my phone will reboot and unroot itself and I should back up my data. /a/DWgVyTK (imgur link)
After using my phone with root I liked it better this way. Anyways because I'm beginner level on this topic I don't know what should I do. I don't want to set up my phone again from the start after the update and I like root but I want my software to be latest as well. Is there any other way to install the update without deleting everything on phone?
Also if I download the latest software update can I flash it with TWRP without deleting anything on phone? Or back up my things with TWRP and install the software and use that back up to get everything back together again? Little bit help would be appreciated.
Ebeninyo said:
Hi, I'm new to rooting. A week ago or so I installed Pixel Experience Rom to my device but didn't liked it to much and my phone was constantly freezing for a second or so. I decided to go back to Oxygen OS with android 9 but keep the TWRP as my recovery and root my phone with Magisk.
Anyways today I got this notification saying that after phone downloads and install the software update my phone will reboot and unroot itself and I should back up my data. /a/DWgVyTK (imgur link)
After using my phone with root I liked it better this way. Anyways because I'm beginner level on this topic I don't know what should I do. I don't want to set up my phone again from the start after the update and I like root but I want my software to be latest as well. Is there any other way to install the update without deleting everything on phone?
Also if I download the latest software update can I flash it with TWRP without deleting anything on phone? Or back up my things with TWRP and install the software and use that back up to get everything back together again? Little bit help would be appreciated.
Click to expand...
Click to collapse
Questions about your Oneplus 5:
What's your current OxygenOS version?
What's the version you want to install?
For OxygenOS Open Beta just follow instructions in the first post here
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003
For stable OxygenOS here in the first post
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
There's no need doing an ota update, cause rom files are mirrored on xda
strongst said:
Questions about your Oneplus 5:
What's your current OxygenOS version?
What's the version you want to install?
For OxygenOS Open Beta just follow instructions in the first post here
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003
For stable OxygenOS here in the first post
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
There's no need doing an ota update, cause rom files are mirrored on xda
Click to expand...
Click to collapse
Thank you very much for answering. I tried dirty rom installing but twrp is not seeing my device's internal memory. I'm guessing that it's because oxygen os encrypts my phone when i enter the system after installation. It happened earlier as well when I tried to install oxygen os and root my phone and the time i tried to install pixel experience rom. I decided not to do clean installation as of now because I don't want to loose my data. (i certainly can get back everything on my phone but it usually takes few hours for that). Is there any other way to unencrypting the phone without wiping everything off?
My current oxygen os version is 9.0.2
I was trying to install 9.0.3.
Ebeninyo said:
Thank you very much for answering. I tried dirty rom installing but twrp is not seeing my device's internal memory. I'm guessing that it's because oxygen os encrypts my phone when i enter the system after installation. It happened earlier as well when I tried to install oxygen os and root my phone and the time i tried to install pixel experience rom. I decided not to do clean installation as of now because I don't want to loose my data. (i certainly can get back everything on my phone but it usually takes few hours for that). Is there any other way to unencrypting the phone without wiping everything off?
My current oxygen os version is 9.0.2
I was trying to install 9.0.3.
Click to expand...
Click to collapse
With which recovery and rom are you able to access your internal storage?
strongst said:
With which recovery and rom are you able to access your internal storage?
Click to expand...
Click to collapse
I've only tried using TWRP as my recovery, Pixel experience rom and oxygen os rom. The thing is because upon entering the phone after flashing a rom you can't access the internal storage of the phone with TWRP because phone encrypts itself. That means I can't dirty flash it and need to wipe everything out with TWRP then reboot TWRP again and install new rom after that flash magisk and reboot to system and set everything up from the scratch.
When I started this thread I didn't knew how to dirty flash a rom. Now I know and realize the problem I'm having is phone's encryption.
UPDATE:
I have used this guide to disable encryption on my phone. (I tried putting the link to the guide but for some reason i can't. It was on Custom Droid about how to remove one plus 5's encryption) I wiped everything on my phone with TWRP, installed the new OTA with Oxygen OS 9.0.3, flashed the file they provided on the guide, started system, went through steps and checked my encryption status and it was still encrypted.
Entered recovery again and wiped everything once more. Installed Magisk entered my system. (I was wiping everything down because otherwise TWRP wasn't able to see my device's storage), went through all the steps again. Installed Magisk's apk. Checked my root status. Everything was okay but still my phone was encrypted. Downloaded latest version of the Magisk. Wiped everything down once more installed Magisk. Rebooted into my system to see my phone's encryption was still there. At this point I gave up and started restoring my apps, data and everything with it.
Now I can't update my software whenever I want because TWRP won't see my device's storage because of encryption. Basically dirty flashing isn't available for me.
Have you guys tried and find a solution for this? If so please let me know. I would highly appreciate it.
Ebeninyo said:
UPDATE:
I have used this guide to disable encryption on my phone. (I tried putting the link to the guide but for some reason i can't. It was on Custom Droid about how to remove one plus 5's encryption) I wiped everything on my phone with TWRP, installed the new OTA with Oxygen OS 9.0.3, flashed the file they provided on the guide, started system, went through steps and checked my encryption status and it was still encrypted.
Entered recovery again and wiped everything once more. Installed Magisk entered my system. (I was wiping everything down because otherwise TWRP wasn't able to see my device's storage), went through all the steps again. Installed Magisk's apk. Checked my root status. Everything was okay but still my phone was encrypted. Downloaded latest version of the Magisk. Wiped everything down once more installed Magisk. Rebooted into my system to see my phone's encryption was still there. At this point I gave up and started restoring my apps, data and everything with it.
Now I can't update my software whenever I want because TWRP won't see my device's storage because of encryption. Basically dirty flashing isn't available for me.
Have you guys tried and find a solution for this? If so please let me know. I would highly appreciate it.
Click to expand...
Click to collapse
To prevent the OxygenOS to encrypt your phones storage you need to flash no verity patch before first boot(instructions). But coming from a custom rom requires to format internal storage, otherwise it won't work.
strongst said:
To prevent the OxygenOS to encrypt your phones storage you need to flash no verity patch before first boot(instructions). But coming from a custom rom requires to format internal storage, otherwise it won't work.
Click to expand...
Click to collapse
Can you be able link me that patch and instructions?
Ebeninyo said:
Can you be able link me that patch and instructions?
Click to expand...
Click to collapse
I already gave you the link to instructions how to flash stable oxygenOS in the 2nd post https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040
Just follow the CLEAN FLASH INSTRUCTIONS and on the 2nd last step you flash that patch which prevents you from encrypted storage.
strongst said:
I already gave you the link to instructions how to flash stable oxygenOS in the 2nd post https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040
Just follow the CLEAN FLASH INSTRUCTIONS and on the 2nd last step you flash that patch which prevents you from encrypted storage.
Click to expand...
Click to collapse
I've already tried the clean flash instructions. However I flashed the patch before magisk last time I tried it but it didn't work. Maybe because my order was wrong. Since I don't have much time right now. I'm going to try that once again tomorrow this time exactly like on the guide. I will let you know about the results.
Thank you very much again. I really appreciate your help.
Ebeninyo said:
I've already tried the clean flash instructions. However I flashed the patch before magisk last time I tried it but it didn't work. Maybe because my order was wrong. Since I don't have much time right now. I'm going to try that once again tomorrow this time exactly like on the guide. I will let you know about the results.
Thank you very much again. I really appreciate your help.
Click to expand...
Click to collapse
Remember to format the internal storage exactly written in the instructions and then flash the no verity patch, otherwise it will not work.
strongst said:
Remember to format the internal storage exactly written in the instructions and then flash the no verity patch, otherwise it will not work.
Click to expand...
Click to collapse
I was looking for other threads in this sub section. I saw this thread. https://forum.xda-developers.com/oneplus-5/help/twrp-encryption-t3889161
I flashed codeworkx twrp like you said on that thread. Now I can decrypt the phone. TWRP asks me for screen password and when I entered it, it showed me the internal memory. Now I can see my device's internal memory from recovery without wiping out everything.
My previous TWRP was twrp-3.2.3-0-cheeseburger.img
Installed twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger.img via twrp app on my phone like you said on that thread. Thank you very much again.
Ebeninyo said:
I was looking for other threads in this sub section. I saw this thread. https://forum.xda-developers.com/oneplus-5/help/twrp-encryption-t3889161
I flashed codeworkx twrp like you said on that thread. Now I can decrypt the phone. TWRP asks me for screen password and when I entered it, it showed me the internal memory. Now I can see my device's internal memory from recovery without wiping out everything.
My previous TWRP was twrp-3.2.3-0-cheeseburger.img
Installed twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger.img via twrp app on my phone like you said on that thread. Thank you very much again.
Click to expand...
Click to collapse
Cool:good:
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!
I seem to have hard bricked my 9T after flashing the MIUI 11 rom from xiaomi.eu. I think culprit is a totally botched/corrupted boot loader and I have no idea how it happened. I've tried reflashing back to stock through stock image .bat files, but no dice. It flashed everything but the device still refuses to boot past the MI screen. If I try to boot into TWRP, my device gets stuck at the TWRP splash screen, no matter which version it is. Does anyone know what I can do or try at this point? Thanks.
So do I, first time I successfully instal first beta v25 miui 11, and than when the v26 comes, stupidly, i flash it from twrp, it tells me that i succeed installing that zip, and than i wipe art and cache and reboot system, but what next i know, my phone brick, i can not instal anyrom, from mi flash tool, or from anywhere. I did everything and still can not fix the problem.
Anyway, you still can enterin TWRP UI, after waiting about 10 to 30 minutes, because after intalling that rom, automatically your data format change from ext4 to f2fs, and twrp will need a lot of time to read your disk.
But, even after doing anything in twrp, still can not make my phone successfully boot into system.
And theres moun I/O error everytime i tried to wipe everything, or fix disk, or change disk format. Everything... and i just dont know what to do anymore.
So may be you can wait patiently until you can entering twrp ui, and please lemme know if you know how to fix this problem
Soapy! said:
I seem to have hard bricked my 9T after flashing the MIUI 11 rom from xiaomi.eu. I think culprit is a totally botched/corrupted boot loader and I have no idea how it happened. I've tried reflashing back to stock through stock image .bat files, but no dice. It flashed everything but the device still refuses to boot past the MI screen. If I try to boot into TWRP, my device gets stuck at the TWRP splash screen, no matter which version it is. Does anyone know what I can do or try at this point? Thanks.
Click to expand...
Click to collapse
i have experience that, then i flash the twrp chinese version and it works.
@flamedrops which one if i may know? I tried 3.3.1-0916-redmi_k20-CN and still not work ?
Soapy! said:
I seem to have hard bricked my 9T after flashing the MIUI 11 rom from xiaomi.eu. I think culprit is a totally botched/corrupted boot loader and I have no idea how it happened. I've tried reflashing back to stock through stock image .bat files, but no dice. It flashed everything but the device still refuses to boot past the MI screen. If I try to boot into TWRP, my device gets stuck at the TWRP splash screen, no matter which version it is. Does anyone know what I can do or try at this point? Thanks.
Click to expand...
Click to collapse
I got exactly the same problem after installing miui 11rom. Installing firmware via fastboot was unsuccessful. God, help us ...
---------- Post added at 07:44 AM ---------- Previous post was at 07:33 AM ----------
Arif Ferdian said:
So do I, first time I successfully instal first beta v25 miui 11, and than when the v26 comes, stupidly, i flash it from twrp, it tells me that i succeed installing that zip, and than i wipe art and cache and reboot system, but what next i know, my phone brick, i can not instal anyrom, from mi flash tool, or from anywhere. I did everything and still can not fix the problem.
Anyway, you still can enterin TWRP UI, after waiting about 10 to 30 minutes, because after intalling that rom, automatically your data format change from ext4 to f2fs, and twrp will need a lot of time to read your disk.
But, even after doing anything in twrp, still can not make my phone successfully boot into system.
And theres moun I/O error everytime i tried to wipe everything, or fix disk, or change disk format. Everything... and i just dont know what to do anymore.
So may be you can wait patiently until you can entering twrp ui, and please lemme know if you know how to fix this problem
Click to expand...
Click to collapse
Just the exact same problem as mine. If you know anything about how to solve this problem, please tell us.
I had the same problem with a miui 10 weekly beta but unfortunately I wasn't able to fix it but lucky me my phone was still in a return period so I returned it back to Amazon and got my money back since then I have always stayed away from beta ROMs . I tried everything but it wasn't booting pass the mi logo as you said
flamedrops said:
i have experience that, then i flash the twrp chinese version and it works.
Click to expand...
Click to collapse
Benfatica said:
I had the same problem with a miui 10 weekly beta but unfortunately I wasn't able to fix it but lucky me my phone was still in a return period so I returned it back to Amazon and got my money back since then I have always stayed away from beta ROMs . I tried everything but it wasn't booting pass the mi logo as you said
Click to expand...
Click to collapse
Ahhhh yes, i was thinking to using my guaranteed card, as i still can relock bootliader with mi flash tools, already trying anything for couples day with zero result, and im giving up hahaha
Arif Ferdian said:
Ahhhh yes, i was thinking to using my guaranteed card, as i still can relock bootliader with mi flash tools, already trying anything for couples day with zero result, and im giving up hahaha
Click to expand...
Click to collapse
did you really reboot it using adb reboot twrp? and reboot system on twrp using twrp cn version?
Yap @flamedrops i already do, and even tried all the TWRP version that exist, and also reflash many Rom, from stock, eu, ct, aosp, miui 11 25, miui 11 26, i flash from adb sideload, from twrp via usb otg, via miflash tool,
I flash boot.img, etc
Still no result.
Already tried everything that i could thinking about
flamedrops said:
did you really reboot it using adb reboot twrp? and reboot system on twrp using twrp cn version?
Click to expand...
Click to collapse
This LR. TEAM is twrp cn version right? And in fact, this version hardly booting to twrp ui version after this problem, easier to entering twrp ui with the ugly themed greek version
Arif Ferdian said:
This LR. TEAM is twrp cn version right? And in fact, this version hardly booting to twrp ui version after this problem, easier to entering twrp ui with the ugly themed greek version
Click to expand...
Click to collapse
ok, yes thats it. have you tried to flash magisk?
@flamedrops not yet, i never tried to flash magisk yet, ill tried next time i could pass twrp splash screen
flamedrops said:
i have experience that, then i flash the twrp chinese version and it works.
Click to expand...
Click to collapse
Can you list your steps to fix this? My data and cache partitions are 0kb and i get i/o errors too.
I have persist problems after installing muiu 11 over the los16.
Thinking about relock it and sens it back to aliexpress seller.
@mvha just go into fastboot mode, and flash persist.img from stock fastboot rom,
With command : fastboot flash persist persist.img
Thats all
Arif Ferdian said:
So do I, first time I successfully instal first beta v25 miui 11, and than when the v26 comes, stupidly, i flash it from twrp, it tells me that i succeed installing that zip, and than i wipe art and cache and reboot system, but what next i know, my phone brick, i can not instal anyrom, from mi flash tool, or from anywhere. I did everything and still can not fix the problem.
Anyway, you still can enterin TWRP UI, after waiting about 10 to 30 minutes, because after intalling that rom, automatically your data format change from ext4 to f2fs, and twrp will need a lot of time to read your disk.
But, even after doing anything in twrp, still can not make my phone successfully boot into system.
And theres moun I/O error everytime i tried to wipe everything, or fix disk, or change disk format. Everything... and i just dont know what to do anymore.
So may be you can wait patiently until you can entering twrp ui, and please lemme know if you know how to fix this problem
Click to expand...
Click to collapse
This makes sense as I remember trying to boot into stock recovery early in the morning. I woke up and it finally booted, but the recovery was in Chinese. I will give 4PDA TWRP about an hour and see what I can do. Thanks.
Soapy! said:
This makes sense as I remember trying to boot into stock recovery early in the morning. I woke up and it finally booted, but the recovery was in Chinese. I will give 4PDA TWRP about an hour and see what I can do. Thanks.
Click to expand...
Click to collapse
If you can not use 4pda, i suggest u to use greek one, thats twrp version the must successfully booting in my experiences
I am thankful that I saw this before updating to newest miui 11
flamedrops said:
ok, yes thats it. have you tried to flash magisk?
Click to expand...
Click to collapse
Can not flash magisk, etc hahahhahaa
Arif Ferdian said:
If you can not use 4pda, i suggest u to use greek one, thats twrp version the must successfully booting in my experiences
Click to expand...
Click to collapse
After you used the Greek twrp did you manage to solve the problem?