Related
I never expected this to happen, my device is toast, after simply trying tp update the super su binaries, it didn't work thre twrp install method, and then i tried normla method, it failed, and now it is stuck at the anmation before it even gets to the android logo,
i can still boot into twrp, buut, how do you get an image over to twrp without a micro sdcard,
jesus,
i don't know my model that's a big problem..
I just bought the device it is a 64gb gold version,
can anyone please help me?
I am freaking out.
i've tried a factory reset, and so on, nothing gets past the stupid animation of a bunch of circles and sprites that are animated
Well,
1. You're just bootlooping it seems - no brick.
2. While you're in TWRP connect it to the PC > a while ago TWRP mounts the storage so you can drag and drop onto the device while in recovery.
3. So doing the above [be in recovery + connected to PC] drag your new rom / files / etc onto the device > perform a full wipe [wiping everything except internal storage] and then flash again.
teh roxxorz said:
Well,
1. You're just bootlooping it seems - no brick.
2. While you're in TWRP connect it to the PC > a while ago TWRP mounts the storage so you can drag and drop onto the device while in recovery.
3. So doing the above [be in recovery + connected to PC] drag your new rom / files / etc onto the device > perform a full wipe [wiping everything except internal storage] and then flash again.
Click to expand...
Click to collapse
thanks so much,
how do i tell what model i have?
i would just flash back to stock, but i'm uncertain with firmware to flash,
it is the 64 gb gold model
i have the serial, is there somewhere i can look that up ith the serial? i also have the product, angler -vn2
it says on my box it's the h1511, but that doesn't that's not the same medels that are atteached to the fiirmawares
GhostCyber said:
thanks so much,
how do i tell what model i have?
i would just flash back to stock, but i'm uncertain with firmware to flash,
it is the 64 gb gold model
i have the serial, is there somewhere i can look that up ith the serial? i also have the product, angler -vn2
it says on my box it's the h1511, but that doesn't that's not the same medels that are atteached to the fiirmawares
Click to expand...
Click to collapse
This is a great article on how to get back to stock: http://forum.xda-developers.com/nexus-6p/general/tutorial-how-to-flash-factory-image-t3252931
---------- Post added at 12:41 AM ---------- Previous post was at 12:37 AM ----------
crowsnestitsupport said:
This is a great article on how to get back to stock: http://forum.xda-developers.com/nexus-6p/general/tutorial-how-to-flash-factory-image-t3252931
Click to expand...
Click to collapse
Model shouldn't matter... The different firmwares listed are different release dates.
crowsnestitsupport said:
This is a great article on how to get back to stock: http://forum.xda-developers.com/nexus-6p/general/tutorial-how-to-flash-factory-image-t3252931
---------- Post added at 12:41 AM ---------- Previous post was at 12:37 AM ----------
Model shouldn't matter... The different firmwares listed are different release dates.
Click to expand...
Click to collapse
i don't know wich stock firmware to use though!
6.0.0 (MDA89D)
6.0.0 (MDB08K)
6.0.0 (MDB08L)
6.0.0 (MDB08M)
6.0.0 (MMB29N)
6.0.1 (MMB29M)
6.0.1 (MMB29P)
6.0.1 (MMB29Q)
wich one of these is for
H1511???
GhostCyber said:
i don't know wich stock firmware to use though!
6.0.0 (MDA89D)
6.0.0 (MDB08K)
6.0.0 (MDB08L)
6.0.0 (MDB08M)
6.0.0 (MMB29N)
6.0.1 (MMB29M)
6.0.1 (MMB29P)
6.0.1 (MMB29Q)
wich one of these is for
H1511???
Click to expand...
Click to collapse
I doesn't matter.. You pick.. Each one from top down is a newer release date with newer security patch. I would go with 29Q. Its the newest.
GhostCyber said:
i don't know wich stock firmware to use though!
6.0.0 (MDA89D)
6.0.0 (MDB08K)
6.0.0 (MDB08L)
6.0.0 (MDB08M)
6.0.0 (MMB29N)
6.0.1 (MMB29M)
6.0.1 (MMB29P)
6.0.1 (MMB29Q)
wich one of these is for
H1511???
Click to expand...
Click to collapse
The firmware doesn't [above] doesn't correspond to your phone model number H1511 [hardware rev]. This isn't like the old bastardized times where 'one version of a phone' has upteen model numbers [looking at you Samsung]
Best to flash MMB29Q as it's the latest. That'll give you the foundation to flash any current custom rom.
Also very important to note the above files are used to flash back to stock, as linked above; they are NOT to be flashed in TWRP.
teh roxxorz said:
The firmware doesn't [above] doesn't correspond to your phone model number H1511 [hardware rev]. This isn't like the old bastardized times where 'one version of a phone' has upteen model numbers [looking at you Samsung]
Best to flash MMB29Q as it's the latest. That'll give you the foundation to flash any current custom rom.
Also very important to note the above files are used to flash back to stock, as linked above; they are NOT to be flashed in TWRP.
Click to expand...
Click to collapse
That, is a great referrance
I am new to moto, i have been samsung for the past decade, and thus am SUPER PARANOID abbbout everything, because,, it's crazy over there
anyway, thanks very much,
i don't understand though why my factory reset doesn't work,
it doesn't make sence to me, but eh, wich ever,
if this works hurray
thanks everyone fore there quick responce
i feel sorta like a fish outa water dealing with nexus devices after samsung for so long.
GhostCyber said:
That, is a great referrance
I am new to moto, i have been samsung for the past decade
Click to expand...
Click to collapse
Moto is not the Nexus 6P, my friend... are you SURE you are referring to the correct device, or was this just a typo?
If you're installing the wrong firmware... ruh oh
GhostCyber said:
That, is a great referrance
I am new to moto, i have been samsung for the past decade, and thus am SUPER PARANOID abbbout everything, because,, it's crazy over there
anyway, thanks very much,
i don't understand though why my factory reset doesn't work,
it doesn't make sence to me, but eh, wich ever,
if this works hurray
thanks everyone fore there quick responce
i feel sorta like a fish outa water dealing with nexus devices after samsung for so long.
Click to expand...
Click to collapse
I would guess that you probably wiped the system in twrp which is why factory reset doesn't work. Also a good idea to do a full backup in TWRP before moding so that you have a fall back. But if you can run ADB you can easily and quickly get back to full stock with the info provided above.
GhostCyber said:
That, is a great referrance
I am new to moto, i have been samsung for the past decade, and thus am SUPER PARANOID abbbout everything, because,, it's crazy over there
anyway, thanks very much,
i don't understand though why my factory reset doesn't work,
it doesn't make sence to me, but eh, wich ever,
if this works hurray
thanks everyone fore there quick responce
i feel sorta like a fish outa water dealing with nexus devices after samsung for so long.
Click to expand...
Click to collapse
Factory reset basically erases all the data - but doesn't modify the system > which is where your issue is.
And it'll definitely work. Do as the linked guide said above to get back to stock and then flash your custom ROM.
But why were you updating the binary, as all ROMs are rooted with supersu 2.52 as a minimum, unless you flashed a non rooted ROM and flashed a super old supersu?
Soulfly3 said:
Moto is not the Nexus 6P, my friend... are you SURE you are referring to the correct device, or was this just a typo?
If you're installing the wrong firmware... ruh oh
Click to expand...
Click to collapse
Yes indeed!!! The Nexus 6 Motorola is shamu, the Nexus 6p Is Angler.
Soulfly3 said:
Moto is not the Nexus 6P, my friend... are you SURE you are referring to the correct device, or was this just a typo?
If you're installing the wrong firmware... ruh oh
Click to expand...
Click to collapse
yes, sorry, i group moto devvices in ces, i know i shouldn't, but basicaly there core google devices
i have a nexus, p i am installing a nexuss 6p fiirmware, as i undderstand it, all nexus 6p firmwares work
GhostCyber said:
yes, sorry, i group moto devvices in ces, i know i shouldn't, but basicaly there core google devices
i have a nexus, p i am installing a nexuss 6p fiirmware, as i undderstand it, all nexus 6p firmwares work
Click to expand...
Click to collapse
Yup, your good!!
GhostCyber said:
yes, sorry, i group moto devvices in ces, i know i shouldn't, but basicaly there core google devices
i have a nexus, p i am installing a nexuss 6p fiirmware, as i undderstand it, all nexus 6p firmwares work
Click to expand...
Click to collapse
Yes, that's correct.
Hey guys,
Not much of a poster but it seems the retus guys are left out in discussions involving flashing our firmware...
I present the official nougat OTA I received for RETUS only. This has the January security patch (vanilla android yet we are still behind security patches...nice Lenovo...).
For those sideloading this and are still on MM, you'll just need to adb sideload the file. Keep in mind that I received my OTA update on a November security patch, so it may not mater at all which patch you have.
RETUS NOUGAT OTA (Mega link)​
Preparation:
For those who rooted and caused a bunch of hell on your system partition, you can grab some stock unsigned firmware here and revert what you did. Fastboot flash the boot, sparsechunks (in order), recovery, and oem images (then reboot back to bootloader to choose recovery mode). You can now finally sideload it flawlessly without losing any data. If you need more information you can check out one the revert to stock firmware guides, I'm not going to post something repetitive.
Root options:
You want root? You have two options...first you obviously need TWRP.
flash a custom ROM
flash this gentleman's (tomparr) custom kernel over on his thread and then flash superSU or Magisk. You can flash both SuperSU and Magisk but you could also just flash Magisk which comes with it's own systemless root.
Revert?
You can reflash MM images but I suggest using something more autonomous like this flashing tool by core720 since there's a lot more commands involved to officially downgrade. There's also an edit of the downgrade bat script in the comments of the thread which I suggest to use instead.
Viper4Android!? Atmos!?
There are currently magisk modules that work (both arise and independent ones).
I am also on the Nov. security and got the notice today of the update being available and twice after what I believe it to be successful it boots back up and tells me there was an error and nothing was updated. So thanks I guess I have no choice but to try to side-load this. Would love to know why it failed to update after being downloaded though.
I am on July security patch and just got the prompt so don't think patch level matters
xantanion said:
I am on July security patch and just got the prompt so don't think patch level matters
Click to expand...
Click to collapse
Please let me know if yours updates, mine has failed four times today already.
Jimi Mack said:
Please let me know if yours updates, mine has failed four times today already.
Click to expand...
Click to collapse
Mine went flawlessly
Jimi Mack said:
I am also on the Nov. security and got the notice today of the update being available and twice after what I believe it to be successful it boots back up and tells me there was an error and nothing was updated. So thanks I guess I have no choice but to try to side-load this. Would love to know why it failed to update after being downloaded though.
Click to expand...
Click to collapse
Jimi Mack said:
Please let me know if yours updates, mine has failed four times today already.
Click to expand...
Click to collapse
I'm not sure where you're coming from, have you ever altered your system partition? If you sideload through recovery, you would be able to see the recovery log and see the error it shows each time rather than having the OTA handled through the OTA client.
DroneDoom said:
I'm not sure where you're coming from, have you ever altered your system partition? If you sideload through recovery, you would be able to see the recovery log and see the error it shows each time rather than having the OTA handled through the OTA client.
Click to expand...
Click to collapse
Tried booting into Recovery to see such logs, all I get is "No Command." I picked this phone up 2nd hand, I am going to assume system partition was altered as the unit was already unlocked but showing to be stock. I am best at this point maybe just installing TWRP and working with what roms are available.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
xantanion said:
Mine went flawlessly
Click to expand...
Click to collapse
You installed this downloaded OTA or did you get yours OTA? Thanks.
Jimi Mack said:
Tried booting into Recovery to see such logs, all I get is "No Command." I picked this phone up 2nd hand, I am going to assume system partition was altered as the unit was already unlocked but showing to be stock. I am best at this point maybe just installing TWRP and working with what roms are available.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
You installed this downloaded OTA or did you get yours OTA? Thanks.
Click to expand...
Click to collapse
Got my OTA today and had no issues. Just got the phone brand new yesterday as well
Jimi Mack said:
Tried booting into Recovery to see such logs, all I get is "No Command." I picked this phone up 2nd hand, I am going to assume system partition was altered as the unit was already unlocked but showing to be stock. I am best at this point maybe just installing TWRP and working with what roms are available.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
You installed this downloaded OTA or did you get yours OTA? Thanks.
Click to expand...
Click to collapse
To unlock the stock recovery menu, bring up that 'no command' instance again and hold the power button and double tap the vol+ while still holding the power button. It's tricky, you may need to press them both at once or just play around with it until you see the menu.
DroneDoom said:
To unlock the stock recovery menu, bring up that 'no command' instance again and hold the power button and double tap the vol+ while still holding the power button. It's tricky, you may need to press them both at once or just play around with it until you see the menu.
Click to expand...
Click to collapse
Thanks, I was able to get into it, but the sad part is I have no idea on what I am looking at, that might as well been a foreign language...lol. I saw several error logs, but as I said, no idea on what I was looking at. I did not know what to expect but was kind of hoping for a red lag or something that said "hey schmuck loot at this. "
Jimi Mack said:
Thanks, I was able to get into it, but the sad part is I have no idea on what I am looking at, that might as well been a foreign language...lol. I saw several error logs, but as I said, no idea on what I was looking at. I did not know what to expect but was kind of hoping for a red lag or something that said "hey schmuck loot at this. "
Click to expand...
Click to collapse
If you invested in some Z mods and want them working (battery packs work but there's no software indication of charge or anything) you may have to flash some stock images to get everything sorted out. If you don't care then by all means you can use a custom nougat rom, the MM modem and radios still work even on a nougat rom.
DroneDoom said:
If you invested in some Z mods and want them working (battery packs work but there's no software indication of charge or anything) you may have to flash some stock images to get everything sorted out. If you don't care then by all means you can use a custom nougat rom, the MM modem and radios still work even on a nougat rom.
Click to expand...
Click to collapse
Hopefully at sometime there is a stock N rom I can flash from TWRP on a MM base.
Or I can try side loading yours and hope that works.
Question: What is the differences in the two "unsigned firmware" in the 1st post?
Just got the update when I checked manually (Consumer Cellular RETUS Unlocked)
First impression: What an... interesting boot animation.
Jimi Mack said:
Hopefully at sometime there is a stock N rom I can flash from TWRP on a MM base.
Or I can try side loading yours and hope that works.
Question: What is the differences in the two "unsigned firmware" in the 1st post?
Click to expand...
Click to collapse
I think there may be a difference in security patches but they have the same build number so I'm not too sure.
holabola said:
Just got the update when I checked manually (Consumer Cellular RETUS Unlocked)
First impression: What an... interesting boot animation.
Click to expand...
Click to collapse
Yeah it is, it reminds me of the days when I had a Motorola razr lol.
For anyone that was wondering, the display size scaling works PERFECTLY.
I originally changed the DPI to make everything smaller, but it led to a lot of random issues with other apps (mainly involving the camera). The display size scaling mimics the effects of a DPI change right out of the box without all the issues and need for a computer (I wasn't rooted so)
Also, when I got the update, I was on the December 1st security patch.
DroneDoom said:
This has the January security patch (vanilla android yet we are still behind security patches...nice Lenovo...).
Click to expand...
Click to collapse
Yeah motoblur might look like stock android, but it is very different under the hood. This is also the first 32-bit nougat phone in existence, and certainly the first nougat phone on the snapdragon 625. This phone is also unique in that it has to work with all of the Moto mods (none of the aosp Roms in the "ROMs" section work with Moto mods, so this probably wasn't trivial to add). For such a unique phone, we got updated pretty quickly. We got nougat before the Axon 7 (advertised as "daydream compatible" for +6 months before updated to 7.0) and plenty of other phones. It's not a nexus or a Oneplus, but Moto did good considering this isn't a flagship (although to most of us, it is).
DroneDoom said:
Magisk
Click to expand...
Click to collapse
Just want to be clear, Magisk v11 will brick on nougat. V12 works perfectly. I've got a whole thread dedicated to Magisk on nougat and was finally able to pass safetynet using s3v3n's 3.0.1 build and the latest v12 Magisk. Did not flash supersu or ARISE.
xxBrun0xx said:
Yeah motoblur might look like stock android, but it is very different under the hood. This is also the first 32-bit nougat phone in existence, and certainly the first nougat phone on the snapdragon 625. This phone is also unique in that it has to work with all of the Moto mods (none of the aosp Roms in the "ROMs" section work with Moto mods, so this probably wasn't trivial to add). For such a unique phone, we got updated pretty quickly. We got nougat before the Axon 7 (advertised as "daydream compatible" for +6 months before updated to 7.0) and plenty of other phones. It's not a nexus or a Oneplus, but Moto did good considering this isn't a flagship (although to most of us, it is).
Just want to be clear, Magisk v11 will brick on nougat. V12 works perfectly. I've got a whole thread dedicated to Magisk on nougat and was finally able to pass safetynet using s3v3n's 3.0.1 build and the latest v12 Magisk. Did not flash supersu or ARISE.
Click to expand...
Click to collapse
Thanks for the feedback (fixed op), I noticed v11 doesn't patch the kernel correctly and the ROM tries to boot without it. I thought it was just me since I was playing around trying to change my cache partition to f2fs but I guess the kernel doesn't support that filesystem for cache (ROM boots but doesn't initialize).
S3v3n's ROM is based on firmware stock right? I tried magisk with V4A module but it doesn't work and Atmos somehow bricks stock but it doesn't brick on a ROM built from different source (works on xperience). I noticed today that the ARISE project has a magisk module for it's latest project so maybe there's a possibility for stock to have systemless V4A.
Question, when I am in Stock Recovery to side load the update, I ma getting this.. anyone know what Status 225 is?
Now send package you want to apply
to the device with "adb sideload ,filename>...
status 255
Installation aborted.
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
I think I may have found the issue, in Stock Recovery, is says :motorola/addison-retail/addison
but under ABOUT PHONE on the phone it states this is on a retus channel. Conflict of information, any suggestions?
Jimi Mack said:
Question, when I am in Stock Recovery to side load the update, I ma getting this.. anyone know what Status 225 is?
Now send package you want to apply
to the device with "adb sideload ,filename>...
status 255
Installation aborted.
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
I think I may have found the issue, in Stock Recovery, is says :motorola/addison-retail/addison
but under ABOUT PHONE on the phone it states this is on a retus channel. Conflict of information, any suggestions?
Click to expand...
Click to collapse
Addison is our phone model's codename. For instance the Moto z variants are codenamed "griffin." They each have individual builds based on a region's network range and so they are codename as well...We are RETUS (retail US) which is the channel that we get our updates from so that each device will get specifically tuned update based on the region it represents. Reteu (Europe), retbr (Brazil) etc.
As for your 255 error, there is no specific documentation about this. It may be some incompatibility error or a failed sideload based on the same error # given in TWRP and CM recoveries.
DroneDoom said:
Addison is our phone model's codename. For instance the Moto z variants are codenamed "griffin." They each have individual builds based on a region's network range and so they are codename as well...We are RETUS (retail US) which is the channel that we get our updates from so that each device will get specifically tuned update based on the region it represents. Reteu (Europe), retbr (Brazil) etc.
As for your 255 error, there is no specific documentation about this. It may be some incompatibility error or a failed sideload based on the same error # given in TWRP and CM recoveries.
Click to expand...
Click to collapse
I thank you. I got the update to begin to load, it fails and aborts at 45% . It states something about content, lists my build number and give a code 755. I can not find out anything about this one either. I guess something is screwy with what is installed on my phone and what should be...
Hello ShieldTV users,
I have a little problem, I flashed my shield and installed a custom recovery. Now I would like to update to the last version but when the shieldTV try to install the update, the system reboot by itself and nothing else than the Shield 6.3 menu appear.
Should I update with Adb and fastboot ?
Sorry if my questions looks dumb AF I'm a bit newbie about the shieldTV and I don't want to mess and brick it.
Thanks in advance for your help
Edit : I also think about getting LineageOS, what do you guys think about it on shieldTV ?
Yes you would need to flash with fastboot.
But you will lose root and twrp if you have those.
---------- Post added at 08:24 PM ---------- Previous post was at 08:19 PM ----------
Has anyone managed to get stock Android Oreo rooted??????
I hard bricked my 2017 trying and had to get a replacement.
I've just sent the replacement into a bootloop.
I'm not even installing it, just using " fastboot boot twrp.img"
I had twrp installed and running great before the Oreo update came along.
I think we need a twrp update....... any ideas??????
mdrodge said:
Yes you would need to flash with fastboot.
But you will lose root and twrp if you have those.
---------- Post added at 08:24 PM ---------- Previous post was at 08:19 PM ----------
Has anyone managed to get stock Android Oreo rooted??????
I hard bricked my 2017 trying and had to get a replacement.
I've just sent the replacement into a bootloop.
I'm not even installing it, just using " fastboot boot twrp.img"
I had twrp installed and running great before the Oreo update came along.
I think we need a twrp update....... any ideas??????
Click to expand...
Click to collapse
Yes after the oreo update I had to change to the latest twrp version for the shield of course I never install only fastboot
I did the update with fastboot, everything went well but I was unable to use the dev version so I used the normal instead.
Looks pretty neat, otherwise, what do you guys think about LineageOs on shield ? Can it be used a the main OS ?
I've not tried it fully but I'd say if you wanted normal Android (Not ATV) then that's the way to go.
I have had lots of China boxes with stock Android and to be honest it's a lot "simpler" but not as smooth.
By simpler I basically mean less hard to do the power user tasks that I often find myself doing.
However Android TV looks better and the average user would probably find it easier to find something to watch.
Also you lose all the gaming features.
Basically you end up with a powerful China box (U could have saved money buy just getting a China box)
---------- Post added at 12:10 PM ---------- Previous post was at 12:08 PM ----------
jionny said:
Yes after the oreo update I had to change to the latest twrp version for the shield of course I never install only fastboot
Click to expand...
Click to collapse
I thought I had the latest version....
Can you drop a link or anything?
Link:https://developers.google.com/android/images
For each device there are two files available with no additional information so if you are using them then wait for the explanation form Google or if anyone tries them both please update the same in the thread.
namaste ?
seems an odd way to roll it out. Flipped a coin. I'm trying QP1A.190711.020. Will update.
flashed 10.0.0 (QP1A.190711.019, Sep 2019) just now.......first thing I noticed was the Powered By Android now has the Robot added to the logo. Security patch says Sept 5 2019. The gestures seem better. Pulling out the side menu in apps like Gmail are easier now. Overall seems way snappier than Beta 6.
Going to flash 10.0.0 (QP1A.190711.020, Sep 2019) and see if it blows up LOL
Can I flash a full factory 10.0 over my February Patch 9.0? I want to update to 10.0 without losing my data, am currently rooted and know if I lock the bootloader I have to wipe. My thought is to flash 10.0 via adb and edit it to remove the -w and I should be able to just load 10.0 without having to wipe my data.
edited
wowzors said:
Can I flash a full factory 10.0 over my February Patch 9.0? I want to update to 10.0 without losing my data, am currently rooted and know if I lock the bootloader I have to wipe. My thought is to flash 10.0 via adb and edit it to remove the -w and I should be able to just load 10.0 without having to wipe my data.
Click to expand...
Click to collapse
You can do that, since it is major update from pie to android 10 you should try clean wipe to avoid issues.
Is there a way to use the classic 3 button navbar from Android Oreo. I'm still using them and I'm on Pie.
KingMike67 said:
flashed 10.0.0 (QP1A.190711.019, Sep 2019) just now.......first thing I noticed was the Powered By Android now has the Robot added to the logo. Security patch says Sept 5 2019. The gestures seem better. Pulling out the side menu in apps like Gmail are easier now. Overall seems way snappier than Beta 6.
Going to flash 10.0.0 (QP1A.190711.020, Sep 2019) and see if it blows up LOL
Click to expand...
Click to collapse
what pixel 2 version do you have ? is it the unlocked version ?
youssefkr said:
what pixel 2 version do you have ? is it the unlocked version ?
Click to expand...
Click to collapse
Its from the google store, unlocked. I am on verizon but I have an unlocked bootloader and am currently on 9.0 February patch with Magisk + TWRP.
quera said:
Is there a way to use the classic 3 button navbar from Android Oreo. I'm still using them and I'm on Pie.
Click to expand...
Click to collapse
Yes you can. The option is still there.
---------- Post added at 07:58 PM ---------- Previous post was at 07:57 PM ----------
youssefkr said:
what pixel 2 version do you have ? is it the unlocked version ?
Click to expand...
Click to collapse
Mine is unlocked (Rogers)
KingMike67 said:
Yes you can. The option is still there.
---------- Post added at 07:58 PM ---------- Previous post was at 07:57 PM ----------
Mine is unlocked (Rogers)
Click to expand...
Click to collapse
It sounded like .20 was the same as .19 but has the September security patch.
Ota is here!
quera said:
Is there a way to use the classic 3 button navbar from Android Oreo. I'm still using them and I'm on Pie.
Click to expand...
Click to collapse
Yes there is according to a video review of Android 10 by Android Central on YouTube
kcteun said:
seems an odd way to roll it out. Flipped a coin. I'm trying QP1A.190711.020. Will update.
Click to expand...
Click to collapse
Flashed over beta6 with the .020 Factory image. No problems. TWRP 3.3.0.0 works (delete screen lock pin on mine). Rooted with Magisk 19.3. Everything working, even viper4android.
kcteun said:
Flashed over beta6 with the .020 Factory image. No problems. TWRP 3.3.0.0 works (delete screen lock pin on mine). Rooted with Magisk 19.3. Everything working, even viper4android.
Click to expand...
Click to collapse
how did u manage to get viper to work?
it always asks to install driver, i let it install, afte reboot same message, even if driver installation was succesfull
Can I flash this android 10 update via twrp , I m rooted and on havoc os august build ?
Anybody else lost dark boot animation after updating from beta?
Hi, the ota image can be installed from the internal storage?
kcteun said:
Flashed over beta6 with the .020 Factory image. No problems. TWRP 3.3.0.0 works (delete screen lock pin on mine). Rooted with Magisk 19.3. Everything working, even viper4android.
Click to expand...
Click to collapse
Oh you lucky duck! Twrp 3.3.0-0 has never fastbooted on my P2XL since it's release. The previous version does, but does not allow me to flash anything properly. Guess I'll do some more experimenting. Even fastbooting the magisk patched boot.img just gives me boot loops when using the 19.3 version. Don't really want to do a FDR, but may have to even though 10 is working just fine after fastbooting it without the -w. Oh well
Badger50 said:
Oh you lucky duck! Twrp 3.3.0-0 has never fastbooted on my P2XL since it's release. The previous version does, but does not allow me to flash anything properly. Guess I'll do some more experimenting. Even fastbooting the magisk patched boot.img just gives me boot loops when using the 19.3 version. Don't really want to do a FDR, but may have to even though 10 is working just fine after fastbooting it without the -w. Oh well
Click to expand...
Click to collapse
do you use latest platform tools bro?
New update has dropped. Version P-MR2-RC001-RZR-190914.3123 and brings the phone up to September 5th for security updates.
I have the update pending but I don't want to download just yet to ensure compatibility with Arter97's kernel. If the WiFi is really better then I might jump on regardless because that's my primary issue at this point. Can anyone confirm either the kernel works or the WiFi is noticably better?
OTA-URL:
https://android.googleapis.com/packages/ota-api/razer_aura_cheryl2/741344047df2f17f6adbe97f7e45a9471037da6f.zip Global
AlexBodewig said:
I have the update pending but I don't want to download just yet to ensure compatibility with Arter97's kernel. If the WiFi is really better then I might jump on regardless because that's my primary issue at this point. Can anyone confirm either the kernel works or the WiFi is noticably better?
Click to expand...
Click to collapse
Compatibility hasn't been confirmed yet, but previous discussions with someone who had an AT&T version that was on a July update had issues with arter97's kernel on September's update. The kernel seemed to be incompatible as it failed to boot and also switched the phone back to the old slot afterwards.
Extracted payload.bin:
https://drive.google.com/drive/folders/1bmPGWDAD3DtqNAMrDn0IGfGLB_HyFVeH
---------- Post added at 10:23 ---------- Previous post was at 10:21 ----------
This seems to be a differential update, as the boot.img is 1/4 of the normal size. I thought, I could patch it with magisk... [emoji53]
the_brad said:
Extracted payload.bin:
https://drive.google.com/drive/folders/1bmPGWDAD3DtqNAMrDn0IGfGLB_HyFVeH
---------- Post added at 10:23 ---------- Previous post was at 10:21 ----------
This seems to be a differential update, as the boot.img is 1/4 of the normal size. I thought, I could patch it with magisk... [emoji53]
Click to expand...
Click to collapse
It seems to be the case as the images are rather small. I'm not sure what to do now that I'm on Havoc OS GSI. Is there a possible way to patch stuffs other than system (such as vendor)?
I'm yet to make a backup as the current app I use for backup (Migrate) doesn't appear to work properly on this phone (while it worked on my previous one, Xperia XZ Premium), and that Titanium Backup hasn't been updated to be compatible with new features (such as split apks) so some backups can no longer work properly after restoring.
I also need to know if there were any improvements regarding Bluetooth compatibility. Currently I cannot use my bluetooth headset on GSI (only phone calls work), even with a modded overlay (with values changed to undo Razer's crippling of certain features such as aptX).
EDIT: I guess it's not that easy as the payloads are most likely block-based OTAs. These updates do not tolerate any changes on the partitions unlike file-based OTAs that we used to have. We'll have to wait for full factory images to come out and make a list of what we really need to flash from stock updates...
Any issues with the update etc please lmk everyone!
Enjoy it!
Rox598 said:
Any issues with the update etc please lmk everyone!
Enjoy it!
Click to expand...
Click to collapse
Not exactly an issue, but can you tell us, when razer will push the factory-image for this new update? That would make things mich easier...
the_brad said:
Not exactly an issue, but can you tell us, when razer will push the factory-image for this new update? That would make things mich easier...
Click to expand...
Click to collapse
Wish I knew!
But I can say to them that people are wanting the factory images if no major issues are present I can't see why it wont be up there but that's me.
I tried updating but it gives me an error everytime.
(Using the Deodoxed version)
Can someone help me with this ?
So trying to game plan here. Logic tells me to flash boot, vendor, and system from factory image of current build. Then let the system update itself. Then flash arter kernel, then go into twrp and flash latest magisk zip to get root.
Is this update still Android 9 or is this taking us to android 10?
---------- Post added at 08:35 PM ---------- Previous post was at 08:34 PM ----------
the_brad said:
OTA-URL:
https://android.googleapis.com/pack.../741344047df2f17f6adbe97f7e45a9471037da6f.zip Global
Click to expand...
Click to collapse
And this .zip file you linked.... Can we flash this in TWRP or is this the standard OTA that needs stock recovery?
mattwheat said:
Is this update still Android 9 or is this taking us to android 10?
Click to expand...
Click to collapse
---------- Post added at 08:35 PM ---------- Previous post was at 08:34 PM ----------
It's this:
is this the standard OTA that needs stock recovery?
Click to expand...
Click to collapse
the_brad said:
mattwheat said:
Is this update still Android 9 or is this taking us to android 10?
Click to expand...
Click to collapse
---------- Post added at 08:35 PM ---------- Previous post was at 08:34 PM ----------
It's this:
Click to expand...
Click to collapse
I'm trying to read between the lines here Brad but I'm not picking up what you're putting down.
mattwheat said:
Is this update still Android 9 or is this taking us to android 10?
---------- Post added at 08:35 PM ---------- Previous post was at 08:34 PM ----------
And this .zip file you linked.... Can we flash this in TWRP or is this the standard OTA that needs stock recovery?
Click to expand...
Click to collapse
This is the standard OTA that needs stock recovery & the update is still Android Pie/9
Also, for anyone that's curious, it doesn't seem to fix any of the speaker phone/call quality issues currently present in Android Pie/9 (but weren't present in Oreo). I can't speak to Wi-fi performance improvements, or other fixes mentioned in the update notice, but I am very thankful that Razer has released this OTA with security patches through September of 2019 ? ?. Thank you Razer!
Wifi
The WiFi is fixed for wifi calling I believe if you put this phone into airplane mode and trying wifi calls it would glitch the wifi out before now seems to work
I think I'll wait to install it until someone else who is more educated in this tests it and makes a guide for it to put stock back on and whatever we need to do to make Arter 97 kernel work with it.
Any fixes to the camera apk?
Razer 2 Global MR2 Sept 2019 Release Magisk Root
I got root on MR2 Build Global from this thread on Page 7 Thank to khaled1881 and the The_brad
https://forum.xda-developers.com/razer-phone-2/how-to/help-root-update-mr2-t3973483
new update
AlexBodewig said:
I have the update pending but I don't want to download just yet to ensure compatibility with Arter97's kernel. If the WiFi is really better then I might jump on regardless because that's my primary issue at this point. Can anyone confirm either the kernel works or the WiFi is noticably better?
Click to expand...
Click to collapse
i reflashed the stock firmware and ran the update to get the latest security update. I also have arter97 r11 kernel installed and magisk and have it rooted with no problems. Google Pay works as well as I was able to get it to pass the CTC scan.