Database Users

[Dev-request][HACK] Increase Internal Memory Size

Galaxy 3 Devs , please take a look on this.
http://forum.xda-developers.com/showthread.php?t=1398797
{
"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"
}
Kernel needs to be patched for this. I am not having access to my PC so if any kernel dev can pull this off then it would be great.
Instructions:-
1-Add Ext4 kernel Modules
Compile the jbd2.ko and ext4.ko modules for the Kernel and put them into /lib/modules inside the ramdisk:
Code:
gandalf $ ls -l ./ramdisk/lib/modules/
totale 1304
-rw-r--r-- 1 root root 236116 11 dic 08.24 ext4.ko
-rw-r--r-- 1 root root 363932 11 dic 08.24 fsr.ko
-rw-r--r-- 1 root root 211200 11 dic 08.24 fsr_stl.ko
-rw-r--r-- 1 root root 58176 11 dic 08.24 jbd2.ko
-rw-r--r-- 1 root root 260568 11 dic 08.24 rfs_fat.ko
-rw-r--r-- 1 root root 90968 11 dic 08.24 rfs_glue.ko
-rw-r--r-- 1 root root 99532 11 dic 08.24 sec_param.ko
gandalf $
2- Patch init.rc file
Patch the init.rc file into the ramdisk to load these modules into the kernel immediately after the first boot stage of the firmware:
Code:
# insmod fsr/rfs modules
insmod /lib/modules/fsr.ko
insmod /lib/modules/fsr_stl.ko
insmod /lib/modules/rfs_glue.ko
insmod /lib/modules/rfs_fat.ko
insmod /lib/modules/sec_param.ko
insmod /lib/modules/jbd2.ko
insmod /lib/modules/ext4.ko
3- Add busybox
Add a copy of busybox into /sbin.
We need it to mount ext4 filesystems on microSD later on.
Code:
gandalf $ ls -l ./ramdisk/sbin/
totale 2088
-rwxr-x--- 1 root root 117948 11 dic 08.18 adbd
-rwsr-xr-x 1 root root 2016700 11 dic 08.21 busybox
lrwxrwxrwx 1 root root 7 11 dic 08.18 ueventd -> ../init
(i686) gandalf ~ (i686) $
4- Patch init.rc again
Change the mount command for /data!
Original code:
Code:
# Mounting of system/userdata is moved to 'on emmc' and 'on nand' sections
# We chown/chmod /data again so because mount is run as root + defaults
[COLOR="Red"]mount rfs /dev/stl6 /data nosuid nodev check=no[/COLOR]
chown system system /data
chmod 0771 /data
Patched code:
Code:
# Mounting of system/userdata is moved to 'on emmc' and 'on nand' sections
# We chown/chmod /data again so because mount is run as root + defaults
[COLOR="red"]exec /sbin/busybox sh /init.data.sh[/COLOR]
chown system system /data
chmod 0771 /data
5- Add init.data.sh file
Add an external shell file, used to mount microsd /data avoiding the Android Init Language used by init.rc.
Code:
gandalf $ cat ./ramdisk/init.data.sh
#!/sbin/busybox sh
/sbin/busybox mount -o nosuid,nodev -t ext4 /dev/block/mmcblk0p2 /data || /sbin/busybox mount -o nosuid,nodev -t rfs /dev/stl7 /data
gandalf $

nice...but it's only for stock ROMs and would probably cause the phone to run slower...

Great concept, particularly but with data to sd, you can put almost all files of app to sd...
Lots of space without increasing memory...
Yet a good concept...

I actually like the implementation of this, but what happens when the SD card is removed?

"If I want to remove the microSD from the slot, FIRST I NEED TO SWITCH OFF THE PHONE!"
No SD, No Phone

kylandomos said:
"If I want to remove the microSD from the slot, FIRST I NEED TO SWITCH OFF THE PHONE!"
No SD, No Phone
Click to expand...
Click to collapse
Yeah... pass.

Doesn't Hybrid Data2Sd already do this?
If not, what is the difference between the two?

maverickgenius said:
Doesn't Hybrid Data2Sd already do this?
If not, what is the difference between the two?
Click to expand...
Click to collapse
Initial app2sd scripts by apollo used to show ext4 space in task manager but currently no script does so. No idea what Hybrid Data2SD actually is.
Sent from my GT-I5800 using Tapatalk

arunmcops said:
Initial app2sd scripts by apollo used to show ext4 space in task manager but currently no script does so. No idea what Hybrid Data2SD actually is.
Sent from my GT-I5800 using Tapatalk
Click to expand...
Click to collapse
even my wait is long to see a kernel/rom to actually show ext4 space in task manager.
G3MOD kernel 2.0(and lower version) supports this feature in the form of data2sd(not apps2sd or hybrid data2sd). But the developers of this kernel messed up the code and later versions of their kernel doesn't seems to support this.

how to compile a script
How to compile a script?

arunmcops said:
Galaxy 3 Devs , please take a look on this.
Kernel needs to be patched for this. I am not having access to my PC so if any kernel dev can pull this off then it would be great.
Click to expand...
Click to collapse
umm.... did i hear the word "HACK' okay ill take and merge this script on my sense port.... maybe in build 1

arunmcops said:
Initial app2sd scripts by apollo used to show ext4 space in task manager but currently no script does so. No idea what Hybrid Data2SD actually is.
Sent from my GT-I5800 using Tapatalk
Click to expand...
Click to collapse
If I remember it right, apollo used the same thing in dual boot kernel. He said its very easy. You can request him to make a new kernel.

This is interesting... Devs pls try this on our G3.
Sent from my GT-I5800 using Tapatalk

Nice job making it to the front page!
Just an idea.
If ClockworkMod is merged with the kernel, people that like to remove their SDCARD can first flash the stock kernel, or any kernel with ClockworkMod and then remove the SDCARD.
Unless I totally read that wrong.
Sent from my Samsung Galaxy S II w/ CM9

The Dark Lestat said:
Nice job making it to the front page!
Just an idea.
If ClockworkMod is merged with the kernel, people that like to remove their SDCARD can first flash the stock kernel, or any kernel with ClockworkMod and then remove the SDCARD.
Unless I totally read that wrong.
Sent from my Samsung Galaxy S II w/ CM9
Click to expand...
Click to collapse
Yes, exactly.
And also this is where a class 10 SD card would shine. Standard internal memory is usually around a class 6.

Clean and efficient, I like. Mounts ext part, if not there it mounts traditional data partition. IE: If you want 2 partitions or you don't want it to take up your SD, don't insert it till after the device is on.

Hamdiz said:
How to compile a script?
Click to expand...
Click to collapse
You'll need to edit from the kernel source and then compile the whole kernel to zImage.
---------- Post added at 12:14 AM ---------- Previous post was at 12:11 AM ----------
arunmcops said:
Galaxy 3 Devs , please take a look on this.
http://forum.xda-developers.com/showthread.php?t=1398797
Kernel needs to be patched for this. I am not having access to my PC so if any kernel dev can pull this off then it would be great.
Instructions:-
1-Add Ext4 kernel Modules
Compile the jbd2.ko and ext4.ko modules for the Kernel and put them into /lib/modules inside the ramdisk:
Code:
gandalf $ ls -l ./ramdisk/lib/modules/
totale 1304
-rw-r--r-- 1 root root 236116 11 dic 08.24 ext4.ko
-rw-r--r-- 1 root root 363932 11 dic 08.24 fsr.ko
-rw-r--r-- 1 root root 211200 11 dic 08.24 fsr_stl.ko
-rw-r--r-- 1 root root 58176 11 dic 08.24 jbd2.ko
-rw-r--r-- 1 root root 260568 11 dic 08.24 rfs_fat.ko
-rw-r--r-- 1 root root 90968 11 dic 08.24 rfs_glue.ko
-rw-r--r-- 1 root root 99532 11 dic 08.24 sec_param.ko
gandalf $
2- Patch init.rc file
Patch the init.rc file into the ramdisk to load these modules into the kernel immediately after the first boot stage of the firmware:
Code:
# insmod fsr/rfs modules
insmod /lib/modules/fsr.ko
insmod /lib/modules/fsr_stl.ko
insmod /lib/modules/rfs_glue.ko
insmod /lib/modules/rfs_fat.ko
insmod /lib/modules/sec_param.ko
insmod /lib/modules/jbd2.ko
insmod /lib/modules/ext4.ko
3- Add busybox
Add a copy of busybox into /sbin.
We need it to mount ext4 filesystems on microSD later on.
Code:
gandalf $ ls -l ./ramdisk/sbin/
totale 2088
-rwxr-x--- 1 root root 117948 11 dic 08.18 adbd
-rwsr-xr-x 1 root root 2016700 11 dic 08.21 busybox
lrwxrwxrwx 1 root root 7 11 dic 08.18 ueventd -> ../init
(i686) gandalf ~ (i686) $
4- Patch init.rc again
Change the mount command for /data!
Original code:
Code:
# Mounting of system/userdata is moved to 'on emmc' and 'on nand' sections
# We chown/chmod /data again so because mount is run as root + defaults
[COLOR="Red"]mount rfs /dev/stl6 /data nosuid nodev check=no[/COLOR]
chown system system /data
chmod 0771 /data
Patched code:
Code:
# Mounting of system/userdata is moved to 'on emmc' and 'on nand' sections
# We chown/chmod /data again so because mount is run as root + defaults
[COLOR="red"]exec /sbin/busybox sh /init.data.sh[/COLOR]
chown system system /data
chmod 0771 /data
5- Add init.data.sh file
Add an external shell file, used to mount microsd /data avoiding the Android Init Language used by init.rc.
Code:
gandalf $ cat ./ramdisk/init.data.sh
#!/sbin/busybox sh
/sbin/busybox mount -o nosuid,nodev -t ext4 /dev/block/mmcblk0p2 /data || /sbin/busybox mount -o nosuid,nodev -t rfs /dev/stl7 /data
gandalf $
Click to expand...
Click to collapse
Nice guide, I will try to build this kernel mod tomorrow. and btw, do we need any partition to make this work?

Since it's a ramdisk tweak, you could even unpack, tweak and repackage.
My Tab makes phone calls yo! (GT-P6800)

Please tell me when you get success. Waiting for a long time to see it work.

arunmcops said:
Please tell me when you get success. Waiting for a long time to see it work.
Click to expand...
Click to collapse
probably next week, cause I'm going to a trip! I will compile it with the stock kernel.....

Lost root on smoothrom 4.1(urgent help needed)

hello guys,yesterday i flashed smoothrom 4.1 and everything was fine. Today i noticed that some root apps are telling me to allow root access through supersu. In supersu i found that all my root apps were granted.Then i downloaded Root checker from google play and it is telling me i have no root. I have already tried flashing supersu.zip from TWRP....after booting backup it is still not rooted. Any solution for this.i am willing to reflash everything except wiping my device.
{
"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"
}
more details from root cheker pro : Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - is NOT installed!
SuperSU application - version 1.25 - is installed!
System File Properties for Root Access:
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 96260 2013-03-21 15:36 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your Nexus 7 device by Root Checker Pro version 1.3.1 from joeykrim in the Android Market - http://goo.gl/NcnHn

problem solved
i myself don't know what i did...but i have root access again

[SOLVED] /system cannot be mounted

SOLVED! Thanks to Alex240188
Alex240188 said:
here is what i have done and just tested as working
If you are using Supersu binaries ignore this step
***PHONE***
Apps > Settings > Developer Options > Root Access > Apps and ADB
***PC Command Prompt***
adb shell
su
***PHONE***
confirm SU popup on phone
*** PC Command Prompt***
Ctrl + C (to exit shell)
adb root
Code:
restarting adbd as root
adb shell
mount -o remount,rw /system
mount
look for this line (it will tell you if you have failed or successfully remounted)
Failed
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 [b][u]ro[/u][/b],seclabel,relatime,data=ordered 0 0
Success
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 [b][u]rw[/u][/b],seclabel,relatime,data=ordered 0 0
CTRL + C to exit from shell
adb push "yourfile.ext" /system/"whereyouwanttoputit"/
in my case
adb push test.txt /system/app/
{
"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"
}
after this initial setup and working point, all you should have to do to future mount as RW in adb is the following 2 commands
adb root
adb shell mount -o remount,rw /system
then when your finished
adb shell mount -o remount,ro /system
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------------
I have a problem making my windows 8 PC write on the /system partition of the nexus 4.
I've tried all of these:
Code:
***adb remount.... FAIL
***adb shell (enter)
mount (enter)
(saw where the system partition is located)
mount -o rw,remount /dev/block/mmcblk0p21 /system....FAIL
***mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system... FAIL
***adb root... FAIL
***called my mother and told her that she wasn't lying to me
The mount -o.... commands do make the system writable, but only on phone and not via PC.
"mount" gives me that /system is rw, but i still can't push files to /system so that means i can only modify /system from the phone itself (or from adb shell), so when i enter the shell, /system is mounted, but when i exit the shell, /system isn't mounted
What i want to do is to make "adb push (bla) /system" work, without going to recovery, nor shell.
I can give details if needed.
Thank you.

Try putting the phone into recovery mode first. Then run:
Code:
adb remount
adb push blahblah.bla /system/

Chromium_ said:
Try putting the phone into recovery mode first. Then run:
Code:
adb remount
adb push blahblah.bla /system/
Click to expand...
Click to collapse
thanks for reminding me... i've added in OP that i don't want to be in recovery, i want to do it while the phone is booted.
Sent from my Nexus 4

so anyone?

Riro Zizo said:
so anyone?
Click to expand...
Click to collapse
here is what i have done and just tested as working
If you are using Supersu binaries ignore this step
***PHONE***
Apps > Settings > Developer Options > Root Access > Apps and ADB
***PC Command Prompt***
adb shell
su
***PHONE***
confirm SU popup on phone
*** PC Command Prompt***
Ctrl + C (to exit shell)
adb root
Code:
restarting adbd as root
adb shell
mount -o remount,rw /system
mount
look for this line (it will tell you if you have failed or successfully remounted)
Failed
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 [b][u]ro[/u][/b],seclabel,relatime,data=ordered 0 0
Success
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 [b][u]rw[/u][/b],seclabel,relatime,data=ordered 0 0
CTRL + C to exit from shell
adb push "yourfile.ext" /system/"whereyouwanttoputit"/
in my case
adb push test.txt /system/app/
after this initial setup and working point, all you should have to do in the future to mount as RW is the following 2 commands
adb root
adb shell mount -o remount,rw /system
then you can
adb push blah.apk /system/app/
adb push bootanimation.zip /system/media/
then when your finished
adb shell mount -o remount,ro /system

Thanks a TON! I wouldn't have lived without doing that! I should put that in OP now...

Root access

Below is the results from Root Checker Pro. I used Towelroot to Root this device a few weeks ago. When i opened SuperSu today I got a prompt to install the SU binary again. Here are the SS's.
{
"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"
}
When I tap OK I get this:
I tap normal and get this:
And then the app closes. Trying again after a reboot produces the same results.
I know that it successfully rooted a few weeks ago and all apps that need root access are functioning fine. Xposed and other root apps are running flawlessly. Knox is unharmed at 0x0 and there is no custom recovery yet. (Wasn't sure if I wanted to void warranty yet). I was considering flashing Safestrap tonight but I don't want to proceed if there are issues. Any suggestions?
-------------
Congratulations! You have root access!
Super User Application Status:
SuperSU application - version 2.01 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 125420 2014-09-29 15:03 su
Analysis: Setuid attribute is not present BUT root user ownership is present. Root access IS correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
Root user id:
uid=0(root)
Root group id:
gid=0(root)
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your SM-N900V - Android 4.4.2 device by Root Checker Pro version 1.3.7 from joeykrim in the Android Market - http://goo.gl/NcnHn

I usually select the twrp option and then reboot and try the install a couple times...eventually it will take.

[GUIDE] Overlapping Partition Tables? Let's fix that

WARNING! Main partition table overlaps the first partition by 6 blocks!
You will need to delete this partition or resize it in an other utility.
This guide is to help those, facing this message, who have been in a mixup when repartitioning their Google Pixel 2 XL devices with the introduction of Android 12 and later ROMs/GSI Images.
More specifically this situation occurs when one follows Dollscythe's 3.8GiB system guide, followed by my (PixelExperience) repartition script.
No worries, let's solve this.
DISCLAIMER:
I AM NOT RESPONSIBLE IF THESE FOLLOWING INSTRUCTIONS ARE NOT EXECUTED PROPERLY.
KINDLY TRIPLE CHECK THE COPIED COMMANDS BEFORE EXECUTING THEM.
ANY ALTERATION TO THE PARTITIONS NOT MENTIONED BELOW COULD CAUSE SERIOUS ISSUES.
Firstly, let's understand why this occurs.
When it comes to repartitioning using sgdisk, with the case of the PixelExperience repartition method, blocks strictly defined from a starting to an ending logical sector.
(FYI: 1 logical sector = 4096 bytes)
When a user follows Dollscythe's 3.8GiB system guide, using parted, in contrast to sgdisk, the logical system sectors are modified to allow 3.8GiB of size.
Whilst this method is ideal for those planning to either flash GSI images which require specifically a larger system image, rather than making use of both product and system_ext partitions on PixelExperience and other ROMs, it is not ideal to mix them both up with each other.
(Both product and system_ext partitions offload large data from the system image, with such system apps like GApps)
So to break this down:
System is modified to adapt to 3.8GiB.
Logical starting and ending sectors system_a, system_b, pstore, aes_a, aes_b, align_parti and userdata partitions are modified.
PixelExperience script attempts to delete stock partition's userdata, but instead conflicts with 3.8GiB table.
Partition table becomes overlapped. (numerical partition numbers are not in order)
That is why it is important to keep track of which partition table your device is currently running, before making any further alterations to your system's table.
To check your current partition table, reboot into a custom recovery that supports the ADB interface via platform tools and:
Code:
adb shell
Code:
sgdisk --print /dev/block/sda
The output of this command should indicate what table you are currently running, depending on the sizes of both system_a and system_b partitions (2.5GiB on stock), or any added ones such as product and system_ext.
So double check that you are running the stock partition table before undergoing any of the guides mentioned above.
It is also worth noting that Pixel 2 XL (taimen) devices, do not revert to the stock partition table upon flashing the stock image.
This behaviour is not the same for Pixel 2 (walleye) devices, as when the stock image is flashed, the partition table is reverted to default.
(This is due to LG and HTC's bootloader behaving in different ways.)
Now, let's untie this knot!
Got the error now? Let's get started.
In short, we're going to undo the changes made, that includes both system_a and system_b partitions to the device, and redo it carefully.
Since sgdisk (installed on the device, by default) is unable to make any changes if it is found in an overlapping state, we will be using parted instead.
Download parted
Ensure you are in an ADB supported custom recovery.
Using platform-tools on an external device, push parted to the device:
Code:
adb push path/to/parted /sbin
Enter adb shell:
Code:
adb shell
Change permissions of parted:
Code:
chmod 777 /sbin/parted
Execute parted:
Code:
parted /dev/block/sda
Print current partition table:
Code:
p free
Remove overlapped partitions (when prompted, return ignore)
Code:
rm 17
rm 16
rm 15
rm 12
rm 11
rm 10
rm 9
rm 8
Recreate stock partitions
Code:
mkpart system_a ext4 169MB 2853MB
mkpart system_b ext4 2853MB 5538MB
mkpart pstore 5538MB 5546MB
mkpart aes_a 5546MB 5547MB
mkpart aes_b 5547MB 5548MB
mkpart align_parti 5548MB 5549MB
mkpart userdata ext4 5549MB 62400MB (for 64GB)
mkpart userdata ext4 5549MB 126300MB (for 128GB)
Wipe -> Format Data -> Yes
Wipe -> Factory Reset
Reboot -> Bootloader
That is what it takes to resort back to the stock partition table.
If done successfully (check via sgdisk --print /dev/block/sda), you can proceed to executing any repartition guide.

Reserved

Hello,
can someone please help me?
I tried to follow the guide to reset the partitions to default, but unfortunately it didn't work. Currently my partitions look like this:
{
"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"
}
What must i do now to reset the partitions correctly?
I think only ext2 on system_a is incrorrect. It must be ext4?
@PixelBoot you have a small typing error on 9. Recreate Stock Partions:
mkpart system_a ext4 169MB 2853MBmkpart system_b ext4 28533MB 5538MB
On system_b you have 28533MB insteat of 2853MB
Edit: I think i have corrected it now:
I have make these additional steps in fastboot:
fastboot format:ext4 system_a
fastboot format:ext4 system_b
fastboot format:ext4 userdata
Device is booting now with Factrory Image