Related
http://androidforums.com/fascinate-all-things-root/179136-bricked-fascinate-beyond-repair.html
This is exactly what happened to a friend of mine as well. He accidentally flashed the captivate Odin3; nothing works now. The weird thing is, is when you plug up the phone now it will do nothing. It won't power on. It won't even give prompt from the computer, anything. The only way it will power up at all is having he battery in only. Can someone explain me how this might happen? Can a software flash just short out a board?
I don't know how to help you...but am wondering why do people try this?????? We know there is no recovery available...I am just speechless.... That's probably why moto locked bootloader cause of crap like this and money loss
tats_06 said:
I don't know how to help you...but am wondering why do people try this?????? We know there is no recovery available...I am just speechless.... That's probably why moto locked bootloader cause of crap like this and money loss
Click to expand...
Click to collapse
Ill on honestly he could of been looking for a way to clear the stock/angel rom, so that he could reflash to stock. Even if you reflash/wipe cache/ reformat some settings remain. For instance if you don't have debugging on and you turn the brightness off by mistake you're FUBAR'd!
Can he get to download mode (battery out! Usb connected. Volume down). If he does, there's still hope.
I actually had to flash the US Cellular kernel in order to get to the point where I could re-flash the stock kernel.
namebrandon said:
Can he get to download mode (battery out! Usb connected. Volume down). If he does, there's still hope.
I actually had to flash the US Cellular kernel in order to get to the point where I could re-flash the stock kernel.
Click to expand...
Click to collapse
Thanks NameBrandon! I knew I read that somewhere but I couldn't remember where.
josh6780 said:
The weird thing is, is when you plug up the phone now it will do nothing. It won't power on. It won't even give prompt from the computer, anything. The only way it will power up at all is having he battery in only.
Click to expand...
Click to collapse
Just to confirm then, because it sounds like you've already tried: are you positive you are unable to get into download mode?
josh6780 said:
http://androidforums.com/fascinate-all-things-root/179136-bricked-fascinate-beyond-repair.html
This is exactly what happened to a friend of mine as well. He accidentally flashed the captivate Odin3; nothing works now. The weird thing is, is when you plug up the phone now it will do nothing. It won't power on. It won't even give prompt from the computer, anything. The only way it will power up at all is having he battery in only. Can someone explain me how this might happen? Can a software flash just short out a board?
Click to expand...
Click to collapse
I have flashed the captivate rom and the i9000 rom before from odin, and was still able to get into download mode. At the time i hadnt made the odin restore files so i had no way of fixing it. The files i created in another thread should be able to get him back, as namebrandon can tell you
namebrandon said:
Can he get to download mode (battery out! Usb connected. Volume down). If he does, there's still hope.
I actually had to flash the US Cellular kernel in order to get to the point where I could re-flash the stock kernel.
Click to expand...
Click to collapse
That is what is so weird about all this. If he usb is plugged in at all the phone will not power on. It will only power on when it is using the battery.
And yes. He was trying to flash back to stock ROM bc he bricked it with a different ROM. He was under the impression that Odin would auto detect his phone.
josh6780 said:
That is what is so weird about all this. If he usb is plugged in at all the phone will not power on. It will only power on when it is using the battery.
And yes. He was trying to flash back to stock ROM bc he bricked it with a different ROM. He was under the impression that Odin would auto detect his phone.
Click to expand...
Click to collapse
If he cannot get into download mode (pull out battery, pull out sd card, put battery back in, hold ONLY the volume down key and plug into computer) then he completely bricked his phone. He might have clicked the update boot loader option in Odin, or just flashed something that he didn't know what would happen when he did.
If he takes it back to verizon, they will most likely replace it as long as he doesn't tell them he rooted it / tried flashing it.
fallingup said:
If he cannot get into download mode (pull out battery, pull out sd card, put battery back in, hold ONLY the volume down key and plug into computer) then he completely bricked his phone. He might have clicked the update boot loader option in Odin, or just flashed something that he didn't know what would happen when he did.
If he takes it back to verizon, they will most likely replace it as long as he doesn't tell them he rooted it / tried flashing it.
Click to expand...
Click to collapse
And it, you know, doesn't show the AT&T boot logo..
But yeah, if he can't get to download mode, it's done.
namebrandon said:
And it, you know, doesn't show the AT&T boot logo..
But yeah, if he can't get to download mode, it's done.
Click to expand...
Click to collapse
Well, that's the problem. He needs it not to show the ATT logo. Lol. Working on that.
josh6780 said:
Well, that's the problem. He needs it not to show the ATT logo. Lol. Working on that.
Click to expand...
Click to collapse
Microwave?
Take the battery out first. 4-5 seconds should do it. Too long and the plastic will melt.
namebrandon said:
Microwave?
Take the battery out first. 4-5 seconds should do it. Too long and the plastic will melt.
Click to expand...
Click to collapse
um. how about that is a horrible idea. i just kicked you on irc for even suggesting that.
If you cant get into download mode, you could always splice a micro usb cable into a surge protected outlet and burn out the board...
I AM NOT RESPONSIBLE FOR WHAT YOU DO TO YOUR PHONE. HOUSE. CAR. DOG. ANYTHING. YOU DO ANYTHING ON YOUR OWN!
fallingup said:
um. how about that is a horrible idea. i just kicked you on irc for even suggesting that.
If you cant get into download mode, you could always splice a micro usb cable into a surge protected outlet and burn out the board...
I AM NOT RESPONSIBLE FOR WHAT YOU DO TO YOUR PHONE. HOUSE. CAR. DOG. ANYTHING. YOU DO ANYTHING ON YOUR OWN!
Click to expand...
Click to collapse
We're to the point of trying to figure out how to completely destroy a phone so it won't boot. I don't think burning out the board is much more of a risk than a microwave for 4-5 seconds. What if his cable lights on fire, then his carpet, etc..
It's a stupid point to argue.
fallingup said:
um. how about that is a horrible idea. i just kicked you on irc for even suggesting that.
If you cant get into download mode, you could always splice a micro usb cable into a surge protected outlet and burn out the board...
I AM NOT RESPONSIBLE FOR WHAT YOU DO TO YOUR PHONE. HOUSE. CAR. DOG. ANYTHING. YOU DO ANYTHING ON YOUR OWN!
Click to expand...
Click to collapse
Well thanks for trying to help but I just took the phone apart, pulled the AMOLED cable and put it back together.
josh6780 said:
Well thanks for trying to help but I just took the phone apart, pulled the AMOLED cable and put it back together.
Click to expand...
Click to collapse
lol.. or you could do that. Nice work.
Love this thread.
That's not how you break a phone, THIS is how you break a phone.
No no no, you're breaking it wrong!
I should take it to AT&T and ask them to activate it. "sir, this is a Verizon phone"
"no it's not"
"yes, it is."
"look you idiot, it as your effing name comes up when you turn it on"
":/"
Got this phone from a friend. She already upgraded to iPhone so this is like a trash or free phone (I will take maximum risk to fix it). There was some moisture under the LCD glass. Put it in a bag of rice for 4 days while the new battery was on its way. That seemed to fix the moisture under the glass, so I'm assuming it fixed any other moisture.
I can get to bootloader (30.04) and the SBF using RSDLite (tried 5.3 and 5.5) appears to go through just fine. Have tried 602.sbf, VRZ_MB810_2.3.32_1FF_01.sbf, and VRZ_MB810_2.3.34_1FF_01.sbf.
Stuck on red M logo. Have tried different ways to get into recovery like holding down Home key or holding down camera key. Nothing I do can get it into recovery so I can wipe and get past this red M.
Should I try some other method I've heard of with Ubuntu and some SBF-flash application?
Hold power and home key until it goes to bootloader, do a wipe data/cache of factory restore.
FluffyMittens said:
Hold power and home key until it goes to bootloader, do a wipe data/cache of factory restore.
Click to expand...
Click to collapse
I think you've got your terminology mixed up. Bootloader is the mode that comes up by pressing both volume keys while powering on. This is where you flash stuff through RSDLite or use adb server to push and do hacker stuff.
Recovery is the phase where you can do factory wipes and data formatting. I can't get into recovery.
When you flash an SBF, it should be flashing a new recovery. I think the phone is hosed.
If wiping data doesn't help, do an SBF
Sent from my DROIDX using XDA App
infazzdar said:
If wiping data doesn't help, do an SBF
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
You've got to be ****ing kidding me.
Haha, I'm sorry, my kid was crawling all over me when I was writing that. What have you done so far?
Edit: Possibly try this, same thing just through ADB.
adb shell
su
format SYSTEM
format DATA
format CACHE
Click to expand...
Click to collapse
FluffyMittens said:
Haha, I'm sorry, my kid was crawling all over me when I was writing that. What have you done so far?
Edit: Possibly try this, same thing just through ADB.
adb shell
su
format SYSTEM
format DATA
format CACHE
Click to expand...
Click to collapse
ADB isn't working. I don't think ADB works in bootloader.
You ask me what I have done so far, but I already put all that information in the OP. That is why I was so frustrated with that second guy. If you guys would take time and not skim over my post that I actually thought out and typed ****, you wouldn't have to waste your time asking me what I have done.
I appreciate the ADB suggestion.
Just trying to collect some information. I'm someone that doesn't let a phone just be deemed as bricked. How charged is the battery?
-Edit: Just checked, ADB doesn't work in bootloader. Confirmed by having RSD open and making sure it sees it, and then tried adb devices. Also as a supporting confirmation for the fun of it, ran the one click root.
-Edit: Further thinking about it, was this phone submerged in water or just had moisture in there? There could just be some minerals formed up on the board that a toothbrush would get rid of. I've fixed phones a dozen times. Some phones will turn on and get stuck. Some wont turn on. Some the backlight comes on but no video signal.
Deoxit
My guess is that the buttons aren't working. There's no way to test that since you can only get to the bootloader, but if you can successfully SBF the phone the odds of any of the solid state gear being bad are pretty low. It does seem odd though that you can't make it to the boot animation and get stuck at the boot logo.
I would suggest getting some deoxit (tv tuner cleaner) and spraying it in around the hardkeys on the bottom of the phone. You don't need too much (especially since it might end up behind the screen). Spray that in there and then work the buttons a few dozen times. That should loosen up any corrosion on the switches and let them close the circuit again. If that doesn't do it, I'm out of ideas, but at least you'll have some deoxit lying around (stuff is great for static-y radio/stereo volume control knobs, etc).
The battery is pretty well charged. When I got it in the mail, there was no charge. I cut a USB cable and hooked it up to power. After about 2 minutes, I tried it. It got to bootloader but said battery was too low. I used the cut USB cable and hooked it around the battery pins in the phone and put the battery in, so it charged it at the same time it was tricking the phone into thinking the battery was full.
Also, if you go into Bootloader and then power off the phone, the green LED comes on. I'm assuming that means it's charging? I was skeptical since all we hear is that you're ****ed if your battery runs out at this stage of the game. It was off this morning and had been plugged in with the green LED all night (no USB cable hack).
As for trying adb while RSDLite is open, no go. adb devices shows blank. Motorola OneClick root didn't work either. It just sat there waiting for my phone. I didn't have the balls to plug in my Bionic to see if Motorola OneClick would work (and therefore the problem is with the Droid X).
As for the water damage, who knows. The lady I got it from was surprised when I told her there was moisture under the screen. I'm not her mommy so she didn't have any reason to withhold information from me. I just thought a bag of rice, a $12 battery off Newegg (free shipping, too), might just get me a sellable Droid X out of the deal.
As for the hardware buttons - they feel like they're clicking, but I know that obviously isn't the 100% test whether they're functioning properly or not. The volume buttons and power button obviously do function, since I can use those to get into BL.
Another brain jog idea: Is there an SBF out there that wipes the data and cache, along with all the other **** it puts on? This probably won't work because I still should be able to get into Recovery - something is FUBAR.
Please give up if you feel like giving up. Bricks exist. This may very well be one of them.
P.S. The girl that gave me this dropped her new iPhone 3 days into ownership. It only cracked the back glass, but the point still remains: she may not be the most graceful phone owner on the planet. Who knows what this DX has been through.
Thanks for all your help, guys.
I would try cracking that thing open and seeing if there are any mineral deposits and cleaning them. This means those weird clips and stuff too, just take a toothbrush to the whole thing and see where that gets you.
As with giving up, I'm a pretty bored guy and finding something to do is better then sitting around and watching Star Trek.
I haven't lost a phone once
Edit: Except for this [email protected]*% of an ACN voip phone that I buffer overflowed in attempt to gain root.. That ended badly.
Same problem
I had the same problem with my dx trying to sbf to .602 I ended up flashing the stock stock froyo sbf and upgrading to gingerbread by rooting and flashing CM7 or any other gingerbread rom. You didn't specify whether or not you tried froyo sbf. No idea if this will work for you but its worth a shot if you haven't already tried it. I also had to use RSD lite 4.9 or 4.8 to get the sbf file to work right.
I'd like to toss my problem into this thread if it's alright. The OP is the closest description to my situation I've read. A co-worker brought his phone to me and it would only get to the round red logo and stop there. No bootloop just a freeze at the red logo.
I tried different ways to get to recovery but was only able to get it to the white bootloader screen. (30.04) So I flashed .340 using RSD and it completes and tells me to manually start the phone. But the phone is already at a white logo (not a red one). I do a battery pull to restart the phone and I still can't get the phone to a recovery by holding down home or any other key while powering on. Battery charge is near full.
The owners explanation of how the phone got this way is that he woke up one morning and there was a 'protection mode' transparency on the screen so he rebooted and had the red logo from then on.
So, I can RSD flash just fine but the phone won't get past the black screen with the white and black M logo.
I would try flashing other files or even the Linux CD option but I can't find anything downloadable since mega got shut down.
Any advice would be appreciated.
Flash the latest rom (Gingerbread, .605) and the red logo will appear. Then, assuming it gets to the droid x loading eye, battery pull and enter recovery.
You can enter recovery by holding power and home, then, once the red/white M shows up, release the power button. Once the triangle appears, press the vol. up and down buttons simultaneously. If that doesn't work, press a bunch of random buttons until the recovery screen comes up. I'm not kidding, it works.
From this menu, scroll with the volume keys, and select with the power button. Wipe data/factory reset, then wipe cache partition. Reboot, and you should be good to go.
NType3 said:
Flash the latest rom (Gingerbread, .605) and the red logo will appear. Then, assuming it gets to the droid x loading eye, battery pull and enter recovery.
You can enter recovery by holding power and home, then, once the red/white M shows up, release the power button. Once the triangle appears, press the vol. up and down together gets buttons simultaneously. If that doesn't work, press a bunch of random buttons until the recovery screen comes up. I'm not kidding, it works.
From this menu, scroll with the volume keys, and select with the power button. Wipe data/factory reset, then wipe cache partition. Reboot, and you should be good to go.
Click to expand...
Click to collapse
1. Would be happy to try .602. Do you know of a working link?
2. It never gets to the eye.
Edit... I found a 602 iso to make a CD boot disk from and used that. The install went perfect but the phone still just boots to a red M logo and freezes there. It doesn't get to the red eye and no button press combo can get it to the recovery screen. I can only get it to the bootloader or let it go to the red logo. The buttons don't feel sticky or anything and the batt is fully charged.
The Fix
Skyroket said:
Got this phone from a friend. She already upgraded to iPhone so this is like a trash or free phone (I will take maximum risk to fix it). There was some moisture under the LCD glass. Put it in a bag of rice for 4 days while the new battery was on its way. That seemed to fix the moisture under the glass, so I'm assuming it fixed any other moisture.
I can get to bootloader (30.04) and the SBF using RSDLite (tried 5.3 and 5.5) appears to go through just fine. Have tried 602.sbf, VRZ_MB810_2.3.32_1FF_01.sbf, and VRZ_MB810_2.3.34_1FF_01.sbf.
Stuck on red M logo. Have tried different ways to get into recovery like holding down Home key or holding down camera key. Nothing I do can get it into recovery so I can wipe and get past this red M.
Should I try some other method I've heard of with Ubuntu and some SBF-flash application?
Click to expand...
Click to collapse
This will have all sbf working files and linux operating systems along with everything you will need try to sbf one of those preff linux. If this doesn't work and your still stuck! Go to this web page you will need.
Motorola Droid X Motherboard Flex Cable Replacement
Motorola Droid X Keypad Flex Cable Replacement
http://www.repairsuniverse.com/motorola-droid-x-replacement-screens-repair-parts.html
Finally here is how you take it apart with out damaging it.
http://www.youtube.com/watch?v=wo7dXyJhL1U
GL to you enjoy your droid x once ya get it working!
I always have to sbf my dx twice, I always boot loop the first time.
Just fyi, if you bootloop after an sbf, you can pull the battery, boot into stock recovery with the usual key combo format data and you'll be all set: no more bootlooping (or double sbfing!)
So first some back-story, I'll get right into it. I recently dropped my phone in some water. As soon as possible I dried off the outside, and let it sit. That was the only thing I could do at the time, I had no rice, no tools to open up the phone, anything. I ended up with a solid red light, and everything unresponsive.
The next day I got some tools to open her up. There was pretty extensive corrosion to the motherboard, so using some alcohol I cleaned it all off, rinsed it, and let it dry. I also took apart everything else and cleaned any corrosion. The inside looks brand new. However, this isn't the point of the thread.
It appeared my cleaning helped quite a bit. Upon re-assembling and plugging in, I immediately got a charging sign on the phone. However, after trying to power on, I got no response. Additionally, The charging signal went out after about 20 seconds, and the whole phone became unresponsive again. I can do this process as many times as I want, but the same thing happens every time.
So I tried a different approach. First I hold down both volume rockers plus the power button, and plug it in while holding them down. This puts the phone into "download mode" However, once in download mode the phone is, again, unresponsive. After plugging into my laptop, my computer recognizes the phone, but not as "Nexus 4," but as "Full JellyBean on Mako."
Is there anything I can do about this? I've heard about drivers being able to be installed when in download mode, but I would not know what these are, where to get them, or how to install them. I really don't mind if my phone never works 100% again, I doubt it would. I just want to be able to get into the storage so I can recover some of the files I lost.
It's also probably worth mentioning I have not gotten a solid red light after the clean. Once in a while I will get a blinking red light after plugging it in, but after less than a minute it stops and goes through the charging/stop charging phase I'm so familiar with. Any help at all would be appreciated, and thanks in advance.
The charging block and/or battery could be wrecked, for safety reasons and because it will probably become faulty soon you should change the battery anyway. If the charging block is broken flashing your phone could fail. It's also possible the board was irreparably damaged, but it's probably worth a try as the parts aren't too expensive.
DrFredPhD said:
The charging block and/or battery could be wrecked, for safety reasons and because it will probably become faulty soon you should change the battery anyway. If the charging block is broken flashing your phone could fail. It's also possible the board was irreparably damaged, but it's probably worth a try as the parts aren't too expensive.
Click to expand...
Click to collapse
After trying to figure more things out, I kept it plugged in for a while. It appears my battery actually holds at least a pretty good charge, as the indicator is full when I plug it in now. However, I don't know what you mean when you say charging block.
Also, I seemed to determine my power button isn't working either. I always thought no response to pushing it meant there was something else going on, but I am able to put it into "download mode" by just holding down the volume rockers and plugging it in. Is there a way to turn on the phone another way besides the power button? Also if not, will buying another power button fix the problem? I don't want to buy one then later figure out the reason it wasn't turning on was just a board problem, and not a problem with the button itself.
You can short the power button with a screwdriver or something should turn the phone on., By charging block I mean the secondary board that the micro usb port is a part of, it can be replaced fairly easily if necessary.
26694484 100
DrFredPhD said:
You can short the power button with a screwdriver or something should turn the phone on., By charging block I mean the secondary board that the micro usb port is a part of, it can be replaced fairly easily if necessary.
Click to expand...
Click to collapse
With a screwdriver? Enlighten me, I'd have no idea how to do that. If I had a faulty charging block, then my phone wouldn't be able to charge correct? My phone was plugged in for a while in download mode, and it gained a full charge from a relatively low charge. I also took the block apart and cleaned any corrosion, so I think that's still functional.
Some more progress, upon further attempting to turn the phone on, I was able to get it into fastboot mode. When plugging into the computer it is recognized, but as just "Android." I will type out what information is displayed here, minus serial number, as a new member cannot submit links in posts apparently.
FASTBOOT MODE
PRODUCT_NAME - mako
VARIENT - mako 8GB
HW VERSION - rev_11
BOOTLOADER VERSION - MAK0230d
BASEBAND VERSION - M9615A-CEFWMAZM-2.0.1700.98
CARRIER INFO - None
SERIAL NUMBER -
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - locked
Also, fastboot at the top (as far as I know) usually says "Start" or "Recovery Mode," but mine says "Restart bootloader." When I try switching with my volume buttons, nothing happens.
Another update, just in case anyone is still listening..
Str1ngcheese said:
Also, fastboot at the top (as far as I know) usually says "Start" or "Recovery Mode," but mine says "Restart bootloader." When I try switching with my volume buttons, nothing happens.
Click to expand...
Click to collapse
This no longer applies, for some reason I am able to switch through all modes, incliding "Start, Power Off, Recovery Mode, and Restart bootloader."
Str1ngcheese said:
Another update, just in case anyone is still listening..
This no longer applies, for some reason I am able to switch through all modes, incliding "Start, Power Off, Recovery Mode, and Restart bootloader."
Click to expand...
Click to collapse
Now that you're at this point, have you attempted to flash the phone with a stock image? I'd be weary of what the other poster said though and ensure your USB connection is holding steady because you don't want it dying half way through a flash because then you'll have a brick.
Monotoko said:
Now that you're at this point, have you attempted to flash the phone with a stock image? I'd be weary of what the other poster said though and ensure your USB connection is holding steady because you don't want it dying half way through a flash because then you'll have a brick.
Click to expand...
Click to collapse
I have tried actually. I used the Nexus Root Toolkit v1.8.0 to try and flash it. At first it wouldn't find the device, but through device manager I manually installed the usb_driver onto the phone. After this, the toolkit was able to find the phone. I attempted to flash the image, but it ended up staying in fastboot mode. The program then suggested I try to enable "force flash," which I did, and this time it was never able to finish because the phone tried to restart, but went through that "charging to unresponsive" state I described in my first post.
Upon trying to flash it normally again, it looks like maybe the phone has to be unlocked to do this properly? I then tried to unlock with the same program, but in order to do that, I need the power button to confirm I actually want to unlock the phone. So yet again, I need that power button working.
Any ideas/suggestions/solutions would be amazing.
Jellybean on mako means that your phone is in lgnpst/qcpnst mode. Looks like something failed to start and made the bootloader trogger that mode
Sent from my Nexus 4 using xda app-developers app
opssemnik said:
Jellybean on mako means that your phone is in lgnpst/qcpnst mode. Looks like something failed to start and made the bootloader trogger that mode
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Soo, any suggestions?
Str1ngcheese said:
Soo, any suggestions?
Click to expand...
Click to collapse
clean all the contacts with alcohol (not the normal one, the other that i dont remember the name).clean all the corrusion that you can find,let your phone charge for some hours and try again
opssemnik said:
clean all the contacts with alcohol (not the normal one, the other that i dont remember the name).clean all the corrusion that you can find,let your phone charge for some hours and try again
Click to expand...
Click to collapse
I've already done that.
Str1ngcheese said:
The next day I got some tools to open her up. There was pretty extensive corrosion to the motherboard, so using some alcohol I cleaned it all off, rinsed it, and let it dry. I also took apart everything else and cleaned any corrosion. The inside looks brand new.
Click to expand...
Click to collapse
Problem is the power button doesn't work, and the flashing fails. It looks like the flashing fails because the phone isn't unlocked. To unlock, I need the power button. Kinda stuck.
Str1ngcheese said:
I've already done that.
Problem is the power button doesn't work, and the flashing fails. It looks like the flashing fails because the phone isn't unlocked. To unlock, I need the power button. Kinda stuck.
Click to expand...
Click to collapse
the golden contacts on the power button / mobo could be damaged, do a little short till phone turns on
opssemnik said:
the golden contacts on the power button / mobo could be damaged, do a little short till phone turns on
Click to expand...
Click to collapse
How would I go about doing a short?
Str1ngcheese said:
How would I go about doing a short?
Click to expand...
Click to collapse
touch in both pins, something that passes electric current(like a yarn,wires, copper wire, something that passes electrical current).its basicly what the power button does.
Update:
To be more specific:
I watered my Fire 8 HD a bit. The bottom side with the speakers got wet, I immediately took it out of the liquid and tried to dry it. All worked well afterwards, expect the Volume down button doesn't correspond anymore, which is not a big deal. Now I haad to shut it off and can't get it back on, because it is always entering recovery mode, not letting me advance to the os.
Any ideas on how to fix this or work around?
Thanks in Advance!
If the partition containing recovery was damaged, I am pretty sure it's dead (unless firmware becomes available?). Dumb question but have you tried resetting and wiping cache when you do get to recovery?
Also if you have enough rice around...
My screen is half green but only in some screens. I just installed a version of viper trying to get it to work on android 11, it didn't and I removed it. After I rebooted, this happened. Also having no sim card detected if that matters.
Edit: Seems like it's happening in apps now too, not on reboot, like for instance the unlock bootloader warning is normal. Fastboot is also fine, no green. I do see it in the recovery screen where you choose your language though.
Edit2: Reflashed Android 11, installed Magisk on both slots and it's still there when it booted back up
Edit3: I wiped all data and flashed the ROM through fastboot and it got worse. Now the bootloader screen is completely green are are the dots around the boot animation. Do I contact support at this point? Seems like it got worse as time went on..
Anyone ever seen this?
Please help
xgerryx said:
My screen is half green but only in some screens. I just installed a version of viper trying to get it to work on android 11, it didn't and I removed it. After I rebooted, this happened. Also having no sim card detected if that matters.
Edit: Seems like it's happening in apps now too, not on reboot, like for instance the unlock bootloader warning is normal. Fastboot is also fine, no green. I do see it in the recovery screen where you choose your language though.
Edit2: Reflashed Android 11, installed Magisk on both slots and it's still there when it booted back up
Edit3: I wiped all data and flashed the ROM through fastboot and it got worse. Now the bootloader screen is completely green are are the dots around the boot animation. Do I contact support at this point? Seems like it got worse as time went on..
Anyone ever seen this?
Please help
Click to expand...
Click to collapse
To me that looks like a HW issue!
xgerryx said:
My screen is half green but only in some screens. I just installed a version of viper trying to get it to work on android 11, it didn't and I removed it. After I rebooted, this happened. Also having no sim card detected if that matters.
Edit: Seems like it's happening in apps now too, not on reboot, like for instance the unlock bootloader warning is normal. Fastboot is also fine, no green. I do see it in the recovery screen where you choose your language though.
Edit2: Reflashed Android 11, installed Magisk on both slots and it's still there when it booted back up
Edit3: I wiped all data and flashed the ROM through fastboot and it got worse. Now the bootloader screen is completely green are are the dots around the boot animation. Do I contact support at this point? Seems like it got worse as time went on..
Anyone ever seen this?
Please help
Click to expand...
Click to collapse
Flash it back to normal factory built
Sent from my IN2023 using Tapatalk
Bad turns to worse. Now stuck in crashdump mode, can't get into edl. Pretty screwed right now
xgerryx said:
Bad turns to worse. Now stuck in crashdump mode, can't get into edl. Pretty screwed right now
Click to expand...
Click to collapse
Msm tool will bring it back. Hopefully you have backed up persist.img just in case.
FreshlyBaked 420 said:
Msm tool will bring it back. Hopefully you have backed up persist.img just in case.
Click to expand...
Click to collapse
I can't get edl mode to stick. Once I release the volume buttons after it's plugged in it just reboots. Won't stay in edl so I can't use the msm tool.
Tried both USB 2 and 3 ports, no difference. Could be a driver thing but nothing I've tried has enabled me to update the qc drivers. Can't get the ones built into the phone obviously.
Nothing is backed up.
So now holding volume up and down and then connecting to PC just brings up fastboot every time. Not even recognizing the driver anymore in device manager.
Update....finally got back into the OS after hours of trying things. Ended up flashing all the img files manually and booting back up. Hugeeeeeee issues. See pictures. The phone is going back.
xgerryx said:
Update....finally got back into the OS after hours of trying things. Ended up flashing all the img files manually and booting back up. Hugeeeeeee issues. See pictures. The phone is going back.
Click to expand...
Click to collapse
That appears to be a loose flex cable to the screen. Shame it can't just be popped back in. Careful when sending it back as they may look at it and suggest it's been dropped (not saying you have) I've worked in the mobile industry in my younger years and we would certainly query this is it came into our shop.
Hopefully they take it in and deal with it, give you a brew device.
Certainly wouldn't be happening pal.
dladz said:
That appears to be a loose flex cable to the screen. Shame it can't just be popped back in. Careful when sending it back as they may look at it and suggest it's been dropped (not saying you have) I've worked in the mobile industry in my younger years and we would certainly query this is it came into our shop.
Hopefully they take it in and deal with it, give you a brew device.
Certainly wouldn't be happening pal.
Click to expand...
Click to collapse
It's funny you say that something could be loose, I have no idea how. I've only had that replacement device for about 2 months and I've never even tossed it in something other than the bed or a chair, normal handling of a device, let alone dropped it. I hope they deal with it though, between the screen and the extreme overheating I wouldn't doubt that something is fried at this point. There's not a scratch on the device.
Waiting for them to send an email about the repair so I can send it back.
xgerryx said:
It's funny you say that something could be loose, I have no idea how. I've only had that replacement device for about 2 months and I've never even tossed it in something other than the bed or a chair, normal handling of a device, let alone dropped it. I hope they deal with it though, between the screen and the extreme overheating I wouldn't doubt that something is fried at this point. There's not a scratch on the device.
Waiting for them to send an email about the repair so I can send it back.
Click to expand...
Click to collapse
Well the overheating could have been a poor contact with the heatsink (more than likely)
The loose connection if it is that won't be your daily as they should clip in, if this is a refurb then that's probably your answer.
It's a weird one but you've just got to roll the dice mate..
All the best of luck with it..
If you can, try to talk to a tech from OnePlus about it.
Get some clarity if possible.
FreshlyBaked 420 said:
Msm tool will bring it back. Hopefully you have backed up persist.img just in case.
Click to expand...
Click to collapse
I have persist.img backed up, but bootloader is locked as I tried to msm.
Anyway to flash it?
areyouanand said:
I have persist.img backed up, but bootloader is locked as I tried to msm.
Anyway to flash it?
Click to expand...
Click to collapse
Check out this thread about the persist.img
https://forum.xda-developers.com/on...de-fix-persist-img-loss-finger-print-t4125909