oneplus 2 not working after screen replacement - OnePlus 2 Q&A, Help & Troubleshooting

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.

Related

I need some serious help.

My Nexus one won't turn on. I tried flashing RADIO 32.24.00.22U_4.03.00.21_2 that I downloaded from Modaco.
After it failed to install showing the error message like
"Multiple Radio images"
and a few others I try to reboot it.
when trying to reboot it there showed a picture of a android and a orangish arrow and a box.
Help...I think I bricked it.
Help?
Please?
Can you get into boot loader? Hold down the track ball, then power on, and keep holding down the track ball...
Also, try holding down the "volume down" toggle button while powering on if the track ball method doesn't work...
If both don't do anything but take you to that same screen, let it sit on that screen for a bit, say 10 minutes just in case...
If still nothing, see what happens when you plug your phone into your computer with the data cable, is it recognized? If so, can you get ADB to recognize it?
Jackasaur said:
Help?
Please?
Click to expand...
Click to collapse
can u get to the recovery image? if u can, its not bricked.
well I tried plugging it into the computer, I tried the wall charger, and nothing seems to work. The LED doesn't come on, and the button combination doesn't work. So I think it's dead for good. :C Before everything got screwed All I saw was a box and an arrow pointing at a android. Which I think meant it was unboxing. I then thought it froze so I tried to take the battery out, and after that it didn't turn on anymore. No LED, no recovery, no nothing. :C Quite sad.
Why the f are so many people intent on taking their batteries out while the phone is updating? I'm not saying that led to the bricking...but it probably didn't help.
Jackasaur said:
well I tried plugging it into the computer, I tried the wall charger, and nothing seems to work. The LED doesn't come on, and the button combination doesn't work. So I think it's dead for good. :C Before everything got screwed All I saw was a box and an arrow pointing at a android. Which I think meant it was unboxing. I then thought it froze so I tried to take the battery out, and after that it didn't turn on anymore. No LED, no recovery, no nothing. :C Quite sad.
Click to expand...
Click to collapse
This part takes a few minutes. I am not totally sure what is happening at this point but I'm assuming it's not good to remove battery during this. Mine sat on that screen for a few min and then finished.
Try to boot up with volume down button held. Then use volume arrows to choose recovery and hit power.
uansari1 said:
Why the f are so many people intent on taking their batteries out while the phone is updating? I'm not saying that led to the bricking...but it probably didn't help.
Click to expand...
Click to collapse
Everyone expects everything to be instant these days... "Uh oh! The screen isn't doing anything, it's been at least 20 seconds! I could just wait and leave it for a few minutes like all the guides say to do. Or I could take my battery out...how could that hurt, right?"
For me it took a good 3-4 minutes on the screen with the arrow and the box.
Anyways, if you can't get to the recovery then you might be buying a new N1.
ahh it took like 5 minutes for me, I have to admit I was a little worried since you dont see status bars or anything, but like said, the guides warn for this.
I cant imagine that removing the battery broke it though, he should be able to load a recovery image
I feel sad for him so bumping
Bleh. I'll just have to wait and see. I'll contact HTC.
tomsan84 said:
ahh it took like 5 minutes for me, I have to admit I was a little worried since you dont see status bars or anything, but like said, the guides warn for this.
I cant imagine that removing the battery broke it though, he should be able to load a recovery image
I feel sad for him so bumping
Click to expand...
Click to collapse
If you remove the battery during the period he did, which is when the phone is actually flashing the radio ROM, yes removing the battery can and likely did break it for him. There are 2 ways to brick an Android device, while flashing a radio ROM and while flashing an SPL...
OP, have you tried any of the button combos we have recommended? Have you tried putting your battery in the phone, then without turning it on, putting it on the charger to see if it can charge the battery at least (you said it wasn't even turning on, which is likely because you have a dead battery)... charge the battery first, then try the button combo's we recommended.
And please, when you report back, and not to sound like an ass, do so clearly and systematically (I can't tell from your posts what did or didn't happen, and whether you tried anything we suggested, nor what the current state of the phone is)... so, please use this format to make it clear to us trying to help:
Battery: Charged or Wouldn't Charge (LED will come on if it is charging)
Trackball+Power: Booted into boot loader, yay! or Went to the damn box
Volume down+Power: Booted into fast boot! or Went to the damn box
And remember, you have to hold down the button, either trackball or volume down, then press the power and keep holding down the trackball or volume down until it either goes to boot loader or it goes to the box screen... you might want to even wait for a minute on the box screen(if it goes to that) while holding down the button to make sure it can't get into boot loader...
Okay so I took the battery out, put it back in, and tried charging it. The Battery LED did not come on, so I'm guessing it's not charging.
The Trackball+Power did not work.
The Volume down+Power did not work.
I think I most likely broke it, due to the fact that I took the battery out while it was flashing the radio ROM onto the phone. I kinda did it on a impulse, which is my fault. So do you think it'd be possible if I did contact HTC they'd send me a swap, and not be able to make my phone work or turn on, and everything will go on as if I "broke" it and not unlock it or anything?
Jackasaur said:
Okay so I took the battery out, put it back in, and tried charging it. The Battery LED did not come on, so I'm guessing it's not charging.
The Trackball+Power did not work.
The Volume down+Power did not work.
I think I most likely broke it, due to the fact that I took the battery out while it was flashing the radio ROM onto the phone. I kinda did it on a impulse, which is my fault. So do you think it'd be possible if I did contact HTC they'd send me a swap, and not be able to make my phone work or turn on, and everything will go on as if I "broke" it and not unlock it or anything?
Click to expand...
Click to collapse
It sounds like you have a true brick... disruption of the radio ROM flashing causes lots of bricks, and did so for you.
It is pretty common, at least with T-Mobile with the G1, to call them up and tell them your phone asked you to update, and while updating it froze and won't turn on or charge anymore. Not sure if HTC will handle it the same as T-Mobile did, but if they do they will just send you a new unit, you send the old one back, and you are back up and running... they might ask that you send it to them first, but there is no way for them to test if it was rooted/unlock boot loader if it can't be powered on, so you should be fine.
Sweet. So I called HTC, and they said they'll repair it, but I asked for a swap instead, so I'll be getting one by either Wednesday, or Thursday. Good stuff! I'll tell you all how it goes. :] Now I am stuck with my Nokia N95. Thanks for all your help.
Did you tell them you have an unlocked bootloader?
uansari1 said:
Did you tell them you have an unlocked bootloader?
Click to expand...
Click to collapse
he doesnt have 2 tell em
lightforce said:
he doesnt have 2 tell em
Click to expand...
Click to collapse
Yeah, he doesn't have to tell them... but they don't have to cover his phone either.
If they find out it's unlocked after the fact, they can charge you to repair the phone.
How exactly will they know he unlocked the bootloader if the device cannot even properly turn on, unless htc has other methods of being able to "restore" the phone, then he should be rather ok. Am I not looking into this deeply enough? Can the phone turn on with a new battery or something? Does HTC have alternatives ways of checking?
Eclair~ said:
How exactly will they know he unlocked the bootloader if the device cannot even properly turn on, unless htc has other methods of being able to "restore" the phone, then he should be rather ok. Am I not looking into this deeply enough? Can the phone turn on with a new battery or something?
Click to expand...
Click to collapse
That's my point man.. I don't know. All they have to see is that open padlock and they can deny the claim.

help i9000 after flash, doing loop of at&t logo, can not enter download mode,

help i9000 after flash, doing loop of at&t logo, can not enter download mode,
when plugged in screen goes black.
!! if anyone can help please do not hesitate, mostly appreciated.
Try to hold the Down+Menu+Power combination while INSERTING the battery into the device.
i try that seem to have no response and when unplugged from usb it loop at&t logo
or plugged in usb screen goes black and no response seem from pressing buttons
I had a similar problem as most phones in Canada seem to have Download/Recovery mode disabled, and here is what worked for me.
Grab something like One Click Un Root (all models), and click one click un root (obviously phone has to be on and plugged into the computer).
This should automatically reboot you into Recovery Mode!
All you have to do is "wipe data/factory default" or something like that (should be the third option).
As it states, you will loose all your data, but at least you will have a functionning phone!
did it work?
Hi. I have similar problem. Can anybody give instruction what can I do?
I have this problem too. Please help somebody
Add me to the list. Bell Galaxy S, went to unlock my phone the screen went black. Now it will not boot into the OS, the galaxy S splash screen displays then nothing. The menu and back button light up, thats all. ****[email protected]@
I have not rooted or anything.
Of course my download mode does not work.. Going to try this one click root thing if I can find it.
NOT HAPPY
This is not working. Probably because the phone is not in USB debugging mode as I can't change it... Is there any other way to get the phone into recovery mode?
**** me
i had the same thing happen to me the other day with my bell galaxy s and my phone wont do the 3 button combo trick. i left my phone plugged in to a wall charger for a while until the back of the phone became a little warm. i pulled the battery and then left the power cord plugged in and put the battery back in. i held the volume down and enter button until the battery charging indicator showed up, then i also pressed and held the power button until the boot animation started (this is the blue moving swirl and music, not the galaxy s splash scree) and then i let go of the power button. it took a few attempts at this before it actually worked, but eventually it will go into download mode at which time you can open the odin app, then plug in the usb cable and flash your phone that way. it did seem to make a difference if the back of the phone (around the camera area) was warm. if i let go of the power button while the music was playing and the phone did not enter download mode i would keep all 3 buttons pressed until it shut down again, then i would only let go of the power button while the phone initiated the charging screen, then once the battery logo was displayed i would hold the 3 buttons again and would just keep doing this until it went into download mode. i have flashed it at least 5 times today and i have been able to do this each time.
i also had an issue where odin would not recognize my phone was plugged in and windows would show a message saying the usb device was not recognized. i left the phone plugged in and while in download mode i pressed the volume up, enter button and power button until the phone went blank and when the galaxy s logo showed up i let go of the power button and the phone would go into recovery mode and then the usb drivers would be installed. i would then do the 3 button combo for download mode and odin would work fine. it took several attempts but it does work. i hope this helps you guys
If I hold all three buttons the splash screen does not come on, it just keeps looping the Galaxy S logo until I let go of the power button....
xZeDgEx said:
If I hold all three buttons the splash screen does not come on, it just keeps looping the Galaxy S logo until I let go of the power button....
Click to expand...
Click to collapse
That's what mine did too, several times in a row and then it worked. For some reason it only works after the battery is charging for a bit and the back becomes warm. then it works at will
No luck. I am probably screwed getting it exchanged now too as I am passed the 14 days from Best Buy.
the on click thing doesn't work, if your phone is already bricked.
also it is not the phone's fault for not working, the phone was working properly before you tried the hacks.
whenever you do these kind of things you know you are entering into the "not supported" "not covered by warranty" zone.
in the worse case scenario, if you can no enter download mode to recover your phone, it'll be to take the phone back to bell and claim warranty on it, and prentent you don't know what happened to it.
xZeDgEx said:
Add me to the list. Bell Galaxy S, went to unlock my phone the screen went black. Now it will not boot into the OS, the galaxy S splash screen displays then nothing. The menu and back button light up, thats all. [email protected]@
I have not rooted or anything.
Of course my download mode does not work.. Going to try this one click root thing if I can find it.
NOT HAPPY
Click to expand...
Click to collapse
AllGamer said:
the on click thing doesn't work, if your phone is already bricked.
also it is not the phone's fault for not working, the phone was working properly before you tried the hacks.
whenever you do these kind of things you know you are entering into the "not supported" "not covered by warranty" zone.
in the worse case scenario, if you can no enter download mode to recover your phone, it'll be to take the phone back to bell and claim warranty on it, and prentent you don't know what happened to it.
Click to expand...
Click to collapse
Its my fault??
I did not hack my phone. Its not rooted, I did nothing to it.
By "unlock" I meant exactly that, unlock as in swiping the screen to unlock it.
The more I search the net the more posts I find of Galaxy S phones randomly bricking...
on the original message sounded more like you went to Unlock the phone, as in SIM unlock the phone using any of the tools available out there, and there has been already several people which had the same problem.
if you go back to Bell for an exchange, you better not use the word "unlock" rather use Swipe
as the message on the phone "swipe the screen to unlock"
there are no known issue about this causing the phone to brick.
if that is what happened to you, you should have started a new topic for people to help you, instead of hijacking the topic from the OP, as your issue is different from OP, the OP actually screwed up because he/she flashed the wrong ROM to the i9000
... anyways, Does it work if you reboot the phone?
I have rebooted the phone about 100 times. The phone crashed when I unlocked it to check a text I received. (not hacked). Has not booted up properly since. I have found many others with the same issue who have also not hacked/rooted/unlocked/ their phones.
Waiting on Best Buy to call me back. I am so pissed right now, I have been bragging to my friends and co-workers how awesome this phone is, one has already picked one up, I hope his doesn't brick too. Not recommending it to anyone anymore..
did you load a lot of MP3 to the phone?
can you boot into Recovery Mode?
in the recovery mode you can wipe the Cache and wipe the data
that should make your phone work normal again
it'll be best to open a topic to help you trouble shoot your interesting issue, as it's the first i've hear that you get a black screen after Swiping out of the lock screen
I can't get into recovery mode. I have tried every button combination I have found. I had about 2 GB of music on the phone. I also installed the Android SDK to try ADB, but since the phone is not in USB debugging mode it does not see it.
xZeDgEx said:
I can't get into recovery mode. I have tried every button combination I have found. I had about 2 GB of music on the phone. I also installed the Android SDK to try ADB, but since the phone is not in USB debugging mode it does not see it.
Click to expand...
Click to collapse
on the other topics relating to the 3 button not working.
have you tried the heating up method?
or the plugging the battery in, when all 3 buttons are pressed? (of course for this one you will need help from a friend, unless you are very skilled at keeping the 3 button on hold meanwhile able to slide in the battery in with out a 3rd hand)

Bootloop help

Hello, first off I will say I am a total novice when it comes to messing with my phone as my upgrade is in a month so I took the plunge and all was well at first. I used SuperOneClick to root my Flipside which runs Froyo 2.2.2. I deleted the bloatware as that was my main goal. This all took place about 2 weeks ago, and no problems existed.
Yesterday when I was reading a simple text message my flipside automatically reset itself and became lodged at the Motorola M logo. I've had this issue in the past before rooting so I just removed the battery in hopes all would work well as before, sadly that wasn't the case. My phone then booted up and only the backlight appeared on the screen causing it to become stuck in the infinite bootloop. I've tried all the different hard resets with the x button and power button, the volume down button, etc. None of them work as only the backlight comes up on my screen so I can't see anything. Is there any way to unroot it or flash it back to stock?
If any of my terminology seems out of place then sorry, I honestly have not a slightest idea what to do nor what is occurring other than the bootloop.
Any help is appreciated and can you please dumb down the answer for me if possible. Thanks!
Kippyyy said:
Hello, first off I will say I am a total novice when it comes to messing with my phone as my upgrade is in a month so I took the plunge and all was well at first. I used SuperOneClick to root my Flipside which runs Froyo 2.2.2. I deleted the bloatware as that was my main goal. This all took place about 2 weeks ago, and no problems existed.
Yesterday when I was reading a simple text message my flipside automatically reset itself and became lodged at the Motorola M logo. I've had this issue in the past before rooting so I just removed the battery in hopes all would work well as before, sadly that wasn't the case. My phone then booted up and only the backlight appeared on the screen causing it to become stuck in the infinite bootloop. I've tried all the different hard resets with the x button and power button, the volume down button, etc. None of them work as only the backlight comes up on my screen so I can't see anything. Is there any way to unroot it or flash it back to stock?
If any of my terminology seems out of place then sorry, I honestly have not a slightest idea what to do nor what is occurring other than the bootloop.
Any help is appreciated and can you please dumb down the answer for me if possible. Thanks!
Click to expand...
Click to collapse
Yup just rsd the sbf back. You will lose everything however so hopefully you've got a backup somehow. Here's the sbf
http://db.tt/H2RuCD8h
Okay so I've downloaded RSD Lite, and I have the file. The problem is I cannot get my phone into bootloader mode or recovery mode so that it will stop the infinite bootloop to stay connected to my computer. Advice?
Kippyyy said:
Okay so I've downloaded RSD Lite, and I have the file. The problem is I cannot get my phone into bootloader mode or recovery mode so that it will stop the infinite bootloop to stay connected to my computer. Advice?
Click to expand...
Click to collapse
I've had a similar problem as you with my flipside. Are you sure you're using the right key combination to get into rsd mode? If you can at the very least get it into bootloader mode by holding down the volume + key while holding the power button, I'm sure you can get it into rsd mode.
Kippyyy said:
Okay so I've downloaded RSD Lite, and I have the file. The problem is I cannot get my phone into bootloader mode or recovery mode so that it will stop the infinite bootloop to stay connected to my computer. Advice?
Click to expand...
Click to collapse
Theres a post here somewhere that has the combo of keys needed to get into bootloader mode. Sorry dont have it saved. Just do a search for it
Okay well I believe I found the thread you were talking about. It mentioned holding the up arrow on the keyboard combined with the power button for 4 seconds. Still nothing. I've tried the x button and power button, the volume up and power button. The thing is my screen won't work period. Nothing shows up but the backlight. So maybe I can or did get it to rsd or bootloader mode, but I can't really tell. I feel like something isn't right here. So I still can't connect it to my pc to use rsd lite.
Kippyyy said:
Okay well I believe I found the thread you were talking about. It mentioned holding the up arrow on the keyboard combined with the power button for 4 seconds. Still nothing. I've tried the x button and power button, the volume up and power button. The thing is my screen won't work period. Nothing shows up but the backlight. So maybe I can or did get it to rsd or bootloader mode, but I can't really tell. I feel like something isn't right here. So I still can't connect it to my pc to use rsd lite.
Click to expand...
Click to collapse
Did you by any chance have the stock launcher app frozen and using a different launcher? Just seems if you are seeing the backlight that possibly it is on the home screen but the launcher is corrupt? Not sure.
I'm not entirely sure. I assume it's stuck in the bootloop because when I power it on the backlight changes shades and then vibrates to signal the screen past the motorola M. Then I can touch the screen and feel a vibration to simulate to slide to unlock and if my usb cable is attached my computer makes the noise to signal it sees my device, but moments later my computer dings to signal device disconnected and my phone goes through the above process again.
I feel as if I can get to the factory reset screen and such because if I time it right I can stop it from doing anything mentioned above and it just hangs as if in a menu of some sort. The downfall is I see nothing and the backlight only appears.
I may just have to scrap it and say well done phone. I can't seem to find a similar issue anywhere on the internet. All the other issues can make the bootloader screen appear and that appears to be my number on problem.
I guess I was just being a complete idiot and thought I had removed my SD card when I didn't. Well now it can connect to my pc so I can flash it. I hope all goes well. I flash it then it should be back to factory settings right?
Kippyyy said:
I guess I was just being a complete idiot and thought I had removed my SD card when I didn't. Well now it can connect to my pc so I can flash it. I hope all goes well. I flash it then it should be back to factory settings right?
Click to expand...
Click to collapse
Yes like straight out the box. The backlight issue just seems to me like a launcher problem but that wouldn't explain why you can't get into bootloader mode. Hmmm strange. Here is another way I just thought of. If it connects to the computer (you said you hear the beep) reflash it via Motorola's site. All the instructions should be there (if they still support it)
Well I was able to flash it using RSD Lite. I could hear the start up tone and such (progress), but unfortunately my screen still won't show anything. I'm assuming the worst and maybe say hardware failure as to why the screen won't boot up? It randomly disappeared when it first went into bootloop and has never come back so that is why I assumed no working screen was a software issue.
Kippyyy said:
Well I was able to flash it using RSD Lite. I could hear the start up tone and such (progress), but unfortunately my screen still won't show anything. I'm assuming the worst and maybe say hardware failure as to why the screen won't boot up? It randomly disappeared when it first went into bootloop and has never come back so that is why I assumed no working screen was a software issue.
Click to expand...
Click to collapse
Yup that sounds like hardware failure. Haven't ever heard of the screen going out on the flipside but the atrix forums are full of them. Maybe you can get your upgrade early. Good luck

can't enter into fastboot

Hello i have recently tried to return my phone from cyanogenmod into the stock rom using this thread: "https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110" and my phone got stuck in the process while making the command "fastboot flash bootloader bootloader.img". And now my device is stuck on boot loop showing the cyanogenmod loading screen.
Anyway now i found a way to get to stock but for that i need to get my device into fastboot. THE PROBLEM IS that my device can't get now into fastboot! i have tried using adb commands but the adb doesn't recognize the device. I have tried fastboot commands but again it doesn't recognize the device. I also tried button combinations, but it didn't work.
Until the incidence i have used to press the power button+ vol down keys to get into fastboot mode, but now it doesn't work. I suspect that it doesn't work since in order to get into fastboot with the button combination i need to first get the device turned off. But when i connect my device to the charger it shows the battery charging screen and the device is stuck on that screen even if it has disconnected from the charger, and it will keep on that screen until the battery has depleted. I have tried shutting it down using the power button but then my phone gets into a loop with the cyanogenmod loading screen, and even if i turn it off it restarts instead.
p.s I have used to think that my fastboot was deleted but on an other thread i have been told that as long as i see the cyanogenmod loading screen of the OS that means i have a boot-loader.
Please help!
I want to get into Fastboot on my Moto Pure.
Thanks a lot
Eden.
Power down 1st
Try volume down & power key together. That will get you into fastboot directly.
Oops just seen that, my bad, I wont respond anymore.
Sent from my Portable
PassatSport15 said:
Power down 1st
Try volume down & power key together. That will get you into fastboot directly.
Oops just seen that, my bad, I wont respond anymore.
Sent from my Portable
Click to expand...
Click to collapse
Haha, as said. can't power off.
Np thanks for responding!
Anyone got an idea?
u cant poweroff does that means your phone is continuously bootlooping or its just booting but takes a hell lotta time to boot up?
Sagar_1401 said:
u cant poweroff does that means your phone is continuously bootlooping or its just booting but takes a hell lotta time to boot up?
Click to expand...
Click to collapse
I think @edenah is saying it just gets stuck at the loading screen. If the battery discharges all the way and the device is plugged in, the battery symbol shows and after the charger is unplugged, the battery charging doesn't go away until the battery dies again or the power button is pressed (which leaves us right back to where we started)
edenah said:
Hello i have recently tried to return my phone from cyanogenmod into the stock rom using this thread: "https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110" and my phone got stuck in the process while making the command "fastboot flash bootloader bootloader.img". And now my device is stuck on boot loop showing the cyanogenmod loading screen.
Anyway now i found a way to get to stock but for that i need to get my device into fastboot. THE PROBLEM IS that my device can't get now into fastboot! i have tried using adb commands but the adb doesn't recognize the device. I have tried fastboot commands but again it doesn't recognize the device. I also tried button combinations, but it didn't work.
Until the incidence i have used to press the power button+ vol down keys to get into fastboot mode, but now it doesn't work. I suspect that it doesn't work since in order to get into fastboot with the button combination i need to first get the device turned off. But when i connect my device to the charger it shows the battery charging screen and the device is stuck on that screen even if it has disconnected from the charger, and it will keep on that screen until the battery has depleted. I have tried shutting it down using the power button but then my phone gets into a loop with the cyanogenmod loading screen, and even if i turn it off it restarts instead.
Click to expand...
Click to collapse
Try this:
Hold power button for 10-20 sek, when screen will turn off hold only vol-(at bootloop screen).
You should flash stock without "oem" commands.
Find how to update bootloader​.
aybarrap1 said:
I think @edenah is saying it just gets stuck at the loading screen. If the battery discharges all the way and the device is plugged in, the battery symbol shows and after the charger is unplugged, the battery charging doesn't go away until the battery dies again or the power button is pressed (which leaves us right back to where we started)
Click to expand...
Click to collapse
Yes thats exactly what i mean.
dzidexx said:
Try this:
Hold power button for 10-20 sek, when screen will turn off hold only vol-(at bootloop screen).
You should flash stock without "oem" commands.
Find how to update bootloader​.
Click to expand...
Click to collapse
tried this, but the device still goes into the cyanogenmod loading screen.
its soft brick but can't be fixed (just thinking any method but no idea man)
get your phone to moto service centre and they can only fix it (or maybe not) caus this is worst case happening to you
if any pro dev read this thread he might be able to answer but badluck (nobody gives a ....)
btw when you connect your phone to pc does it shows unknown device or it just charge the phone?
Sagar_1401 said:
its soft brick but can't be fixed (just thinking any method but no idea man)
get your phone to moto service centre and they can only fix it (or maybe not) caus this is worst case happening to you
if any pro dev read this thread he might be able to answer but badluck (nobody gives a ....)
btw when you connect your phone to pc does it shows unknown device or it just charge the phone?
Click to expand...
Click to collapse
:/
It recognizes it as portable usb device.
And well. I have bought the device in the us but i live outside of the US. so its bit problematic to return it now. Some help could do the trick!
I found SP flash tool and i believe it would do the trick. But i need to get the scatter loading file of the moto pure, but i can't find it anywhere, maybe anyone got the idea how to get that?
edenah said:
:/
It recognizes it as portable usb device.
And well. I have bought the device in the us but i live outside of the US. so its bit problematic to return it now. Some help could do the trick!
I found SP flash tool and i believe it would do the trick. But i need to get the scatter loading file of the moto pure, but i can't find it anywhere, maybe anyone got the idea how to get that?
Click to expand...
Click to collapse
We haven't been able to get the QLoad files for most Moto devices, at least not for the last 2-3 years... Sorry.
Well i have found a way to get the device charged while the screen is off!
If i connect it to my computer while pressing the power button and the vol down button and keep pressing it, the device stays turned off!
Now i'm trying to play with it, to turn the bootloader. so far the classical power and vol combo doesn't work.
edenah said:
Well i have found a way to get the device charged while the screen is off!
If i connect it to my computer while pressing the power button and the vol down button and keep pressing it, the device stays turned off!
Now i'm trying to play with it, to turn the bootloader. so far the classical power and vol combo doesn't work.
Click to expand...
Click to collapse
I am stuck. No button combination works. I suspect that the device isn't really off but the display is just closed. As even to open up the device takes a reallly long press on the power button.
if it got interrupted while flashing bootloader, you're pretty much not going to be able to do anything.
motorola service center is likely the only place that can fix it.
sorry for your luck.
edenah said:
Haha, as said. can't power off.
Np thanks for responding!
Anyone got an idea?
Click to expand...
Click to collapse
ericpeacock79 said:
if it got interrupted while flashing bootloader, you're pretty much not going to be able to do anything.
motorola service center is likely the only place that can fix it.
sorry for your luck.
Click to expand...
Click to collapse
exactly that's what I'm saying but he needs to get his phone to USA as he specified..
only a specialist can help ya
Sagar_1401 said:
exactly that's what I'm saying but he needs to get his phone to USA as he specified..
only a specialist can help ya
Click to expand...
Click to collapse
i see :'(
Ok Thank your guys
I guess its a lost cause.
edenah said:
i see :'(
Ok Thank your guys
I guess its a lost cause.
Click to expand...
Click to collapse
Lost cause? No, probably not... Do you know anyone in the US you trust well enough to receive the phone from repair and ship it to you where ever you are? I believe that is all you need. The US service center cannot ship outside of North America (maybe US), but they can receive packages from anywhere. If you had a US contact that could receive the device and forward it on to you it might be worth it to get it fixed if it is still under warranty, if it isn't, then it might not be worth fixing. Lots of things to consider here.

Bricked Le Pro 3 727 (Blue Screen of Death)

Hello friends,
My LeEco Le Pro3 (727) bricked two days ago and I haven't had any luck turning it back on. It was running LineageOS 8.1 latest official build with an unlocked bootloader, Magisk 16.0, TWRP 3.2.1, and OpenGapps ARM64 8.1 nano. Immediately prior to bricking I was setting it up for bluetooth with my car and was trying to run Google Maps through voice command. As I directed Google Maps to take me to a location, the phone froze, the screen got all "fuzzy" and I got the dreaded blue screen of death.
From that point on I have not been able to turn the phone back on. When I press the power button it will vibrate every 5-10 seconds as though it will turn on but it never does. Ive tried everything I can think of to get to work again including:
- Pressing power button for 2 min, 5 mins, 10 mins
- Pressing power button + vol up (recovery) for 2 min, 5 mins, 10 mins
- Pressing power button + vol down (fastboot) for 2 min, 5 mins, 10 mins
- Pressing power button + vol up + vol down (QFIL MODE) -> Installing Qualcomm driver, downloading "FlashOne2.0", flashing all versions of "qfil files" that I could find but still unable to boot up
- Pressing all different button combinations while plugged in to computer/charger
- Using different cords/chargers/usb ports
- Leaving it to charge overnight/full day then trying to boot up
- Leaving it sitting not charging for a full day then trying to boot up
At this point I'm starting to think it might be a hardware issue but who knows..
Any advice/suggestions would be greatly appreciated.
Thank you.
Where did you buy it from.
I don't have much to add here it seems like you have done everything that you could
Let's clear this up no fashboot right.
Only one thing to try hold power down then plug in USB.
Sent from my LEX727 using xda premium
My one did the same, the issue was motherboard. You should send it back to repair.
mchlbenner said:
Where did you buy it from.
I don't have much to add here it seems like you have done everything that you could
Let's clear this up no fashboot right.
Only one thing to try hold power down then plug in USB.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Thank you for the reply.
It was purchased from a local retailer here in the United States through Google Express. Fortunately I should still be able to return it for a full refund but I would rather have a working phone than my money back.
No flashboot either. It's like the phone just decided to quit working one day. Tried holding power while plugging in USB as well and no change.
marik1 said:
My one did the same, the issue was motherboard. You should send it back to repair.
Click to expand...
Click to collapse
The conclusion I'm reaching at this point too. I'll see what the return policy.
Well if it will not turn on it is hardware issue you should be able to return it.
Sent from my LEX727 using xda premium
That is so strange. The screen going fuzzy like that is indicative of a hardware issue, IMO. I saw that on my laptop once, but that was because I hit the screen too hard. Never seen a BSOD on an Android device before. TIL.
I assume you've already tried an adb logcat. Were you using the original LeEco cable? I heard it has issues since it's not up to spec. 99% hardware failure, but I can't help but think it has something to do with driver communication confusing the device and causing hardware failure (?) if that's even possible.
Just a final update for those curious.
After leaving the phone alone for two days I plugged it into the charger and low and behold it started vibrating and booted up by itself. It was running a Chinese developers editions 720 rom due to the QFIL File I had flashed in my earlier in my attempt to fix it. Battery was drained so I let it charge for a while and everything was fine until I attempted to restart the phone. As the boot animation was loading, I got the blue screen of death for a second time.
I took a quick picture, the phone shut off itself off, and same as before it wouldn't boot again. As other users have suggested it appears to be a hardware issue, likely with the motherboard. Fortunately I was still able to return the phone (purchased through Google Express via a local retailer) and received a full refund. I've since bought another Le Pro3 (727) and hopefully when that one comes in, it won't have any issues.
Thanks to all the users who left suggestions/tips.
shyboi122 said:
Just a final update for those curious.
I've since bought another Le Pro3 (727) and hopefully when that one comes in, it won't have any issues.
Thanks to all the users who left suggestions/tips.
Click to expand...
Click to collapse
You bought the same phone again? :good: You're courageous, lol.
i been experiencing the exact problem like your on my x720, as i boot up the system or enterting the recovery mode the screen go fuzzy on loading screen and shut itself off completly, i can still able access fastboot. As i left it for a while the phone will be able to almost finish the boot then ending it all with a blue screen.
Have anyone found a way to fix this DIY since my phone has past the guarantee plan ?

Categories

Resources