Related
Here are many ways descrbed to root the simple Wifi 4.7 SM-T230, but no one seems to have a glue how to root the SM-T235 (LTE/3G). Is this too complicated, or doesn't any one be interested in this device?
Regards
SS
I think also
slowfax said:
Here are many ways descrbed to root the simple Wifi 4.7 SM-T230, but no one seems to have a glue how to root the SM-T235 (LTE/3G). Is this too complicated, or doesn't any one be interested in this device?
Regards
SS
Click to expand...
Click to collapse
my problem too. I´m looking for a smt 235 root on several sides but it seems no one be interested.
I'll try to give you a clue to root your SM-T235 device and i cant promise you this will work
I know twrp for tab 7 is not working to root SM-T235 because you have degas lte and mali 400 gpu? (i just guessing)
and mine pxa 1088 degas 3g/wifi with vivante gpu. and we have different structure partitions.
So you can not using degas-unpack bootimg for pxa1088.
I think you can use "abootimg" in linux to unpack and repack your recovery image.
I believe tab 8 and tab 10 can use abootimg too.
here's command i used in ubuntu to unpack and repack smt235 stock recovery
to unpack:
$ abootimg -x recovery.img
writing boot image config in bootimg.cfg
extracting kernel in zImage
extracting ramdisk in initrd.img
to repack:
$ abootimg --create newstockrecovery.img -f bootimg.cfg -k zImage -r initrd.img
reading config file bootimg.cfg
reading kernel from zImage
reading ramdisk from initrd.img
Writing Boot Image newstockrecovery.img
now you have new stock recovery image.
(if you wanna take a look what is in initrd.img you can change the extension to initrd.cpio then unzip it,
you can edit fstab, change it to twrp/cwm ramdisk or whatever possibilities. but leave it untouch at the moment)
next step,
Repack a new recovery as a flashable odin:
$ tar -H ustar -c newstockrecovery.img > newstockrecovery.img.tar
$ md5sum -t newstockrecovery.img.tar >> newstockrecovery.img.tar
$ mv newstockrecovery.img.tar newstockrecovery.img.tar.md5
Please note :
i dont have sm-t235 to test.
report here if this abootimg method working.
before experiment, i've been warning you, THIS COULD BE DANGEROUS to your tab.
i hope you know what are you doing before flashing. and you have backup firmware if something goes wrong.
i'll try to port sm-t231 custom recovery to stockcovery sm-t235 later,
depends on your report of course.
my problem too. I´m looking for a smt 235 root on several sides but it seems no one be interested.:crying::crying::crying:
Hi jokowi,
the method did not work odin did failed to flash the image.
I have a theory
I think the latest FW, you could root with the Towelroot is the Firmware XXU1ANE8, for DBT Build Date: 2014/05/22.
One could extract the kernel (boot.img) from the firmware and repack it and flash with Odin.
Then you can root with Towelroot, install SuperSU, freeze KNOX ...
Finally, the suitable kernel must flash back with Odin.
Question #1.: Is the file boot.img the kernel file? I have extract kernel for Galaxy S5 and Galaxy Note3. Both contains the file boot.img. A file zImage is no longer exists in this firmware
Question #2: Can you flash a kernel with Odin for this tablet?
theory #2: Flash the complete Firmware XXU1ANE8 with Odin, root it with Towelroot and flash a newer Firmware with Mobile Odin. The tablet continues to rooted.
You're making me a little troubled. One t235 is coming to me and the 1st thing I wanted to do is... root. After testing functions, obviously.
But I see that the Root Front is hard on this device....:crying:
Many people are interested in rooting that device, but no one can help (find the way to do it ) Device is very good in my opinion (battery life especially good) but what a same I can't uninstall for example Samsung S calendar and install Google's one without duplication reminders! I wait for root for a long time and loosing hope that somebody would help to solve problem with rooting this device
I will buy an other Tab, which can be rooted. Even if it is worse and more expensive than that terrible device.
ari6265 said:
I have a theory
I think the latest FW, you could root with the Towelroot is the Firmware XXU1ANE8, for DBT Build Date: 2014/05/22.
One could extract the kernel (boot.img) from the firmware and repack it and flash with Odin.
Then you can root with Towelroot, install SuperSU, freeze KNOX ...
Finally, the suitable kernel must flash back with Odin.
Question #1.: Is the file boot.img the kernel file? I have extract kernel for Galaxy S5 and Galaxy Note3. Both contains the file boot.img. A file zImage is no longer exists in this firmware
Question #2: Can you flash a kernel with Odin for this tablet?
theory #2: Flash the complete Firmware XXU1ANE8 with Odin, root it with Towelroot and flash a newer Firmware with Mobile Odin. The tablet continues to rooted.
Click to expand...
Click to collapse
I flashed the entire rom XX...E8 from Polland. I supposed the Kernel is the same.
The thing is that Towel R says : "Not supported device, sorry"...
:crying:
Still no root for t235? I can't belive this. I need this root because I want to install boost apps , because I play clash of clans and it's laggy comparing to my i9500. I don't know why...
RE: Any way to root the SM-T235? - stock recovery.img attached - TWRP needed
coco_greu said:
Still no root for t235? I can't belive this. I need this root because I want to install boost apps , because I play clash of clans and it's laggy comparing to my i9500. I don't know why...
Click to expand...
Click to collapse
jokowi said:
I'll try to give you a clue to root your SM-T235 device -
I know twrp for tab 7 (SM-T230/231) is not working to root SM-T235 because you have degas lte and mali 400 gpu? (i just guessing)
and mine (SM-T231) pxa 1088 degas 3g/wifi with vivante gpu. and the structure partitions on the SM-T235 are different from the SM-T231
So you can not using degas-unpack bootimg for pxa1088.
Click to expand...
Click to collapse
Attached is the recovery.img from the stock SM-T235 NE8 ROM dated 5/2014
Hoping someone will help us out by creating a TWRP recovery for the device.
coco_greu said:
Still no root for t235? I can't belive this. I need this root because I want to install boost apps , because I play clash of clans and it's laggy comparing to my i9500. I don't know why...
Click to expand...
Click to collapse
These devices lack 3rd party support since Samsung has severely over saturated the market with so many different models for this device..
Because of that there is very little support.. The best 7 inch tablet for the same price you should of got a Nexus 7 2013, its a better tablet over all, it just lacks a SDcard slot.. Just my personal opinion.. My Galaxy Tab 4 8.0 just released at the same time your Galaxy tab was releases JUST got a TWRP port and not long ago just got root.
my t235y seem to be locked the call function (the tab still recognize the sim network), so i need to root it and i try all method with no hope
anyone please help
TopTongueBarry said:
Attached is the recovery.img from the stock SM-T235 NE8 ROM dated 5/2014
Hoping someone will help us out by creating a TWRP recovery for the device.
Click to expand...
Click to collapse
I have recovery mod and I tried every root/one click root found on forums even if it wasn`t for t235. But nothing works. This is really strange because the tablet is very good and smooth, I don`t know why nobody has interest for this device.
I'm frustrated, so difficult is getting root for this model?
RE: SM-T235 root frustration
mingoandroid said:
I'm frustrated, so difficult is getting root for this model?
Click to expand...
Click to collapse
I was really hoping someone would be able to use the SM-T235 recovery image I posted earlier in this thread to create a TWRP recovery for the device.
The only other hope is to unpack and repack the stock factory image (use the NE8 version dated 5/2014).
There's a lot to performing that effort, and as jokowi mentioned in another post earlier, the degas-unpack bootimg for pxa1088 that works for the SM-T230, 231 is based on degas 3g/wifi with vivante gpu. It won't work on a SM-T235 degaslte.
Maybe this will help ....
Open source link: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-t235
D/L link: SM-T235_recovery_imgNE8.zip
TTB
TopTongueBarry said:
I was really hoping someone would be able to use the SM-T235 recovery image I posted earlier in this thread to create a TWRP recovery for the device.
The only other hope is to unpack and repack the stock factory image (use the NE8 version dated 5/2014).
There's a lot to performing that effort, and as jokowi mentioned in another post earlier, the degas-unpack bootimg for pxa1088 that works for the SM-T230, 231 is based on degas 3g/wifi with vivante gpu. It won't work on a SM-T235 degaslte.
Maybe this will help ....
Open source link: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-t235
D/L link: SM-T235_recovery_imgNE8.zip
TTB
Click to expand...
Click to collapse
bump.
Someone please take this project on for us SM-T235 owners
TopTongueBarry said:
bump.
Someone please take this project on for us SM-T235 owners
Click to expand...
Click to collapse
Please !!!
I just got this tablet. I was actually shocked that till now there wasn't a root solution. I hope someone with knowledge will help us with custom recovery and root solution.
Hello,
I am just new with Samsung smartphones, previously I was on some other devices such Nexus which are easier to mod.
I would like to tweak the kernel( I already got the sources) to add few things but I need for that eventually the ramdisk and the kernel image to make a boot image.
I wanted to download the latest firmware, hoping a default boot image was integrated in it and that I could unpack but I got issue and connection loss so I can't even take a look at it.
I think I will be able to get the boot image with the dd command but to do so I need to be in a mod recovery(such twrp) and currently I can't.
Thx u
Firstly you've created a voting thread. If this is a standard question I suggest in future you leave the options at default.
Why can't you use TWRP?
My build also supports raw image backup of the boot partition.
Sorry about creating wrong thread type
I have extended this feature to include BOOT
Click to expand...
Click to collapse
Woot Yeah I didn't know about that!
So I can just get the current boot image, unpack it, replace with my kernel image, repack and done.
And then flash the boot image throw a zip install or your extended function.
Btw, I am was looking over the net but couldn't find an exact answer to this extra Q, is there any fastboot mode ? So I can just boot in a custom kernel image before flashing it.
Yep, just backup the boot partition using twrp.
Locate the boot image backup in the twrp backup folder.
Unpack it, make your mods, rename it boot.img, copy it to internal or external storage and flash it with TWRP using the INSTALL button.
Samsung devices dont have a fastboot mode.
@ashyx answered my questions, thx to him!
>Samsung devices dont have a fastboot mode.
My latest Samsung Tablet has a fastboot mode but it was manufactured around the end of 2012 ... So it is not quite recent
I've never known a Samsung device to use FASTBOOT, so that's news to me.
Samsung uses its own proprietary ODIN mode.
Which device is this?
Ahhah you gonna say I am half of a lier.
It was my nexus 10. Built by Samsung and running the 5250 exynos chip
Was able to port twrp recovery of blitz smartwatch after unpacking and replacing the kernel file with the lemfo lem5's stock kernel file extracted from unpacking stock recovery of lemfo lem5 and then repacking and flashing it to lemfo lem5. The recovery got successfully installed and all features are working except the recovery screen is flipped / inverted but not the touch response. The touch inputs are the same as non inverted screen and using the touch is pain in the a**s. If the touch input field is at 45 degrees then to access it, need to tap at 225 degrees and on the same radius distance. Can anyone let me know how to flip the recovery screen without affecting the touch fields or is there a similar custom recovery for mtk6580 lollipop smartwatch with flipped screen.
I have not found solution
Same problem with kw88h
And all twrp apk from playstore does not recognize as twrp
Recovery
Flashify can make the job
Only commands from adb... for wipe.
There is not enough space to backup or restore and i think only root and flasify is all you need.
geowolf1000 said:
I have not found solution
Same problem with kw88h
And all twrp apk from playstore does not recognize as twrp
Recovery
Flashify can make the job
Only commands from adb... For wipe
There is not enough space to backup or restore and i think only root is all you need
Click to expand...
Click to collapse
I have got everything working in twrp recovery. The flip recovery is no more a problem now as with some practice now I am comfortably able to use this inverted twrp touch with ease. It works like a charm and just like the official twrp recovery. No problems at all. Now everything is set : bootloader unlocked, rooted with latest binary supersu, custom twrp recovery installed. I also have the stock recovery img backup file, hence can switch back and forth between stock and custom recovery whenever required. No space issue on lemfo lem5 as it has 8gb rom. lastly only xposed installer is to be installed which is not much of a problem as they are available for lollipop with supported sdk and for which as of now I don't see the use of xposed installer right now, hence will install when required. If I am able to somehow flip the recovery screen then that's it! ?
Gautam_Gundap said:
I have got everything working in twrp recovery. The flip recovery is no more a problem now as with some practice now I am comfortably able to use this inverted twrp touch with ease. It works like a charm and just like the official twrp recovery. No problems at all. Now everything is set : bootloader unlocked, rooted with latest binary supersu, custom twrp recovery installed. I also have the stock recovery img backup file, hence can switch back and forth between stock and custom recovery whenever required. No space issue on lemfo lem5 as it has 8gb rom. lastly only xposed installer is to be installed which is not much of a problem as they are available for lollipop with supported sdk and for which as of now I don't see the use of xposed installer right now, hence will install when required. If I am able to somehow flip the recovery screen then that's it! ?
Click to expand...
Click to collapse
If your rom size is not sufficient enough for backup then you can create full rom backup on pc and can restore the same from pc when the need arises. There are software packages available for the same
geowolf1000 said:
I have not found solution
Same problem with kw88h
And all twrp apk from playstore does not recognize as twrp
Recovery
Flashify can make the job
Only commands from adb... for wipe.
There is not enough space to backup or restore and i think only root and flasify is all you need.
Click to expand...
Click to collapse
Gautam_Gundap said:
If your rom size is not sufficient enough for backup then you can create full rom backup on pc and can restore the same from pc when the need arises. There are software packages available for the same
Click to expand...
Click to collapse
I have with chainfire but never had any problem to recover
Thanks
Gautam_Gundap, fantastic work - You've beaten me to the punch as I had been messing with this device since yesterday (already fixed two bootloops I had induced myself -_- ) and I've been looking for a method for porting a TWRP img that wouldn't brick the LEM5.
Would you mind sharing the port? ..Despite the mirrored display/input issues you have so far, having any recovery method right now is very appealing to me considering the hell I had luckily sidestepped, and want to dig further into their stock images: if only to rebuild them with better icons for starters....
If not, can you just run me through your steps for full-backup, and your modification of TWRP for use with LEM5? I don't mind doing the legwork but would rather not walk this firepath alone!
(After 4 years, finally signed up and posted. Feels good to be here, guys! )
cassettesgoboom said:
Gautam_Gundap, fantastic work - You've beaten me to the punch as I had been messing with this device since yesterday (already fixed two bootloops I had induced myself -_- ) and I've been looking for a method for porting a TWRP img that wouldn't brick the LEM5.
Would you mind sharing the port? ..Despite the mirrored display/input issues you have so far, having any recovery method right now is very appealing to me considering the hell I had luckily sidestepped, and want to dig further into their stock images: if only to rebuild them with better icons for starters....
If not, can you just run me through your steps for full-backup, and your modification of TWRP for use with LEM5? I don't mind doing the legwork but would rather not walk this firepath alone!
(After 4 years, finally signed up and posted. Feels good to be here, guys! )
Click to expand...
Click to collapse
There are many advantages of twrp custom recovery, one of them being very fast full rom backup and even faster full rom restore and that too with compression, the pc whereas takes at least 10 times the time to do the same. full rom restore for me does it within 4mins and backup size of full compressed rom is only 1.64GB whereas the pc takes 7GB for the same backup. Needless to say about advantages of other features like customized wipe, flash image and zip files etc. Now for the procedure for porting twrp custom recovery is as follows
Download latest version of mtk extractor for PC. I tried all other methods, but only this one worked for me.
Download custom twrp recovery of blitz or i2 smartwatch which you will find in this forum.
You will require your stock recovery image file for this method. Your watch needs to be rooted to extract the same. Flashify app from playstore will do the job.
Connect watch to pc. Hope you know how to do this. rename stock recovery img to boot. Open mtk extractor and unpack this renamed file. You will find the unpacked files in mtk folder.
Cut these files and paste in a new folder stock recovery.
now rename the custom twrp recovery img you are going to port to boot.
Unpack it, the files will be placed in mtk folder.
Now copy kernel file from the stock recovery folder and paste it in the new unpacked files of ported twrp. PC Prompts replace - yes.
Now repack and you will get boot.img. Rename to recovery.img.
Flash this via fastboot or Flashify. Done. You have now successfully installed twrp recovery.
Note: In the mtk extractor software use the boot feature for all above steps.
If you encounter any problems post here and I will fix it.
To use pc for full rom backup and restore and many other features use cracked version of miracle box v2. 27A. Mtk Droid tools and SP flash tools do not support this watch, so don't waste time trying with it.
Xposed framework installed successfully!
Anyone need full power button menu for lemfo lem5 install advance power menu app from playstore. It works well. Once you long press the power button you get options for power off, reboot, download, recovery, UI restart , screen shot, soft reboot and safe mode reboot. Select floating mode from settings. looks and works nice on smart watch display
Gautam_Gundap said:
There are many advantages of twrp custom recovery, one of them being very fast full rom backup and even faster full rom restore and that too with compression, the pc whereas takes at least 10 times the time to do the same. full rom restore for me does it within 4mins and backup size of full compressed rom is only 1.64GB whereas the pc takes 7GB for the same backup. Needless to say about advantages of other features like customized wipe, flash image and zip files etc. Now for the procedure for porting twrp custom recovery is as follows
Download latest version of mtk extractor for PC. I tried all other methods, but only this one worked for me.
Download custom twrp recovery of blitz or i2 smartwatch which you will find in this forum.
You will require your stock recovery image file for this method. Your watch needs to be rooted to extract the same. Flashify app from playstore will do the job.
Connect watch to pc. Hope you know how to do this. rename stock recovery img to boot. Open mtk extractor and unpack this renamed file. You will find the unpacked files in mtk folder.
Cut these files and paste in a new folder stock recovery.
now rename the custom twrp recovery img you are going to port to boot.
Unpack it, the files will be placed in mtk folder.
Now copy kernel file from the stock recovery folder and paste it in the new unpacked files of ported twrp. PC Prompts replace - yes.
Now repack and you will get boot.img. Rename to recovery.img.
Flash this via fastboot or Flashify. Done. You have now successfully installed twrp recovery.
Note: In the mtk extractor software use the boot feature for all above steps.
If you encounter any problems post here and I will fix it.
Click to expand...
Click to collapse
Very cool - seems straightforward enough. I'll see if I can find something to fix up or workaround to get the rotation back while I'm at it. First thing's first is to give this a shot though. Need to get a windows machine so I'll get it going at work tomorrow!
Will update again soon. Thanks so much for the steps!
Hi guys.. root + twrp ok.. but there are Custom ROM with full smartwatch function (not only standalone)? Or the only one solution (partial solution) is M2D?
Well done! :laugh: I've configured Lem5 TWRP how u can see here:
https://forum.xda-developers.com/smartwatch/other-smartwatches/twrp-lemfo-lem-5-twrp-t3544569
I think/hope i've solved recovery flipped screen issue, because X5 TWRP haven't this problem.
X5 TWRP + Lem5 kernel = solution? I hope so!
If someone want try, please post the result. Thanx at all...!
Sent from my S7 Edge using XDA Labs
I'm trying to flash the recovery through fastboot and I'm getting:
C:\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (9676 KB)...
OKAY [ 0.366s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 0.383s
I tried rooting with Kingroot and it really bloated up my device. Factory reset still keeps Kingroot, so I kinda want to start over fresh with TWRP and a clean image. How do you flash TWRP on this watch?
---------- Post added at 02:53 PM ---------- Previous post was at 02:39 PM ----------
Update: I made sure OEM unlock was checked in developer settings and eventually was able to flash TWRP via Fastboot.
My watch is now bootlooping over and over again in TWRP, says:
"Done processing script file, renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP."
dimex said:
I'm trying to flash the recovery through fastboot and I'm getting:
C:\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (9676 KB)...
OKAY [ 0.366s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 0.383s
I tried rooting with Kingroot and it really bloated up my device. Factory reset still keeps Kingroot, so I kinda want to start over fresh with TWRP and a clean image. How do you flash TWRP on this watch?
---------- Post added at 02:53 PM ---------- Previous post was at 02:39 PM ----------
Update: I made sure OEM unlock was checked in developer settings and eventually was able to flash TWRP via Fastboot.
My watch is now bootlooping over and over again in TWRP, says:
"Done processing script file, renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP."
Click to expand...
Click to collapse
if your bootloader is locked, it will not allow you to flash twrp recovery via fastboot . Use SP FLASH TOOLS for this purpose. Once you flash recovery do not reboot to system. Reboot to recovery for the first time and then it should be ok. Else root your watch first and flash recovery using Flashify. This method will also do the job.
Gautam_Gundap said:
if your bootloader is locked, it will not allow you to flash twrp recovery. Use SP FLASH TOOLS for this purpose. Once you flash recovery do not reboot to system. Reboot to recovery for the first time and then it should be ok. Else root your watch first and flash recovery using Flashify. This method will also do the job.
Click to expand...
Click to collapse
Did you read my update? It's bootlooping TWRP.
dimex said:
Did you read my update? It's bootlooping TWRP.
Click to expand...
Click to collapse
If you are unable to reboot to system, then you need to re flash complete stock rom. You can do this using cracked miracle software. I have already uploaded full stock rom for flashing via cracked miracle box software except data/userdata partition . you can find it in one of the lemfo lem5 threads here. After re flash you can use the steps explained earlier to flash twrp recovery
I just released a fully working TWRP 3.0.2 recovery for X5+ and LEM5 here:
http://roundandroidwatches.proboards.com/thread/1016/twrp-recovery-port-x5-lem5
Don't forget to read all the instructions.
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Click to expand...
Click to collapse
WARNING!!! Be careful what you do here. One mistake and the device is soft-bricked. I take no responsibility for bricked devices, lost warranty or even OTAs not working!! Booting and/or flashing files from this post is on your own risk.
Requirements
Unlocked bootloader
Lenovo Tab 4 Plus with and without LTE and both 8 and 10 inch versions (TB-X704L/F, TB-8704X/F) are supported
Known Issues
WARNING! Our device uses dm-verity (verified boot). The system partition should remain read-only. Otherwise a bootloop will occur. You can flash SuperSU to resolve this but OTA's are no longer possible! You have to restore a factory image or clean system backup to receive OTAs
Download
TWRP for TB-8704X/F (8 inch plus): AndroidFileHost
TWRP for TB-8704V (8 inch plus Verizon): AndroidFileHost (provided by @3m1k)
TWRP for TB-X704L/F (10.1 inch plus): AndroidFileHost
TWRP for TB-8504X/F (8 inch): AndroidFileHost (touch input may only work after connecting mouse)
TWRP for TB-X304L/F (10.1 inch): AndroidFileHost
Instructions
Install fastboot and adb on your PC, e.g. from here
Enable developer options and in there select to unlock your bootloader by enabling OEM unlock and enable USB debugging
Connect your PC to your tablet and run
Code:
adb reboot bootloader
using adb on command line. The tablet will reboot into bootloader mode where you will only see the Lenovo logo. Now you use
Code:
fastboot oem unlock-go
to unlock. This will factory reset your device
Setup the tablet again and reboot again to the bootloader
Then run
Code:
fastboot boot twrp-3.2.3-0-<your-filename>.img
to temporarily boot into TWRP. You can also flash if you are sure
Select to keep system read only when TWRP starts to avoid modification which will make OTAs impossible
Backup at least system and boot partitions. Choose "System Image" for the system partition backup. Keep this backup for OTA updates.
Optionally flash SuperSU or Magisk in TWRP which should install system less. Keep OEM unlock enabled if you flash or modify anything
Writable System Partition
Some mods and root apps require write access to the system partition. By default the system partition is read-only to prevent any modification. Please note that if your system partition is modified in any way it needs to be restored to its original state before a system update (OTA) can be applied.
@dywersant has created a Magisk module here to achieve write access
@KreAch3R has updated the Magisk module to the latest version here
System Updates (OTA)
In order to successfully apply Lenovo system updates after root you have to restore the original boot, recovery (if you flashed TWRP) and system partitions from your current installed version (e.g. S000037) for your variant of the tablet. This will NOT delete your apps and data but will unroot. Note that OTAs are block based and always check the contents of most of the partitions. This means that all of these partitions (except your data) have to be original and have to be on the exact same version (e.g. S000037) for the update to succeed.
Credits
@wonderfulme - for testing the 8" version
@Teddy01 - for testing the 10" version
@3m1k - for providing the 8" Verizon version
TeamWin
Source
TWRP Manifest: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-7.1
Device Tree (TB-8704X): https://github.com/Matshias/twrp_android_device_tb_8704x/tree/android-7.1
Device Tree (TB-8704V): https://github.com/3m1k/twrp_android_device_tb_8704v
Device Tree (TB-X704L): https://github.com/Matshias/twrp_android_device_tb_x704l/tree/android-7.1
Device Tree (TB-8504X): https://github.com/Matshias/twrp_android_device_tb_8504x/tree/android-7.1
Device Tree (TB-X304L): https://github.com/Matshias/twrp_android_device_tb_x304l/tree/android-7.1
Changelog
v3:
Update to TWRP 3.2.3-0
v2:
Update to TWRP 3.2.1-0
v1:
Initial Release
TWRP for Tab 4 8/10 without "Plus"
I built TWRP for both devices and need testers. Here are experimental versions:
Tab 4 8 (TB-8504X/F): twrp-3.1.1-0-tb_8504x_testing1.img
Tab 4 10 (TB-x304L/F): no longer needed. Final version in first post
matshias said:
TWRP for Tab 4 8/10 without "Plus"
I built TWRP for both devices and need testers. Here are experimental versions:
Tab 4 8 (TB-8504X/F): twrp-3.1.1-0-tb_8504x_testing1.img
Tab 4 10 (TB-x304L/F): twrp-3.1.1-0-tb_x304l_testing1.img
Click to expand...
Click to collapse
I can test the 8 inch tomorrow. Thanks for building this btw.
---------- Post added at 02:01 PM ---------- Previous post was at 01:58 PM ----------
Wait, these builds are for the Plus variants only? They will not work with ZA2B0009US, correct? :\
w0rdie said:
Wait, these builds are for the Plus variants only? They will not work with ZA2B0009US, correct? :\
Click to expand...
Click to collapse
ZA2B0009US = TB-8504F so you can take the build for Tab 4 8 (TB-8504X/F) and hopefully it will work out of the box.
matshias said:
ZA2B0009US = TB-8504F so you can take the build for Tab 4 8 (TB-8504X/F) and hopefully it will work out of the box.
Click to expand...
Click to collapse
Just landed there myself. I'll give it a go tomorrow morning and update this post.
Thanks again.
I have tested on X304L work perfectly.
Only one thing when i'm on power via usb TWRP still turning off screen in 2min and seems that all operations are put in wait state until screen turned on again.
:good:
boza12 said:
I have tested on X304L work perfectly.
Only one thing when i'm on power via usb TWRP still turning off screen in 2min and seems that all operations are put in wait state until screen turned on again.
:good:
Click to expand...
Click to collapse
Thanks a lot for testing. I moved the TWRP to the first post.
In the TWRP settings you can switch off whether the screen goes off or not. Are you sure TWRP halts processing while the screen is off?
matshias said:
Thanks a lot for testing. I moved the TWRP to the first post.
In the TWRP settings you can switch off whether the screen goes off or not. Are you sure TWRP halts processing while the screen is off?
Click to expand...
Click to collapse
Yes It does - it happened to me last night also.
EggZenBeanz said:
Yes It does - it happened to me last night also.
Click to expand...
Click to collapse
Can you send me the logs (dmesg output and /tmp/recovery.log) after it happens?
Yes sure.
Is anyone able to make available a system image. I deleted my original back up after the update then messed the root up. I now getting setup app crash and can't get passed setup
EggZenBeanz said:
Yes sure.
Is anyone able to make available a system image. I deleted my original back up after the update then messed the root up. I now getting setup app crash and can't get passed setup
Click to expand...
Click to collapse
Download the factory image for your tablet from the Russian Lenovo forum (lenovo-forums.ru) . In there you will find a fragmented system image. You have to puzzle it together with a script according to XML file in the Image directory. If you wanna flash via fastboot you will have to convert it with img2simg to sparse format. You can also use dd command line TWRP with the raw image file. If you tell me your exact model number I can also upload what you need.
matshias said:
Download the factory image for your tablet from the Russian Lenovo forum (lenovo-forums.ru) . In there you will find a fragmented system image. You have to puzzle it together with a script according to XML file in the Image directory. If you wanna flash via fastboot you will have to convert it with img2simg to sparse format. You can also use dd command line TWRP with the raw image file. If you tell me your exact model number I can also upload what you need.
Click to expand...
Click to collapse
Thanks! That would be awesome if you could. I think I may brick it if I do what you suggest! My model is
TB-X704L/F (10.1 inch plus) could you include the boot image too?
EggZenBeanz said:
Thanks! That would be awesome if you could. I think I may brick it if I do what you suggest! My model is
TB-X704L/F (10.1 inch plus) could you include the boot image too?
Click to expand...
Click to collapse
Is it TB-X704L vor F? This is an important difference.
The boot image you can find as can be flashed in the factory image. You can start with this. When I have time I'll prepare the system image. Not sure when that is though.
matshias said:
Is it TB-X704L vor F? This is an important difference.
The boot image you can find as can be flashed in the factory image. You can start with this. When I have time I'll prepare the system image. Not sure when that is though.
Click to expand...
Click to collapse
Thanks!!!! Confirmed TB-X704F
matshias said:
TWRP for Tab 4 8/10 without "Plus"
I built TWRP for both devices and need testers. Here are experimental versions:
Tab 4 8 (TB-8504X/F): twrp-3.1.1-0-tb_8504x_testing1.img
Tab 4 10 (TB-x304L/F): twrp-3.1.1-0-tb_x304l_testing1.img
Click to expand...
Click to collapse
The twrp-3.1.1-0-tb_8504x_testing1.img flashes and boots fine but there is no touch input.
Logs: https://www.dropbox.com/s/vo2dvi4frpsf9hf/logs.zip?dl=0
(I connected a mouse via USB and got SU flashed)
On my Tab4 8 the touch is also not working with this image.
I think the following lines from dmesg.log are showing, that the touch driver ist not loading:
<4>[ 1.323216] [HXTP] Himax common touch panel driver init
<4>[ 1.323221] [HXTP][ERROR] himax_common_init failed, compare_tp_id = 1
w0rdie said:
The twrp-3.1.1-0-tb_8504x_testing1.img flashes and boots fine but there is no touch input.
Logs: https://www.dropbox.com/s/vo2dvi4frpsf9hf/logs.zip?dl=0
(I connected a mouse via USB and got SU flashed)
Click to expand...
Click to collapse
Do you have the TB-8504X or TB-8504F? Very strange that the touch driver won't load. if you have the F variant then maybe it has a slightly different hardware in which case I'll have to compile separate TWRP for this variant. Can you extract me your stock boot or recovery image and send it to me? I'd then build TWRP with the kernel from your tablet and we'll see what happens
EggZenBeanz said:
Thanks!!!! Confirmed TB-X704F
Click to expand...
Click to collapse
Here is the system image in sparse format for fastboot flashing: MEGA
matshias said:
Here is the system image in sparse format for fastboot flashing: MEGA
Click to expand...
Click to collapse
Amazing, thank you so much. All worked and back to normal. I'll root again with the screen off and provide logs
Sorry if this is off topic, but is there a way to convert the Chinese versions of the Tab 4 / Plus to the Global rom? I'm thinking of getting one from China when I'm there but the lack of Google Play support is a major deal breaker.
Hi everyone, I'm having issues with my P7500 (p4) tab. I bricked it by trying to flash a PIT file to modify the system partition size, then unbricked it by installing the stock ROM I found online for the P7500. I planned to install Android 7.1.2 eOS again so I flashed TWRP but the BigSys variant for a 1GB system partition size. Now all of this worked, but now when I try to install the custom ROM it gives me error 7, saying it's for p4 while I have a p4wifi. Before I bricked it I installed this ROM fine since it is actually a p4 not a p4wifi, I tried to force it by changing the build.prop in the ROM and renaming all the model identifiers to p4wifi but still no luck. Could this have anything to do with the stock ROM I flashed to unbrick it? If so could someone point me to a stock ROM for the P7500 'p4', or was the the TWRP BigSys variant I installed (which shouldn't have modified the model code or anything)
Help is much appreciated!
Hello, I had a similar problem with my P4 that also gave me error 7 after installing the 311 TWRP big sys version because it then is set to p4wifi instead of p4.
My solution was to use the correct TWRP version for the p4. You can find one here:
index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)
index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)
devdb.xda-developers.com
Transfer it to you Tab 10.1 and boot into the TWRP, recovery then just install the .zip file of TWRP for p4.
After you reboot into that one, you are able to install p4 rom again (e.g.
Ae-OS-P7500-PuckRomRemix2020.zip)
I hope this helps.
TWRP 3.11 bigsys is only for the Wifi Version and not for the 3G.