Related
So i am running TWRP and kitkat
i Flashed 2 different lollipop roms both run sluggish and all my downloads in the play store only go half way and just hang and stop
i also can no longer get my PC to see my phone as a storage device to transfers files ...
what is goin on ?????
You didn't clean flash
Sent from my Android 5.0 Nexus 5
you probably didnt clean flash
you probably didnt let it fully sync
you probably didnt flash gapps right (or the right gapps)
first boot on custom roms can be sluggish as it runs a lot of background syncing with google and so, let it play for a while
and by the time you booted 2 l roms, your phone was already hot enough to thermal throtle kick in, so it was running probably at max of 1.1ghz
opssemnik said:
you probably didnt clean flash
you probably didnt let it fully sync
you probably didnt flash gapps right (or the right gapps)
first boot on custom roms can be sluggish as it runs a lot of background syncing with google and so, let it play for a while
and by the time you booted 2 l roms, your phone was already hot enough to thermal throtle kick in, so it was running probably at max of 1.1ghz
Click to expand...
Click to collapse
i have to disagree
i am no noob to flashing and i followed both instructions for both roms
they both do the same thing in the app store... apps download halfway and just get stuck
See logcat.
Hello there, I have bought Wikipad WPT500 recetly, updated it and managed to set boot.img as insecure and root completely. Thing is, it's quite old already, so I would like to OC kernel a bit or at least install twrp. It has potential, that's for sure. Thing is, there's no source available. I;ve contacted dev team from them but no response.
Does anyone know the way to modify kernel (OC it, i know there's no way to add schedulers or governonrs without sources) or compile TWRP without sources, based on stock images ?
After several weeks of battling terrible battery drain, lag and sluggish performance I am back on Stock Nougat, build number NPJS25.93-14-8. With moderate use, my battery is now averaging less than 2% per hour ( < 1% while sleeping), where on the custom ROM of choice it was running over 5% per hour, even while sleeping. I tried every trick and tweak I could find and Better Battery Stats didn't show anything that could account for the high drain. I even tried a different ROM to no avail. So I threw in the towel, returned to stock, and did the latest OTA updates. I am now running rooted with ElementalX kernel 1.04 and I couldn't be more pleases with the overall performance and battery life.
I am sure it was something I missed but I got tired of spending hours trying to get back to the original performance and battery life the custom ROM had several weeks ago. Sometimes you just gotta do what you gotta do.
While ota updates.......i brought to twrp only.... instead of installing latest security update.......... manually tried to install update...bt i can't..... gets an error... didn't u faced such problems
Harshseth said:
While ota updates.......i brought to twrp only.... instead of installing latest security update.......... manually tried to install update...bt i can't..... gets an error... didn't u faced such problems
Click to expand...
Click to collapse
None of STOCK ROM or OTA updates can be flashed/updated by TWRP, you need to be on stock recovery as well everything stock (unmodified system, boot and all).
I faced this problem too, but I fixed mostly of the battery drain tweaking the kernel with the ElementalX app to ~0,80/h. I had to set the little cores working like big cores do, because all little cores and one big were in use always; and applied LightingBlade profile.
Harshseth said:
While ota updates.......i brought to twrp only.... instead of installing latest security update.......... manually tried to install update...bt i can't..... gets an error... didn't u faced such problems
Click to expand...
Click to collapse
In order to use the OTA path you have to be on stock recovery, boot and kernel, not on TWRP. Otherwise you get the error that you experienced.
xAnkris said:
I faced this problem too, but I fixed mostly of the battery drain tweaking the kernel with the ElementalX app to ~0,80/h. I had to set the little cores working like big cores do, because all little cores and one big were in use always; and applied LightingBlade profile.
Click to expand...
Click to collapse
I went that path but it didn't seem to help much. Besides, I am happy with this stock setup. It is much better than when I was on Marshmallow stock and went over to custom ROMs. I can do anything I want to do and install any app I desire to use. Good performance, great battery life, and customizable as much as I want. No need to be on custom.
pastorbob62 said:
After several weeks of battling terrible battery drain, lag and sluggish performance I am back on Stock Nougat, build number NPJS25.93-14-8. With moderate use, my battery is now averaging less than 2% per hour ( < 1% while sleeping), where on the custom ROM of choice it was running over 5% per hour, even while sleeping. I tried every trick and tweak I could find and Better Battery Stats didn't show anything that could account for the high drain. I even tried a different ROM to no avail. So I threw in the towel, returned to stock, and did the latest OTA updates. I am now running rooted with ElementalX kernel 1.04 and I couldn't be more pleases with the overall performance and battery life.
I am sure it was something I missed but I got tired of spending hours trying to get back to the original performance and battery life the custom ROM had several weeks ago. Sometimes you just gotta do what you gotta do.
Click to expand...
Click to collapse
Are you able to root the stock nougat build npjs25 14-8.?
If yes how you rooted your phone. Plzz guide me. I also want to root my stock nougat
ADITYA_KUMAR said:
Are you able to root the stock nougat build npjs25 14-8.?
If yes how you rooted your phone. Plzz guide me. I also want to root my stock nougat
Click to expand...
Click to collapse
Before you can root stock Nougat you must first unlock you bootloader, install TWRP then flash Elemental X kernel 1.04 from TWRP.
pastorbob62 said:
Before you can root stock Nougat you must first unlock you bootloader, install TWRP then flash Elemental X kernel 1.04 from TWRP.
Click to expand...
Click to collapse
What is elemental x kernel. I have a unlocked bootloader.
ADITYA_KUMAR said:
What is elemental x kernel. I have a unlocked bootloader.
Click to expand...
Click to collapse
Instead of asking questions that have been answered numerous times (ad nauseam) you should try reading through the forums. I realize you are a raw noob, but if you wanted to learn Calculus, would you ask a bunch of questions without doing any reading and studying? It's no different when you are modifying your smart phone.
Here is a link to a thread that will guide you to rooting stock Nougat. It works for all versions of stock Nougat.
https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
But don't do anything until you have read through the procedures and fully understand. Above all, make a backup of your system from TWRP before you do anything else.
pastorbob62 said:
Instead of asking questions that have been answered numerous times (ad nauseam) you should try reading through the forums. I realize you are a raw noob, but if you wanted to learn Calculus, would you ask a bunch of questions without doing any reading and studying? It's no different when you are modifying your smart phone.
Here is a link to a thread that will guide you to rooting stock Nougat. It works for all versions of stock Nougat.
https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
But don't do anything until you have read through the procedures and fully understand. Above all, make a backup of your system from TWRP before you do anything else.
Click to expand...
Click to collapse
once I tried to root on stock nogut, so I installed TWRP and flashed SuperSu and my phone got bricked
pastorbob62 said:
After several weeks of battling terrible battery drain, lag and sluggish performance I am back on Stock Nougat, build number NPJS25.93-14-8. With moderate use, my battery is now averaging less than 2% per hour ( < 1% while sleeping), where on the custom ROM of choice it was running over 5% per hour, even while sleeping. I tried every trick and tweak I could find and Better Battery Stats didn't show anything that could account for the high drain. I even tried a different ROM to no avail. So I threw in the towel, returned to stock, and did the latest OTA updates. I am now running rooted with ElementalX kernel 1.04 and I couldn't be more pleases with the overall performance and battery life.
I am sure it was something I missed but I got tired of spending hours trying to get back to the original performance and battery life the custom ROM had several weeks ago. Sometimes you just gotta do what you gotta do.
Click to expand...
Click to collapse
Very true.
Also try LightningBlade tunables(v 1.2.3 ; the newer version does not work that well for me..).
Stock rom provides the best balance between Performance and Battery life.
siddhesh9146 said:
once I tried to root on stock nogut, so I installed TWRP and flashed SuperSu and my phone got bricked
Click to expand...
Click to collapse
If you're rooting on stock Nougat, you must have a custom kernel flashed (or used the temporary dm-verity disabler on the stock kernel) before you root. Else, without the mentioned modifications, you'll trip the anti-rooting protection built into the stock kernel, and you'll have bootloops unless you reflash your stock ROM as you experienced.
Easiest way, as per the guide is to:
Flash/boot TWRP.
Backup.
Flash ElementalX or vegito (any custom kernel will do, as these kernels do not have the anti-rooting protection).
Reboot to test.
Boot back to TWRP
Flash SuperSU v2.79 or newer, or magisk 13 or newer
Reboot.
You should be rooted, on stock, and if you've flashed magisk, Safetynet should be working It's working well on NPJS25.93-14-8 and it's stable. Granted, a few apps now seem to detect root/magisk (and fail to download/update from the Play Store, with an error 0), but nothing that a sideload from a legitimate source wouldn't solve...
champsp said:
Very true.
Also try LightningBlade tunables(v 1.2.3 ; the newer version does not work that well for me..).
Stock rom provides the best balance between Performance and Battery life.
Click to expand...
Click to collapse
True that! :good:
siddhesh9146 said:
once I tried to root on stock nogut, so I installed TWRP and flashed SuperSu and my phone got bricked
Click to expand...
Click to collapse
If you had followed the link I supplied you would have had your answer as to why you had problems and also how to fix it.
echo92 said:
If you're rooting on stock Nougat, you must have a custom kernel flashed (or used the temporary dm-verity disabler on the stock kernel) before you root.
Click to expand...
Click to collapse
Hi, sorry for ask, do you know where can i find the temporary dm-verity disabler?
I tried with a script named "no-verity-opt-encrypt-5.1" (this works for the G5 Plus 'Potter') but i haven't had any success. Even i unpacked the stock boot.img and i tried to manually patch it, but i failed here too.
Honestly i would like to test the stock kernel, because i never used it, i am always attached to flashing EX to get root access. Thank you in advance.
moonlightdrive said:
Hi, sorry for ask, do you know where can i find the temporary dm-verity disabler?
I tried with a script named "no-verity-opt-encrypt-5.1" (this works for the G5 Plus 'Potter') but i haven't had any success. Even i unpacked the stock boot.img and i tried to manually patch it, but i failed here too.
Honestly i would like to test the stock kernel, because i never used it, i am always attached to flashing EX to get root access. Thank you in advance.
Click to expand...
Click to collapse
I don't know if this will still work on later builds than the November/December 2016 builds, but here's the kernel with dm-verity disabled: https://forum.xda-developers.com/mo...t-how-to-root-n-firmware-npj25-93-11-t3532556 Seems to cause bootloops though on the later builds however
Strictly speaking, I misspoke - it's not really a dm-verity disabler, more a stock kernel with dm-verity disabled. I think EX kernel is still the more stable and more reliable option. It would be nice to be able to root the stock kernel though...
echo92 said:
I don't know if this will still work on later builds than the November/December 2016 builds, but here's the kernel with dm-verity disabled: https://forum.xda-developers.com/mo...t-how-to-root-n-firmware-npj25-93-11-t3532556 Seems to cause bootloops though on the later builds however
Strictly speaking, I misspoke - it's not really a dm-verity disabler, more a stock kernel with dm-verity disabled. I think EX kernel is still the more stable and more reliable option. It would be nice to be able to root the stock kernel though...
Click to expand...
Click to collapse
Oh, i see, thanks for your response. I'll look into it to see how he did to by-pass the dm verity, and try to modify the last boot.img that we have.
I mentioned earlier in this thread about getting Error 0 whilst updating apps in Google Play. As it turns out, thanks to this tip here https://forum.xda-developers.com/showpost.php?p=73552496&postcount=57 it appears to be an error with permissions on the /data/media partition.
I managed to fix it with osm0sis' script:
Download from here https://forum.xda-developers.com/showthread.php?t=2239421 the sdcard Fix Permissions script http://forum.xda-developers.com/attachment.php?attachmentid=3761904&d=1464187934
You may wish to back up your data with TWRP or ensure you have your photos and videos somewhere safe prior to flashing this.
Reboot to TWRP and backup your device.
Flash the above script.zip in TWRP and wait for it to complete. (it should be fixing the permissions in /data/media)
Reboot and you should be able to download/update apps again from Google Play afterwards. You may have to uninstall the app and re-install the app if it keeps failing.
I've got this working on a XT1642 running June 2017 stock ROM, rooted with magisk 13.3 and apps including Snapchat and Google Chrome update without issue now.
echo92 said:
I mentioned earlier in this thread about getting Error 0 whilst updating apps in Google Play. As it turns out, thanks to this tip here https://forum.xda-developers.com/showpost.php?p=73552496&postcount=57 it appears to be an error with permissions on the /data/media partition.
I managed to fix it with osm0sis' script:
Download from here https://forum.xda-developers.com/showthread.php?t=2239421 the sdcard Fix Permissions script http://forum.xda-developers.com/attachment.php?attachmentid=3761904&d=1464187934
Click to expand...
Click to collapse
Useful info, this happened to me a couple of days ago. I thought it was something related to the integrated Chrome WebView in conflict with the system WebView, because it only happened when i tried to update Chrome, or any of his variants (dev, beta, canary, etc). Thanks.
This is not a guide as such but more of direction to other peoples hard work and effort. I am not a developer, just an experimenter!
Main Credits - @MishaalRahman and @phhusson.
For me one of the main selling points of the Mediapad M5 was being Project Treble enabled. Being a big Nexus/Pixel fan I am not particularly fond of EMUI.
So after reading this detailed and clear guide by Mishaal Rahman http://www.xda-developers.com/flash-generic-system-image-project-treble-device/, I was able to successfully install an AOSP Generic System Image by phhusion http://forum.xda-developers.com/project-treble/trebleenabled-device-development/experimental-phh-treble-t3709659
My device - CMR-W09 (10.8" non pro wifi).
I flashed v17 with Gapps and SU and apart from an Android System error upon boot it seems to work ok. I have not had much time to play with it but so far Wifi, Bluetooth, sound, camera, fingerprint sensor, MTP and SD card appear to be working. I had issues with google play not downloading apps but worked after clearing data/cache on google play and google play services. Also have issues with superuser force closing.
For the nervous and unsure, you can easily return to stock Huawei firmware by flashing your devices stock system.img in fastboot.
Obviously bootloader needs to be unlocked see guide - https://forum.xda-developers.com/mediapad-m5/how-to/bootloader-unlock-guide-t3781275 by @Apo11on. You can use Apo11on's root guide to download your firmware to get your stock system.img.
OEM needs to be disabled in developer options.
It is best to factory reset via recovery mode and then boot straight into bootloader to keep FRP unlocked.
Do this at your own risk but please read all the available information and guides on XDA.
pphusion has made other Project Treble roms but I have yet to try them. Hopefully it would be nice if someone could fully develop Lineage for this device.
which rom did you use ? the A/B one or A only ?
It's an A-only device.
I tried AOSP with GAPPS and SU but SuperSU shows the su binary as being occupied through several reboots. Getting the Lineage GSI now and will root with magisk.
Edit:
Blah... Lineage is not an option until we have twrp :/ (at least for me) No way to install GAPPS.
Edit:
SU works with phh's super user available from the play store.
Yes i have the AOSP one now on my AL-09 and it works fine till now. Bugs : home Button not working but fingerprint works, supersu with the phhs one works. Bluetooth sometimes gives an error message. Battery drain is a little bit high. I installed the Huawei camera apk from treble forum and This works also good.
Another Bug is Apps sometimes force closing but Not often.
How is Lineage performing?
A little bit off topic, but how did you unlock the bootloader on the Wifi only version since the website for the code is offline for a few weeks now?
Thanks in advance.
Fantastic to see that Treble works.
On my AL09(ASOP with gapps and su) bluetooth never connects to any of my devices and fc on pairing.
Lineage was a non-starter, since I was unable to get gapps running. I was also getting a vendor mismatch toast. I'm back on the stock .125(C00), no working tether is infinitely more useable than no BT.
It was nice to be able to flash something that didn't brick it and was partially useable.
fargonaz said:
On my AL09(ASOP with gapps and su) bluetooth never connects to any of my devices and fc on pairing.
Lineage was a non-starter, since I was unable to get gapps running. I was also getting a vendor mismatch toast. I'm back on the stock .125(C00), no working tether is infinitely more useable than no BT.
It was nice to be able to flash something that didn't brick it and was partially useable.
Click to expand...
Click to collapse
I understand, Do you think it gets more stable for our device in the future?
florian-m19 said:
I understand, Do you think it gets more stable for our device in the future?
Click to expand...
Click to collapse
I think so, if you look at the github comments there is a huawei phone having the same problem, so as long as a phone is having problems it should get fixed
We would like some screenshots to see if this is real @AndDiSa @rcstar6696 @phhusson @MishaalRahman
Just installed it, attached a few screenshots. Haven't tested it a lot, but it boots.
Wie are Not joking, its real ??
Delete, double post
I will be getting my Mediapad M5 8.4 tomorrow and will be flashing the AOSP treble build straight away. Just a heads up a updated build has just been posted with some Huawei related fixes.
i flash it now, and give feedback tomorrow
I flashed the new one with gapps and su, and for the sht-l09 there is no working bluetooth, so that's as far as I go. It will be nice when the BT is fixed for this device.
Works good with dirty flash, Home Button is working now and also Automatic Brightness, but battery draining is really high and it gets hot.
florian-m19 said:
Works good with dirty flash, Home Button is working now and also Automatic Brightness, but battery draining is really high and it gets hot.
Click to expand...
Click to collapse
Have you tried changing the cpu governor? Is it set to something like interactive? I got my Mediapad today but I am waiting for the bootloader unlock code from Huawei.
darren1 said:
Have you tried changing the cpu governor? Is it set to something like interactive? I got my Mediapad today but I am waiting for the bootloader unlock code from Huawei.
Click to expand...
Click to collapse
yes it is on interactive, should i change this ?
florian-m19 said:
yes it is on interactive, should i change this ?
Click to expand...
Click to collapse
Might be worth experimenting with. Try conservative or ondemand if they are available. You can always change back if it doesn't make any difference.
darren1 said:
Might be worth experimenting with. Try conservative or ondemand if they are available. You can always change back if it doesn't make any difference.
Click to expand...
Click to collapse
okay i change it in helix engine to ondemand and the suspend engine is now on powersafe.
So, i have an LG K11 Plus (LM-X410BCW), released in 2018, the hardware of this phone is pretty good but, for some reason, while its CPU does supports 64-Bits, LGE installed an 32-Bits kernel on it (thank you for mistakes like that you always do, LGE.... ugh)
I searched for another root and custom kernel for this phone, and i could not find any. No rooting, no custom bootloader, and no custom kernel. Simply, nothing.
And for the most unfortunate, this phone is now completely abandoned by the manufacturer. Their official ROM and kernel are so bad, so glitched, so awful. The phone does not use the maximum power of its hardware, it keeps rebooting, it's stuck in Android 7.0 and even its camera app is glitched (my BACK flash doesn't work on the back camera, the app recognizes it as a "frontal" flash)
I know for rooting and installing custom kernel, i need another bootloader first
So i plan to make an unofficial bootloader for this model.
But i don't know where to begin, i know nothing about Android deep-modding and developing mobile custom kernels and bootloaders, i've no clues how to do that
I only know the basics of Android app developing, Android shell scripting and i'm more advanced in J2ME applications (completely useless for today's Android standards)
So, ¿where do i begin to do that?
My initial plans is making a unofficial TWRP bootloader for this model, but i don't know how i'll do that
I'd really help you if i knew how to, i also have this phone. I got it for a realtively high price and must say that it's absolutely unworthy of it's existance in our planet and modern society. The absolute maximum of modifications it allowed me to do was to remove bloatware packages using ADB, so i removed almost everything Google/Android related and now i'm working on a list of what you can/can't remove.
I removed the included launchers to only use Evie launcher, installed XDA's Navigation Gestures app (tho it made my phone lag a bit, as any overlay/draw-over-screen app will do), replaced Play Store by F-Droid, and etc... The phone is still bad, sub-entry level hardware even for it's time, has a Vulkan-capable GPU without Vulkan drivers included in the OS, and a 64-bit CPU running a 32-bit Kernel/OS, like you mentioned. But after that, the experience became a little bit smoother, at least!
I don't know nothing about this, but maybe you can get this phone's stock ROM in KDZ format, and start doing brute-force modifications to it, to flash it with LGUp, or LGFlashTool as if it was a stock ROM, but your modified version, because i don't think this phone checks the integrity of the ROM being flashed, or at least not in a way that can't be easily bypassed.
I have found its firmware on the internet, but i don't know how to modify it yet... But maybe i'll not delay much to learn it if i begin to. But i think i'll not be able to change its kernel nor the bootloader, as i want, from the firmware only, only the ROM... So it would be a bit useless as the LG's negligency was most on its software, with that lack of Vulkan and 64-bit support stuff