I purchased an S4 knowing that, at least while on the stock ROM, only a little more than 9GB would be available to the user. I figured that installing a custom ROM would allow me to reclaim this missing space. However, every AOSP ROM I've tried installs to the 9GB of user space on the device and the remaining GB go missing. When stock is installed my S4 sees all 16GB only half of which is usable, and with an AOSP ROM installed my S4 only sees 9GB. Using TWRP I have wiped System, Data, Cache, and Dalvik and that does not return the missing space. My question is, does anybody know of a way to reclaim the missing 6GB or if it will ever be possible to reclaim the missing 6GB?
It's not that it goes missing. You have a partition size that would have to be reformatted to regain that usable space. The system partition will be 7gb and the Rom you install will go to that partition whether it is a 2gb, 1gb or 5gb rom. just flashing a smaller rom won't change that partition size.
Ok, missing is the wrong word but the effect is the same. How can I reformat the system partition so that my S4 has closer to 16GB of space available?
chronoquestion said:
Ok, missing is the wrong word but the effect is the same. How can I reformat the system partition so that my S4 has closer to 16GB of space available?
Click to expand...
Click to collapse
You can't.
They're rumors we might get back some of the storage. Buy an sd card. 32gb are like $15
Sent from my SCH-I545 using Tapatalk 2
Next question, is this problem specific to the Verizon S4 or is the same on all S4s? Can any of the S4s on the market be reformatted?
More Findings
I'm flashed as stock/root/debloated with the faux kernel. In my phone about/storage/misc files it shows System Memory as 6.38GB. I did a backup through TWRP from stock and here is some relevant logs:
/system | /dev/block/mmcblk0p16 | Size: 2753MB Used: 2497MB Free: 255MB Backup Size: 2497MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent
/data | /dev/block/mmcblk0p29 | Size: 9948MB Used: 1986MB Free: 7771MB Backup Size: 1777MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Has_Data_Media Is_Storage Is_Settings_Storage
I think I backed everything up too. The stock ROM must compute that 6.38GB from some other partition
chronoquestion said:
Next question, is this problem specific to the Verizon S4 or is the same on all S4s? Can any of the S4s on the market be reformatted?
Click to expand...
Click to collapse
I have a Sprint S4, and have the same problem. My initial thought would be to find a .pit file with a partition less that 6GB, but I don't know if that's possible or how hard it would be.
Related
OK, I have a Gtab with the 11/15 FB build.
I am curious about the partitions. Really, why ? I have worked in Unix for a bunch of years and am a fan of few, large partitions. So why am I choosing 2048 ? Or the max if 4096 ?
If it were a Sun box (which is what i cut my teeth on) I would make the main card (disk) a 12 GB root partition and 4 GB swap.
Do the same rules not apply ? It looks like there are a few different partitions (/system, /data, etc) but my eyes cannot read the terminal emulator all that well.
Andy
Different beasts
aknipp said:
OK, I have a Gtab with the 11/15 FB build.
I am curious about the partitions. Really, why ? I have worked in Unix for a bunch of years and am a fan of few, large partitions. So why am I choosing 2048 ? Or the max if 4096 ?
If it were a Sun box (which is what i cut my teeth on) I would make the main card (disk) a 12 GB root partition and 4 GB swap.
Do the same rules not apply ? It looks like there are a few different partitions (/system, /data, etc) but my eyes cannot read the terminal emulator all that well.
Andy
Click to expand...
Click to collapse
This may not be 100% correct (& if it's not I'm sure someone will correct me).
Really no comparison between a Sun box & a tablet. Sun would be bigger & better hardware.
The tablet only has a 512M nand chip (that holds most of the os), 512M of ram (to run the os, apps & no dedicated graphics memory), a processor that is designed for low power vs performace & and a emmc...basically a thumb drive( in place of an hdd). On top of that Andoid is really a hydrid os (a linux kernel with a java vm to run apps).
As far as partitions go, here is the structure for the nand chip on MOST of the gTabs:
Partition 2 = BCT = boot Config Table
Partition 3 = PT = Partition Table (this list)
Partition 4 = EBT = Bootloader
Partition 5 = MBT = ?
Partition 6 = BLO = Viewsonic Bird Logo
Partition 7 = MSC = ? inandop.log /possibly inter kernel comm tween part9/10
Partition 8 = OGO = logodata (gTablet logo I believe)
Partition 9 = SOS = recovery kernel
Partition 10 = LNX = kernel
Partition 11 = APP = system(rom)
Partition 12 = CAC = cache
If you look at gtablet.cfg file in any of the nvflash packages you will see these partition definitions, fs types & sizes used by nvflash to create them.
You also have 2 additional partitions on the the 16GB internal sd (emmc):
/data - user apps & settings - only accessible via root access
/sdcard = user & app storage
Don't know why exactly why /data is set @ 2 G . Apps in Android don't have the bloat of desktop/PC apps and are considerably smaller. I can tell you that with 83 apps installed I still have nearly 1G of space left on mine out of the 2G.
For the most part, Android doesn't truly multitask apps like on a desktop. From what I understand, Android has it's own mechanism for freeing memory when needed (swapping). When space is needed, non running apps are terminated but the app is responsible for storing persistent data so that it can be reactivated (assuming the app saves persistent data) when called.
Hope this helps.
Al
Cool, thanks, I boosted it up to 4 GB, does not sound like that will hurt (had to reinstall because it was full- could not tell why)
aknipp said:
I am curious about the partitions. Really, why ? I have worked in Unix for a bunch of years and am a fan of few, large partitions. So why am I choosing 2048 ? Or the max if 4096 ?
Click to expand...
Click to collapse
As to what the various partitions are, I can elaborate a bit more on Al's post above. Try these 2 posts:
SD card partitions
NAND Flash partitions
The Android OS has its distributions (ROMs) divided into those partitions described above for pragmatic reasons which are not hard to figure out--mainly to enable easy upgrades of running distributions; with security being a secondary concern.
There is no reason why you couldn't merge some partitions together. For example, GtabComb-b3.3 merges /cache into /data at system bootup time. If you were willing to lose the protected read-only status of /system, that too could be merged with /cache+/data on the SD card by modifying the init rc files. You could muck around with the system at an even lower level since you have access to the source code. It's really up to you how far you want to go. The kernel doesn't care about the no. of partitions or the filesystems on them, or even where they are.
As for your question about the 2GB size of /data, that's just how VS deemed it to be when they released the gTab and that's the size that's followed by most custom ROMs. You can have a smaller or larger size if you want. I, for example, run 2 different ROMs--VEGAn-Tab 7.1 and GtabComb-b3.3--the former on the internal SD card and the latter on a micro SD card just by loading a different boot partition using CWM. And since my micro SD is just 2GB in size, I've shrunk my /data to 256 MB.
aabbondanza said:
From what I understand, Android has it's own mechanism for freeing memory when needed (swapping).
Click to expand...
Click to collapse
None of the currently used kernels swap; and neither does Android. That's why they kill apps when there is no memory.
Explains things very well. Thank you both.
Please can someone help me to resize the system partition of an Android JB 4.2.2 on cubieboard?
Image: sun7i_android_sugar-cubieboard2-8192cu.img
I need more room (it's only 512MB) to install apps.
Well, the APP disk space (nand partition) is very small and the internal "sdcard" too big.
When I install a few applications the space runs out and the system becomes unstable.
I need to increase the nand and decrease internal sdcard to gain more room to my apps...
Well, I started the process by using the tools:
1) To unpack/repack: imgRePacker_204
2) The image ROM: sun7i_android_sugar-cubieboard2-8192cu.img (Android 4.2.2)
3) To burn to flash: PhoenixSuit1.0.6
unpacking the ROM creates a folder named sun7i_android_sugar-cubieboard2-8192cu.img.dump
So, somewhere in internet I see to change the sys_partition.fex file, and search the system nand partition:
Code:
;------------------------------>mmcblk0p8/nande
[partition]
name = data
size = 1048576
user_type = 0x2
so, I change 1048576 to 2097152 (2097152 * 1024 = 2GB)
but :
1) In installed android, the system has only 512MB and not 1GB as show.
2) By increasing this value, nothing happens when I repack back to IMG and flash to the nand.
(all unpak, change, pack, flash process is fine ! )
Here is my devices list and size:
Code:
NAME SIZE MOUNTPOINT LABEL
nand 3.8G
|-nand1 16M Volumn
|-nand2 16M
|-nand3 16M
|-nand4 512M
|-nand5 512M
|-nand6 16M
|-nand7 32M
|-nand8 320M
|-nand9 16M PRIVATE
|-nand10 256M
`-nand11 2.1G
mmcblk0 14.4G
|-mmcblk0p1 900M /
`-mmcblk0p2 13.5G EXTRA
icemagno said:
Please can someone help me to resize the system partition of an Android JB 4.2.2 on cubieboard?
Image: sun7i_android_sugar-cubieboard2-8192cu.img
I need more room (it's only 512MB) to install apps.
Well, the APP disk space (nand partition) is very small and the internal "sdcard" too big.
When I install a few applications the space runs out and the system becomes unstable.
I need to increase the nand and decrease internal sdcard to gain more room to my apps...
Well, I started the process by using the tools:
1) To unpack/repack: imgRePacker_204
2) The image ROM: sun7i_android_sugar-cubieboard2-8192cu.img (Android 4.2.2)
3) To burn to flash: PhoenixSuit1.0.6
unpacking the ROM creates a folder named sun7i_android_sugar-cubieboard2-8192cu.img.dump
So, somewhere in internet I see to change the sys_partition.fex file, and search the system nand partition:
Code:
;------------------------------>mmcblk0p8/nande
[partition]
name = data
size = 1048576
user_type = 0x2
so, I change 1048576 to 2097152 (2097152 * 1024 = 2GB)
but :
1) In installed android, the system has only 512MB and not 1GB as show.
2) By increasing this value, nothing happens when I repack back to IMG and flash to the nand.
(all unpak, change, pack, flash process is fine ! )
Here is my devices list and size:
Code:
NAME SIZE MOUNTPOINT LABEL
nand 3.8G
|-nand1 16M Volumn
|-nand2 16M
|-nand3 16M
|-nand4 512M
|-nand5 512M
|-nand6 16M
|-nand7 32M
|-nand8 320M
|-nand9 16M PRIVATE
|-nand10 256M
`-nand11 2.1G
mmcblk0 14.4G
|-mmcblk0p1 900M /
`-mmcblk0p2 13.5G EXTRA
Click to expand...
Click to collapse
Use this software, search it on google and install it on your PC, then partition you SD
MiniTool Partition Wizard Pro v7.1
azithro said:
Use this software, search it on google and install it on your PC, then partition you SD
MiniTool Partition Wizard Pro v7.1
Click to expand...
Click to collapse
"3) To burn to flash: PhoenixSuit1.0.6"
This implies using NAND .... SD is not in the context.
Thanks anyway!
Honor 7 has 16gb internal memory but my fon show Total: 3.86gb. as i know rom only take about 6gb space. so where the rest? and what you honor 7 space can u use?
studlolox said:
Honor 7 has 16gb internal memory but my fon show Total: 3.86gb. as i know rom only take about 6gb space. so where the rest? and what you honor 7 space can u use?
Click to expand...
Click to collapse
I can use 10.46GB. I have still 7.7GB free.
Sent from PLK-TL01H
studlolox said:
Honor 7 has 16gb internal memory but my fon show Total: 3.86gb. as i know rom only take about 6gb space. so where the rest? and what you honor 7 space can u use?
Click to expand...
Click to collapse
I had the same problem after update to b140. factory reset helped.
(CZ)jv14 said:
I had the same problem after update to b140. factory reset helped.
Click to expand...
Click to collapse
haha..tq..setled
What will happen if I remove SD card with lots of app install on it to swap it with another sim?
Code:
Filesystem Size Used Free Blksize
/system 2.4G 1.9G 494.2M 4096
/data 10.4G 4.1G 6.3G 4096
/data/sec_storage 17.7M 202.0K 17.5M 1024
/cust 495.9M 433.1M 62.9M 4096
/splash2 62.9M 220.0K 62.7M 4096
/storage/emulated 1.4G 0.0K 1.4G 4096
/mnt/media_rw/sdcard1 59.5G 29.2G 30.3G 131072
"ROM" uses a 2.4G partition
Data is 10.4G
The rest is other Android partitions.. (I've removed a lot from the df above; cache, modem, etc.)
my biggest problem ist, that the dalvik cache uses (in my opinion) an enormous amount of space. i have no idea why. i can only guess, that it needs more space because in /dat/dalvik-cache/ there is an arm and an arm64 dir
at the moment my dalvik's size is about 2,15 GB.
I'm trying to change to splash-screen / boot logo of my Sony Xperia Z4 tablet (SGP771)
I have already rooted my device.
With the help of the bootimg.exe tool I unpacked the boot.img - exchanged the logo.rle and repacked the boot.img.
My custom logo.rle I created with boot_screen_logo_creation_package.
However, when flashing the new-boot.img to my device (with fastboot flash boot new-boot.img) the logo is not changed. Still showing the Sony logo before the bootanimation appears.
My tablet runs the Marshmallow firmware and I'm using the corresponding AndroPlusKernel v31 (Z4T_SGP771_AndroPlusKernel_v31.zip).
I tried already different tools like bootimg_tools from this xda forum, or split_bootimg.pl from the android-wiki.
The one mentioned in my question I found in several forums (wordpress, miui, dark-cyanide-devs ...)
Most of the tools I tried already did not repack the image correctly (fastboot reported "remote: dtb not found")
The tool I used, mentioned in the question, seemed to work for correcly unpacking and repacking. But as I said - the logo does not change -.-
Any suggestions what I am doing wrong?
Doesn't the initial splash logo reside in the bootloader or in another part of the system? I'm pretty sure it isn't in boot.img, at least this was not the case with my HTC phones.
jelbo said:
Doesn't the initial splash logo reside in the bootloader or in another part of the system? I'm pretty sure it isn't in boot.img, at least this was not the case with my HTC phones.
Click to expand...
Click to collapse
Thank you for your reply. Do you have any idea where I could find it? I already searched through the filesystem with the adb shell:
Code:
>find . -name "*.rle"
and also *.png, *.bmp, *.jpg or also > find . -name "*logo*"
I did not open the pictures I found, but by their name I could not tell if there is the logo beyond (besides the logo.rle)
I attached the search result if it helps somehow?
MM365 said:
Thank you for your reply. Do you have any idea where I could find it? I already searched through the filesystem with the adb shell:
Code:
>find . -name "*.rle"
and also *.png, *.bmp, *.jpg or also > find . -name "*logo*"
I did not open the pictures I found, but by their name I could not tell if there is the logo beyond (besides the logo.rle)
I attached the search result if it helps somehow?
Click to expand...
Click to collapse
I'm pretty sure it's not a file on a filesystem and, if it is, it would be on a partition you can not just search on easily. I remember having to flash a boot splash image on my HTC One m7 using fastboot flash splash1 splash.img. splash1 is the dedicated partition for the splash image, on mmcblk0p13.
I don't know how it is on Xperia's, but I guess it's similar. It'd be nice to be able to change this though, I also dislike the bright white Sony splash screen.
Here's the partition info I pulled from Disk Info Pro:
Code:
--------------------------
Internal Storage (MMC)
--------------------------
* TA [mmcblk0p1] Not mounted
Total space: 2 MB
* LTALabel [mmcblk0p2] (/lta-label) [ext4]
Used: 5.7 MB, Free: 10.3 MB, Total space: 16 MB
* modem [mmcblk0p3] (/firmware) [vfat]
Used: 16.8 MB, Free: 63.2 MB, Total space: 80 MB
* pmic [mmcblk0p4] Not mounted
Total space: 128 KB
* alt_pmic [mmcblk0p5] Not mounted
Total space: 128 KB
* limits [mmcblk0p6] Not mounted
Total space: 1 KB
* DDR [mmcblk0p7] Not mounted
Total space: 1 MB
* apdp [mmcblk0p8] Not mounted
Total space: 256 KB
* msadp [mmcblk0p9] Not mounted
Total space: 256 KB
* dpo [mmcblk0p10] Not mounted
Total space: 1 KB
* hyp [mmcblk0p11] Not mounted
Total space: 512 KB
* alt_hyp [mmcblk0p12] Not mounted
Total space: 512 KB
* fsg [mmcblk0p13] Not mounted
Total space: 1.5 MB
* ssd [mmcblk0p14] Not mounted
Total space: 8 KB
* sbl1 [mmcblk0p15] Not mounted
Total space: 1 MB
* alt_sbl1 [mmcblk0p16] Not mounted
Total space: 1 MB
* modemst1 [mmcblk0p17] Not mounted
Total space: 1.5 MB
* modemst2 [mmcblk0p18] Not mounted
Total space: 1.5 MB
* s1sbl [mmcblk0p19] Not mounted
Total space: 256 KB
* alt_s1sbl [mmcblk0p20] Not mounted
Total space: 256 KB
* sdi [mmcblk0p21] Not mounted
Total space: 128 KB
* alt_sdi [mmcblk0p22] Not mounted
Total space: 128 KB
* tz [mmcblk0p23] Not mounted
Total space: 1 MB
* alt_tz [mmcblk0p24] Not mounted
Total space: 1 MB
* rpm [mmcblk0p25] Not mounted
Total space: 512 KB
* alt_rpm [mmcblk0p26] Not mounted
Total space: 512 KB
* aboot [mmcblk0p27] Not mounted
Total space: 1 MB
* alt_aboot [mmcblk0p28] Not mounted
Total space: 1 MB
* boot [mmcblk0p29] Not mounted
Total space: 64 MB
* rdimage [mmcblk0p30] Not mounted
Total space: 32 MB
* persist [mmcblk0p31] (/persist) [ext4]
Used: 5.3 MB, Free: 26.7 MB, Total space: 32 MB
* FOTAKernel [mmcblk0p32] Not mounted
Total space: 64 MB
* misc [mmcblk0p33] Not mounted
Total space: 1 MB
* keystore [mmcblk0p34] Not mounted
Total space: 512 KB
* devinfo [mmcblk0p35] Not mounted
Total space: 1 KB
* config [mmcblk0p36] Not mounted
Total space: 512 KB
* rddata [mmcblk0p37] Not mounted
Total space: 100 MB
* apps_log [mmcblk0p38] (/rca) [ext4]
Used: 5.2 MB, Free: 4.8 MB, Total space: 10 MB
* diag [mmcblk0p39] (/idd) [ext4]
Used: 2.5 MB, Free: 13.5 MB, Total space: 16 MB
* oem [mmcblk0p40] (/oem) [ext4]
Used: 79.2 MB, Free: 220 MB, Total space: 300 MB
* Cache [mmcblk0p41] (/cache) [ext4]
Used: 11.4 MB, Free: 188 MB, Total space: 200 MB
* B2B [mmcblk0p42] Not mounted
Total space: 384 MB
* Data (userdata) [mmcblk0p43] (/data) [ext4]
Used: 13.7 GB, Free: 9 GB, Total space: 22.7 GB
* System [mmcblk0p44] (/system) [ext4]
Used: 4.3 GB, Free: 820 MB, Total space: 5.1 GB
* mmcblk0rpmb [mmcblk0rpmb] Not mounted
Total space: 4 MB
--------------------------
tmpfs mount points
--------------------------
* /dev [tmpfs]
Used: 144 KB, Free: 1.4 GB, Total space: 1.4 GB
* /mnt [tmpfs]
Used: 0 B, Free: 1.4 GB, Total space: 1.4 GB
* /tmp [tmpfs]
Used: 0 B, Free: 1.4 GB, Total space: 1.4 GB
* /storage [tmpfs]
Used: 0 B, Free: 1.4 GB, Total space: 1.4 GB
* /storage/self [tmpfs]
Used: 0 B, Free: 1.4 GB, Total space: 1.4 GB
jelbo said:
I'm pretty sure it's not a file on a filesystem and, if it is, it would be on a partition you can not just search on easily. I remember having to flash a boot splash image on my HTC One m7 using fastboot flash splash1 splash.img. splash1 is the dedicated partition for the splash image, on mmcblk0p13.
I don't know how it is on Xperia's, but I guess it's similar. It'd be nice to be able to change this though, I also dislike the bright white Sony splash screen.
Click to expand...
Click to collapse
Thank you for your help - I really appreciate it !
I tried to >fastboot flash splash custom.img
and >fastboot flash splash1 custom.img
and fastboot reports "Command not allowed"
Code:
target reported max download size of 536870912 bytes
sending 'splash' <750 KB>...
OKAY [0.052s]
writing 'splash'...
FAILED <remote: Command not allowed>
finished. total time: 0x077s
UsbDebugging is enabled.
I used the tool from this xda forum to create the img from a 450x800 png file.
I did not use the tool to flash the img because the tools adb reported my device as "offline" (rebooting did not help)
- so I tried to flash it manually with fastboot...
Do you have any suggestions what went wrong?
MM365 said:
Thank you for your help - I really appreciate it !
I tried to >fastboot flash splash custom.img
and >fastboot flash splash1 custom.img
and fastboot reports "Command not allowed"
Code:
target reported max download size of 536870912 bytes
sending 'splash' <750 KB>...
OKAY [0.052s]
writing 'splash'...
FAILED <remote: Command not allowed>
finished. total time: 0x077s
UsbDebugging is enabled.
I used the tool from this xda forum to create the img from a 450x800 png file.
I did not use the tool to flash the img because the tools adb reported my device as "offline" (rebooting did not help)
- so I tried to flash it manually with fastboot...
Do you have any suggestions what went wrong?
Click to expand...
Click to collapse
First of all, you should not run commands like that if you don't know exactly what you are doing. I'm by no means an expert in this, but when you read my list of partitions you can see there's no partition named splash or splash1. You tried to flash a file into that partition. Also, the file should not be 450x800 but likely the native resolution, which is 2560x1440.
Let me try to ping @[NUT], I'm pretty sure he can tell us right away if it's possible or not. In the meantime, I'll do a little search again myself. So far I haven't found a lot. Looks like it is indeed an .rle file in the kernel.
jelbo said:
First of all, you should not run commands like that if you don't know exactly what you are doing. I'm by no means an expert in this, but when you read my list of partitions you can see there's no partition named splash or splash1. You tried to flash a file into that partition. Also, the file should not be 450x800 but likely the native resolution, which is 2560x1440.
Let me try to ping @[NUT], I'm pretty sure he can tell us right away if it's possible or not. In the meantime, I'll do a little search again myself. So far I haven't found a lot. Looks like it is indeed an .rle file in the kernel.
Click to expand...
Click to collapse
Ok. Thanks.
please let me know if you come to any conclusion.
well, now it's getting interesting.
supersu didn't work for me (always failed to patch boot.img) but i found another way to get root. xda is just great.
it's definitely not my work...just used other people's achievements, so all credits go to them!!!
!!! Please, don't blame me if sth goes wrong. It worked for me and my model. Do it on your won risk!
!!! Before you do anything, back up your phone (in TWRP)
so what you need to gain root:
Yoga Book [YB1-X9OL]
working ADB --> e.g. see here
unlocked bootloader --> see here (unlocking the bootloader does a factory reset, so back up your data)
twrp_recovery --> see here (do not flash it, just boot temporarily)
files for root --> see end of post
1. download attached file
2. boot twrp
3. install 1-Magisk-v7.zip
4. install 2-phh-superuser-magisk-r259.zip
5. reboot
6. install 3-Phh Superuser_1.0.3.3.apk
7. install a root checker to verify
got this way from here: https://forum.xda-developers.com/honor-4x/help/honor-4x-che1-l04-mm-6-0-1-emui-4-root-t3475854/
more about magisk can be found here (maybe even a newer solution/version): https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
screenshot:
{
"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"
}
files for root: View attachment MMroot.zip
EDIT:
You can also use the newest version of Magisk (v.10.2.) to get root, but then follow the following steps:
1. download and install the newest magisk.zip via twrp, phh's superuser is already included, so no need to install it seperately (as with v.7)
2. reboot system
3. install phh's superuser manager from playstore
!!!if you want to update from Magisk v.7., don't do it with magiskmanager cause it will break root.
donwload Magisk's uninstaller.zip (get it here) and install it via twrp before you install v.10.2.
Awesome ! I can't wait to try it , but it's so sad that I have to review my courses now :crying:
Awesome, thanks to the OP, thanks to the god, I installed it perfectly, now it looks stable when I use it
AndyVerne said:
Awesome, thanks to the OP, thanks to the god, I installed it perfectly, now it looks stable when I use it
Click to expand...
Click to collapse
hey u used the instructions above? im a newbie in this so any instructions from yr side on how to do it?
bisharat said:
hey u used the instructions above? im a newbie in this so any instructions from yr side on how to do it?
Click to expand...
Click to collapse
what help do you need?
Hey
What method do you recommend for backing up everything before unlocking for those who do not use google or lenovo services?
So why do you say to not actually flash TWRP, but to only boot to it temporarily? Does this fail if you properly flash TWRP?
Anyone tried this on the non-LTE version YB1-X90F?
west0ne said:
Anyone tried this on the non-LTE version YB1-X90F?
Click to expand...
Click to collapse
i think it would work. i think most important is to know whether partitions are the same and twrp is working.
to find out install disk info and copy the details about your partitions (via the share symbol).
also install AIDA64 then go to "system files" (?) and click on build.prop and copy the information there. do the same for /proc/partitions.
i will check the similarities.
nevertheless you could try to boot (!!!not flash!!!) the recovery, just to see if it boots at all (if yes and partitions are the same, it should be save) as you do not flash it, it doesn't hurt your device but do not use it in any way.
heldc said:
So why do you say to not actually flash TWRP, but to only boot to it temporarily? Does this fail if you properly flash TWRP?
Click to expand...
Click to collapse
because i'm not an experienced developer...and i don't know if it will break at one point or fails in any way (i didn't build it from source, just modified twrp from yoga tab 3 pro).
so if you only boot it, stock recovery will still be there and you could flash stockrom if nothing works at all. I must say I feel quite comfortable this way...use twrp whenever i must, but have stock untouched.
on the other hand, so far twrp worked quite well for me
if you dare flash it, i won't take responsibility in any way.
secondly, doing ota update should be a lot easier with stock recovery.
hope you see my points!?
hajkan said:
Hey
What method do you recommend for backing up everything before unlocking for those who do not use google or lenovo services?
Click to expand...
Click to collapse
funny question, because there's no satisfying way to back up everything without twrp or root! it' s the main reason why i started to find a way for root and 'porting' a custom recovery. now i can use titanium or whatever tool to back up and of course twrp to back up all partitions.
back up what's possible.
danjac said:
i think it would work. i think most important is to know whether partitions are the same and twrp is working............
i will check the similarities.
nevertheless you could try to boot (!!!not flash!!!) the recovery, just to see if it boots at all (if yes and partitions are the same, it should be save) as you do not flash it, it doesn't hurt your device but do not use it in any way.
Click to expand...
Click to collapse
I've not had a chance to try the twrp yet but will give it a go but in the mean time.
Thanks.
Here is the diskinfo.
Code:
--------------------------
Internal Storage (MMC)
--------------------------
* Cache (android_cache) [mmcblk0p12] (/cache) [ext4]
Used: 14.3 MB, Free: 241 MB, Total space: 256 MB
* System (android_system) [mmcblk0p13] (/system) [ext4]
Used: 3.2 GB, Free: 582 MB, Total space: 3.8 GB
* Data (android_data) [mmcblk0p14] (/data) [ext4]
Used: 9.2 GB, Free: 43.7 GB, Total space: 53 GB
--------------------------
SD Card
--------------------------
* SD card [mmcblk1p1] (/mnt/media_rw/B260-11FE, /storage/B260-11FE) [vfat]
Used: 11.5 GB, Free: 17.4 GB, Total space: 29 GB
--------------------------
Memory
--------------------------
* RAM
Used: 992 MB, Free: 2.8 GB, Total space: 3.8 GB
Here's the build.prop
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MMB29M
ro.build.display.id=YB1-X90F_USR_S000239_1612091428_WW06_BP_ROW
ro.build.version.incremental=YB1-X90F_USR_S000239_1612091428_WW06_BP_ROW
ro.build.version.sdk=23
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=6.0.1
ro.build.version.security_patch=2016-10-01
ro.build.version.base_os=
ro.build.date=2016年 12月 09日 星期五 15:04:15 CST
ro.build.date.utc=1481267055
ro.build.type=user
ro.build.user=buildslave
ro.build.host=bjws76
ro.build.tags=release-keys
ro.build.flavor=yeti_10_row_wifi-user
ro.product.ota.model=Lenovo YB1-X90F
ro.product.model=Lenovo YB1-X90F
ro.product.brand=Lenovo
ro.product.name=yeti_10_row_wifi
ro.product.device=yeti
ro.product.board=r2_cht_ffd
ro.lenovo.mtpname=YOGA BOOK
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=x86_64
ro.product.cpu.abilist=x86_64,x86,armeabi-v7a,armeabi,arm64-v8a
ro.product.cpu.abilist32=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist64=x86_64,arm64-v8a
ro.product.manufacturer=LENOVO
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=gmin
# ro.build.product is obsolete; use ro.product.device
ro.build.product=yeti
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=yeti_10_row_wifi-user 6.0.1 MMB29M YB1-X90F_USR_S000239_1612091428_WW06_BP_ROW release-keys
ro.build.fingerprint=Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000239_161209:user/release-keys
ro.build.characteristics=tablet
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.camera.rec.pixel_format=0x10F
sys.powerctl.no.shutdown=1
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=144m
dalvik.vm.heapsize=384m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.dalvik.vm.isa.arm=x86
ro.enable.native.bridge.exec=1
ro.dalvik.vm.isa.arm64=x86_64
ro.enable.native.bridge.exec64=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=6.0_r7
ro.opengles.version=196609
ro.ycbcr.pixel_format=0x10F
ro.spid.gps.FrqPlan=FRQ_PLAN_26MHZ_2PPM
ro.spid.gps.RfType=GL_RF_4752_BRCM_EXT_LNA
ro.spid.gps.pmm=disabled
drm.service.enabled=true
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=Notice.ogg
ro.carrier=unknown
ro.config.alarm_alert=New_Morning.ogg
ro.lenovo.device=tablet
ro.com.google.clientidbase=android-lenovo
persist.backgrounddata.enable=false
ro.lenovo.wificert=no
ro.lenovo.childmode=true
ro.lenovo.mtpname=YOGA
BOOK
ro.product.ota.model=Lenovo
YB1-X90F
debug.show_anr_dialog=false
log.tag.VibeTonz=ERROR
ro.lenovo.operator=open
ro.yeti.telephony.call=false
ro.lenovo.region=row
ro.lenovo.sim=none
ro.lenovo.tablet=wifi
ro.lenovo.platform=intel
ro.lenovo.bqb=pass
ro.lenovo.cta=false
ro.lenovo.videocall=false
persist.sys.timezone=Asia/Shanghai
persist.sys.language=zh
persist.sys.country=CN
ro.product.locale.language=zh
ro.product.locale.region=CN
persist.sys.dalvik.vm.lib.2=libart
dalvik.vm.isa.x86_64.variant=silvermont
dalvik.vm.isa.x86_64.features=default
dalvik.vm.isa.x86.variant=silvermont
dalvik.vm.isa.x86.features=default
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.expect.recovery_id=0x543ffafdb4f6e02c750f8f5883ce5d8b763f13a3000000000000000000000000
west0ne said:
I've not had a chance to try the twrp yet but will give it a go but in the mean time.
Thanks.
Here is the diskinfo.
Code:
--------------------------
Internal Storage (MMC)
--------------------------
* Cache (android_cache) [mmcblk0p12] (/cache) [ext4]
Used: 14.3 MB, Free: 241 MB, Total space: 256 MB
* System (android_system) [mmcblk0p13] (/system) [ext4]
Used: 3.2 GB, Free: 582 MB, Total space: 3.8 GB
* Data (android_data) [mmcblk0p14] (/data) [ext4]
Used: 9.2 GB, Free: 43.7 GB, Total space: 53 GB
--------------------------
SD Card
--------------------------
* SD card [mmcblk1p1] (/mnt/media_rw/B260-11FE, /storage/B260-11FE) [vfat]
Used: 11.5 GB, Free: 17.4 GB, Total space: 29 GB
--------------------------
Memory
--------------------------
* RAM
Used: 992 MB, Free: 2.8 GB, Total space: 3.8 GB
Here's the build.prop
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MMB29M
ro.build.display.id=YB1-X90F_USR_S000239_1612091428_WW06_BP_ROW
ro.build.version.incremental=YB1-X90F_USR_S000239_1612091428_WW06_BP_ROW
ro.build.version.sdk=23
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=6.0.1
ro.build.version.security_patch=2016-10-01
ro.build.version.base_os=
ro.build.date=2016年 12月 09日 星期五 15:04:15 CST
ro.build.date.utc=1481267055
ro.build.type=user
ro.build.user=buildslave
ro.build.host=bjws76
ro.build.tags=release-keys
ro.build.flavor=yeti_10_row_wifi-user
ro.product.ota.model=Lenovo YB1-X90F
ro.product.model=Lenovo YB1-X90F
ro.product.brand=Lenovo
ro.product.name=yeti_10_row_wifi
ro.product.device=yeti
ro.product.board=r2_cht_ffd
ro.lenovo.mtpname=YOGA BOOK
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=x86_64
ro.product.cpu.abilist=x86_64,x86,armeabi-v7a,armeabi,arm64-v8a
ro.product.cpu.abilist32=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist64=x86_64,arm64-v8a
ro.product.manufacturer=LENOVO
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=gmin
# ro.build.product is obsolete; use ro.product.device
ro.build.product=yeti
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=yeti_10_row_wifi-user 6.0.1 MMB29M YB1-X90F_USR_S000239_1612091428_WW06_BP_ROW release-keys
ro.build.fingerprint=Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000239_161209:user/release-keys
ro.build.characteristics=tablet
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.camera.rec.pixel_format=0x10F
sys.powerctl.no.shutdown=1
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=144m
dalvik.vm.heapsize=384m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.dalvik.vm.isa.arm=x86
ro.enable.native.bridge.exec=1
ro.dalvik.vm.isa.arm64=x86_64
ro.enable.native.bridge.exec64=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=6.0_r7
ro.opengles.version=196609
ro.ycbcr.pixel_format=0x10F
ro.spid.gps.FrqPlan=FRQ_PLAN_26MHZ_2PPM
ro.spid.gps.RfType=GL_RF_4752_BRCM_EXT_LNA
ro.spid.gps.pmm=disabled
drm.service.enabled=true
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=Notice.ogg
ro.carrier=unknown
ro.config.alarm_alert=New_Morning.ogg
ro.lenovo.device=tablet
ro.com.google.clientidbase=android-lenovo
persist.backgrounddata.enable=false
ro.lenovo.wificert=no
ro.lenovo.childmode=true
ro.lenovo.mtpname=YOGA
BOOK
ro.product.ota.model=Lenovo
YB1-X90F
debug.show_anr_dialog=false
log.tag.VibeTonz=ERROR
ro.lenovo.operator=open
ro.yeti.telephony.call=false
ro.lenovo.region=row
ro.lenovo.sim=none
ro.lenovo.tablet=wifi
ro.lenovo.platform=intel
ro.lenovo.bqb=pass
ro.lenovo.cta=false
ro.lenovo.videocall=false
persist.sys.timezone=Asia/Shanghai
persist.sys.language=zh
persist.sys.country=CN
ro.product.locale.language=zh
ro.product.locale.region=CN
persist.sys.dalvik.vm.lib.2=libart
dalvik.vm.isa.x86_64.variant=silvermont
dalvik.vm.isa.x86_64.features=default
dalvik.vm.isa.x86.variant=silvermont
dalvik.vm.isa.x86.features=default
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.expect.recovery_id=0x543ffafdb4f6e02c750f8f5883ce5d8b763f13a3000000000000000000000000
Click to expand...
Click to collapse
oh damn, could you please get the info about partitions from disk info again. the most important partitions are missing...like boot, bootloader, recovery, ...
just go to settings and make sure that you check all the following settings (see the attached screenshot):
show mount path
show partition name
show file name
expert mode
unmounted partitions
devicemapper partitions
temp. filesystems
danjac said:
i think it would work. i think most important is to know whether partitions are the same and twrp is working.
to find out install disk info and copy the details about your partitions (via the share symbol).
also install AIDA64 then go to "system files" (?) and click on build.prop and copy the information there. do the same for /proc/partitions.
i will check the similarities.
nevertheless you could try to boot (!!!not flash!!!) the recovery, just to see if it boots at all (if yes and partitions are the same, it should be save) as you do not flash it, it doesn't hurt your device but do not use it in any way.
Click to expand...
Click to collapse
danjac said:
oh damn, could you please get the info about partitions from disk info again. the most important partitions are missing...like boot, bootloader, recovery, ...
just go to settings and make sure that you check all the following settings (see the attached screenshot):
show mount path
show partition name
show file name
expert mode
unmounted partitions
devicemapper partitions
temp. filesystems
View attachment 4001102
Click to expand...
Click to collapse
More detailed disk-info
Code:
--------------------------
Internal Storage (MMC)
--------------------------
* android_bootloader [mmcblk0p1] Not mounted
Total space: 100 MB
* android_bootloader2 [mmcblk0p2] Not mounted
Total space: 100 MB
* android_boot [mmcblk0p3] Not mounted
Total space: 30 MB
* android_recovery [mmcblk0p4] Not mounted
Total space: 30 MB
* android_misc [mmcblk0p5] Not mounted
Total space: 1 MB
* android_metadata [mmcblk0p6] Not mounted
Total space: 16 MB
* android_persistent [mmcblk0p7] Not mounted
Total space: 1 MB
* android_frp [mmcblk0p8] Not mounted
Total space: 1 MB
* android_config [mmcblk0p9] (/config) [ext4]
Used: 4.4 MB, Free: 3.6 MB, Total space: 8 MB
* android_factory [mmcblk0p10] (/factory) [ext4]
Used: 4.4 MB, Free: 5.6 MB, Total space: 10 MB
* android_country [mmcblk0p11] (/country) [ext4]
Used: 90 MB, Free: 934 MB, Total space: 1 GB
* Cache (android_cache) [mmcblk0p12] (/cache) [ext4]
Used: 14.3 MB, Free: 241 MB, Total space: 256 MB
* System (android_system) [mmcblk0p13] (/system) [ext4]
Used: 3.2 GB, Free: 582 MB, Total space: 3.8 GB
* Data (android_data) [mmcblk0p14] (/data) [ext4]
Used: 9.4 GB, Free: 43.6 GB, Total space: 53 GB
* mmcblk0rpmb [mmcblk0rpmb] Not mounted
Total space: 4 MB
* mmcblk0boot1 [mmcblk0boot1] Not mounted
Total space: 4 MB
* mmcblk0boot0 [mmcblk0boot0] Not mounted
Total space: 4 MB
--------------------------
SD Card
--------------------------
* SD card [mmcblk1p1] (/mnt/media_rw/B260-11FE, /storage/B260-11FE) [vfat]
Used: 12.3 GB, Free: 16.6 GB, Total space: 29 GB
--------------------------
Memory
--------------------------
* RAM
Used: 1.5 GB, Free: 2.3 GB, Total space: 3.8 GB
Hey there,
I'm trying to root my Yoga Book too. I have a related post with a little question here : https://forum.xda-developers.com/yoga-book/help/missing-usb-driver-cherry-trail-tablet-t3537008
Thank you !
west0ne said:
More detailed disk-info
Code:
--------------------------
Internal Storage (MMC)
--------------------------
* android_bootloader [mmcblk0p1] Not mounted
Total space: 100 MB
* android_bootloader2 [mmcblk0p2] Not mounted
Total space: 100 MB
* android_boot [mmcblk0p3] Not mounted
Total space: 30 MB
* android_recovery [mmcblk0p4] Not mounted
Total space: 30 MB
* android_misc [mmcblk0p5] Not mounted
Total space: 1 MB
* android_metadata [mmcblk0p6] Not mounted
Total space: 16 MB
* android_persistent [mmcblk0p7] Not mounted
Total space: 1 MB
* android_frp [mmcblk0p8] Not mounted
Total space: 1 MB
* android_config [mmcblk0p9] (/config) [ext4]
Used: 4.4 MB, Free: 3.6 MB, Total space: 8 MB
* android_factory [mmcblk0p10] (/factory) [ext4]
Used: 4.4 MB, Free: 5.6 MB, Total space: 10 MB
* android_country [mmcblk0p11] (/country) [ext4]
Used: 90 MB, Free: 934 MB, Total space: 1 GB
* Cache (android_cache) [mmcblk0p12] (/cache) [ext4]
Used: 14.3 MB, Free: 241 MB, Total space: 256 MB
* System (android_system) [mmcblk0p13] (/system) [ext4]
Used: 3.2 GB, Free: 582 MB, Total space: 3.8 GB
* Data (android_data) [mmcblk0p14] (/data) [ext4]
Used: 9.4 GB, Free: 43.6 GB, Total space: 53 GB
* mmcblk0rpmb [mmcblk0rpmb] Not mounted
Total space: 4 MB
* mmcblk0boot1 [mmcblk0boot1] Not mounted
Total space: 4 MB
* mmcblk0boot0 [mmcblk0boot0] Not mounted
Total space: 4 MB
--------------------------
SD Card
--------------------------
* SD card [mmcblk1p1] (/mnt/media_rw/B260-11FE, /storage/B260-11FE) [vfat]
Used: 12.3 GB, Free: 16.6 GB, Total space: 29 GB
--------------------------
Memory
--------------------------
* RAM
Used: 1.5 GB, Free: 2.3 GB, Total space: 3.8 GB
Click to expand...
Click to collapse
partitions are vrtually the same...just try to boot it. i think there's a good chance it might work, if it starts try and test it...e.g. backup and restore data, see if terminal works and so on...
if yes i think you are good to go
but as always....no guarantee!!!
This worked perfectly for me. Thank you so much!
west0ne said:
More detailed disk-info
Click to expand...
Click to collapse
did you test it? would be nice to get some feedback / results.
cheers.
danjac said:
did you test it? would be nice to get some feedback / results.
cheers.
Click to expand...
Click to collapse
Fastboot seemed to just hang. Going to try downloading a different version and with desktop rather than laptop.
west0ne said:
Fastboot seemed to just hang. Going to try downloading a different version and with desktop rather than laptop.
Click to expand...
Click to collapse
would be nice!
by now, i have one confirmation that twrp and root worked for YB1-X90F (WIFI) from liguangming1981.
but two are better than one