FORUMS
Remove All Ads from XDA

[RECOVERY][MT6735] TWRP-3.0.2 for Lenovo Tab3 7 (TB3-730X)

135 posts
Thanks Meter: 60
 
By 0xAF, Senior Member on 25th September 2016, 02:20 PM
Post Reply Email Thread
7th October 2016, 12:40 AM |#11  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by 0xAF

I'm glad you've solved the problem. I dont know what is 0x7D4 error. It could be some sort of extra locking of the device, but I doubt it. It's more likely to be something related to SPFlash Tools. It could be also a broken firmware, I haven't tried to flash the firmware from the links I've provided. I only used the Original Firmware to extract the original recovery from there. I needed the original kernel from the recovery to be able to start the TWRP.
A fast look in google gives this:

But I guess it's not very helpful.

Just try to read flash, it's safe. I can bet You will get error 0x7D4 or 2004 (depend of version of flashtool). It's extra locked for sure. Btw. why You need original recovery to start TWRP? Maybe You mean that You need it to compile TWRP for this tablet model?
7th October 2016, 05:53 PM |#12  
OP Senior Member
Thanks Meter: 60
 
More
Quote:
Originally Posted by DonKapselo

Just try to read flash, it's safe. I can bet You will get error 0x7D4 or 2004 (depend of version of flashtool). It's extra locked for sure. Btw. why You need original recovery to start TWRP? Maybe You mean that You need it to compile TWRP for this tablet model?

The easiest way to port TWRP is to get it from another device with the same chipset and cpu. I did not wanted to prepare a toolchain/crosscompiler and start from the beginning to compile TWRP. So I took a TWRP from another tablet (DOOGEE_X6pro_Android6.0_20160707). Since it has a recent version of TWRP and is compiled for android 6.
Then all you need is to replace the kernel in this recovery, so we are booting with the kernel for our device. I needed the kernel from our original recovery for that. Then I've touched some files inside the recovery, fixed the fstab and default.prop and repackaged the recovery image.
This is the easiest way to port the recovery IMO. Took me 15-20 mins with all the testing.
This procedure work for any recovery, not only TWRP.
I guess, I could have dumped the original recovery from the device, but since I was looking for custom recovery for some time, I found the dump in the russian forum and downloaded it. So when I decided to port TWRP, I already had the recovery from the dump.
10th October 2016, 10:49 AM |#13  
Junior Member
Thanks Meter: 0
 
More
Thanks for info Any link to step by step how to replace kernet, what data change?
10th October 2016, 01:46 PM |#14  
OP Senior Member
Thanks Meter: 60
 
More
Quote:
Originally Posted by DonKapselo

Thanks for info Any link to step by step how to replace kernet, what data change?

https://www.youtube.com/watch?v=hwMFBuCY-5k
I saw this video and decided to follow the steps.
You will need some intuition about the files you need to change inside the new recovery, as the video shows that only the fstab is needed, but you need more files, like default.prop and some other device dependent files from the original recovery (mostly in root folder).
In this recovery, I've used the default.prop from the original recovery.
As for the fstab, you will need to convert it by hand to a format understandable by TWRP. I've used the TWRP fstab file from the other device (from which I took the recovery in first place) and adopted it to our device. IIRC, almost nothing had to be changed.
I've copied some other device dependent files from the original recovery too.

Since I'm on linux, I've used these tools:
https://github.com/osm0sis/Android-Image-Kitchen.git
https://github.com/osm0sis/mkbootfs/
https://github.com/osm0sis/mkbootimg/

The tools are also available for windows (as the video shows) and for android itself (I believe the CF-SuperSU uses them on android to repack the boot.img).
These tools can repack recovery.img and boot.img.
11th October 2016, 12:37 AM |#15  
Junior Member
Thanks Meter: 0
 
More
Many thanks!
13th October 2016, 03:46 PM |#16  
beldy's Avatar
Junior Member
Flag Prague
Thanks Meter: 1
 
More
Quote:
Originally Posted by 0xAF

Is your bootloader unlocked?
see the "fastboot" command manual, to check if it is unlocked.

yes bootloader is unlocked by command fastboot oem unlock...

It managed to someone already listed above to flash firmware in fastboot mode?
When you turn on the tablet remains lit Lenovo logo, and that's the end ...
Tablet can not even charged because, in the power cable connection tablet immediately turn on and loading TWRP or Lenovo logo screen

I am not progressed and I would appreciate if someone added original recovery or something what my tablet to function again

thx
13th October 2016, 06:45 PM |#17  
OP Senior Member
Thanks Meter: 60
 
More
Quote:
Originally Posted by beldy

yes bootloader is unlocked by command fastboot oem unlock...

It managed to someone already listed above to flash firmware in fastboot mode?
When you turn on the tablet remains lit Lenovo logo, and that's the end ...
Tablet can not even charged because, in the power cable connection tablet immediately turn on and loading TWRP or Lenovo logo screen

I am not progressed and I would appreciate if someone added original recovery or something what my tablet to function again

thx

Hi.
I'll make a dump of my system partition and post a link.
Unfortunately my system partition is not like in the original from the OTA ROM.
I've patched it with xposed and removed some ****ty apps from the OTA ROM.

Meanwhile if someone have OTA ROM, I would appreciate a link.

(you could try asking the Lenovo support for the OTA ROM).
14th October 2016, 08:00 PM |#18  
beldy's Avatar
Junior Member
Flag Prague
Thanks Meter: 1
 
More
Quote:
Originally Posted by 0xAF

Hi.
I'll make a dump of my system partition and post a link.
Unfortunately my system partition is not like in the original from the OTA ROM.
I've patched it with xposed and removed some ****ty apps from the OTA ROM.

Meanwhile if someone have OTA ROM, I would appreciate a link.

(you could try asking the Lenovo support for the OTA ROM).


Thanks for the answer and advice to try anything that can help me
Thx

//EDIT: I add a few screens that I made an attempt to flash ... maybe you help someone ..
Attached Thumbnails
Click image for larger version

Name:	0x7D5.jpg
Views:	698
Size:	213.9 KB
ID:	3903982   Click image for larger version

Name:	0x1388.jpg
Views:	678
Size:	215.3 KB
ID:	3903983   Click image for larger version

Name:	Chip type not match.jpg
Views:	622
Size:	246.0 KB
ID:	3903984   Click image for larger version

Name:	DSC_0002.jpg
Views:	614
Size:	256.1 KB
ID:	3903985  
23rd October 2016, 02:18 PM |#19  
OP Senior Member
Thanks Meter: 60
 
More
Quote:
Originally Posted by beldy

Thanks for the answer and advice to try anything that can help me
Thx

//EDIT: I add a few screens that I made an attempt to flash ... maybe you help someone ..


You should try to flash the dump with "fastboot flash system <file>"
8th November 2016, 02:45 PM |#20  
Junior Member
Germany
Thanks Meter: 0
 
More
Hello,
Got the Lenovo TAB3-730M.
What SuperSU.zip do I have to take to get "root"?
The "SR3-SuperSU-v2.78-SR3-20161103171345.zip" does not work.
8th November 2016, 02:47 PM |#21  
OP Senior Member
Thanks Meter: 60
 
More
Quote:
Originally Posted by Erna1

Hello,
Got the Lenovo TAB3-730M.
What SuperSU.zip do I have to take to get "root"?
The "SR3-SuperSU-v2.78-SR3-20161103171345.zip" does not work.

Looking at the folder with all my files for this lenovo, it seems I've flashed this one: SuperSU-v2.78-201609011115.zip
And it works.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes