Database Develop

[Q] Persistent Android L OTA Upgrade Notification

I am rooted, unlocked, and S-offed and running a custom GPE+ 5.0.1 ROM. I have an unpinnable notification that says "System Update Downloaded: Android L Upgrade for User/Release-Keys". It is an OTA update obviously, but doesn't even say what version it is. I believe I cannot install it because I am running a custom ROM, is that correct? If not, is there any way to install it? Otherwise, how can I get this notification to stop appearing? The update is ~300MB downloaded and I would love to have that space back. Also I think it is keeping my device awake because I use the Xposed mod "Notification Count" and it says the darn thing has sent out a notification a whopping 463 times since my last reboot - within 3-4 hours!. That is insane.
Any help will be appreciated.
EDIT: Woke up the next morning, and now the notification count for this stupid thing is "999+". WTF. Why does it have to be so insistent? Anybody have a solution to this?

A week passed and no response. Bump. Nobody has any idea how to get rid of this thing??

Koolstr said:
I am rooted, unlocked, and S-offed and running a custom GPE+ 5.0.1 ROM. I have an unpinnable notification that says "System Update Downloaded: Android L Upgrade for User/Release-Keys". It is an OTA update obviously, but doesn't even say what version it is. I believe I cannot install it because I am running a custom ROM, is that correct? If not, is there any way to install it? Otherwise, how can I get this notification to stop appearing? The update is ~300MB downloaded and I would love to have that space back. Also I think it is keeping my device awake because I use the Xposed mod "Notification Count" and it says the darn thing has sent out a notification a whopping 463 times since my last reboot - within 3-4 hours!. That is insane.
Any help will be appreciated.
EDIT: Woke up the next morning, and now the notification count for this stupid thing is "999+". WTF. Why does it have to be so insistent? Anybody have a solution to this?
Click to expand...
Click to collapse
Is updating your custom rom to 5.1+ an option? Already many custom roms were updated to 5.1 even 5.1.1.

Interesting. Last time I checked there wasn't a 5.1 version. But it seems the dev recently implemented an initial version: http://forum.xda-developers.com/ver...m-google-play-edition-lollipop-v1-00-t2963841
The current version of 5.1 of this ROM has some known bugs and I would like to hold off until they are fixed - I like having ambient display. Is it worth waiting until they are fixed, or should I just update now?
Is it safe for me to flash the 5.1 ROM over the 5.0.1 without doing even a cache wipe?

Koolstr said:
Interesting. Last time I checked there wasn't a 5.1 version. But it seems the dev recently implemented an initial version: http://forum.xda-developers.com/ver...m-google-play-edition-lollipop-v1-00-t2963841
The current version of 5.1 of this ROM has some known bugs and I would like to hold off until they are fixed - I like having ambient display. Is it worth waiting until they are fixed, or should I just update now?
Click to expand...
Click to collapse
Don't even know what rom it is so its hard to answer. If you prefer a stable rom they yes, you should wait a little more.
Is it safe for me to flash the 5.1 ROM over the 5.0.1 without doing even a cache wipe?
Click to expand...
Click to collapse
You should ask this one in your rom thread, sometime when the update is considered a major update, its recommend to do a full wipe, in some cases you are fine just updating without wiping. You could do a nandroid backup using your custom recovery (save it on your computer, not just on the phone) try to update without wiping. If its working fine, there is no problem, if not you can wipe your phone and restore your backup.
To disable the notification, I would try to go in settings --> apps --> all, search for the updater service, clear cache of that service and then disable it. Then find where the ota file is stored on your phone and delete it. Not sure if it will work, never tried myselef

Is there a way to do a nandroid backup directly to pc? Because I don't have room on my phone, and TWRP Manager only lets internal backups take place.
For some reason I can't search the apps in my ROM. The notification says it is from Google Play Services but I suspect that is simply routed requests from the actual updater service. Do you know what the name of the service is, so I can find it? I have a crazy number of apps and can't find it.

Hi Koolstr,
I know this thread is old, but wanted to let you know I am on an unlocked and rooted HTC One (m7) S-On. I am using TWRP and can backup to external storage using a Micro USB Powered Micro USB Host OTG cable, which I purchased from Amazon.
I am running:
Android version: 5.1
Rom: Google-Plus-Edition-LP_m7_v3.2_072915
Kernel: 3.4.10-NuK3rn3l-Lollipop_v8.00
I am getting a similar Android System Update: Android L upgrade for user/release-keys. I cannot get it to go away. I made a complete nandroid backup and then proceeded applying the update. It will reboot the phone into TWRP recovery and do nothing. The update goes away for a few days and then it comes back. I have tried to look for a way to disable the update, but I am at a stand still. If anyone knows that would be great.
Best,
manderson706

It's something that santod did. I believe there's a post in his topic with the fix. Or just flash the updated GPE from santod

New Update - BLU 06/01/2016 ??

Has anyone else got this notification of update?
Version Number: BLU_V0030UU_V10_GENERIC_5.1_20160518-1813
Version Size: 100.21 MB
Release Date - 2016-06-01

Just got my phone in and yes i have that updates. so far it fails on the recovery screen on reboot. luckly holding power button and force reboot fixed it, not going to install the update again until i see its resolved..

hamilLewiston said:
Has anyone else got this notification of update?
Version Number: BLU_V0030UU_V10_GENERIC_5.1_20160518-1813
Version Size: 100.21 MB
Release Date - 2016-06-01
Click to expand...
Click to collapse
I updated yesterday and all I see different is that radio app got updated to Nextradio

help.
I installed the update and now my phone doesn't boot. I go straight to recovery. Not quite sure what to do. Anyone have any suggestions?
The thing is that I just rooted with KingoRoot other day, voiding the warranty.

hamilLewiston said:
Has anyone else got this notification of update?
Version Number: BLU_V0030UU_V10_GENERIC_5.1_20160518-1813
Version Size: 100.21 MB
Release Date - 2016-06-01
Click to expand...
Click to collapse
I've rooted and flashed tWPR recovery , so don't think can do such OTA update directly.
If anybody has latest ROM tWPR backup, I would like to try.

I restored y phone to original recovery and ROM, but after download and enter recovery, it shows ERROR

Im rooted. Unless its a big difference i dont see any means to uodate

Take out the SD card and then download the update. The phone get's funky if you have an SD card
---------- Post added at 11:22 AM ---------- Previous post was at 11:18 AM ----------
Insane PPC said:
Just got my phone in and yes i have that updates. so far it fails on the recovery screen on reboot. luckly holding power button and force reboot fixed it, not going to install the update again until i see its resolved..
Click to expand...
Click to collapse
If you have an SD card inserted to the phone, remove it before downloading the update. The phone doesn't react too well with an SD card.

AqueousBor said:
I updated yesterday and all I see different is that radio app got updated to Nextradio
Click to expand...
Click to collapse
yeah I received the notification as well. It's only an update to an app "radio" that I dont even use. I'm just patiently waiting for Android 6.0 as they promised the Vivo XL would get.

The Remedy said:
yeah I received the notification as well. It's only an update to an app "radio" that I dont even use. I'm just patiently waiting for Android 6.0 as they promised the Vivo XL would get.
Click to expand...
Click to collapse
Ditto. But I think we both know that's never going to happen.

xphyle1971 said:
Ditto. But I think we both know that's never going to happen.
Click to expand...
Click to collapse
tbh it looks that way but idk their was an official android 6.0 update for another BLU phone I saw on a website the other day but I cant think of which BLU model it was. So i'm still hopeful.

jason4962 said:
Im rooted. Unless its a big difference i dont see any means to uodate
Click to expand...
Click to collapse
Android security updates?
HandsomeFatty said:
Take out the SD card and then download the update. The phone get's funky if you have an SD card
If you have an SD card inserted to the phone, remove it before downloading the update. The phone doesn't react too well with an SD card.
Click to expand...
Click to collapse
Will the update go through even if using TWRP? Will it break root or cause a soft brick? I'm still running the original build that it shipped with (dated 26-12-2015 with 2015-11-01 security patch level).
The Remedy said:
yeah I received the notification as well. It's only an update to an app "radio" that I dont even use. I'm just patiently waiting for Android 6.0 as they promised the Vivo XL would get.
Click to expand...
Click to collapse
When did "they" (Gionee or BLU?) promise the Vivo XL would get MM?

rczrider said:
Android security updates?
Will the update go through even if using TWRP? Will it break root or cause a soft brick? I'm still running the original build that it shipped with (dated 26-12-2015 with 2015-11-01 security patch level).
When did "they" (Gionee or BLU?) promise the Vivo XL would get MM?
Click to expand...
Click to collapse
1. It wouldn't be Gionee doing anything even those this phone is based off of it. 2. Look at the sites that reviewed it, it's been posted many times that it was planned to get Android 6.0 . Android Central....check gsmarena it's out there if you look.

The Remedy said:
1. It wouldn't be Gionee doing anything even those this phone is based off of it. 2. Look at the sites that reviewed it, it's been posted many times that it was planned to get Android 6.0 . Android Central....check gsmarena it's out there if you look.
Click to expand...
Click to collapse
I can't imagine BLU is doing much ROM development. Gionee almost certainly has to provide them with the MM ROM since the Vivo XL is the Gionee Elife S Plus. BLU makes some changes, sure, but they likely aren't developing a MM ROM from scratch.
Anyway, I was just curious and not that interested in reading up on it. I got this phone to be a bedside clock (AMOLED screen FTW) and as a backup in case my DD runs into problems. It was $100 and a good deal at that price, but I have no belief that it will see anything but security patch updates (and even then, I don't expect much).

They arent going to update to 6.0. It used to say that on the Blu website but after the phone launched it was removed from the Blu Vivo XL and Vivo 5 pages.

Can anyone make a flashable zip? I'm using TWRP. I tried modifiing the updater-script, but no luck so far.

I updated the radio but went to an error and now the phone is stuck on boot menu. I can't flash it because it won't connect to any computer.

lemur394395 said:
I installed the update and now my phone doesn't boot. I go straight to recovery. Not quite sure what to do. Anyone have any suggestions?
The thing is that I just rooted with KingoRoot other day, voiding the warranty.
Click to expand...
Click to collapse
Check out http://forum.xda-developers.com/vivo-xl/how-to/rooted-kingroot-replaced-supersu-twrp-t3432078 .
Flash TWRP recovery and then load the backup from 2016-03. Then root with SuperSu.

any mm update ?

BLU on Google +
min1968 said:
I've rooted and flashed tWPR recovery , so don't think can do such OTA update directly.
If anybody has latest ROM tWPR backup, I would like to try.
Click to expand...
Click to collapse
If you check with these folks, they can help immensly!! BLU Development Team on Google+ a small community of BLU users that share information and have ALL kinds of information and links to STOCK, CUSTOM, and other ROM's, plus rooting tips, guides, and links to TWRP and CWM recoveries.

[Discussion / Poll] How successful was your unofficial upgrade to Nougat?

Hi! I am starting this discussion / poll in the hope that people will think twice before upgrading (unofficially) to Nougat. So far, what I see is 3 outcomes: 1) Device gets bricked 2) Unofficial Nougat has major bugs and people decide to downgrade back to Marshmallow 3) Upgrade is successful and user is pleased. I think that the latter scenario is actually quite rare and I feel for inexperienced people who brick their device. My question, before you try to upgrade unofficially: is it worth it?

People who brick their device doesn't follow the steps as there are written.
for example t hey flash the b370 version without the additional package and they reply 'bluetooth isnt working'
i encourage people upgrading to nougat because of the new ui, the better battery/ram management and the appearance of drawer
i rollbacked too many times to marshmallow, upgraded to nougat without any problem or brick, just follow the steps and the installation is successful.

StrangerWeather said:
Hi! I am starting this discussion / poll in the hope that people will think twice before upgrading (unofficially) to Nougat. So far, what I see is 3 outcomes: 1) Device gets bricked 2) Unofficial Nougat has major bugs and people decide to downgrade back to Marshmallow 3) Upgrade is successful and user is pleased. I think that the latter scenario is actually quite rare and I feel for inexperienced people who brick their device. My question, before you try to upgrade unofficially: is it worth it?
Click to expand...
Click to collapse
I have two p9 lites,and they are both running on b370,updated trough hicare (1.99gb),and it works perfectly.Battery life,camera,bluetooth,everthing works amazingly compared to older nougat betas.

L-31 P9, Battery life is much better used to get only 4 hours on screen time watching videos now i get 6 with 25% left so easily 7 (my screen is always at 60% brightness) I'm not rooted because i didn't flash it after but i will root soon using a PC (I'm new to rooting (came from IPhone) yet i can easily do it probably because I'm a very techy person) anyway it seems faster my camera and everything works fine i used to get 1.8gb 4am max now i get 2.2 (with no apps running) also split screen works very well and is not laggy at all, one complain i have is the live wallpaper i used for some reason stoped working after i updated (black hole stock love wallpaper) i went into settings to re apply it as it's happened once before on MM but i said there was no wallpapers at all not even still ones, if someone could give me a link to the live wallpaper I'd really appreciate that but other than that no complaints at all it's much better than MM it even has a F.LUX like function built in to reduce blue light levels to help late at night so you're​ not wide awake , the pull down menu has Many and i mean Many more functions not just 5-10 there's probably 20+ and you can have more than 5 at one time, notifications are good and work well, everything seems overly big to me but thats probably because i used to have my phone on a 300 DPI before de-rooting and updating, like i was saying it has almost no drawbacks it's very polished If you install it correctly (one package before the other and it only takes 20 mins max and you data is not deleted i used tarp not the one from this forum but it works the same i got logged out of apps and that's all that's happend when i updated)

simo255 said:
People who brick their device doesn't follow the steps as there are written.
for example t hey flash the b370 version without the additional package and they reply 'bluetooth isnt working'
i encourage people upgrading to nougat because of the new ui, the better battery/ram management and the appearance of drawer
i rollbacked too many times to marshmallow, upgraded to nougat without any problem or brick, just follow the steps and the installation is successful.
Click to expand...
Click to collapse
I agree 100%.
Upgrade to newer version of OS, official or unofficial, is one of the best thing of Android. But people need to be careful with their device, if it's not an OTA update obviously there are some steps to follow.. every device is different and just flashing whatever without attention may cause problem. Reading the steps to follow takes only 1 minute.

I'm on B132, is there a quick way to upgrade to B370? I've tried hi-care app but says no updates
Thanks

simo255 said:
People who brick their device doesn't follow the steps as there are written.
for example t hey flash the b370 version without the additional package and they reply 'bluetooth isnt working'
i encourage people upgrading to nougat because of the new ui, the better battery/ram management and the appearance of drawer
i rollbacked too many times to marshmallow, upgraded to nougat without any problem or brick, just follow the steps and the installation is successful.
Click to expand...
Click to collapse
sirjohnrl said:
I have two p9 lites,and they are both running on b370,updated trough hicare (1.99gb),and it works perfectly.Battery life,camera,bluetooth,everthing works amazingly compared to older nougat betas.
Click to expand...
Click to collapse
bghyt said:
L-31 P9, Battery life is much better used to get only 4 hours on screen time watching videos now i get 6 with 25% left so easily 7 (my screen is always at 60% brightness) I'm not rooted because i didn't flash it after but i will root soon using a PC (I'm new to rooting (came from IPhone) yet i can easily do it probably because I'm a very techy person) anyway it seems faster my camera and everything works fine i used to get 1.8gb 4am max now i get 2.2 (with no apps running) also split screen works very well and is not laggy at all, one complain i have is the live wallpaper i used for some reason stoped working after i updated (black hole stock love wallpaper) i went into settings to re apply it as it's happened once before on MM but i said there was no wallpapers at all not even still ones, if someone could give me a link to the live wallpaper I'd really appreciate that but other than that no complaints at all it's much better than MM it even has a F.LUX like function built in to reduce blue light levels to help late at night so you're​ not wide awake , the pull down menu has Many and i mean Many more functions not just 5-10 there's probably 20+ and you can have more than 5 at one time, notifications are good and work well, everything seems overly big to me but thats probably because i used to have my phone on a 300 DPI before de-rooting and updating, like i was saying it has almost no drawbacks it's very polished If you install it correctly (one package before the other and it only takes 20 mins max and you data is not deleted i used tarp not the one from this forum but it works the same i got logged out of apps and that's all that's happend when i updated)
Click to expand...
Click to collapse
Potato997 said:
I agree 100%.
Upgrade to newer version of OS, official or unofficial, is one of the best thing of Android. But people need to be careful with their device, if it's not an OTA update obviously there are some steps to follow.. every device is different and just flashing whatever without attention may cause problem. Reading the steps to follow takes only 1 minute.
Click to expand...
Click to collapse
I take your points but looking at the answers and questions forum again today, I still think the number of people bricking or downgrading is quite high. I love Nougat too, but I am warning newbies that it might be worth waiting for an official update or if not, concentrating on what you're doing. My penny's worth...

StrangerWeather said:
I take your points but looking at the answers and questions forum again today, I still think the number of people bricking or downgrading is quite high. I love Nougat too, but I am warning newbies that it might be worth waiting for an official update or if not, concentrating on what you're doing. My penny's worth...
Click to expand...
Click to collapse
I updated to B370 but had to downgrade to mm because my camera wasn't working, but overall it was a great experience. Can't wait to get an update where my camera works.
Sent from my HUAWEI VNS-L31 using Tapatalk

I see a lot of people have camera issue on l31 but for l21 everything seems to be OK. I have B370 on my l21 and I don't even think about rolling back to MM. Newest firmware is (at least in my opinion) stable and for now it runs flawlessly

JaccaPL said:
I see a lot of people have camera issue on l31 but for l21 everything seems to be OK. I have B370 on my l21 and I don't even think about rolling back to MM. Newest firmware is (at least in my opinion) stable and for now it runs flawlessly
Click to expand...
Click to collapse
+1

I have not managed to update my phone to Nougat. Everytime i try to use firmware finder or Hi suite , it keeps downloading the 1,24GB package and not the 1,99GB so i end up with a generic a15 Test Key phone

kourkoubas1981 said:
I have not managed to update my phone to Nougat. Everytime i try to use firmware finder or Hi suite , it keeps downloading the 1,24GB package and not the 1,99GB so i end up with a generic a15 Test Key phone
Click to expand...
Click to collapse
Try the TWRP method.

zgomot said:
Try the TWRP method.
Click to expand...
Click to collapse
I think that you must be bootloader unlock and rooted to use TWRP method . Too complicated for me :/
I have L21C900B170 after the fifth or sixth failure to go to 370 .
Whatever I try through Firmware Finder or HiSuite it keeps downloading the 1,24GB file and not the 1,99 Gb upgrade so I always and up with ND90 test key .
Something is blocking it but no one knows what

kourkoubas1981 said:
I think that you must be bootloader unlock and rooted to use TWRP method . Too complicated for me :/
I have L21C900B170 after the fifth or sixth failure to go to 370 .
Whatever I try through Firmware Finder or HiSuite it keeps downloading the 1,24GB file and not the 1,99 Gb upgrade so I always and up with ND90 test key .
Something is blocking it but no one knows what
Click to expand...
Click to collapse
It's really not all that difficult and there are several guides around here. Unlocking the bootloader and rooting MM is pretty much without risks. I'd say go for it.

kourkoubas1981 said:
I think that you must be bootloader unlock and rooted to use TWRP method . Too complicated for me :/
I have L21C900B170 after the fifth or sixth failure to go to 370 .
Whatever I try through Firmware Finder or HiSuite it keeps downloading the 1,24GB file and not the 1,99 Gb upgrade so I always and up with ND90 test key .
Something is blocking it but no one knows what
Click to expand...
Click to collapse
First this: https://forum.xda-developers.com/huawei-p9lite/how-to/root-root-recovery-bootloader-unlock-t3457564
Then this: https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932

Looks like there is a majority of successful upgrades after all!

Well I did an upgrade and although at first I thought I 'borked it' - the build I have is 'NRD90M test-keys'
But I have to say after manually installing google keyboard and getting a few play store updates installed, it feels like an absolute rocket compared to the old EE B132 version

StrangerWeather said:
First this: https://forum.xda-developers.com/huawei-p9lite/how-to/root-root-recovery-bootloader-unlock-t3457564
Then this: https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932
Click to expand...
Click to collapse
OK i managed to do the unlocking of bootloader - root but the first try of upgrading went me again to N90RDM test keys something :/
During the installation of the b370 files throught TWRP i got a message that there is /system

kourkoubas1981 said:
OK i managed to do the unlocking of bootloader - root but the first try of upgrading went me again to N90RDM test keys something :/
During the installation of the b370 files throught TWRP i got a message that there is /system
Click to expand...
Click to collapse
Did you flash both files?

StrangerWeather said:
Did you flash both files?
Click to expand...
Click to collapse
If he made the same mistake as me then he didn't flash the second file, doh!:silly:
i'm thinking of trying to get twrp back on and having another go......

Problem with lockup / display not turning on across various roms, rooted droid

I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!

What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.

thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks

Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL

MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilà it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.

Just ordered razer phone 2 looking for custom os instructions.

So from what i gathered TWRP doesnt work yet on the razer phone 2 and lineage os doesnt have a build for this phone yet i gotta ask what is available for modding razer and what is the step by step to make that happen. i seen some instructions but other than root there isnt much to do.

SynGreis said:
So from what i gathered TWRP doesnt work yet on the razer phone 2 and lineage os doesnt have a build for this phone yet i gotta ask what is available for modding razer and what is the step by step to make that happen. i seen some instructions but other than root there isnt much to do.
Click to expand...
Click to collapse
TWRP works just fine on this device. It's installed when you fastboot flash arter97 kernel and it works perfect. He just updated it to r10. Good luck!!
Edit: as far as ROMs look around in this forum you'll find a couple of different ones in the same section as arter97 :good:

which one do you suggest? i dont see much of a selection.

SynGreis said:
which one do you suggest? i dont see much of a selection.
Click to expand...
Click to collapse
Right now there really aren't any, although there are a few in development, such as AOSP. I think the initial high price, specialized hardware & relative unpopularity has not helped attract any serious development.
I've noticed that ROM development has decreased significantly in the last few years. I remember the days of the Samsung Galaxy Nexus & the HTC Evo 4G where it seemed as if there was a new ROM released every week. I think its because (a) recent Android operating systems are offering greater customization out of the box, & (b) with the new A/B partitioning scheme, it makes ROM development more difficult.

Cancel your order. Get your money back. This phone while it is awesome at gaming and has a great screen. The OS is ****ty to say the least. I have had more issues with it freezing up. Not wanting to download apps from the play store. Not allowing me to install apps that I have already downloaded on my device. Now it's showing up as the Asus Rog II. This phone is the biggest heaviest piece of **** I've ever had. I promise you if everyone knew the issues this phone has you couldn't give it away free.

mattwheat said:
Cancel your order. Get your money back. This phone while it is awesome at gaming and has a great screen. The OS is ****ty to say the least. I have had more issues with it freezing up. Not wanting to download apps from the play store. Not allowing me to install apps that I have already downloaded on my device. Now it's showing up as the Asus Rog II. This phone is the biggest heaviest piece of **** I've ever had. I promise you if everyone knew the issues this phone has you couldn't give it away free.
Click to expand...
Click to collapse
Mine showed as in rog 2 the last time I reloaded the OS. It's because it searches for "phone 2" and randomly guesses. No biggie, just fix it in the settings. No issues here from playstore, if you do it's common on every Android phone and fixable by clearing the data from the app. Maybe you should reflash the stock firmware? I don't see why you would call this phone ****ty. It's basically running AOSP stock except some theming from Razer. I fixed some freezing issues by reseating the Sim and SD card that I have. This thing rocks, just saying.

I've cleared the play stores cache, data, and dalvic in every method imaginable. Even google play services. I've restored backups, flashed stock .imgs, and flashed the stock odex Ron and the deodexed rom. It doesn't start failing to install play store apps till after I initially install most the apps I normally use then a while later when I think of one I forgot I'll go and try to install. That's when it starts messing up. If I watch a video threw some websites built in player on the webpage I'm viewing... about 15 to 20 seconds into the video everything but sound freezes. And will not correct itself. I have to hold the power button till it reboots. Only videos I can watch without issue is from the YouTube app. It's ridiculous. I've unlocked, rooted, and crack flashed tons of roms on all of my pixel and Nexus devices without any issue besides the random freeze. Which can be quickly fixed by toggling the screen on and off. This **** is ridiculous. So over this phone.

matt that might be just you i havent experienced any issues with this phone whatsoever.
"I think its because (a) recent Android operating systems are offering greater customization out of the box, & (b) with the new A/B partitioning scheme, it makes ROM development more difficult."
can you provide more info on this A/B partition? id love to see what customizable stuff i can do with this.

mattwheat said:
I've cleared the play stores cache, data, and dalvic in every method imaginable. Even google play services. I've restored backups, flashed stock .imgs, and flashed the stock odex Ron and the deodexed rom. It doesn't start failing to install play store apps till after I initially install most the apps I normally use then a while later when I think of one I forgot I'll go and try to install. That's when it starts messing up. If I watch a video threw some websites built in player on the webpage I'm viewing... about 15 to 20 seconds into the video everything but sound freezes. And will not correct itself. I have to hold the power button till it reboots. Only videos I can watch without issue is from the YouTube app. It's ridiculous. I've unlocked, rooted, and crack flashed tons of roms on all of my pixel and Nexus devices without any issue besides the random freeze. Which can be quickly fixed by toggling the screen on and off. This **** is ridiculous. So over this phone.
Click to expand...
Click to collapse
The freezing is due to a bug in Google Chrome. All you have to do to fix this issue is roll back the app version to 72 because version 76 doesn't work on our RP2.
Edit: uncheck auto update

Only freeze I had so far was with the infamous switch switch to the tele lens. Not a single other issue with software.

Other question, if you put the display at 120hz, and you scroll something, does it 'feel' like your finger sticks to text/icons?
I mean, is there no delay like you normally would have at 60hz?
On the Oneplus 7 Pro the 90hz is already a big improvement (less delay) but 120 should really be kickass... anyone?

MasterThiefGarrett said:
Other question, if you put the display at 120hz, and you scroll something, does it 'feel' like your finger sticks to text/icons?
I mean, is there no delay like you normally would have at 60hz?
On the Oneplus 7 Pro the 90hz is already a big improvement (less delay) but 120 should really be kickass... anyone?
Click to expand...
Click to collapse
Take this with a grain of salt, as I just got the RP2, but its the most responsive, "sticky" feeling Android phone I've used. 120hz is like night and day to me.
On a related note, Firefox Fenix with webrender enabled feels significantly more responsive than Chromium atm, as it seemingly renders the whole page instead of stuttering as you scroll like Chrome.

JDBarlow said:
TWRP works just fine on this device. It's installed when you fastboot flash arter97 kernel and it works perfect. He just updated it to r10. Good luck!!
Edit: as far as ROMs look around in this forum you'll find a couple of different ones in the same section as arter97 :good:
Click to expand...
Click to collapse
how can you get twrp in? Everytime i try to flash twrp in i get stuck at powered by android logo.

SynGreis said:
how can you get twrp in? Everytime i try to flash twrp in i get stuck at powered by android logo.
Click to expand...
Click to collapse
Which version of Android are you running currently?
MR1 will be arter97 r11
MR2 will be arter97 r12
http://arter97.com/browse/aura/kernel/

duplicate post

JDBarlow said:
Which version of Android are you running currently?
MR1 will be arter97 r11
MR2 will be arter97 r12
http://arter97.com/browse/aura/kernel/
Click to expand...
Click to collapse
i havent flashed either of those arter because im worried that its gonna screw things up again.
Im sitting on the 9.0 MR1 stock image from razer.
https://developer.razer.com/razer-ph...actory-images/

SynGreis said:
i havent flashed either of those arter because im worried that its gonna screw things up again.
Im sitting on the 9.0 MR1 stock image from razer.
https://developer.razer.com/razer-ph...actory-images/
Click to expand...
Click to collapse
So are you on the global version? If so let it update to MR2 and fastboot flash boot arter97 r12 and you'll be just fine.
Which version are you running then to get stuck on boot logo?
Edit: if you want to stay on MR1 then flash arter97 r11

i tried updating to mr2 but says installation failed.
all i do is
faatboot flash boot kernal.img?

I just rooted MR2 to show you. It took me less than 5 minutes to do the whole process of fastboot flashing kernel booting straight into TWRP recovery which is included then installing magisk immediately rebooting into system and updated magisk. Done

JDBarlow said:
I just rooted MR2 to show you. It took me less than 5 minutes to do the whole process of fastboot flashing kernel booting straight into TWRP recovery which is included then installing magisk immediately rebooting into system and updated magisk. Done
Click to expand...
Click to collapse
My only question is, which version zip of magisk did you use in TWRP to flash? 20 or the latest beta? I'm rooted now with a modded boot.img that someone else used the canary/latest beta. Just don't want to screw myself and end up having to flash mr1 again then taking the update.