Develop Bugs

How to repair Wileyfox Swift when I can get into TWRP but not bootloader

Hi. I've just updated CM13 to the latest nightly using TWRP, but now the system just boots into TWRP - that's whether I select boot system, recovery, or bootloader. I tried restoring from a TWRP backup or another copy of the nightlies zip - it all seems to work fine but doesn't solve the problem. I can connect to the 'recovery' device using adb but adb restart bootloader just loads TWRP again. I've tried wiping first the dalvik/cache, then everything but the internal card, then finally everything but nothing seems to work.
I did get something a little bit like this a few days ago because SuperSU was complaining that I needed to update the binary. I let it do it the way that it suggested one does when TWRP is installed and afterwards couldn't reboot into system, but after a few minutes of frustration sorted things by wiping various partitions.
I attempted to load the full system restore files (cm-13.1-ZNH2KAS29G-crackling-signed-fastboot-74bb753396.zip) using TWRP but that didn't work (I imagine because they're designed to be run via fastboot). I tried loading them via the ADB sideloader option included in TWRP but it failed after a few seconds (I think the message was 'transmitting 0.0x'
I opened that zip and copied the various files to the external card, but I then baulked at installing the image files manually because the only partition option I'm given is boot and my understanding is that each image file should go into its own partition.
The only other potentially pertinent information I can think of:
TWRP keeps reporting "E: Unable to find partition size for '/recovery'"
Has anyone got any ideas please? I had been musing that my next phone would have OTG and NFC, but I wasn't planning to upgrade just yet if I don't absolutely have to.

Have you got it fixed? And if yes - how? I am stuck in a similar situation and can't find a solution for it. Tnx in advance.

Really need help, google flash gone bad

At first I tried to update my existing TWRP (3.2.1-0) to the 3.2.1-2 variant. It flashed ok, but then the phone would only boot to TWRP (reason for upgrade is that 3.2.1-0 would hang). I was attempting initially to put myself on the path to a "custom rom". When this failed, I manually flashed the latest google firmware from their page and it still will not do anything other than fastboot mode. No recovery, no firmware load. When I try to do the flash-all.bat method now, all I get after it loads the archive contents is "error: Cannot generate image for userdata. Guess I got a $1000 brick at this point?? Image from the PC screen included.

See if this thread helps.
https://forum.xda-developers.com/pi...ory-image-flashing-fails-t3715350/post7649698

I am going to have to find another way to look at that thread. My ipad is getting directed to some HTC desire article about and orange and black theme.
I have tried so far very unsuccessfully to wipe everything by booting to twrp via fastboot method. Then I used the dueces script to reflash everything completely (both partitions). No matter whether I flash complete stock or flash magisk and verizon radio files, it just hangs on the white google screen now and that is as far as I have gotten. Left it at home in this mode hoping it will clear.

JoeNeckbone said:
See if this thread helps.
https://forum.xda-developers.com/pi...ory-image-flashing-fails-t3715350/post7649698
Click to expand...
Click to collapse
That link is bad. Three devices are going to an htc desire theming page.

remove the -w from the update line in flash-all.

I have got the same problem since yesterday and search for a solution.

ctradio said:
That link is bad. Three devices are going to an htc desire theming page.
Click to expand...
Click to collapse
Not sure what happened with link, https://forum.xda-developers.com/pi...ry-image-flashing-fails-t3715350/post74751631

new adb dont help for me. I cannot flash slot a and change to b and got the error message that no slot is supported.

Still need help? Have you tried Skipsoft? Sure its not been updated but it might beable to help ..
Where fastboot flashing failed for me one time it got me out of a hole....
Otherwise i can try and remote and help... BTW its not finding the userdata file in the fastboot side... Something isnt right hence why it cant create the userdata file...

I try to boot with skipsoft to temp twrp but stuck on boot.img loading. the flashed twrp stuck on twrp logo and before I have changed from slot b to a inside twrp i can boot. now I cannot flash inside fast boot or delete anything.

Have you guys tried Deuces Bootloop Recovery & Flashing Script? I'd imagine you'd run into the same issues as the script runs a lot of the same fastboot commands...but it has worked wonders for many other users so......
I also might try re-downloading the factory image and comparing the Checksums to make sure you have a whole exact download just in case that's getting in the way of properly generating the userdata image. I'd also suggest making sure you have more than 4GB of space on your C drive; I was getting similar messages about not finding or not generating system images because they couldn't be fully extracted (temporarily) because I didn't have sufficient temp space on my C drive.
But I had encountered this issue before. It was either userdata or system_other partition. I did attempt to fastboot erase and fastboot format those partitions and other tweaks; even messed with changing the size of the partition (you might have better luck). What I seemed to conclude is that I was flashing the wrong month's Full Factory image; i.e. I was manually flashing system_other image from February when the whole phone was still on January. But I believe what I ended up doing was flashing a Full Factory image with the "-w" intact; therefore, if you still have access, you should copybackcup (via TWRP or adb pull) your internal storage (/sdcard and-or /data/media) and simply flash a Full Factory image with wipe option enabled...
Just some thoughts and suggestions...hope this helps...

I figured it out finally. Even though my ADB/Fastboot tools were a later creation date than the ones posted online, the ones online worked great. Even used the dueces script to ensure the junk is gone. Thanks all! Hate pesky gotchas like that!!

Can't root or install TWRP after Dec factory setting

I was rooted on 9 with Magisk. Updated to 10 via Google update on the phone. All worked. Still rooted but didn't have TWRP installed- it wouldn't work. But no worries. I was rooted which is the main thing.
Tried to do the DEC OTA with Magisk. Didn't work. Flashed factory image of December and it worked. Tried to boot img of TWRP. didn't work. Tried to use Magisk to root with the boot.img patch from PC. Didn't work. Phone wouldn't boot.
Reflashed factory image and it didn't work. Changed cord to same USB A and and got it working again. Rinse, repeat. Eventually it stopped working period. adb and fastboot were not talking to the phone.
Used different USB A port and newer cord (same as above) and was able to reinstall Dec factory and it worked. Used new cable to boot twrp.img. Worked. Used that to flash TWRP. Worked. Tried to flash Magist in TWRP. Got TWRP bootloot. Used TWRP to fix bootloop. It restored boot (so far as I can tell- what do I know? I'm just a lawyer) and phone worked but no root. Rinse repeat a number of times. Got Magisk working and THEN tried to flash TWRP. Bad plan. Broke.
Went to screen saying whole thing was broke (Their recovery sort-of screen saying files corrupted in red and I could retry or wipe in blue. But I could factory reset. I avoided that and tried to reflash (using flash-all.bat after removing -w) a number of times. It finally worked. Gave it the overnight to calm down. Me, too.
10 was working. Cord seemed to be working. Came home after work and booted image of TWRP. That worked. Flashed Magisckzip. That dumped me into TWRP which I swear to god I had not flashed, just temp booted. So tonight was rinse and repeat of yesterday's woes.
Anyhow, many attempts to reinstall Dec factory image finally worked (using various cords, USB A & C ports.)
Rinse, repeat.
I have my SD card backed up on my PC so it isn't any kind of disaster for me to do a factory rest but dammit! I don't wanna! It should work.
At the present time I am working with Dec factory image, stock recovery, and not rooted. (Although Tasker seems to be working in location-sound off circumstances. WTAF?)
Taking any and all advice. Thanks.
Aside from full wipe. If that's your only advice please just say "wipe" and move along. If you have another suggestion, please use lots of words.
(My husband says it's the testosterone sensor but I'm the one who fixes the computers, phones, and network so I think my cover is deep enough...)

janehull said:
I was rooted on 9 with Magisk. Updated to 10 via Google update on the phone. All worked. Still rooted but didn't have TWRP installed- it wouldn't work. But no worries. I was rooted which is the main thing.
Tried to do the DEC OTA with Magisk. Didn't work. Flashed factory image of December and it worked. Tried to boot img of TWRP. didn't work. Tried to use Magisk to root with the boot.img patch from PC. Didn't work. Phone wouldn't boot.
Reflashed factory image and it didn't work. Changed cord to same USB A and and got it working again. Rinse, repeat. Eventually it stopped working period. adb and fastboot were not talking to the phone.
Used different USB A port and newer cord (same as above) and was able to reinstall Dec factory and it worked. Used new cable to boot twrp.img. Worked. Used that to flash TWRP. Worked. Tried to flash Magist in TWRP. Got TWRP bootloot. Used TWRP to fix bootloop. It restored boot (so far as I can tell- what do I know? I'm just a lawyer) and phone worked but no root. Rinse repeat a number of times. Got Magisk working and THEN tried to flash TWRP. Bad plan. Broke.
Went to screen saying whole thing was broke (Their recovery sort-of screen saying files corrupted in red and I could retry or wipe in blue. But I could factory reset. I avoided that and tried to reflash (using flash-all.bat after removing -w) a number of times. It finally worked. Gave it the overnight to calm down. Me, too.
10 was working. Cord seemed to be working. Came home after work and booted image of TWRP. That worked. Flashed Magisckzip. That dumped me into TWRP which I swear to god I had not flashed, just temp booted. So tonight was rinse and repeat of yesterday's woes.
Anyhow, many attempts to reinstall Dec factory image finally worked (using various cords, USB A & C ports.)
Rinse, repeat.
I have my SD card backed up on my PC so it isn't any kind of disaster for me to do a factory rest but dammit! I don't wanna! It should work.
At the present time I am working with Dec factory image, stock recovery, and not rooted. (Although Tasker seems to be working in location-sound off circumstances. WTAF?)
Taking any and all advice. Thanks.
Aside from full wipe. If that's your only advice please just say "wipe" and move along. If you have another suggestion, please use lots of words.
(My husband says it's the testosterone sensor but I'm the one who fixes the computers, phones, and network so I think my cover is deep enough...)
Click to expand...
Click to collapse
Oh my, where to start. Definitely sounds like you've got the famous P2XL USB cable bugaboo...at least somewhat. Here's what I would do.
Extract the boot.img from the factory image, place it on your phone and patch it again, then transfer it to your platform-tools folder.
Make sure your platform tools are up to date. Latest version is 29.0.5
Have you also fastbooted the factory image to both slots? If not, do that first. You can manually change slots with..fastboot --set-active=a or b depending what slot your currently on.
If your phone is booting, then go back and fastboot your patched boot.img to both slots with...
..fastboot flash boot magisk_patched.img --slot=all..
If the phone boots you should be rooted.
If you still want twrp, download it again to your pc, put one copy in your platform-tools folder, and one on your phone, remove your screen lock and set it to swipe or none. Then fastboot the twrp 3.3.0-0.img which should boot you into twrp. If it's working, then select install, select image, then flash the twrp image to your recovery ramdisk partition. That should keep your recovery as twrp. Boot up, and you should be good to go :good:

Yes, latest platform tools. After first difficulties I dumped everything, did new downloads and upzips of of factory image, platform-tools, and got new twrp.img, twrp.zip and magisk.zip. Checkedsum on all of them I could.
No. It never occurred to me to fastboot factory image to both slots. I guess I just assumed that The Google (tm) would know what they were doing. Thank you for that. I will give it a shot in the morning. I need enough lead time to fix it if it breaks because my life and office are on that phone.
And now, after learning how to see which slot is active I can learn how to flash to both! Thanks a lot.

janehull said:
Yes, latest platform tools. After first difficulties I dumped everything, did new downloads and upzips of of factory image, platform-tools, and got new twrp.img, twrp.zip and magisk.zip. Checkedsum on all of them I could.
No. It never occurred to me to fastboot factory image to both slots. I guess I just assumed that The Google (tm) would know what they were doing. Thank you for that. I will give it a shot in the morning. I need enough lead time to fix it if it breaks because my life and office are on that phone.
And now, after learning how to see which slot is active I can learn how to flash to both! Thanks a lot.
Click to expand...
Click to collapse
Just a little additional FYI...if you want to keep twrp as your recovery, flash the same image file, NOT the twrp zip file, once you enter twrp after fastbooting it.
And, if you want to know what slot your currently on, the command is...fastboot getvar all. Best of luck to you :good:

Better and better. Now I have no USB. When I go to it in Settings ALL usb prefs are greyed out. Needless to say I haven't tried to flash anything because I can't. So I guess a factory reset is in my future. At least I copied my SD card and Titanium Backup folder. /sigh
Safe mode makes no difference.
If anyone knows how to get the USB working without wiping that would be appreciated.
Oh, and in other "It ain't workin' rite" news, it keeps going back to pixel launcher instead of Nova.
I had a crappy day and now I'm going to bed.

Welp! The Google (tm) is sending my replacement phone...

TWRP 3.3.0.0 Issue on Android 10
My phone is Google Pixel 2XL that is runnung under Android 10 and TWRP 3.3.0.0 img and installer.
I was unable to backup any ROM file under TWRP Recovery.
The error is "Backup Name is: 'PixelDust--14-59-50'
I:Backup_Folder is: '/data/media/0/TWRP/BACKUPS/710KPAE0324504/PixelDust--14-59-50'
I:Calculating backup details...
* Total number of partitions to back up: 3
* Total size of all data: 7486MB
* Available space: 46798MB
[BACKUP STARTED]
* Backup Folder: /data/media/0/TWRP/BACKUPS/710KPAE0324504/PixelDust--14-59-50
Invalid encryption mode 'ice:aes-256-heh'
Failed to mount '/system' (Invalid argument)
I:Actual block device: '/dev/block/bootdevice/by-name/system_a', current file system: 'ext4'
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/710KPAE0324504/PixelDust--14-59-50/recovery.log"
I had tried to flash Magisk.img but it did not work due to error.
The error log is "- Device platform: arm64-v8a
- Copying image to cache
1566+0 records in
1566+0 records out
1603584 bytes (1.5 M) copied, 0.006409 s, 239 M/s
1045+1 records in
1045+1 records out
1070668 bytes (1.0 M) copied, 0.004831 s, 211 M/s
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Unsupported/Unknown image format
! Installation failed"
I was unable to root on my phone.
How can I fix these issues?

Touareg2013 said:
My phone is Google Pixel 2XL that is runnung under Android 10 and TWRP 3.3.0.0 img and installer.
I was unable to backup any ROM file under TWRP Recovery.
The error is "Backup Name is: 'PixelDust--14-59-50'
I:Backup_Folder is: '/data/media/0/TWRP/BACKUPS/710KPAE0324504/PixelDust--14-59-50'
I:Calculating backup details...
* Total number of partitions to back up: 3
* Total size of all data: 7486MB
* Available space: 46798MB
[BACKUP STARTED]
* Backup Folder: /data/media/0/TWRP/BACKUPS/710KPAE0324504/PixelDust--14-59-50
Invalid encryption mode 'ice:aes-256-heh'
Failed to mount '/system' (Invalid argument)
I:Actual block device: '/dev/block/bootdevice/by-name/system_a', current file system: 'ext4'
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/710KPAE0324504/PixelDust--14-59-50/recovery.log"
I had tried to flash Magisk.img but it did not work due to error.
The error log is "- Device platform: arm64-v8a
- Copying image to cache
1566+0 records in
1566+0 records out
1603584 bytes (1.5 M) copied, 0.006409 s, 239 M/s
1045+1 records in
1045+1 records out
1070668 bytes (1.0 M) copied, 0.004831 s, 211 M/s
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Unsupported/Unknown image format
! Installation failed"
I was unable to root on my phone.
How can I fix these issues?
Click to expand...
Click to collapse
You really can't fix it until, and if, twrp is updated to deal with the new partition system that google implemented with A10. However, you can try this slightly outdated adb method that still works
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/

TWRP New install , New Phone issues fastboot

Did standard unlock bootloader (went fine)
Moved a TWRP zip onto phone sd root directory (twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.zip)
adp fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img. (went fine)
But when I look for the zip file (or any system files) it does not show up , even in TWRP file manager.
Redid data wipe and it tells me "Failed to mount /system_root and /vendor
I am 99% sure that its just because these will not mount:
Does anyone have any idea what I can do to get these mounted to start a regular TWRP flash ?

Well I tried adjusting data format and ended up losing the Stock Rom.
And the stuff will still not mount.
UPDATE, rewiped data and got stock rom to load.
Now Data will load but vendor will not.
UPDATE : data and vendor will mount after data wipe. But still cannot see anything that is placed on device.
Such as the zip files I need to install.
UPDATE: now I sideloaded TWRP onto new phone, but now cannot get it to reboot into Rom.
Its odd after plugging it in , it went to a stock recovery even when TWRP was installed.
Found the issues, finally had to run MSM download tool and fix everything from there and start from scratch.
Ended up installing TWRP from fastboot flash recovery image.
Now to get root going on it and magisk.

What device do you have?
You're in the 7T forum but saying you used the 7 Pro twrp.
If you're using 7T, the reason why you don't see internal storage is because TWRP cannot decrypt on OOS (this is not because of a mounting error, this is simply due how oneplus has implemented their encryption).
And on 7T you don't need a zip of any sort to install twrp.
Reading the actual twrp thread would be a good start.

Lossyx said:
What device do you have?
You're in the 7T forum but saying you used the 7 Pro twrp.
If you're using 7T, the reason why you don't see internal storage is because TWRP cannot decrypt on OOS (this is not because of a mounting error, this is simply due how oneplus has implemented their encryption).
And on 7T you don't need a zip of any sort to install twrp.
Reading the actual twrp thread would be a good start.
Click to expand...
Click to collapse
Yes, I read though the threads, But got so bombarded with pages of stuff kind of lost track.
This is why I posted . Also it is a combined Christmas gift for my daughter that she cannot know I am working on. So I think I tried to rush it when she was in school.
Found out about the decryption part after I started the process. Then it was too late and ended up having to start over with tools.
It was a newb move to end up this far and try to rush it.
People did help me get back on track and now I am working on figuring out Magisk. (good help on magisk threads).
Thanks for your response.

eracet said:
Well I tried adjusting data format and ended up losing the Stock Rom.
And the stuff will still not mount.
UPDATE, rewiped data and got stock rom to load.
Now Data will load but vendor will not.
UPDATE : data and vendor will mount after data wipe. But still cannot see anything that is placed on device.
Such as the zip files I need to install.
UPDATE: now I sideloaded TWRP onto new phone, but now cannot get it to reboot into Rom.
Its odd after plugging it in , it went to a stock recovery even when TWRP was installed.
Found the issues, finally had to run MSM download tool and fix everything from there and start from scratch.
Ended up installing TWRP from fastboot flash recovery image.
Now to get root going on it and magisk.
Click to expand...
Click to collapse
Magisk IS your root

Flashing custom ROM assistance

Hi I've been away from the aftermarket ROM game for a while and I'm having a bit of trouble installing. Can anyone link to some instructions. All i could find was the ones posted by the Lineage Team but i am unsure if they are universal instructions or if they are only for Lineage. Some assistance would be great!
So details of what I've tried thus far:
Flashing from recovery (i assume this method is pretty much legacy at this point) -
reboot to recovery
factory reset
flash rom
While attempting this method I was unable to find a way to get the ROM zip on my device in an accessible fashion do to encryption, adb push never completeing, unable to mount external storage, and MTP not allowing me access to internal storage. (this is all with TWRP version 3.6 and 3.5 (the two newest as of this post))
ADB sideload -
Booted into TWRP and started the sideload channel
ran adb sideload <zip file>
this just sits and never progresses
I am using the adb and fastboot versions listed below:
ADB - 31.0.3
Fastboot - 31.0.3
I am also running Linux, I have tried using USB 2.0 as well as 3.0 (both had the same results). I have tried different cables (also same results).
Please let me know if any more information is needed to figure this out.
Thanks.

Some roms are designed to flash from fastboot, others from recovery.
Also, TWRP's failure to decrypt should only apply to Android 12 roms - but for those you'll need to format data (after a backup of course).
So tell us which rom you want to flash. Also see the rom's thread - generally, other users will have faced the same problems.

runekock said:
Some roms are designed to flash from fastboot, others from recovery.
Also, TWRP's failure to decrypt should only apply to Android 12 roms - but for those you'll need to format data (after a backup of course).
So tell us which rom you want to flash. Also see the rom's thread - generally, other users will have faced the same problems.
Click to expand...
Click to collapse
Sorry for the late reply, at the time I had just went back to the OS is was already running simply because they have a script to handle install. Though Right now I really want to at least go back to LineageOS, CalyxOS (the ROM on running now) is just too restrictive.
I know I've had issues installing LineageOS before and at that time I found away around it to get it installed but I don't remember what I did...
So this is what happens I When following the instructions here I always run into issues gaining access to the zip file in recovery/sideloading via ADB. I think last time I installed it I was able to boot to Lineag Recovery and sideload from there but sideloading in TWRP doesn't seem to work for me. and If I try to access the zip from TWRP (to flash in recovery) it's never there or errors out.
I think im going to try again today and will post any errors.

So i just remembered I can adb push and access an external drive while in slot_b but not slot_a.
Edit: NVM cant adb push on either slot in TWRP

So I just installed Lineage Recovery but sideloading doesnt progress at all just sits at verifying signature. I'll post in the lineage thread and post back here if I figure it out.

ok figured it out. Had to place the zip on an external drive, make sure my phone was in Slot A, boot TWRP, mount the external drive and flash from there, I got a few errors saying it couldn't mount /Vendor but it seems to work

deathblade said:
ran adb sideload <zip file>
this just sits and never progresses
Click to expand...
Click to collapse
Try connecting the phone through a USB hub. I had the same issue and this was how I resolved it.