Related
I had a Vibrant before and flashed it constantly. I soft bricked it several time and it was easy just to Odin back to stock and try again. Before I begin to flash Roms on this phone I would like to know how one would fix a bricked Nexus S. I searched "bricked Nexus S" and didn't come up with much.
Sent from my Nexus S using XDA App
Flash a stock img thru fastboot/adb. Just as painless as Odin was if not easier.
Sent from my Nexus S
Yeah I figured that much but I have never used ADB before. What are the commands to flash a stock img and where can I get a stock img? I already have ADB set up, serial # comes up when I enter - adb devices. I'm ready to root and flash but I want to be prepared for anything. I don't want to panic for ten minutes like I did the first time I bricked my Vibrant.
Sent from my Nexus S using XDA App
You should be able to snag a stock image from the development section. As far as what adb commands to use check out any of the root tutorials in development.
Sent from my Nexus S
bricking the phone is not easy... everything can be wiped and reinstalled with ease. Recovery is your friend.
leyvatron said:
bricking the phone is not easy... everything can be wiped and reinstalled with ease. Recovery is your friend.
Click to expand...
Click to collapse
That's why I love this phone. When I first rooted my wife's phone she was a nervous wreck about me ruining it. Now, she jokingly cheers when it boot loops or hangs on the google splash screen.
kenvan19 said:
That's why I love this phone. When I first rooted my wife's phone she was a nervous wreck about me ruining it. Now, she jokingly cheers when it boot loops or hangs on the google splash screen.
Click to expand...
Click to collapse
Coolest wife ever? haha
risegeek said:
Coolest wife ever? haha
Click to expand...
Click to collapse
hehe why'd'ya think I married her
Hi Everyone.
I have my Nexus S for a 3 days - it's brand new. Last night i turned it off. It was about 50% charged. Today i can't turn it on. Phone is dead. What's wrong? There is no any response, even during charging (black screen).
Phone wasn't rooted. It has Android 2.3.2 update.
What can I do?
Van_Dyke said:
Hi Everyone.
I have my Nexus S for a 3 days - it's brand new. Last night i turned it off. It was about 50% charged. Today i can't turn it on. Phone is dead. What's wrong? There is no any response, even during charging (black screen).
Phone wasn't rooted. It has Android 2.3.2 update.
What can I do?
Click to expand...
Click to collapse
not enough information is present. you can attempt to get into bootloader / recovery, plug USB to the computer. When plugged, does the computer make a plugged in noise? if it does.. try turning it on, try using adb on it, etc.
as a last resort: if its not rooted or modified in any way, you can go back to best buy and exchange it since you said you've only had it for 3 days
Van_Dyke said:
Hi Everyone.
I have my Nexus S for a 3 days - it's brand new. Last night i turned it off. It was about 50% charged. Today i can't turn it on. Phone is dead. What's wrong? There is no any response, even during charging (black screen).
Phone wasn't rooted. It has Android 2.3.2 update.
What can I do?
Click to expand...
Click to collapse
First thing to do is pull the battery, let it sit a minute or two, then put the battery back in and try to boot.
Also, try booting into recovery or fastboot. With power off, press and hold volume up button, then press/hold power on switch. You should enter fastboot mode. From fastboot menu, select boot to recovery. The phone will reboot and you'll get to a screen with an "!" and an android robot on it. At that point you press hold power, then press/hold volume up (make note that this is the reverse of what you did earlier).
Once in Recovery, try wiping cache from the menu.
Reboot.
If still no good, then repeat the process but pick factory reset/wipe from the menu in recovery. Note that this will wipe all personal data and apps off the phone but it won't touch your sdcard contents.
The case with pull battery - not working.
I can't enter fastmode using 2 keys combination.
Computer don't recognize the phone. It's brick...
Van_Dyke said:
The case with pull battery - not working.
I can't enter fastmode using 2 keys combination.
Computer don't recognize the phone. It's brick...
Click to expand...
Click to collapse
Last option is to try to trick it into Samsung's Download Mode (see the Odin thread in Development section), but if the keys aren't recognized you can't soft boot into it so you'll need a dongle with a resistor to get there.
Sounds like it's truly a brick at this point. You'll probably have to return it, but I'm concerned about returning a phone that has your personal data on it without being able to wipe it. Doesn't seem like much way around that at this point if you can't get fastboot or download.
get the 301k resistor JIG and then you can go into the download mode even without the 2 keys + usb plug
you can always make your own JIG if you have the materials at home or a nearby Radio shack
Thx for all Your advices
Problem was with the dead battery. The battery died during the night - i don't know why. I think the system waren't able to boot up ant start charging process.
My solution:
I took 9V battery, 2 wires and charged dead battery for a while from 9V battery. Then a put it into phone and plug in to wall charger. Charging process started
Now everything is ok
That's pretty scary that it wouldnt take a charge if run down completelty. But hey handy to know incase it happens to any of us,
If you get any repeat i would take it back to get a fresh battery of course (only right to do so).
here's hoping you never need to though
Van_Dyke said:
Thx for all Your advices
Problem was with the dead battery. The battery died during the night - i don't know why. I think the system waren't able to boot up ant start charging process.
My solution:
I took 9V battery, 2 wires and charged dead battery for a while from 9V battery. Then a put it into phone and plug in to wall charger. Charging process started
Now everything is ok
Click to expand...
Click to collapse
That is scary......
Sent from my Nexus S using XDA App
Bricked
Tried unlocking nexus s last night, now it appears bricked. Cannot connect to computer to reflash as it seems to have wiped the driver. Any ideas on how to bring it back from the dead? thanks
I have managed to see the phone with fastboot. I was hoping that fastboot update, would re-image the brick. Can anyone let me know the correct syntax. I am not able to copy an image onto the phone. Thanks again
Noob {MAC User}... Please be gentle
Greetings Everyone,
Okay, so I endeavoured to root my phone last night and was successful. I ran into trouble when the clockwork recovery and superuser permissions kept getting removed each time I reboot.
Now, I'm at the Google splash screen with no way to move forward. I'm a mac user and I don't really get the adb thing. Got adb to work with mac from a youtube video, but still not sure what commands to run.
What I've done so far:
- wiped cache
- wiped/factory data reset
- retraced my steps by using terminal to setup superuser permission from this post (http://forum.xda-developers.com/showthread.php?t=927838)
What I think:
- maybe in all of my clicks I removed the ROM, so the phone doesn't have a ROM to work with.
This maybe a really infantile conclusion, but I know there's a solution (had a rooted G1 that I flashed all the time and thought I bricked once but was able to get it back to stock).
Eagerly waiting for a reply... no cell phone if this can't be fixed.
Tamara
warrenb said:
Tried unlocking nexus s last night, now it appears bricked. Cannot connect to computer to reflash as it seems to have wiped the driver. Any ideas on how to bring it back from the dead? thanks
I have managed to see the phone with fastboot. I was hoping that fastboot update, would re-image the brick. Can anyone let me know the correct syntax. I am not able to copy an image onto the phone. Thanks again
Click to expand...
Click to collapse
It would be easier to help you if we knew exactly what you did that caused the problem. You said you tried to unlock it...you mean fastboot oem unlock or something else?
If you can get into fastboot, you're not totally lost, but the computer needs to see the phone to do it.
I'm working in a vacuum here on what your real problem is, but without further details, the things you can try are boot into recovery (from the fastboot mode select boot recovery)...if you're stock recovery, press/hold power, then volume up once you see the android "!". From there wipe cache and whatever else it will let you wipe. Try rebooting. IF that didn't work go back to recovery and try a factory reset of the phone (will delete all your apps and stuff on the phone, but not on the sdcard (pics and stuff).
If none of that works, you can still try getting Clockwork recovery on the phone via fastboot. Boot phone to fastboot and then on computer type the command "fastboot flash recovery <put file name of recovery version you're flashing here>"
Once in clockwork, you should have access to adb via the computer. On your computer go to the Development section here and download any of the various nandroid images posted there. Now you use clockwork mounts and storage menu to mount the sdcard. Then use adb to "adb push <insert path and filename of your nandroid image here> /sdcard"
Unmount the sdcard with the clockwork mounts and storage menu. Now go to the backup menu, select advanced restore and find the nandroid image and restore it.
With any luck, you should be able to boot into a fresh phone.
Hi, I recently started having issues with my Sensation. It would reboot and get stuck in the HTC logo boot loop. The phone has and unlocked bootloader, S-OFF, and Super-CID.
I was using the Elegancia rom, so I thought that was the issue. I was able to get the phone into Fastboot mode with Power+Vol Dn and then connect the USB cable to get to Fastboot USB mode. I downloaded The TMOUS RUU 1.50.531.1 from one of the links in a thread in this forum. I was able to succesfully get the stock rom flashed on the phone. However, I wanted the latest version, so I went and downloaded the ICS TMOUS 3.32.531.14 RUU. I followed the same steps as above, got the RUU to recognize the device and start the flash. It got stuck at 27% saying "Updating System". I left it there for 1 hour and it didn't move. I had to force close the RUU program on my laptop and had to do a battery pull on the phone. Now, the phone doesn't power up at all. I can't even get into HBOOT.
I've tried the following so far:
- Left the phone on wall charge without the battery for 6+ hours
- Charged the battery by blocking the middle 2 prongs
- Tried to "jump start" the phone by removing battery, plugging in charger, inserting battery, and waiting for light
- Tried to remove battery and re-insert and pressed Pwr+Vol Dn multiple times.
- Tried to use adb/fastboot but get device not found
- Laptop won't recognize the phone, dont even get the QHUSB_DLOAD message
Is there anything else left to try? Or am I completely bricked?
intel61 said:
Hi, I recently started having issues with my Sensation. It would reboot and get stuck in the HTC logo boot loop. The phone has and unlocked bootloader, S-OFF, and Super-CID.
I was using the Elegancia rom, so I thought that was the issue. I was able to get the phone into Fastboot mode with Power+Vol Dn and then connect the USB cable to get to Fastboot USB mode. I downloaded The TMOUS RUU 1.50.531.1 from one of the links in a thread in this forum. I was able to succesfully get the stock rom flashed on the phone. However, I wanted the latest version, so I went and downloaded the ICS TMOUS 3.32.531.14 RUU. I followed the same steps as above, got the RUU to recognize the device and start the flash. It got stuck at 27% saying "Updating System". I left it there for 1 hour and it didn't move. I had to force close the RUU program on my laptop and had to do a battery pull on the phone. Now, the phone doesn't power up at all. I can't even get into HBOOT.
I've tried the following so far:
- Left the phone on wall charge without the battery for 6+ hours
- Charged the battery by blocking the middle 2 prongs
- Tried to "jump start" the phone by removing battery, plugging in charger, inserting battery, and waiting for light
- Tried to remove battery and re-insert and pressed Pwr+Vol Dn multiple times.
- Tried to use adb/fastboot but get device not found
- Laptop won't recognize the phone, dont even get the QHUSB_DLOAD message
Is there anything else left to try? Or am I completely bricked?
Click to expand...
Click to collapse
It does not boot at all? What happens when you connect it to your PC? If it boots - what's shown on the display (And I don't mean getting to HBOOT. There is a black screen with warning signs which is reversible)?
astar26 said:
It does not boot at all? What happens when you connect it to your PC? If it boots - what's shown on the display (And I don't mean getting to HBOOT. There is a black screen with warning signs which is reversible)?
Click to expand...
Click to collapse
It doesn't boot at all. Even after connecting it to the PC. I don't get any vibrates either.
Do you know if there's a way for me to test to see if power is getting to the necessary places on the circuit board?
intel61 said:
It doesn't boot at all. Even after connecting it to the PC. I don't get any vibrates either.
Do you know if there's a way for me to test to see if power is getting to the necessary places on the circuit board?
Click to expand...
Click to collapse
It probably does. The problem is probably because of damaged firmware/radio on the phone, so it won't boot. Does the computer recognize anything when the phone is connected? Check in device manager (Could point to an error such a QHSUSB_DLOAD).
If not, it could still be fixed, but it will need to be JTAGed, which is best to be done by a professional repair service, as the equipment is expansive and it requires soldering to the motherboard.
astar26 said:
It probably does. The problem is probably because of damaged firmware/radio on the phone, so it won't boot. Does the computer recognize anything when the phone is connected? Check in device manager (Could point to an error such a QHSUSB_DLOAD).
If not, it could still be fixed, but it will need to be JTAGed, which is best to be done by a professional repair service, as the equipment is expansive and it requires soldering to the motherboard.
Click to expand...
Click to collapse
Yea, nothing in the device manager.
I could perform the JTAG myself if I had the pinout and circuit diagram. I think I should have all the parts necessary. I'll search around for a diagram to see if its available. If you know where to get this information, would you send me a PM or post it? If not, its probably not worth paying to get the phone JTAGed, I could go buy a Nexus 4 or something as a replacement.
intel61 said:
Yea, nothing in the device manager.
I could perform the JTAG myself if I had the pinout and circuit diagram. I think I should have all the parts necessary. I'll search around for a diagram to see if its available. If you know where to get this information, would you send me a PM or post it? If not, its probably not worth paying to get the phone JTAGed, I could go buy a Nexus 4 or something as a replacement.
Click to expand...
Click to collapse
Here is a guide: http://www.jtagbox.com/jtag-news/ri...ick-unlock-modelid-cid-imei-repair-supported/
Are you sure you have the equipment? It's not something easily found...
astar26 said:
Here is a guide:
Are you sure you have the equipment? It's not something easily found...
Click to expand...
Click to collapse
Sorry, I meant to say that I could probably assemble the box itself if I had some knowledge of what the parts list was. I definitely don't have access to the actual Riff box. I'll keep trying to see if the phone boots up as I got my hands on a new battery.
Hey guys. I'm kinda desperated so let's see if there is anything else I can do.
I was playing a game on my phone and it started rebooting alone.
At this point, I long pressed the power button, don't ask me why, but I did it. and bang. it is dead. No boot, no loading, nothing. It still vibrates when I try to turn it on.
I had 30% Battery left.
I have root and my phone for 3 months.
I had Nandroid backup.
Long press power button, volume up + power, volume down + power doesn't work.
When connected to PC, I get the QHSUSB_BULK device on.
Tried to ColorOS Method but:
I cannot install ColorOS drivers cause it doesn't detect them.
I tried Qualcomm drivers and they worked, so then I used the program Msm8974DownloadTool to install ColorOS.
It went okay, all finished and I got the green letters in the end.
Still doesn't boot up, nothing changed.
I cannot detect my phone via ADB. Tried with the drivers and without the drivers and with clean drivers.
What can I do? I always had such care for my phone in case of an emergency, but for some weird reason this happened. I wasn't even messing up with the phone, it just died cause I turned it off while booting up?
Okay so, for some reason, I managed to get my phone on fastboot.
I used this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
To reset my phone.
and the phone did all the new loadings and installs ETC....in the end?
My phone still doesn't boot.
Like wow?...
cyldman said:
Okay so, for some reason, I managed to get my phone on fastboot.
I used this guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
To reset my phone.
and the phone did all the new loadings and installs ETC....in the end?
My phone still doesn't boot.
Like wow?...
Click to expand...
Click to collapse
I'm sorry I can't help but one bad move was probably resetting back to stock because now you lost your root and adb access..
jukiewalsh said:
I'm sorry I can't help but one bad move was probably resetting back to stock because now you lost your root and adb access..
Click to expand...
Click to collapse
What do you mean I lost my adb access? I can still find my phone there and it's still working. (aparrently)
I tried to use the command "fastboot reboot" and while it turns off the device from windows, it still doesn't boot back up.
cyldman said:
What do you mean I lost my adb access? I can still find my phone there and its still working. (aparrently)
I tried to use the command "fastboot reboot" and while it turns off the device from windows, it still doesnt boot back up.
Click to expand...
Click to collapse
Disregard that then, when the phone is booted you have to manually give adb access but you're right when it's in recovery or other modes it's already there.
Does your screen power on at all? Do you think your LCD/digitizer could've somehow just died on you?
I highly doubt it, it happened when I shut off the phone when it was rebooting. I dont hear anything when I turn on the phone and i cant press anything or slide to unlock. nothing. so ....yeah. Weird stuff is that I did fastboot reboot and now i can't get to fastboot again. sigh.
Read this thread:
http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696
Somewhere within it is the solution to your QHSUSB_BULK problem.
Already did bro, and I fixed it, did you even read my full post? I managed to install colorOS, but it's still not booting up.
Hello guys! Last update! My phone was not even vibratting when i pressed power button. I put it to charge and finnaly I got a screen. its not what I wanted...but its a small step!
Its the Low battery charge icon! So...I've heard about this other issue about the phone not charging. Could this be it? I will be trying some techniques like https://forums.oneplus.net/threads/...een-opo-not-booting-due-over-discharge.88107/.
Hopefully it will help, but it may take some days.
Hi guys. So I have been going through xda and Google for hours and hours trying solutions, to no avail. I almost never post on forums for help because I can usually find the solution. Not this time. This is my last resort next to throwing my phone out a window or praying for death's sweet release.
The facts: I have a rooted Xperia Z3v. I tried to upgrade TWRP in order to follow some directions on upgrading to Nougat. I flashed TWRP from 2.8.X.X to 3.X.X.X. I rebooted and it never made it to the Sony logo. Now, if I plug the phone in to either a wall socket or PC it vibrates, endlessly at three second intervals, each time with red LED. If I try to enter flash mode, then its the same but with a brief green led after the red. I can enter fastboot (the only way to stop it vibrating while plugged in) and my PC sees it, including Flashtool, but since my bootloader is locked permanently, I can't really do much with it.
When plugged into the wall-charger, I noticed that the charger's LED changes from "Active" to "Inactive" with every vibration. I'm pretty sure I'm in a reboot loop. The screen is totally dead and there's no logo, but every three seconds it kills it self and comes back.
I have tried everything I could think of.
What I have:
I have the stock firmware ready to go
I have TWRP backups on SD card and PC
I have Flashtool
I think my drivers are good, but not 100% sure
I can fastboot
I'm at my wit's end and losing hope.
Please, I'm open to any suggestions at all.
There is a chance to save your phone 50% this trick might work for your phone sort of .
First i need some answers
1.If you go to flash mode the phone vibrates right is it detectable by your pc at that time.
2.did you Try hard reset not by the vol button press but the very sophisticated button under the sim tray.
3.https://forum.xda-developers.com/z3/development/nougat-7-1-1-android-source-project-t3532346
try this I know this is not for your phone but you will be able to actually boot your phone or atleast take a rest for what the heck is going on with your phone
4.If none of the solutions work disscuss with me i am happy to help
Same thing here. Flashed wrong ROM via TWRP.
As a result, immediate loop (repetitive vibration, led blinking red) when connected via USB. No recovery access. Only fastboot access (blue led).
Locked bootloader.
Flashtool:
- tried flashing kernel.sin extracted from a stock ftf - no good (locked bootloader, unlocking requires flashboot which is not accessible).
- tried flashing system.sin extracted from a stock ftf - no good, flashtool says
INFO - Flashing selected system
and immediately after that
INFO - Please check the log before rebooting into system
So it clearly doesn't do anything. Any other approaches to try?
Tech core said:
First i need some answers
1.If you go to flash mode the phone vibrates right is it detectable by your pc at that time.
Click to expand...
Click to collapse
Flashmode does not work, it starts cycling immediately.
Tech core said:
2.did you Try hard reset not by the vol button press but the very sophisticated button under the sim tray.
Click to expand...
Click to collapse
Yes, certainly.
Tech core said:
3.https://forum.xda-developers.com/z3/development/nougat-7-1-1-android-source-project-t3532346
try this I know this is not for your phone but you will be able to actually boot your phone or at least take a rest for what the heck is going on with your phone
Click to expand...
Click to collapse
Can't flash anything, so can't try it.
Tech core said:
There is a chance to save your phone 50% this trick might work for your phone sort of .
First i need some answers
1.If you go to flash mode the phone vibrates right is it detectable by your pc at that time.
2.did you Try hard reset not by the vol button press but the very sophisticated button under the sim tray.
3.https://forum.xda-developers.com/z3/development/nougat-7-1-1-android-source-project-t3532346
try this I know this is not for your phone but you will be able to actually boot your phone or atleast take a rest for what the heck is going on with your phone
4.If none of the solutions work disscuss with me i am happy to help
Click to expand...
Click to collapse
I bought an M4 Aqua to keep me going for now as they're cheap. The E2306 is unrootable with 6.0.1 and I don't want to downgrade to Loli so no possibility to butt**** this one. If s300pmu1 and you figure it out, I'll do the same to mine.
TheControlled said:
I bought an M4 Aqua to keep me going for now as they're cheap. The E2306 is unrootable with 6.0.1 and I don't want to downgrade to Loli so no possibility to butt**** this one. If s300pmu1 and you figure it out, I'll do the same to mine.
Click to expand...
Click to collapse
I didnt get your comment brief it to me
Hello guys,
so two days ago just when I was heading into work my phone randomly started restarting itself again and again. I had it in my pocket, mobile data and wifi off and nothing really going on when this happened. I was on stock Cyanogen OS with 6.0.1, rooted and with Xposed, but nothing too crazy or experimental.
The phone would boot with a small vibration to the Oneplus logo with the "Powered by Android" writing, stay on that for about 17-18 seconds, then reboot again. No way of going to the recovery with the hardware keys, it would just reboot the same again and again. Since I couldn't really do much, not turn it off and no way of disconnecting the battery, I just had to watch it reboot helplessly until the battery was dead. At home with some hassle I could get it charged again, which basically consisted of charging it while it kept rebooting and cooling it while doing that since it would get really, really hot.
The only option that really works is is getting it into fastboot via the volume up + power button. But in fastboot nothing I did so far changed even the smalles thing about it's behaviour. I tried flashing a new recovery image, letting it boot into the recovery via fastboot (both stock recovery and TWRP), reflashing the complete OS via fastboot again (CM 13 ZNH2KAS3P0), completely wiping it via fastboot and flashing an older ROM (CM11S XNPH44S) but so far nothing has even changed a thing. It keeps booting to the Oneplus logo for about 17-18 seconds before rebooting. The only thing that has changed is with the CM11S ROM the fastboot logo of the android head is now bigger.
I checked the bootloader via fastboot, but it's still unlocked.
So yeah, I'm at my wits end and desperate for any help. At this point I fear it might be a hardware issue and I can trash it, but I'm ready to grasp for straws as I don't really have the money for a new device yet.
Any help is appreciated! Thanks guys!
Atomschlumpf said:
Hello guys,
so two days ago just when I was heading into work my phone randomly started restarting itself again and again. I had it in my pocket, mobile data and wifi off and nothing really going on when this happened. I was on stock Cyanogen OS with 6.0.1, rooted and with Xposed, but nothing too crazy or experimental.
The phone would boot with a small vibration to the Oneplus logo with the "Powered by Android" writing, stay on that for about 17-18 seconds, then reboot again. No way of going to the recovery with the hardware keys, it would just reboot the same again and again. Since I couldn't really do much, not turn it off and no way of disconnecting the battery, I just had to watch it reboot helplessly until the battery was dead. At home with some hassle I could get it charged again, which basically consisted of charging it while it kept rebooting and cooling it while doing that since it would get really, really hot.
The only option that really works is is getting it into fastboot via the volume up + power button. But in fastboot nothing I did so far changed even the smalles thing about it's behaviour. I tried flashing a new recovery image, letting it boot into the recovery via fastboot (both stock recovery and TWRP), reflashing the complete OS via fastboot again (CM 13 ZNH2KAS3P0), completely wiping it via fastboot and flashing an older ROM (CM11S XNPH44S) but so far nothing has even changed a thing. It keeps booting to the Oneplus logo for about 17-18 seconds before rebooting. The only thing that has changed is with the CM11S ROM the fastboot logo of the android head is now bigger.
I checked the bootloader via fastboot, but it's still unlocked.
So yeah, I'm at my wits end and desperate for any help. At this point I fear it might be a hardware issue and I can trash it, but I'm ready to grasp for straws as I don't really have the money for a new device yet.
Any help is appreciated! Thanks guys!
Click to expand...
Click to collapse
how old is the device?
As far as I know my sister bought it around summer 2014 when it was released, I got it in late 2015
Atomschlumpf said:
As far as I know my sister bought it around summer 2014 when it was released, I got it in late 2015
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
AFAIK,If this toolkit can't fix your device then it's definitely hw issue.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
AFAIK,If this toolkit can't fix your device then it's definitely hw issue.
Click to expand...
Click to collapse
Well, the tool won't even recognize my phone, so I guess I'm **** out of luck ¯\_(ツ)_/¯
****ing great....
Atomschlumpf said:
Well, the tool won't even recognize my phone, so I guess I'm **** out of luck ¯\_(ツ)_/¯
****ing great....
Click to expand...
Click to collapse
Lol,gave up that early?
It needs around 10 tries to get it correctly recognised.
Use XP system with the proper drivers given in the above thread.This tool doesn't work on adb/fastboot,it works on Usb Debugging Port,hence requires different drivers.
Mr.Ak said:
Lol,gave up that early?
It needs around 10 tries to get it correctly recognised.
Use XP system with the proper drivers given in the above thread.This tool doesn't work on adb/fastboot,it works on Usb Debugging Port,hence requires different drivers.
Click to expand...
Click to collapse
No, I didn't. I tried the USB Drivers I had already installed, the drivers that came in the package and the QPST Tool suggested in the thread on both my and my girlfriends laptop. But if it doesn't work on ADB/fastboot I probably can't use it anyway since my only two options are having the phone on the fastboot screen or having it constantly reboot....
At this point I'm just really, really frustrated and have sorta accepted it's very likely a hardware issue
I'm with the same problem. In my case, the tool does recognize and shows green after the end but when i try to boot, it only shows the boot logo.
I can enter in fastboot and trying the command "fastboot continue" the brightness goes up, but nothing else
already tried various tools, back to stock, qualcomm , and none worked, so can i throw it out of the window?
Edit: can't enter in recovery, and unlike the op, my phone doesn't reboot (at least i didn't notice it)