Database Develop

TWRP AND ROOT FOR ANDROID NOUGAT (SINGLE SIM z3+ ROM)

Hi Guys,
Could someone help me with TWRP and for that matter root for FXP AOSP 7.0.
Thanks very much in advance
Cheers!!
Yawo

yawo76 said:
Hi Guys,
Could someone help me with TWRP and for that matter root for FXP AOSP 7.0.
Thanks very much in advance
Cheers!!
Yawo
Click to expand...
Click to collapse
Earlier I tried and it worked:
I tried flashing TWRP by Fastboot commands & Latest SU zip with TWRP.
But in AOSP Camera is pathetic and front cam is upside down, Quick Charge (Quick Charger) is not working. Have you checked it??

yawo76 said:
Hi Guys,
Could someone help me with TWRP and for that matter root for FXP AOSP 7.0.
Thanks very much in advance
Cheers!!
Yawo
Click to expand...
Click to collapse
Dont use FXP Roms on your device. They warn all users on their webpage that it is really dangerous and can damage your device permanently. At least it slows your devices at about 60%... " fry your emmc and brick your device (this is not a joke)"
http://fxpblog.co/warning/

[email protected] said:
Earlier I tried and it worked:
I tried flashing TWRP by Fastboot commands & Latest SU zip with TWRP.
But in AOSP Camera is pathetic and front cam is upside down, Quick Charge (Quick Charger) is not working. Have you checked it??
Click to expand...
Click to collapse
Thanks, I'm know it works because I was using it before moving to .305 when it was released. I wanted a working TWRP for AOSP Nougat 7.0
Thanks

saturday_night said:
Dont use FXP Roms on your device. They warn all users on their webpage that it is really dangerous and can damage your device permanently. At least it slows your devices at about 60%... " fry your emmc and brick your device (this is not a joke)"
http://fxpblog.co/warning/
Click to expand...
Click to collapse
I'm aware of that. It's the usual disclaimer. Besides I used it for about a month before updating to the new stock .305 firmware.
Thanks

yawo76 said:
I'm aware of that. It's the usual disclaimer. Besides I used it for about a month before updating to the new stock .305 firmware.
Thanks
Click to expand...
Click to collapse
I know exacly that this is not the usual disclaimer, these two bugs are real. I used fxp roms for about three months and the device is getting slower and slower until it dies complete.

saturday_night said:
I know exacly that this is not the usual disclaimer, these two bugs are real. I used fxp roms for about three months and the device is getting slower and slower until it dies complete.
Click to expand...
Click to collapse
Ok, thanks for the information. I'm currently on the .305 firmware so will stay on that.

Every Custom Kernel kills camera

Flashed 15 different times today, stock OOS 7.0. camera works fine on stock, even with magisk installed. As soon as I flash any custom kernel the camera app gets unknown error. Tried clearing cache, etc everything. Only stock kernel works. What gives?

You might want to read the kernel threads for help. Seems like if it was a kernel issue like you claim then someone else might have noticed it. Sounds like user error to me

954wrecker said:
You might want to read the kernel threads for help. Seems like if it was a kernel issue like you claim then someone else might have noticed it. Sounds like user error to me
Click to expand...
Click to collapse
Thanks brain.

Magisk is the reason for those errors, im using custom kernel since android 7.0 with system less superSU only, I already tried three different custom kernels here and they didn't gave me any camera errors

J4DedPrez said:
Thanks brain.
Click to expand...
Click to collapse
Wow, smartass answer for someone who can't flash a kernel without breaking the camera.
Actually, the answer is the solution you need, search and read.

exaflare said:
Magisk is the reason for those errors, im using custom kernel since android 7.0 with system less superSU only, I already tried three different custom kernels here and they didn't gave me any camera errors
Click to expand...
Click to collapse
Thank you friend, sometimes being nice and giving the simple solution is the simplest method.

Migdilu said:
Wow, smartass answer for someone who can't flash a kernel without breaking the camera.
Actually, the answer is the solution you need, search and read.
Click to expand...
Click to collapse
Typical XDA user... It's a real shame kids these days act the way they do

J4DedPrez said:
Typical XDA user... It's a real shame kids these days act the way they do
Click to expand...
Click to collapse
What it's a shame is that there are people who don't know how to read.

Magisk does work with custom kernels, but the order you flash them in is important. Magisk alters certain files in the /boot partition, which is also where the kernel is located. You should flash Magisk first over a clean ROM prior to flashing any custom kernels, or else you may run into issues. If an update for Magisk is pushed, you should also install it in the following order:
1) Dirty flash ROM (or stock kernel)
2) Flash Magisk
3) Flash custom kernel
I'm currently using Magisk v11.6 with Franco's r16 on OOS 4.1.0 without a problem.

Don't mean to be rude, but did you flash the compatible kernel; and not using adb sideload problems; on TWRP 3.0.4-1?
If you did, well then Magisk seems to be a problem for you.
And do post logs next time of you encounter a problem until and unless you are sure you everybody can reproduce that problem with the steps mentioned (which should be though)

If you're still in Android 7.0 (like me), do not use the latest custom kernel release, it will break your camera (Unknown Error). I think it's because the dev has rebased their kernel to the new Android 7.1.1.
Currently, I'm still on FredomOS 2.5 (OOS 4.0.3) and its combined with BluSpark v.72 (last release before the 7.1.1 rebase).
I don't want to use the latest OOS update since it's still full of annoying bugs.

In my opinion only people who understand what they are doing with this kind of stuff should get the oneplus 3 or 3t as it isn't very noob friendly and takes someone that is some what an advanced user or at least knows a little about flashing ROMs and kernels etc..... Or at least is willing to search around and read before they complain to everyone that they can't figure it out. If you want a phone that is simple and noob use friendly then go to Samsung or Apple. not oneplus as phone from this company are aimed at the intermediate up to power user that understands how to solve irregular problems. I've had none of these issues even when I was using my oneplus x. I use the unofficial RR with ex kernel and no problems with camera or anything and great battery life. Bottom line is (in my opinion anyways) oneplus phones are for the more technically savvy so if you aren't some one like that expect to run in to difficulties and have to do some deep research in certain cases. But this is a great community here at xda and we are all willing to help as much as we can but patience is a must.

Anova's Origin said:
Magisk does work with custom kernels, but the order you flash them in is important. Magisk alters certain files in the /boot partition, which is also where the kernel is located. You should flash Magisk first over a clean ROM prior to flashing any custom kernels, or else you may run into issues. If an update for Magisk is pushed, you should also install it in the following order:
1) Dirty flash ROM (or stock kernel)
2) Flash Magisk
3) Flash custom kernel
I'm currently using Magisk v11.6 with Franco's r16 on OOS 4.1.0 without a problem.
Click to expand...
Click to collapse
Same exact order as you, even flashed fresh ROM and kernel only. Can't explain it at all. For now, I'm on stock with no custom kernel but have magisk.

mrinmaydhar said:
Don't mean to be rude, but did you flash the compatible kernel; and not using adb sideload problems; on TWRP 3.0.4-1?
If you did, well then Magisk seems to be a problem for you.
And do post logs next time of you encounter a problem until and unless you are sure you everybody can reproduce that problem with the steps mentioned (which should be though)
Click to expand...
Click to collapse
No sideload, using most recent TWRP, and yes, I will have logs to post tomorrow. As a quick flasher I never really bother for the logs, but this time I'm getting down to the bottom of this. I'll have logs tomorrow

motherninja said:
If you're still in Android 7.0 (like me), do not use the latest custom kernel release, it will break your camera (Unknown Error). I think it's because the dev has rebased their kernel to the new Android 7.1.1.
Currently, I'm still on FredomOS 2.5 (OOS 4.0.3) and its combined with BluSpark v.72 (last release before the 7.1.1 rebase).
I don't want to use the latest OOS update since it's still full of annoying bugs.
Click to expand...
Click to collapse
This is exactly the issue. Thank you
se7ensde said:
In my opinion only people who understand what they are doing with this kind of stuff should get the oneplus 3 or 3t as it isn't very noob friendly and takes someone that is some what an advanced user or at least knows a little about flashing ROMs and kernels etc..... Or at least is willing to search around and read before they complain to everyone that they can't figure it out. If you want a phone that is simple and noob use friendly then go to Samsung or Apple. not oneplus as phone from this company are aimed at the intermediate up to power user that understands how to solve irregular problems. I've had none of these issues even when I was using my oneplus x. I use the unofficial RR with ex kernel and no problems with camera or anything and great battery life. Bottom line is (in my opinion anyways) oneplus phones are for the more technically savvy so if you aren't some one like that expect to run in to difficulties and have to do some deep research in certain cases. But this is a great community here at xda and we are all willing to help as much as we can but patience is a must.
Click to expand...
Click to collapse
:good:

Flashing kernels made for 7.1.1 on 7.0 FW.

954wrecker said:
You might want to read the kernel threads for help. Seems like if it was a kernel issue like you claim then someone else might have noticed it. Sounds like user error to me
Click to expand...
Click to collapse
Normal, helpful, response(don't be discouraged by some).
J4DedPrez said:
Thanks brain.
Click to expand...
Click to collapse
Douche response.
Migdilu said:
Wow, smartass answer for someone who can't flash a kernel without breaking the camera.
Actually, the answer is the solution you need, search and read.
Click to expand...
Click to collapse
Obvious observation.
J4DedPrez said:
Thank you friend, sometimes being nice and giving the simple solution is the simplest method.
Click to expand...
Click to collapse
Hypocrisy.

Hi all !
This discussion might be related with my issue explained here:
https://forum.xda-developers.com/oneplus-5/help/camera-flashlight-youtube-t3886260
but only thing is I never flashed custom kernels, issue appears after a official update !
Any opinion, ideas ?
Thanks

CM13 (Sultan rom ) vs lineage 14.1 (sultan rom) for battery OP3T ???

i ask about which is the best rom from both ? specifically for battery
my using is : facebook and whatsapp .

battery life:cm13>los 14.1
smooth:los 14.1>>>cm13

I used sultan cm13 last week without problems ..shifted to nougat & flashed sultan cm13 again. Everything works gr8 but when I share photos through WhatsApp the device restarts . Can anyone provide the firmware link (not the 1.4 GB)

Specifically for "Battery" ? Use stock ROM.

I installed both tried both, If you are looking for battery , more specifically screen on time, then go for official OS. Official Nougat 4.1.3 gives me 5-8 hours screen on time, depending on use. Sultan ROM lineage 14.1 sometimes heats up, battery backup seems 4-6 hours merely.

can anyone provide link for cm13 op3t ?

goutham raj said:
can anyone provide link for cm13 op3t ?
Click to expand...
Click to collapse
Just a search away
clickkk me

vignesh_may28 said:
I used sultan cm13 last week without problems ..shifted to nougat & flashed sultan cm13 again. Everything works gr8 but when I share photos through WhatsApp the device restarts . Can anyone provide the firmware link (not the 1.4 GB)
Click to expand...
Click to collapse
Can you explain how i can install it
Because i tried two times and always failed
Tried too installed first the firmware in the official post (cm13 post ) but failed again!

arefin_sajib said:
I installed both tried both, If you are looking for battery , more specifically screen on time, then go for official OS. Official Nougat 4.1.3 gives me 5-8 hours screen on time, depending on use. Sultan ROM lineage 14.1 sometimes heats up, battery backup seems 4-6 hours merely.
Click to expand...
Click to collapse
I tried the official Oos 4.1.3 about 1 month
The max SOT i got it was 5 hours

devlamania said:
Specifically for "Battery" ? Use stock ROM.
Click to expand...
Click to collapse
The last beta version was good ( 5.5 hours SOT )but some lags i had it
Waiting​the stable version ?

dlshad0 said:
Can you explain how i can install it
Because i tried two times and always failed
Tried too installed first the firmware in the official post (cm13 post ) but failed again!
Click to expand...
Click to collapse
Can you explain . what problem you faced ? Stuck at boot logo?

dlshad0 said:
I tried the official Oos 4.1.3 about 1 month
The max SOT i got it was 5 hours
Click to expand...
Click to collapse
Must be something you're doing wrong. I've got as high as 10 hours SOT, and definitely over 6 hours "all the time". I have literally stopped using custom roms in the long run since I experienced OOS. Yes I hop on to different roms to test, but so far nothing beats OOS in terms of battery life, smoothness and definitely no bugs.
About sultan rom, dude, I don't know when the hype will finally be laid to rest. I have no clue if the fanboys ever actually "'compared" it extensively. I've done extensive tests long time back with my OnePlus one, and all I found that it's just a plain old hype, made a big comment in boeffla kernel thread back in the OPO days and even Andi agrees to the hype. Haven't tested lately, so it will be unfair if I judge on how good or bad the ROM is for OP3T, but I sure know what to expect. Get down of the hype train, test for yourself in different usage patterns. SOT isn't everything of course. Your usage determines it.

vignesh_may28 said:
Can you explain . what problem you faced ? Stuck at boot logo?
Click to expand...
Click to collapse
I got failed in TWRP always :crying:

Flash firmware first then wipe cache,data,dalvik cache & then flash cm13 ROM.

vignesh_may28 said:
Flash firmware first then wipe cache,data,dalvik cache & then flash cm13 ROM.
Click to expand...
Click to collapse
if firmware give me failed in TWRP? continue to flash cm13 or not ?

Guys, battery is not everything, the thing is you get it be test by your self with your app install, finally Satisfy rom art.

[Closed] [Fix] [Custom Roms] [Santoni] Temporary Fix for Standby battery drain of cus

Thread closed due to maintain issue.
Use MIUI for better battery backup, your can use f2fs with Gabriel kernel in MIUI too.
Edit Feb 13, use these in build.prop, best for power saving at standby mode:
ro.ril.disable.power.collapse=0
pm.sleep_mode=1
Important notice:
If you have android assistant, close all background apps and check the CPU graph in the android assistant app. Wait for the cool down of CPUs. Then move your phone(like waving). You can see CPU starts at 2-3 sometimes 5 percent. In miui, I didn't have such CPU uses while moving my phone. I think this is also a cause of idle battery drain(sensors drain). Please all Devs, look at that problem even if you don't have that problem. Some users are facing this issue(or all?).
...
Hi. I've experienced serious battery drain on both Resurrection Remix, latest build of Nik001 and Luis Build with stock and custom kernel- Clarity. Many of us also experiencing this issue. It drains 5-7 percent per 7-8 hours to me. Using Greenify, Amplify caused me more battery drain! Now, I had found some fixes, but now problem appears like strangers. I don't know which fix solved my battery drain problem. Just test and you may find yours.
If you are having same problem like me, you can try and if doesn't work for you, I'm not responsible. Try these fix with no battery saving app(like greenify), and disabling the D2W. I've not tested with d2w enabled...
Method 1(settings restores automatically, I don't know why):
Doze Setting Editor thread-
[url]https://forum.xda-developers.com/android/apps-games/root-doze-settings-editor-android-t3235130[/URL]
Just set a profile from the app within and save...
Edit: Note: After a reboot, you have to set the settings again...
Method 2:
Go back to original kernel, just flash boot.img in TWRP extracting from the ROM. Don't forget to install Magisk again if you are using it.
Use Naptime for better doze improvement...
Playstore link
Method 3:
Flash other firmwares. First use the latest build, if battery drain continues in idle mode, flash previous builds, you can try stable ROMs firmwares.
Method 4:
Install other kernels(you can use Gabriel's). It seems much stable in standby mode, with some more features, tested. But same battery drain(though 1 percent less than previous .)
Kernel Thread
On Oreo, you can use LH Kernel or if you have issues, then use Anonymous 3.0(this is not available in XDA).
Method 5:
Clean cache of all apps through titanium backup. Avoid restoring app+data through titanium backup.
Method 6:
Flash other ROMs.
Others:
Copy these in build.prop. I don't know if they are needed. I took it from a website(thanks to him).
#Hardware_Power_Saving
ro.config.hw_power_saving=true
#Sensor_Sleep_Control
ro.ril.sensor.sleep.control=1

I have this issue too, so i go back to miui

Radnanum said:
I have this issue too, so i go back to miui
Click to expand...
Click to collapse
Very good.

Please can you post your best battery saving settings I don't understand this app

himfa71 said:
Please can you post your best battery saving settings I don't understand this app
Click to expand...
Click to collapse
The best ones are already there, check for the profiles in the app. Select any of it, and save. There are 3 profiles.

shohabmsk said:
The best ones are already there, check for the profiles in the app. Select any of it, and save. There are 3 profiles.
Click to expand...
Click to collapse
You know which one is best for battery?

himfa71 said:
You know which one is best for battery?
Click to expand...
Click to collapse
Sorry, no. I'm just using the first one. There's just little different in all of them.

Post updated, check again if it can help you again...
And Devs, please check the important notice section. It's really important...

Got this issue. I first tried pixel experience (Oreo) and the battery performance was terrible. Then RR (Oreo), same result. In airplane mode the drain was about 2%/hour.
I finally tried DotOs on Nougat base and work as aspected, with battery drain in idle near to 1%/night. The issue seems oreo-related but I don't understand why some device has it and other not.

camocamo said:
Got this issue. I first tried pixel experience (Oreo) and the battery performance was terrible. Then RR (Oreo), same result. In airplane mode the drain was about 2%/hour.
I finally tried DotOs on Nougat base and work as aspected, with battery drain in idle near to 1%/night. The issue seems oreo-related but I don't understand why some device has it and other not.
Click to expand...
Click to collapse
I've tried RR Oreo and AICP Oreo. Same bug to me. I noticed that CPU ramps up continuously after 5/7 seconds and it never stops. Developer doesn't listen to me or he knows the bug and ignores me. There's no solution I've found yet

it's kind of sad to see MIUI being so batterylife-friendly but not cunstomized roms

myjasson said:
it's kind of sad to see MIUI being so batterylife-friendly but not cunstomized roms
Click to expand...
Click to collapse
Yes. I miss xMIUI, the development is not forwarded. We should pray to have an Oreo MIUI for our device.

Battery drain for me is not that high on pixel experience all though it is still teribble compared to MIUI. I tried using clarity kernel + firmware 32 + Universal Doze in magisk. MIUI is good at battery but terrible at customization. Can anyone recommend another custom ROM that has almost stock battery performance?
Sent from my Redmi 4X using Tapatalk

Sygnomi said:
Battery drain for me is not that high on pixel experience all though it is still teribble compared to MIUI. I tried using clarity kernel + firmware 32 + Universal Doze in magisk. MIUI is good at battery but terrible at customization. Can anyone recommend another custom ROM that has almost stock battery performance?
Click to expand...
Click to collapse
I recommend Unofficial RR Nougat if you want most of customization and battery backup too. I got upto 9:30/45 hour max.
And change your firmware if you find battery backup is not good in any rom.

shohabmsk said:
I recommend Unofficial RR Nougat if you want most of customization and battery backup too. I got upto 9:30/45 hour max.
And change your firmware if you find battery backup is not good in any rom.
Click to expand...
Click to collapse
Just stock kernel? No modifications?
Sent from my Redmi 4X using Tapatalk
---------- Post added at 08:55 AM ---------- Previous post was at 08:53 AM ----------
shohabmsk said:
I recommend Unofficial RR Nougat if you want most of customization and battery backup too. I got upto 9:30/45 hour max.
And change your firmware if you find battery backup is not good in any rom.
Click to expand...
Click to collapse
What firmware do you use?
Sent from my Redmi 4X using Tapatalk

Sygnomi said:
Just stock kernel? No modifications?
Sent from my Redmi 4X using Tapatalk
---------- Post added at 08:55 AM ---------- Previous post was at 08:53 AM ----------
What firmware do you use?
Click to expand...
Click to collapse
While I was using RR, I used firmware 32_PA and 33.
Stock kernel was/is based on Clarity. But even without modifications, everything was fine to me.
Now I'm on MIUI, using firmware 35 with Gabriel kernel. So can't tell much about RR.

shohabmsk said:
While I was using RR, I used firmware 32_PA and 33.
Stock kernel was/is based on Clarity. But even without modifications, everything was fine to me.
Now I'm on MIUI, using firmware 35 with Gabriel kernel. So can't tell much about RR.
Click to expand...
Click to collapse
What version of MIUI are you on right now?

Sygnomi said:
What version of MIUI are you on right now?
Click to expand...
Click to collapse
9.5.4

Custom rom charging issue on the oxygen

hey...i use a mi max 2(oxygen)....i got into custom roms a few months back although now i am running stock miui....cus every rom i installed booted up but i wasnt able to charge my phone at all on aosp roms and miui roms ....only xiaomi.eu worked for me...can anyone help me??

What do you mean by chargjng issues? Explain in full detail. Do you mean battery? Did you swap out cables, adapters. Lots of aftermarket cables are rubbish. Is it original battery? is the charging connection dirty or defective? Does it need cleaning?

kaya.md said:
What do you mean by chargjng issues? Explain in full detail. Do you mean battery? Did you swap out cables, adapters. Lots of aftermarket cables are rubbish. Is it original battery? is the charging connection dirty or defective? Does it need cleaning?
Click to expand...
Click to collapse
The aosp rom versions cannot be charged unless they go back to twrp mode to charge them....

You have to follow all the instructions to install custom roms correct. If not you might have charging issues.

RayfG said:
You have to follow all the instructions to install custom roms correct. If not you might have charging issues.
Click to expand...
Click to collapse
I followed the instructions correctly and still got the error, for some reason ...

What kind of recovery do you usw? Twrp, orangefox ? And what Version?

RayfG said:
What kind of recovery do you usw? Twrp, orangefox ? And what Version?
Click to expand...
Click to collapse
That Orangefox R11.0 you

I needed 4 times with orangefox for a flawless and correct installation process..... Perhaps u have a similar problem.

RayfG said:
I needed 4 times with orangefox for a flawless and correct installation process..... Perhaps u have a similar problem.
Click to expand...
Click to collapse
Thank you, I will try....

MIUI 12 beast os repack 5 quick charging is working fine... Try this Rom

Arya Bhardwaj said:
MIUI 12 beast os repack 5 quick charging is working fine... Try this Rom
Click to expand...
Click to collapse
I would never use miui Roms. I am very content with havocos

I also had the same problem when installing rom with android versions from 8.0 to 10.0. Before that I used to install android 10 on my device and it works normally. But recently after from MIUI rom back to AOSP it was unable to charge unless I booted into recovery. Please someone please help us, I don't have a lot of money but I will reward you if your advice helps me. Thanks for reading here.[/B]

LKbyH4D3S said:
I also had the same problem when installing rom with android versions from 8.0 to 10.0. Before that I used to install android 10 on my device and it works normally. But recently after from MIUI rom back to AOSP it was unable to charge unless I booted into recovery. Please someone please help us, I don't have a lot of money but I will reward you if your advice helps me. Thanks for reading here.[/B]
Click to expand...
Click to collapse
Did you find a fix ?

Any possible fix or workaround (besides hanging on twrp) for this issue?