[Q] Swap/Ext wan't work - XPERIA X8 Q&A, Help & Troubleshooting

Hi all,
after i resize my SD with MiniTool Partition Wizard and create a Linux Swap partition my swap on mobile wan't work. also when i want to create a ext4 for data2sd, it also wan't work -.-
don't have any idea..
Use GingerDX v21 + Alfs v06

safix8 said:
Hi all,
after i resize my SD with MiniTool Partition Wizard and create a Linux Swap partition my swap on mobile wan't work. also when i want to create a ext4 for data2sd, it also wan't work -.-
don't have any idea..
Use GingerDX v21 + Alfs v06
Click to expand...
Click to collapse
hi try this FAT32/EXT2/LINUX SWAP for now
testing only then if work upgrade to ext4
use minitools partition then download userinit.txt
go to this thread
xpraken said:
do this
1) download userinit.txt below to root of sdcard
2) boot into CWM recovery
3)mount /sdcard, /sd-ext (if you have ext partition) and /system
4) run: adb shell
5) move userinit.sh to /sd-ext ->
mv /sdcard/userinit.txt /sd-ext/userinit.sh
6) then,
chmod 755 /sd-ext/userinit.sh
7) reboot
this step will activate the swap without using app like swapper2
Click to expand...
Click to collapse

9) run sdparted: for the differents options see the original thread
This is for my configuration -> sdparted -es 1024M -ss 128M -efs ext3
also when i create partitions with minitool partition?

Swap using terminal emulator:
bash
cd /sdcard
dd if=/dev/zero of=[swap filename] bs=1024k count=[Size in MB]
# E.g. dd if=/dev/zero of=swapfile.swp bs=1024k count=32
# Creates a 32mb empty file called swapfile.swp on sdcard
mkswap [swap filename]
# Formats swap file
[wait at least 30 secs after doing this then]
swapon [swap filename]
# This enables the swap file (NOT swap using Partition)
# [swapoff [swap filename]] (Disable Swap. Be Patient while swap contents are emptied)
----
or if you were looking for partitions...
swapon [Linux swap partition] (/dev/****)

after i successfully parted my sd, moved the userinit tu sd-ext, the Recovery can mount sd-ext.
when i want to boot to rom, it will stuck on Alfs Kernel Boot logo.
i have create an fat32/ext2/swap partition

What do i wrong
{
"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"
}
​

i'm wondering about people who gets ext and swap work fine.
i work over an week to get swap and ext partition to work -.-

could be the sd card itself be the problem?

safix8 said:
could be the sd card itself be the problem?
Click to expand...
Click to collapse
Safix8 it'a not your fault..it's a problem of kernel..i and few people have this problem..the solution for me is remove the ext partition and for swap partition look here. so, swap work for me..

safix8 said:
9) run sdparted: for the differents options see the original thread
This is for my configuration -> sdparted -es 1024M -ss 128M -efs ext3
also when i create partitions with minitool partition?
Click to expand...
Click to collapse
men this how i work with ext2 and swap (linux swap)
use minitools to partition fat32/ext2/linuxswap
i download the userinit.txt and edit the swappiness to 200 bcoz my linux swap is 257mb
then
poweroff ur phone
boot to cwm or xrecovery
mount /sd-ext and /sdcard
first to know if ur phone is connected
type adb devices
if on the list the phone is connected
next
run adb shell
type this
mv /sdcard/userinit.txt /sd-ext/userinit.sh
and
chmod 755 /sd-ext/userinit.sh
at last reboot
to know the swap is working
goto terminal
type FREE
if swap is 0
is not working

xpraken said:
do this
1) download userinit.txt below to root of sdcard
2) boot into CWM recovery
3)mount /sdcard, /sd-ext (if you have ext partition) and /system
4) run: adb shell
5) move userinit.sh to /sd-ext ->
mv /sdcard/userinit.txt /sd-ext/userinit.sh
6) then,
chmod 755 /sd-ext/userinit.sh
7) reboot
this step will activate the swap without using app like swapper2
Click to expand...
Click to collapse
Sweet! Now I'm able to swap without swapper2. Thanks!

adb shell?where

hajiborojobo said:
adb shell?where
Click to expand...
Click to collapse
read this it may help
ADB

Manage swap over app
Try app resetSwap
"https://market.android.com/details?id=com.guille.resetSwap#?t=W251bGwsMSwxLDIxMiwiY29tLmd1aWxsZS5yZXNldFN3YXAiXQ.." for manage your swap (enable, disable, reset, info..)
it's cool , needn't restart

Related

moving apps to sd

it looks a bit different from G1
is this the correct "fstab" conf file to be modified ?
# cat /system/etc/vold.conf
## vold configuration file for Device
volume_sdcard {
## This is the direct uevent device path to the SD slot on the device
media_path /devices/platform/msm_sdcc.2/mmc_host/mmc1
emu_media_path /devices/platform/goldfish_mmc.0/mmc_host/mmc0
media_type mmc
mount_point /sdcard
ums_path /devices/platform/usb_mass_storage/lun0
}
unfortunately i can't find /system/init.rc
hope to inject a standard rom on this device soon !!!
At the moment we cannot get Apps working on the SD Card. Apps2SD won't work.
We are aware of this, and we understand that you'd like these features, but the hackers are currently busy working on exploits to install our own recovery for flashing baked ROMs.
init.rc is located on the top level of the root file system, under /init.rc . You need root to read the said file.
but ...
i'm used to linux and don't understand what we are missing in order to move apps to sd
since i'm root i should be able to do the extra mount of new partition, isn't it ?
actually, as far as understood, if android finds a new partition (either fat or ext) on the sd card it mounts it automagically
I have the same question, too.
Event we can't add extra mount in fstab. We could have the right to mount SD to /data/app, and just copying all apks to SD card, could we??
suoko,
I had done some tests today.
1. I format my sd card into ext3 format and copy all apks in /data/app into my sdcard.
2. mount my sd card on /data/app manually, and change the mode and owner of mounted folder and files.
You can install app into the sd card mounted on /data/app. But once you reboot them, (reset the /data/app), the market will be inconsistent with application list in settings. And I can't unmount the sd card after it mounted on /data/app.
So, I think it is still possible to use sd card for the app installation.
If you have any idea, please let me know... thanks
umount problem
by this "And I can't unmount the sd card after it mounted on /data/app." you mean you can't even access the sd vfat partition with your computer ?
i would only need vfat to be visible via pc not to screw installed apps
gonna try it too in a while
curiosity
as far you know, the install process of apks involves the "unzipping" of apks ?
or it's just a copy from the download apk folder to /data/app ?
what i would try is set a second app folder, this time in /sd/app
where /sd/app is an ext3 partition
so that we can leave main apps in internal memory and put extra apps in sd
the install process of apks is only to copy the app into /data/app folder. It is unzipped when the app is launched first time and cache them in another folder. So, we can found the dalvik-cache in the /data/ folder that the folder it unziped the dex files.
The test I had done is just mount the sd card on "/data/app" folder in android. So, if we want to add a second app folder, we need to change the app loader that I never did it before.
The unmount part means that I can mount the sd card on /data/app but I can't unmount that from /data/app, the message is "failed". The only way to unmount it is to reboot the tattoo. Once removing the sd card from tattoo, I can mount it to PC or tattoo again.
suoko
{
"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"
}
This picture is that I mount the sd card(500MB) on /data. The displaying size of flash (that's my sd card) in tattoo is 361MB, sorry for all chinese, you can find the number in the second line from bottom to up.
I don't know where to change the fstab record in tattoo. But it may be possible to write an app who runs at the machine startup and does the "mount" staff before other apps in /data/app executing.
I had one Hero with Apps2SD installed. It mounts the sd card on /system/sd and /data/dalvik-cache. The apps are installed and launched at /system/sd/app. I think it is the same way like mime.
2 install folders in linux ???
you know what ? i guess in linux is not that easy to set up a second install folder.
I think we could sim link a /data/app/app folder to /sd/app but then the install process should do something:
check /data/app folder space left, and in case it's full, install to /data/app/app
Yes, right. That's the way I use. But I mount the sd card directly on /system. This makes android to calculate the left space of my sd card.
Currently, I need to modify the /init.rc to make it mount at the boot. But the /init.rc seems in the ramdisk image, so I can't modify it and store it back. I don't know where the ramdisk image is, it seems in one of partition 0, 1, 2. Any idea??
hello people
have you test this?
http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/
ok, trying now
formatted my 4gb sd to:
vfat: 3.4 GB
ext2: 508 MB
swap: 32 MB
i found partitions at:
mount -t ext2 /dev/block/mmcblk0p2 /data/myapp
swapon /dev/block/mmcblk0p3
must work on vold.conf now since ext2 on sd is not automatically mounted at /system/sd
another way ...
is create an ext2 img file to be mounted at boot using a loopback device.
no sd partitioning is needed then and the FULL-OF-APPS IMG FILE could be easily moved from one SD to another (aka to another android compatible phone).
modify /system/init.rc to mount an ext2 image on bootup.
http://forum.xda-developers.com/showpost.php?p=3402719&postcount=683
extra ext2 partition creation [750MB] (on ubuntu):
dd if=/dev/zero of=sd.img seek=749999999 bs=1 count=1
mke2fs -F sd.img
mounting it (on android):
[mkdir /data/myapp]
mount -o loop sd.img /data/myapp
current state:
mount: mounting /dev/block/loop0 on /data/myapp failed: Invalid argument
the ext2 loop partition was an end 2008 discussion
http://forum.xda-developers.com/showthread.php?t=463488&page=2
what i think now is extending the /data/app partition with the looped img file.
can we (without lvm) ?
I prefer the second install option
if android detects an extra ext2 partition or an ext2 img file, you can change the default install location in android preferences
Suoko, do your tattoo have /system/init.rc file??
In /init.rc, it doesn't import /system/init.rc. So, we can't use /system/init.rc to mount it.
currently, I need to compile my owned boot.img file. But the compiled file doesn't work. I don't know why. I following the following url to do so: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images.
Any idea??
BTW, why do we need to mount /dev/loop0?? I just use mount -t ext3 /dev/block/mmcblk0p2 /data/app to do so.
why loop?
Cause you don't have to partition the sd this way.
You just create an img file which can be used as a partition.
Think this:
You have a 4 gb sd and want to change it to store more music/vids/maps with a 16 gb one
You take the file and move it from the old sd to the new one.
You want to increase the img file size?
You create a new larger file?
You create it and move old img file contents to it.
We can probably extends its size some way
ok I see. That's a good idea for expanding purpose.
BTW, I had solved the boot.img problems. It is caused by the wrong version I checked out from repo. I use the correct version to build mkbootimg and everything works.
current state:
trying to mount the /dev/block/mmcblk0p2 on /data at the boot time. but all trials failed.
succesfully mounted looped device
extra ext2 partition creation [350MB] (on ubuntu):
# dd if=/dev/zero of=sd.img seek=349999999 bs=1 count=1
# mke2fs -F sd.img
pushing ext2 partition to android [350MB] (on ubuntu):
# adb push ./sd.img /sdcard/sd.img
mounting it (on android) (DO NOT RUN BUSYBOX !!!):
# su
# export LD_LIBRARY_PATH=/system/lib
# export PATH=/system/bin
# insmod /data/local/bin/tattoo-hack.ko
# mount -o rw,remount /dev/block/mtdblock5 /data
# mount -o rw,remount /dev/block/mtdblock3 /system
# mkdir /data/myapp
# mount -o loop -t ext2 /sdcard/sd.img /data/myapp/
[now run busybox]
# /data/local/bin/sh
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 93.0M 0 93.0M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 150.0M 135.7M 14.3M 90% /system
/dev/block/mtdblock5 165.1M 148.1M 17.0M 90% /data
/dev/block/mtdblock4 150.0M 3.7M 146.3M 2% /cache
/dev/block//vold/179:1 3.7G 3.5G 223.5M 94% /sdcard
/dev/block/loop0 323.2M 2.0M 304.5M 1% /data/myapp
re: boot.img problems
huchengtw said:
ok I see. That's a good idea for expanding purpose.
BTW, I had solved the boot.img problems. It is caused by the wrong version I checked out from repo. I use the correct version to build mkbootimg and everything works.
current state:
trying to mount the /dev/block/mmcblk0p2 on /data at the boot time. but all trials failed.
Click to expand...
Click to collapse
are you reading mainfram3 tips ?
http://forum.xda-developers.com/showthread.php?t=641731
i'm gonna look at android install process and SD settings

Partition usage

I've tried creating a partition to use it with Link2SD, but it doesn't seem to be working.
I would love if someone could provide a step-by-step tutorial on how to get the following to work on my S5830I:
*Increase internal storage by using the SD card
*Use the swap reserved space
I've used CWM to create a partition, but Link2SD apparently isn't mounting it correctly. I've tried ext2/ext3/ext4 mount scripts, none work.
Thanks a lot
S5830i swap settings
Try this:
I used ClockwordMod 5.0.2.6 for s5830i and [TeamCooper] Retribution beta 3.5 rom and Terminal Emulator from market
1, Format sd card in clockworkmod recovery:
Advanced/Partition SD card
ext 1024 MB
swap 128 MB
Reboot system
2, Install Terminal Emulator and Run for activate swapping
type su
type fdisk -l dev/block/mmcblk0
You should see this and more lines
/dev/block/mmcblk0p3 1861 1924 514080 82 Linux swap
the red number ( partition number ) will be needed later
type swapon /dev/block/mmcblk0pX
the red is x our partition number
Check with the drive that appeared to
type free
You should see similar:
# free
total used free shared buffers
Mem: 385772 376352 9420 0 26420
-/+ buffers: 349932 35840
Swap: 514076 0 514076
3, Create automatic run for swapping with Root Explorer
Go to /system/etc/init.d folder and set r/w mode ( tap the system r/w button at the top )
Create 05userinit file in this folder
Edit it with text editor ( long tap on the filename and select open in text editor line )
type this
[The first version of 05userinit isn't working, this is the correct code]
#!/system/bin/sh
#Activate swap at boot
swapon /dev/block/mmcblk0pX
echo 60 > /proc/sys/vm/swappiness
the red is x our partition number
Save file and set this permissions ( long tap and Permissions line )
OWNER [x] [x] [x]
GROUP [x] [ ] [x]
OTHERS [ ] [ ] [ ]
Go to /system/etc folder and set r/w mode ( tap the system r/w button at the top )
Create fstab file in this folder
type this
/dev/block/mmcblk0pX swap swap
the red is x our partition number
Save file and set this permissions ( long tap and Permissions line )
OWNER [x] [x] [x]
GROUP [x] [ ] [x]
OTHERS [ ] [ ] [ ]
[Thanks marcedli for the original post]
GermainZ said:
I've tried creating a partition to use it with Link2SD, but it doesn't seem to be working.
I would love if someone could provide a step-by-step tutorial on how to get the following to work on my S5830I:
*Increase internal storage by using the SD card
*Use the swap reserved space
I've used CWM to create a partition, but Link2SD apparently isn't mounting it correctly. I've tried ext2/ext3/ext4 mount scripts, none work.
Thanks a lot
Click to expand...
Click to collapse
I hope this helps. http://www.youtube.com/watch?v=EyQeiT0smwY&list=PLB7A7385718D23F15&index=25&feature=plpp_video
To Make Ext2 Partition for link2sd, using Mini Tool Partitioning Tool in Windows, please checkout this link: http://www.youtube.com/watch?v=1aAUPfowABc&list=PLB7A7385718D23F15&index=16&feature=plpp_video
I actually was doing everything correctly except for the swap activation. It's just that using this method, the internal storage isn't shown as increased in the settings.
GermainZ said:
I actually was doing everything correctly except for the swap activation. It's just that using this method, the internal storage isn't shown as increased in the settings.
Click to expand...
Click to collapse
This method doesn't increase the internal storage. It's give faster and smoother working.
letso82 said:
This method doesn't increase the internal storage. It's give faster and smoother working.
Click to expand...
Click to collapse
I realize that, but I supposed that the phone would think it has more internal memory, showing 1gb in internal memory. That's what I was checking and that's why I thought it wasn't working.
Anyway, this thread can be closed.
hallo plz help
i want swap my ace
terminal type:
swapon /dev/block/mmcblk0p3
swapon not found
What could be the problem?
{
"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"
}
janaman said:
hallo plz help
i want swap my ace
terminal type:
swapon /dev/block/mmcblk0p3
swapon not found
What could be the problem?
Click to expand...
Click to collapse
Have you created a swap partition first of all?
yes CWM create ext partition and swap ...
janaman said:
yes CWM create ext partition and swap ...
Click to expand...
Click to collapse
Are you using the stock kernel?
Sent from my GT-S5830i using xda app-developers app
Razodroid rom Rafael kernel

How to unmount partitions on internal sd card

Hi, I need incease partitions of Userdata. I found some tutorials and for me it looks fine this: http://forum.xda-developers.com/showthread.php?t=2710480.
Unfortunatelly I can't go over step about remove partitions because according to log are being used. I tried a lot of possibility with parted and fdisk but somehere I do mistakes. Can me help with this. See attachment with my steps. Thanks.
{
"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"
}
I found solution after many experiments. The biggest problem it was unmount partitions and then these partitions remove. These things were possible do in OMNI ROM 4.4.4 over ADB. I found this solution here: http://forum.xda-developers.com/showthread.php?t=2712253&page=11
My steps:
0 - You download scripts fs-utils from here - http://forum.xda-developers.com/showthread.php?t=2712253 and copy to MicroSDCard
1 - Install OMNIROM 4.4.4
2 - I was fighting with connection of ADB. I can't run ADB Sideload because I can't connect. I was only freely in recovery menu. I used following commands:
adb shell (this command connect command line to phone and in prompt I had something this ~ # 6 --> don't worry ... try to command ls and if will be listed folder from mobile so thats OK)
adb kill-server
adb start-server
adb devices
You have to try so long until will not correct adb shell .
3 - Now I had the biggest problem. At any cost you have to run unmount(command UMOUNT) and remove(command RM) partitions.
umount /sdcard
umount /data
parted /dev/block/mmcblk0
rm 14
rm 15
mkpartfs logical ext2 1621 5865
name 14 Userdata
mkpartfs logical ext2 5865 7818
name 15 SDCard
quit
These commands must be done. If not something is wrong and you have to fix it some way.
Then it's easy. Run following commands
cd /ext_card/fs-utils
tune2fs -j /dev/block/mmcblk0p14
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p14
e2fsck -fpDC0 /dev/block/mmcblk0p14
tune2fs -j /dev/block/mmcblk0p15
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p15
e2fsck -fpDC0 /dev/block/mmcblk0p15
chown -R 2800:2800 /sdcard
After all steps I didn't have mounted internal SDCard. This is very small problem. In new recovery I formated as vfat and then I formated as ext4 and after restart it was mounted. Resize internal sdcard for apps DONE.

Windows ARM64 on enchilada

{
"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"
}
oneplus 6/6t 都可用
警告!不当操作可能会导致手机变砖!
-
20210822 updata
-
project address : https://github.com/edk2-porting
and
Tool download :https://drive.google.com/drive/folders/1GrX9JTVpKwo3WNshqIljPRc9Q6dPJDJJ?usp=sharing
boot download : https://github.com/edk2-porting/edk2-sdm845/releases
drives download : https://github.com/edk2-porting/WOA-Drivers/archive/refs/heads/main.zip
-
Installation tutorial
new tutorial!(English) https://forum.renegade-project.org/t/faq/95
-
article(Chinese) : https://forum.renegade-project.org/t/6-windows/194
-
Device support status
Device support status
Renegade Project
Renegade Project
renegade-project.org
-
The drive is gradually improving
有问题我会不定期来看的,欢迎提问。
Questions are welcome
What an amazing project . Thx again...
tp
is working phone? contact? camara? gps? etc
rom2525 said:
is working phone? contact? camara? gps? etc
Click to expand...
Click to collapse
These are currently not working
Nice to see. Thanks for your work
Is there any way to do this without the dongle?
stevegsames said:
Is there any way to do this without the dongle?
Click to expand...
Click to collapse
I don't quite understand what "dongle" means?
hehedi233 said:
I don't quite understand what "dongle" means?
Click to expand...
Click to collapse
I'm referring to the USB hub
stevegsames said:
I'm referring to the USB hub
Click to expand...
Click to collapse
If you don’t have a USB HUB, you cannot install the operating system because it requires a mouse and keyboard to operate
hehedi233 said:
If you don’t have a USB HU
hehedi233 said:
If you don’t have a USB HUB, you cannot install the operating system because it requires a mouse and keyboard to operate
View attachment 5365067
Click to expand...
Click to collapse
Is there any way to embed the touchscreen drivers and use the on screen keyboard?
Click to expand...
Click to collapse
These do not work in WINPE. After installing the system and driver, you can use touchscreen
But I don’t recommend installing it on the phone in daily use
hehedi233 said:
View attachment 5357205
oneplus 6/6t 都可用
警告!不当操作可能会导致手机变砖!
-
20210822 updata
-
project address : https://github.com/edk2-porting
and
Tool download :https://drive.google.com/drive/folders/1GrX9JTVpKwo3WNshqIljPRc9Q6dPJDJJ?usp=sharing
boot download : https://github.com/edk2-porting/edk2-sdm845/releases
drives download : https://github.com/edk2-porting/WOA-Drivers/archive/refs/heads/main.zip
-
Installation tutorial
new tutorial!(English) https://forum.renegade-project.org/t/faq/95
-
article(Chinese) : https://forum.renegade-project.org/t/6-windows/194
-
Device support status
Device support status
Renegade Project
Renegade Project
renegade-project.org
-
The drive is gradually improving
有问题我会不定期来看的,欢迎提问。
Questions are welcome
View attachment 5357197View attachment 5357199View attachment 5357201View attachment 5363283
Click to expand...
Click to collapse
I'm having some issues with your parted file in this method my computer system says it's bad it can't it can read it but it won't open it
English video tutorials are for 6T. Can I use the same commands for 6 too?
Can we get line to line English instructions? Links for the instructions in the video are all dead.
ddaggebi said:
English video tutorials are for 6T. Can I use the same commands for 6 too?
Can we get line to line English instructions? Links for the instructions in the video are all dead.
Click to expand...
Click to collapse
Hi!
Yes the same commands can be used on Oneplus 6.
Take a look here under "EFI/NTFS WIndows installation instructions".
Hope that helps you.
- Boot Phone to TWRP/recovery
- adb push parted /sdcard/
adb shell
cp /sdcard/parted /sbin/ && chmod 755 /sbin/parted
umount /data && umount /sdcard
parted /dev/block/sda
rm 17
mkpart esp fat32 6559MB 7000MB
mkpart pe fat32 7000MB 10000MB
mkpart win ntfs 10000MB 70GB
mkpart userdata ext4 70GB 125GB
set 17 esp on
quit
- in TWRP. Reboot bootloader
- Fastboot boot TWRP.img
adb shell
mkfs.fat -F32 -s1 /dev/block/sda17
mkfs.fat -F32 -s1 /dev/block/sda18
mkfs.ntfs -f /dev/block/sda19
mke2fs -t ext4 /dev/block/sda20
mount /dev/block/by-name/pe /mnt
- open Powershell on path Windows 11/Tools/WinPE folder
adb push boot /mnt
adb push efi /mnt
adb push sources /mnt
adb push bootmgr.efi /mnt
- in Recovery. File Manager check if the copied files/folders are shown in mnt folder
- in Recovery. Reboot Bootloader
- Fastboot boot Windows 11\Boot\boot-fajita.img
- Copy to USB Stick (Format to NTFS)
- Windows 11\commands.txt
- Windows 11\Windows 11 ISO\Windows ISO file
- Windows 11\Drivers\WOA-Drivers-Main
- Windows 11\Tools\Dism++
- Windows 11\Tools\TouchScreen.reg
Partition Disks in Windows 11
-----------------------------
diskpart
select disk 0
list part
select part 17
assign letter=Y
exit
Windows 11\Tools\dism++\dism++_arm64.exe
Apply Image - select Windows11.iso file from USB Stick
Install Windows on Partiton C:\
Check "add Boot"
OK
Wait until done....
Drivers - add - select WOA-Drivers from USB Stick
bcdedit /store Y:\efi\microsoft\boot\bcd /set (DEFAULT) testsigning on
bcdedit /store Y:\efi\microsoft\boot\bcd /set (DEFAULT) nointegritychecks on
Aulgreg38 said:
I'm having some issues with your parted file in this method my computer system says it's bad it can't it can read it but it won't open it
Click to expand...
Click to collapse
Hmmm......I had no issues using parted. You run that on your phone not on your Computer.
Yeah I was messing up it was me please don't laugh I was misspelling thing
Once I get a USB keyboard I'll be able to finish kinda still waiting to get one
Wishmasterflo said:
Hi!
Yes the same commands can be used on Oneplus 6.
Take a look here under "EFI/NTFS WIndows installation instructions".
Hope that helps you.
- Boot Phone to TWRP/recovery
- adb push parted /sdcard/
adb shell
cp /sdcard/parted /sbin/ && chmod 755 /sbin/parted
umount /data && umount /sdcard
parted /dev/block/sda
rm 17
mkpart esp fat32 6559MB 7000MB
mkpart pe fat32 7000MB 10000MB
mkpart win ntfs 10000MB 70GB
mkpart userdata ext4 70GB 125GB
set 17 esp on
quit
- in TWRP. Reboot bootloader
- Fastboot boot TWRP.img
adb shell
mkfs.fat -F32 -s1 /dev/block/sda17
mkfs.fat -F32 -s1 /dev/block/sda18
mkfs.ntfs -f /dev/block/sda19
mke2fs -t ext4 /dev/block/sda20
mount /dev/block/by-name/pe /mnt
- open Powershell on path Windows 11/Tools/WinPE folder
adb push boot /mnt
adb push efi /mnt
adb push sources /mnt
adb push bootmgr.efi /mnt
- in Recovery. File Manager check if the copied files/folders are shown in mnt folder
- in Recovery. Reboot Bootloader
- Fastboot boot Windows 11\Boot\boot-fajita.img
- Copy to USB Stick (Format to NTFS)
- Windows 11\commands.txt
- Windows 11\Windows 11 ISO\Windows ISO file
- Windows 11\Drivers\WOA-Drivers-Main
- Windows 11\Tools\Dism++
- Windows 11\Tools\TouchScreen.reg
Partition Disks in Windows 11
-----------------------------
diskpart
select disk 0
list part
select part 17
assign letter=Y
exit
Windows 11\Tools\dism++\dism++_arm64.exe
Apply Image - select Windows11.iso file from USB Stick
Install Windows on Partiton C:\
Check "add Boot"
OK
Wait until done....
Drivers - add - select WOA-Drivers from USB Stick
bcdedit /store Y:\efi\microsoft\boot\bcd /set (DEFAULT) testsigning on
bcdedit /store Y:\efi\microsoft\boot\bcd /set (DEFAULT) nointegrityche
[/QUOTE]
Click to expand...
Click to collapse
Thanks sir. I see you active lots of times on OP6/6T forums. Thanks for your contribution and helping people out!

Dual boot for P-Smart

Code:
disclaimer
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
*/
Hello
This Guide to make Dual-Boot for P-Smart that keep Stock rom untouched and install any GSIs. It allows two Android os installed at the same time and switch between them using SHRP Recovery for dual boot.
This method tested and worked on Fig-la1
Spoiler: General information
This done by creating a new system partition using Parted (shrink userdata partition and creat the new system partition)
To Boot from the new system partition: change the name of the new system partition to "system" and the name of old system partition to any name e.g. "system-b"
To Boot from the old system partition: change the name of the old system partition to "system" and the name of new system partition to any name e.g. "system-b"
Dual boot for P20 lite - demonstration video (I am using SHRP RECOVERY (like TWRP) with tweaks to change boot partition easily, instead of writing terminal commands. This a video shows the dual boot process)
Requirements​
TWRP/SHRP
Parted (attached arm and arm64, unzip the file)
Latest fastboot and ADB commands installed
Backup all your data because you will make a factory reset and format data partition
Steps:​
Boot to TWRP/SHRP
Run the following commands
Code:
adb push /path/to/parted /sbin/parted
adb shell
chmod 777 /sbin/parted
parted /dev/block/mmcblk0
p free
note: parted /dev/block/xxxxx according do your device
3- it will show the list of partition "save this you may use it later". remember the number of old system partition which is in my case "52"
{
"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"
}
4- remove "userdata" partition which in my case number 59 using the following command
Code:
rm 59
5- create the new system partition (partition number 59 in my case ) using the following command
Code:
mkpart name fs_type start end
name: name of new partition e.g "system-b"
fs_type: file system type e.g "ex4"
start: the end value in MB of the previous partition, in my case "7153MB"
end: equal to start + size where size will be the size of the target partition. in my case in need 4GB partition so end=7153MB + 4GB =11153MB
In my case I'll type:
Code:
mkpart system-b ext4 7153MB 11153MB
set 59 msftdata on
name 59 system-b
6- create the "userdata" partition (partition number 60 in my case, start= 11153MB )
In my case I'll type:
Code:
mkpart userdata ext4 11153MB 31.3GB
set 60 msftdata on
name 60 userdata
7- get the new partition list
Code:
p free
8- exit
Code:
quit
9- format userdata and the new system partition using "mkfs.type /dev/block/mmcblk0pxx" (in my case partition number 59 and 60). you may need to reboot to stock recovery to make factory reset
Code:
adb push /path/to/mkfs.ext4 /sbin/mkfs.ext4
adb shell
chmod 777 /sbin/mkfs.ext4
mkfs.ext4 /dev/block/mmcblk0p59
mkfs.f2fs /dev/block/mmcblk0p60
10- You can now switch between two systems using either of these two methods
Spoiler: Using SHRP Recovery
SHRP is a beautiful TWRP-based recovery with modern UI, custom layout, useful functions, and more.
In this method you must have "System" and "System-b" partitions, other names not accepted
1- Download SHRP Recovery for DUAL Boot from here
2- Flash it on recovery_ramdisk or erecovery_ramdisk
3- from the main screen choose tweaks
A- Active new system partition and new data profile
(Important Note: Now "System partition" is the new created partition and "System-b partition" is the default system partition)
B- Active default system partition and default data profile
(Important Note: Now "System partition" is the default system partition and "System-b partition" is the new created partition)
Reboot before make any change
Spoiler: manually
A- To Boot from your new system partition > boot to twrp and run the following command
Code:
adb push /path/to/parted /sbin/parted
adb shell
chmod 777 /sbin/parted
parted /dev/block/mmcblk0
name 52 system-b
name 59 system
or from TWRP terminal write the following
Code:
parted -s /dev/block/mmcblk0 name 52 system-b
parted -s /dev/block/mmcblk0 name 59 system
change the number 52 and 59 according to your partition list (in my case 59: new system partion, 52 old system partition ). Then reboot TWRP and flash your new android os
B- To Boot from your old system partition > boot to twrp and run the following command
Code:
adb push /path/to/parted /sbin/parted
adb shell
chmod 777 /sbin/parted
parted /dev/block/mmcblk0
name 59 system-b
name 52 system
or from TWRP terminal write the following
Code:
parted -s /dev/block/mmcblk0 name 59 system-b
parted -s /dev/block/mmcblk0 name 52 system
change the number 52 and 59 according to your partition list (in my case 59: new system partion, 52 old system partition ). Then reboot
-------------------------------------------------------
@Abdelhay.ali hey bro, can i use shrp recovery to root FIG-LA1?
and which system (rom) will be used as second system?

Categories

Resources