Develop Bugs

Trouble mounting sd card on Linux

I can't mount my EVO (CM 6.1) on a new Linux installation (Debian testing). I have searched the forums and Googled quite a bit, but none of the suggestions seem to pertain to me.
I'm aware I have to select mount on the phone first. (I've mounted it on other Linux systems many times before.)
It's not the SD card; it shows up fine in a Windows VM.
It's not the cable; I've tried two different cables.
I can mount regular USB drives just fine on this system.
Toggling debug mode yields the same result.
The device shows up, but udev never creates the device for the partition:
Code:
% dmesg| tail -14
[238025.284187] usb 2-1.1: new high speed USB device using ehci_hcd and address 16
[238025.387890] usb 2-1.1: New USB device found, idVendor=0bb4, idProduct=0ff9
[238025.387895] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[238025.387900] usb 2-1.1: Product: Android Phone
[238025.387902] usb 2-1.1: Manufacturer: HTC
[238025.387905] usb 2-1.1: SerialNumber: HT06WHL08214
[238025.388060] usb 2-1.1: configuration #1 chosen from 1 choice
[238025.390940] scsi22 : SCSI emulation for USB Mass Storage devices
[238025.391150] usb-storage: device found at 16
[238025.391154] usb-storage: waiting for device to settle before scanning
[238030.378804] usb-storage: device scan complete
[238030.380428] scsi 22:0:0:0: Direct-Access HTC Supersonic 0100 PQ: 0 ANSI: 2
[238030.381361] sd 22:0:0:0: Attached scsi generic sg2 type 0
[238030.391320] sd 22:0:0:0: [sdb] Attached SCSI removable disk
Code:
% ls /dev/sd*
/dev/sda /dev/sda1 /dev/sda2 /dev/sda5 /dev/sdb
Code:
% sudo fdisk -l /dev/sdb
Disk /dev/sdb: 7944 MB, 7944011776 bytes
245 heads, 62 sectors/track, 1021 cylinders
Units = cylinders of 15190 * 512 = 7777280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
Any Linux people out there have any ideas?

That is odd. It appears your linux is misreading the geometry of the memory card. I also have an 8GB SDCard and my fdisk listing from my Mac (UNIX) reads as follows (Note, Darwin's fdisk defaults to "List" if no option is specified)
Code:
$ sudo fdisk /dev/rdisk1
Disk: /dev/rdisk1 geometry: 966/255/63 [15523840 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 0C 4 0 1 - 868 254 63 [ 64260 - 13896225] Win95 FAT32L
2: 83 869 0 1 - 962 101 45 [ 13960485 - 1500453] Linux files*
3: 82 962 101 46 - 966 80 10 [ 15460938 - 62902] Linux swap
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Mine is showing 255 heads, 63 sectors and 966 cylinders for a total of 15523840 512 Byte sectors. You're system seems to be reading (or enforcing) inaccurate data making it impossible to read the partition table.
EDIT: Your phone seems to have an odd product ID (0x0ff9). I can't seem to find a mode that uses that PID. Mine shows PID 0x0c8d when in Disk Mode.

size partition for BoardConfig.mk

Hi
this is from the BoardConfig.mk
Code:
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072
I want to find the actual size partition adb shell cat /proc/mtd" or "adb shell cat /proc/emmc" or "adb shell cat /proc/dumchar_info" doesn't work !

Steps:
*root your device;
*install TWRP or CWM for your device ;
*install busybox tools ( Busybox Free Goolge Play);
After this, enter to recovery mode. Mount /system into TWRP or CWM.
Plug USB cabe, and in your computer input these commands:
adb devices --> verify if device is connected
Now, install parted into /system/bin:
adb push <path-to-file>/parted /system/bin
Now, insert this command:
parted /dev/block/mmcblk0 unit B print
The output is similar :
Code:
~ # parted /dev/block/mmcblk0 unit B print
Model: MMC 008GE0 (sd/mmc)
Disk /dev/block/mmcblk0: 7818182656B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194304B 6291455B 2097152B MRD
2 6291456B 8388607B 2097152B MRD_BK
3 8388608B 10485759B 2097152B MEP2
4 10485760B 31457279B 20971520B ext4 EFS
5 31457280B 46137343B 14680064B Reserved
6 46661632B 48234495B 1572864B LOKE_2ND
7 48758784B 50331647B 1572864B LOKE_1ST
8 50331648B 67108863B 16777216B PARAM
9 67108864B 83886079B 16777216B RECOVERY
10 83886080B 100663295B 16777216B KERNEL
11 100663296B 125829119B 25165824B MODEM
12 125829120B 142606335B 16777216B ext4 NVM
13 142606336B 352321535B 209715200B ext4 HIDDEN
14 352321536B 713031679B 360710144B ext4 CACHE
15 713031680B 2307915775B 1594884096B ext4 SYSTEM
16 2307915776B 7817134079B 5509218304B ext4 USER
Use the column size to fill in the BoardConfig values.
The first column it refers to the mount point.
Ex.: the kernel partition has 16.777.216 bytes mounted in /dev/block/mmcblk0p10
Links references:
http://forum.xda-developers.com/showthread.php?t=2450045
http://stackoverflow.com/questions/...ormation-for-android-device/15639867#15639867
http://forum.xda-developers.com/attachment.php?attachmentid=2397268&d=1384688569

naufragoweb said:
Now, install parted into /system/bin:
adb push <path-to-file>/parted /system/bin
Click to expand...
Click to collapse
Path to.. what file?

Nicofisi said:
Path to.. what file?
Click to expand...
Click to collapse
Path to the "parted" file in your PC

Guide[Linux][Windows]: Migrate to SSD/HDD of any size, only for SATV Pro

Code:
[B][I][COLOR="Red"][SIZE="3"]I am not responsible for bricked devices, dead HDDs, animals
activist campaigns, or any H/W damage caused by you following these
directions. YOU are choosing to make these modificiations, and
you, yourself take responsibility for doing these modifications
to your device.
You can do serious H/W damage to your SATV or even your computer
by doing any of this. So, you have been warned! [/SIZE][/COLOR][/I][/B]
First of all, you should pay your thanks to @Luxferro for mapping out the entire partition array, and building the chart that does all the calculations for using another disk size.
He also proved that it was indeed possible to modify your GPT header to another sized drive.
None of this would have been possible, if it was not for him.
Also thanks to @Tilator for initiating his thread, and proving it was possible to swap your HDD for something else.
1. Preparations and disassembling the SATV
Well, to begin with you should have a working linux environment set up. This can easily be a live CD/DVD/USB. Or you can do it from a virtual environment. You can use DD for Windows now, follow guide as normally.
You should have a hex editor with CRC32 calculating capabilities. I recommend HxD:
https://mh-nexus.de/en/downloads.php?product=HxD
Yes, that is for Windows, I use Linux for all the writing/dumping, but I prefer my Windows hex editor.
It's worth to know, that your device should be bootloader unlocked, and preferably newly factory reset.
Also, an autotool has been made now to do this GPT header edit. See post #3.
Then you can go open up the SATV by prying off the bottom of the casing. I managed to do this with my fingernails. A small plastic pry tool can be used as well.
{
"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"
}
Then you remove the 2 wire sets from the plugs to give more working room. There is 2 sets of tape holding the wires and the HDD in place as well.
There is (on mine at least) just one screw with a small bracket holding the HDD in place, you will need a T6 driver to remove it.
Gently lift the black latch/lock on the connector to the secondary board, then the FCC connector will be easily out.
Then it is just a matter of gently loosening the adhesive on the FCC strip from the HDD and pull out the SATA connector.
With the HDD out, you will have to connect it to your Linux setup somehow. I used an enclosure with a USB3 connection.
With the HDD recognized in the computer, the time has now come to clone you HDD.
You could as well use the bin files Tilator has provided, but if you want your own genuine Netflix ESN, you should use your own.
If you want to use DD for Windows, please continue the guide from post #2. After finishing that part, come back to this post and skip to the hex editing part.
2. Dumping the data from the SATV SSHD
In a terminal window you start by listing the drives:
Code:
sudo -s
fdisk -l
This is to determine which drive you are working with. Remember that the DD command does't care which drive you specify, it will destroy your main drive if you ask it to.
The you continue by dumping the first 6899870 blocks of data to a bin file:
Code:
dd if=/dev/sd[B]X[/B] of=firstpart.bin count=6899870
This will give you a raw image file of all the partitions up until the /data partition which is better left out (it will come later).
Then continue by dumping the last 5120 bytes of data which contains the partition array and the GPT header:
Code:
dd if=/dev/sd[B]X[/B] bs=512 skip=976773158 of=lastpart.bin
EDIT: 26th August 2016, @anchung.chen has experimented with aligning the partitions to Advanced Format 4096 byte sectors (4K alignment). This supposedly gives better performance especially on SSD drives.
It's worth to know that this most likely breaks the OTA updates, as they might write partitions on block level rather than on a file level. OTA updates seems to be working.
Also, anchung.chen has had problems unlocking the bootloader on the 4K aligned disk.
@ahmed68
Reports that TWRP doesn't work well when trying to flash SuperSU.
Please see follow these steps to write the bin files with 4K alignment:
Start by downloading the ELF executable programmed by anchung.chen from this post:
http://forum.xda-developers.com/showpost.php?p=68300570&postcount=44
Patch the lastpart.bin the following way (2TB disk size):
Code:
./shield_pro_new_disk_gpt_calculator-0.3 lastpart.bin [B]2000398934016[/B] lastpart4k.bin
This will recalculate the GPT header to match the 2TB disk, but also rewrite the partition array.
Then continue by writing the firstpart.bin in 2 steps instead of just one:
Code:
if=firstpart.bin of=/dev/sd[B]X[/B] bs=512 count=69888
Code:
dd if=firstpart.bin of=/dev/sd[B]X[/B] bs=512 skip=69790 seek=69888 count=6830080
These 3 steps effectively moves the partitions 16-32 to match 4K alignment structure.
And finish off by writing the lastpart4k.bin:
Code:
dd if=lastpart4k.bin of=/dev/sda[B]X[/B] bs=512 seek=[B]3907029158[/B]
This completes the guide, no more steps needed.
You can now disconnect your HDD. These 2 files also counts as a backup of your SATV (not with settings as userdata was not copied).
Now connect your new SSD in the enclosure.
You can easily start by writing the firstpart.bin:
Code:
dd if=firstpart.bin of=/dev/sd[B]X[/B]
3. Hex-editing the partition array and the GPT header
In your linux terminal load up the block count (called sectors in linux language) of the new drive:
Code:
fdisk -l
A 2 TB disk should have a total block count of 3907029168, but a smaller disk would have a smaller block count, so use fdisk -l to determine this.
Or if you use DD for Windows you have the output from dd --list to work with.
The lastpart.bin must be edited before we can write it on the new disk.
So use the spreadsheet provided by @Luxferro in this post:
http://forum.xda-developers.com/showpost.php?p=67996717&postcount=189
In the column at the buttom right that says disk size, you change the value to match you new disk. In this example for the 2TB it should be 2000398934016 (bytes). This value should be taken from fdisk -l as well.
Now it gets a little hairy!
In the spreadsheet you should start with the buttom value marked out in purple under the row called "Last LBA". This should be E8E0888E:
Open up lastpart.bin in HxD and navigate to offset 00000FA8. There you should find the 4 bytes 0E 60 38 3A illustrated in this picture:
This value is in a format called reverse byte ordering, so to put in your new calculated value, you will have to arrange it like this: 8E 88 E0 E8. Input that value instead of the bytes already there like this picture:
While we are in this particular position in the lastpart.bin we might as well do the CRC32 of the partition array.
Now make a selection containing the 64 bytes or 4 empty lines underneath the line having UDA written in ASCII, and all the way to the top of the file, offset 00000000 to 00000FF0 like in this picture:
In the drop-down menu, choose Analyzis->Checksums and generate a CRC-32 checksum (Not checksum-32).
It will come up in the buttom screen of HxD, and should read 6B CF E5 7D
Navigate to the buttom of the file which contains the GPT header. It should start with an ANSI text reading "EFI PART".
In offset 00001258 you should find the value of the original CRC-32 value containing the bytes 0E 02 C5 DC.
Replace this, again reversing the bytes from your newly calculated CRC-32 value like this: 7D E5 CF 6B:
Now we are actually almost finished! In the spreadsheet all the way to the right, you will find 4 hexadecimal values marked in purple.
First is the position of the GPT header, and the second is the position of the backup GPT header. Since there is only 1 on the SATV, these values are both the same.
Write them into the GPT header on offset 00001218, and 00001220, again reversing the bytes like illustrated in the picture:
Same goes for offset 00001230, Last Usable LBA, and offset 00001248, Starting LBA of array of partition entries.
This brings us to the last thing on the table, the CRC32 of the GPT header itself.
The CRC is located on offset 00001210 and should have the bytes 46 C9 88 78 already there.
Just write 00 00 00 00 to blank them out:
Now make a selection of the GPT header containing the beginning of the header, and to the last written byte before all the zeroes:
In the drop-down menu, choose Analyzis->Checksums and generate a CRC-32 checksum (Not checksum-32).
It will come up in the buttom screen of HxD, and should read 46 9F 24 38
Again, write it instead of the 4 bytes with zeroes reversed like this:
This completes the matter, now just save your work in HxD and write it to the end of your drive.
To do this we need the total block count from the HDD that you fetched in the beginning of the guide from the fdisk -l output, should be 3907029168
The lastpart.bin is 5120 bytes which is the same as 10 blocks of 512 byte length.
So, 3907029168 minus 10 is 3907029158 and put into your DD-line like this:
Code:
dd if=lastpart.bin of=/dev/sda[B]X[/B] bs=512 seek=[B]3907029158[/B]
Or like this if you use DD for Windows:
Code:
dd if=lastpart.bin of=\\?\Device\Harddisk[B]X[/B]\Partition0 bs=512 seek=[B]3907029158[/B]
4. Assembling SATV and finishing up
Now at last, put in your new disk in the SATV and assemble everything back together.
If it doesn't boot in the first try, you could try another cold boot (give it 15 min.).
If that won't do it, you might have to wipe the DATA partition from the fastboot menu.
To cold boot into fastboot, follow this (taken from "http://developer.download.nvidia.com/mobile/shield/ROM/SHIELD_ATV/OTA-1.1/HowTo-Flash-Recovery-Image.txt"):
Code:
HW method:
- Disconnect power cable
- Insert USB OTG cable and make sure to connect other end to a host PC
- Connect power cable to SHIELD
- Quickly start pressing power button for ~3 seconds
- Do not hold the button and connect power supply afterwards
- HDMI TV should be always connected to SHIELD
And format the /DATA partition from fastboot like this:
Code:
fastboot format FS:EXT4 /data
Or do a fastboot oem unlock of the SATV.
Hopefully you will now have a SATV with an upgraded SSD/HDD!

DD for Windows part
Guide for Windows, using dd for Windows by John Newbigin
Download the dd utility from: http://www.chrysocome.net//dd
Code:
[SIZE="4"]
[COLOR="Red"]
WARNING! Using DD for Windows from a command prompt with administrator privileges is DANGEROUS!
If you specify your Windows drive as output file/device, it WILL destroy the partition!
[/COLOR]
[/SIZE]
Code:
[B][I][COLOR="Red"][SIZE="3"]I am not responsible for bricked devices, dead HDDs, animals
activist campaigns, or any H/W damage caused by you following these
directions. YOU are choosing to make these modificiations, and
you, yourself take responsibility for doing these modifications
to your device.
You can do serious H/W damage to your SATV or even your computer
by doing any of this. So, you have been warned! [/SIZE][/COLOR][/I][/B]
So, I used a Windows 10 Pro environment to test this. I think any Windows version based on the NT architecture will be working.
Extract the dd.exe and as the path you want to extract to, use this: "%USERPROFILE%\AppData\Local\Microsoft\WindowsApps"
This gives you the ability to use DD system wide.
Plug in the HDD from your SATV. The disk will be unreadable to Windows as it has no known filesystem. Windows might pop up asking you to format the drive. You MUST ignore that, and press cancel!
Open up a command prompt with administrator privileges. You can do this with Windows key+X to bring up a menu, then choose Command Prompt (administrator).
Navigate to a folder where you want to work from. It doesn't matter where, as you just have to have space enough to store the bin files.
If you need a refreshment in navigating the commnd prompt, you can read up on it here:
http://www.pcstats.com/articleview.cfm?articleid=1723&page=3
Now, run the command
Code:
dd --list
This gives you a lot of information. It even gives you the total byte count of your harddisk drives.
Navigate a little up to locate the right disk:
In this example I didn't use my SATV HDD, but another 750GB HDD I had lying around. The SATV SSHD will have a size of 500107862016 bytes.
Be careful that you choose the right drive to work on, and you also have to find the one that has the device string "\\?\Device\HarddiskX\Partition0".
And X will have to be equivalent to the harddisk number that Windows has assigned to your device.
The you continue by dumping the first 6899870 blocks of data to a bin file:
Code:
dd if=\\?\Device\Harddisk[B]X[/B]\Partition0 of=firstpart.bin count=6899870
This will give you a raw image file of all the partitions up until the /data partition which is better left out (it will come later).
Then continue by dumping the last 5120 bytes of data which contains the partition array and the GPT header:
Code:
dd if=\\?\Device\Harddisk[B]X[/B]\Partition0 of=lastpart.bin skip=976773158 bs=512
You can now disconnect your HDD. These 2 files also counts as a backup of your SATV (not with user settings, data partition was not copied).
Now connect your new SSD in the enclosure. Use dd --list again to determine the right disk to use, and please be careful not to mix up your Windows drive or another drive which contains important data.
You can easily start by writing the firstpart.bin:
Code:
dd if=firstpart.bin of=\\?\Device\Harddisk[B]X[/B]\Partition0
Please continue the rest of the guide in first post.

Hi All:
Thank Luxferro, Tilator and hallydamaster for your hard works, so we could replace the SSHD on shield-pro-tv with any SSD or HHD.
I wrote a small program to do all calculations and generate the new lastpart.bin directly.
usage : ./shield_pro_new_disk_gpt_calculator Input_bin_file New_disk_size_in_byte Output_bin_file
It is for 64-bit Linux PC. Any comments are welcome. And if you like, the source code will be opened.
Well, I think it is quite straightforward to use it. This program just generates the modified lastpart.bin from your original lastpart.bin and disk size (byte) of new SSD/HHD which you will migrate to.
For example of hallydamaster guide, the new 2TB disk has 2000398934016 bytes and 3907029168 sectors. Then
Using following command to generate the correct lastpart.bin for the new 2TB disk.
Code:
./shield_pro_new_disk_gpt_calculator lastpart.bin 2000398934016 new_lastpart.bin
Using following command to write the correct lastpart.bin to the new 2TB disk.
Code:
sudo dd if=new_lastpart.bin of=/dev/sdX bs=512 seek=3907029158

Thanks for the guide.
Does anyone know the performance penalty for using a regular 2TB HDD?

anchung.chen said:
Hi All:
Thank to Luxferro, Tilator and hallydamaster hard works, so we could replace the SSHD on shield-pro-tv with any SSD or HHD.
I wrote a small program to do all calculations and generate the new lastpart.bin directly.
usage : ./shield_pro_new_disk_gpt_calculator input_bin_file disk_size_in_byte output_bin_file
It is for 64-bit Linux PC. Any comments are welcome. And if you like, the source code will be opened.
Click to expand...
Click to collapse
Well, I suppose we have the guide for educational purposes then!
Please, tell something about how to use it.

tech3475 said:
Thanks for the guide.
Does anyone know the performance penalty for using a regular 2TB HDD?
Click to expand...
Click to collapse
I know that another user here @ahmed68 just did his with a SATV, AFAIK.
I don't think it was an SSD atleast.

hallydamaster said:
Well, I suppose we have the guide for educational purposes then!
Please, tell something about how to use it.
Click to expand...
Click to collapse
Well, I think it is quite straightforward to use it. This program just generates the modified lastpart.bin from your original lastpart.bin and disk size (byte) of new SSD/HHD which you will migrate to.
For example of your guide, the new 2TB disk has 2000398934016 bytes and 3907029168 sectors. Then
Using following command to generate the correct lastpart.bin for the new 2TB disk.
Code:
./shield_pro_new_disk_gpt_calculator lastpart.bin 2000398934016 new_lastpart.bin
Using following command to write the correct lastpart.bin to the new 2TB disk.
Code:
sudo dd if=new_lastpart.bin of=/dev/sdX bs=512 seek=3907029158

anchung.chen said:
Hi All:
Thank Luxferro, Tilator and hallydamaster for your hard works, so we could replace the SSHD on shield-pro-tv with any SSD or HHD.
I wrote a small program to do all calculations and generate the new lastpart.bin directly.
usage : ./shield_pro_new_disk_gpt_calculator input_bin_file disk_size_in_byte output_bin_file
It is for 64-bit Linux PC. Any comments are welcome. And if you like, the source code will be opened.
Click to expand...
Click to collapse
have any example how to use it or only run in term ./shield_pro_new_disk_gpt_calculator input_bin_file disk_size_in_byte output_bin_file
plz help I wont to gen gpt for 64gb sd card. I have boot.img for sd card and usb only for l4t Ubuntu thanks.

ahmed68 said:
have any example how to use it or only run in term ./shield_pro_new_disk_gpt_calculator input_bin_file disk_size_in_byte output_bin_file
plz help I wont to gen gpt for 64gb sd card. I have boot.img for sd card and usb only for l4t Ubuntu thanks.
Click to expand...
Click to collapse
You are supposed to do:
Code:
./shield_pro_new_disk_gpt_calculator lastpart.bin 68719476736 lastpart64gb.bin
But take the byte value you get from your own fdisk -l output.
Also, if you are going to use this for Linux and not android, I don't think it will work. The GPT layout that the SATV Pro uses is not standard.

hallydamaster said:
You are supposed to do:
Code:
./shield_pro_new_disk_gpt_calculator lastpart.bin 68719476736 lastpart64gb.bin
But take the byte value you get from your own fdisk -l output.
Also, if you are going to use this for Linux and not android, I don't think it will work. The GPT layout that the SATV Pro uses is not standard.
Click to expand...
Click to collapse
hallydamaster thank you for help
now i use the orig. sshd under ubuntu 14.04 L4T 24.1 i wont to make sdcard for linux and sshd for android to use shield in 4k tv android the best .

I think Nvidia should put boot loader and kernel on internal emmc's for both 16GB and 500GB SATVs rather than keeping significantly different ROM versions for 16GB and 500GB SATVs.
It'd save Nvidia and users time by doing so.
It seems much simpler to add HDDs of any size to 16 GB SATV if the HDD cable is available.

yahoo2016 said:
I think Nvidia should put boot loader and kernel on internal emmc's for both 16GB and 500GB SATVs rather than keeping significantly different ROM versions for 16GB and 500GB SATVs.
It'd save Nvidia and users time by doing so.
It seems much simpler to add HDDs of any size to 16 GB SATV if the HDD cable is available.
Click to expand...
Click to collapse
I certainly agree with that, seems they had a brain fart when deciding how to build the pro. Could be great if we could somehow convert the pro version to boot from internal EMMC.

hallydamaster said:
I certainly agree with that, seems they had a brain fart when deciding how to build the pro. Could be great if we could somehow convert the pro version to boot from internal EMMC.
Click to expand...
Click to collapse
I have serial console print out from 16GB SATV:
http://forum.xda-developers.com/showpost.php?p=67973969&postcount=303
I'm wondering what the output would be for SATV Pro when the HDD is disconnected.
If the first stage boot loader (TegraBoot?) is smart enough, it could check emmc for boot loader.

yahoo2016 said:
I have serial console print out from 16GB SATV:
http://forum.xda-developers.com/showpost.php?p=67973969&postcount=303
I'm wondering what the output would be for SATV Pro when the HDD is disconnected.
If the first stage boot loader (TegraBoot?) is smart enough, it could check emmc for boot loader.
Click to expand...
Click to collapse
That's indeed interesting, lot of info in that output!
I'm pretty sure that @Tilator had someone send him a copy of a complete rip of the EMMC from a 16GB SATV.
He then wrote it to the EMMC on the Pro, which is just empty. It didn't boot with it, but I'm not sure if he tried booting it without the HDD in it.
Cloud be interesting to try though.
Unfortunately I don't really have the time to read up on UART and solder wires on my board to try this. :-/
Not for the time being at least.

i will try to flash satv pro from satv and see it must save in emmc , I wont to make sd card like recovery for satv and satv pro I try repack the partition but bot work I need to edit boot.img #include <sys/mount.h>
#include <unistd.h>
#include <linux/reboot.h>
#include <fcntl.h>
extern char **environ;
int main(int argc, char **unused) {
mount("/dev", "/dev", "devtmpfs", 0, NULL);
mount("/dev/mmcblk0", "/dest", "ext4", 0, NULL);
// mount Android system
// mount("/dev/mmcblk0p1", "/mnt", "ext4", 0, NULL);
mount("/dev", "/dest/dev", NULL, MS_BIND, NULL);
chroot("/dest");
chdir("/");
char * const argv[] = { "/sbin/init", NULL };
execve(argv[0], argv, environ);
}
must change mmcblk0 to mmcblk0p1 ,mmcblk1p1 or sda21/32
---------- Post added at 08:40 PM ---------- Previous post was at 08:20 PM ----------
I take this flash.sh from tegra jetson-tx1
flash.sh: Flash the target board.
# flash.sh performs the best in LDK release environment.
#
# Usage: Place the board in recovery mode and run:
#
# flash.sh [options] <target_board> <root_device>
#
# for more detail enter 'flash.sh -h'
#
# Examples:
# ./flash.sh <target_board> mmcblk0p1 - boot <target_board> from eMMC
# ./flash.sh <target_board> mmcblk1p1 - boot <target_board> from SDCARD
# ./flash.sh <target_board> sda1 - boot <target_board> from USB device
# ./flash.sh -N <IPaddr>:/nfsroot <target_board> eth0 - boot <target_board> from NFS
# ./flash.sh -k LNX <target_board> mmcblk1p1 - update <target_board> kernel
# ./flash.sh -k EBT <target_board> mmcblk1p1 - update <target_board> bootloader
can anybody edit the boot.img to
1. mmcblk0p1 for emmc
2. mmcblk1p1 for sdcard
I think its most work

i flash satv pro from satv i now it come not bootable then i will remove hdd and boot to linux when run sudo fdisk -l i see 2 part of hdd first mmcblk0 (emmc) and sdx its sda in android by dd if=/dev/sdx of=firstpart.bin count=6899870
then dd if=firstpart.bin of=/dev/mmcblk0 and dd if=lastpart.bin of=/dev/mmcblk0 bs=512 seek=xxxxx (xxxxx i will take it from fdisk -l -10) then i most to delete boot patition from sda by sudo fdisk /dev/sda21 # input d , w .
now we have a work satv non pro , i need to use ubuntu in emmc and android in sda for that we must make the first boot img for dualOS like (Geekbox Lollipop Lubuntu dualOS)
http://forum.geekbox.tv/viewtopic.php?f=12&t=3198
anybody have any edia plz help.

ahmed68 said:
now we have a work satv non pro
Click to expand...
Click to collapse
You can boot to Android from emmc (mmcblk0) of SATV Pro without HDD?
Does recovery mode work for SATV Pro without HDD?

Is this fix working with the 3.2 update from a few weeks ago? I'd like to duplicate more of my movies onto my SATV Pro now that the Plex Server is installed.

ahmed68 said:
i flash satv pro from satv i now it come not bootable then i will remove hdd and boot to linux when run sudo fdisk -l i see 2 part of hdd first mmcblk0 (emmc) and sdx its sda in android by dd if=/dev/sdx of=firstpart.bin count=6899870
then dd if=firstpart.bin of=/dev/mmcblk0 and dd if=lastpart.bin of=/dev/mmcblk0 bs=512 seek=xxxxx (xxxxx i will take it from fdisk -l -10) then i most to delete boot patition from sda by sudo fdisk /dev/sda21 # input d , w .
now we have a work satv non pro , i need to use ubuntu in emmc and android in sda for that we must make the first boot img for dualOS like (Geekbox Lollipop Lubuntu dualOS)
http://forum.geekbox.tv/viewtopic.php?f=12&t=3198
anybody have any edia plz help.
Click to expand...
Click to collapse
Hi ahmed, can you please clarify if you had it boot without the HDD?
You cloned the HDD partitions onto the EMMC? And then removed the boot partition from the HDD, and then it booted anyway?
revoman said:
Is this fix working with the 3.2 update from a few weeks ago? I'd like to duplicate more of my movies onto my SATV Pro now that the Plex Server is installed.
Click to expand...
Click to collapse
This procedure will just clone your HDD to another disk, this should be totally independant from Android, unless ofcourse Nvidia would do something to break this.

Maybe I'm the only one who would like to put a smaller HD on my shield TV. Can someone tell me if a 128GB SSD is larger enough or the smaller disk is 256GB?
TIA Polve

Repartitioning Xperia S

How to repartition your Xperia s
The old thread is actually easy but many he not understood
So I he posted YouTube links from which you can understand
How to repartition
Here We Begin:
First of all BACK-UP everything and save it to PC.
Install Minimal ADB and Fatboot into your Windows PC.
Now Switch off your Phone (ACRO S) and
Connect Phone in Fastboot Mode (Power button + Connect USB to PC)
(If phone shows BLUE LED lighten, then everything is going right! IF NOT then Check for Fastboot drivers into your PC)
Now IN PC Open nAOSP.zip and Extract recovery.img to Minimal ADB and Fastboot folder.
(must be installed in c:/program files (x86)/minimal adb and fastboot/keep here)
Open Minimal ADB and Fastboot and type below commands;
~fastboot devices
~fastboot flash boot recovery.img
~fastboot reboot
(Now your phone will restart in TWRP recovery)
----------REPARTITIONING:----------
NOW ACTUAL REPARTITIONING STARTS:
In TWRP GoTo Mount -> uncheck everything (system,data,cache etc)
In PC in Minimal ADB and fastboot type below;
~adb shell
~fdisk -l /dev/block/mmcblk0
Now You'll see some information-table, just copy everything and keep safe. It'll help you.
NOW CONCENTRATE ON LAST TWO ROWS IN THAT INFO-TABLE
/dev/block/mmcblk0p14 49247 261695 7000024 83 Linux
/dev/block/mmcblk0p15 261696 954240 22161424 83 Linux
(Values for your phone may differ)
NOW type below command; (make sure VALUES IN SAME COLOR MATCHES ACCORDING TO YOURS)
fdisk /dev/block/mmcblk0
Command (m for help): p
Command (m for help): d
Partition number (1-15): 15
Command (m for help): d
Partition number (1-15): 14
Command (m for help): n
First Cylender (769-954240, default 769): 49247
Last cylinder or +size or +sizeM or +sizeK (49247-954240, default 954240): 954240
Command (m for help): t
Partition number (1-14): 14
Hex code (type L to list codes): 83
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
YOU'll SEE A ERROR, JUST IGNORE IT
Once partition is Done. Just reboot device. JUST REBOOT!
DONE!
----------Changing File-Syatem to f2fs----------
Into TWRP:
Wipe
Advanced Wipe
Select Data
Repair or Change File system
Change File System
F2FS
Swipe to Change
GO back and do SAME for /cache to change File-System to f2fs
Once it's Done. Just reboot device. JUST REBOOT!
If you see 0MB or any wrong value for data after the reboot, try to format data (Wipe/Format Data).
In Extreme case, convert data to ext4 and convert back to f2fs. It'll hopefully work for you.
DONE!
YouTube Link https://m.youtube.com/watch?v=ZZqJIY-ITwg
One of a kind rom look https://m.youtube.com/watch?v=lwOxauZBP-Q
Xperia S 6.0.1 look https://m.youtube.com/watch?v=j0_7fZyLf8s
Thanks

He*--have. ...sorry for misspelled words

www.youtube.com/c/Nabeelgm
Subscribe for more

Hi, I've got a question, I asked in other repartition thread too. The question is, will I able to install OneOfAKind 5.1.1 again after this repartitioning ? I've read on one of this threads that it only may work with nAOSP and Im a lil' bit confused now :C

How to revert and leave the internal memory as in the original xperia s?
---------- Post added at 05:39 PM ---------- Previous post was at 04:49 PM ----------
I managed to **** my xperia s in inimaginavis ways
First: I tried to partition my internal memory and disappeared from the mmcblk0p12 to mmcblk0p15
How to fix 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"
}
Second: meu celular entrou em loop ao tentar inciar o Twrp.
So I had the brilliant idea of ​​deleting the Cache, System and Data by Adb...
The loop was solved but ...
Is there a solution or can I use my xperia as paper weight? xD

gmnabeel said:
How to repartition your Xperia s
The old thread is actually easy but many he not understood
So I he posted YouTube links from which you can understand
How to repartition
Here We Begin:
First of all BACK-UP everything and save it to PC.
Install Minimal ADB and Fatboot into your Windows PC.
Now Switch off your Phone (ACRO S) and
Connect Phone in Fastboot Mode (Power button + Connect USB to PC)
(If phone shows BLUE LED lighten, then everything is going right! IF NOT then Check for Fastboot drivers into your PC)
Now IN PC Open nAOSP.zip and Extract recovery.img to Minimal ADB and Fastboot folder.
(must be installed in c:/program files (x86)/minimal adb and fastboot/keep here)
Open Minimal ADB and Fastboot and type below commands;
~fastboot devices
~fastboot flash boot recovery.img
~fastboot reboot
(Now your phone will restart in TWRP recovery)
----------REPARTITIONING:----------
NOW ACTUAL REPARTITIONING STARTS:
In TWRP GoTo Mount -> uncheck everything (system,data,cache etc)
In PC in Minimal ADB and fastboot type below;
~adb shell
~fdisk -l /dev/block/mmcblk0
Now You'll see some information-table, just copy everything and keep safe. It'll help you.
NOW CONCENTRATE ON LAST TWO ROWS IN THAT INFO-TABLE
/dev/block/mmcblk0p14 49247 261695 7000024 83 Linux
/dev/block/mmcblk0p15 261696 954240 22161424 83 Linux
(Values for your phone may differ)
NOW type below command; (make sure VALUES IN SAME COLOR MATCHES ACCORDING TO YOURS)
fdisk /dev/block/mmcblk0
Command (m for help): p
Command (m for help): d
Partition number (1-15): 15
Command (m for help): d
Partition number (1-15): 14
Command (m for help): n
First Cylender (769-954240, default 769): 49247
Last cylinder or +size or +sizeM or +sizeK (49247-954240, default 954240): 954240
Command (m for help): t
Partition number (1-14): 14
Hex code (type L to list codes): 83
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
YOU'll SEE A ERROR, JUST IGNORE IT
Once partition is Done. Just reboot device. JUST REBOOT!
DONE!
----------Changing File-Syatem to f2fs----------
Into TWRP:
Wipe
Advanced Wipe
Select Data
Repair or Change File system
Change File System
F2FS
Swipe to Change
GO back and do SAME for /cache to change File-System to f2fs
Once it's Done. Just reboot device. JUST REBOOT!
If you see 0MB or any wrong value for data after the reboot, try to format data (Wipe/Format Data).
In Extreme case, convert data to ext4 and convert back to f2fs. It'll hopefully work for you.
DONE!
YouTube Link https://m.youtube.com/watch?v=ZZqJIY-ITwg
One of a kind rom look https://m.youtube.com/watch?v=lwOxauZBP-Q
Xperia S 6.0.1 look https://m.youtube.com/watch?v=j0_7fZyLf8s
Thanks
Click to expand...
Click to collapse
My device doesnt work anymore, i tried 2 times but when i try to format using TWRP it says:
Failed to mount '/cache' and '/data' (No such device)
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 954240 29161464 83 Linux

Sorry
AnisErrais said:
My device doesnt work anymore, i tried 2 times but when i try to format using TWRP it says:
Failed to mount '/cache' and '/data' (No such device)
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 954240 29161464 83 Linux
Click to expand...
Click to collapse
I just don't have it anymore sorry

foolproof TWRP guide for wileyfox swift (original, V1)

TWRP final guide with EXACTLY what to do;
preparations:
wileyfox swift with cable (original, or high quality cable),
as swift plug is recessed quite deeply not like samsungs ect....
working ADB drivers or platform tools, and access into it from your PC,
latest TWRP for this phone,
first step is locating where your platform tools or ADB is actually installed,
you need to see the actual files like fastboot.exe,ect1.tool.exe,and adb.exe
copy into (platform tools) this folder TWRP.img, (renaming helps here), rename it to
TWRP.img from crackling xxxxxx.img
now make sure USB debugging is enabled in developer options, (press 7 times on build
number to see the developer options)
while in developer options switch on advanced reboot so you see bootloader option
plug in USB cable firmly
reboot your phone, while selecting "reboot", "go into bootloader option"
should get to a screen showing statistics such as
product name- crackling
variant QRD eMMC
Boootloader version- crackling-N-gef75ac3
serial number-XXXXXXXXX
secure boot-enabled
Device state-locked/unlocked
if the last one says locked, make sure you have backups, as continuing from this point
WILL wipe your device, no whatsapp, SMS messages, phone contacts ect..... please make sure
your backup is 100% current before continuing as once unlocked your phone will be factory reset
on your pc inside the platform tools folder, open a command window inside the folder
itself,(hold down SHIFT key , then right click on empty white area to get option "open command
window here).
now you should get a CMD window with the folder name where the platform tools already
populated,
now a quick test to see if everything working,
type fastboot devices and then enter,
should get a printout saying, xxxxxxx Fastboot
where XXXXX is your serial number shown on the screen
if you get nothing checck your cables,drivers ect.....
-----------Optional, if your bootloader is locked,
type fastboot OEM unlock to unlock your bootloader, see warning above........
-----------Optional
now for the meat of the process:
type fastboot flash recovery twrp.img
should get something similar to this:
target reported max download size of 268435456 bytes
sending 'recovery' (16888 KB)...
OKAY [ 0.563s]
writing 'recovery'...
OKAY [ 0.297s]
finished. total time: 0.859s
great, it flashed,
now the tricky bit..... its requires very precise timing, and flexibility as the buttons
are all in one row, and its hard to do everything properly.
UNPLUG the USB cable at this point,
remove the back cover off the phone,
physically remove the battery from the phone,
with the cover still off,
press and hold vol down and power button, and insert the battery into the phone
phone will vibrate, wait till you see wileyfox logo, then ONLY release power button
keep holding vol down button,
eventually TWRP logo appears,
TWRP is now installed, as far as I can make out its only temporary, as at the next reboot
it will flash the standard recovery once more,
hope this help others,
happy customizing....

Hello,
Where you able to mount /system with this method?
If so, what version of TWRP did you use?
Thanks

Cheers eg789123,
"
press and hold vol down and power button, and insert the battery into the phone
phone will vibrate, wait till you see wileyfox logo, then ONLY release power button
keep holding vol down button,
eventually TWRP logo appears, "
Roughly how long was eventually?
Currently typing one-handed...
Jim

This will lead to fail if you have a stock 7.1.1 firmware or old Cyanogen. It should be mentioned that you should flash a compatible bootloader first.

jim13243 said:
Cheers eg789123,
"
press and hold vol down and power button, and insert the battery into the phone
phone will vibrate, wait till you see wileyfox logo, then ONLY release power button
keep holding vol down button,
eventually TWRP logo appears, "
Roughly how long was eventually?
Currently typing one-handed...
Jim
Click to expand...
Click to collapse
quite quickly as soon as it vibrates, will show wileyfox logo, will vibrate again then show TWRP once more,

SlippyMcSlip said:
Hello,
Where you able to mount /system with this method?
If so, what version of TWRP did you use?
Thanks
Click to expand...
Click to collapse
used latest version, 3.1.1.0 TWRP,
I did have to flash eventually my folders to Vfat in order to get my Rom to install, otherwise I kept getting errors when flashing,
found this out by experimenting and flashing different versions until one allowed me to flash.

Thanks for this guide - still useful after years.
Here's my experience with my 2 Swifts with some additions for future reference. (If your phone's side buttons are as crappy as mine, keep reading, there is a way to get to recovery without needing the side buttons at all:)
background:
I'm following this LineageOS 17.1 install guide, specifically the "Installing the correct firmware". I first need to sideload an older Cyanogen 13 via recovery because.. reasons.. (see guide).
To do this I need to first be in Recovery, but not stock recovery because that one would not allow me to sideload either Cyanogen 13 or the new LineageOS. So either TWRP or the LineageOS recovery image for crackling would do - If I could reach it before the phone replaced it with the stock recovery again. So this is where this guide comes in:
Phone #1: This one is a half-decent condition still with the side buttons working most of the time 1st try.
Only thing was the timing of the "tricky bit" where you reinsert the battery while holding down power and volume down. I had the rest of my stuff ready, upon reaching flashed recovery immediately sideloaded the Cyanogen 13 (which replaces the bootloader) and from there on you can reach any flashed recovery also through the new/old/better bootloader's menu. Success!
Phone #2: The side buttons on this one have become very unreliable to the point where it's even hard to navigate the bootloader menu.
I just couldn't get it to work. The side buttons have degraded too much, I couldn't tell if they were actually pressed or not, let alone time it correctly. However I know from #1 I only need to reach recovery once to make it work.
Here's what I did without needing the side buttons at all:
Boot to bootloader, e.g:
Boot normally (fortunately still possible)
Connect usb debugging
Code:
adb reboot bootloader
In bad bootlooder
Do not flash recovery, boot recovery:
Code:
fastboot boot twrp-3.5.2_9-0-crackling.img
(I tried to boot from LineageOS crackling img but that failed. See command log in next post)
In TWRP
Do a factory reset
Code:
adb sideload SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY_v2.zip
Via menu reboot, reboot to bootloader
in good bootloader now
flash recovery:
Code:
fastboot flash recovery twrp-3.5.2_9-0-crackling.img
(this can also be the LineageOS img)
Reboot to recovery using the menu (now this works)
use recovery as you like.
So from here on out I followed the guide including installation of GApps.
I also resized the system partition using parted in TWRP with as detailed in this excellent post, otherwise OpenGApps wouldn't fit.
In the next post is the adb/fastboot command line log where you can see the entire process, hopefully this is useful for anyone with issues with their phone regardless of type.

Code:
###
### Below is a dump of commands to go stock updated Wileyfox Swift (crackling) Android N to LineageOS 17.1 with OpenGapps nano.
### ANYTHING STARTING WITH ### IS NOT A COMMAND BUT DESCRIBES THE PROCESS
### /Downloads contains .imgs for recovery and .zips for sideload, downloaded from LineageOS and OpenGapps.
### /Downloads/parted_gdisk_fdisk_mkfs.ext4-AARCH64 contains parted and mkfs.ext4 to increase system partition size,
### from http://illitrateman.blogspot.com/2020/06/how-to-create-system-partition-in.html
###
### Start, attached USB
Microsoft Windows [Version 10.0.19043.1083]
(c) Microsoft Corporation. All rights reserved.
C:\Users\hbrowser>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
e76fce6c device
### Found out OEM wasn't unlocked. Booted normally and allowed OEM unlock from settings in Android
### Back to bootloader without using volume buttons and such:
C:\Users\hbrowser>adb reboot bootloader
C:\Users\hbrowser>fastboot devices
e76fce6c fastboot
C:\Users\hbrowser>fastboot oem unlock
...
(bootloader) Follow the instructions on screen
OKAY [ 0.037s]
finished. total time: 0.037s
### Had to go through android setup because of OEM unlock - useless but needed to avoid volume buttons
### Back to bootloader again
C:\Users\hbrowser>adb reboot bootloader
error: device '(null)' not found
C:\Users\hbrowser>adb devices
List of devices attached
C:\Users\hbrowser> adb reboot bootloader
error: device '(null)' not found
### Needed to enable USB debug on phone
C:\Users\hbrowser>adb devices
List of devices attached
e76fce6c device
C:\Users\hbrowser>adb reboot bootloader
C:\Users\hbrowser>fastboot devices
e76fce6c fastboot
### Ready to try flash recovery
C:\Users\hbrowser>cd Downloads
C:\Users\hbrowser\Downloads>fastboot flash recovery lineage-17.1-20210710-recovery-crackling.img
target reported max download size of 268435456 bytes
sending 'recovery' (26224 KB)...
OKAY [ 0.826s]
writing 'recovery'...
OKAY [ 1.449s]
finished. total time: 2.277s
### Tried to boot flashed recovery using volume+power buttons, failing miserably:
C:\Users\hbrowser\Downloads>adb devices
List of devices attached
e76fce6c device
C:\Users\hbrowser\Downloads>adb reboot recovery
C:\Users\hbrowser\Downloads>fastboot devices
e76fce6c fastboot
C:\Users\hbrowser\Downloads>fastboot flash recovery lineage-17.1-20210710-recovery-crackling.img
target reported max download size of 268435456 bytes
sending 'recovery' (26224 KB)...
OKAY [ 0.828s]
writing 'recovery'...
OKAY [ 1.792s]
finished. total time: 2.620s
C:\Users\hbrowser\Downloads>adb reboot recovery
C:\Users\hbrowser\Downloads>fastboot devices
e76fce6c fastboot
C:\Users\hbrowser\Downloads>fastboot flash recovery lineage-17.1-20210710-recovery-crackling.img
target reported max download size of 268435456 bytes
sending 'recovery' (26224 KB)...
OKAY [ 0.826s]
writing 'recovery'...
OKAY [ 2.475s]
finished. total time: 3.303s
C:\Users\hbrowser\Downloads>fastboot devices
e76fce6c fastboot
C:\Users\hbrowser\Downloads>fastboot boot recovery lineage-17.1-20210710-recovery-crackling.img
cannot load 'recovery': No such file or directory
### Found out about "fastboot boot"
### Tried it out w/ Lineage 17.1 recovery:
C:\Users\hbrowser\Downloads>fastboot boot lineage-17.1-20210710-recovery-crackling.img
downloading 'boot.img'...
OKAY [ 0.826s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.869s
### No luck, tried some more using side buttons:
C:\Users\hbrowser\Downloads>fastboot flash recovery lineage-17.1-20210710-recovery-crackling.img
target reported max download size of 268435456 bytes
sending 'recovery' (26224 KB)...
OKAY [ 0.828s]
writing 'recovery'...
OKAY [ 1.825s]
finished. total time: 2.652s
C:\Users\hbrowser\Downloads>fastboot flash recovery lineage-17.1-20210710-recovery-crackling.img
target reported max download size of 268435456 bytes
sending 'recovery' (26224 KB)...
OKAY [ 0.825s]
writing 'recovery'...
OKAY [ 0.459s]
finished. total time: 1.286s
C:\Users\hbrowser\Downloads>fastboot flash recovery lineage-17.1-20210710-recovery-crackling.img
target reported max download size of 268435456 bytes
sending 'recovery' (26224 KB)...
OKAY [ 0.826s]
writing 'recovery'...
OKAY [ 0.455s]
finished. total time: 1.282s
### Gave up on side buttons
C:\Users\hbrowser\Downloads>adb reboot recovery
C:\Users\hbrowser\Downloads>adb reboot bootloader
error: device '(null)' not found
###
### Tried fastboot boot w/ TWRP img:
C:\Users\hbrowser\Downloads>fastboot boot twrp-3.5.2_9-0-crackling.img
downloading 'boot.img'...
OKAY [ 0.584s]
booting...
OKAY [ 0.675s]
finished. total time: 1.259s
### Success: we/re in TWRP here:
C:\Users\hbrowser\Downloads>adb devices
List of devices attached
e76fce6c sideload
### Doing something I hoped would work but wasn't in any guide I had seen: sideloading from a fastboot boot-ed recovery, not a flash-ed one
C:\Users\hbrowser\Downloads>adb sideload SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY_v2.zip
serving: 'SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY_v2.zip' (~45%) * failed to read command: No error
### Crossed fingers and rebooted to recovery from TWRP menu.
### After reboot:
C:\Users\hbrowser\Downloads>adb devices
List of devices attached
e76fce6c sideload
### It worked, we're inside Cyanogen 13 recovery here:
C:\Users\hbrowser\Downloads>adb reboot bootloader
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
### OK no adb but no problem, used the CM13 recovery menu to get back to bootloader
### Now actually flashing TWRP recovery:
C:\Users\hbrowser\Downloads>fastboot flash recovery twrp-3.5.2_9-0-crackling.img
target reported max download size of 268435456 bytes
sending 'recovery' (18540 KB)...
OKAY [ 0.587s]
writing 'recovery'...
OKAY [ 1.506s]
finished. total time: 2.094s
### Rebooted phone to recovery again here
### Phone is now running flashed TWRP!
### From here on following this post to increase system partition size
### https://forum.xda-developers.com/t/rom-10-0-official-lineageos-17-1-for-wileyfox-swift.4119901/post-84990507
C:\Users\hbrowser\Downloads>cd parted_gdisk_fdisk_mkfs.ext4-AARCH64
C:\Users\hbrowser\Downloads\parted_gdisk_fdisk_mkfs.ext4-AARCH64>adb push parted /sbin
6093 KB/s (470788 bytes in 0.075s)
C:\Users\hbrowser\Downloads\parted_gdisk_fdisk_mkfs.ext4-AARCH64>adb push mkfs.ext4 /sbin
6704 KB/s (422068 bytes in 0.061s)
### adb shell stuff; disregard the weird ←[6n characters, this is apparently how Windows command shows the adb shell when in recovery mode
C:\Users\hbrowser\Downloads\parted_gdisk_fdisk_mkfs.ext4-AARCH64>adb shell
~ # ←[6nchmod 755 /sbin/parted
~ # ←[6nchmod 755 /sbin/mkfs.ext4
~ # ←[6nparted /dev/block/mmcblk0
GNU Parted 3.2
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) unit s
(parted) p
Model: MMC R821MB (sd/mmc)
Disk /dev/block/mmcblk0: 30535680s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 131072s 132095s 1024s sbl1
2 132096s 133119s 1024s sbl1bak msftdata
3 133120s 135167s 2048s aboot
4 135168s 137215s 2048s abootbak msftdata
5 137216s 138239s 1024s rpm
6 138240s 139263s 1024s rpmbak msftdata
7 139264s 140287s 1024s tz
8 140288s 141311s 1024s tzbak msftdata
9 141312s 142335s 1024s hyp
10 142336s 143359s 1024s hypbak msftdata
11 143360s 143367s 8s devinfo
12 262144s 265215s 3072s modemst1
13 265216s 268287s 3072s modemst2
14 268288s 270335s 2048s misc
15 270336s 270337s 2s fsc
16 270344s 270359s 16s ssd
17 270360s 290839s 20480s splash
18 290840s 291863s 1024s keystore
19 393216s 524287s 131072s oem
20 524288s 524351s 64s DDR
21 524352s 655423s 131072s fat16 modem msftdata
22 655424s 658495s 3072s fsg
23 658496s 658527s 32s sec
24 658528s 724063s 65536s boot
25 724064s 3869791s 3145728s ext4 system msftdata
26 3869792s 3935327s 65536s recovery
27 3935328s 4066399s 131072s odm msftdata
28 4194304s 4259839s 65536s ext4 persist msftdata
29 4259840s 4567039s 307200s ext4 cache msftdata
30 4567040s 4568063s 1024s frp msftdata
31 4568064s 30535646s 25967583s ext4 userdata msftdata
(parted) quit
~ # ←[6ncd /data
/data # ←[6ndd if=/dev/block/mmcblk0p26 of=/sdcard1/recovery.part bs=1k
C:\Users\hbrowser\Downloads\parted_gdisk_fdisk_mkfs.ext4-AARCH64>adb devices
List of devices attached
e76fce6c recovery
### prepare folder b for backups on physical SD card at /sdcard1
C:\Users\hbrowser\Downloads\parted_gdisk_fdisk_mkfs.ext4-AARCH64>adb shell
~ # ←[6ncd /sdcard1
/sdcard1 # ←[6nls -a
. Android LOST.DIR Notifications Ringtones
.. DCIM Movies Pictures
Alarms Download Music Podcasts
/sdcard1 # ←[6nmd b
/sbin/sh: md: not found
/sdcard1 # ←[6nmkdir b
/sdcard1 # ←[6ncd b
/sdcard1/b # ←[6nls
/sdcard1/b # ←[6ncd ..
/sdcard1 # ←[6nexit
### Copy some files needed for partitioning to /sbin
C:\Users\hbrowser\Downloads\parted_gdisk_fdisk_mkfs.ext4-AARCH64>adb push parted /sbin
3559 KB/s (470788 bytes in 0.129s)
C:\Users\hbrowser\Downloads\parted_gdisk_fdisk_mkfs.ext4-AARCH64>adb push mkfs.ext4 /sbin
7496 KB/s (422068 bytes in 0.054s)
C:\Users\hbrowser\Downloads\parted_gdisk_fdisk_mkfs.ext4-AARCH64>adb shell
~ # ←[6nchmod 755 /sbin/parted
~ # ←[6nchmod 755 /sbin/mkfs.ext4
### Make some backups to /sdcard1
~ # ←[6ncd /data
/data # ←[6ntar cvpf /sdcard1/b/data.tar .
./
./lost+found/
./misc/
./misc/vold/
./media/
./media/obb/
./media/0/
./media/0/Music/
./media/0/Podcasts/
./media/0/Ringtones/
./media/0/Alarms/
./media/0/Notifications/
./media/0/Pictures/
./media/0/Movies/
./media/0/Download/
./media/0/DCIM/
./media/0/Android/
./media/0/Android/data/
./media/0/Android/data/.nomedia
./media/0/Android/data/com.google.android.tts/
./media/0/Android/data/com.google.android.tts/files/
./media/0/Android/data/com.google.android.tts/files/download_cache/
./media/0/Android/data/com.google.android.gms/
./media/0/Android/data/com.google.android.gms/files/
./media/0/Android/data/com.google.android.apps.docs/
./media/0/Android/data/com.google.android.apps.docs/files/
./media/0/Android/data/com.google.android.apps.docs/files/pinned_docs_files_do_not_edit/
./media/0/Android/data/com.google.android.apps.docs/cache/
./media/0/Android/data/com.google.android.youtube/
./media/0/Android/data/com.google.android.youtube/files/
./media/0/Android/data/com.google.android.youtube/cache/
./media/0/Android/data/com.google.android.youtube/cache/exo/
./media/0/Android/data/com.google.android.youtube/cache/cronet_media_cache/
./media/0/Android/data/com.google.android.music/
./media/0/Android/data/com.google.android.music/files/
./media/0/Android/data/com.google.android.music/files/._playmusicid
./media/0/Android/data/com.google.android.apps.maps/
./media/0/Android/data/com.google.android.apps.maps/files/
./media/0/Android/data/com.google.android.apps.maps/testdata/
./media/0/Android/data/com.google.android.apps.maps/cache/
./media/0/Android/data/com.google.android.apps.maps/cache/cache_r.m
./media/0/Android/data/com.google.android.videos/
./media/0/Android/data/com.google.android.videos/files/
./media/0/Android/data/com.google.android.videos/files/Movies/
./media/0/Android/data/com.google.android.googlequicksearchbox/
./media/0/Android/data/com.google.android.googlequicksearchbox/files/
./media/0/Android/data/com.google.android.googlequicksearchbox/files/download_cache/
./media/0/Android/data/com.google.android.googlequicksearchbox/files/pending_blobs/
./media/0/Android/data/com.wileyfox.foxhole/
./media/0/Android/data/com.wileyfox.foxhole/cache/
./media/0/Android/data/com.wileyfox.foxhole/cache/.nomedia
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/journal
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/6b252795ac295a4a7cda47dca043156f.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/16ab8a84275fa5f118fba2b6de18dd2a.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/f3c9aa681e0a1bfd4fa4610dcf452878.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/e1d8fa457c200344ee15b29ba08ade16.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/a33f7db12173ef67560cfd72104fa5bd.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/161e5dbfa3c4b7a15067a954dc745205.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/410fbd46ba9d9bf2e386b0c8d1ecbdf1.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/0693488ee7728289efbb3e05c12c3ff5.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/fd066a3d7c69f45743c3b97f6838ff9b.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/33090faed4ae2d43a360a28fcafc15ba.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/6e1f2f8d84d153151594bb46455a1606.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/bdaee8dd07727c6cc0b1cc1e1ba5b7ed.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/7e19b0b4ada70ee784b12e8e2beb1540.0
./media/0/Android/data/com.google.android.gm/
./media/0/Android/data/com.google.android.gm/cache/
./media/0/Android/data/com.android.vending/
./media/0/Android/data/com.android.vending/files/
./media/0/Android/data/com.android.vending/files/installer/
./media/0/TWRP/
./media/0/TWRP/.twrps
./.layout_version
/data # ←[6ncd /
~ # ←[6numount /data
~ # ←[6numount /cache
~ # ←[6numount /sdcard
~ # ←[6ndd if=/dev/block/mmcblk0p25 of=/sdcard1/b/system.part bs=1k
1572864+0 records in
1572864+0 records out
1610612736 bytes (1.5GB) copied, 104.228577 seconds, 14.7MB/s
~ # ←[6ndd if=/dev/block/mmcblk0p26 of=/sdcard1/b/recovery.part bs=1k
32768+0 records in
32768+0 records out
33554432 bytes (32.0MB) copied, 0.438195 seconds, 73.0MB/s
~ # ←[6ndd if=/dev/block/mmcblk0p27 of=/sdcard1/b/odm.part bs=1k
65536+0 records in
65536+0 records out
67108864 bytes (64.0MB) copied, 0.691368 seconds, 92.6MB/s
~ # ←[6ndd if=/dev/block/mmcblk0p28 of=/sdcard1/b/persist.part bs=1k
32768+0 records in
32768+0 records out
33554432 bytes (32.0MB) copied, 0.406862 seconds, 78.7MB/s
~ # ←[6ndd if=/dev/block/mmcblk0p29 of=/sdcard1/b/cache.part bs=1k
153600+0 records in
153600+0 records out
157286400 bytes (150.0MB) copied, 7.381452 seconds, 20.3MB/s
~ # ←[6ndd if=/dev/block/mmcblk0p30 of=/sdcard1/b/frp.part bs=1k
512+0 records in
512+0 records out
524288 bytes (512.0KB) copied, 0.041657 seconds, 12.0MB/s
~ # ←[6nparted /dev/b←[Jlock/mmcblk0
GNU Parted 3.2
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) quit
~ # ←[6ncd /sdcard1
/sdcard1 # ←[6ncd b
/sdcard1/b # ←[6nls
cache.part frp.part persist.part system.part
data.tar odm.part recovery.part
/sdcard1/b # ←[6ncd /
### Here I added the parameter
### -a minimal
### to parted because of some warnings it gave earlier about sector boundaries.
### not sure whether this actually has any effect but warnings are gone and android works fine afterwards
~ # parted /dev/block/mmcblk0 -a minimal
GNU Parted 3.2
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) unit s
(parted) p
Model: MMC R821MB (sd/mmc)
Disk /dev/block/mmcblk0: 30535680s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 131072s 132095s 1024s sbl1
2 132096s 133119s 1024s sbl1bak msftdata
3 133120s 135167s 2048s aboot
4 135168s 137215s 2048s abootbak msftdata
5 137216s 138239s 1024s rpm
6 138240s 139263s 1024s rpmbak msftdata
7 139264s 140287s 1024s tz
8 140288s 141311s 1024s tzbak msftdata
9 141312s 142335s 1024s hyp
10 142336s 143359s 1024s hypbak msftdata
11 143360s 143367s 8s devinfo
12 262144s 265215s 3072s modemst1
13 265216s 268287s 3072s modemst2
14 268288s 270335s 2048s misc
15 270336s 270337s 2s fsc
16 270344s 270359s 16s ssd
17 270360s 290839s 20480s splash
18 290840s 291863s 1024s keystore
19 393216s 524287s 131072s oem
20 524288s 524351s 64s DDR
21 524352s 655423s 131072s fat16 modem msftdata
22 655424s 658495s 3072s fsg
23 658496s 658527s 32s sec
24 658528s 724063s 65536s boot
25 724064s 3869791s 3145728s ext4 system msftdata
26 3869792s 3935327s 65536s recovery
27 3935328s 4066399s 131072s odm msftdata
28 4194304s 4259839s 65536s ext4 persist msftdata
29 4259840s 4567039s 307200s ext4 cache msftdata
30 4567040s 4568063s 1024s frp msftdata
31 4568064s 30535646s 25967583s ext4 userdata msftdata
### ### Point of no return! ### ###
(parted) rm 31
(parted) rm 30
(parted) rm 29
(parted) rm 28
(parted) rm 27
(parted) rm 26
(parted) rm 25
(parted) mkpart 25 ext2 724064 5442655
(parted) name 25 system
(parted) mkpart 26 5442656 5508191
(parted) name 26 recovery
(parted) mkpart 27 5508192 5639263
(parted) name 27 odm
(parted) mkpart 28 ext4 5767168 5832703
(parted) name 28 persist
(parted) mkpart 29 ext4 5832704 6139903
(parted) name 29 cache
(parted) mkpart 30 6139904 6140927
(parted) name 30 frp
(parted) mkpart 31 ext4 6140928 30535646
(parted) name 31 userdata
(parted) quit
Information: You may need to update /etc/fstab.
~ # ←[6ne2fsck -f /dev/block/mmcblk0p25
e2fsck 1.42.9 (28-Dec-2013)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
system: 2606/98304 files (0.0% non-contiguous), 376124/393215 blocks
~ # ←[6nresize2fs /dev/block/mmcblk0p25
resize2fs 1.42.9 (28-Dec-2013)
Please run 'e2fsck -f /dev/block/mmcblk0p25' first.
### The warning above threw me off so I ran both commands once more:
~ # ←[6ne2fsck -f /dev/block/mmcblk0p25
e2fsck 1.42.9 (28-Dec-2013)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
system: 2606/98304 files (0.0% non-contiguous), 376124/393215 blocks
~ # ←[6nresize2fs /dev/block/mmcblk0p25
resize2fs 1.42.9 (28-Dec-2013)
Please run 'e2fsck -f /dev/block/mmcblk0p25' first.
### No change, so just continued making filesystems on partitions where needed:
~ # ←[6nmkfs.ext4 /dev/block/mmcblk0p28
mke2fs 1.44.1 (24-Mar-2018)
Warning: the fs_type small is not defined in mke2fs.conf
Discarding device blocks: done
Creating filesystem with 8192 4k blocks and 2048 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
~ # ←[6nmkfs.ext4 /dev/block/mmcblk0p29
mke2fs 1.44.1 (24-Mar-2018)
Warning: the fs_type small is not defined in mke2fs.conf
Discarding device blocks: done
Creating filesystem with 38400 4k blocks and 9600 inodes
Filesystem UUID: dac5a678-08b8-4d48-aee7-56c37b897905
Superblock backups stored on blocks:
32768
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
~ # ←[6nmkfs.ext4 /dev/block/mmcblk0p31
mke2fs 1.44.1 (24-Mar-2018)
Discarding device blocks: done
Creating filesystem with 3049339 4k blocks and 762528 inodes
Filesystem UUID: c6de72c1-7a7c-4a19-89ef-8d31a25c9e6f
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208
Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done
### Restoring backups from /sdcard
~ # ←[6ndd if=/sdcard1/b/recovery.part of=/dev/block/mmcblk0p26 bs=1k
32768+0 records in
32768+0 records out
33554432 bytes (32.0MB) copied, 6.745916 seconds, 4.7MB/s
~ # ←[6ndd if=/sdcard1/b/odm.part of=/dev/block/mmcblk0p27 bs=1k
65536+0 records in
65536+0 records out
67108864 bytes (64.0MB) copied, 13.897083 seconds, 4.6MB/s
~ # ←[6ndd if=/sdcard1/b/persist.part of=/dev/block/mmcblk0p28 bs=1k
32768+0 records in
32768+0 records out
33554432 bytes (32.0MB) copied, 7.680875 seconds, 4.2MB/s
~ # ←[6ndd if=/sdcard1/b/cache.part of=/dev/block/mmcblk0p29 bs=1k
153600+0 records in
153600+0 records out
157286400 bytes (150.0MB) copied, 31.555507 seconds, 4.8MB/s
~ # ←[6ndd if=/sdcard1/b/frp.part of=/dev/block/mmcblk0p30 bs=1k
512+0 records in
512+0 records out
524288 bytes (512.0KB) copied, 0.104642 seconds, 4.8MB/s
~ # ←[6nmount /dev/block/mmcblk0p31 /data
~ # ←[6ncd /data
/data # ←[6ntar xvpf /sdcard1/b/data.tar .
./
./lost+found/
./misc/
./misc/vold/
./media/
./media/obb/
./media/0/
./media/0/Music/
./media/0/Podcasts/
./media/0/Ringtones/
./media/0/Alarms/
./media/0/Notifications/
./media/0/Pictures/
./media/0/Movies/
./media/0/Download/
./media/0/DCIM/
./media/0/Android/
./media/0/Android/data/
./media/0/Android/data/.nomedia
./media/0/Android/data/com.google.android.tts/
./media/0/Android/data/com.google.android.tts/files/
./media/0/Android/data/com.google.android.tts/files/download_cache/
./media/0/Android/data/com.google.android.gms/
./media/0/Android/data/com.google.android.gms/files/
./media/0/Android/data/com.google.android.apps.docs/
./media/0/Android/data/com.google.android.apps.docs/files/
./media/0/Android/data/com.google.android.apps.docs/files/pinned_docs_files_do_not_edit/
./media/0/Android/data/com.google.android.apps.docs/cache/
./media/0/Android/data/com.google.android.youtube/
./media/0/Android/data/com.google.android.youtube/files/
./media/0/Android/data/com.google.android.youtube/cache/
./media/0/Android/data/com.google.android.youtube/cache/exo/
./media/0/Android/data/com.google.android.youtube/cache/cronet_media_cache/
./media/0/Android/data/com.google.android.music/
./media/0/Android/data/com.google.android.music/files/
./media/0/Android/data/com.google.android.music/files/._playmusicid
./media/0/Android/data/com.google.android.apps.maps/
./media/0/Android/data/com.google.android.apps.maps/files/
./media/0/Android/data/com.google.android.apps.maps/testdata/
./media/0/Android/data/com.google.android.apps.maps/cache/
./media/0/Android/data/com.google.android.apps.maps/cache/cache_r.m
./media/0/Android/data/com.google.android.videos/
./media/0/Android/data/com.google.android.videos/files/
./media/0/Android/data/com.google.android.videos/files/Movies/
./media/0/Android/data/com.google.android.googlequicksearchbox/
./media/0/Android/data/com.google.android.googlequicksearchbox/files/
./media/0/Android/data/com.google.android.googlequicksearchbox/files/download_cache/
./media/0/Android/data/com.google.android.googlequicksearchbox/files/pending_blobs/
./media/0/Android/data/com.wileyfox.foxhole/
./media/0/Android/data/com.wileyfox.foxhole/cache/
./media/0/Android/data/com.wileyfox.foxhole/cache/.nomedia
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/journal
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/6b252795ac295a4a7cda47dca043156f.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/16ab8a84275fa5f118fba2b6de18dd2a.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/f3c9aa681e0a1bfd4fa4610dcf452878.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/e1d8fa457c200344ee15b29ba08ade16.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/a33f7db12173ef67560cfd72104fa5bd.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/161e5dbfa3c4b7a15067a954dc745205.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/410fbd46ba9d9bf2e386b0c8d1ecbdf1.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/0693488ee7728289efbb3e05c12c3ff5.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/fd066a3d7c69f45743c3b97f6838ff9b.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/33090faed4ae2d43a360a28fcafc15ba.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/6e1f2f8d84d153151594bb46455a1606.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/bdaee8dd07727c6cc0b1cc1e1ba5b7ed.0
./media/0/Android/data/com.wileyfox.foxhole/cache/zenkit/FeedImageLoader/7e19b0b4ada70ee784b12e8e2beb1540.0
./media/0/Android/data/com.google.android.gm/
./media/0/Android/data/com.google.android.gm/cache/
./media/0/Android/data/com.android.vending/
./media/0/Android/data/com.android.vending/files/
./media/0/Android/data/com.android.vending/files/installer/
./media/0/TWRP/
./media/0/TWRP/.twrps
./.layout_version
/data # ←[6nqu←[←[←[Jexit
### Ready to see if partition resize worked out
C:\Users\hbrowser\Downloads\parted_gdisk_fdisk_mkfs.ext4-AARCH64>adb reboot recovery
### Back in TWRP
C:\Users\hbrowser\Downloads\parted_gdisk_fdisk_mkfs.ext4-AARCH64>cd ..
C:\Users\hbrowser\Downloads>adb sideload lineage-17.1-20210710-nightly-crackling-signed.zip
serving: 'lineage-17.1-20210710-nightly-crackling-signed.zip' (~47%) * failed to read command: No error
C:\Users\hbrowser\Downloads>adb shell
~ # ←[6ncd /
### Not sure what happened here but at some point I ran into space issues again.
### Used Advanced wipe and filesystem repair, resize in TWRP without effect.
### Rebooted to recovery from TWRP menu again hoping that would make it recognize the added space.
### After reboot correct system partition size became visible in Advanced Wipe.
### Continued:
C:\Users\hbrowser\Downloads>adb sideload lineage-17.1-20210710-nightly-crackling-signed.zip
serving: 'lineage-17.1-20210710-nightly-crackling-signed.zip' (~47%) * failed to read command: No error
### OpenGapps still failed but expected
C:\Users\hbrowser\Downloads>adb sideload open_gapps-arm64-10.0-nano-20210710.zip
serving: 'open_gapps-arm64-10.0-nano-20210710.zip' (~6%) * failed to read command: No error
### Now In TWRP: Resize System partition in Wipe - Advanced
### If error: run again
### This fixes the problem:
C:\Users\hbrowser\Downloads>adb sideload open_gapps-arm64-10.0-nano-20210710.zip
serving: 'open_gapps-arm64-10.0-nano-20210710.zip' (~54%) * failed to read command: No error
C:\Users\hbrowser\Downloads>
### The End

Hey folks, I'm new here obviously and whilst i've managed to do this on a Samsung S5 before (showing my age) - i've been really struggling to get fastboot devices to show my Wileyfox Swift 2.
< waiting for device >
Click to expand...
Click to collapse
So far i've downloaded the Google Drivers from Android Studio, and the phone is listed via adb. Could anyone give any information, that would be truly appreciated.
EDIT:
I tried it on Linux and the drivers were detected straight away - Windows 11 is poo.