Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
wrong forum mate...if you go to this link, they might be able to help you there
http://forum.xda-developers.com/forumdisplay.php?f=1431
hi, i have same problam with my galaxy nexus. i just want to ask how to fix my phone, thanks
IamPoison said:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse
onlinemoon said:
hi, i have same problam with my galaxy nexus. i just want to ask how to fix my phone, thanks
Click to expand...
Click to collapse
i have same problem. can you fix it now?
---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------
IamPoison said:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse
i have same problem. can you fix it now?
adesos said:
i have same problem. can you fix it now?
---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------
i have same problem. can you fix it now?
Click to expand...
Click to collapse
Well done for not reading the thread and realising you were asking the question in the *wrong forum*!
Hey man I have the same problem and my phone is also from UAE. Did you figure it out??
Sorry posting here.
WTF are these guys for real? This thread should have been deleted the day it was started!!
This is posted in wrong section.
**Reported**
Thread Closed​
This forum is for the galaxy note, please post in the correct forum​
Related
I'll tell you the whole story, to get your best understanding of my problem, so please read and help me if you can!
So i've had quite a few problems while trying to modify some stuff on my Android Samsung Galaxy S I9000M from Bell.
At first what I did was root my phone. Secondly I installed Darky's 5.6 Gingerbread edition, but like a dumbass I didn't understand how to install, so I dragged and dropped through the windows explorer the contents from the .zip.
Ever since I've done this, i've had non stop problems.
I've installed Odin 3.0 and the samsung drivers for my Windows 7 64bit computer, and have had the phone recognized by the Odin software when it's in recovery mode, as well as when using it as USB storage. I have never had the phone be recognized by Samsung Kies.
So after I screwed up the installation of Darky's 5.6 my phone started to act all screwed, problems like a ton of force closes, and a few missing apps. This isn't even the worst of it.
My phone started after a while to load up normally, and once I unlocked the device from it's home screen, it would immediately restart, and do it's fancy google color thing for a minute, and then load it's home screen. It would then do this automatically until I took the battery out.
One day after being fed up from hearing my dad yell at me after I just got the phone, I hooked it up to Odin got it to be recognized by my computer, and then tried to load on a new firmware. Nothing worked. There was no message saying it worked, no progress bar was moving, and nothing in the text area where it tells you what its doing, was moving from it's original state of recognizing the device.
I pulled out the device in frustration and turned it on. TADA! Something in there seemed to make it revive and actually work as a phone again. So I made sure it was charged all the time and tried to refrain from restarting the device in fear it would happen.
Well it had restarted, and things were still working fine, no big problems, nothing that wasn't fixed by a restart. Then suddenly I kept getting a lot of force closes on my SMS apps, or Phone app, as well as pretty much anything that was running on my phone started to force close, so I reset my phone.
Bam. Everything has hit the fan now.
My phone turned on and all I had was an Applications button in my single menu window. No phone, no sms, no settings or anything. When i clicked it, it would force close. On my phones first window, it would show "YouTube", "Calculator" and 3 other apps, which I never used.
Ever since then my phone has been a brick to me, with no connectivity to Odin, and no random working resets.
I've tried almost everything I've read here, and my biggest problem is that it's not connecting to Odin properly.
So please, what can I do to fix my phone without having to go pay to get it fixed. Bell said they would charge me $35 to even send it out and then charge me on top of that to fix it.
so no one has any idea what i'm doing wrong? or has experienced similar problems?
Try to reinstall the drivers in kies.
If that don't work do download
Them from android development site.
It should work.
Try the phone in all mode you can to get the drivers to install right.
Then you can try to fix it with kies or odin.
**DamianGTO Steam kernel. 349MB Ram. 256HZ. ext2. js3 base**
Another approach
I too cannot get odin or kies (or usb mass storage) recognized on the PC. I tried for a long time and gave up.
Are you rooted or can you access the root dir? If not can you access the external SD card or market so that you can root?
Do you have clockwork mod or similar?
I can only base my experience never using odin or a pc...
If you can get into recovery mode and start using (if you do not have it already)clockworks mod (and/or steam recovery - which I highly recommend as it can access the removable sd card which is useful to load stuff on to when things go sideways see why in my post http://forum.xda-developers.com/showthread.php?t=929020 ).
Then you can flash whatever you want from the root directory or with steam from the external SD car (root dir there) no odin or pc required (directly).
Then I'd start with stock or at least a custom rom that is based on your carriers stock and go from there.
G
wastedkila said:
I'll tell you the whole story, to get your best understanding of my problem, so please read and help me if you can!
So i've had quite a few problems while trying to modify some stuff on my Android Samsung Galaxy S I9000M from Bell.
At first what I did was root my phone. Secondly I installed Darky's 5.6 Gingerbread edition, but like a dumbass I didn't understand how to install, so I dragged and dropped through the windows explorer the contents from the .zip.
Ever since I've done this, i've had non stop problems.
I've installed Odin 3.0 and the samsung drivers for my Windows 7 64bit computer, and have had the phone recognized by the Odin software when it's in recovery mode, as well as when using it as USB storage. I have never had the phone be recognized by Samsung Kies.
So after I screwed up the installation of Darky's 5.6 my phone started to act all screwed, problems like a ton of force closes, and a few missing apps. This isn't even the worst of it.
My phone started after a while to load up normally, and once I unlocked the device from it's home screen, it would immediately restart, and do it's fancy google color thing for a minute, and then load it's home screen. It would then do this automatically until I took the battery out.
One day after being fed up from hearing my dad yell at me after I just got the phone, I hooked it up to Odin got it to be recognized by my computer, and then tried to load on a new firmware. Nothing worked. There was no message saying it worked, no progress bar was moving, and nothing in the text area where it tells you what its doing, was moving from it's original state of recognizing the device.
I pulled out the device in frustration and turned it on. TADA! Something in there seemed to make it revive and actually work as a phone again. So I made sure it was charged all the time and tried to refrain from restarting the device in fear it would happen.
Well it had restarted, and things were still working fine, no big problems, nothing that wasn't fixed by a restart. Then suddenly I kept getting a lot of force closes on my SMS apps, or Phone app, as well as pretty much anything that was running on my phone started to force close, so I reset my phone.
Bam. Everything has hit the fan now.
My phone turned on and all I had was an Applications button in my single menu window. No phone, no sms, no settings or anything. When i clicked it, it would force close. On my phones first window, it would show "YouTube", "Calculator" and 3 other apps, which I never used.
Ever since then my phone has been a brick to me, with no connectivity to Odin, and no random working resets.
I've tried almost everything I've read here, and my biggest problem is that it's not connecting to Odin properly.
So please, what can I do to fix my phone without having to go pay to get it fixed. Bell said they would charge me $35 to even send it out and then charge me on top of that to fix it.
Click to expand...
Click to collapse
Hey!
I've had the EXACT same problem as you. did you try to put your phone into DOWNLOAD MODE (Close phone, then hold volume down, then home, then power) to see if it connects to odin? Also, before you do anything, make sure you turn on odin first and then select all the files you want. After thats done, then put your phone into download mode, then connect the phone to your computer thru the USB.
I have the feeling I'm going to get repetitive here guys, but I've been reading the troubleshooting threads for over an hour and couldn't find an answer to help me.
Last saturday I was to lazy to move from the couch, so I watched as my S3 Mini ran out of battery. I got the "phone is turning off" screen as usual. Later I went to bed, but as I needed my alarm to go off in the morning I tried turning it on again, and nothing* happened. Plugged it on the wall, nothing*. Replaced the battery, nothing*. Gave it a good half hour plugged, and as you can guess, nothing*.
* when I say nothing, I mean it won't light up, won't vibrate, won't wink for me, won't load any kind of error, it's actually just like if you were trying to turn on a phone without any battery connected, no grasp of life comes from its poor soul.
The only moment I could see some action on the device is when I tried connecting it on the PC a few hours ago, as it installed drivers to Windows. Right after installing the drivers however, it won't show in the file explorer. I've tried to detect it with a few development tools such as ORT and Odin and there was no sucess either. Download or Recover mode will not work as well.
One thing I think worth mentioning, is that ever since I rooted it a couple of years ago, whenever I tried to recharge it while it was off, the standard "green charging battery" would never appear. What would appear on the screen was a freezed loading icon (the one that keeps roling again and again, but frozen). This particular issue never came off, even reseting it or installing new ROMs.
I always used Maclaw's, some of the latest 4.x, because I tought the 5.x was to heavy for the s3 minis.
I've read some about USB JIGs and stuff, but what makes me very curious is what the heck?! The phone was working just fine, the battery runs out and I have a brick? Is this possible? Can anyone tell me any work around?
I apologize for possible grammar mistakes.
ScrewedImei said:
I have the feeling I'm going to get repetitive here guys, but I've been reading the troubleshooting threads for over an hour and couldn't find an answer to help me.
Last saturday I was to lazy to move from the couch, so I watched as my S3 Mini ran out of battery. I got the "phone is turning off" screen as usual. Later I went to bed, but as I needed my alarm to go off in the morning I tried turning it on again, and nothing* happened. Plugged it on the wall, nothing*. Replaced the battery, nothing*. Gave it a good half hour plugged, and as you can guess, nothing*.
* when I say nothing, I mean it won't light up, won't vibrate, won't wink for me, won't load any kind of error, it's actually just like if you were trying to turn on a phone without any battery connected, no grasp of life comes from its poor soul.
The only moment I could see some action on the device is when I tried connecting it on the PC a few hours ago, as it installed drivers to Windows. Right after installing the drivers however, it won't show in the file explorer. I've tried to detect it with a few development tools such as ORT and Odin and there was no sucess either. Download or Recover mode will not work as well.
One thing I think worth mentioning, is that ever since I rooted it a couple of years ago, whenever I tried to recharge it while it was off, the standard "green charging battery" would never appear. What would appear on the screen was a freezed loading icon (the one that keeps roling again and again, but frozen). This particular issue never came off, even reseting it or installing new ROMs.
I always used Maclaw's, some of the latest 4.x, because I tought the 5.x was to heavy for the s3 minis.
I've read some about USB JIGs and stuff, but what makes me very curious is what the heck?! The phone was working just fine, the battery runs out and I have a brick? Is this possible? Can anyone tell me any work around?
I apologize for possible grammar mistakes.
Click to expand...
Click to collapse
try to plug in the phone into charger & leave it there like 20 mins or more. battery loads then.
then try access samsung download mode, if you cant the phone is probably useless (brick for ever) because itslike mthe last standing thing.
& sorry i say that but thats typically samsung behaviuor. there allways this kind of threads in the samsung forums of xda... other manufacturer can mostly be restored or atleast you know what make it dead.
Exactly the same problems happening to me.
This is my thread:
http://forum.xda-developers.com/galaxy-s3-mini/help/sgs3-mini-dead-t3085031
Can you try to follow what appears on this link? (I can't by now because my PC is broken)
I think won't do nothing because you won't be able to access to the recovery mode on android, as me, but to try...
http://forum.xda-developers.com/showthread.php?t=1840030
bejunk said:
try to plug in the phone into charger & leave it there like 20 mins or more. battery loads then.
then try access samsung download mode, if you cant the phone is probably useless (brick for ever) because itslike mthe last standing thing.
& sorry i say that but thats typically samsung behaviuor. there allways this kind of threads in the samsung forums of xda... other manufacturer can mostly be restored or atleast you know what make it dead.
Click to expand...
Click to collapse
Hi there,
Thank you for your interest but I have passed this point already. Tried a brand new battery I had laying down in the drawer (which was fully charged with an universal charger) and there is no answer to any attempt of turning it on. Via recovery, download or normal boot.
CrashOverride93 said:
Exactly the same problems happening to me.
This is my thread:
http://forum.xda-developers.com/galaxy-s3-mini/help/sgs3-mini-dead-t3085031
Can you try to follow what appears on this link? (I can't by now because my PC is broken)
I think won't do nothing because you won't be able to access to the recovery mode on android, as me, but to try...
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
Hello there,
I'm sorry to hear I'm not the only one affected by this bug (lets call it a bug). This shows there is a lack of concern from Samsung on dealing with this issues, and thus we see that old programmed obsolescence.
I will try that later on the weekend, and I come back here with an report.
Cheers
ScrewedImei said:
Hi there,
Thank you for your interest but I have passed this point already. Tried a brand new battery I had laying down in the drawer (which was fully charged with an universal charger) and there is no answer to any attempt of turning it on. Via recovery, download or normal boot.
Hello there,
I'm sorry to hear I'm not the only one affected by this bug (lets call it a bug). This shows there is a lack of concern from Samsung on dealing with this issues, and thus we see that old programmed obsolescence.
I will try that later on the weekend, and I come back here with an report.
Cheers
Click to expand...
Click to collapse
this guide useless for you. how u want flash things with odin if u cant enter download mode at all??
im really sorry for you that this phone is dead. just can give you 1 advice, dont buy samsung in future.
I have been repaired my phone successfully!!!
I just needed to change two capacitors on its motherboard, and that's it.
Here the video where I have found the info and how to do that. It's in Spanish but easy to understand for you I think. But if you need some help, send me a PM.
can you take a picture from the location of the 2 capasitors and the types of it
Hi everyone.
I have some news. It took me a while but I followed CrashOverride93's advice on that video. It actually solved one issue, as I now can turn it on, but now I have a second problem, I'm stuck on a boot loop, with acess to Download mode ONLY. No recovery.
Considering where my issue started, and where I am now, I have tried the following:
- Flashed via Odin stock ROM, kernel;
- flashed Wipe;
- flashed PARAM;
- three button combo.
So far I couldn't get it pass the boot loop. Any thoughts?
Hey Guys
Hope, some of you can help me. The problem is:
i bought a new HTC One Mini 2. Cause i had a Cyanogen 10.1 on my previous phone, i thought, that i should install a new CyanogenMod for this phone again. So i unlocked und flashed the Phone. As custom recovery i used TWRP 2.8.5.0... Found that one here in a Thread. After i flashed cm-12-20150411-NIGHTLY-memul.zip on it. After all, i started my phone again and all worked fine. i thought....
So yesterday i powered off my phone, plugged it to the charging-cable and went to sleep. In the morning i got up, picked my phone and wanted to turn it on. What i saw, was the charging screen, blink led is standing on orange and thats it. Cant power it off again, cant boot to recovery... nothing...
And the point is, i dont have the ultilities and the skill to open the phone and remove the battery to see, if that is the problem.
Do you have any ideas for that?? Thanks for leave an answer
lol
peacer95 said:
Hey Guys
Hope, some of you can help me. The problem is:
i bought a new HTC One Mini 2. Cause i had a Cyanogen 10.1 on my previous phone, i thought, that i should install a new CyanogenMod for this phone again. So i unlocked und flashed the Phone. As custom recovery i used TWRP 2.8.5.0... Found that one here in a Thread. After i flashed cm-12-20150411-NIGHTLY-memul.zip on it. After all, i started my phone again and all worked fine. i thought....
So yesterday i powered off my phone, plugged it to the charging-cable and went to sleep. In the morning i got up, picked my phone and wanted to turn it on. What i saw, was the charging screen, blink led is standing on orange and thats it. Cant power it off again, cant boot to recovery... nothing...
And the point is, i dont have the ultilities and the skill to open the phone and remove the battery to see, if that is the problem.
Do you have any ideas for that?? Thanks for leave an answer
Click to expand...
Click to collapse
I works again. was some buggy thing, i guess. A friend took my phone, did same combination that i did to boot in recovery mode and BOOM it reboots and work properly. So, i can't tell u a real solutions, but if you got same problem, keep trying with the POWER-Button and the VOLUME_DOWN-Button. Worked in my case.
Thread can get closed.
peacer95 said:
I works again. was some buggy thing, i guess. A friend took my phone, did same combination that i did to boot in recovery mode and BOOM it reboots and work properly. So, i can't tell u a real solutions, but if you got same problem, keep trying with the POWER-Button and the VOLUME_DOWN-Button. Worked in my case.
Thread can get closed.
Click to expand...
Click to collapse
What he did was a hard reboot, accomplished by holding the power and vol-up buttons for about 10 seconds. Just wanted to add this.
Hey guys,
any solution to this problem??
Got the same issue. unlocked bootloader with htcdev, installed TWRP Recovery and rooted phone, everything worked fine yesterday.
Today I installed xposed framework, then I plugged-in the charging cable and turned off the phone because I wanted to flash xposed in Recovery. But when the phone turned off, it only showed the charging screen with the message ("This build is for development purposes only Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action.") and didn't react to any button pressings until the battery finally died.
Then I plugged in charging cable again. Now I have again the charging screen, only difference is that the LED doesn't flash permanently but it now blinks. Computer recognizes phone but I can't send fastboot commands since it is turned off.
Any help would be appreciated!
EDIT: After a lot of tries, I finally also managed to fix it with 10 seconds power + volume up....
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