UPDATE 6: I have added boot images for Android 10, December 5 2020 Security Update. (No November and October atm because I have updated my Nokia 3.2 to December Security Patch without backing up.)
UPDATE 6: I have added boot images for Android 10, September 5 2020 Security Update.
UPDATE 5: I have added boot images for Android 10, August 5 2020 Security Update.
UPDATE 4: I have added boot images for Android 10, July 5 2020 Security Update.
UPDATE 3: I have added boot images for Android 10, June 5 2020 Maintenance Release.
UPDATE 2: I have added boot images for Android 10, June 5 2020 Security Update.
UPDATE: I have added boot images for Android 10, March 5 2020 and April 5 2020 Security Update.
Starting from Android 10, May 5 2020 Security Update. I'll be uploading dumped boot images from my Nokia 3.2. I might as well upload other partitions like system and vendor images, but that would be pretty impossible since I have a very slow internet connection. (System and Vendor images takes a lot of space and uploading large file sizes are slower on slow internet lol.)
AGAIN, THESE BOOT IMAGES ARE PULLED FROM THE GLOBAL VARIANT! DO NOT FLASH ON A EUROPE VARIANT OR ELSE YOU MIGHT GET A BOOTLOOP!
Android 10, December 5, 2020
You can get boot images for this version here!
Android 10, September 5, 2020
You can get boot images for this version here!
Android 10, August 5, 2020
You can get boot images for this version here!
Android 10, July 5 2020 (Security Update):
You can get boot images for this version here!
Android 10, June 5 2020 (Security Update and Maintenance Release):
You can get boot images for these versions here!
Android 10, May 5 2020:
You can get boot images for this version here!
Android 10, April 5 2020:
You can get boot images for this version here!
Android 10, March 5 2020:
You can get boot images for this version here!
More soon...
If you are rooted with Magisk and wants to install OTA updates just follow this thread:
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863
(Ignore the TWRP one as Nokia 3.2 can't be flashed with a custom recovery like TWRP)
EDIT:
There are currently no Europe (00EE) boot images available.
what are this? ready to flasg without magisk?
KiatoKid said:
what are this? ready to flasg without magisk?
Click to expand...
Click to collapse
These are stock boot images and patched boot images (patched using Magisk) that can temporarily boot your Nokia 3.2 into rooted state without having to modify the stock boot image itself.
how did you perform the boot.img extraction ?
stizzie said:
how did you perform the boot.img extraction ?
Click to expand...
Click to collapse
I've placed the link for the Guide for that.
But this one is for Mi A2 Lite, but it's pretty much the same as well for Nokia 3.2.
Here it is:
yashinodon said:
If you are rooted with Magisk and wants to install OTA updates just follow this thread:
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863
(Ignore the TWRP one as Nokia 3.2 can't be flashed with a custom recovery like TWRP)
EDIT:
There are currently no Europe (00EE) boot images available.
Click to expand...
Click to collapse
yashinodon said:
UPDATE 6: I have added boot images for Android 10, December 5 2020 Security Update. (No November and October atm because I have updated my Nokia 3.2 to December Security Patch without backing up.)
UPDATE 6: I have added boot images for Android 10, September 5 2020 Security Update.
UPDATE 5: I have added boot images for Android 10, August 5 2020 Security Update.
UPDATE 4: I have added boot images for Android 10, July 5 2020 Security Update.
UPDATE 3: I have added boot images for Android 10, June 5 2020 Maintenance Release.
UPDATE 2: I have added boot images for Android 10, June 5 2020 Security Update.
UPDATE: I have added boot images for Android 10, March 5 2020 and April 5 2020 Security Update.
Starting from Android 10, May 5 2020 Security Update. I'll be uploading dumped boot images from my Nokia 3.2. I might as well upload other partitions like system and vendor images, but that would be pretty impossible since I have a very slow internet connection. (System and Vendor images takes a lot of space and uploading large file sizes are slower on slow internet lol.)
AGAIN, THESE BOOT IMAGES ARE PULLED FROM THE GLOBAL VARIANT! DO NOT FLASH ON A EUROPE VARIANT OR ELSE YOU MIGHT GET A BOOTLOOP!
Android 10, December 5, 2020
You can get boot images for this version here!
Android 10, September 5, 2020
You can get boot images for this version here!
Android 10, August 5, 2020
You can get boot images for this version here!
Android 10, July 5 2020 (Security Update):
You can get boot images for this version here!
Android 10, June 5 2020 (Security Update and Maintenance Release):
You can get boot images for these versions here!
Android 10, May 5 2020:
You can get boot images for this version here!
Android 10, April 5 2020:
You can get boot images for this version here!
Android 10, March 5 2020:
You can get boot images for this version here!
More soon...
If you are rooted with Magisk and wants to install OTA updates just follow this thread:
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863
(Ignore the TWRP one as Nokia 3.2 can't be flashed with a custom recovery like TWRP)
EDIT:
There are currently no Europe (00EE) boot images available.
Click to expand...
Click to collapse
Hello @yashinodon, in the process of rooting, I unknowingly used the Android 10, December 5, 2020 Image on my Android 11 Nokia 3.2. The result is that my Wifi doesn't work.
Can you be so kind as to provide me with the newest boot.img file.
Thank you.
@antran22
Here you go https://drive.google.com/drive/folders/1q3gOus-7yPos3eYayeVkDT5rsvQdmOs4?usp=sharing
Extracted from the Android 11 ota
@
antran22 said:
Hello @yashinodon, in the process of rooting, I unknowingly used the Android 10, December 5, 2020 Image on my Android 11 Nokia 3.2. The result is that my Wifi doesn't work.
Can you be so kind as to provide me with the newest boot.img file.
Thank you.
Click to expand...
Click to collapse
Android 11 (TA-1164) (00WW_3_140) - Google Drive
drive.google.com
Hello,
I'm looking for the Nokia 3.2 Android 11 TA-1156 00EA_3_140 boot.img. Anyone who can provide that ?
I crashed my boot.img and unfortunately I only have a backup from Dez. 2020. Now my WiFi is broken.
Qudyjac said:
Hello,
I'm looking for the Nokia 3.2 Android 11 TA-1156 00EA_3_140 boot.img. Anyone who can provide that ?
I crashed my boot.img and unfortunately I only have a backup from Dez. 2020. Now my WiFi is broken.
Click to expand...
Click to collapse
There's a telegram channel named Nokia OTA Repository. Head over there and download OTA for Nokia 3.2 Android 11 European Version and extract boot image from payload.bin file in zip.
Hello,
Will this work on my Nokia TA-1159 Android 11, security update 5 March 2021? It's the same build number though(00WW_3_140). I was wondering since it's a different model I just want to be on the safe side.
Thanks.
Android 11 (TA-1164) (00WW_3_140) - Google Drive
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
drive.google.com
okuhl3 said:
Hello,
Will this work on my Nokia TA-1159 Android 11, security update 5 March 2021? It's the same build number though(00WW_3_140). I was wondering since it's a different model I just want to be on the safe side.
Thanks.
Android 11 (TA-1164) (00WW_3_140) - Google Drive
drive.google.com
Click to expand...
Click to collapse
I think it will, no harm anyway if you try the fastboot command without flash. sorry for the late reply.
hello, sorry in advance for my poor English, remember me please find boot.img for my phone, here is the build number and everything else thanks in advance : Nokia 3.2 ta 1156,android 11, build number 00WW_3_140
Links aren't working...
all boot link is dead
Hey, i'm looking for the boot.img for the build number 00WW_3_230_SP02 but i can't find it anywhere and not even on the telegram channel.
vewu101 said:
Hey, i'm looking for the boot.img for the build number 00WW_3_230_SP02 but i can't find it anywhere and not even on the telegram channel.
Click to expand...
Click to collapse
You can use my boot image uploads to get to stock android 9, from which you can do a software update to 11.
7heMeowMeowCat said:
You can use my boot image uploads to get to stock android 9, from which you can do a software update to 11.
Click to expand...
Click to collapse
Thanks for the reply, though i just downloaded the latest full ota update from the telegram group and used payload dumper to extract it then i flashed it and then patched the dumped boot.img instead
vewu101 said:
Thanks for the reply, though i just downloaded the latest full ota update from the telegram group and used payload dumper to extract it then i flashed it and then patched the dumped boot.img instead
Click to expand...
Click to collapse
Me too.
Can you send to me the file boot.img of 00WW_3_230_SP02 ??
I need it..
Thank!!
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.0.2 for Huawei Honor 4C CHM-U01 (All Regions) Android 5.1.1-6.0.0Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.1-0:
- support new CM 13.0 pattern encryption (sultanqasim)
- fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
- libtar updated to latest upstream and fixes (jcadduono)
- fixes for loading custom themes (_that)
- TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
- translation updates - added Italian, Czech and Polish and significant updates to Dutch
- progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
- fix input box text display (Dees_Troy)
- reboot option after zip install complete (bigbiff)
- other mostly invisible bug fixes and improvements
DEVICE SPECIFIC CHANGELOG:
Changelog for r1
- Fixed Reboot to System from TWRP Device powered off instead of rebooting
- Switched to Android 6.0 Kernel Fixed various bugs including touch screen not working after a small delay and black screen on boot
- Add backup and wipe of Cust Partition Cust partition should be backed up when downgrading from higher Android version to lower Android version through TWRP
Changelog for r2
- Fixed Mass USB Storage support Corrected file paths
- Bumped TWRP to 3.0.1-0 release
- Unified device identity parameters Prepping for AOSP releases. Avoiding model/device mismatch in TWRP before flashing
Changelog for r3
- Cleaned Ramdisk and now using Kernel compiled from sources
- Bumped TWRP to 3.0.2-0 release
Changelog for r4
- Fixed tzdata issues which lead to zone and posixr errors in recovery logs
TODO
- Fix /data/cust symlink and /data/custom.bin being destroyed after wiping /data/partition (This won't be implemented now as the recovery will be in near future used to flash custom ROMs)
- Add double tap to wake (will look into it, it's just a bonus)
SCREENSHOTS
DOWNLOADS
Unauthorized mirroring of any download file is strictly forbidden. No direct linking to the file below. Redirect all users to download TWRP from this page only.
I released TWRP 3.0.0-0 on other forums and what happened. They just decompiled my image, made changes to prop file and changed TWRP title to their names so as to claim as if it's built by them. Please respect the developer (I ain't one, just a starter) and if you want to build one, build one from the source.
TWRP 3.0.1-0 r4: https://www.androidfilehost.com/?fid=24521665358595470 | https://s.basketbuild.com/devs/mfbcool/huawei/honor4c/twrp_3
TWRP 3.0.1-0 r3: https://www.androidfilehost.com/?fid=24499762636007214 | https://s.basketbuild.com/devs/mfbcool/huawei/honor4c/twrp_3
TWRP 3.0.1-0 r2: https://www.androidfilehost.com/?fid=24459283995313249 | https://s.basketbuild.com/devs/mfbcool/huawei/honor4c/twrp_3
TWRP 3.0.0-0 r1: https://www.androidfilehost.com/?fid=24459283995309979 | https://s.basketbuild.com/devs/mfbcool/huawei/honor4c/twrp_3
XDA: DevDB Information
Unofficial TWRP 3.0.1-0 Recovery Project for Honor 4C CHM-U01
Contributors
@mfbcool , @XePeleato (for fixing Black Screen issue on newer Kirin devices)
TWRP Source Code: https://github.com/TeamWin
Recovery Device Source Code: https://github.com/muhammadfahadbaig/recovery_device_huawei_honor4c
Version Information
Status: Stable
Created 2016-04-01
Last Updated 2016-04-05
XDA:DevDB Information
TeamWin Recovery Project, Tool/Utility for the Huawei Honor 4C
Contributors
mfbcool
Source Code: https://github.com/muhammadfahadbaig/android_device_huawei_cherry
Version Information
Status: Stable
Current Stable Version: 3.0.2-0_r4
Stable Release Date: 2016-04-30
Created 2016-04-15
Last Updated 2016-05-09
Reserved
Cool!
Android小楼阁
来自搭载Android 2.3 GingerBread的华为Y220-T10
zhaozihanzzh said:
Cool!
Click to expand...
Click to collapse
Thanks! :victory:
Great work..... Am compiling Cyanogenmod soon... May be i needed this recovery for proper flashing cm12 or cm13 for proper binaries updates....
inshaalmirza said:
Great work..... Am compiling Cyanogenmod soon... May be i needed this recovery for proper flashing cm12 or cm13 for proper binaries updates....
Click to expand...
Click to collapse
CyanogenMod 12 or 13 for Honor 4C?That's great!
来自搭载Android 2.3 GingerBread的华为Y220-T10
great job.
Root
So how to root huawei honor 4c according to your method on android Marshmallow.
drag0nslayer said:
So how to root huawei honor 4c according to your method on android Marshmallow.
Click to expand...
Click to collapse
Root method doesn't changes. It remains the same. Follow @inshaalmirza guide on rooting Marshmallow.
@drag0nslayer follow this guide for rooting marshmallow
http://forum.xda-developers.com/general/general/root-honor-4c-root-recovery-bootloader-t3318406/
---------- Post added at 08:06 PM ---------- Previous post was at 08:05 PM ----------
Guyz i need some support and members....cant compile cyanogenmod alone... Or it gonna take months... Am a university level student so... Have patience till vacations!!
Hi mfbcool,
Which one should I take for honor 4c MM.
r1 or r2 ??
Why different versions?
*confused*
Thx4answer
br
Utze
utze said:
Hi mfbcool,
Which one should I take for honor 4c MM.
r1 or r2 ??
Why different versions?
*confused*
Thx4answer
br
Utze
Click to expand...
Click to collapse
Both are compatible with Marshmallow. r1 and r2 just indicates releases. r2 has more bugs fixed than r1. Hence go with r2.
mfbcool said:
Both are compatible with Marshmallow. r1 and r2 just indicates releases. r2 has more bugs fixed than r1. Hence go with r2.
Click to expand...
Click to collapse
works flawlessly and charm,,,thanks OP,,,,
Salam
Thanks for the recovery.
How to install it. it is image file?
and which rom u have on your device currently?
I am on kitkat, Should I go for Andriod M or stay here?
Last thing, My boatloadrer is unlocked and have TWRP recovery by Inshal. Any easy way to go to Marshmallow?
I have not changed my region yet.
Regards
Waqar90 said:
Salam
Thanks for the recovery.
How to install it. it is image file?
and which rom u have on your device currently?
I am on kitkat, Should I go for Andriod M or stay here?
Last thing, My boatloadrer is unlocked and have TWRP recovery by Inshal. Any easy way to go to Marshmallow?
I have not changed my region yet.
Regards
Click to expand...
Click to collapse
1. It is an image file and can be flashed through fastboot.
Code:
fastboot flash recovery recovery_name.img
2. It is not for Kitkat but if you need one, I can upload a test version for you
3. You can download Android Marshmallow Beta for Pakistan from here https://cloud.mail.ru/public/Gzqd/mJNsxm6AB . However, I haven't personally tested it.
mfbcool said:
1. It is an image file and can be flashed through fastboot.
Code:
fastboot flash recovery recovery_name.img
2. It is not for Kitkat but if you need one, I can upload a test version for you
3. You can download Android Marshmallow Beta for Pakistan from here https://cloud.mail.ru/public/Gzqd/mJNsxm6AB . However, I haven't personally tested it.
Click to expand...
Click to collapse
Which Rom are you using on your Honor 4c?
And If Andriod M, how did you update it?
What you suggest, Andriod M is better or Andriod L for honor 4C?
This beta version is developed by you or someone else?
and can it directly be flashed on Pakistan Lolipop Rom?
I am sorry, I am at Lolipop, not kitkat.
Waqar90 said:
Which Rom are you using on your Honor 4c?
And If Andriod M, how did you update it?
What you suggest, Andriod M is better or Andriod L for honor 4C?
This beta version is developed by you or someone else?
I am sorry, I am at Lolipop, not kitkat.
Click to expand...
Click to collapse
1. I am on Marshmallow. Changed my region to Malaysia when I was on Kitkat.
2. Android M is much better, stable and smoother than Android 5.1.1
3. I didn't developed the beta version. It's officially released by Huawei in a closed beta test.
Beta version is released by Huawei Pakistan?
Hi.
Looks und feels good.
For first time I was irritated, because the backup folder changed. So I can't find my backups with previous TWRP version.
And the backup duration needs the double time.
TODO
- Fix /data/cust symlink and /data/custom.bin being destroyed after wiping /data/partition
Should I not use "wiping data partition" for the moment?? Because it destroy sometimes or is it harmless??
br
Utze
utze said:
Hi.
Looks und feels good.
For first time I was irritated, because the backup folder changed. So I can't find my backups with previous TWRP version.
And the backup duration needs the double time.
TODO
- Fix /data/cust symlink and /data/custom.bin being destroyed after wiping /data/partition
Should I not use "wiping data partition" for the moment?? Because it destroy sometimes or is it harmless??
br
Utze
Click to expand...
Click to collapse
Yes, you shouldn't wipe Data partition and Factory Reset using TWRP. It destroys custom.bin and /cust/ symlink which holds vendor and firmware information. I have fixed it but the method isn't robust at the moment. As soon as I find a good alternate to the fix, I'll update TWRP.
[Guide/Tutorial] Fix Nexus 6P Bootloop of Death Boot Image Patch - Android 8.1 & More
A Fix for the Nexus 6P Bootloop of Death
Read Me
This requires you to have an unlocked bootloader. You can try different methods to get your phone to boot up and to enable OEM unlocking so you are able to unlock the bootloader and flash these 4core patched boot images.
Note
Not to deduct from the original work of @XCnathan32 or @xls654 in the original thread, but some members have asked me if I would like to create a new thread that is more regularly updated to make it easier for new and returning people to find the appropriate downloads.
You can visit the original thread here.
What needed to be fixed?
This explanation was taken from the original thread. Minor adjustments made.
The problem with most of the devices in a BLOD, is that a hardware failure related to the BIG cluster has occurred. This fix remedies the problem by disabling the BIG cores. Unfortunately, this does mean that you will take a performance hit.
The ramdisk has been modified to reflect use of the 4 cores that remain enabled. This should help performance.
What if my phone doesn't have an unlocked bootloader yet?
You'll want to try heating up your phone just underneath the camera, or leaving it on a low charge in order to get it to boot. Then quickly enable OEM unlocking in the developer options. Different ways of doing it may be explored in the original thread (see above).
Downloads and Instructions on Post #2
Tutorial on patching your own boot images on Post #3
Happy flashing!
Changelog
18/01/2018 - Updated new bootloader unlocking method via the use of `fastboot flashing unlock_critical`
9/01/2018 - Last added TheToto318 AFH Folder, MrMarques01 ElementalX and LOS 15.1 Unofficial (KevinIPS)
8/12/2017 - Initial Post
Downloads Section & Flashing Instructions
Downloads
No more patching each image! Thanks to @osm0sis 's AnyKernel2, has made available a flashable zip that can patch the current kernel and recovery! So there's no more need in patching each image manually. You can find the downloads at osm0sis's BasketBuild: https://basketbuild.com/devs/osm0sis/osmods
Take a look at the BLOD Workaround AK2 .zip as well as the patched versions of TWRP with FBE support.
Original post: https://forum.xda-developers.com/showpost.php?p=75203491&postcount=2142
If you can't access TWRP for whatever reason, I have patched more of the recent boot images. You can find them as the factory images get released: https://basketbuild.com/devs/squabbi/angler/4core-images
Instructions / Flashing Guide
To use these images in a TL;DR way of saying it, is to flash or boot a patched TWRP image and then flash the BLOD Workaround ZIP provided above last!
(Old) YouTube guide for the following instructions: https://youtu.be/czMMp2M6SEo
Now for the more detailed way.
Downloads
Latest SDK Platform Tools (adb & fastboot)
Nexus 6P Factory Images
Latest version of Magisk (for root)
BLOD Workaround AK2 flashable ZIP above.
Patched TWRP also above.
Procedure
You must have the latest version of the SDK Platform Tools or you may experience issues when flashing the images.
You must also need to have an unlocked bootloader.
If you need help installing drivers for your phone, follow this video and skip to the bootloader driver installation part:
https://youtu.be/NGy85rFFhLM?t=4m29s
You must have downloaded the Google USB drivers in the more info of the video!
Script for Reviving a BLOD Device using patched boot images (No TWRP)
Have a look at this great script made by @R3tro7, my quick look says it should do the job just fine!
https://forum.xda-developers.com/nexus-6p/general/tool-utility-script-to-fix-bootlooping-t3761085
For Reviving a BLOD Device
Unlock the bootloader.
Flash/boot patched TWRP.
Flash BLOD Workaround ZIP.
Reboot.
For Updating a BLOD Device
Extract the bootloader and radio images from the downloaded Factory Image
Open the 'images-angler-xxxxx.zip' inside the Factory Image
Extract the system and vendor images.
Reboot your phone into the bootloader.
First update the bootloader: fastboot flash bootloader *drag in extracted bootloader image*.
Reboot back into the bootloader: fastboot reboot-bootloader.
Flash the updated Radio image: fastboot flash radio *drag radio image here*.
Flash the updated boot image: fastboot flash boot *drag boot image here*.
Flash updated system image: fastboot flash system *drag extracted system image here*.
Flash the updated Vendor image: fastboot flash vendor *drag extracted vendor image here*.
Flash the updated PATCHED TWRP: fastboot flash recovery *drag patched TWRP image here*.
Reboot into recovery mode using the volume buttons to change the selection and press the power button to select.
Flash the Magisk zip in TWRP.
Flash the BLOD Workaround ZIP (remember to flash this ZIP last).
Reboot
...
Profit $$$
Previous images & TWRP /data decryption:
Patched Image Collections
All 4core patches can be found in my Android File Host folder.
@TheToto318 Collection - Android File Host Folder
This collection contains (may not be up to date):
Super XE 8.1.0_r2
TWRP 3.2.1-0
crDroidAndroid 8.1 20180103
LineageOS 15.1 - 20171229
Nitrogen-OS-O - 20171226
ElementalX N6P 6.01
crDroidAndroid 8.1 - 20180107
Nitrogen-OS - 20180106
Assorted Downloads
However, for ease of use, here are the links by build number:
Android Nougat Custom ROMs (7.0-7.1)
AOSiP 6.3 SLOBS - MD5: bac7c0ae9c84c9b9a730c2146c145e42
Android Oreo (8.0)
8.0.0 (OPR5.170623.007, Oct 2017) - MD5: ec04aac81a4967712d1c8e619ef400f5
8.0.0 (Unknown Build), build by @SkinlessMage006
Android Oreo (8.1)
8.1.0 (OPM1.171019.011, Dec 2017) - MD5: d1f34010ada50a34b446ab23d2cf850a
Source: GitHub
8.1.0 (Unknown Build), build by @SkinlessMage006
8.1.0 (OPM3.171019.013, Jan 2018) - MD5: 0d937293bfc53cf820c8ee43200d7676
May, June and July Builds of Android
Android Oreo 8.1 Custom ROMs
SuperXE - OPM2.171019.012(8.1.0_r2), thanks to @TheToto318
LineageOS 15.1 Unofficial (Unknown Build). Thanks to @kevinips
Nitrogen-OS-angler-20180106 4 Cores Fix. Thanks to @TheToto318
crDroidAndroid-8.1-20180103 4 Cores Fix. Thanks to @TheToto318
crDroidAndroid-8.1-20180107-angler-v4.0-BETA7 4 Cores Fix. Thanks to @TheToto318
Nitrogen-OS-O-angler-20171226 4 Cores Fix. Thanks to @TheToto318
lineage-15.1-20171229 4 Cores Fix. Thanks to @TheToto318
Android Oreo (8.1) Custom Kernels
Elemental-X 6.00 4-core- Thanks to: @MrMarques01
Instructions & Source: XDA Post #18
Elemental-X 6.01 4-core- Thanks to: @MrMarques01
Instructions & Source: XDA Post #114
TWRP
TWRP 3.2.0-0 - MD5: fdf4030d46a1be1af72777b02271fb21
TWRP 3.2.1-0 - MD5: 11c769711c02912abaa77cebf663e656
TWRP can't Decrypt my Data Partition!
If TWRP cannot decrypt your /data partition, you will need to format the userdata and ensure you do not use a boot image that forces encryption! All stock boot images do by default so be careful!
To format your userdata partition you can do it in either TWRP or the bootloader via fastboot.
Via fastboot: fastboot format userdata
The boot into TWRP, and it should load your internal storage.
OR
Boot into TWRP.
Select Wipe
Then Advanced Wipe
And check 'Internal Storage'
Swipe to wipe.
Reboot back into recovery.
TWRP should load your internal storage.
Patch your own Boot images to use 4 Cores
Here is a YouTube tutorial if you prefer that instead: https://youtu.be/PhObuifEp3Y
Introduction
Patching your own boot image is quite simple, all you need is essentially one tool, your boot image you want to patch and that's about it. The time it takes to patch one may take around 5-10 minutes and less as you get more comfortable with it.
If you feel this is still a little tricky, you can upload the boot image and send me a PM or reply to this thread and I, or someone will patch it for you.
Downloads
Android Image Kitchen by @osm0sis.
Your boot image that needs patching.
Steps
1. Extract the Android Image Kitchen zip that you downloaded. The extracted folder/files should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Drag the boot image you want to patch onto the unpackimg.bat, as for Linux or macOS AIK downloads, you will probably need to use the script via the Terminal in a way like this:
Code:
./unpackimg.sh '~/Downloads/boot.img'
Once the image is unpacked, 2 new folders will be created: split_img and ramdisk.
Now you'll need to edit 3 files in total. Details can be found on GitHub here: https://github.com/squabbi/4core-boot-angler-opm1.171019.011
Once you've done that, just run the repackimg.bat script again and you should see a new file created: image-new.img. This is your newly patched boot image.
Flash it via fastboot or TWRP and see if your phone boots.
Optionally run the cleanup.bat script to return your AIK into a clean state for your next boot image to patch. Be sure to copy the image-new.img to another directory or rename it, otherwise it will be cleaned up! (deleted)
Now that you've patched your boot image, the last step you need to do is share it! Post it as a reply here in this thread and I'll add it to the downloads post, just make sure to mention me using the '@' symbol. Or alternatively, send me a PM and I'll add it to the downloads post as well.
I was closely monitoring the original thread and couldn't keep up OP is not updated for the newer build (DP's and the latest official).
This is a great thread for those who are like me. I just hope first OP would not mind.
Thank you all for your tinkering!
EDIT: does any of your patched boot.img work with any Oreo custom rom? Just asking for when I get bored with stock.
kemistry01 said:
I was closely monitoring the original thread and couldn't keep up OP is not updated for the newer build (DP's and the latest official).
This is a great thread for those who are like me. I just hope first OP would not mind.
Thank you all for your tinkering!
EDIT: does any of your patched boot.img work with any Oreo custom rom? Just asking for when I get bored with stock.
Click to expand...
Click to collapse
I too hope they won't mind. :fingers-crossed:
I always thought that each ROM needed their own boot image, so I would assume that the stock Oreo one will not work on custom ROMs.
I'm more than happy to take requests for patching boot images, so just upload the boot image and send me a link. I'll patch it and then add it to post #2.
Wow man! Thanks for keeping the bootloop solution alive!
Do you know if there is any performance difference when using that modified ElementalX kernel from the other bootloop thread and using just the modded boot image?
Android 8.1 Working Great
Just flashed your 4-core version of TWRP 3.2 and the Android 8.1 boot image, Nexus 6P seems to have updated fine and is running reasonably smooth. Thanks for making a new post and releasing updated 4-core stuff!
Thank you for turning my paperweight 6P into a functional device!
How can I update to 8.1 and use 4 core mod? I'm running 8.0 currently.
Hi squabbi,
First of all thanks for your great work. I'm currently trying to patch the latest ElementalX kernel to used 4 cores only, but I'm a little bit confused as to which files need to be changed, since the github page from post 3 doesn't really detail that. Is it only the changes in fstab, init.angler.rc and boot.img-cmdline (the changes made in the commit history), or does anything else need to be changed?
Thanks for your help
EDIT: Nevermind, I think I figured it out. I think all that needs to be changed is to add maxcpus=4 to the last line of cmdline.sh for ElementalX to use 4 cores only (provided a modified stock boot.img was flashed before ElementalX kernel). I'll test it later and if it's working I'll post the modified ElementalX kernel for Android 8.1.
gb_14 said:
How can I update to 8.1 and use 4 core mod? I'm running 8.0 currently.
Click to expand...
Click to collapse
There are instructions in post 2.
MrMarques01 said:
Hi squabbi,
First of all thanks for your great work. I'm currently trying to patch the latest ElementalX kernel to used 4 cores only, but I'm a little bit confused as to which files need to be changed, since the github page from post 3 doesn't really detail that. Is it only the changes in fstab, init.angler.rc and boot.img-cmdline (the changes made in the commit history), or does anything else need to be changed?
Thanks for your help
EDIT: Nevermind, I think I figured it out. I think all that needs to be changed is to add maxcpus=4 to the last line of cmdline.sh for ElementalX to use 4 cores only (provided a modified stock boot.img was flashed before ElementalX kernel). I'll test it later and if it's working I'll post the modified ElementalX kernel for Android 8.1.
Click to expand...
Click to collapse
Yep, that should be it! Do let us know how to does.
And for the necessary file changes that are shown on GitHub, that's only for boot images.
I'm currently using 7.1 modded boot and my phone just shut down and it can not power on, no charging, no led light, just black screen. It's literally a brick right now, so, any guess?
It cant boot to TWRP
Hi
i have followed every step, but when i want to boot into recovery mode, it will go back to bootloop... goes to the yellowish warning then to Google logo screen with an unlocked lock and it reserts....
i really need your help...
thanks much in advance.
Anyone knows where to get a specific bootloader image ?
MrMarques01 said:
Hi squabbi,
First of all thanks for your great work. I'm currently trying to patch the latest ElementalX kernel to used 4 cores only, but I'm a little bit confused as to which files need to be changed, since the github page from post 3 doesn't really detail that. Is it only the changes in fstab, init.angler.rc and boot.img-cmdline (the changes made in the commit history), or does anything else need to be changed?
Thanks for your help
EDIT: Nevermind, I think I figured it out. I think all that needs to be changed is to add maxcpus=4 to the last line of cmdline.sh for ElementalX to use 4 cores only (provided a modified stock boot.img was flashed before ElementalX kernel). I'll test it later and if it's working I'll post the modified ElementalX kernel for Android 8.1.
Click to expand...
Click to collapse
Looking forward to a positive result!
squabbi said:
There are instructions in post 2.
Click to expand...
Click to collapse
I want to update, without losing any data.
Hi everybody.
As promised, here's the modified 4-core ElementalX 6.00 kernel. Please note that this kernel works with Android 8.1 only.
Download
https://goo.gl/qhhJx8
Instructions:
Flash the modified stock boot.img for Android 8.1 that can be found in post 2 using fastboot or TWRP (This is important)
Flash ElementalX-N6P-6.00-4cores.zip using TWRP
All credit goes to @flar2 for the kernel, @XCnathan32 and @xls654 for creating the 4core patch, and @squabbi for the modified 8.1 stock image.
@squabbi Feel free to add the zip to the OP.
MrMarques01 said:
Hi everybody.
As promised, here's the modified 4-core ElementalX 6.00 kernel. Please note that this kernel works with Android 8.1 only.
Download
https://goo.gl/qhhJx8
Instructions:
Flash the modified stock boot.img for Android 8.1 that can be found in post 2 using fastboot or TWRP (This is important)
Flash ElementalX-N6P-6.00-4cores.zip using TWRP
All credit goes to @flar2 for the kernel, @XCnathan32 and @xls654 for creating the 4core patch, and @squabbi for the modified 8.1 stock image.
@squabbi Feel free to add the zip to the OP.
Click to expand...
Click to collapse
Feedback: Working with Android 8.0. Thanks :good:
v0ne said:
Feedback: Working with Android 8.0. Thanks :good:
Click to expand...
Click to collapse
I hope you mean Android 8.1. Because with 8.0 it actually shouldn't work
Thread Closed Per OP Request
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
Current changelog: 09-04-2019
[note] Brightness Controls don't works on the Samsung Galaxy Tab 4 8.0.
[new] All Samsung Galaxy Tab 4 10.1 & 8.0 Have been updated TWRP-3.3.1-0.
[changed] OTG works .
[fixed] Sleep of death 100% fixed, Brightness Controls works 100% on The Samsung Galaxy Tab 4 10.1 .
Download
Samsung Galaxy Tab 4 10.1
matissewifi
https://drive.google.com/open?id=1Y-BDnnwORRR464OjUXlUpiVFB2bCYYfp
matisselte
https://drive.google.com/open?id=1cPuGADIa7Z6nGJaqOm0mnKe1Gu5yW1-S
matisse3g
https://drive.google.com/open?id=1mI5rgW01YFyXs3vhGCvjoYjwA0ldgqBf
Samsung Galaxy Tab 4 8.0
milletwifi
https://drive.google.com/open?id=1Tarv7ttSjngwwu-DO1mPZlR6_ovyDOAZ
milletlte
https://drive.google.com/open?id=1GWPe5D-SlHedvMcnKFBEhgS5brMBGvhs
millet3g
https://drive.google.com/open?id=1oU9j1k-5uAHBCeWJJ2OlxGLa0mQLyhwB
Great Work
I downloaded and flashed the TWRP for my SM-T330NU (milletwifi) and it works great. It allowed me to flash the new Lineage 16 build and despite the age and limited ability of this old tablet, I am now running Android Pie!
Excellent Work.
Milletlte works great. Flashed your Los16 Build also works Like a Charme.
Thank you.
brewer75 said:
I downloaded and flashed the TWRP for my SM-T330NU (milletwifi) and it works great. It allowed me to flash the new Lineage 16.1 build and despite the age and limited ability of this old tablet, I am now running Android Pie!
Click to expand...
Click to collapse
Can you tell me where you found a Lineage 16.1 build for SM-T330NU ? I can't find it anywhere
TheDude1179 said:
Can you tell me where you found a Lineage 16.1 build for SM-T330NU ? I can't find it anywhere
Click to expand...
Click to collapse
Sorry, the Lineage rom appears to be 16 not 16.1. Here is where I first learned about new ROM development for our SM-T330NU...https://forum.xda-developers.com/tab-4/development/samsung-galaxy-tab-4-light-project-t3877643. DJABHipHop has worked with many Samsung Tab 4 devices and provided more updated roms for us. You need to have Telegram installed then go to https://t.me/LightFastRoms. You will have to read through several postings but you will eventually see the new Lineage build for the milletwifi which is our 330NU. You will need to flash this new TWRP then there are 2 new milletwifi builds on Telegram, make sure you read the postings and eventually flash the build with "ota" in the title in order to have full functionality of the notifications bar.
TWRP Clock Function Incorrect
First of all, this TWRP works great and it is so nice to have an updated recovery available for our Tab 4's. The only thing I have noticed is that the time function is totally incorrect and I haven't been able to correct it from the TWRP settings menu. I don't really care if the time listed at the top of the TWRP page is correct but I have noticed that when I do a backup, the date is totally wrong, for instance I just backed up before flashing the most recent milletwifi build and the backup title is dated 2014-01-12!
You are amazing man i really appreciate you still develop for abandoned devices
Sent from my Poco F1 using XDA Labs
Hi,
TWRP 3.3.3.1-0 milletwifi.tar for T330 milletWIFI for either T330 or T330NU. What is the difference between models.
Mine is T330 not NU version sold in Australia.
I can supply recovery.img for Stock 5.1.1 Latest XSA.
Details extracted from About Device.
Model No. SM-T330 Android Version 5.1.1 Security patch level 02/04/2016 Build # LMY47x.T330XXS1BQA3
SE for Android Enforcing SEPF_SM-T330_5.1.1_0066 Sept 06 2016 Kernel 3.4.0-7541410 dpi @swhE9422#1 Wed Jan 11 18.36.37 KST 2017,
Question: Will recovery.img created and downloaded as per your link, Work for either model of milletwifi, or will a new TWRP recovery.img need to be created using my model T330 STOCK Recovery.img.
Please clarify, Thanks
BeeJ1109 said:
Hi,
TWRP 3.3.3.1-0 milletwifi.tar for T330 milletWIFI for either T330 or T330NU. What is the difference between models.
Mine is T330 not NU version sold in Australia.
I can supply recovery.img for Stock 5.1.1 Latest XSA.
Details extracted from About Device.
Model No. SM-T330 Android Version 5.1.1 Security patch level 02/04/2016 Build # LMY47x.T330XXS1BQA3
SE for Android Enforcing SEPF_SM-T330_5.1.1_0066 Sept 06 2016 Kernel 3.4.0-7541410 dpi @swhE9422#1 Wed Jan 11 18.36.37 KST 2017,
Question: Will recovery.img created and downloaded as per your link, Work for either model of milletwifi, or will a new TWRP recovery.img need to be created using my model T330 STOCK Recovery.img.
Please clarify, Thanks
Click to expand...
Click to collapse
Yes
Cant install TWRP
Hi,
I downloaded the .tar file and loaded it on to my sd card, but my tablet couldn't read it. Then I tried extracting the recovery img from the file and tried to flash it, but i got an error saying, 'Error opening: '/external_sd/samsung tab 4 roms/recovery.img' (No such file or directory)'
Sorry if this a noob question, but what are the exact steps for installing twrp on this tablet? I remember having a OPO, and installing things on it was a breeze. Thanks!
Help!!!!
Waarom krijg ik de inhoud niet te zien?
all links dead
Linkman8x said:
all links dead
Click to expand...
Click to collapse
Delete post new post is up on XDA
DJABHipHop said:
Delete post new post is up on XDA
Click to expand...
Click to collapse
can u give the link? can this works on SM-T231 also?
POPiO. said:
can u give the link? can this works on SM-T231 also?
Click to expand...
Click to collapse
https://forum.xda-developers.com/tab-4/development/unofficial-twrp-samsung-galaxy-tab-4-10-t3978063
Links are dead again - can anybody update?
who ever has the twrp 3.3.1.file can you post on android file host link as the drive link is not working. dont know why this is the case.but who ever ha the actual twrp 3.3.1 imagecan you guys post .
since i have cf auto root install can i just instal twrp img instead of installing twrp reocvery tar.what is easier to do. is this recovery stable.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well, we're finally getting some relatively stable builds of AOSP GSIs and OpenGApps for Android 11.0, so here's my first effort at migrating the Nexus Stock custom ROM for the 2019 Galaxy Tab A 10.0 [SM-T510] to the latest Android OS release. It's very much a work in progress, but it should hopefully help blaze the trail for even better work.
Notes:
The current process may require you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
Custom kernels are specific to OEM releases, and are generally based on the latest update for the SM-T510. Note that the bootloader in this release has roll-back prevention.
The system is based on eremitein's CAOS GSI project with the latest Stock variant from OpenGApps.
Boot logo and default wallpaper is from my Nexus series of custom ROMs for Android TV, and I'm using the Pixel boot animation with black background.
Stock recovery will be replaced with my latest TWRP build for the SM-T510.
I've dialed back most of scary bootloader warnings and Knox Security branding from the boot sequence.
The properties now correctly identify the device as a tablet, and so the Google Dialer is no longer installed. I've also disabled the Emergency button, but SetupWizard still insists on reminding you to insert a SIM (sigh!).
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
Cold charging (low power mode) animates to about 39% and then reboots.
Downloads:
Nexus_Stock_CR_T510XXU5CUL1-20220219.tar.md5 (Odin tarball)
Nexus_Stock_CR_T510XXU5CUL1-20220219.zip (TWRP update)
Build archives:
Android File Host
Change Log:
20220219:
Vendor partition and custom kernel based on T510XXU5CUL1 OEM firmware (December 2021 Update)
System partition based on CAOS 11.0 v315 (January 2022 Security Update)
Latest Google apps from OpenGApps (20220215) w/ rollback for GoogleTTS
20211125:
Vendor partition and custom kernel based on T510XXU5CUJ1 OEM firmware (October 2021 Update)
Update to TWRP v3.6.0 custom recovery on AOSP 11
Latest Google apps from OpenGApps (20211125) w/ rollback for GoogleTTS
20211120:
System partition based on CAOS 11.0 v313+ (October 2021 Security Update)
Latest Google apps from OpenGApps (20211120) w/ rollback for GoogleTTS
20210825:
Vendor partition and custom kernel based on T510XXU5CUF4 OEM firmware (June 2021 Update)
System partition based on CAOS 11.0 v312 (August 2021 Security Update)
Update to TWRP v3.5.2 custom recovery
Latest Google apps from OpenGApps (20210825-TEST)
20210318:
Fixed custom Pixel Launcher so that icon positions are saved.
Fixed clipped pixels on edge of launcher search bar.
Defaults icon layout to 7 columns for main, hotseat and app drawer, just like it used to be for the Nexus 10. (For 6 column layout bump display scaling to Large.)
20210314:
Vendor partition and custom kernel based on T510XXU4BUA1 OEM firmware (January 2021 Update)
System partition based on CAOS 11.0 v302 (March 2021 Security Update)
Update to TWRP v3.5.1 custom recovery
Latest Google apps from OpenGApps (20210130-TEST)
20210216:
Initial build based on T510XXU3BTK1 kernel (November 2020 Update) and CAOS 11.0 v300m.
Latest Google apps from OpenGApps (20210130-TEST)
Instructions:
From OEM stock firmware:
Unlock bootloader
Ensure matching OEM build (e.g. T510XXU3BTK1) is installed
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM tarball (.tar.md5 file) to AP with Odin
When TWRP launches, factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
Reboot to system
From existing TWRP install (for incremental updates):
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install, select your update (.zip file), and then swipe to install
Reboot to system
Source:
android_device_samsung_gta3xlwifi
android_device_samsung_gta3xl
Phh-Treble
Donations:
Your support is always appreciated! Just click here.
I'm leveraging a ton of work done by @phhusson for Treble GSIs and @eremitein for CAOS, so please show them some love!
Reserved.
Worked fine for me. Thanks.
I can't get Magisk 21.4 to work on this rom after updating with TWRP. I also tried to patch the boot.img with Magisk Manager.
Has someone else this working? I will temporary return to Android 10.
waterpolo said:
I can't get Magisk 21.4 to work on this rom after updating with TWRP. I also tried to patch the boot.img with Magisk Manager.
Has someone else this working? I will temporary return to Android 10.
Click to expand...
Click to collapse
I haven't been able to root any ROM based on AOSP 11.0...even the S variants that include su , but I'm not really an expert on rooting.
Yep magisk not working for me also, thats a shame because it's quite smooth overall, hoping for it to work in the next updates
For my Samsung mobile device I see on the XDA forum that Magisk is included in the ROM and isn't allowed to updated when a new version is released, only the Magisk manager could be updated.
I am afraid that installing seperate as on Android 10 isn't possible anymore.
waterpolo said:
For my Samsung mobile device I see on the XDA forum that Magisk is included in the ROM and isn't allowed to updated when a new version is released, only the Magisk manager could be updated.
I am afraid that installing seperate as on Android 10 isn't possible anymore.
Click to expand...
Click to collapse
The problem with that is that there is no Magisk Manager in Play Store with this ROM.
edit: Something appears to be going on with Google and Magisk and it is NOT just with this ROM or even this device. Apparently Google has not only removed Magisk Manager from the Play Store but have done something to keep it from giving root privileges all together!!!
re-edit: I apologize. I panicked. The problem appears to be with this device and the latest version of Magisk and with this ROM and Magisk. I can get version 20.4 to work with other ROMs, but it hangs with this one.
- scratched -
If anyone finds a version of Magisk that works with this ROM, please post it. I've tried V20.4, which causes a hang during boot, and V21.4, and 21.2, which boot but don't work.
lewmur said:
If anyone finds a version of Magisk that works with this ROM, please post it. I've tried V20.4, which causes a hang during boot, and V21.4, and 21.2, which boot but don't work.
Click to expand...
Click to collapse
Magisk V20.4 isn't for Android 11+. Therefor you have to install V21, but unfortunately is this not working.
is this ROM good for daily use or better to use the Android 10 one?
Broman400 said:
is this ROM good for daily use or better to use the Android 10 one?
Click to expand...
Click to collapse
1)
maybe there a bug with Wifi and connections with WPA3 (with PMF), only WPA2 is working here.
But this is a weak statement, cause I'm running a Beta FW on my Router (FB 7590) with some wifi bugs in the past. - I mean my Galaxy S4 with LOS 18.1 hadn't that - I'm not sure -
- EDIT-
Release Router FW arrived today: same result.
2)
my arranged apps/icons in the bottom line are resetted to the default google after an reboot.
whereby:
removing some google apps out of the bottom line will survive a reboot, all other arrangements won't.
e.g. I removed nearly all google apps and left only the outer left and right (see the above 1st screenshot) and dropped installed apps in the free place.
turns out: only the google apps (playstore + camera) are there after an reboot.
could someone check that ?
PMF:= Protected Management Frames
IEEE 802.11w-2009 - Wikipedia
en.wikipedia.org
Great work out there. Can you do this rom for SM-t515?
I can't find any lineage or ressurection rom for this tab
ryan.sn0w said:
Great work out there. Can you do this rom for SM-t515?
I can't find any lineage or ressurection rom for this tab
Click to expand...
Click to collapse
Sorry, I don't have a SM-T515 and it doesn't share the same kernel as the SM-T510. I've tried building ROMs blindly before, and you really can't do it without hardware for testing.
hi,
you wrote : "Ensure matching OEM build (e.g. T510XXU3BTK1) is installed"
My actual OEM is T510XXU4BUA1 which is newer than 510XXU3BTK1.
So each time i try to flash , I've got the message SYSTEM REV CHECK FAIL DEVICE : 4 BINARY : 3 (VENDOR).
I understand that i need to downgrade to T510XXU3BTK1. Is it possible to downgrade inside ANDROID 10 from an OEM 4 bits to an OEM 3 bits? How to do this?
Found the solution. Flash with heimdall orange fox recovery + multidisabler + RR custum ROM then full wipe + nexus custom ROM. All is working, good job, nice fast ROM.
@isaacragui
could do me a favor ?
with your fresh installed LOS, please check from comment #13, point 2)
I would like to know if it's only me.
rw_on_xda said:
@isaacragui
could do me a favor ?
with your fresh installed LOS, please check from comment #13, point 2)
I would like to know if it's only me.
Click to expand...
Click to collapse
Sorry i've almost immediatly switched to a AOSP ROM after having flashed LOS. Not because not working, but prefer AOSP.
Will check if return to LOS.
isaacragui said:
Sorry i've almost immediatly switched to a AOSP ROM after having flashed LOS. Not because not working, but prefer AOSP.
Will check if return to LOS.
Click to expand...
Click to collapse
thanks anyway
Disclaimer
Flash these at your own risk, I am not responsible for any problems that may occur.
It is NOT possible to easily downgrade firmware using recovery once upgraded.
Downgrading requires a special cable and opening of the box.
I am not affiliated with Xiaomi in any way, I just capture and share the public and beta updates.
Spoiler: Mi Box S - MDZ-22-AB
Code:
Android 8
r363 Downgrade/Unbrick Image:
https://mega.nz/file/615mGbSa#4ZuUah3yCinB_VWHpGMtEXaZYFzH7RKhjb5jtVhhg4w
r699 [RELEASE]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/cf1bcb02c65dae169a2313ef62d9d0c63a91588d.zip
Android 9
r2205 [OTA1 BETA0]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/efb7b83f37bb7c4273c366fa4ab237e47d8908e3.zip
r2216 [OTA1 BETA1]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/b045f83bafa03c2d0809fe6470a24c2192a338fe.zip
r2224 [OTA1 BETA2]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/d0b56c3ce4c1cea99c45856da9b194f56a8b53a3.zip
r2231 [RELEASE]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/84eeea378c7cbd03adb8240382717aa457ef6ea5.zip
r2582 [OTA2 BETA1]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/12e5455a8679c24c78bbbc77c63788c3a76eba7c.zip
r2596 [OTA2 BETA2]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/7a65e28754f99c0126b58b25652b97ab5a97926f.zip
r2603 [OTA2 BETA3]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/040153935c0e6f69ceae9eae1cbe222654e991f7.zip
r2604 [RELEASE]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/f69263555adae4e86c9896e34e30a93601de8e2f.zip
r2696 [RELEASE]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/811d10683084df7512b6cd56d137d53193c81856.zip
r3015 [OTA4 BETA0]
https://android.googleapis.com/packages/ota-api/package/11516e231b07ae14df0ae960cde690b601b2dddb.zip
r3091 [BETA]
https://android.googleapis.com/packages/ota-api/package/c5b22f23a38e07c9a8637c54df1d5f55470d71e7.zip
r3131 [BETA USERDEBUG] (VIDEO PLAYBACK BROKEN)
https://android.googleapis.com/packages/ota-api/package/ea3ec819034d1b00667fe6731914be43ae7a0276.zip
r3138 [BETA]
https://android.googleapis.com/packages/ota-api/package/f7f6b68bc80941aee1628b8bf005e1943b5f29cb.zip
r3139 [RELEASE]
https://android.googleapis.com/packages/ota-api/package/6f179c6fb4fe79ec1acebc3434f93232e0351100.zip
r3386 [OTA5 BETA0]
https://android.googleapis.com/packages/ota-api/package/56c7ee1e719ec842dff99dd4af0011f6fc6c7cdb.zip
r3409 [RELEASE]
https://android.googleapis.com/packages/ota-api/package/414e9608ca8a685244e4ee15e8628c98d255e51b.zip
r3595 [RELEASE]
https://android.googleapis.com/packages/ota-api/package/5cabec120b0378853b3d89a58c0171ac3e965046.zip
r3933 [RELEASE - BUILT SEP 28 2021]
https://android.googleapis.com/packages/ota-api/package/05be380dea3b2891a1fd3df98b138981689239ba.zip
Latest: r3933 released Oct 19th, 2021
Spoiler: Mi Box 3 - MDZ-16-AB
Code:
Android 8
r2167 Downgrade/Unbrick Image + Instructions
https://mega.nz/file/ag4U1TxR#WuT7SZmFvq2qkOlnd5_CKVGLM3L40IzXRWLQtjcuK18
https://forum.xda-developers.com/t/help-mi-box-stuck-bricked-mdz-16-ab.3834421/#post-83840349
r2167
https://android.googleapis.com/packages/ota-api/xiaomi_once_once/c23be4862ecb5ecf64a2300049611b3e5c04e00b.zip
r2179
https://android.googleapis.com/packages/ota-api/xiaomi_once_once/5c7bf1ed022e2bb32815d215703bf2e913c2c58e.zip
r2303
https://android.googleapis.com/packages/ota-api/xiaomi_once_once/3215cce132acc34ac9ffc04e2a0fd916aba2c1c0.zip
r2396
https://android.googleapis.com/packages/ota-api/xiaomi_once_once/a6a9b046d14f9504fdb274ed5810469beb0b1f20.zip
r2562
https://android.googleapis.com/packages/ota-api/xiaomi_once_once/2c49569c61c055db0b4f8dee8d49e4b04ecf9100.zip
r2573 (MISSING)
Android 9
r2926
https://android.googleapis.com/packages/ota-api/xiaomi_once_once/ed5bdb6aefb2bb6ee3f46a9f4d46026b9df88159.zip
r3175 (SLEEP BROKEN)
https://android.googleapis.com/packages/ota-api/package/a95c07064eb146946d79ee8b32d49a211c8cdec4.zip
r3420 [OTA2 BETA0]
https://android.googleapis.com/packages/ota-api/package/11aec6d60ea2f9d5cb5de9c8fe694a8f056e6497.zip
r3488 [OTA2 BETA1]
https://android.googleapis.com/packages/ota-api/package/3067d5b6b401bca137ae20b6c2fbbbd0de629b17.zip
r3575 [RELEASE]
https://android.googleapis.com/packages/ota-api/package/f986f8e86b73923f0f5a4e0ae284af7fa62e9bc2.zip
r3617 [OTA3 BETA0 - BUILT MAY 10 2021]
https://android.googleapis.com/packages/ota-api/package/be9ef9fe5334f8f5f9175b7d16315ca1c808ebc3.zip
r3934 [RELEASE - BUILT SEPT 28 2021]
https://android.googleapis.com/packages/ota-api/package/30199226c8b29962145c423a8dccd266c3800542.zip
Latest: r3934 released Oct 20th, 2021
Spoiler: Mi TV Stick - MDZ-24-AA
Code:
r536 - Sep 14 2020 - Security July 2020
https://android.googleapis.com/packages/ota-api/xiaomi_aquaman_aquaman/7349538031695c8e40775e08ee694f66992b5233.zip
r998 - Feb 23 2021 - Security Jan 2021
https://android.googleapis.com/packages/ota-api/package/cd1c1ae76232925c498e92fc9399aed4efa91377.zip
r1241 - May 27 2021 - Security March 2021
https://android.googleapis.com/packages/ota-api/package/8c3ab2cc0f3731b2333b0dcb35de991d436fd773.zip
Latest: r1241 released June 3rd, 2021
Latest firmware as of Oct 2021 include built-in ACR (Automatic Content Recognition), make sure it's disabled in Settings ⭢ Device preferences ⭢ ACR settings. You may also uninstall it by following these commands.
Added r3386 beta for Mi Box S
Changelog: Fix playback issues
Added r3409 for Mi Box S
Changelog: This build resolves the following critical issues:
1) Improve system performance
2) Update security patch
Edit: Public release
criscodecookies said:
Disclaimer: Flash these at your own risk, I am not responsible for any problems that may occur.
It is NOT possible to easily downgrade firmware using recovery once upgraded.
I'm making this thread because I'm tired of digging through blog posts and chat groups if you want the latest beta or an older release firmware.
Please feel free to add if you have a release not yet listed.
Spoiler: Mi Box S - MDZ-22-AB
Code:
O.363 Downgrade/Unbrick Image:
https://mega.nz/file/615mGbSa#4ZuUah3yCinB_VWHpGMtEXaZYFzH7RKhjb5jtVhhg4w
O.699 [RELEASE]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/cf1bcb02c65dae169a2313ef62d9d0c63a91588d.zip
PI.2205 [OTA1 BETA0]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/efb7b83f37bb7c4273c366fa4ab237e47d8908e3.zip
PI.2216 [OTA1 BETA1]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/b045f83bafa03c2d0809fe6470a24c2192a338fe.zip
PI.2224 [OTA1 BETA2]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/d0b56c3ce4c1cea99c45856da9b194f56a8b53a3.zip
PI.2231 [RELEASE]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/84eeea378c7cbd03adb8240382717aa457ef6ea5.zip
PI.2582 [OTA2 BETA1]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/12e5455a8679c24c78bbbc77c63788c3a76eba7c.zip
PI.2596 [OTA2 BETA2]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/7a65e28754f99c0126b58b25652b97ab5a97926f.zip
PI.2603 [OTA2 BETA3]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/040153935c0e6f69ceae9eae1cbe222654e991f7.zip
PI.2604 [RELEASE]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/f69263555adae4e86c9896e34e30a93601de8e2f.zip
PI.2696 [RELEASE]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/811d10683084df7512b6cd56d137d53193c81856.zip
PI.3015 [OTA4 BETA0]
https://android.googleapis.com/packages/ota-api/package/11516e231b07ae14df0ae960cde690b601b2dddb.zip
PI.3091 [BETA]
https://android.googleapis.com/packages/ota-api/package/c5b22f23a38e07c9a8637c54df1d5f55470d71e7.zip
PI.3131 [BETA USERDEBUG] (VIDEO PLAYBACK BROKEN)
https://android.googleapis.com/packages/ota-api/package/ea3ec819034d1b00667fe6731914be43ae7a0276.zip
PI.3138 [BETA]
https://android.googleapis.com/packages/ota-api/package/f7f6b68bc80941aee1628b8bf005e1943b5f29cb.zip
PI.3139 [RELEASE]
https://android.googleapis.com/packages/ota-api/package/6f179c6fb4fe79ec1acebc3434f93232e0351100.zip
PI.3386 [OTA5 BETA0]
https://android.googleapis.com/packages/ota-api/package/56c7ee1e719ec842dff99dd4af0011f6fc6c7cdb.zip
PI.3409 [OTA5 BETA0]
https://android.googleapis.com/packages/ota-api/package/414e9608ca8a685244e4ee15e8628c98d255e51b.zip
Latest Beta: PI.3409 released March 9th, 2021
I'm in the Mi Box S beta so will post links as I get them.
Spoiler: Mi Box 3 - MDZ-16-AB
Code:
Android 8
O.2167 Downgrade/Unbrick Image + Instructions
https://mega.nz/file/ag4U1TxR#WuT7SZmFvq2qkOlnd5_CKVGLM3L40IzXRWLQtjcuK18
https://forum.xda-developers.com/t/help-mi-box-stuck-bricked-mdz-16-ab.3834421/#post-83840349
O.2167
https://android.googleapis.com/packages/ota-api/xiaomi_once_once/c23be4862ecb5ecf64a2300049611b3e5c04e00b.zip
O.2179
https://android.googleapis.com/packages/ota-api/xiaomi_once_once/5c7bf1ed022e2bb32815d215703bf2e913c2c58e.zip
O.2303
https://android.googleapis.com/packages/ota-api/xiaomi_once_once/3215cce132acc34ac9ffc04e2a0fd916aba2c1c0.zip
O.2396
https://android.googleapis.com/packages/ota-api/xiaomi_once_once/a6a9b046d14f9504fdb274ed5810469beb0b1f20.zip
O.2562
https://android.googleapis.com/packages/ota-api/xiaomi_once_once/2c49569c61c055db0b4f8dee8d49e4b04ecf9100.zip
O.2573 (MISSING)
Android 9
PI.2926
https://android.googleapis.com/packages/ota-api/xiaomi_once_once/ed5bdb6aefb2bb6ee3f46a9f4d46026b9df88159.zip
PI.3175 (SLEEP BROKEN)
https://android.googleapis.com/packages/ota-api/package/a95c07064eb146946d79ee8b32d49a211c8cdec4.zip
Spoiler: Mi TV Stick - MDZ-24-AA
Code:
PI.536 - Sep 14 2020 - Security July 2020
https://android.googleapis.com/packages/ota-api/xiaomi_aquaman_aquaman/7349538031695c8e40775e08ee694f66992b5233.zip
PI.998 - Feb 23 2021 - Security Jan 2021
https://android.googleapis.com/packages/ota-api/package/cd1c1ae76232925c498e92fc9399aed4efa91377.zip
Click to expand...
Click to collapse
Can you please correct that PI3409 for Mi Box S is a full Public Final Release?
Latest Mibox S system update (version 3409) gone public. I don't know if Xiaomi mistakenly release it to public as it is the same version as the beta one.
There is one critical issue in this update where USB drive formatted as internal storage is unable to be detected by the Mibox S. External HDD or SSD (not formatted as internal storage) has no problem to access.
I have been looking this files for almost a week. Great post!
On MDZ-16-AB, how do I upgrade from 6.0.1 to O.2167?
extract .zip to FAT32 pen and boot to recovery?
Edit: I already did it
M Huzaifah said:
Latest Mibox S system update (version 3409) gone public. I don't know if Xiaomi mistakenly release it to public as it is the same version as the beta one.
There is one critical issue in this update where USB drive formatted as internal storage is unable to be detected by the Mibox S. External HDD or SSD (not formatted as internal storage) has no problem to access.
Click to expand...
Click to collapse
I can confirm this BUG
unbelievable thas Xiaomi released it to the public
Today I sent a bug report to Xiaomi support
hopefully they will answer soon
nice, now i have a mi stick rom, see if its suitable for porting like mi box s rom is
M Huzaifah said:
Latest Mibox S system update (version 3409) gone public. I don't know if Xiaomi mistakenly release it to public as it is the same version as the beta one.
There is one critical issue in this update where USB drive formatted as internal storage is unable to be detected by the Mibox S. External HDD or SSD (not formatted as internal storage) has no problem to access.
Click to expand...
Click to collapse
I didn't test this but seen a reddit user was able to workaround this by changing "Select USB Configuration" in Developer settings from Charging to MTP.
criscodecookies said:
I didn't test this but seen a reddit user was able to workaround this by changing "Select USB Configuration" in Developer settings from Charging to MTP.
Click to expand...
Click to collapse
this workaround only lasts until next reboot
Should the update mode be done using flash tools or recovery using a pen drive?
With the thumb drive just extract the zip and throw everything in the root?
Thanks.
Added r3420 beta for Mi Box 3
Changelog: Fix playback issue and update security patch
Hoping this helps anyone having sleep playback issues on r3175
Thanks just looking for Mi TV Stick MDZ-24-AA , now just need to find out how to recover might some one have some advice
bwallacep said:
Thanks just looking for Mi TV Stick MDZ-24-AA , now just need to find out how to recover might some one have some advice
Click to expand...
Click to collapse
There's currently no full system image for the Mi TV Stick that I know of, nor do we know the procedure/pins to put it in flash mode yet.
criscodecookies said:
Disclaimer
Flash these at your own risk, I am not responsible for any problems that may occur.
It is NOT possible to easily downgrade firmware using recovery once upgraded.
Downgrading requires a unique cable and opening of the box.
I'm making this thread because I'm tired of digging through blog posts and chat groups if you want to download the latest beta or an older release firmware.
Spoiler: Mi Box S - MDZ-22-AB
Code:
O.363 Downgrade/Unbrick Image:
https://mega.nz/file/615mGbSa#4ZuUah3yCinB_VWHpGMtEXaZYFzH7RKhjb5jtVhhg4w
O.699 [RELEASE]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/cf1bcb02c65dae169a2313ef62d9d0c63a91588d.zip
PI.2205 [OTA1 BETA0]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/efb7b83f37bb7c4273c366fa4ab237e47d8908e3.zip
PI.2216 [OTA1 BETA1]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/b045f83bafa03c2d0809fe6470a24c2192a338fe.zip
PI.2224 [OTA1 BETA2]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/d0b56c3ce4c1cea99c45856da9b194f56a8b53a3.zip
PI.2231 [RELEASE]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/84eeea378c7cbd03adb8240382717aa457ef6ea5.zip
PI.2582 [OTA2 BETA1]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/12e5455a8679c24c78bbbc77c63788c3a76eba7c.zip
PI.2596 [OTA2 BETA2]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/7a65e28754f99c0126b58b25652b97ab5a97926f.zip
PI.2603 [OTA2 BETA3]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/040153935c0e6f69ceae9eae1cbe222654e991f7.zip
PI.2604 [RELEASE]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/f69263555adae4e86c9896e34e30a93601de8e2f.zip
PI.2696 [RELEASE]
https://android.googleapis.com/packages/ota-api/xiaomi_oneday_oneday/811d10683084df7512b6cd56d137d53193c81856.zip
PI.3015 [OTA4 BETA0]
https://android.googleapis.com/packages/ota-api/package/11516e231b07ae14df0ae960cde690b601b2dddb.zip
PI.3091 [BETA]
https://android.googleapis.com/packages/ota-api/package/c5b22f23a38e07c9a8637c54df1d5f55470d71e7.zip
PI.3131 [BETA USERDEBUG] (VIDEO PLAYBACK BROKEN)
https://android.googleapis.com/packages/ota-api/package/ea3ec819034d1b00667fe6731914be43ae7a0276.zip
PI.3138 [BETA]
https://android.googleapis.com/packages/ota-api/package/f7f6b68bc80941aee1628b8bf005e1943b5f29cb.zip
PI.3139 [RELEASE]
https://android.googleapis.com/packages/ota-api/package/6f179c6fb4fe79ec1acebc3434f93232e0351100.zip
PI.3386 [OTA5 BETA0]
https://android.googleapis.com/packages/ota-api/package/56c7ee1e719ec842dff99dd4af0011f6fc6c7cdb.zip
PI.3409 [RELEASE]
https://android.googleapis.com/packages/ota-api/package/414e9608ca8a685244e4ee15e8628c98d255e51b.zip
Latest: PI.3409 released March 9th, 2021
Spoiler: Mi Box 3 - MDZ-16-AB
Code:
Android 8
O.2167 Downgrade/Unbrick Image + Instructions
https://mega.nz/file/ag4U1TxR#WuT7SZmFvq2qkOlnd5_CKVGLM3L40IzXRWLQtjcuK18
https://forum.xda-developers.com/t/help-mi-box-stuck-bricked-mdz-16-ab.3834421/#post-83840349
O.2167
https://android.googleapis.com/packages/ota-api/xiaomi_once_once/c23be4862ecb5ecf64a2300049611b3e5c04e00b.zip
O.2179
https://android.googleapis.com/packages/ota-api/xiaomi_once_once/5c7bf1ed022e2bb32815d215703bf2e913c2c58e.zip
O.2303
https://android.googleapis.com/packages/ota-api/xiaomi_once_once/3215cce132acc34ac9ffc04e2a0fd916aba2c1c0.zip
O.2396
https://android.googleapis.com/packages/ota-api/xiaomi_once_once/a6a9b046d14f9504fdb274ed5810469beb0b1f20.zip
O.2562
https://android.googleapis.com/packages/ota-api/xiaomi_once_once/2c49569c61c055db0b4f8dee8d49e4b04ecf9100.zip
O.2573 (MISSING)
Android 9
PI.2926
https://android.googleapis.com/packages/ota-api/xiaomi_once_once/ed5bdb6aefb2bb6ee3f46a9f4d46026b9df88159.zip
PI.3175 (SLEEP BROKEN)
https://android.googleapis.com/packages/ota-api/package/a95c07064eb146946d79ee8b32d49a211c8cdec4.zip
PI.3420 [OTA2 BETA0]
https://android.googleapis.com/packages/ota-api/package/11aec6d60ea2f9d5cb5de9c8fe694a8f056e6497.zip
Latest: PI.3420 beta released March 11th, 2021
Spoiler: Mi TV Stick - MDZ-24-AA
Code:
PI.536 - Sep 14 2020 - Security July 2020
https://android.googleapis.com/packages/ota-api/xiaomi_aquaman_aquaman/7349538031695c8e40775e08ee694f66992b5233.zip
PI.998 - Feb 23 2021 - Security Jan 2021
https://android.googleapis.com/packages/ota-api/package/cd1c1ae76232925c498e92fc9399aed4efa91377.zip
Latest: PI.998 released Feb 26, 2021
Click to expand...
Click to collapse
Could you please edit O.363 Downgrade/Unbrick Image: link? Thanks
insafsiz said:
Could you please edit O.363 Downgrade/Unbrick Image: link? Thanks
Click to expand...
Click to collapse
Anything wrong with it? These full system images have no googleapis.com link as they're unofficial and thus must be hosted elsewhere.
criscodecookies said:
Anything wrong with it? These full system images have no googleapis.com link as they're unofficial and thus must be hosted elsewhere.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Link is dead
insafsiz said:
View attachment 5259195
Link is dead
Click to expand...
Click to collapse
Weird still works on my end, try this link I found from another forum.