Related
Hi,
I managed to brick my Milestone, terminally I'm afraid, but the symptoms are different than what I see around the forum so they might interest someone else.
So, I first backed up everything with GOT Nandroid and Titanium Backup then modded CyanogenMod 7 RC4 0.08-11.04.05 (Android 2.3.3) successfully, except that the SIM was locked and would not unlock, although it works in another phone. This was a bug supposedly fixed in version 6 of Cyanogen...
Browsing the forums, the only thing that made a bit of sense was that maybe the GSM frequency was set to the wrong value. There is a Nandroid mod (but not GOT) that allows you to change that so I entered GOT Nandroid again. Since it had no such option, I Rebooted. Then, the fun begun.
The phone got stuck on the Motorola logo and no button, not even Power, worked anymore. After waiting for many minutes with no progress, I took out the battery - that made a change , the phone shut down. I then put it back - the phone immediatelly, no, instantly, cause there's no delay as when you were powering it up, lights up with the same Motorola logo. Tried several times, always the same behavior.
I left it booting (but also connected to the charger) for a whole night, no change.
The phone is not seen by the PC when connected to USB. It won't reboot, normally or to recovery. Buttons won't work at all. Yeah, tried with or without the SIM and the sdcard, no change. Tried to start without battery, just the charger, doesn't work.
Useless to say, I am getting bored of that Motorola logo
I suspect that the bootloader in the internal memory got corrupted. Can this be flashed even if the device is not seen by the PC (I mean by the RDSLite installed on it)?
Cheers
When the charger is connected to the phone try at the same timeull out and pull in the battery while holding the buttons who will get you in the OR
Yup, it worked. So first I got the battery with a question mark. Then I put in the battery and I got a battery at 60%. Since I was holding Power+Camera, it continued to the Recovery mode and now I have a working Milestone with Cyanogen mod!!
Thank you a lot, Mikicishte.
I still have to see about the initial locked SIM problem... but that will be mostly fun.
florinadrian said:
I still have to see about the initial locked SIM problem... but that will be mostly fun.
Click to expand...
Click to collapse
Have you tried to factory reset the Milestone, to see if after that the SIM is accessible again ?
http://forum.cyanogenmod.com/topic/14099-sim-card-not-detected-after-factory-reset/
You could try also to install a logger application catlog for example (https://market.android.com/details?id=com.nolanlawson.logcat&feature=search_result ) to see in the logs if you can find out more details to help you with the investigations...
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
florinadrian said:
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
Click to expand...
Click to collapse
or maybe you could try to use an unlock tool to see what error is reporting
https://market.android.com/details?id=com.droidgram.bladeunlock&feature=search_result
I was attempting to flash the ICS4 ROM. I had formatted /system and was done with installing the from from zip. Before I could do anything else, the phone just stopped being responsive. I pulled and restored the battery but the phone will not boot up. What to do now, short of going to my VZW store?
When you say it doesnt boot.. what exactly do you mean? Does anything come up on the screen?
nothing comes when you press the power button, screen remains blank.
ronaldheld said:
nothing comes when you press the power button, screen remains blank.
Click to expand...
Click to collapse
Did you try booting up into recovery and then going to fastboot and reinstalling the stock fxz file to see if that fixed it?
Sure the battery didn't die also?
The phone does not boot into recovery. Pressing the power button does nothing at all, as far as I can see.
I found out that the phone is literally fried. Whether the ICS4 ROM contributed is unknown.
You are most likely covered under manufacturer warranty - seems like a hardware failure. Never known of a ROM flash to fry a phone's board.
They also most likely won't know you even tried to flash a custom ROM.
That part is very good to know.
I will have restart again with rooting, and proceed with flashing Eclipse 2.2.
Is the place you live in very statically charged? When you touch metal do you get shocked alot?
If you touched the battery ports it could have discharged into the phones board and killed it.
Let us know what they do for you.
ronaldheld said:
That part is very good to know.
I will have restart again with rooting, and proceed with flashing Eclipse 2.2.
Click to expand...
Click to collapse
Compared to everything else we do here at XDA, the process to get rooted and flash a ROM is very basic. Getting the phone back up and running is the more difficult part.
What I can say to try is attempt to use a different battery. I had a problem once where both of my batteries functioned properly because I was able to test them in other phones. But when I placed that specific battery into my phone, it wouldn't boot up. I ended up using a different battery and was then able to boot into AP Fastboot and fxz to fix it. Then my "dysfunctional" battery worked properly again.
I have a droid 4 that ended up with bad software. Simple issue is I got no bootloader, no power, no nada. When I connect a regular USB i get a green light in the corner but no activity and no detect. Needless to say, bootloader is corrupt at this point. Sent it back to Moto Repair and they claim physical damage (though I know for a fact there is none) so I'm looking to Flash the bootloader myself. I'm aware it's going to have to be a low level NAND flash. Anyone familiar with this process? Computer does not detect. Does anyone have the latest A.074 Bootloader file I can grab? Need to get this guy running. Any help would be greatly appreciated.
Thanks
Oh, and yes I have a factory programming cable if I can make use of it somehow......
queberican351 said:
I have a droid 4 that ended up with bad software. Simple issue is I got no bootloader, no power, no nada. When I connect a regular USB i get a green light in the corner but no activity and no detect. Needless to say, bootloader is corrupt at this point. Sent it back to Moto Repair and they claim physical damage (though I know for a fact there is none) so I'm looking to Flash the bootloader myself. I'm aware it's going to have to be a low level NAND flash. Anyone familiar with this process? Computer does not detect. Does anyone have the latest A.074 Bootloader file I can grab? Need to get this guy running. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
How did the bootloader get corrupted? I was under the impression the phone would not allow you to flash another bootloader unless it was signed... You should ask Moto what was physically damaged, if it was a simple flash they should be able to fix it easily for you.
NEED DD
That was my thoughts exactly. But they claim liquid damage. I've since then opened the phone and inspected all the stickers....no sign of liquid damage. I would think a 2 minute bootloader flash wouldn't constitute this much despair (on Motorola's part) but such is life. Now I'm just looking to get the first couple Mb in a device dump so I can write it to an sdcard and attempt to boot from there and repair the bootloader. It has to be a device dump from a D4 running the a.074 bootloader. Any takers?
You could try looking in the fastboot files, they're on the Droid 4 development boards, they have both Gingerbread ones
D4 6.16.215 MBM files
Here are the D4 6.16.215 mbm.bin and other low level boot files from the leaked OTA update.zip.
I don't think they are going to help you given that there is no way that I am aware of to boot from the sdcard on a Motorola device.
There is a USB boot option for loading a factory I/O image(pre firmware basic input/output interface), but I don't know how you would initialize it nor do I have the factory image for the D4.
It is most likely a touchpoint on the board that needs to be shorted while the factory cable is inserted and that would bypass the EMMC and initialize the USB boot.
I am just guessing here...good luck!
if you somehow unlock it too, let us know what you did
SD Card boot didn't work and couldn't get it to detect on my windows or linux pc's. Therefore OMAPboot was out of the question. So I parted it out. I've acquired another D4 and I'm curious as to what if any advancements have been made on getting them to work on US GSM carriers? If we're still stuck I'm more than willing to jump into Dev on this and open to suggestions. My new D4 is running bone stock GB. I'm going to keep looking into the SD or USB possible fix's for hardbricks.
Thanx for the replies and thanx to [mbm], Jonpry, PhareignQ (think I mightta spelled that wrong), and HashCode for their knowledge, help, and suggestions along the way.
Hey man! You're the second one with same issue. I'm looking to buy new motherboard for droid 4 with same crapped bootloader + broken cdrom partition
For those who is interesting in, motorola factory cable doesn't work with droid 4 for some strange reason.
I can attest to the fact that the factory cable does, indeed, work with the D4 just like the Razr and other Motorola models.
I am not sure why yours doesn't or what condition your phone is in at this point, but the factory cable will power the device directly, bypassing the battery/charging circuit and allow you to flash it as long as the bootloader and mbmloader are not corrupt.
In that case, when the mbmloader fails, then nothing happens on the device at all unless a factory cable is connected, then it will flash the LED white just once as the cable is inserted and then loop continuously trying to load an interface and fails. The screen does nothing and the device is dead except pressing all 3 hardware buttons will arrest then restart the cycle of failed interface initialization once released.
I have a Razr in this state that I unfortunately attempted to flash some unknown files we received that we foolishly believed may have been an OEM bootloader unlock.
If you flash a corrupt image to the mbmloader the device is toast, AFAIK, although I do believe they have ways to recover them and in the past those methods often involved shorting a set of pads on the board with a paperclip while inserting the factory cable, initializing a timed event where the EMMC was bypassed and and factory I/O file could be loaded via a USB boot option.
I don't know if any of these methods could actually save any of our phones in this state, but I would like to believe its possible!
I just wanted to clarify about the factory cable.
Yup, what @Cellzealot said. I've removed the battery from the D4 and the factory cable works as intended. To be frank I had a moment of ignorance. I had just gotten my D4 (used) and was attempting to try and find a solution for the US GSM band unlock. In reading through the post about the Bionic I found that there was alot of talk about needing to be on bootloader 0A.72 or something to the fact of having success with that. The kid I got it from had already installed the ICS leak. So I paid no attention to the fact that the bootloader on MY phone was 0A.74....so I opened RSD and attempted to send mbm and mbmloader from 0A.72. It failed and that was the last thing ever "sent" to that phone. As soon as I disconnected it the phone powered down and never did anything after that.......
So I pursued the Boot from SD theory to no success, though I believe it is plausible, however probably still required a short to enable it. And Linux and Windows wouldn't even detect the OMAP4430 (as I've heard some people had luck with). So OMAPboot (boot from usb) was out too.
Finally got another D4, and being the phone soldier I try to be, Went right back to town attempting to get this thing to run on AT&T. So far no luck. I've been trying radio's and rom's from different devices and brandings that are running 2.3.6 (I left this one on the stock Gingerbread)
Willing to undertake any suggestions as long as "bootloader" is nowhere in the equation,
queberican351 said:
Yup, what @Cellzealot said. I've removed the battery from the D4 and the factory cable works as intended. To be frank I had a moment of ignorance. I had just gotten my D4 (used) and was attempting to try and find a solution for the US GSM band unlock. In reading through the post about the Bionic I found that there was alot of talk about needing to be on bootloader 0A.72 or something to the fact of having success with that. The kid I got it from had already installed the ICS leak. So I paid no attention to the fact that the bootloader on MY phone was 0A.74....so I opened RSD and attempted to send mbm and mbmloader from 0A.72. It failed and that was the last thing ever "sent" to that phone. As soon as I disconnected it the phone powered down and never did anything after that.......
So I pursued the Boot from SD theory to no success, though I believe it is plausible, however probably still required a short to enable it. And Linux and Windows wouldn't even detect the OMAP4430 (as I've heard some people had luck with). So OMAPboot (boot from usb) was out too.
Finally got another D4, and being the phone soldier I try to be, Went right back to town attempting to get this thing to run on AT&T. So far no luck. I've been trying radio's and rom's from different devices and brandings that are running 2.3.6 (I left this one on the stock Gingerbread)
Willing to undertake any suggestions as long as "bootloader" is nowhere in the equation,
Click to expand...
Click to collapse
Any solution on black screen and broken bootloader?
Here I have black screen with AC adapter connected. If I connect the phone to PC, I have green led indicator, but still black screen. Buttons have no reactions.
Anything new? Two users on a German bulletin board do have the same issue. I will get one Droid 4 of them in the next few days to have a look at it. But this thread sounds like there is no solution?
http://db.tt/u31VG45D
http://forum.xda-developers.com/showthread.php?t=2055839
The first link is to the most recent level 4 bootloader repair kit that we have for the Maserati/Droid 4 which is 0a.6c from pre ICS builds.
It is possible you may be able to use the pbrdl.bin and brdl.bin from those files with the mbmloader.bin and mbm.bin from a more current build to restore your device.
Again, these files are a year old now and may not work but you have little to lose in trying.
Use the method in the second link in Linux to try to restore your bootloader with the omapflash-lnx binary from that thread.
This is very likely to fail if the device has a recent firmware build on it but we don't have any of these repair kits for the newer bootloaders.
Good luck!
Thanks.
I got one of these phones. But it isn't even recognized via USB So I can't use these tools...
Is there any way to flash it via JTAG/ISP/...? Maybe this is the last chance - or this phone is dead ^^
I am running Infected's CM12.1 ROM on my Yuga, and it's been working great, but just yesterday, my phone restarted without warning and optimised all the apps (200 of them), right when it says "starting apps", it restarts again and did this until the battery drained out.
I cannot enter recovery at all. I have TWRP installed on the FOTA partition, but I cannot access that. When I'm holding the volume down key on the reboot, it just skips straight to the CM logo.
While it's optimising apps, I can see the phone in adb, but it's unauthorised, so I cannot run any commands to it.
I can reboot the phone into fastboot, but apart from reflashing the boot.img (which I already did) I don't know what else to try.
I think all the buttons are working, but I saw that the water pads are red underneath two of them. I think there may be water damage, but am not sure.
I'm out of ideas and would very much appreciated if anyone can help me bring my beloved phone back.
Lohot said:
I am running Infected's CM12.1 ROM on my Yuga, and it's been working great, but just yesterday, my phone restarted without warning and optimised all the apps (200 of them), right when it says "starting apps", it restarts again and did this until the battery drained out.
I cannot enter recovery at all. I have TWRP installed on the FOTA partition, but I cannot access that. When I'm holding the volume down key on the reboot, it just skips straight to the CM logo.
While it's optimising apps, I can see the phone in adb, but it's unauthorised, so I cannot run any commands to it.
I can reboot the phone into fastboot, but apart from reflashing the boot.img (which I already did) I don't know what else to try.
I think all the buttons are working, but I saw that the water pads are red underneath two of them. I think there may be water damage, but am not sure.
I'm out of ideas and would very much appreciated if anyone can help me bring my beloved phone back.
Click to expand...
Click to collapse
Have you tried flashing stock FTF ?
You would need FTF from general section and also flashtool which you can get from here. Make sure the FTF is device specific or your would end up bricking up your phone
http://www.flashtool.net/index.php
You can search xda for how to use it. If you still have questions, quote me and I would be glad to help
Hi,
Thanks for helping me out. I tried reflashing a few different ROMs using flashtool, including stock, but nothing helped.
In the end, I bit the bullet and gave it up for dead. The good news was, since the cause seemed to be water ingress, it was covered by my insurance, and so I was given a replacement!
Thanks again for your help.
Hnk1 said:
Have you tried flashing stock FTF ?
You would need FTF from general section and also flashtool which you can get from here. Make sure the FTF is device specific or your would end up bricking up your phone
Click to expand...
Click to collapse
Lohot said:
Hi,
Thanks for helping me out. I tried reflashing a few different ROMs using flashtool, including stock, but nothing helped.
In the end, I bit the bullet and gave it up for dead. The good news was, since the cause seemed to be water ingress, it was covered by my insurance, and so I was given a replacement!
Thanks again for your help.
Click to expand...
Click to collapse
There's nothing sweeter than using a phone for a long time and getting a brand new !
Enjoy mate. No trouble. Just quote me again in case you have any query for me.
Hello!
Just today I bought myself a second-hand Oneplus 3T that had issues booting into the system. The start of the boot animation would show, but after that the screen just goes black and a white notification light turns on. Confident in my basic skills, I bought it and started trying things.
It boots into recovery and fastboot, all nicely, so first I tried wiping everything with stock recovery and then installing OOS that I downloaded from oneplus. Installed it through the stock recovery ADB Sideload, didn't change a thing. So since the bootloader is locked and cannot be opened, I went on to tryin the Qualcomm 9008 unbrick. Went through with it got a green text in MsmDownloadTool and all, but still nothing. Tried to install that same OOS on this "fixed boot partition" but the only change I noticed that I couldn't even get the start of the boot animation. Just the oneplus logo splash screen and black with white light after that....
If the device is powered down it shows the offline charging screen and a green notification light.
The device is out of warranty, I need the help of you people.... I might try installing twrp and formatting the system partition and installing on that, that is if I can get twrp installed in this kind of a situation.. Thanks!!
EDIT; Tried installing twrp, of course cannot flash it through fastboot but I also tried tricking MsmDownloadTool to install twrp instead of stock to no avail. I got the boot animation starting back but nothing else, also clicking "Install from internal storage" in recovery does absolutely nothing, doesn't bring up a file explorer like I would have expected..
Have you tried the Qualcomm MSMtoool to completely reinstall OOS? That may work. Don't try to install TWRP through the MSM tool.
This is an usual brick that takes place when someone has tried to relock the bootloader when a ROM/Recovery has been flashed which is not signed by OnePlus. It has been solved many times, so please do a search on XDA and OP Forums before posting a new question.
thes3usa said:
Have you tried the Qualcomm MSMtoool to completely reinstall OOS? That may work. Don't try to install TWRP through the MSM tool.
This is an usual brick that takes place when someone has tried to relock the bootloader when a ROM/Recovery has been flashed which is not signed by OnePlus. It has been solved many times, so please do a search on XDA and OP Forums before posting a new question.
Click to expand...
Click to collapse
Man I searched for this kind of brick for a few hours, only found a couple, one on xda and another on oneplus forums, and those didn't get solved. The MSM tool package I'm using does write the system.img so I guess it at least tries to install OOS.... Could you point me in the direction of similar brick situations? This doesn't get fixed by wiping any partitions..
Thanks!
MrMatson said:
Man I searched for this kind of brick for a few hours, only found a couple, one on xda and another on oneplus forums, and those didn't get solved. The MSM tool package I'm using does write the system.img so I guess it at least tries to install OOS.... Could you point me in the direction of similar brick situations? This doesn't get fixed by wiping any partitions..
Thanks!
Click to expand...
Click to collapse
I'm guessing you used this guide (https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) and you did install the drivers correctly yeah?
What error do you get when you MSM tool tries to flash the images? Is it the Sahara error?
Try another computer, or switch USB ports. Also try to download the firmware packages by yourself, and select it from the MSM tool. Also try to let the in-program download flash.
Try going into Fastboot and erase everything, from Internal Storage to the System partition, and then re-try the MSM tool.
thes3usa said:
I'm guessing you used this guide (https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) and you did install the drivers correctly yeah?
What error do you get when you MSM tool tries to flash the images? Is it the Sahara error?
Try another computer, or switch USB ports. Also try to download the firmware packages by yourself, and select it from the MSM tool. Also try to let the in-program download flash.
Try going into Fastboot and erase everything, from Internal Storage to the System partition, and then re-try the MSM tool.
Click to expand...
Click to collapse
Bootloader is locked, nothing can be done through fastboot. I get no errors in MSM, it's just this white light brick when booting to the system. I found a third guy on page 46 of that thread (that's a bit of reading) who had a similar sounding issue. He got it fixed by using a newer MSM version I believe. I am currently downloading the one he said he used. So far I've tried 2 diffrerent MSM packages so far. One other guy in that thread said that the white light should mean a kernel panic... I really hope I can get it working
How can I choose what firmware MSM installs? Or is that even what you mean by "download the firmware packages by yourself, and select ir from the MSM tool"?
I appreciate your help. This really is a frustrating kind of error.
MrMatson said:
Bootloader is locked, nothing can be done through fastboot. I get no errors in MSM, it's just this white light brick when booting to the system. I found a third guy on page 46 of that thread (that's a bit of reading) who had a similar sounding issue. He got it fixed by using a newer MSM version I believe. I am currently downloading the one he said he used. So far I've tried 2 diffrerent MSM packages so far. One other guy in that thread said that the white light should mean a kernel panic... I really hope I can get it working
How can I choose what firmware MSM installs? Or is that even what you mean by "download the firmware packages by yourself, and select ir from the MSM tool"?
I appreciate your help. This really is a frustrating kind of error.
Click to expand...
Click to collapse
As I'm aware, you can select packaged files which you have downloaded. It is basically the same file the MSM tool downloads, but it could be a higher version. (I.E: MSM tool downloads OOS 3.5.6 by default, but you could flash a file which you downloaded yourself, which can be OOS 4.0 or so.)
Correct me if I'm wrong, I've only used the MSM tool once or twice, and I'm speaking from reading about it on other threads.
Don't panic, your phone can get into fastboot and recovery, so you can definitely save it. Its just a little annoying, but it's not like its a Samsung device. I've myself had the white light. It can be easily fixed.
Supporting each other is what a community is for. Helping each other is what we do.
Good luck, and update us on what happens.
Update: Tried versions 3.0.6 and 3.0.8 of MSM in addition to the version 3.0.0 I had before. No luck. I'm starting to feel like I've tried everything there is to try... The device works everywhere else like it should, it just doesn't boot into system. Recovery and fastboot and Qualcomm mode are available, just can't seem to fix this with those... I need some help
It could be some sort of hardware damage. Following liquid ingress, my oneplus 3t had the exact same symptoms. The problem in my particular case happened to be with the board with audio jack on it at the bottom, I could use the phone normally (without hardware keys/fingerprint scanner) by disconnecting and blocking the two connectors for those components, until a replacement board arrived. The board cost me £8.50. There could be loads of reasons for this blank screen and white LED though, gluck mate!
hey bro, im facing the same with you on my 2nd hand 3T. almost all rom i tried cant fix that problem, but i got some fix when i flashed RR Sultanized.
- UBL
- flash latest TWRP or blu_spark TWRP recovery
- wipe everything
- follow carefully with this link to flashing RR Sultanized
- flash gapps (im using aroma gapps, pico is recommend)
- boot system to make sure everything is good
- install wakelock from playstore, choose partial wake lock (without this you will get random reboots or shutdown, but white led is gone on mine)
- restart system
- then magisk to root if you like
so far this is saved my poor 3T, good luck bro
sorry for my bad grammar
bluuquthug said:
hey bro, im facing the same with you on my 2nd hand 3T. almost all rom i tried cant fix that problem, but i got some fix when i flashed RR Sultanized.
- UBL
- flash latest TWRP or blu_spark TWRP recovery
- wipe everything
- follow carefully with this link to flashing RR Sultanized
- flash gapps (im using aroma gapps, pico is recommend)
- boot system to make sure everything is good
- install wakelock from playstore, choose partial wake lock (without this you will get random reboots or shutdown, but white led is gone on mine)
- restart system
- then magisk to root if you like
so far this is saved my poor 3T, good luck bro
sorry for my bad grammar
Click to expand...
Click to collapse
He said in OP he can't flash TWRP.
krombopulos said:
It could be some sort of hardware damage. Following liquid ingress, my oneplus 3t had the exact same symptoms. The problem in my particular case happened to be with the board with audio jack on it at the bottom, I could use the phone normally (without hardware keys/fingerprint scanner) by disconnecting and blocking the two connectors for those components, until a replacement board arrived. The board cost me £8.50. There could be loads of reasons for this blank screen and white LED though, gluck mate!
Click to expand...
Click to collapse
Yup, cannot flash twrp throguh ususal means... But you saying you had a similar problem, phone wouldn't boot with those parts connected, but did go just fine with them disconncted? If that's the case, I will start trying it with different parts. I really want to get this thing working! Thank you for both of your inputs!
bluuquthug said:
hey bro, im facing the same with you on my 2nd hand 3T. almost all rom i tried cant fix that problem, but i got some fix when i flashed RR Sultanized.
- UBL
- flash latest TWRP or blu_spark TWRP recovery
- wipe everything
- follow carefully with this link to flashing RR Sultanized
- flash gapps (im using aroma gapps, pico is recommend)
- boot system to make sure everything is good
- install wakelock from playstore, choose partial wake lock (without this you will get random reboots or shutdown, but white led is gone on mine)
- restart system
- then magisk to root if you like
so far this is saved my poor 3T, good luck bro
sorry for my bad grammar
Click to expand...
Click to collapse
Yea... I got my bootloader locked so no luck there... Thanks anyway!
MrMatson said:
Yea... I got my bootloader locked so no luck there... Thanks anyway!
Click to expand...
Click to collapse
Yeah You need to UBL first bro, try via fastboot to flash twrp.
Im using msm tool first, then flashing OOS, next UBL
I don't think UBL will help either, as I am stuck on stock reocevoery.
Update: https://forum.xda-developers.com/general/rooting-roms/installing-twrp-locked-bootloader-t3669879 this guy seems to have succeeded in doing what I tried on a Xiaomi phone. I don't know if it's possible to replicate on a oneplus though... No luck so far
MrMatson said:
Yup, cannot flash twrp throguh ususal means... But you saying you had a similar problem, phone wouldn't boot with those parts connected, but did go just fine with them disconncted? If that's the case, I will start trying it with different parts. I really want to get this thing working! Thank you for both of your inputs!
Click to expand...
Click to collapse
That's right, the phone would boot normally and was usable with the two flexes disconnected, I just had to active a software navbar. TWRP would work normally with them connected, I think that's because the hardware keys/fingerprint scanner aren't active in recovery.
my friend op3 also had similar problem, the problem only occur after changing camera module. change back to original faulty modules seems fixed the issue. after he order other camera module and assemble it back, the device worked normally, it seems that any hw dmg will prevent the phone from booting system.
krombopulos said:
That's right, the phone would boot normally and was usable with the two flexes disconnected, I just had to active a software navbar. TWRP would work normally with them connected, I think that's because the hardware keys/fingerprint scanner aren't active in recovery.
Click to expand...
Click to collapse
Oh... As I have stock recovery, the back key can be used to go back, and it seems to work... Well, any hardware modifications will have to wait, as I do not have a T2 driver and there seems to not be a single one in stock in Finland anywhere, gotta wait out on one from china.... But maybe trying some other parts will work The navigation keys also light up briefly when booting, for a second or so. Thanks!
krombopulos said:
That's right, the phone would boot normally and was usable with the two flexes disconnected, I just had to active a software navbar. TWRP would work normally with them connected, I think that's because the hardware keys/fingerprint scanner aren't active in recovery.
Click to expand...
Click to collapse
koax88 said:
my friend op3 also had similar problem, the problem only occur after changing camera module. change back to original faulty modules seems fixed the issue. after he order other camera module and assemble it back, the device worked normally, it seems that any hw dmg will prevent the phone from booting system.
Click to expand...
Click to collapse
Thanks to you, I have that tingling sensation of trying again! I hope this is not on the motherboard, everything else I can manage.... Just gotta survive the wait for my T2 screwdriver..... This is a nice feeling
MrMatson said:
Thanks to you, I have that tingling sensation of trying again! I hope this is not on the motherboard, everything else I can manage.... Just gotta survive the wait for my T2 screwdriver..... This is a nice feeling
Click to expand...
Click to collapse
Just curious, did the seller give you any information about why the device was bricked?
Cause if he was just trying to modifying the software without knowing what he was doing you should have resolved it by now, as MSM-download-tool does not show specific errors I assume it's able to write software correctly to the corresponding partitions but then something prevents it from booting up to android system, unfortunately the chances for any hardware related problem are definitely there, even very likely...
So if you bought the device assuming a software related problem but got a hardware defect it could look just the same from outside, only further possibilities I see is by having a look inside and even then you'll need some luck finding the issues...
Don't know if you have one of these little phone repair shops around but they're helpful sometimes getting advice about hardware, etc. also YouTube is a great resource for tutorials...
Just my 2 Cents, good luck
- hope you succeed in the end!
Sent from my OnePlus 3T using XDA Labs