no recovery, locked boot loader, fastboot only, qualcom recovery not working - OnePlus 2 Q&A, Help & Troubleshooting

was on CM13/TWRP, suddenly my phone rebooted while i was talking, i looked at it and it had a linux logo on it....waited a bit, didn't go away, so i held power until it turned off.....then it wouldn't turn on.....so i tried recovery, nope. tried fast boot, that worked.. tried to reflash TWRP from fastboot command, failed because device is not unlocked.
can't run oem unlock because i can't get in the OS to developer mode to enable it.....
so i've been trying to do the qualcom recovery, windows 10 laptop, tried all the versions of the qualcom recovery/drivers i can find...... the recovery tool keeps giving me a red error on line 4. either that or it flat out crashes the whole program.
whats my next step? i'm attempting to run it on a windows 7 computer now thinking that may make a difference.
anyone have any thoughts?

Related

LG G2 VS980 Bricked

Guys I need urgent Help
Recently I was running AOSP based ROM and tried to flash RR ROM based on Android 5.1.1.
I was not being flashed and was giving error so I dont remember which bootloader or file I flashed to make RR Rom flashing possible.
Then I flashed Gapps and wiped Cache and Delvik and restarted the cell.
After Restart, it was stuck on bootloop. One thing not to forget, It remains stuck on bootloop for several times and finally boots up, and the first screen comes is Android upgrade that works on 96 apps. As soon as upgrade completes, it reboots and remains stuck on bootloop.
If i try to enter into recovery, it takes me to fastboot mode where blackscreen with like commands stating fastboot is displayed.
If i press the volume button up and plug in the cable while connected to Laptop, Download mode starts but Laptop doesn't detect any device.
On the other hand, if started in fastboot mode, ADB device is detected.
I have tried to install LG Drivers, Verizon Drivers and also universal ADB drivers but nothing has worked so far.
The device is not detected at all.
I have windows 10, also tried on windows 8.1 but same issue.
Even tried disabling Driver Signature enforce or updating system but still same issue.
Anyone who could be able to help will highly be appreciated.

a6000 shut down during MIUI flash, won't boot into recovery

Hey guys I was trying to flash MIUI 8 on my a6000 lenovo. Bear with me because I'm new to this so I might have screwed up.
Rooted and installed TWRP perfectly. Phone was running kitkat.
I then, through TWRP tried to flash MIUI 8 from http://forum.xda-developers.com/lenovo-a6000/development/rom-miui-7-lenovo-a6000-a6000-t3355692
After first swiping right to install the zip, i got an "error executing binary in zip" error. Wiped dalvik,etc. again and tried again and then I got a MD5 file not found "warning". It was not in red letters and after that message there was no progress bar or anything and the phone just stopped responding. I assumed it wasn't working and few minutes later took the battery out. After trying to boot again it would give me the "mi.com" boot screen (not the default lenovo I used to get) and won't boot into neither recovery nor normal mode. (for recovery boot I'm trying holding both volume buttons and the power button at the same time. perhaps that is different now?)
I'm guessing the flashing was going on and i interrupted it. How can I fix this?
Update: It boots into MIUI now however pretty much nothing works as expected. It wont even go into settings. Recovery still seems botched and i cant boot into it.
TLDR: Recovery broken cant boot into it. Can boot into MIUI with very limited capabilities. Cannot select USB debugging and "adb devices" won't find the phone. What can I do?
Alright nevermind guys I managed to fix it. for anyone wondering or having the same issue, i tried many things but what I think worked is this:
Turnt on my phone in fastboot mode (hold volume - and power button) , connected it to the computer and used command "fastboot flash recovery recovery.img" to flash the old TWRP i had on my computer. After that I managed to boot my phone in recovery mode and reflash the rom properly. The weird thing is, my phone could not be recognized by the computer and "adb devices" gave me nothing back so I thought using any fastboot command wouldn't work. Oddly, it did and it flashed TWRP back into my phone.

att lg g6 recovery

so i was just playing around and used adb to and my PC was able to find adb devices and i was run some simple commands but when i try to reboot to boot loader it looks like its trying to as i hear plugged in sound after phone booting but immediatly disconnect sound and it boots normally and i tried rebooting to recovery and it booted to a screen with robot with a red exclmation mark and no command on the bottom and i tried some key combinations but nothing worked except holding vol down and power boots it back, does this mean att or lg have not installed recovery or is it blocked, i am aware bootloader is locked but it should still boot to recovery as it did in the g2 days that i can remember, any ideas, thank you.
update and few questions,
in the lg g 2 days on att non rooted phone the button sequence would take you to factory erase screen and if one accepts it it erases and then boots into stock recovery but now on lg g6 it does not , it erases and boots normally, and i tried adb reboot bootloader and it wont work and i tried adb reboot recovery resulting in flat robot with red exclamation mark and NO COMMAND on the bottom, i am just trying to understand, is it that secure boot in nougat is locking me out or is it att that disabled recovery and fastboot, any thoughts appreciated.

Hard brick

Hey their. So i jsut bought a one plus 6t and started playing around iwth it. I tried to get twrp and i got it but when i rebooted to os i had no wifi. So i download magisk zip and flashed it. After this i got stuck in bootloop and so i wne to twrp and wiped everything except system. Then i rebooted and got this message Qualcomm CrashDump Mode Attempted to kill init! exit code=0x0000000b do_exit. Then i freaked out and accidently wipes system too. Now i think i have a complete brick as adb still works but i cant transfer any file from pc to phone because theirs no system. Please help!!!
Never wipe system and vendor on A/B devices, literally, never.
Boot twrp and flash OOS or use msmdownloadtool.
What do you mean flash OOS. Like flash a fastboot file? And what version of msmdownloadtool should I get as their is no system. Should I get 10 cause that was my last system or it doesn't matter.
Update. I left twrp after flashing a stock image and now adb doesn't recognize my phone. When booting into recovery I go into the one plus recovery. Now I'm really screwed.
Okay now im really screwed. Whenever I boot with power up or power down I get sent to the bootlaoder page that says fastboot mode products name. I cant leave this page however. On the options above the information I click reboot recovery I get sent back to this page.
UPDATE. My phone is a literal brick now. It won't even turn on. I tried to force reboot it before and after it powered off it wont turn on. Its fully charged and when connecting to charger of holding buttons nothing happens. I have no warranty so Im hoping that someone can help me.
The "bootloader page" is fastboot and that's normal because there's no system to boot, you wiped that partition... and ADB only recognizes the phone when the boot process ends and ADB is enabled in the phone.
If you press vol up + down when you connect the usb cable the phone boots in EDL (Emergency Download Mode) mode, long press power + vol up to leave that state.
Now, download msmdownloadtool from here, extract the file, power off you phone, conect the usb cable to your pc, press vol up + down and connect the usb cable to the phone, open msmdownloadtool and flash the OS.
Edit: Read this thread for more detailed instructions.
What do you mean by flash the OS. The OS in the system or do I have to download one?
whenever I plug in my device it vibrates and then goes into the fastboot page. Also adb can detect it if I type in fastboot devices.
So i go the device to work and MsM worked until 4 seconds and then It said param preload for status of connection and status of last communication says device not match image
Try with the fastboot ROM.
When i downloaded another version of MsM it did not say no image match instead it stays at 4sec and says recording download time
Can you give me instructions on how to use the fastboot room? Like after i download it what should i do with it?
Download the rom, unpack it, boot your phone in fastboot (Power + vol up + vol down), connect the phone to your pc and execute the "flash-all.bat" file, and just wait.
um what is flash-all... How does it work what am i supposed to do.
what does unpack it mean?
Hey their im going to assume you meant to unzip the file and then open the file called falsh-all.bash. In that case when i do that i get this message "error: failed to load 'images.zip': No such file or directory
Press any key to exit..." In a CMD window

Note 7 stuck in bootloop after failed flashing attempt. Can't get into fastboot.

ood morning!
While attempting to flash a stock MIUI 10 ROM into my Xiaomi Redmi Note 7, to downgrade back to Android 9.0 due to some app compatilibty issue, I messed up big time and my phone is now stuck in a loop where the screen turns on, nothing shows up, then it restarts, going off for a few seconds and turning on again.
Power Button + Volume UP successfully brings me to the stock recovery 3.0 from xiaomi.
Power Button + Volume DOWN fails to bring me to the fastboot mode.
If I select the Connect with MIAssistant in the recovery the phone will show up as "sideloaded" after using the command adb devices, but the MIPCSuite app does not see it and the command adb restart bootloader also fails to bring up the fastboot mode, it just gets stuck in the loop again.
More context on what went wrong and caused this: I followed an online tutorial to flash a rom using the MIFlash app, so I unlocked the bootloader and tried to flash the rom usin xiaomi's tool. I got a failed to check sparse crc error code and it went downhill from there when I tried to fix things reading multiple threads on the issue. I tried deleting some lines from the flash_all.bat file and tried to flash it again but then the flashing process went seemingly forever so I aborted the operation and now this loop happens. I tried a few more times but with no success.
The first time I tried to use the tool I used the clean all and lock option so I'm not certain if the miflash tool locked the bootloader regardless of the outcome of the flashing attempt.
Is there hope? Can I fix this phone if I only have access to stock recovery and nothing else (although it shows up in adb devices but can't get into fastbootmode) ?
Thanks a lot to anyone who took the time to read and possibly help.
I finally managed to fix it through the Emergency Download Mode (EDL). It requires Xiaomi Authentication which I bypassed using this guide: https://www.droidwin.com/fix-mi-account-authorization-unbrick-xiaomi-edl-mode/
With that setup I flashed a stock rom using the MiFlash tool.

Categories

Resources