Hi,
i just wanted to flash the Dirty Unicorns ROM after I installed CM12S. I installed TWRP, unlocked the bootloader and then wiped system, dalvik, cache and data. Flashed DirtyUnicorns 9.5 official and GApps but when I tried to restart I was stuck at bootloop. And now I can not even push the CM12S zip file via ADB push in recovery. It just doesn't recognize my phone in ADB devices. I can get into fastboot and it does recognize my phone.
I suppose it's because USB Debugging turned itself off... Is there a way to enable it from recovery or fastboot?
PLEASE, what can I do to resolve this problem?
Thank you very much for a swift and fast replies.
You can't enable adb via recovery, it needs to have been done previously in the OS. Use fastboot to flash the stock images, see section 8 of my guide:
http://forum.xda-developers.com/showthread.php?t=2839471
This will at least get your phone booting again. Just don't flash the userdata image or you'll wipe your storage.
Related
I reset my Oneplus one and installed the COS13.1 update.... But now after installing I'm not able to flash twrp through fastboot... Even tho it shows successful on the PC, it wing boot into TWRP
Go to the developer options (tapping on the build number first ofcourse) and then go to the option: "update Cyanogen-recovery". set it to off.
I think that should do it. Haven't installed the update yet, but there is an option like that in the normal CM-13.
edit:
If that doesn't work you can try to flash it through flashify (requires root). If that still doesn't work you can also boot TWRP through fastboot and then install the IMG through TWRP itself (like updating your recovery)
You can boot TWRP via fastboot with using the boot command instead of the flash command:
fastboot boot "image.img"
Still showing that it's failed
Could you boot TWRP without flashing via fastboot? Because if you can do that it means that the system is automatically reflashing the stock recovery at startup.
How did you installed (tried to install) the recovery?
fastboot?
Follow this. TWRP 3.0.2 can be installed this way. 2.8.6 sometimes doesn't.
1. Turn off option to Update Cyanogen Recovery from Developer Options.
2. Flash Recovery via fastboot, the put command to clear cache from fastboot only. DONT REBOOT NOW.
3. Disconnect phone and turn it off.
4. Try booting to recovery. If it fails, dont worry let the phone boot normally then try again. It should work.
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.
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).
Hi,
First of all, yes, I have checked the other threads that talk about reverting to stock and I am still stuck.
So I installed Kang OS which is Android 11, and now I want to revert to stock. I have tried downloading multiple different versions of the fastboot ROM from the page https://androidfilehost.com/?w=files&flid=294300 and run the flash all batch file and every time I am either getting stuck in a boot loop or getting the Verity Crash Dump Screen. I have managed to reach the fastboot screen, and I am waiting on the fastboot screen, for someone to show me some way.
Thanks in Advance.
If you used a pin then your storage is encrypted and the rom you are trying to flash can't use it, that's why you're most likely stuck at boot.
I ran into the same issue and posted about it in the same thread. I think we will need a new version of TWRP as 3.4.0-0 would not accept my pin which had not changed.
To fix your issue, sadly, you'll need to wipe your storage:
Boot the phone into fastboot mode
Attach your USB cable to the phone/PC
Download and unzip the file I've attached (ADB/Fastboot)
Launch an elevated command window in the folder you extracted the attached zip to
Try the command fastboot devices and ensure that it reports the device correctly, if not then you need to install the latest OnePlus drivers
Type the following in the command window : fastboot -w (This will wipe the storage)
Try your rom again (TWRP should remain as the recovery if you had flashed it already, if not then copy the latest TWRP img file to the same folder as the ADB/Fastboot tools, use fastboot and type boot twrpfilename.img this will make the phone boot into TWRP recovery, you can then copy over the TWRP zip and flash it to recovery using the booted version of TWRP)
Once you've done the above you shouldn't really need to use the fastboot scripts as the latest rom should just flash from TWRP.
Get msm download tool for guacamole which is the codename of the op7p. I know the shorts with the global version I am unsure if this works with T-Mobile or others?
MSM is a bit of a severe fix when they've already confirmed they can still get fastboot, MSM is for completely bricked phones that can't access anything. Wiping the storage and going to fastboot will allow them to just flash recovery then flash the stock rom. Way easier.
Boot into twrp. Then format data. Phone will boot then.
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