Related
The problem: I flashed a radio to my device that is (obviously) incompatible with my device (if you really want the details, its embarassing, but I'll post if necessary). My phone freezes on bootup, and never initializes the Radio/ROM (and for good reason).
This is what happens now: If my phone is off, I can turn it on, but I only get the first boot up screen, and the red numbers in the bottom right-hand corner never appear. At that point, I cannot turn off my phone without taking out the battery. If I take out the battery and put it back in, and attach the phone to a charger (or USB cable), the light on the phone will "breathe", as if its charging. However, if I then disconnect the phone, the light will CONTINUE breathing.
I also cannot turn on the phone while its connected to either the charger or USB cable.
My phone is Hard-SPL'ed and Security Unlocked. But the real issue I'm having is that I can't get into Bootloader to flash something else. Apparently, I've corrupted the Bootloader. When I turn the phone on, and press the reset button while holding Vol-down, the phone just goes black.
I might be okay getting a warranty exchange if not for this: I can still hard reset my phone. It doesn't make any sense to me, but when I turn it on, I can do the soft-reset-button, Vol-down, Action button combo, and my phone flashes through Bootloader to give the the hard reset menu. It flashes that screen just long enough to see that my phone has 1.90Olinex as the SPL. So, I think I may be screwed, unless someone here can help.
My wife is very . . . upset . . . about this, and is worried that we'll have to spend money because of my continuous "tinkering" with my phone.
Any help anyone can offer is greatly appreciated.
I know this is my own stupid fault, and I should've known better, but it would be nice to get confirmation from the experts here that I'm just going to have to chalk one up in the "L" column at this point.
Q
Have you tried to flash from the SD card?
Hi Captain_Throwback,
Try copying Raph Radio 1.11.25.01 to the root of a FAT32 SD Card ... you'll need to rename the .NBH to RAPHIMG.NBH.
Pull the SIM out of the phone and power it back on as per usual; I've noticed that the phone "blacks out" for a bit but then switches to flash mode.
Good luck.
PS: suggest getting the large carry-on with the wheels for the guilt trip - heaven knows it's come in handy for me
That's a bummer, man. You gotta at least 'fess up part of the story to prevent someone else from falling into the same trap (however unlikely that may be). And maybe, just maybe, it will help someone else figure out how to fix your problem.
What radio did you try and flash.
Hopefully it wasn't the new Rhodium radio? Or a Rose radio?
I have done this a few times on my tilt, all I did was put it into the boot loader, it worked from hard reset screen as well, and flashed the rom via activesync. I am assuming that you are not able to get a sync, or have you tried yet? I know my fize will also sync [to flash] from bootloadr.
Captain_Throwback said:
The problem: I flashed a radio to my device that is (obviously) incompatible with my device (if you really want the details, its embarassing, but I'll post if necessary). My phone freezes on bootup, and never initializes the Radio/ROM (and for good reason).
This is what happens now: If my phone is off, I can turn it on, but I only get the first boot up screen, and the red numbers in the bottom right-hand corner never appear. At that point, I cannot turn off my phone without taking out the battery. If I take out the battery and put it back in, and attach the phone to a charger (or USB cable), the light on the phone will "breathe", as if its charging. However, if I then disconnect the phone, the light will CONTINUE breathing.
I also cannot turn on the phone while its connected to either the charger or USB cable.
My phone is Hard-SPL'ed and Security Unlocked. But the real issue I'm having is that I can't get into Bootloader to flash something else. Apparently, I've corrupted the Bootloader. When I turn the phone on, and press the reset button while holding Vol-down, the phone just goes black.
I might be okay getting a warranty exchange if not for this: I can still hard reset my phone. It doesn't make any sense to me, but when I turn it on, I can do the soft-reset-button, Vol-down, Action button combo, and my phone flashes through Bootloader to give the the hard reset menu. It flashes that screen just long enough to see that my phone has 1.90Olinex as the SPL. So, I think I may be screwed, unless someone here can help.
My wife is very . . . upset . . . about this, and is worried that we'll have to spend money because of my continuous "tinkering" with my phone.
Any help anyone can offer is greatly appreciated.
I know this is my own stupid fault, and I should've known better, but it would be nice to get confirmation from the experts here that I'm just going to have to chalk one up in the "L" column at this point.
Click to expand...
Click to collapse
Damn I'm sorry to hear about your issue and i feel for ya because I did some stupid **** myself a lil' while back if you remember. Your advice to reflash the oem rom worked for me 100%. Have you tried hard resetting and then trying to get into bootloader mode?
AllTheWay said:
What radio did you try and flash.
Hopefully it wasn't the new Rhodium radio? Or a Rose radio?
Click to expand...
Click to collapse
Ok, I'll tell you . . . it wasn't a Rose radio (I know P1Tater bricked his phone that way) . . . but I figured, the Rhodium, its got the same hardware, right? I mean, T-Mobile is a GSM carrier . . . If I patch it for Raph, it may work . . . even though the radio number is so much different . . . I should still be able to get into Bootloader if it doesn't work, because I'm HardSPL'ed . . .
But no. I can't get into Bootloader. Believe me, I've tried. Every time I try, the phone just goes black. And I have a nice stock AT&T ROM on my Storage Card ready to flash, if only I could get it onto the phone.
I tried plugging into the computer, but it won't recognize the phone at all.
I wish it was REALLY bricked, but the fact that I can still hard reset it is very disappointing.
Captain_Throwback said:
Ok, I'll tell you . . . it wasn't a Rose radio (I know P1Tater bricked his phone that way) . . . but I figured, the Rhodium, its got the same hardware, right? I mean, T-Mobile is a GSM carrier . . . If I patch it for Raph, it may work . . . even though the radio number is so much different . . . I should still be able to get into Bootloader if it doesn't work, because I'm HardSPL'ed . . .
But no. I can't get into Bootloader. Believe me, I've tried. Every time I try, the phone just goes black. And I have a nice stock AT&T ROM on my Storage Card ready to flash, if only I could get it onto the phone.
I tried plugging into the computer, but it won't recognize the phone at all.
I wish it was REALLY bricked, but the fact that I can still hard reset it is very disappointing.
Click to expand...
Click to collapse
This happened to me (sort of.) I flashed a diamond radio to my fuze... without security unlocking it first. Symptom wise, Exact same thing happened. I was able to (after days of tinkering) get it into bootloader from the hard reset screen. I just kept pressing the Hard rest sequence over and over while connected to USB. I noticed, one time, I got the USB at the bottom. Don't know how, don't know why, it just happened, I was then able to flash the Stock Cing ROM. Wierd stuff, But lucky. Hope you get it back on board. Is it insured? Because it would really suck if someone stole your bricked fuze.
Intertrochanterica said:
This happened to me (sort of.) I flashed a diamond radio to my fuze... without security unlocking it first. Symptom wise, Exact same thing happened. I was able to (after days of tinkering) get it into bootloader from the hard reset screen. I just kept pressing the Hard rest sequence over and over while connected to USB. I noticed, one time, I got the USB at the bottom. Don't know how, don't know why, it just happened, I was then able to flash the Stock Cing ROM. Wierd stuff, But lucky. Hope you get it back on board. Is it insured? Because it would really suck if someone stole your bricked fuze.
Click to expand...
Click to collapse
It is insured, and paying $125 is better than having to buy a brand new phone, but if I can avoid spending money, my wife would be much happier .
I can hard reset just fine . . . if only the phone would stay on the bootloader screen when doing that . . . but it doesn't. I assume the bootloader has been corrupted, which is why the phone blacks out when trying to enter bootloader mode. I'll keep trying, I guess. I can't make it any worse. Actually, if I could, I'd be better off, so that way they can't find out my phone is Hard-SPL'ed.
Captain_Throwback said:
I can hard reset just fine . . . if only the phone would stay on the bootloader screen when doing that . . . but it doesn't. I assume the bootloader has been corrupted, which is why the phone blacks out when trying to enter bootloader mode. I'll keep trying, I guess. I can't make it any worse. Actually, if I could, I'd be better off, so that way they can't find out my phone is Hard-SPL'ed.
Click to expand...
Click to collapse
Try plugging it into a car battery, or something like that, and fry the sucker. That's my only piece of advice.
Captain_Throwback said:
I can't make it any worse. Actually, if I could, I'd be better off, so that way they can't find out my phone is Hard-SPL'ed.
Click to expand...
Click to collapse
You could make it worse if you get the white sticker wet and make it turn pink, but that would be very bad for you.
You are at the point to where you cant move beyond your current predicament in wither way. Im afraid I see no other alternative than to pay the $125.
Maybe you could sell your Fuze on Ebay for 125 to cover your insurance cost and you could make a notation on the Ebay site saying something like 'PARTIALLY USED FUZE' like that Carfax commercial does.
update
My phone is still bricked, but I'm taking it to a repair shop after work, where I'll find out whether I'll be getting a free warranty replacement, or paying $125 for an insurance replacement. At least I've been able to successfully determine that a Rhodium radio cannot be flashed to a Raphael. So no one else has to try it .
Keep us updated dude. Also, if you slip the guy $50 he may do the free warranty replacement for you... it might save you $75 and you wont have to use up one of your insurance claims.
Captain_Throwback said:
My phone is still bricked, but I'm taking it to a repair shop after work, where I'll find out whether I'll be getting a free warranty replacement, or paying $125 for an insurance replacement. At least I've been able to successfully determine that a Rhodium radio cannot be flashed to a Raphael. So no one else has to try it .
Click to expand...
Click to collapse
Crap, sorry to hear that. HAAH, just walk into the ATT store and say," I tried turning the phone on and this is what happened." And that you have never heard of XDA forums, roms, and though a radio was only for people in trucks or that wear camo.
iceman4357 said:
Crap, sorry to hear that. HAAH, just walk into the ATT store and say," I tried turning the phone on and this is what happened." And that you have never heard of XDA forums, roms, and though a radio was only for people in trucks or that wear camo.
Click to expand...
Click to collapse
That might work, if I hadn't bought the phone from my best friend, who just happens to manage an AT&T store. He actually knows that I had a custom ROM on my phone, and called ahead to the repair shop to let them know I was coming, and he said hopefully they won't notice the SPL in my bootloader if they try and hard reset it. So it is possible they'll just give the phone a cursory look to make sure its really not working, and then go ahead with a warranty replacement. I'll be sure to let everyone know what happens. In the meantime, the word of the day is "dumbass", LOL.
Farmer Ted said:
Try plugging it into a car battery, or something like that, and fry the sucker. That's my only piece of advice.
Click to expand...
Click to collapse
That's what I would do.
Captain_Throwback said:
My phone is still bricked, but I'm taking it to a repair shop after work, where I'll find out whether I'll be getting a free warranty replacement, or paying $125 for an insurance replacement. At least I've been able to successfully determine that a Rhodium radio cannot be flashed to a Raphael. So no one else has to try it .
Click to expand...
Click to collapse
Honestly I would not take it to the repair shop.
Here is what I would do. Call the warranty replacement department at AT&T. 1-800-801-1101. Tell them that you woke up and now your phone won't turn on. Once you go through all the steps they have to do to fix it, then they will ship you a replacement Fuze right away. The refurbished Fuze will have everything except for a battery and a back cover. Typically when I did this I received a new one the next day that I called.
Now take your battery out of your phone and your SIM card and microSD card. Put your phone in the microwave for 2 seconds. Walla. Now it's bricked and AT&T will have no way to tell if you have HardSPL or a cooked ROM on your phone. Trust me. It will work.
When you get your new phone just send the phone back in packing material that they provide to you and you won't have to spend any money to get a new phone or spend money to fix a phone.
Just do what I told you about. I promise it will work. Just trust me. I've done it before and it worked like a charm. No worries. Trust me, I'm not trying to lead you down the wrong path. I'm trying to get you a replacement just like I got when I bricked my last fuze trying out different radios. And use the phone number that AllTheWay posted just above me once you do what I told you.
P1Tater said:
Just do what I told you about. I promise it will work. Just trust me. I've done it before and it worked like a charm. No worries. Trust me, I'm not trying to lead you down the wrong path. I'm trying to get you a replacement just like I got when I bricked my last fuze trying out different radios. And use the phone number that AllTheWay posted just above me once you do what I told you.
Click to expand...
Click to collapse
I'm curious what it is you told him, in case i'm in a similar position at any point !!
Lemme kno please here or PM is cool!
Thx
JFlitt
AllTheWay said:
That's what I would do.
Honestly I would not take it to the repair shop.
Here is what I would do. Call the warranty replacement department at AT&T. 1-800-801-1101. Tell them that you woke up and now your phone won't turn on. Once you go through all the steps they have to do to fix it, then they will ship you a replacement Fuze right away. The refurbished Fuze will have everything except for a battery and a back cover. Typically when I did this I received a new one the next day that I called.
Now take your battery out of your phone and your SIM card and microSD card. Put your phone in the microwave for 2 seconds. Walla. Now it's bricked and AT&T will have no way to tell if you have HardSPL or a cooked ROM on your phone. Trust me. It will work.
When you get your new phone just send the phone back in packing material that they provide to you and you won't have to spend any money to get a new phone or spend money to fix a phone.
Click to expand...
Click to collapse
Agree with this. If your friend works at the store and knows what you have done, I wouldnt go there. Call the number, fry the damn phone and get a new one. We need you back on your feet to help solve ROM issues my friend.
Has anyone successfully done this??
Link: http://forum.xda-developers.com/showthread.php?t=1220181
I finally hard-bricked my Vibrant, and I'm wondering if this has been accomplished, instead of sending it to a specialist to JTAG it the traditional way!!
Im trying to see if I can resurrect it myself instead of losing it for a week!
And yes I'm aware of the One guy here in the states that does JTAGing, but Id be seriously outa work for a week as my phone is my work/life line, cuz I'm an Independent contractor, so its not about the money Id spend but the time down without a way to work/communicate, I haven't contacted TMO yet and told them it was hosed using the Kies method to upgrade it to Froyo. Wish I never had done that!! Should've known better, didn't see/read any post about the horrors of using Samsungs KIES program until it was too late!!!
I was trying to purge a SH 5.0 install that went bad, I flashed back to stock Eclair. Then went to Froyo, But thats when I developed a problem with boot looping after doing Froyo, so I tried the KIES program to go to "FROYO" and that's when It bricked!!!
Anyways its bricked hard, and I'm wondering if this has actually been done successfully!
And any tips that I might need to get the Heimdall Program to actually detect it thru the USB method, would be awesome! Even though it wont turn on!!
Link to the thread: http://forum.xda-developers.com/showthread.php?t=1220181
JTAG isn't a method that can be done through usb. If you had googled jtag, you would have found out that it is a physical port built into the motherboard of our phones. In fact most electronics have a jtag port.
*Joint Test Action Group**(*JTAG*) is the common name for what was later standardized as the*IEEE
1149.1**Standard Test Access Port and Boundary-Scan Architecture*. It was initially devised for testing*printed circuit boards*using*boundary scan and is still widely used for this application.
Today JTAG is also widely used for*IC*debug ports. In the embedded processor market, essentially all modern processors support JTAG when they have enough pins.*Embedded systems*development relies on*debuggers*talking to chips with JTAG to perform operations like*single stepping*and*breakpointing. Digital electronics products such as*cell phones
*or awireless access point
*generally have no other debug or test interfaces.
In order to flash your phone, it will have to be dismantled, and hooked up to the jtag box.
Beware of angry gingerbread man
Adamcooks, I read the entire squabble about this between you and RaverXX
I downloaded your one click as well!!
So can you give me some advice on how to get my phone to even simply turn on, WO the soldering involved using traditional method of JTAGing??? Mine wont power up or show any LED activity, nothing when plugged in or do anything using traditional methods known to work with "SOFTBRICKING"
I mean, it seems my Boot loader is corrupted, or the other file you suggested, when Raver and u were arguing!! If I could even get a faint indication of life from the phone, It could be brought back to DL, but a DL Jig, as well as all the other extensive methods to get it even to power on, let alone go into DL mode isnt working at all, after many, many try's!
Can your one-click program, with the proper BL's for my T959 Vibrant be acknowledged by either yours or Heimdall's Program, so as to even be able to flash this WO, Jtaging it, even if it wont even power up in any way to handshake with my lappy???
BTW, I'm not trying to start another **** storm, after what happened with RaverXX, but it seems some of the people who had the same scenario as I do, were successful, so I'm wondering between the 2 of you, how to approach and try this, I respect both ya'll's work and contributions, but for me the bottom line is to get my phone working once again, short of either#1 JTAGing it, or trying to go thru the painful experience of trying to get TMO to replace it with a new same model, because KIES fubar'd it!!
Anyway I wish you 2 guys could lay out the proper set of instructions as you suggested, along with the proper files or links, for us to try either his method or yours. I think its possible to resurrect these phones, this way short of physical damage, and as such!! IDT you 2 fellas would've put so much effort into this theory, if there wasn't some merit to it!
So I'm all ears and eyes to your suggestion of how to get my phone to even breath again, so I can go back to DL mode, and get her working again!!
But when nothing what so ever happens, no power up, no lights, no nothing occurs, it seems to me its bricked, even though you say a truly bricked phone , has physical hardware damage, which tech is prolly correct, however in this case, mine is software bricked very hard!!!! And for purposes of communication and clarity, Ill stick with bricked, If I knew the MB was fried and or damaged, Id simply order another one, and replace it, and power up the phone, and be done with this ordeal, but my corruption occurred during using the Samsung KIES program, regrettably!!
And I'm fairly certain that either the Boot loader file is corrupted or the file you say creates a black screen usually displaying the Pc-phone logo is done for, so again, should I try the command prompt instructions to fix that, or do I use your one-click, or go to ravers method ?? I asking legitimately, because I know your knowledge in these matters has merit!! Thanks for your reply!!
Unless he changed his account, that was a different Adam in that other thread. I still say try it, cant make things any worse.
Sent from my ZenDroid, meditating on the XDA App
I may give a sharp response sometimes, but an internet squabbler I am not. connextion(sp) has a motherboard cradle that contacts the correct pins to jtag flash, without causing any damage to your phone.
Have you tried the resistance jig? I think that skorpn is the one who makes them ( 301k ohm resistor plug into the usb port can force d/l mode if the bootloaders aren't borked)
these are the last two resorts in ng phone resurrection.
Beware of angry gingerbread man
Ya My mistake Sorry
Ya I got you mixed up with another developer who has a very similar handle, so many apologies, however I wasn't flaming you anyway, shape or form, just apologizing for the mistaken ID
BTW Is the skorp resistance Jig a completely different animal from the DL Jig Tech Mobile sells doing the same result, in other words is it able to bring a phone like mine in the condition it is, into DL mode??? I saw the Skorp design, it just seems to me, its the same thing I already have from Tech Mobiles design. Accomplishing the same thing, but for phones that actually power on in some way shape or form, light off etc!!
Anyway thanks for your input, and effort, I'm still sorting all the info on everybody's suggestions and methods, short of JTaging it!!! Gonna make a move on a procedure here soon, this evening!!
My Fascinate had an unbrickable mod done a few months ago. I tried flashing CM to it, and now it doesn't boot or go into recovery mode. Download mode is ok so far, but only with a jig. Windows and Odin can't see anything. On Linux (Ubuntu physical box not virtual) the 'unbrickable resurrector' (team hummingmod) doesn't find the device. Heimdall only prints a pit file after it first goes into dl mode, then just detects it but fails the loke handshake everytime until it goes into dl mode again. USB drivers were installed (libusb). Almost everything online says that the phone should be recoverable (like from a soft-brick) but the phone's not even getting detected. The place I mailed it to seemed to know what they're doing, but I'm wondering now if the mod was not done perfectly and if that could be causing this weird issue now. This is my main phone, and none of us are getting any younger so let's get some ideas on this asap.
Mainly, I'm wondering how to turn this from a paperweight back into a phone?
I would contact the people that did it and see what they say.
Unreliable repair site?
ndowens said:
I would contact the people that did it and see what they say.
Click to expand...
Click to collapse
I sent the repair place several messages, and they didn't respond. It's Mobile Tech Videos. When I first got the mod done a few months ago, they seemed ok. Now it's like they just don't even want to hear about the possibility of there being an issue with their work. I have friends that fix these locally, and they've also tried getting it to work using different boxes and setups so it doesn't seem like the problem is on my end (not saying it's definitely not, just doesn't seem so). I sent them messages asking whether they've had any similar issues, and if it's possible to rule out the original mod as the issue. Nothing, not a courtesy response. Nothing, like they just decided to ignore the whole issue. I actually left them some good feedback for them (originally), now I'm wondering if someone else will read that and think that this place is a reliable repair shop -- I'd feel guilty for steering them to the wrong place based on feedback that's no longer current. I could understand if they had assisted a customer in using the mod (that I paid them to do) and then that customer just didn't want to do anything, just complain, then yes I could understand that they'd not want to deal with that. But I actually just started by sending a message that there was an issue, and if they've got a workaround. Since I paid them to do this, I thought they'd at least respond. Nothing. So that could make a person wonder if they know that there's an issue with their work and just don't want to say. Personally, I'd say a business owner with integrity should either stand behind their work or issue a refund in good faith. That's the problem is that there's not enough accountability in these issues.
The phone seems pretty well bricked right now, and since A) it's one of the older original androids and B) this no one's responded here with any ideas and C) I don't know any one locally who I can trust to jtag it -- it seems more and more likely that this is a real brick.
hello all, i just bought a new i9300, already downloaded a bunch of roms, but didn't even had the chance to install any of them.
first of all i want to say this is my third i9300 i done things with(installed recovery kernels and others), also had 2 i9100 and lots of other android phones, so i'm much familiar with ROMs, Kernels, CWM and TWRP, etc.. and also reads carefully every time i do something new (while this one was already done by me to friends devices)
this time something really really strange happened and my new device is now completely dead
i came home, turned it on, everything fine.
installed new drivers, run toolkit v.7, recognized and everything is ok
after all the steps it was in download mode, but Odin didn't show anything.
tried another PC, restarting the device, nothing. odin won't recognize it.
then i tried entering download mode with the key combination, Home button + Power Button + Volume Down.
entered download mode just fine, but still, no odin.
i tried 3 times, first with the cable disconnected, second with the cable connected, and third with the cable disconnected.
on third time something just so weird happen, it entered a different stage, something i don't know, and didn't find anything about it while googling.
all i remember is 4 rows written in red and green
when i turned off the device, it refuse to wake. nothing. no download mode no recovery no indicator for battery charging. just plain nothing
reminding you this is brand new device which was never even massed with odin. just some stage i never seen in my life.
can someone tell what was that stage i was on? why it massed my device in an instant? how in the world i managed to enter a boot-stage i can't find any information about
also to state, the i read about the sdcard mode (need the device opened and to short something) and it's defiantly not this stage.
hope someone can help
thank you very much
return for warranty claim if it has never been messed with is the sensible thing to do
slaphead20 said:
return for warranty claim if it has never been messed with is the sensible thing to do
Click to expand...
Click to collapse
thanks for replay, but the thing is i bought this device from regular shop not samsung distributor in my country
so i don't know if i can even call them
and the shop i bought from don't want any part with it (saying its my fault)
Looks like SDS
The vendor is responsible for warranty repairs not Samsung .
Samsung offer the user an extra limited warranty .
jje
Give it for warranty saying that the phone hanged up then died and you can't even turn it on. Not a word about download mode or anything, act like you know nothing about flashing
As much as i want, the seller refused to take it
so im in bad shape, new device just going to trash
I hope someone can provide information for how a button combination can destroy my device completly.
now im afraid to buy a new one
Sent from my GT-I9100 using Tapatalk 2
What country are you in?
You could take it to Samsung service centre if you have one nearby.
Noambugo11 said:
As much as i want, the seller refused to take it
so im in bad shape, new device just going to trash
I hope someone can provide information for how a button combination can destroy my device completly.
now im afraid to buy a new one
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
This is one of the risks we all run when we mod our devices. just going into download mode should not have done this to your device. Look in your device manager and see if it is even being seen by the pc. Could be the SDS that alot of people have seen
zelendel said:
This is one of the risks we all run when we mod our devices. just going into download mode should not have done this to your device. Look in your device manager and see if it is even being seen by the pc. Could be the SDS that alot of people have seen
Click to expand...
Click to collapse
Hey, if it was the SDS, then i would been triggered anyway from anywhere,
this situation is far more complex, as i said, by the same button combination it entered a different boot stage and not the normal download mode (nor recovery mod), iv'e been searching the hole web just to find a clew to what the hell is this stage, and why it massed my device so badly.
i'm from israel, and i don't think we have samsung service center, just a representer or something.
if i can i will defently send it to samsung all over the world, i just need a phone number or something to contact with them,
do any think samsung will take this device? if so where can i contact them?
Noambugo11 said:
Hey, if it was the SDS, then i would been triggered anyway from anywhere,
this situation is far more complex, as i said, by the same button combination it entered a different boot stage and not the normal download mode (nor recovery mod), iv'e been searching the hole web just to find a clew to what the hell is this stage, and why it massed my device so badly.
i'm from israel, and i don't think we have samsung service center, just a representer or something.
if i can i will defently send it so samsung all over the world, i just need a phone number or something to contact with them,
do any think samsung will take this device? if so where can i contact them?
Click to expand...
Click to collapse
This reminds me of a case we saw just the other day here in the threads. The DL screen was not the normal download screen and it turned out to be a clone device. Think this may have been the case?
zelendel said:
This reminds me of a case we saw just the other day here in the threads. The DL screen was not the normal download screen and it turned out to be a clone device. Think this may have been the case?
Click to expand...
Click to collapse
thanks a lot for your kind answers, when you say clone device you mean not a real i9300? cause if so them i 100% sure it's a real one and not a fake.
i was able to enter download mode while in the toolkit (enebling USB debugging first), but odin didn't show the device at all, then i tried the button combination; Power button + Home Button + Vol Down.
first it entered fine, still odn didn't catch it, second time also into the right download mode
third time, different stage, 3 rows written in red 1 row in green (much like sd-mode, but i'm quite sure it wasn't it, and even if is, how the world i managed to enter it by button combination only?)
i can't remember what was written, i think the word emmc been there, but can't be sure
this thing drive me crazy, i've done it 3 times with other i9300, i did it for i9100, i did 3 galaxy ace, also i9000, did some htc phone,replace many screen for phones and massed with this kinda of stuff a lot, in the PC world, iphones, everything. i can't consider myself noob or even close to it, i never rush into things before reading carefully.
and the matter that no-one know even what i'm talking about making me really think i wan't really responsible for it, but got a bad luck with a faulty device or something. and now i'm stuck with it cause nothing is connected between me and samsung (unless someone here some kind of idea)
Noambugo11 said:
thanks a lot for your kind answers, when you say clone device you mean not a real i9300? cause if so them i 100% sure it's a real one and not a fake.
i was able to enter download mode while in the toolkit (enebling USB debugging first), but odin didn't show the device at all, then i tried the button combination; Power button + Home Button + Vol Down.
first it entered fine, still odn didn't catch it, second time also into the right download mode
third time, different stage, 3 rows written in red 1 row in green (much like sd-mode, but i'm quite sure it wasn't it, and even if is, how the world i managed to enter it by button combination only?)
i can't remember what was written, i think the word emmc been there, but can't be sure
this thing drive me crazy, i've done it 3 times with other i9300, i did it for i9100, i did 3 galaxy ace, also i9000, did some htc phone,replace many screen for phones and massed with this kinda of stuff a lot, in the PC world, iphones, everything. i can't consider myself noob or even close to it, i never rush into things before reading carefully.
and the matter that no-one know even what i'm talking about making me really think i wan't really responsible for it, but got a bad luck with a faulty device or something. and now i'm stuck with it cause nothing is connected between me and samsung (unless someone here some kind of idea)
Click to expand...
Click to collapse
I have never seen this screen myself. The fact that you were able to get it to the screen the first few times is really odd. Sounds like one of the partitions got fried. I would send it back to samsung. This may end up costing you to have it repaired as well as shipping to the closest repair center, Here is the site that may help
http://www.samsung.com/il/#latest-home
Hey all, I'm new here and to Android phones in general.
I just picked up a Photon, not the Q, from a friend who had flashed it to Cricket. I'm looking to put it back to Sprint and replace the Duramax I have, but I'm not smart enough in phone tech to do it. I read somewhere that Motorola made it almost impossible to change PRLs and all that, and everytime I do the ##PRL# deal the screen shuts down for a split second and then pops back up the dialer screen, that happens with a few different ##codes. I've found a few different posts about how to do it, though pretty much all of them are for EVOs, but nothing in it seems to work for me, plus they assume one has the general know how already to do it. I'm a pretty quick learner and don't mind spending time getting to know different systems, so I was wondering if anyone could give me any extra info or links that could set me in the right direction. I appreciate your patience in this, I just want a better phone...
I'm looking through everything about flashing and I'm losing heart pretty quick. I was in the marines for four years and I though they had a lot of acronyms, holy crap... I'm about to call it quits and toss the phone unless there really is an easier-to-understand way of doing it. I don't care about rooting it or anything, I just want a smartphone that works with Sprint...
mrtoby86 said:
Hey all, I'm new here and to Android phones in general.
I just picked up a Photon, not the Q, from a friend who had flashed it to Cricket. I'm looking to put it back to Sprint and replace the Duramax I have, but I'm not smart enough in phone tech to do it. I read somewhere that Motorola made it almost impossible to change PRLs and all that, and everytime I do the ##PRL# deal the screen shuts down for a split second and then pops back up the dialer screen, that happens with a few different ##codes. I've found a few different posts about how to do it, though pretty much all of them are for EVOs, but nothing in it seems to work for me, plus they assume one has the general know how already to do it. I'm a pretty quick learner and don't mind spending time getting to know different systems, so I was wondering if anyone could give me any extra info or links that could set me in the right direction. I appreciate your patience in this, I just want a better phone...
Click to expand...
Click to collapse
I would say don't give up. I think it's quite simple.
Go here and read the last item in the post: http://forum.xda-developers.com/showpost.php?p=20331623&postcount=6
The pack below made by loki should have everything you need to flash an sbf file in rsdlite. I have never gone back to stock, but I did this process when I unlocked and rooted.
http://billionuploads.com/users/LokifishMarz/31/SBF's & Root-Unlock
You may want to confirm some of this with someone more experienced, but usually if you break something, it can be fixed.
I really really appreciate your response and suggestions knG333.
I tried what was posted, flashing the "1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US.sbf" file through RSD Lite a couple of times, but each time it would tell me there was an error flashing it. Do you know if, besides RSD mode, the phone has to have any other settings on it? Like, does debugging have to be on or anything?
Please forgive my ignorance in this, we all started from somewhere, right?
mrtoby86 said:
I really really appreciate your response and suggestions knG333.
I tried what was posted, flashing the "1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US.sbf" file through RSD Lite a couple of times, but each time it would tell me there was an error flashing it. Do you know if, besides RSD mode, the phone has to have any other settings on it? Like, does debugging have to be on or anything?
Please forgive my ignorance in this, we all started from somewhere, right?
Click to expand...
Click to collapse
There is one error message that is normal. Have you tried booting the phone up after flashing in rsd despite the error? "*RSD lite has a known bug where it will give a "failed" error during the final "rebooting phone" phase. IGNORE THIS ERROR AND MANUALLY REBOOT PHONE "
knG333 said:
There is one error message that is normal. Have you tried booting the phone up after flashing in rsd despite the error? "*RSD lite has a known bug where it will give a "failed" error during the final "rebooting phone" phase. IGNORE THIS ERROR AND MANUALLY REBOOT PHONE "
Click to expand...
Click to collapse
Yeah, I rebooted it manually and nothing seemed to have changed. Plus it said it failed during the flashing stage, not during the final rebooting stage, it didn't even get to the rebooting stage.
When the phone shows up in RSD Lite, is the program supposed to show all the details of the phone like IMEI and such? The phone is being recognized by the program, but only the model number is coming up, all other fields for the phone are saying N/A. Am I supposed to put the phone in any specific mode before hooking it up to RSD Lite besides RSD mode from the boot screen?
My previous distress has turned into stubborn perseverence, I'm going to get this thing fixed