Database Info

Scoot CyanogenMod (RLS5.5) - this setup is not dead

Like i've posted in the setup thread from Liquid, this setup is the best i've tried until now, the only one that make missing call an old history in fact
Another better than ever pola 100 nand / nand setup
Download rom (5.5 version - 6 doesn't work with polaris kernel) : Scoot CyanogenMod (RLS5.5) [16.03.2011] and put it on your sdcard in a directory named andboot (at the root level)
with atool download the latest 2.6.32 kernel, modify it as desired
flash your unlocked phone following this tutorial or use atool scripting ability
update needed : none
work : everything except camera !!!! very smooth and very reliable(no missed call for 1 week, that's a revolution) and not so bad battery life
finally, development kernel seems to be not so far from "ready to production" status, with even better nand stability
we're waiting rom update and next krazykilla's kernel with polaris support, for a better stability and ability tu put data on ext4 partition
Thank you to scooter, liquid nr2jt and all androidhtccrew for their tuff work
Nand is not perfect and run corruption sometime that crash your setup : use the nand startup "backup/restore" data ability after you have configured your rom and favorite applications, to avoid loss of everything : it will create a 256Mb image of nand memory in your SD card /andboot directory that you can restore later in case of crash.
you can increment this backup later if you are happy with future modification of your rom
TIPS : noticed that setup as it is is good enough, people at cyanogenmod know their business
- Tip 1 : in atool, you can try to increase advanced battery capacity to improve accuracy because N2jrt has noticed battery calculation is not good and there's a correction factor of 1.6 to apply (i put 1900 but you can increase to 2200 in theory)
- Tip 2 : you can download Roguetool from the market to overclock your phone
- Tip 3 : try the app named killerauto from the market, it does a very good job with very comprehensive settings to free your ram in real time (and increase battery life)
- Tip 4 : In cynogenmod parameters/performance : check the "keep home in memory option" and activate compcache (10%) to get better result - i don't activate JIT
- Tip 5 : i've noticed that's the battery widget is cause of some trouble sometime, you can get rid of it in this case

what's next
- make polaris' atool development kernel compatible with release 6 : thx to scooter and liquid by advance
- Make crazykilla kernel with ext4 support available for polaris (release from his #54 thread doesn't work for me) or maybe unified every kernel to get the best one

crazykilla's kernel is a usual kernel without the polaris support compiled, i don't know why the #54 version don't work and i can't test it anymore (my polaris has a toasted nand).

l1q1d said:
crazykilla's kernel is a usual kernel without the polaris support compiled, i don't know why the #54 version don't work and i can't test it anymore (my polaris has a toasted nand).
Click to expand...
Click to collapse
i get the error message
"install module for this kernel
apply modules/androidupdate.tgz
Failed
from sourceforge"
maybe i missed something

Blinking screen
I've tried it with my XDA Orbit II and all I get is the white blinking screen after running haret. It's written in the man that it takes a lot of time, so I left it and went to sleep When I woke up, the screen was still blinking the same way and had to remove the battery to reboot. WM booted fine, there were files system.img and data.img created on the microsdcard of the size of 300mb (I don't want to flash it on NAND as it is my first attempt to install new software on phone). I tried Froyo, now trying Eclair and after an hour it looks the same. What might be wrong? Should I try stable kernel or other setups?

Krysiul said:
I've tried it with my XDA Orbit II and all I get is the white blinking screen after running haret. It's written in the man that it takes a lot of time, so I left it and went to sleep When I woke up, the screen was still blinking the same way and had to remove the battery to reboot. WM booted fine, there were files system.img and data.img created on the microsdcard of the size of 300mb (I don't want to flash it on NAND as it is my first attempt to install new software on phone). I tried Froyo, now trying Eclair and after an hour it looks the same. What might be wrong? Should I try stable kernel or other setups?
Click to expand...
Click to collapse
i don't know such setup sorry, i work on nand only to get real speed

I don't want to try flashing on NAND until I find a setup that would satisfy me and work well as I would in practice lose the phone for some time while trying to make it work. So far I've succesfully installed this, but I can't make the PIN code work. I tried to disable it in WM in phone settings, but when I do it, it requires me to enter the PIN, and doesn't accept it, just as Android does :/ Does the PIN code problem occurs in NAND installation as well?

this setup is really not ready. i tried so many times and it always hangs and at the end you'd be reinstalling the system back. I'm sticking back to the Not-So-Super-Froyo setup and has since found it to be very very stable although no camera and no GPS working on it. Just a bit of tip to all those who try and occasionally reinstall, after you have found a good stable setup, install your basic favorite apps and games, then get reboot the phone, access the Android Boot Menu and choose Backup Data on the choices. The system will save your stable setup on an image file on your sdcard. So anytime you have a system crash, you can just choose to Restore Data from the Boot Menu. Saves you a lot of installation.

arzakem said:
this setup is really not ready. i tried so many times and it always hangs and at the end you'd be reinstalling the system back. I'm sticking back to the Not-So-Super-Froyo setup and has since found it to be very very stable although no camera and no GPS working on it. Just a bit of tip to all those who try and occasionally reinstall, after you have found a good stable setup, install your basic favorite apps and games, then get reboot the phone, access the Android Boot Menu and choose Backup Data on the choices. The system will save your stable setup on an image file on your sdcard. So anytime you have a system crash, you can just choose to Restore Data from the Boot Menu. Saves you a lot of installation.
Click to expand...
Click to collapse
Yes i've read this technique somewhere, maybe i will try it next time
thank you for the tip anyway

Krysiul said:
I don't want to try flashing on NAND until I find a setup that would satisfy me and work well as I would in practice lose the phone for some time while trying to make it work. So far I've succesfully installed this, but I can't make the PIN code work. I tried to disable it in WM in phone settings, but when I do it, it requires me to enter the PIN, and doesn't accept it, just as Android does :/ Does the PIN code problem occurs in NAND installation as well?
Click to expand...
Click to collapse
yes if i remember well my past haret experience, i had to deactivate PIN in WM to make android work

arzakem said:
although no camera.
Click to expand...
Click to collapse
what kernel do you use ? i use liquid's 2.6.25 + kernel update
I finally follow your advise and came back to "not so super" and begin to use the "backup data" function...
The best setup so far

I've tried deactivating in WM, but that doesn't work as I've written above. I also tried to disable PIN using my friend's LG AT&T and it didn't work either so I guess I have to try some PC software or go to my service provider and ask them to do it. Thanks for replies.

chourmovs said:
what kernel do you use ? i use liquid's 2.6.25 + kernel update
I finally follow your advise and came back to "not so super" and begin to use the "backup data" function...
The best setup so far
Click to expand...
Click to collapse
lol i've read about the 2.6.25 working camera several times yet i chose to follow the blunt idea that "everything current is best ever" setup.
Anyway ill follow your advise now hehe and finally will have a working camera back again. anyway we have a backup hehe. Thanks man!!!
by the way, i liked your post title a lot haha.

arzakem said:
anyway we have a backup hehe.
Click to expand...
Click to collapse
yeah that's why i try other roms today (i'm in a rom rush ) to see if situation is better with backup trick
i saw the great nr2jt say in a topic that he save is data every morning to prevent its loss
that's why i give another try with scoot 5.5 with liquid's 2.6.32
Hey liquid do something for us to use 6 release

post 1 updated

After numerous builds+kernels, loads of frustration (and the inevitable revert to wm for a while) I think I like this setup. Simplicity at its best, Scoot CyanogenMod (RLS5.5) and latest 2.6.32 from atools as per 1st post. Just re-purposed the camera button as 'home'. Even my headset works, albeit intermittently.

Which settings for ATools for pola200?
Hi,
i tried to install this rom on my german pola200. But on the Linux Bootscreen the text is scrolling down and sayes that it installs the rom. But than it scrolls down error messages.
I tried this for houres but it shows no final error or something. The Text is scrolling on and on.
So i think that i used the wrong settings in atool. I used this tutorial to set up atool: http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsNand
What settings should been used?:
- What version to select?: Donut, Eclair or Froyo?
- Best settings for sd-card-partition? I used first partition 3 gb fat32, second partition 1 gb ext2.
- where should i install system and data? Both on second sd-partition? Or should there be a third partition? (the first time i tried to install the system on intern memory but install runs out of space)
Can you please explain the right settings in atool?

best version is froyo.
to choose sd-card partition, you must have your sdcard PREPARED beforehand. Atool does not partition your sdcard for you. As of what to use to partition your sdcard you can search it at google. (im sorry im a little bit short on time now). choose NAND on both system and DATA.

atools has sd partioner inside so you can repart sd card (boot script editor Y), but the sdcard must have only one partition on it (fat32).

i stand corrected thanks l1qu1d.

[Q] Simply Honey Revolution 5.1 on SGS

I've got some questions regarding the install documentation of Simply Honey 5.1 Revolution for SGS ROM
Install Instructions Coming From Froyo OR ECLAIR(CM7/MIUI ODIN TO STOCK FIRST)
First Question regarding CM7 - Does this include CM7.1 as well? The example outside the parenthesis says Froyo or Eclair - CM7 is GB so this is not clear
- 1. Disable any Lagfix.
- 2.Download - xxx LINK REMOVED xxx This is the light version with hardly any apps and only one keyboard and 4 lock screens.
- 3. Flash via ODIN. USE 512PIT FILE.
- 4. Let phone boot. Wait 15 minutes and reboot.
- 5. Enjoy. You may now proceed to the MediumOR Large.
What is the difference between medium and large? Where are these files? I see a Light and Full but nothing else.
[/SIZE]
Install Instructions
Coming from Any Gingerbread Rom (If bootloaders aren't installed or you have trouble follow steps above.)
CM7 issue listed above. Any GB rom sounds like any - including CM7 this adds to the confusion of what will/won't work here.
1. You must first be running a Gingerbread rom (Doesn't matter Lindroid, Rainbows, your cousins top secret GB rom.) If you are not then please follow instructions above.
2. Place SimplyHoney5Beta1.zip on your SD card
Filename is out of date. Please link new file or list correct filename. If the ROM is out of Beta, the filename in the instructsions should reflect this.
3. Use rom manager or flash through recovery.
4. Let phone boot. Wait 15 minutes and reboot.
5. Enjoy
The new script is wipe for who come from SH <3.3 and from Froyo/GB!
It doesn't do wipe if you're running SH 3.5+ ROMs! Very Simple and automatic!
I've called it the "Anti-Noob" Script!
ONLY FOR CWM VERSIONS!! ODIN VERSIONS ALWAYS DO WIPE!!
Downloads CWM Full Roms
Simply Honey 5.1 Final
Light: xxx LINK REMOVED xxx 5 Locks Screens/ Modify Power Control Menu Options
Full: xxx LINK REMOVED xxx 10 Lock Screens
What is the purpose of Update1? Should this be flashed after Full? Is it flashed through CWM recovery? Some additional information here might be helpful. It is linked but no indication of why or when one would use it.
- Update1 - Gallery3D, Polaris Office, SNS Account -
xxx LINK REMOVED xxx
Is this section below a second set of instructions - you seem to list a If you have problems section above; however this one is more comprehensive. I'm not sure which one to follow if I have problems.
HOW TO
The anti-noob install script is a double edge sword so to speak. On one hand it is convinient as it doesn't do a wipe install if already on Simply Honey 3.5 and up. On the other some data needs to occasionally be wiped. That said if you experience ANY problem please follow the steps below.
1. Force Close of certain apps...go to settings/applications/manage applications/all and clear data of the offending app.
If that doesn't work then use Tiatnium backup to wipe data and uninstall the app (as long as it's not a system app such as phone or contacts or settings, you get the picture. Now you are free to re-install the app.)
2. The next step is to try and re-install the rom. Boot into recovery and select install from SD. After it's done and you reboot give it the 15 minutes. Now try again to recreate the original problem.
3. If the problem persists then boot recovery and wipe data factory reset and re-install the rom.
4. Problem still there then ODIN to stock (Stock ROM recommendation?)with repartition, ODIN the Simply3.8 Odin/Heim package. After rebooting boot into recovery and install the latest release of Simply Honey.
If these instructions are still useful, please link to SH 3.8 Odin/Heim package pls.
5. If all else has failed make a backup of everything you want saved to your computer. Boot recovery and go to mounts and storage and select format SD. After it's done reinstall Simply Honey's latest release.
6. If your problem still remains after doing all of this or just the last step then I suggest finding another rom as this one may not be for you.
I made an attempt to convert from CM7.1 this weekend; it wasn't clear what was going wrong but I couldn't get SH 5.1 to load properly. I tried to Odin the SimplyHoney 5.1 light version as per the first group of instructions, however, it was unclear whether I needed to repartition or not. the phone began the robot voice indicating partitions were not correct. I odin'd back to stock and reflashed CM7 with no problems.
Please understand I'm not trying to be critical, and I have rooted/flashed a number of phones over the years. Although I've been a fan of CM in the past, it's absolutely not where it needs to be on the Galaxy S/Vibrant and the Nightlies are not getting there fast enough. After reading the settings/features and positive comments for this ROM I'd really like to try it out, but the vague instructions and lack of links are not making this process easier.
If one of the developers can answer some of these questions, I'd be willing to assist writing documentation for this and future SH releases.

Can't Load Custom Kernels on Samsung S3

So I can't seem to be able to load certain kernels or ROMs without either having my phone freeze up entirely (I tried loading LiquidSmooth v2.37 and my phone kept displaying the Samsung symbol for about half a second, shutting off and then repeating this process over and over) or it gets through bootloader animation (on Eclipse v5.1, CM10.2, or Dirty Unicorns 4.3.1) only to show a COMPLETELY distorted and nonfunctional screen-it shows like 3 battery icons, has a huge message saying widgets loading (even though I have no widgets) or clocks and calenders, and is comprised of colors that don't match the theme of whatever ROM I currently have installed.
The steps that I took to get there were:
1. Boot the phone in CWM (version 6.0.4.3)
2. Wipe data/factory reset
3. Wipe cache partition
4. Flash ROM (zip file) from external SD card
5. Flash Gapps (zip file) from external SD card
6. Flash Kernel (zip file) from external SD card
7. Reboot phone
All of the files I have flashed have been the most current ROMs/Kernels/Gapps and I've made sure they're compatible with my phone, so I'm not sure exactly what's going on. I'm thinking it might possibly be a hardware problem since it happens with the custom kernels I've tried (I've tried it with BMS 3.4.y and dkp 4.3).
Also weirdly for some reason my root isn't lost but every time I try to reboot my phone from CWM, it tells me that that my root access might possibly be lost and it asks me if it should fix it. I haven't lost my root, but this message pops up every time I try to reboot in CWM. I've also tried fixing permissions in ROM Manager (both to make the message go away and to see if that would allow me to successfully flash a custom kernel-it didn't).
Right now I'm running Eclipse v5.1 with 3.4.56-cyanongenmod kernel (it's the one that came with it), but if anyone can help me figure out what's going on I'd greatly appreciate it. The battery life on my phone sucks-I'm only getting 4 or 5 hours with the GPS and bluetooth turned off, so I'd really like to be able to install some other better custom kernels and ROMs. Thanks in advance!

OmniRom Twlight Zone - WTH is going on?

This is my first attempt into breathing life back into my tf300t I've had for almost 3 years. Hardly used it do to the continuing blog down that always occurred and the lack of updates by Asus eventually led me to unlocking/custom rom/rooting and then soon thereafter to here. Knowing nothing about the process and procedures, although somewhat computer literate (I started on a TRS-80 in the early 80s), I did the cursory research for the uneducated I decided to try the lollipop variant of Kisskat 5.1.1. I used TWRP to make a recovery back up and then wiped/flashed/booted. Fooled around with it some but discovered a few quirks. For one, the zone closest to the Asus logo was rather warm to almost hot even if you throttle back the performance. But more importantly after installing my apps via the play store I began to notice some media issues. For one, the video was a bit choppy (I use VLC player) and my mp3s seem to be inoperable on almost any app. (I typically use Fusion and EZ Folder Player but nothing seemed to work). I kept getting issues that seemed to be related to the recognition of folders of file types. Often telling me an mp3 file was not a recognized folder or that the file type was not recognized or in some cases (EZ Folder Player) I simply could not change directories to access files. Any help in these areas may put me back in the KissKat Camp... at least until the thing catches on fire... then we can roast marshmallows and have a camp sing along.
Before jumping on the forum I thought I'd try a more simple fix - try another rom. Tried OmniRom and while not as zippy (or hot) it seemed stable enough to go with for a while. Did the Gapps recommended for the latest pop rom and the superSU file. Loaded my apps from the play store. Then decided that perhaps I should back up all my apps after having went though applying all the correct passwords and what not. Read the Titanium Backup was a the best option. Made an initial internal mem backup of all apps then read that I could create a zip of the apps to use as a recovery method off of an SD Card which sounded the better option for me (seems far more secure). Then I felt that I was at a juncture where I should test my backups before moving on the custom folders and docs and so forth only to find out a problem was in the works when the time came at an inopportune moment down the road. Well I discovered a problem. I booted into TWRP and wiped then used my recovery to bring it back to the last known state before my first flash of a custom rom (not sure if this is even a necessary step but it seemed like it certainly couldn't hurt). Then boot/re-boot to TWRP, and having read a full/complete wipe was necessary I wiped everything (Full data format - then wiped all options in the advanced wipe section other than my SD Card where I was holding my files for flashing). Then flashed (1)OminiRom 5.1.1 (2)Recommended Gapps package (3) SuperSU, and - this is where I may have had a bad moment - the Zip file generated by Titanium Backup Pro - Is this even where I can flash install this file???Was kinda lost there. Well... I think I then tapped the TWRP button for wiping/clearing the Cache / Dalvik Cache having read (although also having read to the contrary) that this was necessary to avoid a bootloop. Then I rebooted and arrived shortly thereafter at the OmniRom Boot animation of the droid bot blinking eyes and wiggling his antennae which is as far as this Rom, which once loaded and operated fine, will now go.
I have since tried several times to reload the rom only to the same end. I have even tried the latest nightly on the rom. Same result. Tried the latest version of TWRP (2 updates since the 2.8.5.0 I initially installed with) and both updated TWRPS were riddled with problems for me - Most importantly they would not reboot - had to force close via the power button only to have TWRP reboot to itself and the process start again. As well, TWRP would not do anything as no partitions were mounted nor could I mount them - just red error messages on the console screen when I attempted to do even a simple wipe. Obviously I was getting deeper into the omniRom twlight zone.
KEEP IN MIND - this is the weird part - I COULD and still can (1) Boot to TWRP and recovery to my initial recovery file I made of JB 4.2.1 stock from Asus (if it didn't suck with lag I would have stayed there to begin with) and (2) I COULD ALSO FLASH THE KISSKAT CUSTOM ROM but as I said I had issues with it which led me to try OmniRom which I thought was a good choice until the problems.
At this point, as I sit here - I have used fastboot to reinstall the TWRP 2.8.5.0 (since it was what worked initially) and I have TWRPed to the recovery JB 4.2.1 and then wiped everything using TWRP - Data Format and all advanced wipe options less my own SD Card. Another issue - I tried the latest release of KissKat #26 and this time, in addition to the problems noted earlier, I cannot seem to mount the SD Card as it is now unrecognized by the TF300t (although it worked fine in the #25 build).
I am at an impasse and any help with any of these problems would be greatly appreciated. I just want to get a decent functioning custom rom on this tablet to get some more life out of it.
Thanks in advance,
Dog.... from somewhere near the outer limits of the realm of... the twlightRom

[ROM][6.0][STOCK]{UPDATED} Lenovo Tab 3 8"/TB3-850F

STOCK ANDROID 6.0 MARSHMALLOW ROM
FOR THE LENOVO TAB 3 8"/TB3-850F
TWRP FLASHABLE ZIP
FORCE ENCRYPTION & DM-VERITY DISABLED​
DISCLAIMER: Your warranty will be voided by installing this ROM, unlocking your bootloader, or flashing a custom recovery. You hereby assume sole responsibility for any positive or negative consequences incurred by flashing this ROM. As always, flashing your Android device or otherwise altering its file system & partitions involves an inherent risk. I am not responsible for any devices which are bricked or otherwise rendered inoperable as a result of flashing this ROM. However, in such scenarios,
I will provide all support feasibly possible. Follow the simple instructions carefully and you should experience no adverse affects.
Lenovo's open source code for this ROM encompasses both the 850F & 850M variants of this tablet. Therefore, this ROM should be completely compatible with the TB3-850M as well.
NOTES:
This Stock Android 6.0 ROM is virtually unmodified. However, it should be noted that dm-verity (device mapping) and force encryption have been disabled via patched boot image. This is the most current stock OS for the Lenovo Tab 3 8"; therefore, no OTAs will need to be installed subsequent to flashing this ROM. In order to ensure that force encryption gets disabled, it is imperative that the /userdata (Data) partition is formatted in TWRP prior to Installation. Please carefully follow the below instructions.
For those members who want a pure stock experience, but also want root access of the stock OS, I'm currently compiling a deodexed & zipaligned version of this ROM, fully rooted with Magisk 14.0 & BusyBox binaries pre-installed.
SPECIFICATIONS:
Android Version: 6.0 Marshmallow
Build No: TB3-850F_S100031_171010_ROW
Kernel Version: 3.18.19
SDK Version: 23
Software Version: TB3-850F_160412
Build ID: MRA58K
Android Security Patch Level: 9/05/2017
Runtime Version: ART 2.1.0
Hardware Version: LenovoPad TB3-850F
Board Platform: MediaTek MT6735M
CPU: 64-Bit, Quad-Core Cortex A-53 - 1.0GHz
GPU: Mali T720 - 450MHz
RAM: 1GB
OS Build Date: 10/10/2017
Source Code: http://pcsupport.lenovo.com/us/en/products/tablets/a-series/tab3-8/downloads/ds112711
REQUIREMENTS:
1. Unlocked bootloader;
2. TWRP recovery;
This is a pure stock, unmodified, TWRP flashable Android 6.0 Marshmallow ROM for the Lenovo Tab 3 8". This ROM was compiled from the most recent stock /boot and /system images. However, as noted previously, the boot image has been unpacked, patched, and repacked in order to disable dm-verity and force encryption. Because raw firmware images were used in compiling this ROM, the file size is in excess of 1GB (approximately 1.35GB).
INSTRUCTIONS:
1. Download the ROM from the link provided and save it to your external micro SD card. Do not save to internal storage, as your /data partition will need to be formatted prior to installation;
2. Boot your tablet into TWRP recovery;
3. Wipe /system, /data, /cache & /Dalvik-ART cache. Also, select "Wipe", then "Format Data." This step is crucial to ensure disabling of force encryption. Please note that once installed, you may go to SETTINGS>>SECURITY and opt to encrypt the userdata on the tablet;
4. Select INSTALL, navigate to the location in which you saved the ROM zip file, and initiate installation. Flashing will complete in approximately 3 - 4 minutes;
5. Reboot system.
You should now have unmodified stock Android 6.0 installed on your Tab 3, as well as disabled dm-verity and disabled force encryption.
DOWNLOAD LINKS:
Stock Android 6.0 ROM --
TB3-850F_S100031_171010_ROW: https://drive.google.com/file/d/1iMf0Ns_XWGpYlNmXCvUsW_1DfaRMeIuO/view?usp=drivesdk
Stock Recovery Image: https://drive.google.com/file/d/1D6A7b080luzsSf0xLJSCqPBNeQLSWo94/view?usp=drivesdk
Unpatched Stock Boot Image: https://drive.google.com/file/d/1azgIrPbfJHBzZF9R4IUMxIGNga6vjipD/view?usp=drivesdk
Lenovo File Manager (APK): https://forum.xda-developers.com/android/general/app-lenovo-file-manager-lenovo-tab-3-8-t3706161
Lenovo Tab 3 8" User Guide --
TB3-850F & TB3-850M (English)(PDF): https://drive.google.com/file/d/18gCTfuZecJnlB0ddBIN02YPaDpuvmzov/view?usp=drivesdk
Older Build(s):
TB3-850F_S100030_161209_ROW: https://drive.google.com/file/d/0B1Sfod4HWfk2aTNtVmJHZGpWZEE/view?usp=drivesdk
BUGS: Please report any and all bugs, no matter how seemingly trivial or insignificant. For those members with the knowledge, please submit a proper bug report. If you are not sure how, simply provide as many facts & details as possible. If you are having problems with apps, please specify as to whether the app is from Google Play. Also, please DO NOT submit bug reports unless you are utilizing this ROM in its present form -- unmodified, pure stock. Custom kernels, mods & tweaks (e.g. Xposed framework) & any deviations from pure stock will make it futile to analyze bug reports. Instead, provide with detail the precise nature of the problem. If reporting a bug, please specify if you are rooted (systemless or system-mode) and/or have BusyBox binaries installed. Submit screenshots of bugs if possible.

Brilliant! Will download now and report back later. Thank you.

My custom ROM for this tablet should be coming out of the Android Kitchen later this evening. I've dubbed it Ethereal OS v1.1 [Android 6.0.1]. Extremely lightweight yet moderately feature packed.

MotoJunkie01 said:
My custom ROM for this tablet should be coming out of the Android Kitchen later this evening. I've dubbed it Ethereal OS v1.1 [Android 6.0.1]. Extremely lightweight yet moderately feature packed.
Click to expand...
Click to collapse
Nice!
After flashing the stock zip TWRP says unknown error. It booted up fine to where you login to your gmail and "bluetooth sharing has stopped working" pops up. Bluetooth can not be turned on within settings. I can not double swipe down to get to the notifications and the "Home" and "Recents" buttons do not seem to work although they both vibrate when pressed.
I will flash stock with SPFT and try your stock rom again.

stonedpsycho said:
Nice!
After flashing the stock zip TWRP says unknown error. It booted up fine to where you login to your gmail and "bluetooth sharing has stopped working" pops up. Bluetooth can not be turned on within settings. I can not double swipe down to get to the notifications and the "Home" and "Recents" buttons do not seem to work although they both vibrate when pressed.
I will flash stock with SPFT and try your stock rom again.
Click to expand...
Click to collapse
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.

Seemed to work, however the loading images and screen is still lenovo. Also they lenovo apps are still there.

rongallant said:
Seemed to work, however the loading images and screen is still lenovo. Also they lenovo apps are still there.
Click to expand...
Click to collapse
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.

MotoJunkie01 said:
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.
Click to expand...
Click to collapse
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.

rongallant said:
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.
Click to expand...
Click to collapse
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...

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.

MotoJunkie01 said:
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.
Click to expand...
Click to collapse
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

MotoJunkie01 said:
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.
Click to expand...
Click to collapse
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.

I've been out of commission, unfortunately, due to impending health issues once again. I know that hospital food sucks, that the pretty nurses don't typically put out easy, and that the hospital WiFi restrictions can easily be bypassed with a proxy server address. Lol. And that's all I've learned in the past ten days. Anyway, hope to be back in my daily routine in the next day or so and finishing some stuff up for this device.

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.

spiker_80 said:
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.
Click to expand...
Click to collapse
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.

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://forum.xda-developers.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

sailor1977 said:
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://forum.xda-developers.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
Click to expand...
Click to collapse
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://forum.xda-developers.com/android/help/lenovo-tab3-8-2016-custom-recovery-t3483454 post #66

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.

MotoJunkie01 said:
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.
Click to expand...
Click to collapse
Cheers buddy. Good stuff ??

@Hemphiz, 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.