Hello everyone!
Bought my Oneplus 3 about a month ago and I am generally happy with it. When I bought it, the phone had Oxygen OS 3.2.1 installed on it and as I have heard that 3.2.4 had issues on it, I didn't install it for a while. Then 3.2.6 came out, I decided to give it a try, but as I couldn't find a direct OTA from 3.2.1 to 3.2.6, I firstly sideloaded the incremental update to 3.2.4 and then from 3.2.6. Of course, wiped the cache afterwards.
However, I started experiencing a significant drop in battery life - not that I had to charge my phone 3 times a day or anything, but still really noticeable (For example, with a day of normal usage I would have had 50-60% left, after the 3.2.6 update - probably 20-25%). So I decided that I had to do a clean install of the OS.
Now to the important part, what I did was wipe cache and data, then with ADB sideloaded the full 3.2.6 zip to my phone. The problem is that I still don't think the battery life is quite like what it was in 3.2.1. Onto my question - would you consider what I have done a clean install, if not - could you please give me instructions how can it be done correctly(if possible without unlocking bootloader, installing TWRP, etc as I do not want to tinker with my phone a lot (of course, I have to - I will do it)). Any other suggestions for resolving the battery drain issue are welcome as well.
Thanks in advance!
ivan.panchev said:
Hello everyone!
Bought my Oneplus 3 about a month ago and I am generally happy with it. When I bought it, the phone had Oxygen OS 3.2.1 installed on it and as I have heard that 3.2.4 had issues on it, I didn't install it for a while. Then 3.2.6 came out, I decided to give it a try, but as I couldn't find a direct OTA from 3.2.1 to 3.2.6, I firstly sideloaded the incremental update to 3.2.4 and then from 3.2.6. Of course, wiped the cache afterwards.
However, I started experiencing a significant drop in battery life - not that I had to charge my phone 3 times a day or anything, but still really noticeable (For example, with a day of normal usage I would have had 50-60% left, after the 3.2.6 update - probably 20-25%). So I decided that I had to do a clean install of the OS.
Now to the important part, what I did was wipe cache and data, then with ADB sideloaded the full 3.2.6 zip to my phone. The problem is that I still don't think the battery life is quite like what it was in 3.2.1. Onto my question - would you consider what I have done a clean install, if not - could you please give me instructions how can it be done correctly(if possible without unlocking bootloader, installing TWRP, etc as I do not want to tinker with my phone a lot (of course, I have to - I will do it)). Any other suggestions for resolving the battery drain issue are welcome as well.
Thanks in advance!
Click to expand...
Click to collapse
Personally, i don't think it' s not a clean install, because a clean install need a full wipe of all partitions (internal storage not mandatory)
Without installing TWRP, i think it will be hard to do a really clean flash. But if you change your mind, you will not regret it
First, i suggest you to follow this great guide (and say thanks to his op) : http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733 to unlock, install twrp, backup.
Second, when you are in TWRP, you can wipe your phone (advanced wipe, all partitions except internal storage and usb-otg)
Third, you can install a ROM based on stock OOS or CM13, look in the right section : http://forum.xda-developers.com/oneplus-3/development
Then, you will have a clean system
Lowxorx said:
Personally, i don't think it' s not a clean install, because a clean install need a full wipe of all partitions (internal storage not mandatory)
Without installing TWRP, i think it will be hard to do a really clean flash. But if you change your mind, you will not regret it
First, i suggest you to follow this great guide (and say thanks to his op) : http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733 to unlock, install twrp, backup.
Second, when you are in TWRP, you can wipe your phone (advanced wipe, all partitions except internal storage and usb-otg)
Third, you can install a ROM based on stock OOS or CM13, look in the right section : http://forum.xda-developers.com/oneplus-3/development
Then, you will have a clean system
Click to expand...
Click to collapse
I am willing to install TWRP and do a clean install of the OS, however, I do insist on having the Onplus-provided ROM(if it can be called ROM at all). Is is possible to install it with TWRP? If not, I should probably install TWRP, wipe everything, go back to the stock recovery and install the zip provided from Onplus? Really appreciate your answer!
ivan.panchev said:
I am willing to install TWRP and do a clean install of the OS, however, I do insist on having the Onplus-provided ROM(if it can be called ROM at all). Is is possible to install it with TWRP? If not, I should probably install TWRP, wipe everything, go back to the stock recovery and install the zip provided from Onplus? Really appreciate your answer!
Click to expand...
Click to collapse
You can consider to flash FreedomOS, a stock based rom who allow you to debloat your phone with Aroma Installer. This rom is really close to stock OOS, an much more easy to flash than the stock zip. Follow the op's post here : http://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348
If you really want the full stock rom you can search on the oneplus site, i think you can find the zip file with the stock OOS (but i really recommend you to choose FreedomOS )
Lowxorx said:
You can consider to flash FreedomOS, a stock based rom who allow you to debloat your phone with Aroma Installer. This rom is really close to stock OOS, an much more easy to flash than the stock zip. Follow the op's post here : http://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348
If you really want the full stock rom you can search on the oneplus site, i think you can find the zip file with the stock OOS (but i really recommend you to choose FreedomOS )
Click to expand...
Click to collapse
I believe I have the full zip for the full 3.2.6 version, the question is whether or not I can flash it directly with TWRP. If that's the case, then that's what I am going to do!
ivan.panchev said:
I believe I have the full zip for the full 3.2.6 version, the question is whether or not I can flash it directly with TWRP. If that's the case, then that's what I am going to do!
Click to expand...
Click to collapse
If you have the stock 3.2.6 zip file you can follow theses instructions on the official oneplus site. There are both TWRP and stock recovery guide.
ivan.panchev said:
I believe I have the full zip for the full 3.2.6 version, the question is whether or not I can flash it directly with TWRP. If that's the case, then that's what I am going to do!
Click to expand...
Click to collapse
If you install TWRP, wipe everything, flash the full ROM zip of OOS 3.2.6, it will work. When you unlock your bootloader, a full wipe occurs regardless, so you may just want to do that and see if things improve.
Sent from the OnePlus 3...
making it "RAIN!"
noobtoob said:
If you install TWRP, wipe everything, flash the full ROM zip of OOS 3.2.6, it will work. When you unlock your bootloader, a full wipe occurs regardless, so you may just want to do that and see if things improve.
Sent from the OnePlus 3...
making it "RAIN!"
Click to expand...
Click to collapse
After the second full charge, I think the things are a lot better - I have only used it for 30 minutes screen on today but is still on 82% (with more than 10 hours idle), which a lot like what I used to have when with 3.2.1. Plus, I am in an area with low network coverage, so that's draining the battery as well. Thanks for all of your answers, if I feel the need, will probably flash the whole stock rom with TWRP.
Related
Hi i want to apply the OTA (MD4) and keep my root acces, so my question is, if is possible to use voodoo root keeper app to apply this update. thanks in advance
juancaperez2000 said:
Hi i want to apply the OTA (MD4) and keep my root acces, so my question is, if is possible to use voodoo root keeper app to apply this update. thanks in advance
Click to expand...
Click to collapse
Hey Juan,
I'm assuming you just got the notification for the OTA. You actually don't have to apply it to get the latest and greatest for our phone. All you have to do is flash Freeza's Stock Rooted Rom (You'll want the DeOdex MD4 Rom). It'll give you the most up-to-date Stock Rom with Root. I've linked and quoted a previous post I made which will give you directions to flash it. Also, CNexus has done a great guide about OTAs over in the general sub-forum. I suggest giving that a look-through.
Also, just a note on the flashing sequence below: In step 4 below, if you're coming from a stock Rom and you're going to a stock Rom, all you have to do is wipe Cache and Dalvik Cache. If you're going to a different Rom, it's best to do a full wipe (in my opinion).
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
topherk said:
Hey Juan,
I'm assuming you just got the notification for the OTA. You actually don't have to apply it to get the latest and greatest for our phone. All you have to do is flash Freeza's Stock Rooted Rom (You'll want the DeOdex MD4 Rom). It'll give you the most up-to-date Stock Rom with Root. I've linked and quoted a previous post I made which will give you directions to flash it. Also, CNexus has done a great guide about OTAs over in the general sub-forum. I suggest giving that a look-through.
Also, just a note on the flashing sequence below: In step 4 below, if you're coming from a stock Rom and you're going to a stock Rom, all you have to do is wipe Cache and Dalvik Cache. If you're going to a different Rom, it's best to do a full wipe (in my opinion).
Click to expand...
Click to collapse
thanks!!! i tought that i need do like qbking77 did on his videos using oding for i can keep my data but you'r right dirty flash can work too (stock to stock)
juancaperez2000 said:
thanks!!! i tought that i need do like qbking77 did on his videos using oding for i can keep my data but you'r right dirty flash can work too (stock to stock)
Click to expand...
Click to collapse
That's right, dirty flashing should work fine. If you're noticing any major issues (FCs, reboots, etc), you might want to use Titanium Backup to back up your important stuff and do a clean flash. But hopefully the dirty flash will be good.
I saw this post earlier, and was going to reply pretty much the same thing. Then I said to myself nope im going to leave it alone Topherk will come by soon enough with a way better reply and exact instructions!! :thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup:
Keep up the great work
Transmitted with a portable device using Xparent Blue Tapatalk 2
edfunkycold said:
I saw this post earlier, and was going to reply pretty much the same thing. Then I said to myself nope im going to leave it alone Topherk will come by soon enough with a way better reply and exact instructions!! :thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup::thumbup:
Keep up the great work
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Thanks Ed, I appreciate the feedback.
Thankfully, I put the hard work in a while ago, so now (for most questions) all I have to do is paste that one post and I'm good to go.
As an aside: yesterday I helped a friend root his GS3 and realized I'm much better at explaining things here on XDA than I am in real life. I kept jumping ahead of myself and trying to explain about wiping /system before I even explained what a custom Recovery is. I should've just asked him to post a question "how do I root" and I could've done a better job explaining it, haha.
Hi all, relative newb here.
If there is an RTFM on this, I'm all ears, and won't mind one bit.
I want to take a stock SPH-L710 to CM13, and read the thread. First step is to install CWM. I will try this first step later tonight, but question I have is whether I need to be rooted first.
Reason I ask is prior to taking OH1, I "tried" to get CWM installed on ND8 version, and it wouldn't take. I tried first via Odin 3.07, allowing after the SUCCESS message to let the phone reboot itself, and when I shut down and tried to get into recovery mode, it would just go tot he stock "download mode" screen. i then tried to flash via Odin, and not allow reboot, pulled the battery, and restarted into recovery, and the stock download screen still came up.
In reading the thread about CM13, the thread says to load CWM. The version that is linked to on the clockworkmod page is 6.0.4.5, which is not the version I was trying to install above (it was an older version). Can I assume that installing this version will allow boot into the CWM recovery, so I can get to the next step?
I also searched, and found useful pages on how to convert a .img to at tar.md5, so I think I'm good to use the version on the cwm url.
I've searched hard to find any mention of not being able to boot into CWM, and it has something to do with OTA updates. Asking these questions now, since for some reason, I can only get this site up here at work, not at home using IE on a 32 bit machine.
TIA...and pointers to RTFMs greatly appreciated.
Eric
ejaf said:
Hi all, relative newb here.
If there is an RTFM on this, I'm all ears, and won't mind one bit.
I want to take a stock SPH-L710 to CM13, and read the thread. First step is to install CWM. I will try this first step later tonight, but question I have is whether I need to be rooted first.
Reason I ask is prior to taking OH1, I "tried" to get CWM installed on ND8 version, and it wouldn't take. I tried first via Odin 3.07, allowing after the SUCCESS message to let the phone reboot itself, and when I shut down and tried to get into recovery mode, it would just go tot he stock "download mode" screen. i then tried to flash via Odin, and not allow reboot, pulled the battery, and restarted into recovery, and the stock download screen still came up.
In reading the thread about CM13, the thread says to load CWM. The version that is linked to on the clockworkmod page is 6.0.4.5, which is not the version I was trying to install above (it was an older version). Can I assume that installing this version will allow boot into the CWM recovery, so I can get to the next step?
I also searched, and found useful pages on how to convert a .img to at tar.md5, so I think I'm good to use the version on the cwm url.
I've searched hard to find any mention of not being able to boot into CWM, and it has something to do with OTA updates. Asking these questions now, since for some reason, I can only get this site up here at work, not at home using IE on a 32 bit machine.
TIA...and pointers to RTFMs greatly appreciated.
Eric
Click to expand...
Click to collapse
The thing is CWM is outdated, i believe to install CM13 successfully, you'd have to install twrp.
Here is the link to the latest, grab the first tar flash it via odin & you should be good to boot into recovery to flash roms.
https://dl.twrp.me/d2spr/
Lonelyskatter12 said:
The thing is CWM is outdated, i believe to install CM13 successfully, you'd have to install twrp.
Click to expand...
Click to collapse
Interesting news...thanks. The "Official" thread says that only CWM can be used. Of course, since that thread has a gazillion replies, I couldn't get through it. Of course...I just noticed that the thread I was reading was not specific to CM13, so I have to do more reading.
Main question....haven't got a hit on whether, after installing custom recovery, I need to root or not.
I am also at a disadvantage, since I can't get this site up at home, only at work, so I can't dowload anything while reading.
Thanks for the reply.
ejaf said:
Interesting news...thanks. The "Official" thread says that only CWM can be used. Of course, since that thread has a gazillion replies, I couldn't get through it. Of course...I just noticed that the thread I was reading was not specific to CM13, so I have to do more reading.
Main question....haven't got a hit on whether, after installing custom recovery, I need to root or not.
I am also at a disadvantage, since I can't get this site up at home, only at work, so I can't dowload anything while reading.
Thanks for the reply.
Click to expand...
Click to collapse
Yes, the official thread is CM13, you don't need Cwm, pretty much twrp supports marshmallow now.
And i believe you would need root.
If there's any way for you to be able to download the files, id be happy to give you step by step instructions :good:
THANKS BIG TIME!!!
Cool beans! I got TWRP 3.0.2.0 installed! And when exiting, I installed superSU, followed instructions, updated via play store, and disabled Knox.
I am in the process of downloading CM13 Nightly from cyanogenmod (cm-13.0-20160428-NIGHTLY-d2spr.zip). I don't see an "official" release there, so I guess a nightly is the best I can do if I want CM13 (weird though, since the unofficial thread started in November, and I only see nightlies starting in April.
So this is what's next correct?:
- wipe the device
- flash rom
- flash gapps
- reboot system
TIA...Eric
FYI...I couldn't take it anymore, didn't feel like tracking the IE issue, so I downloaded chrome
ejaf said:
THANKS BIG TIME!!!
Cool beans! I got TWRP 3.0.2.0 installed! And when exiting, I installed superSU, followed instructions, updated via play store, and disabled Knox.
I am in the process of downloading CM13 Nightly from cyanogenmod (cm-13.0-20160428-NIGHTLY-d2spr.zip). I don't see an "official" release there, so I guess a nightly is the best I can do if I want CM13 (weird though, since the unofficial thread started in November, and I only see nightlies starting in April.
So this is what's next correct?:
- wipe the device
- flash rom
- flash gapps
- reboot system
TIA...Eric
FYI...I couldn't take it anymore, didn't feel like tracking the IE issue, so I downloaded chrome
Click to expand...
Click to collapse
Yeah the Unofficial thread was being maintained by a Developer, who stopped as soon as the officials came out.
And yes
1.) Wipe Data, Cache, System, & Internal Storage (So backup anything on there)
2.) Flash Rom, Gapps, SuperSu 2.71 (If you want root)
& should be good to go
Just found this post here on the "Unofficial" CM thread, which causes me some concern:
http://forum.xda-developers.com/showpost.php?p=65865323&postcount=207
This basically states:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
An example of the steps with the assumption someone was coming from the stock android with TWRP installed and everything to be flash stored on the external sdcard. Assuming the user is in TWRP to start.
Issue a full format of the following partitions, /system, /userdata, /internalstorage, /cache, /dalvik
Add the rom to the flash queue (eg. cm-13.0)
Add an android 6 compatible gapps to the queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot into system for the first time
Once booted reboot into TWRP
Add the same rom zip to the flash queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot to system
Everything should be functioning (at least mostly)
Enjoy
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Not sure about the APN stuff, so I guess i have to read more about that as well.
Thanks for getting me through the "baby" steps though...I'm infinitely further than I was before
ejaf said:
Just found this post here on the "Unofficial" CM thread, which causes me some concern:
http://forum.xda-developers.com/showpost.php?p=65865323&postcount=207
This basically states:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
An example of the steps with the assumption someone was coming from the stock android with TWRP installed and everything to be flash stored on the external sdcard. Assuming the user is in TWRP to start.
Issue a full format of the following partitions, /system, /userdata, /internalstorage, /cache, /dalvik
Add the rom to the flash queue (eg. cm-13.0)
Add an android 6 compatible gapps to the queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot into system for the first time
Once booted reboot into TWRP
Add the same rom zip to the flash queue
Add the Virgin fix to the queue
Run the flash queue (or flash the above file individually without rebooting)
Reboot to system
Everything should be functioning (at least mostly)
Enjoy
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Not sure about the APN stuff, so I guess i have to read more about that as well.
Thanks for getting me through the "baby" steps though...I'm infinitely further than I was before
Click to expand...
Click to collapse
That's the order, now about the apn im not sure, i just use mine for wifi and stuff.
That Cyanogenmod build "04282016" wasn't running so well for me, so I'm on AICP for now.
But i would suggest, OctOs , AICP, or Exodus Roms. Those are the most stable roms for this device.
Same steps just different ROMs.
But i did hear Exodus gives you data right off the bat, so that'd be good to try
Interesting...thanks for the tips. Hopefully I won't have to bother any of you all again, since I really don't have much in the way of knowledge to return
E
FYI...was able to boot up into CM 12.1 over the weekend. Jury's still out on whether to go to a 6.0.1 based ROM, but appreciate all the help.
Eric
I found the APN fix didn't work with the CM13 rom (I've used it previously with 12.1 fine). I also found that the build-in cm update failed on 20160505 nightly. Not sure if this was just that day or a known bug.
So I rooted my 5X with the help of the Nexus root toolkit. I have successfully flashed Elementalx kernel through TWRP and have tried flashing the ROM and GApps through the toolkit and through TWP but always end up in a bootloop at the Google screen. What am I doing wrong?
I'm just looking to load a Custom ROM to possibly squeeze some extra battery life out of my 5X.
Bootloop
Hi mate,
Did you try and clear cache & dalvic after installing the rom through TWRP.
Also did you install the kernel after the rom & gapps, also try another kernel maybe, or use the stock one with the rom ( if possble ).
or grab the factory image and go back to stock & lock the bootloader.
Also, I did read if you do not use the SDK toolkit from Google ( contains Fastboot and ADB ) , you can have issues like this.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I will do some reading and see what else I find.
Later
Which ROM are you flashing? Most have a decent installation instruction you should follow precisely.
Basic steps in correct order:
Download ROM and Gapps.
Clear data and caches (always clean install a new ROM).
Flash ROM
Flash Gapps
Flash custom kernel
Root.
Boot (on pre 7.0 first boot may take 10+ minutes)
slysurfer said:
Hi mate,
Did you try and clear cache & dalvic after installing the rom through TWRP.
Also did you install the kernel after the rom & gapps, also try another kernel maybe, or use the stock one with the rom ( if possble ).
or grab the factory image and go back to stock & lock the bootloader.
Also, I did read if you do not use the SDK toolkit from Google ( contains Fastboot and ADB ) , you can have issues like this.
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I will do some reading and see what else I find.
Later
Click to expand...
Click to collapse
I chose options to clear cache and dalvik when using the Nexus root toolkit and then again manually when I tried to flash through TWRP. I don't quite remember which order I tried to install the kernel. I'm assuming from your question the kernel always always has to be flashed after flashing a ROM? (Even if the kernel was previously flashed?)
I'l look into doing it the 'old fashioned' way as it seems it should iron out any issues. Thanks for the help and please reply if you have a chance!
peltus said:
Which ROM are you flashing? Most have a decent installation instruction you should follow precisely.
Basic steps in correct order:
Download ROM and Gapps.
Clear data and caches (always clean install a new ROM).
Flash ROM
Flash Gapps
Flash custom kernel
Root.
Boot (on pre 7.0 first boot may take 10+ minutes)
Click to expand...
Click to collapse
I'm attempting to flash the latest version of Pure Nexus, Gapps, and Elementalx. From what little research I've done it seems like people are able to run this ROM and kernel combination without issues.
I followed these steps to a T and cleared cache/dalvik after every flash. I am on Nougat right now and the phone would get as far as the Google bot logo. The longest I waited was probably 10-15 minutes. Could it possibly take longer on Nougat? Does that have anything to do with encryption?
Thanks all!
Andrew
Angdvl089 said:
I chose options to clear cache and dalvik when using the Nexus root toolkit and then again manually when I tried to flash through TWRP. I don't quite remember which order I tried to install the kernel. I'm assuming from your question the kernel always always has to be flashed after flashing a ROM? (Even if the kernel was previously flashed?)
I'l look into doing it the 'old fashioned' way as it seems it should iron out any issues. Thanks for the help and please reply if you have a chance!
I'm attempting to flash the latest version of Pure Nexus, Gapps, and Elementalx. From what little research I've done it seems like people are able to run this ROM and kernel combination without issues.
I followed these steps to a T and cleared cache/dalvik after every flash. I am on Nougat right now and the phone would get as far as the Google bot logo. The longest I waited was probably 10-15 minutes. Could it possibly take longer on Nougat? Does that have anything to do with encryption?
Thanks all!
Andrew
Click to expand...
Click to collapse
It's unclear to me if you did a clean flash or not.
Check out post #2 in the pure Nexus thread for detailed installation instructions. Follow them to the letter and you should be fine.
I've been running pure Nexus with elementalX for some time now and never had any problems. Are you sure you aren't using the nougat version of elementalX? 3.05 is NOT the correct version for running pure Nexus at this moment as the ROM is still based on 6.01.
peltus said:
It's unclear to me if you did a clean flash or not.
Check out post #2 in the pure Nexus thread for detailed installation instructions. Follow them to the letter and you should be fine.
I've been running pure Nexus with elementalX for some time now and never had any problems. Are you sure you aren't using the nougat version of elementalX? 3.05 is NOT the correct version for running pure Nexus at this moment as the ROM is still based on 6.01.
Click to expand...
Click to collapse
THAT must be the problem! I didn't know it was running on Marshmallow. I'll give that a try now. Thanks for the obvious answer!
Andrew
Angdvl089 said:
THAT must be the problem! I didn't know it was running on Marshmallow. I'll give that a try now. Thanks for the obvious answer!
Andrew
Click to expand...
Click to collapse
So not only did I need the Marshmallow version of ElementalX but I also needed to update my vendor image for the PN ROM. Thanks for the help! All set from here on out.
Andrew
Angdvl089 said:
So not only did I need the Marshmallow version of ElementalX but I also needed to update my vendor image for the PN ROM. Thanks for the help! All set from here on out.
Andrew
Click to expand...
Click to collapse
Glad to be of help. Have fun with your phone!
First of all make sure you're on the correct firmware for whatever rom and kernel your wanting to use or it will not boot. It will bootloop if on say a Marshmallow build amd your trying to install a Nougat rom.. Now if all matches you can proceed.. This is how I've installed roms for 5-6 years: in twrp wipe: data, system, cache, delvik cache, flash rom, flash gapps (open gapps mini is what I use) flash either SuperSu zip or PHH superuser, next reboot. Some roms (example: DU and AICP) come with SU already inside so no need to flash it.. You can tell because in twrp during flash process you'll see SU being installed If rom comes with it. If you choose to use PHH Superuser you'll need his app from Google play store. Just grab it (search PHH Superuser) and open it and you should be good to go. I use SuperSU as I've had issues using other SU with ARISE sound which is also something i use. Hope that's not confusing. Hmu on hangouts if you need help and I'll help when I'm available: [email protected]
Sent from my LG Nexus 5X using XDA Labs
Need any help
Hi mate, i have now unlocked bootloader, installed twrp and installed pure nexus rom. Did not use the toolkit, i used adb and fastboot using commands... It was easy. If you need a hand with anything give us a yell . [quoter=Angdvl089;68875927]So I rooted my 5X with the help of the Nexus root toolkit. I have successfully flashed Elementalx kernel through TWRP and have tried flashing the ROM and GApps through the toolkit and through TWP but always end up in a bootloop at the Google screen. What am I doing wrong?
I'm just looking to load a Custom ROM to possibly squeeze some extra battery life out of my 5X.[/QUOTE]
hello all,
I have a rooted OP3 running the latest TWRP recovery. Using these instructions I am trying to upgrade to 3.2.8 from 3.2.7. There are no errors displayed during OOS or SuperSU install steps.
But when the phone reboots - it stays stuck at the boot animation. This happens across several attempts. I do not have xposed installed, if it helps. Repeating the above steps with a 3.2.7 image works without issues.
Is there any way I can figure out where the 3.2.8 reboot is getting stuck at? I *do not* want to do a fresh install.
Any thoughts/ Suggestions? I have already posted at the above thread and thought I'd try my luck here too.
EDIT: Can a MOD please move this to Q&A forum. Just realized I posted to Guides, News & Discussion.
backup all your data and install 3.2.8 with the official procedure
Sacob said:
backup all your data and install 3.2.8 with the official procedure
Click to expand...
Click to collapse
That's my last option. But that's as good as starting from scratch. In which case, I might as well postpone until Nougat arrives on the OP3
tropicanapure said:
That's my last option. But that's as good as starting from scratch. In which case, I might as well postpone until Nougat arrives on the OP3
Click to expand...
Click to collapse
and wait without a phone?
Flash the new Beta 10. i'm currently using it with root and it works great
Not sure what you mean - without a phone. I was able to roll back to 3.2.7 with zero issues
I was mulling over installing the Beta - but I understand Nougat is due in Jan? Also, is there a process to move to b10 without losing data?
Sacob said:
and wait without a phone?
Flash the new Beta 10. i'm currently using it with root and it works great
Click to expand...
Click to collapse
tropicanapure said:
Not sure what you mean - without a phone. I was able to roll back to 3.2.7 with zero issues
I was mulling over installing the Beta - but I understand Nougat is due in Jan? Also, is there a process to move to b10 without losing data?
Click to expand...
Click to collapse
i got the impression that your phone wasn't booting xD
well, every time i flash those betas (9 and 10) TWRP asks me for a PIN that doesn't exists and to solve that i need wipe everything... so i wouldn't count on that
tropicanapure said:
hello all,
I have a rooted OP3 running the latest TWRP recovery. Using these instructions I am trying to upgrade to 3.2.8 from 3.2.7. There are no errors displayed during OOS or SuperSU install steps.
But when the phone reboots - it stays stuck at the boot animation. This happens across several attempts. I do not have xposed installed, if it helps. Repeating the above steps with a 3.2.7 image works without issues.
Is there any way I can figure out where the 3.2.8 reboot is getting stuck at? I *do not* want to do a fresh install.
Any thoughts/ Suggestions? I have already posted at the above thread and thought I'd try my luck here too.
EDIT: Can a MOD please move this to Q&A forum. Just realized I posted to Guides, News & Discussion.
Click to expand...
Click to collapse
Did you download the full 3.2.8 zip from http://downloads.oneplus.net? I did. And to my surprise, it erases the whole userdata partition, including TWRP backups and downloaded files (including SuperSU zip). So big warning if you try with that zip. I assume that this zip is intended for those reverting from Nougat Beta, to go back from F2FS to EXT4.
My solution was to restore an old TWRP backup that was saved on my PC and then reflash a modified full 3.2.8 zip where the last line in the update script was removed: the one that erases userdata partition. So before flashing full 3.2.8 zip from http://downloads.oneplus.net I recommend you to remove the last line in the update script.
No, I downloaded the Full ZIP from this official thread on the OP3 forums. I was aware of that line though. And from previous experience - the first thing I do when I make a TWRP backup is to move it off the phone. That and I purchased Titanium Backup long time ago. I use it to back up stuff surgically and sync it up to Dropbox every night. The app also seems to have the ability to make a recovery-flashable "update.zip" - something I have yet to try.
Appreciate the heads-up though.
ptblad said:
Did you download the full 3.2.8 zip from http://downloads.oneplus.net? I did. And to my surprise, it erases the whole userdata partition, including TWRP backups and downloaded files (including SuperSU zip). So big warning if you try with that zip. I assume that this zip is intended for those reverting from Nougat Beta, to go back from F2FS to EXT4.
My solution was to restore an old TWRP backup that was saved on my PC and then reflash a modified full 3.2.8 zip where the last line in the update script was removed: the one that erases userdata partition. So before flashing full 3.2.8 zip from http://downloads.oneplus.net I recommend you to remove the last line in the update script.
Click to expand...
Click to collapse
tropicanapure said:
No, I downloaded the Full ZIP from this official thread on the OP3 forums. I was aware of that line though. And from previous experience - the first thing I do when I make a TWRP backup is to move it off the phone. That and I purchased Titanium Backup long time ago. I use it to back up stuff surgically and sync it up to Dropbox every night. The app also seems to have the ability to make a recovery-flashable "update.zip" - something I have yet to try.
Appreciate the heads-up though.
Click to expand...
Click to collapse
OK. I also use TB, and from now on I use cloud storage :laugh:
After the full modified 3.2.8 zip I successfully flashed official SuperSU 2.79, Xposed v87 and Bluspark r25 kernel. I use F2FS on data partition. It boots and runs fine!
The only thing I'm a bit concerned about is that it stays on the bootlogo (OnePlus logo, Powered by Android) for about 25 secs before the bootanimation begins when booting to system. Much faster before. When booting to recovery (TWRP 28, Bluspark) the time on bootlogo is normal (short). Any thoughts on that?
I wish I had, man. You went a number of steps ahead when your phone went past the boot animation
As a afterthought - try looking through your logs.
ptblad said:
OK. I also use TB, and from now on I use cloud storage :laugh:
After the full modified 3.2.8 zip I successfully flashed official SuperSU 2.79, Xposed v87 and Bluspark r25 kernel. I use F2FS on data partition. It boots and runs fine!
The only thing I'm a bit concerned about is that it stays on the bootlogo (OnePlus logo, Powered by Android) for about 25 secs before the bootanimation begins when booting to system. Much faster before. When booting to recovery (TWRP 28, Bluspark) the time on bootlogo is normal (short). Any thoughts on that?
Click to expand...
Click to collapse
HI please help an old noob out
I recently got an S9 and coming from HTC realised touch wizz is awful.
I have flashed ROMs before (HTC desire) but not for a while so found a guide for ResurrectionRemix and cracked on with it.
I have TWRP 3.2.3-0 installed and flashed the ResurrectionRemix 6.0 on S9 ROM with stock Gapps (it all went as it should as far as I could tell no errors ect).
However, when I reboot the phone it just gets stuck on the Samsung boot screen.
Is there anyone who would help me troubleshoot where I went wrong, please?
I think maybe I need to root first?
Thanks
r3t0x said:
HI please help an old noob out
I recently got an S9 and coming from HTC realised touch wizz is awful.
I have flashed ROMs before (HTC desire) but not for a while so found a guide for ResurrectionRemix and cracked on with it.
I have TWRP 3.2.3-0 installed and flashed the ResurrectionRemix 6.0 on S9 ROM with stock Gapps (it all went as it should as far as I could tell no errors ect).
However, when I reboot the phone it just gets stuck on the Samsung boot screen.
Is there anyone who would help me troubleshoot where I went wrong, please?
I think maybe I need to root first?
Thanks
Click to expand...
Click to collapse
Go into twrp recovery then go to wipe, advanced, then check davlik and check cache then slide to wipe then reboot system
Should boot now but first boot takes a little
If after a few mins you still on that bubble shooting thing then you may have to reflash again
But remember after every flash wipe davlik
Flash ROM first
Flash magisk second(for root)
But only get magisk from XDA unless you trust others
Once up and running go into magisk and if you need to install then do that first then MAGISK HIDE all google apps is what I do especially gms I magisk hide that first also bank apps and certain games that have problems running I found they run perfect after I magisk hide them also go to downloads in magisk and install FORCE FAST CHARGE it helps with charging...
Have fun!!!
81! said:
Go into twrp recovery then go to wipe, advanced, then check davlik and check cache then slide to wipe then reboot system
Should boot now but first boot takes a little
If after a few mins you still on that bubble shooting thing then you may have to reflash again
But remember after every flash wipe davlik
Flash ROM first
Flash magisk second(for root)
But only get magisk from XDA unless you trust others
Once up and running go into magisk and if you need to install then do that first then MAGISK HIDE all google apps is what I do especially gms I magisk hide that first also bank apps and certain games that have problems running I found they run perfect after I magisk hide them also go to downloads in magisk and install FORCE FAST CHARGE it helps with charging...
Have fun!!!
Click to expand...
Click to collapse
Thanks, Dude I worked out what I was doing wrong. My phone is on the latest vendor firmware and as such RR will not work.
Unfortunately, I was following a guide and this was not mentioned, took a bit of reading on the XDA RR page to sus it out.
Since then I did try a GSI but it kept locking up on me so eventually went back to stock ROM.
I really would like a ROM which is as close to pixel as it can get (I wanted a pixel but this phone is trough work so had little choice).
I have seen Pixel Experience ROMs but I'm not sure if they will work with vendor firmware or not.