Ok ladies and gents,
I've been on a mission to root my Note 5 N920I for months now.
My problem is no computer will read/recognise the device. The Mac's seem to not even recognise it's plugged in, with Windows, no matter which driver I install it keeps telling me the "device descriptor failed blah blah blah". I managed to root my S4 very easily on Mac with Jodin3 so I know that it ain't no user error.
I've Googled and Googled ways to root without a computer or installing a custom recovery without root, but from what I understand I can't flash TWRP as recovery without a computer and therefore cannot root without a custom recovery.
I've Googled ways to fix the USB issue by making the xml file and putting it into the correct folder, but for that I need to be rooted. Right?
When she's plugged into a computer with USB debugging on or off nothing comes up in my notifications except for charging. I tried using the toolbox which I found on here (sorry can't remember the name) though it seemed like I was getting close, I couldn't get close enough before my temper got the better off me.
If my memory serves me correctly the OTG function worked when i first got the phone but didn't after the first update. My mate's Note 5 also has the same issue. I Googled it and seemed it was common issue on these phones.
I've tried to learn some Terminal/Command Prompt to see if I can fix it that way through Debian or whatever, only got as far as understanding it, kind of. Big ups to all you coders/programmers out there it really is an artform.
So PLZ PLZ can y'all help me, there has to be a way aside from setting this thing alight and getting a new phone.
My next mission, which I only embarked on a couple nights ago is unbricking my dad's Note 4 (N910G) that just hit the **** one day after spazzing out for a few days then would not turn on. I'm getting close though I haven't put much effort into that yet.
Any advice will be greatly appreciated, thanks in advance. ?
Forgive me if I've posted this thread in the wrong area
Related
Long story short, I've been about to flash a couple custom ROMs, but I understand that the safest way to do so is to first flash back to the stock ROM using Odin. That's where I hit a dead end.
Now, I've rooted my Captivate, but done practically nothing else.
When I plug my phone into my computer (both my desktop and my laptop- W7 Ultimate x64 and Professional x86 respectively), I get a rather long message about how the device has malfunctioned and basically cannot be worked with (poor wording, apologies).
I have installed the proper (x64/x86 on their respective OS's) samsung drivers, and I have tried connecting my phone from within the booted Android interface, as well as download mode (which I have little to no problem getting into).
I have also tried checking the 'debug mode' box within the phone's settings.
I'll concede that I'm no pro when it comes to this level of phone-play. I've built many a computer, and solved many a software problem, but this has me stumped.
I've thought about doing a master reset of some sort, but don't know if that would solve it.
I'd appreciate any and all advice, so thank you in advance.
[Oh, and I sincerely apologize if this was posted in the wrong section. It is, quite honestly, the first thread I've started.]
Try plugging it into another usb port. I have seen windows continue to say a device is not working even after installing the drivers if you had already plugged it in.
I am at a complete loss for words.
I'll at least make it clear right now that I think my problem is solved.
I had been plugging the phone into one of the usb ports located on the actual chassis, and took your advice and instead plugged it straight into my mother board (the back).
B
I
N
G
O
Windows auto-detected it and installed two sets of packages (drivers, I assume).
I feel like a fool, but in an odd, good sort of way.
Thank you, brother.
Not a problem glad I could help.
Absolutely! Me too, bro!
Thanks again.
I have 64bit drivers installed, and my phone is in download mode after a disasterous attempt at flashing for the first time. The phone, when not in Download mode, flashes the AT&T logo unplugged, and an empty battery logo with a spinner in the middle.
I've read endlessly on how to proceed with the reflashing steps, but it requires that I move files to the root folder, and it requires that I enable USB Debugging. I can't enable debugging and I can't seem to get my computer to recognize the phone as a disc drive.
I don't know what to do here, but I'm desperate to get my phone back up and running. I know I screwed up, and I don't need to be reminded of things I should have done. I only want constructive advice that will allow me to use my phone again.
Thank you so much in advance for anything that might get me operational.
STOP POSTING SO MANY THREADS ABOUT THE SAME THING!!!!!
wtf
cant you keep your **** organized into one thread!?
Or just shout out things like that.
I'm resolving the topical issue in each thread and announcing it. I thought these were topical threads and that how I worked it out. But hey, thanks. I'll be sure to keep my **** together in the future.
topical..
but when you have a ton of problems that all relate to your DRIVER situation....then, um dont you think it would be best to solve your DRIVER situation? you know, that thing that would solve most of your issues??
everything you have posted about has been about your computer seeing your phone....that would be driver related. once you fix that, your computer will see your phone. its not complicated and doesnt require a different thread started for every step of your driver problem/resolution
Great, so let's keep it on this thread from now on, and stop arguing, shall we? I'm just trying to be progressive. There. I fixed the damned thing anyhow.
[Q] Yet another "I'm stuck at the AT&T screen and I it's not recognized" thread
Greetings, all
I've been trying to figure this out, off and on, for 2-3 weeks. I could use some help.
Originally, I was running Cognition, but I can't even remember what I was trying to flash because I've tried so many things... The bottom line is that I'm at the download screen, but all the PC's I have (win 7) don't recognize it. I'm convinced that if I can get the PC to recognize it, then I could reload i897uckk4. But...
Things I have done:
- Rebooted, switched cables, turned everything off and on, tried on different machines, all the hardware easy stuff.
- Uninstalled drivers, tried other drivers, uninstalled Odin, Heimdall, Kies, rebooted and tried only one at a time.
- Tried all the USB ports on all the PCs
- Different phones are seen from the 2 cables I've been using.
This phone worked and was recognized on this machine before I screwed it up. I don't see how it's a phone hardware issue. Sure, it could be, but I really don't think so. That leaves drivers for Win 7, 64-bit. I've tried these files as Administrator:
- usb_drivers_GalaxyS_x64
- Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
I've even tried these for kicks:
-SAMSUNG_USB_Driver_for_Mobile_Phones_x86
- SGH-i897_Captivate_USB_Drivers_5_02_0_2
Now that I've tried all I can find, I think the ones I want to keep are the "usb_drivers_GalaxyS_x64"
Thing is, it worked before "The Big Hose of 2014". It should have been recognized, but it stopped being recognized after an unsuccessful attempt at flashing back to stock, after an unsuccessful attempt at Cyanogen. The only thing I can think of is that I tried to flash the wrong ROM version, or something like that, and the phone is in a state where it's not sending the proper handshake.
The error I'm getting is classic, and all over these forums:
- I've tried to manually load "Samsung Android USB Composite Device" driver - Device can not start. Code 10
- All devices like WMC, Mobile Modem, ect - Code 10
- A few others result in the Code 10, too.
I've tried to find the GUID for it in the Registry to delete the Upper and Lower Filters.
What's left? I'm sure it's a small thing. I could use a few more hints.
Two last questions:
Will doing the unbrickable mod help, or is it too late?
Does it charge while in download mode, or if the star like circle is not spinning?
FEF said:
Greetings, all
I've been trying to figure this out, off and on, for 2-3 weeks. I could use some help.
Originally, I was running Cognition, but I can't even remember what I was trying to flash because I've tried so many things... The bottom line is that I'm at the download screen, but all the PC's I have (win 7) don't recognize it. I'm convinced that if I can get the PC to recognize it, then I could reload i897uckk4. But...
Things I have done:
- Rebooted, switched cables, turned everything off and on, tried on different machines, all the hardware easy stuff.
- Uninstalled drivers, tried other drivers, uninstalled Odin, Heimdall, Kies, rebooted and tried only one at a time.
- Tried all the USB ports on all the PCs
- Different phones are seen from the 2 cables I've been using.
This phone worked and was recognized on this machine before I screwed it up. I don't see how it's a phone hardware issue. Sure, it could be, but I really don't think so. That leaves drivers for Win 7, 64-bit. I've tried these files as Administrator:
- usb_drivers_GalaxyS_x64
- Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
I've even tried these for kicks:
-SAMSUNG_USB_Driver_for_Mobile_Phones_x86
- SGH-i897_Captivate_USB_Drivers_5_02_0_2
Now that I've tried all I can find, I think the ones I want to keep are the "usb_drivers_GalaxyS_x64"
Thing is, it worked before "The Big Hose of 2014". It should have been recognized, but it stopped being recognized after an unsuccessful attempt at flashing back to stock, after an unsuccessful attempt at Cyanogen. The only thing I can think of is that I tried to flash the wrong ROM version, or something like that, and the phone is in a state where it's not sending the proper handshake.
The error I'm getting is classic, and all over these forums:
- I've tried to manually load "Samsung Android USB Composite Device" driver - Device can not start. Code 10
- All devices like WMC, Mobile Modem, ect - Code 10
- A few others result in the Code 10, too.
I've tried to find the GUID for it in the Registry to delete the Upper and Lower Filters.
What's left? I'm sure it's a small thing. I could use a few more hints.
Two last questions:
Will doing the unbrickable mod help, or is it too late?
Does it charge while in download mode, or if the star like circle is not spinning?
Click to expand...
Click to collapse
You probably already saw this thread, but in case: Captivate - PC Connection Issues, Download Mode and Recovery Mode Help
As for what is left, trying on another pc could be a good idea. If the drivers aren't already installed on it, even plugged in download mode, it should install drivers.
BWolf56 said:
You probably already saw this thread, but in case: Captivate - PC Connection Issues, Download Mode and Recovery Mode Help
As for what is left, trying on another pc could be a good idea. If the drivers aren't already installed on it, even plugged in download mode, it should install drivers.
Click to expand...
Click to collapse
I've already tried the stuff in the link. I did that first.
I have 7 computers, all running Win 7. This Captivate is not recognized my any of them.
Looks like I'm headed to the unbrickable mod. I'll have to dual boot to Linux for these fixes.
http://forum.xda-developers.com/showthread.php?t=1242466
If worse comes to worse, looks like I have a soldering iron and guitar pick in my future.
https://www.youtube.com/watch?v=frn9o03DHsE
http://www.xda-developers.com/android/the-unbrickable-mod-and-beyond/
Looks like I bricked it good. It's time to work on the hardware, I guess. It would be fun, if I hadn't already screwed up my phone. I bought another Captivate off eBay for $50, so at least I'll have a phone.
This story has a twist for an ending. I thought I'd post just in case someone else is thinking about getting out the soldering iron.
The funny thing is that after my new (old) phone (a nice one too) I bought from eBay showed up, I started flashing and generally screwing around. Both phones look the same so I couldn't tell exactly which one was which, so I plugged them both in, thinking that I'd fine the one that was responsive. They both went into the Ginger Bread funky "Firmware Upgrade Failed" screen. This was a head scratcher, indeed. I read a while back about how build dates are important when flashing soft bricked Captivates.
One of the phones has a build date of 1007. Since is well before 1010, I looked around for the Eclair Stock ROM and found it here.
http://forum.xda-developers.com/showthread.php?t=731989
It appears that the early Captivates are very particular about what you flash when going back to stock. I couldn't tell you why the old phone started working. Maybe because I used a JIG then pulled the battery out for a few days? It's possible. All I know is that "I897UCJF6-final-OCD-REV0" one-click has them both up and running.
At least now I know what I can call my "reset". I'm going to flash GB, then see if I can get to Cognition again, and try "cm-10.2.1-captivatemtd". If they bomb out, I feel real good that I have a way to bring them back.
I hope this can help someone along the way. With the Captivate selling for about $50, albeit 3G, it's not a bad phone at all.
Ok guys,
as the title says Lumia 710 is bricked.
It had last factory update and everything was working fine. Then i had to mess with it and to try to install Rataplan V9.1.
The process was working ok. By default, bootloader was in DLOAD mode, so in order to install custom ROM i needed to upgrade to Qualcomm. I have upgraded it and installed Rataplan .nb rom to the phone with NSSPro V0.54.
This is when my problems start.
The phone starts with one long vibration followed after few seconds with one short virbtation and thats it. No screen, no system, zip!
When i try to connect it again by usb to check it with NSSPro, it always starts in NAND disk mode. It does not matter do i start it normally on power button or with volume up. Its always in NAND. And it is always stuck. While the phone is connected to USB i can see Qualcomm CDMA Technologies MSM device in device manager but it has yellow mark like the driver is not installed.
I have tried several other roms, and NSS always shows that the rom is successfully installed, but the phone (other than vibration and NAND mode) is dead.
I have also tried all the solutions i could find on the net but no help. Tried, nokia recovery tool, WP recovery tool, Chimera e.t.c. Nothing works. Now i have a problem with NSS. It keeps stucking and beeing unresponsive for every option except Custom OS flash. Whatever else i click it either says tha phone is not detected or the app stucks and shuts itself down.
Is there other tool i can try?
Can i do anything to recover this phone or did i kill it?
PLEASE HELP!!!
Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.
droidzer1 said:
Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.
Click to expand...
Click to collapse
Tried allready every solution that i could find or think of, including things You described. Nothing. I was left with no other option but to send phone to service. They have a box unit with which they should be able to recover phone.
That was 2 days ago. today is third day so i am thinking that my phone has gone beyond repair. Only thing i can do is to wait and see...
Why not...?
Why not send it in real life to a windows phone expert. There should be a place to get phones repaired But, if they say that it isn't possible for them you may have rendered your phone useless. Google should be your mighty friend in this case :crying: I wish you very good luck.
Hello Moto,
So I got my Moto G5s Plus awhile back when it was still new and I tried to root it right off (I know...it was stupid, I realize I should've waited a little until the stock firmware was released and more guides were made), and basically I ended up hard bricking my device.
There are no lights, the screen is completely blank, and the power button does absolutely nothing.
I have heard of a way to revive it from level 0, however, and I was on the path to doing that until I realized that-for some reason-my laptop does not recognize my dead phone at all. In the guide (which I've long since lost the link to..) it said that my phone would appear in my device manager (>start>right click on Computer>manage) under the android tab after installing a bunch of ADB drivers and such, as "ADB-somethingsomething". No such thing happened; I couldn't even find the tab it was referencing. Even after uninstalling and reinstalling the drivers that it mentioned, I couldn't seem to get my laptop to recognize my phone.
Interestingly enough, or perhaps not, I plugged it into my brother's laptop and it recognized it just fine (note, he had the drivers already installed and has meddled quite a bit already in this area).
Anyway, so now I have a pretty much mint condition hardware Moto G5s Plus, and I kind of don't want to spent money on another phone unless I know for sure that I can't fix this one. Is there any way to revive it from the dead?
P.S. I've found the stock ROM for the phone...but there's several different packages. (like..NPS26.116-26; NPS26.116-45; NPSS26.116-45-5; etc...) This my be a very stupid question..but how should I know which one is the one I need to download?
Any and all advice/help would be appreciated.
Thank you
[SOLVED]
So I managed to get it working without using a virtual machine.
To address the first problem, my phone wasn't even charged. To solve this I took a rubber band and tied it around the power and volume down buttons and attached it to a wall outlet for about an hour. (The little white light was flashing to signal that it was receiving power...which was more than I had accomplished than..ever..really...)
The second problem was my computer. I still don't know why it worked out like this, but essentially my computer never recognized my phone as the HS-USB or anything. Instead, my computer recognized it as Motorola ADB Interface (even though it was technically off and hard bricked..). This made recovering it easy, as I simply could fastboot flash the correct stock rom to my phone and go from there.
After trying a few different stock ROMs, I finally got the right one, and could boot into bootloader. And thus, finally, I was able to install TWRP, the OS back, Xposed, and Magisk.
I've used my phone for a bit now and no problems have come up. Installing Xposed did take a bit longer than I thought it would, but other than that I got me phone back.
My moto g5s plus is completely dead even bootloader is not working nothing to show just blank how I can get the solution of this problem. Company is asking to change the motherboard. Help
jaura.mohit said:
My moto g5s plus is completely dead even bootloader is not working nothing to show just blank how I can get the solution of this problem. Company is asking to change the motherboard. Help
Click to expand...
Click to collapse
Are they charging u for the motherboard Change
Yes 18000 rupees
---------- Post added at 06:55 AM ---------- Previous post was at 06:29 AM ----------
yograjfire18 said:
Are they charging u for the motherboard Change
Click to expand...
Click to collapse
18000 rupees hel p me to recover my phone
Rooting is software based thing, which should not damage hardware to that level,, right?
The blank-flash stuff can be helpful for you guys, but we don't have blank-flash files for our device.
You can search, learn and manage how to do it.
EDIT: can you check what happens if you keep pressed powe key and volume- key for atleast 2 minuts ??
____Mdd said:
Rooting is software based thing, which should not damage hardware to that level,, right?
The blank-flash stuff can be helpful for you guys, but we don't have blank-flash files for our device.
You can search, learn and manage how to do it.
EDIT: can you check what happens if you keep pressed powe key and volume- key for atleast 2 minuts ??
Click to expand...
Click to collapse
Yea, no, this is 100% software damage. Like I said, I have a mint condition (hardware wise) phone. I'm pretty sure what I did to mess it up was overwrite the data files for the previous OS. I remember trying to get it back to stock ROM, but having a crap ton of trouble finding it...and then pretty much doing a fight or flight thing and trying a stupid and edgy alternative. (I also remember, even while the phone was still working, it only booted into TWRP once or twice, otherwise it would always come up with an error)
I feel like all I need to do is flash the stock ROM to the device...but without my laptop even recognizing it, I don't know how. Essentially, the question being, is there a way to flash the stock ROM to my device without TWRP, without bootloader, without using the device at all (just my laptop); and if there is...does anyone know how?
Pressing the power and volume buttons did nada.
[edit]
I did some searching and I actually found the two links that I used while trying to recover my phone from the dead.
http://www.aryk.tech/2017/09/moto-g5s-plus-unbrick-solutions.html
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
The difference for me is that I never got my laptop to recognize it as any of the "HS-USB Bulk, HS-USB QDLoad 9008, QHS-USB DLoad 9008"; that's where I stopped in the steps.
I'll be trying to follow the steps in the first link again, but this time through virtualbox (make sure there's no conflicting drivers and whatnot). I'll post back with results whenever I get around to it.
flash -61