Related
What happened to this software? Installed it on my Chinese x820 Le Max 2 and it is working great. The FP scanner seems to be faster also! I am curious if anyone is planning to use this as a base for a custom rom, but when I came in the forum this evening, I couldn't find it
I think it was removed because the source was unknown. I think there were problems with encrypted partitions....
Works very well for me. I wiped DATA in TWRP after I installed update. Now all my firmware was updated by doing the update. After the update my phone was encrypted, I simply went into TWRP and wiped DATA after I installed his TWRP backup minus all the boot info. During boot is when that process seems take place, so only system was restored. I then made sure my DATA partition, that I could now see, was mounted and flashed SuperSu. I then added all my root apps as normal. The FP scanner is still somewhat slow, but works almost everytime. I am sorry that this was removed as it is actually better and faster than all previous Roms minus all the Chinese bloat, although a lot of it was changed to reflect US sources, such as all the videos. All in all a very good ROM.
jim262 said:
Works very well for me. I wiped DATA in TWRP after I installed update. Now all my firmware was updated by doing the update. After the update my phone was encrypted, I simply went into TWRP and wiped DATA after I installed his TWRP backup minus all the boot info. During boot is when that process seems take place, so only system was restored. I then made sure my DATA partition, that I could now see, was mounted and flashed SuperSu. I then added all my root apps as normal. The FP scanner is still somewhat slow, but works almost everytime. I am sorry that this was removed as it is actually better and faster than all previous Roms minus all the Chinese bloat, although a lot of it was changed to reflect US sources, such as all the videos. All in all a very good ROM.
Click to expand...
Click to collapse
I also forgot to mention my WiFi, Bluetooth connections work better now, as well as, my TMO WiFi calling. The firmware upgrades were needed and the device is faster and smoother now.
Jim, can you please highlight the steps need to be done to back up and not have encrypted phone? I am on the 15S pure evolution by teamspain. I don't know if my stuff is encrypted or not but please provide the steps to update to the 16S rom without any hiccups. Thanks!
xterminater07 said:
Jim, can you please highlight the steps need to be done to back up and not have encrypted phone? I am on the 15S pure evolution by teamspain. I don't know if my stuff is encrypted or not but please provide the steps to update to the 16S rom without any hiccups. Thanks!
Click to expand...
Click to collapse
Here are the steps I followed. Hopefully this will work for others. My phone is from China, but I do live in US. Supposedly this is supposed to be a US centric rom. Anyhow...
I first made sure I was on stock (15s) with stock recovery or simply flash via adb, a stock recovery image.
Next, I downloaded the ota - firmware-update <5.8_016s_sta.zip> and copied it to the root of my internal storage.
Using the stock file manager I renamed this file to update.zip. Still in the stock file manager, I clicked on it. This starts the upgrade process. After this is complete, all your firmware and most importantly, for me at least, the FP sensor.
However, if stock is fine with you, leave it like this, but your device will be encrypted.
So to remove the encryption which is on the data partition, I rebooted to fastboot mode and used adb.
At the adb prompt, I typed <fastboot boot twrp.img> This boots twrp without loading into your recovery partition.
I then wiped my data partition and re stored using a modified version of the TRWP backup file that I had also downloaded from the same source. I had unzipped this on my C: drive of my PC and removed the boot files <boot.emmc.win and the md5 file>
I then re zipped this and copied to my internal storage and flashed it using the restore option. This restored only system data. The device was now unencrypted and my data drive was visible in Twrp.
I then mounted the DATA partition from inside TWRP and flashed SuperSu.
After that I rebooted normally, I then proceeded to install all my rooted programs as normal. This process should also work with the Indian rom.
My x820 is also from china, how do I know if it's encrypted or not? Right now I have the teamspain rom installed, do I need to really go back to stock 15s or can you upload a stock recovery for us. Also how to wipe data partition, and restore with the modified twrp back up? The guy who uploaded the 16s stuff deleted the thread so we have nothing to go with. Can you reupload all necessary files, and how to remount the data partition again from twrp?
I don't have the files. That is why I was looking for them in the first place.
xterminater07 said:
My x820 is also from china, how do I know if it's encrypted or not? Right now I have the teamspain rom installed, do I need to really go back to stock 15s or can you upload a stock recovery for us. Also how to wipe data partition, and restore with the modified twrp back up? The guy who uploaded the 16s stuff deleted the thread so we have nothing to go with. Can you reupload all necessary files, and how to remount the data partition again from twrp?
Click to expand...
Click to collapse
The two versions that have been encrypted, thus far, the Indian version and the US version. All the other Roms do not have encryption. If you can boot into TWRP and see your data partition and mount it, you are not encrypted. This form of encryption merely hides or makes your data partition invisible to third party programs, like TWRP.
jim262 said:
I don't have the files. That is why I was looking for them in the first place.
Click to expand...
Click to collapse
It is leaked firmware for US models with August 1 2016 Android security update and we are still in July. LMAO.
X829_5.8.16s_EN_US_update (Official Firmware with data partition encryption)
X829_5.8.16s_EN_US_rooted (Rooted firmware with data partition decrypted) -> I don't know who rooted it so caution is advised. I am using rooted ROM without problem though.
Apparently, it works on any X820 (China) and X821 (India) model. But after flashing, your phone model will change to X829. I also don't know who leaked it and do not take any responsibility for the firmware causing irreversible damage.
I am uploading it to mega.co.nz right now. Uploading stock firmware will take 2 hrs and rooted firmware will take another 2 hrs. I will post the links when done.
Hi. Which languages is available in x829 version ? Do you know also which bands are activated ?
Sent from my Le X821 using XDA-Developers mobile app
sanke1 said:
It is leaked firmware for US models with August 1 2016 Android security update and we are still in July. LMAO.
X829_5.8.16s_EN_US_update (Official Firmware with data partition encryption)
X829_5.8.16s_EN_US_rooted (Rooted firmware with data partition decrypted) -> I don't know who rooted it so caution is advised. I am using rooted ROM without problem though.
Apparently, it works on any X820 (China) and X821 (India) model. But after flashing, your phone model will change to X829. I also don't know who leaked it and do not take any responsibility for the firmware causing irreversible damage.
I am uploading it to mega.co.nz right now. Uploading stock firmware will take 2 hrs and rooted firmware will take another 2 hrs. I will post the links when done.
Click to expand...
Click to collapse
May not be the best idea too upload leaked firmware seeing as it got taken down the first time.
sanke1 said:
It is leaked firmware for US models with August 1 2016 Android security update and we are still in July. LMAO.
X829_5.8.16s_EN_US_update (Official Firmware with data partition encryption)
X829_5.8.16s_EN_US_rooted (Rooted firmware with data partition decrypted) -> I don't know who rooted it so caution is advised. I am using rooted ROM without problem though.
Apparently, it works on any X820 (China) and X821 (India) model. But after flashing, your phone model will change to X829. I also don't know who leaked it and do not take any responsibility for the firmware causing irreversible damage.
I am uploading it to mega.co.nz right now. Uploading stock firmware will take 2 hrs and rooted firmware will take another 2 hrs. I will post the links when done.
Click to expand...
Click to collapse
I figured that this was the case, since all the software, such vid files in Live, were US related where they are all Chinese obviously in the Chinese version. I also know they have been opening offices throughout the US, but haven't released anything yet in this country. Even though there might be a slightly different model released here in the US, hence the model number being x829, the software is working flawlessly with my Chinese x820.
deadman96385 said:
May not be the best idea too upload leaked firmware seeing as it got taken down the first time.
Click to expand...
Click to collapse
If it is official firmware, then I don't see a point why it was taken down. There is no clarity. Did OP himself take it down? The links have disappeared from his site as well.
sanke1 said:
If it is official firmware, then I don't see a point why it was taken down. There is no clarity. Did OP himself take it down? The links have disappeared from his site as well.
Click to expand...
Click to collapse
The OP did take it down because he did not know he was not supposed to release it because it was pre-release firmware.
Well, I have the links ready. Nevermind.
sanke1 said:
If it is official firmware, then I don't see a point why it was taken down. There is no clarity. Did OP himself take it down? The links have disappeared from his site as well.
Click to expand...
Click to collapse
Have you ever heard of a Cease and Desist order? People that leak software can get in trouble with the company that is developing it. Have you ever been a beta tester? I am currently testing for Microsoft and Honor and had to agree to not release any of their software until they are ready for it to be released. If you are a beta tester, you will get bounced from the program and if you're an employee, fired. Plus depending on the severity, you could also end up getting sued.
I am neither a beta tester nor an employee. But I do respect that the dude didn't want it posted.
sanke1 said:
It is leaked firmware for US models with August 1 2016 Android security update and we are still in July. LMAO.
X829_5.8.16s_EN_US_update (Official Firmware with data partition encryption)
X829_5.8.16s_EN_US_rooted (Rooted firmware with data partition decrypted) -> I don't know who rooted it so caution is advised. I am using rooted ROM without problem though.
Apparently, it works on any X820 (China) and X821 (India) model. But after flashing, your phone model will change to X829. I also don't know who leaked it and do not take any responsibility for the firmware causing irreversible damage.
I am uploading it to mega.co.nz right now. Uploading stock firmware will take 2 hrs and rooted firmware will take another 2 hrs. I will post the links when done.
Click to expand...
Click to collapse
Thank you for your work.
Hi all, I'm trying to install this rom via twrp and i'm getting an error failed to install because it can't mount /cust/ partition. I try to mount it in twrp as well but it is greyed out. Can anyone tell me how to fix this?
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1......
Click to expand...
Click to collapse
This specific device and Chipset is fairly new and there's very little on the forum that's specific to your device.
With that stated...
You have a Mediatek MT6739 (64 Bit) device that can be very helpful in that aspect.
Though I had located a few threads that won't be very helpful for you but, the following thread is about the best that your possibly going to find for your device at this point in time.
https://forum.xda-developers.com/showthread.php?t=2701283
It does take some time for developments to pop up on the forum for newer Mediatek Chipsets but, where there's a developer (with the same Chipset device), there's always a way depending on the level of difficulty.
I wish you the best of luck with your search!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
I'm also looking for that. But if I can get TWRP on it I'd probably try SU.
How did you get to install the TWRP? I found a few posts but was apprehensive about whether I can use SPFT to flash original stock ROM if things go wrong. I suppose that would be the easiest way.
For what I paid for the phone, it's a decent enough device.
Using SD card as internal memory always result in the total capacity being reported wrongly..256GB becomes 512GB with 50% occupied, 200GB becomes 256GB with 64GB occupied. Still waiting for their tech support to reply but unlikely they would.
Cheers!
I have rooted it several times and flashed the stock image several times too without a problem. Haven't used SU though I used Magisk.
.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
I do not have your issue with storage but my wireless charging mat today stopped charging but still lights up. Phone will still charge via cable. Trying to get a replacement mat.
I installed using SP flash tools on windows and Linux just to see the difference.
If you do a Google for Install TWRP ulefone armor x then you will get some information and relevant files.
Unlocking the bootloader via ADB is straightforward on Windows and Linux too. And then relocking it.
Regards
Charlie
Ibuprophen said:
This specific device and Chipset is fairly new and there's very little on the forum that's specific to your device.
With that stated...
You have a Mediatek MT6739 (64 Bit) device that can be very helpful in that aspect.
Though I had located a few threads that won't be very helpful for you but, the following thread is about the best that your possibly going to find for your device at this point in time.
https://forum.xda-developers.com/showthread.php?t=2701283
It does take some time for developments to pop up on the forum for newer Mediatek Chipsets but, where there's a developer (with the same Chipset device), there's always a way depending on the level of difficulty.
I wish you the best of luck with your search!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Thanks for the input I will have a read.
Charlie-Boy said:
I have rooted it several times and flashed the stock image several times too without a problem. Haven't used SU though I used Magisk.
.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
I do not have your issue with storage but my wireless charging mat today stopped charging but still lights up. Phone will still charge via cable. Trying to get a replacement mat.
I installed using SP flash tools on windows and Linux just to see the difference.
If you do a Google for Install TWRP ulefone armor x then you will get some information and relevant files.
Unlocking the bootloader via ADB is straightforward on Windows and Linux too. And then relocking it.
Regards
Charlie
Click to expand...
Click to collapse
Thanks for the info.
Cheers!
chooks06 said:
Thanks for the info.
Cheers!
Click to expand...
Click to collapse
No problem.
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
Where did you get the TWRP for Ulefone Armor X. I've been trying to search it all over and haven't found anything. If possible can you please share a link? TIA
abhijeet715 said:
Where did you get the TWRP for Ulefone Armor X. I've been trying to search it all over and haven't found anything. If possible can you please share a link? TIA
Click to expand...
Click to collapse
Code:
https://www.needrom.com/download/twrp-armox-x/
There are other places listed on Google.
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
chooks06 said:
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
Click to expand...
Click to collapse
im also facing the same issue... kindly someone help.. ive explained my issue below:
Can someone confirm? My device is encrypted by default, so whenever i install TWRP it says to decrypt device. I tried the pattern, changed it to password, and pin still my device doesnt decrypt in twrp. I feel its a twrp bug, because when i set the device to ask pattern during boot, the same pattern/pin/password is accepted, but not in twrp.
I want to know 3 things:
1. Are your devices encrypted by default (i dont remember encrypting my device, I dont know how it is encrypted)
2. Are you facing this same issue of entering password when you reboot into recovery?
3. What is the purpose of the boot.img in the twrp zip? am i required to flash it before flashing the recovery, or does it remove encryption?
Charlie-Boy said:
I am looking for a custom rom, minus the Google stuff, that will work on my Ulefone Armor X Oreo 8.1. I have a working TWRP recovery and have rooted it via Magisk but went back to stock after a few nagging problems.
The phone spec isn't wonderful so need something lighter but still having plenty of functionality.
Cheers
Click to expand...
Click to collapse
Charlie, could share how you got the TWRP working?
Have been fiddling around until battery showed -1%.. Had to go back to stock.
Thanks mate!
Choo ks
In the folder containing the TWRP recovery there are 3 files, boot.img, scatter, and recovery. You only flash recovery, you have flashed the boot image, ensure the checkbox is unticked after loading from scatter in SP tools. That is what I think you have done to get that result.
Follow the guide here. I did it a few times before success as I followed a guide from another site.
https://www.stupdroid.com/2018/07/Ulefone-Armor-X-root-twrp-.html
Click to expand...
Click to collapse
I think I installed magisk using this method, clearing dalvik and cache.
https://www.stupdroid.com/2018/02/magisk-16.0-download.html
Click to expand...
Click to collapse
Charlie-Boy said:
In the folder containing the TWRP recovery there are 3 files, boot.img, scatter, and recovery. You only flash recovery, you have flashed the boot image, ensure the checkbox is unticked after loading from scatter in SP tools. That is what I think you have done to get that result.
Click to expand...
Click to collapse
That's what I did, using the downloaded scatter file. Was experimenting.
---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------
Charlie-Boy said:
Follow the guide here. I did it a few times before success as I followed a guide from another site.
I think I installed magisk using this method, clearing dalvik and cache.
Click to expand...
Click to collapse
Used the same guide. But TWRP came up with the decrypt data issue.
Did you have that issue?
chooks06 said:
Anyone had this in recovery mode?
Had also tried flashing the TWRP but it just didn't stick and was asking for a password on first launch.
Edit.. all links I tried point to the same location to download. Same files.
Click to expand...
Click to collapse
You ignore the password and change the language to English from Russian. Just don't enter a password at all. The recovery won't stick as Android replaces it when you reboot. After you've completed other steps maybe OEM unlocking then it stays, or so I read somewhere.
chooks06 said:
That's what I did, using the downloaded scatter file. Was experimenting.
---------- Post added at 06:49 PM ---------- Previous post was at 06:44 PM ----------
Used the same guide. But TWRP came up with the decrypt data issue.
Did you have that issue?
Click to expand...
Click to collapse
All of them are encrypted by default now. The password in TWRP should be ignored and just change the language and select storage etc.
abhijeet715 said:
im also facing the same issue... kindly someone help.. ive explained my issue below:
Can someone confirm? My device is encrypted by default, so whenever i install TWRP it says to decrypt device. I tried the pattern, changed it to password, and pin still my device doesnt decrypt in twrp. I feel its a twrp bug, because when i set the device to ask pattern during boot, the same pattern/pin/password is accepted, but not in twrp.
I want to know 3 things:
1. Are your devices encrypted by default (i dont remember encrypting my device, I dont know how it is encrypted)
2. Are you facing this same issue of entering password when you reboot into recovery?
3. What is the purpose of the boot.img in the twrp zip? am i required to flash it before flashing the recovery, or does it remove encryption?
Click to expand...
Click to collapse
Yes all are encrypted.
Yes I get the same request for password which I ignored and selected language and carried on.
I do not know why boot.img is included it just gets in the way.
After installing TWRP unlocking OEM bootloader and all the rest including rooting it I decided it would be better to wait for a new ROM. All we need is a working TWRP and an unlocked bootloader to flash a new ROM and we have that. It doesn't work very smoothly and I felt it could be better which is why I went back to stock.
When I posted this request I didn't imagine others would try installing Magisk etc, waste of time really as you won't stay with it either. Best wait for a ROM I think.
Charlie-Boy said:
Yes all are encrypted.
Yes I get the same request for password which I ignored and selected language and carried on.
I do not know why boot.img is included it just gets in the way.
After installing TWRP unlocking OEM bootloader and all the rest including rooting it I decided it would be better to wait for a new ROM. All we need is a working TWRP and an unlocked bootloader to flash a new ROM and we have that. It doesn't work very smoothly and I felt it could be better which is why I went back to stock.
When I posted this request I didn't imagine others would try installing Magisk etc, waste of time really as you won't stay with it either. Best wait for a ROM I think.
Click to expand...
Click to collapse
Im also unlocked and flashed twrp. I ignored the encryption message and proceeded, hit the storage sizes show 0, and neither can i access the storage to flash anything nor can i take backups. can you go to settings>security in your device, and tell me if your encryption says enabled? Tia
abhijeet715 said:
Im also unlocked and flashed twrp. I ignored the encryption message and proceeded, hit the storage sizes show 0, and neither can i access the storage to flash anything nor can i take backups. can you go to settings>security in your device, and tell me if your encryption says enabled? Tia
Click to expand...
Click to collapse
Mine is the same encryption is enabled. I select external SD storage and I am shown the contents using the same procedure as yourself, I cannot tell you why this is so. I am using the same technique, same phone, same settings, same TWRP, maybe we have different SD card?
That is all I can think of by way of an explanation. It works perfectly for me. I also made a backup which I can select and restore without a problem.
A little ways ago, I bought an unlocked LS998, which was converted to US998 via the Frankenstein method. I thought to try the installation of a custom ROM (A.I.S., if it helps), but after failing to get that working, I reverted to a TWRP backup I made prior to the install. Now however, the phone kicks me a warning that "The Phone is Permanently Locked and Cannot Be Unlocked", which I can't for the life of me figure out. Is there a way to restore the old functionality?
Alsedarna said:
A little ways ago, I bought an unlocked LS998, which was converted to US998 via the Frankenstein method. I thought to try the installation of a custom ROM (A.I.S., if it helps), but after failing to get that working, I reverted to a TWRP backup I made prior to the install. Now however, the phone kicks me a warning that "The Phone is Permanently Locked and Cannot Be Unlocked", which I can't for the life of me figure out. Is there a way to restore the old functionality?
Click to expand...
Click to collapse
Maybe this is what you were talking about... I'm not sure.
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
ChazzMatt said:
Maybe this is what you were talking about... I'm not sure.
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
Click to expand...
Click to collapse
Thanks for the tip--I did have to use that initially to get back into my phone, but the lock I'm talking about is on using my SIM card (confirmed good by my carrier, and which works perfectly if put into another unlocked device).
Well--bit the bullet, deleted EVERYTHING and flashed the latest firmware. Problem seems to be resolved!
Alsedarna said:
Well--bit the bullet, deleted EVERYTHING and flashed the latest firmware. Problem seems to be resolved!
Click to expand...
Click to collapse
Can you specified what did you do?
I'M getting in the sam situation here... no service
Mrxyzl said:
Can you specified what did you do?
I'M getting in the sam situation here... no service
Click to expand...
Click to collapse
Do forgive me if my memory is a tad hazy, as I've since switched phones, but from what I recall, I wiped out every trace of everything from TWRP, flashed a stock, factory image, and in one fell swoop the device was working good as new once more.
TESTED IN INDIAN AND BRAZILIAN DEVICES
https://motoota.lolinet.com/index.p...&carrier=retbr&sn=SERIAL_NUMBER_NOT_AVAILABLE
FOR MEXICAN USERS
https://motoota.lolinet.com/index.p...&carrier=amxmx&sn=SERIAL_NUMBER_NOT_AVAILABLE
Pre-requisites:
1. Battery 50+%
2. Locked bootloader
How to install ?
Step 1: Place the downloaded zip in internal storage and rename it.
( Indian / Brazilian: Blur_Version.29.11.30.albus.retail.en.US.zip or Mexican: Blur_Version.29.11.31.albus.retail.en.US.zip)
Step 2: Go to settings -> apps -> show system apps
and then give storage permission for Motorola update services.
Step 3: Reboot the phone and then check for update in settings app.
#Youtube video tutorial by Rocha Tech
https://youtu.be/xJO31p4GLmU
(Just watch the video without sound if you understand the language )
#FAQ
1. What about my data after i install this update?
Ans: Your data is safe after installing the update. For more safety, you can backup your data as an additional safety measure.
2. Will this work on my bootloader unlocked device ?
Ans: No, it will not work with bootloader unlocked. You need to flash the Oreo stock rom to be able to flash this on your device.
3. Why my country name is not mentioned for updates ?
Ans: You may try Indian update zip file and if it doesn't work then try the Mexican one.
Credits:
Helton Vezzoni @erfanoabdi
Any info about the build, software channel, etc?
XBrav said:
Any info about the build, software channel, etc?
Click to expand...
Click to collapse
Load it up and tell us.
kewlzter said:
Load it up and tell us.
Click to expand...
Click to collapse
Definitely trying. Stock recovery was not spawning ADB, so I'm trying to boot TWRP live. It's been a while, and it's hanging on the TWRP page.
XBrav said:
Definitely trying. Stock recovery was not spawning ADB, so I'm trying to boot TWRP live. It's been a while, and it's hanging on the TWRP page.
Click to expand...
Click to collapse
I tried TWRP (installed) didn't work.
I'll try returning to stock and sideloading tomorrow after work.
Ok, trying the stock way:
1) Reboot into bootloader (Power + Vol Down)
2) Select boot into Recovery.
3) At "No Command" Screen, hold down Power and press Vol Up.
4) Load from SD card, or live dangerously like me and sideload via ADB (Minimal ADB and Fastboot seems to work for me)
Will update once the push is complete.
I just downloaded.
Gave "Motorola Update Services" storage permission.
Copied the file from the computer to the phone's internal storage.
Checked for updates
And voilá, there was the update.
I'm already running Pie.
Up and running here. Didn't like my original image, but after flushing data, it booted fine. It did say I no longer qualify for updates which seems to be a new thing with Motorola and Pie, but common across other devices too. Either way, it all seems to be working.
victorhbm15 said:
I just downloaded.
Gave "Motorola Update Services" storage permission.
Copied the file from the computer to the phone's internal storage.
Checked for updates
And voilá, there was the update.
I'm already running Pie.
Click to expand...
Click to collapse
Did it work really..??
Do we need unlocked bootloader or will it work for all..
Currently running Stock Oreo Firmware locked Bootloader.
Trying to sideload via ADB, will post results after completion of process.
Hello!
Is there an .xml file for this update?
OR
Any proper guide for sideload method?
Thanks
OK! I found a guide for Oreo OTA sideload install.
https://forum.xda-developers.com/z2-play/how-to/official-oreo-z2-play-t3784660
I guess for Pie it is the same.
Tried.
Didn't work.
Can anybody guess what I did wrong?
OldUncle said:
Tried.
Didn't work.
Can anybody guess what I did wrong?
Click to expand...
Click to collapse
Did you follow the steps I posted earlier? What does the phone show for errors?
For those of you who were curious:
1) Software channel remained the same.
2) Dual sim in XT1710-09 seems to be working fine so far (haven't tested a second sim, but the sim statuses are showing for both card slots).
3) No issues with mods so far (Tried the battery pack and gamepad. Hasselblad, projector and speaker are not with me).
4) Build number is PPS29.133-30, Patch Level September 1, 2019.
My phone is in Canada, and the modem patch included works fine as far as I've seen. I haven't fully tested the bluetooth stability yet to see if it's working better than before. Android Auto is working great though.
My smartphone Model name is XT-1710-10, Dual SIM.
I was successfully able to sideload the Update, with the command
"adb sideload Blur_Version.29.11.30.albus.retail.en.US.zip".
It took around 15 to 18 mins for the sideload process to complete, later the phone restarted and showed the usual Moto loading screen for another 12mins or so, for a moment i thought it was stuck, but no, it successfully completed the update process.
Everything is functioning as usual, i noticed that the placement of signal bar, wifi icons, and battery icons on the top right corner of the screen seem to be not proper.
Same is the case with the arrangement of signal and wifi icons on top right portion inside notification drop down menu, seems to be too close to the screen edge.
Additional features I saw after the update are, 3 finger screenshot, Screenshot editor, Media controls provision inside 'Moto Actions'; Attentive display inside 'Moto display'.
Also the addition of "Digital Wellbeing" inside settings Menu.
---------- Post added at 01:33 PM ---------- Previous post was at 01:17 PM ----------
OldUncle said:
Hello!
Is there an .xml file for this update?
OR
Any proper guide for sideload method?
Thanks
OK! I found a guide for Oreo OTA sideload install.
https://forum.xda-developers.com/z2-play/how-to/official-oreo-z2-play-t3784660
I guess for Pie it is the same.
Tried.
Didn't work.
Can anybody guess what I did wrong?
Click to expand...
Click to collapse
It took around 3hrs for me to solve the problem, I am still not clear, what was I doing wrong.
What worked for me somehow was... I properly uninstalled the old ADB installations first vis control panel and then downloaded the latest version of adb i.e adb-setup-1.4.6.exe, and repeated the normal procedure of adb sideload, this time it worked.
I couldn't find an option to enable Android Pie navigation gestures, even in System>Gestures, there is no option.
Do existing TWRP and Magisk root work?
Thanks to everyone who replied with advices :good:
It is my first try to Sidload OTA.
I found out that, I needed the latest OPS27.76-12-25-22/23 stock firmware and I was using OPS27.76-12-25-13.
I fastbooted to the latest but, it didn't work again and I think the reason is that my device is XT1710-11 (Chinese), though I have fastbooted it to RETEU version (Modems preserved) and works fine.
If my guess is correct, that means I need to wait for the fastboot version for Pie
snuk182 said:
Do existing TWRP and Magisk root work?
Click to expand...
Click to collapse
its working great
I get error while sideloading.. i need OPS27.76-12-25-22/23 firmware and I am using OPS27.76-12-42-13/16. On bell canada.
Any advise?
saurav112214 said:
I get error while sideloading.. i need OPS27.76-12-25-22/23 firmware and I am using OPS27.76-12-42-13/16. On bell canada.
Any advise?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/albus/official/
Get the firmware you need from that link and then fastboot flash it to your device.
But make sure if this OTA Pie is for your device.
XBrav said:
Did you follow the steps I posted earlier? What does the phone show for errors?
For those of you who were curious:
1) Software channel remained the same.
2) Dual sim in XT1710-09 seems to be working fine so far (haven't tested a second sim, but the sim statuses are showing for both card slots).
3) No issues with mods so far (Tried the battery pack and gamepad. Hasselblad, projector and speaker are not with me).
4) Build number is PPS29.133-30, Patch Level September 1, 2019.
My phone is in Canada, and the modem patch included works fine as far as I've seen. I haven't fully tested the bluetooth stability yet to see if it's working better than before. Android Auto is working great though.
Click to expand...
Click to collapse
I too have an XT1710-09 (Europe, RETEU software channel). Any idea if this firmware will work for me? Thanks!
LineageOS 17.1 - Official
There is now an official LineageOS 17.1 build available for Ocean! This was not created by me. Most credit seems to be due to SyberHexen. I'm simply posting here because nobody else has done so.
Main Page
Installation Instructions
Greek2me said:
...LineageOS 17.1 - Official...
Click to expand...
Click to collapse
A tear of joy comes to my eye. Thanks for the heads up.
I've been using it daily and so far it's great. No bugs to report yet.
Greek2me said:
I've been using it daily and so far it's great. No bugs to report yet.
Click to expand...
Click to collapse
Thanks for that reassurance.
I'll be a few days behind you. My G7 Power is on a truck. I had been shopping for new device and wanted Moto G7 Power but did not see it in LOS. Then I saw your post. Within minutes I ordered the one I had been eyeing.
As to this thread, typically an LOS official ROM thread will have certain standard language and statements in the original posts. I have no complaint, I'm obviously delighted that you shared the information and you provide links to the official instructions, but be prepared to manage the inclusion of additional information in this thread or hand the thread off to a maintainer to make it the official official thread, or we follow to a new official thread LOS Moto G7 of power.
In any event... Thanks again!
Getting the following error when trying to flash <lineage-17.1-20200912-nightly-ocean-signed.zip>
Error applying update: 18 (ErrorCode::
kDownloadPayloadPubKeyVerificationError)
IronTechmonkey said:
Thanks for that reassurance.
I'll be a few days behind you. My G7 Power is on a truck. I had been shopping for new device and wanted Moto G7 Power but did not see it in LOS. Then I saw your post. Within minutes I ordered the one I had been eyeing.
As to this thread, typically an LOS official ROM thread will have certain standard language and statements in the original posts. I have no complaint, I'm obviously delighted that you shared the information and you provide links to the official instructions, but be prepared to manage the inclusion of additional information in this thread or hand the thread off to a maintainer to make it the official official thread, or we follow to a new official thread LOS Moto G7 of power.
In any event... Thanks again!
Click to expand...
Click to collapse
I'm glad I could reach you on time! I'll keep that in mind about the thread - thanks for the heads-up.
toddk63 said:
Getting the following error when trying to flash <lineage-17.1-20200912-nightly-ocean-signed.zip>
Error applying update: 18 (ErrorCode::
kDownloadPayloadPubKeyVerificationError)
Click to expand...
Click to collapse
I would recommend that you try the installation again, taking care to follow the pre-installation instructions here. Additionally, I recommend that you wipe everything (system, data, internal storage, and cache) before attempting to install LOS.
Install went fairly smooth last night.
Have had a few times (usually when playing a video via the browser) that the "shutdown" popup will show. Phone reboots but the Lineage "corrupt" screen comes up. Hitting Try Again works and it boots successfully.
Device in hand, I’m doing some research before flashing so here is a question about backing up and restoring when using this ROM on G7 Power (and maybe A/B devices in general). I’ve become accustomed to (or spoiled by) being able to install ROM/Gapps/SU, backup, or restore OS and apps (boot, data, system) from TWRP using resources on the external SD without connecting to computer. Not only was that convenient but it was also good for ROM bug testing; easy to test > break > restore.
Having accepted the reality of being attached to a computer for some of this work I’m still wondering about the best way to get full device backups. On a Moto X4 running LOS 15.1, where I had flashed in a recommended order to keep TWRP and LOS on the device (without LOS overwriting boot) there were problems with backing up. The ROM ran fine but any attempt to back it up (whether on device running TWRP via ADB) seemed to trash the existing installation so it would not boot. To be clear I’m not talking about attempts to restore a backup; the mere act of backing up the existing partitions seemed to break things. At the time SyberHexen gave some advise but I never had a chance to try it, and wanted to do a bit more fishing here first.
So - long story/question short(er): Does anybody here know what is the most reliable way to create a “whole device” backup (equivalent to boot/data/system from before A/B) so that a ROM scrambled by testing can be easily restored…to a backup copy that can be selected from an archive of backups (as opposed to just the other slot)?
IronTechmonkey said:
Device in hand, I’m doing some research before flashing so here is a question about backing up and restoring when using this ROM on G7 Power (and maybe A/B devices in general). I’ve become accustomed to (or spoiled by) being able to install ROM/Gapps/SU, backup, or restore OS and apps (boot, data, system) from TWRP using resources on the external SD without connecting to computer. Not only was that convenient but it was also good for ROM bug testing; easy to test > break > restore.
Having accepted the reality of being attached to a computer for some of this work I’m still wondering about the best way to get full device backups. On a Moto X4 running LOS 15.1, where I had flashed in a recommended order to keep TWRP and LOS on the device (without LOS overwriting boot) there were problems with backing up. The ROM ran fine but any attempt to back it up (whether on device running TWRP via ADB) seemed to trash the existing installation so it would not boot. To be clear I’m not talking about attempts to restore a backup; the mere act of backing up the existing partitions seemed to break things. At the time SyberHexen gave some advise but I never had a chance to try it, and wanted to do a bit more fishing here first.
So - long story/question short(er): Does anybody here know what is the most reliable way to create a “whole device” backup (equivalent to boot/data/system from before A/B) so that a ROM scrambled by testing can be easily restored…to a backup copy that can be selected from an archive of backups (as opposed to just the other slot)?
Click to expand...
Click to collapse
Some people have done it with success if u not rooted and have twrp flashed u can't read internal sd it is cripted until magisk is flashed .No I heard that dmvertey will decript with out root but u can't set lock screen in os.
roadkill42 said:
Some people have done it with success if u not rooted and have twrp flashed u can't read internal sd it is cripted until magisk is flashed .No I heard that dmvertey will decript with out root but u can't set lock screen in os.
Click to expand...
Click to collapse
This is the latest twrp for this phone touch ishue should b fixed. Siberhexon updated twrp
roadkill42 said:
Some people have done it with success if u not rooted and have twrp flashed u can't read internal sd it is cripted until magisk is flashed .No I heard that dmvertey will decript with out root but u can't set lock screen in os.
Click to expand...
Click to collapse
Thanks, I've heard about issues with lock screen/encryption and would deal with that for testing purposes by disabling security before doing anything in TWRP. I may have to be content with re-flashing and restoring apps if anything breaks.
[EDIT] I saw that you added a link to a TWRP build.which is appreciated but I would first try the official one (twrp-installer-3.4.0-0-ocean.zip) which the LOS instructions indicate. If I did use an alternative I'd want to get it from a designated portal and know more about its origins.
Derp. Disregard previous mention of official build. That was Pixel not LOS. As yet this is the only thread for LOS Ocean Moto G7 Power dev.
IronTechmonkey said:
Derp. Disregard previous mention of official build. That was Pixel not LOS. As yet this is the only thread for LOS Ocean Moto G7 Power dev.
Click to expand...
Click to collapse
Well the official one is missing some things then one I posted whit h has no problems I use it
roadkill42 said:
Well the official one is missing some things then one I posted whit h has no problems I use it
Click to expand...
Click to collapse
The post you replied to was about LOS, not TWRP, but as to TWRP, I appreciate that you shared and I know custom versions of TWRP may have important additional capability, but I would still not recommend anyone use TWRP from an unknown source. You can make it a known source by sharing a link to where it came from or to its developer.
IronTechmonkey said:
The post you replied to was about LOS, not TWRP, but as to TWRP, I appreciate that you shared and I know custom versions of TWRP may have important additional capability, but I would still not recommend anyone use TWRP from an unknown source. You can make it a known source by sharing a link to where it came from or to its developer.
Click to expand...
Click to collapse
What we use on tellagram group for moto g7 power so it's is better than the one from the official it will get this soon from what I was told believe syber hexon one who did it
roadkill42 said:
What we use on tellagram group for moto g7 power so it's is better than the one from the official it will get this soon from what I was told believe syber hexon one who did it
Click to expand...
Click to collapse
Aaaahhhh, now you are making a connection to things I know. The fact that SyberHexen worked on it would be enough for me to trust it. In any event it is still best to link to the source rather than re-post (whenever possibe) so that people may see the trail and know what they are dealing with. Perhaps you could edit the post where you shared it, to say it came from some of the same devs that work on the ROM. With a note like that I would have had no doubts. In any event, I may wait for the patch to go official and work around the issue until then but it is good to know about. Thanks again for the tip and the tweaked version of TWRP.
[EDIT] Here is a direct link to the download: https://androidfilehost.com/?fid=8889791610682939639.
IronTechmonkey said:
Device in hand, I’m doing some research before flashing so here is a question about backing up and restoring when using this ROM on G7 Power (and maybe A/B devices in general). I’ve become accustomed to (or spoiled by) being able to install ROM/Gapps/SU, backup, or restore OS and apps (boot, data, system) from TWRP using resources on the external SD without connecting to computer. Not only was that convenient but it was also good for ROM bug testing; easy to test > break > restore.
Click to expand...
Click to collapse
Yes, I actually performed my entire installation using TWRP and had all of the necessary files loaded on the external SD card. The only time (to my recollection) that a PC is necessary is to launch TWRP for the first time using Fastboot.
edit: A note of caution: Be sure to follow the "copy partitions" steps regardless. If you do not, you will brick your device. This must only be done once when you transition from stock to a custom ROM.
Greek2me said:
Yes, I actually performed my entire installation using TWRP and had all of the necessary files loaded on the external SD card. The only time (to my recollection) that a PC is necessary is to launch TWRP for the first time using Fastboot.
edit: A note of caution: Be sure to follow the "copy partitions" steps regardless. If you do not, you will brick your device. This must only be done once when you transition from stock to a custom ROM.
Click to expand...
Click to collapse
Thanks. That's the same drill I used for Moto X4 so I'm set... in that regard.
Unfortunately I did a stupid thing facilitated by Moto's dreadful documentation. Having used several devices with sim/SD tray in top right top edge, and with the in-box documentation failing to label the Mic that is now at the top right edge, I very likely damaged the mic thinking it was the tray. My fault for missing a different label for the tray but Moto made this error too easy (and their support claimed the top Mic was the proximity sensor). I will try to exchange device and start over.
does anyone know how to "relock" bootloader on this device even if that is just removing the bootloader lock warning?
IronTechmonkey said:
Thanks. That's the same drill I used for Moto X4 so I'm set... in that regard.
Unfortunately I did a stupid thing facilitated by Moto's dreadful documentation. Having used several devices with sim/SD tray in top right top edge, and with the in-box documentation failing to label the Mic that is now at the top right edge, I very likely damaged the mic thinking it was the tray. My fault for missing a different label for the tray but Moto made this error too easy (and their support claimed the top Mic was the proximity sensor). I will try to exchange device and start over.
does anyone know how to "relock" bootloader on this device even if that is just removing the bootloader lock warning?
Click to expand...
Click to collapse
Not recommended as this can really brick your device.
Just flash custom bootloader logo.bin to remove that screen
---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------
I'll be making new devdb posts for official G7 ocean/channel..
once threads are active please post there.
Thx
SyberHexen said:
Not recommended as this can really brick your device.
Just flash custom bootloader logo.bin to remove that screen
Click to expand...
Click to collapse
That's what I was fishing for. There may be a chance I don't have to exchange device but if so that's what I'll do. Thanks for the coaching and for the work on Moto devices, especially the G7 Power.