Related
Should I root My Samsung Galaxy Note 10.1 ?
Model : GT-N8000
Country : Malaysia
BTW will root cause the Tab to become slow ?
Do I need stock recovery to get OTA ?
As always if you have to ask then the answer is no .
You root when apps or mods require root only .
Root voids warranty ..
This is not the Tab forum do not use any firmware or mods from here on a Tab .
Do I need stock recovery to get OTA
Yes stock and original with no root for OTA .
jje
If you are happy with your Note, than it's not necessary.
I rooted mine, because it was still on 4.0.3, and that is the reason for the many bad reviews on the internet.
After upgrading to 4.1.2, it was like a whole new tablet.
JJEgan said:
As always if you have to ask then the answer is no .
You root when apps or mods require root only .
Root voids warranty ..
This is not the Tab forum do not use any firmware or mods from here on a Tab .
Do I need stock recovery to get OTA
Yes stock and original with no root for OTA .
jje
Click to expand...
Click to collapse
This is not the Tab forum
Click to expand...
Click to collapse
What you mean ? I tot I am at the correct forum ?
ic3tea said:
What you mean ? I tot I am at the correct forum ?
Click to expand...
Click to collapse
You're from Malaysia..me too.
Btw you're in correct forum.When you wrote tab people will confuse it with galaxy tab and root will not slowing down your note.
Sent from my GT-I9100 using xda premium
I actually liked my Note even at 4.0.3.. but I rooted so I could use the Multiwindow manager for multiwindow.. EVERYWHERE!
asdfuogh said:
I actually liked my Note even at 4.0.3.. but I rooted so I could use the Multiwindow manager for multiwindow.. EVERYWHERE!
Click to expand...
Click to collapse
So that I will try and root but BTW just asking is HighXXXXXXXX CMW Recovery good or Darkman Recovery Good ?
TWRP is only for stock rom right ?
There are many benefits to root. All the flashable files here require it.
But technically you will void your warranty.
However there are ways to get back to stock and "unroot" so mostly no one will know the difference if you have to return it.
Both recoveries are good, but HighOnAndroid supported a couple ROMs that Darkman didn't, though I'm not sure this is still the case
blud7 said:
There are many benefits to root. All the flashable files here require it.
But technically you will void your warranty.
However there are ways to get back to stock and "unroot" so mostly no one will know the difference if you have to return it.
Both recoveries are good, but HighOnAndroid supported a couple ROMs that Darkman didn't, though I'm not sure this is still the case
Click to expand...
Click to collapse
How about TWRP Recovery ? TWRP Recovery only work in stoock rom ?
ic3tea said:
So that I will try and root but BTW just asking is HighXXXXXXXX CMW Recovery good or Darkman Recovery Good ?
TWRP is only for stock rom right ?
Click to expand...
Click to collapse
You will need to flash the HighXXXXXXXX CMW in ODIN to get root and cwm. You can then flash either darkman recovery with CWM, TWRP recovery or stay as is..
TWRP recovery isa modified recovery like the other 2 and requires root to use. If you look around you'll find the stock recovery too.
I root my tab with Darkman Recorvey is easy then I tot . Thx you guys .
Sent from my GT-N8000 using XDA Premium HD app
Yes! Rooting is the way to go. There are ways around the warranty issues.
My main reason for rooting is for these essential apps:
Titanium Backup
Ad Blocker
Mobile ODIN
Triangle Away
ROM Toolbox Pro
and many more apps that have useful extended capabilities once rooted.
Some Con's of rooting
1) good mobile app no longer works after rooting.
So if u use good mobile for checking corporate emails, rooting device will break this.
2) there will be some overhead for you to upgrade device when any new firmwares are released. If u are a very busy professional, then this is an overhead you can live without.
3) there are and there always will be chances that you may brick your device.
4) I think u legaly void warranty on device by unlocking it. (I am assuming u want to root to load different firmware)
I am not discouraging.. just givin you other side of the coin.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
smrsxn said:
Some Con's of rooting
1) good mobile app no longer works after rooting.
So if u use good mobile for checking corporate emails, rooting device will break this.
Click to expand...
Click to collapse
Sorry to bump a three month old thread, but would anyone know whether the Lotus Traveler app used for syncing corporate email and calendar works after rooting? Good is trash, so I'm not surprised it wouldn't work. There's not much of a downside finding out for myself by rooting my Note 10.1 because I intend to keep flying stock on my Note 2; but I thought someone might save me the time and trouble.
JasW said:
Sorry to bump a three month old thread, but would anyone know whether the Lotus Traveler app used for syncing corporate email and calendar works after rooting? Good is trash, so I'm not surprised it wouldn't work. There's not much of a downside finding out for myself by rooting my Note 10.1 because I intend to keep flying stock on my Note 2; but I thought someone might save me the time and trouble.
Click to expand...
Click to collapse
For Lotus Traveler - I have no idea. I am unlucky enough to have Lotus Domino for our corporate e-mail and I hate it with a passion.
I have installed and configured Aqua Mail to connect to our Domino server (IMAP) and I can confirm that it works perfectly after rooting. You just need your IT guys to ensure that you have web access enabled. I set mine to check for mail every 15 minutes, if it's more urgent than that then why is it an email anyway.
Rom Noob tips, from a noob, please feel free to correct, add or expand on any points
General rooting options
Titbits
- rooting under normal circumstances shouldnt slow your system, in fact most devs i believe will attempt to make their roms bring out the best performance from that particular tab/phone you may own, throught software optimizations, in cojunction with working as best as it can with your specific hardware, although, sometimes you may have a N8013(american wifi version), the dev may have the n8000(3g version).......n810 is the european wifi version...................weve been mixing and matching rom versions here, i.e. using a n8000 rom on a n8010 hardware, ive done it, as far as i know, no adverse effects, well at least no obvious signs of em
- Usually, the process of flashing a rom will first involve rooting your tablet, and then flashing a recovery, which replaces the official one that may already be on your tab, the official one is usually pretty limited in what you can do, the custom RECOVERY is flashed because it gives you these options, but not limited
-factory reset
used when, flashing new rom, best to use the recovery when ever you wanna factory reset, i dont know if this was a oje of, or just specific to my situation, but ive used the android factory reset on my tf201 asus prime, after having rooted, custom recovery and been running a custom rom for some time, and it soft brick, since thats happenened ive been shy to do it on any android device, which is cool, as the custom recovery is a beatiful thing.......maybe someone can expand on or correct that suspicion
- wipes
cache- wipe your app cache
Davlik - someone gonna have to chime in there
factory/data reset- brings back your android back to its original state, wipes your data, that means, all apps installed, all settings changed
format - allows you to format the different seperate sections of your android rom, example of the different sections would be......kernel, os, sd hardrive ........
nandroid - the best part of a custom recovery in my opinion, the ability to completely back up your rom, settings, apps, homescreens, widgets......essentially, restoring your android EXACTLY where you left off, the few seconds before, it takes to boot into recovery and start the backup procedure..........you can also backup and restore only certain sections of your rom, so you may decide to back up just the kernel, or you may decide to restore, JUST the kernel from a FULL previous backup (that is, all sections backed up, minus, the sd hardrive,
Unless you specifically FORMAT the sd card, it usually wont be touched......id advice caution and reading up, before making a decision to format sd harddrive, with a custom RECOVERY, that may not know the requirements to your android device, i.e. a custom kernel ported from another android device from another company....plus, formatting sd harddrive is not really a thing done all the time, not unless you are thinking about starting from scratch, i mean, REALLY fresh, disclaimer:this would wipe any files you have stored on your android devices, specifically, documents, pics, vids so on so forth
- stock rom
the original android OS shipped with the device
- stock based rom
tweaked stock rom, speed, battery other mods
-CM (CynogenMod)
third party rom, built from the ground up, kinda....there are other different flavors of third party roms, CM is one of them
-when flashing a new rom, it is strongly advised by most devs to wipe cache/davlick and factory reset....before flashing, this helps avoid any conflicts with the previous rom and the new rom......at this point, if you were to reboot, rather then flash the rom, you would have essentially reset the rom to its original state, that means re-entering your wifi, changing settings, installing apps, generally a pain in the ass, if you find your self having to do it to many times in a short period.....titanium backup(root) is your friend, does a good job at backing up your apps and wifi.....havent figured out how to backup the settings i change in the android setting
https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup
-quick boot
https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot
This free app, is a life saver when your new rom doesnt give you the option to reboot into your recovery, sometime found in hold power button/restart/recovery.......just more quicker then the manual way......especially when your having to google up the hardware method because you've not done it in a while and forgotten......which i believe is power off/hold volume down key/then press hold power button/wait for samsung logo/then let go of all buttons and reapettedly press volume up key untill the recovery shows up.......if you end up in DOWNLOAD mode, hold power to switch off, and repeat the process, changing the volume key, its one or the other, one takes you to the recovery, the other to download mode......so just reverse the volume keys, same method, just up instead of down
- supersu/superuser
installable app, that hands out root permission to apps that ask for root, if you dont expresly give persmision, using a supersu app, the app asking for root permission most likely will not work.... .....this app is installed as part of the rooting process
- afwall+ (free)
third party wifi/3g firewall, requires root........allows you to control what apps are able to use your wif/3g......i think its a passive firwall, as in, it uses very little of your resources, in the way it operates
https://play.google.com/store/apps/details?id=dev.ukanth.ufirewall
- rom flashing
sometimes, if you have already flashed a custom rom, and the dev has released the next version of his custom rom, as long as no drastic changes have been made between the two versions, you are able to flash the new version over the old version, keeping all your settings/apps/homescreen/widgets.......although a cache and davlik wipe is usually suggested if doing so
ive forgotten half of what i was originally going to write, so ill just leave it there before i rack my brains .......goodluck whatever you decide
Yes :good:
if it was me?
yea i would do it. it brings life to an old tablet. the 80XX tablets were abandoned by samsung. there are custom roms for Oreo the latest Android OS for N8000. i have a 8020 but no custom roms at the moment.
Good been waiting a whole 5 years for a reply .
So I'm a proud new owner of this device. LG G2 D802, running stock JDQ39B and D80210a-219-10. I like to consider myself a power user, but after a long time with Sony phones, I find mysef a noob after getting this phone. There's no Flashtool and everything looks unfamiliar.
I've been reading and educating myself over this phone and in a nutshell here's what I've found and would like some confirmations:
1. Bootloader unlock in not possible. Instead you use bootloader bypass from Loki.
2. To root my phone I need to follow this guide.
3. Installing custom ROMS requires a working recovery. This guide covers that.
4. Going back to stock is possible with this method.
Here are my quirks;
the trip root checker while rooting. I know rooting voids warranty, duh. However, I'm curious what does one do if you need to take the phone to the repair center? Does doing number 4(flashing stock .kdz) reset this root checker?
Second, usually flashing AOSP/AOKP/CM, etc. required full bootloader unlock. Since that is not possible here, what do I need to run CM for example? Does rooting the phone and installing TWRP(number 2 and nr. 3) set me for endless flashing? Meaning; does installing a recovery cover the Loki bootloader bypass bit?
Hope you guys bare with me. I did a lot of searching but there's so much threads, different variants here; i need to double check before doing these things for the first time. I'm really surprised there are no stickies here; if the threads I linked are good, they really should be stickied.
1. Yes
2. Yes
3. Yes
4. Probably
With TWRP (with Loki-Support), you can flash any ROM that matches your device. No need to unlock bootloader.
amokkx said:
1. Yes
2. Yes
3. Yes
4. Probably
With TWRP (with Loki-Support), you can flash any ROM that matches your device. No need to unlock bootloader.
Click to expand...
Click to collapse
Thank you very much.
I've done some further googling about this "root checker" and supposedly there should be a "Rooted Status" section listed under Settings>About>Status. But I have no "Rooted Status" there. Is it possible not every D802 has that root-checker?
revan17 said:
Thank you very much.
I've done some further googling about this "root checker" and supposedly there should be a "Rooted Status" section listed under Settings>About>Status. But I have no "Rooted Status" there. Is it possible not every D802 has that root-checker?
Click to expand...
Click to collapse
Every single ROM has a root checker. Some of them just don't display the root status in user's interface, just in the bootloader/download mode. Some Lg G2 variants display the root status in both the settings UI and bootloader/download mode.
goodmamba said:
Every single ROM has a root checker. Some of them just don't display the root status in user's interface, just in the bootloader/download mode. Some Lg G2 variants display the root status in both the settings UI and bootloader/download mode.
Click to expand...
Click to collapse
Ah yes, I just found that out. I went into download mode and it says unrooted. Oh well, at least I now know I received a new/non tampered phone from my carrier.
revan17 said:
Ah yes, I just found that out. I went into download mode and it says unrooted. Oh well, at least I now know I received a new/non tampered phone from my carrier.
Click to expand...
Click to collapse
For the "rooted" status to disappear you just have to re-flash a new stock ROM (tried myself). Or simply un-root using a super user app (not tested, just guessing).
goodmamba said:
For the "rooted" status to disappear you just have to re-flash a new stock ROM (tried myself). Or simply un-root using a super user app (not tested, just guessing).
Click to expand...
Click to collapse
I've seen some mixed reports over the "rooted status" disappearing. Some(like you) claim the rooted status goes away after flashing a stock ROM, some say it doesn't.
Oh well, I'll have to root it and just see for myself, I suppose. I really dislike LG's UI.
One more, unrelated to rooting, question. Does the camera work 100% with AOSP/CM ROMS? On my former phone, aosp based roms gave inferior photo quality...though there was no drivers supported for that phone(which isn't the case here). How are things with this phone? Do AOSP based ROMS give on par photos?
I'm literally blown away with photo quality on this phone, would hate to lose it in CM.
revan17 said:
I've seen some mixed reports over the "rooted status" disappearing. Some(like you) claim the rooted status goes away after flashing a stock ROM, some say it doesn't.
Oh well, I'll have to root it and just see for myself, I suppose. I really dislike LG's UI.
One more, unrelated to rooting, question. Does the camera work 100% with AOSP/CM ROMS? On my former phone, aosp based roms gave inferior photo quality...though there was no drivers supported for that phone(which isn't the case here). How are things with this phone? Do AOSP based ROMS give on par photos?
I'm literally blown away with photo quality on this phone, would hate to lose it in CM.
Click to expand...
Click to collapse
One of the tradeoffs of AOSP ROMs is the lack of proper camera software and proper optimisation, testing and overall knowledge. LG lacks updates but they excel in mature stock ROMs. Despite bloatware, they offer the best overall performance and battery life. With a stock (rooted & tuned) ROM you get the best experience on a LG phone.
On CM you get the latest version of Android but you miss the rest, camera sucks, USB on-the-go, wireless storage, battery life, raw performance, poor sound and call quality, poor Bluetooth connections and many other bugs.
My onest advice is to keep the stock ROM, freeze bloatware, root, custom launcher, recovery, xposed framework and proper modules, split view mod, camera mod etc.
This way I easily get 35000 in Antutu and more than 7h of screen time with heavy usage.
its dead easy to flash the D802 mate.
run ioroot with the phone plugged and usb debugging turned on follow on screen prompts no reboots or anything phone now has root. then download the cmw/twrp of your choice. the one I downloaded came with an install recovery.bat file that is almost identical to the ioroot one but installs recovery. the phone will reboot into recovery. reboot again into the rom. change the superuser app to superuserSU (chainfire) off the market place and your away.
to get into recovery you press vol down and power at the same time then when the lg logo appears you let go of power and press it again. as long as you have recovery installed when you press the power button 3 x to do a restore it will boot the recovery not do a restore. if it restores you have no recovery installed.
you sometimes need to make sure the phone is on comport 4 also... that didn't matter to me it worked perfect no matter what port I was on. I tried at least 8 just to make sure. lol.
I found when you restore stock that the rooted mark doesn't go away until you have done 2 factory restores (don't ask why it just works... for me.... every single time) cant say for anyone elses experiences though...
going back to stock is as simple but takes quite a bit of time you have to download a 2gb file to put back on the phone. just use the upgrade recovery option in the lg mobile support tool and let it do its thing.
goodmamba said:
One of the tradeoffs of AOSP ROMs is the lack of proper camera software and proper optimisation, testing and overall knowledge. LG lacks updates but they excel in mature stock ROMs. Despite bloatware, they offer the best overall performance and battery life. With a stock (rooted & tuned) ROM you get the best experience on a LG phone.
On CM you get the latest version of Android but you miss the rest, camera sucks, USB on-the-go, wireless storage, battery life, raw performance, poor sound and call quality, poor Bluetooth connections and many other bugs.
My onest advice is to keep the stock ROM, freeze bloatware, root, custom launcher, recovery, xposed framework and proper modules, split view mod, camera mod etc.
This way I easily get 35000 in Antutu and more than 7h of screen time with heavy usage.
Click to expand...
Click to collapse
twiztednibbz said:
its dead easy to flash the D802 mate.
run ioroot with the phone plugged and usb debugging turned on follow on screen prompts no reboots or anything phone now has root. then download the cmw/twrp of your choice. the one I downloaded came with an install recovery.bat file that is almost identical to the ioroot one but installs recovery. the phone will reboot into recovery. reboot again into the rom. change the superuser app to superuserSU (chainfire) off the market place and your away.
to get into recovery you press vol down and power at the same time then when the lg logo appears you let go of power and press it again. as long as you have recovery installed when you press the power button 3 x to do a restore it will boot the recovery not do a restore. if it restores you have no recovery installed.
you sometimes need to make sure the phone is on comport 4 also... that didn't matter to me it worked perfect no matter what port I was on. I tried at least 8 just to make sure. lol.
I found when you restore stock that the rooted mark doesn't go away until you have done 2 factory restores (don't ask why it just works... for me.... every single time) cant say for anyone elses experiences though...
going back to stock is as simple but takes quite a bit of time you have to download a 2gb file to put back on the phone. just use the upgrade recovery option in the lg mobile support tool and let it do its thing.
Click to expand...
Click to collapse
Rooting was a breeze, TWRP also.
I removed some bloatware with TB. Anything in specific you guys could recommend to delete(which decreases performance or drains battery)? In case I missed it.
Also, is there any mods that give worthwhile performance increase? For example I still see some lag on animations from time to time, especially while swiping between tabs on the dialer.
I miss lockscreen animation from stock
http://forum.xda-developers.com/showthread.php?t=2462905
and read the amazing discoveries in general section. you might just wanna stay stock cause awesome
revan17 said:
Rooting was a breeze, TWRP also.
I removed some bloatware with TB. Anything in specific you guys could recommend to delete(which decreases performance or drains battery)? In case I missed it.
Also, is there any mods that give worthwhile performance increase? For example I still see some lag on animations from time to time, especially while swiping between tabs on the dialer.
Click to expand...
Click to collapse
agreed its simple as pie aint it.
I found if you go into developer options and decrease the animation scales to 0.25 or 0.5 depending on rom u use it is a lot snappier and less laggy. not a fix just a way round it I spose.
bachera said:
I miss lockscreen animation from stock
http://forum.xda-developers.com/showthread.php?t=2462905
and read the amazing discoveries in general section. you might just wanna stay stock cause awesome
Click to expand...
Click to collapse
what amazing discoveries?
twiztednibbz said:
.
what amazing discoveries?
Click to expand...
Click to collapse
Its a thread in general section filled with a lot things people discovered using stock rom.
Totally worth reading. To much to sum up
Sent from my LG-D802 using xda app-developers app
bachera said:
Its a thread in general section filled with a lot things people discovered using stock rom.
Totally worth reading. To much to sum up
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
problem with the stock rom is the wifi is buggy as hell and it will not work with my router at all..
twiztednibbz said:
problem with the stock rom is the wifi is buggy as hell and it will not work with my router at all..
Click to expand...
Click to collapse
old router?
Sent from my LG-D802 using xda app-developers app
bachera said:
old router?
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
brand spanking. its a common problem as well I read. ive tried every single possible thing to make it right. the only thing that works is moving onto kit kat
Hello!
New Axon 7 owner here, since Thursday! I had a couple of questions relating to this phone and thought it would be best to ask here since i'm already familiar with XDA from previous devices. First of all, I noticed that sometimes text on the screen will occasionally appear like it is vibrating, juddering or blurring for a couple of milliseconds whilst scrolling, as the page is moving either upwards or downwards. It seems to happen at random and it does not appear to have a connection with the colours or content being displayed.
I read on one website that it might be due to the pixels in the AMOLED display turning off momentarily when black is displayed on the screen, however, it cannot be the cause of the problem in this instance because it happens when there is no black displayed, for example in Boost for Reddit which uses a colour scheme of white text on a navy-blue background. I found that the issue seems to happen more often when flicking/flinging the page to scroll, rather than keeping my finger on the screen whilst scrolling through the content.
Has anyone else experienced the same thing and can comment on whether it is normal behaviour for this device? I have not owned an AMOLED device before, and so don't know whether this is typical for devices with this type of display. It could of course be a software issue; but it strikes me as more of a hardware-related matter. I would assume it is probably completely normal, since the phone is otherwise perfect and was fully tested prior to being shipped. :fingers-crossed:
Also...
The phone came from a Chinese reseller on AliExpress who exported the phone to myself in the United Kingdom. The device is a A2017 with the China Mobile branding on the back of it, but the phone has in their words been 'converted' to A2017G spec and is running the A2017GV1.2.0B01 ROM. (MiFavor UI v4.2 based on Nougat 7.1.1) The baseband version is TH.2.0.c1.9-00104-M8996FAAAANAZM. I have checked for OTA updates but it is showing the software as fully updated. When the phone is plugged into my Windows 10 PC it shows as 'ZTE A2017G'.
I am wondering whether this 'conversation' includes anything other than switching to the A2017G Global ROM that would need to be kept in mind when modifying software on the device. Like, would it be safe to follow the usual tutorials for flashing software for the A2017, or should I be looking at tutorials for the A2017G instead?
I would like to unlock the bootloader, install TWRP, flash the latest MiFavor UI v5.0 ROM and root it with Magisk, but i'm not sure where to start with this since none of the tutorials seem to cover phones which have been 'converted' to the A2017G firmware. I saw a warning in the Axon7Toolkit thread, saying that some A2017G models may be permanently bricked when flashing packages through EDL mode due to slightly different partition tables. I don't know whether this is something I should be worried about with my A2017 since it has been converted to A2017G status.
If anyone kindly offer some further insight on either of these points, it would be most appreciated. Thanks a lot.
P650SE said:
Hello!
New Axon 7 owner here, since Thursday! I had a couple of questions relating to this phone and thought it would be best to ask here since i'm already familiar with XDA from previous devices. First of all, I noticed that sometimes text on the screen will occasionally appear like it is 'vibrating' or juddering for a matter of milliseconds whilst scrolling, as the page is moving either upwards or downwards. It seems to happen at random and it does not appear to have a connection with the colours or content being displayed.
I read on one website that it might be due to the pixels in the AMOLED display turning off momentarily when black is displayed on the screen, however, it cannot be the cause of the problem in this instance because it happens when there is no black displayed, for example in Boost for Reddit which uses a colour scheme of white text on a navy-blue background. I found that the issue seems to happen more often when flicking/flinging the page to scroll, rather than keeping my finger on the screen whilst scrolling through the content.
Has anyone else experienced the same thing and can comment on whether it is normal behaviour for this device? I have not owned an AMOLED device before, and so don't know whether this is typical for devices with this type of display. It could of course be a software issue; but it strikes me as more of a hardware-related matter. I would assume it is probably completely normal, since the phone is otherwise perfect and was fully tested prior to being shipped. :fingers-crossed:
Also...
The phone came from a Chinese reseller on AliExpress who exported the phone to myself in the United Kingdom. The device is a A2017 with the China Mobile branding on the back of it, but the phone has in their words been 'converted' to A2017G spec and is running the A2017GV1.2.0B01 ROM. (MiFavor UI v4.2 based on Nougat 7.1.1) The baseband version is TH.2.0.c1.9-00104-M8996FAAAANAZM. I have checked for OTA updates but it is showing the software as fully updated. When the phone is plugged into my Windows 10 PC it shows as 'ZTE A2017G'.
I am wondering whether this 'conversation' includes anything other than switching to the A2017G Global ROM that would need to be kept in mind when modifying software on the device. Like, would it be safe to follow the usual tutorials for flashing software for the A2017, or should I be looking at tutorials for the A2017G instead?
I would like to unlock the bootloader, install TWRP, flash the latest MiFavor UI v5.0 ROM and root it with Magisk, but i'm not sure where to start with this since none of the tutorials seem to cover phones which have been 'converted' to the A2017G firmware. I saw a warning in the Axon7Toolkit thread, saying that some A2017G models may be permanently bricked when flashing packages through EDL mode due to slightly different partition tables. I don't know whether this is something I should be worried about with my A2017 since it has been converted to A2017G status.
If anyone kindly offer some further insight on either of these points, it would be most appreciated. Thanks a lot.
Click to expand...
Click to collapse
Look, first of all, I never had that problem, but it would be best if you recorded the phone with 60fps or something so that we can see what you mean. I don't really get the thing you're talking about
You should install A2017 firmware on your phone instead of using the G firmware, because:
-You won't get OTAs
-MiFavor 5.0 is pretty damn awesome
-Maybe the screen stuff will get fixed
First of all, go to Display and try to disable "Adaptive Display" which is a good idea but really badly implemented for some reason. If the display stuff gets fixed, you may as well not RMA it, and you can install the Chinese stuff on it. You're gonna lose all your data so back it up.
First download an official ZTE update zip. I think I've sent one to someone not much ago, I'll try to find it and put the link here
Then check if there's another zip inside. If there is, get that zip out (should be called update.zip) and throw it in the root of the internal storage
Go to Settings - Updates, and see if it detects it. if it does, install it.
After having the Chinese firmware, delete the zip from your phone, and go to Updates, and see if you get any OTAs. if you get one, after it gets installed go there again, because sometimes they are just incremental (you might have to do this 2-3 times depending on which version you install via zip)
This way you don't have to unlock the phone's BL. After having MiFavor 5.0 set up, download the Google apps if you want (I recommend Google Installer apk by Xiaomi, google it) and you're good to go.
Choose an username... said:
Look, first of all, I never had that problem, but it would be best if you recorded the phone with 60fps or something so that we can see what you mean. I don't really get the thing you're talking about
You should install A2017 firmware on your phone instead of using the G firmware, because:
-You won't get OTAs
-MiFavor 5.0 is pretty damn awesome
-Maybe the screen stuff will get fixed
First of all, go to Display and try to disable "Adaptive Display" which is a good idea but really badly implemented for some reason. If the display stuff gets fixed, you may as well not RMA it, and you can install the Chinese stuff on it. You're gonna lose all your data so back it up.
First download an official ZTE update zip. I think I've sent one to someone not much ago, I'll try to find it and put the link here
Then check if there's another zip inside. If there is, get that zip out (should be called update.zip) and throw it in the root of the internal storage
Go to Settings - Updates, and see if it detects it. if it does, install it.
After having the Chinese firmware, delete the zip from your phone, and go to Updates, and see if you get any OTAs. if you get one, after it gets installed go there again, because sometimes they are just incremental (you might have to do this 2-3 times depending on which version you install via zip)
This way you don't have to unlock the phone's BL. After having MiFavor 5.0 set up, download the Google apps if you want (I recommend Google Installer apk by Xiaomi, google it) and you're good to go.
Click to expand...
Click to collapse
Thanks for the response, I appreciate you taking the time to respond to my questions. I will try to record the screen problem over the next few days just so everyone can see for themselves what is happening; it might be easier than trying to explain it. In regards to the update to MiFavor v5.0, i'm just a bit nervous about flashing stuff through the stock recovery considering the phone has already been messed about with. It would actually feel safer to flash the entire phone in MiFlash on my computer, rather than just trying to install over the A2017G firmware and hoping for the best. I wouldn't mind having to unlock the bootloader because it's what i'd like to do anyway, since i'm interested in rooting to get things like AdAway which I have used on all of my previous devices. But I will have a search around for that official update ZIP anyway and see whether i'm able to find it.
Just got what you said and tried it. You're right it blurs when I fling to scroll. But this happens on LCD screens too.
Aj-jss said:
Just got what you said and tried it. You're right it blurs when I fling to scroll. But this happens on LCD screens too.
Click to expand...
Click to collapse
Well, if someone else is also having the same issue then that would make me feel a bit better about it, assuming we are talking about the same thing of course. I will try to record a video of the problem over the next couple of days, as it would be clearer than trying to explain it in writing. I should note that the blurring effect only lasts for a few milliseconds (Less than the duration of the fling!) and it only happens once in every 20 swipes or so. But when it does happen it can be quite distracting. I have owned 4 IPS devices before this (OnePlus One, LG G4) and none of them have had scrolling behaviour like the Axon 7.
I have also found the scrolling on this phone in general to be a lot less smoother than my ZUK Z2 which uses a 5.0" IPS screen and SD820. It seems the momentum each swipe has in propelling the page vertically is a lot less effective, and thus it takes more swipes to scroll down to the end of a page. Maybe this is because the screen is 5.5" opposed to 5.0" and so, it requires longer 'flings' or swipes on the screen to make up for the additional space. But this theory seems like a long shot and it still does not explain why the scrolling in general feels so laggy and stuttery.
The thing I saw on my two phones including Axon7 happens with every fling or swipe. Maybe I didn't quite understand you . Try to record and send the video so I get what you mean.
P650SE said:
Well, if someone else is also having the same issue then that would make me feel a bit better about it, assuming we are talking about the same thing of course. I will try to record a video of the problem over the next couple of days, as it would be clearer than trying to explain it in writing. I should note that the blurring effect only lasts for a few milliseconds (Less than the duration of the fling!) and it only happens once in every 20 swipes or so. But when it does happen it can be quite distracting. I have owned 4 IPS devices before this (OnePlus One, LG G4) and none of them have had scrolling behaviour like the Axon 7.
I have also found the scrolling on this phone in general to be a lot less smoother than my ZUK Z2 which uses a 5.0" IPS screen and SD820. It seems the momentum each swipe has in propelling the page vertically is a lot less effective, and thus it takes more swipes to scroll down to the end of a page. Maybe this is because the screen is 5.5" opposed to 5.0" and so, it requires longer 'flings' or swipes on the screen to make up for the additional space. But this theory seems like a long shot and it still does not explain why the scrolling in general feels so laggy and stuttery.
Click to expand...
Click to collapse
Did you root your phone? Do you intend to? If you do, you can use the conservative governor and fix the lag entirely. Many people believe that the conservative governor is laggier than interactive, but on the SD820 that's not the case. I've tried on SD6xx and 4xx devices (the Moto G2 and G4+ namely) and this is clearly not like this on those phones.
As for the fling thing, well I'd like to see a video, since I never noticed such a thing. I'm on MiFavor 5.0 so maybe something has been changed, because this is Chinese firmware (on the G).
And I believe that you have to fling more because ZTE may have messed up with some files, as they always did... probably not because of the bigger screen
But really, change your firmware to stock A2017. It's completely possible to have Google apps on it, but retailers install the G firmware on tbe Chinese just because they sell it to the global market
Here you go: Download this, and after you have the zip, open it with a zip manager such as winrar or 7zip. If you see a PDF and an update.zip inside, pull the update.zip out and put it in the root of the internal storage, then install it via Settings - Updates. If not just put the zip you downloaded on the root if the internal storage. but i think that zip actually has the other one inside.
https://archive.org/download/A2017B1320161104135351692/A2017-B13-20161104135351692.zip
Choose an username... said:
Did you root your phone? Do you intend to? If you do, you can use the conservative governor and fix the lag entirely. Many people believe that the conservative governor is laggier than interactive, but on the SD820 that's not the case. I've tried on SD6xx and 4xx devices (the Moto G2 and G4+ namely) and this is clearly not like this on those phones.
As for the fling thing, well I'd like to see a video, since I never noticed such a thing. I'm on MiFavor 5.0 so maybe something has been changed, because this is Chinese firmware (on the G).
And I believe that you have to fling more because ZTE may have messed up with some files, as they always did... probably not because of the bigger screen
But really, change your firmware to stock A2017. It's completely possible to have Google apps on it, but retailers install the G firmware on tbe Chinese just because they sell it to the global market
Here you go: Download this, and after you have the zip, open it with a zip manager such as winrar or 7zip. If you see a PDF and an update.zip inside, pull the update.zip out and put it in the root of the internal storage, then install it via Settings - Updates. If not just put the zip you downloaded on the root if the internal storage. but i think that zip actually has the other one inside.
https://archive.org/download/A2017B1320161104135351692/A2017-B13-20161104135351692.zip
Click to expand...
Click to collapse
Thanks for the response, once again! I tried to record the scrolling problem with my DSLR camera but it was a lot harder than you'd think to capture the blurring on there. I will have to review the footage on my laptop and see whether there's anything which clearly shows the effect. But having spoke to several people about this, it is probably normal behaviour for the AMOLED panel. I think the best option for me would be like you said, to flash the stock China firmware and see whether it makes a difference to my issues with scrolling lag. If it doesn't then there's no harm done, as the phone will be much better with the China firmware anyway.
I have one question, what would be the difference between the update package you posted and the one from the official ZTE website? I noticed there is one that says '7.1 Back 6.0 ZTE_A2017V1.1.0B11 Dedicated Upgrade Package (All Network Versions)' which would presumably allow me to revert back to A2017 Marshmallow firmware with OTA updates enabled, as you explained previously. Maybe it would be better to use this one since it is dated 20/03/2017 rather than 04/11/2016. And is it definitely 100% safe to use these update packages to switch from A2017G Global firmware to A2017 China firmware?
http://www.ztedevice.com.cn/support/detail?id=B4C0ACE418834F588FED0C72D6046C78
P650SE said:
Thanks for the response, once again! I tried to record the scrolling problem with my DSLR camera but it was a lot harder than you'd think to capture the blurring on there. I will have to review the footage on my laptop and see whether there's anything which clearly shows the effect. But having spoke to several people about this, it is probably normal behaviour for the AMOLED panel. I think the best option for me would be like you said, to flash the stock China firmware and see whether it makes a difference to my issues with scrolling lag. If it doesn't then there's no harm done, as the phone will be much better with the China firmware anyway.
I have one question, what would be the difference between the update package you posted and the one from the official ZTE website? I noticed there is one that says '7.1 Back 6.0 ZTE_A2017V1.1.0B11 Dedicated Upgrade Package (All Network Versions)' which would presumably allow me to revert back to A2017 Marshmallow firmware with OTA updates enabled, as you explained previously. Maybe it would be better to use this one since it is dated 20/03/2017 rather than 04/11/2016. And is it definitely 100% safe to use these update packages to switch from A2017G Global firmware to A2017 China firmware?
http://www.ztedevice.com.cn/support/detail?id=B4C0ACE418834F588FED0C72D6046C78
Click to expand...
Click to collapse
Well, the package that you found will do too. Most people here expect everything to be done for them, and since I had already found a zip, I thought it would be best to share it at least.
You should actually follow the guide that I just posted - the reason why is that you have to unzip the file and put it in the root of the SD card. It's written so that everyone can understand, so sorry if it's too dense. but if you downloaded the package on the PC (and your phone is somehow able to connect via MTP [or FTP, i have to use this] to your PC) it's just unzip and send.
Choose an username... said:
Well, the package that you found will do too. Most people here expect everything to be done for them, and since I had already found a zip, I thought it would be best to share it at least.
You should actually follow the guide that I just posted - the reason why is that you have to unzip the file and put it in the root of the SD card. It's written so that everyone can understand, so sorry if it's too dense
Click to expand...
Click to collapse
Haha, no problem at all. I will try it and see what happens, but unfortunately the download might take a few hours due to my slow internet connection. Thanks for all your assistance so far, it is of course most appreciated. BTW, I just booted into the bootloader to see what it looked like and everything is displayed in Chinese; which presumably is normal considering the phone is the Chinese A2017 model. At the top of the screen it shows ZTE/P996A03_N/ailsa_ii and another line which says 7.1.1/NMF26V/20170425.120141. What do these numbers mean? I know 7.1.1 is the version of Android and 'ailsa_ii' is of course the codename of the device, like 'bacon' is for the OnePlus One.
P650SE said:
Haha, no problem at all. I will try it and see what happens, but unfortunately the download might take a few hours due to my slow internet connection. Thanks for all your assistance so far, it is of course most appreciated. BTW, I just booted into the bootloader to see what it looked like and everything is displayed in Chinese; which presumably is normal considering the phone is the Chinese A2017 model. At the top of the screen it shows ZTE/P996A03_N/ailsa_ii and another line which says 7.1.1/NMF26V/20170425.120141. What do these numbers mean? I know 7.1.1 is the version of Android and 'ailsa_ii' is of course the codename of the device, like 'bacon' is for the OnePlus One.
Click to expand...
Click to collapse
You sure you booted to the bootloader? Most phones have it blocked and you can only access recovery, EDL and FTM.
Whatever, yeah, the Chinese recovery is in Chinese. G's and U's have it in English. But still, the option that you may need to use is the one that says 'sd' between some Chinese ideograms (install update from sd card). Ofc you'd need an SD card for that, that's why using the system option to update is preferred.
Choose an username... said:
You sure you booted to the bootloader? Most phones have it blocked and you can only access recovery, EDL and FTM.
Whatever, yeah, the Chinese recovery is in Chinese. G's and U's have it in English. But still, the option that you may need to use is the one that says 'sd' between some Chinese ideograms (install update from sd card). Ofc you'd need an SD card for that, that's why using the system option to update is preferred.
Click to expand...
Click to collapse
Ah, that's interesting! I'm certain it was the bootloader since I followed a tutorial on YouTube to access it. Basically, all I had to do was to switch the phone off and then hold both the volume-up and power buttons until the ZTE logo appeared, then release the power button and keep holding the volume button until the bootloader came up! Anyhow, i'll definitely follow your advice and use the update method via the settings menu in MiFavor. But first I will have to wait another hour for the update package to finish downloading, as my internet speed is only 3.3Mbps!
P650SE said:
Haha, no problem at all. I will try it and see what happens, but unfortunately the download might take a few hours due to my slow internet connection. Thanks for all your assistance so far, it is of course most appreciated. BTW, I just booted into the bootloader to see what it looked like and everything is displayed in Chinese; which presumably is normal considering the phone is the Chinese A2017 model. At the top of the screen it shows ZTE/P996A03_N/ailsa_ii and another line which says 7.1.1/NMF26V/20170425.120141. What do these numbers mean? I know 7.1.1 is the version of Android and 'ailsa_ii' is of course the codename of the device, like 'bacon' is for the OnePlus One.
Click to expand...
Click to collapse
My phone is A2017 too. This screenshot might help you understand those numbers.
^^^Ah, that's cool. So P996A03_N is basically just further identification for the device to indicate it is the Chinese A2017 version.
At the moment i'm having problems with the ZIP for rolling back to Marshmallow. It came packaged in an archive called 20170320111600705.zip which I extracted using WinRAR on my laptop. I copied the update.zip file to the root of my internal storage and to the root of the SD card, but neither are recognised when entering the 'System Update' screen. Is it possible that the reseller on AliExpress blocked the ability to update the ROM? I don't know whether to try running the update directly from the bootloader instead.
On the AliExpress listing for the phone is has a warning which says 'Please do not try to flash the phone by yourself. Otherwise your phone will be blocked and lose the network'. I assume this is just to discourage people from flashing custom ROMs to their devices rather than an actual physical limitation.
P650SE said:
^^^Ah, that's cool. So P996A03_N is basically just further identification for the device to indicate it is the Chinese A2017 version.
At the moment i'm having problems with the ZIP for rolling back to Marshmallow. It came packaged in an archive called 20170320111600705.zip which I extracted using WinRAR on my laptop. I copied the update.zip file to the root of my internal storage and to the root of the SD card, but neither are recognised when entering the 'System Update' screen. Is it possible that the reseller on AliExpress blocked the ability to update the ROM? I don't know whether to try running the update directly from the bootloader instead.
On the AliExpress listing for the phone is has a warning which says 'Please do not try to flash the phone by yourself. Otherwise your phone will be blocked and lose the network'. I assume this is just to discourage people from flashing custom ROMs to their devices rather than an actual physical limitation.
Click to expand...
Click to collapse
Okay, then you'll have to use the recovery. Put the zip on the SD card (I guess you already have it there), turn it off and hold power + vol up. Select the option that says sd and select the zip.
I guess it doesn't work because it detected that the zip was for an A2017 and it thinks it's a G
Choose an username... said:
Okay, then you'll have to use the recovery. Put the zip on the SD card (I guess you already have it there), turn it off and hold power + vol up. Select the option that says sd and select the zip.
I guess it doesn't work because it detected that the zip was for an A2017 and it thinks it's a G
Click to expand...
Click to collapse
Ah. Good thinking about the reason it wasn't working! Although, I tried that and underneath where it says Supported API: 3, it shows a message which says 'Sorry, you can't sdcard upgrade'.
EDIT: Oh, wait a second. I remember reading something which said you should enable OEM unlocking before trying to flash the ZIP. Maybe that would work!
EDIT 2: Well, that seems to have worked. I was so scared! But the ZIP flashed successfully and it has rebooted into A2017V1.0.0B13 MiFavor UI v4.0 (Android 6.0.1) I noticed the bootloader screen is now slightly different as it now shows the Chinese symbol next to the ZTE text. It is now showing an OTA update to V1.0.0B15, so i'll start by doing that and work through all the other OTA's until I reach the latest version!
Check the edit to my previous post. I managed to get the phone onto A2017V1.0.0B13 and then OTA updated to A2017V1.0.0B15, but unfortunately there are no further OTA updates available from this point. So with this in mind, the next step would probably be to download the A2017V1.1.0B17 archive from the same source and flash that using the same method, via the bootloader? Then hopefully that should bump me back up to Nougat and allow me to OTA to the latest version of MiFavor. (v5.0)
http://www.ztedevice.com.cn/support/detail?id=B4C0ACE418834F588FED0C72D6046C78
P650SE said:
Check the edit to my previous post. I managed to get the phone onto A2017V1.0.0B13 and then OTA updated to A2017V1.0.0B15, but unfortunately there are no further OTA updates available from this point. So with this in mind, the next step would probably be to download the A2017V1.1.0B17 archive from the same source and flash that using the same method, via the bootloader? Then hopefully that should bump me back up to Nougat and allow me to OTA to the latest version of MiFavor. (v5.0)
http://www.ztedevice.com.cn/support/detail?id=B4C0ACE418834F588FED0C72D6046C78
Click to expand...
Click to collapse
Nah, I think you already can use the inbuilt update function. Now that you are on A2017 firmware it should find the zip easily.
The 'bootloader mode' you are referring to is actually the recovery. The bootloader mode is the one on the picture. You can access to it by using adb, and issuing 'adb reboot bootloader', but you might not have it (in which case the phone will just boot to system)
To unlock the bootloader you need to get fastboot on the phone AFAIK, so that's what the axon7toolkit does, it flashes stuff through MiFlash to get fastboot operational. Google it, it's pretty good; if you ever want to unlock, I think it's the way to go.
Just to get everything clear.
Choose an username... said:
Nah, I think you already can use the inbuilt update function. Now that you are on A2017 firmware it should find the zip easily.
The 'bootloader mode' you are referring to is actually the recovery. The bootloader mode is the one on the picture. You can access to it by using adb, and issuing 'adb reboot bootloader', but you might not have it (in which case the phone will just boot to system)
To unlock the bootloader you need to get fastboot on the phone AFAIK, so that's what the axon7toolkit does, it flashes stuff through MiFlash to get fastboot operational. Google it, it's pretty good; if you ever want to unlock, I think it's the way to go.
Just to get everything clear.
Click to expand...
Click to collapse
Whoops! I have no idea why I kept referring to it as the bootloader, maybe because i've become so used to using TWRP on my ZUK Z2 for almost a year and ended up forgetting what a manufacturers stock recovery looked like! That was a very silly mistake. :laugh:
I haven't been able to get an update to Nougat to appear via OTA in the 'System Update' menu, so instead I will download the update package from the ZTE website and see whether that works. I believe once I have updated to V1.1.0B17 via ZIP it should allow me to OTA to the latest version of MiFavor. Thanks for the tips regarding Axon7Toolkit, I already had it installed on my laptop but didn't know about possibly having to enable the bootloader with MiFlash. That is very interesting!
P650SE said:
Whoops! I have no idea why I kept referring to it as the bootloader, maybe because i've become so used to using TWRP on my ZUK Z2 for almost a year and ended up forgetting what a manufacturers stock recovery looked like! That was a very silly mistake. :laugh:
I haven't been able to get an update to Nougat to appear via OTA in the 'System Update' menu, so instead I will download the update package from the ZTE website and see whether that works. I believe once I have updated to V1.1.0B17 via ZIP it should allow me to OTA to the latest version of MiFavor. Thanks for the tips regarding Axon7Toolkit, I already had it installed on my laptop but didn't know about possibly having to enable the bootloader with MiFlash. That is very interesting!
Click to expand...
Click to collapse
Literally you have to get B17 update through OTA when you're on B15. I did, but the reasons you're not is that you or your reseller have converted it to G model. My friend who also had a Chinese Axon 7 and converted it to G had this problem too. And I don't know what to do about it.
---------- Post added at 03:09 AM ---------- Previous post was at 03:06 AM ----------
And I also think that you had to flash B13 upgrade package(second downloadable zip on ZTE website) because B11 was the same B13 but the rollback version meaning for somebody who is already on Nougat and wants to go back to Marshmallow.
Hey, was big into the android scene years ago, switched to other platforms for a bit just to play with them. Got a used 64 gig 6p and was thinking about dropping a custom rom onto it, but I don't know what's good anymore. What's the most stable, daily driver, minimalist rom out there? Wouldn't mind SOME extra features like task/notification bar customization and things like that. Stability and rock solid performance with great battery life are the concerns. Thank you!
GunnermanBill said:
Hey, was big into the android scene years ago, switched to other platforms for a bit just to play with them. Got a used 64 gig 6p and was thinking about dropping a custom rom onto it, but I don't know what's good anymore. What's the most stable, daily driver, minimalist rom out there? Wouldn't mind SOME extra features like task/notification bar customization and things like that. Stability and rock solid performance with great battery life are the concerns. Thank you!
Click to expand...
Click to collapse
I'm running f2fs file system with ABC oreo build & superUber kernel. I'm on latest radio & bootloader from 8.1. it has been pretty solid. I was on Pure Nexus nougat & Flash kernel; this set-up is tried & true. The Superxe ROM is aroma based and has 8.1 preview although I haven't got to try it yet. Hopefully this might point you in the right direction; there is a f2fs twrp build(s) in the 6p development thread if your interested.
Samuel Holland said:
I'm running f2fs file system with ABC oreo build & superUber kernel. I'm on latest radio & bootloader from 8.1. it has been pretty solid. I was on Pure Nexus nougat & Flash kernel; this set-up is tried & true. The Superxe ROM is aroma based and has 8.1 preview although I haven't got to try it yet. Hopefully this might point you in the right direction; there is a f2fs twrp build(s) in the 6p development thread if your interested.
Click to expand...
Click to collapse
Awesome reply, thank you for the heads up. F2FS is new to me, I'm guessing
https://forum.xda-developers.com/ne...recovery-twrp-2-8-7-0-touch-recovery-t3234976
is the thread you were talking about? I need to get it bootloader unlocked and rooted still, i'll probably tackle it when i get home and drop that version of TWRP onto it. Thanks again!
so it looks like the tools like Wug's are all very outdated, are they safe to use anyway on my device that has all the latest stock stuff? like 8.0 and my version aren't listed in Wug's at all.
GunnermanBill said:
Awesome reply, thank you for the heads up. F2FS is new to me, I'm guessing
https://forum.xda-developers.com/ne...recovery-twrp-2-8-7-0-touch-recovery-t3234976
is the thread you were talking about? I need to get it bootloader unlocked and rooted still, i'll probably tackle it when i get home and drop that version of TWRP onto it. Thanks again!
Click to expand...
Click to collapse
Here's the link to the unofficial twrp for 6p with f2fs support. Don't forget to check the box in twrp "Use rm -rf instead of formatting" after changing data and cache to f2fs. Make sure your rom and kernel support f2fs with kernel being mandatory for best results. Here's the link:
https://forum.xda-developers.com/nexus-6p/development/unofficial-twrp-3-0-3-x-f2fs-support-t3543450
---------- Post added at 12:27 PM ---------- Previous post was at 12:15 PM ----------
GunnermanBill said:
so it looks like the tools like Wug's are all very outdated, are they safe to use anyway on my device that has all the latest stock stuff? like 8.0 and my version aren't listed in Wug's at all.
Click to expand...
Click to collapse
I'm sure that unlocking the phone with the toolkit is safe. It's the method I used. Also in the link above or in the 6p section it should have any info you may need. You can flash recovery by vol dn & power button into bootloader(fastboot), and once you "cd /path tofolder with recovery image/" & "fastboot devices" to make sure you can see your 6p and drivers are installed correctly, you can rename twrp.img to recovery.img & they command is:
fastboot flash recovery recovery.img
I recommend going to xda 6p section; general, & questions, & answers & reading up on everything just to be on the safe side and very important; make backup at all times just to make sure if there is a "booboo" you can easily restore. If you need adb & fastboot installed, there is a thread here on xda "15 sec adb & fastboot installer".
I hope this could help and I hope you enjoy as much as I have.
Latest ROMs which gives me good performance and battery life are paranoid (still nougat, but always a winner), latest 8.1 with pixel 2 mod and aicp rom with kernvatore kernel.
Buying a 6P for good battery life may have been a mistake...
gman88667733 said:
Buying a 6P for good battery life may have been a mistake...
Click to expand...
Click to collapse
Battery life on stock has been as good as my iPhones 6s. Does charge slower though, even when it's rapid.
GunnermanBill said:
Hey, was big into the android scene years ago, switched to other platforms for a bit just to play with them. Got a used 64 gig 6p and was thinking about dropping a custom rom onto it, but I don't know what's good anymore. What's the most stable, daily driver, minimalist rom out there? Wouldn't mind SOME extra features like task/notification bar customization and things like that. Stability and rock solid performance with great battery life are the concerns. Thank you!
Click to expand...
Click to collapse
Clockwork mod is no more, TWRP is the new standard recovery.
Nexus/Pixel line by google gives you the minimalistic ROM you would need,ie. stock ROM :laugh:
Try stock rom for a while. Heck, i got so used to stock , I havent rooted my phone since ages. Atm i have moved on to pixel, and i am perfectly comfortable with stock ROM. I guess custom ROMs only attracted me when i had devices whose software cycle were abandoned by their OEM's.
NoobInToto said:
Clockwork mod is no more, TWRP is the new standard recovery.
Nexus/Pixel line by google gives you the minimalistic ROM you would need,ie. stock ROM :laugh:
Try stock rom for a while. Heck, i got so used to stock , I havent rooted my phone since ages. Atm i have moved on to pixel, and i am perfectly comfortable with stock ROM. I guess custom ROMs only attracted me when i had devices whose software cycle were abandoned by their OEM's.
Click to expand...
Click to collapse
Just now finally rooted etc. My issue with stock was it would crash and reboot sometimes when unlocking it while something was playing over bluetooth. Not going nuts with advanced feature roms, but honestly at this point trust the devs here over the crazies that Google hires these days. Just keeping it safe simple and solid.
You should try the SuperXE Custom ROM on 8.0 with the Pixel 2 features/addons. You should also give PureNexus a try, if you're not so satisfied with Oreo just yet. I'm currently running the Android 8.1 developer preview and I love it, the battery life is great and the ROM is fluid with little bugs.
alright, i thought i had rooted, i guess not. I'm unlocked, i used wug's to root, but it's not sticking. I don't have super user, and i cannot boot into recovery without using ADB. If recovery is selected from the bootloader menu it just brings me to the default android recovery with no options and I have to hold the power button down. I've tried manually flashing the recovery via fastboot and it's the same story. I tried booting into twrp via fastboot and flashing the superuser zip there but it's not in my app drawer. Everything seems to be successful when the operations are running. What gives?
GunnermanBill said:
alright, i thought i had rooted, i guess not. I'm unlocked, i used wug's to root, but it's not sticking. I don't have super user, and i cannot boot into recovery without using ADB. If recovery is selected from the bootloader menu it just brings me to the default android recovery with no options and I have to hold the power button down. I've tried manually flashing the recovery via fastboot and it's the same story. I tried booting into twrp via fastboot and flashing the superuser zip there but it's not in my app drawer. Everything seems to be successful when the operations are running. What gives?
Click to expand...
Click to collapse
the recovery does not stick on stock ROM if you don't flash either supersu or magisk. So you need to put the .zip of either one of those on your phone, then boot to bootloader and fastboot flash the recovery. Next, you boot into the recovery and flash the zip that you put on your phone.
you are now rooted, and your recovery will stick.
I'm currently on stock 8.0 waiting for paranoid android 8.0 update
knevelsg-j said:
the recovery does not stick on stock ROM if you don't flash either supersu or magisk. So you need to put the .zip of either one of those on your phone, then boot to bootloader and fastboot flash the recovery. Next, you boot into the recovery and flash the zip that you put on your phone.
you are now rooted, and your recovery will stick.
I'm currently on stock 8.0 waiting for paranoid android 8.0 update
Click to expand...
Click to collapse
I had flashed the super user zip in the wug kit myself while in TWRP but it still didn't stick. I mentioned that previously but i said a lot of other stuff too i'm not suprised you missed it. I guess I'm probably flashing the wrong SU and will look for another.
edit - grabbed the latest stable super user and it seems good now
What's this vendor image that's a thing now? You have to be tethered to a PC to flash most roms due to it nowadays it seems. Radios used to come in zips i could flash in twrp as well, what happened to that?
Hello,
Can someone help me with some instructions to install twrp and then flash either stock rom or custom rom. I want to have twrp as the recovery so i can flash things in the future and also make twrp backups.
Im running stock 8.1 beta with unlocked bootloader
I know there are guides out there but all of them are 2-3 months old. Since then we've had the 8.1 beta.
Any help will be much appreciated.
ZAFAR- said:
Hello,
Can someone help me with some instructions to install twrp and then flash either stock rom or custom rom. I want to have twrp as the recovery so i can flash things in the future and also make twrp backups.
Im running stock 8.1 beta with unlocked bootloader
I know there are guides out there but all of them are 2-3 months old. Since then we've had the 8.1 beta.
Any help will be much appreciated.
Click to expand...
Click to collapse
You can't.
There is no TWRP for 8.1 so it isn't possible.
This phone has no traditional recovery. Recovery is part of boot.
That means that the boot image needs to be patched for tarp and still be able to boot the system.
Currently, or at least until 8.1 is no longer beta you will not see a tarp that can stay permanently and coexist with 8.1.
ZAFAR- said:
Hello,
Can someone help me with some instructions to install twrp and then flash either stock rom or custom rom. I want to have twrp as the recovery so i can flash things in the future and also make twrp backups.
Im running stock 8.1 beta with unlocked bootloader
I know there are guides out there but all of them are 2-3 months old. Since then we've had the 8.1 beta.
Any help will be much appreciated.
Click to expand...
Click to collapse
If you wanna flash a custom ROM, you can use TWRP (LOS 15.1 and AOSIP are both 8.1 ROMs that can be flashed with TWRP), but I suggest you get very comfortable with ADB and fastboot BEFORE you wipe your phone. As Tech_head said, TWRP gets flashed to the boot, not recovery, so you have to flash TWRP with fastboot each time you want to boot into it, it won't stick.
This phone is not real friendly for flashaholics. Also, be prepared to lose EVERYTHING on your phone if you start flashing custom ROMs, because if you start having problems or want to flash back to stock, you're going to need to wipe all your data (fastboot -w) (this wipes all your media too!). In fact, if you want to flash a custom ROM, you should wipe everything anyway, and don't count on TWRP being able to complete a nandroid backup or restore one. I haven't been able to once. Good luck, this phone's a *****!
Airwolf79, I am a "semi" flashaholic.. I flash updates and different roms, sometimes three or four times a week. I have always used twrp and titanium backup to do so, which makes it very easy to do so. Essential does not let you use this process? That is the gist of what I have been getting on these essential threads.
When you said it was a "b***h", is that a good or bad thing?, I'm an old guy and really don't understand your meaning. I was about ready (and may still) pull the trigger on this phone. But, I need to know what I am getting into..
I want to get a good rootable phone (Verizon), but they are getting very pricey if I go off contract (lg v30, pixel 2).
I really am not understanding the "adb", "fast boot", and"side load" process. Is it that much more of a difficult or time consuming process than using twrp?
Is the use of a computer mandatory?
Thx.
gimpy1 said:
Airwolf79, I am a "semi" flashaholic.. I flash updates and different roms, sometimes three or four times a week. I have always used twrp and titanium backup to do so, which makes it very easy to do so. Essential does not let you use this process? That is the gist of what I have been getting on these essential threads.
When you said it was a "b***h", is that a good or bad thing?, I'm an old guy and really don't understand your meaning. I was about ready (and may still) pull the trigger on this phone. But, I need to know what I am getting into..
I want to get a good rootable phone (Verizon), but they are getting very pricey if I go off contract (lg v30, pixel 2).
I really am not understanding the "adb", "fast boot", and"side load" process. Is it that much more of a difficult or time consuming process than using twrp?
Is the use of a computer mandatory?
Thx.
Click to expand...
Click to collapse
Its not that Essential is blocking any development of TWRP. Development for this phone, and all A/B partition phones for that matter, are really minimal right now, but especially the Essential because so few units were sold. Until Project Treble really gets going and more manufacturers start shipping A/B partition devices, you won't see much development for this phone. Eventually, someone will solve the issues with TWRP, but I doubt well ever see a lot of custom ROMs. When I say this phone's a *****, it's because of the issues with TWRP more than anything. Dirty flashing isn't working for me on AOSIP, Nandroid backups don't work, and flashing firmware can only be done using fastboot AFAIK (yes, with a computer). If you're not computer savvy, then you better pass on this phone if you want to run custom ROMs. It's a great phone even stock though, so up to you if you can settle for stock or u wanna learn more about ADB and fastboot, it's worth it IMO. If u want a phone recent that has good development, go with the OnePlus 5T, but even that phone can be a bit tricky for flashing, as I said, TWRP is not very compatible with Oreo 8.1 yet for any phone. You have to disable your pin/fingerprint each time you boot TWRP because they haven't figured out how to decrypt 8.1 yet. This is all common knowledge if you follow the development threads for these phones. The old days of flashing five ROMs in a day are over man, at least for the time being.
gimpy1 said:
Airwolf79, I am a "semi" flashaholic.. I flash updates and different roms, sometimes three or four times a week. I have always used twrp and titanium backup to do so, which makes it very easy to do so. Essential does not let you use this process? That is the gist of what I have been getting on these essential threads.
When you said it was a "b***h", is that a good or bad thing?, I'm an old guy and really don't understand your meaning. I was about ready (and may still) pull the trigger on this phone. But, I need to know what I am getting into..
I want to get a good rootable phone (Verizon), but they are getting very pricey if I go off contract (lg v30, pixel 2).
I really am not understanding the "adb", "fast boot", and"side load" process. Is it that much more of a difficult or time consuming process than using twrp?
Is the use of a computer mandatory?
Thx.
Click to expand...
Click to collapse
A) LG phones are not root friendly. Only certain SKUs of any model (1 in maybe 8) can even bootloader unlock. Indeed, even rooting is problematic and only the result of security "flaws". If you are a flash-a-holic, you definitely don't want an LG. Or a Samsung, or any phone sold with carrier-specific hardware or firmware....IIRC the Samsung S8 took a calendar year to root.
B) The technical hurdle here on the Essential is also present on Pixel phones. Getting a Pixel will not free you from this.
The A/B partition scheme and boot layout is shared by Pixel and Essential. The easy flashing processes went away with the Nexus program. A/B isn't that bad-but you must learn fastboot and ADB commands. There aren't a whole lot of common one you really need, but you need familiarity with the toolset.
Thx, I will do some googling and reading.
The easiest way i found is to flash TWRP, Flash dump for your phone, then flash 8.1 boot.img so it don't bootloop. The recovery won't stay but you will be stock.
Download the dump for your phone from there
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
So flash TWRP
Flash dump from internal sd
flash stock boot image
gimpy1 said:
Airwolf79, I am a "semi" flashaholic.. I flash updates and different roms, sometimes three or four times a week. I have always used twrp and titanium backup to do so, which makes it very easy to do so. Essential does not let you use this process? That is the gist of what I have been getting on these essential threads.
When you said it was a "b***h", is that a good or bad thing?, I'm an old guy and really don't understand your meaning. I was about ready (and may still) pull the trigger on this phone. But, I need to know what I am getting into..
I want to get a good rootable phone (Verizon), but they are getting very pricey if I go off contract (lg v30, pixel 2).
I really am not understanding the "adb", "fast boot", and"side load" process. Is it that much more of a difficult or time consuming process than using twrp?
Is the use of a computer mandatory?
Thx.
Click to expand...
Click to collapse
I mean no offense by this at all but one would think even a "semi-flashoholic" would be fairly well versed with Fastboot and ADB. Im curious how you have much experience with twrp if you dont know what those two things mean. Unless of course youre coming from an S3 or something and especially someone thats on verizons network. Theyve been pretty famously against unlocking bootloaders since i can remember. Also, it doesnt matter if youre buying off contract or get your phone through your carrier. Youre going to pay the same price in the long run either which way, and contrary to many believers that are stuck in that mind set of "they used to give free phones away or at most like $200" you were still paying the full 699.99-899.99 as you are now days . so my suggestion, buy straight from the source (google, lg, samsung, or even off amazon) and pay with a credit card because especially if you have a zero interest for x amount of time its going to be cheaper in most cases and you dont have to have that out of pocket cash for taxes on the device to pay that day. Ive worked for 3 out of 4 of the top carriers in my life and trust me, its the way to go. Also yes if you are looking for a root friendly phone to flash away on, this thing is not going to be your best choice either. Kick ass phone but not very developer/flash friendly.
Well, after considerable thought, I finally decided against going with the Essential or any unlocked bl.
I just received my LG (vs996) from Verizon day before yesterday.
gimpy1 said:
Well, after considerable thought, I finally decided against going with the Essential or any unlocked bl.
I just received my LG (vs996) from Verizon day before yesterday.
Click to expand...
Click to collapse
Good luck with that...just dumped my v20. LG can suck it.
Well, to each his own, I guess.
Pretty nice phone, but, in still learning to do things without root.
gimpy1 said:
Well, to each his own, I guess.
Pretty nice phone, but, in still learning to do things without root.
Click to expand...
Click to collapse
No root is the least of it...stuck on 7.0.0 forever, and its first and likely last os upgrade isn't likely to come until June 2018 at the soonest.
Pathetic for a supposed flagship.
I was an excited fool, and paid new retail at release. Never again am I buying an LG
Mine came with 8.0 (from Verizon).
gimpy1 said:
Mine came with 8.0 (from Verizon).
Click to expand...
Click to collapse
Oh that is right. I was confusing vs995 and vs996. Oh well.