Hey!
While I was calibrating my fingerprint, phone suddenly turned off and went to recovery with screen off.
I managed to reflash stock rom through fastboot and it boots to system fine, but the screen stays off and the front camera keeps trying to open while playing the MIUI camera sound (sometimes, while booting, the camera does manage to open once, kinda like it's calibrating). Some playing around with ADB and it seems that the SIM isn't recognized either.. antenna maybe?
I opened the phone up and checked everything, there's no visible issues with the electronics, however it could just be the inside of a cable that died?
Does anyone know what this could be? I noticed the screen, fingerprint reader and antenna are all connected to the same removable PCB, but the camera isn't so that's odd.
Aren't we moving way too fast here? Like wtf is happening rn?
First: Explain in detail from the beginning please if you want help.
Second: Please state exactly what is your issue, and the ROM version of your device.
I don't think what you just did is the cause of whatever problem you're facing, do you mind telling me the source from which you got this phone? Otherwise you might want to send it to a service center.
XDHx86 said:
Aren't we moving way too fast here? Like wtf is happening rn?
First: Explain in detail from the beginning please if you want help.
Second: Please state exactly what is your issue, and the ROM version of your device.
I don't think what you just did is the cause of whatever problem you're facing, do you mind telling me the source from which you got this phone? Otherwise you might want to send it to a service center.
Click to expand...
Click to collapse
It's a bit of a long one, so I didn't want to bother too much with the details if anyone knew what those specific issues could be caused by, here goes though:
I am on a Mi 9T bought on Amazon Italy in July 2019. I cannot comfortably send it to a repair center due to every authorized shop around here is just a drop-off point for Xiaomi RMA. I talked to them and, due to (>6 months old) glass damage to the screen and back of the phone, they intended to charge me way more than I can afford, as "solving issues covered by the warranty would require us to replace the accidentally damaged components"
As for what happened:
I was running LOS 17.1 with no issues for a few months. I went to unlock the phone and I heard the reboot vibration, which sent me to recovery (softbricked) but with no screen signal. I assumed it was just a software problem, so I flashed MIUI 12 (global, V12.0.7.0.QFJMIXM) to see what would happen.
As it completed, the phone rebooted itself, the MIUI logo popped up and it went to system (seemingly) without any issues.
I went through the initial wizard and played around with it. everything seemed fine and I even made sure the screen did work in recovery and fastboot. Later, when I went to setup the fingerprint reader, the screen went blank for half a second when I first touched it, and then the same screen death -> reboot to recovery.
The phone was softbricked again, though, this time, reinstalling MIUI didn't yield the same success. Now:
MIUI boots "normally" again
The screen isn't working at all
The front camera opens, as if it's calibrating, when system boots up
The front camera randomly tries to open again every now and then, failing to do so as if the motor is stuck, while MIUI plays the camera closing sound.
Meddling through ADB, the antenna doesn't seem to be working, but I can't be 100% sure due to the methods used
The power and volume buttons, speakers, and the charging light all work.
I have opened the phone up myself, thoroughly checked every cable, connection and PCB, but there is no sign of damage. I put it back together and the same issue continued.
My best guess is that something inside the fingerprint reader went bad and shorted something else.
What that something else is, I couldn't find out. Given the antenna, screen and FOD are all connected to the same little PCB which then runs a couple cables to the motherboard, I am now in the process of finding a couple replacement cables to see if that fixes anything.
As I mentioned before, repair centers are not an option due to the lack of anyone who's willing to help me for less than a good chunk of the price of the phone.
Interesting. So basically what happened is due to the initial soft brick and accordingly you flashed a global MIUI 12 ROM, which in return brought you to the second soft brick which caused some issues within the hardware of the device.
Now you're stuck with a faulty screen, a faulty camera and a faulty antenna.
I don't have the skills to play around with the motherboard and the phone circuit. And I don't care which youtube tutorial you saw, you should have NEVER done that - Of course unless you're actually experienced in that manner, then I apologize for speaking with such prejudice -
I can't help you if you messed up your phone circuit since I have no knowledge about android hardware, however I can safely assume that what caused your issue isn't related to hardware.
I think the issue is caused by an incomplete flashing of a ROM (In this case MIUI 12 global) OR flashing a different variation from your device.
e.g. you flashed only the ROM, but didn't flash the other components of the ROM.
Needless to say, flashing a variation of the ROM that isn't meant for you device can be a disaster recipe.
I recommend flashing LOS again, since you can't go back on Xiaomi devices due to rollback protection.
XDHx86 said:
I don't have the skills to play around with the motherboard and the phone circuit. And I don't care which youtube tutorial you saw, you should have NEVER done that - Of course unless you're actually experienced in that manner, then I apologize for speaking with such prejudice -
Click to expand...
Click to collapse
I understand why you'd think that and have seen people do similar stupid things, however I didn't watch any youtube video and know what I'm doing quite well.
I made sure I flashed the correct rom through fastboot to restore everything to stock. I did try to reflash LOS and whatever else (though it's kind of a pain with adb shell), but it doesn't fix the problem, sadly.
That's why I'm betting on a HW issue.
The fingerprint reader and everything else worked flawlessly in LOS for months, but it made the screen go blank and bricked the device in both LOS and fully functional, stock MIUI.
Currently, I'm battling with this damn thing to get USB debugging working while booted to system, so I can do a few things like cast the screen to my PC and see what works from there.
I have access to fastboot and recovery, but everything I know (editing build.prop or patching the boot image) didn't work so far. Do you have any idea what I could do to get that done?
angometry said:
Currently, I'm battling with this damn thing to get USB debugging working while booted to system, so I can do a few things like cast the screen to my PC and see what works from there.
Click to expand...
Click to collapse
If the touch screen is dead then you can use mouse and OTG cable.
If it is completely black then you can get usb c to HDMI cable (Also usb c hub might work, like this one). Or you can use playstore on pc to download and install apps like (Screen stream over HTTP) on your device, just make sure your device is connected to the internet and you're signed in on your phone as well, you might have to type in the screen password if you have one.
angometry said:
I have access to fastboot and recovery, but everything I know (editing build.prop or patching the boot image) didn't work so far. Do you have any idea what I could do to get that done?
Click to expand...
Click to collapse
I don't know why bother with build.prop unless you have the wrong fingerprint prop. Then you can get the correct one from your device's stock ROM, though I think this is irrelevant to your issue.
All I can think of is:
Wiping dalvik cache, though you might have already done that.
Trying other custom ROMs from here.
You may try to get your device rollback index and installing a MIUI ROM that has index higher than it, and see if that works.
That is as far as I can help, unfortunately.
I have zero knowledge when it comes to hardware, so I can only help with software issues. If none of my solutions worked then sorry for wasting your time :/
XDHx86 said:
If it is completely black then you can get usb c to HDMI cable (Also usb c hub might work, like this one).
Click to expand...
Click to collapse
Wait, does it actually just automatically use it as a 2nd screen if I connect it via HDMI?
XDHx86 said:
I don't know why bother with build.prop unless you have the wrong fingerprint prop. Then you can get the correct one from your device's stock ROM, though I think this is irrelevant to your issue.
Click to expand...
Click to collapse
Sorry, I didn't explain myself, I'm looking for a way to enable USB Debugging without a screen. Thinking that using adb in twrp is the best way, but I can't manage to do it. Do you have any ideas?
If I can get it on, I can then use things like scrcpy to get screen signal through USB.
Main problem with everything else is that the screen is 100% dead. Even with usb otg I don't know how I could possibly get through the setup wizard haha
angometry said:
Wait, does it actually just automatically use it as a 2nd screen if I connect it via HDMI?
Click to expand...
Click to collapse
I haven't tried it myself, however it should detect it as a second monitor. Give it a try the cable isn't costly at all anyway.
angometry said:
I'm looking for a way to enable USB Debugging without a screen. Thinking that using adb in twrp is the best way, but I can't manage to do it. Do you have any ideas?
Click to expand...
Click to collapse
TWRP has debugging mode on by default, however that strictly applies to recovery and fastboot modes only as debugging mode is pretty powerful and can cause security issues. So you better forget about it.
I saw one of my friends who owns an authorized service center use some cable connections to get the screen to display on another touch screen. If you have the capabilities and resources I recommed trying it, though don't mess too much with the motherboard.
Just a question though, can you confirm if the touch is working? If not then there's a chance - Although slight - that this is just a UI problem (Which is pretty common in MIUI ROMs for some reason). In that case deleting dalvik cache or completely reflashing the ROM might solve the issue.
I may not do much help but certainly someone there can help so it's better if you include "usb debugging" in the title and/or the tags. Like changing the title to "Enabling usb debugging without screen" or "Screen is dead, need help to flash ROM"
Using proper title and proper tags can get the right person to help.
Related
By now folks realize there are different hardware variances for the touchscreen which is one reason why some people have issues and others do not.
Don't you hate it when you have a workable system, then an update comes along which fixes something, let's say GPS, but then your touchscreen goes down the tubes? Suddenly you have dead spots, dead bands, ghost/phantom touches, stuck touches, broken drags, etc. Touchscreen works ok when held or plugged in, but is unusable on a table?
Never fear, I've put together packages to handle 3 different variances of the touchscreen.
I was able to make the touchscreen usable again on 3 of 4 test units. The 4th was always bad even out of the box so it might be hopeless for that one.
I do NOT claim this will fix everyones' touchscreen and that isn't even the goal as it might be an impossible task.
The goal is to make 70-80% of the problem units usable (again), but even if only 50% become usable this is an improvement over the current situation.
On to the packages:
In the attached boot-ts.7z file you'll find 4 files:
boot-ts10-lock.img
boot-ts20-lock.img
boot-ts30-lock.img
boot-ts-unlock.img
the ts10, ts20, and ts30 packages handle 3 variances on the touchscreen
You basically try each one to see which works best for your particular touchscreen.
Once you find one (and hopefully you do) then it is locked in place so future updates won't mess up your touchscreen again. No more OTA performance anxiety.
Now let's say there is an update in the future which has touchscreen fixes you want to use, that is where the 4th package comes into play. Once you use the ts-unlock image, you will once again be using touchscreen updates from the manufacturer. If that update doesn't work out, you can go back and use the ts10/20/30 package that was working for you.
Ok, so how does all this work?
I tried to make the process as simple as possible (has been tested on JWR66N, JSS15J, and JSS15Q, will work on LTE and custom ROMs also):
Your bootloader must be UNLOCKED to use these packages. Unlocking your bootloader is covered in this post.
unpack the boot-ts.7z package using 7-zip
you'll be left with a boot-ts directory with the aforementioned files
connect your tablet by USB
make sure USB debugging is enabled
Settings->About tablet [tap "Build number" 7 times]
Settings->Developer options [check "USB debugging"]
you can find adb/fastboot drivers HERE
in a command prompt in the boot-ts directory type (commands in italics)
adb reboot bootloader
wait for the bootloader screen to come up
alternatively use Power+VolDown to get to the bootloader/fastboot screen
fastboot boot boot-ts10-lock.img
this is how you try out package ts10
the screen will hang for 18-24 seconds, this is NORMAL, do not touch
this does NOT flash over your existing kernel
wait until Android is COMPLETELY booted
Note: if you are on Android 4.4 the stock 4.3 kernel will not get past the BouncingBalls
wait 120 seconds for the boot to settle down
press/hold the Power button 10-15 seconds until the tablet reboots
proceed to next step
adb reboot
after booting to Android you MUST reboot at least once
IGNORE any instability up to this point, it is expected
if adb reboot does not work for some reason, use the power button to shutdown/reboot
once you are booted into Android the 2nd time, try out the touchscreen and see if it feels usable
if there is instability, give it one more reboot back into Android before judging
if things are not working acceptably
repeat step #3, with ts20, and ts30 if needed
hopefully between ts10, ts20, and ts30, you will have found a package that works for you
there is nothing else for you to do
you can reboot and use your normal ROMs, custom ROMs, stock kernels, custom kernels, etc.
your touchscreen package is locked in place and won't change unless you want it to
if you want to go back to the way it was before and/or you want a future touchscreen update from the manufacturer
repeat step #3 using boot-ts-unlock.img
upon first reboot you will have the touchscreen software from the installed ROM/kernel
Please post feedback with:
the version of software you are running
what was/is broken
whether any of the packages helped
Remember to click thanks if you find this useful.
That's it folks, hope this helps somebody.
very interesting! lots of FC after loading the file, cant really "Power off using power button" because of FC-windows, using adb reboot instead.
current ROM: [ROM][CM10.2][4.3][CyanogenMod FLO Kangs][DJL10.2][LINARO][Build 10-TEST][2013/08/27]
ts-10: no more jumping in google maps while zooming/panning, but still jumping in other apps. after second reboot, starts jumping in maps again. after third reboot, no jumping on rightside of screen.
screenshot using two fingers
ts-20: lots of jumping on right side of the screen, zooming/panning in gmaps is still jumpy. after third reboot, still jumpy in gmaps.
ts-30: still jumps of right side of the screen, just a few mm from the right bezel,zooming/panning in gmaps is still jumpy. after second reboot, same effect. after third reboot, still jumpy on right side of screen.
so what exactly are in those files?
neonlite said:
very interesting! lots of FC after loading the file, cant really "Power off using power button", using adb reboot instead.
tried ts-10. no more jumping in google maps while zooming/panning, but still jumping in other apps, will try others.
so what exactly are in those files?
Click to expand...
Click to collapse
When you say lots of FCs, can you tell me what ROM/version you are running?
You should IGNORE any instability in that first boot. While you can boot into android using the files I'm providing (and in some cases run fine), there could be mismatches in versions depending on what you have currently installed, which is why I say in RED you must reboot at least once before the system will become stable.
Once you do that reboot, you are back on your original software with just the touchscreen controller updated.
neonlite said:
ts-30: still jumps of right side of the screen, just a few mm from the right bezel,zooming/panning in gmaps is still jumpy. after second reboot, seems most stable.
Click to expand...
Click to collapse
You must IGNORE any results from that first boot for all the packages, especially since you are running CM because (on that first boot) you are essentially running CM with a stock kernel without any kernel mods CM may need.
On CM I would actually not pass judgment until perhaps a second reboot.
One shouldn't have as much instability in that first boot if they are running a stock ROM.
Can you compare the behavior to what you had before trying them out?
I presume you had some issues before, hence trying these out.
sfhub said:
You must IGNORE any results from that first boot for all the packages, especially since you are running CM because (on that first boot) you are essentially running CM with a stock kernel without any kernel mods CM may need.
On CM I would actually not pass judgment until perhaps a second reboot.
One shouldn't have as much instability in that first boot if they are running a stock ROM.
Can you compare the behavior to what you had before trying them out?
I presume you had some issues before, hence trying these out.
Click to expand...
Click to collapse
yes, ignored all FC's. no problem.
ts-10 is running perfectly, no more jumpy stuff. maps/right side of screen, hold and drag working great too.
I really appreciate how much effort you've put into helping others with troubled devices here.
Could we get some clarification on what exactly the 3 packages are? Are these touchscreen settings customized by you or simply the settings from each of the 3 versions of 4.3 we have had available to us?
You sent me here from the other thread and i must thank you, the ts10 one worked fine and now no screen problems, cancelled my replacement. Just a question though, if you tap hard on the camera corner of the tablet whilst holding it in the air, do you hear a small rattle?
It is the touchscreen controller software.
pashinator said:
Just a question though, if you tap hard on the camera corner of the tablet whilst holding it in the air, do you hear a small rattle?
Click to expand...
Click to collapse
Every unit has the rattle. Some louder than others. It is normal. Possibly the lens or focusing mechanism.
sfhub said:
Every unit has the rattle. Some louder than others. It is normal. Possibly the lens or focusing mechanism.
Click to expand...
Click to collapse
cool i thought i broke it by bashing it to get the screen to work again
i've been a long time lurker at the xda forums and your multitouch fix made me register and become a member just to say thanks. ts10 fixed my multitouch issues, going to observer for a few more days and update you if there are bugs. thanks a lot!
My tablet was working perfectly on the JSS15J then JSS15Q came along and I found letters "sticking" while typing and the screen was unresponsive to touch while laying flat on a table. I flashed the ts-10-lock image and so far, so good. I have been typing for awhile now with no "sticking" letters, and while laying flat on a table. I have not encountered the unresponsive screen at all flat on its back or otherwise. I will continue running through scenarios that used to give me problems and report back if I encounter anything. Also, running Bulletproof kernel and no impact with kernel functions.
Thank you sfhub!
Can anyone verify if placing the N7 on a Macbook Pro keyboard still triggers the multitouch craziness with the patch?
This is the video of my N7 placed on my MBPs' keyboard.
http://www.youtube.com/watch?v=H05N1P0dpTo
Can this really be only a software problem?
I am not really experiencing other touchscreen issues with my N7 except for some very rare stuck touches. This one I triggered by accident.
bandit_knight said:
Can anyone verify if placing the N7 on a Macbook Pro keyboard still triggers the multitouch craziness with the patch?
Click to expand...
Click to collapse
So this guy goes to the doctor's office and says my head hurts everytime I hit the wall. The doctor says, then stop hitting the wall.
Couldn't you just slide it over and don't use the tablet on top of the keyboard?
Have you considered the MacBook Pro might be emitting interference? Stray currents and voltages? It doesn't take much to throw these capacitative touchscreens off.
On this thread, most people have it much worse than you making the tablet very hard to use. We are trying to get these units back into a state that is at least usable.
Your case, while an interesting science project really isn't something someone would feel any sense of urgency to help address.
Excellent.
I'll try these now and put them through there paces.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Great work
Incredible!! tried the ts10 and OMG everything is fixed!! Great work, sfhub!!
you should work in Google, seriously! shouldnt he, everybody?
My device is:
1) 4.3 JSS15Q
2) two finger touching registered as one finger, and muiti-touches ghosted. hold on the Left side of screen and the touch is registered repeatedly
1) TS10
Yea I booted 10 first and it is great. I can't reproduce any of the bugs I've seen before using YAMMT.
Google Maps Pinch/Zoom is working flawlessly. I couldn't even zoom in before.
The OP says to "fastboot boot boot-ts10-lock.img". Should we eventually "fastboot flash boot-ts10-lock.img" to make it permanent?
My N7 is:
HW rev_e
Bootloader....... FLO-03.14
15Q - CM 10.2 Kanged Build 9
Sitting the N7 on my Logitech Keyboard doesn't make it go crazy either! LOGITECH FTW
sfhub said:
It is the touchscreen controller software.
Click to expand...
Click to collapse
How do you "lock" it in so that it won't get updated? Is it just a file in the filesystem, if so how do you prevent "fastboot erase" from getting rid of it? I've looked at ektf3k.c and know where I need to make a change so that it will replace any non-matching version, but I don't really know where the actual firmware is stored. It doesn't seem to be in the vendor part of the kernel tree or in the actual ektf3k.c or ektf3k.h files. Where is it kept? kept in fw_data.b
I'm new to Android, but I'm not new to Linux or reverse engineering so please be patient with me. Just looking for a technical description of how you did what you did. What exactly is in the .img files?
EDIT: I haven't booted any of them yet, but I'm guessing these are Linux kernel images with a modified version of the elan driver. Sorry for being stupid, I'm just trying to put this all together in my head and I can't cope with anything that seems like magic. Thanks for your time.
EDIT: Ok, I figured out where the firmware is stored. I also successfully built a ROM with my compiled kernel and flashed them to the tablet. No brick, it booted the second try and seems to work. Of course there's no apps on it hardly.
I'm kinda thinking out loud here, please correct anything that I get wrong:
I started off with the assumption that there was a closed source driver, but that seems to have been incorrect on my part. After looking at the code a little more, I see that ektf3k.c appears to be the lowest level driver, outside the embedded firmware. The driver does only update the firmware in the case that the flash is empty (FFFF.....) or the firmware presented is a higher version (just as you said of course). It appears that a simple change will make it flash any version presented that is different than the one currently flashed in. I plan to try this on my tablet and see if there are any unexpected repercussions from doing so.
I wish I had a datasheet for the controller (hint hint anyone).
DISCLAIMER: I know that you have already solved this problem in an arguably better way, I just want to tinker around a little. Thanks again. :good::good::good:
sfhub said:
By now folks realize there are different hardware variances for the touchscreen which is one reason why some people have issues and others do not.
Don't you hate it when you have a workable system, then an update comes along which fixes something, let's say GPS, but then your touchscreen goes down the tubes?
Never fear, I've put together packages to handle 3 different variances of the touchscreen.
I was able to make the touchscreen usable again on 3 of 4 test units. The 4th was always bad even out of the box so it might be hopeless for that one.
I do NOT claim this will fix everyones' touchscreen and that isn't even the goal as it might be an impossible task.
The goal is to make 70-80% of the problem units usable (again), but even if only 50% become usable this is an improvement over the current situation.
On to the packages:
In the attached boot-ts.7z file you'll find 4 files:
boot-ts10-lock.img
boot-ts20-lock.img
boot-ts30-lock.img
boot-ts-unlock.img
the ts10, ts20, and ts30 packages handle 3 variances on the touchscreen
You basically try each one to see which works best for your particular touchscreen.
Once you find one (and hopefully you do) then it is locked in place so future updates won't mess up your touchscreen again. No more OTA performance anxiety.
Now let's say there is an update in the future which has touchscreen fixes you want to use, that is where the 4th package comes into play. Once you use the ts-unlock image, you will once again be able to get touchscreen updates from the manufacturer. If that update doesn't work out, you can go back and use the ts10/20/30 package that was working for you.
Ok, so how does all this work?
I tried to make the process as simple as possible (has been tested on JWR66N, JSS15J, and JSS15Q):
Your bootloader must be UNLOCKED to use these packages. Unlocking your bootloader is covered in the stickies.
unpack the boot-ts.7z package using 7-zip
you'll be left with a boot-ts directory with the aforementioned files
connect your tablet by USB
make sure USB debugging is enabled
you can find adb/fastboot drivers HERE
in a command prompt in the boot-ts directory type (commands in italics)
adb reboot bootloader
wait for the bootloader screen to come up
alternatively use Power+VolDown to get to the bootloader/fastboot screen
fastboot boot boot-ts10-lock.img
this is how you try out package ts10
the screen will hang for 18-24 seconds, this is NORMAL, do not touch
this does NOT flash over your existing kernel
adb reboot
after booting to Android you MUST reboot at least once
IGNORE any instability up to this point, it is expected
once you are booted into Android the 2nd time, try out the touchscreen and see if it feels usable
if there is instability, give it one more reboot back into Android before judging
if things are not working acceptably
repeat step #3, with ts20, and ts30 if needed
hopefully between ts10, ts20, and ts30, you will have found a package that works for you
there is nothing else for you to do
you can reboot and use your normal ROMs, custom ROMs, stock kernels, custom kernels, etc.
your touchscreen package is locked in place and won't change unless you want it to
if you want to go back to the way it was before and/or you want a future touchscreen update from the manufacturer
repeat step #3 using boot-ts-unlock.img
Please post feedback with:
the version of software you are running
what was/is broken
whether any of the packages helped
Remember to click thanks if you find this useful.
That's it folks, hope this helps somebody.
Click to expand...
Click to collapse
So if we do this can we lock the boot loader backup. If for some reason it doesn't work will I be able to take it back for exchange. After unlocking the boot loader. Do people leave the boot loader unlocked . Is the software staying the same meaning will I be ok downloading future updates.
Is there a way to find out what variance is installed right now on the device? I got JSS15Q and my tablet is useable but sometimes there are ghost touches or the touch is stuck or gets interrupted and the likes.
Hi there,
My phone not turning on not without battery and SD not with home and volume+ and power button not with both volumes and power nothing at all not even vibrating when charging I am not sure if it's the battery but it was charged before I rebooted once rebooted it didn't turn back on I am on aurora ics and cwm.
I didn't have any problems with it partitions might of been wiped but I guess this would leave me with access to bootloader or anything or a vibrate on charge at least it happened as I was formatting another device but put the wrong sd on ubuntu so I started to think it might be the battery except it was charged unless it decided to leak all the charge in no time.
Also it doesn't do anything on usb or charge connection no vibrate no led no light buttons no nothing just nothing.
Sounds like my issue...
If in fact you did format the whole 3.69gb partition, then you wiped the phone.
So far, my only recourse has been to attempt a JTAG and install a bootloader.
I'm thinking that maybe I can try some form of "wire trick", like the ones used on the HTC Sensation, but I don't want to blow it up by shorting something unrepairable.
If you find another solution, please reply as it would be helpful to others.
PoXFreak said:
Sounds like my issue...
If in fact you did format the whole 3.69gb partition, then you wiped the phone.
So far, my only recourse has been to attempt a JTAG and install a bootloader.
I'm thinking that maybe I can try some form of "wire trick", like the ones used on the HTC Sensation, but I don't want to blow it up by shorting something unrepairable.
If you find another solution, please reply as it would be helpful to others.
Click to expand...
Click to collapse
nope i didnt format 3.96 gb it was 3 mb and it was shown as linux cd gadget also it worked afterwards until i rebooted next day then blackness the thing is i cant seem to find a battery to try with so i need to try everything first
The one I have here wouldn't start charging the battery until I force-fed the battery directly. (use a 4-5v charger and directly charge the battery for a couple of minutes).
Mine worked, but I made the mistake of formatting the entire partition (3.69gb), so now the phone does absolutely nothing.
PoXFreak said:
The one I have here wouldn't start charging the battery until I force-fed the battery directly. (use a 4-5v charger and directly charge the battery for a couple of minutes).
Mine worked, but I made the mistake of formatting the entire partition (3.69gb), so now the phone does absolutely nothing.
Click to expand...
Click to collapse
I am a bit confused here so now when you plug it you can do something to it since it's charging? I guess I never did the 3.69 thingy if I am not mistaken..So lemme ask you if I tried the wall outlet for example instead of the USB to tv or laptop would that help to start it? I am thinking of replacing the battery and see what happens that's if I can find it here in Turkey the Turks always into the newest phones so this one is ancient to them to find a battery for...
Mine is in the same state. But I know that in my efforts to get it to start again I accidently wiped the the entire partition. Can't turn it on, can't get a pink screen, not a thing and haven't beenable to find any solution. So I guess all I can do is sit back and check the postings to see if anyone else has the same issue and knows of a way to restore the boot partition.
Burtrum57 said:
Mine is in the same state. But I know that in my efforts to get it to start again I accidently wiped the the entire partition. Can't turn it on, can't get a pink screen, not a thing and haven't beenable to find any solution. So I guess all I can do is sit back and check the postings to see if anyone else has the same issue and knows of a way to restore the boot partition.
Click to expand...
Click to collapse
I'm thinking of trying to run MTTY 1.42 and talk directly with the qualcomm chip to send the boot files myself, but I need to know what I need and where it goes first.
I did this with the HTC Kaiser (AT&T Tilt) with some success.
That was on Windows XP though...not sure if it will run correctly on Win 7.
PoXFreak said:
I'm thinking of trying to run MTTY 1.42 and talk directly with the qualcomm chip to send the boot files myself, but I need to know what I need and where it goes first.
I did this with the HTC Kaiser (AT&T Tilt) with some success.
That was on Windows XP though...not sure if it will run correctly on Win 7.
Click to expand...
Click to collapse
help me i have the same issue....
service
May be best option is to take it to service center.
My nexus 6p suddenly won't start, I've had my phone since May 2016 so more than a year now.
I've flashed a custom ROM onto it, I'm sure this isn't a software issue because it's been running fine since I bought it (and flashed it) and I followed all the instructions correctly.
I've read through this thread and tried the solutions there, hold the power button for longer than usual (a few minutes), hold the volume down button and power together, hold the volume down button then charge it, now hold the power button. I tried all 3 solutions which worked for many in that thread, but not me.
This all started 2 days ago, with no changes software-wise and using the same configuration as when I first flashed it, I opened the app HERE Maps and then my phone froze, totally stuck and unresponsive, restarting was no good, I had to go into TWRP and wipe the cache and dalvik cache, and it booted fine.
Today, same thing, I opened up HERE Maps and it got stuck again, I now notice that it takes longer than usual to start up via the power button, and wiping the cache and dalvik cache does not work anymore, it stucks on boot.
Now, my phone is not able to start at all. I think this is a hardware-related issue.
So quick recap:
1. Opened HERE Maps and gets frozen
2. Wiping cache and dalvik cache no longer works, stuck on boot.
3. Phone not able to start at all.
I am out of warranty period-wise, but I also custom it, so obviously my warranty is out the window. I need some insight from you guys here at XDA before I buy another costly phone.
someRandomSamaritan said:
...Now, my phone is not able to start at all. I think this is a hardware-related issue...
Click to expand...
Click to collapse
You're probably correct. Since you are unlocked and have a working Recovery mode, you may be have some success with the 4 core fix/workaround. Have you attempted a factory reset? Formatted partitions and flashed a full ROM using the flash-all.bat script?
v12xke said:
You're probably correct. Since you are unlocked and have a working Recovery mode, you may be have some success with the 4 core fix/workaround. Have you attempted a factory reset? Formatted partitions and flashed a full ROM using the flash-all.bat script?
Click to expand...
Click to collapse
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken
someRandomSamaritan said:
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken
Click to expand...
Click to collapse
Can you access recovery or bootloader mode?
If within warranty, contact google/Huawei depending on where you purchased the phone from.
You could try telling google that your phone is bootlooping for a potential out of warranty RMA.
someRandomSamaritan said:
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken
Click to expand...
Click to collapse
Is it recognized at all when you plug a data cable to your PC? Your phone may be stuck in Qualcomm's EDL mode. Search.
No recovery mode, no TWRP, not within warranty, plug in data cable into PC not detected (makes sense, it's not powered on after all)
You could try telling google that your phone is bootlooping for a potential out of warranty RMA.
Click to expand...
Click to collapse
This is a possible option..I'll try that tomorrow when it's morning
Anything else I could try? I think the most obvious methods are not available for me with this kinda situation
someRandomSamaritan said:
No recovery mode, no TWRP, not within warranty, plug in data cable into PC not detected (makes sense, it's not powered on after all)
Click to expand...
Click to collapse
If your phone is in EDL mode, there is no indication the phone is on. No boot, no lights, no noise (except from the PC when the USB driver loads). You may want to try several long power button only holds (several minutes) with the phone plugged into your PC. I suppose it is also possible the power switch is bad, but you would be the first I've heard of. Unless you bought your phone directly through Google you will get nowhere with them. They will direct you to Huawei and you said you were out of warranty.
v12xke said:
If your phone is in EDL mode, there is no indication the phone is on. No boot, no lights, no noise (except from the PC when the USB driver loads). You may want to try several long power button only holds (several minutes) with the phone plugged into your PC. I suppose it is also possible the power switch is bad, but you would be the first I've heard of. Unless you bought your phone directly through Google you will get nowhere with them. They will direct you to Huawei and you said you were out of warranty.
Click to expand...
Click to collapse
Okay, this is helpful, you guys seems to think it is in EDL mode (which I haven't heard of until now), I'll try this and hopefully a driver loads or something
EDIT: nope, no drivers are loading, doesn't seem to be anything new in device manager, no device plug in sound, how sure are you that I'm in EDL mode?
It did work a few times yesterday (being able to boot into TWRP and wiping cache and dalvik cache), but now I'm not so lucky, it doesn't work anymore. I don't believe my phone is completely dead for some reason, I still do believe it can be saved. Hopefully I'm right :|
If I plan on buying a new phone, should I buy another 6p? I love the look and feel of it, and it's easy to mod. I can't really go and get another different phone because I prefer purenexus ROMs than any other, it's just simple and clean, problem is, what if another year from now my new 6p breaks? How can I trust that the new phone won't break the exact same way?
What if I end up buying a new 6p every 1 year or so? I'm starting to question the reliability of the 6p, is what I'm facing a very common issue?
someRandomSamaritan said:
If I plan on buying a new phone, should I buy another 6p? I love the look and feel of it, and it's easy to mod. I can't really go and get another different phone because I prefer purenexus ROMs than any other, it's just simple and clean, problem is, what if another year from now my new 6p breaks? How can I trust that the new phone won't break the exact same way?
What if I end up buying a new 6p every 1 year or so? I'm starting to question the reliability of the 6p, is what I'm facing a very common issue?
Click to expand...
Click to collapse
I wouldn't recommend the nexus 6p. I would have a look at the latest pixel 2. They have project treble.
Your issue is different than most others. Most n6p with issues are bootlooping devices.
I have the same exact problem and have tried all sorts of fixes...
This is a serious problem most likely on Huawei's end. All I was doing was charging my phone and using facebook and my phone freezes...
BadBoy2K7 said:
I have the same exact problem and have tried all sorts of fixes...
This is a serious problem most likely on Huawei's end. All I was doing was charging my phone and using facebook and my phone freezes...
Click to expand...
Click to collapse
Did you managed to solve it in the end or ended up RMAing the phone away and getting a new one?
I wouldn't recommend the nexus 6p. I would have a look at the latest pixel 2.
Click to expand...
Click to collapse
Pixel 2 is some expensive thing, out of my budget
someRandomSamaritan said:
Pixel 2 is some expensive thing, out of my budget
Click to expand...
Click to collapse
Then you should look for alternatives. Perhaps OnePlus 5T, etc.
I think I'm out of luck, my phone seems to be dead
As a last resort, I do plan to take it to a phone repair shop and see if they could do something, maybe the battery died? Unlikely but it's worth trying
I tried what was suggested here, plug the phone to a PC and see if a drivers loads or if detected by device manager, or if hearing connect/disconnect sound. Nothing, no signs. Anything else to try by myself?
someRandomSamaritan said:
I think I'm out of luck, my phone seems to be dead
As a last resort, I do plan to take it to a phone repair shop and see if they could do something, maybe the battery died? Unlikely but it's worth trying
I tried what was suggested here, plug the phone to a PC and see if a drivers loads or if detected by device manager, or if hearing connect/disconnect sound. Nothing, no signs. Anything else to try by myself?
Click to expand...
Click to collapse
Repairmen in China have been repairing nexus 5x and 6p by resoldering the cpu. I wish I knew a way to contact a reliable english speaking repair centre.
I was facing bootlooping problem with my Nexus 6P and bootloader was locked so was unable to flash ROM by any mean.
So I tried following few threads and did "fastboot continue" and my device is not showing any sign of power since then. When connected to PC then no USB connection is there.
Is there any suggestions that can solve issue?
someRandomSamaritan said:
Did you managed to solve it in the end or ended up RMAing the phone away and getting a new one?
Click to expand...
Click to collapse
No. Unfortunately this happened to me last month and ive had the phone for almost 2 years now. Its sad because others are having the same issue and I think the hardware is faulty
I just called up a local phone repair and they said from their experience of repairing nexus 6p phones, most (if not all) of them had dead motherboards. The technician told me to get a new model of a phone and skip the 6p as it is a poorly built phone.
I consider saving up for a pixel..
NoobInToto said:
Repairmen in China have been repairing nexus 5x and 6p by resoldering the cpu. I wish I knew a way to contact a reliable english speaking repair centre.
Click to expand...
Click to collapse
Ive heard of people baking motherboard on Nexus 5x and many other phones to reflow the solder.
Yesterday, after a few hitches, I installed twrp 311 and then RR and immediately switched to AOSPE. Now in having the issues described in the title. It might be relevant that the handset got a little wet, but it's gotten wet before and nothing's happened. Could it be a software issue? A hardware issue? A coincidentally timed buildup of dust? Other people have similar issues, but as far as I've seen nobody has had a phone that seems to have a broken USB port except when the phone turns off. Also, the charging connection breaks when I jiggle the cable in the port, which might be relevant.
Halp
Try charging with another USB cable and report. Avoid charging through power banks, they can cause such issues.
william.johhn7! said:
Try charging with another USB cable and report. Avoid charging through power banks, they can cause such issues.
Click to expand...
Click to collapse
I guess I should have added that I tried all the usual stuff. Multiple wall chargers, multiple cables, including a power-only cable, and I've never had any issues with this or other power banks, but it's possible. I'm still leaning towards/hoping that it's a software issue brought on by my flashings.
westinator said:
I guess I should have added that I tried all the usual stuff. Multiple wall chargers, multiple cables, including a power-only cable, and I've never had any issues with this or other power banks, but it's possible. I'm still leaning towards/hoping that it's a software issue brought on by my flashings.
Click to expand...
Click to collapse
Well, power banks has affected my device resulting to what you're facing now. So I don't use them anymore. Try fastboot back to miui. See if the issue persists. If it does, approach the service center. If the port's damaged, then they'll probably replace the sub-board which can cost you around 30% the cost of the device. And if you're under warranty period, you'll be lucky to get it replaced for free.
william.johhn7! said:
Well, power banks has affected my device resulting to what you're facing now. So I don't use them anymore. Try fastboot back to miui. See if the issue persists. If it does, approach the service center. If the port's damaged, then they'll probably replace the sub-board which can cost you around 30% the cost of the device. And if you're under warranty period, you'll be lucky to get it replaced for free.
Click to expand...
Click to collapse
Alright thanks for the advice, I'll try a different ROM... Will switching back to miui relock my bootloader?
westinator said:
Alright thanks for the advice, I'll try a different ROM... Will switching back to miui relock my bootloader?
Click to expand...
Click to collapse
Offficial stable?(I hate it) I don't know. Forked version(Better than official miui)(Xiaomi.eu, multirom, miuipro) won't.
william.johhn7! said:
Offficial stable?(I hate it) I don't know. Forked version(Better than official miui)(Xiaomi.eu, multirom, miuipro) won't.
Click to expand...
Click to collapse
So I flashed the latest land xiaomi.eu and the issue persisted. I turned it off to charge it. I'm in the good ol' US of A, though, so no Xiaomi service centers to go to, and it's out of warranty (not that a Gearbest warranty is worth anything). I'm still hoping it's an elusive software issue, and I still think the behavior (the usb port clearly does function, just not when the phone is booted into recovery or the system or anything else) points to a software issue.
probably unrelated - the flashlight worked in AOSPE and doesn't work in the latest land xiaomi.eu
On a somewhat related note, anyone know where I can find a phone with an SD 800-series soc for under $200?
westinator said:
So I flashed the latest land xiaomi.eu and the issue persisted. I turned it off to charge it. I'm in the good ol' US of A, though, so no Xiaomi service centers to go to, and it's out of warranty (not that a Gearbest warranty is worth anything). I'm still hoping it's an elusive software issue, and I still think the behavior (the usb port clearly does function, just not when the phone is booted into recovery or the system or anything else) points to a software issue.
probably unrelated - the flashlight worked in AOSPE and doesn't work in the latest land xiaomi.eu
On a somewhat related note, anyone know where I can find a phone with an SD 800-series soc for under $200?
Click to expand...
Click to collapse
Flashlight doesn't work in miui roms but works for custom ROMs?! very odd. Try wiping battery stats through twrp. And the last hope to get it working is by fastboot flashing. If that doesn't help, the device needs to be serviced. There must be some local centers that services Xiaomi products.
Anyways forwarding your matter to others(A telegram group consisting of other users and developers). Lets see if they can help.
westinator said:
So I flashed the latest land xiaomi.eu and the issue persisted. I turned it off to charge it. I'm in the good ol' US of A, though, so no Xiaomi service centers to go to, and it's out of warranty (not that a Gearbest warranty is worth anything). I'm still hoping it's an elusive software issue, and I still think the behavior (the usb port clearly does function, just not when the phone is booted into recovery or the system or anything else) points to a software issue.
probably unrelated - the flashlight worked in AOSPE and doesn't work in the latest land xiaomi.eu
On a somewhat related note, anyone know where I can find a phone with an SD 800-series soc for under $200?
Click to expand...
Click to collapse
Flash global stable ROM in edl mode, for me thats the only way to be sure that it's not software
It wont lock the bootloader
bekcicandrej said:
Flash global stable ROM in edl mode, for me thats the only way to be sure that it's not software
It wont lock the bootloader
Click to expand...
Click to collapse
It fixed it!
Some things happened between my last post and the problem fixing itself:
I think I put my phone into edl mode, but rebooted it because I had to go and didn't have time to flash miui
My corrupted samsung sdxc, that I should have mentioned before, was somehow fixed by xiaomi.eu when aospe and rr couldn't fix it
My phone restarted in my pocket when I didn't tell it to - I discovered this when I was prompted to decrypt it at boot
I tried to allow adb in dev settings, but it failed with the error message "your device is temporarily restricted" or something like that
With hopeful/wishful heart, I plugged it in after getting back from a meeting, and everything seemed to work connection-wise (???? don't question, just be grateful I guess). I reflashed AOSPE because I like it better than any other ROM I've tried, and not only did the usb port continue to function normally, but the flashlight started working again!
I guess I'll make monthly sacrifices to the deity of smartphones, or maybe to that xiaomi bunny.
Problem Solved, and thanks for all of your effort. Maybe the suggestions helped! Who knows...
westinator said:
It fixed it!
Some things happened between my last post and the problem fixing itself:
I think I put my phone into edl mode, but rebooted it because I had to go and didn't have time to flash miui
My corrupted samsung sdxc, that I should have mentioned before, was somehow fixed by xiaomi.eu when aospe and rr couldn't fix it
My phone restarted in my pocket when I didn't tell it to - I discovered this when I was prompted to decrypt it at boot
I tried to allow adb in dev settings, but it failed with the error message "your device is temporarily restricted" or something like that
With hopeful/wishful heart, I plugged it in after getting back from a meeting, and everything seemed to work connection-wise (???? don't question, just be grateful I guess). I reflashed AOSPE because I like it better than any other ROM I've tried, and not only did the usb port continue to function normally, but the flashlight started working again!
I guess I'll make monthly sacrifices to the deity of smartphones, or maybe to that xiaomi bunny.
Problem Solved, and thanks for all of your effort. Maybe the suggestions helped! Who knows...
Click to expand...
Click to collapse
Glad to hear the good news.
FYI I flash miui in edl on a bi-monthly basis, just to refresh the partitions
So. I have used the unbrick tool several times before because sometimes I want to go back to out of the box factory. Locked bootloader, the whole nine. Well, it failed, so I unplugged it to try again, and no matter what I do, I can't get my computer to recognize that it's connected to the computer. I've been trying the holding volume up while plugging it in while in test mode. Like I said, I've used it before. I made sure I had plenty of battery life before I tried it, so I know the battery isn't dead. Do I need to look into getting another phone, or has anyone had a phone brick this badly and know how to fix it.
Just to rule out the obvious, have you tried different cable and computer?
gabriwinter said:
Just to rule out the obvious, have you tried different cable and computer?
Click to expand...
Click to collapse
Yeah. I've tried both of my laptops. Works perfectly on both for my s8+, but won't register my OP5 at all. I plug it in and nothing even shows up in device manager on both laptops.
godraistlin said:
Yeah. I've tried both of my laptops. Works perfectly on both for my s8+, but won't register my OP5 at all. I plug it in and nothing even shows up in device manager on both laptops.
Click to expand...
Click to collapse
I'm not very familiar with windows, you could try booting a Ubuntu livecd and typing in a terminal: dmesg
Then plug in the phone.
see if you can find any reference to the device being connected within the kernel messages.
How did you brick your OP in the first place? Does it still charge?
Z-Blade said:
How did you brick your OP in the first place? Does it still charge?
Click to expand...
Click to collapse
It bricked in the middle of using the unbrick tool. It literally doesn't do anything. No charging, no vibrations. Nothing.
gabriwinter said:
I'm not very familiar with windows, you could try booting a Ubuntu livecd and typing in a terminal: dmesg
Then plug in the phone.
see if you can find any reference to the device being connected within the kernel messages.
Click to expand...
Click to collapse
device descriptor read/64, error -32
That's the error I got. Problems with USB communication.
The fact it does not even charge sounds like a hardware issue. Even when its bricked it should at least charge.
godraistlin said:
device descriptor read/64, error -32
That's the error I got. Problems with USB communication.
Click to expand...
Click to collapse
This is an EPIPE error, this means the device is not answering the USB protocol requests and the pipe is broken.
In my experience this has always been due to a faulty cable, but in your case I'm afraid the device is juts not behaving as it should.
Next step would be to troubleshoot the hardware; This is not my area but maybe someone experienced can help out indicating what should be the next steps.
It may be that some small hardware parts could be replaced or the damage could be more severe.
Did you power down the phone then hold the power and volume down buttons at the same time to try and boot directly into recovery? If you can boot into recovery and have TWRP you could format the data on your phone using TWRP. That would erase everything on your phone except TWRP. Your computer would recognize your phone as an external hard drive and you could copy and paste a full ROM zip onto the phone memory and flash it with TWRP. If the tool you used installed the stock recovery I'm not sure what your options are but being able to boot into recovery would be a sign that your phone isn't actually hard bricked. Using automated tools to flash your phone is a really bad idea. It is much safer to flash manually.
I think there is close to zero chance that you have a hardware issue based on what you described. I've never heard of anyone hard bricking an OP5 so I think your phone is recoverable. If you can't figure it out a competent phone repair shop should be able to get you up and running again.
There's also One Plus tech support but if you try to get help from them I would probably just tell them your phone got borked after an update. If you tell them the entire circumstance they probably won't even try to help you.
Good luck.
Did you try holding power button for >40 seconds?
godraistlin said:
So. I have used the unbrick tool several times before because sometimes I want to go back to out of the box factory. Locked bootloader, the whole nine. Well, it failed, so I unplugged it to try again, and no matter what I do, I can't get my computer to recognize that it's connected to the computer. I've been trying the holding volume up while plugging it in while in test mode. Like I said, I've used it before. I made sure I had plenty of battery life before I tried it, so I know the battery isn't dead. Do I need to look into getting another phone, or has anyone had a phone brick this badly and know how to fix it.
Click to expand...
Click to collapse
If it's totalled then one plus will have no idea what is wrong either, send it back mate.
After reviewing all the replies, which won't work for you.
Way back in 2016, I faced the same issue with my op3. My issue was fixed by one of my friend by detaching the battery and reinstall the battery so that the board can boot. If that doesn't work for you, then suggest you to please check the type c connector funtionality.
dladz said:
If it's totalled then one plus will have no idea what is wrong either, send it back mate.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.
GAMIT PRUTHVI said:
After reviewing all the replies, which won't work for you.
Way back in 2016, I faced the same issue with my op3. My issue was fixed by one of my friend by detaching the battery and reinstall the battery so that the board can boot. If that doesn't work for you, then suggest you to please check the type c connector funtionality.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.
gabriwinter said:
This is an EPIPE error, this means the device is not answering the USB protocol requests and the pipe is broken.
In my experience this has always been due to a faulty cable, but in your case I'm afraid the device is juts not behaving as it should.
Next step would be to troubleshoot the hardware; This is not my area but maybe someone experienced can help out indicating what should be the next steps.
It may be that some small hardware parts could be replaced or the damage could be more severe.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.
jhs39 said:
Did you power down the phone then hold the power and volume down buttons at the same time to try and boot directly into recovery? If you can boot into recovery and have TWRP you could format the data on your phone using TWRP. That would erase everything on your phone except TWRP. Your computer would recognize your phone as an external hard drive and you could copy and paste a full ROM zip onto the phone memory and flash it with TWRP. If the tool you used installed the stock recovery I'm not sure what your options are but being able to boot into recovery would be a sign that your phone isn't actually hard bricked. Using automated tools to flash your phone is a really bad idea. It is much safer to flash manually.
I think there is close to zero chance that you have a hardware issue based on what you described. I've never heard of anyone hard bricking an OP5 so I think your phone is recoverable. If you can't figure it out a competent phone repair shop should be able to get you up and running again.
There's also One Plus tech support but if you try to get help from them I would probably just tell them your phone got borked after an update. If you tell them the entire circumstance they probably won't even try to help you.
Good luck.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.