Good day!
I'm one of those ZF5 owners who won their bootloader-"defective" phones out of the ASS-US Trash Lottery. Due to this problem, we are faced with an issue that keeps us from unlocking our bootloaders and enjoying the life that most of you enjoy --- the life of having a non-stock ROM.
I approach you all with a hopeless heart. Is there any available custom ROM out there that will boot with stock ASS-US kernels? I've tried some, but they all had issues:
AOSP 5.0.2 by tank0412
No support for dual-SIM functionality (I need both SIMs).
Vibrator not working (It's not what you think), though not necessarily a problem.
PZ-SleekStock ROM v4 by PaletroxZ
Without its default Borets kernel (custom), it's basically just stock ROM with a custom boot animation.
Any info is appreciated. (Better yet, if a fix for freezing bootloaders comes out, please tell me as well!)
What i did was,
I flashed jelly bean raw fw,then unlocked the bootloader using the official unlocking app from asus's site, unlocked the bootloader,then i flashed lollipop raw fw (surprisingly the bootloader remained unlocked)as soon as everything flashed, i didn't booted to rom,instead rebooted to bootloader directly,flashed twrp 3.0 M4 and flashed my CleanStock ROM, now there's no freezing issue at all till now,its been a week no freezes...
My device is a501cg with 2gb ram and 8gb rom,1.6ghz processor...
prathmesh pande said:
What i did was,
I flashed jelly bean raw fw,then unlocked the bootloader using the official unlocking app from asus's site, unlocked the bootloader,then i flashed lollipop raw fw (surprisingly the bootloader remained unlocked)as soon as everything flashed, i didn't booted to rom,instead rebooted to bootloader directly,flashed twrp 3.0 M4 and flashed my CleanStock ROM, now there's no freezing issue at all till now,its been a week no freezes...
My device is a501cg with 2gb ram and 8gb rom,1.6ghz processor...
Click to expand...
Click to collapse
Can you confirm that you have been experiencing the freezing issues in the past?
Also, I believe that flashing stock firmware does not re-lock your bootloader (As implied by the issues of many problematic ZF5 users who tried to flash stock firmware but still had freezing issues.)
cnswico said:
Can you confirm that you have been experiencing the freezing issues in the past?
Also, I believe that flashing stock firmware does not re-lock your bootloader (As implied by the issues of many problematic ZF5 users who tried to flash stock firmware but still had freezing issues.)
Click to expand...
Click to collapse
Yes, i was facing a lottttt of freezing in the past, it was like minimum 4-5 times freezing per day...
(Also i faced random reboots during call mostly because double tap 2 wake i.e. zenmotion was enabled so i don't use it anymore....without dt2w enabled,no random reboots at all)
After doing the entire process mentioned in the previous post, till now no freezes...
prathmesh pande said:
Yes, i was facing a lottttt of freezing in the past, it was like minimum 4-5 times freezing per day...
(Also i faced random reboots during call mostly because double tap 2 wake i.e. zenmotion was enabled so i don't use it anymore....without dt2w enabled,no random reboots at all)
After doing the entire process mentioned in the previous post, till now no freezes...
Click to expand...
Click to collapse
You already tought posting your process into a new thread? It may fix everybody's or some of them bootloader's problem
Sent from my ZenFone 5 (A500CG) using XDA Labs
MarconiGRF said:
You already tought posting your process into a new thread? It may fix everybody's or some of them bootloader's problem
Sent from my ZenFone 5 (A500CG) using XDA Labs
Click to expand...
Click to collapse
I will tag my post to my ROM's thread ,hope so it will help
prathmesh pande said:
Yes, i was facing a lottttt of freezing in the past, it was like minimum 4-5 times freezing per day...
(Also i faced random reboots during call mostly because double tap 2 wake i.e. zenmotion was enabled so i don't use it anymore....without dt2w enabled,no random reboots at all)
After doing the entire process mentioned in the previous post, till now no freezes...
Click to expand...
Click to collapse
I tried what you said. 5 minutes in. BANG! My phone froze again.
I rebooted my phone, lasted less than a minute. Freeze, once again. Thanks for trying, anyway. My phone is hopeless.
cnswico said:
I tried what you said. 5 minutes in. BANG! My phone froze again.
I rebooted my phone, lasted less than a minute. Freeze, once again. Thanks for trying, anyway. My phone is hopeless.
Click to expand...
Click to collapse
With which android version ur device was originally shipped when u purchased it?
prathmesh pande said:
With which android version ur device was originally shipped when u purchased it?
Click to expand...
Click to collapse
1.17. Version which headed the official bootloader unlocker.
Related
Finally Motorola released the OTA update for Moto g 3rd gen with 3 different improvements .The size of OTA is 177.4 Mb.
1.Stagefright Fix
2.Add Night Mode to Camera
3.Bug fixes and Stability Improvements
Source:http://www.gammerson.com/2015/09/moto-g-3rd-gen-ota-update-fix-download.html
so this update will fix the overheating issue and battery drain issue?
gonzodesigns said:
so this update will fix the overheating issue and battery drain issue?
Click to expand...
Click to collapse
What issues are those? I've seen very few reports of those types of issues with the 3rd gen. Obviously, those things happens to a small portion of users on almost every Android phone.
screen on time is decent, but could be better. I'd love to find a permissive kernel I could tweak...anyone up for it??
Im still running the release version firmware. Had night mode since release so i wonder apart from stagefright what the UK release will bring?
Does anyone have this as a flashable zip yet?
Sent from my MotoG3 using xda premium
bozzykid said:
What issues are those? I've seen very few reports of those types of issues with the 3rd gen. Obviously, those things happens to a small portion of users on almost every Android phone.
Click to expand...
Click to collapse
my personal experience with an 8gb model was a hot skillet in just 3 minutes on wifi or lte network plus doing some search i found a lot of users reporting the same issue so its not a very small percent it is a known issue maybe some users dont report it or dont care about it but it really gets hot. maybe some batchs maybe the 8gb model who knows!
every phone have small issues some related to hardware some related to software thats why i asked if the upgrade fix this one
but a phone that turns in to a hot skillet its not safe to use.
Update notes
gonzodesigns said:
so this update will fix the overheating issue and battery drain issue?
Click to expand...
Click to collapse
Umm... What overheating and battery drain issues . My Moto G3 is definitely the coolest running phone is ever owned, and battery life is very good to excellent.
Sounds to me like you have other issues going on.
Sent from my MotoG3 using Tapatalk
Not showing up on my US retail version yet.
Himalaya saxena said:
Finally Motorola released the OTA update for Moto g 3rd gen with 3 different improvements .The size of OTA is 177.4 Mb.
1.Stagefright Fix
2.Add Night Mode to Camera
3.Bug fixes and Stability Improvements
Source:http://www.gammerson.com/2015/09/moto-g-3rd-gen-ota-update-fix-download.html
Click to expand...
Click to collapse
This OTA does not load itself if you have a custom recovery. To avail of this OTA the phone should have the STOCK recovery.
Unlocked bootloader does not matter, but being on STOCK recovery is must for the update to recognize the fingerprint and load the OTA.
After changing the custom recovery to STOCK recovery, phone is stuck at blank screen after the OTA update. Trying to figure out what to do.
Any suggestions?
arunhebbare said:
This OTA does not load itself if you have a custom recovery. To avail of this OTA the phone should have the STOCK recovery.
Unlocked bootloader does not matter, but being on STOCK recovery is must for the update to recognize the fingerprint and load the OTA.
After changing the custom recovery to STOCK recovery, phone is stuck at blank screen after the OTA update. Trying to figure out what to do.
Any suggestions?
Click to expand...
Click to collapse
anyone help i facing the same issue
asrupesh said:
anyone help i facing the same issue
Click to expand...
Click to collapse
I am surprised to notice that after the update the system has vanished and the booting process stops on a blank screen (with screen lit dimly).
No worry. Here is the solution. Flash STOCK firmware....
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Here is the link for the procedure
http://www.gammerson.com/2015/08/how-to-flash-stock-firmware-of-Moto-g-3rd-gen.html
Can some one capture the OTA and make a custom rom flashable file?
Currently my phone is bricked. Will update later.
arunhebbare said:
I am surprised to notice that after the update the system has vanished and the booting process stops on a blank screen (with screen lit dimly).
No worry. Here is the solution. Flash STOCK firmware....
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Here is the link for the procedure
http://www.gammerson.com/2015/08/how-to-flash-stock-firmware-of-Moto-g-3rd-gen.html
Can some one capture the OTA and make a custom rom flashable file?
Currently my phone is bricked. Will update later.
Click to expand...
Click to collapse
I found the solution just clean flash stock rom without root or any modifiction.
Then update, It works perfectly without any problem... I updated by following this method......
asrupesh said:
I found the solution just clean flash stock rom without root or any modifiction.
Then update, It works perfectly without any problem... I updated by following this method......
Click to expand...
Click to collapse
Can u give stock rom link
samarjatt said:
Can u give stock rom link
Click to expand...
Click to collapse
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
asrupesh said:
I found the solution just clean flash stock rom without root or any modifiction.
Then update, It works perfectly without any problem... I updated by following this method......
Click to expand...
Click to collapse
Hi, thank you.
Which stock rom did you use from the link? There are two there for the xt1550. I guess the one with the 23.72-47_cid7(Newer Build) is the one?
If you could elaborate what you did it would help others.
arunhebbare said:
Hi, thank you.
Which stock rom did you use from the link? There are two there for the xt1550. I guess the one with the 23.72-47_cid7(Newer Build) is the one?
If you could elaborate what you did it would help others.
Click to expand...
Click to collapse
No i used Older version 23.72-33... I didnt get update notification in newer 23.72-47 update...
aion11 said:
Not showing up on my US retail version yet.
Click to expand...
Click to collapse
US carriers seem to be much slower pushing out updates. Since they mostly use foreign support it makes little sense. I work for the same company as my carrier, but different division and word I have is they aren't pushing out the update for this phone because the phone isn't in their list of devices yet. BTW, I'd be curious if anyone actually knows someone that got the stagefright bug. You have as big a chance to get struck by lightning as you are in getting stagefright. Anything with Kit Kat or later makes it almost impossible for stagefright to replicate on their phone.
Tel864 said:
US carriers seem to be much slower pushing out updates.
Click to expand...
Click to collapse
The Moto G 3rd gen is sold in the US fully unlocked with no carrier branding. So the carriers don't push out the updates. Motorola generally pushes their updates to India first but the US usually comes soon after.
Hi,
I was rooting my Moto G4 XT1625 US retail version (non-Amazon version) but getting stuck at boot. So, I said, what the heck, I went on to flash CM13 on it. That works but I found battery life to be worse, and so I would like to try to go back to stock (with root of course).
However, I'm having trouble figuring out which is the correct stock ROM from file factory. I'm not sure what is the naming convention, and there doesn't seem to be any easy way to search on file factory. Currently, there are 26 pages with a total of 774 ROMs there.
Thanks.
Hello, in case you haven't resolved your problem yet here is what I did to return my phone to stock. I have the same model, XT1625 (not Amazon). Download this file http://www.filefactory.com/file/28u...PJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml.zip
Follow these instructions: http://www.stechguide.com/download-stock-firmware-of-moto-g4-and-g4-plus/
good luck
romuloxiii said:
Hello, in case you haven't resolved your problem yet here is what I did to return my phone to stock. I have the same model, XT1625 (not Amazon). Download this file http://www.filefactory.com/file/28u...PJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml.zip
Follow these instructions: http://www.stechguide.com/download-stock-firmware-of-moto-g4-and-g4-plus/
good luck
Click to expand...
Click to collapse
Thank you very much. I managed to restore to stock from a Nandroid backup, but I will download this and keep it as a backup in case I need it in the future.
Still, I wonder about the naming convention of the files. It will make searching in the future a lot easier if we know how they are named.
Out of curiosity, does anyone know if you can flash the normal xt1625 retail rom on a boot loader unlocked Amazon xt1625?
MadGoat said:
Out of curiosity, does anyone know if you can flash the normal xt1625 retail rom on a boot loader unlocked Amazon xt1625?
Click to expand...
Click to collapse
I did flash an older retail room and it worked but when I tried a later rom it bricked the phone. I had to send it in and Motorola reflashed it with the latest retail rom.
Tel864 said:
I did flash an older retail room and it worked but when I tried a later rom it bricked the phone. I had to send it in and Motorola reflashed it with the latest retail rom.
Click to expand...
Click to collapse
They did this under warranty?
pastorbob62 said:
They did this under warranty?
Click to expand...
Click to collapse
Yes they did. It was free overnight shipping both ways....I shipped it out with the prepaid label on Sunday and had it back Thursday morning.
Tel864 said:
Yes they did. It was free overnight shipping both ways....I shipped it out with the prepaid label on Sunday and had it back Thursday morning.
Click to expand...
Click to collapse
Wow! That is awesome. I always thought if you unlocked it the warranty was void.
pastorbob62 said:
Wow! That is awesome. I always thought if you unlocked it the warranty was void.
Click to expand...
Click to collapse
It was never unlocked, I missed the window and waited too late to get my unlock code. My wife needed a phone so I gave her this phone and picked up another non amazon G4 for myself. At least it now has a non-Amazon rom on it and is on the retus update channel instead of AMZ. Maybe I got lucky and they flashed the wrong rom on it but I'm not complaining.
Does anyone have link to stock firmware of XT1625 Amazon Ad variant?
I unlocked the bootloader and tried all the techniques on this forum to remove ads. All methods failed with "Unauthorized software installed" message at boot.
The only method worked was installing APK and running it.
I tried downloading and flashing ATHENE_AMZ_MPJ24.139-64_65_cid50_amz from Motorola website but it does not have motoboot.img as mentioned in the steps.
I would like to re-lock the bootloader but need a stock firmware to do that. Could someone please provide it?
does anyone have this file posted someone else so i don't have to wait 5 hours for it to download. not paying for this.
Quick question for those that have flashed NPJ25.93-14, did they fix the issues with it? Play store downloads? Battery drain? Ghost touches? Camera problems? Music playback? And notifications sound?... It's the only reason I've not flashed the aforementioned ROM... I'm curious.
These were problems first reported when the ROM was released in December. Thanks.
jman_131 said:
Quick question for those that have flashed NPJ25.93-14, did they fix the issues with it? Play store downloads? Battery drain? Ghost touches? Camera problems? Music playback? And notifications sound?... It's the only reason I've not flashed the aforementioned ROM... I'm curious.
These were problems first reported when the ROM was released in December. Thanks.
Click to expand...
Click to collapse
The following bugs are known to be fixed -
2G mode in Mobile Networks (Wasn't there after Marshmallow)
Notification Volume (Was low after Marshmallow)
UI Lags (Animations weren't very smooth after last month's Nougat update)
Bluetooth Connection Time (Used to take much longer in the previous build)
http://www.androguider.com/2017/01/moto-g4g4-plus-receives-yet-another.html?m=1
Danny1976 said:
The following bugs are known to be fixed -
2G mode in Mobile Networks (Wasn't there after Marshmallow)
Notification Volume (Was low after Marshmallow)
UI Lags (Animations weren't very smooth after last month's Nougat update)
Bluetooth Connection Time (Used to take much longer in the previous build)
http://www.androguider.com/2017/01/moto-g4g4-plus-receives-yet-another.html?m=1
Click to expand...
Click to collapse
In that case I will continue to wait before I upgrade. I have Nougat on my Moto G3, and I like it, but the battery issues(both charging/discharging) are no es bueno. Some people have reported that rebooting into safe mode multiple times, helps with certain issues. YMMV.
Is safe flash 3.5.7 firmware to avoid random reboots on custom ROM?
I'm not having issues with IMEI or signal drops, but I'm having random reboots.
I read few people flashed it and random reboots have gone.
Someone who flashed 3.5.7 firmware can share if it works or not?
Thanks in advance
Enviado desde mi ONE A2003 mediante Tapatalk
Santi_SAZ said:
Is safe flash 3.5.7 firmware to avoid random reboots on custom ROM?
I'm not having issues with IMEI or signal drops, but I'm having random reboots.
I read few people flashed it and random reboots have gone.
Someone who flashed 3.5.7 firmware can share if it works or not?
Thanks in advance
Enviado desde mi ONE A2003 mediante Tapatalk
Click to expand...
Click to collapse
Do you care about voLTE ? If not, you could go back to 3.0.x - 3.1 firmware: I flashed too the newest firmware and experienced random reboots. I reflashed 3.1 stock ROM (so with 3.1 firmware) and now all is good.
casual_kikoo said:
Do you care about voLTE ? If not, you could go back to 3.0.x - 3.1 firmware: I flashed too the newest firmware and experienced random reboots. I reflashed 3.1 stock ROM (so with 3.1 firmware) and now all is good.
Click to expand...
Click to collapse
Flashing 3.5.6 firmware gave me random reboots. 3.5.7 firmware not. 3.0.x and 3.1.x work also fine.
Use the firmware files from @Spannaa
https://www.androidfilehost.com/?w=files&flid=53150
I don't care about VoLTE, but I think better new firmware always
I guess it is so simply flashing the firmware that you want
Enviado desde mi ONE A2003 mediante Tapatalk
Santi_SAZ said:
I don't care about VoLTE, but I think better new firmware always
I guess it is so simply flashing the firmware that you want
Enviado desde mi ONE A2003 mediante Tapatalk
Click to expand...
Click to collapse
So go ahead and flash it . But be sure to have EFS and important partitions backuped !
BeHappyToo said:
Flashing 3.5.6 firmware gave me random reboots. 3.5.7 firmware not. 3.0.x and 3.1.x work also fine.
Use the firmware files from @Spannaa
https://www.androidfilehost.com/?w=files&flid=53150
Click to expand...
Click to collapse
Do you know if flashing 3.0.x or 3.1.x fixes random shut offs, not just reboots? As in, my phone will sometimes randomly not want to wake from sleep and I'm forced to force reboot. Happens at least once a day, and I wouldn't classify this as a random reboot since it doesn't reboot by itself.
Latiken said:
Do you know if flashing 3.0.x or 3.1.x fixes random shut offs, not just reboots? As in, my phone will sometimes randomly not want to wake from sleep and I'm forced to force reboot. Happens at least once a day, and I wouldn't classify this as a random reboot since it doesn't reboot by itself.
Click to expand...
Click to collapse
Black screen of death does nothing to do with firmware, it happened to me from time to time on 3.1.x firmware as well. It's usually a ROM thing.
i had a lot of reboots with the newer firmware.now back on 3.1.1 en its al gone.rom that i use is tesla.
Sent from my ONE A2003 using XDA-Developers Legacy app
NeoVsk said:
Black screen of death does nothing to do with firmware, it happened to me from time to time on 3.1.x firmware as well. It's usually a ROM thing.
Click to expand...
Click to collapse
Oh, is that what people refer to it as?
I've gotten it on pretty much every ROM I've tried, and I have a feeling it's a problem with Doze, since it seemed to happen much much more often when I use Greenify.
Latiken said:
Oh, is that what people refer to it as?
I've gotten it on pretty much every ROM I've tried, and I have a feeling it's a problem with Doze, since it seemed to happen much much more often when I use Greenify.
Click to expand...
Click to collapse
I don't use Greenify and I have Ambient Display deactivated so you're might be onto something. Did you try to connect the phone to your computer and collect logs when it's dead?
NeoVsk said:
I don't use Greenify and I have Ambient Display deactivated so you're might be onto something. Did you try to connect the phone to your computer and collect logs when it's dead?
Click to expand...
Click to collapse
I haven't tried, but I most certainly can. How would I go about doing that?
I also have reason to believe that it could also be a memory leak of some sort, or the battery begins to fail, as usually when I'm forced to reboot it I lose anywhere from 5-30% of battery life.
Latiken said:
I haven't tried, but I most certainly can. How would I go about doing that?
I also have reason to believe that it could also be a memory leak of some sort, or the battery begins to fail, as usually when I'm forced to reboot it I lose anywhere from 5-30% of battery life.
Click to expand...
Click to collapse
Just check this thread: https://forum.xda-developers.com/oneplus-2/general/logs-t3533826
If your battery drains it seems like your phone got stuck in some sort of loop that kept your CPU/sensors/whatever fully loaded.
NeoVsk said:
Just check this thread: https://forum.xda-developers.com/oneplus-2/general/logs-t3533826
If your battery drains it seems like your phone got stuck in some sort of loop that kept your CPU/sensors/whatever fully loaded.
Click to expand...
Click to collapse
Alright cool, I will try and get these logs if I notice my phone do it while I have access to my computer. I have a feeling it won't detect the phone though, since my phone doesn't charge while in this state.
NeoVsk said:
Just check this thread: https://forum.xda-developers.com/oneplus-2/general/logs-t3533826
If your battery drains it seems like your phone got stuck in some sort of loop that kept your CPU/sensors/whatever fully loaded.
Click to expand...
Click to collapse
So my device did the black screen thing again. I plugged it into my computer to see if it would be recognized. It pops up us "QUSB_BULK" which a quick Google search seems to indicate that the device is bricked; however, this is obviously not the case.
Any ideas?
i had IMEI 2 - 0 issue on 3.5.6 and not any issues with random reboot or signal drop, after update 3.5.7 IMEI has been fixed and no problems at all
Is that an OTA for 3.5.6 to 3.5.7?
Is that an OTA for 3.5.6 to 3.5.7? I dirty flashed the 41mb 3.5.7 firmware zip file through TWRP, nothing happened, thankfully didn't brick the phone either!
BeHappyToo said:
Flashing 3.5.6 firmware gave me random reboots. 3.5.7 firmware not. 3.0.x and 3.1.x work also fine.
Use the firmware files from @Spannaa
https://www.androidfilehost.com/?w=files&flid=53150
Click to expand...
Click to collapse
subhash8765 said:
Is that an OTA for 3.5.6 to 3.5.7? I dirty flashed the 41mb 3.5.7 firmware zip file through TWRP, nothing happened, thankfully didn't brick the phone either!
Click to expand...
Click to collapse
No, not an OTA. I have dirty flashed serveral different firmware versions. No problems with installing them.
The firmware version on the phone doesn't change?
The firmware version on the phone settings wouldn't change? It's still 3.5.6 , not sure if that flash was successful, it did take a while to boot up though
BeHappyToo said:
No, not an OTA. I have dirty flashed serveral different firmware versions. No problems with installing them.
Click to expand...
Click to collapse
subhash8765 said:
The firmware version on the phone settings wouldn't change? It's still 3.5.6 , not sure if that flash was successful, it did take a while to boot up though
Click to expand...
Click to collapse
3.5.6 is the rom version.
Flashing firmware from another version won't change this.
The only indication you'll get is that the baseband version will change (but not always as some of the firmwares have the same baseband version).
Spannaa said:
3.5.6 is the rom version.
Flashing firmware from another version won't change this.
The only indication you'll get is that the baseband version will change (but not always as some of the firmwares have the same baseband version).
Click to expand...
Click to collapse
Hi,
Noob Question, But I haven't flashed 3.5.6 can I still be able to update with the 3.5.7 firmware patch ? Also I believe that this does enable our dearest OpenPlus 2 with VoLTE ?
(P.S. I'm on Nougat 7.1.1, I hope it doesn't mess with the firmware 3.5.7)
Regards,
V.
I recently bought a OnePlus 5 with h2Os . I flashed it to oxygen OS using stock recovery. The problem is that the phone keeps on rebooting randomly from time to time.
I have tried several fresh flashes. Wipes. Factory reset but to no use. I wonder if there is any catch when flashing from H2Os to O2 OS . Or is my device faulty ?
I didn't check thoroughly if the behavior was the same on H2Os.
Any leads , help , guidance ?
Do you had this problem with the preinstalled h2Os?
I did not check. I flashed O2 as soon as I got home. So I can't say if it misbehaved on hydrogen os.
Have you downloaded the OxygenOS firmware from oneplus net?
Yes. From official website
salimbaba said:
Yes. From official website
Click to expand...
Click to collapse
Try to download even the official recovery and flash with that even if it seems equal... Otherwise i think you've to reflash h2os and test the phone and if the problem occurs again maybe the device is defective but without tests we have no answers :fingers-crossed:
Hitman478™ said:
Try to download even the official recovery and flash with that even if it seems equal... Otherwise i think you've to reflash h2os and test the phone and if the problem occurs again maybe the device is defective but without tests we have no answers :fingers-crossed:
Click to expand...
Click to collapse
Has there been reports of such faults on op5 ? I will probably be returning it tomorrow. But now I am afraid if the next op5 I get would be trouble free or not.
salimbaba said:
Has there been reports of such faults on op5 ? I will probably be returning it tomorrow. But now I am afraid if the next op5 I get would be trouble free or not.
Click to expand...
Click to collapse
I've never heard about this issue before but i'm only one, maybe try at the support forum on oneplus net
I think it has to do with unlocking bootloader and root. I erased everything, went back to stock rom and relocked bootloader and no reboot today.
Greetings everyone,
I have been using a G4 Plus (indian retail unit) since 2017 and was on Nougat for years now. The phone never got Oreo for me. I tried using this trick from the thread to successfully upgrade to Oreo. Now, ever since the upgrade, I haven't had any issues apart from the battery. On Nougat, I used to get atleast 4.5 hours on screen time and 5 at max usage. I'm a moderate user. I charge the phone early in the morning. Now, it has been reduced to 3 hours 42 minutes on an average. I have my GPS Turned off, Screen Brightness and everything related adjusted. And the figures above are without battery saver. I don't want to downgrade as I like the Oreo UI and fluidity of the OS. The phone heats up at points when CPU usage is a bit high. Not a huge issue for me though. Anything I can do fix the battery life?
SpiralX15 said:
Greetings everyone,
I have been using a G4 Plus (indian retail unit) since 2017 and was on Nougat for years now. The phone never got Oreo for me. I tried using this trick from the thread to successfully upgrade to Oreo. Now, ever since the upgrade, I haven't had any issues apart from the battery. On Nougat, I used to get atleast 4.5 hours on screen time and 5 at max usage. I'm a moderate user. I charge the phone early in the morning. Now, it has been reduced to 3 hours 42 minutes on an average. I have my GPS Turned off, Screen Brightness and everything related adjusted. And the figures above are without battery saver. I don't want to downgrade as I like the Oreo UI and fluidity of the OS. The phone heats up at points when CPU usage is a bit high. Not a huge issue for me though. Anything I can do fix the battery life?
Click to expand...
Click to collapse
You can analyze with apps like better battery stats to find roque processes maybe.
strongst said:
You can analyze with apps like better battery stats to find roque processes maybe.
Click to expand...
Click to collapse
What is the best stock rom for stability & battery life? Maybe I should downgrade.
SpiralX15 said:
What is the best stock rom for stability & battery life? Maybe I should downgrade.
Click to expand...
Click to collapse
The nougat ones, android 7. But downgrade is risky you know?
strongst said:
The nougat ones, android 7. But downgrade is risky you know?
Click to expand...
Click to collapse
Why is it risky? Can I go to stock Android? And what build should I opt?
SpiralX15 said:
Why is it risky? Can I go to stock Android? And what build should I opt?
Click to expand...
Click to collapse
If you have upgraded with method 2 you most likely upgraded the bootloader too hence downgrading to nougat and downgrading the bootloader bricks your device. If you don't downgrade the bootloader it should work correct @echo92?
strongst said:
If you have upgraded with method 2 you most likely upgraded the bootloader too hence downgrading to nougat and downgrading the bootloader bricks your device. If you don't downgrade the bootloader it should work correct @echo92?
Click to expand...
Click to collapse
Aware of this one. Can I downgrade with a locked bootloader? Ofcourse I won't be flashing bootloader.
SpiralX15 said:
Aware of this one. Can I downgrade with a locked bootloader? Ofcourse I won't be flashing bootloader.
Click to expand...
Click to collapse
You need to skip the bootloader when flashing with fastboot.
But wait for echo92 to confirm :highfive:
strongst said:
You need to skip the bootloader when flashing with fastboot.
But wait for echo92 to confirm :highfive:
Click to expand...
Click to collapse
Can someone confirm this about the downgrade?