My kindle fire hdx 7 bicked. And I tried to flash the rom downed from the amozon updating software named update-kindle-13.3.1.0_user_310079820 into it in the fastboot model. But I just cann't flash anthing into it because of the message that" Flashing not allowed for locked hw"
Is there anyone know how to solve this problem?
Same issue - FAIL: flashing not allowed for locked hw. Kindle Fire HDX 8.9 - trying to ROM CM10
I know this is going to sound harsh but please do read more before attempting something like this.
A quick glance of the threads on here will have made you quickly realise that flashing anything on the HDX is not possible at this time.
Threads like this do scare me. If you're not sure, don't do. Simple.
Sent from my KFTHWI using Tapatalk
How did you brick it?
Sent from my KFHDX using Tapatalk
failed1234 said:
How did you brick it?
Sent from my KFHDX using Tapatalk
Click to expand...
Click to collapse
Everyone needs to stop using the term "brick". It is 99% likely not a brick. Bootloop is not a brick. Stuck at boot screen is not a brick. QHSUSB_BULK mode is not a brick. They are just symptoms of something you did incorrectly & they are usually fixable with a little patience & common sense.
---------- Post added at 07:56 AM ---------- Previous post was at 07:51 AM ----------
failed1234 said:
How did you brick it?
Sent from my KFHDX using Tapatalk
Click to expand...
Click to collapse
Everyone needs to stop using the term "brick". It is 99% likely not a brick. Bootloop is not a brick. Stuck at boot screen is not a brick. QHSUSB_BULK mode is not a brick. They are just symptoms of something you did incorrectly & they are usually fixable with a little patience & common sense.
Well maybe I'll phrase it better: how did you screw up your Kindle?
Sent from my KFHDX using Tapatalk
GSLEON3 said:
Everyone needs to stop using the term "brick". It is 99% likely not a brick. Bootloop is not a brick. Stuck at boot screen is not a brick. QHSUSB_BULK mode is not a brick. They are just symptoms of something you did incorrectly & they are usually fixable with a little patience & common sense.
Click to expand...
Click to collapse
*ahem*
http://forum.xda-developers.com/showthread.php?t=2588608
lol
...but yah, if it's fixable it ain't "bricked"
Spec-Chum said:
*ahem*
http://forum.xda-developers.com/showthread.php?t=2588608
lol
...but yah, if it's fixable it ain't "bricked"
Click to expand...
Click to collapse
Soft Bricked?
Spec-Chum said:
*ahem*
http://forum.xda-developers.com/showthread.php?t=2588608
lol
...but yah, if it's fixable it ain't "bricked"
Click to expand...
Click to collapse
LMFAO...
Yeah, I know. But if you put bootloop there in the title, then I get a billion daily PM's asking if they have a bootloop or brick, so I include both words in the title. You would think with all the warnings, I wouldn't be getting so many "ooops" emails, yet there they are, every morning.
GSLEON3 said:
LMFAO...
Yeah, I know. But if you put bootloop there in the title, then I get a billion daily PM's asking if they have a bootloop or brick, so I include both words in the title. You would think with all the warnings, I wouldn't be getting so many "ooops" emails, yet there they are, every morning.
Click to expand...
Click to collapse
Reminds me of an old programming quote "Yay! It Works!!!11 It works!!11one. Well, it compiles. What does segfault mean???"
Related
Are hard bricks fixable?
If you're talking about the current one, no. Not unless you have a dev cable and the SBK.
Sent from my MB860 using XDA Premium App
IrshaadH said:
Are hard bricks fixable?
Click to expand...
Click to collapse
Well hard brick means unfixable... so something that seems like a hard brick that someone eventually finds a fix for, isn't really a hard brick anymore.
So no, not fixable, but it may not really be a hard brick.
Just like they said Hardbrick isn't fixable unless you know alot about technology. Softbrick is good as long as you retain the RSD you are good to go for the fixing.
I see, thanks for the input guys!
Does anyone have any experience with jtag and unbricking? I ask because after bricking two phones, a third probably won't go over so well with the warranty dept. I'm willing to pick up a jtag jig so that I can keep developing but I'd like to pick the brain of someone with experience in this area before I do so. Possibly someone with the hardware already whose willing to soft brick and attempt a recovery. I know its a lot to ask but if we have
a definite way to unbrick we can really go at it. Plus I'd be willing to use the jig I pick up to attempt unbricking for others if they soft brick while devving.
Sent from my ADR6300 using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=1618429
Sent from my ADR6425LVW using xda app-developers app
I saw that thread but he never posted whether or not he was successful
Sent from my ADR6300 using xda app-developers app
Don't tell me you bricked your rezound....
Sent from my ADR6425LVW using Tapatalk 2
---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------
Evocm7 said:
Don't tell me you bricked your rezound.... would be awesome if there was a way to unbrick. I'm going to search on this a bit.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Sent from my ADR6425LVW using Tapatalk 2
did you try to get you rezound into "download" mode? i know there was another member that could unbrick it if you could get into that mode. when i bricked i couldnt get it to work. but maybe your brick was a different type then mine
synisterwolf said:
did you try to get you rezound into "download" mode? i know there was another member that could unbrick it if you could get into that mode. when i bricked i couldnt get it to work. but maybe your brick was a different type then mine
Click to expand...
Click to collapse
qhusb_dload? I tried by doing the wire trick (like for s-off). I figured if I could get that I'd be able to recover but it wasn't working for me. Is there another way?
Right now I get no indication that the phone has any signs of life, no power on at all and not even a charge led. I have another one on its way but I really don't want to try for three strikes. I'm thinking I'm going to stay s-on for devving. It should be harder to brick then.
chad0989 said:
qhusb_dload? I tried by doing the wire trick (like for s-off). I figured if I could get that I'd be able to recover but it wasn't working for me. Is there another way?
Right now I get no indication that the phone has any signs of life, no power on at all and not even a charge led. I have another one on its way but I really don't want to try for three strikes. I'm thinking I'm going to stay s-on for devving. It should be harder to brick then.
Click to expand...
Click to collapse
This is the exact reason I never s-off'd. I don't need the smallest mistake to cost me a phone. With all of the aroma installers, it doesn't really seem necessary.
chad0989 said:
Does anyone have any experience with jtag and unbricking?
Click to expand...
Click to collapse
I've done similar stuff with routers.. not phones, but I imagine it's the same idea.
tcpsyn on gchat.
MajikUF said:
This is the exact reason I never s-off'd. I don't need the smallest mistake to cost me a phone. With all of the aroma installers, it doesn't really seem necessary.
Click to expand...
Click to collapse
You do know he's been working on cm9 to bring to us right?
Sent from my ADR6425LVW using xda premium
chad0989 said:
qhusb_dload? I tried by doing the wire trick (like for s-off). I figured if I could get that I'd be able to recover but it wasn't working for me. Is there another way?
Right now I get no indication that the phone has any signs of life, no power on at all and not even a charge led. I have another one on its way but I really don't want to try for three strikes. I'm thinking I'm going to stay s-on for devving. It should be harder to brick then.
Click to expand...
Click to collapse
yep thats the one. if you could get it into download mode then you can flash a stock recovery and stock hboot back on. but like you said, there was no life at all. it sounds like you did what i did. :/
i dont think you need to worry about how many you are RMA'ing. im on my 3rd now. 2 HW failure and this one has a bad screen.
synisterwolf said:
did you try to get you rezound into "download" mode? i know there was another member that could unbrick it if you could get into that mode. when i bricked i couldnt get it to work. but maybe your brick was a different type then mine
Click to expand...
Click to collapse
Wasn't the whole purpose of the "wire trick" that we used for S-OFF for forcing the phone into download mode?
**edit**
oops didn't read the whole discussion. My bad
synisterwolf said:
yep thats the one. if you could get it into download mode then you can flash a stock recovery and stock hboot back on. but like you said, there was no life at all. it sounds like you did what i did. :/
i dont think you need to worry about how many you are RMA'ing. im on my 3rd now. 2 HW failure and this one has a bad screen.
Click to expand...
Click to collapse
It would still be nice to have a solid way of unbricking. If I keep sending them back with the same exact problem I feel they would get suspicious eventually. Plus the new one I just got is pretty flawless so far, no dead pixels or anything so I'd like to keep it.
I have a new CM build sitting here right now that I'm terrified to try. Haha. So if you're uh sending the one with the bad screen back and want to try a couple things out first...
Yea that would be sick if we could get this to work. Probably, to find a JTAG/Uart port, we would have to take the board out of the device. I don't really wanna do it to mine since I wouldn't know how to put it back together
chad0989 said:
It would still be nice to have a solid way of unbricking. Plus if they keep coming back with the same exact problem I feel they would get suspicious eventually.
I have a new CM build sitting here right now that I'm terrified to try. Haha. So if you're uh sending the one with the bad screen back and want to try a couple things out first...
Click to expand...
Click to collapse
If you go S-On it should fix the bricking. Atleast that's what JonMan said lol
dmeadows013 said:
If you go S-On it should fix the bricking. Atleast that's what JonMan said lol
Click to expand...
Click to collapse
I concluded that also, since whatever partition is getting corrupted won't be able to be written to. But I haven't had the guts to try it again yet.
How about it with your new one and let me know. Haha. I'm already two bricks in.
chad0989 said:
I concluded that also, since whatever partition is getting corrupted won't be able to be written to. But I haven't had the guts to try it again yet.
How about it with your new one and let me know. Haha. I'm already two bricks in.
Click to expand...
Click to collapse
Lol I haven't gotten my new one yet went to VZ yesterday and they said they only had new ones in stock and no warranty replacements. They offered me a Razr. Why couldn't I just get a new one? I dunno... Dumbass Verizon lol
Gonna try HTC Repair Department today and see if I can get one from them. If not I'll just keep trying at VZ
dmeadows013 said:
Lol I haven't gotten my new one yet went to VZ yesterday and they said they only had new ones in stock and no warranty replacements. They offered me a Razr. Why couldn't I just get a new one? I dunno... Dumbass Verizon lol
Gonna try HTC Repair Department today and see if I can get one from them. If not I'll just keep trying at VZ
Click to expand...
Click to collapse
trade you my rez for your gnex
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------
a.mcdear said:
Wasn't the whole purpose of the "wire trick" that we used for S-OFF for forcing the phone into download mode?
**edit**
oops didn't read the whole discussion. My bad
Click to expand...
Click to collapse
lol no worries.
---------- Post added at 02:10 PM ---------- Previous post was at 02:09 PM ----------
chad0989 said:
It would still be nice to have a solid way of unbricking. If I keep sending them back with the same exact problem I feel they would get suspicious eventually. Plus the new one I just got is pretty flawless so far, no dead pixels or anything so I'd like to keep it.
I have a new CM build sitting here right now that I'm terrified to try. Haha. So if you're uh sending the one with the bad screen back and want to try a couple things out first...
Click to expand...
Click to collapse
do you think it has something to do with the kernel that is causing the bricks?
One thing I'm worried about is if devs stay s-on to prevent bricking then how would they know if their stuff would brick other people's phones or not?
Sent from my ADR6425LVW using Tapatalk 2
ijustwantmydock said:
One thing I'm worried about is if devs stay s-on to prevent bricking then how would they know if their stuff would brick other people's phones or not?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
what about if everyone s-on's ? i mean s-off is nice but if it means brick/no brick....
dmeadows013 said:
Lol I haven't gotten my new one yet went to VZ yesterday and they said they only had new ones in stock and no warranty replacements. They offered me a Razr. Why couldn't I just get a new one? I dunno... Dumbass Verizon lol
Gonna try HTC Repair Department today and see if I can get one from them. If not I'll just keep trying at VZ
Click to expand...
Click to collapse
Just call *611 and keep hitting 0 until you get someone. They'll transfer you to the tech support people and they'll hook you up.
I had 4.1.1 unlocked and rooted. I reverted back to stock and locked bootloader updated to 4.1.2 and had a bootloop. I ran the no you verizon and it fixed the bootloop but it won't give me root or unlock my bootloader. I would upload my pastebin but limited due to little posts.
no2burner said:
I had 4.1.1 unlocked and rooted. I reverted back to stock and locked bootloader updated to 4.1.2 and had a bootloop. I ran the no you verizon and it fixed the bootloop but it won't give me root or unlock my bootloader. I would upload my pastebin but limited due to little posts.
Click to expand...
Click to collapse
for those having problems with roms pre vramc3 and are having boot loop problems I would recommend getting a usb jig on eBay or Amazon or making one.
http://galaxys2root.com/galaxy-s2-hacks/how-to-make-a-usb-jig-for-your-galaxy-s2/
It'll save you a ton of time dealing with those finicky pit files and spending hours on Odin.
Then you can download whatever stock Rom and flash it with Odin!
eboodnero said:
for those having problems with roms pre vramc3 and are having boot loop problems I would recommend getting a usb jig on eBay or Amazon or making one.
http://galaxys2root.com/galaxy-s2-hacks/how-to-make-a-usb-jig-for-your-galaxy-s2/
It'll save you a ton of time dealing with those finicky pit files and spending hours on Odin.
Then you can download whatever stock Rom and flash it with Odin!
Click to expand...
Click to collapse
You'll still have to use Odin and the pit files, all it does is boot your phone into Download Mode when you can't or have issues doing so.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
You'll still have to use Odin and the pit files, all it does is boot your phone into Download Mode when you can't or have issues doing so.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
Ah thanks for clearing that up : )
I don't have a boot loop anymore. Im stock with 4.1.2 but the "no you Verizon" get a critical error. And, I don't know why.
Post 4.... waiting another 5 min
post 5... :crying:
no2burner said:
post 5... :crying:
Click to expand...
Click to collapse
Try posting in the Casual thread and asking for help
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
Try posting in the Casual thread and asking for help
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I would but like I said I need 10 posts to post a url which I need to explain..
Post 7 yayyyy
no2burner said:
I would but like I said I need 10 posts to post a url which I need to explain..
Click to expand...
Click to collapse
You can always get around the url posting by doing something like wwwDOTgoogleDOTcom or something similar.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
You can always get around the url posting by doing something like wwwDOTgoogleDOTcom or something similar.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
In order to even post where I need to I have to have 10 posts anyways.
no2burner said:
In order to even post where I need to I have to have 10 posts anyways.
Click to expand...
Click to collapse
Ahh. I forgot about that.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
Ahh. I forgot about that.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
Im gettin there, I hope to be a regular on here now anyways so to the future! :highfive:
Yay 10 posts :angel:
eboodnero said:
for those having problems with roms pre vramc3 and are having boot loop problems I would recommend getting a usb jig on eBay or Amazon or making one.
http://galaxys2root.com/galaxy-s2-hacks/how-to-make-a-usb-jig-for-your-galaxy-s2/
It'll save you a ton of time dealing with those finicky pit files and spending hours on Odin.
Then you can download whatever stock Rom and flash it with Odin!
Click to expand...
Click to collapse
Dude please stop telling people about JTags and JIGs on eBay if their phone can boot then there is a 99.9% chance that there is a fix or workaround for what they're experiencing...usually people are not explaining the problem correctly but even still this guy said his phone is working and he is up and running....straight to the point just please stop telling people they need to buy extra stuff without first trying to help them or fully understanding what exactly the problem is that theyre experiencing....i know you want to help which in my opinion is fantastic but even if you dont know the answer try and look it up for them or direct them in the right place for further assistence before telling them they need to buy something which in reality is just not the case
JamesPumaEnjoi said:
Dude please stop telling people about JTags and JIGs on eBay if their phone can boot then there is a 99.9% chance that there is a fix or workaround for what they're experiencing...usually people are not explaining the problem correctly but even still this guy said his phone is working and he is up and running....straight to the point just please stop telling people they need to buy extra stuff without first trying to help them or fully understanding the problem theyre experiencing....i know you want to help which in my opinion is fantastic but even if you dont know the answer try and look it up for them or direct them in the right place for further assistence before gelling them they need to buy something which in reality is just not the case
Click to expand...
Click to collapse
I posted that before shangrila corrected me. You're right, I'm sorry :/ I won't be recommending that at all. I think those were the only two posts I made about them. Sorry!
Sent from my SCH-I605 using Tapatalk 2
eboodnero said:
I posted that before shangrila corrected me. You're right, I'm sorry :/ I won't be recommending that at all. I think those were the only two posts I made about them. Sorry!
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Its fine man it really is....most of the time if you can AT THE VERY LEAST boot your phone into download mode then you should be okay and there is probably a fix but you just have to find it....keep helping people man even just pointing someone in the right direction is a much much much better way to go about helping than telling someone to buy something that is very unnecessary.... Keep it up though man you'll be fine just please stop with the JTags and JIGs lol
So I reverted my bootloader back to 4.1.1 unlocked and rooted it again. Updated my radio to 4.1.2 now I feel like I have my phone again.
Sent from my SCH-I605 using xda app-developers app
Casual 4.1.2
Im trying to root on Note2 i605VRAMC3. But Casual stops to download Heimdall_1.4RC3_mac32.pkg over and over. I have a mac64 and have downloaded and installed Heimdall_1.4RC3_mac64.pkg but still with no luck. Can someone help me me, Thanks
I need some serious help, my galaxy s2 wont boot into recovery i just get a "firmware upgrade encountered an issue...", i cant get odin to recognize it, and during the time i could boot into recovery, i couldnt mount the sd card to flash a firmware, and last time odin recognized it kept getting stuck on modem.bin and say (write error) or something of the sorts, please i desperately need help
Here maybe this http://forum.xda-developers.com/showthread.php?t=2058683 could help you.
Sent from my GT-I9100 using xda app-developers app
Stop referring people to that thread of yours when phones aren't bricked. Immediately. Or I will deal with you. Are we clear ? :-/
If they follow those steps & the phone isn't bricked, they sure as fcuk will have a brick on their hands if it goes wrong.
This person's phone isn't even remotely close to being bricked, it's a simple case of 'Odin won't work' like 99.9999% of those cases on here, and the fix is usually very simple.
OP - This gets covered here so many times per week it ain't funny. Search for similar threads, there are a bunch troubleshooting steps you need to follow (This is the final time I'm typing that as well, from now on people will just get 'Search').
king_below_my_lord said:
Here maybe this http://forum.xda-developers.com/showthread.php?t=2058683 could help you.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
thank you but the problem is that i cant get odin to recognize the phone, and i cant seem to find a fix on the site that i haven't yet tried, so, i'm trying to see if anyone has anything other that install drivers, uninstall kies, and use samsungs cable, because i've tried all of those multiple times with no luck
MistahBungle said:
Stop referring people to that thread of yours when phones aren't bricked. Immediately. Or I will deal with you. Are we clear ? :-/
If they follow those steps & the phone isn't bricked, they sure as fcuk will have a brick on their hands if it goes wrong.
This person's phone isn't even remotely close to being bricked, it's a simple case of 'Odin won't work' like 99.9999% of those cases on here, and the fix is usually very simple.
OP - This gets covered here so many times per week it ain't funny. Search for similar threads, there are a bunch troubleshooting steps you need to follow (This is the final time I'm typing that as well, from now on people will just get 'Search').
Click to expand...
Click to collapse
Yeah I get it :thumbup: (that's why the first line of the guide is meant to and usually does, scare people off), but if he eventually reaches the desperation point(no amount of flash attempts succeeds) , following my guide would be better than blind flashing of pit files(in a case where recovery is completely inaccessible my guide is useless) , which I have seen people recommending to do, if the user is lucky enough to flash a kernel and bootup the recovery, memory block corruption(it can happen because of reasons like phone turned off while flashing via Odin, removing cable midway of odin flash, and possibly several others) can also be effectively corrected.
Edit :I have made the guide a little bit more safer so that any noob who ignores all the warnings and go ahead with the procedure will stop after the first step if he/she is not having corrupted block's, effectively keeping him/her safe.
Sent from my GT-P6200 using xda app-developers app
king_below_my_lord said:
Yeah I get it :thumbup: (that's why the first line of the guide is meant to and usually does, scare people off), but if he eventually reaches the desperation point(no amount of flash attempts succeeds) , following my guide would be better than blind flashing of pit files(in a case where recovery is completely inaccessible my guide is useless) , which I have seen people recommending to do, if the user is lucky enough to flash a kernel and bootup the recovery, memory block corruption(it can happen because of reasons like phone turned off while flashing via Odin, removing cable midway of odin flash, and possibly several others) can also be effectively corrected.
Edit :I have made the guide a little bit more safer so that any noob who ignores all the warnings and go ahead with the procedure will stop after the first step if he/she is not having corrupted block's, effectively keeping him/her safe.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
um so do you think there is hope, i really dont want to lose this phone...
gmatni said:
um so do you think there is hope, i really dont want to lose this phone...
Click to expand...
Click to collapse
Well I don't think you could even attempt my guide since you can't flash via Odin and don't have recovery, it works only for people who can somehow bootup into recovery.
Sent from my GT-P6200 using xda app-developers app
king_below_my_lord said:
Well I don't think you could even attempt my guide since you can't flash via Odin and don't have recovery, it works only for people who can somehow bootup into recovery.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
do you think you might have any other tips that might help me?
gmatni said:
do you think you might have any other tips that might help me?
Click to expand...
Click to collapse
Without Odin you're basically screwed, did you try different computers? Or are you sure that your usb port is in full working condition?
Sent from my GT-P6200 using xda app-developers app
king_below_my_lord said:
Without Odin you're basically screwed, did you try different computers? Or are you sure that your usb port is in full working condition?
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
i haven;'t tried a different computer yet but my laptop is basically new just less than a month old and i tried all of the usb ports on it
MistahBungle said:
Stop referring people to that thread of yours when phones aren't bricked. Immediately. Or I will deal with you. Are we clear ? :-/
If they follow those steps & the phone isn't bricked, they sure as fcuk will have a brick on their hands if it goes wrong.
This person's phone isn't even remotely close to being bricked, it's a simple case of 'Odin won't work' like 99.9999% of those cases on here, and the fix is usually very simple.
OP - This gets covered here so many times per week it ain't funny. Search for similar threads, there are a bunch troubleshooting steps you need to follow (This is the final time I'm typing that as well, from now on people will just get 'Search').
Click to expand...
Click to collapse
I hope you read all my replies (also those in the guide thread because I have explained some stuff and made some changes ) basically if a user ignores everything in my guide and flashes any of the pit files, only if the flash fails will he get a brick(as usual), otherwise he will have an sd card with a lot less space. I hope you don't mind me quoting you in my main post.
Sent from my GT-P6200 using xda app-developers app
---------- Post added at 02:26 AM ---------- Previous post was at 02:19 AM ----------
gmatni said:
i haven;'t tried a different computer yet but my laptop is basically new just less than a month old and i tried all of the usb ports on it
Click to expand...
Click to collapse
Try everything possible to get it working, like on a friend's computer, for some people changing computer's have worked.
Sent from my GT-P6200 using xda app-developers app
king_below_my_lord said:
I hope you read all my replies (also those in the guide thread because I have explained some stuff and made some changes ) basically if a user ignores everything in my guide and flashes any of the pit files, only if the flash fails will he get a brick(as usual), otherwise he will have an sd card with a lot less space. I hope you don't mind me quoting you in my main post.
Sent from my GT-P6200 using xda app-developers app
---------- Post added at 02:26 AM ---------- Previous post was at 02:19 AM ----------
Try everything possible to get it working, like on a friend's computer, for some people changing computer's have worked.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
alright i guess ill just do all i can and hope for the best, thank you for your time
Kies, where's kies?
Install Kies, and then kill it.
Sent from my GT-I9100 using xda app-developers app
My Solution
gmatni said:
i haven;'t tried a different computer yet but my laptop is basically new just less than a month old and i tried all of the usb ports on it
Click to expand...
Click to collapse
Yes...myself faced the same problem , i tried to 3 different laptops but ODIN didn't detect my S2 . Finally with my luck , it got detected in my Home PC and i flashed it..are you able to go to download mode ? if no use USB jig... :good:
Try this :
http://forum.xda-developers.com/showthread.php?p=42592007#post42592007
Wow. That's a magical fix
OP - You were told to search for similar threads, there are 6 or so other steps you haven't even tried once yet. Bottom line is, if you want your phone fixed, you're going to need to do everything and quite possibly do it over & over till it works. Nobody here can do that for you. If you can't be bothered trying 2nd or 3rd PC and go thru the troubleshooting steps as well on those if necessary, your phone is going to stay busted.
The end.
MistahBungle said:
Wow. That's a magical fix
OP - You were told to search for similar threads, there are 6 or so other steps you haven't even tried once yet. Bottom line is, if you want your phone fixed, you're going to need to do everything and quite possibly do it over & over till it works. Nobody here can do that for you. If you can't be bothered trying 2nd or 3rd PC and go thru the troubleshooting steps as well on those if necessary, your phone is going to stay busted.
The end.
Click to expand...
Click to collapse
ok so i tried on 6 computers with nothing, I installed kies on all of them then killed it nothing, I tried 5 versions of ODIN and that didnt work, I tried uninstalling all the phones drivers and installing them all over again, and still nothing...
How about your usb cable?
Sent from the little guy
gastonw said:
How about your usb cable?
Sent from the little guy
Click to expand...
Click to collapse
I tried 3 of them, the original Samsung cable, and an original LG cable, along with another generic one
Well, don't you think it would be smart to get another S2 cable?
Borrow it, buy it, whatever.
Sent from the little guy
gastonw said:
Well, don't you think it would be smart to get another S2 cable?
Borrow it, buy it, whatever.
Sent from the little guy
Click to expand...
Click to collapse
my friend has an S2 as well, I just borrowed his hes here with me, and still nothing, whats happening is that the computers arent even recognizing that something has been plugged in, none of them are, his phone is recognized instantly by odin and all, but once he unplugs his and i plug it into mine, it just does nothing
I just rooted and installed cwm using Odin, the noob proof way. But I keep going to reboot into cwm and I'm only getting the factory recovery, what gives?
Sent from my SGH-T999 using xda app-developers app
Resolved. Updated to 6.X
Sent from my SGH-T999 using xda app-developers app
Wrong Forum ?????
S3 trouble shooting? Nope, it's regarding an s3.
Sent from my SGH-T999 using xda app-developers app
Nickdroid86 said:
S3 trouble shooting? Nope, it's regarding an s3.
Click to expand...
Click to collapse
This is not S3 troubleshooting. This is International GT-i9300 S3 (Specifically) Troubleshooting...
Nickdroid86 said:
Sent from my SGH-T999
Click to expand...
Click to collapse
You don't have one of these phones.
Ok well my xda app just says sIII q&a and troubleshooting.. its mistake. Plus I could have an internship s3 also, either way cwm works the same across the two. For the sake of people jumping down my throat. Regardless it's resolved so this can be locked anyways.
Sent from my SGH-T999 using xda app-developers app
Nickdroid86 said:
Ok well my xda app just says sIII q&a and troubleshooting.. its mistake.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Might need the forum selection subscriptions updating on your app .
Nickdroid86 said:
For the sake of people jumping down my throat.
Click to expand...
Click to collapse
It would be a mistake to make an assumption that everything works the same on both devices. If I gave you an i9300 CWM recovery, you could brick your device.
I'm sorry you feel like people are jumping down your throat but they are not. It is for YOUR OWN PROTECTION. Be savvy and post in the right forums. We cannot guess if you have the wrong device and we can give you advice that can lead to your device being bricked forever. You would not be happy.
I would rather be told I am in the wrong forum than people not mention it in case they offend my delicate nature - then allow me to brick my device. You should be grateful we pointed it out to you.
Also, we are pointing it out for people here. FOR THEIR PROTECTION. What if someone came here and asked you for a link to the recovery you used? You post it still not knowing you're in the wrong forum. You could be partly responsible for how many bricks????
Now everyone knows and no one has a bricked phone. Knowledge prevails.
rootSU said:
It would be a mistake to make an assumption that everything works the same on both devices. If I gave you an i9300 CWM recovery, you could brick your device.
I'm sorry you feel like people are jumping down your throat but they are not. It is for YOUR OWN PROTECTION. Be savvy and post in the right forums. We cannot guess if you have the wrong device and we can give you advice that can lead to your device being bricked forever. You would not be happy.
I would rather be told I am in the wrong forum than people not mention it in case they offend my delicate nature - then allow me to brick my device. You should be grateful we pointed it out to you.
Also, we are pointing it out for people here. FOR THEIR PROTECTION. What if someone came here and asked you for a link to the recovery you used? You post it still not knowing you're in the wrong forum. You could be partly responsible for how many bricks????
Now everyone knows and no one has a bricked phone. Knowledge prevails.
Click to expand...
Click to collapse
Very well said good sir...
IF I HELPED YOU DONT FORGET TO SAY THANKS! I WOULD FOR YOU...
____________________________________
sent from my i577/1.5oc/running one hella LiquidSmooth
rootSU said:
It would be a mistake to make an assumption that everything works the same on both devices. If I gave you an i9300 CWM recovery, you could brick your device.
I'm sorry you feel like people are jumping down your throat but they are not. It is for YOUR OWN PROTECTION. Be savvy and post in the right forums. We cannot guess if you have the wrong device and we can give you advice that can lead to your device being bricked forever. You would not be happy.
I would rather be told I am in the wrong forum than people not mention it in case they offend my delicate nature - then allow me to brick my device. You should be grateful we pointed it out to you.
Also, we are pointing it out for people here. FOR THEIR PROTECTION. What if someone came here and asked you for a link to the recovery you used? You post it still not knowing you're in the wrong forum. You could be partly responsible for how many bricks????
Now everyone knows and no one has a bricked phone. Knowledge prevails.
Click to expand...
Click to collapse
I'm not reading all that because I'm busy, but apparently you are here more for argument, rather the helping side of things. The thread is over, and it would be a mistake to make assumptions, because that in itself was an assumption, the recovery I used said specifically it would work with either model. But thanks for your help I guess.
Sent from my SGH-T999 using xda app-developers app
Nickdroid86 said:
I'm not reaching all that because I'm busy, but apparently you are here more for argument, rather the helping side of things. The thread is over, and it would be a mistake to make assumptions, because that in itself was an assumption, the recovery I used said specifically it would work with either model. But thanks for your help I guess.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I'm not here for an argument. I'm here to stop people breaking their devices. Something that seems lost on you. It's a shame you're "too busy" to read the important information I just posted and too ignorant to realise that you're lucky nothing worse happened to your device.
For anyone who does actually care, since the t999 T-mobile USA device that the OP has, has completely different hardware, the kernels are NOT interchangeable, so no recovery is interchangeable either.
This thread needs to be locked and lost in the ether.
Actually, incorrect, I'm not ignorant at all, the only mistake I made was clicking on the "wrong forum" when it said "s3 q&a" because they failed to mention it was the international model, in my app. I never had any intentions on posting a link to the cwm file I used. Really guy, get over yourself. You made your awesome point now move on.
Sent from my SGH-T999 using xda app-developers app