Database Info

[Tool][AIO]Universal Android Flasher v1.40 b (ROM-dump,adb,Fastboot,build.prop,etc.)

Universal Android AIO Flasher Tool$
Updated [16/8/2012] to to v1.40 beta
NANDROID Backup added!
Screenshot taker added!
ROM Dump - Backup/restore added!
Build.prop maker added!
Splash Image Maker added!
{
"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"
}
Warning:This is for advanced users only,I take no responsibility of any damage done to your device using this tool.
I was tired of typing commands for flashing my android,So i made a GUI Application that does all the hassle of flashing etc. easily.
It will work with most Android phones [Rooted] out there.
Right now it has following features:
1.Complete Fastboot Flasher: It can Flash Boot,Recovery,System,Userdata,Radio Images and even Splash Images.
It can also Help in Restoring Nandroid backups(not tested)
2.ADB Flasher:For Cyanogenmod only. It can Flash Boot images,Recovery Image and Splash Image on a Live Running Android Device without rebooting phone
3.Boot Animation Changer: yes it can also change boot animation of Android,
Just choose any zip file of any name and it will flash it.
If it throws an error try "remount System" button
4.Integrated ADB shell: Just with a single click of a button,the Output console becomes ADB shell.
5.Reboot menu: Reboot straight to recovery mode or Fastboot (bootloader mode) or reboot normally with a single click.
5.1 Remount System to r/w with a single click
6.APK Installer. (testing phase).
7.Universal Device Unrooter: removes superuser and SU binary.
8.Splash Screen Image Maker (Converter):Now you can make your own custom Splash Images and flash them straight away in a few clicks.
So many resolutions available.It automatically resizes and coverts the image files.
9.Build.prop editor: Now you can easily import build.prop file from your device or harddrive and edit it in inbuilt richtext editor and save it right on the device or your harddisk.
10.ROM Dump:Now you can dump ROM images easily with included 3 different methods (2 of them not tested)
11.Full Backup/Restore:now possible for ICS 4.0+ devices-easy backup and restore.
12.Online NANDroid Backup:Clockworkmod compatible Online Nandroid Backup-Works on all devices-No need to switch off the device.
ONandroid binary developed by "ameer1234567890"
Original link:http://forum.xda-developers.com/showthread.php?t=1620255
13.Screenshot:now possible to take screenshots from PC (testing)-only for WVGA devices
While Flashing,there is no need to rename image files or copy pasting them here and there,Just browse to the desired file and flash it right away.Just that the path should'nt have spaces in its name.!:highfive:
Usage:
Connect your device in Fastboot mode (for fastboot flasher) or in Debugging mode (for ADB flasher and Boot animation changer) and start the program.
the features are pretty much self explanatory.
If you get stucked or error comes in,you should rectify the problem and restart the application to ensure optimal performance.
Prerequisites:
Fastboot and ADB drivers must be installed and properly working before using this program.
Other upcoming features are:
1.Build.prop editor -added in v1.00
2.Kernel flasher
3.Recovery tools
4.Zipalign
5.Odex/deodex
6.Suggest more...
7.God knows what more...
Any suggestions are Welcome and much Appreciated.:good:
This is an alpha application and may contains bugs like it won't show errors,you have to determine them by looking at shell output,but if you have connected device properly and have drivers installed,you won't run into problems!:angel:
This might not work on Windows Xp,You might need to install NET framework 4.0 or higher to make it work.
Latest Version 1.40 beta
Note:for ffmpeg converter to work,you must download ffmpeg from here and extract it in tools folder of flasher:
http://www.multiupload.nl/ZY3UKJ8BZO
Mirrors for ffmpeg:
http://www.4shared.com/archive/0wKm1az1/ffmpeg.html
http://turbobit.net/jk4g1bdydrrf.html
For those who are unable to get their devices connected:Try copying "adb","AdbWinApi",and"AdbWinUsbApi" files from your android-sdk(or wherever you have adb) to flasher's /tools folder (replacing original ones),then try running Flasher again.
If You liked my work,Atleast Click Thanks Button,its Free,It encourages me.:victory:

Changelog:
[16/8/2012] New Release v1.40 beta:
Added Clockworkmod compatible Online NANDroid Backup
Added Ability to take screenshots
Better error handling
Added Splash screen
[01/8/2012] New Release v1.20 beta:
Added Backup/restore (for 4.0+ only)
Added ROM Dump !
Added Flash_image binary
Added QVGA-lanscape resolution
fixed some permission errors.
[25/7/2012] New Release v1.00 beta:
Build.prop Editor Added!
HD resolutions added in Splash maker (You can request more)
Radio/Modem flasher added in fastboot
added reboot from fastboot
List MTD partion info
Bootanimation changer fixed
Added alternate bootanimation changer
Added Apk reinstall option
Remount system fixed
Fixed splash overwrite bug
Changed download site for ffmpeg
Improved unrooter code
[20/7/2012] New Release 0.99:
MAJOR UPDATE
Splash Image maker added
Refreshed UI
Too many internal changes
[17/7/2012] Minor Release 0.95.2:
Fixed Files path Bug (Having spaces in names)-now you can choose practically any file from any path.
Internal tweaks
[15/7/2012] New Release 0.95:
Added APK Installer
Added Universal unrooter
Other interface changes
Minor fixes
[14/7/2012] New Release 0.91:
Added reboot menu
Added flash_image binary installer for non CM phones
Added System remounter
Added integrated ADB shell
Fixed bootanimation changer
Minor fixes
[14/7/2012]Initial release 0.7

fonehacker said:
Android AIO Flasher
I was tired of typing commands for flashing my android,So i made a GUI Application that does all the hassle of flashing etc. easily.
Right now it has following features:
1.Complete Fastboot Flasher: It can Flash Boot,Recovery,System,Userdata and even Splash Images.
It can also Help in Restoring Nandroid backups(not tested)
2.ADB Flasher: It can Flash Boot images,Recovery Image and Splash Image on a Live Running Android Device without rebooting phone
3.Boot Animation Changer: yes it can also change boot animation of Android,
Just choose any zip file of any name and it will flash it.
While Flashing,there is no need to rename image files or copy pasting them here and there,Just browse to the desired file and flash it right away!:highfive:
Usage:
Connect your device in Fastboot mode (for fastboot flasher) or in Debugging mode (for ADB flasher and Boot animation changer) and start the program.
the features are pretty much self explanatory.
Prerequisites:
Fastboot and ADB drivers must be installed and properly working before using this program.
Other upcoming features are:
1.Build.prop editor
2.APK Installer
3.Kernel flasher
4.God knows what more...
Any suggestions are Welcome and much Appreciated.:good:
This is an alpha application and may contains bugs like it won't show errors,you have to determine them by looking at shell output,but if you have connected device properly and have drivers installed,you won't run into problems!:angel:
This might not work on Windows Xp,You might need to install NET framework 4.0 or higher to make it work.
Download Link:
http://www.multiupload.nl/PVXRL25OKO
If You liked my work,You can hit Thanks Button,It encourages me.:victory:
Click to expand...
Click to collapse
awesome!!!!!!

NICE WORK

nicely done!! :good: keep it up!!

looks awesome

BDogg718 said:
link down..or hijacked...lol
Click to expand...
Click to collapse
Link is perfectly working,just checked.

that is weird. it keeps taking me to some internet vs hollywood site..lol. could u db it for me please? would love to try this

BDogg718 said:
that is weird. it keeps taking me to some internet vs hollywood site..lol. could u db it for me please? would love to try this
Click to expand...
Click to collapse
Just added a 4shared mirror

Well built programme indeed! Congrats!
Tried it out in fastboot mode and flashed cwm recovery image and it went perfectly well!
Tried it on adb interface in live mode got an error, please see the attachment.
Can I suggest an option to add reboot to recovery or simple reboot on the programme interface?:good:

clavicle said:
Well built programme indeed! Congrats!
Tried it out in fastboot mode and flashed cwm recovery image and it went perfectly well!
Tried it on adb interface in live mode got an error, please see the attachment.
Can I suggest an option to add reboot to recovery or simple reboot on the programme interface?:good:
Click to expand...
Click to collapse
The error is beacouse the A9 might not have have flash_image binary.I'll work on it for A9 and similar devices.
That's gud,I'll add those features.:good:
More suggestions are whole heartedly welcomed....

clavicle said:
Well built programme indeed! Congrats!
Tried it out in fastboot mode and flashed cwm recovery image and it went perfectly well!
Tried it on adb interface in live mode got an error, please see the attachment.
Can I suggest an option to add reboot to recovery or simple reboot on the programme interface?:good:
Click to expand...
Click to collapse
Great Job
Can I link this to my Karbonn A9 & Spice Stellar Threads?

prasad12ka4 said:
Great Job
Can I link this to my Karbonn A9 & Spice Stellar Threads?
Click to expand...
Click to collapse
Sure you can...:good::laugh:

awesome

Works Well !!!
Tried with many other tools to flash splash.img for my spice mi 425 didnt work ....This One works flawlessly and also tried with stock boot.img flash it worked... Thanks a ton to fonehacker!!!

This is really a great work Mr.FOnehacker
keep up:cyclops: the great work
fonehacker said:
Android AIO Flasher
Updated to to.91
I was tired of typing commands for flashing my android,So i made a GUI Application that does all the hassle of flashing etc. easily.
It will work with most Android phones [Rooted] out there.
Right now it has following features:
1.Complete Fastboot Flasher: It can Flash Boot,Recovery,System,Userdata and even Splash Images.
It can also Help in Restoring Nandroid backups(not tested)
2.ADB Flasher: It can Flash Boot images,Recovery Image and Splash Image on a Live Running Android Device without rebooting phone
3.Boot Animation Changer: yes it can also change boot animation of Android,
Just choose any zip file of any name and it will flash it.
If it throws an error try "remount System" button
4.Integrated ADB shell: Just with a single click of a button,the Output console becomes ADB shell.
5.Reboot menu: Reboot straight to recovery mode or Fastboot (bootloader mode) or reboot normally with a single click.
5.1 Remount System to r/w with a single click
While Flashing,there is no need to rename image files or copy pasting them here and there,Just browse to the desired file and flash it right away.Just that the path should'nt have spaces in its name.!:highfive:
Usage:
Connect your device in Fastboot mode (for fastboot flasher) or in Debugging mode (for ADB flasher and Boot animation changer) and start the program.
the features are pretty much self explanatory.
If you get stucked or error comes in,you should rectify the problem and restart the application to ensure optimal performance.
Prerequisites:
Fastboot and ADB drivers must be installed and properly working before using this program.
Other upcoming features are:
1.Build.prop editor
2.APK Installer
3.Kernel flasher
4.God knows what more...
Any suggestions are Welcome and much Appreciated.:good:
This is an alpha application and may contains bugs like it won't show errors,you have to determine them by looking at shell output,but if you have connected device properly and have drivers installed,you won't run into problems!:angel:
This might not work on Windows Xp,You might need to install NET framework 4.0 or higher to make it work.
Latest Version 0.91
If You liked my work,You can hit Thanks Button,It encourages me.:victory:
Click to expand...
Click to collapse

Please suggest more features and list out bugs...
Thanks everyone,
You are all kindly requested to give suggestions for more features and also list out all bugs you have encountered.

fonehacker said:
Thanks everyone,
You are all kindly requested to give suggestions for more features and also list out all bugs you have encountered.
Click to expand...
Click to collapse
I think it would be more appropriate if you could hyperlink/incorporate the links of respective recovery/boot/system images of phones in the programme.
Or even better idea is to select a phone, version, type of image required say recovery or any other and then programme leads the user to a particular webpage to download the required file and start using the programme. This option can excellent with a dedicated server to provide link in the programme itself, but manual option isn't a bad idea either.
This can be extended to bootanimations etc. too.
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
Add to it the option of backing up files before writing anything on phone, (no I know you can't backup system.img ).

clavicle said:
I think it would be more appropriate if you could hyperlink/incorporate the links of respective recovery/boot/system images of phones in the programme.
Or even better idea is to select a phone, version, type of image required say recovery or any other and then programme leads the user to a particular webpage to download the required file and start using the programme. This option can excellent with a dedicated server to provide link in the programme itself, but manual option isn't a bad idea either.
This can be extended to bootanimations etc. too.
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
Add to it the option of backing up files before writing anything on phone, (no I know you can't backup system.img ).
Click to expand...
Click to collapse
Actually there are just too many android models out there,so it's virtually impossible link the webpages for respective phones.
This is made to make the flashing like process more easier and user friendly.
BootAnimation changer is provided,but every phone has a different type of boot animations,so users have to search it themselves.
ADB flasher problem solved or not?
And yes,I am working on APK installer and system backup feature,and yes,system can be backed up.

@fonehacker
tried this amazing tool to flash cwm recovery for micromax funbook but it gave me permission error. I tried it in adb method, same was the case with varun's tool too.
wr m I going wrong?
and sum blogs say that t latest version of funbook with baseband 1.2 needs permission change for folders
'dev'
'block'
and 'nandg' file
I tried to change permission but was unable to change permission of nandg file.
watt to do pleas help!!

ZTE T815/Telstra Tempo T815 [ROOT][RECOVERY][ROMS]

{
"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"
}
This is a thread for the ZTE T815/Telstra Tempo T815. I hope other users who have this device might get some benefit and enjoyment out of this thread.
BACKUP!
Start here for a guide to extracting a ROM dump from your T815 and processing it to create a backup you can use to restore your phone if anything goes wrong for you
Custom Recovery and Root Method
I have ported PhilZ Touch Recovery V6 (6.59.0 - based on CWM 6.0.5.1) to the T815. Installation method and rooting instructions can be found here
Custom ROMs (list will be updated as new ROMs are posted)
[ROM] [PussyFap V3][KitKat] ZTE T815 - here
[ROM] [Pure LG G3][KitKat] ZTE T815 - here
[ROM] [Cherry ROM Lite v2.1][KitKat 4.4.2] ZTE T815 - here
[ROM][Amgoo OS][KitKat4.4.4] ZTE T815 - here

How install custom recovery and root ZTE T815
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROM's have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledge about the phone and phone utilities also.
Make sure that whatever you do, you are doing it at your own responsibility.
I have been able to port PhilZ Touch Recovery V6 (6.59.0 - based on CWM 6.0.5.1) to the ZTE T815. To flash this recovery to your device you will need the following:
- USB VCOM Driver - Installation tutorial and download of driver here (Don't worry that it says MTK6577, it works fine with MTK6572 based devices)
- Smart Phone Flash Tool - Download for all versions can be found here - scroll to the bottom of the list to find latest version
- Scatter file and custom recovery image - download here
- PC and USB cable
Method:
1. Follow the tutorial and install the USB VCOM driver.
2. Install SP Flash Tool - once installed, run as administrator.
3. On the "Download" tab page, click the box on the right hand side named "Scatter-loading". Browse to the location where you saved the downloaded "MT6572_Android_scatter.txt" file, select it and click "Open".
4. In the lower section of SP Flash Tool screen, tick the box next to RECOVERY. This is the ONLY box that is to be selected.
5. On the RECOVERY line, go across to the to the blank cell under the "Location" heading and click on it. Now browse to the location where you saved the downloaded "recovery.img", select it and click "Open". The line should now show the location of the file.
6. Turn off your phone and remove the battery.
7. On SP Flash Tool, click the "Download" button at the top of the page and THEN connect your phone to the PC via the USB cable (battery still out).
8. All going well, you should now see the download progress being displayed across the bottom of the screen. Once completed, you will see a big green tick displayed in the middle of the screen. Success! Your phone now has PhilZ Touch Recovery installed.
To access Recovery Mode, from power off hold down the volume up button and power button together for around 6 seconds (press and hold volume up first then press and hold power). You will now see the recovery main menu.
Root: (after you have your custom recovery installed)
1. Download supersu.zip (latest version) here - thanks to @Chainfire
2. Send zip file to your SD card.
3. Boot into recovery and install zip from SD card.
4. Reboot - your device is now rooted.
Important:
Make yourself a backup. (Note: the external SD card is /storage/sdcard1 - if you try to backup to sdcard0, you will run out of memory.)
To bring this PhilZ Touch Recovery to you, thanks and credit must be given to the following:
- Phil3759
- Koush for having created and maintaining cwm
- Cyanogenmod for making all this possible
- Tallustus from Team Skyfire for his great support over IRC: MAJOR CREDITS
- Dees_Troy from TWRP team for pigz source and many great ideas in their recovery + source for backups compatibility
- Chenglu for his unpacking tools and porting i9505: Huge credit
- kbc-developers for the base semi-touch code and much more
[email protected] for his great job / support
- sk8erwitskil for his recovery source, a great place to start learning
- shoe63 for his help from the start across many devices
- DooMLoRD for his work and help with Sony
- [NUT] for his ports to Sony
- wanam for compiling sensors-free kernels for N71xx/i317M, i9500 and i9505 to fix boot delay for custom kernels, exfat support and much more
- dougiebee for his work on fixing time on many Qualcom devices
- ausdim for all the support in developing kernels for i9505
- dr.ketan for his precious help in porting to the N7000 & N7100 (I don't own one) and all the support in threads
- Chainfire for his support (stock recovery flash) and all his work for the Android community
- 1966zippy for bringing it to the ZTE T815!

[ROM] [PussyFap V3][KitKat] ZTE T815
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I have had my first success at porting a custom ROM to the T815, so I present to you ***** Fap V3.
Requirements
BACKUP BEFORE DOING ANYTHING ELSE - If this ROM isn't for you then this is your fallback position.
You must be rooted.
You must have a custom recovery installed
You must have experience flashing but if not, feel free to ask questions before flashing.
Patience as the ROM takes a while to boot
To Install
Download zip file from link below and then send the file to your device's SD card. Boot into recovery, go to "Wipe and Format Options", use "Clean to Install a New ROM" and let finish then back to main menu. Choose "Install Zip" and select "choose zip from /storage/sdcard1 (second option from top). Navigate to the PussyFap_v3_T815.zip file and install. Go back to "Wipe and Format Options"and wipe Cache and wipe Dalvik/ART Cache. Go back to main menu and hit "Reboot System Now". Enjoy exploring this custom ROM.
Note: Google Play Store is an older version but it will update to the latest version once you have signed in and have an active internet connection.
Download ***** Fap V3 ROM for ZTE T815 here
Features:
Full Lollipop UI
Lollipop Framework
Tinted Status Bar
Nice settings
Smooth performance
Performance Control
Engineer Mode
Init.d Tweaks
Battery Icon Styles
Dynamic system bars
Progress bar animation
Known Bugs:
- GPS not working Appears it is working, just MT6572 GPS is really crap!
- shows 2 sim slots instead of 1
- I have not used this ROM to make calls so there may be issues that are radio/sim related. Let me know what you find and I will try to fix.
Screenshots:
Full Credits:
Team *****

Thanks for your helpful information

PetaX8 said:
Thanks for your helpful information
Click to expand...
Click to collapse
You're very welcome.
Sent from my GT-I9506 using XDA-Developers mobile app

[ROM] [Pure LG G3][KitKat] ZTE T815
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Another ROM for you to enjoy - Pure LG G3
Requirements
- BACKUP BEFORE DOING ANYTHING ELSE - If this ROM isn't for you then this is your fallback position.
- You must have a custom recovery installed
- You must have experience flashing but if not, feel free to ask questions before flashing.
- Patience as the ROM takes a while to boot
To Install
Download zip file from link below and then send the file to your device's SD card. Boot into PhilZ recovery, go to "Wipe and Format Options", use "Clean to Install a New ROM" and let finish then back to main menu. Choose "Install Zip" and select "choose zip from /storage/sdcard1 (second option from top). Navigate to the "Pure LG G3_T815.zip" file and install. Go back to main menu and hit "Reboot System Now".
Download Pure LG G3 ROM for ZTE T815 here
Features:
- 99% LG G3 UI
- LG G3 boot animation
- Smart Pause
- Palm Motion
Bugs:
- Let me know
Screenshots:
Credits:
- Muhammad Restu
- Team LG Developers
- needrom
- Smart Four Team

Thanks for updating me on this 1966zippy. Its worked perfectly for me

millsb0mb said:
Thanks for updating me on this 1966zippy. Its worked perfectly for me
Click to expand...
Click to collapse
Glad to hear. Hope you enjoy the ROMs.

1966zippy said:
Glad to hear. Hope you enjoy the ROMs.
Click to expand...
Click to collapse
Works significantly better thanks

zte t815 it says recovery mode i updated it from then it is happening

frank bird said:
zte t815 it says recovery mode i updated it from then it is happening
Click to expand...
Click to collapse
If you are in recovery mode with a purple background and a green android in the middle then you are in the recovery mode that we set out to achieve. Just touch "go back" on the screen until you are at the main menu and then select "reboot phone now" and you will boot to your stock OS.
If you are on the black recovery screen (stock recovery), it means that some part of the process did not work and you didn't get the custom recovery flashed correctly. You can navigate through the stock recovery menu by pressing volume down to select the line with the option you want and then confirm your selection with volume up (which I think goes against "normal" thinking and is a trap for making incorrect selections, so be careful, says he who has fallen for this same trap and blitzed his phone!).
You need to get back to the "reboot now" option and then try the process again (be sure you have the USB VCOM drivers installed properly.):good:

[ROM] [Cherry ROM Lite v2.1][KitKat 4.4.2] ZTE T815
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Here is another ROM for you to explore - Cherry ROM Lite v2.1
Requirements
- BACKUP BEFORE DOING ANYTHING ELSE - If this ROM isn't for you then this is your fallback position.
- You must have a custom recovery installed
- You must have experience flashing but if not, feel free to ask questions before flashing.
- Patience as the ROM takes a while to boot
To Install
Download zip file from link below and then send the file to your device's SD card. Boot into PhilZ recovery, go to "Wipe and Format Options", use "Clean to Install a New ROM" and let finish then back to main menu. Choose "Install Zip" and select "choose zip from /storage/sdcard1 (second option from top). Navigate to the "Cherry ROM Lite_v2.1_T815.zip" file and install. Go back to main menu and hit "Reboot System Now".
Download Cherry ROM Lite v2.1 for ZTE T815 here
Features:
- Amazing performance
- Audio enhancements
- Cyanogen file manager and browser
- Added GPS settings for better access to satellites
- SuperSU pre-installed
- Excellent RAM management
Bugs:
- Let me know
Screenshots:
Credits:
- Dertio Acos
- Unknown Porting Team
- Computer+Android
- 1966zippy for porting to T815

is there any new roms coming in? what about CyanogenMod? are you guys making a "pure" android ROM for T815? i didn't like the ***** fap rom as it doesn't work well with small screen, lg rom is perfect but slow, is the cherry rom near stock??
PS: great work keep up. if you could maybe remove the dual sim notification as i only have 1 sim slot, also maybe its a good idea to upload de-bloated stock rom for t815

Jesus Chen said:
is there any new roms coming in? what about CyanogenMod? are you guys making a "pure" android ROM for T815? i didn't like the ***** fap rom as it doesn't work well with small screen, lg rom is perfect but slow, is the cherry rom near stock??
PS: great work keep up. if you could maybe remove the dual sim notification as i only have 1 sim slot, also maybe its a good idea to upload de-bloated stock rom for t815
Click to expand...
Click to collapse
Thanks for your feedback. I do have plans to upload more ROMs as I port them and get most of the bugs squashed but, as I am on a massive learning curve regarding porting myself, it is taking a bit of time. I don't reckon I've done too bad so far for only a couple of weeks! I will leave the CyanogenMod ROM for a while, as it looks like it is one of the more complicated ROMs to port, but I will try to get it up here at some stage. I am working with a pure android ROM at the moment so hopefully that works out and I can upload it soon. The Cherry ROM is debloated and has some nice features but the only way to find out is to give it a whirl.
As for the dual sim thing, I am still trying to work out how to modify the ROM to only show the one sim (as I said, still got "L" plates on) and once I work out how to do this I will repost the corrected ROMs. I agree that a debloated stock ROM is a great idea so I will work on that when time permits.:highfive:

thanks
1966zippy said:
Thanks for your feedback. I do have plans to upload more ROMs as I port them and get most of the bugs squashed but, as I am on a massive learning curve regarding porting myself, it is taking a bit of time. I don't reckon I've done too bad so far for only a couple of weeks! I will leave the CyanogenMod ROM for a while, as it looks like it is one of the more complicated ROMs to port, but I will try to get it up here at some stage. I am working with a pure android ROM at the moment so hopefully that works out and I can upload it soon. The Cherry ROM is debloated and has some nice features but the only way to find out is to give it a whirl.
As for the dual sim thing, I am still trying to work out how to modify the ROM to only show the one sim (as I said, still got "L" plates on) and once I work out how to do this I will repost the corrected ROMs. I agree that a debloated stock ROM is a great idea so I will work on that when time permits.:highfive:
Click to expand...
Click to collapse
thanks for the lightning fast reply, ill be looking forward to pure stock android with support for single sim. keep up the good work and you da real MVP. perhaps check out alcatel pixi 3 xda http://forum.xda-developers.com/android/general/root-alcatel-one-touch-pixi-34-official-t3193624 as the 4 inch version have very similar spec with t815. (i have 4.5 inch with much fast/newer chipset,alias it doesn't have any custom rom) :good::good::good:

Jesus Chen said:
thanks for the lightning fast reply, ill be looking forward to pure stock android with support for single sim. keep up the good work and you da real MVP. perhaps check out alcatel pixi 3 xda http://forum.xda-developers.com/android/general/root-alcatel-one-touch-pixi-34-official-t3193624 as the 4 inch version have very similar spec with t815. (i have 4.5 inch with much fast/newer chipset,alias it doesn't have any custom rom) :good::good::good:
Click to expand...
Click to collapse
LOL!:laugh: Around 6 month ago I was looking for a cheap phone to mod and my final choice was between the Tempo T815 and Pixi 3(4), the Pixi winning out because it was $5 cheaper. It was the right choice as I found @kirito9's thread which was crammed full of info and ROMs. I learned a few things about working with the Mediatek MT6572 chipset and porting ROM's (thanks again to @kirito9 here, absolute legend) over there, all the while watching a small thread about the Tempo T815 where they had all stopped posting as no one could get root on the T815. I thought I could take the bits that I have worked out and apply them to this little supported device so here we are. I am no expert on all things MT6572 but I am working things out slowly so hang in there and I will put more ROMs and helpful info up here when I can.

[ROM] [Amgoo OS][KitKat 4.4.4] ZTE T815
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements
- BACKUP BEFORE DOING ANYTHING ELSE - If this ROM isn't for you then this is your fallback position.
- You must have a custom recovery installed
- You must have experience flashing but if not, feel free to ask questions before flashing.
- Patience as the ROM takes a while to boot
To Install
Download zip file from link below and then send the file to your device's SD card. Boot into PhilZ recovery, go to "Wipe and Format Options", use "Clean to Install a New ROM" and let finish then back to main menu. Choose "Install Zip" and select "choose zip from /storage/sdcard1 (second option from top). Navigate to the "Amgoo OS_T815.zip" file and install. Go back to main menu and hit "Reboot System Now".
Download Amgoo OS for ZTE T815 here
Features:
- Android Lollipop Inspired UI
- Deodexed
- Zipaligned
- Debloated
- Rooted (KingUser)
- Updated GAPPS (Google Chrome(Default Browser), Google App, Google Play Services, Hangouts(Default Messenger), Google Play Music(Default Music Player), Google Now Launcher(Default Launcher), Google Play Store)
- Modded System App (Lollipop Themed)
- Xposed Modules Integrated in Settings.apk
- Amgoo os Boot Logo
Bugs:
- Sound works OK but I can't get it as loud as I would like
- Anything else, let me know
Screenshots: (Apologies for poor screens but this ROM is worth trying for it's UFO live wallpaper alone!)
Credits:
- Nayeem Hossen For Porting This ROM
- Mou For making the boot logo
- 1966zippy for porting to T815

Full ROM Dump Backup & Read Back Method
This guide will show you how to make a full ROM dump of your ZTE T815 (Mediatek MT6572) device. It can be used to make a full backup at anytime but I strongly suggest that you follow this procedure prior to making any modifications to your device. That way you will always have a completely stock unmodified image to return to if things go bad or aren't what you expected. Don't say you haven't been warned!
Things you will need:
- ADB Drivers - here or here
- USB VCOM Driver - Installation tutorial and download of driver here (Don't worry that it says MTK6577, it works fine with MTK6572 based devices)
- MTK Droid Tools - here - scroll to the bottom of the list to find latest version
- Smart Phone Flash Tool - Download for all versions can be found here - scroll to the bottom of the list to find latest version
- Notepad++ - here
- A PC and USB Cable
Preparations:
- Install ADB Drivers system wide and follow tutorial to install USB VCOM Driver
- Install Notepad++
- Create a folder somewhere convenient (e.g. desktop) and give it a name related to phone/mods etc.
- Into this folder, install MTK Droid Tools and SP Flash Tool.
Process:
Make Scatter File
Run MTK Droid Tools as administrator. Once the program has started, connect your phone via the USB cable and you will see that your phone information loads up on the left side of the page. Below this you will see a button that says "Block Map". Press it. You will now see a screen displaying Block Info and at the bottom left a button "Create scatter file". Press this button and save the "MT6572_Android_scatter.txt" file to the folder that you made earlier. Don't close MTK Droid Tools, just minimise it at this stage and unplug your phone.
Read Back ROM From Phone
Run SP Flash Tool as administrator. By default it starts on the Download tab. You will see a button labelled "Scatter-loading" at the top right of the screen. Press this button and direct it to the "MT6572_Android_scatter.txt" that you just saved. Once loaded, change to the "readback" tab along the top and then click "Add". A line is added below and you need to click in the blank area under the heading "File". Browse to the location where you want to save your ROM dump (in that same folder again would be appropriate) make sure you retain the file name of "ROM_0" and press "Save".
There is now a dialogue box that pops up, "Readback block start address". The "Type" must remain as Hex. The "Start address" should also remain as it is - 0x0000000000000000. The "Length" address is determined by the address of the partition we wish to finish our ROM dump at. I would suggest that we use the address of the last partition in the phone. To find out this address we need to examine the scatter file. Open the scatter file with Notepad++ (this will keep the formatting in place). Easy way is to right click on the file and select "Edit with Notepad++" from drop down menu. Scroll to the bottom of the page and find the FAT partition information. The "linear_start_addr:" value here is where to end the ROM dump so carefully copy the address and paste into the "Readback block start address" dialogue in the "Length" field. (e.g. the linear start address of my FAT partition is 0x97140000 so this is the figure I enter into "Length").
Note: If you have already been using your phone before doing this backup method, you may wish to create a ROM dump that excludes your personal info. If so, you might choose not include the CACHE and USERDATA partitions in the backup so you would end the ROM dump at the linear start address of the CACHE partition (in my phone this is 0x36340000, for example).
Once the "Length" value is entered, press OK. Turn your phone off at this stage. Once it is fully powered down, click "Read Back" and then connect your powered off phone to the USB cable and all things going well you should see the progress bar at the bottom go blue and start moving. Once completed successfully you will see a green circle with a tick in it. Done! Disconnect your phone.
Process ROM For Use With SPFT
Turn your phone back on and when ready reconnect to MTK Droid Tools. Change to "root, backup, recovery" tab and press on the button labelled "To process file ROM_ from Flash Tool". Browse to your modding folder location and open "ROM_0". The processing will start and you will be prompted to make a CWM recovery automatically. Answer "No" and then "Cancel" when it asks to choose recovery. You will see the process in action and it will end with the message "Task is complete" at the end of the script. The folder containing this processed backup is located in yourmoddingfolder/Mtk_Droid_Tool_v2.5.3/backups. If you examine the contents of this processed ROM backup you will note that the output folder now also contains a scatter.txt file.
Restore process to follow - edit soon:good:

1966zippy said:
This guide will show you how to make a full ROM dump of your ZTE T815 (Mediatek MT6572) device. It can be used to make a full backup at anytime but I strongly suggest that you follow this procedure prior to making any modifications to your device. That way you will always have a completely stock unmodified image to return to if things go bad or aren't what you expected. Don't say you haven't been warned!
Click to expand...
Click to collapse
Can I borrow this post?

kirito9 said:
Can I borrow this port?
Click to expand...
Click to collapse
Assuming port was supposed to be post, you absolutely can borrow it, mate. [emoji106]
Sent from my GT-I9506 using XDA-Developers mobile app

[TWRPv3.x.x]Tank Xtreme Pro Recovery

{
"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"
}
.
Screenshots attached below.
TeamWin Touch Recovery for BLU Tank Extreme Pro
Code:
* [U][B]Disclaimer[/B][/U]
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Older Version
CHANGELOG for 3.1.1-0:
TWRP 3.1.1 is Out, Brings Minor Fixes
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
FEATURES
Backup & Restore fully functional
Micro SDcard and USB OTG storage support
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
Full SELinux support
Built with android-7.0 TWRP tree
CHANGELOG for 3.2.0-0:
TWRP 3.2.0 is now out
Allow restoring adb backups in the TWRP GUI (bigbiff)
Fix gzip backup error in adb backups (bigbiff)
Fix a bug in TWRP’s backup routines that occasionally corrupted backup files (nkk71)
Better support for installing Android 8.0 based zips due to legacy props (nkk71)
Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
v2 fstab support (Dees_Troy)
Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
Various other minor bugfixes and tweaks
CHANGELOG for 3.2.2-0:
TWRP 3.2.2-0 brings ADB fixes and improvements to OTA updates
adb backup fixes
OTA style update zips will now install automatically without prompting for decrypt
minor tweaks to handling date/time on Qualcomm devices
updates to some language translations
CHANGELOG for 3.2.3-0:
TWRP 3.2.3-0 is out now for most currently supported devices.
Fix automatic installing of OTA zips on encrypted devices
Remove SuperSU from TWRP
Support both md5 and md5sum file extensions when doing MD5 checking for zip files
BUGS:
MTP NOT Recognize Driver--So No mtp connection-- work-around for this now, is to use "mount as USB drive", this will allow similar function as MTP, but only for your micro-SDcard
SUPPORT: Post your questions below. I'll answer whenever I get time.
INSTALLATION
Most devices can be updated quickly and easily within TWRP if you already have version 3.x.y-z or higher installed
1) Download the latest version from DOWNLOAD TAB
2) Copy that file to your sdcard
3) Reboot to TWRP
4) Hit INSTALL and tap the "Images..." button in the lower right
5) Browse to the location of the TWRP image (recovery.img) on your device and select it
6) Select RECOVERY from the PARTITION list and swipe to flash
7) Go to Menu: Reboot recovery
If First time install
You can install with spft as described in following link BUT FIRST NEED unlock bootloader.
Instructions for Flash stock recovery or Custom recovery MEDIATEK devices only
You can also install with fastboot commands after unlocking bootloader.
****UNLOCKING BOOTLOADER WILL CAUSE WARNING ON SCREEN WHEN POWERING ON****
****WARNING WILL PAUSE THE BOOT PROCESS FOR % SECOND DELAY , Not big problem****
BOOTLOADER UNLOCK
How to Unlock Bootloader via Fastboot
1. Setup ADB and Fastboot on your PC.
2. Enable USB debugging and OEM Unlock on your Android device.
1). open settings
2). scroll to about phone
3). tap "Build number" 7 -8 times
4). go back, now you have new menu option"Developer options
5). open and make sure "off" switch at top is slid to right to turn on
5). slide switches for OEM unlocking and ADB debugging
6). Now connect usb cable from PC to Phone
7). phone should have popup window asking for authorization to connect with ADB
3. Connect your device to the PC with a USB cable.
4. Open a command window on your PC.
5. Boot your device into bootloader mode using the following command:
Code:
adb reboot bootloader
└ You may get a request to authorize USB debugging on the device, accept it.
6. Once your device is in bootloader mode, issue the following command to unlock bootloader:
Code:
fastboot oem unlock
You get a confirmation screen on your device. Press Volume Up button to highlight Yes and press Power button to select it.
This will begin bootloader unlocking process, which shouldn’t last more than couple of minutes.
7. Once bootloader is unlocked, your device will reboot into bootloader mode. You need to boot it into system now using the command below:
Code:
fastboot reboot
During reboot, your device will go through a factory reset and then finally boot into system.
RECOVERY INSTALL
1. make sure developer options is enabled
1). open settings
2). scroll to about phone
3). tap "Build number" 7 -8 times
4). go back, now you have new menu option"Developer options
5). open and make sure "off" switch at top is slid to right to turn on
5). slide switches for OEM unlocking and ADB debugging
6). Now connect usb cable from PC to Phone
7). phone should have popup window asking for authorization to connect with ADB
2. Reboot to bootloader
Code:
adb reboot bootloader
3. Test recovery works for your device
(example commands assume you have the 3.2.0 version of recovery downloaded to the desktop)
Code:
Fastboot boot Desktop/twrp-3.2.0-recovery.img
4. If recovery boots good, then return to bootloader and flash (commands work from in booted twrp)
These steps are what I find to be best order to prevent the stock rom from replacing the stock recovery on boot.
Code:
adb reboot bootloader
fastboot flash recovery Desktop/twrp-3.2.0-recovery.img
fastboot boot Desktop/twrp-3.2.0-recovery.img
adb wait-for-device
adb reboot recovery
ROOT
If your device haven't ROOT:
Thanks to @Chainfire for the file!
Rooting instructions: put the SuperSu...zip on sdcard. Go to TWRP and tap INSTALL. Search the zip file and select. Swipe to install. Reboot system.
Dowload: SuperSU V2.82
DOWNLOADS In Download Tab
SCATTER File
Stock boot ----- Stock recovery
TWRP 3.1.1 ------ TWRP 3.2.0 ------ TWPR 3.2.1 ------ TWPR 3.2.2-0 (based in stock V7.0.04.04_GENERIC 24-05-2018)
-----Added--TWRP 3.2.2-0(repacked)Has ro.secure=0; ro.adb.secure=0; to allow adb while data is wiped.
TWRP 3.2.3-0 [Has ro.secure=0; ro.adb.secure=0; to allow adb while data is wiped.] (based in stock V7.0.04.05_GENERIC 06-08-2018) download in post#2
Note:
After TWRP3.2.2 the partitions for the backup save have been modified to: /dev/block/platform/mtk-msdc.0/by-name/
So if you have a version older than TWRP3.2.2 you should copy the
Root [Internal Storage or MicroSD] / TWRP/ BACKUPS / VCIBIZMR7HT8GES8 / year-month-date-hour-minute-second_BLU_T0010UU_V70040x_GENERIC_dd-mm-yyyy
folder to the new one folder
Root [Internal Storage or MicroSD] / TWRP / year-month-date-hour-minute-second_BLU_T0010UU_V70040x_GENERIC_dd-mm-yyyy
of the version TWRP3.2.2 or last.
We've added the partition for internal storage if you want to create a backup of it. But keep in mind that the more files there are in the internal storage, the larger the size of the backup made and this will depend on your choice and how you can save it to other larger storage capacity.
So be more careful!
Contributors
@lopestom
@Dees_Troy
@teamwin
@vampirefo
Version Information
Status: Beta
Current Beta Version: 3.2.3-0-20181013
Beta Release Date: 2017-12-24
XDA:DevDB Information
Tank Xtreme Pro Recovery, Tool/Utility for all devices (see above for details)
Contributors
mrmazak, lopestom, vampirefo
Version Information
Status: Beta
Created 2017-12-08
Last Updated 2018-10-13

Instructions to unlock and relock bootloader
Instructions to unlock and relock bootloader soo... :silly:
https://youtu.be/5ZVW-XzPCXE
https://youtu.be/Zf6hMqGbC_4

With older version TWRP, does MTP work? I see you list it not working on 3.2.
MTP to me is more important than version of TWRP used.
Sent from my Tank Xtreme Pro using Tapatalk

vampirefo said:
With older version TWRP, does MTP work? I see you list it not working on 3.2.
MTP to me is more important than version of TWRP used.
Sent from my Tank Xtreme Pro using Tapatalk
Click to expand...
Click to collapse
No, mtp not working at all on this device. The recovery that I used to port older version is yours from life Max. Boh of these on this thread came from lopestom.
Suspect something in kernel, like touch on life Max was problem in kernel. As of last time I checked, sources we're not published from blue yet.

mrmazak said:
No, mtp not working at all on this device. The recovery that I used to port older version is yours from life Max. Boh of these on this thread came from lopestom.
Suspect something in kernel, like touch on life Max was problem in kernel. As of last time I checked, sources we're not published from blue yet.
Click to expand...
Click to collapse
Ok, thanks I will compile a recovery for Tank, see if I have any better luck with it.
I suspect it's the recovery looking for MTP in the wrong place, Android 6 and 7 access to MTP would be different.
Blu Life Max is Android 6, so MTP would be in platform, while tank is Android 7 so would be in virtual.
Sent from my Tank Xtreme Pro using Tapatalk

vampirefo said:
Ok, thanks I will compile a recovery for Tank, see if I have any better luck with it.
I suspect it's the recovery looking for MTP in the wrong place, Android 6 and 7 access to MTP would be different.
Blu Life Max is Android 6, so MTP would be in platform, while tank is Android 7 so would be in virtual.
Click to expand...
Click to collapse
@mrmazak tested some TWRP and we have same issue with driver mtp in PC/laptop like Indisponible driver so the device is recognized but cannot open mtp. If we boot ROM so that's recognizing and open.
I tried with libtwrpmtp.so from sbin folder: replacing from other, open to know if need more informations and compared with same lib name of Android 6 as I have mtp working..... So no luck!
Remember: TWRP3.1.1 and 3.2.0 from me is based in Android 7 Nougat TWRP base x32.
As I'm no good with programming to open libtwrpmtp.so to see if have or need specific info so... I hope that you can help better on it...
Congrats and enjoy...
Sent from my BLUBOO Xtouch using XDA Labs

lopestom said:
@mrmazak tested some TWRP and we have same issue with driver mtp in PC/laptop like Indisponible driver so the device is recognized but cannot open mtp. If we boot ROM so that's recognizing and open.
I tried with libtwrpmtp.so from sbin folder: replacing from other, open to know if need more informations and compared with same lib name of Android 6 as I have mtp working..... So no luck!
Remember: TWRP3.1.1 and 3.2.0 from me is based in Android 7 Nougat TWRP base x32.
As I'm no good with programming to open libtwrpmtp.so to see if have or need specific info so... I hope that you can help better on it...
Congrats and enjoy...
Sent from my BLUBOO Xtouch using XDA Labs
Click to expand...
Click to collapse
I don't know about your 3.2 recovery, mrmazak used my Blu Life Max recovery, I told that recovery to look in platform for MTP, that's why I suspect my Blu Life Max recovery is the problem.
If I am correct, just rebuilding a new recovery telling it to look in virtual for MTP should work, if I am wrong it won't, doesn't hurt to try.
Sent from my Tank Xtreme Pro using Tapatalk

vampirefo said:
I don't know about your 3.2 recovery, mrmazak used my Blu Life Max recovery, I told that recovery to look in platform for MTP, that's why I suspect my Blu Life Max recovery is the problem.
If I am correct, just rebuilding a new recovery telling it to look in virtual for MTP should work, if I am wrong it won't, doesn't hurt to try.
Sent from my Tank Xtreme Pro using Tapatalk
Click to expand...
Click to collapse
I assume you already looked, but, the recovery log shows mtp error , over and over again.
Code:
E:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] response write returned -1, errno: 5, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 22
pretty sure it happens with all versions

The stock boot img has "init.usb.configs.rc"
in this file it sets usb_gadget # for mtp.
there is nothing that I find similar in the twrp.
I am thinking to add this rc file to twrp and import it with the init.rc to see if it changes anything.
***UPDATE*** No change with adding this configfs file
Attached is a listing of all mentins of "mtp" in the stock boot.img ramdisk
this link is in Russian , but google translate helps.
posts #1354 and 1355 reference the same error I see in the recovery log. Also mention addressing the usb_gadget #
.

mrmazak said:
The stock boot img has "init.usb.configs.rc"
in this file it sets usb_gadget # for mtp.
there is nothing that I find similar in the twrp.
I am thinking to add this rc file to twrp and import it with the init.rc to see if it changes anything.
***UPDATE*** No change with adding this configfs file
Attached is a listing of all mentins of "mtp" in the stock boot.img ramdisk
this link is in Russian , but google translate helps.
posts #1354 and 1355 reference the same error I see in the recovery log. Also mention addressing the usb_gadget #
.
Click to expand...
Click to collapse
Oh, well if MTP doesn't work it doesn't work, I compiled my own today, removed MTP tab and just use Mount USB Storage instead, works fine for micro sdcard. I compiled mine using TWRP 8.1 source, and uploaded it to needrom.

vampirefo said:
Oh, well if MTP doesn't work it doesn't work, I compiled my own today, removed MTP tab and just use Mount USB Storage instead, works fine for micro sdcard. I compiled mine using TWRP 8.1 source, and uploaded it to needrom.
Click to expand...
Click to collapse
I just gave this a try, I have noticed something, could be intentional , not sure.
On your other recovery you could flash system as image, this one you cannot.

mrmazak said:
I just gave this a try, I have noticed something, could be intentional , not sure.
On your other recovery you could flash system as image, this one you cannot.
Click to expand...
Click to collapse
Correct something I don't use, that's controlled by recovery.fstab
just use this recovery.fstab if you want that option, unpack recovery and replace recovery.fstab

vampirefo said:
Correct something I don't use, that's controlled by recovery.fstab
just use this recovery.fstab if you want that option, unpack recovery and replace recovery.fstab
Click to expand...
Click to collapse
thanks, is it ok to add this version to the downloads of this thread?

mrmazak said:
thanks, is it ok to add this version to the downloads of this thread?
Click to expand...
Click to collapse
Thanks fine with me.
Sent from my Tank Xtreme Pro using Tapatalk

vampirefo said:
Thanks fine with me.
Sent from my Tank Xtreme Pro using Tapatalk
Click to expand...
Click to collapse
I've added you as contributor and added your version, with the fstab that has system_image and also cache enabled (because of an error message in recovery.log that stated could not mount cache)

sorry for asking,, can i use this recovery into blu tank xtreme 5.0??
im looking everywhere the method how to root blu tank xtreme 5.0 android 6

gabmika69 said:
sorry for asking,, can i use this recovery into blu tank xtreme 5.0??
im looking everywhere the method how to root blu tank xtreme 5.0 android 6
Click to expand...
Click to collapse
No!
Each device should have the own Custom Recovery.
Sent from my BLUBOO Xtouch using XDA Labs

Please HELP!
Was hung on boot with TWRP installed. Fixed the problem by installing SuperSU to unlock the bootloader. No help needed.

🗃️S4 Unified Collection & Guides📚

Welcome to S4 Unified Collection!
​STOCK ROM FIRMWARES
[Check my Guides for Installation]
Note: If you can't find the Firmware for your device from the link below, then it's not my fault. Android File Host informed me, they delete files with less population on downloads. I don't have these files anymore.
You can find the latest Stock ROM Firmware for your S4 variant below:
GT-I9295 (jactivelte): I9295XXSDQD6 / Build Date: 2017-04-20 / OS: Lollipop 5.0.1
GT-I9500 (ja3gxx): I9500XXUHQD1 / Build Date: 2017-04-25 / OS: Lollipop 5.0.1
GT-I9505 (jfltexx): I9505XXUHQK1 / Build Date: 2017-11-09 / OS: Lollipop 5.0.1
GT-I9505G (jgedlte): I9505GUEUDPF1 / Build Date: 2016-05-13 / OS: Lollipop 5.1.1
GT-I9506 (ks01lte): I9506XXUDRB1 / Build Date: 2018-02-15 / OS: Lollipop 5.0.1
GT-I9515 (jfvelte): I9515XXS1BQD2 / Build Date: 2017-04-17 / OS: Lollipop 5.0.1
GT-I9515L (jfvelte): I9515LUBU1BQF1 / Build Date: 2017-06-08 / OS: Lollipop 5.0.1
SCH-I545 (jfltevzw): VERIZON USERS: since your bootloader is locked, you must be on the VRUAMDK
SCH-I545L (jfltelra): I545LWWSGQA1 / Build Date: 2017-01-05 / OS: Lollipop 5.0.1
SCH-R970 (jflteusc): R970TYSGPL1 / Build Date: 2016-12-02 / OS: Lollipop 5.0.1
SCH-R970C (jfltecri): R970CVRUFND1 / Build Date: 2014-04-11 / OS: KitKat 4.4.2
SCH-R970X (jfltecsp): R970XWWSGQA1 / Build Date: 2017-01-05 / OS: Lollipop 5.0.1
SGH-I337 (jflteatt): AT&T USERS: since your bootloader is locked, you must be on the UCUAMDB or UCUAMDL
SGH-I337M (jftlecan): I337MVLSGQB1 / Build Date: 2017-02-09 / OS: Lollipop 5.0.1
SGH-M919 (jfltemo): M919UVSFQA1 / Build Date: 2017-01-04 / OS: KitKat 4.4.4
SM-S975L (TracFone-StraightTalk): S975LUDUANB1 / Build Date: 2014-02-04 / OS: Jelly Bean 4.3
SPH-L720 (jfltespr): L720VPSGPL1 / Build Date: 2016-12-20 / OS: Lollipop 5.0.1
MODEMS & BOOTLOADERS
[Check my Guides for Installation]
Note: If you can't find the Modem/Bootloader for your device from the link below, then it's not my fault. Android File Host informed me, they delete files with less population on downloads. I don't have these files anymore.
You can find the latest Bootloader & Modem for your S4 variant below:
GT-I9295 (jactivelte): I9295XXSDQD6 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
GT-I9500 (ja3gxx): I9500DXUHPB1 MODEM
GT-I9505 (jfltexx): I9505XXUHQK1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
GT-I9505G (jgedlte): I9505GUEUDPF1 MODEM
GT-I9506 (ks01lte): I9506XXUDRB1_I9506XXUDRA1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
GT-I9515 (jfvelte): I9515XXU1BQD2 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
GT-I9515L (jfvelte): I9515LUBU1BQF1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SCH-I545 (jfltevzw): VERIZON USERS: since your bootloader is locked, you must be on the VRUAMDK
SCH-I545L (jfltelra): I545LWWSGQA1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SCH-R970 (jflteusc): R970TYSGPL1 COMBINED BOOTLOADER & MODEM / BOOTLAODER - MODEM
SCH-R970C (jfltecri): R970CVRUFND1 COMBINED BOOTLAODER & MODEM / BOOTLOADER - MODEM
SCH-R970X (jfltecsp): R970XWWSGQA1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SGH-I337 (jflteatt): AT&T USERS: since your bootloader is locked, you must be on the UCUAMDB or UCUAMDL
SGH-I337M (jftlecan): I337MVLSGQB1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SGH-M919 (jfltemo): M919UVSFQA1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SM-S975L (TracFone-StraightTalk): S975LUDUANB1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SPH-L720 (jfltespr): L720VPSGPL1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
RECOMMENDED ROMS
Recommend ROMs for the variants below, are:
Official LineageOS / LineageOS microG, Official crDroid, Official DivestOS or any of JDCTeam ROMs with tags [LIVE] [STABLE] [DAILY]
GT-I9505 (jfltexx)
GT-I9505G (jgedlte)
GT-I9507 (jtfddxx)
GT-I9508 (jfltezm)
GT-I9515 (jfvelte)
GT-I9515L (jfvelte)
SCH-I545 (jfltevzw) VERIZON USERS: since your bootloader is locked, you must be on the VRUAMDK
SCH-I545L (jfltelra)
SCH-R970 - jflteusc
SCH-R970C (jfltecri)
SCH-R970X (jfltecsp)
SGH-I337 (jflteatt) AT&T USERS: since your bootloader is locked, you must be on the UCUAMDB or UCUAMDL
SGH-I337M (jftlecan)
SGH-M919 (jfltemo)
SM-S975L (TracFone-StraightTalk)
SPH-L720 (jfltespr)
Recommened ROMs for the variants below are:
GT-I9295 (jactivelte): Official LineageOS / LineageOS microG
GT-I9500 (ja3gxx): -
GT-I9506 (ks01lte): Unofficial LineageOS 20.0 or Unofficial crDroid
TWRP RECOVERIES
[Check my Guides for Installation]
The list below contains the variants which can use the latest Official Unified TWRP Recovery or Unofficial TWRP Recovery or OrangeFox Recovery:
GT-I9505 (jfltexx)
GT-I9505G (jgedlte)
GT-I9507 (jtfddxx)
GT-I9508 (jfltezm)
SCH-I545 (jfltevzw)
SCH-I545L (jfltelra)
SCH-R970 - jflteusc
SCH-R970C (jfltecri)DCTeam
SCH-R970X (jfltecsp)
SGH-I337M (jftlecan)
SGH-M919 (jfltemo)
SM-S975L (TracFone-StraightTalk)
SPH-L720 (jfltespr)
The list below contains the variants which need a specific TWRP Recovery version:
GT-I9295 (jactivelte): Official TWRP Recovery
GT-I9500 (ja3gxx): Official TWRP Recovery
GT-I9506 (ks01lte): Official TWRP Recovery / TWRP- 3.6.0_9-0 or OrangeFox Recovery Project
GT-I9515 (jfvelte): Official TWRP Recovery
GT-I9515L (jfvelte): Official TWRP Recovery
SGH-I337 (jflteatt): TWRP Recovery Locki Patched by mattgyver
GAPPS & microG
GApps
Note: You should always use the smallest package of GApps, be sure you have selected Platform: ARM and the proper Android version of the ROM you are going to flash. If the ROM you want to flash include GApps, no need to download and flash any GApps at all.
Most of the GApps have also a config. file which can be used to to configure your installation the way you like. You can skip any Package that you don't want to be part of your installation. For more infos about that, read the instructions of the GApps you chose or search in Google.
MindTheGapps
BiTGApps
NikGApps (Only Core version)
Open GApps / Open GApps Unofficial A12L
LiteGapps
microG
If you don't want to use Google Play Services and general move away from Google, microG and its variants is an open source alternative which replace these services.
NanoDroid
MinMicroG
BiTGApps microG
microG
MAGISK ROOT
You can check my Guides for installation.
Magisk (APK)
Magisk.zip (Flashable Zip)
Uninstall.zip (Flashable Zip)
Magisk Canary (APK)
Magisk Delta
FoxMagiskModuleManager (This app replace the official magisk module repository since no longer available)
Momo (You can use this app too check if any modifications related Magisk are detected or not)
Universal SafetyNet Fix by kdrag0n [Video Guide]
Shamiko (Hide Root from apps) [Guide]
Note: If your apps detect root, follow this Guide (or this) to pass SafetyNet and have certified Play Store. [YouTube Video Guide]. For Microsoft Intune and other microsoft apps, check this guide.
PIT FILES
Note: If you messed the partitions of your device, you can fix it by simply flashing the PIT FILE for your variant via Odin in the PIT TAB.
The list below contains PIT FILES for some variants:
GT-I9500 (ja3gxx) PIT FILE
GT-I9505 (jftlexx) PIT FILE
SAMSUNG USB DRIVER
Note: If you have a problem while you connect the device to your PC and PC can't recognize it, you may miss the Samsung USB DRIVER. To fix follow these steps:
1. Download SAMSUNG USB DRIVER.
2. Unzip it and install it to your PC.
3. Connect your device and done! Now should be ok.
ODIN
You can download ODIN HERE. Recommened version is Odin 3.12.3
ULTIMATE COLLECTIONS & GUIDES (APPS)
Check the Privacy & Security section in my Guides.
If for some reason you can't find/install an app on Google Play Store due country restrictions or anything, you can sideload the app from APKMirror.
Android Ultimate Collection & Guides
Windows Ultimate Collection & Guides
ReVanced & ReVanced Extended - Guides & Useful Links
UNIVERSAL ANDROID DEBLOATER
Universal Android Debloater
S4 UNIFIED COLLECTION MIRROR
S4 Unified Collection AFH Mirror
DISCORD SERVER
Please verify yourself at #welcome channel. Read #FAQ channel.
Discord Server
JDCTEAM UNIVERSE
Here you can find the work of JDCTeam over the years for our S4 device!
Scroll Down to check the Guides
​

Welcome to S4 Unfied Guides!
!DISCLAIMER!
Most people I know (including myself) who used my Guides and steps, did that with success many times. If you don't follow exactly the steps or you do a mistake during the process, I do not take any responsibility for any unexpected results or damage that may happen. However I am here to help if something goes wrong, just ask in the thread.​
INSTALL BOOTLOADER & MODEM
You can flash Bootloader & Modem with two methods:
Combined: [Recommended]
1. Download Odin and the COMBINED BOOTLOADER _MODEM.tar for your variant to your PC. [You can find everything in my Collection]
2. Reboot your device to Download Mode by pressing Power Button + Vol.down + Home Button and run Odin from your PC as administrator.
3. Put the COMBINED BOOTLOADER_MODEM.tar to AP section, untick Auto-Reboot, flash!
4. When It's done, reboot your device by pressing Power Button for couple of seconds.
Seperate:
1. Download Odin, the BOOTLOADER.tar and MODEM .tar for your variant to your PC. [You can find everything in my Collection]
2. Reboot your device to Download Mode by pressing Power Button + Vol.down + Home Button and run Odin from your PC as administrator
3. Put the BOOTLOADER to BL section and MODEM to CP section, untick Auto-Reboot and flash!
4. When It's done, reboot your device by pressing Power Button for couple of seconds.
Notes:
Check what version of Modem and Bootloader you have with apps like Device Info HW.
If Modem & Bootloader didn't changed to the version you wanted, do the same steps again with the method you have selected.
If for some reason Odin failed to flash, make sure your run Odin as adminstrator, try to change USB Port in your PC and don't move the cable during flash. Also if you have Odin and the files on an External hard drive, move Odin and all the files you want to flash, into one folder to your Main Drive for example C: drive.
For Stock Rom to have your WiFi working you need to have the same version of Modem/BL as your Firmware. For example if you have QK1 Stock ROM then you need to have QK1 Modem/Bootloader. On Custom ROMs doesn't matter. You can have any Modem/BL of your variant you want but recommend is always the latest.
INSTALL TWRP RECOVERY
ODIN Method (No TWRP Recovery currently installed)
1. Download Odin and the .tar file of the TWRP to your PC. [You can find everything in my Collection]
2. Reboot to Download Mode by pressing Power Button + Vol.Down + Home Button.
3. Run Odin as adminstrator > connect your device to PC > put the .tar file of TWRP in AP section > untick Auto-Reboot in options and flash.
4. Done! Restart to TWRP Recovery. (power button+vol.up+home button)
Recovery Method (TWRP Recovery already installed)
1. Download .img of TWRP Recovery. [You can find everything in my Collection]
2. Reboot to Recovery by holding Power Button + Volume Up (+).
3. Press Install Image.
4. Locate the recovery.img you recently downloaded.
5. Select it and choose the option Recovery and Flash.
6. Go back and Reboot to Recovery.
7. Done! Your new recovery should be installed.
CLEAN INSTALL CUSTOM ROM
Note: If you have issues after flash check possible solutions here:
Check integrity of all downloads (compare checksums), do the downloads again.
Make sure you Wiped everything and Formated Data (format data not just wipe) except external SDCard and USB OTG.
Flash only the ROM (without GApps and Magisk) and check if the problem persists. If yes, flash another ROM.
Try other GApps package.
If nothing helps, go back to stock and start from scratch.
Note: You can also Flash Custom ROM using ADB sideload Method.
1. Backup all your data to PC or to external SDCard. [All your data into Internal Storage will be lost on step 7 while Formating Data or Wiping Internal Storage]
2. Install the latest Bootloader & Modem for your S4 variant. [Read the Install Bootloader & Modem Guide above]
3. Download: [You can find everything in my Collection]
TWRP Recovery.
Custom ROM of your choice.
GApps (be sure you have selected Platform: ARM and the proper Android version of the ROM you are going to flash) if the ROM you are going to flash does not include. [Optional]
Magisk Root. [Optional]
4. Move all these files in one folder to your PC or to External SDCard if you have one.
5. Install TWRP Recovery. [Read the Install Custom Recovery Guide above]
6. Turn off your device and Reboot to Recovery Power Button + Volume Up (+)
7. Installation:
Steps without external SDCard:
Select Wipe > Advanced Wipe
Select Dalvik / ART Cache, System, Data, Internal Storage, Cache and then Swipe to Wipe. [All your data into Internal Storage will be lost]
Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
Connect your device to PC while you are on TWRP and transfer into Internal Storage, the ROM, GApps etc. and the files you want to flash.
Flash ROM > GApps [Optional]
Reboot Enjoy!
[Optional] If you want to root, reboot once again to TWRP Recovery and flash Magisk (you need to download it again if you previously had it in Internal Storage) then reboot to system and enjoy!
Steps with external SDCard:
go to Advanced > File Manager > External_SD and delete all folders in ur ext sd card (For example you should delete: Android, .android_secure, LOST.DIR, DCIM, etc) except your personal files/folders and the folder with your custom ROM/Gapps/Magisk/DFE you want to flash.
Each app on your phone with the WRITE_EXTERNAL_STORAGE permission may create files or folders in ur sdcard. Most of these folders have once been created by one of these apps and many of them may be deleted with a few exceptions (e.g. Android, .data, .android_secure, these contain important system or app data like a game's downloaded content):
.android_secure: apps installed and then moved to sdcard
Android: app data/cache
data: app data
.estrongs: ES file manager
LOST.DIR: sort of trash folder (collects recovered files after phone crashes)
DCIM: phone gallery's photos and previews
OTA-update: Over The Air update service
ppy_cross: an unknown third-party app's data.
So I recommend to delete them so you can put your phone/sdcard in a clean state and is guaranteed to be able to re-create these folders.
Select Advanced Wipe
Select Dalvik / ART Cache, System, Data, Internal Storage, Cache and then Swipe to Wipe. [All your data into Internal Storage will be lost]
Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
Flash ROM > GApps [Optional]
Reboot Enjoy!
[Optional] If you want to root, reboot once again to TWRP Recovery and flash Magisk then reboot to system and enjoy!
DIRTY INSTALL YOUR CUSTOM ROM
Note: Before you start flashing, keep in mind the ROM you dirty flashing MUST be the same with the one you have already installed.
1. Make a full nandroid backup, just in case something goes wrong. You can use TWRP to do that. (TWRP > Backup > Select everything) [Optional]
2. Remove all Magisk modules. [Optional]
3. Reboot to TWRP and Wipe Dalvik / ART Cache, System and Cache.
4. Flash the ROM > GApps [Optional] > Magisk [Optional]
5. Reboot and Enjoy!
I've skipped some explanations, because if you are going to dirty flash, you already know for example how to boot to TWRP.
CLEAN INSTALL OFFICIAL STOCK ROM
Note: For Stock Rom to have your WiFi working you need to have the same version of Modem/BL as your Firmware. For example if you have QK1 Stock ROM then you need to have QK1 Modem/Bootloader. On Custom ROMs doesn't matter. You can have any Modem/BL of your variant you want but recommend is always the latest.
1. Download the latest stock ROM (Firmware), Modem & Bootloader for your variant, TWRP Recovery (.tar file) and ODIN to your PC. [You can find everything in my Collection]
2. Install TWRP Recovery [Read the Install Custom Recovery Guide above]
3. Reboot to TWRP Recovery and Select Wipe > Advanced Wipe
4. Select Dalvik / ART Cache, System, Data, Cache, External SDCard (if you have) and then Swipe to Wipe.
5. Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
6. Reboot to Download Mode Power by pressing Power Button + Vol.Down + Home Button
7. Run Odin as adminstrator from your PC > connect your device > put the Stock Rom (Firmware) file to AP section and flash it!
8. Let the ROM boot.
9. Install the same version of Bootloader & Modem as your Firmware. [Read the Install Bootloader & Modem Guide above]
10. Enjoy!
BACKUP & RESTORE ROM (NANDROID BACKUP)
Check this Youtube Video to see the process in action.
Backup:
1. Reboot to Recovery (Power Button + Volume Up (+))
2. Choose Backup and Select Boot > System > Data (excl. storage)
3. Select Storage and choose SDcard if you have one otherwise let it on Internal Storage.
4. Swipe to Backup.
5. Done!
Restore:
1. Reboot to Recovery. (Power Button + Volume Up (+))
2. Select Wipe > Advanced Wipe.
3. Select Dalvik / ART Cache, System, Data, Cache and then Swipe to Wipe.
4. Press Home Button to go back and Select Restore.
5. Select the backup file with the ROM and make sure Boot, System and Data (excl. storage) are selected.
6. Select Swipe to Restore and when completed Reboot to System.
7. Done!
MAGISK ROOT
The easiest way to root your device is via Magisk, it should work in all ROMs, Stock and Customs.
Install Magisk:
1. Install latest TWRP Recovery. [Read the Install Custom Recovery Guide above]​2. Download the Magisk [You can find it in my Collection]​3. Reboot to TWRP Recovery by pressing Power Button + Volume Up (+) and flash it.​4. Reboot and check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK. [You can find it in my Collection]​Note#1: From Official TWRP Recovery 3.5.1 and onward (and other recoveries based on that), Magisk.apk can be flashed as apk without the need of rename it to .zip. So you can simply flash the Magisk.apk in TWRP.​Manually Creation of Flashable Zip:​Download the latest Magisk APK and rename the Magisk.apk → Magisk..zip.​​Note#2: If your bank apps detect root, follow this Guide.​
Uninstall Magisk:
Flash the Uninstall.zip in TWRP Recovery and reboot. [You can find it my Collection]
If Magisk App isn’t uninstalled automatically, manually uninstall the app.
Manually creation of Flashable Uninstall Zip:
Download the latest Magisk APK and rename the Magisk.apk → uninstall.zip
Uninstall Magisk directly through the Magisk app. Simply press the Uninstall button.
Note: If your apps detect root, follow this Guide (or this) to pass SafetyNet and have certified Play Store. [YouTube Video Guide]
MIXER_PATHS (INCREASE VOLUME VALUES)
Check HERE and HERE.
HOW TO TAKE LOGS
How to take logs on Android
SCREEN RETENTION FIX
Screen Retention FIx: If you have an issue with screen retention apply this configuration to your device ROM.
BATTERY TIPS
Samsung Galaxy S4 Battery Model: B600BE
Battery Replacment (Video)
Advanced Guide
Simple Battery & Charging Tips
Improve your SOT
Battery Calibration
Method 1
Steps:
1. Discharge your phone fully until it turns itself off.
2. Turn it on again and let it turn itself off.
3. Plug your phone into a charger and, without turning it on, let it charge until the on-screen or LED indicator says 100 percent.
4. Turn your phone on. It's likely that the battery indicator won't say 100 percent, so plug the charger back in (leave your phone on) and continue charging until it says 100 percent on-screen as well.
5. Unplug your phone and restart it. If it doesn't say 100 percent, plug the charger back in until it says 100 percent on screen.
6. Repeat this cycle until it says 100 percent (or as close as you think it's going to get) when you start it up without it being plugged in.
Method 2
Notes: It won't dramatically extend battery life, but it will give your old battery at least 30 minutes additional run time.
Steps:
1. Get "GSam or Ampere" from the Google Play Store.
2. Launch the app and fully charge your phone. (Important: Only proceed with the calibration when the word "Full" appears in GSam or Ampere.)
3. While your phone is still connected to the cable reboot your phone to recovery mode, open file manager and navigate to "/data/system" and delete "batterystats.bin," "batterystats-checkin.bin," and "batterystats-daily.xml."
4. Reboot your phone (while it is still plugged in) and charge it until it reads "full" on GSam or Ampere.
5. Unplug the cable and use your phone normally until it shuts down (0 percent )
6. Charge your phone to 100% while it is turned off.
7. Boot into os and plug in your phone and charge it until it says "full" on the GSam or Ampere.
8. Unplug and have fun!
Battery Capacity Health
Notes:
1) Before checking the battery health, charge the device to 100%.
2) Check charge counter values and consider first 4 digits from left as your battery capacity in mAh. And check charge counter. (Charge counter/level)*100 is the battery capacity.
To find battery capacity in Windows:
Enable Developer options in your device.
Enable USB Debugging in your device.
Conect your device to PC and give permissions.
Open Minimal ADB (run cmd.exe) or Platform tools.
Type "adb shell dumpsys battery" command in Minimal ADB or Platform tools.
To find battery capacity in Android (Terminal) - Root needed:
Download an android terminal app like Termux,
Open terminal and type: cat/sys/class/power_supply/battery/charge_full
Overheating
Following reasons will lead to device heating issue:
During the initial setup after purchase or when restoring data.
Downloading large files.
Using apps that require more power or using apps for extended periods such as:
Playing high-quality games for long time.
Recording videos for extended periods.
Streaming videos while using the maximum brightness setting.
Using the Screen Mirroring / Smart View feature (connecting mobile to a TV).
While multitasking or when running many apps in the background i.e:
Using Multi window.
Updating or installing apps while recording videos.
Downloading large files during a video call.
Recording videos while using a navigation app.
Large amount of data for syncing with the cloud, email, or other accounts.
Exposing device under sunlight when temperature is high around you.
Extensive usage of mobile hotspot and tethering feature.
Using device in areas with weak signals or no reception or in roaming network.
Charging the battery with a damaged / unapproved USB cable.
Device's multipurpose jack is damaged or exposed to foreign materials, such as liquid, dust, metal powder, and pencil lead.
Solution:
Turn off Wi-fi, GPS , bluetooth and other connectivity options when not in use by dragging the notification panel.
Decrease screen brightness.
Close background running applications.
Too many applications installed in device may result in device heating since their corresponding process will keep on running in background. It is advised to uninstall un-necessary apps if not using them.
Avoid using apps like GPS, data dependent apps or graphic intensive games for longer duration since they require more energy to function, causing device to heat.
It is advised not to use device while charging as it may cause the device to over heat.
General:
DO:
Use manual brightness or dim the screen.
Turn off notifications for apps you don't use. Better still, delete/disable the apps entirely if you don't need them.
Enable battery or power saving mode when you want to extend your battery life.
Use the power adapter that came with your phone. Other chargers can charge slowly/faster but they can also damage your phone or battery.
Turn off bluetooth, location tracking, and Wi-Fi (unless you are actively using it)
Turn off print services from bluetooth connection preferences.
Avoid extremes of heat and cold. If your phone gets very hot or cold it can strain the battery and shorten it's lifespan.
DON'T:
Have Bluetooth or Wi-Fi turned on constantly.
Leave apps running in the background. Instead restrict background usage off apps that you don't need running.
Push email means your device is always listening for new email which drains alot of battery.
Drain your phone battery all the way to 0% or charging it all the way to 100%. Keep it between 20% - 90% for longer battery lifespan.
The more advanced the graphics and animations are (games, videos, photos, animations), the harder the processor and graphics chip in your smartphone have to work. More activity means more battery use.
PRIVACY & SECURITY
Some useful links:
All about Privacy & Security at Privacy Guides.
Electronic Frontier Foundation.
PrivacyTests: Open-source tests of web browsers privacy.
Check if your email address or your phone number is in a data breach at Have I been Pwned & at Firefox Monitor.
Test your browser to see how well you are protected from tracking and fingerprinting at Cover Your Tracks by EFF and at Bromite fingerprint mitigations tests.
WebRTC IP Leak Test. WebRTC is a new communication protocol that relies on JavaScript that can leak your actual IP address from behind your VPN. You can find more infos how to disable it at Privacy Guides in browsers section.
Ad Block Tester is a free service on the Internet to evaluate content blocking solutions. It is not designed to be a benchmark, but it reveals the level of blocking against a set of hosts that are very popular.
Check on AM I FLoCed? by EFF if your your Chrome browser has been turned into a guinea pig for Federated Learning of Cohorts or FLoC, Google’s latest targeted advertising experiment.
How to block ads on Android.
εxodus: εxodus analyzes Android applications in order to list the embedded trackers and ads.
Spyware Watchdog Article Catalog: A catalog which determinate under tests and tracking if an app is spyware and what data it collects.
CryptPad: CryptPad is built to enable collaboration. It synchronizes changes to documents in real time. Because all data is encrypted, the service and its administrators have no way of seeing the content being edited and stored.
PrivateBin: PrivateBin is a minimalist, open-source online pastebin where the server has zero knowledge of pasted data. Data is encrypted/decrypted in the browser using 256-bit AES. It is the improved version of ZeroBin.
ShutUP10++ , Privacy.Sexy: Disable major tracking features of Windows.
General:
Always prefer Open Source or well popular Programs, Apps, ROMs, Kernels & Stuff.
Open Source doesn't mean it's 100% safe but it's unlikely to have something suspicious, since you and other users can check the code in GitHub or in any other code hosting platform the "stuff" is hosted. You can also find and use FOSS apps at Droid-ify.
Prefer ROMs & Kernels with SELinux Enforcing. You can find informations here.
Always download and install Apps, Programs, ROMs & Stuff from official sources and do not use redirection links from different sites. Google is your friend to find the official source of the stuff you want.
Always check the permissions an app requires, before download and install it to your device. If an app ask for permissions which has nothing to do with the app functionality then it's should be reconsider or ask the developer why these permissions needed.
You can also check if the app includes trackers and ads with εxodus.
If you want to avoid Google and Play Store (De-Google), you can choose a ROM without GApps preinstalled like LineageOS and use Droid-ify client which is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device. Note that not all apps from Play Store will be available in Droid-ify or F-Droid. Only Open Source projects. You can find alternatives though.
Alternative you can use LineageOS for microG or any ROM which support signature spoofing and can support microG and use Aurora Store.
For Windows use the default Windows Defender & Malwarebytes to scan your files whenever you want (Prefered before open or install them). Also use the addon/extension uBlock Origin in your Browser. These should be enough for normal users. You can also use the tool ShutUp10++ or Privacy.Sexy to disable major tracking features of Windows.
For Android Do not use any antivirus - antimalware since it's useless, just check what apps and from where you installing.
Always verify the source of addons/extensions in your browser. Avoid installing random and unpopular addons/extensions. Keep it minimal and clean, so browser can be fast and safe, no need bunch of extensions.
If you are using VPN, always check the terms and rules of the provider. Avoid random VPN Services.
Recommended VPN Services.
Using a VPN will not keep your browsing habits anonymous, nor will it add additional security to non-secure (HTTP) traffic.
Recommended is to encrypt your data/files always before uploading them to cloud with tools like Cryptomator.
Always use unique and strong passwords for each of your accounts.
Use awarded open source Password Managers like KeePass or KeePassXC for Desktop and KeePassDX for Android to manage your passwords and have them with you safe, encrypted and secure. Must be noted you can use the same database file between these programs.
Always enable 2 Step Authentication wherever is available for your accounts.
You can use apps like Aegis Authenticator.
Do not open or click on links attached in unknown emails or SMS you may get. Always check the address of the email or the number of SMS and verify it's legit from the official source.
Create and use "burned" email for accounts/sites you have concerns but you definitely want to try them. Do not use your personal or business email. You can also create and use email aliases of your email with SimpleLogin which is open source and awesome service.
DISCORD SERVER
Please verify yourself at #welcome channel. Read #FAQ channel.
Discord Server

Changelog
Note: Changes in Collection & Guides happens in real time. The date I post these Changelogs is just a sum up since I can't post all the changes the time that happening to avoid spamming the thread. So you can always consider the Collection & Guides Up-to-Date. However, I may announce some big changes in posts before I include them in the Changelogs.​
LATEST
Update: 18/01/2023
Changelog
ARCHIVED
Update: 29/10/2022
Changelog
Update: 01/07/2022
Changelog
Update: 07/05/2022
Changelog
Update: 01/04/2022
Changelog
Update: 28/02/2022
Changelog
Update: 04/02/2022
Changelog
Update: 23/12/2021
Changelog
Update: 01/10/2021
Changelog
Update: 31/08/2021
Changelog
Update: 01/05/2021
Changelog
Update: 19/04/2021
Changelog
Update: 27/02/2021
Changelog
Update: 28/01/2021
Initial Release

Hi guys,
I can't manage to install the Bootloader & Modem via Odin on my phone.
Does the phone need to be already rooted in order to install the B&M?
Attached is also the capture I took when rebooting the phone in Download mode.
I selected "reboot to bootloader" in order to install the B&M, because otherwise Odin won't detect that the phone is connected to the PC. Probably I'm doing something wrong.
Any help will be very much appreciated.
Thanks in advance.
{
"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"
}

R_A_N_D_Y said:
Does the phone need to be already rooted in order to install the B&M?
Click to expand...
Click to collapse
I'n not 100% sure, but I think no
R_A_N_D_Y said:
Attached is also the capture I took when rebooting the phone in Download mode.
Click to expand...
Click to collapse
The picture shows your device in recovery
R_A_N_D_Y said:
I selected "reboot to bootloader"
Click to expand...
Click to collapse
How did you do that? I'm not aware of such a reboot option.
You should boot into download mode (see above for how to). It should look like attached picture 1
In Odin, before you start flashing, you should see a success message "<ID ... Added!! If not, you should check if you have all required driver installed for your device.

pocketrule said:
I'n not 100% sure, but I think no
The picture shows your device in recovery
How did you do that? I'm not aware of such a reboot option.
You should boot into download mode (see above for how to). It should look like attached picture 1
In Odin, before you start flashing, you should see a success message "<ID ... Added!! If not, you should check if you have all required driver installed for your device.
View attachment 5212215View attachment 5212217
Click to expand...
Click to collapse
Thank you very much !

R_A_N_D_Y said:
Hi guys,
I can't manage to install the Bootloader & Modem via Odin on my phone.
Does the phone need to be already rooted in order to install the B&M?
Attached is also the capture I took when rebooting the phone in Download mode.
I selected "reboot to bootloader" in order to install the B&M, because otherwise Odin won't detect that the phone is connected to the PC. Probably I'm doing something wrong.
Any help will be very much appreciated.
Thanks in advance.
Click to expand...
Click to collapse
No need root.
Download and install the Samsung USB Drivers in your PC. (You can find it in my collection)
Download the Combined Bootloader & Modem for your variant from my collection.
Turn off your device.
Reboot your device to Download Mode by pressing Power Button + Vol.down + Home Button and run Odin from your PC as administrator.
Put the COMBINED BOOTLOADER_MODEM.tar to AP section, untick Auto-Reboot in options and flash!
When It's done, reboot your device by pressing Power Button for couple of seconds.

New Update:
Changelog:
Added Changelog Tracking at #3 post
Added Privacy & Security section in Guides.
Added a Note to check Privacy & Security Guide at Useful Apps section in Collection.
Added Flashable Zips for Install & Uninstall Magisk in Collection.
Updated the Magisk Guide and added Flashable Zip method.
Reordered the sections in Guides.

Hi Retrial, first of all this is a really useful post thank you so much!
I just bought a brand new S4 GT-I9505 and I used the latest TWRP in your post wich is twrp-3.5.1_9-0-jflte.img.tar for flashing lineage-17.1-20210116-UNOFFICIAL-jflte.zip and I have some question if you are so kind to aswer me:
I want to update the firmware so I downloaded the last one for Italy from Updato.com which is I9505XXUHPK2 (Genuary 2017) and I would like to know if is a good idea to flash it with Odin and if I have to fresh re-installing Lineage. Then I would like to know if after updating the firmware I can update only XXUHQC1_BOOTLOADER and XXUHQC1_COMBINED which are the international versions and obviously the most recent versions.
Do you think is possible? Thanks in advance. Kind Regards

hermes127 said:
Hi Retrial, first of all this is a really useful post thank you so much!
I just bought a brand new S4 GT-I9505 and I used the latest TWRP in your post wich is twrp-3.5.1_9-0-jflte.img.tar for flashing lineage-17.1-20210116-UNOFFICIAL-jflte.zip and I have some question if you are so kind to aswer me:
I want to update the firmware so I downloaded the last one for Italy from Updato.com which is I9505XXUHPK2 (Genuary 2017) and I would like to know if is a good idea to flash it with Odin and if I have to fresh re-installing Lineage. Then I would like to know if after updating the firmware I can update only XXUHQC1_BOOTLOADER and XXUHQC1_COMBINED which are the international versions and obviously the most recent versions.
Do you think is possible? Thanks in advance. Kind Regards
Click to expand...
Click to collapse
Hello,
If you flash firmware u need to reflash lineageos from start along with twrp. U can only do it via Odin.
Btw use the latest for your variant from my collection. Doesn't matter the country.
Flashing firmware=flashing stock rom. Why u want to do that if u are already in los?
You can flash bootloader and modem seperate yes (but I recommend to use my combined .tar which include both of them), without the need to flash everything again. Just go to Odin and flash the combined .tar I have made to AP. Once again, all the latest versions are included in my collection, doesn't matter the country so just use them.
All the infos and steps you need are in my collection and guides. Let me know if you have more questions.

Retrial said:
Flashing firmware=flashing stock rom. Why u want to do that if u are already in los?
Click to expand...
Click to collapse
Hi thanks for your fast response! I want to flash an updated firmware because my S4 GT-I9505 is new and probably from an old stock so the firmware is for sure the old one (2013-2014) ,right now in lineage os in setting/info I can't see the current version of baseband. I don't care if I have to re-install Lineage and the recovery, I had to do it before installing Lineage, I know I forgot it... but I wanted just to know if is possible to do now without breaking something. Now you say that it doesn't make sense and that is better to just flash your combined Modem and Bottloader package, is it correct? What's your advice: installing your last complete firmware or just the combined Bootloader and Modem package? I red somewhere in this forum that it's better to update the firmware before installing lineage so I wanted to do the installation again in the right way. Sorry if it's an annoying question I'm not an expert and I want just to be sure. Thank you so much for your support.

hermes127 said:
Hi thanks for your fast response! I want to flash an updated firmware because my S4 GT-I9505 is new and probably from an old stock so the firmware is for sure the old one (2013-2014) ,right now in lineage os in setting/info I can't see the current version of baseband. I don't care if I have to re-install Lineage and the recovery, I had to do it before installing Lineage, I know I forgot it... but I wanted just to know if is possible to do now without breaking something. Now you say that it doesn't make sense and that is better to just flash your combined Modem and Bottloader package, is it correct? What's your advice: installing your last complete firmware or just the combined Bootloader and Modem package? I red somewhere in this forum that it's better to update the firmware before installing lineage so I wanted to do the installation again in the right way. Sorry if it's an annoying question I'm not an expert and I want just to be sure. Thank you so much for your support.
Click to expand...
Click to collapse
Just follow what Retrial said; flashing his combo-file will accomplish what you want. Starting from scratch like you wanna do isn't any better.
I flashed bootloaders and modems so often, I can't even remember. Flashing stock firmware? Maybe once!

hermes127 said:
Hi thanks for your fast response! I want to flash an updated firmware because my S4 GT-I9505 is new and probably from an old stock so the firmware is for sure the old one (2013-2014) ,right now in lineage os in setting/info I can't see the current version of baseband. I don't care if I have to re-install Lineage and the recovery, I had to do it before installing Lineage, I know I forgot it... but I wanted just to know if is possible to do now without breaking something. Now you say that it doesn't make sense and that is better to just flash your combined Modem and Bottloader package, is it correct? What's your advice: installing your last complete firmware or just the combined Bootloader and Modem package? I red somewhere in this forum that it's better to update the firmware before installing lineage so I wanted to do the installation again in the right way. Sorry if it's an annoying question I'm not an expert and I want just to be sure. Thank you so much for your support.
Click to expand...
Click to collapse
Firmware=Stock Samsung ROM. Firmware does not include Modem & Bootloader. So even if u flash Firmware u have to also flash Bootloader & Modem.
Now you say that u are on lineageos, I don't know what version you are but you can flash via Odin the combined .tar file which include Bootloader & Modem and then clean install via TWRP the latest LineageOS along with latest GApps if you use.
If you want to start from scratch-fresh then follow my Guides: "Clean Install Official Stock ROM" and then the guide "Clean Install Custom ROM".
With few words: go to TWRP wipe everything, the connect ur device to PC and flash via Odin the latest Firmware (stock ROM). Let it boot and then flash via Odin the latest Bootloader & Modem. Then flash TWRP and clean install the latest LineageOS with GApps (optional).
Everything you need is on my collection and all steps in my guides. Since u have i9505 variant you need the latest Firmware/Modem & Bootloader which is I9505XXUHQK1.
Let me know how it goes or if you have any other questions.

Retrial said:
Flashing firmware=flashing stock rom. Why u want to do that if u are already in los?
Click to expand...
Click to collapse
Retrial said:
Firmware=Stock Samsung ROM. Firmware does not include Modem & Bootloader. So even if u flash Firmware u have to also flash Bootloader & Modem.
Now you say that u are on lineageos, I don't know what version you are but you can flash via Odin the combined .tar file which include Bootloader & Modem and then clean install via TWRP the latest LineageOS along with latest GApps if you use.
If you want to start from scratch-fresh then follow my Guides: "Clean Install Official Stock ROM" and then the guide "Clean Install Custom ROM".
With few words: go to TWRP wipe everything, the connect ur device to PC and flash via Odin the latest Firmware (stock ROM). Let it boot and then flash via Odin the latest Bootloader & Modem. Then flash TWRP and clean install the latest LineageOS with GApps (optional).
Everything you need is on my collection and all steps in my guides. Since u have i9505 variant you need the latest Firmware/Modem & Bootloader which is I9505XXUHQK1.
Let me know how it goes or if you have any other questions.
Click to expand...
Click to collapse
Wow your instructions are absolutely detailed and useful, thank you so much Retrial for your support.! I'll opt for the "start from scratch-fresh" install by following your guides. If I can take advantage of your competence I would like to ask you just one last advice: I switched to Lineage OS for privacy reasons (I don't like google so I don't need GApps) and I also use it for sharing internet to my MacBook Pro with USB tethering (not wifi tethering which is not safe for privacy) so do you think that the Optimized Lineage OS (Android 10) version from JDCTeam is the right version for me? May I use the Android 11 version? Probably I'm asking you to much things and I can understand if you can't answer me, you have been really kind and I really appreciated your help. Anyway I'll post here my experience with "start from scratch-fresh instal" .

Anything for the AT&T S4 Active (+) variant?

hermes127 said:
Wow your instructions are absolutely detailed and useful, thank you so much Retrial for your support.! I'll opt for the "start from scratch-fresh" install by following your guides. If I can take advantage of your competence I would like to ask you just one last advice: I switched to Lineage OS for privacy reasons (I don't like google so I don't need GApps) and I also use it for sharing internet to my MacBook Pro with USB tethering (not wifi tethering which is not safe for privacy) so do you think that the Optimized Lineage OS (Android 10) version from JDCTeam is the right version for me? May I use the Android 11 version? Probably I'm asking you to much things and I can understand if you can't answer me, you have been really kind and I really appreciated your help. Anyway I'll post here my experience with "start from scratch-fresh instal" .
Click to expand...
Click to collapse
Don't worry mate, ask whatever you want. I will help if I can.
Optimized LineageOS 10 is great but it's EOL (end of life). Optimized LineageOS 11 is also great and it's currently under development.
But since you are looking for privacy & security it's better to use Official LOS with guarantee monthly security patches cause lately optimized los stays a bit behind on updates. (Dev is busy) Soon official 11 will also be released.

blackhawk said:
Anything for the AT&T S4 Active (+) variant?
Click to expand...
Click to collapse
I think ur variant has locked bootloader so I don't know if anything exist.

Retrial said:
I think ur variant has locked bootloader so I don't know if anything exist.
Click to expand...
Click to collapse
Thank you. If you become aware of any work arounds please let me know.
It's a phone that is expendable now

blackhawk said:
Thank you. If you become aware of any work arounds please let me know.
It's a phone that is expendable now
Click to expand...
Click to collapse
I know there is a workound for S4 AT&T on specific firmware with locki patched TWRP but I don't think it's exist anything for ur S4 active at&t. I will let u know if I find anything.

Retrial said:
Don't worry mate, ask whatever you want. I will help if I can.
Optimized LineageOS 10 is great but it's EOL (end of life). Optimized LineageOS 11 is also great and it's currently under development.
But since you are looking for privacy & security it's better to use Official LOS with guarantee monthly security patches cause lately optimized los stays a bit behind on updates. (Dev is busy) Soon official 11 will also be released.
Click to expand...
Click to collapse
Ok thank you, I'll follow your advice.

[GUIDE][RECOVERY] TWRP 3.6.0_9-0 Custom Recovery for Lenovo Tab3 8 | TB3-850F/M

{
"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"
}
Lenovo Tab3 8 Tablet
Models: TB3-850F/M
TWRP 3.6.0_9-0​OVERVIEW
The TWRP ports currently available for the Lenovo Tab3 8 are outdated by a number of years and are lacking in official support for more recent Android release versions. TWRP 3.6.0_9-0 was originally compiled using the Android 9 tree, and therefore supports all Android versions up to, and including, Android 9 Pie. This custom recovery build also includes improved manageability of Android supported filesystem standards, better protection against data loss and corruption, added functions, and improved theming support. Likewise, I've made several bug fixes and cleaned up the codebase. To read a more in-depth list on the changeling of TWRP 3.6.0, visit this link the official TeamWin site here: TWRP 3.6.0 Release Notes
REQUIREMENTS
First and foremost, you need an unlocked bootloader. There are a plethora of guides hosted here on XDA that provide detailed instructions for standard bootloader unlocking. If your tablet is not yet unlocked, go ahead and complete that task and return here once finished. Secondly, you will need a Windows PC or laptop with the SDK platform tools installed or, alternatively, the Minimal ADB & Fastboot tools (link provided below). Note that a Linux or Mac machine may also be used; for purposes of this guide, however, I will be focusing solely on a Windows setup. Next, you will need an internet connection to download the files provided in the links below. Lastly, you will need the factory supplied or a quality equivalent USB-A to micro USB data syncing/charging cable.
COMPATIBILITY
This TWRP custom recovery is compatible with both hardware variants (80 & 81) of the TB3-850F model, as well as the TB3-850M 4G-LTE supported model.
DISCLAIMER
Installing a custom recovery on an Android mobile device is an invasive procedure in terms of the modifications made to the stock partition index. Flashing the partitions of your device is a task that encompasses the inherent risk of bricking or otherwise rendering your device inoperable. By proceeding further, you are assuming sole responsibility for the integrity and operability of your tablet. Follow the instructions carefully, employ some patience, and things should go smoothly. I would encourage inexperienced members to read this guide in full prior to starting the instructions.
INSTRUCTIONS:​
Download the Minimal ADB & Fastboot tools from the below link and install the program on your Windows PC & laptop. Next, open your Windows File Explorer, open your C: drive, then open Program Files x86. Copy the Minimal ADB & Fastboot folder and paste it to your desktop. (Copying the directory to the desktop isn't required, but does configure the ADB & Fastboot path to a more convenient directory from which to work);​
Download TWRP 3.6.0_9-0 from the below link and save the image file in your ADB & Fastboot folder on your computer;​
Boot your tablet into fastboot mode as follows: with your tablet booted into the Android OS, ensure ADB Debugging is enabled in the Developer Options menu. Connect the tablet to your PC using a sufficient USB-A to micro USB syncing/charging cable;​
Open the ADB & Fastboot folder on your computer. Double click cmd-here.exe to open a command window, and execute the following command:
Code:
adb reboot bootloader
Your tablet may prompt you to authorize the ADB connection;​
If properly connected your Tab3 8 will boot into fastboot mode, which will be indicated by the status displayed on the tablet. To verify proper fastboot communication between your computer and tablet, execute this command:
Code:
fastboot devices
If everything is set up properly, the command window will return an alphanumeric string consistent with your tablet S/N;​
If your S/N isn't displayed, or if your are given a WAITING... notification, your tablet is not being recognized correctly. Change USB ports, try a different data syncing cable, and/or update your fastboot drivers;​
Once a solid connection has been verified, execute the following command to flash TWRP to your tablet:
Code:
fastboot flash recovery twrp.img
(The TWRP file you downloaded below is named twrp.img. The above flashing command assumes that you have left the filename unchanged.);​
You may now boot your tablet into TWRP recovery mode by executing:
Code:
fastboot boot twrp.img
​
Task complete. You should now running TWRP 3.6.0_9-0 on your Lenovo Tab3 8 device. ​
DOWNLOADS:
• TWRP 3.6.9_9-0 Lenovo Tab3 8
• Minimal ADB & Fastboot Tools v1.4.3
THANKS & MENTIONS:
First and foremost, thanks to TeamWin Recovery Project for providing the base build, and for their many years of hard work and contributions to the custom Android community. Thanks to the XDA members who remain dedicated to the Lenovo Tab3 8 and its continuing development projects. Although I'm slow, I have two more projects in the works for our beloved tablets. Thank you for your patience my friends.​BUGS:​Please leave a comment detailing any bugs or instabilities you may encounter. I will diligently try to patch and fix any reported bugs.​

Hi,
I flashed TWRP v3.4.1-0 from your link but I end up in a boot loop where I fail to mount any of the partitions.
The DL Link for TWRP v3.6.0_9-0 seems to be broken. Do you have an alternate for that?
Note: I'm working on a TB3-850F.
Thanks!

Okay I think dm-veriry is to blame. If you mounted /system after installing TWRP, dm-veriry will be triggered and the device will boot loop.
You need to flash a dm-verity disabler. I'll get you a link .

Any chance you might also have a link to the updated twrp you had linked above? It's a dead link now.

Diznatch52 said:
Any chance you might also have a link to the updated twrp you had linked above? It's a dead link now.
Click to expand...
Click to collapse
Sure. I'll fix the link

Ok link is fixed. Follow these steps.
Warning: This will wipe all data from your device.
Download the no-veriry_opt encrypt file linked below and save it to an external micro SD card. Insert the micro SD in your TB3-850F;
Install TWRP v3.6.0_9-0 and reboot recovery;
Select Wipe, Format Data, and swipe to commence.
Select Install and navigate to the saved location of the no-verity zip you downloaded in Step 1. Select the zip and swipe to commence installation.
Reboot system
no-verity_opt-encrypt_v6.1.zip
If you want root access of the Android OS, install a Magisk systemless root script after Step 4.

Awesome! I'll give it a shot.

Diznatch52 said:
Awesome! I'll give it a shot.
Click to expand...
Click to collapse
Download Magisk v24.3 from this link https://mega.nz/file/4c43FbwS#Qd-pKoupa8LZ-EI9qe5Zsr3L4rSz8NDv2Ojknrd8sCk
Install it after Step 4 if you want root. After you are booted, you can update Magisk to the latest v25.2 using the Direct Install option.

For some reason, after this process, running `adb reboot recovery` brings me to an android crash screen. Any idea why?

To confirm, this procedure did work and you were able to boot into the OS? Once you confirm I'll try to resolve your ADB issue.

Yes.

Diznatch52 said:
Yes.
Click to expand...
Click to collapse
Ok download the official TWRP App, grant it root permission, and flash the TWRP v3.6.0_9-0 to the recovery partition. Reboot your tablet and then try the adb reboot recovery command again.
When you flashed the original TWRP with fastboot, did you immediately boot into recovery and flash TWRP again using the Install>Image option?

As soon as I unbrick this again, I'll give it a shot
Edit: booting into recovery now gives me twrp! Thanks so much!
Now time to see if I have better luck flashing lineageOS

IT WORKED!
Thank you so much!

Anytime friend. Glad it worked out.

Update: December 13, 2022.
I am presently working on bumping TWRP up to v3.7.0_9-0.
The v3.7.0 base build includes Python support for Android Oreo & newer versions.; keymaster API V1 fixes; fixes on copying sepolicy on devices with no /vendor partition; several fixes on custom theme support as well as perfected ROM multiboot functionality. Also, I am updating my implementation of PIGZ compression for data transfer speed improvements and enhanced protection against data corruption. Stability improvements and minor bug fixes also included.
I will keep the OP updated with an ETA.

Diznatch52 said:
IT WORKED!
Thank you so much!
Click to expand...
Click to collapse
I have a build of LineageOS 14.1 that I optimized, fixed some bugs and removed settings entries on SIM cards & mobile networks. Open source libraries have been updated and the security patch level bumped up to June, 2022. GApps have been removed and several performance enhancements have been added. I'm without a working 850F at this time, but I should have a working device soon. I will post the LOS 14.1 build as soon as I can fully test it.

Diznatch52 said:
IT WORKED!
Thank you so much!
Click to expand...
Click to collapse
I have a build of LineageOS 14.1 that I optimized, fixed some bugs and removed settings entries on SIM cards & mobile networks. Open source libraries have been updated and the security patch level bumped up to June, 2022. GApps have been removed and several performance enhancements have been added. I'm without a working 850F at this time, but I should have a working device soon. I will post the LOS 14.1 build as soon as I can fully test it.
Oh, I nearly forgot, would you care to list your stock firmware build number please. Thanks

That would be incredible. I don't know if I still have access to my stock firmware build. I've already got a version of LOS 14.1 (could admittedly be snappier) installed. If you tell me how to find it, happy to send it over.

I just meant on your 850F, go to device settings, about tablet, and let me know your build number. Thx