Hello there!
I recently got my hands on stock Moto G4 from my cousin. The thing is, he fell with it on his pocket and now when you try to power it on it show the Motorola logo screen briefly, turns off, then turns on again and shows the logo screen again and so on. The phone charges up normally, enter fastboot mode just fine (although I can't enter recovery, only little droid with exclamation mark, but maybe it's because it's locked).
I searched throughout the xda forums and google for solutions and tried everything that looked like it could work. Nothing did. I tried the following:
1 - Change the battery;
2- Install another stock rom via fastboot and adb;
About the phone state: the display is just fine. The only things that were damaged with the fall were a part of the back that was a little kneaded, a little below of the sim slot. As I disassembled the phone I noted that the metal shield in that place of the motherboard was a little bit kneaded too.
I am afraid it might be more of a hardware issue, but if you guys could give me some light or some other ideas, it would be really appreciated.
Thanks!
Related
Here's the whole story:
My Cingular 8525 has sticked to bootloader about a month ago, and after the study ( flashing different ROMs, search wiki here ,search web pages, forum ) ,I finally sent it to some workshop to have one chip replaced.
After the replacement, everything goes fine.But now it sticks to bootloader again, it some time can boot into OS, but most of the time , it will boot into bootloader.I found taking battery out and leave the phone awhile then put the battery back could some time "help" the phone to boot into OS.
When boot, the phone seems to have not enough "strength" to boot into normal OS, so it select to boot only in bootloader.Maybe we could just give the phone some "strength"?
And this time, I guess,it is not the chip which might lead the problem.
So has someone any suggestion ? ( When I disassembly my phone, I found there's one little battery on the mainboard, might the battery has some thing to do with this ? )
What os are you using? If its wm6.1 that could be your problem - stability issues... You might have bad blocks. Check this using MTTY... Instructions on the Hermes upgrading forum.
Wouldn't remove the battery on the mainboard unless you know what it does. yYou could ask Mike Channon as he is the guru of hardware...
Hope this helps...
Cheers...
This happened to me too and all I had to do was hold the power button longer until the screen comes on
black981502 said:
This happened to me too and all I had to do was hold the power button longer until the screen comes on
Click to expand...
Click to collapse
...and it can "cure" the bootloader ?
On my phone, I really need to hold power button longer, but the screen still comes with bootloader.
Recently I guess it might be because of the shield of the "mainboard-screen wire"(I 'm Chinese and does not know how to exactly express this stuff). When I replace the connector myself(I recently replaced this wire to fix the white screen problem , and white screen are gone, but the bootloader comes soon ), I found the wire is originally wrapped using some metal paper, and because the old metal paper has been stick to old wire using glue or something and hard to take it off, so I left the new wire "raw",after I assemble the phone, everything goes fine, but after one night , the phone goes into bootloader.
I'll disassemble the phone these days and add some new metal paper to wrap the wire and see the effect.
PS:
Appending to the sympton:
When the phone is booting
If the signal led turns green ,the phone will boot into OS, and soon the logo will appear.
But if the led does not light up, the bootloader will come soon.
After I disassemble the phone and add some metal paper to wrap the wire, 8525 first boot normally into OS.
But after one night continous power on, after one reset, the phone goes into bootloader again.
It was so frustrated!Maybe there really had some hardware issue in my phone ? Can someone figure it out ?
Has anyone any sugestion?
PS.
During the one－night “OS Time”， when I reset the phone and intensionally boot the phone into bootloader, the phone cann't start card-flash process even if the condition of card-flash are all met( card, filename, FAT32 ).
But after the OS Time ,I reset the phone without pushing power+ok button, instead of boot up normally, the phone goes directly to bootloader and start to "card-flash", after the flash , the phone finally stick to bootloader.
Someone help me please, even some clue or where I could probably find any clue!!!
First of all, hi to all of you.
Me being a noob with the Nexus, something VERY messed up has just happened to me.
Let me explain from the beginning:
I received the nexus yesterday as a gift from a friend of mine who works at Google (yes, it is the one with the android waving a banner on the back of the phone)
Used it yesterday perfectly, even updated to 2.1.update perfectly fine.
Today, as the batter was dying out, I finally got home and started to charge it (the battery icon was white, with a red outline and a red slash across the battery icon)
Then, the Nexus stopped responding and turned off.
When I tried to turn it back on, it just stays on the boot screen and does nothing.
Now, I have tried the volume down + power button to get to the reset, chose "recovery" and it went right back to the frozen boot screen.
To my knowledge, it is not rooted (although I have read that the Nexus' that employees receive are rooted, I have no idea)
Now, I am stuck with a Nexus paperweight , it doesn't turn on and cant seem to get it out of the boot screen.
Any one here can lend a hand???
P.S. I hope I posted in the correct forum and want to thank anyone that can help ahead of time!
Update:
I did the volume down + trackball + power on thingy and I connected the Nexus to my laptop.
It comes out FASTBOOT USB in red, so it seems it is not totally bricked.
Found the USB drivers and...that's where I am stuck.
I know there is a way to recuperate the Nexus, but I have no idea how...any ideas?
EDIT: Total NOOB moment here, the phone doesn't come with the battery installed, it's sitting at the bottom of the box under the documentation. I was thrown off by the fact that the bootloader said battery ok.
Just got the Amazon Prime edition Moto G Play (Model XT1607) in the mail today and it's just in a continual boot loop cycle; the Moto splash screen flashes for a few seconds and then reboots. I'm able to get into the bootloader, but any option I select just reboots the device. I assume it's hardware issue because it only even turns on if I have the charger plugged in (although the bootloader screen does say battery is ok), it shuts off immediately after removing the cord (yes, I've let it sit plugged in for a while). Is there anything I can try without being able to get into recovery? I assume I'm out of luck until they post the factory images for this model?
Hahaha it's okay bro, we've all made some kind of noob mistake at some point.
I once spent four hours trying to root a phone, everything went perfectly, I'd reboot the phone and still not have root. Turns out, I didn't realize my GF plugged her phone into the back of my computer to charge and adb was only picking up her phone instead of mine.
Sent from my Moto G Play using XDA Labs
Hey, I broke my op2 screen so I bought one from ebay, teared it apart all correctly (i'm a computer technician), installed the new screen, all fine but a weird symptom appears:
- It boots and shows the Oneplus logo then screen all black. I know it booted cuz the touch buttons work and i can ear the sound of unlocking etc. Also if i plug into the pc I can easily access its memory.
- If I try to enter recovery I know it enters too but the screen is all black, the only mode I can see the screen is fastboot mode and it stays and acts normally.
- I did a full reset on the phone back to stock via adb, thinking it was software, its all stock now, still the same occurs
Im out of ideas so I just think the screen is faulty from ebay, did this happened to anyone?
Thanks in advance
My screen broke 6 months ago, so it wasn't used/charged for 6 months. Now I've replaced the screen, but it won't start up anymore. First thing I saw was the warning "low battery", so I charged it for a while. Still, nothing. Charged it for several days, nothing. Checked the battery voltage, 3.80 volts, exactly what it should be I think?
The phone does do something though. When I hold the "on" button, after 5 seconds it buzzes and the screen shows the oneplus logo and android. Just for two seconds, then nothing. Same thing with "on" and volume down, the start-up screen for 2 seconds...
When I use "on" and volume up, I get the screen saying "fastboot mode". And that doesn't go away untill I press "on" for a while.
I can connect it to my laptop, but cant see it. But when I take the battery out while connected to the laptop, the phone will show the "low battery" warning. Connect the battery again, and the logo and android message come on for two seconds...nothing more.
So the screen works, the battery is charged, but no way to turn it on. Tried holding the "on" button for 15 seconds, same result. Just a 2 seconds oneplus logo visible...
I have no clue what this could be, I hope its not completely fubar...
Thanks in advance, Fred Doe
Hey Fred Doe,
I wouldn't like to hijack your post, but I seem to have run into the exact same issue here.
A friend of mine got his screen replaced, and the phone acts exactly the same as yours.
I have disassembled the phone and checked all connections, but everything seems to be correct on the inside.
The phone does seem to boot, and it does boot into recovery mode (it responds to the button presses by vibrating) but the screen just doesn't show anything.
Only when doing fastboot the screen stays on.
Hopefully someone here can point us in the right direction.
there's not much to hijack here...sure sounds like the same problem. At this moment I gave up, guess its a lost cause..
Guys, the exactly same thing here. I've tried to unbrick it but failed.... So far what I know is that bootloader is locked.
I would like to know what steps should us do in order unlock bootloader, get screen functioning while getting access back to bootloder (TWRP) so after that we can install a new ROM!
Any clue from the community of OnePlus 2? This phone is still a good phone! Thnx
Have you guys tried running the msm tool. It'll restore everything to stock if you can it to work. If either of you have magisk installed it can cause issues with charging while the phone is off I believe.
I mean honestly sounds more like hardware issue that a msm wouldn't fix, but it's weird that your screen works in fastboot.
If you do the msm tool though be aware it will wipe everything on your device, and relock the bootloader if it is unlocked.
Like I said doubt it will help, but just a thought.
Edit: Also make sure you use the correct one for your device.
Edit sorry guys wrong forum ignore everything I said. Apparently xda labs thought my OP6T was a OP2.
Sent from my ONEPLUS A6013 using XDA Labs
@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.
dajosova said:
@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.
Click to expand...
Click to collapse
But the screen does show up & stays on in fastboot?
I'm no expert but any stretch. I just jumped ship from lg my 6t is the 1st OP phone I've owned. But if the screen does work normally in fastboot then it wouldn't be illogical to entertain the idea that it was a software issue. So I mean this is a bit of a chin scratcher.
Sent from my ONEPLUS A6013 using XDA Labs
Thanks for replying.
IWhen I press Power + Vol. Up it shoes Fast Boot screen. Then I connect cable and sometimes I can use command line but can't unlock bootloader with command line. All methods found indicate to use Recovery but since my screen doesn't work on Recovery I'm stuck.
When I press Power + Vol. Down (for entering Recovery) screen it goes all black but the capacitive buttons and Volume button give back a vibration response, as if it have entered Recovery Mode but since I can't see nothing on screen I can do anything either.
My bootloader is locked because I see that info via command line.
Thanks anyway
PS: I think something is corrupted. My OP2 was unlocked much time ago. I frquently change ROM's and have also updated TWRP. The only thing I did was disassembling the phone in order to change a shattered screen glass.
I've also tried different methods and installed in my pc different Qualcomm drivers, ADB, etc.
I'm getting close to the point of testing with broken touch, buying a new touch screen but with frame or giving up completely and buy a new phone :|
The last option get me in doubt because I would like a phone wich is good and fast and decent battery but not with a premium price... and popular so I can unlock it without hassle in order to install root apk's.