I guess I soft bricked my OPT - OnePlus 2 Q&A, Help & Troubleshooting

Hello Forum,
well I guess I kinda soft bricked my OPT as I somehow managed to wipe everything (with TWRP). Of course the Device won't boot a OS, fortunately fastboot and TWRP is working but no matter how I flash a ROM (via recovery or via fastboot) no data gets written to the phone. For example if I open my phone on the computer there is only one folder, the TWRP folder.
I already tried several toolkits and fastboot images. (for example)
Any help is really appreciated thanks

Related

How to copy files from a non-root/stock recovery Samsung with broken screen/no touch

Hey guys. just wanted to share how I got access to all files (no sms/mms though) on a screen locked, non-rooted, stock rom Samsung S5 (in this case also with a black and broken screen with no touch).
First of all, thanks to FuzzyMeep Two and his post -> http://forum.xda-developers.com/showthread.php?t=2339530
The trick is to access the phone with ADB commands and copy the files that way. The problem is that stock recovery doesn't support adb commands, so first off we must flash a custom recovery. This has to be a terrible security breach on Samsungs part, as flashing a custom recovery won't wipe the phone.
What I did was download Odin (Samsung flash tool) and a CWM custom recovery. Then I entered download mode on the samsung and flashed the recovery no problems. Then I rebooted the phone in recovery mode.
From here on I used the above mentioned post, with the custom recovery I could find the phone with ADB devices command and thereafter run the program ADB data recovery which pulls all the files from the phone and puts it on you'r harddrive.
Hope this post will help someone, and thanks to XDA for all the help I have gotten on this site.

PSA: Ticwatch E&S factory reset

This is just a friendly notice for Ticwatch E&S users. If you do anything that resets the watch back to default, it seems the device needs to boot to the stock recovery before it will boot back into the system. The only way to do this after flashing TWRP is to reboot to the bootloader and and run 'fastboot boot StockRecovery_TicwatchE.img' with the image file from the root thread by @EpicLPer. Normally, this wouldn't be a big deal but this could be an issue if you do this away from a PC where you can run fastboot.
This is also a big problem if you screw up and flash a broken TWRP and can't reboot into the bootloader. I was working on a recovery procedure for this but screwed the pooch on that too so I'm going to see if I can RMA the dead watch.
BackCheck said:
This is just a friendly notice for Ticwatch E&S users. If you do anything that resets the watch back to default, it seems the device needs to boot to the stock recovery before it will boot back into the system. The only way to do this after flashing TWRP is to reboot to the bootloader and and run 'fastboot boot StockRecovery_TicwatchE.img' with the image file from the root thread by @EpicLPer. Normally, this wouldn't be a big deal but this could be an issue if you do this away from a PC where you can run fastboot.
This is also a big problem if you screw up and flash a broken TWRP and can't reboot into the bootloader. I was working on a recovery procedure for this but screwed the pooch on that too so I'm going to see if I can RMA the dead watch.
Click to expand...
Click to collapse
You can flash the stock recovery and all other stuff via the Flash Tool. You don't have to RMA a dead flashed watch, you can recover 99% of all the bricks you do via that. But you'll have to ask @Luxios for that as I don't know how to correctly use it
He's also trying to make a hacked bootloader which allows you to boot into recovery and fastboot directly from the watch without ADB.
EpicLPer said:
You can flash the stock recovery and all other stuff via the Flash Tool. You don't have to RMA a dead flashed watch, you can recover 99% of all the bricks you do via that. But you'll have to ask @Luxios for that as I don't know how to correctly use it
He's also trying to make a hacked bootloader which allows you to boot into recovery and fastboot directly from the watch without ADB.
Click to expand...
Click to collapse
Flash Tool is a mighty powerful tool, alright. I couldn't find a good scatter file so in a caffeine deprived state I tried to cobble one together. I may have damaged the preloader. It does show up in device manager but it is different that the VCOM preloader device that was showing. Now it totally crashes Flash Tool too. I'm still working on it but since I have a second watch now, I might just RMA this one and start over.
Again, if anyone has a good scatter file please post it. I found one after the fact but I get errors and it's for another MT2601 device, not the Ticwatch.
The good news is I found if you power down the watch and hold the power button on boot you'll get a long vibrate. If you release the button and hit it 3 or 4 times during the vibrate you'll be in the bootloader.
Anyone have stock or even custom working system.img and boot.img?
great
thank you very much man, i was blocked in twrp recovery after a factory reset, and now i should have installed stock recovery, thanks to your post .

Help me Recover my files from no more booting Redmi 4 Prime. I will pay for success

Hi there,
after a normal shutdown, my xiaomi redmi 4 prime is not booting anymore.
it is stuck on MI Logo. I can enter fastboot and download mode. Phone is NOT rooted and Bootloader seems to be locked, but fastboot flash recovery seems to work. But all my hope to get a twrp started failed until now. I REALLY need the files from that phone. If somebody can help me, i will pay you money if you SUCCESSFULLY help me recover the files.
Beside, adb mode does not more work, after trying to fastboot flash a twrp image. But in ADB Mode i was in sideload mode, where no commands like pull did work. Oh and i never turned od developer mode i think. I will not stop believing there must be some person on this planet who can rescue my data.
thanks for any help.
I believe adb and developer mode are irrelevant since they work from within the system. One option is to make twrp recovery boot and copy files from it, but since you tried and failed you could try something else, but as last resort since I don't remember if it saved my data.
Since your bootloader is locked you cannot flash boot partition, but you can flash every other which cold fix your system. You should find EXACT same rom you had and extract partitions you want to flash (you have tutorials online, I don't remember, think you just extract them). If you try to flash complete rom with locked partition, process will fail.
fastboot flash system
fastboot flash recovery
fastboot flash data?!or whatever (or not data if your files are there)
Hope I gave you another perspective..

Nokia x6.1 bootloops to twrp.

So it had been a while since I had tried getting into recovery twrp but I figured I could remember how so I did
fastboot flash boot twrp etc.img
This was a mistake according to the site here > https://twrp.me/nokia/nokia6_1.html
WARNING: If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Click to expand...
Click to collapse
Which is exactly what I did
So now my phone is either stuck on the Nokia logo, or I can load twrp.
They provide some info on fixing it but I'm not sure I understand what they are saying. Can anyone help with this?
The phone was running Oreo (not sure which version unfortunately) and it was fully rooted and running magisk/xposed/su just fine before my mistake.
I don't have access to fastboot. Only Twrp and adb commands.
Edit, I can get to fastboot/download mode through the twrp terminal.
[SOLVED]
So I was able to use twrp to copy all of my internal files onto an sd card.
Then I set about getting this tool here > https://github.com/RaghuVarma331/Nokia-Tool the firmware specific to my phone, and modifying the bat file found here > https://github.com/RaghuVarma331/Nokia-Tool/blob/master/batscripts/Nokia-Tool-DRG-B2N-PL2-CTL.bat (because windows for some reason gave me a 16 bit application warning when I tried to use the tool exe)
My phone flashed a bunch of time and I was able to load up an almost entirely stock android 10, still capable of using magisk, edxposed, etc.
And now all there is to do is to get everything back onto it and set up which is at this point, the best case scenario.

Soft bricked phone: looking for advice

Hi
I would like to ask for some advice.
I've recently soft bricked my MI2S. I can boot to recovery (TWRP 2.8.1) and fastboot. The phone isn't recognised by Windows or Ubuntu, so I can't flash anything with fastboot. Actually, fastboot, adb or MiFlash don't detect the phone. I've tried to use a USB stick with an OTG cable, but TWRP doesn't detect the USB stick. If I boot to system, it stays on the MI logo (I can wait a full night, it won't change).
My question is, do I have a problem with my USB port? I'm equipped to solder a new one, if necessary. Or is my connection problem due to another reason? I wouldn't want to go through soldering if it is for nothing. Especially, when I started to mess up with the phone, it was locked with a different MI account (it was my wife's account, but it took me a few days to connect the dots together), and I couldn't connect with MiFlash, adb or fastboot either.
The steps I did to get it soft bricked:
Flashed TWRP 2.8.1 with fastboot
Rebooted to recovery
Rebooted to MIUI (a few times)
Attempted to flash TWRP 3.5.0 (my memory fails a bit there, I think I did it via fastboot)
The last didn't work because I'm still on TWRP 2.8.1
And I can't add any more zip file to flash via recovery, nor can I use adb sideload or flash with fastboot.
Any advice or comments are more than welcome. You may just have an idea that I didn't think of.
Regards
Matt
Quick update:
I don't know if you would agree, but I can't see my issue to be a software one (the device not being recognised)
I've ordered a USB port directly from China and I'll see if I can unbrick the phone from that point.
It's great that you can still access to recovery and fastboot.
First, I advice you to back up your data.
If you cannot use adb sideload or flash with fastboot.
Try in fastboot mode
- fastboot erase cache;
- fastboot erase system;
- fastboot erase userdata.
See if that can solve your issue.

Categories

Resources