Galaxy Nexus freeze after unlock **UNROOTED** troubleshooting - Samsung Galaxy Nexus

Alright, so here is what's going on.
I had my alarm go off earlier today, got up, unplugged my phone like normal. I swiped off the notifications I didn't care about like a tapatalk message etc. I noticed that Google Current's automatically updated. I'm sure that's no huge deal.
I locked the screen and went about my day. I tried to swipe to unlock, and the phone freezes and reboots. The phone is responsive until you unlock it, then it just freezes and reboots.
Tried safe mode once, and it worked fine. I then turned it off, and tried normally booting again, same freezing and rebooting. So I went to go back to safe mode, and now safe mode is doing the same thing, which means that a factory reset is now out of the question.
What the hell man.
Specs:
- Samsung Galaxy Nexus
- All stock apps except added Facebook and Tapatalk
- Jellybean 4.2.2 software I believe. I'd double check if I could.
- Still locked and unrooted
Any ideas on where to go from here? No warranty, so any ideas would help
It turns on, goes to lock screen. Then freezes when I try to get anywhere from that lock screen. Even on safe mode.
Then it will reboot automatically after about 30 seconds.
I should note I received a text in this time, and thought maybe just pulling the notification bar down and going straight to the text would work. The notification bar works, but when I hit the text, it froze the same way.
This must be some sort of self check or some Android process crashing. But I can't utilize safe mode to fix it.
Any ideas on what to do? I know there are threads with this problem, but this involves an unrooted phone, of which I have seen no threads, or threads with answers. I am not experienced with getting too far into Android, so just a direction to go, or something to try when I get home would be awesome. (At work currently)
The only options I have right now are the options upon booting with the volume down, which are Start - Restart bootloader - Recovery Mode and Turn off. In this screen, here is my info:
FASTBOOT MODE
PRODUCT NAME - tuna
VARIANT - maguro 16GB
HW VERSION - 9
BOOTLOADER VERSION - PRIMELA03
BASEBAND VERSION I9250UGLL1
CARRIER INFO - NONE
SERIAL NUMBER - xxxxxxx
SIGNING - production
LOCK STATE - LOCKED
In recovery mode, I see a dead android guy with a red triangle and an exclamation mark in it.
I realize you guys probably get a lot of dumb questions so I tried unloading all the information I could. My replies will be 5 minutes apart, as I'm new and I see that's a restriction on being here.
Thanks in advance

You can try unlock the bootloader (it'll erase your data so be careful) and then try flashing the oficial google image via fastboot and see if it solves it.
EDIT: in that screen of red triangle press up and power at the same time to show the options. There you can do a factory reset to see if it solves it. No need to unlock the bootloader that way.

Daedalus93 said:
You can try unlock the bootloader (it'll erase your data so be careful) and then try flashing the oficial google image via fastboot and see if it solves it.
EDIT: in that screen of red triangle press up and power at the same time to show the options. There you can do a factory reset to see if it solves it. No need to unlock the bootloader that way.
Click to expand...
Click to collapse
Got it. It works now, but curious, is this a common occurrance? I have no idea what caused it, which worries me. But it seems to be working fine.
Wasn't worried about data loss, I haven't had the phone for too long yet. I plan on just installing the minimum apps. The point of me not unlocking it was to avoid issues, but I had more luck with unlocking it than leaving it locked.
That said, I wasn't aware you had to hold the vol up and power button to get to the options from the dead Android screen. That was an oversight on my part when I was looking up for data.
Words cannot explain how thankful I am, so thank you
Moderators can close this thread if needed.

slipstreamconversion said:
Got it. It works now, but curious, is this a common occurrance? I have no idea what caused it, which worries me. But it seems to be working fine.
Wasn't worried about data loss, I haven't had the phone for too long yet. I plan on just installing the minimum apps. The point of me not unlocking it was to avoid issues, but I had more luck with unlocking it than leaving it locked.
That said, I wasn't aware you had to hold the vol up and power button to get to the options from the dead Android screen. That was an oversight on my part when I was looking up for data.
Words cannot explain how thankful I am, so thank you
Moderators can close this thread if needed.
Click to expand...
Click to collapse
No problem everything should work as intended now. What happened was a bit strange indeed. It it happens again with everything in stock then there is a possibility that it is faulty hardware and you should replace it. Maybe it was some configuration bug and nothing extreme

Daedalus93 said:
No problem everything should work as intended now. What happened was a bit strange indeed. It it happens again with everything in stock then there is a possibility that it is faulty hardware and you should replace it. Maybe it was some configuration bug and nothing extreme
Click to expand...
Click to collapse
Fauly hardware can cause this issue? I baby this phone, has yet to be dropped (let's admit, it's inevitable), the only thing it's seen is three drops of water that fell off my sunroof onto it. I immediately grabbed my phone and wiped it off, but it was all on the screen, not in the speaker or anything.
Either way, I'll keep an eye on it. Thanks again

slipstreamconversion said:
Fauly hardware can cause this issue? I baby this phone, has yet to be dropped (let's admit, it's inevitable), the only thing it's seen is three drops of water that fell off my sunroof onto it. I immediately grabbed my phone and wiped it off, but it was all on the screen, not in the speaker or anything.
Either way, I'll keep an eye on it. Thanks again
Click to expand...
Click to collapse
Yes. My phone recently was stuck on a bootloop and I've already sent it for repair. Yeah drops are never good
No problem

Related

HTC One X Update Gone Bad. HELP

Hi there, this is my first post, i didnt want it to be like this but i have come to you in desperation.
I was excited about 4 hours ago to realise my phone was getting an update saying it was going to imporve battery life etc..
Well i let it do its thing while it was downloading, i went to check after an hour or so and it said the software had been corrupted or something along those lines, either way it had to start the download again.
It was about bed time when this happened so i chucked it on the charger, fell asleep, woke up and it was doing something on a kind of screen i had never seen before, black screen, obviously showing that it is processing the update(i was a little tired from waking up) i think i remember taking its time maybe longer than it should have been.
I went back to sleep woke up about an hour ago from now and checked my phone and the screen would not turn on, i think the charger cable had fallen out from the phone because it is loose and does that some times.
So i placed the cord back in and it didnt seem to respond with the red led coming up for a while then all of a sudden it worked for some reason, but was flashing. i suspected this was because the battery had been sucked dry. So after a while the led stopped flashing and i pressed the power button, sure enough it powers up straight away to the HTC - quietly brilliant screen. And thats that, end of story. It's stuck on that screen WTF?
I have been through forums like these interested in changing ROMs and so on but it all seems so complicated i never even bothered, so obviously i am a noob, but i dont think there is any reason for this to happen other than sh*t luck.
Can anyone help us out?
Your better off sending for repair unless you want to start unlocking the bootloader etc.
Reboot your phone in bootloader ( press PowerButton + Volume down at the same time) you will get to a screen with various lines, look factory reset, navigate that menu with your volume keys. Hit factory reset you should get . See if it fixes it.
masucu said:
Reboot your phone in bootloader ( press PowerButton + Volume down at the same time) you will get to a screen with various lines, look factory reset, navigate that menu with your volume keys. Hit factory reset you should get . See if it fixes it.
Click to expand...
Click to collapse
mercccccccccccccccccccccccccccccccci
zezo_ddd said:
mercccccccccccccccccccccccccccccccci
Click to expand...
Click to collapse
Well did it work? before you say that long thanks
Thanks for your help, unfortunately, the factory reset didnt work.
What happened when i first did it, the update screen came up like the first time but still ended up freezing on the quietly brilliant screen.
I'd be willing to unlock the bootloader, i really dont want to send the phone away for a third time. Why didnt i get the Galaxy S3!?!?!
I hate to ask, can u point me to the right thread to do that, there seems to be a few but they seem to have different purposes.
Thanks again.
helter_skelter87 said:
Thanks for your help, unfortunately, the factory reset didnt work.
What happened when i first did it, the update screen came up like the first time but still ended up freezing on the quietly brilliant screen.
I'd be willing to unlock the bootloader, i really dont want to send the phone away for a third time. Why didnt i get the Galaxy S3!?!?!
I hate to ask, can u point me to the right thread to do that, there seems to be a few but they seem to have different purposes.
Thanks again.
Click to expand...
Click to collapse
If you wait a day or so, the RUU will be released for your region now that the OTA has been released.
You'll be able to fully reload your phone - this is all HTC do when you send it for repairs and you can do it in a lot less time.
At the moment, HTC may even reload the 2.17 software so you may still have the problem again when trying to load the OTA.
Thanks all for your interest.
I spoke with customer support and they told me exactly what i already had done, factory reset through hboot.
After that was a no go, he told me i have to send it back to the point of sale, so they can flash the software?
Where can i find this ruu once it has been released?
I'm pretty sure the updates all say to not have the phone plugged in when updating.
Sent from my HTC One X using xda app-developers app

Random now permanent black screen issue

Bought this phone off the electronic bay, arrived totally fine, no signs of any damage, worked just fine. Upgraded it with the sony OTA updates to 4.1 and then the screen started acting a little funny. Sometimes when hitting the unlock button it would just light up the backlight. Then a few days later it stopped ever doing anything besides lighting up the backlight. Then it progressed to doing what I show in the video.
It still plays alert tones when i get messages or calls, but obviously the phone is totally unusable, but charges up fine.
any ideas what is going on here? Called Sony for a repair, but I was unaware they just charge a flat $185 irregardless of what the problem is...ridiculous.
foofiebeast said:
Bought this phone off the electronic bay, arrived totally fine, no signs of any damage, worked just fine. Upgraded it with the sony OTA updates to 4.1 and then the screen started acting a little funny. Sometimes when hitting the unlock button it would just light up the backlight. Then a few days later it stopped ever doing anything besides lighting up the backlight. Then it progressed to doing what I show in the video.
It still plays alert tones when i get messages or calls, but obviously the phone is totally unusable, but charges up fine.
any ideas what is going on here? Called Sony for a repair, but I was unaware they just charge a flat $185 irregardless of what the problem is...ridiculous.
Click to expand...
Click to collapse
Hi,
The best way to rule out any software problems would be to flash the latest 6.2.B.1.96 ftf using Flashtool. So, first make sure that the phone has enough charge, then press and hold the volume up+power combination until you get three vibrations. Then press and hold the volume down key and simultaneously connect the USB cable when Flashtool prompts you to. Once the flashing is complete, disconnect your phone and turn it on normally.
Regards,
abcdjdj
Sent from my LT26i using xda app-developers app
I already flashed back to stock just using the sony bridge app. It seemed to work fine (nothing showed up on the screen the entire time). After the phone boots up I can hear notification sounds as it gets all my texts and voicemails/whatever else. But otherwise it still does what is shown in the video below:
here is the video again, not sure if it worked last time:
http://www.youtube.com/watch?v=jbrpsWburMw
foofiebeast said:
I already flashed back to stock just using the sony bridge app. It seemed to work fine (nothing showed up on the screen the entire time). After the phone boots up I can hear notification sounds as it gets all my texts and voicemails/whatever else. But otherwise it still does what is shown in the video below:
here is the video again, not sure if it worked last time:
http://www.youtube.com/watch?v=jbrpsWburMw
Click to expand...
Click to collapse
What bug u reported is the bug of .200 and .211 official bug.. Its fixed in .96fw.. Wipe everything when u flash .96fw... So there won't be any problems..
sudhindrakv said:
What bug u reported is the bug of .200 and .211 official bug.. Its fixed in .96fw.. Wipe everything when u flash .96fw... So there won't be any problems..
Click to expand...
Click to collapse
Well there is a slight problem.
The phone does not have an unlocked bootloader yet, so I can't use flashtool. It has been flashed back to stock using the method I mentioned above. I have just finished installing ADB because (bear with me please) there is no way to turn the phone into fastboot mode without turning it off (I cannot currently turn it off because I can't see what is happening on the screen and don't remember how this phone works when you hold down the lock key to turn it off). I can perform a hard reset, but no way to just get it to turn off entirely.
So I thought I could use adb to shut it down, but adb won't work unless I have debugging enabled, which again I can't do unless I could basically just blindly navigate the menu to those buttons.
Although if I wait until the phone is fully dead then I can hopefully get it into fastboot mode, but that only gives me one chance. Plus it has a full charge right now, so that's going to be awhile.
Any suggestions?
I can get it in to fast boot if I'm quick, but I still can't enable debugging beforehand so its semi worthless.
I've been trying to watch videos to see where the button placement is to navigate through the menu to blindly enable debugging, but I can't seem to figure it out. It also doesn't help that I have no idea what version of android is now on the phone. I used the mac sony bridge app to restore the phone, but i'm not sure if that set it back to stock stock, or what version of android it set it to.
I am also now even more confused because I connected the phone to the computer and when I browsed it, all the pictures I took were still there...which should have been wiped when I restored it with sony bridge...
figured out it was 4.1 and watched review videos until i found one that showed the menu layout (although now I realize google images would have been more helpful).
Now going to see if I can get the bootloader unlocked.
I still feel like flashing 6.2.B.1.96 isn't going to do anything, because I assume that is what the sony bridge app flashed to it. Also I don't see where you are talking about that the issue I am having was a known issue, if you could point me in that direction that would be very helpful.
EDIT: Actually I'm not sure I enabled debugging after all, as when I do adb devices, no device is listed as running, just a blank space. Though I'm still not convinced doing the above would do anything, as it is basically what I have already done, just with flash tool as opposed to the official sony route.
Anyone have any ideas? I got a torx 6 and opened the phone, checked the connection between the motherboard and phone and it is fine. Screen is still having same issue.
I would be happy to just buy a replacement part for it, but i have no idea what part is messing up. Is it the display (the touch works fine) or is it the motherboard (it seems weird that it would be this because the phone functions completely normally, I even accidentally answered a call yesterday).
If i was to try and replace the LCD (or whatever it is) would I have to replace the digitizer as well? At which point it would make more sense to just sell the phone for parts I suppose.
You can use the flash tool by bin4ry with a locked bootloader. Not sure if you're past that stage though.
Sent from my LT26i using xda app-developers app
dkconor said:
You can use the flash tool by bin4ry with a locked bootloader. Not sure if you're past that stage though.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
I'll go ahead and try that out, but is there really much of a point do you think? Considering I've technically flashed the phone back to stock using the official software, why would it be any different doing it this way?
I am asking honestly btw, not trying to sound rude. I'm thinking it is more of a hardware failure, i just have no idea what part exactly is failing.
The phone itself works totally 100% fine, the touch works totally 100% fine, the only thing that is not happening is the data getting to the screen and displaying. The screen just flashes white for a second and then fades out (as you can see in the youtube link). Or it flashes a solid block of white at the top in the middle and faded white the rest of the way down and then it slowly all fades out (or disappears immedaitely if i press the lock button. The buttons all work fine (physical and touch) and i can navigate around the phone, albeit totally blindly.
This is really frustrating, and I'm pretty disappointed to see how sony had no interest at all in helping me resolve this situation.
Flashtool works with lock and unlocked bootloader
XDAプレミアムを使用 して私のLT28hから送ら れてきた
UchihaDareNial said:
Flashtool works with lock and unlocked bootloader
XDAプレミアムを使用 して私のLT28hから送ら れてきた
Click to expand...
Click to collapse
....right i know, but why does that matter. Why would reflashing my phone help at all at this point. Did you even read my post?
Listen to us
Alright so you came to this thread for...help
We have told you numerous times to flash using this tool (dev host link):
http://d-h.st/Kb8
install the flashtool created by Binary (sorry for username spelling error)
Download the ftf
https://docs.google.com/file/d/0B18FXPCopQhkeXNoWGVWbzlRaG8/edit?pli=1
now USING FLASHTOOL (link 1)
FLASH the FTF (link 2)
A clean flash. This flash is different from the flash that Sony will provide you for obvious reasons.
Using this method will COMPLETELY remove any doubt whether the issue is regarding software or hardware. Then you dont have to "think" whether the issue is hardware related or software related.
Sorry if i sounded rude but i had a hard time comprehending why you would not use the advice given by i believe 2 different indiviuals on a questions and answers thread.
424aca said:
Alright so you came to this thread for...help
We have told you numerous times to flash using this tool (dev host link):
http://d-h.st/Kb8
install the flashtool created by Binary (sorry for username spelling error)
Download the ftf
https://docs.google.com/file/d/0B18FXPCopQhkeXNoWGVWbzlRaG8/edit?pli=1
now USING FLASHTOOL (link 1)
FLASH the FTF (link 2)
A clean flash. This flash is different from the flash that Sony will provide you for obvious reasons.
Using this method will COMPLETELY remove any doubt whether the issue is regarding software or hardware. Then you dont have to "think" whether the issue is hardware related or software related.
Sorry if i sounded rude but i had a hard time comprehending why you would not use the advice given by i believe 2 different indiviuals on a questions and answers thread.
Click to expand...
Click to collapse
Hi,
because I could not follow the advice from the first user because the bootloader is locked. The second person gave me the advice, but honestly it seemed like pretty pointless advice. I don't understand how it is "obviously different" if it is literally flashing the same firmware (at least the first advice was that). I don't think it's that strange to ask why it would be any different.
To me it sounds like I had a broken window in my house and I asked someone how to fix it. I bought the replacement glass from store A and it didn't fit. I asked for help and someone pointed me to the exact same item at store B and said that surely it would work. Do you understand why this could be confusing? I feel like about half the time people give help on XDA it is very general and people are just looking for "thanks"...
I'll definitely try this though if you think there's a chance that it might work out differently. I'll try and get it set up tonight, thanks for the encouragement, I understand I probably sound stupid, just trying to figure out what to do.
Also, I assume this flash tool won't work if USB debugging isn't enabled. As I've said in previous posts, I can click things just fine, but because I can't see what I am doing, I don't have way of knowing where to click on the menu.
Does anyone have their phone set up with this version of android still. If you could take screen shots of each click to make to get to the dubugging box (and if there is a confirmation box) i would greatly appreciate it. I only had the phone for a week before this randomly happened, so I hadn't thought to enable debugging yet, as I hadn't even thought about custom firmware yet.
EDIT: Or even just a picture of what the screen that comes up when you long press to shut the phone down. I have no way of turning off this phone right now without just waiting for it to run out of battery.
Holding down the power button for a long time does nothing, holding vol up and power restarts it, but I need a way to turn it off. If i hold the power button for like a second so instead of locking it, the menu comes up, I just can't seem to find the freakin button for power off.
(please remember I can see nothing on the screen, it is just blank).
flashtool does not need debugging when you doing the actual flashing
to turn off the phone
SIMULTANEOUSLY hold down
Power+ Vol up + Vol Down (AT THE SAME TIME)
wait for about maybe less than 25 seconds and you will experience THREE short consecutive vibrations
at this time...the phone is off
then you can begin the flashtool method

[Q] Samsung Ace II will not turn on

Hello, new here and I know nothing about rooting nor have I rooted my phone but after looking all over the net I have come here in hopes of finding some tech wizards that can help me.
The Problem:
Turned phone off and a few hours later I tried turning it back on but it only shows the screen with model number and Samsung under it. It shows for a few seconds then the screen goes black and keeps looping like this. I have not rooted or anything. Not dropped in water ( water square is pink though). Phone shows no water damage or corrosion after opening.
What have I done?
I tried booting in recovery and download mode but i have never done it before and I was not successful at getting any other screen besides the model number Samsung screen.
I have tried a different battery after spending some time at the mall (no on carries it any more as it is no longer made) different battery did nothing. Repair guys suggested it may be the button sticking and said hey could clean it for $25. Instead I went home searched the web and disassembled my phone. I cleaned the button areas on the inside of the case and the contact on the inside attached to the circuit board. I have reassembled and it still does the same thing.
After more research I found a video saying to actually remove the internal button from the circuit board to stop the loop (which will leave me with no power button) I have not tried this as I am not that bold (yet).
I am wondering if it is a software problem that can be fixed by using Odin and installing the stock firmware but I just have not found a proper guide that makes enough sense for me to actually try. I don't want to waste my time with something I have never done and make things worse.
I have downloaded Odin and firmware from sammobile but that is about as far as I can go without some hand holding....
Thanks for reading my story any help would be much appreciated.
Fishheadman said:
Hello, new here and I know nothing about rooting nor have I rooted my phone but after looking all over the net I have come here in hopes of finding some tech wizards that can help me.
The Problem:
Turned phone off and a few hours later I tried turning it back on but it only shows the screen with model number and Samsung under it. It shows for a few seconds then the screen goes black and keeps looping like this. I have not rooted or anything. Not dropped in water ( water square is pink though). Phone shows no water damage or corrosion after opening.
What have I done?
I tried booting in recovery and download mode but i have never done it before and I was not successful at getting any other screen besides the model number Samsung screen.
I have tried a different battery after spending some time at the mall (no on carries it any more as it is no longer made) different battery did nothing. Repair guys suggested it may be the button sticking and said hey could clean it for $25. Instead I went home searched the web and disassembled my phone. I cleaned the button areas on the inside of the case and the contact on the inside attached to the circuit board. I have reassembled and it still does the same thing.
After more research I found a video saying to actually remove the internal button from the circuit board to stop the loop (which will leave me with no power button) I have not tried this as I am not that bold (yet).
I am wondering if it is a software problem that can be fixed by using Odin and installing the stock firmware but I just have not found a proper guide that makes enough sense for me to actually try. I don't want to waste my time with something I have never done and make things worse.
I have downloaded Odin and firmware from sammobile but that is about as far as I can go without some hand holding....
Thanks for reading my story any help would be much appreciated.
Click to expand...
Click to collapse
Try this - Press and hold Volume up + Home + Power buttons together a few seconds, you should get recovery mode. And then find factory reset.
garak elim said:
Try this - Press and hold Volume up + Home + Power buttons together a few seconds, you should get recovery mode. And then find factory reset.
Click to expand...
Click to collapse
Thanks for the reply. I have tried this many times and tried again after reading your reply. This should work fairly fast from what I understand right?
My phone is a virgin mobile phone (Canada) is it possible they have locked out recovery / download modes?
When I try to start in recovery nothing happens at all. Screen does not light, phone does not vibrate. Again I have never tried this until now so I don't know if the phone ever booted into these special modes when it was working.
Fishheadman said:
Thanks for the reply. I have tried this many times and tried again after reading your reply. This should work fairly fast from what I understand right?
My phone is a virgin mobile phone (Canada) is it possible they have locked out recovery / download modes?
When I try to start in recovery nothing happens at all. Screen does not light, phone does not vibrate. Again I have never tried this until now so I don't know if the phone ever booted into these special modes when it was working.
Click to expand...
Click to collapse
It's weird. I found something on page hard-reset.com. I cannot post link here now. I put "samsung ace2 recovery" into google and it was on first page. It's hard reset key combination. Try it.
When you plug the phone into the charger, do you get the battery charging status screen?
garak elim said:
It's weird. I found something on page hard-reset.com. I cannot post link here now. I put "samsung ace2 recovery" into google and it was on first page. It's hard reset key combination. Try it.
Click to expand...
Click to collapse
Forget my previous post. I was wrong. I try find another solutions.
Is your battery fully charged?

Is my 1+3 dead!?

Hi everyone,
I'm experiencing pretty silly situation with my phone.
So the story begins here:
I was surfing the web while listening to music in the bus when suddenly my oneplus3 randomly turned off and I couldn't turn it back on. (I was on something around 15% on battery so it's not a low battery problem) I tried to turn it on several times and after holding the power button for like 10secs it turned on, and after pressing the power button again (because I needed to get past unlocked bootloader screen and dm-verity) I saw a boot screen. The capacitive button leds turned on and after 3 secs it turned off again, so I started worrying... After a while I tried to access the recovery, but no luck at all. It powers it self off after bootscreen. So I started to research. Tried to flash the entire OS, partritions with msmdownload tool. After several unsuccessful flashes (firehosewritedata failed sometimes while writing userimg or system.img or boot.img) I did get the download complete green text message, and after successful flash, the white LED turned on, even the phone was not plugged in USB or charger and turned off. The screen is completely black and the white led just flashes constantly without blinking or anything. I could only turn the led off by pressing the power button for another 10 secs. And after turning the phone off, problem still remains. After oneplus logo phone shuts down...
I can access bootloader.
And after flashing everything should be on stock, because now I only got screen only about bootloader, no dm-verity..
And of course - I still cannot access the recovery.
p.s. I tried to do the power cycle (as the tech support told me) but still no luck at all.
did u tried the full msmdownload tool (1gb) or the 55mb version ?
Mukthar. said:
did u tried the full msmdownload tool (1gb) or the 55mb version ?
Click to expand...
Click to collapse
1GB version
djemm1996 said:
1GB version
Click to expand...
Click to collapse
Are you sure that you did it right? Did your phone show up as mentioned in the instructions?
Puddi_Puddin said:
Are you sure that you did it right? Did your phone show up as mentioned in the instructions?
Click to expand...
Click to collapse
Of course. Everything is done right. I also get that green "download complete" message.
p.s I also opened the phone. water indicators are fine and no major defects what can i see by eye... All connectors are good as well.
Puddi_Puddin said:
Are you sure that you did it right? Did your phone show up as mentioned in the instructions?
Click to expand...
Click to collapse
And yes, phone was connected right. :good: installed drivers with test mode on Win10 and got Snapdragon device in COM devices. As well the MsmDownload tool shows up my device in port #20
Any ideas?
djemm1996 said:
Any ideas?
Click to expand...
Click to collapse
Follow method 2 from the Hard Brick guide by Naman Bhalla and try two or three times.
Sometimes it takes more than once for restoration.
Since you opened the phone, i think your warranty is gone now.
If the msmdownloadtool didnt help you, there is nothing you can do i think.
try to flash again, and if it still maybe something short inside.
if you have disassembly your phone, try disconnecting various flex cable like camera, sim slot etc that connect to the mainboard, that doesn't prevent device from powered on, then try to turning it on.
if it still, check your mainboard, if you don't know how, send it back.
AcidNoteZ said:
Since you opened the phone, i think your warranty is gone now.
If the msmdownloadtool didnt help you, there is nothing you can do i think.
Click to expand...
Click to collapse
Is ir really gone? There is a still warranty void sticker on the screw there, but of course it's possible to see by eye that the phone has been opened.
I have an appointment with Level2 tech support @oneplus, they are going to remotely flash the entire OS, but do you think they are using pretty similar technique as the msmdownloadtool?
djemm1996 said:
Is ir really gone? There is a still warranty void sticker on the screw there, but of course it's possible to see by eye that the phone has been opened.
I have an appointment with Level2 tech support @oneplus, they are going to remotely flash the entire OS, but do you think they are using pretty similar technique as the msmdownloadtool?
Click to expand...
Click to collapse
They are doing the same thing like you did.
I already had a session since i thought they are going to do something "special"
You can try the remote session but im afraid that wont help you if you already did it multiple times.
What about battery? Charged?
drmuruga said:
What about battery? Charged?
Click to expand...
Click to collapse
Yes battery is charged of course. It's just doint the same thing. Turns on, after a while when bootscreen comes it just turns off and white notification led appears, after that nothing.
I tried to flash it with tool using method 2 for like 15 times with "download complete" messages, but still no luck at all. Tried to erase partritions with fastboot, flashing just only recovery, modded recovery etc. but I still cannot access the recovery nor system. I just don't get it why the phone does not boot into recovery if I flash it or boot it straight away, It just only turns off and that's it. nothing more. Only black screen and white led lighting all the time (after a while the phone turns warm).
I have read all the MsmDownloadTool thread in "Mega Unbrick thread" and saw that few people have experienced the very same situation as me, so I was wondering if there is any fix for this? It's so strange that I was just surfing the Web and it just turned off by it self with like static image for miliseconds and after that just black screen.
There should be any fix. I guess that it's just a partition error...
Ok, not good news. I had a little remote session before a while. They says it's already a hardware problem.
AcidNoteZ said:
Since you opened the phone, i think your warranty is gone now.
If the msmdownloadtool didnt help you, there is nothing you can do i think.
Click to expand...
Click to collapse
Pfffft you think manufacturers notice when you take apart phones? Hell I took apart my Xperia Z2 because it was having problems and then glued it back together with cyanoacrylate hahahaha (worst thing to do but wtv) and no one noticed though it was seemless and everything looked perfect
Guys, I've got something for you! Not really the same thing as Naman.
p.s. not saying its original hehehehe keep safe
man i got a very similiar problem but my op3 has a black screen i was also on low battery around 5-15% when my phone went off after i was in twrp
Actually I was on twrp too! Also I have recently noticed that recovery loading speed was far too long than normal one. I'm talking for something about 5-7 minutes after reboot into twrp. So, who knows what did happen. Just made an RMA request. Will see how it goes.
Anyway, I was on stock 7.1.1 and it's just rooted with custom recovery and that's it! Nothing more! Is that just a factory failure or maybe it's caused by drops i have had? Nothing serious for a 4-5 times for a half year. Of course I have used it even in winter when the snowflakes are coming down from the sky and little rain. Btw, these liquid indicators are white, so all safe. ::laugh:
A
makadama said:
man i got a very similiar problem but my op3 has a black screen i was also on low battery around 5-15% when my phone went off after i was in twrp
Click to expand...
Click to collapse

Lenovo P2 display black after recovering from a bootloop

Hey guys.
I am posting this particular issue because while I could find something similar to this issue (recovering from a bootloop for this very device), I couldn't find much in case your screen remained black afterwards.
I know why the bootloop took place (or at least I'm almost sure I know why):
-Via dr.fone, I chose the root option. This is a naïve move, as I know that one-click rooting options basically never work. Well, I know this now at least. However, the root never happened, as my device didn't even have OEM activated (there are some issues happening in this regard with lenovo). The program just couldn't continue, telling me that my phone wasn't registered in the data base or something like that. I was honestly just messing around because I didn't have OEM access, just wanted to see what error would pop up.
-The bootloop happened the day after, about 16 hours later. It also happened randomly, while the phone was idle without being connected to the PC. The screen was black, but I knew it was bootlooped because it would vibrate consistently every 10 seconds or so.
-If I pressed the Up+down+power buttons simultaneously, the blue LED in the top right corner would light up and a very long vibration would happen. There's a thread on this issue already, and adding a new firmware solved this.
-I tried to solve this by using ADB to add the stock firmware again. The bootloop stopped after this and the phone would charge. It didn't while bootlooping.
-I tried to factory reset and nothing happened. Except that my USB debugging option is now turned off, which makes things harder because I can't find a way to turn it on without having access to my phone.
I was wondering if there'd be a solution for this very situation. It's also worth noting that my screen is basically shattered, but I don't think it's an LCD issue because these two things happened at the same time. I find it too much of a coincidence.
Do you guys know what could be going on? I also wiped the cache data, even though my phone was factory reset just to give it a shot.
I very much appreciate your attention.
PS: this is literally only the display and the touch screen. Even the fingerprint sensor works.
Did you unlocked bootloader before root ?
Shreyash01 said:
Did you unlocked bootloader before root ?
Click to expand...
Click to collapse
No, the root didn't even take place. I tried to unlock the bootloader, but the Lenovo servers are down for that. So my bootloader is not unlocked.
I think that is the reason..
Your bootloader is not unlocked. You must have to ask someone before doing..
I think costumer care is the only option.

Categories

Resources