Hi all!
Fairly new to rooting & flashing on Android - but I've done so successfully in the past on an older device.
Not fully happy with OxygenOS (wanted to flash a Cyanagen ROM) - but I'm having some trouble getting everything to work.
Here are the steps I followed and results:
Put OP2 into Developer Mode & enabled USB debugging
Connected OP2 to MacBookPro via USB
Opened Terminal on Mac & ran "adb reboot bootloader" to reboot the device into fastboot mode
One in Fastboot Mode, ran "fastboot devices" via Terminal to ensure it was readying my OP2 (everything is fine here)
In Terminal, ran "fastboot flash recovery recovery.img" (I had previously downloaded a copy of TWRP into the same folder as ADB & Fastboot & renamed the TWRP image to "recovery.img")
In Terminal, next ran "fastboot boot recovery.img"
Once it booted into TWRP, I navigated to the SuperSu .ZIP file saved on my OP2 and ran through the install process...and rebooted the device.
This is where it hangs on the boot screen - It's a red dot with 2 white dots circling around it.
(I tried to add an image of the screen to this post, but it says I'm too much of a newb to be able to post images
It's been on this screen for at least 30 minutes now - and I'm thinking it shouldn't take this long at this point (but I could be wrong).
Can anyone please help me?
Thank you much in advance!
just one more step
here you go:
http://forum.xda-developers.com/oneplus-2/help/oneplus-2-bootloop-flashing-supersu-t3424834
Related
Hello everyone!
Okay, so I'll try to keep it as short as possible but with the most information I can give ofc.
So here's what I did with my Oneplus 2:
- unlocked bootloader
- flashed custom recovery (twrp)
- flashed superSU.zip
- flashed xposed.zip
- used it for about half a year if not even longer
everything on Lollipop 5.1 stock rom so xposed would work.
Everything was fine but some day when I wanted to enter twrp recovery it didn't work. (I swear, this is the most illogical thing ever but I DID NOT CHANGE A THING!)
I tried to enter recovery via fastboot but that didn't work either.
So I reflashed latest TWRP recovery.img for OP2 via fastboot.
When I pressed power + vol. down to see if it'd work nothing happened.
When I tried to enter recovery when my system was booted via power button->restart->recovery my phone got stuck in a bootloop.
I had to go in fastboot mode to enter "fastboot continue" in order to get my phone booting normal again.
Then, one night when my phone was in my pocket it vibrated and got stuck in the bootloop again, even though it was booted into system and locked last time I used it (minutes before that).
I had no access to a computer at that moment so I had to wait for a few days.
Now when I boot my phone in fastboot mode and try to enter "fastboot continue" on my cmd nothing happens with my phone and cmd says "(command write failed (Unknown error))" even though "fastboot devices" shows that my device is connected properly.
I also tried:
- the FirstAidKit, copied the Win Files in my fastboot directory and started the firstaid.bat but it stops on "fastboot flash boot boot.img" (I waited for like two hours).
- a different USB port (USB 3 and USB 2)
I am kinda depending on my phone so yeah..
If someone knows how to fix this I would be very grateful.
Have a good day/night
SoulSnatcher
Do you have a backup??
If yes, download the latest official OS from Oneplus and the stock recovery. Flash the stock recovery. Try rebooting into stock recovery. If it succeeds, wipe everything and flash OS via adb sideload.
Honestly, I can't guess what went wrong with your device. Maybe it could've been some app which crashed the entire system.
AJay27 said:
Flash the stock recovery.
Click to expand...
Click to collapse
Same problem as with the FirstAidKit:
"fastboot devices" does display the device but "fastboot flash recovery recovery.img" doesn't do anything (I waited for 1h just to make sure).
I'll try this Mega Unbrick Guide for A Hard Bricked OnePlus 2 next, even though I can get into fastboot but since it doesn't do s**t I'll have to give it a try. I mean, what's the worst thing that could happen? That my phone gets bricked?!
Haha.... hmm.
I'll keep the person(s) updated who care to know what's happening.
Cheers
fml
Hi friends, i have followed instructions as per youtube video (official oneplus),struck on rebooting ..now i am able to fastboot,twrp recovery menu,have backed up using twrp backup.But not able to reboot to system.The boot logo after one plus symbol kept on rotating infinitely.Please help me.
Do a factory reset
Sent from my ONE A2005 using Tapatalk
My phone is not getting power on,though i have done factory reset from twrp 3.000 recovery.Still no go struck in boot menu with rotating logo after 1+ symbol..
Hello . Firstly try get your phone into fastboot mode. Once you have get up adb. (if you don't have adb, or find it really confusing to install, get wugfreshs root tool kit has built in adb terminal)
Open up your terminal plug in your phone and type
Code:
fastboot devices
Something should come up .
Once you done that grab the latest twrp for your device. Then FLASH! AAHHHHHHH, PROTECTOR OF THE UNIVERSE. In fastboot
Code:
fastboot flash recovery twrp.img
Once that's done type
Code:
fastboot boot recovery twrp.img
The it should boot into recovery from. Here your computer should recognize your device . You should be able to easily drag and drop a new rom and gaps on to your device
---------- Post added at 08:52 AM ---------- Previous post was at 08:50 AM ----------
Brandon Indar said:
Do a factory reset
Click to expand...
Click to collapse
Also factory reset only works on a rom level. So if roms wrong. It won't do anything
So, I had the same problem and here is my fix for it.
I am not sure, but I think you will lost all your data on this way :/
You can Skip the first 2 lines, because when you installed TWRP you already done this
1. Go to a Computer and install Adb
2. Download Minimal Adb and Fastboot
3. Download the offical Rom on the OP2 Site and copy the .zip file into the Fastboot folder
4. Rename the .zip into rom.zip
5.Connect your phone to the Computer
6. Start into Twrp, go to advanced, click on adb Sideload
6. Now go to your computer, into the Fastboot Folder and start the command line and type: adb sideload /path/to/rom.zip
7. It should now take some minutes to install the Rom, you will see how many percentages on the Screen (It will only show until 50%, don't worry about that)
8. Voila, your Phone should now work again
To root it again, there are some modified UpdateSu-Files specially for your current Rom.Version. When you are on 3.5.6 you can use the attached file
Weird: I was just using it normally, it switched off and now it stays stuck on the Google logo; when entering recovery mode, I get TWRP"s splash screen and it stays there, so I cannot even recover.
Suggestions please??
Note 1: I'm pretty bad with this kind of stuff, need step-by-step instructions.
Note 2: rom is AOSP 7.1.2 but I guess is irrelevant, as even TWRP does not load.
Thanks in advance!!
Can you fastboot boot the TWRP recovery?
Hmmm dont know exactly what that means sorry; I mean I havent tried connecting it to the laptop and using thr ADB toolkit, but I can reset via Power+VolDown to the bootloader menu (? the android layind down and giving the option to StartSystem/ SwitchOff/ Restart/ RecoveryMode), and choosing RecoveyMode it tries to launch TWRP (it even shows the logo) but stays there on the splashscreen, doesn't quite manage to give me the TWRP menus
Someone?
AndDiSa said:
Can you fastboot boot the TWRP recovery?
Click to expand...
Click to collapse
let's see... I set in recovery mode, connect to the PC (does not recognise it), and with "fastboot boot twrp.img" it just sends/writes the file, the tab shows the Google logo with open lock, and then tries to launch Twrp, but as before, it just get stuck in the splashscreen "TeamWin Recovery Project 3.3.1.0" , so just the same.
Command "fastboot flash boot twrp.img" the same
Command "fastboot flash recovery twrp.img" the same
Command "adb devices" returns the list empty
Command "adb reboot recovery" returns "error: no devices / emulators found"
Command "fastboot oem unlock" returns "(bootloader) bootloader is already unlocked"
I tried running a tool called FirstAid (https://forum.xda-developers.com/devdb/project/dl/?id=16684) but does nothing for me
I'm lost, please help
Video and photos of the issue (device, not adb)
video: https://photos.app.goo.gl/GrFrmQhbyQeHVFZN7
Well, looking at your video it seems that there is no bootable ROM installed and also the recovery (for what ever reason) has some issues to start.
The fact, that you are able to boot into bootloader shows that at least it's not completely bricked ... but there's still the chance that the flash memory has some issues.
I would connect the device via usb with a PC and try to do a
fastboot boot <twrp-3.3.1-grouper.img>
to whether in that case the recovery is booting.
If this is successful, the next step would be re-flashing the recovery into the recovery partition and booing into recovery mode from the bootloader.
If this is successful, too, wiping and flashing a new ROM would be the last step.
Recently, I purchased a TicWatch Pro 2020 (saw that Kali Nethunter now seems to work on it and I thought it could be a cool device to add).
I have installed nethunter onto several other devices already (Nexus, OnePlus, etc.) and of course ran into issues. Usually I spend a long time on them and it is fun to do it. But I seem to have run into a wall recently with the watch.
When I was first trying to set up the watch, I could send commands with adb to get it into the bootloader menu but then it would not recognize it. I did eventually get the right drivers installed and had my VM recognize the watch with the ADB drivers.
I did manage to complete Step 1 of the tutorial https://www.kali.org/docs/nethunter...-on-the-ticwatch-pro/#1-unlock-the-bootloader
(unlocking it).
I went through to step 2, put it into bootloader again and flashed the vendor and twrp .img files. Once I did this, I tried to switch the device into recovery mode (after it went back to the bootloader menu on its own) as per instructions. But the weird thing is when I initialized recovery mode, it just sent me back to the bootloader menu, all while also not recognizing it on my VM/PC at all. When I tried to start the watch, it just sent the device into a permanent loading loop (after showing the logo and cycling the 4 different colored Google dots around the watch). I can get it back into the bootloader menu by holding both buttons down but I can't get my device to be recognized with a data connection (so it seems effectively bricked).
Normally I look this up myself but since there is not much information regarding this device and this specific rom out there just quite yet, I can't locate anything (compared to troubleshooting the OnePlus 7 Pro). Any ideas or input is appreciated!
Edit: will just let it run over night (drain battery to see if it may or may not help).
Thought I would leave a quick update in case you may be running into this issue yourself.
I let it run over night and run out of power to see if it would do anything. It now seems to be recognized by my pc, but it would not connect. I am installing everything through a VM but it appears that the PC could not recognize the device (I only had drivers installed on my VM, not my main device). When I installed the drivers on my main desktop it began to recognize it again on my VM. Not sure why this was an issue or how it became one or if it was a combination between everything but now at least I can send adb and fastboot commands to my watch again. Will try to flash a stock rom for it and try again to get out of the boot process (still confused as to why it will not go into recovery mode but it instead goes back into boot loader mode when I select it)...
Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?
i got nethunter and twrp working on the ticwatch 2020, it was a pain finding the right files to use and i soft bricked my watch many times in the process.
https://forum.xda-developers.com/t/...shark-4g-ticwatch-c2-skipjack-9aug20.3821013/ this post has the right vendor.img and twrp recovery image, in particular this mega folder https://mega.nz/folder/cVVBRaxL
1-Vendor-Images-22-Jun-2020.zip unzip this file it is located in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/ROM/22-Jun-2020 it contains the vendor.img you'll need
tic-watch-pro-2020-twrp.img in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/TWRP this is the TWRP Recovery.img you'll need
Magisk-v21.0.zip and nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip are both needed from the TicWatch_Pro_NetHunter_files.zip at https://build.nethunter.com/contributors/re4son/catfish/
1) Enable ADB and unlock bootloader then enter these fastboot commands on pc
fastboot flash vendor.img
fastboot format userdata
fastboot format cache
fastboot flash recovery tic-watch-pro-2020-twrp.img
2) Reboot into WearOS and Setup Watch
3) Enable ADB again and reboot into recovery
adb reboot recovery
4) move Magisk-v21.0.zip into the TWRP folder on the watch
install Magisk-v21.0.zip from TWRP recovery (it'll patch the boot.img itself)
5) Enable ADB Sideload from the Install menu in TWRP
adb sideload nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip
6) Reboot into wearOS with kali splash screen, you will have to open the magisk app after you open the nethunter app to give it root as there isn't a proper pop-up screen to give root access
**circle screen does semi cut off a few buttons in the nethunter and magisk apps, touch your watchface close to the "corner" where it is to select it
I hope this all helps! Cheers mate
unidentifieduser said:
Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?
Click to expand...
Click to collapse
i just realized i typed all the above and didn't reply to your message, it was a mixture of two install methods with leaving out the flashing of the rom file itself
First of all, I must note that this is my first time flashing a phone, so don't rely too much on my knowledge on the subject, please!
So...
I started by unlocking the OEM and USB debugging from the developer menu, then downloading and extracting ADB tools to my PC. I unlocked my A1 just fine. I then proceeded to install twrp on my phone by using the "fastboot flash boot twrp.img" (as it was named in my ADB folder) and "fastboot reboot" commands. It should be noted that the "fastboot flash recovery twrp.img" did NOT work in the previous step so I have to use the "boot" command instead. TWRP was working perfectly, and I wiped the data from my system and data slots from twrp (there was no cache option in the menu except dalvik which I also wiped).
After that, I added tissot's evolution_tissot-ota-td1a.221105.001-11121815-unsigned.zip and ProjectElixir_3.2_tissot-13.0-20221102-0447-BETA-OFFICIAL.zip to my phone via fastboot after download. Both were flashed successfully (I didn't try to do them both at the same time, of course. One didn't work and stuck on the boot screen for project elixir, so I tried the other after wiping the older one). Both were stuck on the boot screen for their respective teams.
EDIT: Tried it with the stock version PKQ1.180917.001.V10.0.18.0.PDHMIXM.zip, and it worked! Any idea what the issue is here?
If anyone needs more info, I would be glad to provide it. A little help goes a long way!
Cheers