So i was using RessurectionRemix (a version from last month) and recovery twrp 3.1.0-0 and the phone was working great!
Yesterday i left my phone charging over night and in the morning i wake up to my phone bootlooping!
So i tried different things including everything it says here https://forum.xda-developers.com/le-max-2/how-to/guide-hard-brick-fix-qualcomm-hs-usb-t3492949 without luck
I can get it into recovery and fastboot but as soon as i let the key combination go the phone stops and just shows a black screen (screen is on) and i cant get into qualcomm recovery to flash!
And the only way to shut off the phone is by holding power + vol up + vol down!
Any solution or suggestions?
Use flashone method to unbrick
md07 said:
Use flashone method to unbrick
Click to expand...
Click to collapse
As i already mentioned i cant get into qualcomm recovery so i cant use flashone
try to flash fastboot rom from cucoco's.
Tsoler said:
As i already mentioned i cant get into qualcomm recovery so i cant use flashone
Click to expand...
Click to collapse
connect phone to computer, try force shutdown phone by hard button, ater phone shutdown, immediately release power but keep both volume. Phone maybe will enter Qualcomm flash dead mode, and Flashone will regconize com phone (refresh nedded)
Hope you success ! And believe, if a phone can flash with Qfil or Flashone, almost that phone never die (software)
Are you able to connect to the phone via Vysor, either via Chrome browser or as a standalone app on Windows PC when you do not see anything on the phone screen? Please post if Vysor install goes thru successfully. Hope your developer options/USB debugging are on. I assume your phone boots but may have display issues either hw or sw.
md07 said:
connect phone to computer, try force shutdown phone by hard button, ater phone shutdown, immediately release power but keep both volume. Phone maybe will enter Qualcomm flash dead mode, and Flashone will regconize com phone (refresh nedded)
Hope you success ! And believe, if a phone can flash with Qfil or Flashone, almost that phone never die (software)
Click to expand...
Click to collapse
Did what you said but nothing happens
kayyappan said:
Are you able to connect to the phone via Vysor, either via Chrome browser or as a standalone app on Windows PC when the you do not see anything on the phone screen? Please post if Vysor install goes thru successfully. Hope your developer options/USB debugging are on. I assume your phone boots but may have display issues either hw or sw.
Click to expand...
Click to collapse
Phone gets recognized but not long enough to do anything (windows makes sound but doesn't install anything and doesn't show up in device manager)
try this guide
https://www.gizmochina.com/2016/11/20/leeco-x820-max-2-super-unbrick-guide/
You have mentioned that you are able to see the device in recovery and fastboot till you release the buttons - does this mean if the buttons are held say in fastboot mode you are able to see the device via "fastboot devices" or in recovery the twrp screen or nothing ever shows up at all? Are the buttons clicking properly? Check individually to make sure - particularly the power button. Does it vibrate at any point of time when you press and hold the power button? Are you able to see any backlight when you say the screen is on?
If there no backlight shine a torch or sunlight from the side of the screen to see anything at all on the screen.
Vysor reports apk not installed when it attempts to download from PC to phone but fails. With Vysor you will have two windows one showing status of phone - this is the main window. The other is the mirrored one - that of the phone when you click view on the main window. I forgot that the phone requires approval to install the apk. Please see the attached thumbnails. Keep touching the screen about 3 cms up from the bottom of the screen (not the phone) to see any change. Hope your touch works.
I know it is quite frustrating to try a number of things. I recently went thru the same on Galaxy S4 to make sure the phone but for the screen works OK prior to ordering the screen. Besides in my case developer options was disabled and touch also did not work. It took about a week of learning and trying to see something on Vysor. I never have used a Sam phone till that time this broken phone was handed over to me.
After a lot of trying i found out that when i keep pressed power + vol down or vol up while connected to pc and device is off it gets recognized as
qualcomm hs-usb qdloader 9008 long as i keep the keys pressed so i tried the flashone method but it just says could not connect
Are Qualcomm drivers loaded on your computer? I have not used flashone. I used QPST to see if phone is connected. I am not sure if they are same.
kayyappan said:
You have mentioned that you are able to see the device in recovery and fastboot till you release the buttons - does this mean if the buttons are held say in fastboot mode you are able to see the device via "fastboot devices" or in recovery the twrp screen or nothing ever shows up at all? Are the buttons clicking properly? Check individually to make sure - particularly the power button. Does it vibrate at any point of time when you press and hold the power button? Are you able to see any backlight when you say the screen is on?
If there no backlight shine a torch or sunlight from the side of the screen to see anything at all on the screen.
Vysor reports apk not installed when it attempts to download from PC to phone but fails. With Vysor you will have two windows one showing status of phone - this is the main window. The other is the mirrored one - that of the phone when you click view on the main window. I forgot that the phone requires approval to install the apk. Please see the attached thumbnails. Keep touching the screen about 3 cms up from the bottom of the screen (not the phone) to see any change. Hope your touch works.
I know it is quite frustrating to try a number of things. I recently went thru the same on Galaxy S4 to make sure the phone but for the screen works OK prior to ordering the screen. Besides in my case developer options was disabled and touch also did not work. It took about a week of learning and trying to see something on Vysor. I never have used a Sam phone till that time this broken phone was handed over to me.
Click to expand...
Click to collapse
It doesn't stay long enough in recovery or fastboot to do anything it shuts off after a few seconds even with the buttons pressed after that it just shows a black screen
Phone vibrates when i press power and shows leeco logo (not os logo) and after 1-2 seconds screen goes black and phone vibrates again and shows leeco logo again and just continues looping
if i try to press power + vol up normally it goes into recovery but as soon as recovery is loaded screen goes black (screen on just doesn't show anything) the same goes for fastboot if i press power + vol down it loads fastboot but after 1-2 seconds screen goes black
if i keep pressing keys the phone just stays longer in recovery/fastboot but only 4-5 seconds
I assume you have adb and fastboot. Since you say the screen remains on when booting to recovery open a command prompt at the directory where adb is and issue a command "adb devices" without quotes. Does it just exit without showing any device or throws up some error? Try this irrespective of the black screen.
Have you looked at and tried what is given by @HTC-TYTN2 at post #8? It is for Le Max 2 and you will find a link to Quallcomm drivers too. Do not bother that the link mentions X820 even your Max 2 is 821, 829, etc.
since it happened after charging, you might want to check your cable and battery. best is to get a cheap usb multimeter.
Gesendet von meinem LEX820 mit Tapatalk
I too thought it could be the battery based on that's the screen goes off. But he also mentioned that the screen remains on but nothing to be seen after a short while. Wanted to suggest slow speed charging probably via a laptop usb as I'm not sure if he used high speed charging resulting in battery issue.
Did you solve the problem?
My phone just died completely! No response at all anymore. I'm contacting the seller now to send the phone back.
Looks like it is a hardware defect! A pretty odd one but nothing i can do anymore. I send it back and post what the problem is as soon as get any information.
Thanks to everyone who tried to help!
Tsoler said:
My phone just died completely! No response at all anymore. I'm contacting the seller now to send the phone back.
Looks like it is a hardware defect! A pretty odd one but nothing i can do anymore. I send it back and post what the problem is as soon as get any information.
Thanks to everyone who tried to help!
Click to expand...
Click to collapse
Try this:
https://www.androidfilehost.com/?w=files&flid=136823
download file, unzip, open folder, connect phone to USB via fastboot ( phone off phone + hold volume -) . Click to the flash app in your PC. The app should find the phone. Confirm TWRP problem -NO and start flash.
Drivers must be installed.
Drivers here.
https://uloz.to/!A6B4AmEVx87S/adbdriverinstaller-exe
I can, pass the cuoco rom by qfil? Another type of flash, because I can not access recovery and twrp ?, only by fastboot
RaphaBraga23 said:
I can, pass the cuoco rom by qfil? Another type of flash, because I can not access recovery and twrp , only by fastboot
Click to expand...
Click to collapse
Try this via fastboot mode.:
https://www.androidfilehost.com/?w=files&flid=136823
download file, unzip, open folder, connect phone to USB via fastboot ( phone off phone + hold volume -) . Click to the flash app in your PC. The app should find the phone. Confirm TWRP problem -NO and start flash.
Drivers must be installed.
Drivers here.
https://uloz.to/!A6B4AmEVx87S/adbdriverinstaller-exe
Related
Well, after spending almost 11 hours trying to boot into recovery or download, I know for sure that there is something going on with my phone re: hardware locked. The date on my box is 7-16. It is an early Vibrant. But no matter what I do, I cannot get into download or recovery which means my ****ing phone is literally worthless.
I have tried all possible thousands of combination's of buttons, batteries, and cords while booting and nothing happens.
The Vibrant logo shows, then it shows the pink, annoying as hell T-mobile logo, than goes to the Galaxy S logo which loads for a little bit and then just leads me to a black screen. Eventually the 4 buttons on the front of the phone turn on and then nothing else happens. It will just sit like this forever.
I know all I need to do is get a working ROM loaded but it is literally impossible to do so.
Can anyone offer any suggestions? Or are anyone else having the same problem?
I guess the only way I can get a working phone is to get in touch with T-mobile and do a Warranty exchange. That's a damn shame too, because I will be without a working phone for a week.
What about using adb?
adb reboot recovery -or- adb reboot download ?
I had a hw locked vibrant, never tried the adb reboot download, recovery did work.. I added another line on my account last night for somone, who got a vibrant, theirs wasn't hw locked, so I traded 'em ;P
Agree with the above poster I have been stuck on the vibrant screen or dark screen and adb still worked to save me
when i try to use adb, it just tells me that it cant find the device. i'm not able to boot into android OS at all.... screen just hangs. so my computer is never getting a chance to see my phone hence why i cant use adb to reboot it into recovery or download.
I believe your device has to go into recovery mode then check with and devices and if you see a device I THINK it is and reboot download, I am 90% certain
Sent from my SGH-T959 using Tapatalk
have you installed the drivers? phone DOES NOT have to boot into android for adb to read it.
98classic said:
have you installed the drivers? phone DOES NOT have to boot into android for adb to read it.
Click to expand...
Click to collapse
i do believe i have the correct drivers installed. i was able to use adb to run lagfixes before i was having this problem. when i boot my phone, i get a sound from my computer saying that it recognizes a usb device. the two drives in the vibrant show up in My Computer but i cannot access them as windows says they are not accessable at the moment.
at what point will adb be able to recognize my phone when booting? no matter what i do when i try adb shell i get error: device not found
It could be the phone not bring in debugging mode, either because it's been turned off or the os isn't getting far enough to turn it on. I think I've been able to get adb to recognize my phone even while it was booting up (at the white vibrant screen). Maybe you can try adb then?
Same problem here. I probably just have to sell it fast on ebay or something. Hopefully some kind of fix starts by the end of the week. First phone in my smartphone life to brick from a simple Voodoo lag fix. Please XDA gods find a solution.
crazycaveman said:
It could be the phone not bring in debugging mode, either because it's been turned off or the os isn't getting far enough to turn it on. I think I've been able to get adb to recognize my phone even while it was booting up (at the white vibrant screen). Maybe you can try adb then?
Click to expand...
Click to collapse
nope, no go. adb will not recognize my device no matter what. and the device isnt loading the OS so i cannot turn debugging on. i guess this is a real "brick" then.
This sounds like a rant rather than a question. Just sayin'.
DKYang said:
This sounds like a rant rather than a question. Just sayin'.
Click to expand...
Click to collapse
fixed that. my bad.
Check my thread in the dev section... I can get ADB working when you are stuck at the vibrant screen... MIGHT... just might work in your situation...
My thread is probably fallen back a few pages now... its a [Guide] [Think Tank]
renocivik said:
Check my thread in the dev section... I can get ADB working when you are stuck at the vibrant screen... MIGHT... just might work in your situation...
My thread is probably fallen back a few pages now... its a [Guide] [Think Tank]
Click to expand...
Click to collapse
thanks for the suggestion. i found your thread and went through the steps in the OP... still no luck. no matter what i do, i cannot get passed the black screen the loads after the galaxy s logo. i also cannot get into download mode or recovery no matter what combination of button presses i use.
just do the following , i used to have the problem of going into the download mode and this is what realy worked to me :
1- turn off the phone.
2- plug in the USB cable.
3- wait until the battery green charging start.
4- press the vol + , vol - , the power botton together.
5- when the screen gose black release the power botton only.
you should now be in the downloading mode
core99 said:
just do the following , i used to have the problem of going into the download mode and this is what realy worked to me :
1- turn off the phone.
2- plug in the USB cable.
3- wait until the battery green charging start.
4- press the vol + , vol - , the power botton together.
5- when the screen gose black release the power botton only.
you should now be in the downloading mode
Click to expand...
Click to collapse
this isnt working either. :-(
I just fixed this on my phone. Your phone will go into download mode. Plug the phone in and wait for the battery symbol to fully load. Hold Vol + and _ and PWR until it goes black, then release the PWR button only. It will go into DL mode. Fire up Odin, and flash the "Froyo that does not brick" ROM. It will boot into the i9000 recovery mode and give you an error. Hold the Vol + and - and PWR again and release PWR when the phone goes black. It will go into DL mode again. Now with Odin, flash the factory firmware, making sure to click re-partition this time. After the phone reboots, it will fire right up into the factory ROM.
atoz350 said:
I just fixed this on my phone. Your phone will go into download mode. Plug the phone in and wait for the battery symbol to fully load. Hold Vol + and _ and PWR until it goes black, then release the PWR button only. It will go into DL mode. Fire up Odin, and flash the "Froyo that does not brick" ROM. It will boot into the i9000 recovery mode and give you an error. Hold the Vol + and - and PWR again and release PWR when the phone goes black. It will go into DL mode again. Now with Odin, flash the factory firmware, making sure to click re-partition this time. After the phone reboots, it will fire right up into the factory ROM.
Click to expand...
Click to collapse
this is exactly the method i want to try. but unfortunately i cannot get the phone into recovery or download mode. i have tried at least 100 times now with many different combination's of plugging the usb cord in and pressing the volume and power buttons.
two ideas: one, is it possible that i wiped recovery and download mode from my phone on accident? the reason why i ask is that i was super tired and flashing roms and kernels to my phone. i flashed back to my original stock rom and then i flashed the kernel. for some reason, i selected wipe date/cache in Rom Manager before flashing the kernel. i have no idea why i did this. seriously. totally noob move. so im assuming i have a kernel flashed but now there is no ROM installed for the phone to boot into.
two, if above is not the issue, than im going to assume that the phone is not recognizing any button presses while its off, so when i turn it on it just recognizes that the power was pressed and ignores the volume presses, thus not booting the phone into recovery or download.
edit: i should mention again that at no time does adb recognize my device. so i cannot use adb to reboot the phone into the mode i need.
just a comment for the OP - the vibrant isnt worthless, it is something that YOU did to get the phone into its current state. So dont blame the phone for something that it didnt do on its own.
/end rant
byt3b0mb said:
just a comment for the OP - the vibrant isnt worthless, it is something that YOU did to get the phone into its current state. So dont blame the phone for something that it didnt do on its own.
/end rant
Click to expand...
Click to collapse
I understand what you mean. I appreciate your criticism of my original post. Let me say that I wrote it while frustrated. But I know that isn't an excuse.
The device is fantastic. I know that I did this to it myself. It's unfortunate.
Anyways, I received a replacement phone. I will be more careful this time.
My samsung vibrant running 4.0.4 ICS zenwich 1.8.4 randomly shut off today, not even able to turn on, it was the Sleep of Death I have got before, so i pulled battery and reboot, still nothing.
The phone now boots, but their is no display
The phone will literally turn on, have the 4 buttons light up on the bottom, have the screen be responsive to touches, but the physical display is off
I can unlock my phone by swiping, hear the volume up sound, even dial calls by blind touching. It is the same idea as a PC that is plugged in, just so VGA cable to the monitor.
I have tried rebooting to recovery, download mode and tried to heimdall, but it never finds my device, i tried to sdk in and reboot to download mode via cmd prompt but no luck finding device too
I am all out of ideas and nothing is seems to be working
Any advice on resolving this issue would be appreciated
wafflebroski said:
My samsung vibrant running 4.0.4 ICS zenwich 1.8.4 randomly shut off today, not even able to turn on, it was the Sleep of Death I have got before, so i pulled battery and reboot, still nothing.
The phone now boots, but their is no display
The phone will literally turn on, have the 4 buttons light up on the bottom, have the screen be responsive to touches, but the physical display is off
I can unlock my phone by swiping, hear the volume up sound, even dial calls by blind touching. It is the same idea as a PC that is plugged in, just so VGA cable to the monitor.
I have tried rebooting to recovery, download mode and tried to heimdall, but it never finds my device, i tried to sdk in and reboot to download mode via cmd prompt but no luck finding device too
I am all out of ideas and nothing is seems to be working
Any advice on resolving this issue would be appreciated
Click to expand...
Click to collapse
Device Manager show anything is plugged in?
FaultException said:
Device Manager show anything is plugged in?
Click to expand...
Click to collapse
Yes, It shows up as the linusb winusb t-959 but neither heimdall or android sdk find the device.
wafflebroski said:
Yes, It shows up as the linusb winusb t-959 but neither heimdall or android sdk find the device.
Click to expand...
Click to collapse
So were you able to get into Download Mode at all? And if so was the display on then?
FaultException said:
So were you able to get into Download Mode at all? And if so was the display on then?
Click to expand...
Click to collapse
i think it did because it wasnt at a lock screen, and when i touched the soft buttons they would light up, but the phone wasnt in an OS.
the screen was still off though, I can't get anything to make it turn on
wafflebroski said:
i think it did because it wasnt at a lock screen, and when i touched the soft buttons they would light up, but the phone wasnt in an OS.
the screen was still off though, I can't get anything to make it turn on
Click to expand...
Click to collapse
What method did you use to get into Download Mode?
FaultException said:
What method did you use to get into Download Mode?
Click to expand...
Click to collapse
take battery out, hold vol + and - and power button, put battery in while usb connected
wafflebroski said:
take battery out, hold vol + and - and power button, put battery in while usb connected
Click to expand...
Click to collapse
You may've gotten into recovery, I can't really get into download mode like that. Try this:
Unplug USB & remove battery
Insert battery but do not power on.
Hold VOL-UP + VOL-DOWN
Insert USB and wait a few seconds, while still holding them
FaultException said:
You may've gotten into recovery, I can't really get into download mode like that. Try this:
Unplug USB & remove battery
Insert battery but do not power on.
Hold VOL-UP + VOL-DOWN
Insert USB and wait a few seconds, while still holding them
Click to expand...
Click to collapse
Ok that works, I'm defineatly in download mode, the device shows up in ODIN, but not heimdall. I am not familiar with ODIN, how would I go about flashing the ICS zen rom? I found a tutorial to flash back to stock ROM and wipe all data, but I would like to be able to just reflash the ICS rom
wafflebroski said:
Ok that works, I'm defineatly in download mode, the device shows up in ODIN, but not heimdall. I am not familiar with ODIN, how would I go about flashing the ICS zen rom? I found a tutorial to flash back to stock ROM and wipe all data, but I would like to be able to just reflash the ICS rom
Click to expand...
Click to collapse
Ok, so it shows the download mode on the screen of the phone?
If so, that's good news and means your screen is not shot.
Try to get Heimdall to work. Are you in windows? Then you'll need to uninstall the samsung drivers and do this (from CM update guide):
CM update guide said:
1. Run the included zadig.exe in the drivers folder of the Heimdall Suite.
2. From the menu, choose Options » List All Devices.
3. From the drop down, select Samsung USB Composite Device or Gadget Serial.
4. Click Install Driver.
NOTE: A prompt may appear warning that the installer is unable to verify the publisher of the driver. Ignore it and select "Install this driver anyway."
5. Heimdall can now be used safely on the Windows computer.
Click to expand...
Click to collapse
Once heimdall is running, try grabbing the boot.img out of the zen zip and do this:
Code:
heimdall flash --kernel boot.img
See if anything comes of that.
The screen never turned on.. it just went into download mode and i was able to see from ODIN that it was recognized. So i ODIN'd back to stock rom, i heard the phone reboot, but still no display.
Like before the phone's screen is 100% responsive, i can unlock the phone, hear the usb plugging in noise, just no display. It just blows my mind because the screen works but its not on.. I am very confused
wafflebroski said:
The screen never turned on.. it just went into download mode and i was able to see from ODIN that it was recognized. So i ODIN'd back to stock rom, i heard the phone reboot, but still no display.
Like before the phone's screen is 100% responsive, i can unlock the phone, hear the usb plugging in noise, just no display. It just blows my mind because the screen works but its not on.. I am very confused
Click to expand...
Click to collapse
That's not good. Your phone might be done for then. I once repartitioned with no partition files and still download mode worked on a fresh battery pull.
Maybe try leaving the battery out for a while and see if it fixes itself, since it seems to be an electronics problem, maybe something needs time to reset or something.
Sent from my SGH-T959 using xda premium
Yea I've had the battery out for over 30 mins and nothing. I even opened up my phone last night to check all the ribbon wires and connections, everything looked fine and i removed the motherboard & replugged everything in.. still no luck
it's a good thing my contract is up I think I am going to get the samsung galaxy s 3..
RIP vibrant best phone i ever had, I'm surprised it lasted this long with all the mods I had done to it haha
my xt890 lcd screen and digitizer were broken so i changed them and the phone was working fine for a week, i then wanted to update to kitkat through oem update; everytime i tried it would give me error . i then read that since i unlocked bootloader and rooted my phone and installed cwm recovery i couldnt do an oem update and i had to do a factory reset in order to update through oem, so i did just that ; after the phone finished factory reset and booted i proceeded with oem update while the phone was charging, everything was going fine the file was downloading, i went to the bathroom and came back the display was black, but touch screen was working fine...through more searching i read that this could be from the update, and i should do another reset... since i couldnt see anything even recovery menu. i downloaded moborobo so i can see my screen on pc and proceeded to factory reset ... now i cant even see through moborobo and im stuck. i think im stuck in recovery screen, but no way to be sure , hence i cant get usb debug.Please help.
I tried to Unroot my Galaxy Tab 10.1 LTE last night and think I may have bricked my tablet. I used the instructions here on the XDA forum which had a link to all the Stock ROM's in one place. I got the most recent one and the only one for USA but it said it was for the model 7510. I didn't think that would be a problem since the USB drivers I installed on my PC were also labeled as being for the 7510 and they worked.
This tablet is the SCH-I905. Now I can't get it to boot at all. Gets stuck in a boot loop. Shows the Samsung logo, then resets and does it again. I can't get it in recovery mode either. Goes to a black screen and hangs.
Using the normal process to get to Download mode doesn't work. Holding Power and Volume Up, then letting go of the Power button, then pressing Volume Down and then Up. That's one weird thing. I can get to the option screen that shows the Download and Recovery mode options. Normally I would hit the Volume Down button to select Download mode and on the screen it says to press Volume Up to continue or Volume Down to cancel. If I press Volume Up it goes to a black screen and hangs. If I press Volume Down I get the Odin Download screen that says Waiting on USB cable.
That screen doesn't look the same as what I normally see but I'm not sure what's different. I didn't memorize each line of text. I just know there's not as much text there as there usually is. My PC will not recognize the tablet no matter which USB port I try to use and the tablet doesn't recognize that the USB cable is plugged in. I had no problem with the USB connection before I flashed the 7510 stock ROM.
So, if I cannot get to recovery mode and I can't get Download mode to work so I can use Odin to flash a different rom then is this thing bricked or is there something else I can try? I am about to try using my laptop and its USB ports but I don't think that's going to make any difference.
BTW, I have since found the correct 'stock recovery rom' at droidbasement.com and downloaded it to my PC. I just need to get on the tablet somehow.
Many people have your problem. I have my Lte verizon bricked as yours. The problem is demaged bootloader, only nvflash can fix it but actually our bootloader is locked and we need a hex key called sbk. At least we have to wait that somebody hack our tab from the basement. For now we can only search and share result.
pickupcash said:
I tried to Unroot my Galaxy Tab 10.1 LTE last night and think I may have bricked my tablet. I used the instructions here on the XDA forum which had a link to all the Stock ROM's in one place. I got the most recent one and the only one for USA but it said it was for the model 7510. I didn't think that would be a problem since the USB drivers I installed on my PC were also labeled as being for the 7510 and they worked.
This tablet is the SCH-I905. Now I can't get it to boot at all. Gets stuck in a boot loop. Shows the Samsung logo, then resets and does it again. I can't get it in recovery mode either. Goes to a black screen and hangs.
Using the normal process to get to Download mode doesn't work. Holding Power and Volume Up, then letting go of the Power button, then pressing Volume Down and then Up. That's one weird thing. I can get to the option screen that shows the Download and Recovery mode options. Normally I would hit the Volume Down button to select Download mode and on the screen it says to press Volume Up to continue or Volume Down to cancel. If I press Volume Up it goes to a black screen and hangs. If I press Volume Down I get the Odin Download screen that says Waiting on USB cable.
That screen doesn't look the same as what I normally see but I'm not sure what's different. I didn't memorize each line of text. I just know there's not as much text there as there usually is. My PC will not recognize the tablet no matter which USB port I try to use and the tablet doesn't recognize that the USB cable is plugged in. I had no problem with the USB connection before I flashed the 7510 stock ROM.
So, if I cannot get to recovery mode and I can't get Download mode to work so I can use Odin to flash a different rom then is this thing bricked or is there something else I can try? I am about to try using my laptop and its USB ports but I don't think that's going to make any difference.
BTW, I have since found the correct 'stock recovery rom' at droidbasement.com and downloaded it to my PC. I just need to get on the tablet somehow.
Click to expand...
Click to collapse
Did you solved the issue?
Please share ..., i face the same problem now ...
regards,
erwien.
Did you solved the issue.
share me......i face the same problem now
.
.
.
.
.
.
.
.
.
.
.
.
help me plz
Recently my DNA has been getting laggy and restarting occasionally, and yesterday after sending a simple text message it decided to enter a reboot-loop that I think is probably fatal.
When I plug it in to any power, it turns on, shows the white/green HTC screen, and then immediately shuts down, and repeats the cycle. I have not been able to get it to turn off (while on power), and cannot turn it on (even into the loop) while off power. HOWEVER, I CAN use the vol - shortcut to get to the bootloader screen BUT I cannot select anything, as it immediately shuts down when I try to do something.
My DNA is running the latest stock software (OTA from Verizon, i think 4.4.2), and i have not modified it (S-ON, unrooted etc...).
Any and all help would be appreciated!
Bonus: on the 95% chance it is dead, should i go moto x/droid turbo or stick with a *gasp* iphone 5 for 2 months until gs6/htc m9?
androidnj7 said:
Recently my DNA has been getting laggy and restarting occasionally, and yesterday after sending a simple text message it decided to enter a reboot-loop that I think is probably fatal.
When I plug it in to any power, it turns on, shows the white/green HTC screen, and then immediately shuts down, and repeats the cycle. I have not been able to get it to turn off (while on power), and cannot turn it on (even into the loop) while off power. HOWEVER, I CAN use the vol - shortcut to get to the bootloader screen BUT I cannot select anything, as it immediately shuts down when I try to do something.
My DNA is running the latest stock software (OTA from Verizon, i think 4.4.2), and i have not modified it (S-ON, unrooted etc...).
Any and all help would be appreciated!
Bonus: on the 95% chance it is dead, should i go moto x/droid turbo or stick with a *gasp* iphone 5 for 2 months until gs6/htc m9?
Click to expand...
Click to collapse
At any point can you get it to answer
Fastboot devices
?
dottat said:
At any point can you get it to answer
Fastboot devices
?
Click to expand...
Click to collapse
I can not get it to receive any signals from me in the bootloader as it shuts down immediately. I tried connecting it to my computer for use with adb, but fastboot WAS enabled and developer tools were DISABLED (i think), plus it cannot keep a constant connection, so that wasn't working.
After doing some research I think I can save it IF I can get it to a stable state from the one it is currently in, and then using the bootloader screen to do a factory reset ( or use
"adb reboot recovery"), but like I said that is depenednet on getting it to stop the boot loop.
I also tried doing something called an RUU (I have limited knowledge of this, i sued the dottat one), but since it cannot establish a constant connection, it did not work.
Im open to any suggestions at this point! Thanks
I seem to have posted my reply in haste.
I have installed the "minimal adb and fastboot" tool that was suggested for basic fastboot use. Fastboot will not recognize it when I use "fastboot devices".
I did install the HTC drivers a while ago, but I suspect they may not work, could that be the issue? I am running win 8.1.
Thanks
androidnj7 said:
I seem to have posted my reply in haste.
I have installed the "minimal adb and fastboot" tool that was suggested for basic fastboot use. Fastboot will not recognize it when I use "fastboot devices".
I did install the HTC drivers a while ago, but I suspect they may not work, could that be the issue? I am running win 8.1.
Thanks
Click to expand...
Click to collapse
Possibly. What does the device show up as in device manager?
dottat said:
Possibly. What does the device show up as in device manager?
Click to expand...
Click to collapse
For the 5-10 seconds its "on" every cycle, it shows up as a CD Drive (not the HTC6435 etc etc that it usually does)
androidnj7 said:
For the 5-10 seconds its "on" every cycle, it shows up as a CD Drive (not the HTC6435 etc etc that it usually does)
Click to expand...
Click to collapse
Hold volume up and power until the screen flickers and immediately switch to volume down only. Get it right and you will land in boot loader. Need boot loader to show fastboot usb
dottat said:
Hold volume up and power until the screen flickers and immediately switch to volume down only. Get it right and you will land in boot loader. Need boot loader to show fastboot usb
Click to expand...
Click to collapse
Yes I have gotten into the bootloader before but as soon as it shows up (and i try to select using the vol +/-) it shuts down and restarts right away. Basically, I cant even get the bootloader in a stable state.
androidnj7 said:
Yes I have gotten into the bootloader before but as soon as it shows up (and i try to select using the vol +/-) it shuts down and restarts right away. Basically, I cant even get the bootloader in a stable state.
Click to expand...
Click to collapse
Fastboot usb is going to be your only option. If you aren't able to stay there it's hardware. Any chance a button is stuck?
dottat said:
Fastboot usb is going to be your only option. If you aren't able to stay there it's hardware. Any chance a button is stuck?
Click to expand...
Click to collapse
You are right unfortunately, I can absolutley not stay in the bootloader with any sort of stability. I read on another thread that opening it up and disconnecting the battery from the motherboard would help, so thats what I did. As soon as I sealed it back up, the reboot-loop started right up again. My guess is that the motherboard is fried, its either that or the battery is holding no charge whatsoever.
If the board is fried, im done right?
if its the battery, is there any way to manually charge not going through the board?
Thanks for all your help btw!
The phone has been in the drawer for quite a long time (5+ Years)
I come to try flash root to it and it wont boot into fastboot. all that happens is a black screen and nothing else.
ADB reports it as being there till it reboots ( 'adb reboot bootloader' ) , when the phone reboots its a black screen and if i plug in a usb lead then i get the standard windows was unable to recognise this device. ( Attached is a device manager Grab of it )
I have tried to use Flashtool64 (latest version) it reboots to the same black screen. The only way then to get it back to a usable phone is to unplug the lead and press the power button till it vibrates.
I have spent 10+ hours reading and reading everywhere and nothing that has been suggested has been succesful.
This is my last hope ( I realise its a 10 year old phone) and am hoping someone can help me sort this out.
Many Thanks in advance
You wrote nothing about the version of adb and drivers you are using.
ze7zez said:
You wrote nothing about the version of adb and drivers you are using.
Click to expand...
Click to collapse
I have tried the latest and older version from 2013. Same result
peanuthead71 said:
I have tried the latest and older version from 2013. Same result
Click to expand...
Click to collapse
Maybe try this:
https://www.rescuedigitalmedia.com/fix-unknown-usb-device-device-descriptor-request-failed-on-windows
ze7zez said:
You wrote nothing about the version of adb and drivers you are using.
Click to expand...
Click to collapse
I have tried the latest and older version from 2013. Same result
ze7zez said:
Maybe try this:
https://www.rescuedigitalmedia.com/fix-unknown-usb-device-device-descriptor-request-failed-on-windows
Click to expand...
Click to collapse
Tried that.i have spent a very long time on this. Starting to get to the point that the phone is poop. And needs to be binned
To confirm the functionality of the equipment.
Can you transfer files from/to phone in adb mode?
Yes, the device problem only happens when it reboots to bootloader for fastboot access. I think bootloader is corrupted . Can't flash new one without boitloader/fastboot access. Well that's my understanding
What about flashmode?
Flash mode:
1) Connect the USB cable to the computer (do not connect it to the phone yet)
2) Turn off the phone
3) When the phone turns off, plug the USB cable into the phone and hold the Volume Down button
4) The phone should boot into Flashmod mode!
Your Xperia Z Ultra should be in Flash Mode now and the device’s LED light should turn into Green
Fastboot mode:
1) Connect the USB cable to your computer (don't connect it to the phone yet)
2) Turn off the phone
3) When the phone turns off, plug the USB cable into the phone and hold the Volume Up button
4) The phone should boot into fastboot mod!
Your Xperia Z Ultra should be in Flash Mode now and the device’s LED light should turn into Blue
peanuthead71 said:
Yes, the device problem only happens when it reboots to bootloader for fastboot access. I think bootloader is corrupted . Can't flash new one without boitloader/fastboot access. Well that's my understanding
Click to expand...
Click to collapse
Same. Even EMMA doesn't work. Which was a suggestion. Or flash prog (used old and new) all seem to reboot to bootloader/fastboot which has same error as stated.
The usb vol down with plugging in usb / power on doesn't work either.
neither does the vol up + power / usb
ammended to clarify
when powering up/vol down i get a short vibration, then it boots normally. pressing vol up + power gets black screen.
usb + vol Down does nothing, usb + Vol up also does nothing
I am thinking that the phone is not booting into a software that 'tells the USB what it is. Th OS boots fine tho and it sees the phone and can xfer to and from the phone