I was trying to root my Google Pixel, and after booting the image file and the phone rebooted, it's stuck on the dancing dots.
How can I fix it?
Yakuzahi said:
I was trying to root my Google Pixel, and after booting the image file and the phone rebooted, it's stuck on the dancing dots.
How can I fix it?
Click to expand...
Click to collapse
Mine did that. I forced it to power down, then booted normal to verify it was ok. Then did it again and it was fine.
Sent from my Pixel XL using XDA Labs
TonikJDK said:
Mine did that. I forced it to power down, then booted normal to verify it was ok. Then did it again and it was fine.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
I did power it down but to boot and only runs on the dancing dots.
Yakuzahi said:
I was trying to root my Google Pixel, and after booting the image file and the phone rebooted, it's stuck on the dancing dots.
How can I fix it?
Click to expand...
Click to collapse
I have read other people having same problem, they were mostly using outdated android tools
mac796 said:
I have read other people having same problem, they were mostly using outdated android tools
Click to expand...
Click to collapse
The problem is that I was on 7.1.1 and the root method was for 7.0.
Yakuzahi said:
I was trying to root my Google Pixel, and after booting the image file and the phone rebooted, it's stuck on the dancing dots.
How can I fix it?
Click to expand...
Click to collapse
Yakuzahi said:
The problem is that I was on 7.1.1 and the root method was for 7.0.
Click to expand...
Click to collapse
Mine did the same but I figured out because I was using the minimal adb . I started out on 7.1 though
Yakuzahi said:
I was trying to root my Google Pixel, and after booting the image file and the phone rebooted, it's stuck on the dancing dots.
How can I fix it?
Click to expand...
Click to collapse
Hey, I also happened to foolishly apply the root method for 7.1.0 after I OTA updated to NMF26Q. Here's what I did to fix this (I assume you know your way around the command line, if not just let me know):
0) Ensure that adb and fastboot are installed on your computer, you can search in the web for installers or get the Android SDK installer.
1) Boot your phone to the bootloader. Whether it is powered off or at the dancing dots, hold power until it vibrates, then release the power button and immediately hold power and volume down.
2) Go get the TWRP RC1 ZIP and boot image here, if your phone is the XL version change sailfish to marlin in the URL.
3) Open up a terminal/command prompt, change the directory to where you downloaded the two files above. Then enter:
Code:
fastboot boot twrp-3.0.2-0-RC1-fastboot-sailfish.img
4) The command line should tell say OKAY and your phone should now be in TWRP. You should also be able to access internal storage, you need to place the zip file in there.
5) Tap install, find the TWRP zip file you downloaded, then flash. Don't reboot yet, go back to the main menu, tap reboot then tap recovery.
6) Since you flashed TWRP this will be the recovery now and you no longer need the boot file. Now download the latest SuperSU zip found here, flash it and reboot normally, and you are done!
Thank you for this, @techhexium! It's hard to tell versions from chainfire - I really thought I had a 7.1.1 version of boot-to-root.img. Apparently I was wrong, since I got stuck atthe dancing dots, too. I set up with TWRP latest (which is still 3.0.2-0-RC1) and the latest SuperSu, and I can boot again. Worth noting, instead of the specific superSu version you linked, it's better to get the latest release from chainfire.eu . 2.79SR1 in particular has a compatibility fix with TWRP that's important.
Related
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
nexus_5_ said:
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
Click to expand...
Click to collapse
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Thank you very much for the reply, I really do have no idea as to how to flash the factory image because i am very new in this area. Could you please recommend software and which factory image i should download, please ?? thanks very much.
:good:
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Also, you mentioned a 'special kernel' what does that mean. All i want to do to my device is install cyanogenmod 12 and for that i believe it needs to be rooted, so i am really confused. What should I do know
I'm having this same problem, and unfortunately, when I start the phone on fastboot, I can not access the recovery mode in order to upload a factory image of nexus 5.
I used the new tool available her for quick flash, and now, I don't have a phone.
First, don't panic. Your phone is still very easy to recover. Unfortunately I can't get you a complete walkthrough here (for now at least), so I'll give you the main idea and you'll have to do your homework (as maybe you should have done before).
1. You need to get fastboot working on your computer. It's included in the Android sdk package, but there might be some easier way to get it. Google it. You might need drivers for your pc too. Google it as well.
2. Then you need to get into fastboot mode on your phone. To do it, hold down power button AND volume down button until it gets into fastboot mode. You will see an android on his back with the cover open. At this point, connect your phone to your pc, open a terminal on your pc and type "fastboot devices" without the quotes "". It should find your phone if fastboot is working. If it doesn't work go back to step 1.
3. Download TWRP recovery on your pc and place the img file in the same folder as your fastboot executable (not mandatory but easier). It can be found here https://dl.twrp.me/hammerhead/
4. Always in fastboot mode, type "fastboot flash recovery twrp-2.8.7.1-hammerhead.img" assuming you downloaded that file, which you should have by the way. It should install fine. If you haven't placed the file in the same directory as your fastboot executable, you will need to provide the path to your img file as well.
5. Then use the volume rocker to switch between modes and choose reboot recovery.
6. You should now be in TWRP recovery. At this point, download a custom kernel (anyone found on xda for hammerhead should do) and push it to your phone. It should be fairly simple with TWRP. Then flash your new kernel using install. It should help you get your phone booting normally. Alternatively, you can download a custom ROM like cm12.1 and flash it altogether. It will install everything needed for your phone to boot up too. Beware if flashing a ROM though, I strongly advice you to do a factory reset before flashing it. You will find that option in the wipe menu.
Hope it helps, let me know if you need further assistance.
Yesterday, I have tried everything to have my computer to recognize the "fastboot" command, and I installed like 2 or 3 different programs for that. With my old Windows 7, I have been able to push a flashed image to fix this issue, using the fastboot command, but with Windows 10, it's always telling me it's not a valid command. I'll keep trying it, otherwise, i'll have to "resurrect" my old Windows XP computer.
Also, I noticed now that, while trying to install the fastboot, as per some files that I could download, but no file has been copied into my computer, not even if I run it as admin.
fixed. but no RECOVERY mode options....
Hi Guys,
Thank you very much for the help, I have finally recovered the phone and running android 6.0 MRA58N but it is not rooted. Now if you don't mind could you teach me how to root because i have checked lots of videos and tuts but none worked for me...
IMPORTANT:
when i am in recovery mode why cannot I access options even when i press volume up + power button and release them at the same time...????
Thanks in advance.
Just flash a custom recovery via fastboot. Just make sure your bootloader is unlocked. Can't link though.
hi guys i have used nexus 5 mobile with cyanogenmod 14.1 .It worked properly in 1 year. after that suddenly switched off and it not properly boot up .i try to switch on my mobile , first it show google with unlock logo properly and when it show cyanogenmod logo it stuck and again show google with unlock logo....i try recovery mode to wipe and flash the same rom ....the process is interrupt at middle stage and again show the google..i try lots of time . after few try that process finished completely without interrupt. then use my mobile 1 day same as i used first time root. after that same problem occur on my mobile ..so help me guys
@[email protected], possible power button problem?
A burst of fearsome energy overtook me tonight and I just had to root my phone
Kingoroot, Kingroot, Towelroot etc didn't work. Then I read about this thing called TWRP.. sounds great, I said.
Unlocked the bootloader, got TWRP recovery going, tested it out, got ready to add SuperSU and the one that gets rid of bootloader unlocked screen.
Boot loop. Stuck on the Motorola logo. It aint going anywhere.
I've tried all of the suggestions I could find so far here, like using mfastboot to clear cache and user data. It's looking like a dead end. I was following the instructions on a youtube video so of course I didn't back up anything before I tried SuperSU Should I cut my losses and try the stock firmware, or could I do more damage that way?
This is going to ruin my weekend, isn't it?
bootloophell said:
A burst of fearsome energy overtook me tonight and I just had to root my phone
Kingoroot, Kingroot, Towelroot etc didn't work. Then I read about this thing called TWRP.. sounds great, I said.
Unlocked the bootloader, got TWRP recovery going, tested it out, got ready to add SuperSU and the one that gets rid of bootloader unlocked screen.
Boot loop. Stuck on the Motorola logo. It aint going anywhere.
I've tried all of the suggestions I could find so far here, like using mfastboot to clear cache and user data. It's looking like a dead end. I was following the instructions on a youtube video so of course I didn't back up anything before I tried SuperSU Should I cut my losses and try the stock firmware, or could I do more damage that way?
This is going to ruin my weekend, isn't it?
Click to expand...
Click to collapse
If you can still boot to your custom recovery its really not a big deal. Just install the ROM zip of your choosing and appropriate gapps. If you are boot looped when it starts to reboot just hold in the power button for about 10 seconds till it powers off then press and hold volume down while still keeping the power button pressed. After about 5 seconds or so of holding both buttons stop pressing both together. If done correctly you should be at the boofloader screen.
n0ts0smart said:
If you can still boot to your custom recovery its really not a big deal. Just install the ROM zip of your choosing and appropriate gapps. If you are boot looped when it starts to reboot just hold in the power button for about 10 seconds till it powers off then press and hold volume down while still keeping the power button pressed. After about 5 seconds or so of holding both buttons stop pressing both together. If done correctly you should be at the boofloader screen.
Click to expand...
Click to collapse
Yes, I can get to the bootloader. Factory reset there and reset using TWRP doesn't fix the bootloop. That's kinda where I am right now.
Uninstalling SuperSU did it! I used the un-su zip file.
Do you have one of the following 1)Motorola USB drivers for your PC and fastboot or mfastboot/adb setup for your device? 2)ROM zip on your internal storage. 3)A USB OTG drive? Any of these will work. Let me know which you have and we will go from there.
n0ts0smart said:
Do you have one of the following 1)Motorola USB drivers for your PC and fastboot or mfastboot/adb setup for your device? 2)ROM zip on your internal storage. 3)A USB OTG drive? Any of these will work. Let me know which you have and we will go from there.
Click to expand...
Click to collapse
It's ok, I'm back in business - the issue was the installation of the latest version of SuperSU. I used Install from SD Card in TWRP to install the SuperSU remover and it booted fine.
Taking my time now because I need this phone, I'm living in a new country. I backed up and tried an older SuperSU but didn't work - I suppose by doing a factory reset I might have done something that stops a root.
Edit: this http://forum.xda-developers.com/showpost.php?p=63615067
Download the latest stable build of super SU from Chainfires site here. http://download.chainfire.eu/supersu-stable
Then just flash the zip you downloaded in TWRP. You don't need the systemless version of SU if that is what you were trying to do.
n0ts0smart said:
Download the latest stable build of super SU from Chainfires site here. http://download.chainfire.eu/supersu-stable
Then just flash the zip you downloaded in TWRP. You don't need the systemless version of SU if that is what you were trying to do.
Click to expand...
Click to collapse
I think that was the one that bootlooped it. I'll be doing a backup first this time
My main reason for posting my solution in this thread is in case the same thing happens to someone else. Removing SuperSU with that un-su.zip solved it for me.
Hi all,
This is not the right forum, but I didn't see one specifically for Spark X models, so I'm sorry.
A friend of mine has a Wileyfox Spark X device, which was bootloader unlocked, had TWRP 3.0.2 installed and was running on the original firmware (6.0.1) but rooted and xposed installed.
Now an update came out for Android 7. To update the device, I put back the original firmware and recovery, started doing the upgrades and all went smooth.
Device is up and running on Android 7, however when I now try to install TWRP again, it won't work.
(fastboot flash the TWRP recovery (same version as before - 3.0.2) seems to work ok. I then go to pull the battery after flashing, put battery back, and start recovery by pressing vol down and power.
I see the device going to a black screen, then reboot and keeps doing this as long as I keep the vol down pressed. Once I release the device continues normal boot and goes into Android.
I assume this has to do with a change in Android 7?
Seems I can get TWRP working again, if I flash the original boot image, however then ofcourse the Android boot doesn't work anymore. (additionally once in TWRP, it seems /system cannot be mounted anymore and TWRP thinks no system is installed)
So in short, I believe I should get a newer TWRP version that is compatible with Android 7. I tried the different versions available on twrp.me (up to 3.1.1.0) however to no avail. None works with the latest android.
As such, the device is able to run in android 7, but without root. (no adb root option in developer options, adb root doesn't work either, kingroot etc also no go)
Does anyone have any options that I can still try? or could help me with a proper TWRP version that should work? (I did find some TWRP recoveries on 4pda (russian website) for Spark + that claim to be for Android 7, but those didn't work either))
Thanks !
@Asansi
I'm sorry I can't help you, but may I ask how you rooted the phone? I can't get mine to be properly rooted.
I can help you with any problem. I'm a senior person in that model since I have been using it ever since. If you could like
Sent from my Wileyfox Spark using XDA
HackerAce said:
I can help you with any problem. I'm a senior person in that model since I have been using it ever since. If you could like
Sent from my Wileyfox Spark using XDA
Click to expand...
Click to collapse
Apologies for ressurecring a zombie thread but, OP has a spark X and you have a Spark, so it would appear that you SENIOR person in that model failed at the very first hurdle.
Am still wonderng if there is an sign of a 7.0 compatible twrp for spark X? Don't suppose anyone has a link to the latest Spark X firmware either?
TWRP versions
Asansi said:
Hi all,
This is not the right forum, but I didn't see one specifically for Spark X models, so I'm sorry.
A friend of mine has a Wileyfox Spark X device, which was bootloader unlocked, had TWRP 3.0.2 installed and was running on the original firmware (6.0.1) but rooted and xposed installed.
Now an update came out for Android 7. To update the device, I put back the original firmware and recovery, started doing the upgrades and all went smooth.
Device is up and running on Android 7, however when I now try to install TWRP again, it won't work.
(fastboot flash the TWRP recovery (same version as before - 3.0.2) seems to work ok. I then go to pull the battery after flashing, put battery back, and start recovery by pressing vol down and power.
I see the device going to a black screen, then reboot and keeps doing this as long as I keep the vol down pressed. Once I release the device continues normal boot and goes into Android.
I assume this has to do with a change in Android 7?
Seems I can get TWRP working again, if I flash the original boot image, however then ofcourse the Android boot doesn't work anymore. (additionally once in TWRP, it seems /system cannot be mounted anymore and TWRP thinks no system is installed)
So in short, I believe I should get a newer TWRP version that is compatible with Android 7. I tried the different versions available on twrp.me (up to 3.1.1.0) however to no avail. None works with the latest android.
As such, the device is able to run in android 7, but without root. (no adb root option in developer options, adb root doesn't work either, kingroot etc also no go)
Does anyone have any options that I can still try? or could help me with a proper TWRP version that should work? (I did find some TWRP recoveries on 4pda (russian website) for Spark + that claim to be for Android 7, but those didn't work either))
Thanks !
Click to expand...
Click to collapse
I've tried TWRP 3.0.2-0 (i.e. latest from https://dl.twrp.me/porridgek3/): it flashes Ok but it won't boot up afterwards. I've tried 3.0.2-0 but as you say "it seems /system cannot be mounted anymore and TWRP thinks no system is installed)". After letting it finish, Root Checker (not unsurprisingly) says that device is not rooted. Have you progressed with this issue? BTW I've emailed TWRP Support (from their web page) asking if they have a working version.
Same problem here, It's pretty annoying. My sister's getting this same phone (on Android 6) soon so I might just make a full backup with TWRP on it and somehow restore it on my phone.
Systemless Root
I can't decide whether to try the rooting method given in https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung
The method is:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Has anyone had experience of this method?
Resurrection! This post shall LIIIIVE!
No, seriously tho, does anyone have any updates on the issue? Or could at least point me in the right direction to root a Wileyfox Spark X? At this point, any help is much appreciated, since I have not been able to get ANY method working for me.
Thanks a lot
Sent from my Wileyfox Spark X using XDA Labs
Systemless Root
ScreamingSteve said:
Resurrection! This post shall LIIIIVE!
No, seriously tho, does anyone have any updates on the issue? Or could at least point me in the right direction to root a Wileyfox Spark X? At this point, any help is much appreciated, since I have not been able to get ANY method working for me.
Thanks a lot
Sent from my Wileyfox Spark X using XDA Labs
Click to expand...
Click to collapse
Steve,
Have you tried the method detailed in post #7?
johnaaronrose said:
Steve,
Have you tried the method detailed in post #7?
Click to expand...
Click to collapse
I am afraid not, since I can't install TWRP. One info would help me out a lot tho: would an Android-Downgrade (from 7.0 to CM13) help with installing TWRP and rooting?
Steps taken earlier:
quite literally everything (that would make sense even remotely)
Steps taken today:
- Downloading TWRP 3.2.1-0 (https://twrp.me/wileyfox/wileyfoxsparkx.html)
- fastboot-unlocking the bootloader (no issues)
- trying to install TWRP (no issues there either)
- when trying to reboot straight to recovery, I don't get past the bootlogo, suggesting to me that either the install or TWRP was corrupted.
Any help one might get?
Thanks a lot?
TWRP
ScreamingSteve said:
I am afraid not, since I can't install TWRP. One info would help me out a lot tho: would an Android-Downgrade (from 7.0 to CM13) help with installing TWRP and rooting?
Steps taken earlier:
quite literally everything (that would make sense even remotely)
Steps taken today:
- Downloading TWRP 3.2.1-0 (https://twrp.me/wileyfox/wileyfoxsparkx.html)
- fastboot-unlocking the bootloader (no issues)
- trying to install TWRP (no issues there either)
- when trying to reboot straight to recovery, I don't get past the bootlogo, suggesting to me that either the install or TWRP was corrupted.
Any help one might get?
Thanks a lot?
Click to expand...
Click to collapse
The only version that I had success with was 3.0.2 from https://dl.twrp.me/porridgek3/"]https://dl.twrp.me/porridgek3/[/URL]
Even then, It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. still in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu.
AlwaysLivid suggested that you can boot to TWRP by executing "fastboot boot recovery.img" (where recovery.img is the TWRP img file renamed) on MSDOS Prompt / Terminal according to whether you're using Windows or a Linux distro (e.g. Ubuntu which I use). Presumably this would be after you have taken the battery out for a few seconds before inserting it again and have then booted into the appropriate mode with the Volume Down & Power buttons held down.
johnaaronrose said:
The only version that I had success with was 3.0.2 from https://dl.twrp.me/porridgek3/"]https://dl.twrp.me/porridgek3/[/URL]
Even then, It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. still in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu.
AlwaysLivid suggested that you can boot to TWRP by executing "fastboot boot recovery.img" (where recovery.img is the TWRP img file renamed) on MSDOS Prompt / Terminal according to whether you're using Windows or a Linux distro (e.g. Ubuntu which I use). Presumably this would be after you have taken the battery out for a few seconds before inserting it again and have then booted into the appropriate mode with the Volume Down & Power buttons held down.
Click to expand...
Click to collapse
Thanks a lot, I'll try your method, the explicit call to boot the TWRP image could really help.
Thanks for your extended explanation tho, showed me some new ways to eventually get this stuff to work.
Sent from my Wileyfox Spark X using XDA Labs
johnaaronrose said:
I can't decide whether to try the rooting method given in https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung
The method is:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Has anyone had experience of this method?
Click to expand...
Click to collapse
Finally, your advice with "Fastboot boot twrp.img" worked magic!
Got twrp installed, but now I'm facing the same problem as you with the systemless root. I'll dig around a little and see what I can find.
I Got twrp installed, installed a patched boot image, and now I'm caught in a boot loop, buttons do nothing, my computer isn't picking it up, what do I do? Is there anything that I can do?
Lackinginknowledge said:
I Got twrp installed, installed a patched boot image, and now I'm caught in a boot loop, buttons do nothing, my computer isn't picking it up, what do I do? Is there anything that I can do?
Click to expand...
Click to collapse
Shouldn't be using a patched boot image. That's only if there is no TWRP available for your device. Go to the pinned unbricking guide
I had the same issues and just ignored twrp and went ahead and just installed magisk and EdXposed. Is there an official Android 10 twrp I can install?
Arden144 said:
Shouldn't be using a patched boot image. That's only if there is no TWRP available for your device. Go to the pinned unbricking guide
Click to expand...
Click to collapse
Ahhhhhh I see where I went wrong. I ended up finding and flashing the correct boot image and now I'm happy
Yes
It feels Great to fix a device you soft bricked correct? Enjoy.! That's the ONLY way you'll learn.
LowaEastSide said:
It feels Great to fix a device you soft bricked correct? Enjoy.! That's the ONLY way you'll learn.
Click to expand...
Click to collapse
It does indeed, though I do also enjoy having devices that are not softbricked 100% of the time
Oneplus 7 Pro rooted and twrp installed. Tried to install Lineage OS, twrp said it was successful, however it's
just stuck in an endless boot cycle with the circle moving over the curvy line.
I've tried restarting and that has not helped. I've gone back into twrp but the downloads folder where the Lineage zip
was is no longer there. I thought i'd just put the stock oneplus Oxygen OS back on but i can't copy the file to the phone.
What can i do? or have I just got an expensive paperweight now? I need help!
IthinkIfckedmyphone said:
Oneplus 7 Pro rooted and twrp installed. Tried to install Lineage OS, twrp said it was successful, however it's
just stuck in an endless boot cycle with the circle moving over the curvy line.
I've tried restarting and that has not helped. I've gone back into twrp but the downloads folder where the Lineage zip
was is no longer there. I thought i'd just put the stock oneplus Oxygen OS back on but i can't copy the file to the phone.
What can i do? or have I just got an expensive paperweight now? I need help!
Click to expand...
Click to collapse
Had this yesterday, fix like this.
Get the fastboot OOS Rom for the version you were on before the mess up.
Vol up and down with power button to enter fastboot mode.
Unzip file , and run flash all bat
@soka said:
Had this yesterday, fix like this.
Get the fastboot OOS Rom for the version you were on before the mess up.
Vol up and down with power button to enter fastboot mode.
Unzip file , and run flash all bat
Click to expand...
Click to collapse
Thank you for your reply, that didn't work though! It ended up completely bricked, wouldn't even turn on. I managed to salvage it though in the end with MSM. :good: