Related
Hi all,
I have a 8125 (Wizard) that I bought used with a broken LCD - I replaced the LCD with hopes of having a functional phone, but I'm not quite there...
It WAS working as a nice little PDA for a while, with the newest Cingular ROM (2.25 I believe). HOwever, I received absolutely NO signal on the radio - the little animation just constantly went like it was forever searching.
So, in my newfound expertise in flashing HTC devices, I decided to flash this to a different ROM. First, I tried the one they call Button 1.05. No bones - it'd drop connection before even going to the tri-color.
Next, I tried the SlimEdition 2.2b of WM6 (I wanted to put WM6 on it anyway, and with this old of a phone, I'm keeping away from excessive gadgets). Same deal as the Button 1.05.
On to the Faria WM6 I found in another forum. This one didn't even find my phone.
Before suggesting I try doing the flashes more than 1 time, I did.. I've been trying to flash this thing for over a month...
Additionally (and probably part of the problem), when I connect the phone to my mini-USB (no, not HTC OEM) it establishes connection about 1/3 of the time....the rest of the time I get a "USB Device not Recognized" warning from XP - I then disconnect it and reconnect it until AS4.5 sees it.
Most recently, I tried putting the Button 1.05 on again, and actually made progress...sorta...
Once I got the RUU running, I actually got it to progress to 2% before the RUU declared a connection failure. Stuck in the RUU screen, I tried all the ROM's I have on this thing, and none get past 2%.
So, NOW, I have an 8125 that's stuck in the RUU screen. I dont know what I can try next, or what might be the problem - however, if anyone knows or has spare parts they're willing to donate to science (I can afford to pay the shipping - that's about it) then I would be most grateful. My initial thoughts are bad USB port or mainboard, but I haven't a clue where to get them.
Alternatively, if I dont hear from anyone soon with good news, I will be offereing for sale 1 hardly used LCD/Digitizer combo for what I paid for it. (approx $45 USD).
Summary (long post, eh?):
1> Can I get out of the tri-color RUU screen, or did it getting to 2% and then dying effectively brick this phone?
2> Anyone have suggestions on what to replace to prevent AS4.5 (or even Windows) from misdetecting the phone when connected via USB?
3> Anyone have parts for above-mentioned repairs/replacements? I'd be most grateful....
TIA!
- M
Follow up - next day (yes, next day)....
Apparently, the Forum Gods were watching over me as I spewed about my flashing issues......
I tried flashing it one more time, using the Slim v2 WM6 ROM....wouldn't ya know, the sunnovabatch worked....
Dunno why or what I did differently, but I dont want anyone pounding their heads trying to find an answer for this....
(I'll still take any donor phones, though...this one is 'better', but still not 'great')
Thanks for lookin!
- M
thats good to hear. say, how hard you think it would be to replace a usb port connector? mine is broken
collwatt said:
thats good to hear. say, how hard you think it would be to replace a usb port connector? mine is broken
Click to expand...
Click to collapse
Well, I've never replaced one myself, but it looks like it's just a few solder joints....
Can anyone confirm this? I dont want to mislead you by saying it's easy, in case it just looks easy, and really isn't.....
Also, I think I saw a thread elsewhere where someone had a bunch of the USB connectors that (s)he was selling....search here first - I'm pretty sure it'll be a better deal than you'll find on fleabay....
GL!!!
- M
hiya guys i recently bought a second hand hd2 after reading some reviews on how good it was so obviously i just had to start messing with it and coming from a htc wildfire was expecting things to be just as simple as root and install a rom wich after reading up went sweet as a nut took bot 30 mins total ......so heres the problem i was really impressed showed my phone off to every1 including my dad who was also impressed so bought 1 aswell (second hand so cant get a replacement as the phone is technically not broken) now for the last 4 or 5 days ive been trying to duplicate what ive done on my phone on his but cant get the damn thing recognized and before anyone says it lol ive tried everything i can fiind on the net about the issue ive tried diffrent usb ports on my pc wich is running win7 ive tried his pc also running win7 ....my laptop with winxp all usb ports from fresh install and another laptop running vista all with the appropriate programs wmdc and activesync for xp ......i have 7 usb cables diffrent makes but 3 are official htc including the original cable for hd2 (wich i used to flash my phone) and ive tried 2 of his including his original for hd2 ....reinstalled win6.5 using sd card method and still nothing apart from the fact it charges on every cable ive tried wich to me says that the usb port on the phone is fine it doesnt bring up the menu asking how i want to use the connection i.e charge activesync or mass storage (and ive got the option ticked to ask me....and ive tried deselcting fast connect) it just doesnt recognise the connection and windows doesnt respond at all to the phone being connected even in bootloader mode it stays on serial and doesnt change to usb..... everything radio, rom is the same now as when i did mine same cable but no connection ......i think that covers everything ive tried does any1 know off anything ive missed or know if theres a fix for this issue lmao sorry bout the essay just wanted to get accross that i think ive tried EVERYTHING thanks for taking the time to read
My guess,,, bent /broken/ missing pin in the phones USB socket, or connection fault in the associated wiring to the USB port, so data connection isn't being triggered but charging works because those two pins are fine.
Can try cleaning the USB port, a soft DRY toothbrush perhaps, give the port a close examination.
thanks for quick reply i did examine the port everything looked fine couldnt see anything bent in there a clean might help but looks ok to me thats the odd thing the phone looks new no damage to the port or phone and ive read about other people having the same issue but ive tried everything that has helped others with no success just wondering wether the phones a scrapper win6.5 definatly not a keeper lol
Lol ill take it off your hands before you "scrap" it. ...
Sent From My Fingers To Your Face.....
lol ive bin messing with it for days now feel like throwing it at a wall!! if i do ill let you know lmao
richlee007 said:
lol ive bin messing with it for days now feel like throwing it at a wall!! if i do ill let you know lmao
Click to expand...
Click to collapse
If the USB is the only issue you would probably still get a reasonable price for it on ebay.
Sent From My Fingers To Your Face.....
i think that the phone in general probably gets bought for the multiple o.s .....i know thats why i got mine yea the phone has some impressive upsides but i should have read the downsides this phone seems to be a accident waiting to happen dodgy usb, dead touchscreens, dodgy or sticky power buttons and getting bricked through normal usuage .... the list seems endless from what ive read in last few days ....my hd2 seems to have gone fine but just wondering how long its gonna last im scared to use it now lmao
I wouldn't worry about that. People are always gonna post their horror stories but not many come here to say ,
"Everything's fine, touchscreen hasn't died yet..."
If it reassures you at all, I've had mine since launch, its been dropped, flashed numerous times, got soaked in the rain, smashed into a fridge and the only thing wrong with her is a small dent on the bezel by the screen. I'd say it's a pretty resiliant device for what is essentially a 4" piece of glass....
Sent From My Fingers To Your Face.....
lol yea that sounds like some hardcore usage ......and yea i suppose as im looking for an actual problem or rather an answer to a problem with the phone only natural im gunna find other peoples problems
I beleive like Sam said your data transfer pins are not working. Especialy sense you said it does not ask if you want ActiveSync or Disk drive.
And without working data tranfer pins you will not be able to flash Android. You can flas MAGLDR and cLK via SD card, but you can not flash CWM or use fastboot commands without a USB connection. Sorry friend, best thing to do is flash a good custom Windows Mobile ROM to your dad's HD2 or get the USB fixed.
Hey guys thanks for the advice looks like he's getting custom windows rom lol anything for speed and useability improvements any suggeations for a good custom rom to try as I'm new tink the hd2 and a fan of android not too sure on the windows side of things
Sent from my HTC HD2 using XDA Premium App
Hi Everybody,
I believe that I am now in serious trouble with my Motorola Defy. I have tried to look everywhere today to find a similar problem to what I am experiencing, and although I can find all the problems, I can't find anyone which has happened like this. It would be so great if someone could help me. I am so so desperate and in total panic right now. I need this phone to work which I had bought in Germany (where my home base is set up) but I am currently working in Estonia where salary really does not allow me to just go out and buy a new one - not even a cheap 20€ phone.
I originally bought the phone about 1 1/2 years ago with Android 2.1. After about 6 months I did the official update to Android 2.2. This is where a few things started to go wrong. Google maps would crash the phone so that I would have to take the battery out to restart it. The camera didn't work properly, and not at all with the flash, and the phone would quite often restart itself. I could however live with all this and just accepted it as I didn't want to do anything to make it worse - I trust myself 100% with computers and there isn't much that I can't do with them. But with phones, that's where I have to put my hands up as I really don't trust myself to do anything because of the fear of bricking one.
Anyway, today as I was using the phone after taking a few pictures the phone had frozen, so as always I took the battery out and turned it on again, when it loaded up and as soon after I put my pin and unlock number in, it restart itself, So I again I put my pin and unlock number in, and it restarted itself. After this I couldn't even put my pin number in.
I then did went into Bootloader to do a wipe and restore, This however, after taking two hours and just watching the yellow dots move along, was clear to me that this also wasn't working. After coming home from work I then copied the instructions found I think in the Beginners Defy Guide on this site for using RSD Lite and an SBF File. This then failed and in Bootloader it also then said Corrupt.
So I then started to watch a video on youtube for a complete guide from unbricking to installing CM10 (something I wanted to do the whole time and never trusted myself). Meanwhile, whilst everything was downloading, although the phone still had about 60% battery, I thought I would plug it in just to charge it for a bit, this however also did not work but I left it in just in case it was working.
After everything was finished downloading, I unplugged the phone from the wall and now it won't even turn on,, neither in Bootloader, or the screen. It does NOTHING! :crying::crying:
When I plug it into the computer the little white led light comes on (top left of the phone) and the computer makes the sound that something is plugged in. This is also recognised my RSD Lite, however once a file has been created it cannot be flashed. It's like the phone is there, but it isn't.
I am really desperate to get this working as I really need this phone for work, and like I said just cannot afford to run and buy anything.
I'm very sorry if I have posted this in a wrong area, but I honestly did try to find something. I just don't understand how plugging it in to charge can stop it from not even opening bootloader, It's like it's got a mind of it's own.
Thank you very very much for reading, and I apologise that it's so long,
Best Wishes,
Steve
To get into the bootloader , keep the volume up button pressed and then press the power button. Is this what you tried to do?
And I didn't get the part where you wiped through the bootloader. As far as I know there is no option there. Do you mean the stock recovery?( The yellow dots are there in the stock recovery)
Sent from my MB526 using xda app-developers app
wahat3 said:
Hi Everybody,
I believe that I am now in serious trouble with my Motorola Defy. I have tried to look everywhere today to find a similar problem to what I am experiencing, and although I can find all the problems, I can't find anyone which has happened like this. It would be so great if someone could help me. I am so so desperate and in total panic right now. I need this phone to work which I had bought in Germany (where my home base is set up) but I am currently working in Estonia where salary really does not allow me to just go out and buy a new one - not even a cheap 20€ phone.
I originally bought the phone about 1 1/2 years ago with Android 2.1. After about 6 months I did the official update to Android 2.2. This is where a few things started to go wrong. Google maps would crash the phone so that I would have to take the battery out to restart it. The camera didn't work properly, and not at all with the flash, and the phone would quite often restart itself. I could however live with all this and just accepted it as I didn't want to do anything to make it worse - I trust myself 100% with computers and there isn't much that I can't do with them. But with phones, that's where I have to put my hands up as I really don't trust myself to do anything because of the fear of bricking one.
Anyway, today as I was using the phone after taking a few pictures the phone had frozen, so as always I took the battery out and turned it on again, when it loaded up and as soon after I put my pin and unlock number in, it restart itself, So I again I put my pin and unlock number in, and it restarted itself. After this I couldn't even put my pin number in.
I then did went into Bootloader to do a wipe and restore, This however, after taking two hours and just watching the yellow dots move along, was clear to me that this also wasn't working. After coming home from work I then copied the instructions found I think in the Beginners Defy Guide on this site for using RSD Lite and an SBF File. This then failed and in Bootloader it also then said Corrupt.
So I then started to watch a video on youtube for a complete guide from unbricking to installing CM10 (something I wanted to do the whole time and never trusted myself). Meanwhile, whilst everything was downloading, although the phone still had about 60% battery, I thought I would plug it in just to charge it for a bit, this however also did not work but I left it in just in case it was working.
After everything was finished downloading, I unplugged the phone from the wall and now it won't even turn on,, neither in Bootloader, or the screen. It does NOTHING! :crying::crying:
When I plug it into the computer the little white led light comes on (top left of the phone) and the computer makes the sound that something is plugged in. This is also recognised my RSD Lite, however once a file has been created it cannot be flashed. It's like the phone is there, but it isn't.
I am really desperate to get this working as I really need this phone for work, and like I said just cannot afford to run and buy anything.
I'm very sorry if I have posted this in a wrong area, but I honestly did try to find something. I just don't understand how plugging it in to charge can stop it from not even opening bootloader, It's like it's got a mind of it's own.
Thank you very very much for reading, and I apologise that it's so long,
Best Wishes,
Steve
Click to expand...
Click to collapse
Check out this link all the best :good:
Have not done much with rooting android devices in years and recently bought an Atoto A6 for a work van. I started messing around with it at home. Was able to gain root with Kingoroot and the replacing it with SuperSU. I emailed them about unlocking the bootloader but I'm not sure whoever responded even knew what I was talking about. Although ADB was working with system booted, I was not able to connect to the unit in fastboot. If you boot into recovery, it automatically runs an update and reboots. And if you boot into Fastboot with acc powered, fastboot automatically restarts. So using adb to reboot into bootloader and then removing power from acc would get me to a fastboot screen(although screen is off, putting power back to acc would show screen at fastboot mode) but I was never able to connect. I was trying different things to boot into an actual recovery, the A6 has no physical buttons, just a small hole for the reset. At some point it completely stopped responding. None of the sensor buttons light up and nothing on the screen. The micro sd I had in no longer works either. I did have update.zip backed up. Anyone know if there would be a way to use that to boot from a new micro sd or any other ideas to try, any help is appreciated.
The a6 has a mediatek mt8127. Was coming up as Alps A6. The build was alps/full_A6_series/A6_series:6.0/MRA58K/1506516231:user/test-keys . I did have it apart and have pics of the board, don't know if they would be useful though.
Upon further review, board mounted reset button was screwed up, all good now. Would be nice to figure out the bootloader on this, although I don't have it installed in a vehicle, this unit seems to run pretty well. Not a fan of the the launcher setup and appearance .
stabone00 said:
Upon further review, board mounted reset button was screwed up, all good now. Would be nice to figure out the bootloader on this, although I don't have it installed in a vehicle, this unit seems to run pretty well. Not a fan of the the launcher setup and appearance .
Click to expand...
Click to collapse
Glad you "unbricked" it, and glad somebody is willing to risk rooting it. That might go on my weekend project list, would appreciate more details on Kingroot and how you swapped it with SSU. I miss ad blockers, among other things.
I got the same unit from Amazon last week (2gb touch only version), but wish I had opted for the physical button model now.
My biggest complaint is the damned FM radio app, which by default comes on when it comes out of sleep, and there's no obvious way to disable it. The volume level on FM is like 2x streaming/MP3 volume so it blasts you when starting the car if you forget to turn volume way down when you get out. I'd love to know the actual app name so I could disable it entirely, since I never listen to broadcast radio anyway.
Oh, and the parallax on the thing is annoying, getting a finger lined up on small touch targets takes some practice.
Other than that issue, I'm not unhappy with the unit. 2-second boot is legit, and living in Florida and an open sunroof junkie, I'm especially pleased with the screen brightness.
Using CarWebGuru instead of the default Atoto launcher makes for a much better experience, and I like the fact that the Atoto controls on the bottom (home, back, multi-tasking, brightness, mute) all remain there no matter what launcher you choose.
Sound quality using my car's factory amp (via a Metra CANBUS harness) is surprisingly good too, I can't tell much difference between the A6 and the Pioneer FH-X730 it replaced at the volume levels I like, though there is some RF bleed from the SoC. And it's a near-perfect fit in a Schoshe double-din GM dash kit, there's not enough room for a toothpick around the edges of the screen and the dash kit inner bezel.
For rooting use KingOroot. You need the one for windows, the app on the unit itself won't do it. Then just google replacing kingoroot with Supersu, there are lots of threads about it. You could try the simple version but I ended up manually replacing files to do it, it's not bad at all. I wouldn't be to worried about bricking it, I have been trying all different things to get to a bootloader and at worst it re-updated and was working fine. What i did with the reset button, Ive done to othere devices, those surface mount buttons are junk. After doing a ridiculous amount of research, I found that MTK units don't enable fastboot. The preloader is what you have to get into to do anything, using mtk drivers. I could catch it right when its booting, installs the mtk vcomm drivers, but jumps right out. Once you are in that you need their flash tool, SDflash and there is MTKtools. So once thats figured out, i'm hoping to be able to get a custom recovery on. Without fastboot, it seems a bit more tricky, without that reset button I could be missing something simple. Hopefully more people start screwing with these, I doubt the people at Atoto are going to be of much help. So far tho, it seems like a decent unit. Let us know if you find out anything.
So far I was able to extract the boot and recovery img files. You can connect to the preloader using SP Flash by setting it up to read
Ima let you do the heavy lifting on this one Stabone.
For now, I'm just frustrated on the damn FM app opening at startup and it's nested in the Atoto firmware somewhere, not an isolated app.
One other quirk, on my car (with GM 11bit CANBUS), the illumination signal seems to be flipped from what Atoto is expecting...lights on means brighter screen, lights off means dim. I've tried it with both an Axxess and PAC CANBUS adaptor, so it's not the harness' fault. Just using the NONE setting for now and manually dimming the screen myself.
I sure hope stabone00 keeps working on this. I have been following this thread closely. I have been wanting to root this but I have it installed in the car now. why cant this be easy like a nexus 7. I am very afraid of bricking it and I really like the head unit
Not sure what happened to my last post, it should've been a bit longer then that, hah, oh well. Anyway I'm a little stuck here. After finding out as much as I did, I was going to try a few things. I'm running a dual boot laptop with opensuse as my main and a windows 10, for occasions as such, the tools used for this head unit are more abundant for windows(at least found easier). So recently I wiped my systems and now am having this Rsa Key Fingerprint issue when trying to connect with adb. I'm spending way to0 much time on this as it is, lol. But running into this bs is really pain. Now I've tried for hours to do something here but it's almost as someone's watching what i'm doing and countering my moves. Now I've factory reset this thing about four times and never lost root. After struggling with this rsa fingerprint issue, I did a factory reset and now SuperSu is gone, although I can't say for sure totally cause I still have not access to ADB. Any suggestions for the rsa issue, let me know, otherwise I'm not going to be wasting much more time with this. BTW, anyone getting anywhere with this, you need the modified version of MTK android tools to recognize this unit. I have boot and recovery img's and a scatter file if needed.
Got passed issue with adbkeys. Now I accidentally flashed a recovery when it was not ready. I am now stuck in a boot loop. Made lots of backups, but for some reason, none contain the preloader.bin. Not sure why that happened, but that is needed to flash backups with SP tools. If anyone could send me that, it would be great. I can't pull it cause I can't get it to connect to mtk droid tools. Maybe there is another way, but I don't know it.
stabone00 said:
Got passed issue with adbkeys. Now I accidentally flashed a recovery when it was not ready. I am now stuck in a boot loop. Made lots of backups, but for some reason, none contain the preloader.bin. Not sure why that happened, but that is needed to flash backups with SP tools. If anyone could send me that, it would be great. I can't pull it cause I can't get it to connect to mtk droid tools. Maybe there is another way, but I don't know it.
Click to expand...
Click to collapse
I have the same unit. If you can tell me how to pull it, I'd be happy to help.
smithkt said:
I have the same unit. If you can tell me how to pull it, I'd be happy to help.
Click to expand...
Click to collapse
Have you tried anything with it yet? There's quite a bit to it. The info is all searchable on here, you are looking for mediatek devices, sp flash tool, mtk droid tools. Let me know if you have adb and drivers installed. All the info needed for this unit is available , but there is a lot of info on mediatek devices, so it's a lot to look at. You need to have developers options enabled and oem unlocked and usb debugging on . If you can connect to your unit through adb, thats a start. Don't attempt anything with fastboot, it's not enabled on this unit. You'll then want to look for the modified version of mtk droid tools 2.5.3. If you are able to connect with that, I'll tell you what to do next. Not so sure my unit is recoverable, i've lost the startup atoto screen and can no longer connect with sp flasher. Hopefully there is something that can be done.
stabone00 said:
Have you tried anything with it yet? There's quite a bit to it. The info is all searchable on here, you are looking for mediatek devices, sp flash tool, mtk droid tools. Let me know if you have adb and drivers installed. All the info needed for this unit is available , but there is a lot of info on mediatek devices, so it's a lot to look at. You need to have developers options enabled and oem unlocked and usb debugging on . If you can connect to your unit through adb, thats a start. Don't attempt anything with fastboot, it's not enabled on this unit. You'll then want to look for the modified version of mtk droid tools 2.5.3. If you are able to connect with that, I'll tell you what to do next. Not so sure my unit is recoverable, i've lost the startup atoto screen and can no longer connect with sp flasher. Hopefully there is something that can be done.
Click to expand...
Click to collapse
No I haven't done anything with it yet. I wasn't planning on rooting the device. The only reason it's not in my car already is it's been 10-20 F and I don't have a garage. I have the thing sitting on my kitchen table so I can play with it.
I'll look through the info and see what I can do.
smithkt said:
No I haven't done anything with it yet. I wasn't planning on rooting the device. The only reason it's not in my car already is it's been 10-20 F and I don't have a garage. I have the thing sitting on my kitchen table so I can play with it.
I'll look through the info and see what I can do.
Click to expand...
Click to collapse
I have it hooked up with two switches, one feeds constant and other switch, and other switch feeds acc. Rooting it isn't too bad, but if you look into how the sp flasher is used, you could make a stock rom before doing it. I'm hoping there are test points on the board that can be used to get this flashed again. I'm not sure how it got this far gone. I had it bootlooping at the ATOTO startup, tried to flash the original boot and recover, seems like it wiped the preloader.
Have you had luck in unbricking your atoto?
I'm thinking about buying one also buy would like to root with kingroot and put a recovery into stereo if it's possible. Let me know your success is possible.
Thanks
Steven
scoolro said:
Have you had luck in unbricking your atoto?
I'm thinking about buying one also buy would like to root with kingroot and put a recovery into stereo if it's possible. Let me know your success is possible.
Thanks
Steven
Click to expand...
Click to collapse
So far it seems to be a very solid unit. Rooting it isn't an issue. I had been trying different things with this unit and at one point I thought it was almost unbrickable. It still might be, just haven't found a solution for my issue (which was completely my fault), although I'm pretty confident there is one. There is a lot of info about mediatek devices on here, a bit different approach when flashing a custom recovery.
Overall I was liking the unit, hadn't seen any issues some of the others had. Hope to see more people getting involved.
I hope you get the unit working soon.
I'm thinking about getting the same unit and I want to root it so I can get ADAWARE and XPOSED app installed. I'm also thinking about getting a Bluetooth media steering control for it also.
I've only seen the Atoto A6 on Amazon.ca for about $280. Hopefully there is another site that sells cheaper.
Again good luck and keep us informed with your progress if possible.
Steven
Atoto offered a to replace the unit with the PB model, as this one is no longer available. After doing as much research as I did, I am certain that this can be fixed. There should either be a way for force the preloader or get into a meta mode/ flashing mode. I'm going to keep it and see. I'm ordering the PB as soon as it is available again on Amazon.
So driving home from work today, I noticed an update pending for the A6. Was in a good coverage area (using a MiFi hotspot, btw, not my phone), downloaded it at a long stop light, hit install, and after reboot, I got the dead Android ERROR! graphic. About **** myself, thought I might have bricked it. At the next red light, I did a reset (I keep a slim toothpick in the console now, for just such emergencies) and I'm back to the old November build.
I ended up sending my 62721p back and am waiting for the pb model.
Did you have it rooted?
stabone00 said:
I ended up sending my 62721p back and am waiting for the pb model.
Did you have it rooted?
Click to expand...
Click to collapse
Nope, couldn't be assed, it's basically a Poweramp/Waze/Spotify machine for me now, figured I don't need root for that, and all the cool root-level stuff the Rockchip and Sofia units get isn't available for this thing anyway.
Did get the update to stick the second time around, but noticed no changes in functionality. MCU got updated as well.
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.