I noticed the audio level can sometimes be a little low, despite being at the same volume setting. Restarting the device seems to resolve the issue, though In looking for the audio settings it appears as though i don't have any audio options, i.e Histen sound and audio equalizer. These options were previously available under EMUI 5.1, but not on EMUI 8.
Any ideas?
I'm on EMUI 8 and everything is here. Do you have any mod installed? https://imgur.com/b5XnFBy https://imgur.com/Khb5cWt
Paulo87 said:
I'm on EMUI 8 and everything is here. Do you have any mod installed? https://imgur.com/b5XnFBy https://imgur.com/Khb5cWt
Click to expand...
Click to collapse
Thanks. No mods are installed for audio. This is what i see:
https://imgur.com/a/IncHN
My 'about phone' page shows exactly what yours does.
@mightyjcb :
What's your firmware version ?
C900B321 ?
mightyjcb said:
Thanks. No mods are installed for audio. This is what i see:
https://imgur.com/a/IncHN
My 'about phone' page shows exactly what yours does.
Click to expand...
Click to collapse
If your version is C432, i would suggest that you backup everything, plug it to your pc and restore your phone.
If you have a different version, it might be due to licensing. Best of luck :good:
oslo83 said:
@mightyjcb :
What's your firmware version ?
C900B321 ?
Click to expand...
Click to collapse
I'm using C432. Running b360a
mightyjcb said:
I'm using C432. Running b360a
Click to expand...
Click to collapse
And you updated from wich version ? Any rebrand during the way ?
Are you using a simcard ? Which carrier, mnc and mcc ?
I saw some histen config references on some xml or prop...
oslo83 said:
And you updated from wich version ? Any rebrand during the way ?
Are you using a simcard ? Which carrier, mnc and mcc ?
I saw some histen config references on some xml or prop...
Click to expand...
Click to collapse
I updated to Oreo B360 using the OldDroid method from what i think was the last update issued to Nougat OTA by Huawei/Honor.
I then installed LOS 15.1 and reverted back to EMUI 8 by flashing :
System (stock)
Recovery (stock)
KERNEL_B360a_TOUCH_FIX, then flashed the stock kernel over the touch fix image.
Mostly from your advice in thread https://forum.xda-developers.com/honor-9/help/oreo-nougat-recovery-stf-l09-t3760961)
No rebranding took place.
I have a sim card in the phone on the Giff Gaff network (Uses o2 infrastructure).
MCC: 234
MNC: 10
Cheers
No viper4android ?
Bluetooth headset ?
Sincebyou reverted back to EMUI 8 from LOS15 by flashing stock System then stock recovery:
Did you performed a full system wipe in stock recovery ? This may bee needed.
Matte, if you have a pc, connect your phone to your pc and in hisuite there's an option to restore your phone. It will install the latest full package. If you don't own a pc or don't want to use your pc, you can always try going in to the settings menu> System> System update> Options> Download latest full package.
Make sure you backup all of your data in both cases. Good luck.
oslo83 said:
No viper4android ?
Bluetooth headset ?
Sincebyou reverted back to EMUI 8 from LOS15 by flashing stock System then stock recovery:
Did you performed a full system wipe in stock recovery ? This may bee needed.
Click to expand...
Click to collapse
No viper4android has ever been installed. No bluetooth headset has ever been used with the device.
A full system wipe and stock recovery was necessary in order to go back to EMUI8 from LOS.
Paulo87 said:
Matte, if you have a pc, connect your phone to your pc and in hisuite there's an option to restore your phone. It will install the latest full package. If you don't own a pc or don't want to use your pc, you can always try going in to the settings menu> System> System update> Options> Download latest full package.
Make sure you backup all of your data in both cases. Good luck.
Click to expand...
Click to collapse
I can try the restore using Hisuite on my PC later. In the meantime, using the 'Download latest full package' simply returns no update available. The same to pressing 'Check For Updates' on the System Updates page. Which i think is probably the correct behavior given that i am running the latest version available.
I have exactly same problem as you. No Histen sound effects nor audio equalizer. Volume after restart is great, then i can pick up phone after few hours and it's really quiet on max volume. Did you debloat your phone ? Because i accidentally deleted stock music app, it could have something to do with it.
I noticed i also was not able to do any OTA updates to the device either. @robenzo420 are you running/ able to run Oreo patched to March 1st 2018? This encouraged me to fix the issue.
I used HiSuite to rollback to Nougat. Then updated OTA to Oreo, patch mentioned above was then available to update to OTA.
I now have the Histen sound effects available again.
Is this related to the 360 kernel fix image i installed? Is it related to my reverting back to EMUI 8 from a custom ROM - probably.
robenzo420 said:
I have exactly same problem as you. No Histen sound effects nor audio equalizer. Volume after restart is great, then i can pick up phone after few hours and it's really quiet on max volume. Did you debloat your phone ? Because i accidentally deleted stock music app, it could have something to do with it.
Click to expand...
Click to collapse
I cant say for certain, but don't think i deleted that app.
Be interesting to know exactly how we both managed to do this to these devices. Sadly, i do not think there is the developer support available to answer it.
mightyjcb said:
I noticed i also was not able to do any OTA updates to the device either. @robenzo420 are you running/ able to run Oreo patched to March 1st 2018? This encouraged me to fix the issue.
I used HiSuite to rollback to Nougat. Then updated OTA to Oreo, patch mentioned above was then available to update to OTA.
I now have the Histen sound effects available again.
Is this related to the 360 kernel fix image i installed? Is it related to my reverting back to EMUI 8 from a custom ROM - probably.
Click to expand...
Click to collapse
No OTA for me, probably because i'm unlocked and rooted. Check my post history i found temporary fix for me, no low volume anymore.
mightyjcb said:
I noticed i also was not able to do any OTA updates to the device either. @robenzo420 are you running/ able to run Oreo patched to March 1st 2018? This encouraged me to fix the issue.
I used HiSuite to rollback to Nougat. Then updated OTA to Oreo, patch mentioned above was then available to update to OTA.
I now have the Histen sound effects available again.
Is this related to the 360 kernel fix image i installed? Is it related to my reverting back to EMUI 8 from a custom ROM - probably.
Click to expand...
Click to collapse
No, i'm still running older build. What is 360 kernel fix? I flashed something kernel related for enabling buttons on my phone.
robenzo420 said:
No OTA for me, probably because i'm unlocked and rooted. Check my post history i found temporary fix for me, no low volume anymore.
Click to expand...
Click to collapse
I believe you are correct. Rooting will mean that you are unable to update the device OTA. I am not so sure about OTA updates with the device unlocked.
robenzo420 said:
No, i'm still running older build. What is 360 kernel fix? I flashed something kernel related for enabling buttons on my phone.
Click to expand...
Click to collapse
Then that is most likely the kernel image i referred to. It has a fix for buttons among other things. (If you want, you can flash the stock kernel image over the custom one you have now, and it will leave buttons active etc.)
As i say, this issue is now resolved.
Related
These update packages should work on global variant Nokia X6.
Usage:
Confirm your current version by dialing *#*#227#*#* before update.
Then download the package and rename to the specific filename I gave, place it to root directory of internal storage and dial *#*#874#*#* to update.
After the update procedure completed, update package will be deleted from your phone automatically.
Global Release:
Note: From DRG-250A build, it blocked current bootloader unlock method, be careful.
Click to expand...
Click to collapse
June 2018 to August 2018 (DRG-250A-0-00WW-B05-229D-0-00WW-B01-update.zip)
August 2018 to September 2018 (DRG-250B-0-00WW-B01-250A-0-00WW-B05-update.zip)
Android Pie November 2018 (DRG-330B-0-00WW-B01-update.zip)
Thanks for your work supporting our device!
Do you have boot image of 250A version?
izkyline said:
Do you have boot image of 250A version?
Click to expand...
Click to collapse
Yes that would be handy. I read that payload_dumper doesn't work on incremental updates. I'm still looking for ways to extract a boot.img
Hi bro I need to unlock the blltloader for my nonia 6.1 ta-1050 . If you could help me plzz
---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------
My nokia
DRG-250A-boot_patched.img patched with Magisk v17.1:
https://www111.zippyshare.com/v/12gKJE7u/file.html
how to update the path for x6
Hello,
*#*#227#*#* works well.
*#*#874#*#* has no response at all. Is root or bootloader required to do that?
I just realize the X6 I bought from ebay is global firmware version, which does not support OTA. Use OTA to update to latest firmware is a key feature I am looking for. I do not care it is China version or Global version.
Do you have any suggestion that what should be the easiest way? Hopefully no bootloader required. Thanks!
google play pretent CN OTA?
Boss,
After discuss with many other user, we think it is because I am using China version rom, but installed Google play, which pretent OTA update.
Do you think so? Could you give us a solution?
I bought the phone from ebay. I just need OTA.
yshgcs said:
Hello,
*#*#227#*#* works well.
*#*#874#*#* has no response at all. Is root or bootloader required to do that?
I just realize the X6 I bought from ebay is global firmware version, which does not support OTA. Use OTA to update to latest firmware is a key feature I am looking for. I do not care it is China version or Global version.
Do you have any suggestion that what should be the easiest way? Hopefully no bootloader required. Thanks!
Click to expand...
Click to collapse
Will this work on Android one varient i.e , Nokia 6.1 plus?
Do you have boot image of 250B version? I need root my device, boot September, help me
thaidaidong25 said:
Do you have boot image of 250B version? I need root my device, boot September, help me
Click to expand...
Click to collapse
Use the boot image from Nokia 7 Plus. They work. Just don't flash it, only boot it.
thanks for sharing, i just installed the pie version on my nokia 6.1 plus
Hey I just installed the pie version on my Nokia 6.1 plus (TA-1083).
Will the installation void my warranty?
My camera app is crashing like crazy... Is anyone else experiencing this?
xoxoJoelxoxo said:
Hey I just installed the pie version on my Nokia 6.1 plus (TA-1083).
Will the installation void my warranty?
My camera app is crashing like crazy... Is anyone else experiencing this?
Click to expand...
Click to collapse
No, it will not destroy the warranty at all. As for the camera app, go to the app's settings and try wiping its data completely. Then reboot your phone and try again.
DJBhardwaj said:
No, it will not destroy the warranty at all. As for the camera app, go to the app's settings and try wiping its data completely. Then reboot your phone and try again.
Click to expand...
Click to collapse
Well, that didn't do the trick, but I just simply clicked 'disable' after wiping the data and it gave me a message of "uninstalling app and installing factory camera app" which worked beautifully.
Now everything's working fine.
1. *#*#874#*#* is this make my phone rooted ?
because when i type it on my phone, it give message such install, chance data erased, and the last is root
"Would you like to install the following system software?
System upgrade to 330B.B01
You will be unable to use your device or make emergency calls during the upgrade.
It will lead to unexpected result if you cut off power or remove downloaded file while updating software.
There is small possibility of erasing user data caused by upgrade purpose. If need, please backup your data before installing system upgrade.
The normal update can not be guaranteed after the device is rooted. If root contributes to abnormal use on the device in update process, the user should be responsible for it oneself"
2. my type is TA-1116 with build number 00WW_2_50A_SP01, after updating using this method, will it change to another model and build number or not ?
3. is the link that has been shared is the latest update that rolled to some user on 31 October 2018 ?
thank's for sharing the file, and kindly reply to my question
snowdance said:
1. *#*#874#*#* is this make my phone rooted ?
because when i type it on my phone, it give message such install, chance data erased, and the last is root
"Would you like to install the following system software?
System upgrade to 330B.B01
You will be unable to use your device or make emergency calls during the upgrade.
It will lead to unexpected result if you cut off power or remove downloaded file while updating software.
There is small possibility of erasing user data caused by upgrade purpose. If need, please backup your data before installing system upgrade.
The normal update can not be guaranteed after the device is rooted. If root contributes to abnormal use on the device in update process, the user should be responsible for it oneself"
2. my type is TA-1116 with build number 00WW_2_50A_SP01, after updating using this method, will it change to another model and build number or not ?
3. is the link that has been shared is the latest update that rolled to some user on 31 October 2018 ?
thank's for sharing the file, and kindly reply to my question
Click to expand...
Click to collapse
1. Your phone won't be rooted
2. Your phone model won't change but build number, of course, will be changed due to system update.
3. Yes, yes it is.
hoatongoc said:
1. Your phone won't be rooted
2. Your phone model won't change but build number, of course, will be changed due to system update.
3. Yes, yes it is.
Click to expand...
Click to collapse
already installed it last night, and it work's !
thank's for the reply
Will I still receive OTA updates by HMD for my device when I check for it?
xoxoJoelxoxo said:
Will I still receive OTA updates by HMD for my device when I check for it?
Click to expand...
Click to collapse
you will, i already ask it with the support center from my country in indonesia
Hey guys,
On TeamMT's firmware finder is EMUI for VTR-L09 and VTR-L29 International (C432) available.
Post here if you tried to update and if it's works or not.
Edit: Updated B381 with a modified version of my guide. I'll release it today for testing purposes. I didn't do a factory reset, all my files are still there. But I noticed that the system works slowly.
Did you update through e-recovery in ff?
If you do factory reset, it will probably fix the slow performance.
Does the device show as official in play store/about? Is it beta or official release? Did you upgrade from B384?
skolebolle said:
Did you update through e-recovery in ff?
If you do factory reset, it will probably fix the slow performance.
Does the device show as official in play store/about? Is it beta or official release? Did you upgrade from B384?
Click to expand...
Click to collapse
I updated with my own script I released here (tutorial 4)
It's not slow anymore, I did a reboot and now everything works fine.
I upgraded from B381.
There's no information by Huawei if it's beta or stable.
And what do you mean with official in play store? Couldn't find anything like that.
He talks about 'certified device' under settings in google play.
Firicel69 said:
He talks about 'certified device' under settings in google play.
Click to expand...
Click to collapse
There's nothing about that, I googled some screenshots and the part with "Device certification" is completely missing. Play Services updated directly after I launched Pie for the first time.
See the attached screenshot.
Jannomag said:
I updated with my own script I released here (tutorial 4)
It's not slow anymore, I did a reboot and now everything works fine.
I upgraded from B381.
There's no information by Huawei if it's beta or stable.
And what do you mean with official in play store? Couldn't find anything like that.
Click to expand...
Click to collapse
Works just fine, tnx.
I doubt that beta fw would be up to c432. Besides a day ago Oreo downgrade popped up there was no fw update this month.
Jannomag said:
There's nothing about that, I googled some screenshots and the part with "Device certification" is completely missing. Play Services updated directly after I launched Pie for the first time.
See the attached screenshot.
Click to expand...
Click to collapse
It should come after some time. Try reset phone and wait. If it says uncertified it's bad. If it says certified, it's safe for us to upgrade before official release.
skolebolle said:
It should come after some time. Try reset phone and wait. If it says uncertified it's bad. If it says certified, it's safe for us to upgrade before official release.
Click to expand...
Click to collapse
I'm on Pie now for 10 hours and installed some apps via Play Store. Still nothing to see there.
EDIT: I removed the data and cache from play store app. Now it's saying "Not certified". So I checked some guides and on the official Google page to enable custom roms for using Googles services there's the command "adb root".
My output is "adbd cannot run as root in production builds", so maybe it's still in beta. I don't know what this means for me but I hope there will be any problems with Google in the future for me.
EDIT2: I followed this tutorial and added my device to the device list. Play Store still shows uncertified but I'm hoping, that this won't affect me. At the moment I can use everything as before.
Jannomag said:
I'm on Pie now for 10 hours and installed some apps via Play Store. Still nothing to see there.
EDIT: I removed the data and cache from play store app. Now it's saying "Not certified". So I checked some guides and on the official Google page to enable custom roms for using Googles services there's the command "adb root".
My output is "adbd cannot run as root in production builds", so maybe it's still in beta. I don't know what this means for me but I hope there will be any problems with Google in the future for me.
EDIT2: I followed this tutorial and added my device to the device list. Play Store still shows uncertified but I'm hoping, that this won't affect me. At the moment I can use everything as before.
Click to expand...
Click to collapse
Unfortunately, this happens when the firmware still is not "approved for installation". That the device is not certified can make it hard to install bank apps, Netflix, Spotify and more. Also I think you will not receive any more ota. I would go back to b384 and wait to get official update.
skolebolle said:
Unfortunately, this happens when the firmware still is not "approved for installation". That the device is not certified can make it hard to install bank apps, Netflix, Spotify and more. Also I think you will not receive any more ota. I would go back to b384 and wait to get official update.
Click to expand...
Click to collapse
I always installed firmwares which aren't approve for installation (checked with FF). Never had any issues with banking, netflix, spotify and other apps.
But I never checked this, because I didn't know this.
Is this the same as SafetyNet?
Downgrade from 9 to 8
Jannomag said:
Hey guys,
On TeamMT's firmware finder is EMUI for VTR-L09 and VTR-L29 International (C432) available.
Post here if you tried to update and if it's works or not.
Edit: Updated B381 with a modified version of my guide. I'll release it today for testing purposes. I didn't do a factory reset, all my files are still there. But I noticed that the system works slowly.
Click to expand...
Click to collapse
Hello,
How downgrade my VTR-L09C432 from android 9 to android 8 or how relock bootloader on android 9?
coabog said:
Hello,
How downgrade my VTR-L09C432 from android 9 to android 8 or how relock bootloader on android 9?
Click to expand...
Click to collapse
If you're willing to test it, you can try my script. Please use tutorial #3 and this TWRP.
The reason for tutorial #3 is this guide I've found. The linked script works the same as my script does.
Just follow tutorial#3 but first completely remove any device lock like pin and fingerprint.
Otherwise, there's no official method for the P10. I'll try my own when I have time, maybe today's afternoon.
How's the phone compared to oreo? Any difference in terms of daily performance? Smoother?
Firicel69 said:
How's the phone compared to oreo? Any difference in terms of daily performance? Smoother?
Click to expand...
Click to collapse
No issues, the animations feel a bit smoother I think.
I noticed that gboards haptic feedback failed sometimes which is kinda annoying. Mostly I type very fast and it feels like I missed a key when I'm in a flow. That's the only bug I noticed.
Face unlock is way faster btw
Did they change the camera app or is it still the same? Thanks .
Camera app is a bit different, has adittional slider to switch functions, more convenient imo.
@Jannomag do you have 'Game Suite' app on pie? I am confused if it disappeared or I've missed some update with gpu turbo patch.
On Pie, there is something like Apps assistant. You can find this in Settings > Apps.
lukastob said:
@Jannomag do you have 'Game Suite' app on pie? I am confused if it disappeared or I've missed some update with gpu turbo patch.
Click to expand...
Click to collapse
If I remind correctly it was there, yes. But I never used it.
So we can get it in about one or two weeks?
https://bit.ly/2H9FM3W
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!
The downgraded, tz fixed 6.2.8.0-3233/6.2.7.7-3033/6.2.7.6-2933/6.2.7.1-2493/6.2.6.8-2315 have been re-edited with this older rom. It's rooted and has a fully removed OTA patch so no more worrying about your 4K auto updating to the latest efuse burner OS. I'm going to slowly release more downgraded roms with this OTA patch on this forum. If you would like to download the latest rom with the older interface, I have a separate page found here
Fire TV Stick 4K 6.2.8.1 r3_4054 Fully Patched Rom
Here's the latest release 6.2.8.1_r3_4054 of the pre-rooted rom I've combined into one patched ota removed zip which packs the downgraded older interface with accessibility settings working again. After flashing, clear data in...
forum.xda-developers.com
Changelogs For All Downgraded Roms:
No more OTA updates so keep factory resetting as many times as you want! It won't update ever again until you manually flash a rom in TWRP!!!!!!
Your apps work as they should, will test out relocking the bootloader with this at some point.
Amazon FreeTime is now a stub apk for more storage space inside the system
TZ downgrades are necessary when installing these roms in TWRP
6.2.6.8/2315 makes the Imdb TV app disappear on this version
Notes:
If any of you guys are experiencing download issues I'd be glad enough to fix that! Let me know!!!!!!!
Here's the new downgraded 6.2.7.1-2493 OTA patched rom users have been waiting to downgrade!!
6.2.8.0-3233 is here! Enjoy the fast and snappy launcher performance!!!
Patched Roms that don't have Accessibility mods
6.2.7.6-2933
6.2.7.7-3033
6.2.8.0-3233
Issues (NS6268/NS6271/2493/NS6276/2933)
Unlike 6.2.7.7/3033, AV Sync Tuning will not work with these roms. Some apps require a system update for use. Install 6.2.7.7/3033 or 6.2.7.6/2933 to fix.
6.2.6.8-2315 will kick you back to the home menu after going through settings
Work in Progress
N/A
Skel40 said:
The downgraded, tz fixed 6.2.7.7-3033 have been re-edited with this older rom. It's rooted and has a fully removed OTA patch so no more worrying about your 4K auto updating to the latest efuse burner OS. I'm going to slowly release more downgraded roms with this OTA patch on this forum. If you would like to download the latest rom with the older interface, I have a separate page found here
Fire TV Stick 4K 6.2.8.1 r3_4054 Fully Patched Rom
Here's the latest release 6.2.8.1_r3_4054 of the pre-rooted rom I've combined into one patched ota removed zip which packs the downgraded older interface with accessibility settings working again. After flashing, clear data in...
forum.xda-developers.com
Changelogs:
No more OTA updates so keep factory resetting as many times as you want! It won't update ever again until you manually flash a rom in TWRP!!!!!!
Your apps work as they should, will test out relocking the bootloader with this at some point.
Amazon FreeTime is now a stub apk for more storage space inside the system
Click to expand...
Click to collapse
Do NOT relock your bootloader. Your stick will be bricked.
SweenWolf said:
Do NOT relock your bootloader. Your stick will be bricked.
Click to expand...
Click to collapse
I relocked the bootloader before with the patch FOTA and it works
6.2.7.6/2933 patched is now available to flash and downgrade
@Skel40 Is it possible to roll out the ability to route audio thru USB on this thing like I want to use USB DAC thru OTG /w bypassing android audio drivers so I can route the audio on 3.5mm jack to Aux? Is that gonna work all on AFTV4k? thanks
yan2xme said:
@Skel40 Is it possible to roll out the ability to route audio thru USB on this thing like I want to use USB DAC thru OTG /w bypassing android audio drivers so I can route the audio on 3.5mm jack to Aux? Is that gonna work all on AFTV4k? thanks
Click to expand...
Click to collapse
I wouldn't know. Maybe @SweenWolf would give you an idea what you're talking about
please add 6.2.6.8 pls cause this is the only version that support gapps with google search by tsynik, heres the rooted version of rbox https://download.djjproject.com/firestick4k/mantis-6.2.6.8-rooted_r1.zip
thanks @Skel40
So this will downgrade my fire stick so I can root it with k4y0z root guide?
I've been unable to stream any fire stick apps after downgrading. The programs say 'can't find that title' or something like that. Newer versions work fine that have the new launcher.
What is going on here? Any ideas?
Only Plex and Emby work..
I have feeling I know why this is happening. I'm not installing Magisk. dm-verity might be the issue.
I just wanted to play audio in Passthrough, don't really care about rooting, just downgrading.
Also, why are they called pre-rooted ROMs anyway? They are the furthest thing from pre-rooted.
Just install magisk it roots it in seconds and you will be fine on 6.2.7.1. This thread is old.
Hi @Skel40 please che you build an 6.2.7.3-2773 rom with fixed tz image?
Or just share a fixed tz.img for this version.
It would be greatly appreciated
johnny_cage said:
Hi @Skel40 please che you build an 6.2.7.3-2773 rom with fixed tz image?
Or just share a fixed tz.img for this version.
It would be greatly appreciated
Click to expand...
Click to collapse
I'll look into it and post it here
Here it is. Be sure to skip the update screen by holding the menu and back arrow at the same time for Voiceview while internet is disconnected. Guide can be found here https://www.aftvnews.com/how-to-ski...reset-on-a-fire-tv-firestick-or-fire-tv-cube/
Skel40 said:
Here it is. Be sure to skip the update screen by holding the menu and back arrow at the same time for Voiceview while internet is disconnected. Guide can be found here https://www.aftvnews.com/how-to-ski...reset-on-a-fire-tv-firestick-or-fire-tv-cube/
Click to expand...
Click to collapse
Don't know how to thank you. Any way to donate via paypal?
"SOLVED"
I uploaded/copied the 3gb into my local download folder > update using the "choose update package" method, and failed.
The message said "Can't verify update, Can't flash this stable ROM". Any idea why?
Im currently on 13.0.10.0 (Android 11)
Update : Updated to V13.0.7.0.SKEMIXM as of 21 December 2022. Technically "fixed"
Have you tried redownloading it? Sometimes a wayward bit on a big download like this can mess up the checksum and prevent verification.
Jedi3815 said:
Im currently on 13.0.10.0 (Android 11)
Click to expand...
Click to collapse
Hang on, are you're trying to downgrade? I don't know how well that is supported via the built-in update functionality. Or is this a typo - I can't find 13.0.10.0 for this device?
aricooperdavis said:
Have you tried redownloading it? Sometimes a wayward bit on a big download like this can mess up the checksum and prevent verification.
Click to expand...
Click to collapse
Yes, about 5 times from 5 different sources. All failed
aricooperdavis said:
Hang on, are you're trying to downgrade? I don't know how well that is supported via the built-in update functionality. Is this a typo, I can't find 13.0.10.0 for this device.
Click to expand...
Click to collapse
Nope. Currently 13.0.10 android 11, wanting to upgrade to 13.0.5 android 12.
Ah I see. I have no idea how the OTA update system works with different android versions, sorry
I
aricooperdavis said:
Hang on, are you're trying to downgrade? I don't know how well that is supported via the built-in update functionality. Or is this a typo - I can't find 13.0.10.0 for this device?
Click to expand...
Click to collapse
The device was on v 13.0.10 for the latest Android 11 build. V 13.0.5 was the new MIUI build for Android 12, and for me brought a plethora of bugs. Immediately after the update, I received another notification for an update available, v13.0.6, which sort of fixed a couple of these bugs (such as a broken fingerprint sensor, akin to what Pixels experienced late last year) and I performed a factory reset afterwards. Most of them are gone now, but it's a complete mess this update system/ model.
Jedi3815 said:
Nope. Currently 13.0.10 android 11, wanting to upgrade to 13.0.5 android 12.
Click to expand...
Click to collapse
Try pausing the update from your system update settings pane, go into download, delete the package and restart download after a reboot.
Frank_Kinuthia said:
Try pausing the update from your system update settings pane, go into download, delete the package and restart download after a reboot.
Click to expand...
Click to collapse
I did that before, still fail. Now they have released the 13.0.6 Android 12 version, successful. so yeay.