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
Hi everyone!
I'm wondering, how risky it is to flash new firmware to the tab? Is it really brickable, I mean, is it possible to really really brick the tab to a point where it's not possible to fix it? I'm asking partly because I'm a rookie, but mostly because it seems that everyone who manages to brick their tab around here, is somehow able to restore it. Or am I mistaken?
Where I live, the tab has a starting price of $1100. And thats gotta be one of the most expensive bricks in xda history. And if I brick mine, I know I won't be able to resist buying a new one, which adds ut to a $2200 pricetag and a very VERY angry gf..
thanks btw to all of you who make this place what it is
As risky as any other device. Simple. The risk doesnt just lay on the devices shoulders, its the user and the rom maker.
Sent from my GT-P1000 using XDA App
Okay, I'm so confused with the brick-terminology being used here. In all posts regardig new firmware to the tab you'll see at least to guys saying that they bricked their tab. Only to say that they fixed it/unbricked it moments later.
I thought that if you bricked your device, whatever device it is, then it's dead, period. No more usefull than a brick like the ones you'll find in a brick wall, just a hell of a lot more expensive. Heck, the word "unbrick" shouldn't even exist by this definition.
So, let me rephrase:
If I brick my tab, can't I just unbrick it? And if not, why? Is it even possible for the tab to be totally and permanently bricked forever? Is the tab in any way safer to fool around with than other devices? Do we know anyone who have bricked their tab permanently? Should I be afraid of fooling around with my tabs firmware for real?
I think it's just a question of perception on the part of the person who "bricked" their device (the "brickie"? ). If you flash and find that you have what appears to be a dead device then you may well come on here and say "I've bricked my device!". You may then find that it's not bricked at all as there is a way (previously unknown to yourself) to recover. I remember in the old days on here people would pick up "bricked" phones on ebay etc, knowing that quite often they could recover them. It probably still happens...
But devices certainly can get permanently bricked too as you know. Personally, I would only flash if I had confidence in myself that it would work, having read up on the procedure and seen enough working examples. Others may just dive in and see what happens . Only you can decide if it's worth the risk or not, but these days I think it's quite rare to permanently brick a device if you fully understand the procedures and the risks. A stable recovery ROM makes a big difference. Not sure if the SGT has that yet.
paulshields said:
A stable recovery ROM makes a big difference. Not sure if the SGT has that yet.
Click to expand...
Click to collapse
It's in the works, just not quite there yet.
As Paul said, there's always going to be a risk it COULD happen. But following documentation and fully understanding the task at hand before diving in helps to limit the risks to a minimum.
Thanks to all of you for enlightening me
When I was flashing the different files to get calling on my ATT Tab I managed to flash the wrong file and get the device not to boot up but there was still the "download mode" to go into and I was then able to flash the correct file. I find it is very rare to actually "brick" a device requiring the device to be replaced or cracked open & reprogrammed manually. Most of the time now when a device is described as a brick it just won't boot the OS like it is normally supposed to.
paulshields said:
I think it's just a question of perception on the part of the person who "bricked" their device (the "brickie"? ). If you flash and find that you have what appears to be a dead device then you may well come on here and say "I've bricked my device!". You may then find that it's not bricked at all as there is a way (previously unknown to yourself) to recover. I remember in the old days on here people would pick up "bricked" phones on ebay etc, knowing that quite often they could recover them. It probably still happens...
But devices certainly can get permanently bricked too as you know. Personally, I would only flash if I had confidence in myself that it would work, having read up on the procedure and seen enough working examples. Others may just dive in and see what happens . Only you can decide if it's worth the risk or not, but these days I think it's quite rare to permanently brick a device if you fully understand the procedures and the risks. A stable recovery ROM makes a big difference. Not sure if the SGT has that yet.
Click to expand...
Click to collapse
Lol @ "brickie" - I guess you have to be British to get that one?
As for "bricking" , quite right, the device isn't "bricked" if it can be fixed by the user.
People have gotten sloppy with the term, but really it means that you could build a house with it if it were fat enough, but it's no more useful than an expensive paperweight.
The worst you can do without bricking is boot-loop/no-boot which can usually be fixed. The point is, if the device shows any signs of life whatsoever, it's usually fixable.
I thought I bricked my tab, I got the infamous "phone-!-pc" screen
http://forum.xda-developers.com/wiki/index.php?title=File:Samsung_Galaxy_S_Black_Screen_of_Death.jpg
I thought I was screwed. However, I still had it connected via USB and Odin still running and I saw that the com port popped up. I though, hmmmm
clicky and bam, its flashing.
Got it back.
This was after a stupid botched flash attempt on my part.
So, I think you REALLY gotta mess it up to be proper "bricked"
I did a lots of tries and I thing that is not that easy to brick, but I can give a suggestion: Backup the EFS folder!!!!!!!!!!!!!!
I deleted by mistake with root explorer the nv_data and relatives backups, and I had a corrupted IMEI that is not a brick but I think is one of the bad things (and hard to recover if not impossible if you don't have a backup) because if the carriers ban double IMEI the phone (tab) will not work + is not legal
Forgot to say: seems that some SGS firmware upgrades corrupted the IMEI too, I didn't see something flashing the TAB, but restoring the EFS folder will fix (almost always) the problems
I have not tried to brick my GT, but the JM6 gave me a scare... I have been flashing it for a while now.
The one thing you have to give up for now is SWYPE. I se you have a norwegian flag... And norwegian is not included in any flash I have found. So if you ever decide to try flashing. Say goodbye to SWYPE in norwegian for now...
Yeah, the loss of the Norwegian keyboard is the only thing stopping me from flashing jm6. Lucky for me, I'm very patient.
Sent from my HeTC Desire using XDA App
Apparently, you can brick it. I succeeded !
I flashed with Odin and a custom made PDA package including boot.bin but no repartition.
Odin flashed without problems but the Tab did not reboot and simply 'died'.
Black screen all the time, no recovery/download mode, not seen by the PC, does not charge on ac/dc (neither the charger or the PDA ever gets hot, no sound on connection, ...).
I'm letting the battery discharge completely (but how long can that take when it's not using any energy...) to test again tomorrow but I will probably RMA it on monday.
One thing that concerns me is not being able to remove the battery to force the phone to shut down completely.
As an example when I originally 'bricked' my SGS using Kies, no matter how many times I powered the phone it simply refused to go into Recovery or Download mode. All it would do was show me the two icons on screen.
The only way I managed to totally shut the phone down was by removing the battery and wait 30 seconds before returning. Only then would the SGS allow me to access the 3-Button Recovery/Download Mode.
So..... has anyone come across a situation where you needed to remove the battery and if so how did you manage to recover?
Beards said:
One thing that concerns me is not being able to remove the battery to force the phone to shut down completely.
As an example when I originally 'bricked' my SGS using Kies, no matter how many times I powered the phone it simply refused to go into Recovery or Download mode. All it would do was show me the two icons on screen.
The only way I managed to totally shut the phone down was by removing the battery and wait 30 seconds before returning. Only then would the SGS allow me to access the 3-Button Recovery/Download Mode.
So..... has anyone come across a situation where you needed to remove the battery and if so how did you manage to recover?
Click to expand...
Click to collapse
The worst I have done is get the device in the "Phone---!----PC" mode where you can't enter "Download Mode". It seems that simply flashing a new PIT file and then forcing it off, it will then enter download mode again.
alias_neo said:
The worst I have done is get the device in the "Phone---!----PC" mode where you can't enter "Download Mode". It seems that simply flashing a new PIT file and then forcing it off, it will then enter download mode again.
Click to expand...
Click to collapse
A little un-nerving isn't it... I have deep thoughts of not being able to get the Tab to drop out of memory by not being able to remove the battery and flush.
Beards said:
One thing that concerns me is not being able to remove the battery to force the phone to shut down completely.
As an example when I originally 'bricked' my SGS using Kies, no matter how many times I powered the phone it simply refused to go into Recovery or Download mode. All it would do was show me the two icons on screen.
The only way I managed to totally shut the phone down was by removing the battery and wait 30 seconds before returning. Only then would the SGS allow me to access the 3-Button Recovery/Download Mode.
So..... has anyone come across a situation where you needed to remove the battery and if so how did you manage to recover?
Click to expand...
Click to collapse
I think that when you leave/turn "USB Debugging" on in Applications -> Development, it is fairly save. As long as you are near a computer with adb installed and you have your usb cable within reach, you can reboot the device into recovery with adb reboot recovery or just reboot with adb reboot.
Another way is of course to let the battery run out of power, charge it and reboot.
appelflap said:
I think that when you leave/turn "USB Debugging" on in Applications -> Development, it is fairly save. As long as you are near a computer with adb installed and you have your usb cable within reach, you can reboot the device into recovery with adb reboot recovery or just reboot with adb reboot.
Another way is of course to let the battery run out of power, charge it and reboot.
Click to expand...
Click to collapse
Are you saying that the Tab will accept an "adb reboot" in it's unresponsive black screen state or some other? I'v not yet come across a state where just holding power didn't turn it off.
appelflap said:
I think that when you leave/turn "USB Debugging" on in Applications -> Development, it is fairly save. As long as you are near a computer with adb installed and you have your usb cable within reach, you can reboot the device into recovery with adb reboot recovery or just reboot with adb reboot.
Another way is of course to let the battery run out of power, charge it and reboot.
Click to expand...
Click to collapse
Running down the battery is an option... but it would take an age seeing as you're not doing anything with the phone except looking at two icons on a black screen.
alias_neo said:
Are you saying that the Tab will accept an "adb reboot" in it's unresponsive black screen state or some other? I'v not yet come across a state where just holding power didn't turn it off.
Click to expand...
Click to collapse
That thought passed me by as well.
alias_neo said:
Are you saying that the Tab will accept an "adb reboot" in it's unresponsive black screen state or some other? I'v not yet come across a state where just holding power didn't turn it off.
Click to expand...
Click to collapse
I did . I was fooling around with the button definitions of the tab, I lost all my buttons so to speak (also the powerbutton) and couldn't get into the system. A simple adb reboot got me out of there without any problem.
Yes, I believe adb can connect with the Tab in very unresponsive states and still issue commands. I've seen it also with my old galaxy S. A bad flash and a blank screen still gave me access to the system shell with adb.
My lesson learned is: alway have "USB Debugging" turned on.
Hello XDA Community!
I made a post about this issue before, but have more details so hopefully someone can help me figure out this issue.
My phone even when unplugged from my PC continuously says USB Connected/ USB Debugging in the notification menu.
Also, when I try and reboot the phone, instead of booting even to the Vibrant logo screen, the loading circle continuously blinks on and off, without actually booting.
As I type this, I am not holding down the power button, and the loading circle is blinking on and off by itself....
I used to be able to turn the phone on into recovery mode in the past, but now when I try to reboot into recovery I get a big yellow picture that says "Downloading"
The only way the phone will turn on is if it is plugged in.
I am fairly certain that this reboot issue and the USB issue are correlated in some way.
Did anyone else have this issue with their phones? And if so, how did you solve it?
Another thing I have just discovered...
When the phone is on and idle, the USB Connection notification will constantly blink on and off, which is why I think the phone would do the same when trying to power on!
Is this a hardware issue or a software issue?
I have not flashed anything in a very long time before this issue started happening so I believe a restore is unnecessary .
Someone please help me! This is very annoying, not only do I have NO notification bar because of the constant USB Connection notification turning on and off, I cannot turn on my phone at all unless it is plugged in!
ACK!
Take it back
I carry the insurance, so personally if this was happening to me I would not even mess with it. It sounds like you have a genuine problem with the phone and it needs to be replaced.
If it is possible to do try a nandroid backup of your phone to make getting back to where you are on your new device easier. Then take your phone back to stock with the recovery image here -->
http://forum.xda-developers.com/showthread.php?t=734475 (Thank you justanothercrowd)
One you have a stock device see if you are still having the issue. If you are take it back as defective. Even if you don't have the insurance, that sounds like a factory defect and should be covered by the factory warranty. The insurance just makes the process easier and makes sure they just give you a swap out at the store rather than having to wait for repairs. It also covers things the warranty does not, such as screen breakage - which is the specific reason I carry the insurance.
Ah crap wish I had insurance.... Do I have to do that whole odin procedure or is there a one click un root procedure as well?
Sent from my SGH-T959 using XDA App
Nevermind i just read through that link you posted. So when i go to a t mobile store do i have to unroot or can i just hide my root applications until i get a new phone?
Sent from my SGH-T959 using XDA App
I actually have not had reason to go back to stock, or even use odin yet at this point. My only roms were .zip files that I flashed via clockwork recovery.
I would say that your best best it to just follow the instructions on justanothercrowd's thread very carefully and deliberately. You are already having issues with reboots and your USB port, so this is not the time to deviate into experiments.
So to cut you off and just answer you next three questions:
Q) Can I just . . .
A) No! Just follow the directions exactly.
Q) But can I . . .
A) No! Just follow the directions exactly.
Q) Do I have to . . .
A) Hey look, Just follow the damn directions exactly!
Sorry, I can't help much beyond that. You chose to modify your phone and risk that you would not have issues, just like the rest of us here. In your case you did have issues. Now you have to get it back to stock so they don't have any reason to claim you caused this or that your warranty is void. I hope all goes well and it works out for you. Let as know and keep us posted. Good luck.
Lo N Slo said:
Nevermind i just read through that link you posted. So when i go to a t mobile store do i have to unroot or can i just hide my root applications until i get a new phone?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
We must have been typing at the same time LOL.
There is a thread on unrooting, and basically it is just deleting a few things. After doing this you should not have any non-stock applications on the phone and there would be no reason to think it was rooted unless they went digging on the file system. Personally, I would delete those telltale files just in case, it looks a little suspicious to bring in a phone that looks like it has not been used since you bought it, but they have no proof you did anything and you can claim that you first did a factory reset to see if it would fix the problem.
Just want to keep this thread going, as I am having the exact same issue as the OP as of today. It happened out of the blue, and I haven't flashed anything new to my phone since JI6 was released, other than that, it's just a stock, rooted phone.
Hoping someone has an idea, but I will likely get it replaced under warranty, since the GPS has never worked either.
damnit damnit damnit I really wish I had warranty.
Random question about clockword mod recoveries.
If I were to do a backup right now, and save that file to my computer, could I restore that file later on a different phone after I root my replacement?
I don't have that many mods flashed, and I know all of the apps can be synced, but still it would be sooo convenient .
I believe that is how it works, so yes. It should be no different then when you clone a hard drive to put the image on multiple computers for easy distribution.
It is (just like the cloning metaphor) hardware specific. Just like I could not purchase a upgrade computer and expect a cloned image to work, don't expect to create a Vibrant backup and restore it on a Captivate.
That said, you should be able to restore your backup to new (identical) hardware.
By the way, what is the warranty on these? I thought it was a year for defects. I didn't think the Vibrant had been around long enough yet for anyone to be off warranty.
it should be a year, but there was also the option for a purchased warranty. I did not purchase a warranty, so I should be good on just my manufacturer's defect warranty
Being discussed here:
http://forum.xda-developers.com/showthread.php?t=817643
Hi there,
your first thought might be: Ah jeez another one posting the same **** 2000 people posted before ^^. But anyways i think my problem is a special case:
yesterday i wanted to flash another radio to my htc magic via clockwork recovery. However something must have gone wrong. After the recovery rebooted my phone i got stuck at the "htc magic" splash screen. Pressing the home or the back or vol-down button or home and back button at the same time doesnt change the situation. still stuck at splash screen. fastboot and recovery dont seem to work.
After some really bad panicking minutes, i pulled the batery out of the phone and let it rest, while googling and searching the **** out of every forum on the net. Some minutes later i reassembled the battery and started the htc magic without pressing any other buttons, hoping it would juts boot and say "kidding ))" on the display. but yeah ... it didnt ^^.
Now im coming to the odd part, which differs from most other posts i saw on other forums and here on xda: after quite a while my htc magic suddenly made that "bling bling" sound, as it did whenever it started android successfully. i nearly burst into tears when i heard that sound, hoping that i would be able to access the phone via fastboot or adb. but ... i wasnt able to :S. the screen went black after that "bling bling" sound and stayed that way until i pulled the battery again.
i could repeat that procedure and reproduce the sound and behaviour, but i couldnt access the phone via any possible way i could find on the web :S.
hopefully somebody, who knows more can help. my last step would be jtagging the phone. but the tools are kinda pricy for such an "old" phone. and i couldnt find anyone in my area who could borrow me the tools or repair the phone for cheap money.
thanks in advance im counting on your knowledge
Try this low cost JTAG
tested by me with 2 T-Mobile Mytouch 3G
thanks for your fast response. if jtagging really is my last chance:
- what did you pay for all the parts of the schematic ?
- how long did it take you to put everything together?
- do i need a parallel port on my computer, or is it possible to use an usb port ?
- and do you think a newbie to smoldering and stuff could be successfully assembling all those parts?
- can you provide me with links and/or other pictures, which could help me?
thanks again for your effort
kinda exciting this whole thing :>
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: