Related
STOCK ANDROID 6.0 MARSHMALLOW ROM
FOR THE LENOVO TAB 3 8"/TB3-850F
TWRP FLASHABLE ZIP
FORCE ENCRYPTION & DM-VERITY DISABLED
DISCLAIMER: Your warranty will be voided by installing this ROM, unlocking your bootloader, or flashing a custom recovery. You hereby assume sole responsibility for any positive or negative consequences incurred by flashing this ROM. As always, flashing your Android device or otherwise altering its file system & partitions involves an inherent risk. I am not responsible for any devices which are bricked or otherwise rendered inoperable as a result of flashing this ROM. However, in such scenarios,
I will provide all support feasibly possible. Follow the simple instructions carefully and you should experience no adverse affects.
Lenovo's open source code for this ROM encompasses both the 850F & 850M variants of this tablet. Therefore, this ROM should be completely compatible with the TB3-850M as well.
NOTES:
This Stock Android 6.0 ROM is virtually unmodified. However, it should be noted that dm-verity (device mapping) and force encryption have been disabled via patched boot image. This is the most current stock OS for the Lenovo Tab 3 8"; therefore, no OTAs will need to be installed subsequent to flashing this ROM. In order to ensure that force encryption gets disabled, it is imperative that the /userdata (Data) partition is formatted in TWRP prior to Installation. Please carefully follow the below instructions.
For those members who want a pure stock experience, but also want root access of the stock OS, I'm currently compiling a deodexed & zipaligned version of this ROM, fully rooted with Magisk 14.0 & BusyBox binaries pre-installed.
SPECIFICATIONS:
Android Version: 6.0 Marshmallow
Build No: TB3-850F_S100031_171010_ROW
Kernel Version: 3.18.19
SDK Version: 23
Software Version: TB3-850F_160412
Build ID: MRA58K
Android Security Patch Level: 9/05/2017
Runtime Version: ART 2.1.0
Hardware Version: LenovoPad TB3-850F
Board Platform: MediaTek MT6735M
CPU: 64-Bit, Quad-Core Cortex A-53 - 1.0GHz
GPU: Mali T720 - 450MHz
RAM: 1GB
OS Build Date: 10/10/2017
Source Code: http://pcsupport.lenovo.com/us/en/products/tablets/a-series/tab3-8/downloads/ds112711
REQUIREMENTS:
1. Unlocked bootloader;
2. TWRP recovery;
This is a pure stock, unmodified, TWRP flashable Android 6.0 Marshmallow ROM for the Lenovo Tab 3 8". This ROM was compiled from the most recent stock /boot and /system images. However, as noted previously, the boot image has been unpacked, patched, and repacked in order to disable dm-verity and force encryption. Because raw firmware images were used in compiling this ROM, the file size is in excess of 1GB (approximately 1.35GB).
INSTRUCTIONS:
1. Download the ROM from the link provided and save it to your external micro SD card. Do not save to internal storage, as your /data partition will need to be formatted prior to installation;
2. Boot your tablet into TWRP recovery;
3. Wipe /system, /data, /cache & /Dalvik-ART cache. Also, select "Wipe", then "Format Data." This step is crucial to ensure disabling of force encryption. Please note that once installed, you may go to SETTINGS>>SECURITY and opt to encrypt the userdata on the tablet;
4. Select INSTALL, navigate to the location in which you saved the ROM zip file, and initiate installation. Flashing will complete in approximately 3 - 4 minutes;
5. Reboot system.
You should now have unmodified stock Android 6.0 installed on your Tab 3, as well as disabled dm-verity and disabled force encryption.
DOWNLOAD LINKS:
Stock Android 6.0 ROM --
TB3-850F_S100031_171010_ROW: https://drive.google.com/file/d/1iMf0Ns_XWGpYlNmXCvUsW_1DfaRMeIuO/view?usp=drivesdk
Stock Recovery Image: https://drive.google.com/file/d/1D6A7b080luzsSf0xLJSCqPBNeQLSWo94/view?usp=drivesdk
Unpatched Stock Boot Image: https://drive.google.com/file/d/1azgIrPbfJHBzZF9R4IUMxIGNga6vjipD/view?usp=drivesdk
Lenovo File Manager (APK): https://forum.xda-developers.com/android/general/app-lenovo-file-manager-lenovo-tab-3-8-t3706161
Lenovo Tab 3 8" User Guide --
TB3-850F & TB3-850M (English)(PDF): https://drive.google.com/file/d/18gCTfuZecJnlB0ddBIN02YPaDpuvmzov/view?usp=drivesdk
Older Build(s):
TB3-850F_S100030_161209_ROW: https://drive.google.com/file/d/0B1Sfod4HWfk2aTNtVmJHZGpWZEE/view?usp=drivesdk
BUGS: Please report any and all bugs, no matter how seemingly trivial or insignificant. For those members with the knowledge, please submit a proper bug report. If you are not sure how, simply provide as many facts & details as possible. If you are having problems with apps, please specify as to whether the app is from Google Play. Also, please DO NOT submit bug reports unless you are utilizing this ROM in its present form -- unmodified, pure stock. Custom kernels, mods & tweaks (e.g. Xposed framework) & any deviations from pure stock will make it futile to analyze bug reports. Instead, provide with detail the precise nature of the problem. If reporting a bug, please specify if you are rooted (systemless or system-mode) and/or have BusyBox binaries installed. Submit screenshots of bugs if possible.
Brilliant! Will download now and report back later. Thank you.
My custom ROM for this tablet should be coming out of the Android Kitchen later this evening. I've dubbed it Ethereal OS v1.1 [Android 6.0.1]. Extremely lightweight yet moderately feature packed.
MotoJunkie01 said:
My custom ROM for this tablet should be coming out of the Android Kitchen later this evening. I've dubbed it Ethereal OS v1.1 [Android 6.0.1]. Extremely lightweight yet moderately feature packed.
Click to expand...
Click to collapse
Nice!
After flashing the stock zip TWRP says unknown error. It booted up fine to where you login to your gmail and "bluetooth sharing has stopped working" pops up. Bluetooth can not be turned on within settings. I can not double swipe down to get to the notifications and the "Home" and "Recents" buttons do not seem to work although they both vibrate when pressed.
I will flash stock with SPFT and try your stock rom again.
stonedpsycho said:
Nice!
After flashing the stock zip TWRP says unknown error. It booted up fine to where you login to your gmail and "bluetooth sharing has stopped working" pops up. Bluetooth can not be turned on within settings. I can not double swipe down to get to the notifications and the "Home" and "Recents" buttons do not seem to work although they both vibrate when pressed.
I will flash stock with SPFT and try your stock rom again.
Click to expand...
Click to collapse
I got the same error with Bluetooth Share force closing two times at the setup screen. Probably a corruption issue during archiving the ROM. I'll do an md5 and archive the ROM again.
Seemed to work, however the loading images and screen is still lenovo. Also they lenovo apps are still there.
rongallant said:
Seemed to work, however the loading images and screen is still lenovo. Also they lenovo apps are still there.
Click to expand...
Click to collapse
This is not a custom ROM. This is pure stock. The Lenovo boot logo, boot animation & apps are supposed to be there. Like the title implies this an "Unmodified" stock ROM.
MotoJunkie01 said:
This is not a custom ROM. This is pure stock. The Lenovo boot logo, boot animation & apps are supposed to be there. Like the title implies this an "Unmodified" stock ROM.
Click to expand...
Click to collapse
My bad, understood.
On another note, I am finding it very buggy. The home and overview buttons do not work. They show you clicked it along with the haptic feedback, but nothing happens. The back button works and is the only way I know to get back to the home screen.
Also the tool panel you pull from the top stops working after a little while until I reboot. Then works for a little while.
The Play store downloads barely work. They show pending and nothing happens. I force quite, cleared the cache, disabled, reverted to the stock app and it works for a little bit. Then the other Play Store app comes back. Anyways, I am not complaining. I appreciate the work you put into this. It's awesome we get to do it at all. Just giving my feedback. P.S. It's a new TB3-850F.
rongallant said:
My bad, understood.
On another note, I am finding it very buggy. The home and overview buttons do not work. They show you clicked it along with the haptic feedback, but nothing happens. The back button works and is the only way I know to get back to the home screen.
Also the tool panel you pull from the top stops working after a little while until I reboot. Then works for a little while.
The Play store downloads barely work. They show pending and nothing happens. I force quite, cleared the cache, disabled, reverted to the stock app and it works for a little bit. Then the other Play Store app comes back. Anyways, I am not complaining. I appreciate the work you put into this. It's awesome we get to do it at all. Just giving my feedback. P.S. It's a new TB3-850F.
Click to expand...
Click to collapse
Yes. Very buggy indeed. I have determined that the bugs are due to corruption during the unpacking of the system image. I'm repacking the ROM now to alleviate the bugs. Thanks for your input...
I've managed to fix the major bugs reported upon initial install of the ROM -- Recents & Home Buttons, Quick Pulldown Menu, Google Framework bugs, New App Shortcut bugs, etc. Simply corruption during packing (archiving) the ROM zip. I will try my best to get a new build posted sometime today.
MotoJunkie01 said:
I've managed to fix the major bugs reported upon initial install of the ROM -- Recents & Home Buttons, Quick Pulldown Menu, Google Framework bugs, New App Shortcut bugs, etc. Simply corruption during packing (archiving) the ROM zip. I will try my best to get a new build posted sometime today.
Click to expand...
Click to collapse
Dear MotoJunkie
İs it possible to upload stock Fm Radio Aplication(offline radio) of Tab3 8? İn my Turkish model, theres no Fm radio aplication. I need it to use tablet in my car.
Thanks
MotoJunkie01 said:
I've managed to fix the major bugs reported upon initial install of the ROM -- Recents & Home Buttons, Quick Pulldown Menu, Google Framework bugs, New App Shortcut bugs, etc. Simply corruption during packing (archiving) the ROM zip. I will try my best to get a new build posted sometime today.
Click to expand...
Click to collapse
Did you get around to uploading it? I am unable to use the OTA update file. Says its missing 'android-info.txt'
Also, anyone care to point me to a way to get back to stock/unrooted?? Nooooo, I didn't backup my ROM first. That would have made way to much sense.
I've been out of commission, unfortunately, due to impending health issues once again. I know that hospital food sucks, that the pretty nurses don't typically put out easy, and that the hospital WiFi restrictions can easily be bypassed with a proxy server address. Lol. And that's all I've learned in the past ten days. Anyway, hope to be back in my daily routine in the next day or so and finishing some stuff up for this device.
Hi, is this thread alive? I'm interested in solution because i have about 60 tablets and need a solution to clone form one source tablet (config, apps, wlan, users, etc.) to other 59. I have tried adb backup --twrp and it went ok, but when i tried restore it gave errors with system partition and now i can only recover tablet with factory ROM from this thread (but it is buggy and cannot put it int to production like this). Is it possible to create system rom from other working tablet? Iwill be very pleased If You can write step by step, how to create zipped rom from working device so i can then upload it to share with others.
spiker_80 said:
Hi, is this thread alive? I'm interested in solution because i have about 60 tablets and need a solution to clone form one source tablet (config, apps, wlan, users, etc.) to other 59. I have tried adb backup --twrp and it went ok, but when i tried restore it gave errors with system partition and now i can only recover tablet with factory ROM from this thread (but it is buggy and cannot put it int to production like this). Is it possible to create system rom from other working tablet? Iwill be very pleased If You can write step by step, how to create zipped rom from working device so i can then upload it to share with others.
Click to expand...
Click to collapse
The thread is alive and I'm currently ironing out the errors on the posted ROM. The errors are due to a couple of permissions which are omitted on my updater-script file. I'll be posting an updated and hopefully error free release this week. Thanks for your interest and sorry for the delay in development. I've had a number of health issues of late and I'm now recovering.
Problem after wiping /system
Hi,
I´m new right here. I bought a new TB3-850F and wanted to flash the Original Stock Rom. After opening the Bootloader and booting into twrp like this way https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786 I wiped the /data /System /dalvic and /Cache. After that I rebooted the system.
But it only shows after starting the Lenovo-Logo. No more booting. Because of this I can´t start the fastboot modus with Minimal ADB and Fastboot.
Is there some idea how I can boot into fastboot?
Many thanks for your help,
sailor1977
sailor1977 said:
Hi,
I´m new right here. I bought a new TB3-850F and wanted to flash the Original Stock Rom. After opening the Bootloader and booting into twrp like this way https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786 I wiped the /data /System /dalvic and /Cache. After that I rebooted the system.
But it only shows after starting the Lenovo-Logo. No more booting. Because of this I can´t start the fastboot modus with Minimal ADB and Fastboot.
Is there some idea how I can boot into fastboot?
Many thanks for your help,
sailor1977
Click to expand...
Click to collapse
I´ve got a solution: After powering down, press power, wait 1 sec then hold both vol up & down also (all 3 Buttons) until vibrates. After starting in recovery Modus hold power button und press once the vol up.
With help of: https://forum.xda-developers.com/android/help/lenovo-tab3-8-2016-custom-recovery-t3483454 post #66
Ok. I've debugged the Stock 6.0 ROM in the OP. Fixed the Bluetooth force close issue at startup and the bugs involving the hardware buttons and the pull down menu. I'm traveling for work at the moment. Soon as I'm back home Monday I'll post the fixed build in the OP.
MotoJunkie01 said:
Ok. I've debugged the Stock 6.0 ROM in the OP. Fixed the Bluetooth force close issue at startup and the bugs involving the hardware buttons and the pull down menu. I'm traveling for work at the moment. Soon as I'm back home Monday I'll post the fixed build in the OP.
Click to expand...
Click to collapse
Cheers buddy. Good stuff ??
@Hemphiz, I hope all is well my friend. Something I wanted to get your input on. It seems that a few members have been experiencing boot loops and other problems after following the TWRP & Root thread I revised. I'm sort of at a brick wall in terms of figuring out what's going on. I'm thinking that maybe there are regional variants that are incompatible with the TWRP we use. Or, it could be one of those situations where instructions are not being closely followed. What are your thoughts? Thanks.
Few days ago as expected, official users (who is using CN-EN official ROMs) of Le Pro 3 AI (further mentioned "x7") got an OTA update to the latest release of EUI 6.0.030S.
The miracle that expected was not appeared. It is still based on Android 6.0.1 (Marshmallow).
The ROM is still not localized for other countries, it contains only CN and EN languages.
And there still many bloatware of LeEco services that is very annoyance.
But first of all, the apps inside are now more optimized and as I see, they starting and function faster then previously.
Ok, let's go to the main part - links =)
The Official Site where you can download the ROM based on OTA update scheme is HERE. Also you can download a copy of OTA package from HERE.
But if you want to download faster, you can use my clouds where I'm continuously holding the most of Official ROMs for x7.
---> MEGA (follow into the folder called "original_stock")
---> FEX
Inside my clouds you can find that the ROM filenames contains not only a version but also an appropriate suffix (_OTA or _FASTBOOT). It's used to separate the ROMs by the installation method.
The FASTBOOT prepared ROMs contains an installation scripts (.BAT for Windows and .SH for Linux/Mac) for not only full installation (with clearing of User Storage), but also for update (without clearing of User Storage).
Please be careful, don't even try to install via FASTBOOT without clearing of User Storage, if you currently have functioning non Official multilingual EUI like 5.9.027S (faked as 028S in menu "About phone") or other non official!!! If you'll do this you will get many conflicts in settings and apps.
I expect that the FASTBOOT updating instructions are widely known, but remind them once more:
1) Enable the "Developer options" menu by clicking on "Build number" 7 times in the "About phone"
2) In the "Developer options" menu, turn on "OEM unlocking" and "USB debugging"
3) Connect the phone to the computer with a USB cable
4) Run one of the installation scripts from the folder of the unpacked firmware
5) Immediately upon startup, allow on the phone screen the "USB debugging" permission for your computer, preferably within the checkbox "always trust this device"
6) Wait until the installation process finishes (15-20 mins), calmly referring to the fact that the phone itself will reboot into FASTBOOT mode, and also please ignore the Sparse format error message (it's normal)
7) The phone itself will reboot into a new OS ... the first launch will be very long
Please feel free to ask anything here about the installation process, cloud links etc.
But be ready that I'm not fast answering.
Any other questions including the comparison of EUI versions performance and functionality will be ignored by me.
We still have the device that is highly secured with unknown protection mechanism and that gets us unable to build any quality custom ROM. =|
thank you
I should have researched before buying the device kk was already "lost" trying to find a customized rom for him. this part of the text: "We still have the device that is highly secured with unknown protection mechanism and that gets us unable to build any quality custom ROM. =| " , clarified me a lot
I istalled it but it does not have google play store?
azizo07 said:
I istalled it but it does not have google play store?
Click to expand...
Click to collapse
ROM does not have Google applications. You need install it. I think this still working in this version: https://forum.xda-developers.com/le-pro3/leeco-le-pro3-a1-model-x651-guides-development--and-mods/automated-installer-gapps-morelocale2-t3752576
Ok installed the 30s mod version from https. ://4pda.ru/forum/index.php?showtopic=895159&st= 2020#entry77308634
and it includes gapps.
You can install another launcher to get rid of ads.
There is no root for this rom, right?
azizo07 said:
Ok installed the 30s mod version from https. ://4pda.ru/forum/index.php?showtopic=895159&st= 2020#entry77308634
and it includes gapps.
You can install another launcher to get rid of ads.
There is no root for this rom, right?
Click to expand...
Click to collapse
030S mod is based on APKs of 030S with few modifications... but it also runs the old Boot from version 027S... so it may have some unexpected behavior...
yes, all of these ROMs have no root... but with mods based on Boot of 027S version you can use a temporary root (one time booting into TWRP) for further system modifications and then back to boot with native stock kernel and modified system will run good (expect the problems with apps you may cause by modifications)
hi, how i can install this ROM if I use a non official Rom? I mean, I recived this phone yesterday with a 028s (stable) that is non official, and I want to install this official ROM.
Help please
My cell phone has brick
You have some rom to fix it?
Does the NFC work on this rom? I had 028s before but the NFC was disabled.
Hi im install rom eui 6.0.030s "https://4pda.ru/forum/index.php?showtopic=895159&st=2020#entry77308634"]https://4pda.ru/forum/index.php?showtopic=895159&st=2020#entry77308634 But me phone have in antutu 50000 . Ealier was 100000. What is wrong i see Stock-thermal.zip but i cant dowload . plise help
can't see inside the package "4) Run one of the installation scripts from the folder of the unpacked firmware"
or can i use rename the package to update.zip and run on the system update?
cyzarine said:
can't see inside the package "4) Run one of the installation scripts from the folder of the unpacked firmware"
or can i use rename the package to update.zip and run on the system update?
Click to expand...
Click to collapse
What you can't see? The scripts?
You need to look at the contains of unpacked ROM zip that have suffix "FASTBOOT" in filename. There must be files with names like "x7_fastboot_tool.bat" and "x7_fastboot_tool_noUser.bat" and also same files with ".sh" extensions for Linux.
For installation to start you need to run one of this scripts. To run from CLI (CMD), not by double-clicking on it.
what's the score in antutu in new rom ? I have 50000....
dilnix,
I've downloaded the FULL_X7_X7-CN-FN-KGXCNFN6003009091S-6.0.030S.zip which don,t have the fastboot tools.
Do you have instructions to install this?
Big thank you!
cyzarine said:
dilnix,
I've downloaded the FULL_X7_X7-CN-FN-KGXCNFN6003009091S-6.0.030S.zip which don,t have the fastboot tools.
Do you have instructions to install this?
Big thank you!
Click to expand...
Click to collapse
This is an OTA package. But it's buggy, my try to make a direct update from 028S to this 030S with OTA way was failed, and I heart many reviews about same behavior.
So I think the best way to update is to use Fastboot with scripts and executable provided in my package that contains "_FASTBOOT" suffix in filename.
From there you can use script "x7_fastboot_tool_noUser.bat" (or .sh option in Linux) to make update to 030S (only from clean stock 025S, 026S or 028S, not from fake 027S or any mod) without clearing of Userdata Storage.
Or you can use script "x7_fastboot_tool.bat" (or .sh option in Linux) to make a new installation of 030S with clearing of Userdata Storage (from any other previous ROM).
If you can't download by my links provided in topic, please write here and I'll try to solve this.
grzegorzkuc said:
what's the score in antutu in new rom ? I have 50000....
Click to expand...
Click to collapse
My x650 shows 87000 in antutu on 030S. I can't know what is reason you having less.
Currently my Le pro 3 ai is on non official 5.9.27s I have to downgrade it to 5.9.25s.what should I do. Further I want to update my device to eui 6.0.30s. Any help is highly appreciated .
I think that is 027s custom rom better than this 028s. I recommend you to not change anything.
Sent from my LEX657 using Tapatalk
AmanS99 said:
Currently my Le pro 3 ai is on non official 5.9.27s I have to downgrade it to 5.9.25s.what should I do. Further I want to update my device to eui 6.0.30s. Any help is highly appreciated .
Click to expand...
Click to collapse
As an example of this way how to move into stock 028S with flashing first 025S and then just update to 028S (or 030S if you want) I prepared a video half of year ago. HERE
I understand that not all processes there are perfect... for example I used ADB to push ROM instead of MTP that is much faster =)
But if you have experience and you sure in other option of processing the steps explained in this video - enjoy and good luck.
Hope it will help somebody.
P.S.: Now I have some trouble with focus (can't focus larger then 120 cm) in stock Camera on EUI 030S and have a plan to get 028S back just for testing of Camera and focus processing.
P.S.2.: If you will have desire to get back into custom 027S you had earlier, you always can make it. It's available on both forums (XDA & 4pda). But you need to know, that changing of using between clean stock and custom ROMs is always requires you to clean a Userspace too.
Thanks for your reply . But I want to ask is there is risk of getting brick if anything goes wrong.
Can we continue to discuss topics about the new - big thx to devs, btw! - official 17.1 version in this thread, pls?
(I know the differences to the unofficial version(s) might be minimal - or even null? - however I think it's always of value to be as clear, sharp and crisp avoiding ambiguities, esp. for folks who are not too familiar with the different contexts)
BTW: just for the record my (dirty) upgrade path from lineage-16.0-20201003-nightly-hlte-signed.zip version to lineage-17.1-20201010-nightly-hlte-signed.zip was as follows:
DLed / copied off my NAS the files of lineage-17.1-20201010-nightly-hlte-signed.zip, open_gapps-arm-10.0-nano-20201010.zip and Magisk v20.4 to external SD)
Let the system DL and install recent pending updates
Rebooted into Recovery (twrp-3.4.0-1-hlte)
Created a nandroid backup of Boot, System, Data and EFS partition to internal SD (and copied those to the external SD, plus a further copy to my NAS)
Wiped Dalvik / ART Cache, System and Cache partition
Installed LOS and GApps
(Dirty) Rebooted into System letting the system run a couple of minutes, checking for updates etc.
Rebooted into Recovery
Installed Magisk
Wiped Dalvik / ART Cache
Rebooted into System
(Enabled systemless host file in Magisk to support Adaway Adblocker app)
PS: This thread has been moved off the Development Folder by a Forum Moderator
Quick questions:
1. Does that AdAway work well?
2. Does automatic dark mode work for you? I have to turn it on manually. Maybe due to turned off GPS so it can't get my location and set sunrise and sunset times?
asassello said:
Quick questions:
1. Does that AdAway work well?
2. Does automatic dark mode work for you? I have to turn it on manually. Maybe due to turned off GPS so it can't get my location and set sunrise and sunset times?
Click to expand...
Click to collapse
1 : yes
2 : yes..update maybe your modem
re 1: yes2 (using it quite some time on various devices and it seems to do what I expect it should do, though some apps seem to bypass the 'normal' DNS resolution. OT: And I'm still haven't made up my mind yet if DoH or DoT are good or bad ...)
re 2: dark mode? What's that?
rayman95 said:
1 : yes
2 : yes..update maybe your modem
Click to expand...
Click to collapse
Are you sure NFC works? I mean paying in shops? I updated modem and now it's N9005XXUGPQB1. And paying still doesn't work. I've just tried.
odoll said:
re 2: dark mode? What's that?
Click to expand...
Click to collapse
Sorry. It's dark theme (I don't have English set as default language). [emoji846]
installation error
https://download.lineageos.org/hltetmo
Can somebody please confirm that paying through NFC works? If so - what's your modem and baseband?
Also I've installed GAPPS PICO maybe that's the case? Although on LOS 16 I also had Pico and it worked, but maybe I'm missing some app like Google search or something?
Been using Lineage OS 16 ever since it was officially released for HLTE. I gotta say, the development of that release has came a long way and by the time of writing this, I'd say it's the most stable and clean custom rom for the Note 3 out there.
I did try the new release the second I received a notification for an update. How did it go? Well let's just say I'm glad I created a full system backup before wiping LOS 16. This new release is still very buggy, unpolished and missing a lot of features. Nothing that will render your phone unusable, but compared to 16, it doesn't stand a chance, which is understandable.
I do appreciate all of the time that the devs are still willing to put into the platform. However I'd recommend users that are looking for a rock stable experience to stick with Lineage OS 16 for the time. You're not missing out on a lot.
loudseries said:
This new release is still very buggy, unpolished and missing a lot of features. Nothing that will render your phone unusable, but compared to 16, it doesn't stand a chance, which is understandable.
Click to expand...
Click to collapse
I think your statement will get more weight, when it will be supported with some facts:
It'd be helpful if you would underpin your statement with some of your findings about e.g. which bugs you found and which features you are missing!? thx
odoll said:
I think your statement will get more weight, when it will be supported with some facts:
It'd be helpful if you would underpin your statement with some of your findings about e.g. which bugs you found and which features you are missing!? thx
Click to expand...
Click to collapse
I have to agree with you, because except my 2 issues (with NFC payments and night mode that doesn't switch automatically) I actually don't have any other problems.
Ver. 17 seems faster and snappier than 16.
Also on 16 sometimes sharing from ie. Firefox to WhatsApp caused the later one not loading (just black screen).
So for me only that NFC seems to be a real issue. Other than that I'd advice anyone trying 17.
made a clean flash with nanodroid and last lolz..the rom is mostly usable ..
got sometimes, not often some little freezes and stock music stop..otherwise it's reliable
both options, stay on 16.0 for stability or move to 17.1 are possible...
rayman95 said:
made a clean flash with nanodroid and last lolz..the rom is mostly usable ..
got sometimes, not often some little freezes and stock music stop..otherwise it's reliable
both options, stay on 16.0 for stability or move to 17.1 are possible...
Click to expand...
Click to collapse
for me the only difference is the size of the home screen changed (changed trebuchet to a larger grid before), otherwise i would not even have noticed it is not 16 anymore, rock stable even after a dirty flash
rayman95 said:
made a clean flash with nanodroid and last lolz..the rom is mostly usable ..
got sometimes, not often some little freezes and stock music stop..otherwise it's reliable
both options, stay on 16.0 for stability or move to 17.1 are possible...
Click to expand...
Click to collapse
Yea,i have the same issue . Sometimes works okey and sometimes phone is just unresponsive, freezing. Youtube vanced most of the time stuck while screen is turned off ect.
Some really weird stuff there but I'm sure all will be okej later on.
Btw what BL and CP u using?
Scorpionea said:
Yea,i have the same issue . Sometimes works okey and sometimes phone is just unresponsive, freezing. Youtube vanced most of the time stuck while screen is turned off ect. Some really weird stuff there but I'm sure all will be okej later on.
Btw what BL and CP u using?
Click to expand...
Click to collapse
I'm on PQB1 nordic modem and BRL1 bootloader.
rayman95 said:
I'm on PQB1 nordic modem and BRL1 bootloader.
Click to expand...
Click to collapse
Have the same as you . I thought it could be bootloader issue but guess not.
Thx
Dirt update and no more freezes issues...I don't know if it's a the new rom or the dirt update... Anyway, but now got dl issues..browser fc when I want to dl a file...
odoll said:
Can we continue to discuss topics about the new - big thx to devs, btw! - official 17.1 version in this thread, pls?
(I know the differences to the unofficial version(s) might be minimal - or even null? - however I think it's always of value to be as clear, sharp and crisp avoiding ambiguities, esp. for folks who are not too familiar with the different contexts)
BTW: just for the record my (dirty) upgrade path from lineage-16.0-20201003-nightly-hlte-signed.zip version to lineage-17.1-20201010-nightly-hlte-signed.zip was as follows:
DLed / copied off my NAS the files of lineage-17.1-20201010-nightly-hlte-signed.zip, open_gapps-arm-10.0-nano-20201010.zip and Magisk v20.4 to external SD)
Let the system DL and install recent pending updates
Rebooted into Recovery (twrp-3.4.0-1-hlte)
Created a nandroid backup of Boot, System, Data and EFS partition to internal SD (and copied those to the external SD, plus a further copy to my NAS)
Wiped Dalvik / ART Cache, System and Cache partition
Installed LOS and GApps
(Dirty) Rebooted into System letting the system run a couple of minutes, checking for updates etc.
Rebooted into Recovery
Installed Magisk
Wiped Dalvik / ART Cache
Rebooted into System
(Enabled systemless host file in Magisk to support Adaway Adblocker app)
PS: This thread has been moved off the Development Folder by a Forum Moderator
Click to expand...
Click to collapse
Hello. I have the latest version of LineageOS 16 installed and TWRP (3.3.1.0). I ask you if, after transferring the ROM file to the phone, it is possible to use TWRP to upgrade to 17.1 (by installing the zip file) or if I have to use ADB shell (as it says on the LineageOS official site).
Sorry I'm not an expert and some steps are not clear to me
Thank you
PS
Why you wrote "dirty"
(Dirty) Rebooted into System letting the system run a couple of minutes, checking for updates etc.
Hi Apten
i) think your Qs won't need a full quote
ii) drity flashing
iii) sure you can DL the ROM (and TWRP) to your (internal RAM) of your phone and upgrade or clean install from recovery (twrp)
rayman95 said:
Dirt update and no more freezes issues...I don't know if it's a the new rom or the dirt update... Anyway, but now got dl issues..browser fc when I want to dl a file...
Click to expand...
Click to collapse
I've just dirty updated from 1010 to 1017 build . Will see how it goes later on.
Just tested with chrome downloading lineage and no issue with Fc
Model - ROG Phone 5 Ultimate (Possibly ROG Phone 5 as well see here )
2021/11/05
Version Name - WW-18.0840.2109.188
Release Date - 2021/11/05
OTA Download Link - Download
RAW Download Link - PENDING
Stock Boot Image - Download
Magisk Patched Boot Image - Download
Changelog
ROG Phone 5 (ZS673KS) software Image：WW-18.0840.2109.188 for WW/JP/EU/RU only*
This firmware is only for ROG Phone 5 WW/JP/EU version use and not applicable to ROG Phone 5S/5S Pro series models.
Note: Please be patience it's normal when downloading status bar stop a while with large update package.
For WW SKU Improved Item:
1. Optimize the charging experience function
Steps of Update:
1. Check software version of your device**
2. Download device software and Update SOP (From “Manual” Item)
3. Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW.
4. Software update cannot transfer the software SKU and downgrade the software version.
5. Wrong SKU may cause update failure, please update the same SKU version only.
**How to know the device model?
Path: Settings->About-> Model number
Example: ASUS PadFone2
**How to know the device software version?
Path: Settings->About-> software information->Build number
Example: CHT_PadFone2-user-10.4.17.15-UpdateLauncher
**System upgrade may cause part of data missing, please back up your important data before system upgrading.
Click to expand...
Click to collapse
Spoiler
2021/08/24
Version Name - WW-18.0840.2107.151
Release Date - 2021/08/24
OTA Download Link - Download
RAW Download Link - Download
Stock Boot Image - Download
Magisk Patched Boot Image - Download
Changelog
ROG Phone 5 (ZS673KS) software Image：WW-18.0840.2107.151 for WW/JP/EU only*
Note: Please be patience it's normal when downloading status bar stop a while with large update package.
For WW SKU Improved Item:
1.Updated Android security patch to 2021-07
2.Fixed issue with sending MMS messages on Optus Australia
3.Fixed an issue where some videos played through apps would get stuck and without response.
4.Fixed issue where AirTriggers would become insensitive after opening Taobao APP
For JP SKU Improved Item:
1.Updated Android security patch to 2021-07
2.Fixed an issue where some videos played through apps would get stuck and without response.
3.Fixed issue where AirTriggers would become insensitive after opening Taobao APP
Steps of Update:
1. Check software version of your device**
2. Download device software and Update SOP (From “Manual” Item)
3. Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW.
4. Software update cannot transfer the software SKU and downgrade the software version.
5. Wrong SKU may cause update failure, please update the same SKU version only.
**How to know the device model?
Path: Settings->About-> Model number
Example: ASUS PadFone2
**How to know the device software version?
Path: Settings->About-> software information->Build number
Example: CHT_PadFone2-user-10.4.17.15-UpdateLauncher
**System upgrade may cause part of data missing, please back up your important data before system upgrading.
Click to expand...
Click to collapse
*********************************************************************************************************************
2021/07/22
Version Name - WW18.0840.2106.86
Release Date - 2021/07/22
OTA Download Link - Download
RAW Download Link - Waiting
Stock Boot Image - Download
Magisk Patched Boot Image - Download
Changelog
ROG Phone 5 (ZS673KS) software Image：WW-18.0840.2106.86 for WW/JP/EU only*
Note: Please be patience it's normal when downloading status bar stop a while with large update package.
Note: Please be patience it's normal when downloading status bar stop a while with large update package.
Improved Item:
1. Updated Android security patch to 2021-06
2. Fixed an issue where the game would crash when using multiple windows to open the settings and change the system navigation
3. Fixed the problem of broken sound when using screen recording
4. Fixed the problem of low notification sound when using Bluetooth headsets in standby mode
5. Fixed an issue where blocking notifications in the game could not block Facebook messenger notifications
6. Fixed the problem of reduced call volume
7. Fixed the problem of using a microphone to record the voice of a team in the game, and the problem of not being able to record your own voice
8. Fixed the problem that the 5G network cannot be detected when connected to the GT-AX11000 router
9. Fixed a serious delay in the screen when entering the game with Geforce Now
10. Optimize touch experience
11. Fix sound effect for speaker playback.
Steps of Update:
1. Check software version of your device**
2. Download device software and Update SOP (From “Manual” Item)
3. Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW.
4. Software update cannot transfer the software SKU and downgrade the software version.
5. Wrong SKU may cause update failure, please update the same SKU version only.
**How to know the device model?
Path: Settings->About-> Model number
Example: ASUS PadFone2
**How to know the device software version?
Path: Settings->About-> software information->Build number
Example: CHT_PadFone2-user-10.4.17.15-UpdateLauncher
**System upgrade may cause part of data missing, please back up your important data before system upgrading.
Click to expand...
Click to collapse
I would assume it is all the same, since the firmware you posted is
https://dlcdnets.asus.com/pub/ASUS/...S_I005_1-ASUS-18.0840.2106.86-1.1.92-user.zip
and the firmware from https://forum.xda-developers.com/t/new-firmwair-version-ww18-0840-2106-86.4309457/ is also
https://dlcdnets.asus.com/pub/ASUS/...S_I005_1-ASUS-18.0840.2106.86-1.1.92-user.zip
twistedumbrella said:
I would assume it is all the same, since the firmware you posted is
https://dlcdnets.asus.com/pub/ASUS/...S_I005_1-ASUS-18.0840.2106.86-1.1.92-user.zip
and the firmware from https://forum.xda-developers.com/t/new-firmwair-version-ww18-0840-2106-86.4309457/ is also
https://dlcdnets.asus.com/pub/ASUS/...S_I005_1-ASUS-18.0840.2106.86-1.1.92-user.zip
Click to expand...
Click to collapse
It is the same, I'm looking for the RAW File.
JazonX said:
It is the same, I'm looking for the RAW File.
Click to expand...
Click to collapse
Wouldn't it also be the same then?
twistedumbrella said:
Wouldn't it also be the same then?
Click to expand...
Click to collapse
Not really, Once you install an OTA, The Active boot partition switches to the opposite one to boot the new firmware.
If you have Root + TWRP, I find this messy because then you have to manually patch the boot images, and it is usually after a few bootloops and softbricks. There is an option in Magisk, Install to inactive slot. That doesn't work always, at least during my ROG II and ROG III days.
Good thing about the RAW files, They do a clean install without wiping, and you can set it up easily afterwards with the usual magisk and patch steps without losing userdata. For a firmware upgrade I always prefer Raw files.
I actually found a RAW file from a usual source I used to get these, But surprisingly this version is not available in the ASUS site. Its about 3 digits below the current one.
WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw | Download
Well... I can at least take some of your worries... OTAs won't be a thing after you unlocked your bootloader. You need to manually install them via magisk again. So there is no chance these automatic updates will break your phone.
Furthermore you don't have to worry about root + TWRP as well because there is no twrp for this phone and I doubt there will be one in the next time.
But applying updates and keeping root access without loosing your user data should be no problem. Magisk has special options for this and many people here update that way without bootloops and soft bricks.
JazonX said:
Not really, Once you install an OTA, The Active boot partition switches to the opposite one to boot the new firmware.
If you have Root + TWRP, I find this messy because then you have to manually patch the boot images, and it is usually after a few bootloops and softbricks. There is an option in Magisk, Install to inactive slot. That doesn't work always, at least during my ROG II and ROG III days.
Good thing about the RAW files, They do a clean install without wiping, and you can set it up easily afterwards with the usual magisk and patch steps without losing userdata. For a firmware upgrade I always prefer Raw files.
I actually found a RAW file from a usual source I used to get these, But surprisingly this version is not available in the ASUS site. Its about 3 digits below the current one.
WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw | Download
Click to expand...
Click to collapse
I think you completely misunderstood my comment. I was saying that if the firmware for both models is the same, it is likely the raw files for both are the same (but still separate from the firmware).
In addition to what was already pointed out above, you have things backwards. The RAW firmware is intended to be a low-level rebuild. The regular firmware is not an incremental (which I assume is what you were thinking) and comes will a full firmware image every time.
Edit: The version from this thread now includes a separate flash_raw and flash_raw_and_wipe command.
twistedumbrella said:
I think you completely misunderstood my comment, but I am sure someone new will appreciate the explanation (with a few corrections).
In addition to what was already pointed out above, you have things backwards. The RAW firmware is intended to wipe your data, while the regular firmware upgrades are not. The regular firmware is not an incremental (which I assume is what you were thinking) and comes will a full firmware image every time.
Click to expand...
Click to collapse
RAW never wipes data. I've done it for almost 2 years in my ROG II.
That's how I usually update my firmware.
Unless something is changed in ROG 5 ... If yes, Then I'm wrong.
I'm yet to test all these anyway, Since unit is still on the way.
JazonX said:
RAW never wipes data. I've done it for almost 2 years in my ROG II.
That's how I usually update my firmware.
Unless something is changed in ROG 5 ... If yes, Then I'm wrong.
I'm yet to test all these anyway, Since unit is still on the way.
Click to expand...
Click to collapse
Then apparently it has changed. I didn't have a ROG II, but I have the ROG 5 in hand. I couldn't tell you what has changed, though.
You can, however, opt out of the erase. Not sure if you have to convert the raw to images first, though. I think that would be the method you used in previous phones. It was a flash_all script (or command, if you were on Windows).
Edit: The version from this thread now includes a separate flash_raw and flash_raw_and_wipe command.
twistedumbrella said:
Then apparently it has changed. I didn't have a ROG II, but I actually have my ROG 5. Couldn't tell you what else has changed.
You can, however, opt out of the erase. Not sure if you have to convert the raw to images first, though. I think that would be the method you used in previous phones. It was a flash_all script (or command, if you were on Windows).
Click to expand...
Click to collapse
Ohh .. In that case I was super wrong, and apologies over my misinformation.
Yeah, Actually ROG II Raw files had a Flash-all file which installs the full firmware, and reboots.
I even had a source (A Persian website) to get these when the OTA releases.
I was on windows, and usually after a RAW installation, the cache (Art or Dalvik, Whatever it is we have now) gets cleared and Phone becomes a little bit snappier than it was before.
Guess we gotta stick to ASUS OTA files from the support site then.
Thanks a lot ! : )
These updates come with a flash_raw script that looks more or less harmless. There is no visible wipe command included, but the phone did appear wiped after installing.
The flash_all, on the other hand, has a rather obvious section to opt in or out of an erase that opting out on Linux and Windows. I think the wipe isn't as much a wipe as it overwrites the partition.
I typically install my firmware with fastboot using a slightly modified version of the flash_all script and an unpacked payload. Somehow I broke the installer, which gives me a chance to test the raw again.
Edit: The version from this thread now includes a separate flash_raw and flash_raw_and_wipe command.
JazonX said:
The cache (Art or Dalvik, Whatever it is we have now) gets cleared and Phone becomes a little bit snappier than it was before
Click to expand...
Click to collapse
I thought that rumor died long ago. Usually unless things go wrong clearing the cache should not make your phone faster.
It's like closing all apps/recents after each usage in order to boost the performance.
Anubarak16 said:
I thought that rumor died long ago. Usually unless things go wrong clearing the cache should not make your phone faster.
It's like closing all apps/recents after each usage in order to boost the performance.
Click to expand...
Click to collapse
I think Art broke that. If I remember the explanation, the idea was to create something like the old odex layout that was less sloppy. The code that used to be cached is now broken out into a physical file alongside the application. It's also how apps like *that one everyone remembers for IAP* are able to modify code without breaking signatures.
Successfully rooted using the same commands from here and the root images in the OP.
JazonX said:
Successfully rooted using the same commands from here and the root images in the OP.
Click to expand...
Click to collapse
Any word on the raw firmware? What about the existing boot images?
twistedumbrella said:
Any word on the raw firmware? What about the existing boot images?
Click to expand...
Click to collapse
The RAW firmware I shared earlier - I didn't test it since it's a downgrade.
If the current firmware gets a RAW release, I will definitely test it.
Currently I patched only Boot Slot_A and booted to system using A. (using the same patched image I updated in OP)
Since there is no TWRP, I dont want to manually patch A and B both.
Magisk is stable, Didnt pass SafetyNet - So might need a module for that.
JazonX said:
The RAW firmware I shared earlier - I didn't test it since it's a downgrade.
If the current firmware gets a RAW release, I will definitely test it.
Currently I patched only Boot Slot_A and booted to system using A. (using the same patched image I updated in OP)
Since there is no TWRP, I dont want to manually patch A and B both.
Magisk is stable, Didnt pass SafetyNet - So might need a module for that.
Click to expand...
Click to collapse
You do need a module. It's posted in one of the root threads. I guess we won't know if you need different boot images until someone tests, but at least you seem to be comfortable patching your own.
twistedumbrella said:
You do need a module. It's posted in one of the root threads. I guess we won't know if you need different boot images until someone tests, but at least you seem to be comfortable patching your own.
Click to expand...
Click to collapse
Patching own images are always reliable...
SafetyNet Passed with this fix !
JazonX said:
Patching own images are always reliable...
SafetyNet Passed with this fix !
Click to expand...
Click to collapse
Glad you found it. Good luck.
I flashed the raw firmware. It was a downgrade and my device was already set up and in use, but it included the scripts and commands to install without a wipe (finally). Moving the latest firmware to the sdcard allowed me to update almost immediately after finishing the flash.
I would assume it works on the Ultimate, since everything else has been identical and the date on that package is the same as the software image.
New update !
Honeywell EDA50 Handheld Computer / barcode scanner
Currently on Android 7.1 from Android 4.4.4 (assumption)
There are 2 versions of this, with and without Google Mobile Services.
I need to free up a lot of RAM to avoid app closures when using the
scanner to interact with very java-heavy pages. To further this effort,
I have already 'disabled' almost everything that I can incl the OEM
chrome in favor of Chromium. Its not enough. This is a 2G/16G device.
The bootloader is supposedly unlockable, but HW support has no
idea how to do it. Original ROM for either 4.4 or 7.1 of either
flavor are not available per HW engineering. Device is End Of Life.
Thoughts / Suggestions?
Why don't you flash the non GMS version instead of disabled the gms app?
siheyo said:
Why don't you flash the non GMS version instead of disabled the gms app?
Click to expand...
Click to collapse
Non-GMS is not available as an 'intact' ROM, only ota updates.
Non-GMS updates will not install, likely version conflict. Though I could probably start with initial Android 4.x and progress from there... I would need root in order to do so... And the original ROM image.
You could downgrade the eda50 to android 4.x first. Use the update from sdcard function to do it from stock recovery. After it done, just go back to recovery and upgrade itu to android 7.1 non-gms version. It doesn't beed root or bootloader unlocked. Just try using the stock recovery and sdcard.
In order to downgrade, I need an intact 'whole' rom image. Trying to revert to Android 4.x using an OTA merely results in factory wipe and clean slate start with Android 7.1, gms intact.
Think that I start to look into how to unlock bootloader. If can root, in particular root shell, then perhaps can Frankenstein a version that works but no gms. This just became a possibility after an engineer (at Honeywell) let it slip that nothing special is needed to unlock.
Incidentally, engineer states that if I happen to find a new-in-box version, that app licensing is intact (no charge) for Android 4 platform. It was also mentioned there is a backup rom image stored in the "IPSW" partition but is removed when jump to Android 7.
Now to see if I can find a NIB Android 4 EDA50...