Related
Hello,
can somebody upload exactly this FW for this phone?
For 2 SIM cards? Yes
Software channel: reteu
Baseband version: M8937_11.16.02.51R CEDRIC_EMEADSDS_CUST
Kernel: original (stock): 3.18.31....
Android security level: 1 August 2017
Android version: 7.0
Build number: NPPS25.137-72-4
I can't find this ROM anywhere, but reallly need it. Thx in advance.
Mcandrew2809 said:
Hello,
can somebody upload exactly this FW for this phone?
For 2 SIM cards? Yes
Software channel: reteu
Baseband version: M8937_11.16.02.51R CEDRIC_EMEADSDS_CUST
Kernel: original (stock): 3.18.31....
Android security level: 1 August 2017
Android version: 7.0
Build number: NPPS25.137-72-4
I can't find this ROM anywhere, but reallly need it. Thx in advance.
Click to expand...
Click to collapse
I managed to break my XT1676 also, couldn't find the NPPS25.137-15-11 image either.
I ended up flashing NPP25.137-33 using RSDLite but modifying the flashing script to not flash the partition layout or the bootloader as they are older versions and got it back up and running. If you had that image on the phone previously and you have an unlocked bootloader you can do the same.
Let me know if you need more instructions.
Cheers.
Thank you for replying, raiamino.
I'd like to ask if is there any other option especially for phones with locked bootloader? I'd like to reflash my phone because it became unbelievably slow and laggy after some time. Factory reset didn't help much.
I flashed a lot of phones in the past (for example Sony Ericsson Xperia X8, Lenovo S60...) but this phone really surprises me about flashing. I found a lot of custom ROMs here on xda and I was thinking about flashing some also, but I'm a little bit scared of it - I don't know, which one is compatible and which isn't (nowhere is written if is custom ROM built for 2/16, 3/16, SingleSIM, DualSIM... variant). I need Moto Gestures feature (really useful thing for me) also, but don't know, if any custom ROM supports it. Do you know about any which will not cause brick (or hard brick) if I will flash it? Thx in advance.
Btw, sorry for bad English, but it's not my native language. Greetings from little big country - Slovakia.
Mcandrew2809 said:
Thank you for replying, raiamino.
I'd like to ask if is there any other option especially for phones with locked bootloader? I'd like to reflash my phone because it became unbelievably slow and laggy after some time. Factory reset didn't help much.
I flashed a lot of phones in the past (for example Sony Ericsson Xperia X8, Lenovo S60...) but this phone really surprises me about flashing. I found a lot of custom ROMs here on xda and I was thinking about flashing some also, but I'm a little bit scared of it - I don't know, which one is compatible and which isn't (nowhere is written if is custom ROM built for 2/16, 3/16, SingleSIM, DualSIM... variant). I need Moto Gestures feature (really useful thing for me) also, but don't know, if any custom ROM supports it. Do you know about any which will not cause brick (or hard brick) if I will flash it? Thx in advance.
Btw, sorry for bad English, but it's not my native language. Greetings from little big country - Slovakia.
Click to expand...
Click to collapse
you can do the following - warning it will erase everything on internal storage including photos music downloads documents etc - backup to sd card or laptop first if you want to keep these things
put phone into fastboot mode and connect to laptop
In a terminal/command prompt window assuming you have fastboot installed type the following
Code:
fastboot erase userdata
When you restart your phone it will be like the first time you switched it on (albeit with upgraded firmware version)
LineageOS supports moto gestures - For me they all work except shake to open camera app but you can set it to open with a double press of the power button
Flashing a custom rom designed for your phone will not hard brick it as it will never touch the bootloader so you will always be able to enter fastboot mode
Of course you can soft brick which means it either bootloops or you cant access recovery if you don't follow the correct process but you can solve that just by repeating the process correctly
All right, I will give it a try at evening (not enough time right now). So If I will do the fastboot command...
Code:
fastboot erase userdata
...what will happen? Is it the same procedure as factory reset + wipe cache?
Mcandrew2809 said:
All right, I will give it a try at evening (not enough time right now). So If I will do the fastboot command...
Code:
fastboot erase userdata
...what will happen? Is it the same procedure as factory reset + wipe cache?
Click to expand...
Click to collapse
yes but it also wipes everything on internal storage data partition
A reset + wipe cache will format data but not user data (things that are stored on internal storage such as pictures music documents downloads)
It does not format system or anything else
Thank you, it helped a lot! :highfive:
EDIT: what's difference between erase and format in fastboot? Would something bad happen if i do format command instead of erase?
Mcandrew2809 said:
Thank you, it helped a lot! :highfive:
EDIT: what's difference between erase and format in fastboot? Would something bad happen if i do format command instead of erase?
Click to expand...
Click to collapse
Iv no idea - it will either give an error unknown command or do something
erase userdata is the correct use
Hello,
I have the same phone and like to download the stock rom first before flashing a custom one (RR e.g.). I can't find anywhere a download for this version's custom rom yet. Is there any way to save the stock rom out of the still unmodified phone?
Thanks for your help!
Bro.. check this.. npps is for xt 1676 ( Europe, Turkey ) and npp is for xt 1677 ( India) . Both are dual sim 3gb version phones.. just may be customization difference. Hopefully all modem bands may work.
Npps or xt 1676 unfortunately dont have version above 25.137-15 ( which is an older firmware from what u have ) , so never flash it.
But npp have higher version 72/76/82.
Just in case u are not confident enough avoid gpt, and bootloader flashing.
Btw.. if you have messed up ur bootloader ( cant boot into fastboot) .. i think give these files a try.. btw.. you have nothing to loose since u have messed up pretty bad with bootloader.
This is the only last try till Oreo upadate ( if moto ever release it for g5)
Btw.. if u get successful.. please share.
https://www.clangsm.com/forum/index.php?showtopic=482933
---------- Post added at 02:34 PM ---------- Previous post was at 02:16 PM ----------
And if u are worried about modem ( which may cause wifi /signal issue) avoid flashing modem or try flashing old modem from npps25.137-15 ( the file is available in same directory) you can use the modem file only for flashing )
I mean.. first flash the complete npp25.137-76 ( i choose that file because its non branded ) .. after successful boot, check wifi and sim.
If everything is ok.. use the same..
If you have problems with wifi or sim..
Use modem file from npps 25.137-15 and flash modem partion only.
Or completely avoid all trial and error methods. And just flash npp25-137-76 with out flashing modem , bootloader, gpt, - its just like flashing a new kernel and system.. everything except system and kernel will remanin the same.
The method works only if u have a working bootloader. If its not there.. there is no way to trial and error things.. till u courageously flash the bootloader and gpt from npp version..
Hope you will get something.
---------- Post added at 02:51 PM ---------- Previous post was at 02:34 PM ----------
Currently.. my xt1676 is working with August security update ( npps - 25.137-72-4 ) rooted, unlocked.. i am trying hard to mess it up.. unfortunately twrp backup helps me to unbrick few times!! But soon or later i will manage to mess it up!!!???
Only then i will give these files a try... ( Or atlest till pixel 2 comes to retailer near by) . For now this is my backup phone after selling s7 edge.
This is just 2 weeks old.. and i manage to mess its os 5-6 times till now.. so i think i will be joining your club soon
Just the same phone as yours..2 weeks old.. but its alive till now.
showlyshah said:
Just the same phone as yours..2 weeks old.. but its alive till now.
Click to expand...
Click to collapse
Hi. Sorry for bumping an old thread but I thought it was better then to make a new one.
I bought this phone a few days ago and it had NPPS25.137-72-4 when delivered. Been trying to read up a bit on this device but since I'm used to samsung, it all takes a while to figure things out
Got it unlocked/rooted fine, but I want to make sure I have something to fall back on in case of trouble.
I've been searching for this fw without any luck. Any chance some one got it and can share it?
NPPS25.137-72-4
Or if anyone can suggest a different one that could work. ( I don't really understand the fw names yet)
Thanks in advance.
tys0n said:
Hi. Sorry for bumping an old thread but I thought it was better then to make a new one.
I bought this phone a few days ago and it had NPPS25.137-72-4 when delivered. Been trying to read up a bit on this device but since I'm used to samsung, it all takes a while to figure things out
Got it unlocked/rooted fine, but I want to make sure I have something to fall back on in case of trouble.
I've been searching for this fw without any luck. Any chance some one got it and can share it?
NPPS25.137-72-4
Or if anyone can suggest a different one that could work. ( I don't really understand the fw names yet)
Thanks in advance.
Click to expand...
Click to collapse
Take a twrp backup .. a clean one..
tys0n said:
Hi. Sorry for bumping an old thread but I thought it was better then to make a new one.
I bought this phone a few days ago and it had NPPS25.137-72-4 when delivered. Been trying to read up a bit on this device but since I'm used to samsung, it all takes a while to figure things out
Got it unlocked/rooted fine, but I want to make sure I have something to fall back on in case of trouble.
I've been searching for this fw without any luck. Any chance some one got it and can share it?
NPPS25.137-72-4
Or if anyone can suggest a different one that could work. ( I don't really understand the fw names yet)
Thanks in advance.
Click to expand...
Click to collapse
There's no flash able zips of stock ROMs here unfortunately. Weird for me too since I was Samsung through and through. Take a back up of your own ROM via TWRP or you can use the debloated stock ROM by Fedray on the ROM forum.
showlyshah said:
Take a twrp backup .. a clean one..
Click to expand...
Click to collapse
Smonic said:
There's no flash able zips of stock ROMs here unfortunately. Weird for me too since I was Samsung through and through. Take a back up of your own ROM via TWRP or you can use the debloated stock ROM by Fedray on the ROM forum.
Click to expand...
Click to collapse
Thanks for your answers.Thats actualy first thing I did after flashing twrp to have a clean backup of system and boot.
I also made a few partition backups in terminal, like persist, oem, modem and a few others so hopefully I'm fine.
Do you guys know if I can take stock recovery from lower version fw in case I would ever need it again?
I highly doubt I ever will, but just in case
Edit: If anyone needs a system/boot backup of this fw, just let me know and I'll upload it.
tys0n said:
Thanks for your answers.Thats actualy first thing I did after flashing twrp to have a clean backup of system and boot.
I also made a few partition backups in terminal, like persist, oem, modem and a few others so hopefully I'm fine.
Do you guys know if I can take stock recovery from lower version fw in case I would ever need it again?
I highly doubt I ever will, but just in case
Edit: If anyone needs a system/boot backup of this fw, just let me know and I'll upload it.
Click to expand...
Click to collapse
Infact i need a full twrp backup of the exact same firmware.. if u can uplaod.. please do that.. btw.. if u need recovery image i can extract it from ota.. and send to you.
showlyshah said:
Infact i need a full twrp backup of the exact same firmware.. if u can uplaod.. please do that.. btw.. if u need recovery image i can extract it from ota.. and send to you.
Click to expand...
Click to collapse
Yes please. If you could do that, that would be great
I'll zip the backup and upload it in a few hours when I get to my computer.
tys0n said:
Yes please. If you could do that, that would be great
I'll zip the backup and upload it in a few hours when I get to my computer.
Click to expand...
Click to collapse
Me too.. i will do it tomorrow itself.
Ok, here we go. Stock TWRP backup from XT1676.
NPPS25.137-72-4
CEDRIC_XT1676-NPPS25.137-72-4_TWRP.zip
Unzip, put in your twrp backup folder and restore.
https://firmware.gem-flash.com/index.php?a=browse&b=category&id=13304
I got this too..
Hi guys, I'm going to buy a OnePlus 5T, coming from a Motorola Moto X Play.
I used to do basic and old modding, without a need to think about project Treble or encrypt/decrypt.
I know now it is project Treble enabled also in stable channel, so now I would like to take away some doubts.
I actively watched threads and updates but I'm really confused by a big amount of things to consider, like:
- Do I need a Treble compatible Magisk?
- Do I need a Treble compatible TWRP?
- What's "no-verity" useful for? Why could I need to decrypt my OP5T?
- Do I have to follow a specific procedure to flash official updates if I have a custom recovery and Magisk installed?
So... A good list of ToDo, things I need to know before bricking the new beautiful entry is the request :angel:
If you can help me also with links, I'll appreciate.
nplezka said:
- Do I need a Treble compatible Magisk?
- Do I need a Treble compatible TWRP?
- What's "no-verity" useful for? Why could I need to decrypt my OP5T?
- Do I have to follow a specific procedure to flash official updates if I have a custom recovery and Magisk installed?
Click to expand...
Click to collapse
This guide is great to give you a start.
- No, you don't need Treble compatible Magisk. Magisk 16.0 works fine.
- Yes, you need the latest blu_spark or codeworkx TWRP. You can get to them from the guide above. Don't use the official TWRP btw.
- (I'm not very knowledgeable about this) I believe no-verity is to keep the device decrypted. I'm running it encrypted at the moment and see no reason to decrypt the phone.
- Kinda specific but nothing special. Here's my procedure (I'm running stable OOS ROM):
Download Full ZIP file (~1.6 GiB), not the OTA one. If your phone is rooted, system update will download the full file (instead of the ota); or you can use Oxygen Updater from the app store.
Change lockscreen lock from passcode to none (because my TWRP can't run properly with passcode. I have heard that many people don't need to do this)
Reboot to TWRP recovery
Flash Full Zip and Magisk in that order
(Some people say clear cache/dalvik before and after flashing, idk)
Reboot to system and change lock screen back to normal.
I think there's no big to do stuff with oneplus if you only do basic modding but I run my device fairly basic anyway so others can chime in with more advanced stuffs.
squaresmile said:
[*]Change lockscreen lock from passcode to none (because my TWRP can't run properly with passcode. I have heard that many people don't need to do this)
Click to expand...
Click to collapse
Maybe it's a stupid question, but I never had a pin or password on my lockscreen, and for sure I will simply use the fingerprint (or face-unlock? ?) on my future OP5T, so this point is only for who use a password/pin/sequence, right?
nplezka said:
Maybe it's a stupid question, but I never had a pin or password on my lockscreen, and for sure I will simply use the fingerprint (or face-unlock? ) on my future OP5T, so this point is only for who use a password/pin/sequence, right?
Click to expand...
Click to collapse
Pretty sure you need password/pin to use fingerprint/face unlock. However, I have heard that others can go to TWRP fine with a password/pin so you probably will be fine. I must have messed up somewhere I'm too lazy to fix now.
squaresmile said:
Pretty sure you need password/pin to use fingerprint/face unlock. However, I have heard that others can go to TWRP fine with a password/pin so you probably will be fine. I must have messed up somewhere I'm too lazy to fix now.
Click to expand...
Click to collapse
Do you think I have to do something in particular when I'll update to the OOS update with Treble, starting from the in-built firmware (don't know the exact version, but I'm talking about Nougat)? Or I can update normally?
It'll be the first thing I'll do, before unlocking and rooting. :cyclops:
nplezka said:
Do you think I have to do something in particular when I'll update to the OOS update with Treble, starting from the in-built firmware (don't know the exact version, but I'm talking about Nougat)? Or I can update normally?
It'll be the first thing I'll do, before unlocking and rooting. :cyclops:
Click to expand...
Click to collapse
Probably not if you follow the updater in settings. I would expect the stock update process to be pretty stable.
Sorry for the silly question , but can we downgrade from oreo to MM ? No root !
i know that is a bootloader issue like 8 have a bootloader and 6 a differet one , but is there a way to bypass this ?
the A5 2017 threds are DEAD
Naikkon said:
the A5 2017 threds are DEAD
Click to expand...
Click to collapse
is one of the reasons I'm leaving the a5 2017...
@Naikkon, if you have installed the update with July security patch it's not even possible to downgrade to nougat (from what I read on other threads)
Edy97 said:
@Naikkon, if you have installed the update with July security patch it's not even possible to downgrade to nougat (from what I read on other threads)
Click to expand...
Click to collapse
I wouldn't take that as gospel. Even if the bootloader cannot be downgraded, often bootloaders are backwards compatible. Therefore flashing everything except BL should work.
ashyx said:
I wouldn't take that as gospel. Even if the bootloader cannot be downgraded, often bootloaders are backwards compatible. Therefore flashing everything except BL should work.
Click to expand...
Click to collapse
Hey dude. Since you seem to be active, will you answer my one query?
I have the Korean U+ variant of the A5 2017. I have flashed twrp(from the dev that is making Hades ROM), downgraded to the Nougat BL and modem but I can't flash any custom ROM such as Lineage. It just gets stuck at patching system unconditionally. Yes, I have wiped everything from including data and system and everything, changed recoveries to the ones from @RaymanFX but nothing seems to help. Seems the system partition just can't be flashed the Lineage way on my phone. I however made a fellow xda member @moozer make a twrp backup of Lineage and was able to restore and run it pretty smooth but can't flash OTA's or anything. I mostly active here so if you need something from my side like the logs I'll always be here but please look into my issue so these issue can be easily resolved in the future and people like me don't have to suffer as much.
Did you wipe or FORMAT the Data partition? Wipe will not work.
ashyx said:
Did you wipe or FORMAT the Data partition? Wipe will not work.
Click to expand...
Click to collapse
Absolutely I did FORMAT the DATA partition, did type "yes" and I think that's because the encryption on the /data partition might come to play right? The issue is driving me nuts since its the first time I've faced something like this and have no idea how to fix this. Sorry for the late reply since you didn't quote me had no idea you actually replied. @ashyx ???????
Edwin Hamal said:
Absolutely I did FORMAT the DATA partition, did type "yes" and I think that's because the encryption on the /data partition might come to play right? The issue is driving me nuts since its the first time I've faced something like this and have no idea how to fix this. Sorry for the late reply since you didn't quote me had no idea you actually replied. @ashyx ???????
Click to expand...
Click to collapse
Sometimes this can happen if there is an issue with the system partition.
I suggest to go to the advanced wipe options. Select to change the format of the SYSTEM partition. First change it to EXT2 then change it back to EXT4. This will FORMAT the partition.
Next FORMAT DATA.
If that doesn't do it then there is either an issue with the ROM or your device isn't compatible with the ROM.
This is my question. I'm currently on ATTMX channel, but, my carrier has being saying in lot of forums AT&T México, that we are not being updated to Android Pie, due to end of cycle. I already found that:
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
Is where you can find the update already in Stock format. My Albus is under OPSS27.76-12-25-15-2-4. But that's my question if not, I'm just leaving already the phone, wasn't all that worth it after all, but if I can update it, would be awesome for a second hand move.
Any kind of help, or comment, would be awesome. Thanks.
Vesaniaheim said:
This is my question. I'm currently on ATTMX channel, but, my carrier has being saying in lot of forums AT&T México, that we are not being updated to Android Pie, due to end of cycle. I already found that:
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
Is where you can find the update already in Stock format. My Albus is under OPSS27.76-12-25-15-2-4. But that's my question if not, I'm just leaving already the phone, wasn't all that worth it after all, but if I can update it, would be awesome for a second hand move.
Any kind of help, or comment, would be awesome. Thanks.
Click to expand...
Click to collapse
In theory, it is possible to update.
My device is RETAR channel. And I updated using this file from the RETAIL channel.
Sorry if my English is not good: D
I also have a xt1706 from att mx, i used the method in this post https://forum.xda-developers.com/z2-play/how-to/download-z2-play-pie-ota-t3977367 but i had to install first the stock rom for retail moddel, exactly the ALBUS_RETAIL_8.0.0_OPSS27.76-12-25-23_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, after that i copied the ota file from the post above to internal storage, searched on my system apps for motorola update services, give it storage permissions, reboot phone and when it booted the OTA appeared, so i just installed the OTA and rebooted, everything is working fine, a lot better than oreo stock or other pie based roms. the only issue i had was with Netflix, i can't install from play store due the phone showing on search for updates that system integrity is at risk.
What i'm trying to do now to solve that is to install the retail version of pie from this https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/ In the past i've installed some retail version from this web and everything worked fine so i hope installing the retail pie stock everything will work fine, speacially with netflix xD maybe i'll root because i need to record calls and none of the record callers are working fine because of the compatibility with pie, the only working method is with root.
I will update this if my attempt to install the retail version of pie and/or rooting is successful
Vesaniaheim said:
This is my question. I'm currently on ATTMX channel, but, my carrier has being saying in lot of forums AT&T México, that we are not being updated to Android Pie, due to end of cycle. I already found that:
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
Is where you can find the update already in Stock format. My Albus is under OPSS27.76-12-25-15-2-4. But that's my question if not, I'm just leaving already the phone, wasn't all that worth it after all, but if I can update it, would be awesome for a second hand move.
Any kind of help, or comment, would be awesome. Thanks.
Click to expand...
Click to collapse
I have the XT1710-06 AMXMX Channel (not the ATTMX) with bootloader unlocked and rooted with Magisk. I upgraded to Pie using the retail version firmware from the page you mention.
1.- First I was on this stock Oreo version for my phone: XT1710-06_ALBUS_AMXMX_8.0.0_OPSS27.76-12-25-15-2-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2.- Then I installed the retail Oreo ALBUS_RETAIL_8.0.0_OPSS27.76-12-25-23_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip to check if everything was working fine
3.- And finally I installed Pie with this firmware: ALBUS_RETAIL_9.0_PPS29.133-30_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Maybe I could skiped the step 2, I'm not sure.
I had an issue with my SD Card because system said it was damaged and I had to format it like 2 or 3 times. This happened randomly when I restarted the phone. Now all is working fine.
irvingagm said:
What i'm trying to do now to solve that is to install the retail version of pie from this https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/ In the past i've installed some retail version from this web and everything worked fine so i hope installing the retail pie stock everything will work fine, speacially with netflix xD maybe i'll root because i need to record calls and none of the record callers are working fine because of the compatibility with pie, the only working method is with root.
I will update this if my attempt to install the retail version of pie and/or rooting is successful
Click to expand...
Click to collapse
The thing with Netflix will be solved once you rooted your phone with Magisk.
̶Y̶e̶s̶ ̶y̶o̶u̶ ̶c̶a̶n̶,̶ ̶b̶u̶t̶ ̶a̶t̶ ̶l̶e̶a̶s̶t̶ ̶m̶y̶ ̶X̶T̶1̶7̶1̶0̶-̶0̶6̶ ̶h̶a̶s̶ ̶i̶s̶s̶u̶e̶s̶ ̶r̶e̶c̶o̶g̶n̶i̶z̶i̶n̶g̶ ̶t̶h̶e̶ ̶U̶S̶B̶ ̶c̶o̶n̶n̶e̶c̶t̶i̶o̶n̶ ̶o̶n̶ ̶P̶C̶.̶ ̶I̶ ̶h̶a̶v̶e̶ ̶t̶e̶s̶t̶e̶d̶ ̶m̶a̶n̶y̶ ̶c̶u̶s̶t̶o̶m̶ ̶R̶O̶M̶'̶s̶,̶ ̶A̶O̶S̶P̶,̶ ̶A̶E̶X̶,̶ ̶L̶i̶n̶e̶a̶g̶e̶ ̶O̶S̶ ̶f̶o̶r̶ ̶8̶.̶1̶,̶ ̶9̶ ̶a̶n̶d̶ ̶1̶0̶ ̶a̶n̶d̶ ̶e̶v̶e̶r̶y̶ ̶s̶i̶n̶g̶l̶e̶ ̶o̶n̶e̶ ̶o̶f̶ ̶t̶h̶e̶m̶ ̶g̶e̶t̶s̶ ̶t̶h̶e̶ ̶U̶S̶B̶ ̶c̶o̶n̶n̶e̶c̶t̶i̶o̶n̶ ̶w̶o̶r̶k̶i̶n̶g̶ ̶p̶r̶o̶p̶e̶r̶l̶y̶,̶ ̶h̶o̶w̶e̶v̶e̶r̶,̶ ̶a̶l̶s̶o̶ ̶e̶v̶e̶r̶y̶ ̶s̶i̶n̶g̶l̶e̶ ̶o̶n̶e̶ ̶o̶f̶ ̶t̶h̶o̶s̶e̶ ̶c̶u̶s̶t̶o̶m̶ ̶R̶O̶M̶s̶ ̶h̶a̶s̶ ̶i̶s̶s̶u̶e̶s̶ ̶w̶i̶t̶h̶ ̶t̶h̶e̶ ̶S̶p̶e̶a̶k̶e̶r̶s̶,̶ ̶s̶p̶e̶c̶i̶a̶l̶l̶y̶ ̶w̶h̶e̶n̶ ̶t̶h̶e̶r̶e̶ ̶i̶s̶ ̶a̶n̶ ̶o̶n̶g̶o̶i̶n̶g̶ ̶c̶a̶l̶l̶ ̶i̶t̶ ̶d̶i̶s̶t̶o̶r̶t̶s̶ ̶t̶h̶e̶ ̶a̶u̶d̶i̶o̶ ̶s̶o̶ ̶m̶u̶c̶h̶ ̶i̶t̶ ̶i̶s̶ ̶i̶m̶p̶o̶s̶s̶i̶b̶l̶e̶ ̶t̶o̶ ̶u̶s̶e̶ ̶t̶h̶e̶ ̶p̶h̶o̶n̶e̶ ̶d̶a̶i̶l̶y̶ ̶f̶o̶r̶ ̶c̶a̶l̶l̶s̶,̶ ̶w̶h̶i̶c̶h̶ ̶i̶n̶t̶e̶r̶e̶s̶t̶i̶n̶g̶l̶y̶ ̶t̶h̶i̶s̶ ̶i̶s̶s̶u̶e̶ ̶d̶o̶e̶s̶ ̶n̶o̶t̶ ̶h̶a̶p̶p̶e̶n̶ ̶o̶n̶ ̶S̶t̶o̶c̶k̶ ̶R̶O̶M̶.̶ ̶H̶a̶s̶ ̶a̶n̶y̶o̶n̶e̶ ̶h̶a̶d̶ ̶t̶h̶i̶s̶ ̶p̶r̶o̶b̶l̶e̶m̶?̶
EDIT: Actually the USB connection issue is caused by a bad guide that lacks some commands. This guide gets everything right without any issues.
https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-flash-update-stock-rom-t3838213
EDIT2: The audio issue only affects users who have upgraded to Stock Pie. This ROM's modem file causes distortion on audio during calls and must be avoided during the upgrading process. To fix the audio issue simply flash the modem file from Stock Android Oreo.
I'm currently on OPSS27.76-12-25-15-2-4
Can i upgrade directly to PPS29.133-30
Or do i need to flash them one by one (That would be annoying and nonsensical).
Please confirm.
Yes, you can.
AndroidManager said:
I'm currently on OPSS27.76-12-25-15-2-4
Can i upgrade directly to PPS29.133-30
Or do i need to flash them one by one (That would be annoying and nonsensical).
Please confirm.
Click to expand...
Click to collapse
I actually fixed the USB connection issue, it was actually caused by a bad installation (one of those flashing adb guides has missing commands needed for proper USB mode to function properly), this is NOT ROM issue as the missing commands will cause the USB connection to fail whether it is Nougat, Oreo or Pie.
Follow this guide. https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-flash-update-stock-rom-t3838213
But keep in mind one thing.
Avoid flashing the modem file NON-HLOS.bin because it is known the modem file from Stock Pie causes audio issues on Custom ROMs. This will be helpful later if you decide to flash Custom ROMs into it.
Ok. One more thing. My phone model is xt1710-06. That ROM is compatible with it right? Please reply soon, as I'm about to flash it.
leodexe said:
I actually fixed the USB connection issue, it was actually caused by a bad installation (one of those flashing adb guides has missing commands needed for proper USB mode to function properly), this is NOT ROM issue as the missing commands will cause the USB connection to fail whether it is Nougat, Oreo or Pie.
Follow this guide. https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-flash-update-stock-rom-t3838213
But keep in mind one thing.
Avoid flashing the modem file NON-HLOS.bin because it is known the modem file from Stock Pie causes audio issues on Custom ROMs. This will be helpful later if you decide to flash Custom ROMs into it.
Click to expand...
Click to collapse
yes
AndroidManager said:
Ok. One more thing. My phone model is xt1710-06. That ROM is compatible with it right? Please reply soon, as I'm about to flash it.
Click to expand...
Click to collapse
Do you speak spanish by any chance? I also have that model and that one comes from Spanish Providers for Latin America. I had some issues earlier because of some inaccuracies and other stuff I wasn't aware like the modem thing from Stock Android 9 distorting audio during calls. Now I got everything working properly and flashed Custom ROM AEX (you need Treble TWRP to flash custom ROMs) with working audio without problems.
I tried the internal storage method, but nothing happened. Then i tried the ADB method, which also failed (invalid signature). I'm gonna try to update to OPSS27.76-12-25-23 first, if that works, then I'll attempt to upgrade to PPS29.133-30 again.
In any case, it's very annoying. Let's hope it works though.
Once I'm done with that, I have to waste more time on rooting it, then enabling Camera2 API & Wireless display...
I tried the internal storage method, but nothing happened. Then i tried the ADB method, which also failed (invalid signature). I'm gonna try to update to OPSS27.76-12-25-23 first, if that works, then I'll attempt to upgrade to PPS29.133-30 again.
In any case, it's very annoying. Let's hope it works though.
Once I'm done with that, I have to waste more time on rooting it, then enabling Camera2 API & Wireless display...
Are you using fastboot or mfastboot? And you are using up to date adb?
Didn't work. Invalid signature again. :/
Screw this. I'm gonna unlock bootloader, then root the phone, then flash Pie ROM through RSDlite. If even that fails, then screw Pie. I'll stay on Oreo.
AndroidManager said:
I tried the internal storage method, but nothing happened.
Click to expand...
Click to collapse
Sometimes this method works, sometimes may not work.
AndroidManager said:
Then i tried the ADB method, which also failed (invalid signature). I'm gonna try to update to OPSS27.76-12-25-23 first, if that works, then I'll attempt to upgrade to PPS29.133-30 again.
Click to expand...
Click to collapse
You need bootloader unlocked for this process.
felipecassiors said:
Your bootloader must be unlocked.
Click to expand...
Click to collapse
JulioCeesarC said:
I recomend bootloader unlocked for this process
Click to expand...
Click to collapse
HTCDevil said:
Bootloader unlocked but without root
Click to expand...
Click to collapse
RSDLite didn't work either. It was not able to detect my device at all, so i couldn't proceed flashing this way.
Then i followed this video: https://www.youtube.com/watch?v=n57v9r2jysw
It's basically the same as the ADB method, except he extracts the ZIP file & uses individual commands to flash all items. I tried his method, and it worked wonders. I'm on Pie ROM now, it's all good.
AndroidManager said:
RSDLite didn't work either. It was not able to detect my device at all, so i couldn't proceed flashing this way.
Click to expand...
Click to collapse
RSD Lite isn't recommended as it can screw up your basebands getting a phone with no signal whatsoever. The standard ADB fastboot is recommended over everything else.
AndroidManager said:
Then i followed this video: https://www.youtube.com/watch?v=n57v9r2jysw
Click to expand...
Click to collapse
In 1:30 of the video, the following commands are missing:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
Without these commands, the USB and MTP Mode of the phone will never work. This is true for the XT-1710-06, and probably true for all other variants. Besides, it will do a heavier installation, meaning it will install all the OEM stuff that will eat space, resources and you will not probably use anyways.
AndroidManager said:
It's basically the same as the ADB method, except he extracts the ZIP file & uses individual commands to flash all items. I tried his method, and it worked wonders. I'm on Pie ROM now, it's all good.
Click to expand...
Click to collapse
Yes, it is, in fact, it is the exact same method as the standard ADB fastboot flash, because you need to extract the zip file anyways. But this video is mostly based on @JulioCeesarC's guide, which specifically lacks these three commands which are needed for a proper correct installation.
A better guide for flashing/updating Z2P to Pie 9.0 is this one: https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-flash-update-stock-rom-t3838213
The first statement in this guide is that YOUR BOOTLOADER must be unlocked for this process. This will become useful later if something goes wrong. As a locked bootloader can render the phone completely bricked if something goes wrong during the process. You were so LUCKY because your locked bootloader refused to flash the update. Otherwise you could end with a dead unrecoverable phone.
However, all of these guides in XDA forgets another important REQUIRED step:
If you upgrade to Stock Pie, and you decide to flash a Custom ROM later, you will have audio issues during calls. This is caused by the Stock Pie's faulty modem file (NON-HLOS.bin), the good thing is that the Stock Oreo's modem file works flawlessly and must be skipped during the upgrading/flashing process.
If you wanted a Spanish guide, then all you had to do is just ask for one. There might be more spanish users that don't quite understand english very well and might mess up with this trivial process. I will make a Spanish guide to help them and avoid more conflicts and unwanted bricks. I know all this through proper testing with trial and error.
Hey. I just tried plugging USB, and it is working fine. Even File transfer mode is working fine... I have not noticed any issues so far. So I'm gonna keep it as is without reflashing the ROM with those additional commands. If i encounter an issue later, i will consider your suggestion.
BTW, Now i am running Pie & have an unlocked bootloader. Please tell me the proper way to root the phone. I tried rooting before with TWRP & Magisk, but the phone went to bootloop. I then had to reflash the Pie ROM with ADB method to get it working again. I think the problem has to do with DM-Integrity & Encryption, but I've already wasted hours getting Pie to run on it, and don't want to waste more hours trying to root it. So a quick and easy working guide would be useful.
Also, i don't intend to install any custom ROMs on it. I just have to root it so i can enable Camera2 API (disabled on my variant), and enable wifi display (disabled by default on most AOSP based ROMs, including mine).
BTW, I don't understand spanish. I was looking for guides and found that video. I enabled english subtitles & understood enough to give it a shot. I have some experience with flashing & rooting in the past, so i can understand these concepts and methods.
Well, i followed this thread: https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
And was able to root my phone without bootlooping. All is well for now. Now i will enable Wifi Display & Camera2 API. Once those are done. I'll have peace at last.
---------- Post added at 01:47 AM ---------- Previous post was at 01:27 AM ----------
Just successfully enabled wireless display (persist.debug.wfd.enable=1) & camera2 API (persist.camera.HAL3.enabled=1) within build.prop
Both are working as intended. I have succeeded in doing everything i desired to do. It only took a bunch of hours & a headache...
But thanks a lot to "leodexe" for helping me out. You're cool, friend!
AndroidManager said:
Hey. I just tried plugging USB, and it is working fine. Even File transfer mode is working fine... I have not noticed any issues so far. So I'm gonna keep it as is without reflashing the ROM with those additional commands. If i encounter an issue later, i will consider your suggestion.
Click to expand...
Click to collapse
Oh, mine is XT1710-06 and it had issues with the USB mode, I figured out it was because of the missing OEM commands, I tested several times flashing without these and the USB connection would never work, after a simple flash with all the commands it started to work again, so if yours worked without these then maybe it's a thing of luck. But keep in mind that without the OEM commands there will be more installed stuff, I prefer to include the OEM commands to remove all the bloatware, so the user can decide which thing to install later.
AndroidManager said:
BTW, I don't understand spanish. I was looking for guides and found that video. I enabled english subtitles & understood enough to give it a shot. I have some experience with flashing & rooting in the past, so i can understand these concepts and methods.
Click to expand...
Click to collapse
I am doing a spanish guide anyways, so spanish users can properly do the upgrade process without messing everything.
AndroidManager said:
I have succeeded in doing everything i desired to do. It only took a bunch of hours & a headache...
Click to expand...
Click to collapse
Same feeling bro, it took me a few nights and lots of headaches to get things working after upgrading.
AndroidManager said:
But thanks a lot to "leodexe" for helping me out. You're cool, friend!
Click to expand...
Click to collapse
Hey, thanks, no problem, the first time I arrived at this forum I had no clue how to do most things, so I'm here to help anyone whenever I can. Keep up the good work!
Hello,
I have a device that I obtained through beta testing that has not been released yet. I am allowed to keep the device now that testing is over. I am not happy with the stock rom and some of the apps it forces you to keep. I cannot remove them through ABD either. There is no stock ROM image available yet. Therefore, I cannot port TWRp or root.
I stumbled on project treble. I ran treble check and it says my phone is supported as it came with android 11. It supports systemless updates and has A/B system partition. I really like stock android ASOP. Is there anyway I can flash a generic image? What's the odds of it working correctly? Since there is no image available yet and I cannot port TWRP I have to worrying about not being able to recover the device if things go wrong. I know you can flash without TWRP which is why I decided to ask about this. Would I have a better chance flashing roms for supported devices with similar hardware? How should I proceed?
Thanks,
Rocky
as long as you have a compatible custom recovery AND the stock rom in case something go wrong, you can flash any GSI according to your device's architecture
Roizoulou said:
as long as you have a compatible custom recovery AND the stock rom in case something go wrong, you can flash any GSI according to your device's architecture
Click to expand...
Click to collapse
Since it is a beta unit I have neither as it has not been officially released. I have never flashed one of these roms so I do not know how well they work after flashing. I know the device has a pretty popular SOC which is a snapdragon 750g so I would assume if a gai runs good on another device using the 750g then it should work.
bigroc2223 said:
Since it is a beta unit I have neither as it has not been officially released. I have never flashed one of these roms so I do not know how well they work after flashing. I know the device has a pretty popular SOC which is a snapdragon 750g so I would assume if a gai runs good on another device using the 750g then it should work.
Click to expand...
Click to collapse
best you can do is dump the whole rom, make a backup before going any further
Roizoulou said:
best you can do is dump the whole rom, make a backup before going any further
Click to expand...
Click to collapse
I don't think I can dump it without root right?
bigroc2223 said:
I don't think I can dump it without root right?
Click to expand...
Click to collapse
an unlocked bootloader first and just search for how to dump system on google. it usually just need a pc and ADB
bigroc2223 said:
I don't think I can dump it without root right?
Click to expand...
Click to collapse
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
Roizoulou said:
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried this before it requires root. I just double checked and the prereqs say root required too. This sucks because the device has decent specs. It's just the ROM and software on it are crappy. After doing some reading the biggest thing I'm worried about is flashing and not having mobile data since it is a 5g phone. I read about someone else flashing and not being able to get their mobile data to work.
bigroc2223 said:
I tried this before it requires root. I just double checked and the prereqs say root required too. This sucks because the device has decent specs. It's just the ROM and software on it are crappy. After doing some reading the biggest thing I'm worried about is flashing and not having mobile data since it is a 5g phone. I read about someone else flashing and not being able to get their mobile data to work.
Click to expand...
Click to collapse
what is the device?
Roizoulou said:
what is the device?
Click to expand...
Click to collapse
It's a beta device from TCL. It has not been released yet. I read that phh GSI should be compatible with all android phones with treble support. Therefore, I think I might just go for it. The only thing is if I end up with a bug I more than likely will probably have to figure it out on my own.
bigroc2223 said:
It's a beta device from TCL. It has not been released yet. I read that phh GSI should be compatible with all android phones with treble support. Therefore, I think I might just go for it. The only thing is if I end up with a bug I more than likely will probably have to figure it out on my own.
Click to expand...
Click to collapse
just try phh's first and if you encounter issues, try other custom roms
Roizoulou said:
just try phh's first and if you encounter issues, try other custom roms
Click to expand...
Click to collapse
I think I might of found a solution. I am pretty sure there is a way to boot a ROM before flashing it. I could of sworn I read this somewhere. It was an adb command. It allowed you too boot the ROM instead of flashing it. This would allow me to preview the ROM before officially flashing it to the device. I just cannot remember where I saw this at or the command.
My goal is to get a working gsi installed. From there I would like to get TWRP flashed on the device so it can be rooted. If I would need to port TWRP I think I could figure it out. This way when the device is officially released it will have TWRP ready to go for it. Also, since it will have TWRP I will be able to start porting roms as soon as they release the system image.
bigroc2223 said:
I think I might of found a solution. I am pretty sure there is a way to boot a ROM before flashing it. I could of sworn I read this somewhere. It was an adb command. It allowed you too boot the ROM instead of flashing it. This would allow me to preview the ROM before officially flashing it to the device. I just cannot remember where I saw this at or the command.
My goal is to get a working gsi installed. From there I would like to get TWRP flashed on the device so it can be rooted. If I would need to port TWRP I think I could figure it out. This way when the device is officially released it will have TWRP ready to go for it. Also, since it will have TWRP I will be able to start porting roms as soon as they release the system image.
Click to expand...
Click to collapse
like DSU loader?
Roizoulou said:
like DSU loader?
Click to expand...
Click to collapse
Never heard of that this was just an adb command.
I just downloaded ASOP 11.0 v309. Treble info says my device requires system-arm64-ab.img.xz. So I downloaded system-roar-arm64-ab-gapps.img.xz and system-roar-arm64-ab-vanilla.ikg.gz so hopefully those are the right ones. One has Gapps and one does not. Was going to flash the Gapps version first and see how things go. Then if need be flash vanilla.
I got a problem with phone calls. When I dial out I get call ended. Incoming calls I can hear them ring but get no way to answer. Also I am not getting text messages.
Roizoulou said:
like DSU loader?
Click to expand...
Click to collapse
I got it all working bro thanks for your help
bigroc2223 said:
I got it all working bro thanks for your help
Click to expand...
Click to collapse
gapps or vanilla?
Roizoulou said:
gapps or vanilla?
Click to expand...
Click to collapse
I was able to get them both to work. However, I am trying to use the gapps version, but I am getting an error that the device is not google certified. I cannot find a workaround unless I unroot which I do not want to do =(
bigroc2223 said:
I was able to get them both to work. However, I am trying to use the gapps version, but I am getting an error that the device is not google certified. I cannot find a workaround unless I unroot which I do not want to do =(
Click to expand...
Click to collapse
rooted with magisk?
Roizoulou said:
rooted with magisk
Click to expand...
Click to collapse
It comes rooted with phh superuser. I'm trying to find a way to pull my boot.img from the device so I can use it to flash magisk since it has a workaround for non Google certified devices.