Database Users

Galaxy Note 8 - GT-N5110 Update 4/22/2013...

The Note 8 model GT-N5110 has been updated in the U.S.
As of yesterday, the device is running a new kernel & the build number is now JZO54K.N5510UEDMD1.
Not sure what has changed, just said stability improvements, but as soon as I am finished building my dev environment on the new machine, I will grab the update & pot it here, unless someone beats me to it.

FYI... After applying the update I had to re-root my device.
Sent from my GT-N5110 using Tapatalk 2

Using SuperSU Pro's "survival mode" setting, I maintained root.
If anybody is interested in looking closer, here's the .zip for the update. I renamed it to the version name. It was named update.zip in the /cache/fota directory.
https://www.dropbox.com/s/qbcmt2lpb6o72po/UEDMD1.zip

MSHampton said:
FYI... After applying the update I had to re-root my device.
Sent from my GT-N5110 using Tapatalk 2
Click to expand...
Click to collapse
Using VooDoo & Koush's SuperUser, I was able to restore root with a single click! Same probably goes for others as well.

Since my 5110 is rooted, trying to force the update gives me the stock "Your device has been modified" message, so I assume I have to unroot to get this update? Any recommendations on doing just that, or is there another way around this?

Juvenall said:
Since my 5110 is rooted, trying to force the update gives me the stock "Your device has been modified" message, so I assume I have to unroot to get this update? Any recommendations on doing just that, or is there another way around this?
Click to expand...
Click to collapse
It's actually not about being rooted or not rooted. It's what you changed with that root access. If there are any system modifications, apps frozen, etc, those have to be reverted back in order for the OTA to work, but you can remain rooted and even keep root with the apps mentioned above.

I did nothing besides the root itself and I'm still getting that message. Can't update.

I too am unable to update the device due to the same Message. All I did was root and install busy box. I'm thinking the only way to be able to install the OTA at this point is to either factory reset or install the zip from recovery.
I've tried to uninstall busybox to see if that was the problem but it won't proceed with the uninstall.
Sent from my GT-N5110 using Tapatalk HD

are y'all using any apps to keep root?

What I Did to Update/Keep Root
Download/install Voodoo OTA Rootkeeper from the market and use it to make a backup su. Then download the file referenced earlier in this thread, rename it update.zip, and place it in the root directory of your external SD card.
Then unroot using Voodoo OTA Rootkeeper and boot into recovery. Install the update and reboot.
Then reroot via OTA Rootkeeper.
Viola! Updated

docfreed said:
Download/install Voodoo OTA Rootkeeper from the market and use it to make a backup su. Then download the file referenced earlier in this thread, rename it update.zip, and place it in the root directory of your external SD card.
Then unroot using Voodoo OTA Rootkeeper and boot into recovery. Install the update and reboot.
Then reroot via OTA Rootkeeper.
Viola! Updated
Click to expand...
Click to collapse
I was getting the error message like some others say they got so;
I followed these instructions except instead of downloading the file in the thread, I rebooted after unrooting and checked for software update through the about device>software update>check for updates. I did it and updated, rebooted and did it again and there was another update just a wee bit larger than the first. Cycled through both updates, rebooted, rerooted, rebooted again and I am updated with root.
Now if I can just figure out what the updates actually did.

Personally I like Koush's Superuser. No funky permissions, no paid "donation" version, just SuperUser access that works.
What I do to keep my system OTA updatable:
1. Install & launch Framaroot.
2. select "Install SuperSu", but do not reset device.
3. Install CWM's SuperUser by Koush. (This way the SU app is not in the "/system/app" folder, it is in "/data/app", which saves you some DRM headaches
4. Launch the new SuperUser & follow prompts to "Install" the new SU binary.
5. Make Backup with VooDoo
6. Open Framaroot again & select "Unroot"
7. Restore your new CWM SuperUser binary with the backup you took using VooDoo in step #5.
8. Reset device & rock & roll.
It is okay to have SU in the /System/* folder, but I find it causes issues with apps that are DRM strict, like many of the cable/dish/streaming apps, so I prefer to install it normally thru Play Store, or via file browser.

What am I missing? I updated but don't have the same build as JZO54K.N5510UEDMD1. I am using the .zip in a post on the 1st page. This is what I have...
Edit: I think I'm fine, I was getting mixed up in the original post stating its JZO54k.N5510, not N5110 as it should be. Can someone still confirm for me?
Also, the method right above mine works wonderful.

I'm waiting to hear that I'm hotter with the ladies or something else good after applying the update to want to.
From the file list, they did patch quite a bit of stuff.
ls -lR
.:
total 888
drwxr-xr-x 3 root root 4096 Apr 23 09:37 META-INF
drwxr-xr-x 3 root root 4096 Apr 23 09:37 patch
drwxr-xr-x 3 root root 4096 Apr 23 09:37 recovery
-rw-r--r-- 1 root root 887040 Jun 22 2011 sboot.bin
drwxr-xr-x 3 root root 4096 Apr 23 09:37 system
./META-INF:
total 40
-rw-r--r-- 1 root root 1772 Jun 22 2011 CERT.RSA
-rw-r--r-- 1 root root 15412 Jun 22 2011 CERT.SF
-rw-r--r-- 1 root root 15359 Jun 22 2011 MANIFEST.MF
drwxr-xr-x 4 root root 4096 Apr 23 09:37 com
./META-INF/com:
total 8
drwxr-xr-x 2 root root 4096 Apr 23 09:37 android
drwxr-xr-x 3 root root 4096 Apr 23 09:37 google
./META-INF/com/android:
total 8
-rw-r--r-- 1 root root 209 Jun 22 2011 metadata
-rw-r--r-- 1 root root 1736 Jun 22 2011 otacert
./META-INF/com/google:
total 4
drwxr-xr-x 2 root root 4096 Apr 23 09:37 android
./META-INF/com/google/android:
total 300
-rw-r--r-- 1 root root 221760 Jun 22 2011 update-binary
-rw-r--r-- 1 root root 72624 Jun 22 2011 updater-script
./patch:
total 4564
-rw-r--r-- 1 root root 4655574 Jun 22 2011 boot.img.p
drwxr-xr-x 7 root root 4096 Apr 23 09:37 system
./patch/system:
total 28
-rw-r--r-- 1 root root 142 Jun 22 2011 SW_Configuration.xml.p
drwxr-xr-x 2 root root 4096 Apr 23 09:37 app
drwxr-xr-x 2 root root 4096 Apr 23 09:37 bin
-rw-r--r-- 1 root root 204 Jun 22 2011 build.prop.p
drwxr-xr-x 3 root root 4096 Apr 23 09:37 etc
drwxr-xr-x 2 root root 4096 Apr 23 09:37 framework
drwxr-xr-x 2 root root 4096 Apr 23 09:37 lib
./patch/system/app:
total 972
-rw-r--r-- 1 root root 2046 Jun 22 2011 ApplicationsProvider.apk.p
-rw-r--r-- 1 root root 2044 Jun 22 2011 BackupRestoreConfirmation.apk.p
-rw-r--r-- 1 root root 2055 Jun 22 2011 BluetoothAvrcp.apk.p
-rw-r--r-- 1 root root 2033 Jun 22 2011 BluetoothMap.apk.p
-rw-r--r-- 1 root root 2027 Jun 22 2011 CSC.apk.p
-rw-r--r-- 1 root root 2057 Jun 22 2011 CertInstaller.apk.p
-rw-r--r-- 1 root root 2050 Jun 22 2011 DSMForwarding.apk.p
-rw-r--r-- 1 root root 2025 Jun 22 2011 DefaultContainerService.apk.p
-rw-r--r-- 1 root root 2046 Jun 22 2011 DrmProvider.apk.p
-rw-r--r-- 1 root root 2021 Jun 22 2011 EdmSysScopeService.apk.p
-rw-r--r-- 1 root root 2063 Jun 22 2011 EdmVpnServices.apk.p
-rw-r--r-- 1 root root 74275 Jun 22 2011 FactoryTest.apk.p
-rw-r--r-- 1 root root 2110 Jun 22 2011 HiddenMenu.apk.p
-rw-r--r-- 1 root root 2048 Jun 22 2011 InputDevices.apk.p
-rw-r--r-- 1 root root 2065 Jun 22 2011 KeyChain.apk.p
-rw-r--r-- 1 root root 2052 Jun 22 2011 PackageInstaller.apk.p
-rw-r--r-- 1 root root 2037 Jun 22 2011 PartnerBookmarksProvider.apk.p
-rw-r--r-- 1 root root 2072 Jun 22 2011 Personalization.apk.p
-rw-r--r-- 1 root root 2073 Jun 22 2011 PickUpTutorial.apk.p
-rw-r--r-- 1 root root 2076 Jun 22 2011 Preconfig.apk.p
-rw-r--r-- 1 root root 2118 Jun 22 2011 PreloadInstaller.apk.p
-rw-r--r-- 1 root root 308 Jun 22 2011 PreloadInstaller.odex.p
-rw-r--r-- 1 root root 540182 Jun 22 2011 SamsungApps_Tablet.apk.p
-rw-r--r-- 1 root root 162779 Jun 22 2011 SamsungIME.odex.p
-rw-r--r-- 1 root root 2133 Jun 22 2011 SecBluetooth.apk.p
-rw-r--r-- 1 root root 3423 Jun 22 2011 SecBrowser.apk.p
-rw-r--r-- 1 root root 2259 Jun 22 2011 SecCalendarProvider_Kona_Tablet.apk.p
-rw-r--r-- 1 root root 2115 Jun 22 2011 SecCalendar_Kona_SPen.apk.p
-rw-r--r-- 1 root root 3843 Jun 22 2011 SecContacts.apk.p
-rw-r--r-- 1 root root 2043 Jun 22 2011 SecContactsProvider.apk.p
-rw-r--r-- 1 root root 2058 Jun 22 2011 SecDownloadProvider.apk.p
-rw-r--r-- 1 root root 2083 Jun 22 2011 SecDownloadProviderUi.apk.p
-rw-r--r-- 1 root root 2059 Jun 22 2011 SecHTMLViewer.apk.p
-rw-r--r-- 1 root root 2652 Jun 22 2011 SecLauncher2.apk.p
-rw-r--r-- 1 root root 2062 Jun 22 2011 SecLiveWallpapersPicker.apk.p
-rw-r--r-- 1 root root 2056 Jun 22 2011 SecMediaProvider.apk.p
-rw-r--r-- 1 root root 2059 Jun 22 2011 SecOmaDownloadProvider.apk.p
-rw-r--r-- 1 root root 2112 Jun 22 2011 SecPhone.apk.p
-rw-r--r-- 1 root root 2108 Jun 22 2011 SecSettings.apk.p
-rw-r--r-- 1 root root 2038 Jun 22 2011 SecSettingsProvider.apk.p
-rw-r--r-- 1 root root 2057 Jun 22 2011 SecSoundRecorder.apk.p
-rw-r--r-- 1 root root 2078 Jun 22 2011 SecWallpaperChooser.apk.p
-rw-r--r-- 1 root root 2060 Jun 22 2011 SecurityProvider.apk.p
-rw-r--r-- 1 root root 1922 Jun 22 2011 SharedStorageBackup.apk.p
-rw-r--r-- 1 root root 2079 Jun 22 2011 Stk.apk.p
-rw-r--r-- 1 root root 2171 Jun 22 2011 SystemUI.apk.p
-rw-r--r-- 1 root root 2072 Jun 22 2011 TasksProvider.apk.p
-rw-r--r-- 1 root root 2069 Jun 22 2011 TelephonyProvider.apk.p
-rw-r--r-- 1 root root 2045 Jun 22 2011 UserDictionaryProvider.apk.p
-rw-r--r-- 1 root root 2027 Jun 22 2011 VpnDialogs.apk.p
-rw-r--r-- 1 root root 2060 Jun 22 2011 minimode-res.apk.p
-rw-r--r-- 1 root root 2116 Jun 22 2011 serviceModeApp.apk.p
./patch/system/bin:
total 12
-rw-r--r-- 1 root root 171 Jun 22 2011 debuggerd.p
-rw-r--r-- 1 root root 171 Jun 22 2011 mdnsd.p
-rw-r--r-- 1 root root 185 Jun 22 2011 wpa_supplicant.p
./patch/system/etc:
total 12
-rw-r--r-- 1 root root 151 Jun 22 2011 apks_count_list.txt.p
drwxr-xr-x 2 root root 4096 Apr 23 09:37 security
-rw-r--r-- 1 root root 556 Jun 22 2011 security_profile.dat.p
./patch/system/etc/security:
total 4
-rw-r--r-- 1 root root 203 Jun 22 2011 otacerts.zip.p
./patch/system/framework:
total 352
-rw-r--r-- 1 root root 194 Jun 22 2011 CustFeature.jar.p
-rw-r--r-- 1 root root 166 Jun 22 2011 CustFeature.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 GlobalConfig.jar.p
-rw-r--r-- 1 root root 172 Jun 22 2011 GlobalConfig.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 access.control.jar.p
-rw-r--r-- 1 root root 168 Jun 22 2011 access.control.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 allshare.jar.p
-rw-r--r-- 1 root root 172 Jun 22 2011 allshare.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 allsharelib.jar.p
-rw-r--r-- 1 root root 181 Jun 22 2011 allsharelib.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 am.jar.p
-rw-r--r-- 1 root root 174 Jun 22 2011 am.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 android.policy.jar.p
-rw-r--r-- 1 root root 177 Jun 22 2011 android.policy.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 android.test.runner.jar.p
-rw-r--r-- 1 root root 176 Jun 22 2011 android.test.runner.odex.p
-rw-r--r-- 1 root root 264 Jun 22 2011 apache-xml.jar.p
-rw-r--r-- 1 root root 184 Jun 22 2011 apache-xml.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 bmgr.jar.p
-rw-r--r-- 1 root root 173 Jun 22 2011 bmgr.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 bouncycastle.jar.p
-rw-r--r-- 1 root root 182 Jun 22 2011 bouncycastle.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 bu.jar.p
-rw-r--r-- 1 root root 169 Jun 22 2011 bu.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 com.android.future.usb.accessory.jar.p
-rw-r--r-- 1 root root 168 Jun 22 2011 com.android.future.usb.accessory.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 com.android.location.provider.jar.p
-rw-r--r-- 1 root root 174 Jun 22 2011 com.android.location.provider.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 com.google.widevine.software.drm.jar.p
-rw-r--r-- 1 root root 161 Jun 22 2011 com.google.widevine.software.drm.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 content.jar.p
-rw-r--r-- 1 root root 172 Jun 22 2011 content.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 core-junit.jar.p
-rw-r--r-- 1 root root 167 Jun 22 2011 core-junit.odex.p
-rw-r--r-- 1 root root 235 Jun 22 2011 core.jar.p
-rw-r--r-- 1 root root 177 Jun 22 2011 core.odex.p
-rw-r--r-- 1 root root 1617 Jun 22 2011 ext.jar.p
-rw-r--r-- 1 root root 177 Jun 22 2011 ext.odex.p
-rw-r--r-- 1 root root 2118 Jun 22 2011 framework-res.apk.p
-rw-r--r-- 1 root root 209 Jun 22 2011 framework.jar.p
-rw-r--r-- 1 root root 183 Jun 22 2011 framework.odex.p
-rw-r--r-- 1 root root 193 Jun 22 2011 framework2.jar.p
-rw-r--r-- 1 root root 179 Jun 22 2011 framework2.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 ime.jar.p
-rw-r--r-- 1 root root 172 Jun 22 2011 ime.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 input.jar.p
-rw-r--r-- 1 root root 167 Jun 22 2011 input.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 javax.obex.jar.p
-rw-r--r-- 1 root root 164 Jun 22 2011 javax.obex.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 kies_feature.jar.p
-rw-r--r-- 1 root root 171 Jun 22 2011 kies_feature.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 libvtmanagerjar.jar.p
-rw-r--r-- 1 root root 168 Jun 22 2011 libvtmanagerjar.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 minimode.jar.p
-rw-r--r-- 1 root root 173 Jun 22 2011 minimode.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 monkey.jar.p
-rw-r--r-- 1 root root 174 Jun 22 2011 monkey.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 multiwindow.jar.p
-rw-r--r-- 1 root root 171 Jun 22 2011 multiwindow.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 org.simalliance.openmobileapi.jar.p
-rw-r--r-- 1 root root 172 Jun 22 2011 org.simalliance.openmobileapi.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 pm.jar.p
-rw-r--r-- 1 root root 168 Jun 22 2011 pm.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 requestsync.jar.p
-rw-r--r-- 1 root root 166 Jun 22 2011 requestsync.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 sec_edm.jar.p
-rw-r--r-- 1 root root 174 Jun 22 2011 sec_edm.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 sec_feature.jar.p
-rw-r--r-- 1 root root 160 Jun 22 2011 sec_feature.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 sec_platform_library.jar.p
-rw-r--r-- 1 root root 168 Jun 22 2011 sec_platform_library.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 seccamera.jar.p
-rw-r--r-- 1 root root 176 Jun 22 2011 seccamera.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 secface.jar.p
-rw-r--r-- 1 root root 170 Jun 22 2011 secface.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 sechardware.jar.p
-rw-r--r-- 1 root root 173 Jun 22 2011 sechardware.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 secmediarecorder.jar.p
-rw-r--r-- 1 root root 169 Jun 22 2011 secmediarecorder.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 services.jar.p
-rw-r--r-- 1 root root 184 Jun 22 2011 services.odex.p
-rw-r--r-- 1 root root 196 Jun 22 2011 svc.jar.p
-rw-r--r-- 1 root root 171 Jun 22 2011 svc.odex.p
-rw-r--r-- 1 root root 2110 Jun 22 2011 twframework-res.apk.p
-rw-r--r-- 1 root root 196 Jun 22 2011 twframework.jar.p
-rw-r--r-- 1 root root 178 Jun 22 2011 twframework.odex.p
-rw-r--r-- 1 root root 194 Jun 22 2011 uiautomator.jar.p
-rw-r--r-- 1 root root 173 Jun 22 2011 uiautomator.odex.p
./patch/system/lib:
total 112
-rw-r--r-- 1 root root 43641 Jun 22 2011 libSamsungVoiceEngine.so.p
-rw-r--r-- 1 root root 251 Jun 22 2011 libbcc.so.p
-rw-r--r-- 1 root root 178 Jun 22 2011 libbcinfo.so.p
-rw-r--r-- 1 root root 184 Jun 22 2011 libchromium_net.so.p
-rw-r--r-- 1 root root 164 Jun 22 2011 libmdnssd.so.p
-rw-r--r-- 1 root root 584 Jun 22 2011 libstagefright_soft_aacdec.so.p
-rw-r--r-- 1 root root 677 Jun 22 2011 libstagefright_soft_aacenc.so.p
-rw-r--r-- 1 root root 38271 Jun 22 2011 libwebcore.so.p
-rw-r--r-- 1 root root 168 Jun 22 2011 libwebrtc_audio_preprocessing.so.p
./recovery:
total 1200
drwxr-xr-x 2 root root 4096 Apr 23 09:37 etc
-rw-r--r-- 1 root root 1217002 Jun 22 2011 recovery-from-boot.p
./recovery/etc:
total 4
-rw-r--r-- 1 root root 535 Jun 22 2011 install-recovery.sh
./system:
total 8
-rw-r--r-- 1 root root 13 Jun 22 2011 CSCVersion.txt
drwxr-xr-x 2 root root 4096 Apr 23 09:37 lib
./system/lib:
total 4
-rw-r--r-- 1 root root 20 Jun 22 2011 libbcc.so.sha1

Two Updates?
I see some folks referring to JZO54K.N5510UEDMD1 - we have of course the GT-N5110 (WiFi only) Tablets. Are these typo's? Or is there a second update?
After the first update, I have a build number of JZO54K.N5110UEDMD1. I have not seen a second update.

UEDMD1 is the latest one, just started today, or yesterday.
Sent from my SCH-I535 using Tapatalk 2

johnnyvol said:
I followed these instructions except instead of downloading the file in the thread, I rebooted after unrooting and checked for software update through the about device>software update>check for updates. I did it and updated, rebooted and did it again and there was another update just a wee bit larger than the first. Cycled through both updates, rebooted, rerooted, rebooted again and I am updated with root.
Click to expand...
Click to collapse
This is the way I ended up getting the update. Worked like a charm.
Sent from my GT-N5110 using xda premium

jntdroid said:
UEDMD1 is the latest one, just started today, or yesterday.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Actually I was referring to the "N5510" part that was stated above - I assume it should read N5110. We should all have a UEDMD1 part

Is anyone else seeing a performance hit after applying this?
I haven't gotten rid of all the junkware in /system yet (required to restore to apply the update - maybe not 100%, but as I don't have a phone I'd gotten rid of the phone stuff, so the update gacked) and that may be the cause, but I was surprised that Antutu was reporting a 3-5% performance hit after the update.

GSLEON3 said:
Personally I like Koush's Superuser. No funky permissions, no paid "donation" version, just SuperUser access that works.
What I do to keep my system OTA updatable:
1. Install & launch Framaroot.
2. select "Install SuperSu", but do not reset device.
3. Install CWM's SuperUser by Koush. (This way the SU app is not in the "/system/app" folder, it is in "/data/app", which saves you some DRM headaches
4. Launch the new SuperUser & follow prompts to "Install" the new SU binary.
5. Make Backup with VooDoo
6. Open Framaroot again & select "Unroot"
7. Restore your new CWM SuperUser binary with the backup you took using VooDoo in step #5.
8. Reset device & rock & roll.
It is okay to have SU in the /System/* folder, but I find it causes issues with apps that are DRM strict, like many of the cable/dish/streaming apps, so I prefer to install it normally thru Play Store, or via file browser.
Click to expand...
Click to collapse
Worked great now rooted. Had the update in place before so good to go.

Problem after reversing encryption! Help please!

After I tried to get rid of encryption under Android 5 and restoring a backup, I seem to have severe problems with my phone:
I'm on Slimkat Final 9.0 and had to try out encryption under Android 5.0 / CM 12 for an article. So I made a TWRP Backup plus a backup of all files on internal memory (/mnt/shell/emulated/0). Than I flashed CM 12 and successfully enabled encryption. So far so good. I got my screenshots and now I had to get back my running system.
After a few errors I made a factory reset with TWRP which deleted my internal memory as well and I'm sure I got rid of encryption. Restored my TWRP backup and was confronted with a huge problem restoring my internal memory backup. But I finally managed that as well.
What's happening now is, that at least the Google Play Store got a problem. As soon as I try to update an app, the Play Store FCs. Plus I get an error in TWRP about "Unable to locate partion and-sec".
I tried deleting app-data and app-cache as well as restoring the backup again. No dice.
file/folder rights:
Code:
[email protected]:/mnt/shell/emulated # ls -l
drwxrwx--x 91 root 1028 4096 Apr 23 06:51 0
drwxrwx--x 2 root 1028 4096 Apr 22 15:13 legacy
drwxrwx--x 7 root 1028 4096 Apr 23 05:29 obb
[email protected]:/mnt/shell/emulated/0 # ls -l
drwxrwx--x 4 root 1028 4096 Apr 23 05:29 Android
drwxrwx--- 5 root 1028 4096 Apr 22 20:54 data
How can I get my system back to how it was?

Samsung J700P CM13 Alpha builds [Testers Needed]

Hi
This thread is for cm13 on j700p testers to test the builds and report bugs , i don't test any of those builds posted here as i don't own a j700p device .
Download :
Alpha 1:
https://www.mediafire.com/download/a4w8sdezzs8umti
Alpha 2 :
http://forum.xda-developers.com/showpost.php?p=68886823&postcount=6
Alpha 3 :
http://forum.xda-developers.com/showpost.php?p=69014807&postcount=31
How to report bugs :
-Type a list of the bugs u have
- attach a logcat using syslog app [ download from here https://play.google.com/store/apps/details?id=com.tortel.syslog ]
Regards

I will test it out when i can get a copy of the EFS partition.

kernel is not seandroid enforcing
and that's it
stuck on samsung galaxy j7 logo

minz1 said:
kernel is not seandroid enforcing
and that's it
stuck on samsung galaxy j7 logo
Click to expand...
Click to collapse
Ok thank you for reporting , the kernel need some work. ..

minz1 said:
I will test it out when i can get a copy of the EFS partition.
Click to expand...
Click to collapse
You have ril broken ?

Alpha 2
https://www.mediafire.com/download/wh59bpspwlh9cbu
Changelog :
Force permissive selinux
Some cm patches

trying it out now messi
---------- Post added at 01:57 AM ---------- Previous post was at 01:31 AM ----------
didnt work even on the alpha build it stays at the j7 screen I used TWRP to flash it

Starchild2k said:
trying it out now messi
---------- Post added at 01:57 AM ---------- Previous post was at 01:31 AM ----------
didnt work even on the alpha build it stays at the j7 screen I used TWRP to flash it
Click to expand...
Click to collapse
Maybe it's a problem with the partitions size , you can check it by running :
cat /proc/mtd
And
cat /proc/partitions in adb
And post the results here

messi2050 said:
Maybe it's a problem with the partitions size , you can check it by running :
cat /proc/mtd
And
cat /proc/partitions in adb
And post the results here
Click to expand...
Click to collapse
179 0 15388672 mmcblk0
179 1 15360 mmcblk0p1
179 2 58816 mmcblk0p2
179 3 512 mmcblk0p3
179 4 32 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 768 mmcblk0p7
179 8 512 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 16 mmcblk0p10
179 11 10512 mmcblk0p11
179 12 10240 mmcblk0p12
179 13 14336 mmcblk0p13
179 14 3072 mmcblk0p14
179 15 3072 mmcblk0p15
179 16 13312 mmcblk0p16
179 17 15360 mmcblk0p17
179 18 12289 mmcblk0p18
179 19 7159 mmcblk0p19
179 20 3072 mmcblk0p20
179 21 8 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 1024 mmcblk0p23
179 24 9216 mmcblk0p24
179 25 3217408 mmcblk0p25
179 26 307200 mmcblk0p26
179 27 46080 mmcblk0p27
179 28 11621356 mmcblk0p28
179 32 4096 mmcblk0rpmb
252 0 1048576 vnswap0
179 64 62533632 mmcblk1
179 65 62532608 mmcblk1p1
this is from the original firmware

Starchild2k said:
179 0 15388672 mmcblk0
179 1 15360 mmcblk0p1
179 2 58816 mmcblk0p2
179 3 512 mmcblk0p3
179 4 32 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 768 mmcblk0p7
179 8 512 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 16 mmcblk0p10
179 11 10512 mmcblk0p11
179 12 10240 mmcblk0p12
179 13 14336 mmcblk0p13
179 14 3072 mmcblk0p14
179 15 3072 mmcblk0p15
179 16 13312 mmcblk0p16
179 17 15360 mmcblk0p17
179 18 12289 mmcblk0p18
179 19 7159 mmcblk0p19
179 20 3072 mmcblk0p20
179 21 8 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 1024 mmcblk0p23
179 24 9216 mmcblk0p24
179 25 3217408 mmcblk0p25
179 26 307200 mmcblk0p26
179 27 46080 mmcblk0p27
179 28 11621356 mmcblk0p28
179 32 4096 mmcblk0rpmb
252 0 1048576 vnswap0
179 64 62533632 mmcblk1
179 65 62532608 mmcblk1p1
this is from the original firmware
Click to expand...
Click to collapse
I need you to run this command too
ls -al /dev/block/bootdevice/by-name

messi2050 said:
I need you to run this command too
ls -al /dev/block/bootdevice/by-name
Click to expand...
Click to collapse
lrwxrwxrwx 1 root root 20 Jan 1 14:31 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 1 14:31 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 1 14:31 backup -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 1 14:31 boot -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Jan 1 14:31 cache -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Jan 1 14:31 carrier -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 Jan 1 14:31 ddr -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Jan 1 14:31 efs -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jan 1 14:31 fota -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Jan 1 14:31 fsc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Jan 1 14:31 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 Jan 1 14:31 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Jan 1 14:31 modemst1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 1 14:31 modemst2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 1 14:31 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 1 14:31 param -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 1 14:31 persdata -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Jan 1 14:31 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 1 14:31 persistent -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 Jan 1 14:31 qhee -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 1 14:31 qsee -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 1 14:31 recovery -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 20 Jan 1 14:31 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 1 14:31 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 1 14:31 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 1 14:31 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Jan 1 14:31 system -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Jan 1 14:31 userdata -> /dev/block/mmcblk0p28

When you get the phone to boot into android I'd be more than happy to beta/alpha test, but with this being my daily driver (duh) I kinda wanna keep my buddy awake when I'm at school, but if it gets really rough then I'll pitch in, but yea same error here
"KERNAL IS NOT SEANDROID ENFORCING"
I would donate but I have no job and alas no money.
Good luck though! Can't wait to see CM13 running on the J700P, shoulda gone with Verizon, lol.

LexignisOfficial said:
When you get the phone to boot into android I'd be more than happy to beta/alpha test, but with this being my daily driver (duh) I kinda wanna keep my buddy awake when I'm at school, but if it gets really rough then I'll pitch in, but yea same error here
"KERNAL IS NOT SEANDROID ENFORCING"
I would donate but I have no job and alas no money.
Good luck though! Can't wait to see CM13 running on the J700P, shoulda gone with Verizon, lol.
Click to expand...
Click to collapse
Look at Xiaomi for your next phone. IIRC they have CDMA bands.

minz1 said:
Look at Xiaomi for your next phone. IIRC they have CDMA bands.
Click to expand...
Click to collapse
I want a more popular/mainstream phone I'd love a nexus but I'm thinking I might have a wider selection of roms if I went Galaxy.
Thanks for the suggestion though, I'll look into it, it's gonna be a while before I cut myself off from Virgin Mobile (can't stand the signal though).

LexignisOfficial said:
I want a more popular/mainstream phone I'd love a nexus but I'm thinking I might have a wider selection of roms if I went Galaxy.
Thanks for the suggestion though, I'll look into it, it's gonna be a while before I cut myself off from Virgin Mobile (can't stand the signal though).
Click to expand...
Click to collapse
nononononononononono
if you like roms, don't get a samsung phone. xiaomi has more rom selection than samsung. pls pls pls don't get a galaxy in general if you like your experience on xda

minz1 said:
nononononononononono
if you like roms, don't get a samsung phone. xiaomi has more rom selection than samsung. pls pls pls don't get a galaxy in general if you like your experience on xda
Click to expand...
Click to collapse
Well its gonna be a while and ive done 0 research so calm yourself
Sent from my SM-J700P using Tapatalk
---------- Post added at 03:49 AM ---------- Previous post was at 03:22 AM ----------
minz1 said:
nononononononononono
if you like roms, don't get a samsung phone. xiaomi has more rom selection than samsung. pls pls pls don't get a galaxy in general if you like your experience on xda
Click to expand...
Click to collapse
Also you still need that efs partition? I replied to a week old thread and dunno if its still relevent
Sent from my SM-J700P using Tapatalk

LexignisOfficial said:
Well its gonna be a while and ive done 0 research so calm yourself
Sent from my SM-J700P using Tapatalk
---------- Post added at 03:49 AM ---------- Previous post was at 03:22 AM ----------
Also you still need that efs partition? I replied to a week old thread and dunno if its still relevent
Sent from my SM-J700P using Tapatalk
Click to expand...
Click to collapse
Oh no, I'm just going to replace this phone. If you want to send it I'll try using it to fix my phone, but I'm set on a new one.

minz1 said:
Oh no, I'm just going to replace this phone. If you want to send it I'll try using it to fix my phone, but I'm set on a new one.
Click to expand...
Click to collapse
Why not? If you ever decide to pickup again you'll be glad it's alive and it doesn't take to long to backup w/ TWRP

How about keeping this thread clean for tester posts only... Btw Ill be buying an iphone soon afterwards if this project is still going ill donate this phone to the cause and use it for testing. (I hop back and forth between boost mobile phones)
Sent from my SM-J700P using Tapatalk

Synz86 said:
How about keeping this thread clean for tester posts only... Btw Ill be buying an iphone soon afterwards if this project is still going ill donate this phone to the cause and use it for testing. (I hop back and forth between boost mobile phones)
Sent from my SM-J700P using Tapatalk
Click to expand...
Click to collapse
+1 for this , guys please take your conversations to the pm , I'm busy with my college those days but i will try to create a bootable build in the next days and will share it here to test

Lenovo Tab 4 8 Plus (aka TB-8704F/X)

It's been released in Europe for quite some time and from what I'm hearing it's about to hit the American market as well. Doen't seem to get any love yet on XDA.
Lovely little thing, from my three days with it. S625/64GB/4GB RAM/SD Slot/LTE. Comes with Android 7.1.1 stock.
Looks likes something that could finally replace the N7 2013, provided the community picks it up. I'm honestly surprised there's been little to no chatter about it whatsoever.
Did anyone manage to compile TWRP for it yet or root it otherwise?

wonderfulme said:
It's been released in Europe for quite some time and from what I'm hearing it's about to hit the American market as well. Doen't seem to get any love yet on XDA.
Lovely little thing, from my three days with it. S625/64GB/4GB RAM/SD Slot/LTE. Comes with Android 7.1.1 stock.
Looks likes something that could finally replace the N7 2013, provided the community picks it up. I'm honestly surprised there's been little to no chatter about it whatsoever.
Did anyone manage to compile TWRP for it yet or root it otherwise?
Click to expand...
Click to collapse
I don't own the device so I cannot help you there. But what you can check is if the device can be bootloader unlocked in developer settings. That's a requirement for TWRP and also what you need is a kernel/boot image to build TRWP. Since there don't seem to be factory images available for this yet it will be difficult to retrieve a boot image from the device. Also Lenovo hasn't released any source code for this yet even though they are obliged to do so. Shame on them! I suggest you complain in the Lenovo forums about it. It's clearly a GPL violation.

matshias said:
I don't own the device so I cannot help you there. But what you can check is if the device can be bootloader unlocked in developer settings. That's a requirement for TWRP and also what you need is a kernel/boot image to build TRWP. Since there don't seem to be factory images available for this yet it will be difficult to retrieve a boot image from the device. Also Lenovo hasn't released any source code for this yet even though they are obliged to do so. Shame on them! I suggest you complain in the Lenovo forums about it. It's clearly a GPL violation.
Click to expand...
Click to collapse
Thanks, I actualy did just that - asked about the kernel source on their official forum. Don't expect any major breakthroughts though (see https://forum.xda-developers.com/showthread.php?t=1555099, for instance).
As for whether the bootloader is locked or not, I have honestly no idea. Neither the "long phone number" method nor the "fastboot oem device-info" works. I have Android SDK installed and it works just fine when I plug in my N7 2003. The USB debugging is enabled and allowed for my desktop. Still, zero results. The Lenovo one doesn't even show up when running "fastboot devices".
Yet the "Lenovo Moto Smart Assistant" whatever it's supposed to do identifies the tablet when connected with USB just fine.
So I guess it's a safe bet to say that we're a long way from rooting this one. Or, more likely, I'm doing something wrong. Never had adb/fastboot issues with N7 though.
I'll just sit and wait till it hits the US market and generates some deserved interest because on the surface it's not a bad tablet at all. The battery life, the screen, the price/performance ratio, the SD slot and LTE capability all make that for a good web browser/book reader. It's not that bad looking either. Although I have yet to find a proper case unless resorting to Alibaba or something. It's even got a half-decent camera.
Overall, it's totally worth the $300 or whatever you end up paying. Comes with next to no bloatware, doesn't overheat. Even has that Dolby thing and a fingerprint scanner for some reason. Only wish it could be rooted and ran LineageOS or something.

wonderfulme said:
Thanks, I actualy did just that - asked about the kernel source on their official forum. Don't expect any major breakthroughts though (see https://forum.xda-developers.com/showthread.php?t=1555099, for instance).
As for whether the bootloader is locked or not, I have honestly no idea. Neither the "long phone number" method nor the "fastboot oem device-info" works. I have Android SDK installed and it works just fine when I plug in my N7 2003. The USB debugging is enabled and allowed for my desktop. Still, zero results. The Lenovo one doesn't even show up when running "fastboot devices".
Yet the "Lenovo Moto Smart Assistant" whatever it's supposed to do identifies the tablet when connected with USB just fine.
So I guess it's a safe bet to say that we're a long way from rooting this one. Or, more likely, I'm doing something wrong. Never had adb/fastboot issues with N7 though.
I'll just sit and wait till it hits the US market and generates some deserved interest because on the surface it's not a bad tablet at all. The battery life, the screen, the price/performance ratio, the SD slot and LTE capability all make that for a good web browser/book reader. It's not that bad looking either. Although I have yet to find a proper case unless resorting to Alibaba or something. It's even got a half-decent camera.
Overall, it's totally worth the $300 or whatever you end up paying. Comes with next to no bloatware, doesn't overheat. Even has that Dolby thing and a fingerprint scanner for some reason. Only wish it could be rooted and ran LineageOS or something.
Click to expand...
Click to collapse
Are you sure you are in fastboot mode? Can you try adb reboot bootloader and then connect with fastboot again?
Also you should check that in developer settings you have an option OEM unlock.
Well you don't need the kernel source for TWRP. What you need is the following:
* kernel image somehow extracted
* partition layout. If cat /proc/partitions works via adb then this is sufficient.
* extracted /system/build.prop and output of mount command
This should be enough to get it booting. Decrypting the data partition is another step, but for root it's not needed.
Extracting the kernel image is the hard part as long as there is no factory image available. But first check if the tablet can be unlocked otherwise it's not worth the effort.

matshias said:
Are you sure you are in fastboot mode? Can you try adb reboot bootloader and then connect with fastboot again?
Also you should check that in developer settings you have an option OEM unlock.
Well you don't need the kernel source for TWRP. What you need is the following:
* kernel image somehow extracted
* partition layout. If cat /proc/partitions works via adb then this is sufficient.
* extracted /system/build.prop and output of mount command
This should be enough to get it booting. Decrypting the data partition is another step, but for root it's not needed.
Extracting the kernel image is the hard part as long as there is no factory image available. But first check if the tablet can be unlocked otherwise it's not worth the effort.
Click to expand...
Click to collapse
There was indeed an option for "OEM unlock" in dev settings which I somehow missed. Works as intended now.
So here's the output of fastboot:
Code:
F:\AndroidSDK\platform-tools>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.054s]
finished. total time: 0.054s
Guess we're out of luck here?
I also did an "adb shell" and /proc/partitions as well as /system/build.prop are readable, "mount" works, however I have no idea where the kernel is stored. There's a "/firmware" dir but it's unaccessible, I'm thinking maybe that's where:
Code:
2|TB-8704X:/ $ uname -a
Linux localhost 3.18.31-perf-g40dd5c6-dirty #1 SMP PREEMPT Fri Jul 7 02:02:41 CST 2017 aarch64
TB-8704X:/ $ id
uid=2000(shell) gid=2000(shell) groups=2000(shell),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc) context=u:r:shell:s0
TB-8704X:/ $ ls -ld firmware
dr-xr-x--- 4 system system 16384 1970-01-01 03:00 firmware
TB-8704X:/ $ cd firmware
/system/bin/sh: cd: /firmware: Permission denied
Also, FWIW, here's a list of files/dirs in / in case I missed something of note. I'm not really comfortable with Android internals.
Code:
130|TB-8704X:/ $ ls -l
total 4232
dr-xr-xr-x 61 root root 0 1970-03-08 03:34 acct
drwxr-xr-x 2 root root 40 1970-01-01 03:00 bt_firmware
drwxrwx--- 7 system cache 4096 2017-08-10 16:42 cache
lrwxrwxrwx 1 root root 13 1970-01-01 03:00 charger -> /sbin/healthd
drwxr-xr-x 2 root root 0 1970-03-08 03:34 config
lrwxrwxrwx 1 root root 17 1970-01-01 03:00 d -> /sys/kernel/debug
drwxrwx--x 43 system system 4096 1970-03-08 03:34 data
-rw-r--r-- 1 root root 995 1970-01-01 03:00 default.prop
drwxr-xr-x 15 root root 3500 1970-03-08 03:34 dev
drwxr-xr-x 3 root root 4096 1970-01-01 03:00 dsp
lrwxrwxrwx 1 root root 11 1970-01-01 03:00 etc -> /system/etc
-rw-r--r-- 1 root root 186677 1970-01-01 03:00 file_contexts.bin
dr-xr-x--- 4 system system 16384 1970-01-01 03:00 firmware
-rw-r----- 1 root root 1578 1970-01-01 03:00 fstab.qcom
-rwxr-x--- 1 root root 1246704 1970-01-01 03:00 init
-rwxr-x--- 1 root root 1846 1970-01-01 03:00 init.carrier.rc
-rwxr-x--- 1 root root 3295 1970-01-01 03:00 init.class_main.sh
-rwxr-x--- 1 root root 1156 1970-01-01 03:00 init.environ.rc
-rwxr-x--- 1 root root 1730 1970-01-01 03:00 init.mdm.sh
-rwxr-x--- 1 root root 29161 1970-01-01 03:00 init.msm.usb.configfs.rc
-rwxr-x--- 1 root root 7054 1970-01-01 03:00 init.qcom.class_core.sh
-rwxr-x--- 1 root root 12035 1970-01-01 03:00 init.qcom.early_boot.sh
-rwxr-x--- 1 root root 3775 1970-01-01 03:00 init.qcom.factory.rc
-rwxr-x--- 1 root root 37960 1970-01-01 03:00 init.qcom.rc
-rwxr-x--- 1 root root 2029 1970-01-01 03:00 init.qcom.sensors.sh
-rwxr-x--- 1 root root 12173 1970-01-01 03:00 init.qcom.sh
-rwxr-x--- 1 root root 2962 1970-01-01 03:00 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 97623 1970-01-01 03:00 init.qcom.usb.rc
-rwxr-x--- 1 root root 10950 1970-01-01 03:00 init.qcom.usb.sh
-rwxr-x--- 1 root root 26676 1970-01-01 03:00 init.rc
-rwxr-x--- 1 root root 9584 1970-01-01 03:00 init.target.rc
-rwxr-x--- 1 root root 12058 1970-01-01 03:00 init.usb.configfs.rc
-rwxr-x--- 1 root root 5715 1970-01-01 03:00 init.usb.rc
-rwxr-x--- 1 root root 411 1970-01-01 03:00 init.zygote32.rc
-rwxr-x--- 1 root root 684 1970-01-01 03:00 init.zygote64_32.rc
drwxr-xr-x 10 root system 220 1970-03-08 03:34 mnt
drwxr-xr-x 2 root root 40 1970-01-01 03:00 oem
drwxrwx--x 13 root system 4096 1970-01-01 03:00 persist
dr-xr-xr-x 518 root root 0 1970-01-01 03:00 proc
-rw-r--r-- 1 root root 11549 1970-01-01 03:00 property_contexts
drwxr-xr-x 3 root root 60 1970-01-01 03:00 res
drwx------ 2 root root 40 2017-07-06 21:00 root
drwxr-x--- 2 root root 160 1970-01-01 03:00 sbin
lrwxrwxrwx 1 root root 21 1970-01-01 03:00 sdcard -> /storage/self/primary
-rw-r--r-- 1 root root 1957 1970-01-01 03:00 seapp_contexts
-rw-r--r-- 1 root root 90 1970-01-01 03:00 selinux_version
-rw-r--r-- 1 root root 285602 1970-01-01 03:00 sepolicy
-rw-r--r-- 1 root root 17999 1970-01-01 03:00 service_contexts
drwxr-xr-x 4 root root 80 2017-08-12 15:57 storage
dr-xr-xr-x 16 root root 0 1970-03-08 03:34 sys
drwxr-xr-x 21 root root 4096 1970-01-01 03:00 system
lrwxrwxrwx 1 root root 16 1970-03-08 03:34 tombstones -> /data/tombstones
-rw-r--r-- 1 root root 14131 1970-01-01 03:00 ueventd.qcom.rc
-rw-r--r-- 1 root root 4857 1970-01-01 03:00 ueventd.rc
lrwxrwxrwx 1 root root 14 1970-01-01 03:00 vendor -> /system/vendor
-rw-r--r-- 1 root root 524 1970-01-01 03:00 verity_key
So are we out of options yet unless a new Linux kernel exploit eventually comes along OR Lenovo decides to release the firmware? I don't believe dirtycow would work here, considering July 2017 security updates have been applied.

That's quite sad.
Just got it and been playing with it for a couple days now. Device itself seems to be fine, but not having root is PITA.

wonderfulme said:
So are we out of options yet unless a new Linux kernel exploit eventually comes along OR Lenovo decides to release the firmware? I don't believe dirtycow would work here, considering July 2017 security updates have been applied.
Click to expand...
Click to collapse
The firmwares just showed up on the Russian Lenovo forums. So we can build TWRP if you post all the prerequisites mentioned a few posts earlier (partition layout, mount output, ...)

matshias said:
The firmwares just showed up on the Russian Lenovo forums. So we can build TWRP if you post all the prerequisites mentioned a few posts earlier (partition layout, mount output, ...)
Click to expand...
Click to collapse
Here's the output for the TB-8704X LTE version.
Mount points:
Code:
TB-8704X:/ $ mount
rootfs on / type rootfs (ro,seclabel,size=1705664k,nr_inodes=426416)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1811380k,nr_inodes=452845,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,size=1811380k,nr_inodes=452845,mode=755,gid=1000)
none on /config type configfs (rw,relatime)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/dm-0 on /system type ext4 (ro,seclabel,relatime,discard,data=ordered)
/dev/block/bootdevice/by-name/cache on /cache type ext4 (rw,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/bootdevice/by-name/persist on /persist type ext4 (rw,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/bootdevice/by-name/dsp on /dsp type ext4 (ro,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/bootdevice/by-name/modem on /firmware type vfat (ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,size=1811380k,nr_inodes=452845,mode=755,gid=1000)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/dm-1 on /data type ext4 (rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered)
/dev/fuse on /mnt/runtime/default/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
Partitions:
Code:
TB-8704X:/etc $ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.6G 4.7M 1.6G 1% /
tmpfs 1.7G 652K 1.7G 1% /dev
tmpfs 1.7G 0 1.7G 0% /mnt
/dev/block/dm-0 3.6G 3.2G 336M 91% /system
/dev/block/bootdevice/by-name/cache 248M 744K 242M 1% /cache
/dev/block/bootdevice/by-name/persist 27M 512K 26M 2% /persist
/dev/block/bootdevice/by-name/dsp 12M 4.9M 6.4M 44% /dsp
/dev/block/bootdevice/by-name/modem 84M 74M 10M 88% /firmware
tmpfs 1.7G 0 1.7G 0% /storage
/dev/block/dm-1 52G 14G 38G 27% /data
/dev/fuse 52G 14G 38G 27% /storage/emulated
TB-8704X:/ $ cat /proc/partitions
major minor #blocks name
254 0 524288 zram0
179 0 61071360 mmcblk0
179 1 86016 mmcblk0p1
179 2 1 mmcblk0p2
179 3 8 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 256 mmcblk0p10
179 11 256 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 32 mmcblk0p15
179 16 32 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 16 mmcblk0p18
179 19 15360 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 65536 mmcblk0p22
179 23 65536 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 3984588 mmcblk0p25
179 26 262144 mmcblk0p26
179 27 32768 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 512 mmcblk0p29
179 30 32 mmcblk0p30
179 31 262144 mmcblk0p31
259 0 32 mmcblk0p32
259 1 512 mmcblk0p33
259 2 1024 mmcblk0p34
259 3 32768 mmcblk0p35
259 4 512 mmcblk0p36
259 5 4096 mmcblk0p37
259 6 128 mmcblk0p38
259 7 128 mmcblk0p39
259 8 256 mmcblk0p40
259 9 256 mmcblk0p41
259 10 256 mmcblk0p42
259 11 256 mmcblk0p43
259 12 256 mmcblk0p44
259 13 256 mmcblk0p45
259 14 256 mmcblk0p46
259 15 256 mmcblk0p47
259 16 8 mmcblk0p48
259 17 65536 mmcblk0p49
259 18 204800 mmcblk0p50
259 19 55492071 mmcblk0p51
179 32 4096 mmcblk0rpmb
253 0 3922408 dm-0
253 1 55492055 dm-1
/system/build.prop, just in case: https://pastebin.com/raw/jQn9N8nc
Kindly let me know if I missed anything.
Also, that Russian site lists the model number as TB-8704X_S000026_170707_ROW_QFIL, while my version of build.prop contains TB-8704X_S000026_170707_ROW (withot the "QFIL"). I'm not entirely up to date on Lenovo's naming conventions, but could that possibly suggest a slightly different model or should we disregard it altogether?
Edit: Nevermind, QFIL seems to be the name of the Qualcomm firmware update software.
Thanks!

I also hope that rooting or later a LineageOS will be available. I bought my one from Amazon in Germany 64GB/4GB/WiFi and it has following build number TB-8704F_S000024_170706_ROW. I came from Nexus 7 (2012).

Bought mine via Lenovo in the UK for £280 and loving it. I've been looking for a decent 8" tablet which wasn't stupidly expensive and this ticks all the boxes.
4GB /64GB + SD card
1920x1080 screen
Good audio with those front facing speakers
Decent battery life so far
Would love to be able to root and install Lineage as I use on my OPO as well, that would be perfect.
Love it so much I've ordered one for my old man as well.

wonderfulme said:
Thanks, I actualy did just that - asked about the kernel source on their official forum. Don't expect any major breakthroughts though (see https://forum.xda-developers.com/showthread.php?t=1555099, for instance).
As for whether the bootloader is locked or not, I have honestly no idea. Neither the "long phone number" method nor the "fastboot oem device-info" works. I have Android SDK installed and it works just fine when I plug in my N7 2003. The USB debugging is enabled and allowed for my desktop. Still, zero results. The Lenovo one doesn't even show up when running "fastboot devices".
Yet the "Lenovo Moto Smart Assistant" whatever it's supposed to do identifies the tablet when connected with USB just fine.
So I guess it's a safe bet to say that we're a long way from rooting this one. Or, more likely, I'm doing something wrong. Never had adb/fastboot issues with N7 though.
I'll just sit and wait till it hits the US market and generates some deserved interest because on the surface it's not a bad tablet at all. The battery life, the screen, the price/performance ratio, the SD slot and LTE capability all make that for a good web browser/book reader. It's not that bad looking either. Although I have yet to find a proper case unless resorting to Alibaba or something. It's even got a half-decent camera.
Overall, it's totally worth the $300 or whatever you end up paying. Comes with next to no bloatware, doesn't overheat. Even has that Dolby thing and a fingerprint scanner for some reason. Only wish it could be rooted and ran LineageOS or something.
Click to expand...
Click to collapse
I have the tab 4 8" and you can unlock the boooader know developer mode.

Anonwatch said:
I have the tab 4 8" and you can unlock the boooader know developer mode.
Click to expand...
Click to collapse
Already figured as much. You might want to take a look at matshias's thread at https://forum.xda-developers.com/thinkpad-tablet/general/twrp-root-tab-4-plus-tb-x704l-f-tb-t3664407
He's got TWRP working on both 8 and 10+.

Hey guys. I own Lenovo tab 3 8 plus (TB-8703F) and there are ads popping out everywhere when I open playstore or chrome etc? How to get rid of this?

Vicky khan said:
Hey guys. I own Lenovo tab 3 8 plus (TB-8703F) and there are ads popping out everywhere when I open playstore or chrome etc? How to get rid of this?
Click to expand...
Click to collapse
Wrong thread for your device - but install an ad-blocker

Many thanks for your great work. Everything has worked as described and I am super happy with this new tablet, replacing my Nexus 7.
I am surprised that there is so little activity around the Tab 4 here on XDA, but I am confident that once people understand that this is a really cool tablet and practically the only one with modern specs that comes close to the N7, there will be Custom ROMs and more. It's a beautiful piece of hardware and even without Custom ROM, the Lenovo Android is surprisingly lean and without bloatware (except for Microsoft Office).

Hi,guys!Just bought it from Amazon for $118(16GBROM)!
It's wonderful and I speak Russian, Macedonian, Bulgarian,German,a bit Serbian!
If you need help for Russian, just message me!:

Just had my memory card (128GB Samsung Pro) 'eaten' by my tablet - while on holiday with no computer access and it had my videos and music on it.
I've seen reports of this on other sites as well, and am fuming right now as this is an almighty ****-up if it's a regular occurrence, makes the tablet basically useless to me.
Edit: Took the card out of the tablet and stuck it in my Honor 9, no errors and all files work perfectly. Put it back in the Lenovo, so corrupt and won't let me do anything other than format it. Bloody Lenovo

jimmy19742 said:
Hi,guys!Just bought it from Amazon for $118(16GBROM)!
It's wonderful and I speak Russian, Macedonian, Bulgarian,German,a bit Serbian!
If you need help for Russian, just message me!:
Click to expand...
Click to collapse
Hate to say it, but sounds like you bought the Tab 4 8 and not the Tab 4 8 Plus. If it is the Plus, you got a steal!

magoo5289 said:
Hate to say it, but sounds like you bought the Tab 4 8 and not the Tab 4 8 Plus. If it is the Plus, you got a steal!
Click to expand...
Click to collapse
Yup 8504X not 8704X!

I saw this but am skeptical by nature and don't read Russian.
http://proshivkis.ru/?p=lenovo-tab-4-8-plus-wifi-lineageos-14-1

[Desbrick xt890] Solution to service required code corrupt

Hello, this solves service required code corrupt
Download:
Debrick-intel_blank_flash.7z.zip MD5: ea90220f2a6f080c960dcf6254463b89
Extract Debrick-intel_blank_flash.7z.zip
Extract Debrick-intel_blank_flash.7z
Contents of the folder Debrick-intel_blank_flash
Code:
-rw-r--r-- 1 621 sep 26 2014 1RSD_BlankFlash.xml
drwxr-xr-x 2 4096 abr 8 2016 Driver
-rw-r--r-- 1 1781 sep 26 2014 PFT_BlankFlash.xml
-rw-r--r-- 1 66528 sep 26 2014 dnx_firmware.bin
-rw-r--r-- 1 18073088 sep 26 2014 droidboot.img.POS.bin
-rw-r--r-- 1 8413938 sep 26 2014 droidboot.unsigned_raw
-rw-r--r-- 1 1937660 sep 26 2014 ifwi_firmware.bin
-rw-r--r-- 1 2874 ene 13 19:29 intel_blank_flash.bat
-rwxr-xr-x 1 2302 ene 13 22:32 intel_blank_flash.sh
-rw-r--r-- 1 43008 jun 22 2009 libgcc_s_dw2-1.dll
-rw-r--r-- 1 11362 ene 10 2009 mingwm10.dll
-rw-r--r-- 1 66528 sep 26 2014 osr_dnx_firmware.bin
-rwxr-xr-x 1 260 ene 13 19:52 sec_xfstk.sh
-rw-r--r-- 1 880 ago 11 2014 soft_fuse.bin
-rw-r--r-- 1 155648 ene 12 13:01 wdapi1140.dll
-rw-r--r-- 1 1377280 feb 12 2013 xfstk-dldr-api.dll
-rw-r--r-- 1 1292288 feb 12 2013 xfstk-dldr-solo.exe
From Windows
1) We enter the folder Debrick-intel_blank_flash
Install drivers "iSocUSB-Driver-Setup-1.0.4.exe" found in the "Driver" subfolder.
2) Run "intel_blank_flash.bat"
And we turn on the phone while connected to your computer
That should fix your brikck phone.
From GNU / Linux
First way:
1) Install Phone Flash Tool Lite
https://01.org/node/2463
(Depending on your favorite distribution)
2) Link "xfstkFlashTool" from the folder where you installed /usr/local/bin
3) We mark the script as executable
Code:
Chmod + x sec_xfstk.sh
and we execute it sec_xfstk.sh
And we turn on the phone while connected to your computer
Second way:
1) we install xfstk
https://sourceforge.net/projects/xfstk/
2) We connect "xfstk-dldr-solo" from the folder where we installed /usr/local/bin
3) We mark the script as executable
Code:
Chmod + x intel_blank_flash.sh
and we execute it intel_blank_flash.sh
And we turn on the phone while connected to your computer
This repairs the service required code corrupt. the best debrick for motorola razer i (xt890).
Finally flashing with rsd-lite or fastboot with the version of your favorite rom
Sorry for my English
a greetings

Hello! thank you for the magnificient support... but...
I tried your script...
few times it failed, but finally that makes me going into the bootloader.
BUT after that, i was unable to flash anything. I tried with RSD lite and also manual fastboot from stock firmware.
I decided to try tomorrow so i selected "power off". Now the phone is dead. Neither the green led nor the message "service required code corrupt" shows up. Now it's a total brick

ok it discharged. now when i turn on it goes on bootloader but these messages are displayed:
Esip signature missing
E:invalid GPT partition gpt_main
E: not found osip header
E:mismatched osii detected
E: no valid GPT existed
invalid mbr partition os type 0x 0
failed to load GPT partitions no any partition found!
E: no PDS partition found!
How to proceed? every try of using fastboot to load something fails...
Thankyou...

yostyle said:
ok it discharged. now when i turn on it goes on bootloader but these messages are displayed:
Esip signature missing
E:invalid GPT partition gpt_main
E: not found osip header
E:mismatched osii detected
E: no valid GPT existed
invalid mbr partition os type 0x 0
failed to load GPT partitions no any partition found!
E: no PDS partition found!
How to proceed? every try of using fastboot to load something fails...
Thankyou...
Click to expand...
Click to collapse
I GOT THE SOLUTION YAYYYYY
i was able to flash only th gpt.bin contained in the ota update file found here in the forum (that is Blur_Version.91.2.26001.XT890.Retail.en.EU)
after that i flashed (skipping the GPT part) the files contained in 9.8.2I-50_SMI-29_S7_USASMI01UKE1021.0R_USASMIJBRTGB_P007_A005_S1FF_fb that i found at https://firmware.center/firmware/
THANK TO YOU I HAVE MY PHONE ALIVE! :good::good::good::good: