Database Develop

I Bricked My Phone

Hi everyone, as you can see in topic I bricked my phone. or at least I think I did it.
To make a long story short - my brother gave me Xpera T, I installed cm12 but had problems with gapps (google apps has stopped), then I tried to remove it to have clean install and got the situation in recovery "can't mount cache/system..."
Then I tried parted /dev/block/mmcblk0 mkfs ext2
But, after I did it I restarted phone and now I can't turn it on. There is no any sign it's alive. Like a brick :-/
When I connect phone to computer and try power+up it won't enter recovery mode so I can't use ADB or Fastboot.
Only trace that phone exists shows dmesg command:
[ 135.031450] usb 3-5: new high-speed USB device number 9 using xhci_hcd
[ 135.196087] usb 3-5: New USB device found, idVendor=05c6, idProduct=9008
[ 135.196095] usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 135.196100] usb 3-5: Product: QHSUSB_DLOAD
[ 135.196103] usb 3-5: Manufacturer: Qualcomm CDMA Technologies MSM
[ 135.196734] qcserial 3-5:1.0: Qualcomm USB modem converter detected
[ 135.197345] usb 3-5: Qualcomm USB modem converter now attached to ttyUSB0
So, is there any hope that I coul'd repair it, or the garbage is the right place for it?
Thank you!

Here's how to unbrick.
First turn off the phone and connect the phone to the computer while holding the volume down button. Wait for few minutes until the drivers are installed correctly. now you can disconnect the phone.
1. Download and install flashtool.
2. Download the stock rom for your device. Click here for a list of stock ROMs.
3. Right click and copy the downloaded file, and go to C:\flashtool\firmware\ and paste.
4. Open flashtool. Click the "lightning" symbol and select "flashmode" and click OK.
5. Select the file name you just downloaded, Put a tick on "No final verification" and click "flash".
6. Wait for a minute or two until you get a popup window. (It will say "press the back button and connect the phone to pc". But DO NOT do that)
7. Now turn off the phone. Connect the USB cable to the computer, but don't connect it to the phone yet.
8. Press and hold the volume down button. Keep pressing and connect the USB cable to the phone.
9. Release the volume down button as soon as the popup window go away.
10. DO NOT disconnect the USB cable until the flashtool say "Flashing completed".
11. Now unplug the cable and turn on the phone. It will take a few extra minutes to boot for the first time.
Hit the thanks button if this helped. :good:

The file I need to download is no longer available, can you upload it again?

marko-marko said:
The file I need to download is no longer available, can you upload it again?
Click to expand...
Click to collapse
Done. Checkout the post #2
All the links are updated.
Be careful what ROM you download. Double check the Model no. of your phone and the ROM. They must match.

I did everything you said until number 9 (Release the volume button as soon as the popup window go away) because that window never got away.
In flashtool windows says:
Device connected with USB debugging off
For 2011 devices line, be sure you are in MTP mode
Device disconnected
On mobile turns on red light when it's connected to USB, but turns off very soon, after flashtool says it's disconnected.

marko-marko said:
I did everything you said until number 9 (Release the volume button as soon as the popup window go away) because that window never got away.
In flashtool windows says:
Device connected with USB debugging off
For 2011 devices line, be sure you are in MTP mode
Device disconnected
On mobile turns on red light when it's connected to USB, but turns off very soon, after flashtool says it's disconnected.
Click to expand...
Click to collapse
Did you do the step 7 right? did you turn off the phone before connecting the cable?

Yes, the phone is turned off. It can't be turned on after I bricked it

marko-marko said:
Yes, the phone is turned off. It can't be turned on after I bricked it
Click to expand...
Click to collapse
I edited the instructions. Give it a try. Hope this will work :angel:

InfinitelyCrazy said:
I edited the instructions. Give it a try. Hope this will work :angel:
Click to expand...
Click to collapse
Nothing, same as the last time.
Firstly I have removed the battery for 15 minutes and than installed driver.
I followed procedure, but again number 9 never happened.
I tried to update driver for qualcomm (that is mobile) but it says that it's already updated.

OxygenOS install bricked my phone (and there are no Windows machines around)

I think I've managed to successfully brick my phone through the following process...
1. boot into recovery
2. enable sideload mode
3. adb sideload the OxygenOS beta 9 image (downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_9/)
Everything went smoothly and the sideload process finished successfully. Rebooted the phone, wandered away for a bit...and now it's just a black screen that won't turn on. Plugging it into my laptop I see that is identifying itself as a QUSB__BULK device:
Code:
usb 1-1.4.4: new high-speed USB device number 18 using xhci_hcd
usb 1-1.4.4: New USB device found, idVendor=05c6, idProduct=9008
usb 1-1.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1.4.4: Product: QUSB__BULK
usb 1-1.4.4: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 1-1.4.4:1.0: Qualcomm USB modem converter detected
usb 1-1.4.4: Qualcomm USB modem converter now attached to ttyUSB0
What are my options at this point? All of the recovery guides I've been able to find so far start by downloading some Windows utilities, and I don't have easy access to a Windows machine.

Use the Hard Brick guide, download the full tool unbrick guide and it should work fine, follow method 2. you can find hard unbrick guide on google.

Unfortunately, the hard unbrick guide (if you mean forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/) seems to be Windows-only (it has instructions for downloading lots of Windows device drivers, etc), and as I said in my original question, I don't have a Windows machine handy.

So I have not looked alot around but I haven't seen any guides or something for Linux, but 2 ideas:
1: try that guide, maybe Linux won't need the drivers and it would work just fine.
2: you can download a windows image, install it on a Virtual Machine,unbrick your phone and then delete the VM and everything.

Is your phone's bootloader unlocked? If yes, things will much more simple.
anyway, try download full 3.2.8 ROM from OP site, boot your phone to fastboot mode and sideload it.

Cannot see my OnePlus 3T with fastboot with Ubuntu 16.10 Yakkety Yak

I'm using Ubuntu Yakkety Yak, 16.10.
According to Android SDK manager: Android SDK Tools v 25.0.3 Android Build Tools v 25.0.2 Android SDK Tools v 25.2.5
My phone is a OnePlus 3t and I'm developing for it for a while, adb works normally, udev rules are configured. I enabled OEM boot, and manage to reboot in a way which looks like to me fastboot. After rebooting to "fastboot" the device's USB id is exactly the same as in normal boot, that's a red flag.
Regular USB ID is Bus 001 Device 024: ID 05c6:676c Qualcomm, Inc.
I get the desired fastboot one when I switch the USB mode to MTP (Bus 001 Device 013: ID 2a70:9011).
My final goal is to unlock my phone ans install TWRP (for DayDream mod). Since fastboot devices doesn't show any device I cannot issue fastboot oem unlock.
Do I need some USB driver for Linux for the MTP mode? The Bus 001 Device 013: ID 2a70:9011 doesn't show any OEM manufacturer string.
This should just work. I don't get it. I'm tearing my hair out.
android.stackexchange.com/questions/169509/why-fastboot-devices-is-empty-on-ubuntu-16-10
android.stackexchange.com/questions/166033/how-to-flash-and-root-oneplus-3t-on-linux?noredirect=1&lq=1

MrCsabaToth said:
I'm using Ubuntu Yakkety Yak, 16.10.
According to Android SDK manager: Android SDK Tools v 25.0.3 Android Build Tools v 25.0.2 Android SDK Tools v 25.2.5
My phone is a OnePlus 3t and I'm developing for it for a while, adb works normally, udev rules are configured. I enabled OEM boot, and manage to reboot in a way which looks like to me fastboot. After rebooting to "fastboot" the device's USB id is exactly the same as in normal boot, that's a red flag.
Regular USB ID is Bus 001 Device 024: ID 05c6:676c Qualcomm, Inc.
I get the desired fastboot one when I switch the USB mode to MTP (Bus 001 Device 013: ID 2a70:9011).
My final goal is to unlock my phone ans install TWRP (for DayDream mod). Since fastboot devices doesn't show any device I cannot issue fastboot oem unlock.
Do I need some USB driver for Linux for the MTP mode? The Bus 001 Device 013: ID 2a70:9011 doesn't show any OEM manufacturer string.
This should just work. I don't get it. I'm tearing my hair out.
android.stackexchange.com/questions/169509/why-fastboot-devices-is-empty-on-ubuntu-16-10
android.stackexchange.com/questions/166033/how-to-flash-and-root-oneplus-3t-on-linux?noredirect=1&lq=1
Click to expand...
Click to collapse
Just OEM unlock from the settings...

domsch1988 said:
Just OEM unlock from the settings...
Click to expand...
Click to collapse
I wish it was that easy. The Settings option is more precisely called "OEM unlocking" with the explanation "allow the bootloader to be unlocked". So it just allows it, but does not do the unlocking itself. I turned this option on. For the unlocking I should issue the fastboot oem unlock command. I did try to install TWRP BTW without it, but obviously it didn't succeed. I need to unlock first, just as other tutorials say. For that I first have to see my phone in the fastboot devices list, which is empty. I'm still tearing my hair out.

MrCsabaToth said:
I wish it was that easy. The Settings option is more precisely called "OEM unlocking" with the explanation "allow the bootloader to be unlocked". So it just allows it, but does not do the unlocking itself. I turned this option on. For the unlocking I should issue the fastboot oem unlock command. I did try to install TWRP BTW without it, but obviously it didn't succeed. I need to unlock first, just as other tutorials say. For that I first have to see my phone in the fastboot devices list, which is empty. I'm still tearing my hair out.
Click to expand...
Click to collapse
Try running
Code:
sudo fastboot devices

casual_kikoo said:
Try running
Code:
sudo fastboot devices
Click to expand...
Click to collapse
Yes, sudo didn't make any difference from the beginning.

Hello,
I too am going crazy trying to get fast boot to work on this OnePlus 3T. My research prior to purchasing indicated that this phone was friendly to rooting. I'm no on hour 6, and still can't get fast boot to work. Using Ubuntu 16.04, and the adb and fastboot packages installed from the standard repositories (apt-get install adb..)
sudo, sudo -s, udev rules, etc. nothing has worked.
If anyone has used this phone and os combination to get the unlocking working, please advise.

I've found out the root cause of my problem. I thought that fastboot is one step further from the "actual" fastboot screen. You have to issue the fastboot commands when you see the screen what is in my android stackexhange link.

So I could unlock the bootloader now, now when I try to flash TWRP I get:
Code:
[email protected]:~/Android/Sdk/platform-tools$ sudo ./fastboot flash recover twrp-3.0.3-1-oneplus3t.img
target reported max download size of 440401920 bytes
sending 'recover' (17588 KB)...
OKAY [ 0.560s]
writing 'recover'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.580s

The USB device I see is
Code:
Bus 001 Device 018: ID 18d1:d00d Google Inc.
and I set up udev rules for it.

Ok, it was just a typo: recover -> recovery

Finally!
Thank you MrCsabaToth!
After 2 more hours trying this following instructions for Windows 7, and OS X (after Ubuntu 16), MrCsabaToth's reply looks to be the way to get past the fastboot oem unlock step.
You have to run it while actually on the phone's boot screen where it gives you options of what type of boot to do, where the top line option is "fast boot". Only then, will the fastboot command from the terminal work.
Not even the oneplus web site tutorial, which is for this exact phone, mentions this. WTF......

Bricked Redmi 4a

Hi folks, lately I wanted to root my phone to disable annoying storage shortage popups, and chose path of TWRP (twrp-3.2.2-0-rolex) + SuperSU (SR5-SuperSU-v2.82-SR5-20171001224502)
But after I flashed recovery partition with fastboot I wasn't able to boot my device, was continuously seeing MI logo.
By the way after I flashed recovery partition I checked boxes to install TWRP app.
I was following instructions in this thread: https://forum.xda-developers.com/redmi-4a/how-to/root-redmi-4a-t3726735
But as a result I wasn't able to boot my device, after some more lookup in one of forums I read that problem could be solved by replacing aboot system file with file provided by author.
Problem is that that file was prepared for Redmi 3S, while mine is 4A.
As a result I have totally bricked phone, which doesn't want to boot, even display is not turning on.
After leaving phone for few days, i started to see that hope as red LED light on home button was blinking when holding power button.
Now in my Linux machine I see these logs:
usb 1-2: new high-speed USB device number 9 using xhci_hcd
usb 1-2: New USB device found, idVendor=05c6, idProduct=900e
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2: Product: QHSUSB__BULK
usb 1-2: Manufacturer: Qualcomm CDMA Technologies MSM
Anyone have idea how I can get access to internal storage again?
I want to replace that aboot file with original one, and continue solving ROOTing issue.
Thanks in advance!

clumsywalker said:
Hi folks, lately I wanted to root my phone to disable annoying storage shortage popups, and chose path of TWRP (twrp-3.2.2-0-rolex) + SuperSU (SR5-SuperSU-v2.82-SR5-20171001224502)
But after I flashed recovery partition with fastboot I wasn't able to boot my device, was continuously seeing MI logo.
By the way after I flashed recovery partition I checked boxes to install TWRP app.
I was following instructions in this thread: https://forum.xda-developers.com/redmi-4a/how-to/root-redmi-4a-t3726735
But as a result I wasn't able to boot my device, after some more lookup in one of forums I read that problem could be solved by replacing aboot system file with file provided by author.
Problem is that that file was prepared for Redmi 3S, while mine is 4A.
As a result I have totally bricked phone, which doesn't want to boot, even display is not turning on.
After leaving phone for few days, i started to see that hope as red LED light on home button was blinking when holding power button.
Now in my Linux machine I see these logs:
usb 1-2: new high-speed USB device number 9 using xhci_hcd
usb 1-2: New USB device found, idVendor=05c6, idProduct=900e
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2: Product: QHSUSB__BULK
usb 1-2: Manufacturer: Qualcomm CDMA Technologies MSM
Anyone have idea how I can get access to internal storage again?
I want to replace that aboot file with original one, and continue solving ROOTing issue.
Thanks in advance!
Click to expand...
Click to collapse
Your better choice must be flash with fastboot method. You did some mistakes its better do a clean flash. If you have some sensors or wifi issues after that you must do a edl mode flash.
Your problem was you don't flashed lazyflasher to remove the crypto of the data partition

manucarcor said:
Your better choice must be flash with fastboot method. You did some mistakes its better do a clean flash. If you have some sensors or wifi issues after that you must do a edl mode flash.
Your problem was you don't flashed lazyflasher to remove the crypto of the data partition
Click to expand...
Click to collapse
Try with test point. I do before when i put miui 10 for mi 6.

Did you fix it?
If not then short the test point . In your device manager on the PC you make sure that there is Qualcomm hs-usb qdloader 9008 port and use a old version of Mi Flash tool 2015 because latest version of Mi Flash tool can't detect it after that download the Global ROM flash it via MI Flash tool and get the magic done make sure you select flash all .....

Complete Wipe system , dalvik and cache , also vendor , data too and Install ROM as new ...

Yet again, Fastboot is stuck on “Sending 'boot.img'”

Fastboot version 30.0.4-6686687
Trying to temporarily boot TWRP recovery image twrp-3.4.0-0-lake.img on my unlocked Motorola Moto G7 Plus.
Phone is connected via USB Type-C to Type-C cord from the box to my laptop running Linux (Manjaro 20.0.3) Live USB system.
When I run ./fastboot boot twrp-3.4.0-0-lake.img or ./fastboot boot boot.img (same file, renamed) with and without sudo, it always gets stuck at Sending 'boot.img' (30080 KB) doing nothing.
Bootloader logs section of fastboot mode shows only cmd: download:01d60000.
The PC I use now is the only PC that helped me to actually unlock the bootloader. Other PCs I have were not able to send correct fastboot commands (for example, oem help transformed into oem helpersion, and oem get_unlock_data cut to oem get_unlock). Those PCs had regular USB Type-A 3.0 ports, so I had connected them to my phone with corresponding 3rd-party cable. It might've been of insufficient quality though.
All files are located near to the root of extrenal SSD connected to another Type-C port, so the absolute paths to TWRP image and fastboot executable should not be too long.
Type-C cords I'm using now are new and OK.
Motorola doesn't distribute Linux drivers for their devices.
What else could be wrong here? Please help. Any advice is appreciated.
Will update this post later with my own findings as well for people who could stumble a similar problem.
Update 1
Tried fastboot boot boot.img on another PC. It is also running Linux (Ubuntu 20.04). Connection is from Type-A to Type-C. Wire is good. No noticeable changes. Main issue persists.

What does "fastboot devices" say? Try running the commands with root and with a different USB cable.
Edit: It should work. I just bootet TWRP 3.4.0-0 several times. I used Fedora Linux with android-tools-20180828gitc7815d675-4.fc31.x86_64 which includes fastboot. BL on device is MBM-3.0-lake_retail-38523c9-200214

Any further update on that ?
Same happens with my device (motorola one power).
The bootloader logs shows "cmd: download:<8 letter hash/code>"
And cancelling the operation doesn't do any harm, just your next command will fail with
"FAILED (remote: 'unknown command')", and bootloader logs will print an empty line starting from cmd:.
Did it work later on, what change did it require if you remember a bit ?
Update: The OP has put the question on reddit:
https://www.reddit.com/r/MotoG/comments/iwcx2v
The solution that worked for him was using windows... dont get angry sometimes we have to use the unused : )

SOLUTION: connect the phone using a USB hub
When plugin the G7 Plus, functioning MTP and ADB, but fastboot “Sending 'boot.img'” dont worked properly
The HUB worked for me, even in the same port
Regards

Hello!
I came here, just to say that I had the same issue with my Moto Z3 Play (beckham), when trying to fastboot boot. It was stuck in "Sending 'boot.img'".
Doesn't make any sense, but when I tried the solution of USB Hub, it worked. Command was accepted and loaded as it was normal as usual.
Thank you very much for this tip!
Best regards