Hi, I open this thread because I wanted to kindly ask for advice on what the best bootstack to install Pie Roms like Resurrection Remix 7.0.2 or ViperOS 6.7 might be.
I have already used the A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX but, when I flash it, even with TWRP_3.2.3-0L_v1.3-Axon7-Labs_Mod and its Remove Message function, I cannot remove the Bootloader Unlock Warning and I cannot boot directly into recovery (either from the phone off with the combination of keys or through the advanced restart of the Roms) without pressing the VolumUp key 2 or 3 times on the Bootloader Unlock Warning screen.
It's not a particularly annoying thing but it led me to wonder if there was a better Bootstack (in the past I tried the Axon7_RR-O_B32-B10_TREBLE-Ready_Oki20180803_FULL_EDL by Oki and I liked his Customized Bootstack with the personalized boot image)
So I wanted to kindly ask if anyone is aware of a better or more stable or more updated Boostack than this (all 3 would be better :fingers-crossed.
I accept any advice and I thank in advance anyone who will know how to help me and the whole forum to keep this device still alive (a special thanks to Raystef66, Oki, NFound and DrakenFX for all the work and guides that have been very useful to me in recent days).
Hi,
When flashing full EDL from DrakenFX, did you put a generic splash.img in the specific "splash" folder located in EDL TOOL ? If I remember correctly, this could delete annoying warning message when booting.
Volumetrik said:
Hi,
When flashing full EDL from DrakenFX, did you put a generic splash.img in the specific "splash" folder located in EDL TOOL ? If I remember correctly, this could delete annoying warning message when booting.
Click to expand...
Click to collapse
I downloaded A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX.zip and flashed it with A2017G-O-B04-MODEM.zip from TWRP before flashing the rom.
Punisherk said:
I downloaded A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX.zip and flashed it with A2017G-O-B04-MODEM.zip from TWRP before flashing the rom.
Click to expand...
Click to collapse
OK, I made a mistake, full EDL is by Oki and not DrakenFX. This is in full EDL package the abitility to flash "splash.img".
This operation can be performed in EDL mode, that's what I meant in my previous post.
In the past, I tried your method (flashing by TWRP) , but I can't help since it didn't work for me.
Volumetrik said:
OK, I made a mistake, full EDL is by Oki and not DrakenFX. This is in full EDL package the abitility to flash "splash.img".
This operation can be performed in EDL mode, that's what I meant in my previous post.
In the past, I tried your method (flashing by TWRP) , but I can't help since it didn't work for me.
Click to expand...
Click to collapse
Thanks for the answer, I have already tried Oki's EDL in the past (Axon7_RR-O_B32-B10_TREBLE-Ready_Oki20180803_FULL_EDL) but, I experienced some problems flashing an alternative recovery to NFound's 3.2.1-7 present inside the package after the installation.
If I'm not mistaken then it seems to me that the DrakenFX boostack is more recent and updated (I'm not an expert, I only compared the modification and creation dates of the files and the original creation dates of the ZTE boostacks, modified and used by Oki , and LineageOS used by DrakenFX, and so it seemed to me ).
I will try again and see how it goes.
For the moment the combination of A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX with A2017G-O-B04-MODEM (especially this because the A2017G_OreoModem proposed by DrakenFX to be combined with his bootstack is more dated and, here in Italy, with the latest original modem published by ZTE, the reception in LTE with Fastweb is much better) and RR-P-v7.0.2-20200112-axon7-OFFICIAL works beautifully without bugs (or at least I haven't experienced it yet :fingers-crossed.
Can I kindly ask you if you know any other modified bootstack besides Oki's and DrakenFX's that are worth trying?
PS: I apologize if there are grammatical errors but my English is a bit rusty and I am helping myself with Google Translate to write these messages .
I didn't try another kernel/bootstack. However, many users talk about baddar kernel.
If you can try it (or another one) , I am very interested by your feedback [emoji39]
Volumetrik said:
I didn't try another kernel/bootstack. However, many users talk about baddar kernel.
If you can try it (or another one) , I am very interested by your feedback [emoji39]
Click to expand...
Click to collapse
If I remember correctly the Resurrection Remix 7.0.2, which I am currently using, it is based on the Baddar kernel RC1.2 (OrdenKrieger's work).
I am currently using it with great satisfaction and it works beautifully.
For the activities that I have done so far I have not encountered any bugs, the phone works fast and smooth and the battery lasts 90-100% longer than before (more than 2 days between a recharge, for a battery older than 2 years , it's miraculous).
Punisherk said:
Hi, I open this thread because I wanted to kindly ask for advice on what the best bootstack to install Pie Roms?
Click to expand...
Click to collapse
Saw your post and you reminded me about AEX 5.8 ROM by NFound. One of the versions had a great battery life, and there was bootstack transition recommended by NFound itself.
Not sure, but he suggest to use A2017U B12 Oreo beta bootstack instead of A2017U B35 Nougat on later versions. Why? I don't know.
Most of people will use Universal v2 by DrakenFX, some may stay on Verequies no splash (B20 US?)/NFound (B12 US?) bootstack/Oki.
Did anyone stayed with Nougat bootstack on Oreo/Pie and have an opinion about this mix?
Few minutes ago, I jumped to b12 bootstack, with TWRP 3.2.1-8 treble and no issues so far.
klałn said:
Saw your post and you reminded me about AEX 5.8 ROM by NFound. One of the versions had a great battery life, and there was bootstack transition recommended by NFound itself.
Not sure, but he suggest to use A2017U B12 Oreo beta bootstack instead of A2017U B35 Nougat on later versions. Why? I don't know.
Most of people will use Universal v2 by DrakenFX, some may stay on Verequies no splash (B20 US?)/NFound (B12 US?) bootstack/Oki.
Did anyone stayed with Nougat bootstack on Oreo/Pie and have an opinion about this mix?
Few minutes ago, I jumped to b12 bootstack, with TWRP 3.2.1-8 treble and no issues so far.
Click to expand...
Click to collapse
If I'm not mistaken, NFound's guide to installing AEX plans to Treblelize the phone by creating multiple partitions and formatting Data and Cache in f2fs file system instead of ext4.
I tried this solution about a year ago, following a guide, but the result, even after a couple of attempts, was not satisfactory in my case (long-term instability problems, sometimes abnormal battery consumption and not really working fluid).
At the end of the tests I had returned to the original system making myself lean towards waiting for new solutions.
I haven't tried AEX since, but I think I'll think about it since time and updates have gone by.
For Verequies, if I remember correctly, it should be included in one of the two EDL packages proposed in the Oki guide [GUIDE] [TREBLE] Axon 7 Custom OREO ROM installation for newbies - 2018.08.05.
I also tried this system but, for the results obtained, I preferred to use another solution.
Currently I have installed the RR 7.0.2 with the DrakenFX Universal Boostack, even if with another Modem compared to the one proposed by him for the A2017G (i.e. the A2017G-O-B04-MODEM of the original Oreo update of the ZTE because, here in Italy with Fastweb operator, it has better reception in LTE +).
Everything works beautifully, smoothly, without bugs or crashes (with formatting in ext4 because, in f2fs instead, crashes started already after 2 days without restarting the device) and the battery consumption is halved (two days between a charge and the other that, for a battery 2 years old and more, seems almost a miracle).
I also really like the enormous possibility of personalization that RR brings with it.
I will try to experiment an installation with the original Nougat boostack, as you suggested, to see the results and compare them.
For the TWRP to be used, do you suggest the NFound 3.2.1-8 or the TWRP_3.2.3-0L_v1.3-Axon7-Labs_Mod made in collaboration (personally I prefer the second one for the multi language besides other things)?
Punisherk said:
If I'm not mistaken, NFound's guide to installing AEX plans to Treblelize the phone by creating multiple partitions and formatting Data and Cache in f2fs file system instead of ext4.
I tried this solution about a year ago, following a guide, but the result, even after a couple of attempts, was not satisfactory in my case (long-term instability problems, sometimes abnormal battery consumption and not really working fluid).
At the end of the tests I had returned to the original system making myself lean towards waiting for new solutions.
I haven't tried AEX since, but I think I'll think about it since time and updates have gone by.
For Verequies, if I remember correctly, it should be included in one of the two EDL packages proposed in the Oki guide [GUIDE] [TREBLE] Axon 7 Custom OREO ROM installation for newbies - 2018.08.05.
I also tried this system but, for the results obtained, I preferred to use another solution.
Currently I have installed the RR 7.0.2 with the DrakenFX Universal Boostack, even if with another Modem compared to the one proposed by him for the A2017G (i.e. the A2017G-O-B04-MODEM of the original Oreo update of the ZTE because, here in Italy with Fastweb operator, it has better reception in LTE +).
Everything works beautifully, smoothly, without bugs or crashes (with formatting in ext4 because, in f2fs instead, crashes started already after 2 days without restarting the device) and the battery consumption is halved (two days between a charge and the other that, for a battery 2 years old and more, seems almost a miracle).
I also really like the enormous possibility of personalization that RR brings with it.
I will try to experiment an installation with the original Nougat boostack, as you suggested, to see the results and compare them.
For the TWRP to be used, do you suggest the NFound 3.2.1-8 or the TWRP_3.2.3-0L_v1.3-Axon7-Labs_Mod made in collaboration (personally I prefer the second one for the multi language besides other things)?
Click to expand...
Click to collapse
Have been on B12 Nougat bootstack and I don't recommend it.
- Offline charging worked when ROM was installed, without ROM, offline charging still worked but broke Oreo recovery.
- Fastboot worked - like above
- B04 modem worked
- Different BMS/battery behaviour on low health battery (72%) - SOT was same, no shutdowns on low battery, better battery percentage calculation.
(Could be placebo due to battery health and warmer weather)
- Colder phone on low tasks (placebo)
It isn't worth to stay on B12 bootstack.
Everything was fine, until played with him, then **** happened.
3.2.1-8, 3.2.3 with vendor support and 3.2.3 oki recovery doesn't work, if they are flashed on clean B12 - 3 blinks.
They only work, when flashed on DrakenFX bootstack and moving to B12 bootstack.
On first boot to recovery on DFX, they doesn't work, but on second boot they are working.
After flashing no splash message aboot on B12 it worked, until i tried fastboot - everything broke up, incl. system partitions.
Related
Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!
dude...I just got the N6P and ran CM13 within hours. This is what I did...
unlocked the bootloader
downloaded the lastest (MTC19X) image off of https://developers.google.com/android/nexus/images and unpacked it into the C:\Program Files (x86)\Android\android-sdk\platform-tools folder
ran the flash-all.bat
fastbooted TWRP
installed CM13. (didn't wipe internal storage)
installed arm64 open Gapps pico
BAM!!!
right now running stock kernel. it's cool. I'm PrivacyGuard-ing the hell out of all my apps (turned off START AT BOOT and KEEP AWAKE for almost every downloaded app), though, so battery is OK
also using Kernel Adiutor but underclocking values for the CPUs doesn't seem to stick
So it likely worked for you since you had flashed the newest vendor.img first. Apparently there are compatibility issues with certain features that cause them not to work (such as WiFi) if you're using an older one.
chaoticyeshua said:
Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!
Click to expand...
Click to collapse
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!
kaufikauf said:
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!
Click to expand...
Click to collapse
Very much so. I appreciate it!
Has anyone encountered the constant popup of the Select Sim Card message? I'm using project fi and I am still unable to find a solution to this issue.
Hi all,
I'd like to enable phone encryption on my Z00AD (running 6.0.1 .134) and I'm wondering how much that may affect performance and battery life.
Anyone already using it wanting to share their experience?
Thanks
I did on LL and upgraded to MM just fine. Also when I did a factory reset in MM I re-encrypted it, no problem.
Encryption/decryption is done by hardware (Intel CPU) so there is no performance/battery issue.
Thanks, good to know.
I was more worried about battery life than performance, but if either one is negligible I'm all set.
Done, worked like a charm [emoji106]
Encrypted in 5 minutes flat, no performance or battery hit that I can see, really a no brainer.
Performance and battery life is great with encryption as others have mentioned. However, I suspect they've changed something with the encryption from Lollipop to Marshmallow given I am unable to unlock the phone in TWRP, even on fresh installs (flashing raw Lollipop with Asus Flash Tool, making sure to delete all data/cache, sideloading Marshmallow, then setting things up). It also seems since I am not able to unlock the phone in TWRP, when I go to flash SU/Magisk/Xposed, it is only temporary (I think saved in dalvik). Made a thread about this, but it doesn't seem anyone else has used encryption + TWRP in Marshmallow yet, or hasn't bothered to reply (http://forum.xda-developers.com/zenfone2/help/twrp-invalid-password-mm-update-z00a-t3453228)
Doesn't the last TWRP 3.2.3 solve this issue
https://dl.twrp.me/Z00A/
Or have you find a working TWRP build that can decrypt?
fred_gaou said:
Doesn't the last TWRP 3.2.3 solve this issue
https://dl.twrp.me/Z00A/
Or have you find a working TWRP build that can decrypt?
Click to expand...
Click to collapse
Fred, it's a 2 years old thread, yes TWRP was fixed years ago for this
Hi all XDA's members and Meticulus's RR ROM contributors,
I would like to share my experience with Meticulus's RR ROM for Honor 5C.
First I tried Elite V6 with no success : bootloop, F2FS or EXT4 nothing to do ; the Elite V7 is available from Christmas but I see that there are bugs to fix for Hassan, so I gave up and restored a backup of my STOCK system.
The restore was not good as my camera and audio no longer worked...
Before I get back to the STOCK update NEM-L51C432B357, I decided to try Meticulus's RR. It was a very good idea as I now have a renamed Honor 5c to hi6250 (...) working with no bug up to now.
LTE OK, SMS OK, GPS OK, SDCARD OK, AUDIO OK, VIDEO OK, GAPPS OK, MTP OK, etc
Adaway OK, Afwall+ OK, Magisk v14 OK
+ Bonus : Evie Launcher working as it was not using with STOCK ROM (icon size issue) !
Many thanks to Meticulus and contributors for sharing this very good work.
---
To be more precise for Honor 5C owners :
DEVICE : HONOR 5C
ROM STOCK BUILD : NEM-L51C432B350
MODDED RECOVERY .. : TWRP-3.1.1-0-hi6250-v5.2.zip
ROM INSTALLED .... : RR-N-v5.8.5-20171214-hi6250-Meticulus.zip
GAPPS INSTALLED .. : open_gapps-arm64-7.1-pico-20171225.zip
---
Steps of my successful installation with SDCARD and no SIM CARD :
1- FASTBOOT the TWRP then reboot to the TWRP RECOVERY
2- Wipe all except external SDCARD
3- Install the ROM
4- Reboot to TWRP RECOVERY
5- Install the GAPPS
6- Reboot to system (RR)
7- During RR Android setup, when asked insert the SIM CARD.
It would perhaps also have been successful with the SIM CARD inserted from the beginning...
---
Questions/feature requests :
- On Resurrection Remix site, I have not found your great ROM why ?
- On XDA Dev, there is no thread "Resurrection Remix For The Honor 5C [METICULUS]" but a "[ROM][7.1.2] Resurrection Remix For The Honor 6x [METICULUS]" one, this is why I put my comments here and in the Elite thread for those like me unable to get Elite V6 or V7 working with their Honor 5C.
- One thing is really missing to me (not found in settings) : the scheduled start/stop that worked very well with the STOCK ROM.
Do you think that this useful feature could be added on a future version ?
- The double TAP for screen wake up, would be a great bonus feature (was not provided in the STOCK ROM).
- Not tested the OTG, I will tell it in this thread.
Thanks again.
---
Meticulus's replies :
1. It is unlikely that any device with a kirin processor will get "official support" for LineagOS and therefore Resurrection Remix. There just isn't enough source.
2. Just because there is no "Honor 5c" thread doesn't mean you should come here and confuse information. It makes the water muddy. There is nothing stopping you from creating a thread in the "Honor 5c General" and post your experienced there.
3. Scheduled device start and sleep is not something I will work on.
4. DoubleTap 2 Wake only works on some P9 Lite's. Other devices with different touchscreens simply do not have the hardware capability.
5. I'm glad you like the ROM but please re-post your experiences in the Honor 5c section. I intend to delete these posts...
Is working dual sim and volte
Is works dual sim and volte
Sim working fine??
What do you think solved the audio issue?
Reverting to Stock Rom backup could have helped somehow.
Renaming it maybe ? And how did you rename it? After installing this rom mine became hi6250.
I own a nmo-l31 and ever since installing EliteRom v7 i could not get the audio working. Installed EliteRom v6 , applied l-31 patch,nothing.
Trying to switch to stock rom with dload gave error
Directly flashing boot,system,cust,recovery from firmware packages didnt change anything on the userspace ,literally.My files,homescreen etc. remained the same and only recovery changed. I think i made a mistake there but who knows.
Now installed this ResurrectionRemix twrp and rom after seeing this thread.Audio still refuses to work .
thatwasmyfakeacc said:
What do you think solved the audio issue?
Click to expand...
Click to collapse
I had the same problem on my NEM-L51. The problem is (or at least i think it is), that the vendor partition is somehow corrupted.
Short explaination, the vendor partition holds some drivers which are not open source (therefore not in the android kernel) and also aren't shipped in the custom roms (because of copyright stuff). So you always need to have them, if the custom rom depends on them (and most/all of the honor 5c custom roms do so). That's also the reason why you always have to flash the custom rom over your emui5.x and if you screwed your whole system, you first need to flash a backup or get back to emui on a different way before you can flash a working custom rom again.
So that's the explaination part. I installed twrp on my device, took a complete backup, flashed aosp from meticulus, everything worked except of Audio/Videos. Flashed LineageOS from Hassan, everything worked except of audio/video playback. Flashed backup, everything worked except audio/video. WTF. I don't know why, but i believe that the backups made with TWRP were somehow not complete, because flashing all partitions (the backup was over all partitions, triple checked, made new backups from stock) didn't solve audio issues, not even on the stock backup. What I now did was getting back to stock with the dload method, and flashed again directly the lineageos from hassan, which then worked. I had a try before where i first accidentially flashed aosp again, and same problems occured again. Also the now stock backup again didn't work. That's why i think that the TWRP backups for Honor 5c NEM-L51 are somehow not right.
Tl;dr if you have audio/video playback issues, try to get back to stock (make sure those features work on your stock rom) and flash again. If it still doesn't work, custom rom is maybe not compatible with nem-l51 (only experienced that with meticulus roms, hassans work great).
thatwasmyfakeacc said:
I own a nmo-l31 and ever since installing EliteRom v7 i could not get the audio working. Installed EliteRom v6 , applied l-31 patch,nothing.
Trying to switch to stock rom with dload gave error
Directly flashing boot,system,cust,recovery from firmware packages didnt change anything on the userspace ,literally.My files,homescreen etc. remained the same and only recovery changed. I think i made a mistake there but who knows.
Click to expand...
Click to collapse
Try again with the dload method, maybe use another UPDATE.zip. I had to try it several times, device booted sometimes for ever, and suddenly it worked. No idea why, but maybe try it again.
Custom Roms is good but overal it lacks supports for long terms and quality of pictures taken are not as nice as stock ones
stevedat said:
Custom Roms is good but overal it lacks supports for long terms and quality of pictures taken are not as nice as stock ones
Click to expand...
Click to collapse
also system collect trash files that slows you down. i used to be all in for custom roms but now i dont use them because they will break in time and standby batterydrain will increase rapidly.
thelous said:
also system collect trash files that slows you down. i used to be all in for custom roms but now i dont use them because they will break in time and standby batterydrain will increase rapidly.
Click to expand...
Click to collapse
Rite, it's just for fun.
shankarjdhv125 said:
Is works dual sim and volte
Click to expand...
Click to collapse
Hi,
Dual SIM not tested, Volte I don't know if it works using my ISP (free.fr) and don't know how to check this.
An advice, don't update Magisk, I have done it on several rr (honor 5c, idol3 5.5), the result was bootloop.
I just moved from Pure Nexus 7.1 to SuperXE 8.1. I think I forgot to flash vendor image but otherwise did full clean flash. ROM boots but when trying to connect to WiFi there is voice input but no keyboard. Haven't ever seen something like this before... Added vendor image and redid full/clean flash multiple times with same result. Unfortunately, activity on that ROM thread is a bit slow and I'm down without my phone so decided to ask for help here.
Adding $20 bounty for help fixing. Serious withdrawal mode without my phone. I have a backup phone but it is nearly unusable...
Solution here https://forum.xda-developers.com/showpost.php?p=76126862&postcount=263
Since you are coming from Nougat to Oreo i would suggest you first flash the full oreo factory image before flashing the oreo custom rom. Its not usually a must but solves a lot of minor problems
Hi everyone,
To flash the last rom (nightly ) of LineageOS ( in Oreo,from the 2 february), i had to put the firmware 5.1.7. After flash this firmware i was able to flash the ROM but it makes my phone extremely slow and with screen issues (i can still use the tactile but the screen doesnt follow).
I restored but the problem stills then i put le last stable ROM from Oneplus on android pie (9.0.3). It is a bit better (still really slow) and after a moment i get now like a white noise (same as on TV but with color moreover) by wink ( was more and more often on Google Maps), I had to reboot cause i couldnt use more my phone.
Thanks you in advance !
Ps : I've got TWRP from siankatabg and i'm not rooted , if you want me to send log tell me how pls.
Up :good:
When you were flashing did you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Flash codework's TWRP for Pie. After that reboot into recovery, wipe everything down and use clean flash instructions for your OTA. It should be able to fix any issue you were having. If not let me know.
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Raidenne said:
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Click to expand...
Click to collapse
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Ebeninyo said:
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Click to expand...
Click to collapse
My issues seem gone since few weeks with the last OTA (it very rarely happens now). I don't know what caused that even if i use my backup.
Thanks for your support !