[Q] Having a hard time starting. Need help getting passed this seemingly minor issue.

I'm following a course from StackSkills to learn how to develop applications. I'm using Andriod Studio SDK. I am still in the absolute beginning and in the video it showed to drag a widget to the "phone?" and when I tried doing that it didn't allow me to. When I try to drag onto the phone it displays a "cancel" symbol where the pointer would be. I apologize beforehand if this is not the proper location for the thread. I'm new here as well. Thanks for any help.

[HOW TO FIX] all Fix Unbrick hard bricked Moto G 4.4 an 5.0

1。download the HS USB Driver to install
•Riff BOX JTAG drivers + Driver Signature Enforcement Overrider

2。download Fix Unbrick DownloadTool Unzip，open the DownloadTool run start auto Fix Unbrick done:good::good:
http://www.mediafire.com/download/rn...Fix_MoTo_G.rar

Moto e 2nd gen 4g is hard bricked............

My Moto e 2nd gen 4g is hard bricked. Its not opening anything. When connected to computer it shows QHSUSB_BULK. I have searched and installed the driver software but the blank flash(it is first gen moto e's) is not working. Can anyone help me to solve this problem?

Lg l90 d405n hard bricked

Hello,
after weeks of research and trying I'm here to share with you my problem.
Before some weeks I tried to unlock the bootloader of my lg l90, I got an error message and then it died, or that I thought.
The phone has no download mode, recovery, anything, it has just a black screen. Searching the web I found lot of people having the same problem as me, although none of the solutions I found online was able to fix my device. As some other people have the same problem it would be good if we could fix it.

What I've got:

• Black screen lg l90 d405n


• windows pc


• ubuntu pc


• image & verinfo folders if I connect my phone to a windows pc


• all partitions of the phone when I connect it on a ubuntu pc

What I've tried:

• Lg flash tool (and official kdz )


• pushing aboot (and some other files) through terminal


• b2b

Having a solution (or an idea of solution) please share it below :D

[Help] HiSense U970 hard bricked

Hello guys, I have a HiSense U970 with the MT6589 chipset which got hard bricked a week ago. The phone is running a stock 4.2.1 JB and rooted. The problem is that whenever I try to flash anything using SP Flash Tool it shows this error:

BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032)
[EMI] Enable DRAM failed

I am hopeful the phone isn't totally dead since it can be:
- Detected by the computer WITHOUT the battery while holding vol down
- In Device Manager, it would show MTK USB Port (ComX) under Ports when vol down is held.

This is what happens now:
- Charging does not do anything.
- Cannot boot into recovery
- Cannot be detected by MTK Droid Tools (but I think this app needs a powered up phone to be detected by its system)
- Cannot flash anything using SPFT v3.1320.0.174 and v5.1524.00

I have searched the internet for fixes and solutions but, everything that I have found leads to that error.
Here was what I had done before the problem arose.
- Installed Preloader driver
- Used the latest version of SPFT
- Formatted whole flash except bootloader as I cannot flash the cwm rom found here without formatting
- Flashed ONLY the recovery and then downloaded it.
Green circle appears and after that, it cannot boot anymore. Cannot charge. Cannot boot into recovery.

I have tried the following with no luck:
- Used SPFT v5.1524.00 and v3.1320.0.174
- Flashing only the preloader
- Flashing only the recovery
- Format whole flash
- Formatting whole flash except bootloader
- Format all + download (v5)
- Firmware upgrade + upgrade (v3)
- Using the write memory method for writing preloader
- Flashing stock preloader
- Doing a memory test
All of which goes to the error 4032.

I have also tried using different USB ports with the same results.

If it helps, I used the scatter file for MT6589 and not my own scatter file. Using my own scatter file does not do anything before I flashed the recovery rom so, I used the MT6589 scatter file instead. Also, my scatter file was different from the MT6589.
- This was the scatter file I used.
- And this is my log from MTK Droid Tools which hopefully contains the addresses for the scatter file (I accidentally replaced my own [yea i know, stupid me])
I also cannot find the same scatter file that I had created anywhere on the internet.

I am willing to supply you with anything as long as I have access to it (hoping I have the file/information you need:fingers-crossed:).

I am hoping that you know or at least the very least, can guide me out of mine and others misery. Thank you. :fingers-crossed:

[Q] Hard Bricked (qhsusb_bulk) XT1072 (Moto G - 4G LTE 2nd gen )

Hi everyone,
My brother has a Motorola XT1072 (Moto G - 4G LTE 2nd Gen) and he has bricked the device. He was playing with fastboot...
So, currently he has a totally dead phone (can't boot, no LED when charging, etc.)
When I plug the device to my computer, the only thing I see is that it's detected as qhusb_bulk (under windows and before the driver installation) and as Bus 001 Device 014: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode) (under linux with a lsusb).

I finally found a solution to a similar problem : http://forum.xda-developers.com/moto...oto-g-t2833798
So I tried qboot on Linux and Windows, and always failed with the same error : FAILED (blank-flash:greet-device:unexpected packet).

Qboot is detecting my device :

Code:

---

[root@rincevent blankflash]# ./qboot devices
/dev/ttyUSB0        "QCOM emergency download"

---

But when I try a blank flash, it doesn't work :

Code:

---

[root@rincevent blankflash]# ./qboot blank-flash --debug=2
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - No data from serial, retrying...
D - No data from serial, retrying...
D - No data from serial, retrying...
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - No data from serial, retrying...
D - No data from serial, retrying...
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - No data from serial, retrying...
D - No data from serial, retrying...
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - No data from serial, retrying...
D - No data from serial, retrying...
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
FAILED (blank-flash:greet-device:unexpected packet)

---

And my qboot.ini :

Code:

---

# MSM8626
[config 0x801]
  programmer=programmer_8626.mbn
  singleimage=singleimage_8626.bin
[config 0x805]
  programmer=programmer_8926.mbn
  singleimage=singleimage_8926.bin

[diag error.0x0001090D]
  count=5
  message="blank-flash:greet-device:error reading packet"
  last-seen="Sat Oct 24 16:48:18 2015, CEST"
  first-seen="Sat Oct 24 16:15:24 2015, CEST"
  chip=
  chip.sn=0x0
  chip.id=0x0
  chip.rev=0
  chip.sv-sbl=0
  qboot.version=2.4
  hostname=rincevent
[diag blank-flash]
  fail=5
  pass=0
  yield=0.00%
  dphu=100.00

---

Conclusion : qboot is detecting my device but can't flash it. They don't speak the same language :'(

My Goal : Reinstall Flashboot on my device

Now, I'm only guessing, and will take any advice which could help me.

--> I suppose that I need a newer version of qboot, or at least a newer version of programmer.mbn and singleimage.bin

--> I've found this repository, which aims to ease qboot usage : https://gitlab.com/Negan1911/motofla...er/MotoFlasher
There is a repository inside, with many qboot version : https://gitlab.com/Negan1911/motofla...sher/Component
I don't understand what are falcon and ghost, how this guy found this files, etc.

I'm a bit lost, here are some question :

• I can't find any other qboot version. Is it a leak ? or community made ?


• What are falcon_444, falcon_50, ghost, ... ? What is the code name of my phone ?


• How do I know which version of programmer.mbn and singleimage.bin I need ? And what is the number : programmer_8926.mbn; programmer_8626.mbn


• Can someone with a XT1072 can rip programmer.mbn and singleimage.bin for me ?


• Are programmer.mbn and singleimage.bin are community made ? Or is it a leak ?


• Can I use another tool (other than qboot) to communicate with my device (this "QCOM emergency download") ? Is there a specification somewhere to understand how it works ?


• Is my previous android version important ? Why ? Fastboot is changing between android version ? I read somewhere that's encrypted, isn't it ?


• Could I use a tool like emmc_recover[y] and how ? http://forum.xda-developers.com/show...&postcount=249 or https://github.com/Fuses/emmc_recover

Thanks by advance for your help,
Please be comprehensive if I've forgotten a rule of this board, I'll do my best to correct this post if necessary.

Lg G4 hard brick... need help please wiling to donate cash.

Hi everybody..
I'm in desperate need of help. After attempting to root my g4 somehow something went wrong and the phone is completely dead with no sign of life . I know there isn't a way yet to unbrick the g4 but I'm hoping somebody out there is working on it and maybe can help me out.. I'm willing to donate for the help Thank you !

Is there any possiblity to fix zenfone 2 hard brick? still havent found any fixes

zenfone 2 show a usb logo and cant access to recovery mode..many of us were researching for the fix of it but dont know how far it goes. All we need os dnx and os image to flash the boot..is there any help..please help me out :(

How to make a hard reset?

Hi
How to make a hard reset in these phone?
Thanks

Enviado desde mi E5823 mediante Tapatalk

Is it Hard Bricked or Boot loader problem? help need

It think I posted this in the wrong Forum? so I have posted it here.
The pictures I took on the phone disappeared all 300+ pictures disappeared .I am the only one using the Samsung
and it was on my table all that day. So I went to google to find a photo recovery software & found a software called
Wondershare Dr.Fone for Android (you can find videos on youtube) & using the software it can do 2 things, auto root the phone to find the photos and bring it back to normal or you Have to have your phone rooted. The auto root setting was not working on the Wondershare Dr.Fone for Android software so I went to the google play store on my Samsung and found a root app that a lot seem to like as it was 4.4 stars, went to install that the app stated I should have "Kingo SuperUser" on my computer so had that put on the went to root the phone & it did not work.
I got a screen on the Samsung saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Youtube had a video on this same problem so I went to Sammobile's site and download the firmware what was
"2014-06-11 USA(Verizon) Version 4.4.2 PDA (I605VRUFND7) Kies. After I downloaded that I downloaded Odin3_v3.10.6 opened it had auto "Reboot & F.Reset Time" selected and added the firmware MD5 file add in the "AP" secion then Entered Download mode on the Samsung & hooked it up to my computer
then I hit start about 30min later it Passed with a green light and everything seem back to normal 3 hours later I went to turn the Samsung off and latter that night when I went to turn it on it got stuck at the Samsung logo that happen 2 times and on the third time it did not come on & so can't "enter download mode" and the "usb Jig" did not work.
What happen & what do I need to next. Do I take the phone to someone to fix this.

Short version of the story :)
.Pictures I took 300+ disappeared so when looking for recovery software

.Found a software called "Wondershare Dr.Fone for Android" (the software had "2" Options for recovering. 1 the software would
Auto Root and bring the Samsung back to normal after recovering the pictures or I would have to had the phone already rooted.

. When to the google play store with the Samsung, found a root app download that & "It stated I should download "Kingo SuperUser" to my computer so I did that.

.It failed & got a screen on the Samsung Saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".

.Went to Sammobile's site and download Firmware 2014-06-11 USA(Verizon) Version 4.4.2 PDA (I605VRUFND7) Kies

.Download Odin3_v3.10.6 had auto "Reboot & F.Reset Time" selected and added the firmware MD5 file add in the "AP" secion
Entered download mode & the Samsung passed

.Everything was back I had it on for 3-4 hours then shutdown the phone later that night went to turn on and it got stuck
at the Samsung logo 2 times and on the 3rd time it would not turn on nor enter "Download Mode"

.Got a "usb Jig" & that did not work and now I am here wondering what do next & what happen to my Samsung Galaxy Note 2 do I need to take to someone to fix it ?

Samsung Galaxy Not 2 Unlocked
SCH-I605V version (Verizon)
my battery was %70 full
when it was in "Odin Mode " it stated
Current Binary: Samsung Official
System Status: Official
RP SWREV: A3

64gb Micro SD Android Support - 32 GB Hard Limit?

Hi All,

I'm looking for an Android phone as a cheap, large capacity MP3 player. I currently have an iPhone 5S 32GB, but I have a pretty extensive music collection that I'd like to store on one device.

I've been looking on eBay as well as using GSMArena.com and 95% of the Android phones state that they only accept 32GB Micro SD cards. Is this a hard limit?
There's only one Android phone I've found that accepts 64GB cards - Samsung Galaxy Trend Plus S7583T
Am I going to run into problems if I try to use a 64GB card in any of the other Android devices? Can I get around the 32GB limit?

Thanks in advance!

PS - I apologise if I've placed this in the wrong forum!
PS #2 - I'm also interested in any Windows Mobile devices that support 64GB microSD cards!

hard brick

Any development in the hard birck of g4 or not?

Post to factory reset _ Micromax a1 hard brick

Post to factory reset Micromax a1 has hard bricked. Its not turning on. not boot logo. Never rooted. Current OS Marshmallow. But whenever I connect it with laptop, Laptop is detecting and giving back a sound.

Can someone help here.