Problem occur in stock fw(3.2.4), Nexus 2.01 and even after rollback to .3.1.0
My HDX when lying on the table goes on and off every minute(clock resets to 0:00 after each reboot), but when I start to use it, it's working fine without auto reboot...
At first when I flashed Nexus everything was ok but then I was busy and haven't used my tab for few weeks and now I have this annoying problem.
Because of this battery goes low very fast.
Is this hardware or software problem?
Hope for your help.
Clock reset to 0.00 is normal with your Nexus Rom after reboot; when wifi is on while you reboot time setting is ok...
It has been fixed with 2.05
I would install and use stock for a day to try if the problems still are there...
(maybe 13.3.2.3, because after that you can install TWRP and a custom rom straight away...; but disable OTA or disable wifi while on stock, otherwise you will get an update)
Maybe a complete new installation (stock -> twrp -> custom rom) will fix it
futzmaster said:
Clock reset to 0.00 is normal with your Nexus Rom after reboot; when wifi is on while you reboot time setting is ok...
It has been fixed with 2.05
I would install and use stock for a day to try if the problems still are there...
(maybe 13.3.2.3, because after that you can install TWRP and a custom rom straight away...; but disable OTA or disable wifi while on stock, otherwise you will get an update)
Maybe a complete new installation (stock -> twrp -> custom rom) will fix it
Click to expand...
Click to collapse
I'm now on 13.3.2.3.2 and problem is still there... I get clock reset on stock fw not nexus, is this normal too?
I also did factory reset...
Long shot - try a forced shutdown via long press of power button. On rare occasions I have found this corrects device weirdness. Really should have the same effect as soft powering off but for some reason it seems to work. Worst case you've lost 2-3 min trying.
Also check if same behavior occurs while booted into recovery. If so almost certainly a hardware issue, possibly when CPUs throttle down or some other 'idle' state kicks in.
Davey126 said:
Long shot - try a forced shutdown via long press of power button. On rare occasions I have found this corrects device weirdness. Really should have the same effect as soft powering off but for some reason it seems to work. Worst case you've lost 2-3 min trying.
Also check if same behavior occurs while booted into recovery. If so almost certainly a hardware issue, possibly when CPUs throttle down or some other 'idle' state kicks in.
Click to expand...
Click to collapse
Did hardware reset, unfortunately without success...
What do you mean with "booted into recovery"? Fastboot or another fw slot with safestrap?
Flashed cm11 and still got this issue! I'm done...
I think you don't need to test custom roms yet...
Your goal should be to have a clean stock rom with no errors.... (no safestrap and stock custom recovery)
If you still have errors you need to contact amazon anyway i guess....
futzmaster said:
I think you don't need to test custom roms yet...
Your goal should be to have a clean stock rom with no errors.... (no safestrap and stock custom recovery)
If you still have errors you need to contact amazon anyway i guess....
Click to expand...
Click to collapse
alright, what's the steps to recover to clean stock from twrp with cm11?
Related
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
MI_SS_IL said:
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
Click to expand...
Click to collapse
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
captemo said:
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
Click to expand...
Click to collapse
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
MI_SS_IL said:
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
Click to expand...
Click to collapse
I have dirty flashed every one. the only thing I try to do when gong dirty is to still give it that 10 settle time. no particular reason other than my OCD
Okay, thanks for the replies. I'll play around with it some more, maybe try a fresh install and see if that changes anything. I'll let you know if I figure it out.
Chris
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
I guess I can't edit the title to reflect the correct issue? Thread can be deleted if the moderators want. Hellybean is running strong ... it's the first ROM I get 0 random reboots.
Thanks for the help captemo and to the makers of Hellybean.
Chris
beanstalk
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
hotgly said:
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
Click to expand...
Click to collapse
Same issue. Any of the 4.3 ROMS.
MI_SS_IL said:
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
Click to expand...
Click to collapse
So did you:
1- restore a stable backup
2- boot to recovery and flash TWRP (which version?)
3- Boot back into recovery
3- wipe and flash HellyBean
Is this correct?
My device is a local re-branded and enhanced Xolo a500s/it's like a karbon a5 a think. After successfully updated my device via OTA and after my device rebooted. My screen started to flicker randomly. My phone is not rooted and im still using the official stock rom. I found a temporarily solution by doing a Factory Reset, the flickering would be gone but it will come back after my phone screen goes off and on. Anyway to fix this?
I suspect that the new lockscreen bloatware system app that comes with the update causes this, but hey I only suspect it and i'm new to the android community. I can't disable it(googled already, and the only way to freeze/remove it is to root.) I can't root my device for something like a hunch. I'm waiting for a software update that would fix my device's touchscreen collide bug.
Appreciate all of your thoughts.
Try to start your phone in Safe Mode or try to start in Recovery (if your phone has available) and do a Factory Reset
UltraWelfare said:
Try to start your phone in Safe Mode or try to start in Recovery (if your phone has available) and do a Factory Reset
Click to expand...
Click to collapse
Thanks for the reply, I really appreciate it. I was able to disable the bloatware new systapp lock the came with it and it didn't solve the problem. I will try your method. Again thank you very much. I will check in later to post the result, hopefully this fixes it all
*edit
I successfully managed to boot in safe mode, the flickering has stopped but it return right after the screen goes back from sleep. Then I do a factory reset then after that the phone starts up and the result is still the same.
I will try the recovery mode though.
*edit
okay, i've managed to enter recovery menu. the one where you use the volume buttons to move. Is it really safe to select Wipe Data/Factory Reset there? Is that what you're prompting me to do in your post?
drckml said:
Thanks for the reply, I really appreciate it. I was able to disable the bloatware new systapp lock the came with it and it didn't solve the problem. I will try your method. Again thank you very much. I will check in later to post the result, hopefully this fixes it all
*edit
I successfully managed to boot in safe mode, the flickering has stopped but it return right after the screen goes back from sleep. Then I do a factory reset then after that the phone starts up and the result is still the same.
I will try the recovery mode though.
Click to expand...
Click to collapse
Report back if something new happens
UltraWelfare said:
Report back if something new happens
Click to expand...
Click to collapse
The results are still the same... your method do work yes. The flickering is gone after rebooting but as soon as you know press the power button and screen goes off then press the power button again and the screen turns on again from standby, the flickering returns.
Before doing some OTA updates my device is like v7 or v8 and now it's v9.1
and I didn't have any screen flickering problems before updating to v9.1 so I can safely assure that it's not in the hardware. It really just happened right after updating my device.
Another question, will installing a custom rom fix this software bug? But I really don't want to install those yet at the moment.
Any, Thank you very much. I really really really really appreciate it all man. I'm really at loss now. This is my first android phone that's why.
drckml said:
The results are still the same... your method do work yes. The flickering is gone after rebooting but as soon as you know press the power button and screen goes off then press the power button again and the screen turns on again from standby, the flickering returns.
Before doing some OTA updates my device is like v7 or v8 and now it's v9.1
and I didn't have any screen flickering problems before updating to v9.1 so I can safely assure that it's not in the hardware. It really just happened right after updating my device.
Another question, will installing a custom rom fix this software bug? But I really don't want to install those yet at the moment.
Any, Thank you very much. I really really really really appreciate it all man. I'm really at loss now. This is my first android phone that's why.
Click to expand...
Click to collapse
First of all try factory data reset.Secondly if it doesn't work try a custom rom(if you really want to)and check if the bug has gone.If it doesn't then there is something fault with your device
UltraWelfare said:
First of all try factory data reset.Secondly if it doesn't work try a custom rom(if you really want to)and check if the bug has gone.If it doesn't then there is something fault with your device
Click to expand...
Click to collapse
So the only is custom rom/original stock rom before update(which is impossible because I haven't backed up one before updating)
is the only solution eh.
The reason that I held back from installing a custom rom is because I'm waiting for the touchscreen bug fix for my device iva OTA. Will I still able to get it after installing a custom rom?
Again many thanks. Is there a way to give you a thanks on every posts?
drckml said:
So the only is custom rom/original stock rom before update(which is impossible because I haven't backed up one before updating)
is the only solution eh.
The reason that I held back from installing a custom rom is because I'm waiting for the touchscreen bug fix for my device iva OTA. Will I still able to get it after installing a custom rom?
Again many thanks. Is there a way to give you a thanks on every posts?
Click to expand...
Click to collapse
If there is a way to restore back to your stock version or find a way to get back to stock version then yes .
If you had a Sony Device then you could restore it with SEUS.Now with a Xolo I really dont know.Ask to the specific device forum
UltraWelfare said:
If there is a way to restore back to your stock version or find a way to get back to stock version then yes .
If you had a Sony Device then you could restore it with SEUS.Now with a Xolo I really dont know.Ask to the specific device forum
Click to expand...
Click to collapse
Thanks a lot man. I've flashed a stock rom and my device got fixed from screen flickering. Really looks like a firmware bug. So I've just downgraded.
Again thanks a million
HI guys,
My tablet is giving me issues with my wifi all of the sudden.
It was working fine and now it just says Turning on Wi-Fi... this never stops.
I have a Huawei Mediaoad S7-301u
Any ideas how I can get my wifi back up and running?
A restart should do. If you don't have to do this too often. All custom roms for the Mediapad should exhibit this fom time to time, stock rom is too long gone to remember, but if you're still using it you found the answer for that.
Usually it should happen after wakeup from standby, and if it occurs several times a day, another rom may perform better, also increasing screen timeout should help.
If wifi is completely gone, restore a nandroid backup or recover the stock rom via dload method, if there's no custom recovery, which would prevent that. Custom rom and no backup means doing a clean flash.
lecorbusier said:
A restart should do. If you don't have to do this too often. All custom roms for the Mediapad should exhibit this fom time to time, stock rom is too long gone to remember, but if you're still using it you found the answer for that.
Usually it should happen after wakeup from standby, and if it occurs several times a day, another rom may perform better, also increasing screen timeout should help.
If wifi is completely gone, restore a nandroid backup or recover the stock rom via dload method, if there's no custom recovery, which would prevent that. Custom rom and no backup means doing a clean flash.
Click to expand...
Click to collapse
I have done a few restarts and I have also reinstalled the same rom. I am starting to think it is the rom, it seemed buggy from the start.
Which rom would you suggest?
Stability-wise it's the older the better. Stock rom and After Silence's CM10(probably gone forever) . He developed the kernel Zyr3x was also using, whose roms got buggier and buggier. Zyr3xs AOKP, maybe, that was my first custom rom on the Mediapad, but I don't remember the bugs there were. Some, but not many.
I'm so lost and confused over this since yesterday...
so 2 days ago my phone started lagging and hanging and freezing until i realized i have got this issue with data encryption
i have a rooted sony z2 with TWRP Custom recovery
first i didn't know it was with data encryption failure so i literally factory reset and installed all my apps and data again and again!!!
On both rooted and non rooted rom ....
after every time my phone started to lag !!
after one whole day of trying everything i finally realized its actually with the data encryption and i should change my ex4 to something else... so here again i wiped the phone and changed to ex3 and installed and all my data and apps all over again
but after a couple hours...same problem again.....
im literally so tired of not knowing what to do ! my head hurts so much due this ugh....
Please help me get rid of this issue thanks ...!
Hey, i would flash the full stock rom without root and twrp and look. I think it is a problem with the twrp recovery.
On my V30 with Oreo we should flash a zip that disable data encryption after some modification in Recovery.
Just try for a week the full stock rom.
Nemeziz 56th said:
Hey, i would flash the full stock rom without root and twrp and look. I think it is a problem with the twrp recovery.
On my V30 with Oreo we should flash a zip that disable data encryption after some modification in Recovery.
Just try for a week the full stock rom.
Click to expand...
Click to collapse
Well i have already tried using the stock ROM without any root or recovery !!
and its still the same
however im not sure whats the zip file u r talking about and where i can get it for my Sony z2 D6502...
By the way i just thought it might be another reason that my device is lagging so much after installing like 30/40 apps.
i have overclocked my CPU with root and even after flashing the stock rom i feel like CPU settings hasn't been reset? is it possible?
its always on end MAX and less Min value on both stock/pre root rom my CPU gets very hot on TWRP specially, its more than 70Celcious so i thought maybe its a hardware issue and my CPU is overheating bcuz its old or something... and i should prolly change my CPU ?
i really don't understand whats wrong with my phone and im so confused about what to do
I had here a Z1 and Z2 both was my previous phones.
I didnt experienced such problems except i backup or restore anything in TWRP.
My questions for you are:
On which Version are you now?
What do you done exactly before the problem starts?
Get a Monitor App from Playstore and look what cause this high load. Or you take a look in the Developers Option for this.
We got here a not tasty problem, maybe you backup your whole data and reset all to stock and don't install any apps, after a while installing step by step your apps.
Nemeziz 56th said:
I had here a Z1 and Z2 both was my previous phones.
I didnt experienced such problems except i backup or restore anything in TWRP.
My questions for you are:
On which Version are you now?
What do you done exactly before the problem starts?
Get a Monitor App from Playstore and look what cause this high load. Or you take a look in the Developers Option for this.
We got here a not tasty problem, maybe you backup your whole data and reset all to stock and don't install any apps, after a while installing step by step your apps.
Click to expand...
Click to collapse
I dont think if its even about TWRP because i even installed the stock rom with Flashtool and started installing my apps one by one and after a couple hrs device started lagging and freezing and odd how Wifi gets soooo slow ! (like everything gets slow in it) and also when i reboot the phone it oddly takes long time on boot menu to load .
im not sure if i did anything to cause it tbh...
it just happened on a normal day...
it gets soooo slow and leaves no other way for me but factory reset option...
i have the latest rom 23.5.A.1.291
the only time i can get it temporary fixed is when i backup the rom on TWRP and factory reset the Rom and Restore it back!
and everything is working fast and fine again only for like 6 or less hours...
and while data is restoring TWRP shows the CPU Temp on +80C !! Is this normal?
Btw i have a unlocked bootloader.
do u have any idea what i should do?
Yes i do! You need a structure by fixing a problem, my plan is:
You must explorer the problem why your phone get so laggy.
Perform a factory reset and use your phone for 1 Day with this stock setup. (Dont restore your old apps or data)
Look often into the Task Manager to show what cause the cpu load.
Nemeziz 56th said:
Yes i do! You need a structure by fixing a problem, my plan is:
You must explorer the problem why your phone get so laggy.
Perform a factory reset and use your phone for 1 Day with this stock setup. (Dont restore your old apps or data)
Look often into the Task Manager to show what cause the cpu load.
Click to expand...
Click to collapse
man i kinda feel like its my CPU that is messsed up and idk why
cpu usage doesnt show any app, no app is taking more than 1%.
i think ,my system is overclocking...
and if it is how can i reset or stop it smh?
I don't know what's wrong with this phone, but once it's rooted it will eventually enter a boot loop after some restarts or power on/off cycles. You can boot to recovery or fastboot, but no matter what you do there, the only way to fix the bootloop is flashing the stock boot and recovery partitions and formating data from there. The phone will reset to factory and boot up normally, but you will loose all your config, apps, etc. It's a pain in the a** to setup everything all over again every few days. Every time you have to restart your phone is like playing russian roulette, you never know when the boot loop will happen, but it will come up sooner or later no matter what you do. I have performed a lot of tests just rooting and without touching a single thing in config or apps, after some restart cycles it boot loops.
I'm fed up with it because it's so unreliable, it may work fine if you use it stock but I personally need root. I have ended up being so afraid of restarts that I have not powered it off or restarted since a month.
By the way this is my first One Plus and I don't know if this issue happens with other models from the brand.
This is just my experience and my advise.
Even i am a nord 2 owner and currently i am running custom os android 12 , even before this i had no probs like this with root.....
I bricked my device while installing gsi but that was different...
[RECOVERY][UNOFFICIAL] TWRP 3.6.0_11-0 for OnePlus Nord 2 5G [denniz]
Team Win Recovery Project 3.x, or TWRP 3.x for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven...
forum.xda-developers.com
Fastboot reboot recovery
Do this, then flash latest magisk....
You'll be good
satanishere16 said:
Even i am a nord 2 owner and currently i am running custom os android 12 , even before this i had no probs like this with root.....
I bricked my device while installing gsi but that was different...
[RECOVERY][UNOFFICIAL] TWRP 3.6.0_11-0 for OnePlus Nord 2 5G [denniz]
Team Win Recovery Project 3.x, or TWRP 3.x for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven...
forum.xda-developers.com
Fastboot reboot recovery
Do this, then flash latest magisk....
You'll be good
Click to expand...
Click to collapse
Indeed that's what I tried first because I usually solved boot loops with that method in other phones in the past. But with this one that trick does not work, I tried with several magisk versions before trying other things that didn't work either such as restoring a nandroid backup with TWRP or wiping everything and formatting data on TWRP. The only thing that worked was the method I described in OP, which I found in other thread in this forum. I have read reports about other people suffering the same problems, so I know I'm not alone.
By the way it seems to happen only with stock ROM. Which custom ROM are you using?
Regards
Pixel experience android 12....
Dev tab
Hi,
I can confirm that I had the same problem as you to root 3 One Plus Nord 2 (DN2103) from different friends wishing to stay on OxygenOS.
The root works fine and then totally randomly the OnePlus animation keeps looping after a reboot.
By doing a "fastboot -w" it starts again correctly but obviously with a loss of data.
Recently I got a Nord 2 from a friend for testing and it turns out that using the latest version of Magisk Canary, the root seems to remain after several reboots but to be tested over several months.
I've also seen here owners of European Nord 2 who confirm that root works well with Magisk Canary.
Edit : After about 10 reboots, the phone went back to bootloop.
Yes it's really exhausting root this phone. I tried custom roms without any problems with Magisk but stock is broken somehow. I need to use stock because of video recording quality. I have now Magisk 24.3 but didn't really restart it yet because of this. You shoud backup all data before restart . You can use data format in twrp, that works too.
Sperafico said:
Hi,
I can confirm that I had the same problem as you to root 3 One Plus Nord 2 (DN2103) from different friends wishing to stay on OxygenOS.
The root works fine and then totally randomly the OnePlus animation keeps looping after a reboot.
By doing a "fastboot -w" it starts again correctly but obviously with a loss of data.
Recently I got a Nord 2 from a friend for testing and it turns out that using the latest version of Magisk Canary, the root seems to remain after several reboots but to be tested over several months.
I've also seen here owners of European Nord 2 who confirm that root works well with Magisk Canary.
Click to expand...
Click to collapse
Thank you very much. Next time I will try switching to magisk canary channel. I'm on stable and sticking to 24.1 because the last time I updated from that version to 24.3 I got into a boot loop.
8vasa8 said:
Yes it's really exhausting root this phone. I tried custom roms without any problems with Magisk but stock is broken somehow. I need to use stock because of video recording quality. I have now Magisk 24.3 but didn't really restart it yet because of this. You shoud backup all data before restart . You can use data format in twrp, that works too.
Click to expand...
Click to collapse
Thanks for your answer. In my case the first thing I tried was flashing magisk again, then restoring a full nandroid backup with twrp, and then formatting data in twrp, but none of these steps worked.
I also heard about this problem being solved in custom ROMs but I haven't found any that fit my needs or any that has everything working, so I prefer to keep on rooted stock.
#metoo . We need devs to look into this problem. Been using rooted Android phone for years but now it s***s without root on Nord 2.
As long as you use an untouched stock rom (or after modding re-flashed by OnePlus servicepoint, rebooted into stock recovery, wipe all and re-flash stock, in a OnePlus store), root works fine on stock rom. Every attempt different than above will fail one day or another. I decided not to take OTAs because too many things can go wrong / turn unstable.
The phone is my daily driver, also for work. But I am rooted with Magism 24.3 (stable) and have various modules running including LSPosed, Shamiko, USNF, and in LSPosed GravityBox, XprivacyLua pro and a few more.
Works awesomely. Just don't touch things afterwords. In that case, yes, the phone sucks. Big time.
Xatanu said:
I don't know what's wrong with this phone, but once it's rooted it will eventually enter a boot loop after some restarts or power on/off cycles. You can boot to recovery or fastboot, but no matter what you do there, the only way to fix the bootloop is flashing the stock boot and recovery partitions and formating data from there. The phone will reset to factory and boot up normally, but you will loose all your config, apps, etc. It's a pain in the a** to setup everything all over again every few days. Every time you have to restart your phone is like playing russian roulette, you never know when the boot loop will happen, but it will come up sooner or later no matter what you do. I have performed a lot of tests just rooting and without touching a single thing in config or apps, after some restart cycles it boot loops.
I'm fed up with it because it's so unreliable, it may work fine if you use it stock but I personally need root. I have ended up being so afraid of restarts that I have not powered it off or restarted since a month.
By the way this is my first One Plus and I don't know if this issue happens with other models from the brand.
This is just my experience and my advise.
Click to expand...
Click to collapse
shoud what can i do any bramhastra or something ?
Look basically i am nerd and i agree that so apart from root i have question that installing TWRP and Custom Rom,is that working correctly with no issues? particularly pixelos
[email protected] said:
Look basically i am nerd and i agree that so apart from root i have question that installing TWRP and Custom Rom,is that working correctly with no issues? particularly pixelos
Click to expand...
Click to collapse
TWRP and custom roms works without issue. Even root is working with custom.
NANDroid does NOT work on stock rom! TWRP does, but no NANDroids possible.
Unfortunately I agree...
I spent so much time because of manipulations that I am used to doing, and which leads to a boot loop and a brick of the phone immediately afterwards.
The only solution I had was to flash the rom, which of course leads to a total reset each time and a considerable waste of time.
This is my 3rd and last OnePlus phone that I buy, I'm sick of all my lost data and hours spent just getting it started.
Oh my oneplus nord 2 is now in final bootloop. Cant make anything work, just keeps rebooting when plugging in power so $350 down the drain. Would not recommend..
Why down the drain? It's not 1 year old, so Oneplus will renew firmware under warrantee.
Xatanu said:
I don't know what's wrong with this phone, but once it's rooted it will eventually enter a boot loop after some restarts or power on/off cycles. You can boot to recovery or fastboot, but no matter what you do there, the only way to fix the bootloop is flashing the stock boot and recovery partitions and formating data from there. The phone will reset to factory and boot up normally, but you will loose all your config, apps, etc. It's a pain in the a** to setup everything all over again every few days. Every time you have to restart your phone is like playing russian roulette, you never know when the boot loop will happen, but it will come up sooner or later no matter what you do. I have performed a lot of tests just rooting and without touching a single thing in config or apps, after some restart cycles it boot loops.
I'm fed up with it because it's so unreliable, it may work fine if you use it stock but I personally need root. I have ended up being so afraid of restarts that I have not powered it off or restarted since a month.
By the way this is my first One Plus and I don't know if this issue happens with other models from the brand.
This is just my experience and my advise.
Click to expand...
Click to collapse
U r wrong
I'm not sure if it's just a coincidence, but for me, it always happens after about a week or two of ignoreing "you have an update available" popup. I thought maybe it modified the boot image, like magisk, to run at the next startup.
I agree that this is very annoying. If I didn't need Google Pay, I'd just install another rom.
Like said. Have your device Factory-flashed by OnePlus, REBOOT to stock recovery, do a FULL WIPE and FACTORY FLASH stock AGAIN! Only with the official OnePlus tool and software.
Only this way all your old fiddling around is erased. If you ROOT then, all will be fine. Of course, neglect further updates, but the device will work fine. Mine is in this state, heavily tweaked (Magisk, Zygisk, USNF, GravityBox, etc. etc. and it runs stable for over 10 weeks without any hickup.