Database Users

PLS HELP.. Bricked !

Last night I accidentally flashed Samsung Galaxy S2 WIUI ROM on my defy. When restarted, the 2nd init recovery is not working
Unable to boot into the OS. The screen is at the Motorola M logo indefinitely. The only recovery that 'seems' to be a bit working is the stock recovery. But it has only install sdcard/update.zip option. When I give any ROM there, it says failed to verify signature. I renamed an official MIUI release (2.4.20) to update.zip and tried.
I tried to flash the sbf file. But the RSD lite tool is not showing my phone when connected to the USB.
Can someone tell me what needs to be done. Since the phone is rooted, it's not under warranty too

Please read the all in beginners guide. If it didn't work, please post here again.
Verstuurd van mijn MB525 met Tapatalk

I tried everything. Now, the battery doesn't seem to be charging too. it shows a ? icon in the battery screen.

tinyutilsdroid said:
I tried everything. Now, the battery doesn't seem to be charging too. it shows a ? icon in the battery screen.
Click to expand...
Click to collapse
Then you can boot in a rom?
Verstuurd van mijn MB525 met Tapatalk

tinyutilsdroid said:
I tried everything. Now, the battery doesn't seem to be charging too. it shows a ? icon in the battery screen.
Click to expand...
Click to collapse
Probably battery is flat, but you can`t charge it normal way if the system isn`t loaded.
Now you have two options:
1. charge it a`la McGyver
2. buy a wall charger for defy battery (6-8 quids on ebay)

Thanks everyone. Yes, the battery was dead. I had to buy a battery charger to charge up and used rsd lite to restore.. Again, thanks to all the geniuses for building tools and writing up detailed notes!!
Sent from my MB525 using xda app-developers app

[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus X

A Big Thanks to @Synthio for providing me these files.Without his help,this guide wouldn't have been possible at all. ​
Hi Peeps !!
A hard bricked OPX has nothing but a black screen (nothing ever comes on the screen, not even a boot logo ), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition. The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OPX should be detected as QUALCOMM-HS USB Diagnostics xxxx. You might have a bricked OPX as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition.
The solution for OPX hardbrick is similar to OPO and OP2 - you just need a Qualcomm driver and a recover package.
So,here we go !!
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753 (Extract these files to a folder on desktop.)
2.) Recovery Tool :- https://drive.google.com/folderview?id=0B3gqVK2lYqBiY1M2NjRjVllvYXM&usp=sharing (Download all files inside this folder and put them in a folder on desktop.)
Step 2 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 sec and while keeping it pressed,connect OPX to PC.Hold volume up until your PC finds a new hardware .
Step 5 :- Go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics xxxx" device or something like this (It must be Unknown Devices as QHUSB_BULK or under COMs and Ports as Qualcomm xxxx). Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Step 6 :- After installing the drivers,"Run As Administrator" the MSMDownloadToolV2.0 in the recovery tools folder.
Step 7 :- Click start at top left corner and wait for it to finish (Download Complete will come)
Step 8 :- Disconnect phone from PC and boot into system.
Now you can again do anything you wish to (unlock bootloader,etc).To unlock bootloader,go to developer options and tick "Enable OEM Unlock" first.
When you will need this guide ? :-
1.) If your phone is totally black (no racism)
2.) When you have locked the bootloader by mistake . (This happens when you flash a rom without having oem unlocking enabled.)
PS:- This method will wipe all data and restore your phone to OxygenOS and English Bootloader.
Thanks.
​

Hi
Great work!
I finally got a mod to close my thread and it has been closed.
I'll wait for the file that does not wipe /data

Thanks a loot. Gonna try it today at the end of the day.
Enviado do meu SM-N9005 através de Tapatalk

OnePlus*X*Unbrick Tool Mini... Only 47 MB is here :-
https://www.androidfilehost.com/?fid=24269982087019810
It doesn't wipe data either...
Sent from my ONE A2003 using Tapatalk

So if we are having the bootloader unlocked and try this tool to make it lock the bootloader? Means is it possible?

Silverstarjigar said:
So if we are having the bootloader unlocked and try this tool to make it lock the bootloader? Means is it possible?
Click to expand...
Click to collapse
No.It will keep the bootloader unlocked if it is unlocked already.

Man you are the real mvp... Thanks a lot some people i know are really screwed up because of thier opx got hard brick and there was no such guide available thanks alot mate really thanks

Will Try
Welp, ordered a new OPX yesterday. Just searched "qualcomm oneplus x driver" right when I woke up before work today and found this thread and felt stupid but saw it was as recent as today so I was pretty pumped. Thanks, will try ASAP and then can sell my other OPX, the new one or refuse delivery tomorrow . They deliver so fast now! 3 days!

thanks master sifoo.. my opx back to alive now ?

Thanks
Hello
Thank you for your post
I did all what's explained and when I run MSMDownloadToolV2.0 and click start it says "Waiting for device" and nothing happen!
I've been waiting more than 30 mints and nothing actually happen ..
Hope you help me ..
Thanks!​

DANETO said:
Hello
Thank you for your post
I did all what's explained and when I run MSMDownloadToolV2.0 and click start it says "Waiting for device" and nothing happen!
I've been waiting more than 30 mints and nothing actually happen ..
Hope you help me ..
Thanks!​
Click to expand...
Click to collapse
Can you give me Teamviewer access? I will see what the issue is and solve it.
Sent from my ONE A2003 using Tapatalk

Naman Bhalla said:
Can you give me Teamviewer access? I will see what the issue is and solve it.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
OfCourse
but I'll download it now and I'll tell you once I finished
Thank you

Naman Bhalla said:
OnePlus*X*Unbrick Tool Mini... Only 47 MB is here :-
https://www.androidfilehost.com/?fid=24269982087019810
It doesn't wipe data either...
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
So, if I used this Mini Tool, what would it change on my phone? Kernel, system, etc...
Thank you for your hard work.

DANETO said:
OfCourse
but I'll download it now and I'll tell you once I finished
Thank you
Click to expand...
Click to collapse
Hi !!
Has your issue been solved or you still need help ? I am online for some hours now.

Aphex13 said:
So, if I used this Mini Tool, what would it change on my phone? Kernel, system, etc...
Thank you for your hard work.
Click to expand...
Click to collapse
It will not change system but will restore kernel to stock.

Naman Bhalla said:
Hi !!
Has your issue been solved or you still need help ? I am online for some hours now.
Click to expand...
Click to collapse
I tried to solve it many times but still remains

DANETO said:
I tried to solve it many times but still remains
Click to expand...
Click to collapse
PM me now with Teamviewer ID and pass. I will fix it in any case.
Sent from my ONE A2003 using Tapatalk

Did layers work for anyone??
Sent from my ONE E1003 using Tapatalk

Thanks my phone's alive once again.
Sent from my ONE E1003 using Tapatalk

Sorry for my bad english
Can this tool unbrick any case of hard brick ? For example when I change the fastboot logo ? When I type 'fastboot erase bootloader' ?
Envoyé de mon ONE E1003 en utilisant Tapatalk

I broke my axon 7 HELP!!!!!

Hey Guys,
recently I tried to root my ZTE Axon 7 and install TWRP on it(A2017G)(Firmware B03).
It failed and i wanted to reinstall my bootloader and my recovery (i think that i wanted this)
Before i did that i backed up my boot and recovery is i´ve been told to.
I think something went wrong there, but i realised it too late.
When it was failed i didnt know how to reinstall the backuped boot and recovry files, so i thought i could rename them to boot and recovery and flash then with ADB. This failed either and now when i want to start my phone the screen that says ZTE pops up for a second and then goes black.
I know that was silly, but now my Phone is broken and i cant do anything with it, i can not start it, i can not boot in recovery, i can not boot to fastboot.
I tried to boot into Recovery Mode, but the same thing either...
The screen flashes and goes off.
I can´t do anything.
Also when i try to turn it on the LED on the top flashes red and green. I don´t know if its related to my problem, but i need help
PLEASE!!!
I don´t know what to do:crying::crying::crying::crying:

I've uploaded the A2017G B03 stock boot.img and recovery.img (both in the same zip file) to Mediafire, here's the link:
http://www.mediafire.com/file/lz2jco2np4innau/B03.zip

This happened once (well, more than once to be precise) to me too but there's a fix for it.
http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
What you want to do is follow all of the steps (using axon7root.exe) and use the boot.img and recovery.img provided by razorblader.

I don't think you will have a chance to bring it back to life. It looks like you are in DFU mode but need EDL mode for using tenfars tools.
Unfortunately for the G model you can't enter this mode with hw keys.
But I also have this issue and looking for a solution.
As of now only way is to send it in for repair...

I had the exact same problem and tried pretty much everything I could think off but as Deje63 mentioned the only way is to give it back to the seller and get a refund (if you still can) or send it in for repair.

Just today an Axon 7 owner in the german android-hilfe forum got information he will get a new Axon 7 from ZTE.
He did also send it in for repair because the same issue. It seems even ZTE (europe/germany) does not have the tools/knowledge to flash a stock rom on such bricked devices.
I ask myself what the hell they did or think in reducing the features (for the G model) in fastboot/adb/firmware to that grund. I am a long time in Android but never had a device were there was no chance to (re)flash at least an official stock rom.

themarcc said:
...
Click to expand...
Click to collapse
Try to access the FTM (Factory Test Mode) by holding the power button and the volume down button. It will say FTM on the display if it was successful.
In case you are still stuck in DFU mode you might have to hold the power button for at least 6 seconds to get the phone to try to reboot.
If you can get into the FTM mode connect the Axon 7 to your PC.
It should show up in the device manager as a Android ADB device.
adb reboot edl
Your screen should go blank and the device should show up as 'Qualcomm HS-USB QDLoader 9008 com X' in device manager. If you get this far you can use tenfar's axon7root.exe to flash the boot.img and the recovery.img and the phone should boot up normally after that.

Are you sure talking about A2017G? I was able to enter stock recovery (volume up and power). All other key combination leads to DFU mode, regardless the phone was plugged in or not. And believe me, I tried even stupid ones.
But will try when it is back from repair.

DeJe63 said:
Are you sure talking about A2017G? I was able to enter stock recovery (volume up and power). All other key combination leads to DFU mode, regardless the phone was plugged in or not. And believe me, I tried even stupid ones.
But will try when it is back from repair.
Click to expand...
Click to collapse
I'm talking about the G model of course, on the U version this wouldn't be a problem.
Hope other people who still have their bricked G version phones try this so we can clarify if there's a chance to get into the FTM mode and can determine which 'type' of brick could potentially be revived.
No clue if this is a possibility if the wrong kind/corrupt/whatever bootloader got flashed to the phone but it's worth a try.
Edit: Read in another thread that another user stuck in DFU mode on the G model couldn't make the FTM mode work so there's little hope for this to be working unfortunately.

I do have a question as well. My G model only boots til ENTER ANDROID PASSCODE. Cannot boot into recovery only FTM is possible. Device Manager indicates an adb device, but there seems to be a special driver. Does anyone know how to help?
Thanks in advance...Marcus
Gesendet von meinem Lenovo K50a40 mit Tapatalk

try it with "default_password" without the "

I just tried it several times. After some time it says: 'wrong password' , unfortunately
Gesendet von meinem Lenovo K50a40 mit Tapatalk

marcus.linkenbach said:
I just tried it several times. After some time it says: 'wrong password' , unfortunately
Gesendet von meinem Lenovo K50a40 mit Tapatalk
Click to expand...
Click to collapse
Hi Marcus,
I have got the same problem. Did you find any solution since then?
Anyone give me any suggestion please ... :crying:

Yes. The solution was to set it up for a repair. They changed my device without any problems. I told them my phone entered into this state by upgrading on an ota update.
sent from zte axon 7 with tapatalk

marcus.linkenbach said:
Yes. The solution was to set it up for a repair. They changed my device without any problems. I told them my phone entered into this state by upgrading on an ota update.
sent from zte axon 7 with tapatalk
Click to expand...
Click to collapse
Hi,
I have finally found the solution. I have boot into edl mode via FTM and re-flash TWRP then do a factory reset. Now, it coming back !!
:good:

dolvliz said:
Hi,
I have finally found the solution. I have boot into edl mode via FTM and re-flash TWRP then do a factory reset. Now, it coming back !!
:good:
Click to expand...
Click to collapse
Good to know. But for that I got second cable, charger, headset and cover ??
sent from zte axon 7 with tapatalk

[HELP] Bricked Samsung S8 (US T-MO version) with Qualcomm HS-USB QDloader 9008

Guys need help....I recently bought a Samsung S8 (t-mobile version) without knowing much of its history thinking it had a deeply discharged battery, but after a good 10 hrs on the charger it still won't turn on, no LEDs, no vibration, nothing, a complete black screen so it will NOT boot into recovery or download mode. However, it does seem to take a charge as the back side does get a bit warm when charged. When plugged into the PC (Win 10) it does not get recognized under My PC but I hear the USB plug-in chime and under the Device Manager, I get "Qualcomm HS-USB QDloader 9008" on COM port 3. From what I've found online, seems like I will need the original S8's complete eMMC image and load it onto the sdcard and recover it that way, even if it's possible.
Can anyone help/guide me in the proper direction? Really hoping to recover this device. This might even help others who may have or will brick their S8's. Hope we can find root soon if that's what's needed to fix this. Thanks a lot in advance

Anyone?! There has to be someone who can help me out here....

Display broken? For not getting an image when you plug in the power?
Have you tried pressing volume-down+bixby+power button for a full 10 seconds?
Verstuurd vanaf mijn SM-G955F met Tapatalk

Root is definitely not what you need to fix this device, root would be something to access the system on a fully functional device to begin with. Maybe try the Odin carrier switch method and see if that recognizes the device.
Where did you buy the device and what did they say was wrong with it? Do you have no option of returning it because it very well my have been messed with and have Knox tripped anyways.

Bisquit-02 said:
Display broken? For not getting an image when you plug in the power?
Have you tried pressing volume-down+bixby+power button for a full 10 seconds?
Verstuurd vanaf mijn SM-G955F met Tapatalk
Click to expand...
Click to collapse
Display is in like new condition, not even a blemish. No image upon power or on the wireless charging pad, the battery does get a bit warm when charging for few hours.
Yes, I have tried that exact combo for a good 60 seconds but nothing.

Either the battery is dead or a loose connection on the charger outlet.
Either way, it doesn't charge.
Verstuurd vanaf mijn SM-G955F met Tapatalk

whoamanwtf said:
Root is definitely not what you need to fix this device, root would be something to access the system on a fully functional device to begin with. Maybe try the Odin carrier switch method and see if that recognizes the device.
Where did you buy the device and what did they say was wrong with it? Do you have no option of returning it because it very well my have been messed with and have Knox tripped anyways.
Click to expand...
Click to collapse
The reason I commented about root was then someone can get a backup of the eMMC or a backup of the bootloader, so I can flash that, if that possibly fixes it. From what I can understand, something got corrupted and for that reason the device will not boot at all (nothing on the screen), so Odin is out of the question, since the device has to be in the Download mode for Odin to recognize it.
What I have found from further reading is that I can use QFIL (Qualcomm Flash Image Loader) to flash stock firmware since it recognized the S8 on COM port 3 when connected and QFIL recognized "Qualcomm HS-USB Qloader 9008" message, but what I have seen is people using MBN files (firehose.MBN) and an XML file to revive the phones. I've tried looking for those files even within the S8's stock firmware (AP, BL, CSC) but nothing.
Is there anyone who has experience working with QFIL who can guide me or provide with the files I need to flash this device back to stock.

Bisquit-02 said:
Either the battery is dead or a loose connection on the charger outlet.
Either way, it doesn't charge.
Verstuurd vanaf mijn SM-G955F met Tapatalk
Click to expand...
Click to collapse
Appreciate your input but it does charge

taj786 said:
Appreciate your input but it does charge
Click to expand...
Click to collapse
If u can return it go do it, thats not a issue that can be solved here im guessing is a hardware conection/display issue. If u cant reach download mode then i think u cant get help here

This is not hardware issue or anything like it. What youve done, same as I have, is wiped the download and recovery partitions of the phone. QFIL can fix this, but same as you I have not found the required files. I did find the programmer firehose but its an efl. I can not find the meta file it apparently needs. Did you ever fix this

taj786 said:
Guys need help....I recently bought a Samsung S8 (t-mobile version) without knowing much of its history thinking it had a deeply discharged battery, but after a good 10 hrs on the charger it still won't turn on, no LEDs, no vibration, nothing, a complete black screen so it will NOT boot into recovery or download mode. However, it does seem to take a charge as the back side does get a bit warm when charged. When plugged into the PC (Win 10) it does not get recognized under My PC but I hear the USB plug-in chime and under the Device Manager, I get "Qualcomm HS-USB QDloader 9008" on COM port 3. From what I've found online, seems like I will need the original S8's complete eMMC image and load it onto the sdcard and recover it that way, even if it's possible.
Can anyone help/guide me in the proper direction? Really hoping to recover this device. This might even help others who may have or will brick their S8's. Hope we can find root soon if that's what's needed to fix this. Thanks a lot in advance
Click to expand...
Click to collapse
No no no, display is fine, odin will not help you. Your phone is in a mode called edl. This happens when your bootloader is corrupt or unbootable for some reason. The bad news is this typically called a hard brick, as it requires special software to recover from that isnt available typically to the public.
Absolutely agree with the poster who said try and return it. This mode is very difficult to recover from, if its at all possible. There are tools that some of us have that might be able to recover it, but they havent worked on v2 bootloaders so far. The sdcard stuff doesn't work with the s8 as it was turned off due to security issues.
Let me know if you cant return it and I'll see what i can do, but no promises

partcyborg said:
No no no, display is fine, odin will not help you. Your phone is in a mode called edl. This happens when your bootloader is corrupt or unbootable for some reason. The bad news is this typically called a hard brick, as it requires special software to recover from that isnt available typically to the public.
Absolutely agree with the poster who said try and return it. This mode is very difficult to recover from, if its at all possible. There are tools that some of us have that might be able to recover it, but they havent worked on v2 bootloaders so far. The sdcard stuff doesn't work with the s8 as it was turned off due to security issues.
Let me know if you cant return it and I'll see what i can do, but no promises
Click to expand...
Click to collapse
Looks like I've done the same thing with S8+ G955F. I was trying to fix an FRP issue and flashed a mixture of Nougat 7.0, combination and CRED BL and now it just shows black screen, can't get to download mode. This was all done with Odin.

Bisquit-02 said:
Display broken? For not getting an image when you plug in the power?
Have you tried pressing volume-down+bixby+power button for a full 10 seconds?
Verstuurd vanaf mijn SM-G955F met Tapatalk
Click to expand...
Click to collapse
taj786 said:
Guys need help....I recently bought a Samsung S8 (t-mobile version) without knowing much of its history thinking it had a deeply discharged battery, but after a good 10 hrs on the charger it still won't turn on, no LEDs, no vibration, nothing, a complete black screen so it will NOT boot into recovery or download mode. However, it does seem to take a charge as the back side does get a bit warm when charged. When plugged into the PC (Win 10) it does not get recognized under My PC but I hear the USB plug-in chime and under the Device Manager, I get "Qualcomm HS-USB QDloader 9008" on COM port 3. From what I've found online, seems like I will need the original S8's complete eMMC image and load it onto the sdcard and recover it that way, even if it's possible.
Can anyone help/guide me in the proper direction? Really hoping to recover this device. This might even help others who may have or will brick their S8's. Hope we can find root soon if that's what's needed to fix this. Thanks a lot in advance
Click to expand...
Click to collapse
Good morning, my S8 and the same happened to me, to downgrade the oreo to the nougat; I did a JIG with resistors; When you download the keys, the JIG does not work on time, then after; I do not know how to say why.

then it means im doomed.. im experiencing the same shiiit
\

Brick Redmi 4 Prime ?

Hello,
i hink i have brick my redmi 4 prime. I have unlock bootloader. after this install twrp and i have boot to twrp all works fine. After this bootet to normal rom - works fine but after next reboot its stucks on mi boot logo.
I can go to Fastboot mode (Power+Vol. DOWN) but my PC dont find the redmi. When i try to go Download mode (Power+Vol.UP nothing happens. With Powser+VolUp and DOWN i can onley restart the bootlogo.
Have anyone a idea ?? sory for bad englisch

You could try a deep flash cable but if your last official rom before is a later one it shouldn't work and edl mode is blocked.
In this case you have to use the testpoint method.

As you can go to fastboot, situation isn't that bad yet. Try reconnecting your phone with pc and make sure the connection is good. Bad connection results in not finding the device in pc. Also, try different usb cable or port for connection failure.

Ok thanks guys its working now. After a little bit testing i come to recover Mode and have Flash New Firmware. All works fine. Thanks!
Gesendet von meinem Redmi 4 Prime mit Tapatalk