Related
hii
i am new to this world of upgrading and flashing . i rooted my samsung galaxy grand i 9082 yesterday and seeking to upgrade it to kitkat 4.4.2 .. I read some in the forums about some stability issue and also dual sim feature will no longer be avalable. please tell me are these true.
please guide me step by step how to upgrade and solve the issues. i really dont know what is cm11 ,what is cynogem mod.. please spoon feed me or provide a link for the same.
regards
CM 11 = CyanogenMod..
CyanogenMod (pronounced /saɪ.'æn.oʊ.dʒɛn.mɒd/) is an enhanced open source firmware distribution for smartphones and tablet computers based on the Android mobile operating system. It offers features and options not found in the official firmware distributed by vendors of these devices.
Features supported by CyanogenMod include native theming support, FLAC audio codec support, a large Access Point Name list, an OpenVPN client, an enhanced reboot menu, support for Wi-Fi, Bluetooth, and USB tethering, CPU overclocking and other performance enhancements, soft buttons and other "tablet tweaks", toggles in the notification pull-down (such as wi-fi, Bluetooth and GPS), app permissions management, as well as other interface enhancements. CyanogenMod does not contain spyware or bloatware. In many cases, CyanogenMod may increase performance and reliability compared with official firmware releases.
CyanogenMod is developed as free and open source software based on the official releases of Android by Google, with added original and third-party code.
Source: CyanogenMod Wiki
Click to expand...
Click to collapse
Please tell me how to get a 4.4.2 version. And also please tell how to take a backup of my original firmware if I wish to rollback to original firmware in case
Regards
Sent from my GT-I9082 using XDA Free mobile app
umang2792 said:
hii
i am new to this world of upgrading and flashing . i rooted my samsung galaxy grand i 9082 yesterday and seeking to upgrade it to kitkat 4.4.2 .. I read some in the forums about some stability issue and also dual sim feature will no longer be avalable. please tell me are these true.
please guide me step by step how to upgrade and solve the issues. i really dont know what is cm11 ,what is cynogem mod.. please spoon feed me or provide a link for the same.
regards
Click to expand...
Click to collapse
You should better read/ask in your phone's section.
Here is a short preview of the "advanced" android world :
- In order to backup your phone data you need a recovery.
- The most known recoveries are CWM and TWRP (in most phones you get into recovery pressing power and volume buttons while the phone is off).
- From the recoveries you can install a new ROM (firmware) to your phone, make a backup/restore or flash zip files (that run commands and move files)
- Cyanogenmod / Cm is a famous ROM with different versions for many phones. Cm11 is the Cyanogenmod kitkat version (10 jellybean, 9 icecream etc)
I hope you got the main idea
Sorry I am not getting the backup and restore option in my cwm as it shows in the videos
[App] Srlabs releases "SnoopSnitch" for detecting IMSI-Catchers, silent SMS...
unfortunetely it only works with some qualcom based devices, you can find a list of working devices under:
https://opensource.srlabs.de/projects/snoopsnitch/wiki/DeviceList
new version is out: 0.9.3
Version 0.9.3
Support Android 5
Fix initialization issue on newer devices
Translation to German and Dutch
Click to expand...
Click to collapse
SnoopSnitch is an Android app that collects and analyzes mobile radio data to make you aware of your mobile network security and to warn
you about threats like fake base stations (IMSI catchers), user tracking and over-the-air updates. With SnoopSnitch you can use the data collected in the GSM Security Map at gsmmap.org and contribute your own data to GSM Map.
This application currently only works on Android phones with a Qualcomm chipset and a stock Android ROM. It requires root priviliges to capture mobile network data.
Requirements:
Qualcomm-based Android phone (see list below)
Stock Android ROM, version 4.1 or later
Note: Unfortunately, custom Android ROMs like CyanogenMod are not supported, as they lack the drivers necessary to collect radio data.
Root privileges on phone
Tested Devices:
The following devices have been verified to work:
Samsung S3 Neo (GT-I9301I)
LG G2 (LG-D802)
Sony Xperia Z1 (C6903)
Samsung S5 (SM-G900F)
Motorola Moto E (Moto E)
Samsung S4 (Qualcomm variant)
It is very likely that other Qualcomm-based Android phones also work, if they are rooted and have a stock firmware.
Incompatible Devices:
The following devices have been found to be incompatible and can not be used with SnoopSnitch:
UNSUPPORTED: Every device without a Qualcomm chipset
UNSUPPORTED: Every device with custom ROM
UNSUPPORTED: Samsung Galaxy S2 & S3
UNSUPPORTED: Nexus 5
UNSUPPORTED: Huawei Ascend Y300
Click to expand...
Click to collapse
from https://opensource.srlabs.de/projects/snoopsnitch (project site)
or google play link:
https://play.google.com/store/apps/details?id=de.srlabs.snoopsnitch
Not working on my HTC ONE M7 converted to GPE 5.0.1 .
Root, S-OFF etc. available. Is there any information about this?
geminga said:
Not working on my HTC ONE M7 converted to GPE 5.0.1 .
Root, S-OFF etc. available. Is there any information about this?
Click to expand...
Click to collapse
Possibly your kernel lacks the necessary support. For instance people with a Nexus 5 can flash this kernel: http://d-h.st/mmb (thanks to this thread: http://forum.xda-developers.com/google-nexus-5/general/radio-enable-lte-band-3-nexus-5-d820-t2928561). About what the OP said: I can't see why this app wouldn't work on a custom ROM such as CM11 as long as the kernel has the necessary options.
xd.bx said:
About what the OP said: I can't see why this app wouldn't work on a custom ROM such as CM11 as long as the kernel has the necessary options.
Click to expand...
Click to collapse
Well, Carsten Nohl, one of the developers, said yesterday on 31C3, that on CustomROMS like CM certain proprietary drivers are missing, which are needed for getting certain debugging information. Later yesterday in a workshop on 31C3 participants found out, that on some CM11 Phones the app is working.
There the app worked on:
Samsung S3 Neo
Samsung S5
LG G2
Sony Xperia Z1
Motorola Moto E
and dind't work on
Samsung S2, S3, S4 and S5 Exynos
Nexus 5
Fairphone
you can watch the presentation from Nohl on 31C3 here:
http://media.ccc.de/browse/congress...830_-_mobile_self-defense_-_karsten_nohl.html
on my nexus5 with slimkat 8.20 it says:
"device /dev/diag does not exist"
About the compatible devices - I can confirm the app works on on Xperia V with the stock 4.3 Android. It gives no errors, but I have not yet encountered malicious GSM cells to verify the detection works ok.
Why do we have to make long distance calls and send sms to use this app?
http://forum.xda-developers.com/showthread.php?t=1422969
Celestial Fury said:
Why do we have to make long distance calls and send sms to use this app?
Click to expand...
Click to collapse
This is part of active testing, the number called should be busy. Read more on the project site mentioned in the first post.
rudolfm said:
This is part of active testing, the number called should be busy. Read more on the project site mentioned in the first post.
Click to expand...
Click to collapse
Sure I did. It doesn't say why we have to call/sms a specific number and why we data can't be gathered from our every day call/sms and why data can't be sent to the test site through the internet rather than call/sms.
XsheldorX said:
on my nexus5 with slimkat 8.20 it says:
"device /dev/diag does not exist"
Click to expand...
Click to collapse
You need to flash a compatible kernel. http://d-h.st/mmb
Works on my SONY Xperia Z1 with CM11.
Though, when doing the test call my device was banned, for whatever reason....
Yeah I can (probably) confirm this with Z1 compact with CM 11. Works since day one I guess. The test works (around the first days incoming calls and sms did not, probably because of overload of the callingserver), but never had any sort of attacks. Now I'm in doubt if radio-part does not work with cm 11, as mentioned in the description, or there were zero attacks.
Another thing I observed. The software sometimes produces many wake-locks. But I guess thats normal if backgroundservice is active.
@ papperlapapp: Did you monitor any attacks (SS7 or silent sms)? Or even IMSI-catchers?
Installed the app without problems on my S5 with Phoenix ROM (Stock Based). However, when I start the active test, the app stops responding and android asks me several times if I want to close it. I chose no every time. Now I'm wondering if the tests are still running in the background or if the app just hang. Started the tests about 35 min ago, still waiting, absoluteley nothing happened yet.
Why not install something like https://f-droid.org/repository/browse/?fdfilter=monitor&fdid=com.eolwral.osmonitor and see if that task is stil running?
Usefull tool anyway
happy monitoring
Works on Samsung Note 3 SM-N9005
Sent fra min SM-N9005 via Tapatalk
xperia E1 seemingly working
E1 seems to work.
but now what ? where are the logfiles where I see stuff live?
google 31c3 "mobile self defense" for the thrilling background story
let's all hope the CCC talkers have learnt better English by 2016 (Mr Nohl being one of the best still) !
https://media.ccc.de/browse/congres...self-defense_-_karsten_nohl.html#video&t=3838
xd.bx said:
Possibly your kernel lacks the necessary support. For instance people with a Nexus 5 can flash this kernel: http://d-h.st/mmb (thanks to this thread: http://forum.xda-developers.com/google-nexus-5/general/radio-enable-lte-band-3-nexus-5-d820-t2928561). About what the OP said: I can't see why this app wouldn't work on a custom ROM such as CM11 as long as the kernel has the necessary options.
Click to expand...
Click to collapse
Will this kernel work on Nexus 5 with lollipop 5.01 ? I notice the file name is specific for android 4.4.2
MForce22 said:
Will this kernel work on Nexus 5 with lollipop 5.01 ? I notice the file name is specific for android 4.4.2
Click to expand...
Click to collapse
I don't know. Just try, at worst you'll have to reflash the old kernel back.
itman-ch said:
Why not install something like https://f-droid.org/repository/browse/?fdfilter=monitor&fdid=com.eolwral.osmonitor and see if that task is stil running?
Usefull tool anyway
happy monitoring
Click to expand...
Click to collapse
it is on play store too ^^
srlabs posted a device list:
https://opensource.srlabs.de/projects/snoopsnitch/wiki/DeviceList
and a new version is out:
Version history
Version 0.9.2
Fixed app lock-up issues
Improved device compatibility check
Handled unsupported LTE gracefully
Version 0.9.1
Fix problem where SnoopSnitch would leave the phone muted after a test
Remove issue with disappearing (Skype) dialing dialogs
Resolved performance issue in analysis
Version 0.9.0
Initial public release
Click to expand...
Click to collapse
Mediatek MT8173 & MT8176 development
Hi folks, after I've long been working on my device and only made little progress in building LineageOS for my Xiaomi Mi Pad 3 I decided to look for other developers with similar devices.
My Mi Pad 3 (codename: cappu) is a tablet based on a Mediatek MT8176 SoC. It was launched in April 2017. The tablet comes with a 7.9" display with a resolution of 2048 pixels by 1536 pixels at a PPI of 326 pixels per inch. It is powered by a 2.1GHz/1.7GHz Hexa Core processor ( 2 x 2.1GHz Cortex A72 + 4 x 1.7GHz Cortex A53 ) and it comes with 4GB of RAM. The tablet packs 64GB of internal storage that cannot be expanded. It was shipped out with Android 7.0 (Miui) and is still on this version).
Two months ago Xiaomi finally released Kernel Source Code for my device. It was broken, but I fixed most of the conflicts, streamed the kernel up to latest linux-stable and added some features. I also tried to build LineageOS & AOSP trees, but I have to admit, I'm starting to get desperate. For this specific SoC - even it's predecessor MT8173 - there is no activie development. And that is what I am looking for!
I collected some devices that either use MT8176 SoC, or the older MT8173 SoC. Some of them have Kernel Sources, which I listed and linked below.
All questions, requests for help, suggestions, ... are welcome. If you own any of the listed devices feel free to write and help. This thread is also on Reddit.
MT8176
Xiaomi Mi Pad 3
GPD XD+
Chuwi Hi9
Teclast Master T8
Teclast Master T10
Asus Zenpad 3S 10
Acer Iconia Tab 10 A3-A50
Alfawise Tab
MT8173
ALLDOCUBE Freer X9 (Cube Free X9 (U89))
HITSAN Onda V10 Pro
Pegasus JDTab J01
Acer Chromebook R13 CB5-312T-K8Z9
Amazon Fire HD 10 2017
Lenovo N23 Yoga
Lenovo Flex 11
Xiaomi Mi Box 3 2016
Amazon Fire TV (sloane)
Firmwares & Source-Code:
Chuwi Hi9
https://www.needrom.com/download/chuwi-hi9/ (Firmware)
Acer Iconia Tab 10 A3-A50
https://github.com/Goayandi/android_kernel_acer_titan
https://snlookup.com/acer-iconia-tab-10-a3-a50-tablet-p104780 (Firmware & Kernel-Source)
Xiaomi Mi Pad 3
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/cappu-n-oss (Kernel-Source)
https://github.com/Goayandi/android_kernel_xiaomi_cappu/tree/3.18.108 (Kernel-Source)
http://en.miui.com/a-234.html (Firmware)
https://multirom.me/index.php?m=app&a=view&id=81&app=roms (Firmware)
Teclast T10
https://www.needrom.com/download/teclast-t10-e3c5/ (Firmware)
Teclast T8
https://www.needrom.com/download/teclast-t8-e8c1/ (Firmware)
GPD XD+
https://github.com/Goayandi/android_kernel_mt8176_common (Kernel-Source)
https://github.com/skelton/android_kernel_mt8176_common (Kernel-Source)
https://droidbox.co.uk/how-to/flashing-gpd-xd-plus-firmware/ (Firmware)
http://www.gpd.hk/news.asp?id=1519&selectclassid=002002 (Firmware)
Asus Zenpad 3S 10
https://github.com/Goayandi/android_kernel_asus_z500m (Kernel-Source)
http://dlcdnet.asus.com/pub/ASUS/EeePAD/Zenpad/Z500M/Z500M_V13_6_10_15_kernel.zip (Kernel-Source)
https://www.asus.com/us/Tablets/ASUS-ZenPad-3S-10-Z500M/HelpDesk_BIOS/ (Firmware)
Onda V10 Pro
https://www.needrom.com/download/onda-v10-pro/ (Firmware Android)
http://onda.cn/Tablet_Supports.aspx?id=371 (Firmware Phoenix OS)
http://onda.cn/Tablet_Supports.aspx?id=370 (Firmware Phoenix OS)
Pegasus JDtab J01
https://www.needrom.com/download/jdtab-j01/ (Firmware)
Amazon Fire TV 2015 (sloane)
https://github.com/Goayandi/android_kernel_amazon_sloane (Kernel-Source)
Amazon Fire HD 10 (7th Generation)
https://fireos-tablet-src.s3.amazon...PR/Fire-HD10_7th_Gen-5.3.6.2-20180315.tar.bz2 (Kernel-Source)
https://kindle-fire-updates.s3.amaz...wyB/update-kindle-40.6.0.5_user_605485120.bin (Firmware)
ALLDOCUBE Freer X9 (U89)
http://51cube.com/services?_search=U89 (Firmware)
https://www.leakite.com/2017/10/cube-stock-firmware.html (Firmware)
First thanks for your initiative! And I am very interested in obtaining a Custom ROM for my Teclast T10 E3C5 device with the aforementioned MTK8176 Chipset. I cannot help you with development but are open to test it and report bugs.
Hi Goayandi,
I'm not sure how many experienced ROM developers you will get. (I'm not one of them. I have compiled and modded existing ROMs, but never ported one.) I've heard several people say they will look into building a custom ROM for mt8163 or mt8173. But that's always as far as it gets. They never come back with any results. So I was just curious, what are you getting stuck on?
As far as I can tell, one major problem with porting to Mediatek is that they modify a lot of Google's OS code like frameworks and libraries. I do see that you already have some MTK customized repositories in your github library. You may have to do some reverse engineering of the stock ROM to confirm that the MTK changes are the same ones you have in your repos. Yes, that's a huge pain. It's also likely that MTK's patches for mt81xx and mt67xx, which is probably what you have, are pretty different.
One suggestion I want to make is to start out with a ROM that's as close to stock as possible. That means building a plain AOSP build NRD90M. This will reduce as many trouble-causing variables as possible. That's how I would do it. If you accomplish that, it will be easy to move on to higher Android versions or LineageOS, etc.
I would also use the prebuilt kernel for now. There is not much point to compiling your own for the same reason I just mentioned. A lot more variables would enter the equation. (Unless maybe you can test it independently with the stock FW.)
Any chances of giving TeamMAD access to one of these devices?
I have a Teclast T8 stuck in fastboot mode. No recovery, no system. adb cannot see the device. Is there a way to recover from that?
xivxivxiv said:
I have a Teclast T8 stuck in fastboot mode. No recovery, no system. adb cannot see the device. Is there a way to recover from that?
Click to expand...
Click to collapse
In T10 thread I have heard of same kind of issue. Disconnect battery (solder) or wait for device to die, then charge and it should be fine
BiG_FooT said:
In T10 thread I have heard of same kind of issue. Disconnect battery (solder) or wait for device to die, then charge and it should be fine
Click to expand...
Click to collapse
I tried that. That would work if recovery were bootlooping, and system were intact. In my case, my T8 cannot get to system. The Teclast Logo goes through its animation on startup, then gets stuck there. Holding volume up and power gives me 3 choices: recovery, fastboot, normal. Recovery and Normal are both broken. Fastboot is the only one I can do. How to recover from that?
xivxivxiv said:
I tried that. That would work if recovery were bootlooping, and system were intact. In my case, my T8 cannot get to system. The Teclast Logo goes through its animation on startup, then gets stuck there. Holding volume up and power gives me 3 choices: recovery, fastboot, normal. Recovery and Normal are both broken. Fastboot is the only one I can do. How to recover from that?
Click to expand...
Click to collapse
You need to reflash firmware/rom with the sp flash tool.
fastmix said:
You need to reflash firmware/rom with the sp flash tool.
Click to expand...
Click to collapse
You should flash stock firmware on your tablet with SPflash tools. Search for Mediatek SPflash + your device name in Google. Flash procedure should look like this:
FLASH Mediatek device
- Unpack FlashTools, and Click on Flash_tool.exe
- Select "scatter-Loading" and search MT8173_Android_scatter.txt in ROM
- Wait file to be added into Flash Tool
- Select "Download Only" or if upgrade "Firmware upgrade"
- Turn off your phone (and don't turn on the phone).
- Press “Download” button to start
- and connect your phone into the computer via USB data cable.
- The process will start and a red progress bar will appear after color purple, yellow.
- And green circles display
- Finish !
- You can now safely disconnect your phone and turn it on.
So you should look for your ROM/FIRMWARE and than flash it. Key step for you is to turn of the tablet, push download button in SPflash tools, and then connect USB to the tablet. Flash will then start!
But Google for instructions on how to use SPflash
Thank you, BiG_FooT and fastmix! Leaving it in power off state before SP flash was the missing step. I don't know how I missed that in previous Google searches. Fully working tablet now.
I now have two of these things. If you (or any others interested in developing this Mediatek) want me to use one of my Teclast T8s for testing for you, let me know.
Has anyone successfully flashed the firmware??
The system.img for all the ROMs is corrupt
Hi! I have an Alfawise Tab (rebranded JDTAB 01) with MT8173 chipset and android 6.0.
I managed to find the stock firmware and recovery, so i tried to port this TWRP recovery: https://forum.xda-developers.com/mi-pad/development/recovery-twrp-3-2-1-0-mi-pad-3-cappu-t3744185 unsuccessfully, maybe because of the different android versions(?)
I don't know....
Does anyone know how to port- build a custom recovery for these chipsets (mt8173-76)?
Or know if there is a working TWRP based on android 6.0 and these chipsets?
So, is there still any development? Where kernel-sources for Teclast devices can be found?
What an utter failure. Of both the manufacturers and the community.
It's fairly clear that the problem is hardware fragmentation. There is just too much diversity in Android hardware platforms, even too many different ARM-based CPUs, and too few users on many of those to justify a major development effort for any of them.
The moral of the story must be: if you want your tablet to remain useful for more than a couple of years, don't buy a cheap Chinese generic one made by a company that isn't a famous global brand. Stick to hardware that has sold in the millions.
ralphclark said:
What an utter failure. Of both the manufacturers and the community.
It's fairly clear that the problem is hardware fragmentation. There is just too much diversity in Android hardware platforms, even too many different ARM-based CPUs, and too few users on many of those to justify a major development effort for any of them.
The moral of the story must be: if you want your tablet to remain useful for more than a couple of years, don't buy a cheap Chinese generic one made by a company that isn't a famous global brand. Stick to hardware that has sold in the millions.
Click to expand...
Click to collapse
What we really need to do is reverse engineer a few roms already built for these chipsets, then see what they all have in common. This will help us figure out what needs to be done to the kernel, and what firmware we need.
Any news? Has anyone tried to flash GPD firmware on one of the other tablets with the same chipset? I have a Chuwi Hi9 with MTK 8173 and I would love to be able to change the ROM, the default one sucks big time. I actually bought it because it had the same chipset as one of the GPD devices.
Where To Start??
Goayandi said:
Mediatek MT8173 & MT8176 development
Click to expand...
Click to collapse
Hi,
If I were you I would start by having a really good look through the MTK_X20_BASE_AOSP open source code here https://github.com/archermind/MTK_X20_BASE_AOSP
In that you will find all the required mtk binary's and documented associated google dependency's and stock mtk app's needed. Dig through all the make files and compare your project_confg which should be in your system/data/misc on 6.0 and vendor/data/misc 7.0 with the one in that source to see whats built.
Because it's mediatek it's messy and things are all over the place but after days of reading it you can kinda start follow the rabbit eventually :laugh:
Take what you need and assemble it into a nice logical fashion using a experienced dev's work as a example and try a AOSP build if that works then try Lineage.
When you have things stable follow others who have stepped up in firmware version.
Most things should work if you have a working kernel.
Best place to start would be HERE it's invaluable :good:
There are other places and make's for BT WiFi GPS etc etc so ensure to explore it well.
Obviosly get the blobs from your own device if poss else pinch them form that source and give them a try it's all trial and error.
If I ever find the time I may join you one day to build a rom for the Lenovo Tab2 mt8165 please note most of these mt8xxxx have a equivalent mt67xx/mt65xx see my sig below for a example.
Good Luck and Happy building :fingers-crossed:
bigrammy said:
Hi,
If I were you I would start by having a really good look through the MTK_X20_BASE_AOSP open source code here https://github.com/archermind/MTK_X20_BASE_AOSP
In that you will find all the required mtk binary's and documented associated google dependency's and stock mtk app's needed. Dig through all the make files and compare your project_confg which should be in your system/data/misc on 6.0 and vendor/data/misc 7.0 with the one in that source to see whats built.
Because it's mediatek it's messy and things are all over the place but after days of reading it you can kinda start follow the rabbit eventually :laugh:
Take what you need and assemble it into a nice logical fashion using a experienced dev's work as a example and try a AOSP build if that works then try Lineage.
When you have things stable follow others who have stepped up in firmware version.
Most things should work if you have a working kernel.
Best place to start would be HERE it's invaluable :good:
There are other places and make's for BT WiFi GPS etc etc so ensure to explore it well.
Obviosly get the blobs from your own device if poss else pinch them form that source and give them a try it's all trial and error.
If I ever find the time I may join you one day to build a rom for the Lenovo Tab2 mt8165 please note most of these mt8xxxx have a equivalent mt67xx/mt65xx see my sig below for a example.
Good Luck and Happy building :fingers-crossed:
Click to expand...
Click to collapse
Hello!
Do I have a chance to do this with my teclast T8 device if I don't have even kernel-source code? For now I've ported most of firmwares different from my stock ROM (MIUI, ZenUI etc). But I would like to upgrade android version ( Nougat to Oreo) if it possible. Since not so long new device ( alldocube X) was released on same chipset (mt8176) with installed android Oreo, maybe this may help some way?
Sword900 said:
Hello!
Do I have a chance to do this with my teclast T8 device if I don't have even kernel-source code? For now I've ported most of firmwares different from my stock ROM (MIUI, ZenUI etc). But I would like to upgrade android version ( Nougat to Oreo) if it possible. Since not so long new device ( alldocube X) was released on same chipset (mt8176) with installed android Oreo, maybe this may help some way?
Click to expand...
Click to collapse
Hello To All
I have a Teclast M89 That I rooted with Magisk and have a working TWRP for backing up.
I am very interested in Testing Kernels and new Roms.I have already wiped and reflashed device a couple times -now Everything for testing,flashing, and booting has been verified.
@Goayandi
Just stopping by to say thanks for this, used some stuff from here for lineage-12.1 on Fire HD10
https://forum.xda-developers.com/hd8-hd10/orig-development/rom-lineage-12-1-t3953677
I bought this tab in mid 2015 and it is showing its age. Wanted to see whats available for the device but couldn't find anything on this device although there is thread for A7-30 variant here.
These Lenovo Tabs have many variants with minor differences such as A7-10, A7-20, A7-30 all 7' ones and the 8" ones have A8 in their names. I have the A7-20F (F stands for Wifi only version, there is another with SIM facility whose identifier I don't remember right now) so most of the testing I will do with be applicable to this one.
I'm collating all available resources here since info on this old device is hard to come by. Ff there is anyone else who would like to join and may find useful later on. I'm new to android hacking so this may be slow on progress.
P.S: Links may contain software which is not tested/not working/unofficial/unstable software. Do not flash them without any backup plans for recovery if something goes wrong. This is a work-in-progress thread.
Known Issues:
1. The tab is reported to have ghost touch issues. Many have reported on the official forums. I myself am facing the same problem. Ghost touches are reported around the top edges where I also am seeing on my tab. People have reported updating drivers resolve it. I use the Partial Screen app as a workaround for the time being.
2. Some people have reported that the stock Lollipop ROM for this device is buggy. Will stay with stock Kitkit for the time being.
Hardware Specs:
Sources:
https://support.lenovo.com/in/en/downloads/ds104407
VCOM Drivers:
SPFlashtool
For flashing: https://spflashtools.com/
Recovery:
TWRP Recovery 2.8.7.0 for A7-20F: https://forums.lenovo.com/t5/Lenovo...P-2-8-7-0-for-Lenovo-Tab-2-A7-20F/m-p/2217156 Reported working here
OR
TWRP Recovery 2.8.7.0 for A7-20F: http://lenovo-forums.ru/topic/14955-lenovo-tab-2-a7-20-расширенный-twrp-recovery/. Reported working on Lenovo forms link here
ROMs
Stock 4.4.2: http://lenovo-forums.ru/topic/14573-lenovo-tab-2-a7-20-прошивка-t2-a7-20f-s08-150820-row/ Reported working here
Other Guides:
These guides may provide useful info on undesired outcomes, additional steps, results etc. which can help us plan for these in advance.
Links to working software for A7-20F at Lenovo forums: https://forums.lenovo.com/t5/Lenovo...2-A7-20F-T2-A7-20F-S08-150820-ROW/m-p/2216538
Guide with links to stock ROM for A7-20F: https://blogthetech.com/flash-file-lenovo-tab-2-a7-20f-firmware-download-stock-rom/
Guide using TWRP Recovery for A7-10: https://www.getdroidtips.com/twrp-recovery-lenovo-tab-2-a7-10f/
Guide using Philz CWM for A7-10: https://androidrootguide.com/2015/06/how-to-root-lenovo-tab-2-a7-10-and-install-cwm-recovery.html
Downgrading from Lolipop to Kitkat: https://forums.lenovo.com/t5/Lenovo...ade-from-buggy-Lollipop-to/m-p/2189574#M27033
Another guide on stock ROM intstalltion for A7-10F: https://www.getdroidtips.com/stock-rom-lenovo-tab-2-a7-10f/
Rooting guide for A7-20F: https://guideroot.net/lenovo-tab-2-a7-20-download-firmware-android-8-0-o/
Updated to Lollipop: https://www.youtube.com/watch?v=OiIH9D0Xxmo
Reserved for future use
Needed to upgrade my T2 A7 20f to Lollipop to continue running a specific app and tried a few different approaches with varying success. The CM12.1 ROM is under-done and full of problems and so is the T2 A7 10f stock ROM. There are screen rendering issues (poor quality) and battery charging issues. Seems that we really need to stick to a ROM based on the 20f to get decent functionality. After a lot of looking, found this link from Lenovo support:
A7-20F_USR_S000024_1605111428_MP1V1_BMAIN_ROW.rar
drive.google.com
This is version T2-A7-20F_USR_S000024_1605111428_MP1V1_BMAIN_ROW
ROW in China speak means Rest Of World i.e. not China version.
It downloads O.K and installs O.K using the included SPFlash tool.
Maybe useful to those still running this clunker?
Best if someone provides a more permanent home for this ROM before it disappears
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano/pico gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
Almost all
Known Issues
If you have wifi issues with latest release, please after install firmware apply patch:
SM-T320: https://drive.google.com/file/d/1E79Gcn7rNox2vP3OUd5FcVm2-a0aE12n/view?usp=sharing
SM-T325: https://drive.google.com/file/d/1fn1zJLL8dTJJJyoMEqph3DPH50YJp_gO/view?usp=sharing
Links
SM-T320
7. 20200411: march security patch, kernel update: https://drive.google.com/file/d/1I3QGfAEo55MKoEpBHBoZwj9a6EWzFBzA/view?usp=sharing
6. 20191211: december security patch, video recording, kernel from q with new wlan driver: https://drive.google.com/file/d/1YsniqI2RPwPKN9dB_7fKBAo9QkzxSFs_/view?usp=sharing
5. 20191130: latest sources, update kernel (autobrightness, some cleanup): https://drive.google.com/file/d/1swloB3vCfNsVzr9qsCmgpP8FpdrbXaJ2/view?usp=sharing
4. 20191112: november security patch: https://drive.google.com/file/d/1KQUcfna2rbeq8TLZfu44e63la59-rmzY/view?usp=sharing
3. 20191102: https://drive.google.com/file/d/1qJstVdMuPOM5ihsWqNvQeO4NyzsaVVIF/view?usp=sharing
2. 20191029: rollback dtb blocks to old stock: https://drive.google.com/file/d/1bY-vCQj57Gfgco1HeGbkkyjJEdOYOG2D/view?usp=sharing
1. 20191026: initial build: https://drive.google.com/file/d/1H3X036Qe9MJwEkE2zMPH5gQ05DLTkCzc/view?usp=sharing
SM-T325
4. 20200411: march security patch, kernel update: https://drive.google.com/file/d/13W9kC8RXK9CkqhDt5X9SQ7k9GISHbI5w/view?usp=sharing
3. 20191214: fix audio issues from last release: https://drive.google.com/file/d/1Mo3tPRTXtik2kBVNLJ8kw_bA6NJAgMuW/view?usp=sharing
2. 20191211: december security patch, ril + mobile data, internal speaker, kernel from q with new wlan driver: https://drive.google.com/file/d/13ARo1qiUh9MrNh9DHNlwxdo028cGpAjI/view?usp=sharing
1. 20191130: latest sources, update kernel (autobrightness, some cleanup), november security patch: https://drive.google.com/file/d/1Y4w1enXmMmDmLCvgzQSf5V6w-6wiPqLA/view?usp=sharing
Gapps
https://opengapps.org
Recovery
Use official version from:
SM-T320: https://twrp.me/samsung/samsunggalaxytabpro8.4wifi.html
SM-T325: https://twrp.me/samsung/samsunggalaxytabpro8.4lte.html
Sources
Sources: https://github.com/Lineageos
Device: https://github.com/Valera1978/android_device_samsung_mondrianwifi and https://github.com/Valera1978/android_device_samsung_mondrianlte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_mondrianwifi and https://github.com/Valera1978/android_vendor_samsung_mondrianlte
Thanks
Thanks to LineageOS team
Hello. 2 weeks ago with a big discount, I bought used a tab pro 8.4 wifi tablet.
I develop firmware for several tablets - note 12.2 on the same qcom 800, tab a 2016 on exynos 7870 (wifi<e) and a tab s3 on qcom 820 (wifi<e).
Initially, I thought, since the note pro is almost then same, as the tab pro series (actually, the note pro was develop based on the tab pro series), it turned out that these are huge differences, and I spent a huge amount of time to launch the tablet.
There were literally problems with everything - I spent almost a week launching just a panel and correctly turning it on/off. Then a huge amount of time to launch wifi and bt. Well, at the end, the sensors and cleanup the sources.
A bit later I'll build sm-t325 version and may be 10.1 sm-t525 (but I don't have this tablets, please send me to pm if you ready to help with test)
All my tablets already has android q. Of course after cleanups sm-t320 will get android q too.
Working for me only with pico gapps
del
Valera1978 said:
Hello. 2 weeks ago with a big discount, I bought used a tab pro 8.4 wifi tablet.
I develop firmware for several tablets - note 12.2 on the same qcom 800, tab a 2016 on exynos 7870 (wifi<e) and a tab s3 on qcom 820 (wifi<e).
Initially, I thought, since the note pro is almost then same, as the tab pro series (actually, the note pro was develop based on the tab pro series), it turned out that these are huge differences, and I spent a huge amount of time to launch the tablet.
There were literally problems with everything - I spent almost a week launching just a panel and correctly turning it on/off. Then a huge amount of time to launch wifi and bt. Well, at the end, the sensors and cleanup the sources.
A bit later I'll build sm-t325 version and may be 10.1 sm-t525 (but I don't have this tablets, please send me to pm if you ready to help with test)
All my tablets already has android q. Of course after cleanups sm-t320 will get android q too.
Click to expand...
Click to collapse
everything seems to work. thank you for this huge job
Thanks a lot! For me it works too!!! I used TWRP 3.2.3.0 and gapps mini (arm)! Dont forget a full wipe after installation.
Sent from my [device_name] using XDA-Developers Legacy app
@Valera1978
THX, you have done a great job, alot of us have waiting for this Version 16, camera works fine.
@Valera1978
Which Security Date has got this ROM.
Wound you like to update this ROM monthly with newest Patch level ?
bierma32 said:
@Valera1978
Which Security Date has got this ROM.
Wound you like to update this ROM monthly with newest Patch level ?
Click to expand...
Click to collapse
Current security update is october 2019.
You can monitor new update in: https://github.com/LineageOS/android_build/blob/lineage-16.0/core/version_defaults.mk , PLATFORM_SECURITY_PATCH define
Usually a new update appears on the 5-10th of the month (in lineage code) and after it I'm building new version.
Thank you for your working. I really expect the version of SM-T325
And what about SM-T520?
TechDriver said:
And what about SM-T520?
Click to expand...
Click to collapse
sm-t520 has differ platform. this is exynos5420 like t900\p900\901.
Thanks much! You brought a new life into my favorite tablet! It's hard to find a premium 8.4 tablet these days and hardware in this 5 year old one is running strong with your ROM.
Спасибо Валера!
Incredible to find developers still going strong in creating latest android version builds for this tablet after 5 years. Kudos to OP!
Works flawless and surely has added couple of more years life to the tablet now.
new versions.
Added version for sm-t325.
Unfortunately I do not have a t325 and I need somebody to test firmware. Please make backup efs/modem/may be all before test just in case.
Links in first post.
Valera1978 said:
new versions.
Added version for sm-t325.
Unfortunately I do not have a t325 and I need somebody to test firmware. Please make backup efs/modem/may be all before test just in case.
Links in first post.
Click to expand...
Click to collapse
I've tried test version on my SM-T325. There was repetitive rebooting problem initially and I cannot set anymore
However, thank you for your effort and I believe you can fix this problem.
How do i install this?
sorry to be a noob but this is my first time rooting an android device in about 8 years.
I have rooted by T320 and have super user.
I have installed the TWRP app.
I have odin.
I have all the downloads suggested on both my PC and my Samsung SD card.
WTF am i supposed to do from there? Do i install the mondrianwifi i find in the TWRP app if, so to boot or recovery? Or am i supposed to install the version the author linked. I hav read multiple articles but they don't explain what i am doing, why, how i should choose my options and they are all seriously out of date (given the age of the tablet)
Help!? Can someone give me a breadcrumb trail?
---------- Post added at 03:13 PM ---------- Previous post was at 02:51 PM ----------
scyto said:
sorry to be a noob but this is my first time rooting an android device in about 8 years.
Help!? Can someone give me a breadcrumb trail?
Click to expand...
Click to collapse
Ok i figured it out by a lot of poke and hope and got lucky.
I have the new firmware on with micro apps.
Was non intuitive how long the tablet takes after first reboot to get everything ready and WTF is that slider / circle animation - i thought it was telling me to slide my finger from right to left (that was up for like 2.5 mins the first time) luckily i just waited.
On first use lots of apps reported crashing most stopped but BT app was in infinite reboot.
Did hard reboot and the BT app is still infinitely rebooting along with android.process.media
Trying a factory reset, use TWRP to wipe device (all but SD card) and reinstall to fix....
---------- Post added at 03:32 PM ---------- Previous post was at 03:13 PM ----------
now its hung at the strange animation for more than 10 mins and power button does nothing? What next?
Another wipe and re-install not connected to USB seemed to fix it.
nrpia said:
I've tried test version on my SM-T325. There was repetitive rebooting problem initially and I cannot set anymore
However, thank you for your effort and I believe you can fix this problem.
Click to expand...
Click to collapse
Please post logs,
SM-T325 builds appreciated
Valera1978 said:
new versions.
Added version for sm-t325.
Unfortunately I do not have a t325 and I need somebody to test firmware. Please make backup efs/modem/may be all before test just in case.
Links in first post.
Click to expand...
Click to collapse
WOW just WOW
@Valera1978 Thank you for all your efforts and bringing this device back to life! I'm happily looking forward to test builds for the SM-T325 and provide logs if needed.
Valera, What is new in release from 11/02 (lineage-16.0-20191102-UNOFFICIAL-mondrianwifi)? Or it is targeted to owners of SM-T325 and you just misplaced it in SM-T320 section?