This will update you to June 2016 driver your rom may or may not include this driver already
do a nandroid aka twrp backup of your system partition before you flash just in case
Requires you to be on mm rooted rom and bootloader unlock not really required but how are you rooted on mm if you don't have a locked bootloader so yeah just saying
kitkat it bootloops and lollipop it boatloads do not use this if you are on nougat It causes horrible performance and black screens instead of content
Download from this thread
http://forum.xda-developers.com/showthread.php?t=3435159
Then flash in twrp
That is it easy
in above linked thread people have improved Benchmark scores and better stability and performance it works fine for me your miles may differ as always flash at your own risk
thanks airidosas252 for the find of the new drivers
Wow thanks for this. I was hesitant at first so I did some research and after backing up my system partition, I flashed it and my phone is definitely much more responsive. I don't know why this wasn't included in the PF4 update because it makes a big difference in performance.
I recommend anyone building ROMs based on PF4 include this in your ROM.
Can't it work on stock lollipop rom?
edit it doesnt work on kitkat or lollipop i had an unlocked bootloader on both roms i tried ni2 rooted tw based rom and cm12.1 unofficial for klte aosp rom try more roms and firmwares if you feel like it but i dont think it works on kitkat or lolipop
[email protected] said:
This will update you to June 2016 driver your rom may or may not include this driver already
do a nandroid aka twrp backup of your system partition before you flash just in case
Requires you to be on mm rooted rom and bootloader unlock not really required but how are you rooted on mm if you don't have a locked bootloader so yeah just saying
kitkat it bootloops and lollipop it bootloops
Download from this thread
http://forum.xda-developers.com/showthread.php?t=3435159
Then flash in twrp
That is it easy
in above linked thread people have improved Benchmark scores and better stability and performance it works fine for me your miles may differ as always flash at your own risk
thanks airidosas252 for the find of the new drivers
Click to expand...
Click to collapse
In a TIM G900M Unlocked? (ROOT, TWRP Recovery, 6.0.1) Can Works? [Android Security Patch 01/08/2016]
Thanks.
it worked on my g900v bootloader unlocked rooted on 6.01 mm aosp just do a backup of your system partition in twrp before you flash if it doesnt work just restrore the system partition backup in twrp and your phone will boot backup just fine
Related
I Had just rooted my GTAB2 and it'd been two days. And suddenly the news came out that Official JB 4.2.2 has been released for the GT-P3100
So i Opted for unrooting and getting back my Official status but it didnt work
But then i found this trick
1.Install Triangle away
2.Have a cf-autorooted tab (GT-P3100)(may work on other models)
3.First Reset the flash counter using Traingle Away.
4.Enable the tracker option and reboot.
5.Then boot into Stockrecovery. (CWM Recovery or any other recovery won't do the trick. U can reinstall it after the OTA.)
6.Wipe Data/Factory reset.
7.Wipe Cache.
8.Wipe Dalvik Cache.
9.Reboot.
10.Voila!!! You have a device with Official Status with ROOT and Can recieve OTA.
May or May NOT WORK, but it did work for me
PLEASE NOTE THIS IS ONLY APPLICABLE IF YOU ARE NOT USING A CUSTOM ROM AND USING THE OFFICIAL STOCK WITH JUST ROOT.
accepting the ota update will most likely unroot the device. the new firmware will also probably be patched so unless you are sure that a root exploit exists for the new firmware, than perhaps it is best to wait for the odin flashable version from sammobile and use mobile odin pro to flash. mobile odin pro has an option called everoot which will root the rom. this is probably easier to do than trying to root a new firmware with a patched kernel.
ashraf sharif said:
accepting the ota update will most likely unroot the device. the new firmware will also probably be patched so unless you are sure that a root exploit exists for the new firmware, than perhaps it is best to wait for the odin flashable version from sammobile and use mobile odin pro to flash. mobile odin pro has an option called everoot which will root the rom. this is probably easier to do than trying to root a new firmware with a patched kernel.
Click to expand...
Click to collapse
Also if we can't use any custom recovery .
, then what's the need to root the device?
no one is saying that you cannot use custom recovery. you can use whatever you please custom kernel ,recovery,rom, whatever you choose is your choice.My point is that not everyone root6s thier phone so they can flash a custom rom. In my case I use official roms all the time. official kernel all the time. official recovery all the time. my phone has official status aLL THE TIME.
so why root?
if not to flash aosp roms and cwm or twrp orthe multitude of mods and roms? yes Ive been there and done that. ive overclocked and undervolted and ran aokp miui pa u name it. I have never found a rom that was 100 percent working and compatible for any phone ever. in fact most of the time i came across major bugs that made most roms unusable as a daily driver. stability is hard to find in aosp land . the manufacturers do not release sources. so cameras and fingerprint scanners and mhl and other features either are barely functional or sometimes will never work.
I ROOT BECAUSE I CAN CUSTOMIZE THE STOCK FIRMWARE THAT I USE. without root i cant use greenify ton hibernate my apps. without root i cant freeze apps in sd maid or tibu or rom toolbox pro. Root allows me to change my bootanimations . byn 8using root explorer. root allows me to edit my build prop. root allows me to zipalign my apps. and debloat them. root improves my user experience . it allows me to enjoy the stability and long battery life and full functionality if stock roms without having to use a stripped gown vanilla android rom. been there and was not impressed. but to each his own.
Android 5.0 (Lollipop) Bootloader and KitKat Compatibility
Everyone wants Lollipop, however it is worth considering some of the possible consequences of upgrading via OTA update.
Bootloader:
A new Bootloader (BL) will almost certainly be included in the OTA update. It is also very likely no KitKat Kernel, stock or custom will be able to boot properly with the 5.0 BL. Perhaps the Kernel DEVs can find a workaround.
Root:
It may take some time to gain root access on Lolipop as on other devices this has required a custom Kernel. A custom kernel itself may require kernel sources to be released - something that has taken weeks / months in the past. Finally Chainfire Roots Lollipop on the Nexus 9. :highfive:
Xposed Framework:
Developer has said he will wait for CyanogenMod based on Lollipop before properly starting development of an ART version of Xposed. CM12 may take a few weeks to release. Expect to do without Xposed for at least a month, probably longer since root is also required (see above.)
Custom Recovery:
This has not been an issue before, but it is always possible a new Bootloader could break compatibility with existing Custom Recoveries. Obviously, you would not be able to restore a CWM / TWRP backup without a functional custom recovery; but even then, it is unlikely you will be able to boot your KitKat backup.
Custom ROMs:
This is another area that could be affected by a new Bootloader. It is unknown if existing custom ROMs will require new Kernels / system changes in order to work with the new BL - something that could take days, weeks or months.
Performance:
Currently the performance difference between KitKat and Lollipop is unknown. If the first release of Lollipop for Android One has performance issues, you may be unable to revert back to stock KitKat.
Possible solution:
Wait for a flashable zip [NOT OTA Update zip] of Stock Android One Lollipop ROM - this would mean your Bootloader remains at it's current version and potentially allowing you to change 'back and forth' between Stock KitKat and Stock Lollipop. However, it is currently unknown if the newer BL is a requirement for Android 5.0 Kernels.
This is taken from the Moto G thread and all credits goes to @lost101.The sole motive of this is to create awareness about the new bootloader included in 5.0
Multi part question here which, in my mind, are somewhat related.. I've read up on many posts but these questions I still am not totally clear on and would rather not risk bricking trying to experiment....
#1) When a nandroid is taken on a particular firmware (say 4.4.4) and then after upgrading firmware to a different firmware (say 5.0.2) and I encounter a problem where there is no OS left after wiping and failing to install a custom ROM (TWRP will report: no OS installed! are you sure you want to reboot?), can I flash restore the 4.4.4 nandroid and be ok or will I brick because of bootloader incompatibility [I come from motorola phones recently - this is my first HTC]?
#2) When adding additional ROMs to multiROM do the ROMs have to be of the same firmware version? Moreover, can multiROM have a sense ROM as it's primary ROM and a GPE ROM as a secondary ROM and vice versa?
( FYI - as of this posting I still have yet to successfully boot my secondary ROM using multiROM - I can successfully install mod'd TWRP, the manager, and the patched kernel but something is eluding me - anyone with a link to a very simplified and step by step procedure on installing mulitRoom would be appreciated. I thought I had enough understanding [of the procedures I could find anyways] but apparently not, as I obviously can not get secondary Rom to boot.) I'm able to add the ROM in TWRP but when I reboot, the ROM is not listed after pressing cancel and going to the multiROM boot screen, there is simply nothing there.
#3) Re: multirom - When I reboot into the mod'd TWRP recovery and flash gapps (or any zip file for that matter) how do I know which ROM the zip is being applied to (ie: primary or secondary)?
Feel free to answer as many or as few of the questions as I know it is a lot. Thanks in advance!
HTC one m8 verizon, rooted, s-off, BL unlocked,
Successfull flashes of Viper, Skydragon, FluentROM, Adrenaline2.4* (*current DD)
kerryh said:
Multi part question here which, in my mind, are somewhat related.. I've read up on many posts but these questions I still am not totally clear on and would rather not risk bricking trying to experiment....
#1) When a nandroid is taken on a particular firmware (say 4.4.4) and then after upgrading firmware to a different firmware (say 5.0.2) and I encounter a problem where there is no OS left after wiping and failing to install a custom ROM (TWRP will report: no OS installed! are you sure you want to reboot?), can I flash restore the 4.4.4 nandroid and be ok or will I brick because of bootloader incompatibility [I come from motorola phones recently - this is my first HTC]?
#2) When adding additional ROMs to multiROM do the ROMs have to be of the same firmware version? Moreover, can multiROM have a sense ROM as it's primary ROM and a GPE ROM as a secondary ROM and vice versa?
( FYI - as of this posting I still have yet to successfully boot my secondary ROM using multiROM - I can successfully install mod'd TWRP, the manager, and the patched kernel but something is eluding me - anyone with a link to a very simplified and step by step procedure on installing mulitRoom would be appreciated. I thought I had enough understanding [of the procedures I could find anyways] but apparently not, as I obviously can not get secondary Rom to boot.) I'm able to add the ROM in TWRP but when I reboot, the ROM is not listed after pressing cancel and going to the multiROM boot screen, there is simply nothing there.
#3) Re: multirom - When I reboot into the mod'd TWRP recovery and flash gapps (or any zip file for that matter) how do I know which ROM the zip is being applied to (ie: primary or secondary)?
Feel free to answer as many or as few of the questions as I know it is a lot. Thanks in advance!
HTC one m8 verizon, rooted, s-off, BL unlocked,
Successfull flashes of Viper, Skydragon, FluentROM, Adrenaline2.4* (*current DD)
Click to expand...
Click to collapse
You won't brick it.. softbrick/bootloop maybe.. but it's easy enough just to keep a copy of the different firmware zips to flash before restoring that version nandroid.
dottat said:
You won't brick it.. softbrick/bootloop maybe.. but it's easy enough just to keep a copy of the different firmware zips to flash before restoring that version nandroid.
Click to expand...
Click to collapse
Much oblige! I assume then what to do would be to NOT reboot to system but to BOOTLOADER and fastboot flash the zip? or would I flash the firmware from TWRP (I thought firmware had to be fastbootRUU flashed)?
thx again
Hi I am currently on the canadian note 4. I am having some difficulty with cyanogenmod 12.1 lately so I wanted to move to CMRemix for better stability. The Installation guide ask the bootloader and the modem to be updated, I am doing that by reverting to an up to date stock rom and then installing CMRemix (Odin did not want flash for some reason.)
What I understand from the bootloader is that it is like the BIOS on a PC. Can my not up to date bootloader be causing the bug on CM 12.1? I am having the bluetooth crash bug and an overall slow system. CM also does not seem to work to well with spotify.
I am not an expert but I have been running custom rom for 3 years on my note 4 and note 2.
Thanks
PhilRattlehead said:
Hi I am currently on the canadian note 4. I am having some difficulty with cyanogenmod 12.1 lately so I wanted to move to CMRemix for better stability. The Installation guide ask the bootloader and the modem to be updated, I am doing that by reverting to an up to date stock rom and then installing CMRemix (Odin did not want flash for some reason.)
What I understand from the bootloader is that it is like the BIOS on a PC. Can my not up to date bootloader be causing the bug on CM 12.1? I am having the bluetooth crash bug and an overall slow system. CM also does not seem to work to well with spotify.
I am not an expert but I have been running custom rom for 3 years on my note 4 and note 2.
Thanks
Click to expand...
Click to collapse
Odin didn't want to flash the stock ROM???
Flash a stock ROM with Odin. Then flash a custom recovery like TWRP. Then do an advanced wipe and wipe cache delvik, system, data. The bluetooth could be unstable on CM12. You can look for a stable ROM and flash that if you're looking for everything to work flawlessly
i7vSa7vi7y said:
Odin didn't want to flash the stock ROM???
Flash a stock ROM with Odin. Then flash a custom recovery like TWRP. Then do an advanced wipe and wipe cache delvik, system, data. The bluetooth could be unstable on CM12. You can look for a stable ROM and flash that if you're looking for everything to work flawlessly
Click to expand...
Click to collapse
I tried flashing the modem and bootloader, not the entire firmware. I ended up installing the stock firmware in the end. I am doing the updates now and will install CMRemix shortly after
I always go stock before I flash a new ROM. Best way unless directed otherwise
Hi all. I'm a bit of a noob who just really started digging into custom roms and rooting this month. A friend helped me root Lollipop when I first got this phone and I've been putting off updating to marshmallow for 6 months, but learned how over the past weekend and I'm loving it! Small problem, though, and I don't know if it's even a real one, but here it is. After all is said and done flashing the XstreStoLite 3.3.1 rom and Aroma add on pack, everything works fine, but the arter97 kernel is no longer listed as the active kernel, even though in XstreStoLite's settings when presented with the overwrite kernel option I always selected No. Is there a reason this is happening? Can I just reflash the kernel now, and is it safe to do so without brick in the phone? Does this rom or any other necessary apps/root features require the custom kernel? Thanks! This was my process in getting my phone up and running:
Factory reset
Flash stock 6.0.1 with Odin
Flash arter97 recovery with Odin
Recovery mode to flash arter97 kernel and superSU
Flash XstreStoLite in recovery, factory reset
Flash aroma addon
Additional random question I had: at what point, if any, should I be flashing the custom bootloader and modem, and does a factory reset/cache wipe delete those or is it one and done? Thank you!
The bootloader and modem flashing is needed if you want to move from 5.x lollipop to 6.x marshmallow.
If you are allready on 6.x there is no need.
If you lost your custom kernel you can reflash it in twrp and after wipe cache/dalvik cache.
If you flash the corect version of kernel the is no problem of softbrick.
Flash a 6.x kernel on a 6.x rom