Related
My OP2 is currently 100% stock, never rooted, and is running Oxygen OS 2.2.1. I have tried OTAing, flashing dirty and clean but the phone itself keeps getting the boot loop logo (Powered by Android screen with the capacity buttons off). I have enabled google apps so I'm not sure what is causing the bootloop. A history of my phone is that on 2.1.0, I tried updating the phone via OTA and I would get "Installation failed" once the entire bar finishes in Recovery. The same thing happened for 2.2.0 > 2.2.1 so I had to dirty flash the phone, otherwise I would get "Installation failed".
I keep a spare file of 2.2.1 off of Oneplus' download site so whenever this boot loop occurs, I turn the phone off and go into recovery > install from downloads > and flash the 2.2.1.
Try this ? http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Djarenga said:
Try this ? http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Click to expand...
Click to collapse
My phone isn't bricked
bump
willy156 said:
My phone isn't bricked
Click to expand...
Click to collapse
Is it, if you can't boot it up.
serkka8 said:
Is it, if you can't boot it up.
Click to expand...
Click to collapse
Hi, my phone is on 2.2.1 fine. but every time i try to update (ota shows me 3.1.0) i get a boot loop
I just tried the 3.1.0 OTA and my phone got stuck on the Powered by android screen. I had to turn the phone off and go into recovery and flashed my 2.2.1 file to unbrick myphone.
try the full rom zip intead of the OTA.
NickRuler said:
try the full rom zip intead of the OTA.
Click to expand...
Click to collapse
with or without wiping data/cache first? I'll try the 3.1.0 full zip file flashing next. think ill try to factory reset after
willy156 said:
with or without wiping data/cache first? I'll try the 3.1.0 full zip file flashing next. think ill try to factory reset after
Click to expand...
Click to collapse
Try it without wiping first. If it works , you wont lose your data.
Edit: If you dont mind losing your data, I would suggest that you use this
http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
This will flash OxygenOS 3.0.2 and restore all partitions to stock.
This should also solve your OTA problems.
OK so here's what's going on.
I have a nexus 6p OTA 7.0 build rooted. I downloaded cm 14.1 and the correct Gapps which is Android 7.1 arm64 I used full version.
Booted to custom recovery and wiped all but internal storage. Then went to flash as usual flashed cm14.1 first. Yes downloaded from the CyanogenMod site official release. Then flashed the Gapps mentioned. And wiped cache after each installion.
Rebooted system and it loads the cm loading screen as should be. But the issue lies within this....it's takes 10-15 minutes to boot and goes straight to "Android system, there's an internal problem with your device. Contact your manufacturer for details" message. Hit OK and phone runs...set up completely goes through and everything. Once set up is done the message "cm bug report has stopped working" shows up.
I did use wugfresh toolkit to do all of this at newest version with all current updates.
What can I do to fix this error? Is it in the 14.1 ROM? Is it the Gapps? Or what's going on if someone can explain or help that'd be great. Again phone is working and fully functional but that internal error message is really concerning to me.
jessyjoseph2044 said:
OK so here's what's going on.
I have a nexus 6p OTA 7.0 build rooted. I downloaded cm 14.1 and the correct Gapps which is Android 7.1 arm64 I used full version.
Booted to custom recovery and wiped all but internal storage. Then went to flash as usual flashed cm14.1 first. Yes downloaded from the CyanogenMod site official release. Then flashed the Gapps mentioned. And wiped cache after each installion.
Rebooted system and it loads the cm loading screen as should be. But the issue lies within this....it's takes 10-15 minutes to boot and goes straight to "Android system, there's an internal problem with your device. Contact your manufacturer for details" message. Hit OK and phone runs...set up completely goes through and everything. Once set up is done the message "cm bug report has stopped working" shows up.
I did use wugfresh toolkit to do all of this at newest version with all current updates.
What can I do to fix this error? Is it in the 14.1 ROM? Is it the Gapps? Or what's going on if someone can explain or help that'd be great. Again phone is working and fully functional but that internal error message is really concerning to me.
Click to expand...
Click to collapse
Flash the vendor.img that is linked in the CM 14.1 OP. This will resolve the "internal problem" error:
http://forum.xda-developers.com/showthread.php?t=3498453
Sent from my Nexus 5X using Tapatalk
Do I just enter recovery and flash it there? Do I need to reset the phone and do a clean flash as well? Or can I just download the vendor.img and boot to recovery and flash it. Thanks for the info
SlimSnoopOS said:
Flash the vendor.img that is linked in the CM 14.1 OP. This will resolve the "internal problem" error:
http://forum.xda-developers.com/showthread.php?t=3498453
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Do I just enter recovery and flash it there? Do I need to reset the phone and do a clean flash as well? Or can I just download the vendor.img and boot to recovery and flash it. Thanks for the info
Flash it within twrp, as written in CM14.1 OP
I have attempted to flash LineageOS 13 to my phone using TWRP recovery. Before flashing I chose advanced wipe and wiped everything except for the internal memory and SD card. I checked the zip file to make sure that it was openable and that it was the correct file size. When installing, it said that the install was successful but after rebooting the phone is stuck on the Huawei logo and will not boot.
What have I done wrong?
mackelbot said:
I have attempted to flash LineageOS 13 to my phone using TWRP recovery. Before flashing I chose advanced wipe and wiped everything except for the internal memory and SD card. I checked the zip file to make sure that it was openable and that it was the correct file size. When installing, it said that the install was successful but after rebooting the phone is stuck on the Huawei logo and will not boot.
What have I done wrong?
Click to expand...
Click to collapse
Flash again and wipe only danvik and cache that will be dirty flash,
If you have emui 3.1, update to emui 4.1 by twrp because the most of Openkirin's rom are basd on it. But other roms like Omni, Aokp, Aicp, Slim and Lineage os 14.1 are based on emui 4.0
RootingPro-18 said:
Flash again and wipe only danvik and cache that will be dirty flash,
Click to expand...
Click to collapse
That was how I did it the first time and I got an error message saying that it failed to flash the rom
DarkJoker360 said:
If you have emui 3.1, update to emui 4.1 by twrp because the most of Openkirin's rom are basd on it. But other roms like Omni, Aokp, Aicp, Slim and Lineage os 14.1 are based on emui 4.0
Click to expand...
Click to collapse
Okay, I didn't know this. I'll have a go and see if it works
mackelbot said:
That was how I did it the first time and I got an error message saying that it failed to flash the rom
Click to expand...
Click to collapse
That because you deleted system
RootingPro-18 said:
That because you deleted system
Click to expand...
Click to collapse
Didn't delete system the first time. Just cache/dalvik
mackelbot said:
Didn't delete system the first time. Just cache/dalvik
Click to expand...
Click to collapse
Wait? You said wipe all except intrenal and Sd card! System is different partition
mackelbot said:
Okay, I didn't know this. I'll have a go and see if it works
Click to expand...
Click to collapse
Read the instructions when installing ROMs. It'll save you headaches
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..
I like Lineage OS but the fact the second screen stays on even when locked drains battery even with a custom Kernal. I would love to be stock and rooted but since I DS the boot. I understand flashing stock will get rid of it(maybe I am wrong?). I just want a stock rom or a way to go to stock and stay rooted? is this possible or am I stuck with everyone else?
Yes. There seems to be too good Oreo ROMs out right now. Take a look in the ROMs kernels page
https://forum.xda-developers.com/v20/development/vs995-verizon-lg-v20-stock-oreo-rooted-t3845669
https://forum.xda-developers.com/v20/development/alpha-omega-rom-oreo-vs995-h910-ls997-t3847510
kaluna00 said:
Yes. There seems to be too good Oreo ROMs out right now. Take a look in the ROMs kernels page
https://forum.xda-developers.com/v20/development/vs995-verizon-lg-v20-stock-oreo-rooted-t3845669
https://forum.xda-developers.com/v20/development/alpha-omega-rom-oreo-vs995-h910-ls997-t3847510
Click to expand...
Click to collapse
Thank you, Is alpha Rom hard to install?
stevieshae said:
Thank you, Is alpha Rom hard to install?
Click to expand...
Click to collapse
No. Details should be in the OP
kaluna00 said:
No. Details should be in the OP
Click to expand...
Click to collapse
question, really quick... "partition backup procedure:
** This Is Required To Downgrade Back To Nougat 7.0 **
use a twrp flashable zip for your specific variant that is based on 7.0 nougat
or
download partition backup & restore" what does this mean haha?
stevieshae said:
question, really quick... "partition backup procedure:
** This Is Required To Downgrade Back To Nougat 7.0 **
use a twrp flashable zip for your specific variant that is based on 7.0 nougat
or
download partition backup & restore" what does this mean haha?
Click to expand...
Click to collapse
The first part just means to boot into TWRP recovery and use the backup function preferably with an SD card and then back that up somewhere else. Boot into TWRP, select Backup, make sure Boot, System, and Data are selected (They should be by default) select storage and choose where you want to save the recovery. Then Swipe to Backup, this can take a while.
Once you're done with backing up, should anything go wrong later, you can boot back into TWRP and select the backup using Restore, to go back to your original state at the time of backup.
jackson019 said:
The first part just means to boot into TWRP recovery and use the backup function preferably with an SD card and then back that up somewhere else. Boot into TWRP, select Backup, make sure Boot, System, and Data are selected (They should be by default) select storage and choose where you want to save the recovery. Then Swipe to Backup, this can take a while.
Once you're done with backing up, should anything go wrong later, you can boot back into TWRP and select the backup using Restore, to go back to your original state at the time of backup.
Click to expand...
Click to collapse
Thank you jackson for the fast response, have you tried the rom, and do you like it?
stevieshae said:
Thank you jackson for the fast response, have you tried the rom, and do you like it?
Click to expand...
Click to collapse
I'm currently using Alpha Omega v1.3.0 with my VS995 and it seems pretty good. Unless it's been updated though, the Oreo firmware is missing from v1.3.0. If you're on a ROM that isn't based on Oreo firmware, you need a ROM with Oreo firmware flashed first. I used AO 1.0.7, then clean installed 1.3.0 on top of it. I also had a weird bug with advanced calling getting disabled, but I fixed it and posted the solution in the main AO thread. I think it was a rare issue though on Verizons end. Finally, Magisk Manager was recently updated and no longer supports Magisk versions under v18.0. Since AO v1.3.0 comes with Magisk v17.1 you'll probably have to flash Magisk v18.1 (latest as of right now) to get that working properly.
jackson019 said:
I'm currently using Alpha Omega v1.3.0 with my VS995 and it seems pretty good. Unless it's been updated though, the Oreo firmware is missing from v1.3.0. If you're on a ROM that isn't based on Oreo firmware, you need a ROM with Oreo firmware flashed first. I used AO 1.0.7, then clean installed 1.3.0 on top of it. I also had a weird bug with advanced calling getting disabled, but I fixed it and posted the solution in the main AO thread. I think it was a rare issue though on Verizons end. Finally, Magisk Manager was recently updated and no longer supports Magisk versions under v18.0. Since AO v1.3.0 comes with Magisk v17.1 you'll probably have to flash Magisk v18.1 (latest as of right now) to get that working properly.
Click to expand...
Click to collapse
I cant lock with fingerprint. I came from lineage 7.1(android N) and I dont see anything on how to use fingerprint.... any ideas?
stevieshae said:
I cant lock with fingerprint. I came from lineage 7.1(android N) and I dont see anything on how to use fingerprint.... any ideas?
Click to expand...
Click to collapse
Are you on Alpha Omega now? If you went from a Nougat based ROM straight to Oreo, then you need to make sure the Oreo firmware gets flashed or the fingerprint will not work (There won't even be a fingerprint option in the menu). Clean Install AO 1.0.7 which contains Oreo firmware, then clean install AO 1.3.0 and you should be fine. Note that Magisk is out of date in the ROM and you should also flash Magisk v18.1 as well if you run into an issue with Magisk Manager.
jackson019 said:
Are you on Alpha Omega now? If you went from a Nougat based ROM straight to Oreo, then you need to make sure the Oreo firmware gets flashed or the fingerprint will not work (There won't even be a fingerprint option in the menu). Clean Install AO 1.0.7 which contains Oreo firmware, then clean install AO 1.3.0 and you should be fine. Note that Magisk is out of date in the ROM and you should also flash Magisk v18.1 as well if you run into an issue with Magisk Manager.
Click to expand...
Click to collapse
I cant get texting to work.. or calling? is that because I need to do the flash like you said?
stevieshae said:
I cant get texting to work.. or calling? is that because I need to do the flash like you said?
Click to expand...
Click to collapse
Sounds like you didn't install Alpha Omega 1.0.7 first. I had the same issue when the Oreo firmware didn't get installed coming from Nougat. If you clean install AO 1.0.7 in the install log you should see something about "Flashing prerequisite full firmware" at the beginning. Following the completion of that, you need to follow the same clean install process to flash AO 1.3.0 and you should be good.
jackson019 said:
Sounds like you didn't install Alpha Omega 1.0.7 first. I had the same issue when the Oreo firmware didn't get installed coming from Nougat. If you clean install AO 1.0.7 in the install log you should see something about "Flashing prerequisite full firmware" at the beginning. Following the completion of that, you need to follow the same clean install process to flash AO 1.3.0 and you should be good.
Click to expand...
Click to collapse
So flash AO 1.0.7 then 1.3 by formating data, the wipe dalvic, data, system, and cache. then install twrp and magisk. reboot into recovery. then install 1.3?
Also... Should I install dirty santa kernal?
stevieshae said:
So flash AO 1.0.7 then 1.3 by formating data, the wipe dalvic, data, system, and cache. then install twrp and magisk. reboot into recovery. then install 1.3?
Click to expand...
Click to collapse
First off, you should be rooted with TWRP 3.2.3-4 from here already installed. Then follow these steps:
Clean Install -> Format Data -> Advanced Wipe -> Cache, Dalvik, Data, System
Install 1.0.7 -> Choose the proper kernel for your root method
If you rooted via dirtysanta, choose the mk2000 santa kernel
Reboot to recovery, no need to go to setup
Clean Install 1.3.0 -> Format Data -> Advanced Wipe -> Cache, Dalvik, Data, System
Use the same kernel from above
Flash Magisk v18.1
Wipe Dalvik/Cache
Reboot to System