Related
Hi guys, I'm freaking out!
I'm proposing to my girlfriend this weekend and the PacMan ROM I was using (4.4.2 I believe) was lagging/running out of storage, so I decided to flash to the newest 4.4.4 ROM I could find. I wanted to make sure my phone was in tip top shape for the big weekend. I booted into TWRP and took the normal steps to flash (wipe ROM,dalvik,cache) but this time I also decided to delete internal storage because I was running out previously and just kind of wanted a fresh start. I decided to try the MerkMod ROM (4.4.4) w/PA 4.4.4 micro GApps, and everything worked great (fast, no reboots) after flashing....until I tried the camera maybe a day later. I got the 'Can't connect to Camera' error, and freaked out immediately because I need to snap some selfies of the big moment this weekend! I then tried deleting the camera thru Titanium Backup and flashing PA's Google Camera module, which didn't work either.
So then I went through all of the steps to go to ND8 stock from MerkMod as outlined by CNexus in this thread. I also switched to Philz recovery. Unfortunately, the camera would also freeze up/not start on the stock ND8 ROM as well (no explicit 'cant connect to camera error' but the screen was all black and the phone froze up). TW + samsung bloat was literally about to make me throw up, so then I decided to try SlimKat 4.4.4 w/Slim GApps, and I'm still getting the camera error. I deleted the Camera2.apk in SlimSettings and downloaded Google Camera, and that didn't work either.
I have no idea what happened! I don't think there was any physical/water damage to the phone, so I don't think it's a hardware issue. Should I try to go back to an older version of the stock ROM? Did this happen because I deleted my internal storage, or used PA Gapps (I've read that both might have contributed)? If so, how do I fix this!? PLEASE HELP!
riazrahman said:
Hi guys, I'm freaking out!
I'm proposing to my girlfriend this weekend and the PacMan ROM I was using (4.4.2 I believe) was lagging/running out of storage, so I decided to flash to the newest 4.4.4 ROM I could find. I wanted to make sure my phone was in tip top shape for the big weekend. I booted into TWRP and took the normal steps to flash (wipe ROM,dalvik,cache) but this time I also decided to delete internal storage because I was running out previously and just kind of wanted a fresh start. I decided to try the MerkMod ROM (4.4.4) w/PA 4.4.4 micro GApps, and everything worked great (fast, no reboots) after flashing....until I tried the camera maybe a day later. I got the 'Can't connect to Camera' error, and freaked out immediately because I need to snap some selfies of the big moment this weekend! I then tried deleting the camera thru Titanium Backup and flashing PA's Google Camera module, which didn't work either.
So then I went through all of the steps to go to ND8 stock from MerkMod as outlined by CNexus in this thread. I also switched to Philz recovery. Unfortunately, the camera would also freeze up/not start on the stock ND8 ROM as well (no explicit 'cant connect to camera error' but the screen was all black and the phone froze up). TW + samsung bloat was literally about to make me throw up, so then I decided to try SlimKat 4.4.4 w/Slim GApps, and I'm still getting the camera error. I deleted the Camera2.apk in SlimSettings and downloaded Google Camera, and that didn't work either.
I have no idea what happened! I don't think there was any physical/water damage to the phone, so I don't think it's a hardware issue. Should I try to go back to an older version of the stock ROM? Did this happen because I deleted my internal storage, or used PA Gapps (I've read that both might have contributed)? If so, how do I fix this!? PLEASE HELP!
Click to expand...
Click to collapse
Right now, I think the best first step for you would be to try flashing the ROM and GAPPs package with a different recovery.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Navigate to the above link and download the latest zip (not md5) file to flash in your current recovery. Your current recovery will simply flash the zip file and overwrite your current recovery with PhilZ.
I personally can't see a GAPPs package causing that sort of issue, as it is not replacing code, changing libraries, or messing with the kernel. The GAPPs package is simply flashing system apps to the /system folder of the Android OS. Additionally, I use the PA GAPPs package when I flash CM11 nightlies.
A recovery can make all the difference of making sure that the correct files are being flashed to the correct areas and I, personally, find PhilZ to be the most bug-free and user-friendly.
When you boot into PhilZ, make sure you have all the files that you intend to flash on your device.
In PhilZ, the Wipe Data/Factory Reset option actually has an option to wipe the device to install a new ROM. Use that option
Install your ROM of choice and your GAPPs package. Reboot and see what happens.
Also, just had a passing thought: Did you flash a custom kernel? Did you not make a backup of your last working setup?
Higgs_Boson said:
Right now, I think the best first step for you would be to try flashing the ROM and GAPPs package with a different recovery.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Navigate to the above link and download the latest zip (not md5) file to flash in your current recovery. Your current recovery will simply flash the zip file and overwrite your current recovery with PhilZ.
I personally can't see a GAPPs package causing that sort of issue, as it is not replacing code, changing libraries, or messing with the kernel. The GAPPs package is simply flashing system apps to the /system folder of the Android OS. Additionally, I use the PA GAPPs package when I flash CM11 nightlies.
A recovery can make all the difference of making sure that the correct files are being flashed to the correct areas and I, personally, find PhilZ to be the most bug-free and user-friendly.
When you boot into PhilZ, make sure you have all the files that you intend to flash on your device.
In PhilZ, the Wipe Data/Factory Reset option actually has an option to wipe the device to install a new ROM. Use that option
Install your ROM of choice and your GAPPs package. Reboot and see what happens.
Also, just had a passing thought: Did you flash a custom kernel? Did you not make a backup of your last working setup?
Click to expand...
Click to collapse
Thanks for your prompt and detailed reply! I did switch to Philz recovery after Odining to ND8, but I'll try again using the link you provided. Unfortunately I never made a backup, my mistake. I never explicitly tried a custom kernel, could my initial flash to MerkMod have changed the kernel?
riazrahman said:
Thanks for your prompt and detailed reply! I did switch to Philz recovery after Odining to ND8, but I'll try again using the link you provided. Unfortunately I never made a backup, my mistake. I never explicitly tried a custom kernel, could my initial flash to MerkMod have changed the kernel?
Click to expand...
Click to collapse
Sorry. After re-reading your post, I do see where you mentioned switching to PhilZ. However, please make sure that you have the latest version of PhilZ (which can be found at the link I previously provided).
After reading up on MerkMod, I have no reason to believe that ROM to be the cause of your issues. It is OMNI ROM-based and I have run OMNI ROM on my device without any issues. I, personally, use CM11 as my daily driver. But, as long as you are using the latest PhilZ recovery and flashing D2LTE ROMs to your device, there should be no issue. Also, make sure the GAPPs package you are using matches the Android version of the ROM you are flashing (e.g. 4.4.4 GAPPs --> 4.4.4 ROM)
If you download the .MD5 version of PhilZ, you can flash that via ODIN. Good luck to you.
Also, forgot to mention it in my previous post, but congratulations in advance on your engagement!
I don't think there's much to help here with. You said you odined to stock ND8 and still had the error. At that point, it definitely sounds hardware related and I would say that something is wrong with the device itself.
CNexus said:
I don't think there's much to help here with. You said you odined to stock ND8 and still had the error. At that point, it definitely sounds hardware related and I would say that something is wrong with the device itself.
Click to expand...
Click to collapse
Ah that's what I was afraid of :crying: I reflashed Philz and installed CM11 nightly with PA micro gapps 4.4.4 and am still getting the same issue. I did read a thread that mentioned something that Gummy ROM was the only one to work for someone in a similar situation, so I may try that. Then I think I'll try Odin to ND8 one more time just in case, and then just give up. I guess I can try to borrow a digital camera from a friend. I do still have a TEP plan with sprint so maybe they can replace the camera module at my local store without me having to pay the ridiculous $100 deductible.
One last thing, if this was kernel related, what's a good kernel for me to try?
Thank you both for your time and insight.
riazrahman said:
Ah that's what I was afraid of :crying: I reflashed Philz and installed CM11 nightly with PA micro gapps 4.4.4 and am still getting the same issue. I did read a thread that mentioned something that Gummy ROM was the only one to work for someone in a similar situation, so I may try that. Then I think I'll try Odin to ND8 one more time just in case, and then just give up. I guess I can try to borrow a digital camera from a friend. I do still have a TEP plan with sprint so maybe they can replace the camera module at my local store without me having to pay the ridiculous $100 deductible.
One last thing, if this was kernel related, what's a good kernel for me to try?
Thank you both for your time and insight.
Click to expand...
Click to collapse
Not likely that it's kernel related if the standard kernel with CM11 didn't work. You can always try the DKP kernel, which I use, found here in the Sprint S3 development forum.
Higgs_Boson said:
Not likely that it's kernel related if the standard kernel with CM11 didn't work. You can always try the DKP kernel, which I use, found here in the Sprint S3 development forum.
Click to expand...
Click to collapse
Ah understood, well I just tried GummyROM and Odined to ND8 again and still no dice, so I gave up on blaming the kernel. I just don't get it...if it's a hardware issue would both of my cameras go out? Shouldn't I still be able to access the front camera if theres a short or something in my rear camera? I feel like my phone just doesn't know theres cameras attached to it because I deleted something I shouldn't have while flashing the first time around.
One last question before I try the Sprint store tomorrow...while I was using Odin I saw the re-partition option. Now I know I shouldn't touch that unless I have a .pit file, so I left it unchecked this time. However, if I did track down a pit file, could repartitioning potentially solve this issue?
riazrahman said:
Ah understood, well I just tried GummyROM and Odined to ND8 again and still no dice, so I gave up on blaming the kernel. I just don't get it...if it's a hardware issue would both of my cameras go out? Shouldn't I still be able to access the front camera if theres a short or something in my rear camera? I feel like my phone just doesn't know theres cameras attached to it because I deleted something I shouldn't have while flashing the first time around.
One last question before I try the Sprint store tomorrow...while I was using Odin I saw the re-partition option. Now I know I shouldn't touch that unless I have a .pit file, so I left it unchecked this time. However, if I did track down a pit file, could repartitioning potentially solve this issue?
Click to expand...
Click to collapse
The only thing that repartitioning will do is restore the memory partitions in your phone in the event that one of the partitions became corrupted.
This is essentially what a PIT would be restoring:
Code:
sprint # cat parted.txt
cat parted.txt
Model: MMC MAG4FB (sd/mmc)
Disk /dev/block/mmcblk0: 30777344s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 8192s 131071s 122880s modem
2 131072s 131327s 256s sbl1
3 131328s 131839s 512s sbl2
4 131840s 132863s 1024s sbl3
5 132864s 136959s 4096s aboot
6 136960s 137983s 1024s rpm
7 137984s 158463s 20480s boot
8 158464s 159487s 1024s tz
9 159488s 160511s 1024s pad
10 160512s 180991s 20480s param
11 180992s 208895s 27904s ext4 efs
12 208896s 215039s 6144s modemst1
13 215040s 221183s 6144s modemst2
14 221184s 3293183s 3072000s ext4 system
15 3293184s 28958719s 25665536s ext4 userdata
16 28958720s 28975103s 16384s ext4 persist
17 28975104s 30695423s 1720320s ext4 cache
18 30695424s 30715903s 20480s recovery
19 30715904s 30736383s 20480s fota
20 30736384s 30748671s 12288s backup
21 30748672s 30754815s 6144s fsg
22 30754816s 30754831s 16s ssd
23 30754832s 30765071s 10240s grow
Info credit: http://androidforums.com/virgin-mob...ameleon-some-efs-imei-info-brick-backups.html
Hence, I have no reason to believe this would help you.
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.
Sorry if its a stupid question, I used to be on XDA all the time but now have babies and dont have the time anymore.
I am on 3.2.6 w/ root and xposed. How do I upgrade to 4.0.2?
First of all, let me tell you that you won't have Xposed on 4.0.2 as Xposed doesn't work on Nougat yet. And it'll probably take a while till the dev manages to port it. So if you *need* Xposed modules, stay on Marshmallow.
Secondly, there are a few options chose from in the process. I won't be writing a full guide with all possibilities as there are many written already. So, to make a quick one tailored for you, I have a few questions:
- are you OK with clean flashing (recommended) or do you want a simple upgrade?
- wanna stay on ext4 filesystem or switch to f2fs (recommended)?
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
First of all, let me tell you that you won't have Xposed on 4.0.2 as Xposed doesn't work on Nougat yet. And it'll probably take a while till the dev manages to port it. So if you *need* Xposed modules, stay on Marshmallow.
Secondly, there are a few options chose from in the process. I won't be writing a full guide with all possibilities as there are many written already. So, to make a quick one tailored for you, I have a few questions:
- are you OK with clean flashing (recommended) or do you want a simple upgrade?
- wanna stay on ext4 filesystem or switch to f2fs (recommended)?
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
i think i'm the same like him, i'm in ( 3.2.8 / without root ), and i want to upgrade to 4.0.2.
and i have no problem with the data (i have my backup),
and with the ( F2FS ) , i think it's the better one ... is that right ?
so what i do know ??
* and for Xposed do you have idea how long it will take ? .
khaahkd said:
so what i do know ??
* and for Xposed do you have idea how long it will take ? .
Click to expand...
Click to collapse
OK, so, to clean flash OOS 4 and convert to f2fs:
1. Download necessary files - ROM, TWRP (unofficial 3.0.4 or blu_spark v15), SuperSU (latest stable recommended)
2. Backup everything (files, app, make a nandroid) - the phone will be completely wiped in the process!
3. Connect to PC, flash new recovery
4. Reboot to recovery
5. Go to advanced wipe, format data to f2fs
6. Wipe all partitions
7. Reboot to recovery (probably not necessary, but can't hurt)
8. ADB push ROM and SuperSU to /sdcard
9. Navigate to install in TWRP, select ROM, wait for it to finish
ALTERNATIVE instead of 8+9: go to sideload mode in TWRP, ADB sideload ROM directly from PC
10. Flash SuperSU
11. Reboot to recovery (maybe also not necessary, but usually makes sure that stock ROMs doesn't overwrite recovery with its own)
12. Boot to system - that should be it!
13. Move files back to phone, restore backed up apps ...
If you want a custom kernel, flash it any time AFTER step 10!
About Xposed for Nougat, I've only heard from the dev that's he's working on it, but he's not close yet. He's doing this in his free time and can only afford to spend a few hours a week ... So I guess it'll be a few more months.
Happy flashing!
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
OK, so, to clean flash OOS 4 and convert to f2fs:
...........
Happy flashing!
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Thanks a lot man.
I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Does anyone know what the problem could be?
I would suggest you clean flash OOS first before going to Freedom.
I think RR is based on Lineage OS while Freedom is based on stock OOS.
Envoyé de mon iPhone en utilisant Tapatalk
Wrong forum.
danecr7 said:
I would suggest you clean flash OOS first before going to Freedom.
I think RR is based on Lineage OS while Freedom is based on stock OOS.
Envoyé de mon iPhone en utilisant Tapatalk
Click to expand...
Click to collapse
RR is based on CM. I'm just scared to flash OOS in case it goes wrong because stock OOS will overwrite TWRP with its stock recovery and then I'll be screwed because I'll have no way to restore from a backup if it goes wrong
RazorBlade123 said:
Wrong forum.
Click to expand...
Click to collapse
Yeah I thought it seemed a little out of place but I don't know where to post it? Is there a general questions forum?
evilkitty69 said:
RR is based on CM. I'm just scared to flash OOS in case it goes wrong because stock OOS will overwrite TWRP with its stock recovery and then I'll be screwed because I'll have no way to restore from a backup if it goes wrong
Click to expand...
Click to collapse
I don't think that there is a risk in flashing stock OOS. But if the custom recovery is overwritten then flash it back, your backup files are stored in your internal memory and unless you wipe it you are safe.
danecr7 said:
I don't think that there is a risk in flashing stock OOS. But if the custom recovery is overwritten then flash it back, your backup files are stored in your internal memory and unless you wipe it you are safe.
Click to expand...
Click to collapse
Even when I tried flashing other CM based ROMs, including ones I'd flashed before, it failed, only flashing RR actually worked. I don't know why this is the case but I'm not sure flashing OOS without knowing what the issue is, is the solution because if I lose TWRP there's no telling whether I'll be able to flash it back in fastboot if the phone isn't working properly
evilkitty69 said:
Even when I tried flashing other CM based ROMs, including ones I'd flashed before, it failed, only flashing RR actually worked. I don't know why this is the case but I'm not sure flashing OOS without knowing what the issue is, is the solution because if I lose TWRP there's no telling whether I'll be able to flash it back in fastboot if the phone isn't working properly
Click to expand...
Click to collapse
I once flashed RR based on android 7.1.1 and because I did not like it very much I wanted to go back to Freedom but at that time it was based on android 7.0.1 thus I was unable to boot. Maybe you are facing the same issue. But in my case I hardbricked my device and used the unbricking tool from OP3 forum.
If you download the latest OOS zip file you can flash it through TWRP and you won't lose you custom recovery.
danecr7 said:
I once flashed RR based on android 7.1.1 and because I did not like it very much I wanted to go back to Freedom but at that time it was based on android 7.0.1 thus I was unable to boot. Maybe you are facing the same issue. But in my case I hardbricked my device and used the unbricking tool from OP3 forum.
If you download the latest OOS zip file you can flash it through TWRP and you won't lose you custom recovery.
Click to expand...
Click to collapse
All of the ROMs I tried with were android 6.0.1, I'm avoiding touching android 7 because I'm not a fan
The strange thing is that in TWRP under "mount", system is unchecked and it won't stay checked when I reboot or try to flash something and then the flash fails. Strangely however, I can flash RR afresh and it will work but nothing else works
Therefore I don't think OOS would work either
Hey all. I recently factory reset my P2XL due to certain issues, so I'm back on stock, 8.1.
I'm going to root it again soon and all that jazz. If I plan on staying on stock everything (kernel, rom (when custom roms are developed), etc), is there a reason to install TWRP? I'd rather wait for an official TWRP to come out for TWRP backup purposes, but I can't really think of a reason to flash the beta for now.
I just boot the TWRP image whenever I need it. I haven't bothered to install it. No real reason to since I can't do backups with it anyway.
Kenneth196 said:
Hey all. I recently factory reset my P2XL due to certain issues, so I'm back on stock, 8.1. I'm going to root it again soon and all that jazz. If I plan on staying on stock everything (kernel, rom (when custom roms are developed), etc), is there a reason to install TWRP? I'd rather wait for an official TWRP to come out for TWRP backup purposes, but I can't really think of a reason to flash the beta for now.
Click to expand...
Click to collapse
No. You can always fastboot boot it if the need arises. Reboot and it's gone.
TWRP is official now :good:
https://dl.twrp.me/taimen/
Badger50 said:
TWRP is official now :good:
https://dl.twrp.me/taimen/
Click to expand...
Click to collapse
Have you flashed it yet? Did backups work on the 3.1.1 beta2 or just this new version?
equlizer said:
Have you flashed it yet? Did backups work on the 3.1.1 beta2 or just this new version?
Click to expand...
Click to collapse
Yep, it flashed just fine. Already flashed a couple of zips with it. Haven't tried backup/restore yet, but I'll get there :good: