Database Users

[Q] Dalvik-cache ?

Hi.
Where is Dalvik-cache placed here ?:
Code:
# ls -al
total 256
drwxr-xr-x 23 root root 4096 Jun 24 10:08 .
drwxr-xr-x 23 root root 4096 Jun 24 10:08 ..
drwxr-xr-x 2 root root 4096 Nov 20 2011 .config
-rw-r--r-- 1 root root 147816 Jun 24 10:08 .readahead
drwxr-xr-x 2 root root 4096 Jan 5 08:16 bin
drwxr-xr-x 3 root root 4096 Nov 20 2011 boot
drwxr-xr-x 18 root root 4400 Jun 24 10:10 dev
drwxr-xr-x 118 root root 12288 Jun 24 10:08 etc
drwxr-xr-x 4 root root 4096 Nov 20 2011 home
drwxr-xr-x 22 root root 12288 Jan 5 08:16 lib
drwx------ 2 root root 16384 Nov 20 2011 lost+found
drwxr-xr-x 3 root root 60 Jun 24 10:10 media
drwxr-xr-x 2 root root 4096 Oct 25 2011 mnt
drwxr-xr-x 4 root root 4096 Dec 27 17:24 opt
dr-xr-xr-x 164 root root 0 Jun 24 2012 proc
drwx------ 27 root root 4096 Jun 24 10:25 root
drwxr-xr-x 21 root root 680 Jun 24 10:27 run
drwxr-xr-x 3 root root 12288 Jan 5 08:17 sbin
drwxr-xr-x 2 root root 4096 Oct 25 2011 selinux
drwxr-xr-x 4 root root 4096 Nov 10 2011 srv
drwxr-xr-x 12 root root 0 Jun 24 10:07 sys
drwxrwxrwt 18 root root 4096 Jun 24 10:25 tmp
drwxr-xr-x 12 root root 4096 Nov 10 2011 usr
drwxr-xr-x 15 root root 4096 Oct 1 2011 var

It is normally /data/cache/dalvik-cache
You have no data on there though....

I'm sure you are right.
Many thanks for your reply
# ls -al data/
total 96
drwx------ 3 Lajka users 32768 Jun 23 08:37 .
drwx------ 17 Lajka users 32768 Jan 1 1970 ..
drwx------ 2 Lajka users 32768 Jun 23 18:24 com.keramidas.TitaniumBackup
Click to expand...
Click to collapse

Its /data/dalvik-cache/
Send from my LG GT540 Android 4.0.3 Polishblood PreRC CM9

Thanks, and means, that I have no dalvik-cache ?.
Why?

hmm where did you get this and what are you trying to do? You dont have a recovery?

Hi.
What do you mean ?.
I have accessed the GT540 from my linux box, and can't see it.
I would delete the dalvik-cache.
No recovery available.
What's a way to get it ?.

Maybe there is a way but ... get a recovery

Please advice me to make a recovery, thanks!

aalested said:
Please advice me to make a recovery, thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1224747 just follow this

Indeed this was a nice link. Many many thanks :laugh:

Does this mean to be done when the telephone starts up ?
Next put your phone in Fastboot mode by rebooting then holding Camera+Power
Click to expand...
Click to collapse

aalested said:
Does this mean to be done when the telephone starts up ?
Click to expand...
Click to collapse
to go in fastboot mode turn your phone off. then press power on and at the same time hold the camera button

@andreas__
Thank you. I tried it, and the screen gets black and warm, nothing else.
Why that ?.
From this thread:
http://http://forum.xda-developers.com/showthread.php?t=1224747
There stands:
Now, installing custom ROMs. Pick any ROM you'd like from the ROM Development section, if you can, get the recovery version, it is much easier to install. Determine if it is a recovery backup, or update.zip
Click to expand...
Click to collapse
Which one can I use for my GT540 with Android 2.1 ?

aalested said:
@andreas__
Thank you. I tried it, and the screen gets black and warm, nothing else.
Why that ?.
Which one can I use for my GT540 with Android 2.1 ?
Click to expand...
Click to collapse
you did it correct if its black.
you now have to setup fastboot for your PC.
If you installed the drivers and have the needed files on your PC you can flash recovery.
Easy Fastboot tool by Junwei178:
http://forum.xda-developers.com/showthread.php?t=1729020
If you have recovery installed, you can flash any ROM you want.

Yep if you use the tool get the original version. first use the repartition tool (for more app space) (select the 150Mb)then when that is done flash a recovery then flash a system followed by a boot. the on screen instructions should be easy enough to follow

andreas__ said:
you did it correct if its black.
you now have to setup fastboot for your PC.
If you installed the drivers and have the needed files on your PC you can flash recovery.
Easy Fastboot tool by Junwei178:
http://forum.xda-developers.com/showthread.php?t=1729020
If you have recovery installed, you can flash any ROM you want.
Click to expand...
Click to collapse
Thanks for your reply.
But which ROM can I use for my GT540 with Android 2.1 ?
Link please, thank you

-Grift- said:
Yep if you use the tool get the original version. first use the repartition tool (for more app space) (select the 150Mb)then when that is done flash a recovery then flash a system followed by a boot. the on screen instructions should be easy enough to follow
Click to expand...
Click to collapse
Ok, but where is the "the tool get the original version" ?
Link ?.

aalested said:
Thanks for your reply.
But which ROM can I use for my GT540 with Android 2.1 ?
Link please, thank you
Click to expand...
Click to collapse
as -Grift- gave full instructions for the fastboot tool you now should have android 2.3 installed on your GT540.
IF you REALLY want back to 2.1 (maybe because of battery life)
check this:
http://forum.xda-developers.com/showthread.php?t=1368013

@andreas__
Manny thanks, great!

Need a copy of mmcblk0

Hi guys,
I am in desperate need of a raw img of mmcblk0. All I need one of you to do is get an adb shell or in terminal emulator with root type:
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img count=524288
This creates a raw image dump I can use to help unbrick my device. It does NOT contain any sensitive data like IMEI or ESN, etc... I need MJE on Verizon Note 3 specifically. Thank you very much in advanced!
EDIT: 2/14 11:15am CST I am still in need of MJE N900V image. Surely would appreciate anyone with the time.

ryanbg said:
Hi guys,
I am in desperate need of a raw img of mmcblk0. All I need one of you to do is get an adb shell or in terminal emulator with root type:
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img
This creates a raw image dump I can use to help unbrick my device. It does NOT contain any sensitive data like IMEI or ESN, etc... I need MJE on Verizon Note 3 specifically. Thank you very much in advanced!
Click to expand...
Click to collapse
Dev Edition matter? I can offer one up if that is acceptable

TechSavvy2 said:
Dev Edition matter? I can offer one up if that is acceptable
Click to expand...
Click to collapse
It's worth a shot, I sure would appreciate it.

/dev/mmcblk0 is the entire device - 32 GB
Is that really what you mean?

ryanbg said:
It's worth a shot, I sure would appreciate it.
Click to expand...
Click to collapse
aight, give me a minute
Edit: Sorry give me another minute, had to re-root really quick
Edit: PS, any other dd's you want me to run for you while I'm at it?
---------- Post added 14th February 2014 at 12:12 AM ---------- Previous post was 13th February 2014 at 11:58 PM ----------
bftb0 said:
/dev/mmcblk0 is the entire device - 32 GB
Is that really what you mean?
Click to expand...
Click to collapse
This.

TechSavvy2 said:
aight, give me a minute
Edit: Sorry give me another minute, had to re-root really quick
Edit: PS, any other dd's you want me to run for you while I'm at it?
---------- Post added 14th February 2014 at 12:12 AM ---------- Previous post was 13th February 2014 at 11:58 PM ----------
This.
Click to expand...
Click to collapse
Cancel that!!! I gave you a bad command. Just delete unbrick.img

ryanbg said:
Cancel that!!! I gave you a bad command. Just delete unbrick.img
Click to expand...
Click to collapse
Already cancelled it out when I realized the size and time it was gonna take. Another memory block you need perhaps?
Code:
major minor #blocks name Label
7 0 21861 loop0
7 1 3150 loop1
7 2 26019 loop2
7 3 9387 loop3
7 4 2111 loop4
7 5 4190 loop5
7 6 26019 loop6
179 0 30535680 mmcblk0
179 1 15360 mmcblk0p1 apnhlos
179 2 58816 mmcblk0p2 modem
179 3 512 mmcblk0p3 sbl1
179 4 32 mmcblk0p4 dbi
179 5 32 mmcblk0p5 ddr
179 6 2048 mmcblk0p6 aboot
179 7 512 mmcblk0p7 rpm
179 8 512 mmcblk0p8 tz
179 9 10240 mmcblk0p9 pad
179 10 10240 mmcblk0p10 param
179 11 14336 mmcblk0p11 efs
179 12 3072 mmcblk0p12 modemst1
179 13 3072 mmcblk0p13 modemst2
179 14 11264 mmcblk0p14 boot
179 15 13312 mmcblk0p15 recovery
179 16 13312 mmcblk0p16 fota
179 17 7159 mmcblk0p17 backup
179 18 3072 mmcblk0p18 fsg
179 19 1 mmcblk0p19 fsc
179 20 8 mmcblk0p20 ssd
179 21 8192 mmcblk0p21 persist
179 22 9216 mmcblk0p22 persdata
179 23 2777088 mmcblk0p23 system
179 24 1048576 mmcblk0p24 cache
179 25 26521583 mmcblk0p25 userdata
179 32 512 mmcblk0rpmb
179 64 30702592 mmcblk1
179 65 30701568 mmcblk1p1
254 0 21861 dm-0
254 1 3150 dm-1
254 2 26019 dm-2
254 3 9387 dm-3
254 4 2110 dm-4
254 5 4189 dm-5
254 6 26019 dm-6

TechSavvy2 said:
Already cancelled it out when I realized the size and time it was gonna take. Another memory block you need perhaps?
Code:
major minor #blocks name Label
7 0 21861 loop0
7 1 3150 loop1
7 2 26019 loop2
7 3 9387 loop3
7 4 2111 loop4
7 5 4190 loop5
7 6 26019 loop6
179 0 30535680 mmcblk0
179 1 15360 mmcblk0p1 apnhlos
179 2 58816 mmcblk0p2 modem
179 3 512 mmcblk0p3 sbl1
179 4 32 mmcblk0p4 dbi
179 5 32 mmcblk0p5 ddr
179 6 2048 mmcblk0p6 aboot
179 7 512 mmcblk0p7 rpm
179 8 512 mmcblk0p8 tz
179 9 10240 mmcblk0p9 pad
179 10 10240 mmcblk0p10 param
179 11 14336 mmcblk0p11 efs
179 12 3072 mmcblk0p12 modemst1
179 13 3072 mmcblk0p13 modemst2
179 14 11264 mmcblk0p14 boot
179 15 13312 mmcblk0p15 recovery
179 16 13312 mmcblk0p16 fota
179 17 7159 mmcblk0p17 backup
179 18 3072 mmcblk0p18 fsg
179 19 1 mmcblk0p19 fsc
179 20 8 mmcblk0p20 ssd
179 21 8192 mmcblk0p21 persist
179 22 9216 mmcblk0p22 persdata
179 23 2777088 mmcblk0p23 system
179 24 1048576 mmcblk0p24 cache
179 25 26521583 mmcblk0p25 userdata
179 32 512 mmcblk0rpmb
179 64 30702592 mmcblk1
179 65 30701568 mmcblk1p1
254 0 21861 dm-0
254 1 3150 dm-1
254 2 26019 dm-2
254 3 9387 dm-3
254 4 2110 dm-4
254 5 4189 dm-5
254 6 26019 dm-6
Click to expand...
Click to collapse
Sorry I'm in a bit of a panic. Trying to remember how to piece together a debrick image. Appreciate your patience again.
EDIT: Here we go Link

ryanbg said:
Hi guys,
I am in desperate need of a raw img of mmcblk0. All I need one of you to do is get an adb shell or in terminal emulator with root type:
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img
This creates a raw image dump I can use to help unbrick my device. It does NOT contain any sensitive data like IMEI or ESN, etc... I need MJE on Verizon Note 3 specifically. Thank you very much in advanced!
Click to expand...
Click to collapse
Actually it DOES contain sensitive data since it contains ALL 32GB of the internal flash
You need to be rooted and with a decent busybox and do more like:
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img count=524288
(this will create a 256MB image).
IMHO you also need to create the debrick image on the same family product - it would be VERY interesting if that would work from a verizon developer edition model (and I would really want to see that tested) but I have some doubts. I would also be interested if any other debrick image would work - I assume you have N900V but IMHO it would be again VERY interesting to try with a N900W8 debrick image (but be very, very careful when you later write stuff with the modem-related stuff, which is very different in N900W8 and you really want to keep your N900V modem and stuff ).

xclub_101 said:
... it would be VERY interesting if that would work from a verizon developer edition model (and I would really want to see that tested) but I have some doubts. I would also be interested if any other debrick image would work ...
Click to expand...
Click to collapse
I guess I need to go looking for the right threads, but is it correct to say that the SDcard unbrick method (Qualcomm phone versions) only provides a kind of volatile boot scaffolding so that the device owner can enter Odin/download mode... and that no flashing of the device occurs until the owner actually performs the subsequent flash operation using Odin? (That is, none of the content of the unbrick image is ever written to the device being rescued?)
A second question is whether version locking occurs - I thought I saw someone claiming that a prior release unbrick image, even if taken from the same device (e.g. MI9 or MJ7 prior to a MJE upgrade) will not launch into download mode - is that right?

bftb0 said:
I guess I need to go looking for the right threads, but is it correct to say that the SDcard unbrick method (Qualcomm phone versions) only provides a kind of volatile boot scaffolding so that the device owner can enter Odin/download mode... and that no flashing of the device occurs until the owner actually performs the subsequent flash operation using Odin? (That is, none of the content of the unbrick image is ever written to the device being rescued?)
A second question is whether version locking occurs - I thought I saw someone claiming that a prior release unbrick image, even if taken from the same device (e.g. MI9 or MJ7 prior to a MJE upgrade) will not launch into download mode - is that right?
Click to expand...
Click to collapse
That is somehow true, but IMHO if all relevant partitions are wiped on the internal flash (from SBL1 to ABOOT) then all those will be read from microSD and have the code and signatures from there, and the "Odin mode" itself will be the version from microSD.
And here we have a number of interesting paths:
- the signature/hash on SBL1 itself is similar among Note 3 versions - that would result on all steps up to and including ABOOT being valid, so the "special Odin mode" will be entered; if the signature/hash on SBL1 is NOT similar between Note 3 families (or even before and after a major bootloader version) not even the "special Odin mode" will be started;
- if "special Odin mode" is started we can see another fork - if the "downgrade limitations" are part of the microSD code itself then you will be able to write any single firmware you were able to write when the internal SBL1/ABOOT was at the same version as the microSD SBL1/ABOOT - in other words you will be able to downgrade as far back as the microSD SBL1/ABOOT will let you!
- however there are some reports that the "downgrade restrictions" are actually stored in the internal flash in the "invisible/protected" regions there - and can be reset with special JTAG-like hardware:
http://forum.gsmhosting.com/vbb/f672/regarding-knox-s4-1775213/
Even in that last case there would still be a small chance that the "downgrade restrictions" might be skipped when booting from microSD since the internal flash could be considered at that point "less reliable" (or hopefully somebody at Samsung forgot to read that extra info on this special path - we can all hope )
So yes, I have also seen some people claiming stuff but I would still like to see more detailed tests on it with detailed reports on what is failing at what point! And especially on the microSD with the N900W8 "happy bootloader" or even with some much earlier "early development bootloader" (I have seen something like that mentioned somewhere)!

bftb0 said:
I guess I need to go looking for the right threads, but is it correct to say that the SDcard unbrick method (Qualcomm phone versions) only provides a kind of volatile boot scaffolding so that the device owner can enter Odin/download mode... and that no flashing of the device occurs until the owner actually performs the subsequent flash operation using Odin? (That is, none of the content of the unbrick image is ever written to the device being rescued?)
A second question is whether version locking occurs - I thought I saw someone claiming that a prior release unbrick image, even if taken from the same device (e.g. MI9 or MJ7 prior to a MJE upgrade) will not launch into download mode - is that right?
Click to expand...
Click to collapse
My theory on this (for public, bftb0 already knows) is you can boot anything that isn't fused to a lower binary counter, and since these values are inconsistent with firmware updates, it gives you a little wiggle room. AKA if A flag in ODIN is A2, you can not use an A1 aboot (MI9), but I (think) could use MJ7 since it's counter value is 2, same as MJE. These values are stored in AP RAW ANTI ROLLBACK in QFPROM. It is my belief that these values are also accessed from the shadow register as opposed to being read every time, since I was able to downgrade and replicate. I'm almost positive it's pulling these flags from RPMB. I'm extremely curious what P is since I may have full control. P1 changed to P0 when I downgraded my SBL1, TZ, and RPM to the testbit bootloader leaked by designgears, which doesn't make much since I believe all three of those have their own counters.

well ryanbg can summarize when he gets some free time (and I think that there are further experiments in the queue) but an initial attempt at performing a rescue of his bricked retail SM-900V phone (which was on MJE prior to hard bricking by a TZ partition mod) using a 200 MiB dump of mmcblk0 from a MJ7 device resulted in .... nothing.
I haven't seen anything in any of the posts so far about folks talking extra precautions involving repair of the secondary GPT (after doing a raw dump of the unbrick.img to their SDcard media), so I suppose that means that the SDCard unbrick method is - when it works - supposed to be insensitive to the fact that the unbrick SD Card does not have a complete UEFI set of primary & secondary GPTs - and might even have garbage sitting at the secondary GPT offsets.
For the MJ7 trial, we used dd if=/dev/block/mmcblk0 bs=4096 count=50000 (200 MiB) which is sufficiently large to capture everything including some amount of slop at the beginning of /system (p23). I thought I saw a post where someone was using 300 MB unbrick images, making the claim that smaller sizes didn't seem to work. Doesn't make much sense though, as only about ~ 180 MB are needed for everything up to and including p22. (p1 - p22 are ordered contiguously in LBA address space on the SM-900V, and p23 is 2.7GB, so clearly an intact copy of /system can't be needed).
any ideas welcome

sorry to resurrect this thread, but I can't seem to find a sm-n900v debrick/unbrick img anywhere. i've found the 900T, 900A, 9005 images, but nothing for 900v.
my retail edition n900v is definitely hard bricked and I could use some assistance.

Does any one have a note 3 verizon mj7 debrick/unbrick.img

Verizon VK810 rooted and TWRP

Wheres the roms? This thing is finally rooted with recovery, are there any known working roms?
Sent from my VK810 4G using XDA Premium HD app

Chance77 said:
Wheres the roms? This thing is finally rooted with recovery, are there any known working roms?
Sent from my VK810 4G using XDA Premium HD app
Click to expand...
Click to collapse
Give it time, grasshopper. These things take time. There are just enough differences between the 500/501 and 810 and the dev's need time to mod the kernel, build and find testers.
Also, as far as I know, we don't have source for the VK810 yet so that may slow things down a bit.
Believe me, i'm also waiting on an AOSP / GPE experience to make this thing perfect.

LG already released source. https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=vk810

edgemaster191 said:
Give it time, grasshopper. These things take time. There are just enough differences between the 500/501 and 810 and the dev's need time to mod the kernel, build and find testers.
Also, as far as I know, we don't have source for the VK810 yet so that may slow things down a bit.
Believe me, i'm also waiting on an AOSP / GPE experience to make this thing perfect.
Click to expand...
Click to collapse
I wish I shared your optimism. I hope I'm wrong but it isn't looking good. The only reason we got TWRP support is because someone that has the other device helped with the 810. There seems to be next to no momentum on the 810 side. There just doesn't seem to be a lot of developers who have that device.

prana22 said:
I wish I shared your optimism. I hope I'm wrong but it isn't looking good. The only reason we got TWRP support is because someone that has the other device helped with the 810. There seems to be next to no momentum on the 810 side. There just doesn't seem to be a lot of developers who have that device.
Click to expand...
Click to collapse
I would do something but I have never even compiled CM11 let alone tweaked it to work with a new device. I can work with a developer who doesn't have one, but I don't know enough to do it on my own.

That is where I am as well. I know just enough to get myself in trouble.
Sent from my VK810 4G using XDA Free mobile app

anyone care to share a system dump of the VK810?
boot.img and system partition would be useful
my local verizon store refuses to sell it to me without a contract............ sigh
probably going to get it from amazon

Sure, how do I do that? <-- I am a noob

popezaphod said:
Sure, how do I do that? <-- I am a noob
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2450045
info about the various partitions,good reading: http://www.all-things-android.com/content/review-android-partition-layout
if you have the custom recovery installed, you could do a backup of the device from recovery and share the files
don't share your EFS partition because it contains your unique IMEI/ESN number, and sometimes devices break if you flash someone else's EFS partition. don't share your userdata partition obviously
(if you can't figure out which is the EFS partition from the WAY #2 image, or how to do a system dump, I just need the following partitions and partition layout)
What I need:
1) Following partitions
BOOT - contains ramdisk info necessary to compile a working boot image
RECOVERY - not that necessary, but more info is useful
SYSTEM - probably contains modem libraries not present in the v500 system partition
2) Partition Layout
needed to compile a working ROM
more info is better... so a complete system dump (minus EFS and userdata) would be great
thanks for helping...

Good Amount of Info
ro.product
Code:
[ro.product.board]: [MSM8960]
[ro.product.brand]: [lge]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.device]: [altev]
[ro.product.locale.language]: [en]
[ro.product.locale.region]: [US]
[ro.product.manufacturer]: [LGE]
[ro.product.model]: [VK810 4G]
[ro.product.name]: [altev_vzw]
[email protected]:/ # getprop | grep ro.build.
ro.build
Code:
[ro.build.characteristics]: [tablet]
[ro.build.date.utc]: [1392900914]
[ro.build.date]: [Thu Feb 20 21:55:14 KST 2014]
[ro.build.description]: [altev_vzw-user 4.2.2 JDQ39B VK81010C.1392900840 release
-keys]
[ro.build.display.id]: [JDQ39B]
[ro.build.fingerprint]: [lge/altev_vzw/altev:4.2.2/JDQ39B/VK81010C.1392900840:us
er/release-keys]
[ro.build.host]: [LGEARND9B11]
[ro.build.id]: [JDQ39B]
[ro.build.product]: [altev]
[ro.build.tags]: [release-keys]
[ro.build.target_country]: [US]
[ro.build.target_operator]: [VZW]
[ro.build.target_region]: [US]
[ro.build.type]: [user]
[ro.build.user]: [hyungjin.yoo]
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [VK81010C.1392900840]
[ro.build.version.release]: [4.2.2]
[ro.build.version.sdk]: [17]
Stock aBoot img
https://www.dropbox.com/s/kf3fysyhvlyw8l0/aboot.img
Boot IMG w/ TWRP Installed(Not sure if that matters or not)
https://www.dropbox.com/s/egm0rp381cahbeo/boot.img
TWRP Recovory
https://www.dropbox.com/s/ypwreq1c07yj36v/VK810_twrp_2.7.0.1.zip
Recovory IMG w/ TWRP Installed
https://www.dropbox.com/s/23xy2o8qydqsunu/recovery.img
Stock build.prop
https://www.dropbox.com/s/4rqciye90mhp1cj/build.prop
Partitions
Code:
7 0 5229 loop0
7 1 22901 loop1
179 0 15388672 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 24576 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 780 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 512 mmcblk0p21
179 22 512 mmcblk0p22
179 23 2195456 mmcblk0p23
179 24 1392640 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 262144 mmcblk0p26
179 27 24576 mmcblk0p27
179 28 3072 mmcblk0p28
179 29 8 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 512 mmcblk0p31
259 0 512 mmcblk0p32
259 1 8 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 11247616 mmcblk0p35
259 4 4079 mmcblk0p36
254 0 5229 dm-0
254 1 22900 dm-1
lrwxrwxrwx root root 1970-01-13 12:13 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-13 12:13 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-13 12:13 bnr -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-13 12:13 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-13 12:13 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-13 12:13 drm -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-13 12:13 eksst -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-13 12:13 encrypt -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-13 12:13 factory -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-13 12:13 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-13 12:13 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-13 12:13 grow -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-13 12:13 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-13 12:13 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-13 12:13 m9kefs3 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-13 12:13 misc -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-13 12:13 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-13 12:13 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-13 12:13 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-13 12:13 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-13 12:13 persist -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-13 12:13 rct -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-13 12:13 recovery -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-13 12:13 reserved -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-13 12:13 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-13 12:13 rpmbak -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-13 12:13 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-13 12:13 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-13 12:13 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-13 12:13 sns -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-13 12:13 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-13 12:13 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-13 12:13 tombstones -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-13 12:13 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-13 12:13 tzbak -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-13 12:13 userdata -> /dev/block/mmcblk0p35
Right now I have a lot of stuff removed from my rom but I do have a stock backup so later I will revert back and and post partition images.
As for stock recovery.img and stock boot.img, I do not have that so maybe someone else can grab that for us that didn't install TWRP yet(Didn't even think of getting it before I installed it and would be nice to have to go back to stock for warranty exchange)
Also let me know of anything else I can do to help you. Thank You

NICG said:
Right now I have a lot of stuff removed from my rom but I do have a stock backup so later I will revert back and and post partition images.
As for stock recovery.img and stock boot.img, I do not have that so maybe someone else can grab that for us that didn't install TWRP yet(Didn't even think of getting it before I installed it and would be nice to have to go back to stock for warranty exchange)
Also let me know of anything else I can do to help you. Thank You
Click to expand...
Click to collapse
Thanks for posting....
Slightly strange values...
VK810 (LTE):
Code:
BOARD_BOOTIMAGE_PARTITION_SIZE := 25165824 # 24M
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 25165824 # 24M
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 2248146944 # 2114M
BOARD_USERDATAIMAGE_PARTITION_SIZE := 11517558784 #10984
BOARD_FLASH_BLOCK_SIZE := 131072 # (BOARD_KERNEL_PAGESIZE * 64)
V500 (wifi):
Code:
BOARD_BOOTIMAGE_PARTITION_SIZE := 23068672 # 22M
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 23068672 # 22M
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 880803840 # 840M
BOARD_USERDATAIMAGE_PARTITION_SIZE := 6189744128 # 5.9G
BOARD_FLASH_BLOCK_SIZE := 131072 # (BOARD_KERNEL_PAGESIZE * 64)
can you post the output of the below command? Want to verify the BOARD_FLASH_BLOCK_SIZE settings
cat /proc/mtd
EDIT1:
Who wants to be a guinea pig for my first cm-11.0 build? (requires you to have TWRP recovery)
0) Post here saying that you are testing the ROM. If someone else posted, then wait and see what happens
1) Perform a backup in TWRP recovery
2) Did I say to perform a backup?
3) Flash the cm-11 zip file in TWRP recovery. the boot.img is already LOKI patched
<removed>
4) Reboot
See if the device starts up properly.
If it doesn't, then go back to TWRP recovery and restore your backup
Risky? Maybe. If you are afraid, then don't flash it and wait for someone else to do it.....

I tested the download and it seems there is a device name mismatch somewhere:
installing '/extenal_sd/cm-11-20140512-UNOFFICIAL-vk810_loki.zip'
checking for MD5 file...
skipping MD5 check no MD5 file found
This package is for "vk810" devices; this is a "altev"
E: Error executing updater binary in zip
error flashing zip
failed

traccdma said:
I tested the download and it seems there is a device name mismatch somewhere:
installing '/extenal_sd/cm-11-20140512-UNOFFICIAL-vk810_loki.zip'
checking for MD5 file...
skipping MD5 check no MD5 file found
This package is for "vk810" devices; this is a "altev"
E: Error executing updater binary in zip
error flashing zip
failed
Click to expand...
Click to collapse
probably.... vk810 is the device name, altev is the model/board/product name... probably a mismatch somewhere.....
I'll recompile when I get home
(v500 = awifi = wifi only version, v510 = palman = GPE version)

paperWastage said:
probably.... vk810 is the device name, altev is the model/board/product name... probably a mismatch somewhere.....
I'll recompile when I get home
(v500 = awifi = wifi only version, v510 = palman = GPE version)
Click to expand...
Click to collapse
i think we should stick with v500/v510/vk810 convention.....
http://forum.xda-developers.com/showpost.php?p=48103469&postcount=22
from this, it looks like the recovery image needs to be fixed...
http://forum.xda-developers.com/showpost.php?p=48331517&postcount=10
for now, I've manually edited the META-INF/com/google/android/updater-script to include "altev" as part of the check
0) Post here saying that you are testing the ROM. If someone else posted, then wait and see what happens
1) Perform a backup in TWRP recovery
2) Did I say to perform a backup?
3) Flash the cm-11 zip file in TWRP recovery. the boot.img will be LOKI-patched during the flash (which means don't use my previous upload where I pre-patched the boot.img)
http://d-h.st/tAq
4) Reboot
See if the device starts up properly.
If it doesn't, then go back to TWRP recovery and restore your backup
Risky? Maybe. If you are afraid, then don't flash it and wait for someone else to do it.....

with cm-11-20140513-unofficial-vk810.zip:
set_metadata_recursive: some changes failed
E: error executing updater binary in zip
error flashing zip
updating partition details...
tried booting it anyway and it brings up LG logo once, powers off/back on, and boots up to recovery (TWRP) on its own

traccdma said:
with cm-11-20140513-unofficial-vk810.zip:
set_metadata_recursive: some changes failed
E: error executing updater binary in zip
error flashing zip
updating partition details...
tried booting it anyway and it brings up LG logo once, powers off/back on, and boots up to recovery (TWRP) on its own
Click to expand...
Click to collapse
http://www.xda-developers.com/android/how-to-fix-a-broken-rom-flash-in-certain-kitkat-roms/
hmm, not sure why TWRP is complaining. need to investigate tomorrow. if the update_script failed, then the boot.img wasn't patched, so the new boot image won't boot at all.
were you able to restore from nandroid backup?
you also try replacing the update-binary in the ROM with this
http://forum.xda-developers.com/showthread.php?t=2532300

that got much further and even booted into CyanogenMod 11 with the VZW Gpad V810!!
After unzipping your file, overwriting the update-binary file in meta-inf\com\google\android with the file from the thread you posted, it said successful. Rebooted once while it said Android is updating app xxx of xxx, then Welcome to CyanogenMod
Seems to be missing drivers though. First boot seemed stable except it didn't recognize Verizon mobile data (or SIM card). I was in there at least 10 minutes. In settings, I used the slider to try and turn on wifi, but it never turned blue and a few seconds later it reverted back off. I slid bluetooth on, and it did the same thing and went into a boot loop. It gets to the android desktop for about 5 seconds then reboots. I wiped cache and dalvik cache and it got no further.

traccdma said:
with cm-11-20140513-unofficial-vk810.zip:
set_metadata_recursive: some changes failed
E: error executing updater binary in zip
error flashing zip
updating partition details...
tried booting it anyway and it brings up LG logo once, powers off/back on, and boots up to recovery (TWRP) on its own
Click to expand...
Click to collapse
whenever that happens get a recovery log, They are very helpful

traccdma said:
that got much further and even booted into CyanogenMod 11 with the VZW Gpad V810!!
After unzipping your file, overwriting the update-binary file in meta-inf\com\google\android with the file from the thread you posted, it said successful. Rebooted once while it said Android is updating app xxx of xxx, then Welcome to CyanogenMod
Seems to be missing drivers though. First boot seemed stable except it didn't recognize Verizon mobile data (or SIM card). I was in there at least 10 minutes. In settings, I used the slider to try and turn on wifi, but it never turned blue and a few seconds later it reverted back off. I slid bluetooth on, and it did the same thing and went into a boot loop. It gets to the android desktop for about 5 seconds then reboots. I wiped cache and dalvik cache and it got no further.
Click to expand...
Click to collapse
good to hear...
need two things:
system dump of stock ROM.
The proprietary libs I'm using right now is from v500 which probably doesn't have the radio libs. maybe wifi/bt driver is different too
logs
As Drgravy said, logs are helpful. Recovery log, /proc/last_kmsg from kernel boot, ...

Sorry been a little busy but here you go.
Stock Rooted System IMG
https://www.dropbox.com/s/rpxmbp1lgb5a4k9/system.img

[GUIDE] Increase internal storage for Grand i9082

Hi guys
today i am gonna guide you to increase internal storage of galaxy grand.
so first you need following things.
1. patience
2. computer with adb enabled.
3. galaxy grand i9082 with CWM or Philz or TWRP installed.
This procedure will wipe out your whole internal partition. means your all data on internal storage will be gone.
So make back up first.
This is dangerous procedure. needs advance knowledge.
1. So, first boot into recovery.
i think you guys know how to do that.
2. Connect PC and mobile
3. open terminal/CMD on PC/linux computer.
4. type following
PHP:
adb shell
5. Type
PHP:
cd /dev/block
parted mmcblk0
print
6. This looks like following
PHP:
print
Model: MMC M8G1WA (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 14.7MB 15.7MB 1049kB cal
2 15.7MB 16.0MB 262kB sysparm_dep
3 16.0MB 16.3MB 262kB parm-spml_dep
4 16.3MB 16.5MB 262kB RF_CAL_FILE
5 16.5MB 24.9MB 8389kB KERNEL
6 24.9MB 33.3MB 8389kB RECOVERY
7 33.3MB 53.0MB 19.7MB modem
8 53.0MB 86.2MB 33.3MB reserved
9 86.2MB 88.3MB 2097kB SBL1
10 88.3MB 90.4MB 2097kB SBL2
11 90.4MB 98.8MB 8389kB PARAM
12 98.8MB 99.4MB 524kB DTSBK
13 99.4MB 99.9MB 524kB DTS
14 99.9MB 108MB 8389kB VC-FirmwareBK
15 108MB 117MB 8389kB VC-Firmware
16 117MB 117MB 262kB FOTA_SIG
17 117MB 138MB 21.0MB ext4 efs
18 138MB 1212MB 1074MB ext4 CSC
19 1212MB 2822MB 1611MB ext4 system
20 2822MB 3409MB 587MB ext4 HIDDEN
21 3409MB 7813MB 4404MB ext4 data
7. last 4 partitions i.e number 18,19,20, 21 will be erased and repartitioned again.
this is dangerous step. dont do it. if you dont understand what you doing.
8. type following
PHP:
rm 21
rm 20
rm 19
rm 18
9. Now we will create new partitions as we wanted. copy following cammands one by one followed by ENTER.
PHP:
mkpartfs primary ext2 138 538
mkpartfs primary ext2 538 1638
mkpartfs primary ext2 1638 1838
mkpartfs primary ext2 1838 7813
quit
10. after last "QUIT" command it wil say.
PHP:
quit
Information: You may need to update /etc/fstab.
Ignore the warning Reboot into recovery again on pc type
11.
PHP:
adb shell
mke2fs /dev/block/mmcblk0p18
tune2fs -j /dev/block/mmcblk0p18
mke2fs /dev/block/mmcblk0p19
tune2fs -j /dev/block/mmcblk0p19
mke2fs /dev/block/mmcblk0p20
tune2fs -j /dev/block/mmcblk0p20
mke2fs /dev/block/mmcblk0p21
tune2fs -j /dev/block/mmcblk0p21
This will create ext3 partition from ext2
Now convert them to ext4
12.
PHP:
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p18
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p19
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p20
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p21
Now lets check everything is ok
13.
PHP:
cd /dev/block
parted mmcblk0
print
This should look like following
14.
PHP:
Number Start End Size File system Name Flags
1 14.7MB 15.7MB 1049kB cal
2 15.7MB 16.0MB 262kB sysparm_dep
3 16.0MB 16.3MB 262kB parm-spml_dep
4 16.3MB 16.5MB 262kB RF_CAL_FILE
5 16.5MB 24.9MB 8389kB KERNEL
6 24.9MB 33.3MB 8389kB RECOVERY
7 33.3MB 53.0MB 19.7MB modem
8 53.0MB 86.2MB 33.3MB reserved
9 86.2MB 88.3MB 2097kB SBL1
10 88.3MB 90.4MB 2097kB SBL2
11 90.4MB 98.8MB 8389kB PARAM
12 98.8MB 99.4MB 524kB DTSBK
13 99.4MB 99.9MB 524kB DTS
14 99.9MB 108MB 8389kB VC-FirmwareBK
15 108MB 117MB 8389kB VC-Firmware
16 117MB 117MB 262kB FOTA_SIG
17 117MB 138MB 21.0MB ext4 efs
18 138MB 538MB 400MB ext4
19 538MB 1638MB 1100MB ext4
20 1638MB 1838MB 200MB ext4
21 1838MB 7813MB 5975MB ext4
So you can see your last partition is now 5.9 GB...
Now flash any rom you wanted,......
ENJOY...
CHECK THIS POST IF SOMETHING GETS MESSED UP ..THIS PROCESS WILL FIX ALL PARTITIONS AND MAKE THEM AS THEY WERE EARLIER
Disclaimer :- I will not be responsible for BRICKED devices.. USE THIS PROCEDRE ON YOUR OWN RISK>>>...................
[/U][/I][/B]​
XDA:DevDB Information
[GUIDE] Increase internal storage for Grand i9082, Tool/Utility for the Samsung Galaxy Grand Duos i9082
Contributors
k2wl, rutvikrvr
Version Information
Status: Stable
Created 2014-09-07
Last Updated 2014-09-16

Reserved

Reserved

reserved.

reserved.for more

How to restore a bricked device or how to restore the device if something goes wrong?
FILES REQUIRED : baffin.pit https://s.basketbuild.com/filedl/devs?dev=rutvikrvr&dl=rutvikrvr/i9082/restore/baffin.pit
ANy stock ROM (link for mk3) : https://docs.google.com/file/d/0B80jsFgYZGOhRHJoY200Zktyekk/edit
ODIN: http://forum.xda-developers.com/attachment.php?attachmentid=1751204&d=1361535462
STEP 1 : In the PIT option add .. the baffin.pit AND IN THE PDA OPTION PUT THE FIRMWARE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
STEP 2 : HIT START AND ONCE ITS COMPLETE YOUR PHONE SHOULD WORK FINE ...THEN YOU CAN ROOT YOUR DEVICE AND TRY THIS PROCEDURE AGAIN :laugh: :laugh:

Internal storage increased on Grand Duos
@k2wl You are an angel for us :laugh: You rockKkK man. Thank you very much for this amazing guide. With this awesome guide you made many Grand duos users on XDA forum indebted to you. :good::good::good:
PS : Hey members, See the screenshot of what is going to happen to your internal storage of GalaxyGrand Duos after following this guide successfully .

@k2wl Please clear this doubt of mine?. Will this storage space remains same even after restoring nandroid backup whether stock or custom!

Trilochanaaya said:
@k2wl Please clear this doubt of mine?. Will this storage space remains same even after restoring nandroid backup whether stock or custom!
Click to expand...
Click to collapse
I think .. Only if u flash stock via Odin .... Not recovery ... Only then the partition table gets restored

rutvikrvr said:
I think .. Only if u flash stock via Odin .... Not recovery ... Only then the partition table gets restored
Click to expand...
Click to collapse
it remain same after flashing via recovery. nandroid i dont know. never used one...LOL....

Can you plz make a flashable zip as I'm not an expert in this and I didn't understand those codes

Is it safe???
Is It safe i mean if something goes wrong during the process then what will happen to the device?? i have done many tweaks with my phone but 1st time i m a bit scared

k2wl said:
it remain same after flashing via recovery. nandroid i dont know. never used one...LOL....
Click to expand...
Click to collapse
@k2wl Sorry didn't get you! I am thinking that when we backup ROM using TWRP/CWM it's called nandroid backup. I prefer having STOCK ROM backup just to be safe in case something goes wrong while flashing. My question is about this backup, Will these internal storage changes remain?

This method was beta tested by me and @k2wl :good:
---------- Post added at 10:38 PM ---------- Previous post was at 10:37 PM ----------
Trilochanaaya said:
@k2wl Sorry didn't get you! I am thinking that when we backup ROM using TWRP/CWM it's called nandroid backup. I prefer having STOCK ROM backup just to be safe in case something goes wrong while flashing. My question is about this backup, Will these internal storage changes remain?
Click to expand...
Click to collapse
The /system partition's size gets reduced to 1GB using repartitioning AFAIK, so the stock ROM won't probably will not fit on it.

Basic questions(Noobie questions)
#1 - Would work on SGG GT-i9080L ? (Same grand.. just, not duos (?) )
#2 - Are newbies able to do this tutorial withouth knowledge? Just following the steps.
#3 - Would this problem affect on doing this? (SDCard is emulated inside the internal storage so not taking the extsdcard as sdcard.) Link: http://forum.xda-developers.com/galaxy-grand-duos/help/help-single-partition-external-sd-t2866826

GabrielCool1 said:
Basic questions(Noobie questions)
#1 - Would work on SGG GT-i9080L ? (Same grand.. just, not duos (?) )
#2 - Are newbies able to do this tutorial withouth knowledge? Just following the steps.
#3 - Would this problem affect on doing this? (SDCard is emulated inside the internal storage so not taking the extsdcard as sdcard.) Link: http://forum.xda-developers.com/galaxy-grand-duos/help/help-single-partition-external-sd-t2866826
Click to expand...
Click to collapse
#1 Yes.
#2 The thing that matters the most in such cases is to follow the instructions carefully
#3 Your problem is an isolated one for the grand community and I'm not sure it will solve it or not.
Bonus tip: If you can post the result of 'print' (read in OP that command) we may be able to help you.

This guy must be a god's man??

VanshKhanna said:
Can you plz make a flashable zip as I'm not an expert in this and I didn't understand those codes
Click to expand...
Click to collapse
flashable zips often can currupt partitions..i have bad experience in this.
so i suggest. if yo do it carefully..one by one...it will not affect your device...and its one time procedure...
FuTech.360 said:
Is It safe i mean if something goes wrong during the process then what will happen to the device?? i have done many tweaks with my phone but 1st time i m a bit scared
Click to expand...
Click to collapse
only if you currupt boot loader partition...that would be end of it...but if you follow steps one by one...it will work..
GabrielCool1 said:
Basic questions(Noobie questions)
#1 - Would work on SGG GT-i9080L ? (Same grand.. just, not duos (?) )
#2 - Are newbies able to do this tutorial withouth knowledge? Just following the steps.
#3 - Would this problem affect on doing this? (SDCard is emulated inside the internal storage so not taking the extsdcard as sdcard.) Link: http://forum.xda-developers.com/galaxy-grand-duos/help/help-single-partition-external-sd-t2866826
Click to expand...
Click to collapse
as Akiratomorya said.. give log of "print command"
i will help you out.
ishmeet1995 said:
This guy must be a god's man??
Click to expand...
Click to collapse
thanks...

Man thanks

Reza Khan said:
Man u r just awesome keep good works
Click to expand...
Click to collapse
pl dont quote the op ..pl edit ur post

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