Hello guys, Im a experienced user with ROMs, recovery, boot and etc but i have a problem now, and i will try to explain shortly:
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I have a connection with pc(win8.1)
- The computer can communicate with the phone in fastboot mode and adb(recovery)
- the drivers are installed correctly
- BOOTLOOPIN ON GOOGLE
How this happened:
I was minding my own business and my phone was on my desk when it suddenly rebooted itself and then it bootlooped forever. I had some situations when it rebooted itself but always ended in a successful boot, this time it didnt wanted to start.
What have i done till now:
- First thing i entered recovery(TWRP) and dirtyflashed my current rom version and wiped dalvik/cache. (unsuccessful)
- after several times doing the dirtyflash i finally decided to make a complete hard/factory reset the result was none (after i rebooted to recovery again ALL THE DATA WAS THERE WITHOUT ANY DIFFERENCE, like nothing happened)
- Second thing i tried flashing with Odin3 in Download mode - result was unsuccessful (Operation failed at ~45% and the phone freezed) - I tried this several times with different versions of the software and firmware on 2 different computers (same result)
- Third thing i tried to push img with ADB - no result
- Fourth thing i tried the NexusToolKit and using the UNROOT/GOBACK TO STOCK/SOFTBRICK option - operation was SUCCESSFUL (that's what the cmd console said) BUT, after around 15 mins booting on GOOGLE it started booting my old custom ROM that i had (CarbonROM) with its custom boot animation and i was WTF?! - after several minutes it finally booted the rom. As i tried to unlocked it the touchscreen and processing was very slow and unresponsive, it took around 10-15sec. to unlock the phone and then opening the home menu, and in a short delay the phone restarted itself.
- I tried deleting system,data,userdata,cache and etc with the toolkit but same resault - when i rebooted the information was still there.
- I readed alot on the forums and i found that it maybe caused my my eMMC but long ago i checked with a google store app that my chip is from the safe ones and cant go brickbug.
Some information about the phone:
Product Name - tuna
Variant - maguro 16gb
HW version - 9
Bootloader Version - primemd04
baseband version - I9250XXLJ1
carrier info - none
serial number - 0149C7ED0D020018
signing - production
lock state- unlocked
if anything needed pls ask
valkata1212 said:
Hello guys, Im a experienced user with ROMs, recovery, boot and etc but i have a problem now, and i will try to explain shortly:
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I have a connection with pc(win8.1)
- The computer can communicate with the phone in fastboot mode and adb(recovery)
- the drivers are installed correctly
- BOOTLOOPIN ON GOOGLE
How this happened:
I was minding my own business and my phone was on my desk when it suddenly rebooted itself and then it bootlooped forever. I had some situations when it rebooted itself but always ended in a successful boot, this time it didnt wanted to start.
What have i done till now:
- First thing i entered recovery(TWRP) and dirtyflashed my current rom version and wiped dalvik/cache. (unsuccessful)
- after several times doing the dirtyflash i finally decided to make a complete hard/factory reset the result was none (after i rebooted to recovery again ALL THE DATA WAS THERE WITHOUT ANY DIFFERENCE, like nothing happened)
- Second thing i tried flashing with Odin3 in Download mode - result was unsuccessful (Operation failed at ~45% and the phone freezed) - I tried this several times with different versions of the software and firmware on 2 different computers (same result)
- Third thing i tried to push img with ADB - no result
- Fourth thing i tried the NexusToolKit and using the UNROOT/GOBACK TO STOCK/SOFTBRICK option - operation was SUCCESSFUL (that's what the cmd console said) BUT, after around 15 mins booting on GOOGLE it started booting my old custom ROM that i had (CarbonROM) with its custom boot animation and i was WTF?! - after several minutes it finally booted the rom. As i tried to unlocked it the touchscreen and processing was very slow and unresponsive, it took around 10-15sec. to unlock the phone and then opening the home menu, and in a short delay the phone restarted itself.
- I tried deleting system,data,userdata,cache and etc with the toolkit but same resault - when i rebooted the information was still there.
- I readed alot on the forums and i found that it maybe caused my my eMMC but long ago i checked with a google store app that my chip is from the safe ones and cant go brickbug.
Some information about the phone:
Product Name - tuna
Variant - maguro 16gb
HW version - 9
Bootloader Version - primemd04
baseband version - I9250XXLJ1
carrier info - none
serial number - 0149C7ED0D020018
signing - production
lock state- unlocked
if anything needed pls ask
Click to expand...
Click to collapse
first question is, what do you mean by download mode and odin? are you not using the google galaxy nexus? for all i know, that device has fastboot but not download mode, which is a proprietary fork of fastboot (i think). am i wrong? how do you boot into download mode?
your emmc might be locked in read-only mode. when the emmc firmware data structures get corrupted beyond the firmware capacity to fix them, the firmware downgrades to read-only mode, in which you can at least recover the stored information (or part of it).
grab a different custom recovery version than the one in your phone and "fastboot flash" it. then get into the recovery. do you get the newly flashed recovery or the old one that was already on your phone?
Lanchon said:
first question is, what do you mean by download mode and odin? are you not using the google galaxy nexus? for all i know, that device has fastboot but not download mode, which is a proprietary fork of fastboot (i think). am i wrong? how do you boot into download mode?
your emmc might be locked in read-only mode. when the emmc firmware data structures get corrupted beyond the firmware capacity to fix them, the firmware downgrades to read-only mode, in which you can at least recover the stored information (or part of it).
grab a different custom recovery version than the one in your phone and "fastboot flash" it. then get into the recovery. do you get the newly flashed recovery or the old one that was already on your phone?
Click to expand...
Click to collapse
Im using the Samsung galaxy nexus and under "download mode odin" i mean VOLUME DOWN + power button. Phone got both odin and fastboot. Fastboot works in bootloader mode ( volume up + volume down + power button).
I already tried with another custom recovery different from the one currently using, yes it flashes the new one - i tried with philz and cw recovery, both booted but again i couldnt wipe everything.
Lanchon said:
first question is, what do you mean by download mode and odin? are you not using the google galaxy nexus? for all i know, that device has fastboot but not download mode, which is a proprietary fork of fastboot (i think). am i wrong? how do you boot into download mode?
your emmc might be locked in read-only mode. when the emmc firmware data structures get corrupted beyond the firmware capacity to fix them, the firmware downgrades to read-only mode, in which you can at least recover the stored information (or part of it).
grab a different custom recovery version than the one in your phone and "fastboot flash" it. then get into the recovery. do you get the newly flashed recovery or the old one that was already on your phone?
Click to expand...
Click to collapse
the galaxy nexus certainly has download mode/Odin.
it is a Samsung device, they all have this.
just like even the HTC nexus device have hboot
to the op, I wish you much luck, I cannot comment much on this, I had similar happen once and I used "fastboot boot recovery.img" and luckily was able to fix my device from there, but I see this happen sometimes to others (few threads on here about it) where they weren't able to get her back up and running I hope that is not the case for you.
---------- Post added at 12:13 AM ---------- Previous post was at 12:08 AM ----------
oh, also, do you have multiple batteries? have you tried another battery? seems simple enough, but I've heard of devices acting awry similar to this when the battery has taken a crap. (sometime the battery will act as if it's charging and holding charge just fine, but it never actually gets itself to fully charged, for example I think fully charged battery should read about 4.12 with a voltmeter, but one that's gone faulty doesn't reach that, is as if it just cannot provide enough juice needed to get things done causing the device to fail while trying to use that battery)
ashclepdia said:
the galaxy nexus certainly has download mode/Odin.
it is a Samsung device, they all have this.
just like even the HTC nexus device have hboot
to the op, I wish you much luck, I cannot comment much on this, I had similar happen once and I used "fastboot boot recovery.img" and luckily was able to fix my device from there, but I see this happen sometimes to others (few threads on here about it) where they weren't able to get her back up and running I hope that is not the case for you.
---------- Post added at 12:13 AM ---------- Previous post was at 12:08 AM ----------
oh, also, do you have multiple batteries? have you tried another battery? seems simple enough, but I've heard of devices acting awry similar to this when the battery has taken a crap. (sometime the battery will act as if it's charging and holding charge just fine, but it never actually gets itself to fully charged, for example I think fully charged battery should read about 4.12 with a voltmeter, but one that's gone faulty doesn't reach that, is as if it just cannot provide enough juice needed to get things done causing the device to fail while trying to use that battery)
Click to expand...
Click to collapse
I have one and only stock battery. TWRP has a battery counter and it seems ok it stays always on 100% when plugged in the usb. I will try to check it with a voltmeter but i doubt that the problem is from the battery.
Waiting Lanchon to asnwer
valkata1212 said:
Im using the Samsung galaxy nexus and under "download mode odin" i mean VOLUME DOWN + power button. Phone got both odin and fastboot. Fastboot works in bootloader mode ( volume up + volume down + power button).
I already tried with another custom recovery different from the one currently using, yes it flashes the new one - i tried with philz and cw recovery, both booted but again i couldnt wipe everything.
Click to expand...
Click to collapse
ok! i had 2 galaxy nexus and never realized they had download mode lol, or at least i dont remember knowing!
so to confirm: you flash any recovery and it sticks and works. you flash it using "fastboot flash recovery x.img". you ARE NOT booting it directly with "fastboot boot x.img". confirm?
this means that your emmc is not fully locked down, and is good news.
Lanchon said:
ok! i had 2 galaxy nexus and never realized they had download mode lol, or at least i dont remember knowing!
so to confirm: you flash any recovery and it sticks and works. you flash it using "fastboot flash recovery x.img". you ARE NOT booting it directly with "fastboot boot x.img". confirm?
this means that your emmc is not fully locked down, and is good news.
Click to expand...
Click to collapse
BAD NEWS: NOPE, i do not confirm, i only did fastboot boot x.img!! Now i tried fastboot flash recovery x.img, restarted bootloader, and entered to recovery and - bang - old recovery is there. It's seems that my phone is a goner right??
valkata1212 said:
BAD NEWS: NOPE, i do not confirm, i only did fastboot boot x.img!! Now i tried fastboot flash recovery x.img, restarted bootloader, and entered to recovery and - bang - old recovery is there. It's seems that my phone is a goner right??
Click to expand...
Click to collapse
ok your emmc is locked in read-only mode. i had a gnex brought to me in that condition and there was absolutely nothing i could do to fix it. writes are ignored by the emmc (but return "ok" to the kernel) and take near zero time. i tried issuing emmc erase commands, etc, and they were all ignored. i tried booting via USB (via an OMAP debugger) and i couldn't accomplish anything. there is a thread here in xda that details what i tried and what i found out. in the end, i had to replace the motherboard of that phone.
but... i know more now
there is one thing you could try: completely reset the emmc. but really, given that you didnt follow a simple fastboot flash instruction and did a fastboot boot instead makes me think that you wont be able to correctly follow the procedure to completion, but we can try.
the trick is to resize the boot partitions, and during that operation the complete emmc will be wiped. this includes the corrupted FTL data structures inside the emmc that i suspect are causing the read-only lock.
so, caveats:
-this has never ever been tried on this device or this emmc. but it was done successfully in some kindles of the same era, which have a different but similar emmc (both are samsung emmcs). take a look here but DO NOT follow that procedure:
http://forum.xda-developers.com/showthread.php?t=2413453
-everything gets wiped! including bootloaders, partition table, partitions, etc.
-the kindle can boot from usb, but the gnex cant. if the gnex is shut down or rebooted after wiping the emmc but before reconstituting the boot chain, THE DEVICE WILL BE BRICKED FOREVER and never boot again.
-if something goes wrong, BRICK.
-the procedure we will improvise and try can be plain wrong, and the device might BRICK.
-the emmc might ignore the boot partition resize command, in which case it wont brick any further, but this whole adventure would be a failure.
-actually i lied. if the device is rebooted without a proper boot chain, there is a boot-over-USB OMAP debugger that can boot it into a monitor. but reconstituting the boot chain from there might be impossible.
read everything twice and make sure you understand everything i write. ASK instead of guessing!
FROM NOW ON: everything you do, you will do it in latest release of TWRP for your device. before doing ANYTHING here, each time you boot your phone you will enter fastboot mode and "fastboot boot" this TWRP image. then you will "adb shell" to it, or "adb push/pull" to/from it.
first i need a map of your emmc. adb shell then run this and paste the output:
ls -l /dev/block/mmc*
ls -l /dev/block/platform/[whatever device name]/by-name
fdisk -l /dev/block/mmcblk0
---------- Post added at 03:25 PM ---------- Previous post was at 03:19 PM ----------
please post outputs in [ CODE ] tags so that its more readable.
Lanchon said:
ok your emmc is locked in read-only mode. i had a gnex brought to me in that condition and there was absolutely nothing i could do to fix it. writes are ignored by the emmc (but return "ok" to the kernel) and take near zero time. i tried issuing emmc erase commands, etc, and they were all ignored. i tried booting via USB (via an OMAP debugger) and i couldn't accomplish anything. there is a thread here in xda that details what i tried and what i found out. in the end, i had to replace the motherboard of that phone.
but... i know more now
there is one thing you could try: completely reset the emmc. but really, given that you didnt follow a simple fastboot flash instruction and did a fastboot boot instead makes me think that you wont be able to correctly follow the procedure to completion, but we can try.
the trick is to resize the boot partitions, and during that operation the complete emmc will be wiped. this includes the corrupted FTL data structures inside the emmc that i suspect are causing the read-only lock.
so, caveats:
-this has never ever been tried on this device or this emmc. but it was done successfully in some kindles of the same era, which have a different but similar emmc (both are samsung emmcs). take a look here but DO NOT follow that procedure:
http://forum.xda-developers.com/showthread.php?t=2413453
-everything gets wiped! including bootloaders, partition table, partitions, etc.
-the kindle can boot from usb, but the gnex cant. if the gnex is shut down or rebooted after wiping the emmc but before reconstituting the boot chain, THE DEVICE WILL BE BRICKED FOREVER and never boot again.
-if something goes wrong, BRICK.
-the procedure we will improvise and try can be plain wrong, and the device might BRICK.
-the emmc might ignore the boot partition resize command, in which case it wont brick any further, but this whole adventure would be a failure.
-actually i lied. if the device is rebooted without a proper boot chain, there is a boot-over-USB OMAP debugger that can boot it into a monitor. but reconstituting the boot chain from there might be impossible.
read everything twice and make sure you understand everything i write. ASK instead of guessing!
FROM NOW ON: everything you do, you will do it in latest release of TWRP for your device. before doing ANYTHING here, each time you boot your phone you will enter fastboot mode and "fastboot boot" this TWRP image. then you will "adb shell" to it, or "adb push/pull" to/from it.
first i need a map of your emmc. adb shell then run this and paste the output:
ls -l /dev/block/mmc*
ls -l /dev/block/platform/[whatever device name]/by-name
fdisk -l /dev/block/mmcblk0
---------- Post added at 03:25 PM ---------- Previous post was at 03:19 PM ----------
please post outputs in [ CODE ] tags so that its more readable.
Click to expand...
Click to collapse
Im doing the adb shell commands now but I have 1 question: How to find my DEVICE NAME?? im not sure what to type from all the data i get, i will wait until you respond to proceed.
EDIT: This is what i get for now:
Code:
~ # ←[6nls -l /dev/block/mmc*
ls -l /dev/block/mmc*
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
brw------- root root 179, 0 2015-02-05 15:26 mmcblk0
brw------- root root 179, 8 2015-02-05 15:26 mmcblk0boot0
brw------- root root 179, 16 2015-02-05 15:26 mmcblk0boot1
brw------- root root 179, 1 2015-02-05 15:26 mmcblk0p1
brw------- root root 259, 2 2015-02-05 15:26 mmcblk0p10
brw------- root root 259, 3 2015-02-05 15:26 mmcblk0p11
brw------- root root 259, 4 2015-02-05 15:26 mmcblk0p12
brw------- root root 259, 5 2015-02-05 15:26 mmcblk0p13
brw------- root root 179, 2 2015-02-05 15:26 mmcblk0p2
brw------- root root 179, 3 2015-02-05 15:26 mmcblk0p3
brw-rw---- radio radio 179, 4 2015-02-05 15:26 mmcblk0p4
brw------- root root 179, 5 2015-02-05 15:26 mmcblk0p5
brw------- root root 179, 6 2015-02-05 15:26 mmcblk0p6
brw------- root root 179, 7 2015-02-05 15:26 mmcblk0p7
brw------- root root 259, 0 2015-02-05 15:26 mmcblk0p8
brw-rw---- radio radio 259, 1 2015-02-05 15:26 mmcblk0p9
~ # ←[6n
Code:
~ # ←[6nls -l /dev/block/platform/
ls -l /dev/block/platform/
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x root root 2015-02-05 15:26 omap
~ # ←[6n
Code:
~ # ←[6nls -l /dev/block/platform/omap
ls -l /dev/block/platform/omap
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x root root 2015-02-05 15:26 omap2_mcspi.3
drwxr-xr-x root root 2015-02-05 15:26 omap_hsmmc.0
~ # ←[6n
Code:
~ # ←[6nfdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1923584 15388671+ ee EFI GPT
Partition 1 does not end on cylinder boundary
~ # ←[6n
Tell me if you need something
valkata1212 said:
How to find my DEVICE NAME??
Click to expand...
Click to collapse
you should try all options!
but i think it is probably omap/omap_hsmmc.0
are you sure you are "fastboot boot" booting into the latest TWRP recovery before doing adb shell??? your fdisk command doesn't support GPT disks, that is very strange.
also do:
cat /proc/partitions
cat /proc/mounts
also from the pc (are you using linux or windows?):
create a PC folder and cd into it, then:
adb pull -p /dev/block/mmcblk0boot0
adb pull -p /dev/block/mmcblk0boot1
tell me the exact size of the two downloaded files. KEEP THESE FILES SAFE!
Lanchon said:
you should try all options!
but i think it is probably omap/omap_hsmmc.0
are you sure you are "fastboot boot" booting into the latest TWRP recovery before doing adb shell??? your fdisk command doesn't support GPT disks, that is very strange.
also do:
cat /proc/partitions
cat /proc/mounts
also from the pc (are you using linux or windows?):
create a PC folder and cd into it, then:
adb pull -p /dev/block/mmcblk0boot0
adb pull -p /dev/block/mmcblk0boot1
tell me the exact size of the two downloaded files. KEEP THESE FILES SAFE!
Click to expand...
Click to collapse
I can 100% confirm Im on the newest TWRP recovery version v2.8.4.0 flashed with fastboot boot x.img
And here are the results i got, and also those new commands:
Code:
~ # ←[6nls -l /dev/block/platform/omap/omap_hsmmc.0/by-name
ls -l /dev/block/platform/omap/omap_hsmmc.0/by-name
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
lrwxrwxrwx root root 2015-02-05 18:06 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-02-05 18:06 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-02-05 18:06 dgs -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-02-05 18:06 efs -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-02-05 18:06 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-02-05 18:06 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-02-05 18:06 param -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-02-05 18:06 radio -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-02-05 18:06 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-02-05 18:06 sbl -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-02-05 18:06 system -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-02-05 18:06 userdata -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-02-05 18:06 xloader -> /dev/block/mmcblk0p1
~ # ←[6n
Code:
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name
31 0 1024 mtdblock0
179 0 15388672 mmcblk0
179 1 128 mmcblk0p1
179 2 3584 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 8192 mmcblk0p7
259 0 12224 mmcblk0p8
259 1 16384 mmcblk0p9
259 2 669696 mmcblk0p10
259 3 442368 mmcblk0p11
259 4 14198767 mmcblk0p12
259 5 64 mmcblk0p13
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
~ # ←[6n
Code:
~ # ←[6ncat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime 0 0
/dev/block/mmcblk0p11 /cache ext4 rw,seclabel,relatime,user_xattr,barrier=1,data
=ordered 0 0
/dev/block/mmcblk0p12 /data ext4 rw,seclabel,relatime,user_xattr,barrier=1,data=
ordered 0 0
/dev/block/mmcblk0p12 /sdcard ext4 rw,seclabel,relatime,user_xattr,barrier=1,dat
a=ordered 0 0
~ # ←[6n
AND THIS IS WHAT I GET WHEN I TRIED TO PULL THE FILES U ASKED: (both mmcblk0boot0/1)
Code:
E:\WugFresh Development\Nexus Root Toolkit\data\MMC>adb pull -p /dev/block/mmcbl
k0boot0
remote object '/dev/block/mmcblk0boot0' not a file or directory
lol please repeat:
ls -l /dev/block/platform/omap/omap_hsmmc.0/by-name
using a wider terminal so that the output can be read
your partitions are:
Code:
major minor #blocks name
31 0 1024 mtdblock0
179 0 15388672 mmcblk0
179 1 128 mmcblk0p1 xloader
179 2 3584 mmcblk0p2 sbl
179 3 20480 mmcblk0p3 efs
179 4 8192 mmcblk0p4 param
179 5 4096 mmcblk0p5 misc
179 6 4096 mmcblk0p6 dgs
179 7 8192 mmcblk0p7 boot
259 0 12224 mmcblk0p8 recovery
259 1 16384 mmcblk0p9 radio
259 2 669696 mmcblk0p10 system
259 3 442368 mmcblk0p11 cache
259 4 14198767 mmcblk0p12 userdata
259 5 64 mmcblk0p13 metadata
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
---------- Post added at 03:34 PM ---------- Previous post was at 03:28 PM ----------
cat /proc/mtd
cat /proc/emmc
dd if=/dev/block/mmcblk0boot0 of=/tmp/mmcblk0boot0
dd if=/dev/block/mmcblk0boot1 of=/tmp/mmcblk0boot1
from the PC:
adb pull /tmp/mmcblk0boot0
adb pull /tmp/mmcblk0boot1
---------- Post added at 03:36 PM ---------- Previous post was at 03:34 PM ----------
get the latest philz touch recovery for gnex. fastboot boot into it, then try this again:
fdisk -l /dev/block/mmcblk0
Lanchon said:
lol please repeat:
ls -l /dev/block/platform/omap/omap_hsmmc.0/by-name
using a wider terminal so that the output can be read
your partitions are:
Code:
major minor #blocks name
31 0 1024 mtdblock0
179 0 15388672 mmcblk0
179 1 128 mmcblk0p1 xloader
179 2 3584 mmcblk0p2 sbl
179 3 20480 mmcblk0p3 efs
179 4 8192 mmcblk0p4 param
179 5 4096 mmcblk0p5 misc
179 6 4096 mmcblk0p6 dgs
179 7 8192 mmcblk0p7 boot
259 0 12224 mmcblk0p8 recovery
259 1 16384 mmcblk0p9 radio
259 2 669696 mmcblk0p10 system
259 3 442368 mmcblk0p11 cache
259 4 14198767 mmcblk0p12 userdata
259 5 64 mmcblk0p13 metadata
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
---------- Post added at 03:34 PM ---------- Previous post was at 03:28 PM ----------
cat /proc/mtd
cat /proc/emmc
dd if=/dev/block/mmcblk0boot0 of=/tmp/mmcblk0boot0
dd if=/dev/block/mmcblk0boot1 of=/tmp/mmcblk0boot1
from the PC:
adb pull /tmp/mmcblk0boot0
adb pull /tmp/mmcblk0boot1
---------- Post added at 03:36 PM ---------- Previous post was at 03:34 PM ----------
get the latest philz touch recovery for gnex. fastboot boot into it, then try this again:
fdisk -l /dev/block/mmcblk0
Click to expand...
Click to collapse
Code:
~ # ←[6ncat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00001000 "w25q80"
~ # ←[6n
hmm :?
Code:
~ # ←[6ncat /proc/emmc
cat /proc/emmc
cat: can't open '/proc/emmc': No such file or directory
~ # ←[6n
I downloaded and fastboot booted latest phillz and i did the command again, but the resault is the same:
Code:
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1923584 15388671+ ee EFI GPT
Partition 1 does not end on cylinder boundary
~ #
So i pulled both mmcblk files, they are 2,048 KB each.
this is going to be redundant, buy do it just in case:
adb pull -p /dev/block/mmcblk0p##
where ## is 1 to 9 and 13 (skip 10, 11, 12)
Lanchon said:
this is going to be redundant, buy do it just in case:
adb pull -p /dev/block/mmcblk0p##
where ## is 1 to 9 and 13 (skip 10, 11, 12)
Click to expand...
Click to collapse
Done. had to do the trick with dd if=/dev/block/mmcblk0p of=/tmp/mmcblk0p first then adb pull /tmp/mmcblk0p, but i got the files now, their size range are from 64 KB to 20,480 KB (largest one)
Whats next:?
EDIT: first reboot into clean latest TWRP
dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-beg bs=1M count=96
dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000
from the PC:
adb pull -p /tmp/mmcblk0-beg
adb pull -p /tmp/mmcblk0-end
beg should be 96MB
end should be 28MB
verify, that on the PC.
DO NOT REBOOT THE PHONE FROM THIS POINT FORWARD!
we want those files in the ramdrive
Lanchon said:
EDIT: first reboot into clean latest TWRP
dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-beg bs=1M count=96
dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000
from the PC:
adb pull -p /tmp/mmcblk0-beg
adb pull -p /tmp/mmcblk0-end
beg should be 96MB
end should be 28MB
verify, that on the PC.
DO NOT REBOOT THE PHONE FROM THIS POINT FORWARD!
we want those files in the ramdrive
Click to expand...
Click to collapse
downloaded beg and i confirm its 98 MB but i have a problem with END, it doesnt want to copy it im tmp, i deleted the "skip=15000 part" and it came out 250 MB!! but couldnt pull it cuz it game me "no space left on device"
What should i do? Reboot and do this again or ?
valkata1212 said:
downloaded beg and i confirm its 98 MB but i have a problem with END, it doesnt want to copy it im tmp, i deleted the "skip=15000 part" and it came out 250 MB!! but couldnt pull it cuz it game me "no space left on device"
What should i do? Reboot and do this again or ?
Click to expand...
Click to collapse
reboot
redo first dd
no need to pull again
redo second dd, and tell me the error message or whatever it outputs. form now on, i recommend you dont try to fix things without posting first, one error can mean BRICK.
Lanchon said:
reboot
redo first dd
no need to pull again
redo second dd, and tell me the error message or whatever it outputs. form now on, i recommend you dont try to fix things without posting first, one error can mean BRICK.
Click to expand...
Click to collapse
Code:
E:\WugFresh Development\Nexus Root Toolkit\data\MMC>adb shell
~ # ←[6ndd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000
dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000
It doesnt start the operation dont know why, just like the first time i did. Beg finished for 2-3 sec but -end just doesnt show up.
valkata1212 said:
Code:
E:\WugFresh Development\Nexus Root Toolkit\data\MMC>adb shell
~ # ←[6ndd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000
dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000
It doesnt start the operation dont know why, just like the first time i did. Beg finished for 2-3 sec but -end just doesnt show up.
Click to expand...
Click to collapse
you are saying:
-no error displayed
-no file created
?
does the phone stop responding?
Long-time UNIX guy here, but relatively new to the world of Android.
I have recently purchased an Asus MemoPAD (ME103K) ; I then became root, and took a `dd` image of the read-only `system` partition to the external SD card:
Code:
$ su
# dd if=/dev/block/platform/msm_sdcc.1/by-name/system \
of=/storage/MicroSD/system.img bs=1M
# ls -l /storage/MicroSD/system.img
-rw-r--r-- 1 root root 2147483648 Sep 27 13:15 system.img
The size (exactly 2GiB) was a bit suspicious - could it be that this was because of the FAT32 partition on the SD card?
No, it was not - `tune2fs -l` revealed that this was indeed, a valid EXT4 image, exactly sized at 2GiB, which passed `fsck -f` with no errors at all.
And `fastboot` (from the linux machine attached to the tablet) concurred, after an `adb reboot bootloader`:
Code:
linuxbox# fastboot getvar all
(bootloader) version-bootloader: 3.03
(bootloader) version-hardware: rev_c
(bootloader) variant: LEOPARDCAT 16G
(bootloader) version-baseband: H00_0.16.F_0521
(bootloader) serialno: 0a3dXXXX
...
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x0000000080000000
That size, is indeed 2GB:
Code:
linuxbox# python2 -c 'print 0x0000000080000000'
2147483648
So, all is good - I have a backup of the image. Now to test restoring it.
I try to flash the system.img back to the tablet - to make sure I can recover from anything, the sort of bullet-proof backup we do in the Unix world (*e.g. restore contents of a drive via `dd if=backup.image of=/dev/sdXXX`*).
Everything related to `adb` and `fastboot` work flawlessly - so I try...
Code:
linux_box# fastboot devices
0a3dXXXX fastboot
linux_box# mount /dev/sdcard /mnt/sdcard
linux_box# cp /mnt/sdcard/system.img .
linux_box# fastboot flash system system.img
error: cannot load 'system.img'
Hmm. I download and build the `android-tools-5.1.1` of my distribution from sources, adding debug information - and step in the debugger, to see this failure:
Code:
# gdb --args fastboot flash system system.img
...
(sorry, can't paste links yet - see this image: http i stack imgur com 9bIEM.png
Interesting - even though I am in a 64bit machine, apparently there are issues that turn the file size "negative" (in a 32bit world, the file size of my image, 2^31, is indeed considered negative - to be exact, `-2147483648`.
OK, fine - how do they flash large image files in Android?
Googling, searching - turns out they use this `make_ext4fs` tool, that creates flashable images. In fact it is part of what I just compiled, so I might as well use it:
Code:
# mkdir /system
# mount -o loop,ro system.img /system
# ls -l /system
total 208
drwxr-xr-x 106 root root 8192 Sep 17 22:24 app
drwxr-xr-x 3 root 2000 8192 Sep 26 21:08 bin
-rw-r--r-- 1 root root 6847 Sep 12 16:59 build.prop
drwxr-xr-x 19 root root 4096 Sep 26 21:08 etc
drwxr-xr-x 2 root root 4096 Aug 11 22:27 fonts
drwxr-xr-x 4 root root 4096 Sep 12 16:56 framework
drwxr-xr-x 10 root root 16384 Sep 12 16:59 lib
drwxr-xr-x 2 root root 4096 Jan 1 1970 lost+found
drwxr-xr-x 3 root root 4096 Aug 11 22:18 media
drwxr-xr-x 59 root root 4096 Aug 11 22:29 priv-app
-rw-r--r-- 1 root root 126951 Aug 1 2008 recovery-from-boot.p
drwxr-xr-x 3 root root 4096 Aug 11 21:02 scripts
drwxr-xr-x 3 root root 4096 Aug 11 21:02 tts
drwxr-xr-x 11 root root 4096 Sep 26 21:08 usr
drwxr-xr-x 8 root 2000 4096 Aug 11 22:29 vendor
drwxr-xr-x 2 root 2000 4096 Sep 26 21:09 xbin
# ../extras/source/extras/ext4_utils/make_ext4fs \
-l 2048M new_system.img /system
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 2666/131072 inodes and 375014/524288 blocks
Cool - so I can apparently build system images from plain old folders. The sky will be my limit - I'll be able to add anything I want to this image.
Let's burn it...
Code:
# fastboot flash system new_system.img
erasing 'system'...
OKAY [ 0.064s]
sending 'system' (2088960 KB)...
^C
I waited for 1h before hitting that Ctrl-C. And had to power-cycle the tablet, which booted back in fastboot mode.
This is not looking good.
What if I build a smaller image? Maybe the 2GB are somehow an issue, and this partition is not used to full capacity - it has free space:
Code:
# ../extras/source/extras/ext4_utils/make_ext4fs \
-l 1536M new_system.img /system
# ./fastboot flash system system.img
erasing 'system'...
OKAY [ 0.065s]
sending 'system' (1572864 KB)...
OKAY [ 51.039s]
writing 'system'...
OKAY [235.080s]
finished. total time: 286.183s
OK, this looks very promising (and only took 5 min). I guess I can now reboot back and everything should be normal, yes?
No
(sorry, can't paste links yet - see this image: http i stack imgur com U7wiX.png
I don't mind a temporarily bricked device, as long as I **do** get to control it in the end (machines that I am not a master of, are machines I don't care to operate
Any ideas on what I did wrong and what I can do to fix this?
Thanks in advance.
P.S. I checked the Asus support page for my tablet - they only provide the sources for the kernel, and the Over-the-air .zip file. That in turn contains a file-system level backup from the root - i.e. the `system` folder exists in there as just a folder, not an image, not a `system.img` that I can flash - so that doesn't really help me.
[SOLVED] Booted from external sd.
I documented how I solved it in android stack exchange, article 124344 (can't post links - the url is formed from .... http android.stackexchange.com questions 124344 trying-to-flash-a-system-img-i-took-with-dd-failing )
Executive summary - I edited my custom boot image /fstab.qcom to point /system to the external SD card, and dd-ed my image there.
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.