Hey there so recently I have upgraded to stock nougat but I'm getting tired of the lag I'm getting on it, I'm getting it more so than MM before. I didn't bother with custom firmware before as I could tolerate the lag on MM and I could use android pay.
Now browsing around the forums I have gathered that there is a chance if I downgrade it could brick the phone? Am I stuck with the stock firmware for the moment?
Is there any way that I can improve the phone's performance in the mean time?
(I have cleared the cache, it improved for a few days until it went to the normal lag again)
I downgraded the other day just fine from stock 7.0 to stock 6.0.
gpt.bin and bootloader.bin cannot downgrade once updated to the latest (I just ignored the errors and went ahead). Everything else flashed with no errors.
Once back on MM 6.0 I reflashed Lineage OS 14.1. Wasn't impressed with stock 7.0 like I thought I would be.
Just remember, if you downgrade there is no going back to Nougat, and if you happen to mistakenly update via OTA it is instant hard brick... at least until we can manage to get a full factory firmware image of Nougat.
Honestly, if you are willing to go that far, why not start with a simple factory reset?
Factory reset is a must with this update to 7.0 anyone willing to downgrade vs trying a factory reset needs their head examined.
Related
Hello,
I was on 4.4.2 and rooted. Started getting OTA notifications about lollipop a few days ago. So, I reverted to stock/flashed KDZ. Now my phone is unrooted, stock 4.4.2 again (clean install, with factory reset).
Now, for some reason, when I go to Settings > System Updates to look for lollipop (or any update), it doesn't find anything! Same exact phone, same exact software (VS98027A).
Why is it saying my phone is up to date when just a few hours ago it was finding Lollipop??
daniel178 said:
Hello,
I was on 4.4.2 and rooted. Started getting OTA notifications about lollipop a few days ago. So, I reverted to stock/flashed KDZ. Now my phone is unrooted, stock 4.4.2 again (clean install, with factory reset).
Now, for some reason, when I go to Settings > System Updates to look for lollipop (or any update), it doesn't find anything! Same exact phone, same exact software (VS98027A).
Why is it saying my phone is up to date when just a few hours ago it was finding Lollipop??
Click to expand...
Click to collapse
you should have DL'd it and pulled from your phone. Are you sure it was LP?
It did download--every time. But of course I didnt back it up (not that I'd know where it downloaded to anyway) since I naturally thought there would still be an update to find after i flashed the phone.
I can't be 100% sure which update it was, but it was at LEAST a couple hundred megs, most likely more.
So I had been running the unnofficial 5.0.2 CM lollipop on my phone for a while when I finally decided I would do a full wipe and flash the latest version of it (1/26). Prior to the full wipe, the phone had been running fine. But since 1/26, it started depleting battery rapidly and it had tons of input lag. So... I wiped again and went back to what I previously had... only, my problems did not go away. So then I decided I would wipe and go back to CM11. Now, it is a little better, but still is having odd lag / behavioral issues.
My question is this.... I did several full wipes. This doesnt seem to be resolving my issues. I am guessing that wipes dont really get rid of strange behavior. Is there another step? I tried the "repair" option in TWRP but that didnt help much. I am using the latest TWRP. Should I odin a factory ROM then re-root everything? If so, does knox become removable, or am I stuck with it?
So I've had my nexus 7 2013 (wifi) for a while and before Lollipop came out on the ota update I decided to flash it myself because I was a bit inpatient. Since then I've been flashing the images on my own, but I still get a message on the table about an update, but I can not update it through the tablet itself anymore even when I have the factory recovery and everything else is flash backed to stock. I would like to know if there is a solution to this problem as flashing everything back to stock has not worked. Thank you.
Hello, I previously had my 6P on Marshamallow 6.0.1 with systemless root. When the Android N previews came about I manually flashed it using the method in this thread here (9. How To Update To A New Build Of The Stock ROM). However, I decided to revert because some apps don't work well in N. But when I used the same exact method with the 6.0.1 images my phone gets stuck at the login screen, flashes the message "the process android.process.acore has stopped" when I open the camera, and bootloops. Any help please?
Have you tried factory reset then re flash M
Fe Mike said:
Have you tried factory reset then re flash M
Click to expand...
Click to collapse
I'm definitely thinking about doing a factory reset but it's a last resort. In the meantime is there anything else I can do?
Edit: LOL I think I accidentally factory reset it anyway. I'll let you know if it works!
Hello,
I want to know if it is possible to root the stock rom, and keep OTA.
Actually, my objective is to use screen mirroring (miracast), and I heard rooted devices can achieve that by changing build.prop. I didn't want to switch from stock rom, since I like it and like updating OTA.
Maybe if I adb boot twrp and install supersu, but keep regular revovery, I can still get OTA?
If there's another solution to screen mirroring, I'd be glad to know, too.
Thanks in advance!
I've tried to root stock rom and keep the system unmodified through Magisk. For whatever reason OTA always fails even though I have stock recovery, supposedly unmodified system, and rolling back to stock boot image prior to trying the OTA.
The only thing that works is to flash the stock firmware and then taking OTA. The only problem is that the stock firmware is tough to come by, but I read that someone got their hands on the latest 93-10 firmware image. So that's good.
I've since moved onto Pixel Experience 8.1 rom without any regrets. The camera works really well and battery is nearly up to par with stock Nougat.
No, unfortunately these things still modify the the system and boot partition and the upgrade script knows it and causes the update to fail. We don't know exactly everything the OTA update scripts check (it's not just a simple text file) but it is obviously something that it knows you are rooted even when nothing else does. :/
You must be completely stock to take an OTA update... the only exception is your bootloader lock state doesn't matter at this time, we do know that it is capable of detecting that as well.
I have done that and I got Bootloop! So don't Try!
else
https://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175