Database Info

[Q] Bricked??

OK. I have the ATT htc one x. I was attempting to install Cyanogenmod 9. I unlocked the bootloader. Rooted the phone. I loaded twrp. This is where things get fuzzy. For some reason I was not able to load the .zip file of cyanogen. Then when I restarted the device it went into a kind of loop. Twrp was gone and I could and can go into the boot loader but the os is gone and it just shuts down if I attempt to go into recovery or reboot. Also, to make things worse, the phone is no longer being recognized by my computer with adb. Is my phone bricked or is there something I can do to set things right?!?!?!?!

did you install the twrp with working usb mount?

No. I installed it using goomanager. I wasn't able to install twrp or CWM using usb mount.

Is fastboot usb working in the bootloader (It will say fastboot usb in the bootloader screen while your device is plugged in)? You may have to ruu if both recovery and the os is not loading, but you'll have to relock your oem bootloader first using fastboot if possible. Otherwise I wouldn't know of any other fix without recovery working, unless someone on here knows of another way. This has happened to me once and I had to just ruu and start everything over again.

No fastboot usb is not working is there any way I can restore the ability to access it?
I have nothing left on it anymore so restoring is no problem if I can get access to my device.
[solved]
just downloaded drivers and moved them to htc driver folder in program files for anyone who was wondering.

glad to hear. was actually just about to ask whether you had the drivers installed correctly. Hope everything works out from there.

I'm so bricked. please help!!!!!!!!!!!

I updated to the newest version from asus site Version WW_V10.6.1.8 and then by mistake flashed the latest version of TWRP recovery. now the tablet is bricked. I cant access fast mode, no adb. it only boots into recovery each time but I cant restore anything and cant access external sd card. please help!!!

tainka said:
I updated to the newest version from asus site Version WW_V10.6.1.8 and then by mistake flashed the latest version of TWRP recovery. now the tablet is bricked. I cant access fast mode, no adb. it only boots into recovery each time but I cant restore anything and cant access external sd card. please help!!!
Click to expand...
Click to collapse
If the tablet is new and you still have the receipt my best advice is to try and take to the store and they will exchange it for you. other than that your only choice is to try and see if updating the drivers from Asus or even using another PC let's you gain access to Fastboot. Other than that the incompatible version of TWRP that you flashed most likely bricked your device.
Erik

When tablet will be in twrp, in connect tablet to PC and command "adb reboot bootloader". Now flash asus 4.2.1 via fastboot

Hazard17 said:
When tablet will be in twrp, in connect tablet to PC and command "adb reboot bootloader". Now flash asus 4.2.1 via fastboot
Click to expand...
Click to collapse
ok, this worked! I have fastboot but adb shell does not work. The weirdest thing is when I press the green android icon in boot loader screetn the system boots normally!!!! but!!! when i do restart it always boots into the twrp screen. the only way to boot the system is with your command. I tried to flash the patched recovery which works with the new firmware (the flash is ok) but i cant pass the recovery screen. How can I get rid of this recovery????

URGENT!! Fastboot can't be detected on PC Android 10 Boot slot TWRP

I'm sure my drivers are fine cuz i messed this up via fastboot.
so i got android 10 on my op7p. There were some magisk modules that caused a bootloop. But i cant uninstall those modules without twrp. So i decided to flash twrp into a boot slot via fastboot. then, i set the active-slot to that. but then I still don't get twrp idk why. Now, I can get into fastboot but my pc doesnt detect it, I cant boot into the system either. The only thing my pc detects is when i power the phone off and plug it in, it automatically boots into the unlocked bootloader screen and gets stuck in there. PC detectes an "unknown usb mass storage device". HELP!!!

xnegra80 said:
I'm sure my drivers are fine cuz i messed this up via fastboot.
so i got android 10 on my op7p. There were some magisk modules that caused a bootloop. But i cant uninstall those modules without twrp. So i decided to flash twrp into a boot slot via fastboot. then, i set the active-slot to that. but then I still don't get twrp idk why. Now, I can get into fastboot but my pc doesnt detect it, I cant boot into the system either. The only thing my pc detects is when i power the phone off and plug it in, it automatically boots into the unlocked bootloader screen and gets stuck in there. PC detectes an "unknown usb mass storage device". HELP!!!
Click to expand...
Click to collapse
How did you flash twrp? On A/B devices like the OP7P you can't simply fastboot flash twrp since that will cause you bootloops. To install twrp you have to fastboot boot the image and when TWRP is booted you have to flash the installer zip file. Since you are now stuck in a bootloop, you can try to recover your boot image with something like this https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345 (no guarantees on this).
Fastboot flash this image and see if you can boot again. If that does also not work I believe the best thing you could do is reset everything with the MSMDownloadTool.

Did you use this command: fastboot flash recovery filename.img?
If yes, you'll have to use MSM to restore it

THREAD CLOSED! If interested in the subject please follow this thread: https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997
Relevant posts have been copied to that thread.

Need to recover photos from phone - dead Galaxy S6

Hey guys, in a little bit of a dilemma.
My s6, for some reason, cannot pass the flashing "Samsung" logo when booting it up. I have not rooted this phone, nor have I installed a custom recovery or rom. This phone is stock as it gets.
And I need to recover the photos off the phone. Issue is, I thought it would be simple as going into recovery mode and doing adb pull/sdcard/DCIM/Camera or something like that.
BUT I do not have USB debugging enabled!!! Never even turned on developer settings.
I tried to get into bootloader and use fastboot, but fastboot devices shows up with nothing. adb commands do not work, except when I press "install update from ADB", then only the very basic ADB commands work such as adb reboot, adb sideload etc.
So I am not sure what to do from here. Fastboot is not working (I have installed the Samsung drivers from the official webpage, but I haven't restarted my computer so i will try that).
Please help me to recover these photos :crying::crying::crying:

Hi,
If Download mode is working, flash TWRP recovery with Odin.
Go to Mount, select Data partition > Enable MTP and access files from PC.
Recover your data, then flash fresh new ROM https://forum.xda-developers.com/galaxy-s6/general/guide-tutorial-howto-samsung-galaxy-s6-t4108425

Phone is Cycling between Bootloader Unlocked Screen and Motorola Sp

I just tried rooting my phone. The phone is cycling back and forth between the bootloader is unlocked screen and the Motorola splash screen.
To repeat some steps from a prior post.
My phone had QPR30.80-58-3 .
I downloaded that ROM and extracted the boot.img file.
I downloaded the latest Magisk Manager and installed it on my phone.
I ran through the patching process for boot.img.
I requested an unlock code from Motorola and unlocked the bootloader.
I flashed the patched boot image which patched partition b.
I flashed the patched boot image to partition a.
I rebooted which began the cycle.
I tried holding down the power button but it returns to the cycle.
I can get back to the bootloader with the Volume Down and Power buttons.
Any suggestions on what could get me back to a functioning phone, rooted or not rooted?

I would confirm the version of the boot image you flashed matches the version of the installed rom. You could also try to flash the unpatched / original boot.img to see if that gets you booting again.

dafunk60 said:
I would confirm the version of the boot image you flashed matches the version of the installed rom. You could also try to flash the unpatched / original boot.img to see if that gets you booting again.
Click to expand...
Click to collapse
I checked that the image I patched was from the QPR30.80-58-3 ROM which matched the level after the phone was updated.
I flashed that original boot image which flashed partition a and then rebooted. I did not flash partition b.
It first came up with the unlock warning screen. It sat on the Motorola splash screen for a noticeable amount of time followed by a yellow screen with a circle around the Motorola symbol. Finally it ended up on a blue Hello there screen with a yellow start button.
This screen was unresponsive. Eventually through various cyclings through all this I ended up on a screen that said Android could not boot and gave me an option of a factory reset. I did that but it did not help getting past the Hi there screen.
I went back and flashed the QPR30.80_58 image on both partitions a and b. This got me back to setting up the phone again. The phone is at QPR30.80_58. I am considering just rooting at this level.

So I tried patching the original QPR30.80_58 boot image. I did notice that it appeared the phone had automatically staged the QPRS30.80_58_3 update. I proceeded in (false) hopes that I could stop that.
It flashed the b partition. Ended up stuck in the bootloader unlock loop. I flashed the a partition but no change.
Previously I had ended up on a recovery screen automatically after some time. I could not force this to happen.
I tried flashing the original unpatched boot image but would end up on a non-functioning Hello there screen.
I tried adb recovery and adb shell but came back with device unauthorized.
I tried following some instructions on using fastboot erase userdata and fastboot erase cache. No change.
I finally found out that the Recovery menu was option off the bootloader screen. However, that came up with No command.
Lenovo Rescue did not want to recognize my XT2043-4 device.
I flashed the unpatched retail QPRS30.80_58_3 boot image to both a and b partitions. That got me back to a functioning phone. After getting through the login and setup steps I did find that it was at QPRS30.80_58_3.
Out of curiosity, I tried Lenovo Rescue again. I received a "Failed to match connected device. Reconnect device, then try again." which did not work.
Now I am at a loss.

DougPeterson said:
So I tried patching the original QPR30.80_58 boot image. I did notice that it appeared the phone had automatically staged the QPRS30.80_58_3 update. I proceeded in (false) hopes that I could stop that.
It flashed the b partition. Ended up stuck in the bootloader unlock loop. I flashed the a partition but no change.
Previously I had ended up on a recovery screen automatically after some time. I could not force this to happen.
I tried flashing the original unpatched boot image but would end up on a non-functioning Hello there screen.
I tried adb recovery and adb shell but came back with device unauthorized.
I tried following some instructions on using fastboot erase userdata and fastboot erase cache. No change.
I finally found out that the Recovery menu was option off the bootloader screen. However, that came up with No command.
Lenovo Rescue did not want to recognize my XT2043-4 device.
I flashed the unpatched retail QPRS30.80_58_3 boot image to both a and b partitions. That got me back to a functioning phone. After getting through the login and setup steps I did find that it was at QPRS30.80_58_3.
Out of curiosity, I tried Lenovo Rescue again. I received a "Failed to match connected device. Reconnect device, then try again." which did not work.
Now I am at a loss.
Click to expand...
Click to collapse
Happy to hear you have a working phone again! The lack of touchscreen response & the stuck at the hello screen issues are what others have reported when they used a boot image from a different version than on the phone. I suspect that something got confused between the version & slot somewhere along the way. As far as the Lenovo Rescue software not seeing the phone, it's communicating via ADB. If I recall correctly I needed to reauthorize the PC to connect via ADB after updating from 30.80-58 to 30.80-58-3. When I connect the phone via USB there's a popup on the phone asking to authorize the PC. Can you connect via ADB in the command line? If yes, you may want to reinstall the Lenovo software. If no, I would troubleshoot the ADB connection.
I originally rooted the 30.80-58 version. When 30.80-58-3 was released all I did was flash the unpatched boot.img, took the update OTA, let it reboot, then flash a patched boot.img from 30.80-58-3. All worked as expected, user data was intact.

dafunk60 said:
Happy to hear you have a working phone again! The lack of touchscreen response & the stuck at the hello screen issues are what others have reported when they used a boot image from a different version than on the phone. I suspect that something got confused between the version & slot somewhere along the way. As far as the Lenovo Rescue software not seeing the phone, it's communicating via ADB. If I recall correctly I needed to reauthorize the PC to connect via ADB after updating from 30.80-58 to 30.80-58-3. When I connect the phone via USB there's a popup on the phone asking to authorize the PC. Can you connect via ADB in the command line? If yes, you may want to reinstall the Lenovo software. If no, I would troubleshoot the ADB connection.
I originally rooted the 30.80-58 version. When 30.80-58-3 was released all I did was flash the unpatched boot.img, took the update OTA, let it reboot, then flash a patched boot.img from 30.80-58-3. All worked as expected, user data was intact.
Click to expand...
Click to collapse
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?

DougPeterson said:
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?
Click to expand...
Click to collapse
If you want to get into recovery, boot into the bootloader than do
Code:
fastboot reboot fastboot
That'll boot you into fastbootd which has an option to go to the real recovery

DougPeterson said:
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?
Click to expand...
Click to collapse
If adb isn't showing any devices connected that would explain why the rescue software cannot find your phone. Perhaps you don't have the correct driver installed. Windows Device Manager shows the phone as a Motorola ADB Device on my PC.
View attachment 5061327
Another possibility is that you have multiple versions of adb on your PC. Older versions won't work but the adb.exe in "C:\Program Files (x86)\Rescue and Smart Assistant" works for sure. With your phone booted into android & unlocked, plug it into your PC. Do you see the "USB debugging connected" on the phone? If you don't I would re-check that USB debugging is enabled. If you do see the debugging notification, on your PC, open a command prompt and navigate to "C:\Program Files (x86)\Rescue and Smart Assistant". Run
Code:
adb devices
Does adb find your phone?