Hi,
Yesterday my WileyFox Spark+ came in, which is still equipped with COS13.0.1, based on Android 6.0.1.
When I tried rooting the phone, I got stuck at the point of using TWRP for flashing SuperSU.zip.
Until then, I had succesfully followed the following process:
-Enabled 'OEM Bootloader allowed to be unlocked' in Developer Options
-Installed USB drivers and such on PC
-Enabled USB debugging, apps from unknown sources, ADB install unsigned apps allowed etc.
-Unlocked bootloader like this in CMD:
fastboot devices (my phone showed up)
fastboot flashing unlock
I pressed volume up button (yes)
I selected boot mode fastboot
-Flashed TWRP Recovery to phone like this in CMD:
fastboot flash recovery twrp3100.img
-I booted into TWRP recovery
A lot of folders and some files were present there, but almost all folders were 'empty'. I couldn't reach my SC-Card with SuperSU.zip on it.
TWRP even said no OS was installed when I wanted to reboot to retry.
I was confused for a while, only to discover the OS was still there after booting into System.
I tried to flash SuperSU from ADB, but that also didn't work. I issued the following commands in CMD:
adb reboot recovery
(ticked adb sideload in TWRP +wipe dalvik & cache)
adb sideload supersu279.zip
TWRP said it executed succesfully, but failed to access /data and /cache.
It was at this point that I discovered the phone was encrypted already from the box. I had never considered this as an option.
It's weird though, because I have heard that flashing SuperSU from ADB should work even with an encrypted phone.
Now the interwebs and WileyFox themselves say Encryption is disabled when you factory reset the phone. So I did that, but it just booted into TWRP with the same circumstances.
Few folders, almost all empty. SD-card not visible.
I tried sideloading SuperSU again, but without result.
Any idea how i should progress further? 'Cause I have run out of ideas..
Is it possible to flash SuperSU via fastboot or anything?
I have found a LineageOS 13 ROM for my phone, but it's a .zip so I don't think I can use it.
Anyway, any help would be greatly appreciated!
Cheers.
NB: I don't care about encryption, i'd rather have it gone, but whatever option is best for rooting this thing will work fine for me.
Related
Hi,'
I think I disabled google app on my nexus 5 (stock android) and since then my phone is stuck in boot loop. (My phone does not go past logo of marshmallow rolls or message saying starting apps 10 of 10). I have very important data that is not yet backed up and I need them to be recovered.
From various threads, I did following in recovery mode
1. Wipe cache option under recovery menu - as it was mentioned, that it would not delete any user data on my sdcard. (No help, still stuck with boot loop)
2. In recovery mode - there was an option to mount phone memory and I did that. My phone shows a message at the bottom of the screen that it is successfully mounted. But I am not familiar how to proceed further or to recover data from my phone.
My phone is running stock android and I think I have not disabled USB debugging. I am not familiar about ADB, but can follow your guidelines and execute them. When I connect my phone to windows laptop, I see my laptop trying to install the MTP device driver, but fails saying unable to find the driver.
I need to recover my data and Any help is greatly appreciated.
Is your bootloader unlocked? I'm guessing not.
Sent from my Nexus 5X using XDA Free mobile app
If the bootloader is unlocked, you could flash twrp and then mount the data partition from twrp. If the bootloader is not unlocked, you could try pulling the data from the phone using adb commands. Was debugging enabled in the rom?
I have not unlocked my boot loader. Is there a guide to use adb with stock android?
Only if you enabled debugging in developer options.
Today, I installed 15sec ADB installer and booted my device in to recovery mode by pressing power and volume keys.
Then under recovery menu there was an option called - Mount / System. I selected it by pressing power key and from ADB ran adb devices.
No devices was listed, when I ran ADB devices.
But I saw another option in my phone recovery screen - Apply update from ADB.
I got a message in phone - "Now send the pacakge you want to apply to the device with adb sideload filename".
Now, when I execute ADB devices in my PC cmd prompt, I see my device with its serial number.
then I tried to use ADB Pull /sdcard/ to recover files from PC command prompt. But I got a message - saying error closed.
Am I doing the right things? Can you guys guide me to recover files from this point.
My bootloader version is HHZ20h. Product - Hammerhead.
I noticed from below link a user has had luck with sideloading a launcher. Has anyone here tried it ? will it affect my data on phone?
https://code.google.com/p/android/issues/detail?id=64773#c22
Any guide to sideload google search app in recovery mode?
Have you considered side loading the OTA from Google? https://developers.google.com/android/nexus/ota Directions are on the site.
When you get to this point
(But I saw another option in my phone recovery screen - Apply update from ADB.
I got a message in phone - "Now send the package you want to apply to the device with adb sideload filename".), you send the ota zip. (Adb sideload <name of zip> ). You have to make sure the zip file is in the folder with adb files.
Sent from my Nexus 9 using Tapatalk
I tried to install OTA update and did the reboot. But it did not help.
Can anyone provide me a launcher that I can sideload in recovery mode? Reading from various threads, I think my phone is in this state because I disabled the google app, which is also the launcher.
Thank you
Try to flash system image without userdata wipe and wiping only cache
Sent from my fx-82MS CAF using Tapatalk
santi1993 said:
Try to flash system image without userdata wipe and wiping only cache
Sent from my fx-82MS CAF using Tapatalk
Click to expand...
Click to collapse
How to perform this flash without wiping my user data? Any guide for it?
Download the stock image from Google that matches the rom currently installed on the phone, extract system.img, boot phone into fastboot mode, and type fastboot flash system system.img at the command prompt, and reboot.
audit13 said:
Download the stock image from Google that matches the rom currently installed on the phone, extract system.img, boot phone into fastboot mode, and type fastboot flash system system.img at the command prompt, and reboot.
Click to expand...
Click to collapse
Let me try it. so far I have been able to execute only adb sideload commands, after choosing Apply update from ADB.
Let me try this - fastboot flash system system.img.
smartey said:
Let me try it. so far I have been able to execute only adb sideload commands, after choosing Apply update from ADB.
Let me try this - fastboot flash system system.img.
Click to expand...
Click to collapse
Boot ur phone in fastboot mode (From power off to vol down + power), then connect it to the pc and install latest_google_drivers for nexus devices, ull need to manually install them, after that ur fastboot will recognize ur device.
From that type fastboot devices, if u see ur device connected u simply need to get into the commands that the other user gave to you, i u are lucky ur device will boot.
if u had unlocked bootloader the thing was easy as installing twrp 3.0.2.0 and backup all ur data via MTP
Maybe it's me not understanding what's new, I've "rooted" quite a few phones going back to the OG Droid - Motorola, Samsung, HTC. Never had any significant issue following directions and getting it done. Maybe things have changed over time. OG Pixel, 128GB, with sailfish-opr3.170623.008 (8.0.0). Auto-update disabled, USB debugging enabled, bootloader unlocked.
Setup: twrp-3.2.1-2-sailfish.img in platform-tools with adb and fastboot (latest versions). twrp-pixel-installer-sailfish-3.2.1-2.zip and Magisk-v16.0.zip at root of "Pixel/Internal Shared Storage". I also extracted a fresh boot.img from a factory image.
Just to make sure I'm starting fresh:
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot --slot other flash boot boot.img
So far so good.
Code:
fastboot boot twrp-3.2.1-2-sailfish.img
TWRP comes up, I give it my PIN, it says decrypt OK, I tell it to install twrp-pixel-installer-sailfish-3.2.1-2.zip. Install seems fine, no errors reported. Back up a couple of levels, and "reboot recovery." It tries, eventually goes to a black screen for a few seconds, then does another reboot to system. No TWRP. Am I wrong in thinking I should be in TWRP at this point?
I can do the above, but flash Magisk-v16.0.zip instead, and I do end up with root, so that works. Just no way to get to TWRP except by fastbooting an external image.
I've also tried installing VerifiedBootSigner-v8.zip after installing twrp.zip, but that fails at the end with an "unable to verify..." or similar message. I'm not sure if that's supposed to be required or not currently, the TWRP install instructions don't mention it, but other guides do.
What am I doing wrong?
All I've ever done was boot to fastboot, adb boot <path-to-twrp>.img, and flash twrp. No need to use the boot signer anymore.
Sent from my Pixel using Tapatalk
Well, I can only guess that twrp-pixel-installer-sailfish-3.2.1-2.zip isn't compatible with the boot image in sailfish-opr3.170623.008.
I installed sailfish-opm1.171019.021-factory-68d3b69a.zip, then the twrp (and Majesk) install worked, just as expected.
So I was stupid enough to wipe all partitions (Data, system, internal storage etc) thinking that I'll do a super clean install of the new update.
Now I flash the new file (which I downloaded from the official website), it flashes just fine but gives me a bootloop.
I have (or had) root and can flash TWRP fine.
What else can I do to get back any running rom?
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Hopefully this will help you like it did with me .
Try flashiing stock boot.img from adb or try to the unbrick tool
Absolutely nothing at all worked, not even in the slightest, everything gave me a boot loop. Except for one thing; I flashed the Open Beta DP3 zip file in twrp and that worked, then I use set it up and used the rollback-to-stable release file to revert to stable release.
I see absolutely no logic behind how and why this worked and not the other traditional methods though, anyone have any clarification on this please?
Thank you for your responses though guys, much appreciated!
If you can still access TWRP recovery, try sideloading a rom via fastboot on a Windows PC. Boot to TWRP > Advanced > Sideload. On your Windows machine - Open fastboot and type "adb sideload *rom name*.zip. See if that works. If sideloading fails for whatever reason but you can still access TWRP try pushing the rom to internal storage by using fastboot again. Boot to TWRP on your phone and do nothing else. On your Windows machine open fastboot and type "adb push *rom name*.zip /data/media/0" this will push the rom to your internal storage.
railpressureflip said:
Absolutely nothing at all worked, not even in the slightest, everything gave me a boot loop. Except for one thing; I flashed the Open Beta DP3 zip file in twrp and that worked, then I use set it up and used the rollback-to-stable release file to revert to stable release.
I see absolutely no logic behind how and why this worked and not the other traditional methods though, anyone have any clarification on this please?
Thank you for your responses though guys, much appreciated!
Click to expand...
Click to collapse
the most important thing you missed mentioning was which ROM were you ON when you wiped everything?
bcz if it was using an August security patch, and if you tried to go back to a july one without formatting data you were bound to get bootloops.
glad that it finally worked though.
but if you wanna try again, be sure to format data and your super clean install will go through.
wipe everything
format data
reboot fastboot
fastboot boot recovery
adb push stock stable ROM
flash via twrp
adb push twrp zip
flash twrp zip
reboot
now you will be fine.
speedyjay said:
If you can still access TWRP recovery, try sideloading a rom via fastboot on a Windows PC. Boot to TWRP > Advanced > Sideload. On your Windows machine - Open fastboot and type "adb sideload *rom name*.zip. See if that works. If sideloading fails for whatever reason but you can still access TWRP try pushing the rom to internal storage by using fastboot again. Boot to TWRP on your phone and do nothing else. On your Windows machine open fastboot and type "adb push *rom name*.zip /data/media/0" this will push the rom to your internal storage.
Click to expand...
Click to collapse
Thank you very much! Sideloading rom worked for me (OP6T).
I went through the process of using Smali and Magisk on my phone. Everything was good. Since I was doing this for PoGo, I decided to "clean-up" by disabling some of the settings. I turned off OEM unlocking, reboot the phone in to the bootloader and did a adb flashing lock. I rebooted the phone and not get the error "Can't find a valid operating system". I can boot in to the bootloader with the power button + down volume but I can't unlock the bootloader with ADB and fastboot.
Am I screwed?
I'm also not able to boot in to recovery. I also get the error "Can't find valid operation system"
Well probably too late to reply.
I'm not an expert, i'm newbee but when i installed my custom rom i met some problems to reboot. I solved them by re-installing firm operating system. You can do it by connecting your device with a good usb cable and go to google website : android flash tool
This will reinstall a new an clean system (but erase your data if not saved before).
After that you can install a custom rom from the begining.
As title says, by mistake I have wiped everything: Dalvik Cache, System, Data, Internal Storage, Cache, Micro SD. Everything.
How did this happen? Well, yesterday I ran into some problems after first rooting my 7PRO on Friday night. I couldn't get past the unlocked bootloader message. So eventfully I just decided to boot into TWRP and wipe the device. Not understanding what I was doing I chose wipe and ticked all the above listed items. I should have just done a factory reset I'm aware now.
I can't get past the fastboot screen. I select recovery mode and it just sends be straight back to fastboot. I figured I would just sideload a custom rom through TWRP, but I cant get back to it again. I cant install TWRP because my phone isn't detected on my computer now.
I'm hoping this is fixable. Because I'm fairly certain I cant get back from this. Maybe someone has some fixes. Cheers
Is the phone detected in fastboot mode?
Install the system wide adb-fastboot drivers.
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
If you can get the phone to be detected in fastboot mode you could send some commands to reboot into recovery mode or try flashing twrp again