Guys,
If anyone can help me, I'd be eternally grateful. I have a Telus Fascinate, which I flashed Darky's Rom 10.2, then updated to 10.3 and everything was awesome (Used the i9000 rom). Then I got cute and f'd up my phone. I put a theme on by booting into recovery and installing from zip. Now my phone is in a loop. It boots into Darky rom, then gives an error (Something about not being able to use a USB device) about 10 seconds after my home screen loads, then it reboots....continually. Now, I can't seem to get it to go into download or recovery mode using the three button thing. I have tried to search the forums, and if this is in a wrong area, my apologies.
I am totally desperate. I don't think it's bricked, but I am at a loss as to what to do. If I have to, I will build a jig, but that's way out of my comfort zone. Is there anything anyone can suggest to get my phone into download mode so that I can reflash.
Thanks to anyone and everyone who reads and tries to help.
BD
EDIT: Sorry, didn't see the date on this thread, at least it isn't from last year.
I am so glad I bought a jig. I was doing a Telus Fascinate for a friend and it did this as well when I flashed a different kernel. It was my mistake but I needed a jig none the less.
You can try plugging the cable in just as you press the buttons on the phone to get into download mode, that has worked for me in the past but you should just order a jig on eBay or somewhere. It is worth it or make one if you wanted but you said that was a little out of your comfort zone.
I did end up purchasing a jig on ebay, and it's the best $10 I ever spent. Took way to long to come, but everything is back as it should be. Thanks for checking in to help, Vakman.
Two things I learned from this experience:
1) It's best to have a jig if you are fooling around with the Telus Fascinate. It's a unique device and there just are not very many people with experience on the net. If I were to do it again, I'd buy the jig first. Best case, you don't need to use it, but it does provide peace of mind in case something does go wrong.
2) Custom ROMs are totally worth the trouble. I now have a great rom, running Gingerbread 2.3.4. It has been a huge upgrade to my phone. My GPS is functioning flawlessly and it was unusable before. I have improved battery life and have corrected all the hardware buttons so I am 100% fully functional. Highly recommend the Darky Rom 10.2.2 for the Telus Fascinate.
BD
Related
Hey guys, I want to quickly thank all of you who come by and read this and offer me any help, I GREATLY appreciate it!
So my story quickly in a nutshell, I was on Caulkins ics rom, I wanted to flash the new alpha build for CM9, didn't flash back to GB first, tried flashing using clockwork on the ics Caulkins rom, it froze, and now it won't boot up. What happens when I turn it on it;
1. Samsung Galaxy S II - logo appears,
2. ... that is all. It resets every 15-20 seconds or so.
I cannot get into recovery mode using vol up+power button, however I can get into odin mode with vol dwn+power (which I was told because of this there is hope). However! I have tried both the one touch odin 181 EL29 restore/root, and it get's 98% done everytime, but gets stuck when it says writing the "data.img" and it never progresses further from there. I have tried this numerous times with different cables, different usb ports and different computers.
Now when I try the other odin 185 version, I have attached all the appropriate tar files and md5 files in the pda, phone and csc slots, and have tried MANY different files for those and watched several videos from QBKING77 and others dealing with how to restore using odin, but everytime I have flashed with this version of odin, everything works fine and my phone resets and all... but once again... never gets the past the Samsung Galaxy S II logo, and it keeps resetting every like 15-20 seconds.
Does anyone know what I can do? Or is there no hope and should I make a claim with my insurance? I haven't tried a jig yet, but idk if that would really help me out in this case,
any and all thoughts and comments are greatly appreciated,
again, thank you for your time
If nobody else has a better idea for you, this is the site I keep available for if I slip up for some reason.
http://mobiletechvideos.mybigcommerce.com/samsung-epic-4g-touch-jtag-brick-repair/
Good luck.
Sent from my SPH-D710 using xda premium
Not to be a ****, but you realize there are at least a dozen threads about this exact issue right? I know we all make mistakes but you really, really need to read before you flash, and read before you post..
http://forum.xda-developers.com/showthread.php?t=1525495
http://forum.xda-developers.com/showthread.php?t=1591199
Those were just on the first page of general. Of course this also comes up dozens of times in every ROM thread. Learn to read people, this is embarrassing. We all felt bad a week into ICS but now there is so much evidence that it's just embarrassing.
If you had taken the time to do a Google search rather than post you would know your phone is hard bricked and cannot be fixed. You can either file a claim with asurion for a hundred bucks if you have insurance (which is the right thing to do) or you can lie and go to Sprint and hope they swap it for you in store. But since that is at best questionable and at worst fraud, you should pay the moron tax and file a claim. Even doing that is ridiculous since you are affecting all of us every time you file a claim that was preventable. Every root related claim is one tiny step closer to the end of claims for root related issues.
http://www.google.com/search?hl=en&...cO2twf8hfSHCA&ved=0CCcQrQIwAA&biw=320&bih=533
Sent from my SPH-D710 using xda premium
@abhaxus- there is no need to be so rude. You can point someone in the right direction without sounding so harsh.
VDub2174 said:
@abhaxus- there is no need to be so rude. You can point someone in the right direction without sounding so harsh.
Click to expand...
Click to collapse
Actually I dont think he was harsh he was right on point... He notated links that can be used for reference and yes he is 100% correct. There are numerous links and new threads popping up every day about the same exact issue. Within mostly all ICS threads it shows how to flash different roms... He also started his post as not to be a ****...
Ok people seriously we got to do better when dealing with these ICS roms since we can all start a new post to get the community to help us but we can not read posts where the community has given great advice to be safe.
2OP sorry about what happen to you but most get stuck with the blue light of death. It seems like yours may be trying too boot up. Try sfhubs odin packages and see what happens. Hopefully you can get into download mode. Sorry bout what has already been said but what you did has been posted a million times as something not too do... Please try and be more careful in the future so this stuff wont happen to you again...
Good Luck
If it is getting stuck on data.img, you are screwed. The EMMC memory was corrupted by the ICS-based kernel and custom recovery. By the time ODIN gets to it, it is too late, nothing will write to your /data partition because the EMMC memory is damaged. ODIN, Mobile ODIN, CWM, JTAG will all fail.
Your option is basically to return your phone for replacement, either from Sprint or Samsung.
Thanks guys for all the input, and I know, I didn't wanna waste more space and time starting a new thread and all, but I did search, and did a lot. But everything I found was with people posting that they were still able to get into recovery, but I am not able to. I will check out the links given above, thanks for the help folks
ok long story short. never flashed a kernal before but i decided to try cm10 and went with the gingerbread build and so i flashed the kernal and cm10 compatible rom. it wasnt running very well so i flashed back to the froyo kernal and the compatible cm10 rom.
all was ok but i wanted to go back to cm7 because the phone was considerably faster and so...
today tried to restore one of my cm7 kang back ups from recovery and the phone died. i think what happened is i got mixed up with the back ups and i must have restored the gingerbread cm10 first and without realiszing it flashed the cm7 with a froyo kernal and bang we have a dead phone. it simply wouldnt boot past the google lettering and so when i got home i decided to flash a full sbf and start from scratch however when i tired i got the dreaded battery low error so i followed this
http://forum.xda-developers.com/showthread.php?t=892026
and it worked but rsd lite didnt show my phone. there was simply nothing there when i started it. all very annoying so i uninstalled everything and by the time i started again i got the message battery low.
so my question is can mcgyver work if the battery is actually really low say 10-20 per cent or less?
is it worth buying a new fully charged battery and using that?
why wouldnt rsd lite recognize my phone?
is there anyway to charge the battery when it is like this?
nb. i am running windows 7 sp1 and have installed the latest drivers and rsd lite am my phone is a moto defy m525 red lense.
all very annoying and in five years of rooting and flashing i have never been in a situation where i couldnt recover it. too be honest i have been here before with the defy but i had a spare battery and a proper wall charger and so that was problem solved but i dont own them anymore and i am now not sure/ cant remember if a simple full battery will help hence the questions.
In theory it should work. You are supplying the terminals with the intended 5V and a ground.
However it is recommended to charge your battery, use an external battery charger and then flash the SBF. Its hell of a risk trying to flash SBF with low battery. The phone may actually brick with no way to restore it.
it is strange but using the mcgyver method i can get the bootloader ready to program i simply cant get rsd lite to see my phone and neither does windows. there are loads of posts and threads on this but not many (none actually when the situation i am is mentioned) offer a solution.
so i have ordered a new battery which will hopefully arrive tomorrow and i will see how we get on from there.
rockmonkey1973 said:
it is strange but using the mcgyver method i can get the bootloader ready to program i simply cant get rsd lite to see my phone and neither does windows. there are loads of posts and threads on this but not many (none actually when the situation i am is mentioned) offer a solution.
so i have ordered a new battery which will hopefully arrive tomorrow and i will see how we get on from there.
Click to expand...
Click to collapse
do u have blank flash mode enabled in rsd?
does defy show up in device manager?
try switching usb ports
Sent from my MB526 using xda premium
nogoodusername said:
d
try switching usb ports
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
doh!
amazing i simply used another cable and usb port and then i had to unplug it and plug it again and drivers started to be installed. (i had already installed motos drivers but hey windows wanted more!).
i also went back to the older 4.9 version of rsd lite. it has been a long long time since i have had to do this. installing nordic and will try and install one of my other back ups. all should be well very soon fingers crossed.
looks like the spare battery i bought will be going back then. oh well.
cheers mate your post prompted me to try again and just tinker and it worked so appreciate that.
edit: seems a bit stuck and i am now a little unsure what to do. the android bootscreen is stuck and rsd lite is saying maually power up this phone. i am a little concerned because it is still saying in process even though it has flashed the sbf. i have tried turning it off and nothing happens. it looks like i am actually going to have to unplug the cables remove the mgyver wires and take out the battery and boot it.
bollox. it is dead again so i have to start again. trying a different sbf this time. not sure what happened there. maybe i was too impatient?
honestly not sure what is happening here. i have tried a standard blurred sbf 2.2 and the phone is now stuck on the m animation and rsd lite iks omce again saying manually start this phone. what in the world do i do next?
ah god i will have to do some more reading because it is ****ed. i now have a white light and black screen. rsd lite just remained stuck at 100 per cent in process and manually boot your phone. have tried it three times and that is all i get. not sure if it is because i am flashing froyo sbfs when i have had a 2.3 kernal on the device? it is why i have avoided flashing them in the first place and the first time i ever do bang i get a bricked phone when i try to restore it back to cm7. the phone came with 2.1 so should i be flashing them?
very boring and very very annoying.
getting quite tired of this little game and am on the brink of buying another phone.
ok i have a red lense defy and after much reading i have realised that i must be flashing the wrong sbfs now call me stupid but i actually am very confused about which one i need to flash.
i started on 2.1 originally then i flashed 2.2 and then stuck cm7 on the phone with a froyo kernal. however when i upgraded to cm10 i tried the 2.3 kernal.
so with this background in mind will this work???
http://forum.xda-developers.com/showthread.php?t=1595013
can i follow this to flash the sbf and get root?
or is there another sbf i need to flash. all i need to be able to do is root the phone and install cwm and then i can flash one of my back ups (properly this time).
rockmonkey1973 said:
ok i have a red lense defy and after much reading i have realised that i must be flashing the wrong sbfs now call me stupid but i actually am very confused about which one i need to flash.
i started on 2.1 originally then i flashed 2.2 and then stuck cm7 on the phone with a froyo kernal. however when i upgraded to cm10 i tried the 2.3 kernal.
so with this background in mind will this work???
http://forum.xda-developers.com/showthread.php?t=1595013
can i follow this to flash the sbf and get root?
or is there another sbf i need to flash. all i need to be able to do is root the phone and install cwm and then i can flash one of my back ups (properly this time).
Click to expand...
Click to collapse
Thats for BL7.. Some Defy+ with 2.3.6 were BL7. You definitely don't need to flash it..
Just flash the last SBF that worked for you..
neo.ank said:
Thats for BL7.. Some Defy+ with 2.3.6 were BL7. You definitely don't need to flash it..
Just flash the last SBF that worked for you..
Click to expand...
Click to collapse
yes mate i did the last sbf i flashed over a year ago was nordic and i got the error as listed above. have no idea what i am doing wrong but i must be doing something. trouble is the new battery has arrived and i have already tried a new sbf and still getting the same problem... manually need to reboot the phone.
bit worrying because obviously i will only have a certain number of tries before this new battery dies on me.
edit: absolutely annoying. part of the problem with the guides on here are that they are mostly incomplete. they dont actually tell you everything you need to do. take for instance this the guide for unbricking
http://forum.xda-developers.com/showthread.php?t=1828639
it is totally useless because what he fails to mention is that
to boot into stock recovery you need to hold down the volume button when you power on the phone and you will get a droid with an exclamation mark and then you need to hold down both the volume up and down buttons which after a few seconds will take you to stock recovery. then you can wipe cache etc and the phone will boot. i found this out here (notice how people are telling the guy to simply flash a new sbf!)
http://forum.xda-developers.com/showthread.php?t=1608812
the mad thing is if i had found that simple post just above and knew about the up and down volume buttons i would have fixed the defy on the very first try. that is what is so annoying about this situation.
ok
red lense defy.
long story short i flashed one of the bl7 defy plus gingerbread sbfs.
so i have gone through the root procedure by installing the rooted sbf in rsd lite and then i can install 2nd init 2.0.3 and can get a custom recovery installed.
but every time i try to install cm7.2 euro skank it reverts back to the bootloader. here is what i have done twice in recovery with the exact same result.
wipe cache, data, dalvik and battery stats/ flash cm7 froyo kernal/ then flash the rom/ then flash gapps and then wipe again and then reboot.
when the phone starts again i am once again back to the bootloader and i have to start all over again.
so a very simple question from the position i am in what exactly do i need to do to get cm7 running on the phone.
double post but there are worse crimes!
ok so i have realised that i am stuck on the gingerbread kernal and that any froyo based rom is not gonna work.
wow how did i end up here! bloody hell that is what happens when you start getting ****ed off with the phone not doing what you think it should. anyways it is done now and i have cm7 all up and running and have even been able to make a back up so that if anything happens in the future when i am experimenting then i have a decent base from which to start. everything is working including the camera data wifi calls and well everything except...
i have one all rather serious problem that i really need to get sorted (this is it if i can fix this then i can leave the phone alone).
my battery is not recognized. now the phone runs on the battery which is a big step up from before where i was literally having to leave it plugged in just to keep it on. but the battery icon at the top is displaying a question markn and i dont know if it is charging or not. i also have no idea how much battery is left.
i have flashed both the defy red lense ics battery zip and the defy plus battery fix and i wiped cache dalvik and battery stats before i flashed them and the cache after but neither of these worked.
anyone actually care to help out here. what do i need to do to get my battery recognized? seriously if you know then please share because i have wasted a day and a half on this and through sheer frustration dug myself into a huge hole and it took ages to climb out.
all i am asking for is a bit of guidance from someone who actually knows what they are talking about. if that sounds like you do me a favour and simply tell me what i should do because i am now totally and utterly stumped.
cheers.
rockmonkey1973 said:
yes mate i did the last sbf i flashed over a year ago was nordic and i got the error as listed above. have no idea what i am doing wrong but i must be doing something. trouble is the new battery has arrived and i have already tried a new sbf and still getting the same problem... manually need to reboot the phone.
bit worrying because obviously i will only have a certain number of tries before this new battery dies on me.
edit: absolutely annoying. part of the problem with the guides on here are that they are mostly incomplete. they dont actually tell you everything you need to do. take for instance this the guide for unbricking
http://forum.xda-developers.com/showthread.php?t=1828639
it is totally useless because what he fails to mention is that
to boot into stock recovery you need to hold down the volume button when you power on the phone and you will get a droid with an exclamation mark and then you need to hold down both the volume up and down buttons which after a few seconds will take you to stock recovery. then you can wipe cache etc and the phone will boot. i found this out here (notice how people are telling the guy to simply flash a new sbf!)
http://forum.xda-developers.com/showthread.php?t=1608812
the mad thing is if i had found that simple post just above and knew about the up and down volume buttons i would have fixed the defy on the very first try. that is what is so annoying about this situation.
Click to expand...
Click to collapse
rockmonkey1973 said:
double post but there are worse crimes!
ok so i have realised that i am stuck on the gingerbread kernal and that any froyo based rom is not gonna work.
wow how did i end up here! bloody hell that is what happens when you start getting ****ed off with the phone not doing what you think it should. anyways it is done now and i have cm7 all up and running and have even been able to make a back up so that if anything happens in the future when i am experimenting then i have a decent base from which to start. everything is working including the camera data wifi calls and well everything except...
i have one all rather serious problem that i really need to get sorted (this is it if i can fix this then i can leave the phone alone).
my battery is not recognized. now the phone runs on the battery which is a big step up from before where i was literally having to leave it plugged in just to keep it on. but the battery icon at the top is displaying a question markn and i dont know if it is charging or not. i also have no idea how much battery is left.
i have flashed both the defy red lense ics battery zip and the defy plus battery fix and i wiped cache dalvik and battery stats before i flashed them and the cache after but neither of these worked.
anyone actually care to help out here. what do i need to do to get my battery recognized? seriously if you know then please share because i have wasted a day and a half on this and through sheer frustration dug myself into a huge hole and it took ages to climb out.
all i am asking for is a bit of guidance from someone who actually knows what they are talking about. if that sounds like you do me a favour and simply tell me what i should do because i am now totally and utterly stumped.
cheers.
Click to expand...
Click to collapse
First of all Stop whining about the guides being incomplete. They have helped a lot of people before you and are still helping.. If you mean every post should mention trivial stuff like booting into recovery and wiping data then just imagine the redundancy of the stuff.
If only you were patient enough to read before reacting. Defy Beginner's guide clearly mention 'bout booting into recovery & bootloader so its your folly for not collecting the info before processing..
anyone actually care to help out here. what do i need to do to get my battery recognized? seriously if you know then please share because i have wasted a day and a half on this and through sheer frustration dug myself into a huge hole and it took ages to climb out.
all i am asking for is a bit of guidance from someone who actually knows what they are talking about. if that sounds like you do me a favour and simply tell me what i should do because i am now totally and utterly stumped.
Click to expand...
Click to collapse
Don't know what you've wasted your day on, but all I can suggest is flash the battery fix for Defy+. Search for it. not difficult to find.
neo.ank said:
First of all Stop whining about the guides being incomplete. They have helped a lot of people before you and are still helping.. If you mean every post should mention trivial stuff like booting into recovery and wiping data then just imagine the redundancy of the stuff.
If only you were patient enough to read before reacting. Defy Beginner's guide clearly mention 'bout booting into recovery & bootloader so its your folly for not collecting the info before processing..
Click to expand...
Click to collapse
whining! i didnt think i was whining although i can get annoyed and sometimes my frustration is vented without thinking. i accept that the phone being where it is is indeed my fault. in fact if i had just left it alone then it would have been running as well as it ever did. i am also a great advocate of the developers who spend there time providing us roms and tools for us to use and i can say hand on heart i appreciate the fine work they do often for free. i am also an avid reader of the guides being a simple bod with very little knowledge of flashing hacking and what not and they have saved my bacon more times than i care to remember over the last four or five years. and so you are spot on the guides help a lot... not just me but many before me and most likely many after and give us mere mortals the chance to stay current with firmware long after the manufacturer has abandoned the phone. so while i may have been complaining rather angrily i was not whining.
the fact is that guide is incomplete. not only is it incomplete but it is the one that is linked to on the wiki as the guide to follow on how to unbrick your phone.
if you are like me a tinkerer who every once in a while likes to try out a new rom and who doesnt know the every inner workings of the procedures and who needs to follow instructions then i think the least you can expect is for the definitive guide to be correct! i mean that isnt too much to ask for is it.
so yes i do expect them to list every basic important step one must follow to fix the phone because that is what instructions do they guide people who dont know what they are doing. that is there sole purpose and if they dont do that job then they should either be edited so they do or deleted.
and yes yesterday i was very annoyed at the fact that the guide i was following does not actually tell you exactly what one should do and i can promise you if it had of done then i would not be in the position i am in it is as simple as that. i mean you cant seriously expect people to think oh right these are the instructions for unbricking the phone but i bet you they aint right so i had better read some more instructions for the same thing... and hey they might not be complete as well so i had better read yet another set just in case. leave it out will you.
at the end of the day it doesnt matter and at the risk of repeating myself i know that if i had left well alone the phone would be fine so ultimately i have no one else to blame but myself. if i had been a little more patient and less stressed wondering why the phone wouldnt boot after what appeared to be a successful flash then i would have got there in the end without being stuck on a gingerbread kernal.
neo.ank said:
Don't know what you've wasted your day on, but all I can suggest is flash the battery fix for Defy+. Search for it. not difficult to find.
Click to expand...
Click to collapse
well if you had read through this thread then you may have seen i have wasted a day and a half on quite a lot of reading as it goes. you may have also seen that i have flashed 2 battery fixes and that they havent helped. so i am wondering if you know what else i could do to fix the problem? if you do and you dont mind telling me then i would be grateful. if you dont then no big deal... i will read through a few more threads and see if i cant get to the bottom of it.
EDIT: I have reread what i wrote and i take that back the guide is far from useless in fact it is excellent and i mean that. in every other way it is spot on and is the de facto guide to sorting yourself out of a hole. but it does miss out some vital information that (i think at least) really should be there. still water under the bridge and all that. we are were we are and one must move on. bottom line it is only a phone and if it comes to it i will buy another. the only reason i havent actually bought another so far is the buld quality and form factor of the defy is still yet to be bettered. but maybe it is a sign a message from above telling me to move on to pastures new.... although i would still like to fix the battery issue.
ok it is fixed. as i was writing this reply i installed the white rabbit rom (which i read included red lense battery fixes). true to its word there are five downloadable files. i got four (one woudnt download) and rebooted the system and hey presto.
well what a difference a day and a decent nights kip make. and colour me impressed. this rom is a work of genius. i see it is based on euro kangs cm7 effort with a few nice (well actually loads) extras thrown in for good measure. have to say i am really liking it. calls data wifi camera and battery all work and it looks and feels swift and very polished.
so all is well that ends well. and what a journey. man all i wanted to do was restore cm7 from my back ups. flashing the gingerbread based cm10 before i did it i reckon screwed me and i didnt realise what i had done until after when it wouldnt boot. however xda saved the day as it always does (even if it did take me quite a lot time to get there this time round). i may even write a mini guide but then either no one would bother reading it or i would get loads of people whining at me telling me how it aint right so i think i will avoid that little task and leave it to people more brave and knowledgeable than i.
cheers all for the help in this thread, the time taken by others to write stuff down and the people who provide us with some great software for our ageing but still great phone.
me to
pls help
jalal-jap said:
me to
pls help
Click to expand...
Click to collapse
if you need help mate then a little bit more info is gonna be required.
i will say this that i havent quite fixed it completely. i have the rom running sweet as a pie and the phone will work away from a power source but the battery percent/ icon remains locked at 100 per cent so i have no way of knowing if the phone is charging. when i plug it in to my laptop it says usb connected but again it doesnt list it as charging. so i have no way of knowing if the battery is actually getting charged or how much is really left.
i am also far from an expert more a bumbling old timer who rarely posts here unless desperate.
bear all that in mind and i will do all i can to help (provided you specifically say what you want help with)
edit: lmao... i couldnt have picked a worse sbf to flash. amazing. i have been so so careful in all the time i have owned this phone (over a year i reckon now) and i may have finally actually broken it.
i aint even certain i can charge the battery and once it runs down it will simply die. obviously there is hope that someone will come up with a downgrade method at some point in the future but for the time being i think the phone is ****ed.
i will try ics tomorrow and see if i can get any joy there but i think the only way i can now use the phone is to buy an external battery charger. funny really i used to own both a spare battery and a charger for this very reason and yet i sold them when i got rid of the old defy. so i am gonna have to buy one off ebay tomorrow and use it that way. at least then i will be able to use the phone.
rockmonkey1973 said:
if you need help mate then a little bit more info is gonna be required.
i will say this that i havent quite fixed it completely. i have the rom running sweet as a pie and the phone will work away from a power source but the battery percent/ icon remains locked at 100 per cent so i have no way of knowing if the phone is charging. when i plug it in to my laptop it says usb connected but again it doesnt list it as charging. so i have no way of knowing if the battery is actually getting charged or how much is really left.
i am also far from an expert more a bumbling old timer who rarely posts here unless desperate.
bear all that in mind and i will do all i can to help (provided you specifically say what you want help with)
edit: lmao... i couldnt have picked a worse sbf to flash. amazing. i have been so so careful in all the time i have owned this phone (over a year i reckon now) and i may have finally actually broken it.
i aint even certain i can charge the battery and once it runs down it will simply die. obviously there is hope that someone will come up with a downgrade method at some point in the future but for the time being i think the phone is ****ed.
i will try ics tomorrow and see if i can get any joy there but i think the only way i can now use the phone is to buy an external battery charger. funny really i used to own both a spare battery and a charger for this very reason and yet i sold them when i got rid of the old defy. so i am gonna have to buy one off ebay tomorrow and use it that way. at least then i will be able to use the phone.
Click to expand...
Click to collapse
You're on BL7 now and there's a reason people advise to avoid it. Most of the fixes and scripts doesn't work with BL7 including the battery fixes.
I'd suggest you to go for Quarx's build for GB kernel (along with the battery fix), Randomly flashing ROMs and fixes won't help.
Moreover, I strongly recommend you to search and read carefully. You're not the first one to face the problem, and there's a solution. Even if you waste(?) a couple of days reading 'bout it, it won't kill your phone, but if you do something out of desperation it might.
neo.ank said:
Moreover, I strongly recommend you to search and read carefully. You're not the first one to face the problem, and there's a solution. Even if you waste(?) a couple of days reading 'bout it, it won't kill your phone, but if you do something out of desperation it might.
Click to expand...
Click to collapse
i take it you mean this like in retrospect? of course you are right a deep breath and a walk does wonders for a fuddled head and is far better than simply rushing into the next desperate attempt to repair. however it is easy to say this after the event yes!
the battery wont charge and if i flash another rom it gives me the big battery icon with question mark so i am once again stuck in a corner with no where to go. basically it is ****ed because none of the battery fixes work. the battery works when there is power in it but it just wont charge when in the phone. because the battery ran down last night the only way i can use my phone at the moment is tethered to the mcgyver trick.
so the plan is to buy a separate charger and use that to charge the battery. then i reckon i should be at least able use the phone (although this yet to be tested).
amazing seriously amazing. a year of owning this phone a year of flashing and hacking and being ultra conservative and then all it takes is a few minutes of madness and it is royally screwed. the crying shame about it is that i have installed the best rom i have ever seen in the white rabbit and if the external charger doesnt work i wont get to play with it! still live and learn.
edit: by the way do you know if the mcgyver trick actually charges the battery?
.
rockmonkey1973 said:
i take it you mean this like in retrospect? of course you are right a deep breath and a walk does wonders for a fuddled head and is far better than simply rushing into the next desperate attempt to repair. however it is easy to say this after the event yes!
the battery wont charge and if i flash another rom it gives me the big battery icon with question mark so i am once again stuck in a corner with no where to go. basically it is ****ed because none of the battery fixes work. the battery works when there is power in it but it just wont charge when in the phone. because the battery ran down last night the only way i can use my phone at the moment is tethered to the mcgyver trick.
so the plan is to buy a separate charger and use that to charge the battery. then i reckon i should be at least able use the phone (although this yet to be tested).
amazing seriously amazing. a year of owning this phone a year of flashing and hacking and being ultra conservative and then all it takes is a few minutes of madness and it is royally screwed. the crying shame about it is that i have installed the best rom i have ever seen in the white rabbit and if the external charger doesnt work i wont get to play with it! still live and learn.
edit: by the way do you know if the mcgyver trick actually charges the battery?
.
Click to expand...
Click to collapse
The battery fixes replace your battd.bin binary file which stores the info about the battery. Surprisingly there isn't a single binary that work with each phone, it acts weirdly and not sure what fix will work for a particular phone.. I again suggest you, every battery fix you find. You're not the first one to face the problem and its been sorted for many..
Mcgyver just supply the device with intended charge as the battery does. It doesn't charge the battery.
Don't know if you tried this one.
Defy Red Lens Battery Fix
neo.ank said:
The battery fixes replace your battd.bin binary file which stores the info about the battery. Surprisingly there isn't a single binary that work with each phone, it acts weirdly and not sure what fix will work for a particular phone.. I again suggest you, every battery fix you find. You're not the first one to face the problem and its been sorted for many..
Mcgyver just supply the device with intended charge as the battery does. It doesn't charge the battery.
Don't know if you tried this one.
Defy Red Lens Battery Fix
Click to expand...
Click to collapse
i have tried it mate. i have also tired the ics defy red lense and the white rabbit rom had four of them available to download. none of them have worked. basically as it is now the phone will not stay on without the mcgyver leads and the battery wont charge. i have flashed 6 different battery fixes.
edit: it is strange once i have given it a blast on mcgyver for an hour or so i can then use the phone normally. however the battery is locked at 100 per cent and there is no indication it is charging when a usb lead is plugged in. seriously i have tried 6 of the fixes and none have actually worked.
if you are saying there is a fix for this then i would love to know what it is because i havent found one yet.
edit again!!!: ok this is strange because now when i plug it in to a usb lead the green light appears as if it was charging. very very strange this. i mean like really ****ing weird.
final edit: ok i am officially giving up. it has beaten me and for the first time ever i have got myself into a situation that i cant get out of. who would have thought a simple battery would be the cause of so much ****ing grief. anyway. for total clarity.
i am now running white rabbit rom runs great highly recommended and way quicker than the cm10 efforts that are being worked on at the moment. i have tried 6 battery fixes. none work. i am sometimes able to use the phone without being connected to the mcgyver leads but the battery remains locked at 100 per cent. other times the phone dies and the only way to boot it again is the mcgyver leads. if i do that then battery may change to say 25 per cent or even 75 per cent. basically it is all over the shot. i have tried to install another rom and this leads to the exact same thing. if i turn it on without the mcgyver leads i get the battery error. sometimes when connected to the usb port the phone has the led green light like it is charging then other times it doesnt. it is basically well and truly ****ed up.
so i am giving up. i have wasted quite enough time on a phone i have been thinking of changing as it is. i am gonna buy a sensation as a short term replacement. not as nice as the defy form wise but far faster and with a decent modding community so it will do for now. i will return here every now and then to see if someone comes up with a way to downgrade the bl7 but until that happens the phone is gonna gather dust in my drawer.
i think this thread serves as decent guide as to what shouldnt be done if you want to unbrick your phone (and also includes a few little things that may be missing elsewhere) so hopefully someone can learn from it. cheers all and see you later.
ok well this is the end of this thread (unless i find a proper working solution).
i was unable to charge the phone unless i used the mcyver trick. basically the only way it would accept a charge was if the mcgyver leads were connected. however the battery would charge once the mcgyver leads were in place but stays locked at 100 per cent no matter what i do. it may be the rom i am using but every time i tried another i got the battery error.
i have now bought an external battery charger and spare battery. it works a treat. i simply use the charger to charge one battery and use the other battery to power the phone. when the battery dies i simply switch them around and use the phone as normal.
this way i am no longer having to boot the phone using mcgyver and the only thing i am missing is the ability to charge the battery internally or tell how much battery life is actually left.
so all told all is well that sort of ends well. at least i can carry on using the defy. i was looking at buying another phone but they are all either too big or too slippy/ fragile in the hand. the only one i would like to buy is the orange san diego but there is no root and even worse there is no sim unlock. so for the time being i will stick with the nearly indestructible defy and hope that moto see sense and release a four inch, 8mp onboard camera and better screen carbon copy. fingers crossed.
So... I was trying to port a skyrocket ROM to our device with CM9.1.0 as the base. I just flashed it on my device. Flash went fine. I thought it would be fine... However, when I hit reboot, nothing. Black screen. I don't know what happened. It doesn't seem to be responding to any commands. I'm trying a ton of things. I can't figure out anything... Somebody, answers please? Can I do anything? A jig maybe? Really hope this isn't the end for my SGS2...
Edit - Tmobiles generously sending me a new one for 5$.
DinoSoup said:
So... I was trying to port a skyrocket ROM to our device with CM9.1.0 as the base. I just flashed it on my device. Flash went fine. I thought it would be fine... However, when I hit reboot, nothing. Black screen. I don't know what happened. It doesn't seem to be responding to any commands. I'm trying a ton of things. I can't figure out anything... Somebody, answers please? Can I do anything? A jig maybe? Really hope this isn't the end for my SGS2...
Edit - Tmobiles generously sending me a new one for 5$.
Click to expand...
Click to collapse
I'm thinking you may have jumped the gun a little on the "getting a new phone from Tmobile"
I'm sure you've tried taking th ebattery out and holding the volume buttons with the power button and trying to get into recovery or download mode?
Also the Jog in my opinion would have helped as a last resort, XDA is filled with so much usefull info that it would prob have been better to get the phone working on your own so you can see why it happened.
I'm willing to bet it just got stuck on some kind of boot loop....But since your getting a new phone I'm sure your going to be nervous rooting the new one....Nothing learned
NhCarDealer said:
I'm thinking you may have jumped the gun a little on the "getting a new phone from Tmobile"
I'm sure you've tried taking th ebattery out and holding the volume buttons with the power button and trying to get into recovery or download mode?
Also the Jog in my opinion would have helped as a last resort, XDA is filled with so much usefull info that it would prob have been better to get the phone working on your own so you can see why it happened.
I'm willing to bet it just got stuck on some kind of boot loop....But since your getting a new phone I'm sure your going to be nervous rooting the new one....Nothing learned
Click to expand...
Click to collapse
Turns out, I had technically flashed a Skyrocket ROM (my port). Nothing can be done about that... Lesson learned: Don't port from skyrocket's stock ROMs.
I've read a lot about SDS and there seems to be no general consensus on the symptoms of it. Some people say they can enter recovery/dl/etc but the phone crashes all the time. Others say that their phone doesn't turn on at all and won't charge.
Here is my issue with my S3.
I just recently installed 4.3 pacman rom. I got everything set up and everything was going great. I tried to flash ACID MOD 7.0/DevilKernel, and they both failed, so I rebooted back into the system and the phone just shut off.
If I take the battery out and hook it up to a charger, the LED will light up. However, if I plug it in with the battery already inside of it, the LED does not turn on. Also, if I hook up the phone to my computer, it'll make a sound like it is trying to mount the device, but it'll make a stutter sound like it failed. It doesn't do this automatically, it only does it if I try to enter recovery/download mode/or turn the phone on.
I'm not sure if the phone is completely dead, or bricked, or what is going on? Or if anyone has any other suggestions - other than changing the battery, which I did do, lol.
Sounds bricked. What model is you s3 btw? And can you post links to everything you've flashed?
SDS doesn't affect our S3's, it was only the international model that had this issue, and I believe it was only on the original firmware.
Sent from my SCH-I535 using Tapatalk 4
http://forum.xda-developers.com/showthread.php?t=2015525
latest nightly
+ 4.3 gapps. it booted fine from gapps.
http://forum.xda-developers.com/showpost.php?p=38599629&postcount=1005
acid mod v7
2802 + 2805 for sammy devices
http://forum.xda-developers.com/showthread.php?t=2240832
devil kernel
prior to flashing pac i installed 2.6.3 twrp because the 2.5.x i was on did not work. i booted in, flashed pac, got everything set up. after restoring the apps and whatnot, i went back to twrp to install acid + devil kernel. they both failed, so i just rebooted from there and it never turned back on. i just assumed the battery was dead, charged my bat in my external charger, and yeah, never turned on since then.
any way to do this without jtag? i'm not at home right now to do something like that and am out of the country, so im a bit unsure how hard it'd be to get those supplies.
i was able to go to a samsung a/s place, but they would only send back to america. i don't think it is worth paying 200+ when this phone is probably only worth 400 or so out of the box, brand new, maybe even less.
i just assumed it was SDS because the symptoms seemed spot on, but it was really weird. i've never had any issues like this flashing roms and it wont' even go to the boot logo. if i plug it in, it makes it seem like it is trying to mount, but there are no vibrations or anything like that on the phone.
thanks for all the help doc, like always.
Thanks for providing the links! Makes it so much easier to help when we don't have to search for everything!
I'm afraid you have bricked your device. I don't know about the Acid mods compatibility with our device, so it may be part of the problem, but that kernel is for the international S3 (I9300/9305). (I'm assuming you have the T999 btw). Never flash anything for the international models, you're nearly guaranteed to brick the phone!
But there's hope! Verify your model number by looking under the battery. Then check out KAsp3rd's unbrick thread in the development section. It should be towards the top.
Give that a shot and say a prayer! It won't fix all bricks, it depends on what was overwritten, but there's a good chance it'll fix yours!
In the future, it's best to stay out of the international models forum altogether! The devices are very different and you take a huge risk when using anything you find there!
Good luck!
Sent from my SCH-I535 using Tapatalk 4
Thanks Doc. I don't think it'll be fixed unless someone in that thread wants to try to flash that devil kernel and see if they can unbrick it w/o jtag. I followed those instructions to a T, and no dice. Although, I can't really tell if my battery is charged right now. I don't have my external charger on me. I will try again tomorrow, but I really doubt it at this point.
Really? Maybe give it another try with a different SD if possible. I saw the posts there and there's no reason I can see that it wouldn't fix when aboot got overwritten.
Sent from my SCH-I535 using Tapatalk 4
DocHoliday77 said:
Really? Maybe give it another try with a different SD if possible. I saw the posts there and there's no reason I can see that it wouldn't fix when aboot got overwritten.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Yeah, it is really weird.
After some toying with it I figured out that it only tries to mount the device when connected to the computer IF and only IF my phone is connected to the computer with no battery. It didn't do this before, which is odd. Even if I take out the SD card it still does this now. Before it would fail to make any sound, and now it tries to install the driver. But then it says it fails to install the driver for it, which is the bricked one, the SUBS DWLND or whatever.
I tried following Kasp3rd's advice to hold the button down longer, and I held it down for a whole five minutes with no luck.
I will try another SD when I get the chance, right now I only have a 64gb with no avail to back it up. The SD card is super old though, you are right Doc. It is from my OG droid, but really I haven't had a need for SD cards since I was on an iPhone after my droid and since the S3 is mine, but i'm not using it, I never really bought a nice SD card for it.
I'm going to run to the store in a bit to get one though and hopefully that will make a difference?
May have missed the part about it being 64GB before. Could be the age, but also those 64's have given lots of folks some problems in the past. Seems the S3 can be a bit finicky with those.
Sent from my SCH-I535 using Tapatalk 4
i need help! ill donate a little cash to the first person that finds a working solution im absolutely stumped on this. two weeks ago i tried upgrading my rooted sprint note 4 from android 4.4.4 to lollipop and everything seemed to go well until i opened up the camera and i went in to a bootloop. since then it hasn't stopped. i have tried flashing stock tars with odin. ive tried CM roms, noterized rom, tons of roms with custom recovery. ive used windows xp, and windows 7, 2 different computers, different cables, different usb ports. odin with administrator rights. nothing will stick. ive gotten passes and fails with odin. when it passes the phone will work as long as im on a charger after first boot once it comes off the charger it immediately goes in to a bootloop and then will not go past the samsung logo and if it does it reboots at the Spark logo. ive wiped cache 3x and factory reset 3x prior to flashing ive checked threads for the past two weeks and only made this account to ask for help. im not new to rooting and have never encountered and issue like this before. i can get in to download mode and recovery so i still have hope its just beyond my knowledge. occasionally recovery bootloops unless im on a charger as well. can someone PLEASE help me?? its making my stomach sick. my only option for internet is a galaxy s5 i bought with root for hotspot so everything i do takes forever to download. sorry for the legthy post im just trying to be detailed as possible for what ive already tried. like i stated above ive done my research this is my last option. thank you.
Could be your battery is dying. Heard of similar situations where it was due to battery failing.
ianmb said:
Could be your battery is dying. Heard of similar situations where it was due to battery failing.
Click to expand...
Click to collapse
i was thinking that as well but with my luck figured that would be too easy of a solution and weird that it decided to go ploop immediately after the flash. i play XBL off my hotspot and it can get rather hot. i usually keep an ice pack with a piece of cloth under it when i run it for an extended period of time though. ill buy a cheap one on ebay as a test. appreciate your input.
ianmb said:
Could be your battery is dying. Heard of similar situations where it was due to battery failing.
Click to expand...
Click to collapse
hey the stupid battery was the issue. dm me your PayPal if you'd like and I'll throw you a couple dollars for a beer or something. I feel like an idiot.
AssmanProctologist said:
hey the stupid battery was the issue. dm me your PayPal if you'd like and I'll throw you a couple dollars for a beer or something. I feel like an idiot.
Click to expand...
Click to collapse
Not a problem. Just glad to help out. Keep your money bro, times are hard for some.