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!
Related
Hi guys! This bootloader unlock version is only for ARGENTINIAN models.
You can donate me (PAYPAL LINK COMING SOON) and @cerg2010cerg2010 through paypal.
@cerg2010cerg2010 PAYPAL EMAIL: [email protected] OR QIWI: +79157840294
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
No more secure boot error!
I thank my friend @cerg2010cerg2010 for helping me out in patching the aboot.
Supported Model:
Code:
H440AR
-> Steps:
(1) Downgrade to v10a or v10d version of Android.
(2) Root your device.
(3) Download this patched aboot file. Click Here for v10a. Click Here for v10d.
(4) Connect your phone to the computer. In command prompt, type "adb shell".
(5) Transfer the aboot file into /sdcard/ folder.
(6) Type "su" to enter the root shell. Then type "dd if=/sdcard/<file_name_you_downloaded_in_3rd step> of=/dev/block/<your aboot partition>".
(7) Restart your phone by typing "reboot".
You have unlocked your bootloader!
Refer Notes for more information.
-> Notes:
1) The aboot_5120_patched.bin or aboot_10d_patched.bin is the patched version of aboot partition of your device. Secure boot validation has been patched such that secure boot is always valid, so you can flash your own TWRP and Custom ROM.
2) Don't upgrade to any updated version of Android if you get any through OTA update. It might brick your device.
I'll give it a try soon, hopefully if the guys here are correct 4g/lte should work now. Thanks a lot!
Edit: apparently this fixed the issue regarding LTE using argentinian bands, I'll keep testing it but so far it holds even after a call and a low signal area it just switches from lte to 3g and so on (which wasn't working with the other aboot)
Korelev said:
I'll give it a try soon, hopefully if the guys here are correct 4g/lte should work now. Thanks a lot!
Edit: apparently this fixed the issue regarding LTE using argentinian bands, I'll keep testing it but so far it holds even after a call and a low signal area it just switches from lte to 3g and so on (which wasn't working with the other aboot)
Click to expand...
Click to collapse
Thanks for confirming!
You did it!!!! Many Many Thanks!!!! T.T
69PerTTu69 said:
You did it!!!! Many Many Thanks!!!! T.T
Click to expand...
Click to collapse
Hey, I'm trying to download the Argentinean aboot, but the link is dead. Can anyone help me with it ?
mayankjet said:
Hey, I'm trying to download the Argentinean aboot, but the link is dead. Can anyone help me with it ?
Click to expand...
Click to collapse
They aren't broken
69PerTTu69 said:
They aren't broken
Click to expand...
Click to collapse
My bad.
links are not working for me
edit: apparently they are now
Quick question: by unlocking the bootloader I should be able to later flash a custom recovery and then root the phone, right? As the argentinian version seems to be unrootable via kingroot (which is what the general thread recommends). Do I got this right, or is there a simple version to root it? Thanks.
Kon22 said:
Quick question: by unlocking the bootloader I should be able to later flash a custom recovery and then root the phone, right? As the argentinian version seems to be unrootable via kingroot (which is what the general thread recommends). Do I got this right, or is there a simple version to root it? Thanks.
Click to expand...
Click to collapse
First you need to be on Lollipop.
Root it by using Kingroot.
Unlock the bootloader.
Flash TWRP 3.1.1.0
Flash MM v20b zip proposed by Korelev.
Flash Supersu.
Now you have a rooted MM.
walterfuster said:
First you need to be on Lollipop.
Root it by using Kingroot.
Unlock the bootloader.
Flash TWRP 3.1.1.0
Flash MM v20b zip proposed by Korelev.
Flash Supersu.
Now you have a rooted MM.
Click to expand...
Click to collapse
I tried rooting it using Kingroot with no success, both with the APK and the app on PC. Running stock lollipop, obviously. I assumed the argentinian version (H440AR) couldn't be rooted via kingroot, which is why I'm wondering if the only way is to simply unlock bootloader, flash TWRP and then flash SuperSU.
Kon22 said:
I tried rooting it using Kingroot with no success, both with the APK and the app on PC. Running stock lollipop, obviously. I assumed the argentinian version (H440AR) couldn't be rooted via kingroot, which is why I'm wondering if the only way is to simply unlock bootloader, flash TWRP and then flash SuperSU.
Click to expand...
Click to collapse
The thing is, you can't unlock the bootloader without first having su permissions.
AR device version shouldn't be a problem.
Mine is Argentinian too and I easily rooted it.
Try with an older version of Kingroot. You can easily find it around apk's sites.
If no luck, try flashing an H440N kdz (I'm on POL v10i) with LG Flash Tool 2014, and see what happens.
You can do a dirty flash if you don't want to lose your data.
P.S.: I even switched from Kingroot to SuperSU. I highly recommend this. Kingroot converts your phone in a turtle.
walterfuster said:
The thing is, you can't unlock the bootloader without first having su permissions.
AR device version shouldn't be a problem.
Mine is Argentinian too and I easily rooted it.
Try with an older version of Kingroot. You can easily find it around apk's sites.
If no luck, try flashing an H440N kdz (I'm on POL v10i) with LG Flash Tool 2014, and see what happens.
You can do a dirty flash if you don't want to lose your data.
P.S.: I even switched from Kingroot to SuperSU. I highly recommend this, Kingroot convert your phone in a turtle.
Click to expand...
Click to collapse
Huh, that's odd then, that Kingroot couldn't do it. I'll keep looking into it, then. Thanks for the help, will report back.
walterfuster said:
The thing is, you can't unlock the bootloader without first having su permissions.
AR device version shouldn't be a problem.
Mine is Argentinian too and I easily rooted it.
Try with an older version of Kingroot. You can easily find it around apk's sites.
If no luck, try flashing an H440N kdz (I'm on POL v10i) with LG Flash Tool 2014, and see what happens.
You can do a dirty flash if you don't want to lose your data.
P.S.: I even switched from Kingroot to SuperSU. I highly recommend this. Kingroot converts your phone in a turtle.
Click to expand...
Click to collapse
Hello there. I managed to use kingroot to root one of the two spirits I have (the other one still doesn't budge, for whatever reason) and indeed it turns the phone into a turtle. I was wondering, is it possible to flash superSU without flashing marshamallow before? Not that I'd mind flashing it, but without the ability to use an SD card as internal storage the main advantage is gone, and I wouldn't wanna have MM if it hurts battery time or fluidity of the phone.
Kon22 said:
Hello there. I managed to use kingroot to root one of the two spirits I have (the other one still doesn't budge, for whatever reason) and indeed it turns the phone into a turtle. I was wondering, is it possible to flash superSU without flashing marshamallow before? Not that I'd mind flashing it, but without the ability to use an SD card as internal storage the main advantage is gone, and I wouldn't wanna have MM if it hurts battery time or fluidity of the phone.
Click to expand...
Click to collapse
If I don't get wrong, you want to stay on a SuperSU rooted LP, right?
Well, you can get that, not by flashing, but by replacing Kingroot with SuperSU.
you'll have to do the following:
https://forum.xda-developers.com/a3...place-kingroot-kinguser-t3308989/post65167979
P.S.: If you decide to stay on LP for definitely, I highly recommend you apply the Tomo's tweaks.
They get the most of Spirit running LP:
https://forum.xda-developers.com/lg...formance-battery-saving-t3217133/post63121297
So if I get this right I should be able to use custom roms after doing this procedure? I've been asking about in the LOS14.1 rom thread but people talking about a bluescreen when they ran out of signal in the argentinian model scared me off. I cant get a new phone atm in case I brick this one. Nobody could give me a definitive answer about it so far.
Niku200 said:
So if I get this right I should be able to use custom roms after doing this procedure? I've been asking about in the LOS14.1 rom thread but people talking about a bluescreen when they ran out of signal in the argentinian model scared me off. I cant get a new phone atm in case I brick this one. Nobody could give me a definitive answer about it so far.
Click to expand...
Click to collapse
Yes, following this procedure can get your bootloader unlocked. Also LOS does have that blue scrren error, only if you don't have network service. However it's not that big of a issue. You can prevent blue screen by using airplane mode.
mayankjet said:
Yes, following this procedure can get your bootloader unlocked. Also LOS does have that blue scrren error, only if you don't have network service. However it's not that big of a issue. You can prevent blue screen by using airplane mode.
Click to expand...
Click to collapse
I knew about that workaround but signal is pretty unstable where I live. Specially when I travel and I like to use spotify while doing so. I'd like to avoid it as much as I can. I guess I'll give it a go and if it fails I can go back flashing a stock firmware.
Niku200 said:
I knew about that workaround but signal is pretty unstable where I live. Specially when I travel and I like to use spotify while doing so. I'd like to avoid it as much as I can. I guess I'll give it a go and if it fails I can go back flashing a stock firmware.
Click to expand...
Click to collapse
Okay.
So, I've been trying to download this several times but I'm always hit with a trafic limit from the person who shared it. Would somebody share me the files somehow?
Hello, I tried downgrading today to oreo (from official version of pie) because I wanted to root and flash resuruction remix rom. I unlocked my bootloader and then I installed android oreo from the website for pixel 2 xl, copied the files into the adb directory and ran the "flash-all" batch file. But now my device is stuck at the google screen with the unlcoked lock image, before this screen it says that my device is corrupt. How can I solve this issue and go back to oreo?
Thanks
abdane said:
Hello, I tried downgrading today to oreo (from official version of pie) because I wanted to root and flash resuruction remix rom. I unlocked my bootloader and then I installed android oreo from the website for pixel 2 xl, copied the files into the adb directory and ran the "flash-all" batch file. But now my device is stuck at the google screen with the unlcoked lock image, before this screen it says that my device is corrupt. How can I solve this issue and go back to oreo?
Thanks
Click to expand...
Click to collapse
Please list your exact steps trying to flash back to Oreo.
Unless I am mistaken (it does happen) I was under the impression flashing the 8.1 factory image was all that's needed to return to stock Oreo.
List your steps/process (and files used) and let's see if someone can't help you out.
Initially, I unlocked my bootloader and data was wiped, then I installed android 8.1 (the recommended version from resuruction remix rom forum) and extracted the files into the directory of adb, then I ran "flash-all" and it was running, then at the end it showed a fail error and now my device is not booting up, I can only access fastboot mode
abdane said:
Hello, I tried downgrading today to oreo (from official version of pie) because I wanted to root and flash resuruction remix rom. I unlocked my bootloader and then I installed android oreo from the website for pixel 2 xl, copied the files into the adb directory and ran the "flash-all" batch file. But now my device is stuck at the google screen with the unlcoked lock image, before this screen it says that my device is corrupt. How can I solve this issue and go back to oreo?
Thanks
Click to expand...
Click to collapse
Could be your Android PlatformTools are out of date?
abdane said:
Initially, I unlocked my bootloader and data was wiped, then I installed android 8.1 (the recommended version from resuruction remix rom forum) and extracted the files into the directory of adb, then I ran "flash-all" and it was running, then at the end it showed a fail error and now my device is not booting up, I can only access fastboot mode
Click to expand...
Click to collapse
If I am reading your steps right...
My suggestion is flash vanilla Oreo.
I wouldnt be surprised of there is some parition structure change that the Modded ROM is screwing up.
get back to vanilla
Mod after being stabel
parakleet said:
If I am reading your steps right...
My suggestion is flash vanilla Oreo.
I wouldnt be surprised of there is some parition structure change that the Modded ROM is screwing up.
get back to vanilla
Mod after being stabel
Click to expand...
Click to collapse
Im sorry, what do you mean by vanilla oreo? You mean the very first oreo ROM?
parakleet said:
If I am reading your steps right...
My suggestion is flash vanilla Oreo.
I wouldnt be surprised of there is some parition structure change that the Modded ROM is screwing up.
get back to vanilla
Mod after being stabel
Click to expand...
Click to collapse
abdane said:
Im sorry, what do you mean by vanilla oreo? You mean the very first oreo ROM?
Click to expand...
Click to collapse
I think the suggestion is that you flash the stock factory 8.1 image found on the Google site (the link to it is in my 9x and 8x links in my sig).
I agree with this.
Fastboot the factory 8.1 image using the flash-all, leave the -w in so you wipe any fragments, and you should have a brand new, fresh start.
Az Biker said:
I think the suggestion is that you flash the stock factory 8.1 image found on the Google site (the link to it is in my 9x and 8x links in my sig).
I agree with this.
Fastboot the factory 8.1 image using the flash-all, leave the -w in so you wipe any fragments, and you should have a brand new, fresh start.
Click to expand...
Click to collapse
I think I confused you guys, sorry, what i did is that I flashed the STOCK version of 8.1 Oreo, I wanted to downgrade from pie. I installed the official one from google and ran the "flash-all" command and failed at vendor_b
michaelbsheldon said:
Could be your Android PlatformTools are out of date?
Click to expand...
Click to collapse
I just uninstalled it, installed the latest version and still not working :/
I am trying to fastboot the files separately: bootloader, boot, radio, system and vendor images. They all pass except for the vendor image, it always fails there (Data write failure unknown error). Any help?
abdane said:
I just uninstalled it, installed the latest version and still not working :/
Click to expand...
Click to collapse
If you are for sure unlocked and critical unlocked, next step is to unzip everything in the Google factory image (about 25 files), then
use this with instructions listed: https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
It's fixed things for me several times when I just could not get results with flash-all.bat.
Alright, wow finally I got it to work. THe issue was either the cable or the port, I was using the originisl type-c to type c cable, tried my old LG G5 typeA to type c and worked fine, wow. Thanks for the help everyone!!! Phone is back and alive
abdane said:
Alright, wow finally I got it to work. THe issue was either the cable or the port, I was using the originisl type-c to type c cable, tried my old LG G5 typeA to type c and worked fine, wow. Thanks for the help everyone!!! Phone is back and alive
Click to expand...
Click to collapse
I thought you already read over my 8x or 9x guides, or I would've mentioned that in the first place
8x Guide:
-have a 2.0 USB in case your 3.0 USB doesn't work properly
-Reboot PC, change between 2.0 and 3.0 cables, and change USB ports if having trouble using fastboot
9x Guide:
*Unlocked bootloader and Critical_unlock completed.
*Latest SDK Tools found here
*USB 2.0 & 3.0 cables available (trust me)
hi dude, I have the same problem with you , have you solved yet?
after flash the factory image android o , it shows device corrupt..
Az Biker said:
I thought you already read over my 8x or 9x guides, or I would've mentioned that in the first place
8x Guide:
-have a 2.0 USB in case your 3.0 USB doesn't work properly
-Reboot PC, change between 2.0 and 3.0 cables, and change USB ports if having trouble using fastboot
9x Guide:
*Unlocked bootloader and Critical_unlock completed.
*Latest SDK Tools found here
*USB 2.0 & 3.0 cables available (trust me)
Click to expand...
Click to collapse
This exact info should be a sticky on every single thread!!
CyberpodS2 said:
This exact info should be a sticky on every single thread!!
Click to expand...
Click to collapse
I just created a "troubleshooting thread" for this situation in the 2 XL guides section
Link in my sig.
Should be much easier to point people to these steps before we spend two pages trying to help out just to find out it was a USB cable, or old SDK tools
Ble_Ale said:
hi dude, I have the same problem with you , have you solved yet?
after flash the factory image android o , it shows device corrupt..
Click to expand...
Click to collapse
I've had this happened a couple of times no Rhyme or Reason the only way out of it is to flash The Flash all with the -w. I believe it has something to do with Googles security.
Edit. I take that back I've switched to the other slot before and restored a backup and gotten out of it if that other slot isn't corrupt
I thought Android Pie has a mandatory "Anti Roll back" feature that prevents going back to Android Oreo?
That is not true then?!
samteeee said:
I thought Android Pie has a mandatory "Anti Roll back" feature that prevents going back to Android Oreo?
That is not true then?!
Click to expand...
Click to collapse
unless you do fastboot flashing unlock and fastboot flashing unlock_critical it is not possible to roll back.
if you do both above you can over-write the critical partitions allowing the roll-back.
the general population would not be doing these, so in essence they do block rolling back to earlier versions, but in a disaster situation it can be done.
uicnren said:
unless you do fastboot flashing unlock and fastboot flashing unlock_critical it is not possible to roll back.
if you do both above you can over-write the critical partitions allowing the roll-back.
the general population would not be doing these, so in essence they do block rolling back to earlier versions, but in a disaster situation it can be done.
Click to expand...
Click to collapse
Got it. Thanks for the explanation.
Guys I need your help and I’m desperate to someone get me to the right dirrection.
I just got a pixel 2 xl, I unlock the bootloader and root with twrp. I try to install a lineage os rom with the gaps and it looks like everything when the well. I erase the cache and free I reboot it went back to the bootloader screen. From that point I have been spending all day trying to get back to factory or at least trying to install any other rom with out any luck. It someone can help me out I will be more than happy to send a Starbucks card or something. I just got the phone,
I forgot to mention that when I try to use the and side load it says something about the e drive, like if there es no drive on my phone
rectangularspace said:
Guys I need your help and I’m desperate to someone get me to the right dirrection.
I just got a pixel 2 xl, I unlock the bootloader and root with twrp. I try to install a lineage os rom with the gaps and it looks like everything when the well. I erase the cache and free I reboot it went back to the bootloader screen. From that point I have been spending all day trying to get back to factory or at least trying to install any other rom with out any luck. It someone can help me out I will be more than happy to send a Starbucks card or something. I just got the phone,
Click to expand...
Click to collapse
Do you know and understand how you use fastboot or the Deuces script to flash factory images to return you to stock OS?
Well not really. But I follow many instrucciones from differents post and nothing
rectangularspace said:
Well not really. But I follow many instrucciones from differents post and nothing
Click to expand...
Click to collapse
Read over this thread. Then let us know if you need help. https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77530335
Also, if you have twrp installed, you can flash the OTA zip that corresponds to your current OS version :good:
I do have twrp installed the problem is that I don’t have the zip on the phone to install the ota file.
Try with deceus Script (Just search for it) and select repair bootloop. It will download the factory Image and flash it on a and b partition then your phone will boot again. But your data will be lost :/
Ok., I will let you guys know thank you
Also, I forgot to mention that it looks like that I don’t have a OS installed ( twrp is telling me that every time i try to get out to the get out of the twrp menu. At this point i haven’t don’t anything mention in this post because I’m resetting my computer nd I’m installing right now the android sdk software.
You don't have to install the full Android SDK software for the job you're trying to do. You can download the latest Fastboot commands and ADB through Google, or even XDA(somewhere).
I've installed adb to my Windows commands, so once in recovery, when I need a file, I just "adb push file.zip /sdcard/".
No worries though. You'll be back up and running. ?
Edit: Also, if you still have data on your phone, you can check using the file explorer on TWRP. If you do, you can adb pull anything you want to keep.
@rectangularspace Link to the standalone platform tools HERE. This is all you need.
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
rectangularspace said:
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
Click to expand...
Click to collapse
Yes, but going down from 9 to 8 will cause/require a data wipe.
rectangularspace said:
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
Click to expand...
Click to collapse
Why did you decide to install Oreo?? There will be no further security or functionality updates for 8.1. The next monthly update to Pie should be the first Monday of next month (October 1st) if you don't get a OTA nag before then.
I have the update available to install on my settings. But what I'm looking for is to start over on rooting my pixel 2 xl. But after last experience I'm a little conservative when it comes to mess with the phone. I'm reading right now the post where it says to do the critical unlock for the phone but I don't know witch bootloader version I have. Can you guys help me out
I have tmz10n version on my bootloader. It means that I need to do the critical unlock? By the way I did already unlock my bootloader and i Haven lock it again. And I think at some point when I was having trouble with my phone to put it back to run I did also the critical unlock process.
rectangularspace said:
I have tmz10n version on my bootloader. It means that I need to do the critical unlock? By the way I did already unlock my bootloader and i Haven lock it again. And I think at some point when I was having trouble with my phone to put it back to run I did also the critical unlock process.
Click to expand...
Click to collapse
You only need to do the unlock process one time, BUT there are two separate unlock commands which include unlock_critical. If in doubt you can use fastboot device-info or getvar to check the current status. Make sure you are using the latest version of the platform tools I linked to above. One word of caution... don't EVER re-lock your bootloader or you WILL run into problems. Even if you are returning the phone to Google for RMA you do not need to re-lock it.
My bad, after unlock my bootloader I haven't look back again. So it is unlock right now. Thank you for advised. For what I read the only way to unlock it it will be by running the command fastboot right? If I upgrade to pie using the upgrade available in my settings right now, it will not lock the bootloader right?
rectangularspace said:
My bad, after unlock my bootloader I haven't look back again. So it is unlock right now. Thank you for advised. For what I read the only way to unlock it it will be by running the command fastboot right? If I upgrade to pie using the upgrade available in my settings right now, it will not lock the bootloader right?
Click to expand...
Click to collapse
I meant the only way to lock the bootloader will be thru a fastboot command.
rectangularspace said:
I meant the only way to lock the bootloader will be thru a fastboot command.
Click to expand...
Click to collapse
Yes, once you have successfully unlocked the phone in fastboot using the two separate commands, you will never have to do it again, AND flashing anything will not re-lock the bootloader. Please read over Nathan's GUIDE HERE to confirm you have done this correctly (and completely). Once this is done you can flash OTA's , full Google images, custom roms, etc. Lastly, if you are properly unlocked you cannot brick your phone. No matter how bad it gets, you will always have a path to restore the phone to it's original state. Don't hesitate to take the OTA being offered on your phone. It will take you to 9.0 without losing data or locking anything. :good:
The last time I rooted a phone was 3 years ago, in general whenever I try to root a phone I feel like the entire process has changed and im completely out of the loop.
All i want to do is make it so i can install f.lux and youtube vanced, how do I do this?
I know that I need to install magisk but apparently I also need to enable the bootloader whatever that means?
Sideload, flashing, caprip, boot-image, fastboot, TWRP: these words mean nothing to me, they serve to confuse and demean me.
Is there any resource for figuring out how to go from a new out-of-the-box moto g30 to one which lets me install youtube vanced? Usually I'd look up a tutorial but the only one I found was in spanish and I don't speak spanish.
Thanks for any help you can give.
First things first.
Android has Night Light built in and Youtube Vanced doesn't need root.
But, if you're still serious about rooting and installing magisk to make use of all of the really useful modules, you'll need:
An Unlocked Bootloader: Motorola's Own Guide
Keep in mind that unlocking the bootloader will wipe your phone and void its warranty, so be absolutely sure you want to do it and back up your files.
Then you'll need to manually patch a boot.img from your stock ROM (can be found here.) and flash it using ADB (Android Debug Bridge) using your PC.
I rooted mine within 3 days of owning it and have been enjoying it with no problems whatsoever ever since.
I used this guide as reference. If you have any questions you can always just message me here or on Telegram (@Kuntitled).
samjoebobtomted said:
The last time I rooted a phone was 3 years ago, in general whenever I try to root a phone I feel like the entire process has changed and im completely out of the loop.
All i want to do is make it so i can install f.lux and youtube vanced, how do I do this?
I know that I need to install magisk but apparently I also need to enable the bootloader whatever that means?
Click to expand...
Click to collapse
Bootloader is small program which runs before Android operating system running. Bootloader is first program to run so It is specific for board and processor. -RootJunky
Click to expand...
Click to collapse
Unlocking the bootloader
You can flash a custom system only if the bootloader allows it. Note, though, that the bootloader is locked by default. You can unlock the bootloader, but doing so deletes user data for privacy reasons. After unlocking, all data on the device is erased, that is, both private app data and shared data accessible over USB (including photos and movies). Before attempting to unlock the bootloader, back up any important files on the device. - https://source.android.com/setup/build/running
Click to expand...
Click to collapse
samjoebobtomted said:
Sideload,
Click to expand...
Click to collapse
Generally sideload means installing an app without the playstore.
samjoebobtomted said:
flashing,
Click to expand...
Click to collapse
Flashing usually refers to installing through fastboot mode or recovery
samjoebobtomted said:
caprip,
Click to expand...
Click to collapse
codename or development name for Moto G30
samjoebobtomted said:
boot-image
Click to expand...
Click to collapse
The boot.img is the fie that creates the boot partition
/bootThis is the boot partition of your Android device, as the name suggests. It includes the android kernel and the ramdisk. The device will not boot without this partition. Wiping this partition from recovery should only be done if absolutely required and once done, the device must NOT be rebooted before installing a new one, which can be done by installing a ROM that includes a /boot partition.
-RootJunky
Click to expand...
Click to collapse
samjoebobtomted said:
fastboot,
Click to expand...
Click to collapse
Fastboot refers to several things
Fastboot is the fastboot protocol to communicate with an Android device.
Fastboot.exe is the part of SDK Platform-Tools used to communicate with an Android device when it's in fastboot mode.
samjoebobtomted said:
TWRP:
Click to expand...
Click to collapse
Twrp is a Custom recovery,
The stock recovery has very limited functions,
a custom recovery has more options
/recoveryThis is specially designed for backup. The recovery partition can be considered as an alternative boot partition, that lets the device boot into a recovery console for performing advanced recovery and maintenance operations on it. -RootJunky
Click to expand...
Click to collapse
samjoebobtomted said:
these words mean nothing to me, they serve to confuse and demean me.
Is there any resource for figuring out how to go from a new out-of-the-box moto g30 to one which lets me install youtube vanced? Usually I'd look up a tutorial but the only one I found was in spanish and I don't speak spanish.
Thanks for any help you can give.
Click to expand...
Click to collapse
I have general Moto rooting instructions here
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Kuntitled said:
First things first.
Android has Night Light built in and Youtube Vanced doesn't need root.
Click to expand...
Click to collapse
Wait really I didn't even realize I didn't need a root for that lol.
Kuntitled said:
But, if you're still serious about rooting and installing magisk to make use of all of the really useful modules, you'll need:
An Unlocked Bootloader: Motorola's Own Guide
Keep in mind that unlocking the bootloader will wipe your phone and void its warranty, so be absolutely sure you want to do it and back up your files.
Then you'll need to manually patch a boot.img from your stock ROM (can be found here.) and flash it using ADB (Android Debug Bridge) using your PC.
I rooted mine within 3 days of owning it and have been enjoying it with no problems whatsoever ever since.
I used this guide as reference. If you have any questions you can always just message me here or on Telegram (@Kuntitled).
Click to expand...
Click to collapse
Hi thanks this really helped me get the grip of things haha.
I managed to unlock the bootloader but I'm a bit confused on what stock ROM you were referring to, the link you sent had a bunch of possibilities, I assume I need a reteu one since that's the name of my phone's software channel but there's a wide variety of them and the guide you sent seems to have their own ROM as well.
Either way thanks for all the help!
samjoebobtomted said:
Wait really I didn't even realize I didn't need a root for that lol.
Hi thanks this really helped me get the grip of things haha.
I managed to unlock the bootloader but I'm a bit confused on what stock ROM you were referring to, the link you sent had a bunch of possibilities, I assume I need a reteu one since that's the name of my phone's software channel but there's a wide variety of them and the guide you sent seems to have their own ROM as well.
Either way thanks for all the help!
Click to expand...
Click to collapse
You should check the Build Number under "About Phone" in settings, and match it what you find on that link i sent.
I am seeing a lot of folks who are still (year later) unable to enjoy custom ROM with T-Mobile devices, so I wanted to quickly post this easy method for enjoying your device with FULL DATA. If you are using a T-Mobile branded OnePlus 9 Pro and have accepted all normal OTA updates as of 9/8/22, you should be on C.19 firmware.
Assuming you have already unlocked your bootloader, you can safely upgrade to EU C.62 firmware found at:
OP9PRO_Android12_C62_EU_Firmware
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
I completed this process while already on Nameless but it should work for others too. No more dodgy modules, hacked MSMDownloadTools or sorta working phones. Note, firmware and local updates are NOT the same. You are not cross-flashing to an entirely new software but ONLY required firmware modules for latest custom ROMs. Hope this helps!
P.S. if you receive any error while sideloading your new firmware, DO NOT unplug or reboot your phone. Repeat the process until it's completed successfully.
So you are saying no need to msm to EU first? I am on C.19, is this supposed to be flashed in fastboot? No modem issues??
nextbigleap said:
So you are saying no need to msm to EU first? I am on C.19, is this supposed to be flashed in fastboot? No modem issues??
Click to expand...
Click to collapse
That's exactly what I am saying, fastboot flash the firmware only and say goodbye to data issues.
My system update is showing c.17 as the latest update. I can't seem to get c.19. Would switching to eu firmware delete user data too?
MudaTrucka said:
My system update is showing c.17 as the latest update. I can't seem to get c.19. Would switching to eu firmware delete user data too?
Click to expand...
Click to collapse
No user data removed.
Appreciate this post. Do you plan on keeping this updated as EU gets updates?
SaintZ93 said:
Appreciate this post. Do you plan on keeping this updated as EU gets updates?
Click to expand...
Click to collapse
I will do my best!
Why does this work where the eu msm converter has problems with the modem? After you flash this firmware can you take future ota updates without modem issues as well?
The latest firmware from non-branded OnePlus 9 Pro is now available!
OP9PRO_Android12_C63_NA_Firmware
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
This finally brings those of us on T-Mobile, especially closer to the bleeding edge.
Is this file modified in any way? Why didn't the people in the conversion thread do this before? I just don't get it, help me understand how we are avoiding all those problems. Can you also share the fastboot commands you use to flash this firmware please? Thank you.
rageoner said:
Is this file modified in any way? Why didn't the people in the conversion thread do this before? I just don't get it, help me understand how we are avoiding all those problems. Can you also share the fastboot commands you use to flash this firmware please? Thank you.
Click to expand...
Click to collapse
Of course, it's modified because OnePlus doesn't create firmware packages for our community. However, the files within the package are original dumps.
You can easily sideload this fix through your custom recovery using adb sideload OP9PRO_Android12_C63_NA_Firmware.zip for example.
Ok, one last question, are we able to take ota updates after doing the sideload? I know this is the latest firmware so there won't be any but in the future are we able to take ota?
Question:
1-what room is best for my LE2127 for daily use
2-Hasselblad camera exist a app
3-what TWRP are we using now
thanks in advance
Could someone please post steps to sideload Le2127 to EU / Global C.62EU / C.63NA No data loss ?
can I sideload this from t-mobile c.17? Also what recovery can I use? TWRP is for android 11
I use this for adb side loading..
[TOOL] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)
Hello everyone, today I present my new creation: we are talking about a tool that allows you to do many things , from the bootloader to flash the factory image , comfortably. Now you're probably asking: but there are already other tools available...
forum.xda-developers.com
luckylui said:
I use this for adb side loading..
[TOOL] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)
Hello everyone, today I present my new creation: we are talking about a tool that allows you to do many things , from the bootloader to flash the factory image , comfortably. Now you're probably asking: but there are already other tools available...
forum.xda-developers.com
Click to expand...
Click to collapse
Should I just select oneplus 8 pro as the device? The 9 pro technically isn't supported. I also can't get my computer to recognize my phone in recovery so sideloading is not working, all drivers installed and my pc recognizes my phone in any other state.
MudaTrucka said:
Should I just select oneplus 8 pro as the device? The 9 pro technically isn't supported. I also can't get my computer to recognize my phone in recovery so sideloading is not working, all drivers installed and my pc recognizes my phone in any other state.
Click to expand...
Click to collapse
Do the other option and go from there.
The Tool All In One is a great tool with many uses. You can choose the OP8P and it will work for OP9P. My question is will this really work side loading C.62 or C.63 on Le2127 and not lose data. I still have yet to read a clear guide on doing this. Also there's a lot of us that still use the TMO 9 Pro but I don't see anyone responding to this thread sharing that it really works. It would be nice but I'm not even gonna try until I know for sure that it really does work !
Bulauski2005 said:
The Tool All In One is a great tool with many uses. You can choose the OP8P and it will work for OP9P. My question is will this really work side loading C.62 or C.63 on Le2127 and not lose data. I still have yet to read a clear guide on doing this. Also there's a lot of us that still use the TMO 9 Pro but I don't see anyone responding to this thread sharing that it really works. It would be nice but I'm not even gonna try until I know for sure that it really does work !
Click to expand...
Click to collapse
You can't help folks that don't want to help themselves.