Develop Bugs

[Q]Hboot stuck on "Checking SD card update..."

Anyone got any idea why this might be happening?
One remark in the Revolution HD ROM thread suggested starting again from scratch (re-locking) - I hope that's excessive...
Do you think it's because of the amount of data on my SD? or perhaps I should remove a file it's getting caught up on?

[Fixed]
Either by unplugging the AC charger, or deleting a bundle of large, non-flashable .zip files on my SD card.

just had the same prob and thought i had bricked it...did a google and found your post unplugged it from the wall charger and it carried on loading...phew!
thanks for the tip

beanbean50 said:
just had the same prob and thought i had bricked it...did a google and found your post unplugged it from the wall charger and it carried on loading...phew!
thanks for the tip
Click to expand...
Click to collapse
yup mine from time to time does the same thing just unplug that thing and it fires away.

beanbean50 said:
just had the same prob and thought i had bricked it...did a google and found your post unplugged it from the wall charger and it carried on loading...phew!
thanks for the tip
Click to expand...
Click to collapse

Supaiku said:
Either by unplugging the AC charger, or deleting a bundle of large, non-flashable .zip files on my SD card.
Click to expand...
Click to collapse
This is why I love Google and XDA. Something so simple. Unplugged from the wall and panic over.

Just Me said:
This is why I love Google and XDA. Something so simple. Unplugged from the wall and panic over.
Click to expand...
Click to collapse
This! I already mildly panicked
Thanks for the help.

USB Powered problem?
Looks like the problem is not FIXED for me. I'm still stuck at the HBOOT checking SD card update screen while attempting to root the device. I just got the phone today and followed all instructions to successfully unlock the bootloader. Now this thing is driving me crazy. I read on another thread that the USB charging might contribute to this problem, but I really don't know how to fix this. The SD storage is at default state. I only copied the SuperSU zip file while following the instructions. Please help.
PS: I noticed that the phone is not fully charged. It is somewhere below 50% power. Could this be the case?

Do you flash the custom recovery after successfully unlock the bootloader ?

I couldn't even get into FASTBOOT to type in the necessary commands. It's just stuck there at HBOOT Checking SD Update...Unplugging and replugging the USB cable got me in with FASTBOOT USB, but then the FLASH RECOVERY IMG command prompt execution just got stuck at waiting for device. So no recovery whatsoever at this stage.

LordGMLP said:
I couldn't even get into FASTBOOT to type in the necessary commands. It's just stuck there at HBOOT Checking SD Update...
Click to expand...
Click to collapse
Pull USB Cable and it will work, then put it in again

Already tried that mate. The command prompt shows waiting for device and stuck there.

LordGMLP said:
Already tried that mate. The command prompt shows waiting for device and stuck there.
Click to expand...
Click to collapse
Try reinstall HTC Sync for the drivers perhaps!?
Your SDK Kit with fastboot and adb commands is working?
Reboot PC?

putti71 said:
Try reinstall HTC Sync for the drivers perhaps!?
Your SDK Kit with fastboot and adb commands is working?
Click to expand...
Click to collapse
Yes. I used those to unlock the bootloader. And if HTC Sync is the problem, I wouldn't be surprised. It doesn't detect the phone when it is plugged in . Even the installation was troublesome. I had to set to Windows XP compatibility to install it on Win8 CP 64bit

LordGMLP said:
Yes. I used those to unlock the bootloader.
Click to expand...
Click to collapse
So you do have "My Htc" under Android USB Devices when checking the Device Manager in your PC, maybe uninstall and reinstall HTC Sync will help ?

Uhm no. I don't have anything that's called My HTC or Android and the like in my device manager . Don't know why but I got through the bootloader unlocking process by following the HTCDev instructions

Then download the Htc Sync and install it as it will install the required driver. You can uninstall the htc sync but leave the driver.
Give it a try and see how it goes.

Uninstalled and reinstalled HTC Sync a dozen times, still no luck. I highly suspect the drivers are incompatible with Windows 8 x64 at the moment. Like I said, the installation requires WinXP compatibility mode, otherwise the installer gave me the 'administration privileges' error, even though it was 'run as administrator' already . HTC Sync itself didn't detect my phone at all when it was plugged in. Better wait for HTC Sync Manager then

I just updated the HTC sync from the link above and the installation went smoothly. The different is I'm on Windows 8 32 bit. I remember that Htc Sync is working fine for my other laptop which was on windows 8 x64 but unable to test it now as I reverted to windows 7.

Strange. The link you provided clearly said the latest version was 3.2.20. But when I pressed download, the exe file said 3.2.10? Perhaps they forgot to update their download server? Damn. I had high hope with the One X. But looks like I'll stick with the iPhone a bit longer, until HTC sorts things out.

[Q] galaxy nexus troubleshooting help please

hi, i got this sgn from a friend with a broken screen, and ive now replaced the screen and the phone turns on and boots up no problem. but when i plug it in to my puter, it says usb device not recognized, one ot the usb devices attached.... as well in settings the wifi on/off toggle starts greyed out, if i go into the wifi setup, i can push the toggle and it says turning on wifi, but then after about 20 seconds or so, it just flicks the toggle back to off. bluetooth if i press the toggle, it instantly flicks back to off, and wont turn/stay on. and the last thing i have noticed that is not right, is when i try to go into the camera, it just f/c's and says gallery has has stopped, yet if i go into the gallery, it comes up. but f/c's if i try to access the camera.. i am thinking its probably a hardware issue, just was wondering if anyone might be able to give me any extra insight or suggestions, thanks in advance.
edit: oh, and the phone charges through the usb port, which i find weird that the puter wont recognize it...

slickwidnick said:
hi, i got this sgn from a friend with a broken screen, and ive now replaced the screen and the phone turns on and boots up no problem. but when i plug it in to my puter, it says usb device not recognized, one ot the usb devices attached.... as well in settings the wifi on/off toggle starts greyed out, if i go into the wifi setup, i can push the toggle and it says turning on wifi, but then after about 20 seconds or so, it just flicks the toggle back to off. bluetooth if i press the toggle, it instantly flicks back to off, and wont turn/stay on. and the last thing i have noticed that is not right, is when i try to go into the camera, it just f/c's and says gallery has has stopped, yet if i go into the gallery, it comes up. but f/c's if i try to access the camera.. i am thinking its probably a hardware issue, just was wondering if anyone might be able to give me any extra insight or suggestions, thanks in advance.
edit: oh, and the phone charges through the usb port, which i find weird that the puter wont recognize it...
Click to expand...
Click to collapse
hey,
if you don't mind rooting and phone is not underwarranyty, try: wugfresh nexus toolkit
or cyanogemod.org
may help fix...... and both are automated very easy.

gnexususer said:
hey,
if you don't mind rooting and phone is not underwarranyty, try: wugfresh nexus toolkit
or cyanogemod.org
may help fix...... and both are automated very easy.
Click to expand...
Click to collapse
Yeah, see the problem is my computer won't recognize the phone to be able to perform any of the functions of the toolkit... So I don't know what options (if any) I have...

slickwidnick said:
Yeah, see the problem is my computer won't recognize the phone to be able to perform any of the functions of the toolkit... So I don't know what options (if any) I have...
Click to expand...
Click to collapse
try reboot to odin bootloader. long press volume down + power button. can u boot it up?

memaro_maro said:
try reboot to odin bootloader. long press volume down + power button. can u boot it up?
Click to expand...
Click to collapse
yeah, ive got a usb jig to boot it into odin download mode, but i think i tried it but the computer still didnt recognize it, ill try it again and let you nkow what happens.. also, i have another working sgn here, and i switched out the boards, cause the usb port is not on the mainboard, it is connected by a flex ribbon (thinking it may be a faulty usb port) but either one generates the same results..

You dont need Odin. Just use fastboot and flash the latest Factory image. There are plenty of guides on how to do that. Good luck! If you cant get it to work just let me know.
Sent from my Galaxy Nexus using XDA Premium HD app

slickwidnick said:
yeah, ive got a usb jig to boot it into odin download mode, but i think i tried it but the computer still didnt recognize it, ill try it again and let you nkow what happens.. also, i have another working sgn here, and i switched out the boards, cause the usb port is not on the mainboard, it is connected by a flex ribbon (thinking it may be a faulty usb port) but either one generates the same results..
Click to expand...
Click to collapse
correctly install/setup adb & fastboot first & try ~
http://forum.xda-developers.com/showthread.php?t=2588979
if still not recognize ur device use odin tool, from odin bootloader
odin ~
http://forum.xda-developers.com/galaxy-nexus/general/guide-restore-to-stock-unbrick-galaxy-t2065470

memaro_maro said:
correctly install/setup adb & fastboot first & try ~
http://forum.xda-developers.com/showthread.php?t=2588979
if still not recognize ur device use odin tool, from odin bootloader
odin ~
http://forum.xda-developers.com/galaxy-nexus/general/guide-restore-to-stock-unbrick-galaxy-t2065470
Click to expand...
Click to collapse
okay i tried your advice, but the computer still fails to recognize the phone, i installed the drivers, cause the computer picks up the other sgn that i have here, i just unplugged the one thats fine, and plugged in the one i am trying to fix ant it doesnt do anything,...

Go to System Settings -> Storage -> 3 dots -> USB connection, and set MTP ON (V)
and if that doesn't work, try another DATA cable
.

Ed V said:
Go to System Settings -> Storage -> 3 dots -> USB connection, and set MTP ON (V)
and if that doesn't work, try another DATA cable
.
Click to expand...
Click to collapse
tried setting mtp on, tried setting ptp on, tried setting debugging mode off and on, tried a different cable, still nothing..
something i did notice was that i have another sgn here and i went to the storage settings, and i was able to uncheck both mtp and ptp and my computer installed a new device "samsung something something" cant remember what the new device was tho..
oh and the bootloader is locked on the sgn im trying to fix and it is unlocked on the second sgn i have here...
could that have something to do with any of this?

[Q] E980 bricked - Computer says "unknown device" - Only boots into Recovery and DL

[Q] E980 bricked - Computer says "unknown device" - Only boots into Recovery and DL
My wife somehow managed to bork her Optimus G Pro. She was running rooted stock, and the phone ended up somehow booting to CWM. She said she "picked a few selections", and the phone won't get past CWM now.
I can't do the mobile flash tool because every time I connect the phone, it somes up as Unknown Device. This is after I updated the drivers on both computers. Tried various ports & USB cables, same thing. MY E980, by the way, shows up fine in Device Manager.
I've tried restoring a previous backup, but it still boots right back to recovery. For some reason, the phone doesn't recognize the external card, or I would have tried making a backup on the other phone with the bootloader included, but I have no way of getting it onto the broken phone, unless I can push it via adb somehow.
Anyway, I appreciate any help anyone can give

ixijimixi said:
My wife somehow managed to bork her Optimus G Pro. She was running rooted stock, and the phone ended up somehow booting to CWM. She said she "picked a few selections", and the phone won't get past CWM now.
I can't do the mobile flash tool because every time I connect the phone, it somes up as Unknown Device. This is after I updated the drivers on both computers. Tried various ports & USB cables, same thing. MY E980, by the way, shows up fine in Device Manager.
I've tried restoring a previous backup, but it still boots right back to recovery. For some reason, the phone doesn't recognize the external card, or I would have tried making a backup on the other phone with the bootloader included, but I have no way of getting it onto the broken phone, unless I can push it via adb somehow.
Anyway, I appreciate any help anyone can give
Click to expand...
Click to collapse
If the message you are referring to is one that pops up using a windows computer. I have seen it most of the times I have flashed back to stock. Unknown device, device can't be recognized, something not installed, etc. Carrying on with the restore method even so has also worked every time.
---------- Post added at 01:18 PM ---------- Previous post was at 01:13 PM ----------
Return to stock method: http://forum.xda-developers.com/showthread.php?t=2420219

abumy said:
If the message you are referring to is one that pops up using a windows computer. I have seen it most of the times I have flashed back to stock. Unknown device, device can't be recognized, something not installed, etc. Carrying on with the restore method even so has also worked every time.
---------- Post added at 01:18 PM ---------- Previous post was at 01:13 PM ----------
Return to stock method: http://forum.xda-developers.com/showthread.php?t=2420219
Click to expand...
Click to collapse
Yep, that's the message. I'm running Windows 7.
I'll give it a shot when I get home, but without the device showing up in the com port section of device manager, I can't change the phone over to port 41, right?

I have a TWRP backup from my other E980 that I included the Bootloader option in the backup. Is there any way to push that to the phone using ADB?

I don't know if OP has the same problem as mine. My phone just keep boot into CWM all the time. No matter which rom I flash.
And I Finally found a method to solve this problem, please look here:
http://forum.xda-developers.com/showpost.php?p=49370751&postcount=70
It salve my phone and I don't have to use the LG tools
@ixijimixi

laofan said:
I don't know if OP has the same problem as mine. My phone just keep boot into CWM all the time. No matter which rom I flash.
And I Finally found a method to solve this problem, please look here:
http://forum.xda-developers.com/showpost.php?p=49370751&postcount=70
It salve my phone and I don't have to use the LG tools
@ixijimixi
Click to expand...
Click to collapse
Reading that post, it sure seems like what I'm going through. I'll have to give it a shot tonight. Either way, thanks for the response. This thing has me pulling my hair out.

ixijimixi said:
Reading that post, it sure seems like what I'm going through. I'll have to give it a shot tonight. Either way, thanks for the response. This thing has me pulling my hair out.
Click to expand...
Click to collapse
before you boot into system, make sure you already have one system installed( I did once wipe system and fogot to install a rom..)
At least that post is working for me! Now I am using TWRP,

laofan said:
before you boot into system, make sure you already have one system installed( I did once wipe system and fogot to install a rom..)
At least that post is working for me! Now I am using TWRP,
Click to expand...
Click to collapse
No luck with that post. Followed every step on two different computers, but neither computer will recognize it (keep getting that "unknown device" error in windows).
I saw a post somewhere that someone had luck formatting their system drive in Recovery, but that seems a little bit drastic to me. I'll probably try uninstalling and reinstalling all the drivers again first. And more swearing. LOTS more swearing...

ixijimixi said:
No luck with that post. Followed every step on two different computers, but neither computer will recognize it (keep getting that "unknown device" error in windows).
I saw a post somewhere that someone had luck formatting their system drive in Recovery, but that seems a little bit drastic to me. I'll probably try uninstalling and reinstalling all the drivers again first. And more swearing. LOTS more swearing...
Click to expand...
Click to collapse
Did you install LG driver in those two computer?
That post has cover issues when device is not recognized. If that doesn't help, you need to go back to stock using files in the General section

I'm also having the same problem. Can I run those adb commands on a Ubuntu machine?

ixijimixi said:
No luck with that post. Followed every step on two different computers, but neither computer will recognize it (keep getting that "unknown device" error in windows).
I saw a post somewhere that someone had luck formatting their system drive in Recovery, but that seems a little bit drastic to me. I'll probably try uninstalling and reinstalling all the drivers again first. And more swearing. LOTS more swearing...
Click to expand...
Click to collapse
try this one, use the TWRP method. ( I got into recovery bootloop again today, my computer could not see my phone at all. And I accidently press continue on OTA... f**k, then phone run into recovery for 2 hours.)
This method help me out even when computer could not see your device.
http://forum.xda-developers.com/showthread.php?t=2451696

laofan said:
Did you install LG driver in those two computer?
That post has cover issues when device is not recognized. If that doesn't help, you need to go back to stock using files in the General section
Click to expand...
Click to collapse
Right, but if my computer isn't connecting to my phone (except to show it as an "Unknown Device"), and ADB isn't connecting, and none of the recoveries see the ext. SD card, how do I get the files across?

laofan said:
try this one, use the TWRP method. ( I got into recovery bootloop again today, my computer could not see my phone at all. And I accidently press continue on OTA... f**k, then phone run into recovery for 2 hours.)
This method help me out even when computer could not see your device.
http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
Holy crap...that idea with the TWRP terminal command got me up and booting! So glad that I kept TWRP on there!
For some reason, it's still not reading either the SD card or recognizing the device on USB, but at least this is progress, and at least I can run the thing.
*update* and now it seems to be reading the SD card. At least with that and wifi, I'll be able to move files to/from the phone. I'm going to try reinstallng drivers. With all the reinstalling, uninstalling, and swearing I've done lately, I think there's a good chance that'll work.

ixijimixi said:
Holy crap...that idea with the TWRP terminal command got me up and booting! So glad that I kept TWRP on there!
For some reason, it's still not reading either the SD card or recognizing the device on USB, but at least this is progress, and at least I can run the thing.
*update* and now it seems to be reading the SD card. At least with that and wifi, I'll be able to move files to/from the phone. I'm going to try reinstallng drivers. With all the reinstalling, uninstalling, and swearing I've done lately, I think there's a good chance that'll work.
Click to expand...
Click to collapse
well You should owe me 8 thanks hit for saving your phone..:fingers-crossed: LOL
I would also recommend reinstall drivers, then reboot computer( it is important), and try different USB ports on your PC. my computer just won't recongize my phone on one port, but it does on the other. God knows why...

laofan said:
well You should owe me 8 thanks hit for saving your phone..:fingers-crossed: LOL
I would also recommend reinstall drivers, then reboot computer( it is important), and try different USB ports on your PC. my computer just won't recongize my phone on one port, but it does on the other. God knows why...
Click to expand...
Click to collapse
Heheheh, yeah, I was going to, but then I read your previous sig. Perfectly happy to ignore.
My google-fu failed me major league on this mess. I'm just hoping it's not a busted USB port on the phone.

ixijimixi said:
Heheheh, yeah, I was going to, but then I read your previous sig. Perfectly happy to ignore.
My google-fu failed me major league on this mess. I'm just hoping it's not a busted USB port on the phone.
Click to expand...
Click to collapse
Try different USB ports on PC. When my PC could not see my phone, I also panic and thinking that the USB port on the phone goes wrong.
Then I switch the port which my mouse is usually hook up. Bang! Windows is installing driver and few seconds Iater I was accessing the files on the phone.
Just give it a try.
My signature is just for fun...Emm, I should change it to " hit thanks twice if you like my post "..

laofan said:
Try different USB ports on PC. When my PC could not see my phone, I also panic and thinking that the USB port on the phone goes wrong.
Then I switch the port which my mouse is usually hook up. Bang! Windows is installing driver and few seconds Iater I was accessing the files on the phone.
Just give it a try..
Click to expand...
Click to collapse
Well, I'm out of ports to try on my work computer. I'll try on my home computer later on. It didn't read it last night...but then again, the phone wasn't booting last night either
My signature is just for fun...Emm, I should change it to " hit thanks twice if you like my post "..
Click to expand...
Click to collapse
"Hit the thanks button like a rat pressing a lever for a nugget of food, thanks"

zenfone 2 usb problem? No bootloader, or xfstk, still boots to OS

Hey everyone hopefully someone has an idea what is wrong with this phone.
I cannot enter the bootloader it keeps blinking and eventually just goes to the official recovery.
Tried going into xfstk (which i have used before), cant connect get usb drive has malfunctioned on computer.
Inside the OS (6.0) when i plug it in to the computer i get cant connect get usb drive has malfunctioned on computer.
I tried replacing the usb board same thing.
Also quick charge doesnt work anymore (im guess all related).
Is it a mobo problem, or any other things i can try?

Have you tried ? , update from sd card --putting the firmware you are on or the next updated version ,on ext sd before booting into recovery and updating ,
i have tried this method recently , hope it works for you ?

sharkie545 said:
Hey everyone hopefully someone has an idea what is wrong with this phone.
I cannot enter the bootloader it keeps blinking and eventually just goes to the official recovery.
Tried going into xfstk (which i have used before), cant connect get usb drive has malfunctioned on computer.
Inside the OS (6.0) when i plug it in to the computer i get cant connect get usb drive has malfunctioned on computer.
I tried replacing the usb board same thing.
Also quick charge doesnt work anymore (im guess all related).
Is it a mobo problem, or any other things i can try?
Click to expand...
Click to collapse
here are few things you can try.
1. enable usb debugging and connect your phone to PC.
now assuming you already got adb and fastboot driver on pc..
run command adb reboot-bootloader
if this does not work. try other method.
2. download droidboot.img firmware image and place in in root of your phone
download turminal on phone. now run terminal emulator and run the following commands one by one. wait for little time after every command.
$ su
# dd if=/sdcard/droidboot.img of=/dev/block/mmcblk0p13
# reboot bootloader
third you can try updating firmwware via recovery as timbernot suggested. if it fails as well. then xfstk is needed.
there may be chance your fastboot partition is wasted. i have never tried to erase in via adb. i will try to erase it via adb and tell you if got success

timbernot said:
Have you tried ? , update from sd card --putting the firmware you are on or the next updated version ,on ext sd before booting into recovery and updating ,
i have tried this method recently , hope it works for you ?
Click to expand...
Click to collapse
I tried to apply update via recovery. Same problem.
sukhwant717 said:
here are few things you can try.
1. enable usb debugging and connect your phone to PC.
now assuming you already got adb and fastboot driver on pc..
run command adb reboot-bootloader
if this does not work. try other method.
2. download droidboot.img firmware image and place in in root of your phone
download turminal on phone. now run terminal emulator and run the following commands one by one. wait for little time after every command.
$ su
# dd if=/sdcard/droidboot.img of=/dev/block/mmcblk0p13
# reboot bootloader
third you can try updating firmwware via recovery as timbernot suggested. if it fails as well. then xfstk is needed.
there may be chance your fastboot partition is wasted. i have never tried to erase in via adb. i will try to erase it via adb and tell you if got success
Click to expand...
Click to collapse
I'm not rooted, so with su? Nothing happens.
Xfstk was my first choice, but when I plug my phone into computer I can never get the phone to connect (get USB drive has malfunctioned). I have used it successfully before.
I can't enable USB debugging either for some reason. Once it says developer options enabled. I cannot find developer options.

Tapping build number numerous times ?
Nothing ?
---------- Post added at 01:13 PM ---------- Previous post was at 12:56 PM ----------
sharkie545 said:
[/HIDE]
I tried to apply update via recovery. Same problem.
[/HIDE]
I'm not rooted, so with su? Nothing happens.
Xfstk was my first choice, but when I plug my phone into computer I can never get the phone to connect (get USB drive has malfunctioned). I have used it successfully before.
I can't enable USB debugging either for some reason. Once it says developer options enabled. I cannot find developer options.
Click to expand...
Click to collapse
re update from sd , firmware UL- blah blah , put another .zip on the end , so should read as user.zip.zip
Wipe data first cache too and try again

timbernot said:
Tapping build number numerous times ?
Nothing ?
---------- Post added at 01:13 PM ---------- Previous post was at 12:56 PM ----------
re update from sd , firmware UL- blah blah , put another .zip on the end , so should read as user.zip.zip
Wipe data first cache too and try again
Click to expand...
Click to collapse
Ill try reflashing again, as i said reflashing works but still same problems. - didnt wipe data though - so will give that a try.
USB developers showed this time oddly enough, but still get A request for the USB device descriptor failed. on computer when i plug it in. (two diff computers - drivers installed - different cords - windows 7 and 10)

sharkie545 said:
Ill but still get A request for the USB device descriptor failed. on computer when i plug it in)
Click to expand...
Click to collapse
You have to tick the box on screen of phone to allow it to make contact with the pc , maybe your phone screen timed out and you missed the pop up on phone? , set phone screen to time out for a couple of mins and attempt again
:good:
Ps the wipe data , can take a while

sharkie545 said:
Ill try reflashing again, as i said reflashing works but still same problems. - didnt wipe data though - so will give that a try.
USB developers showed this time oddly enough, but still get A request for the USB device descriptor failed. on computer when i plug it in. (two diff computers - drivers installed - different cords - windows 7 and 10)
Click to expand...
Click to collapse
well seems like you have broken partition. need to flash xfstk. as it is booting properly you will not get it detected as moorefield. but even though install soc driver. then run xfstk. load files and click begin download. now connect your phone to pc in switch off mode and turn on

timbernot said:
You have to tick the box on screen of phone to allow it to make contact with the pc , maybe your phone screen timed out and you missed the pop up on phone? , set phone screen to time out for a couple of mins and attempt again
:good:
Ps the wipe data , can take a while
Click to expand...
Click to collapse
Unfortunately, still same problem yea it does take a long time lol never understood why. - wiped, clean install same problem. No popsups on phone ever just goes device has malfunctioned on computer.
sukhwant717 said:
well seems like you have broken partition. need to flash xfstk. as it is booting properly you will not get it detected as moorefield. but even though install soc driver. then run xfstk. load files and click begin download. now connect your phone to pc in switch off mode and turn on
Click to expand...
Click to collapse
Unfortunately i have tried that a dozen times, i know its supposed to from a off phone when you turn it on theres a delay from your phone actually turning on till when you see the asus logo, this is when xfstk takes over - but even then i get device malfunctioned on computer - (begin download mode is on).

sharkie545 said:
[/HIDE]
Unfortunately, still same problem yea it does take a long time lol never understood why. - wiped, clean install same problem. No popsups on phone ever just goes device has malfunctioned on computer.
[/HIDE]
Unfortunately i have tried that a dozen times, i know its supposed to from a off phone when you turn it on theres a delay from your phone actually turning on till when you see the asus logo, this is when xfstk takes over - but even then i get device malfunctioned on computer - (begin download mode is on).
Click to expand...
Click to collapse
Can you confirm build /date info ?

timbernot said:
Can you confirm build /date info ?
Click to expand...
Click to collapse
Build Number: MMB29P.WW-ASUS_Z00A-4.21.40.184_0577_user
Kernel: 3.10.72-x86_64_moor-gcb00463

sharkie545 said:
Build Number: MMB29P.WW-ASUS_Z00A-4.21.40.184_0577_user
Kernel: 3.10.72-x86_64_moor-gcb00463
Click to expand...
Click to collapse
edit my mistake you are on 6.0 already
Out of ideas , cannot help but think its something simple , even tho developers options is ticked , is USB debugging ticked lower down ? Going back to home screen - swipe down and flick thru different options, camera- charge only- file transfer ?
Driver issue but doesnt explain it happening on other pc`s so seems more like ^^^
Then again if a USB hardware issue on phone, usb charge board -- i havent witnessed it so not able to comment.
If i come up with any ideas i will post - goodluck
I am going to try something on my own fone first before i let you know
I am going to attempt the official downgrade version of LP WW-52.20.40.196 from .144 M - via sd card and update from sd in recovery , with the view of updating/downgrading droidboot in the process- i have just managed the downgrade from .184 M to .144 via same method which is nice to learn
@sharkie545
Success -- Downgrade of MM to LP works with the downgrade firmware above works via update from sd in MM recovery ------- Marvelous
Stays on` updating IFWI ` for approx 8 mins but after that - bingo !
It also erases data after which it didnt updating in same OS
Also , i set it up -- after a reboot , detected .134 and ..144 and .184 MM update packages

timbernot said:
edit my mistake you are on 6.0 already
Out of ideas , cannot help but think its something simple , even tho developers options is ticked , is USB debugging ticked lower down ? Going back to home screen - swipe down and flick thru different options, camera- charge only- file transfer ?
Driver issue but doesnt explain it happening on other pc`s so seems more like ^^^
Then again if a USB hardware issue on phone, usb charge board -- i havent witnessed it so not able to comment.
If i come up with any ideas i will post - goodluck
I am going to try something on my own fone first before i let you know
I am going to attempt the official downgrade version of LP WW-52.20.40.196 from .144 M - via sd card and update from sd in recovery , with the view of updating/downgrading droidboot in the process- i have just managed the downgrade from .184 M to .144 via same method which is nice to learn
@sharkie545
Success -- Downgrade of MM to LP works with the downgrade firmware above works via update from sd in MM recovery ------- Marvelous
Stays on` updating IFWI ` for approx 8 mins but after that - bingo !
It also erases data after which it didnt updating in same OS
Also , i set it up -- after a reboot , detected .134 and ..144 and .184 MM update packages
Click to expand...
Click to collapse
Im going to try a few things first, i believe it has to do with the chip, or ribbon cable or IC chip. So im going to try to purchase a broken asus zenfone 2 (lcd problem) and swap some parts see if it fixes it. If it does well i know thats the problem. As i believe this is hardware related.

sharkie545 said:
[/HIDE]
Im going to try a few things first.
Click to expand...
Click to collapse
Wow just wow !!!!!!!!

timbernot said:
Wow just wow !!!!!!!!
Click to expand...
Click to collapse
Hehehe I appreciate the help. I have reformated many times lol. But since xfstk cannot be detected either (moorfield USB drive has malfunctioned) leads me to believe it has to be hardware related. Since moorfield is irrelevant of software/bootloader. It's kinda like the ultimate savour. Saved me out of some hetic problems before. (Leading me to wipe me imei #s lol which I had to than learn how to reprogram back lol)
Thank you again.

As the saying goes 'nothing ventured ......'
At least for all my hard work I found a way to downgrade from MM to LP with no PC , which obviously rewrites boot loader
Thank you
And you are two minutes away from finding out , should you decide to gamble like me
Although I have many phones to fall back on

emmc error? Suddenly black screen

Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!

slev!n said:
Hello guys,
Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.

knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/

knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
slev!n said:
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/
Click to expand...
Click to collapse
slev!n said:
Hello guys,
I've got an issue and don't know if it belongs to the build or not. I'm on the last build with my 3T and today after charging my phone I couldn't turn on WiFi or start any app. It just didn't open. So I restated my phone but it never booted. Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
Sounds to me like an hardware error involving (but not necessarily limited to) emmc access. That would explain, why the parts still in ram (like homescreen) were still working but apps won't start anymore, as well as the blank screen on device startup (even the logo needs emmc access to read the logo partition).
Try unbricking (I'm afraid your pc won't find the device, if my guess is correct), if that fails: rma or repair center.

slev!n said:
Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)

150208 said:
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)
Click to expand...
Click to collapse
Thanks, I'll create a post there. Just one more post here:
I used this phone just carefully at home as a media device. So this brick came totally out of nowhere. When I connect my bricked 3T now to my computer it makes the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more pop up again.

slev!n said:
I'll create a post there.
Click to expand...
Click to collapse
When you've created that post ask the moderators to move this complete conversation from this thread to the newly created on in the help forum, please. This helps to keep this thread readable and searcheble.
For your trouble: if you can't boot rom, recovery nor fastboot mode, it doesn't make sense to debug the usb connection: what should the pc connect to if none of the three is bootable? There is just nothing up to connect to. That's why I recommended unbrick tool - if that fails rma or go to a repair center.

Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!

Post SS of the device manager after connecting the phone to the PC

150208 said:
Post SS of the device manager after connecting the phone to the PC
Click to expand...
Click to collapse
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
@slev!n: please ask the moderators to move the existing conversation to thos from the los16 thread here. If all postings have moved, ask the moderators to move this thread from op3/help to op3t/help.

@nvertigo67 I wanted to do so and was searching how to contact moderators but couldn't find it in my XDA app. Maybe someone can give me a hint? I'm kind of new on xda... Thanks!
@150208 And as I wrote: it's not possible to get any kind of message on windows anymore. Just the sound appears when I connect and disconnect.
@nvertigo67 I was also following your advice to use the unbrick tool. I followed the steps on oneplus forum:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
When it comes to the integrity check windows doesn't accept "TESTSIGNING ON". And so windows doesn't recognise my phone in the device manager for the next steps.
And I guess RMA or repair centres are super expensive. I don't know if it's worth it? I thought about buying a device with a broken screen on eBay and try to change the motherboard...

Log in with a web browser locate each posting of the comversation. For each posting in question use the little triangle icon at the botom on the left side, report each posting, set non-urgent and pit the link of this thread together with something like "Please move this posting to the linked thread, thanx in advance".
For disabling driver signature enforcement try method 2. from this post: http://maxedtech.com/about-testmode/
Most of tbe time xda postings are more reliable and more current then the Oneplus forums: https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722, https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722

slev!n said:
[MENTION=4405529]i thought about buying a device with a broken screen on eBay and try to change the motherboard...
Click to expand...
Click to collapse
If you already have a thought why do you keep asked here though? If you want another possible solution, at least put an effort to provide the information needed when asked by the one who tried to help you
I'm not into a guessing games, so i'm out
nvertigo67 said:
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
Click to expand...
Click to collapse
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
If it's hw problem, i'll try not to jump on MB conclussion yet, since there are still another possible reason
When talking about MSM, you need to make sure it's available first on the device manager
Otherwise, it's a waste of data for downloading the tool in these human malware days
Oh yes, the msm guide is quite lag behind. You don't need to boot into test mode anymore with the current driver for qualcomm
I flashed a lot qualcomm devices with w10 without the need to boot into test mode

150208 said:
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
Click to expand...
Click to collapse
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
For the costs of rma: maybe it's expensive - maybe oneplus will be obliging... Since you don't relay on the device as your daily driver, you can ask for an estimate of costs - so you can decide if it's worth the costs.

nvertigo67 said:
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
Click to expand...
Click to collapse
Wait, I fail to see your explanation in line with mine. I want to start debug it on the windows side, but you seems to see it on the phone side.
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.

150208 said:
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.
Click to expand...
Click to collapse
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc. In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side. Once this is fixed (at least fastboot mode is up again) you can utilize the "normal" usb connection again.
What do you want to do with the usb connection, if neither fastboot mode nor recovery is up amd running? What is your suggested next step, if the device is recognized? What should the pc recognize if neither fastboot nor adb os an option? Which command or procedure will fix the emmc?

nvertigo67 said:
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc.
Click to expand...
Click to collapse
Yes, there are other tools but i'm not gonna bother since it's paid
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect. There are 4 status when a device plugged into the pc.
1. detected and driver is loaded
2. detected and driver isn't loaded
3. detected but not recognized
4. no sign at all
1 and 2 is sw problem, 3 and 4 is hw problem
In order for MSM to do it's job, you need to have either problem no 1 or 2 with qualcomm qloader 9008 driver already or later detected in devmanager
So it's important to know the driver status
OP states there was sounds coming then nothing, which mean it's either 2 or 3, more like 3 but again i repeating myself i don't like guessing games
I don't understand the part why you're explaining/asking about fastboot recovery or etc, his phone is on dead state, nothing-literally-no sign of life unless he plug it to the pc and then it making sounds for the first time,
Why do you even bother thinking about it?
nvertigo67 said:
Which command or procedure will fix the emmc?
Click to expand...
Click to collapse
No procedure will fixed his phone since there are no enough information
I think your other question should be already answered. If else, i don't know what to say anymore.

150208 said:
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect.
Click to expand...
Click to collapse
If so, please explain how you can format a partition or fix the partition table if neither fastboot mode nor recovery (or a rooted system for that matter) is bootable.
@slev!n: please give a screenshot of the device manager to @150208. I'm too curious to learn how to fix a broken emmc without recovery nor fastboot mode.

Thank you so far!
I dont want to bother someone. Just thinking about further options thats why I wrote my thought about replacing the motherboard down.
I 'm in test mode now and I did this:
"Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for a few seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB (under COMs and Ports)]."
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?

slev!n said:
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?
Click to expand...
Click to collapse
The pic is from msm tool, not the device manager. No unknown device in device manager?