[Q] Kernel Partition Corrupt? - Moto G Q&A, Help & Troubleshooting

So I flashed C-Rom (a ROM similar to Carbon) and it worked mostly fine -- a few SystemUI crashes, and Play Music acted weirdly. However, I stuck with it until it randomly did a soft reboot. When the OS was back up, I noticed that the GPS ceased to function. Then it soft rebooted again. Up for 30 seconds. Soft reboot. It went on and on; my phone was unusable.
Until I flashed Carbon ROM -- as the last time I did it was featureless, but it had been updated -- to my device. I am currently loving it! Just as great as C-Rom but much more stable. However, something weird occurred. I tried to flash RenderBroken's Render Kernel later. I got the unlocked bootloader warning screen, but it just stayed there...I thought the ROM wouldn't boot, until I got the notification sounds all of the sudden. So the ROM booted, just the screen only showed the bootloader screen and wouldn't respond except to the power button. So I flashed CM11, flashed the kernel, same problem.
I got curious about this problem, and noticed that an issue that appeared with it is that when uploading Instagram photos -- they would appear as a black box, on both Carbon and CM11. So I plugged my phone into my PC, ran LogCat while trying to upload an Instagram photo:
E/ConnectivityService( 1058): Can't set delayed ACK size:java.io.FileNotFoundException: /sys/kernel/ipv4/tcp_use_userconfig: open failed: ENOENT (No such file or directory)
E/ConnectivityService( 1058): Can't set delayed ACK size:java.io.FileNotFoundException: /sys/kernel/ipv4/tcp_delack_seg: open failed: ENOENT (No such file or directory)
The issue with GPM is that when playing downloaded music, the Play/Pause button has about a 10 second delay till the music stops or starts. I tried to run LogCat there, but my screen froze, the terminal wasn't showing anything and then my phone crashed and the terminal filled with errors -- a lot of them kernel related. (I also tried instagram on a Moto G running C-Rom, works fine).
So I believe that the problem is kernel related, even though I've flashed quite a few kernels recently so the partition "should" have been cleaned. Is there any way to debug the kernel and know for sure? Or how else can I go about looking for a solution? I'm a debugging noob, but I know my way around the Android OS for the most part. Any help would be greatly appreciated.

You don't mention doing a 'Dalvik cache' wipe in Recovery. I believe it's generally good practice to do this when changing kernels. I suggest you do a wipe and reflash current or alternative kernel. If you still have issues, post in the thread for that kernel.
Ultimately, you might have to return to stock firmware; since all custom ROMs [currently] are very much a work-in-progress and come with an assortment of bugs and quirks.

Just tried that, didn't work unfortunately ? The problem is it has worked for me before, so I need to figure out how to debug and fix it. So I'm curious is, how should I go about searching for it?
Sent from my Moto G using XDA Free mobile app

It sounds like you are running logcat on the phone itself, try doing it on PC via adb.
adb logcat -v long > logcat.txt​

lost101 said:
It sounds like you are running logcat on the phone itself, try doing it on PC via adb.
adb logcat -v long > logcat.txt​
Click to expand...
Click to collapse
Just did that; now what am I looking for? Because since I'm having trouble with both Instagram and getting the kernel to work, I believe they are related. So the question is how do I find the problem with Instagram? I had it only output lines with the E tag but a lot of them look like:
E/mm-camera-CORE( 506): new_ew[157]=0.813300, 0.860912, 0.809075, 0.688594, 0.837469, 0.830200, 0.790950
The file will show up in my gallery if I take it through the Instagram app, which would mean that Instagram is having trouble retrieving the file...which is what the kernel assists with, correct? I also have tried sharing to Instagram through the gallery with the same issue. So what do you think? Sounds like a kernel issue?

Related

kadspd error in latest initrd

First of all i would like to thank all the devs who spent alot of time and effort in developing android for us.
Down to business i finally got time to spend trying out android, im using haret method and i know its not as fast and complete way of using android, but im just gonna do this to provide feedback.
Alright heres my setup,
Using Atool
Polaris, 320x240 panel 1 (pola 100), no vibrate on boot, sd system, sd data. made the default.txt.
2.6.32_zImage-11-29-10-liquid-latest
androidinstall.tgz from Super Froyo release 16
androidupdate.tgz from androidhtc
Initrd from androidhtc
Installscript from atools, erase data and system, advance mode, install system, install update, fix permission, clear davik cache.
The install begins and never finishes, it keeps repeating infinitely around
INFO: task kadspd:17 blocked for more than 120 seconds.
and alot of other memory address related stuff
i did check this thread, but after a few pages i didnt see a solution there
Kaspsd:17
after some testing i think it was the initrd because i changed it dzo's last initrd from dzo and it worked. could this have to do with my sd card being class 2.
I hope this can help you guys. I'll post further results when i get more testing done.
Update:
Ok it seem, the loop is not within the install script, but the boot up process although i saw it say "Install module for this kernel", why is it installing again when the last script is still disabled?
Btw, this occurred when i tried replacing the initrd back again after the install was successful using dzo's initrd.
Dzo's initrd was causing a weird issue on wake up, the lock screen, was inverted like in a mirror. wth?
Regards,
Lord Meshadieme
waiting for more detailed results...
Um, can you be more specific im not very linux oriented.
Lets see, here's the steps, starting trying to do a fresh install which basically succeeded (this is using your kernel and initrd), but concurrently its stuck booting. BTW why does the booting process have a line saying "Install modules for this kernel" so here's the dmesg from the successful install. no bootlog since it never completes booting in the loop..
It does boot using dzo's initrd, although quite buggy, (the bootlog below is from that successful boot using dzo's initrd) i'm gonna try it again and see what works and what doesn't. anything specific you want me to check?
Update:
So far testing shows BT turning on, haven't testing file transfer or headset.
Turning on Wifi freezes the phone, already applied the androidupdate..
Calling works GSM.
Battery is showing incorrect value, there's a fix for it somewhere right? i'll search for it.
Waking up from sleep does that weird inverted screen for like a second then it goes to normal. (it is literally like a mirror, text is even flipped)
USB Mass Storage, is connecting but the drive does not show up in windows.
can't test market without internet, not sure how to use internet through usb yet.
no gprs/edge/3g to test right now.
Camera, is weird i was able to take a picture but it was a dark shade of green... but now i cant the app hangs.
cant test gps since the default map tool asks for internet too.
I think you did a really mess!!
what you call "kadspd error" is when kernel kill a script due to long time execution (you probably wait too long). The action is the message "install modules!!!!".
Please next time pay more attention!
Follow all the steps in atools guide. You forget to mix the rom with the module update!!!!
BTW install MY kernel, and apply update before the first boot.

[Q] To root or not to root for update

Hi
I have a Samsung Galaxy GT-I5801 with me for past couple of years.
Its current OS spec are:
Firmware version- 2.2
Baseband version- I5801DDJP2
Kernel version- 2.6.32.9 [email protected] #2
Build Number- FROYO.DDJP6
My phone has become kind of slow, like for even basic tasks like opening call log or messaging app, it takes good 10-15 seconds. Sometimes it even goes unresponsive when trying to end a call thus causing call to continue thus carrier balance reduction. There are no 3rd party apps installed on it. Even updating the pre-installed apps gives the message of memory being low.
Now my query is:
Will flashing it to a custom ROM will improve its working at least in the basic areas of call and texting?
If so, then which is the most suitable custom ROM?
Is it necessary to root the phone before flashing it ?
Which tool is best/easiest for said purposes?
Please go easy on me, I've been out of the IT and tech game since past 1 year and bit rusty on these things
RudraP said:
Will flashing it to a custom ROM will improve its working at least in the basic areas of call and texting?
If so, then which is the most suitable custom ROM?
Is it necessary to root the phone before flashing it ?
Which tool is best/easiest for said purposes?
Click to expand...
Click to collapse
I would say yes. I don't know what is causing the freezes, but (beside that this could also be a hardware problem) a custom ROM should fix that.
Any GB-based ROM should do a fine job. There are also Froyo-based ROMs for our device. The CM7.2 build by marcellusbe does a very good job.
Nope. If you flash via Odin (Flash-Software for Windows) you just need a usb-connection. If you flash it via recovery, you may need to flash a custom recovery first.
Derp - another proud Galaxy3 user :highfive:
DerpyDerp said:
I would say yes. I don't know what is causing the freezes, but (beside that this could also be a hardware problem) a custom ROM should fix that.
Any GB-based ROM should do a fine job. There are also Froyo-based ROMs for our device. The CM7.2 build by marcellusbe does a very good job.
Nope. If you flash via Odin (Flash-Software for Windows) you just need a usb-connection. If you flash it via recovery, you may need to flash a custom recovery first.
Derp - another proud Galaxy3 user :highfive:
Click to expand...
Click to collapse
I tried SuperOneClick but it failed to even detect my phone, let alone root. Tried rooting directly through phone by installing z4root on it. It too failed to root my device, just a blue screen saying "Running Exploit" with z4mod logo kept on displaying for 10-15 minutes, after which phone switched off itself. Had to power it back on myself. Tried it couple of times more but no success.
So now if I use Odin to directly flash the firmware to a modded one, would it work, considering the fact that the phone hasn't been rooted. More importantly, would it be wise to do so? Don't want to hard brick the device as its my backup device after my Xperia SP took a plunge in the water and now fails to even boot, just vibrates thrice and that's it.
Update:
Took a leap of faith with Odin and Cyanogen & now the device is rockin' like a grandma with a new hip replacement Lags no more, operation is smooth, but a 2nd minor problem has cropped up.
It now refuses to install any app from Play Store citing Insufficient Space. I changed the default installation space to external but still the problem persists.
Update 2:
For my above mentioned problem, looks like something to do with Gapps but I don't know what it is and what to do about it. Moreover as today I tried to make calls or send messages, I found out I'm unable to do so. The dialler dials after good 2-3 minutes of pressing/selecting the dial option for a number while message inbox is empty but it refuses the receive any sms citing Inbox is full. I thought just flashing the firmware should do the trick but looks like it just was the tip of the iceberg.
You can find the gapps (Google Apps - like Play Store, Gmail, ...) here:
http://goo.im/gapps/
Assuming you're on Gingerbread (CM 7.x) it's this package: http://goo.im/gapps/gapps-gb-20110828-signed.zip
Put this zip-file on your SD card, power off your phone and/or reboot to recovery. Navigate to "Select zip from sd card" -> select your gapps.zip and flash. Then "wipe cache" and "wipe dalvik cache" anywhere in the submenus Just to make sure the gapps get recognized correctly.
Another trick for expanding the internal storage is Link2SD. You need a 2-partition sd-card for this. 1. partition with FAT and 2. one with ext2/3/4
Link2SD will mount this second partition to the internal storage to expand your storage for apps and other system stuff.
You know... Getting the most of a half-dead low-end device needs a bit of geekiness
bad zip
Well I selected erase all data option in the phone which booted it into recovery mode. Here I cleared the cache and the user data. When I tried to install zip file from sd card it gave the following error message, "Can't open /sdcard/gapps-gb-20110828-signed.zip (bad) Installation Aborted"
What seems to be the problem now?
Update:
Tried again and this time it worked. Now everything is running fine. Thanks a ton for the help mate, can't express my gratitude through words.
I do want to ask one thing here.
If I install this, http://forum.xda-developers.com/showthread.php?t=1803180, will the JB experience be coupled with performance drop ?
Honestly Cyanogen has turned me into a junkie, now I want to try on the new but stable mods. Moreover as my Xperia SP is now out of warranty, I'm planning to get it fixed and then root and flash it too!

[Dev][WIP][Wi-Fi&BATTERY FIX]

Nothing to see here
Keep
Require users of this device to obtain logs.
I would like both operating system logs (logcats) and kernel logs (dmesg)
Would like both these from a fresh boot for each of these logs. e.g. Fresh boot -> let device sit for 3minutes -> enable wi-fi (one for logcat and another for dmesg
With USB debugging enabled and ADB installed on your computer, type in terminal/CMD:
adb shell logcat > LOGCAT.txt
adb shell dmesg > DMESG.txt
Please upload to devhost or gdrive, thanks
Shaky156 said:
Require users of this device to obtain logs.
I would like both operating system logs (logcats) and kernel logs (dmesg)
Would like both these from a fresh boot for each of these logs. e.g. Fresh boot -> let device sit for 3minutes -> enable wi-fi (one for logcat and another for dmesg
With USB debugging enabled and ADB installed on your computer, type in terminal/CMD:
adb shell logcat > LOGCAT.txt
adb shell dmesg > DMESG.txt
Please upload to devhost or gdrive, thanks
Click to expand...
Click to collapse
Hey there! I hope you can help me to find out the origin or solution of the Blake_wakelock.
Here you can find my logcat and the DMESG, nevertheless, the DMESH seems to be broken, that was the input i got. Hope it works:
https://drive.google.com/folderview?id=0B2za6z4lr1pxb2xNLVNma3ExZGM&usp=sharing
CM17X said:
Hey there! I hope you can help me to find out the origin or solution of the Blake_wakelock.
Here you can find my logcat and the DMESG, nevertheless, the DMESH seems to be broken, that was the input i got. Hope it works:
https://drive.google.com/folderview?id=0B2za6z4lr1pxb2xNLVNma3ExZGM&usp=sharing
Click to expand...
Click to collapse
Your system contains a tonne of errors, and fatal errors. It is best for you to wipe the whole system and install the recovery os image provided by nvidia.
The dmesg has no logging in there
Shaky156 said:
Your system contains a tonne of errors, and fatal errors. It is best for you to wipe the whole system and install the recovery os image provided by nvidia.
The dmesg has no logging in there
Click to expand...
Click to collapse
God. What kind of errors if may i know. For the record, my system is as it was shipped from nvidia, i didn't installed another one, except that i made some changes disabling service; may it affect?
Thank you.
CM17X said:
God. What kind of errors if may i know. For the record, my system is as it was shipped from nvidia, i didn't installed another one, except that i made some changes disabling service; may it affect?
Thank you.
Click to expand...
Click to collapse
Yes disabling services will affect the stability of the device!!!!
I recommend NOT to do that.
Shaky156 said:
Yes disabling services will affect the stability of the device!!!!
I recommend NOT to do that.
Click to expand...
Click to collapse
I agree with you, but some of them are just useless and hog my battery; for example, why do i need a wereable or fitness service running in the background all the time if i don't even know the extra gadgeds for that? Also, Location services and Analytics services still running all the time and preventing my device go to sleep, so, what other thing can i do different of install a tasker or greenify which cause more troubles?
CM17X said:
I agree with you, but some of them are just useless and hog my battery; for example, why do i need a wereable or fitness service running in the background all the time if i don't even know the extra gadgeds for that? Also, Location services and Analytics services still running all the time and preventing my device go to sleep, so, what other thing can i do different of install a tasker or greenify which cause more troubles?
Click to expand...
Click to collapse
Re-enable the services, install BBS. Then provide a logcat, dmesg requires root, and a prinscreen of bbs after an hour of idle
You have or had skype installed causing errors and possibly other applications that arent compatible.
I recommend for you to do a full wipe and install nvidias recovery OS and not to touch services, then report errors and provide logs
In your post you stated Kernel Development. Would this extend to compiling the cifs modules (cifs.ko, md4.ko and nls_utf8.ko)? Would love a set compatible with the 1.2 stock kernel.
daeymon said:
In your post you stated Kernel Development. Would this extend to compiling the cifs modules (cifs.ko, md4.ko and nls_utf8.ko)? Would love a set compatible with the 1.2 stock kernel.
Click to expand...
Click to collapse
Hi I already have a custom kernel up and running, but I'm not free until next week to return to some shield development.
Shaky156 said:
Hi I already have a custom kernel up and running, but I'm not free until next week to return to some shield development.
Click to expand...
Click to collapse
To be honest, I'm not after a full blown kernel. Just the modules. As long as I have those I can use insmod to get cifs working. But there is no rush. Any help you can provide to the Nvidia Shield Tablet user base will be greatly appreciated by us all.
Here my logs:
dmesg: https://drive.google.com/file/d/0B38PAzV2Je-AVnc5c3RQYUNFcDQ/view?usp=sharing
logcat: https://drive.google.com/file/d/0B38PAzV2Je-AdEg0RDV4SWtjUlU/view?usp=sharing
logcat_wifi: https://drive.google.com/file/d/0B38PAzV2Je-AbmlTaTFacVZ4WjQ/view?usp=sharing
First 2 have been taken 2-3 mins after booting, the 3rd once I enabled wifi. Hope it helps.
johnnystuff said:
Here my logs:
dmesg: https://drive.google.com/file/d/0B38PAzV2Je-AVnc5c3RQYUNFcDQ/view?usp=sharing
logcat: https://drive.google.com/file/d/0B38PAzV2Je-AdEg0RDV4SWtjUlU/view?usp=sharing
logcat_wifi: https://drive.google.com/file/d/0B38PAzV2Je-AbmlTaTFacVZ4WjQ/view?usp=sharing
First 2 have been taken 2-3 mins after booting, the 3rd once I enabled wifi. Hope it helps.
Click to expand...
Click to collapse
Hi thank you. There are a few issues I can see with the software youre currently running on your shield tablet.
First thing is the root, supersu is causing major fatal errors within your system. This may or may not be causing a kernel error too, but a kernel error caught my eye, it is related to pmic. (so update supersu or remove root altogether)
Wi-fi does contain alot of errors too but I think we need to wait for nvidia to fix that too
Regarding Wi-Fi weak signal. Nvidia seems to have fixed this issue with their new OTA update. It seems to me that the firmware code requires changing which we cannot do.
Thanks fo the heads-up. The device is still brand new so I haven't really played properly with it. Just rooted it following the guide right here in this section and installed supersu, changed launcher and added few apps. Guess I updated the nvidia firmware first but that's all. Stock kernel, stock rom. It's all good so far, no major issues but the battery drain) is humongous. I suspect the wifi being one major issue here.
I hadn't time to play with better-battery-stats or similar yet but I noticed there's always an app that seems like wasting my battery. Yesterday it was evernote (just opened it once and never used it since) today is n7player, again, I used it cpl days ago not yesterday. If the display is taking 50-60% of the battery life and android system is always around 10-15, these apps take up to 15-25% which is clearly not what should happen. Could also be a kernel issue registering activities where there are not, so the problem being in the kernel rather than in those apps but I'm mostly guessing here..... v0v
I was waiting for an official cwm and to check those few roms out there before trying them but it really looks like the stock nvidia-rom and/or kernel is kinda borked.
Got the device today, LTE version, so I can join the testers' croud too if there's still need in testers.
updated mine to 5.0 today. I have great wifi signal.
ragzz03 said:
updated mine to 5.0 today. I have great wifi signal.
Click to expand...
Click to collapse
Ironically update 1.2.1 was "Resolve WiFi and Battery issues" even before 5.0. The thread started before that was released, so it was probably just timing. The devs over at Nvidia pay close attention to the feedback, both good and bad.

[LineageOS] List of bugs and things not working for the Official ROM

Download link https://download.lineageos.org/osprey
There is a need to maintain list of stuff not working in the nightlies, since some people have Osprey as their primary phone
The purpose of this post is for easy access to a list of bugs by both the developers and the end user
Feel free to add to the post
-mention the ROM version
-the bug
-and any other relevant information
List
version lineage-14.1-20170125-nightly
Bug : Cellular Data doesn't work after disconnecting from Wifi
Temporary Solution : Developer Options -> Cellular data always active
Bug : When music is played through headphones and charger is connected/disconnected sound is played via both the headphones and speakers. Also happens for Shutter Sound
Bug : Random Bluetooth Disconnections after long periods of bluetooth being connected
Solution : Disable Battery Optimization on all bluetooth related services
Bug: version: lineage-14.1-20170302 -lineage-14.1-20170309
Bug: Phone doesn't rescan new media such as Whatsapp images, downloaded images
Temporary Solution : Manually rescan media
Ideally it should be in the first post of the LOS thread in Original Android Dev. But if you manage to maintain it, it could be referenced.
Hey guys, my phone is stuck on "Checking for updates" and I am looking for a solution. If I install this rom will it fix my problem?
Is it as easy as downloading it, starting on bootloader and $ adb sideload thisthing.zip ?
All the help is highly appreciated, I am not interested in modding stuff or special apps, I just want my phone to run again. Thanks.
MOTO G3 - XT1540 2015
LostInTheDarkness said:
Hey guys, my phone is stuck on "Checking for updates" and I am looking for a solution. If I install this rom will it fix my problem?
Is it as easy as downloading it, starting on bootloader and $ adb sideload thisthing.zip ?
All the help is highly appreciated, I am not interested in modding stuff or special apps, I just want my phone to run again. Thanks.
MOTO G3 - XT1540 2015
Click to expand...
Click to collapse
Are you on stock rom? A simple reboot should fix the problem. And if you could send screenshots that would be good
M_Maha said:
Are you on stock rom? A simple reboot should fix the problem. And if you could send screenshots that would be good
Click to expand...
Click to collapse
If by stock rom you mean the original and official rom then yes. I've rebooted a thousand times now, wiped data and cache another thousand times, recovery/reset another hundred times, and got adventurous to flash a rom via adb sideload but it complained about invalid signature or something. Still stuck on "checking for updates".
The screenshot is a blue screen with a yellow progress line telling me "Checking for updates" just after the welcome and wifi verification., just like this one but with a different label "Software Update - Checking for updates": http://www.androidpolice.com/wp-con...nexus2cee_screenshot_20161020-090044_1024.png

[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.

Categories

Resources