yashsingh1/xdaforums huggingface dataset:
[Android General] MotoJunkie01:
I got the same error with Bluetooth Share force closing two times at the setup screen. Probably a corruption issue during archiving the ROM. I'll do an md5 and archive the ROM again.
[Android General] rongallant:
Seemed to work, however the loading images and screen is still lenovo. Also they lenovo apps are still there.
[Android General] MotoJunkie01:
This is not a custom ROM. This is pure stock. The Lenovo boot logo, boot animation & apps are supposed to be there. Like the title implies this an "Unmodified" stock ROM.
[Android General] rongallant:
My bad, understood.

On another note, I am finding it very buggy. The home and overview buttons do not work. They show you clicked it along with the haptic feedback, but nothing happens. The back button works and is the only way I know to get back to the home screen.

Also the tool panel you pull from the top stops working after a little while until I reboot. Then works for a little while.

The Play store downloads barely work. They show pending and nothing happens. I force quite, cleared the cache, disabled, reverted to the stock app and it works for a little bit. Then the other Play Store app comes back. Anyways, I am not complaining. I appreciate the work you put into this. It's awesome we get to do it at all. Just giving my feedback. P.S. It's a new TB3-850F.
[Android General] MotoJunkie01:
Yes. Very buggy indeed. I have determined that the bugs are due to corruption during the unpacking of the system image. I'm repacking the ROM now to alleviate the bugs. Thanks for your input...
[Android General] MotoJunkie01:
I've managed to fix the major bugs reported upon initial install of the ROM -- Recents & Home Buttons, Quick Pulldown Menu, Google Framework bugs, New App Shortcut bugs, etc. Simply corruption during packing (archiving) the ROM zip. I will try my best to get a new build posted sometime today.
[Android General] D-Assault:
Dear MotoJunkie

İs it possible to upload stock Fm Radio Aplication(offline radio) of Tab3 8? İn my Turkish model, theres no Fm radio aplication. I need it to use tablet in my car.

Thanks
[Android General] rongallant:
Did you get around to uploading it? I am unable to use the OTA update file. Says its missing 'android-info.txt'

Also, anyone care to point me to a way to get back to stock/unrooted?? Nooooo, I didn't backup my ROM first. That would have made way to much sense.
[Android General] spiker_80:
Hi, is this thread alive? I'm interested in solution because i have about 60 tablets and need a solution to clone form one source tablet (config, apps, wlan, users, etc.) to other 59. I have tried adb backup --twrp and it went ok, but when i tried restore it gave errors with system partition and now i can only recover tablet with factory ROM from this thread (but it is buggy and cannot put it int to production like this). Is it possible to create system rom from other working tablet? Iwill be very pleased If You can write step by step, how to create zipped rom from working device so i can then upload it to share with others.
[Android General] MotoJunkie01:
The thread is alive and I'm currently ironing out the errors on the posted ROM. The errors are due to a couple of permissions which are omitted on my updater-script file. I'll be posting an updated and hopefully error free release this week. Thanks for your interest and sorry for the delay in development. I've had a number of health issues of late and I'm now recovering.
[Android General] sailor1977:
Problem after wiping /system

Hi,

I´m new right here. I bought a new TB3-850F and wanted to flash the Original Stock Rom. After opening the Bootloader and booting into twrp like this way https://xdaforums.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786 I wiped the /data /System /dalvic and /Cache. After that I rebooted the system.

But it only shows after starting the Lenovo-Logo. No more booting. Because of this I can´t start the fastboot modus with Minimal ADB and Fastboot.

Is there some idea how I can boot into fastboot?

Many thanks for your help,

sailor1977
[Android General] sailor1977:
I´ve got a solution: After powering down, press power, wait 1 sec then hold both vol up & down also (all 3 Buttons) until vibrates. After starting in recovery Modus hold power button und press once the vol up.

With help of: https://xdaforums.com/android/help/lenovo-tab3-8-2016-custom-recovery-t3483454 post #66
[Android General] MotoJunkie01:
Ok. I've debugged the Stock 6.0 ROM in the OP. Fixed the Bluetooth force close issue at startup and the bugs involving the hardware buttons and the pull down menu. I'm traveling for work at the moment. Soon as I'm back home Monday I'll post the fixed build in the OP.
[Android General] Hemphiz:
Cheers buddy. Good stuff ??
[Android General] MotoJunkie01:
[MENTION=6939319]Hemphiz[/MENTION], I hope all is well my friend. Something I wanted to get your input on. It seems that a few members have been experiencing boot loops and other problems after following the TWRP & Root thread I revised. I'm sort of at a brick wall in terms of figuring out what's going on. I'm thinking that maybe there are regional variants that are incompatible with the TWRP we use. Or, it could be one of those situations where instructions are not being closely followed. What are your thoughts? Thanks.
[Android General] Hemphiz:
Hard to say mate. Im certainly no expert at this stuff. I tend to read, read abit more, then triple check things before I start flashing stuff. It worked for me first time. OEM unlock followed by flash recovery.img. That simple. So it's hard to say. Basically every thread you visit people experience problems ??
[Android General] MotoJunkie01:
You have a point there mate. Nothing ever goes 100% smoothly in the Android arena.
[Android General] rmleonard:
has anyone found a copy of the ROM file TB3-850F_S100026_160923_ROW or similar -- that is TWRP flashable?

I'm not sure why, but all copies I've found referenced initially seem "unzippable" -- (header errors or block errors) -- the files found (which have a ZIP extension) open much more readily with an UNRAR tool... weird....

I'll try flashing the individual img files after work this evening...

Thoughts?

(in this case --- google is not friendly enough - of the five or six files found, none flash correctly - and most have errors...)

I'm not looking for anything custom -- just a stock ROM for the TB3-850F

MotoJunkie's file will be here when it gets here --- BUT in the meantime -- the stock file would be nice.....

THANK You!!

Rich Leonard
[Android General] MotoJunkie01:
I'll be posting my fixed, revised stock ROM this evening. I'll simply be replacing the current link of the ROM with a new link. I will make reference here when it is uploaded and ready. Keep in mind that it is not the most recent build and, as such, you will receive notification of an OTA upon boot up. To accept the OTA, you must be running pure stock /boot, /system/ & /recovery firmware.
[Android General] MotoJunkie01:
New build is up in the OP. I need testers because my device is currently on loan. This build consists of raw partition images and, thus, the file size is considerably larger than the previous build (1.35GB). Once I get my device back I will get my custom ROM posted.
[Android General] rmleonard:
New ROM --- 6.01?

From TWRP --- install ZIP

Updater process ended w/ ERROR: 6

Error installing zip file '/external_sd/Tab3_stock6.0.1.zip'

Updating Partition Details...

... done

?????

Rich
[Android General] MotoJunkie01:
Ahhh. I know what that is. Give me a little bit to correct it. Curious as to if you performed a full wipe first?
[Android General] rmleonard:
.... line 13? no quotes in the updater-script?

do I win the no-prize?:D:D
[Android General] MotoJunkie01:
Well, that could or could not be the issue. Try a full wipe, reboot TWRP, then try. If Error 6 persists, then I'll revise my script.
[Android General] rmleonard:
full wipe? ----- on the TWRP main screen -- I select Wipe, the swipe to do the factory reset ----

reboot --- then retry the install from zip file -- still error 6

2nd try --- Advanced Wipe (double ply method I guess?) --- I checked Dalvik/Art Cache, System, Cache, Data NOT internal Storage NOR Micro SDCard

wiped w/ out error ---

-- -- -- install -- ERROR 6 same as before ---

rebooted and am waiting for next step (and also made changes to updater-script and am trying to zip the file back up....) will try that next while waiting....

---------- Post added at 07:36 PM ---------- Previous post was at 07:18 PM ----------

Does Full Wipe mean :: "Format Data" (insert Robot wildly waving arms - - - Danger Will Robinson -- Danger!!!!)

or moving the threat level from orange up to Plaid --- via the "Partition SD Card"

or doing what I did w/ the Advanced Wipe?

Rich
[Android General] MotoJunkie01:
Full wipe: Select Wipe, Advanced Wipe, and wipe /cache, /system, /data, /dalvikART (formatting /data is optional). Ok. So Error 6 indicates that a path is incorrectly written in updater-script. Did you notice any path errors in the script? I appreciate your assistance because I'm having to do this "blind", without a device. In any event I do have Notebook ++ on my PC to write the Edify script. I'll look back over it momentarily and extract META-INF from the OTA to double check my paths.
[Android General] MotoJunkie01:
I have rewritten my script. Zipping everything back up and uploading. Should have a new link in the OP in half hour
[Android General] rmleonard:
Does the updater-script need the mount("ext4".......etc......) line (found in the updater script for Tab3_Stock6.0.zip file)????

the current script doesn't "mount" anything... it just begins w/ the package_extract_file....

---------- Post added at 08:36 PM ---------- Previous post was at 08:29 PM ----------

right now --- on reboot --- (or in TWRP telling it to reboot ---) it says -- No operating system --- (that is a good thing -- correct?)

there are no path errors (shown)

it begins:::

Updating partition details...

...done

Full SELinux support is present.

MTP enabled

Installing zip file 'external_sd/Tab3_stock6.0.1.zip'

Checking for MD5 file...

Skipping MD5 check: no MD5 file found

<RED ON>

Updater process ended with ERROR: 6

ERROR installing zip file '/external_sd/Tab3_stock6.0.1.zip'

</RED OFF>

Updating Partition details...

...done
[Android General] MotoJunkie01:
Yes. Even though twrp says no OS, continue with boot anyway. It should boot up. Great work. How long did the process take in TWRP before Error 6 returned? And no, because the script is merely flashing a raw partition image directly to the partition, mounting is not needed within the script itself. I have a new build I'm about ready to post.
[Android General] rmleonard:
More info

How long...

<blink>

.... about that long ....

I went back to beginning....

Fastboot OEM unlock

Reboot back to recovery / twrp

Reformat/wipe/etc....

Now all I can do is boot into twrp

(All is clear)

Installing 6.0.1..

It seems to just go, no pausing ....

Error 6

MISC INFO:

IF I tell twrp to ALLOW WRITES .. all hell breaks loose, partitions don't mount, errors all over...

Gets stuck in openrecovery script bootloop...

Once you clear that - and reformat ... you can get back to deciding what to do...

So, is the error 6 because it can't correctly write to system.... or are there a bunch of errors because it can't find or create mount points?

On twrp start -- allow or not allow system writes? ?

My wife says I'm getting punchy and should go to bed.... so I'll pick up from here tomorrow -- maybe from work.. else tomorrow night

Rich
[Android General] MotoJunkie01:
I've rewritten the script, re-zippped the archive, and posted in the OP. Thank you for your assistance. The Error 6 was due to absence of an assert get.prop entry in the script opening. No mounting is needed for raw partition images, since no directories are being extracted and flashed. It should work now. Thanks again. When you reboot system after flashing the ROM, TWRP may still indicate there is no OS, and ask "are you sure?" Ignore this and commence with booting of the OS. You may notice, also, my script notes this device as "TB3-850M" in my get.prop assert line. This is because TWRP identifies this tablet as TB3-850M, even though the model is TB3-850F. This is likely because the TWRP was originally rebased for TB3-850M and was ported to TB3-850F.
[Android General] rmleonard:
Still no workie ---

in looking at the two updater-scripts ---

it never gets past the assert in the new script...

on the old script --- it gets past the assert, displays the MotoJunkie header/tag... and gets all the way down to "Stock Android 6.0 ......"

the new never displays any of that....

I am gonna try a quickie tweak of the updater script --- re-pack the doo-dad then move the dingus up to the whatsis and see if that makes a difference....

Rich
[Android General] MotoJunkie01:
Thanks. Again, your help is appreciated. Go ahead and try a mountpoint for /system. I've never had to do it on other devices, but it's worth a shot here. And any tweaks you see fit to make.
[Android General] MotoJunkie01:
I'll try and get my device back today so I can get this script working for the zip installer.
[Android General] cybrshdw:
Installing this?

installing zip file /external_sd/stock6.0_tab3.zip

chescks for md5 non found and skips

everything seems to go ok until it finishes

then its telling me zip file is corrupt

error installing zip file

then it tells me its updating partion details

and thats it, so when i reboot its stuck on lenovo screen

i can get into fastboot and recovery via holding down up vol and pluging in usb

--- when in fast boot i can fastboot flash boot boot.img but when i try the system.img it fails

-- ok why i didnt do this eirlier lol i just extracted the files to my sd card and flashed indivually with twrp everythings ok now.....
[Android General] MotoJunkie01:
Good. Did you try flashing SuperSU root script yet?
[Android General] rmleonard:
(back after a migraine bout.... -- feeling better) ---

I re-wrote the updater-script and then rezipped all of the pieces --- AND.... (taaa-daaa)

here is the updated script:::

assert( getprop("ro.product.device") == "TB3-850M" ||

getprop("ro.build.product") == "TB3-850M" ||

getprop("ro.product.name") == "TB3-850M" ||

abort("This package is for "TB3-850M" devices; this is a ""

+ getprop("ro.product.device")

+ "".")

);

ui_print(" ");

ui_print(" Android 6.0 {TB3-850F_S100026_160923_ROW}Pure Stock ROM");

ui_print(" for Lenovo Tab 3 8" TB3-850F ");

ui_print(" by MotoJunkie01@xda........07/24/2017 ");

ui_print(" ");

#

ui_print("Extracting system...");

package_extract_file("system.img", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system");

show_progress(0.750000, 0);

ui_print(" ");

ui_print("Extracting logo...");

package_extract_file("logo.img", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo");

show_progress(0.050000, 5);

ui_print(" ");

ui_print("Extracting boot image...");

package_extract_file("boot.img", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot");

show_progress(0.050000, 5);

ui_print(" ");

ui_print("Installation of Stock Android 6.0 is complete......");

ui_print(" ");

The ANDROID notes state to leave a BLANK line at the end of the file ---

I'm not sure if that means 2 LF chars or what --- but I still get that [E:...[]] error upon completion

the docs also state that white space is irrelevant --- so I made sure that I formatted the text in the assert line so that I know where/what/why quoted text is joined.

I texted/emailed/contacted [MENTION=6596524]jemmini[/MENTION] -- still no answer about an update to TWRP,

So What is next?

....

I'm going to play with script until I get the end of file error to go away.....

---

Rich Leonard

---------- Post added at 04:33 PM ---------- Previous post was at 04:17 PM ----------

Flash is done ---

setup complete ---

out of gate -- it phone home (so to speak) ---

it now wants to download: TB3-850F_S100026_160923_ROW_TO_TB3-850F_S100030_161209_ROW

Great! ----

and there are 17 updates in the Play Store ---- (I turned AUTOUPDATE off -- )

hmmm.... after a few minutes --- it still says all are "pending" --- that was an error somewhere back --- maybe the ROM updater will fix that ....

IIRC -- when the download is complete -- the device will reboot into TWRP not into the bootloader... and will not auto run the updater

but inside TWRP -- navigate to /data/data/com.lenovo.ota/app_otapackages/{long string of letters and digits}_lenovoota.zip

hmmmmm...... error --- "This package is for "TB3-850F" devices; this is a "TB3-850M" -----

okay --- I'll tweak the script back to 850F (and hope TWRP doesn't hiccup) ---- either that or I'll write a simple assert script to reset the ro...prop settings.....

More after the freeway ride home....

wheeeee... <sigh>

Rich
[Android General] MotoJunkie01:
[MENTION=4235409]rmleonard[/MENTION] nice work. You've been a life saver on this with my device on loan. Thank you. If you want to upload, I'll get your revised version, upload myself and link it back in the OP, giving you credit for your work of course. Go ahead and list yourself as well in the updater-script. After all, you got it going.

To ensure that the update takes, flash stock recovery just long enough to take the OTA, then reflash TWRP.
[Android General] rmleonard:
The build.prop file needs to be modded such that all TB3-850M references become TB3-850F...

This has to happen in both the system.img and the recovery.img (boot.img too?)

Are the img files yaffs formatted? Ext3/4? Are the ISO type images?

What is the best/easiest way to tinker from a Linux boxen?

My tinker box is a very old core2 Intel laptop w/12GB ram, and Ubuntu 17.04.... perfect for tinkering.

I have the android ide/sdk from Google, (not sure how to create Lenovo emulator),

I'd love to be able to build a AOSP 7.0 image for the beastie....

But TWRP comes first....

Anyone have the hardware descriptor for the Lenovo?

Rich
[Android General] MotoJunkie01:
Believe it or not, the updater-script I used came directly from the OTA META-INF folder. The OTA updater-script uses 850M instead of 850F in the get.prop lines. That's the part that gets me puzzled. Great work on your revisions. I'm glad the ROM is now up and running.

The /system partition is in fact ext4, while /data I'm pretty sure is f2fs.
[Android General] rmleonard:
Old school reminder

If, as you said, the boot and recovery have the 850M embedded... then they send the ack-nak to the server which sends back the wrong OTA update, and the system which has the 850F causes the mismatch....(which sounds almost reasonable to me...)
[Android General] MotoJunkie01:
That makes sense.
[Android General] rmleonard:
Ran a few tests ...

The OTA sent, is correct.

Updating the device recovery, to twrp, causes the failure, because the boot now contains 850M (in default. Prop and build.prop) altering those files on the system.img does not help here...

I'm going to try the Hempiz files to return to a stock boot Environ... if that works, I'll stay w/ external twrp to do direct mods and let innards stay more vanilla....

Other answers... yes, the system.img file can be mounted as a loop/ext4 img on a Linux system, and if you know what you are doing... you can 'pre-load' all sorts of things... as of yet, there is no image signing on this tablet.

If the Hempiz files return device close to stock, I'll do a write up, and show all the pieces and what they do....

Rich
[Android General] MotoJunkie01:
Nice work ..
[Android General] rmleonard:
1) Hempiz files all work ---

2) external TWRP flashed over the SR3 SuperSU no problem

3) Still cannot get the OTA to work ----

it downloads (51Mb) -- left to its own --- it crashes

if I use TWRP (internal or external) the failure shows version mismatch 850F (the ota query) versus 850M (ro.product.device / etc)

I left a second message w/ jemmini --- first response didn't help --- I'll try picking apart the TWRP loader/img file and see if I can get anywhere w/ that.

is there a library w/ the Lenovo source files for TWRP somewhere?

are you familiar w/ the toolchain setup for building TWRP?

Also --- I read somewhere that the mediatek mt6735 is supposed to be 1.5 Ghz not 988Mhz

if true --- overclocking is also a possibility....

I'm off to sleep --- I'll write up work doc in the morning...
[Android General] MotoJunkie01:
With the OTA, you have the option of editing the updater-script to remove all device checks performed by the OTA while it checks for a full stock partition index. Also, very curious. Are you sure about your board platform being mt6735? Mine has the MediaTek mt8161. Could there be variances with this tablet?
[Android General] MotoJunkie01:
Quick question out of curiosity, why do you want to relock your bootloader?
[Android General] rmleonard:
I am trying to eliminate variables as to why the OTA won't work ----

so the first thing I'd like to do is to return the tablet to actual "stock" configuration ---

then go through all of the steps again ---- this time w/ out installing TWRP onto the local system to see if that is it....
[Android General] MotoJunkie01:
The oldest myth in Androidology is that an OTA won't install with an unlocked bootloader. As long as your /system, /boot, /recovery, /oem & /vendor partitions are pure unmodified stock, the OTA will install. The bootloader has no bearing on an OTA, so that may save you some work.
[Android General] rmleonard:
Is the Lenovo OTA server offline? I can no longer check system updates without receiving an error...
[Android General] MotoJunkie01:
I heard the same thing from somebody else yesterday. I'll ask somebody in the company who may have information on this.
[Android General] rmleonard:
okay ---- the OTA is back ---- BUT --- it downloads fine, reboots when you click -- brings up hungry Andy --- he munches the file --- then keels over --Dead Andy ----

after a few minutes -- the device reboots -- and comes up as before -- you can check the OTA and find it waiting to arrive ---

More poking and prodding ahead ----

Rich

---------- Post added at 12:39 PM ---------- Previous post was at 12:11 PM ----------

if someone can post their property settings this might help me...

if you haven't yet tinkered your tablet --- enable USB debugging and then start ADB

then from your Linux prompt type in

$> adb shell getprop > proplist.txt

then view the proplist.txt file -- sanitize anything that you think you don't want the world to see.... and post file here in the forum?

if system says you can't post a file

copy/paste it between "code" tags

(that will make text pretty....)

Thank You!!!!
[Android General] MotoJunkie01:
Install the app called DiskInfo from the Play Store (free). Tick all options available in app settings. It will give you a rudimentary partition map.
[Android General] rmleonard:
Not sure where to go next?!...

not sure when or how --- but it looks as though I've bricked the poor thing....

okay --- it happens ---

I've downloaded SP Flash Tool v5 1624 (for 64Bit Linux)

(yes I also downloaded/installed libusb-dev)

I more or less followed this XDA posting

I've gotten more response out of the tool by adding the UDEV rules...

Now I'm at the point where:

DA set to MTK_AllInOne_DA.bin

the scatter file from

TB3-850F_USR_S100023_1604141138_MPM0._ROW.zip

the header of the scatter file says:

config_version: V1.1.2

platform: MT6735M

project lcsh8735m_6_co

Anyone have any thoughts as to what to do next?

the tablet --- to get to the "yellow-bar" step --- does require pressing the volume_Down after starting the download in

I get BROM ERROR 3182 more often than not (S_PL_Validation_Fail)

thought I do also get S_FT_Download_Fail (4008)

in dmesg I can see the tablet "connect" when plugged in and disconnect when unplugged

a "common" message in the syslog is:::

mtp-probe: device ... was not an MTP device

I am starting SP FlashTool w/ the tablet OFF

after setting flashtool up --- I click download --- then plug in the tablet to the USB port...

the red line races... followed by the yellow line --- then pause, pause --- error....

help?