Related
My wife left the window open near my only laptop that have, and a thunderstorm came through.......well you no the rest. Dead laptop after it completly dried, I get power but a driver is stuck in loop mode, so only the boot screen shows up. Well my question is do anybody on xda developers no how, or no anyone who knows how to change roms using only a wizard. I have a t-mobile mda (waiting for the fall for new pocket pc releases) with current wm6 rom crossbow reloaded 1.7. Would like to change to mfrazz xda6 (the real wizard window mobile 6 rom from ngenetics) rom. I thought I read somewhere that someone changed there rom with their pocket pc from the SD card. Please read my question thoroughly. I no theres a method by using a card reader and entering bootloader.....and so on, and so on. I have no access to any type of computer ( until I buy a new one ), and I need instructions or someone point me into the direction for changing my rom with just my pocket pc. I will continue to search forums, google, or whatever myself until we get and answer to this. Thank you all for reading my new post, and helping out in any form or fashion. Oh yeah I forgot to mention; please do not post or respond with any negativity. I no it say junior member ( noob) next to my users name , but i'm a grown ass man so respect me like one. Remember i'm the senior noob.
This is a little off topic, but have your tried booting your laptop and then pressing the F8 key before the Windows boot screen is displayed? From this screen you can try the "Last Known Good...." or try to boot into safe mode. If that doesn't work, you can try booting from your Windows CD and doing a repair installation of windows? If you can get power and it sticks at the boot screen, then some of your boot files may be corrupted. I'm assuming that you have Windows XP. Hope this helps. I don't know anything about flashing ROMs from the SD card, but have heard something about that in this forum or HoFo.
STOP TRYING TO TURN IT ON!! you're making it worse. trust me.
i work as a computer technician, i fix machines that have been spilled on all the time.
shut it down, take it somewhere to have it fixed. it might be dry on the OUTSIDE, but the inside is either
1.) still wet
2.) corroded chips that are shorting out
the only way to really tell, is disassemble it. take everything apart, REMOVE ALL ELECTRICITY to the computer, and check to see where the liquid is and what damage it has done. if you see corrosion spots, get a soft bristle tooth brush, run the part under water and use mild soap to brush it off. rinse it off, then let it dry for 48 hours minimum.
do not do this with the hard drive, optical drive, or LCD - just PCBs.
i've had dozens of computers come to me that had an entire cup of soda/beer/tea/coffee/water, etc. on it and was able to get it working. Water is the easiest to fix, as there are no sugars or anything to bond to the components.
its not the liquid that causes the problem, its the electricity running through it.
lol at this point i think im more worried about your laptop, and i am pretty sure there is a way to boot off of an sd card but im not sure, im sure somone here will know
h4ck must be a member of the geek squad!
my sony vaio laptop
when I saw my laptop it was soak and wet. I removed the keyboard pad, and unscrewed all the screws. Yes there was water on the inside, and I tried to dry it as much as possible. Went on vacation came back three weeks later. Before there was no power, when I return home I turn on my laptop and voila, it comes. I hit the f8 key and started it from its last known good config. System restarts but a small blue screen appears, then disappears. So I return to the bootscreen option and started it up in safe mode with networking. Everything came on in safe mode in a smaller screen size. I went to start/computer system/vaio recovery. Now this is were I messed up. Insted of using the last good config. check point, I used complete system recovery back to its normal state the way I bought it. all programs and software will be deleted.(just like a hard reset for pocket pc). It did a complete recovery of my hard drive c, and restore everything to factory settings. Now when it restarts a message says its missing some files and to repair this hit the "r" key and insert the windows xp cd-rom disc. I did this but it won't boot from the hard disk for some reason. Then after some time from trying to boot from the cd-rom disc, a small blue screen appears with the message: "A problem has been detected and windows has been shut down to prevent damage to your computer. The problem seems to be caused by the following file: ati2dvag. The device driver got stuck in an infinite loop. This usually indicates problem with the device itself or with the device driver programming the hardware incorrectly. please check your hardware device vendor for any driver updates. technical information: *** stop: 0x000000EA (0x81cB2440, 0x81E0A440, 0xF896DCB4, 0x00000001) ati2dvag- beginning to dump of physical memory-physical memory dump complete. Contact your system administrator or technical support group for further assistance." Sorry guys for the long story but thats everything. I know this is a forum about PDA's but i'm just responding to the response. By the way have anybody found anything yet?
I won't flame you, but this was posted in the wrong forum regardless of what ROM you are using to flash to your device. Just keeping things clean.
Yeah, you're on the right track. You need to make a note of the file it says it's missing and the directory path. Then boot using the XP CD and choose r for recovery console. Depending on the number of windows partitions, you may need to choose the correct partition and provide an administrator password. After that you will see a DOS-like prompt. Copy the missing file from the XP CD to the hard drive. The command should look something like this:
expand d:\i386\missingFile.ex_ c:\windows\system32
D: is your CDROM and C: is your hard drive. Make sure you copy it into the directory that you made a note of earlier.
Also, here is a link that talks about an infinite loop problem with ATI drivers http://www.sightsea.com/pghpchd/pages/infinite_loop.html
Hello,
I'm sorry to bother you with an apparently repetitive thread, but I assure it is not.
I've been dealing with this problem for over a year now. Of course there were times that I simply gave up, but every now and then I searched all over the internet (seriously; very resilient, I am) and tried everything. Nothing seems to work.
The issue is: one day I was reading something on Google Reader and the tablet restarted. When it came back, it was in this password screen.
[AS A NEW USER I COULDN'T POST THE IMAGE - please see attachment ending in 41]
Detail: I had never, EVER set any kind of password. I don't do this with any of my devices unless I'm obliged to (as in Windows 8, this big piece of shiite).
So the thing is: I did not set a password, I did not choose to ask for a password in any situation and there isn't a single combination that I haven't tried. The thing doesn't even ask me to stop -- like 'hey, you've tried your 30k input, I think you should stop now'.
Now, for you not to start cursing me, I tried EVERYTHING that is basic and post-basic to fix it. I did wipe the data, I tried flashing another ROM, I did cold boot, factory reset, EasyFlashed, nvflashtf and whatnot. I swear to GoogleGods that I, as a non-expert-but-very-keen-on-technology, could.
Another thing that happens is when I try to enter the recovery mode, after using the nvflash, it doesn't work. The image that appears to me is this one:
[SAME THING -- attachment ending in 38]
Again: I'm not a complete noob. I know how to get into things; all I need is a simple guidance. I'm really sorry if this has been posted before and only I couldn't find it, but I won't be so if someone helps me to get it and solve my problem. I can't stand this anymore -- now it's just a matter of pride.
Thank you all.
This happened to me on my SL101 after I flashed a ROM of some sort. I used ADB commands to push the stock ROM back to it and to push another Recovery to it. Mine was in worse shape, Recovery loop, and then I finally got it to where yours currently is. My physical nor on screen keyboard would even work. Look up some ADB commands, perhaps you already know them, and attempt to either push the stock ROM or a new Recovery blob back to it.
D
DatDude123 said:
Look up some ADB commands, perhaps you already know them, and attempt to either push the stock ROM or a new Recovery blob back to it.
D
Click to expand...
Click to collapse
Yeah, well, y'know, I'm not at this level yet, but I'll dig into ADB and stuff.
I tried to use this sometime in the past, but my computer was so bad back then that I had to give up to keep my sanity. Now I've got a fairly good one (very good, considering the few things I use it for), however much less time.
Tonight is the night, though. I'll study as much as I can and I'll fix this ****. Any tip you may remember now would be useful.
Thanks.
I'm struggling with something even before I start: there's no way I can get access to the system and turn the USB Debugging on.
I know I'm not getting much attention, but I won't give up. Please just do not accuse me of spamming; I'm just a desperate geek that has been kept away from his toy.
Alright, after the childish speech, here's the latest update: I cannot use de ADB thing because there's no way I can turn on the USB debugging mode.
Or is there? The latest news is that I can get access to some system files through the ASUS File Manager (turns out it still reads the MicroSD Card, even though I could not update the device this way). So, technicians, is there a way to hack into this beast? Fu ck, I don't even know how to call it anymore.
There isn't much I can do with this File Manager. Mostly visualize the folders and rename this and that (which is the only thing I reckon might be useful).
Jesus, I'm sleepy, I can't even write properly anymore. Please someone help me. It can't be that hard.
maycondimas said:
I know I'm not getting much attention, but I won't give up. Please just do not accuse me of spamming; I'm just a desperate geek that has been kept away from his toy.
Alright, after the childish speech, here's the latest update: I cannot use de ADB thing because there's no way I can turn on the USB debugging mode.
Or is there? The latest news is that I can get access to some system files through the ASUS File Manager (turns out it still reads the MicroSD Card, even though I could not update the device this way). So, technicians, is there a way to hack into this beast? Fu ck, I don't even know how to call it anymore.
There isn't much I can do with this File Manager. Mostly visualize the folders and rename this and that (which is the only thing I reckon might be useful).
Jesus, I'm sleepy, I can't even write properly anymore. Please someone help me. It can't be that hard.
Click to expand...
Click to collapse
For some reason i thought you were on th sl101(slider) so i didnt comment. So heres the deal, any fix is going to be data destructive(nothing you can do at this point as even if you manage to pull data from the tablet, it will be encripted) You need Easyflasher(dev section) follow the instructios there (basically donwloading stock firmware from asus and by using nvflash in apx mode it will re-partition storage, and upload the stock firmware to the tf101)
If you hit any problems, post them here and ill help you further
Edit: just read you post more, if you tried easyflaher and it didnt work, please post the details of what you tried within easyflasher.
Its a strange issue, if it happend to me and id tried the things you already have, this is what id try:
-Flashing ubuntu from the dev section(i known very little about how nvflash works but it maybe only re-partitioning certain partitions, ubuntu i would imagine would require a full re-partitioning)
-alternativly (or on top of the previous idea) use one of the ubuntu installers(OLiFE on ubuntu worked the best for me, but franks tools/ newer software based on franks tools should work fine) and flash the Prime! rom on its own.
If these dont work, your last resort is asus - but thats a long shot lol
maycondimas said:
I know I'm not getting much attention, but I won't give up. Please just do not accuse me of spamming; I'm just a desperate geek that has been kept away from his toy.
Alright, after the childish speech, here's the latest update: I cannot use de ADB thing because there's no way I can turn on the USB debugging mode.
Or is there? The latest news is that I can get access to some system files through the ASUS File Manager (turns out it still reads the MicroSD Card, even though I could not update the device this way). So, technicians, is there a way to hack into this beast? Fu ck, I don't even know how to call it anymore.
There isn't much I can do with this File Manager. Mostly visualize the folders and rename this and that (which is the only thing I reckon might be useful).
Jesus, I'm sleepy, I can't even write properly anymore. Please someone help me. It can't be that hard.
Click to expand...
Click to collapse
If you can't get into anything, but you can enter APX Mode, but NVFlash doesn't work, then I'm not sure anything will as NVFlash completey deletes and recreates all the partitions on the drive
So unless you have been unlucky and downloaded a bad version of an NVFlash ROM....
I know you say you have used NVFlash but I`ll stick this here anyway
The way I restore is:
Connect tablet to PC and make sure the tablet is turned off (Make sure it is the only USB device connected other than keyboard/mouse)
Hold Volume Up + Power for a few seconds until you hear the USB connect sound on the PC, release the buttons, you are in APX mode
Install APX drivers if you have not already
Now extract this
http://www.xdafileserver.nl/Files/Asus/Asus%20Transformer%20(TF101)/STOCK%20ROMS/ICS%20.27/NVFLASH_ICS_9.2.1.27_WW_NOROOT.7z
And run "download.bat"
I think you should see some text appear on the tablet screen, and progress will be shown in the command prompt window on the PC
Wait for it to complete 100%
Its been a while so I can't remember if the tablet will reboot on its own or if you need to hold power for 30 seconds to get out of APX mode
Either way, make sure it is completely finished and reboot the tablet
Only thing I can remember going wrong with NVFlash was the first time I rebooted after a sucessful boot, it would hang on a black screen
Just hold power for 30 seconds and then power on normally, done, if it has worked you have your tablet back, if not, I think its a hardware issue > see asus
Im very keen to get this fixed/ find the issue as uptil now I thought the tf101 was virtually software invincible, you need to pay attention to what the nvflash process says, the one thing I can think of as to why nvflash didn't work is it can't write over encrypted partitions although that would make no sense why it wouldn't.
Just a suggestion... make sure you're not docked. Some people report issues when nvflashing while docked (I can't replicate those issues except with the Tubuntu tool).
Is there a solution?
I also have an error! see picture
Hi,
First of all, great site you've got there, been checking it ever since I laid my hands on my first htc g1.
Secondly, and I hope I'm not double-posting about an issue already raised, as I've screened the threads quite thoroughly.
Here's the issue I have with my MK808B.
I've tried to start it with a USB ubuntu pendrive plugged into the USB OTG (I had saved some files I wanted to transfer, didn't realize it would mess things up).
Regular start up with this hdmi key is Google tv screen > android screen > home screen.
I get stuck at android screen, no matter how long I wait.
Out of nowhere, I tried to use another 2A power supply, as this had been advertised on other threads, no sucess... I also tried to start it with a paperclip pressing the reset button, didn't work...
Honestly, I don't know what to do exactly, I think it might have tried to boot ubuntu out of the usb stick...
I think I have no option left but to flash it (thus losing all that is installed already on it).
Is there any trick that could restore things the way they were? Any suggestion welcome.
Thanks for your time and help.
Solved by flashing
Hi,
Since no mgic trick happened to save the day, I was left with no choice but to flash it.
Used rockchip batch tools, crossed my finger so the stick wasn't a clone with the mediatek chip, flashed stock plus goodies rom, waited 10-15 minutes, and voila!
good as new, got rid of the chinese apps I couldn't even log on, but got a full wipe of my data.
TL;DR - Flashed a ROM designed for N3+ (which is supposed to be same phone) but touch screen is unresponsive now. Need help with SP MDT or editing uboot
EDIT 15. July, 2014.: I've asked a guy from www.NeedRom.com to tell me his LCM driver and touchscreen which are located in factory mode (VOL- + HOME + POWER). He gave me same driver names as mine. LCM driver is RX_5720TM_813a and touchscreen is ili2113a.
I've tried removing the digitizer from my phone (lost warranty, but **** it, i'm not sending it back to china) and when i've entered factory mode again, it said touchscreen: (null).
So it seems that digitizer is properly attached (and should be working?).
Does anybody have a clue what's going on here? I've tried flashing 15 ROMs and NONE fixed the touchscreen. It's fully unresponsive. It doesn't work even if I off/on the screen few times like it worked before.
____________________________________________________________________________________________
Hello everyone, like title says I have unresponsive touchscreen on my Star N9800 phone. It's pretty much a new phone, octa core, quad core GPU, 2GB RAM, 16GB storage, etc.
What I've done is I flashed the ROM designed for Star N3+ (which is supposed to be same phone) but my touch screen is unresponsive ever since then. I've googled and read some articles on xda about SP MDT. It's a tool which can help us choose the display driver we want the phone to run with. I actually ran into a problem when i downloaded SP MDT. I can select the database etc, but when i get to scatter file it just doesn't want to load it. Either it's incorrect name or file type. I've downloaded 3 original ROMs from needrom.com and strangely the scatters seem to be different. But none is accepted by SP MDT. I need someone of knowledge who can teach me where to find uboot and how to edit it correctly. I'm not a linux/android programmer and I really don't wanna get involved into much programming. I understand basic stuff, i can find files on the system, i can edit build prop correctly, remove or edit boot_logo, boot anim etc, but this is a bit more than that. 2
Please share some knowledge with me and please don't point me to google. There's no solution there, i've googled for 3 days now. The last resort for me is to make a post here (and hopefully don't get ignored for spamming because this isn't spam).
My email is: [email protected] - you can notify me here if I don't get automatically emailed by xda.
Thanks in advance.
BUMP
Have no solution but would like to learn as well if anyone can help us...
I had the same issue but gave up and flashed another rom instead.
Flashing another ROM didn't help my problem. Well partially it did. I've flashed 2014-1-7 original N9800 ROM and the touchscreen only needs 1 or 2 off/ons till it starts working. I'm kinda fine with it because it was completely unusable. Flashing drivers with SP MDT didn't really help. I've tried flashing RX5720TM_828A (from N3+ ROMs) and LP057APK (default in N9800 ROMs) and RX5720TM_813A (2nd in N9800 ROMs), and so far my touchscreen works only with 813A LCM driver. When i turn off the phone and then hold VOL- & POWER & OFF/ON it goes to factory mode. There i clicked version and it showed that 813A is installed as LCM driver, BUT touchscreen says (null). Could it be that my digitizer is no longer connected or what? Cuz it sometimes works correctly without turning the display off/on at all.
EDIT 15. July, 2014.
EDIT 15. July, 2014.: I've asked a guy from www.NeedRom.com to tell me his LCM driver and touchscreen which are located in factory mode (VOL- + HOME + POWER). He gave me same driver names as mine. LCM driver is RX_5720TM_813a and touchscreen is ili2113a.
I've tried removing the digitizer from my phone (lost warranty, but **** it, i'm not sending it back to china) and when i've entered factory mode again, it said touchscreen: (null).
So it seems that digitizer is properly attached (and should be working?). It is possible that digitizer is detected but not working?
Even if i boot into recovery, screen doesn't react to touches.
Does anybody have a clue what's going on here? I've tried flashing 15 ROMs and NONE fixed the touchscreen. It's fully unresponsive. It doesn't work even if I off/on the screen few times like it worked before.
Apparently it's the calibration which ****ed up my phone. I'm now trying to figure out how to calibrate the screen through CWM.
ever find a solution?
i have a star n9800 too. suddenly i have been having all of the same issues, but here is the kicker: i never flashed anything but the stock rom that came with my phone, which was the same as kitkat version available on needrom.com. i have tried full factory resets, i have restored my original backup, none of it has fixed my phone. in factory mode, everything tests fine, but even when i launch in to TWRP, about 75% of the time, my touch doesn't work. i am wondering if one of the cables inside has come loose or something, but it is so intermittent that i find it doubtful.
hopefully you have found a solution that you can share with me.
Touch screen sometimes not react
AlexZap said:
i have a star n9800 too. suddenly i have been having all of the same issues, but here is the kicker: i never flashed anything but the stock rom that came with my phone, which was the same as kitkat version available on needrom.com. i have tried full factory resets, i have restored my original backup, none of it has fixed my phone. in factory mode, everything tests fine, but even when i launch in to TWRP, about 75% of the time, my touch doesn't work. i am wondering if one of the cables inside has come loose or something, but it is so intermittent that i find it doubtful.
hopefully you have found a solution that you can share with me.
Click to expand...
Click to collapse
-------------------------------------------------------
I have exactly the same issue and same signes, the phone itself is working good, ring for incomming phone but the the screen is not reacting i cannot take the call, it receives emails.
Did someone have a solution please let me know... thanks
My phone is star N9800, 2Gb memory and 16 Gb storage, android 4.4.2 originaly installed and was working fine during 9 months
Touchscreen - hardware failure
Hi,
I am wondering if you may have experience and be able to help me with my Star N9008 phone which has has had its touch screen stop working while I had it in storage for about 3 months.
Very well stored, no shock, no humidity. I keep it with my laptop backpack as a spare in case my everyday phone fails.
Today I powered it up to make sure battery was good (found it good at 95%) and update applications, etc. Basically, just checking it was still good to serve as a backup should I need it.
Thing is, I found the touch screen is completely unresponsive. Connected a mouse to it and verified all was working good, did up the updates, etc.. using the mouse. Reboot and boot into service mode and restore menu. Also, no touchscreen response (I use TWRP). Thus, it must be hardware failure.
From experience, would you know what would cause this, and how to resolve?
Thank you.
So, its been a while.
So, it's been a while. I still have the phone in storage and pity it doesn't work...
I haven't bothered opening up the phone if I don't know what to really try and also risk damaging it.
Also didn't bother ordering a new digitizer to replace as it's economically unviable.... the phone is now really getting behind as new tech is further evolving, so I do unfortunately see it going in the rubbish soon (along with two brand new batteries I had purchased for it just before it died).
Has anyone been successful at finding the culprit?
In my case, it was fine and very well stored... so I don't really have an explanation other than the phone possibly having a 'countdown timer' to break it... (yeah, a bit too conspiratorial, lol)
I did not find a solution yet , phone still sits in storage
xt2043-4 unable to get into EDL mode. It died during a restore with the Lenovo "smart" software.
When plugged in I something's get a single led blink. Nothing however when I plug it into my PC. I have an edl cable that doesn't seem to do anything either. Are there test points/jtag? I don't want to open it up unless I can actually do something.
kaleamity said:
xt2043-4 unable to get into EDL mode. It died during a restore with the Lenovo "smart" software.
When plugged in I something's get a single led blink. Nothing however when I plug it into my PC. I have an edl cable that doesn't seem to do anything either. Are there test points/jtag? I don't want to open it up unless I can actually do something.
Click to expand...
Click to collapse
Download Qualcomm qloader drivers....see if device shows up as Qualcomm 9008 In Windows Device manager or maybe it says Qualcomm bulk hub...if it is you are in edl mode and you need to download blank flash file from the rom archive on lionnet moto firmware under our device...unzip the file and run the .bat file with admin privileges it will run the file and reload the critical bootloader files to get you to bootloader screen ...then reflash STOCK...I did this last week because I rebooted to edl from TWRP...
Nothing shows up. I get a few led blinks but nothing in device manager or otherwise.
Anyone found the answer to this? Im having the same issue
kaleamity said:
xt2043-4 unable to get into EDL mode. It died during a restore with the Lenovo "smart" software.
When plugged in I something's get a single led blink. Nothing however when I plug it into my PC. I have an edl cable that doesn't seem to do anything either. Are there test points/jtag? I don't want to open it up unless I can actually do som
Shane8705 said:
Anyone found the answer to this? Im having the same issue
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hi there! I myself have a hard-bricked G Stylus (US model). After reading this and related threads, as well as doing a LOT of independent research on this. I have a feeling that the only hope lies in potential EDL test points located on the motherboard. I've looked at a teardown video on Youtube, and I see several sets of potential test points. From further research, it appears that test points for EDL are always located right next to each other.
I'm purchasing some iFixit tools this month, which include the required T3 driver bit. Once I get access to the motherboard, I fully intend to test every possible set of EDL points. I'll post my findings on this and any related thread in the G Stylus forums here on XDA. If I'm successful in restoring the phone, I will post a photo of the points that need to be bridged to enter EDL mode.
Wish me luck!
Have you had any luck with this? And I'm wondering if you mind describing how you got into this situation.
On my phone (I think it's a Moto G Stylus, XT2043-4, that I got through Google Fi in the US), I was trying to modify an app on the phone. So I used "adb pull" to get the APK. Then I extracted, edited, and recompiled it with apkeasytool, but then I couldn't write it back to the proper directory because the filesystem was read only. At that point I went through the process of unlocking the bootloader via the Motorola website, and then tried to root the phone. That's where my problems started.
I can go through the details if anyone thinks it would matter, but essentially, I wasn't paying attention and flashed the incorrect files... multiple times... I ended up with a phone that appeared to be dead (nothing on the screen no matter what I did). However, I noticed that when I plugged it in it popped up as the "Qualcomm 9008 Port" thing in Windows Device Manager. After reading up on that I realized that it was in EDL mode and I tried to run the blank-flash.bat file I found. After some trial and error, it appeared to work, however, I was holding the power button at the time and the phone may have restarted in the middle of the script. At that point, it stopped appearing in Device Manager and I haven't gotten it back, except that after disconnecting the battery, I get an LED flash when it's plugged in as well as some other strange behavior that I'll describe below.
Anyway, after all the previous catastrophes, I decided to open it up and look for these mythical test points. I'm attaching some pictures in case they help anyone. One after exposing the mainboard, another after lifting the obvious cables, and finally one with the obvious test point candidates numbered.
I'll describe what I've figured out so far:
- When I disconnect the ribbon that covers 6, 7, 8, and 9, I don't even get the LED flash when connecting/disconnecting the phone to the computer. So I don't think those are likely to be test points, but I don't know what that cable is for.
- The middle ribbon appears to connect the battery, and I don't get the LED flash when that is connected. It doesn't happen when I connect the USB to the computer OR when I hold the power button. I don't understand why this happens.
- The rightmost ribbon doesn't cover anything. So I leave it connected.
- When USB is connected and not the middle ribbon, all the points seem to show 0V except 3 (0.417V) and 5 (1.803V). 6 is 1.792V when the middle ribbon is connected, but dissipates during measuring when the middle ribbon is disconnected. 10 also seems to dissipate when the middle ribbon is disconnected, and I can't measure it when connected because it gets covered up.
- If I short or ground 10 or 12 while plugging in, the LED flashes until I remove the short or ground.
Anyone have any thoughts? Anything else I can check?
moorevineyard said:
Have you had any luck with this? And I'm wondering if you mind describing how you got into this situation.
On my phone (I think it's a Moto G Stylus, XT2043-4, that I got through Google Fi in the US), I was trying to modify an app on the phone. So I used "adb pull" to get the APK. Then I extracted, edited, and recompiled it with apkeasytool, but then I couldn't write it back to the proper directory because the filesystem was read only. At that point I went through the process of unlocking the bootloader via the Motorola website, and then tried to root the phone. That's where my problems started.
I can go through the details if anyone thinks it would matter, but essentially, I wasn't paying attention and flashed the incorrect files... multiple times... I ended up with a phone that appeared to be dead (nothing on the screen no matter what I did). However, I noticed that when I plugged it in it popped up as the "Qualcomm 9008 Port" thing in Windows Device Manager. After reading up on that I realized that it was in EDL mode and I tried to run the blank-flash.bat file I found. After some trial and error, it appeared to work, however, I was holding the power button at the time and the phone may have restarted in the middle of the script. At that point, it stopped appearing in Device Manager and I haven't gotten it back, except that after disconnecting the battery, I get an LED flash when it's plugged in as well as some other strange behavior that I'll describe below.
Anyway, after all the previous catastrophes, I decided to open it up and look for these mythical test points. I'm attaching some pictures in case they help anyone. One after exposing the mainboard, another after lifting the obvious cables, and finally one with the obvious test point candidates numbered.
I'll describe what I've figured out so far:
- When I disconnect the ribbon that covers 6, 7, 8, and 9, I don't even get the LED flash when connecting/disconnecting the phone to the computer. So I don't think those are likely to be test points, but I don't know what that cable is for.
- The middle ribbon appears to connect the battery, and I don't get the LED flash when that is connected. It doesn't happen when I connect the USB to the computer OR when I hold the power button. I don't understand why this happens.
- The rightmost ribbon doesn't cover anything. So I leave it connected.
- When USB is connected and not the middle ribbon, all the points seem to show 0V except 3 (0.417V) and 5 (1.803V). 6 is 1.792V when the middle ribbon is connected, but dissipates during measuring when the middle ribbon is disconnected. 10 also seems to dissipate when the middle ribbon is disconnected, and I can't measure it when connected because it gets covered up.
- If I short or ground 10 or 12 while plugging in, the LED flashes until I remove the short or ground.
Anyone have any thoughts? Anything else I can check?
Click to expand...
Click to collapse
Hi there! I actually did find some more potential EDL points underneath the speaker grill (underneath the black plastic piece below the battery).
I've tested them all... and no luck so far... The only reproducible result I can share is:
When the battery is unplugged, attempting to use any two points results in an LED flash every 15 seconds or so. No other behaviors.
Motorola came so close to having a perfectly repairable phone... What a disappointment.
This seems strange to me. Most of what I've read about other phones with the EDL mode and test point access seems to indicate that it's not possible to mess it up with any of the normal tools (adb, fastboot, recovery, blank-flash, etc.). Is that incorrect?
Basically, I had the impression that the Qualcomm EDL mode was provided by a more segregated component on the board that could reprogram the rest of the system, but not incorrectly reprogram itself the way you can incorrectly reprogram the bootloader.
moorevineyard said:
This seems strange to me. Most of what I've read about other phones with the EDL mode and test point access seems to indicate that it's not possible to mess it up with any of the normal tools (adb, fastboot, recovery, blank-flash, etc.). Is that incorrect?
Basically, I had the impression that the Qualcomm EDL mode was provided by a more segregated component on the board that could reprogram the rest of the system, but not incorrectly reprogram itself the way you can incorrectly reprogram the bootloader.
Click to expand...
Click to collapse
It appears that certain models aren't failproof. Similar situation with a mislabled black-flash. Flashed it multiple times and ended up unable to do anything going forward. I saw the edl points on a similar phone the moto g power on youtube and hoped that they were somewhat easily identified. Unfortunately doesn't seem to be the case, I too have tried every combo that I saw on the board. Same blinking lights as described, but nothing shows on the PC. I am able to get it working on other devices however as I have two.
Today I started researching repairing a hard brick of a moto g stylus after letting it sit around for a couple months. I came across the android doctor video that shows how to do this on a g8+ but unfortunately I found out that the mobos aren't laid out similarly. Subsequently found this thread. Bummed to find out the EDL points haven't been discovered. Hopefully someone does find them and posts here. I guess I'll do a little more research but otherwise I guess it's back to the shelf this phone goes.
FWIW I found this thread, but the points illustrated here don't seem to work for me: https://forum.xda-developers.com/t/sofia-edl-points-found.4457105/
Well I tried most points on the board. I was cycling through when I hit either I-J or J-K and my pc said there was a short on a USB port. I removed the ribbon cable to reveal that the jumper I made had melted. The led no longer flashes and the phone is now totally dead jim. Charging for a while doesn't seem to have any effect, nor letting it sit. Whatever shorted killed it. I was incredibly careful but clearly not careful enough.
That said I have another 2020 stylus (bootlocked unfortunately). So I'll be part harvesting as my current phone degrades. Thank you all for your help and good luck to you on this phone! Shame on Moto for really trying to keep people out of it... The glue, the edl cable not working, the points being potentially behind the battery ribbon. Just unnecessary nonsense imo.
EDL es el 10 y 12 me pasa que no se mantiene se desconecta despues de 5 segundos