Okay, so I rooted and installed a custom ROM on my cousin's Droid X for her a few weeks ago. All went smoothly. Suddenly yesterday, about 3/4 of her screen came up with just like, gray lines. The top portion is normal, however. But you can't see too much of the screen at all. (I'll try to post a pic soon.)
Sooo she obviously needs to try to do a warranty claim on the phone, and needs to get it back to stock. How can I go about this? Obviously it's gonna be hard doing anything that requires physically seeing stuff far down on the screen, or even midway...
Hate to sound rude, but help asap would be great; as she has to go to work soon so trying to help while I can... Thanks guysss
UPDATE: Trying to use RSD LITE to SBF it now. Crossing fingers that works, and also that I can manage to hit "data wipe/restore" on the screen. We shall see :-/ lol
Update #2: After flashing the sbf (it stated "PASS"), the phone then became stuck on the bootloader screen, no matter what is tried when the battery is inserted and the phone is powered on... no way to get in recovery, etc...
Phone just says:
BOOTLOADER 30.04
then underneath it says Err: A5, 70, 70, 00, 1F
After finally reading online, it seems it's probably due to the wrong sbf being flashed. (She was kind of freaking out and rushing me due to her having to leave for work )
So after reading this thread linked below, it seems I can possibly unbrick and get out of the bootloader by using that SBF.
thread: http://forum.xda-developers.com/showthread.php?t=902074
Update #3: Okay, it seems that last try worked to get it past the bootloader and to a different screen, though due to the gray bars on most of it, all I can really see is the status bar... which shows a blue triangle (which i read means it needs to be reactivated, and the service bars and the battery.
I'm not completely sure how to make certain it's unrooted and back to stock with just this area available to view, anyone else have any idea? I'm not overly familiar with how stock looks on Droid X, as I have a Captivate...
Pic attached for reference of what it's looking like.
From the nofitication bar, it looks stock. Hard to tell though but if you SBF'ed and it said PASS, then it should be back to stock. Good luck with your claim.
It's unrooted and stock, but with an issue like that they'll probably send another one as soon as they boot it up. Besides, rooting wouldn't cause a display failure like that, so it would be pretty ballsy of them to deny you.
Related
Hello all,
I have recently upgraded from my g1 to an HD2. HD2 is a great phone but still miss android . Anyways, today I wanted to get my g1 to work without a sim or data plan and was about to start working on it when my g1 screen dimmed to just the blacklight with a black screen. I turned it off and tried turning it back on but it just comes up with the backlight on a black screen. It does not even get to the G1 screen. I cannot get to recovery mode or any other mode for that matter. I have searched around but not found any real solution to this problem (if there is one). I am thinking my phone is bricked but have heard possibilities using ADB. I have never used ADB before and if anyone knows if this is a possible fix to my problem that would be great. It would be nice to know if it actually could fix my problem before looking into it and learning it all while finding out it has no chance of fixing my problem. I have tried using my sim card and a different sd card so those are not causing the problems.
So the background of what I am running on my g1. Right before I got my HD2 I was using Cyanogen version 4.2.14.1 with and ext 3. I had no problems with it until now. I got my HD2 a week ago and my g1 has been on about twice in that time without a sim card just for comparing purposes to the HD2. Then just today (about 2-3 days since I last turned it on) the screen just went black and I had my problems. I cannot return my phone because it has been over a year and I dont have insurance on the phone so these are not possibilities for me unfortunately. I also don't really want to get parts from other g1's and take apart and put my g1 back together. I am just looking for something with ADB or any other possible solution to the problem (if one exists).
Any help would be greatly appreciated!
I had this happen to me before. Apparently, it was a hardware GPU problem that would cause a boot loop because it couldn't draw anything on the screen. This happened on SuperD, AOSP, Cyanogen, and stock Donut.
If your problem is the same, you should be able to get into recovery, regardless of your ability to see what you're doing. Easy way of telling is to hit Camera+End on boot. If it doesn't vibrate, you're able to flash still. You may be able to get the screen back temporarily by either pulling the battery or letting the battery die and recharging.
Anyways, I ended up flashing the DREAIMG.nbh, and trying to upgrade back to 1.6 to remove traces of hacking. (Be careful if you have DangerSPL, you want to restore the default before flashing DREAIMG.nbh) I eventually got the screen working on 1.6, but it died again, so I sent it in to T-Mobile and got a replacement. I'm now using AOSP with no problems.
One small note, however, I did start having my problems using Cyanogen's mod. May want to bring it up with him?
Sorry if this sounds scatterbrained, it's a bit late and I should be asleep right now.
e:Just realized you said the warranty was void. You may be able to get something out of what I did, though? Good luck, in any case.
Thanks very much for the help even though it was really late. I did understand pretty much everything you said and I tried the camera plus power button and it didn't vibrate so it should mean I probably can flash things still. I have drained the battery and am charging it back up to see if that helped.
I have a friend who knows ADB so I am going to have him look at it to see if we can't get it working through there. Also the G1 screen has been popping up but then fading right when its about to change to the boot animation. So we will see how things go and I'll try a couple different things and report back if anything seems to work or open up more possibilities.
Thanks again for your information.
Ok, so my friend and I were going to flash a rom through fastboot. It was responding and such so we knew we were able to get it in there.
Anyone know what the command to flash a rom in fastboot is and if there are specific instructions to follow?
Any help would be greatly appreciated!
coolookoo said:
Ok, so my friend and I were going to flash a rom through fastboot. It was responding and such so we knew we were able to get it in there.
Anyone know what the command to flash a rom in fastboot is and if there are specific instructions to follow?
Any help would be greatly appreciated!
Click to expand...
Click to collapse
google it. i did and got about 100 links telling me how to do it. "unroot g1 with fastboot."
sorry i have the same problem, but my g1 is not rooted nor has it been flashed before, my friend messed it up somehow? wen i turn it on all there is is a blank highlighted black screen. What do yall suggest i should do
r3s-rt said:
google it. i did and got about 100 links telling me how to do it. "unroot g1 with fastboot."
Click to expand...
Click to collapse
First of all we are not trying to unroot the phone just flash another rom
Secondly we already tried your "fantastic" method of using google before coming to the forums
Ok I think I just bricked my G1
I was following the steps on theunlockr.com and was following the steps to the T like I always do.
The problem incurred after flashing the spl. I flashed the correct radio then ir rebooted and went back into recovery mode. Then I flashed the spl all seemed well home+back and never rebooted. It stayed on a black screen for over 30 mins. So I took out the battery and waited a few mins and put battery back in and same thing. Just a black screen nothing I can do. I have tried holding home+power and camera+power and back+power nothing. I am stuck have looked it up and this is the best forum I have found to post in.
Any input would be great.
thanks
nate
I think I have finally, fully bricked my Droid 2.
A little background: This is my fifth one, mostly all for hardware issues stemming from poor craftsmanship in the refurbed phones. This one though, is gone as far as I can see it. I got this phone last week, and had waiting a week to make sure everything was fine. It was, so last night I rooted it and tried to put Epic 2.7 on it. It failed Epicly (no pun intented) and I was forced to do a full SBF on it. In the process, something got a hiccup and I was left with Droid 2 flashing "Service Required" and a RSD Lite telling me it had 100% successfully flashed. I tried once again to flash it using the SBF from a different source, and the battery died halfway through. The USB port won't even engage now so I can't charge my battery, even when it's off. When I try to turn it on, it says "Service Required" then below, it flashed "Battery Low, cannot run" or something to that effect. Well, can't flash it if I can't charge it, eh? I'm stuck in a catch-22 and I can't really see a way out.
I'm going to try my luck tomorrow and take it back to Verizon, claim it's their fault (my ERI reflash code was manually changed in one of my older phones I had received, so anything is possible now) and jump ship to a Galaxy or something non-HTC. In the mean time, is there anything I could try and do to remedy this?
Note: I didn't know where to put this, sorry if it's in the wrong section.
drburke said:
I think I have finally, fully bricked my Droid 2.
A little background: This is my fifth one, mostly all for hardware issues stemming from poor craftsmanship in the refurbed phones. This one though, is gone as far as I can see it. I got this phone last week, and had waiting a week to make sure everything was fine. It was, so last night I rooted it and tried to put Epic 2.7 on it. It failed Epicly (no pun intented) and I was forced to do a full SBF on it. In the process, something got a hiccup and I was left with Droid 2 flashing "Service Required" and a RSD Lite telling me it had 100% successfully flashed. I tried once again to flash it using the SBF from a different source, and the battery died halfway through. The USB port won't even engage now so I can't charge my battery, even when it's off. When I try to turn it on, it says "Service Required" then below, it flashed "Battery Low, cannot run" or something to that effect. Well, can't flash it if I can't charge it, eh? I'm stuck in a catch-22 and I can't really see a way out.
I'm going to try my luck tomorrow and take it back to Verizon, claim it's their fault (my ERI reflash code was manually changed in one of my older phones I had received, so anything is possible now) and jump ship to a Galaxy or something non-HTC. In the mean time, is there anything I could try and do to remedy this?
Note: I didn't know where to put this, sorry if it's in the wrong section.
Click to expand...
Click to collapse
This is the correct section And if your phone turns on at all, it's not bricked Your phone would need to be 100% gone to be bricked
Hmm. Perhaps the statement "My phone hates me and put me in a catch-22" is a better qualified statement then? haha.
drburke said:
Hmm. Perhaps the statement "My phone hates me and put me in a catch-22" is a better qualified statement then? haha.
Click to expand...
Click to collapse
Probably I was just trying to cheer you up
For you to be able to do anything if your battery is really dead you need to find away to charge it or get a charged battery to try to do another SBF. Make sure the SBF is the 2.3.20 verizon version (assuming you have the 2.3.2 update)because the 2.2.0 version won't load on your updated D2. If you aren't succeding in windows there is a linux method that anybody can try via my ubuntu livecd. I'll update this post with links when I get on my laptop.
Sent from my DROID2 using XDA App
Reboot into recovery.you should see the ! Android. Press the search button on the keyboard. Scroll down to wipe data with the arrow keys and press ok. Delete to go back to the main screen. Then go to reboot and hit ok.
Sent from my DROID2 using XDA App
This happened to me as well. You need to find another battery to use or buy a 3rd party external charger.
The phone will only charge the battery when software is installed. The phone is nowhere near bricked but you do need a full battery to SBF back to a workable state.
I don't think Epic 2.7 should be used on updated D2's because I don't think the ROM is compatible with the updated version. I could be wrong though.
I seem to remember an editor at engadget or bgr had this problem on an original droid? I think they made some Frankenstein charger with a jumper or something and got it to charge so they could fix their software. They wrote an article about it.
so my mytouch 4g wont turn on even with a different battery. i plug it it in and it gives me a flash on th screen but thats it. any suggestion without sending it in
Take it to a tmo store, they'll swap it.
I got it off of Craigslist I think it was previously tampered with
Sent from my HTC Desire using XDA App
so i was in the process of doing a custom splash screen last night. i went through all the instructions on how to push the custom splash through terminal. everything went how the instructions said, but once i reboot it my phone turned off and never came back on. it doesnt power on, boot into recovery, nothing! i put the phone to charge and the red light comes on on the top left but when i take it off the charger it stays on.
i been rooted for about a month now and i was running cm7 build 8 when this happened. i just want to see if anybody has any idea on what going on. i tired everything i can think of. taking out the battery and normally powering on and nothing. taking off the battery and volume down and power to boot into recovery and nothing. taking off the battery, sd card, sim, putting back the battery and doing both normal power on and to boot into recovery and nothing.
First of all you just hijacked the guys old dead thread and second it sound like you just bricked your phone. As there is boot animation and there is slash screen. Seems like you flashed wrong thing. If the screen don't even turn on its dead then.
Sent from my HTC Glacier
Don't flame the poor guy! He's got it bad enough as is! And he didn't flash the "wrong thing" there are several threads on flashing splash screens in this phone's forum. Cut the guy some slack. He knows it may be bricked, he's just hoping it's not. And he was hoping for someone to provide some possible help. Not be be given **** for not opening a new thread.
i thread jacked because the thread was old and didnt want to clutter by starting a new one when im having some what the same problem. but no i pushed the splash image. i had already flashed a boot animation a few day back. i had call of android running on my phone as a boot animation. i just want to know is theres other methods of reaching hboot or recovery.
First of all don't put words in my mouth as my post does not contain any flame, second when I said wrong thing I meant he may not have meet the requirement for the splash image if he did correctly then obviously he would have had it up and running. Best thing for him would be going back to the original thread where he downloaded the image and asking the OP and troubleshoot it but at this point its to late all he can do now is warn others.
But if his phone is not old lol he can social engineer and play the victim card and send it back to HTC but first would be trying TMo saying he didn't get the POST OTA as he had PRE OTA and when he try to install the OTA it went blank and act like he has no idea what is going on, as he simply just want the phone to work or he will cancel service and do acting best of his life.
i already know i probably super bricked it. becuase ive bricked it before but not like this. i was able to fix it very quickly before. its like if the phone just doesnt have a battery. im just going to wait to see if anybody else has any more input. if not ill head to the tmo store see what they can do.
BlackSHELF said:
But if his phone is not old lol he can social engineer and play the victim card and send it back to HTC but first would be trying TMo saying he didn't get the POST OTA as he had PRE OTA and when he try to install the OTA it went blank and act like he has no idea what is going on, as he simply just want the phone to work or he will cancel service and do acting best of his life.
Click to expand...
Click to collapse
I do apologize for using the word flame. It was too strong. But I get fired up when people criticize instead of offering insight. If you had posted the above paragraph first, I wouldn't have had any issues. This is good and viable option. Albeit a last resort, but much better than criticizing for thread jacking. And I am the OP of the thread that he's using and am doing EVERYTHING I can to help him figure out a way to get this resolved.
coupetastic-droid said:
i already know i probably super bricked it. becuase ive bricked it before but not like this. i was able to fix it very quickly before. its like if the phone just doesnt have a battery. im just going to wait to see if anybody else has any more input. if not ill head to the tmo store see what they can do.
Click to expand...
Click to collapse
ok, I just got caught up on your issue. I am going to do a little research and see if I can come up with anything to maybe help. Do you have adb set up? What recovery are you running?
Same thing happened to me, flashed a rom rebooted and the phone never turned on again.
thanx every one for trying to help. i tried everything i can think of and i could not get that phone to power on at all. it was completely dead. so i went to the tmo store by my pad and they gave me a brand new one. now i just need to gain s=off on this one which i cant do for some reason. i dont know why since it was fairly easy to gain s=off on my other mt4g. ill figure out though.
coupetastic-droid said:
thanx every one for trying to help. i tried everything i can think of and i could not get that phone to power on at all. it was completely dead. so i went to the tmo store by my pad and they gave me a brand new one. now i just need to gain s=off on this one which i cant do for some reason. i dont know why since it was fairly easy to gain s=off on my other mt4g. ill figure out though.
Click to expand...
Click to collapse
Don't know if you used this guide yet or not but I will post it anyway http://forum.xda-developers.com/showthread.php?t=858996
toby4059 said:
Don't know if you used this guide yet or not but I will post it anyway http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
I aready got s=off but thanx anyways.
Sent from my CM7 Glacier using XDA App
Hi.
I had the same problem on my htc glacier (mytouch 4g) which was turn it on, stuck on the htcwelcome screen, keep loading and then turn off automatically. My phone is rooted and cusome flashed to the new htc 3.0 sense when this happened, i did a back up and restore to the oem mytouch sense and now it is working just perfectly. So if your phone is rooted you might give it a shot and hope it will work again
i had same prob kinda
i flashed a rom was useing it for a week and today i went to use camera and while camera was loaded the screen shut off like not beining used it did the crt thing and all then it wouln't come out of it so i pulled battary after like 5 min of a lighted black screen and went to power phone back on and nothing like no batt.....
anyways what i was geting to is that i called tmoble and they said it sounded like a hardware problem if you can plug it in to wall or car charger and nothing.. when i plug it into a usb on pc i get
hsusbs or something so u all might want to look into that.
i have s mytouch 4g it wont boot
i rooted my mytouch 4g ussing gfree and then i installed sense 3.0 rom and it worked then force closed left me in bootloader then from there flasheed cm7 worked good for 15 days then said force closed again then never turned back on aghain now when i plug it back in it tells me cannot install drivver software and it recognizes it as qhsusb_dload any solutions or its a gonner contact me at [email protected]
So, as I cant leave things alone.....come on, who can right?.
Verizon Tab....
Im a Droid X kinda guy, we dont have Kernals (thanks Motorola ) so sometimes this stuff gets confusing, so many options right....
Flashed the VZW Kernal after a few attempts, worked, started messing with Roms, ok cool. Started backing up using CWM, ok cool.
Here is where **** goes wrong....
Started tweaking rom, went to reboot, typical boot loop, no biggie, Odin and Heimdall are my best friends, infact at this point I think my 4 year old has seen me use them enough that she can do it, lol.
decided to nuke and repave, but the usual factory files failed halfway through, wtf?, so I got the Phone---!---PC icon, whoops.....
Did some heavy ready/searching, seems there is not to much out there for detailed info on this.
Found a few posts scattered, one was a system dump, and the person said he flashed everything to repair, so I decided to follow instructions, big giant huge EFF-UP !!
What I know now, after all is said and done......
I flashed the bootloader.
Well, now I know.
So, it happens that VZ tech was nice enough to still send me a replacement, I tell them the truth, they know my DX has the GB leak, wifes Dpro is rooted/rom, etc.
Lesson....
um, dont flash boot loader? ha ha ha.
Oh, I did crack the Tab open, took battery out, looked inside, real ***** getting back cover off, looked real good at cover, possible to airbrush/change colors though...
The tab is not really bricked if you can power it on. There is still a way to "unbrick" it.
oldmacnut said:
I got the Phone---!---PC icon,
Oh, I did crack the Tab open, took battery out, looked inside, real ***** getting back cover off, looked real good at cover, possible to airbrush/change colors though...
Click to expand...
Click to collapse
Phone-!-pc icon is download mode, so you were not bricked. Usually, just reconnect to the pc and flash again.
Where did you get the three blade screw driver to open your tab?
rangercaptain said:
Phone-!-pc icon is download mode, so you were not bricked. Usually, just reconnect to the pc and flash again.
Where did you get the three blade screw driver to open your tab?
Click to expand...
Click to collapse
Tab doesn't turn on anymore after accidentally flashing bootloader, no response. not even if I plug it into wall. button commands dont work either.
I have a wood shop, and alot of tools.
oldmacnut said:
Tab doesn't turn on anymore after accidentally flashing bootloader, no response. not even if I plug it into wall. button commands dont work either.
I have a wood shop, and alot of tools.
Click to expand...
Click to collapse
You're not the first to do that. Use three wall charger for at least four hours, and try again.
In the stickie section (you can see that part of the forum if you view with a pc) there are some instructions involving some button sequences and the usb cord. But you may have to send tab away to samsung for a clean flash with a JTAG Box.
What is the name of the 3-blade screw driver, and where can I get one? It seems gorilla glass is a farce.
rangercaptain said:
You're not the first to do that. Use three wall charger for at least four hours, and try again.
In the stickie section (you can see that part of the forum if you view with a pc) there are some instructions involving some button sequences and the usb cord. But you may have to send tab away to samsung for a clean flash with a JTAG Box.
What is the name of the 3-blade screw driver, and where can I get one? It seems gorilla glass is a farce.
Click to expand...
Click to collapse
New one arrives tomorrow, Im not going to worry about the bricked one, Ill send it back.
Dont remember the name of the screwdriver, I have alot of strange small tools, large collection of bits, you can get away with a regular small bit.
Taking the back off was a huge *****, you wont break anything, just a pain. Battery is huge, and a good majority of the weight.
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: