Related
Hey guys, im new to the scene, and while fiddling around with my Galaxy S3, i have managed to brick it! Here is what happened.
I rooted the phone using a tutorial from here:
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Everything worked fine and the phone successfully rooted. But than i came across roms ... and i found a tutorial that told me how to install CyanogenMod 9:
http://forum.xda-developers.com/showthread.php?t=1778165
I tried to follow the instructions, but i would get (Error 7), and i realized that this tutorial instructed me to install the ClockworkMod Recovery version 5.8.4.7. So i downloaded the file from ClockworkMod's website, and it was in a .img format. When i had rooted my phone and installed ClockworkMod i used a .tar version via Odin, and this time i had a .img. After going through many tutorials, i found someone that showed how to install the .img varient via Android Terminal Emulator. So i followed the instructions:
http://forum.xda-developers.com/showthread.php?t=1363132
After i was finished following the instructions i rebooted the phone. And boom, it would not turn on. I tried all variants of holding the external buttons etc. Than i plugged the phone into a Windows PC. and the phone shows up in device manager as "QHSUSB DLOAD". So after tirelessly researching, i finally found the drivers for this and installed them. And know the phone shows up in Odin as COM10 in yellow. So i tried to flash the stock Image. I fire up Odin, select PDA, than the stock image, and click start. This is all that happens in the "Message Log":
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
(I have attached a screenshot of the above)
Please guys, i just got the phone and now it is bricked, any help would be greatly appreciated. Thanks!!
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Hi, Thanks for your reply. I tried using a "Jig" and it did not put the S3 into download mode. LIke i said previously. When the S3 is connected to my PC it shows up as "QHSUSB DLOAD". And no Samsung drivers would work with it. I had to research and find the drivers that finally worked and allowed Odin v1.85 to see the phone as "COM10", and i select the ROM under the PDA and click the "Start" button. But than it does not go past SetupConnection. I thought maybe the "Jig" was faulty and didnt work, but i tested it with another working Samsung Galaxy S2, and it worked exactly as it was supposed to. Should i still try your suggestion or is it pointless?
neubauej said:
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Click to expand...
Click to collapse
Ouch.
It sounds like your bootloaders might be borked, so kinda pointless.
I would get ahold of Josh at www.mobiletechvideos.com as it sounds like jtag might be required.
Hey, Thanks for the info. But the image i flashed via the Android mobile terminal app on the phone, i was flashing a ClockworkMod v5.4.8.1, that was made for the AT&T i747 (I have the Bell i747M, which i am told is the same thing?) , is that the bootloader? I know someone here that is local that does the jTag repair. But im not sure if the problem i have is in relation to the bootloader. Please let me know. As the phone still does show up when connected to the PC.
neubauej said:
Ouch.
It sounds like your bootloaders might be borked, so kinda pointless.
Get ahold of Josh at as it sounds like jtag might be required.
Click to expand...
Click to collapse
I tried your solution. The phone when connected to the PC with does not show up in Odin 3.07 (Correct version for my phone, from your link), But if i turn on Odin 1.85, the phone shows up fine in that as COM10 in yellow. So does my phone need a jTag? Samsung Canada told me to send the phone in for service and they will reset it and send it back. At the moment the phone does not turn on or go into download mode, and when connected to the computer it shows up as HS-USB QDLoader. So my question is: If i send it to Samsung, will they discover that i have Rooted it and void my warranty and not fix the phone?
neubauej said:
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Click to expand...
Click to collapse
If you send it to Samsung its unlikely they will notice or care that its rooted.
I have sent them 2 devices that I wanted them to reflash after I did stupid things and hardbricked, fully expecting to pay for it, and it was returned to me flashed and at no charge. This was after I told the customer service rep that I was flashing custom firmware and i screwed it up.
YMMV.
The worst case scenario there is they void your warranty and charge you a minimal fee to reflash it.
As for your bootloaders, you pushed a custom recovery that failed, corrupted, or was an incorrect application. The recovery lies in the bootloader..
If it doesn't power up, won't go into download mode, and Odin won't flash it I'd say its jtag or send it to sammy time.
I see, well i do not care if they charge me anything. Money is not an issue, Ok well i just got the email from Samsung with the shipping label. Thanks for your information.
neubauej said:
If you send it to Samsung its unlikely they will notice or care that its rooted.
I have sent them 2 devices that I wanted them to reflash after I did stupid things and hardbricked, fully expecting to pay for it, and it was returned to me flashed and at no charge. This was after I told the customer service rep that I was flashing custom firmware and i screwed it up.
YMMV.
The worst case scenario there is they void your warranty and charge you a minimal fee to reflash it.
Click to expand...
Click to collapse
Goodluck!
Fyi 5.4.8.7 is the clockwork version I'm running.
After doing some more research, i found that another person with a different Samsung phone. Followed the same instructions to flash ClockworkMod via Android Mobile Terminal using the same instructions i did and got the same problem. On his post somebody told him that the flash was made to the wrong partition or something like that. So ... Lesson for next time. READ EVERYTHING BEFORE TRYING IT!
neubauej said:
Goodluck!
Fyi 5.4.8.7 is the clockwork version I'm running.
Click to expand...
Click to collapse
Yeah just go to Samsung. Its too bad u never read that the newer versions of CWM recovery don't work on the 747m. The 747 and our m variants are close but still a bit different in a few ways although when coming here for rooms and stuff we have to use this at&t 747. Section. There is a great rooting post under the development stickies and it mentions the UNICERSAL VERSION OF CWM RECOVERY FOR 747m phones and that is the one I used and all of us 747m users should install. 5.4.0.4 or something like that. Definitely not 5.8.x.x. I could have told u that would brick your phone and most proper posts would too. And unfortunately yes the recovery resides in the boot loader area so it can cause a brick.. so keep that in mind when u get your phone fixed. Either use the earlier cwm rec version or just change to TWRP RECOVERY which I just did and many recommend now anyways.
Good luck and I'll come back to post the link with the best root and cwm rec install forOUR 747M phones and remember there are some differences and not all 747 mods will work for us so please read up first
Sent from my SGH-I747M using xda premium
pchemerys said:
Yeah just go to Samsung. Its too bad u never read that the newer versions of CWM recovery don't work on the 747m. The 747 and our m variants are close but still a bit different in a few ways although when coming here for rooms and stuff we have to use this at&t 747. Section. There is a great rooting post under the development stickies and it mentions the UNICERSAL VERSION OF CWM RECOVERY FOR 747m phones and that is the one I used and all of us 747m users should install. 5.4.0.4 or something like that. Definitely not 5.8.x.x. I could have told u that would brick your phone and most proper posts would too. And unfortunately yes the recovery resides in the boot loader area so it can cause a brick.. so keep that in mind when u get your phone fixed. Either use the earlier cwm rec version or just change to TWRP RECOVERY which I just did and many recommend now anyways.
Good luck and I'll come back to post the link with the best root and cwm rec install forOUR 747M phones and remember there are some differences and not all 747 mods will work for us so please read up first
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
I don't think the version he used was the issue as other Canadian users report that 5.8.x.x works fine.
http://forum.xda-developers.com/showthread.php?p=29664739
Edit: the link with instructions for terminal emulator on the op is for the lg thrill which writes the recovery onto block 6. On this phone it needs to be written to block 18.
Sent from my HTC One S using xda app-developers app
Frowben said:
I don't think the version he used was the issue as other Canadian users report that 5.8.x.x works fine.
http://forum.xda-developers.com/showthread.php?p=29664739
Edit: the link with instructions for terminal emulator on the op is for the lg thrill which writes the recovery onto block 6. On this phone it needs to be written to block 18.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Ah yes..that makes sense. That would pooch the phone. As for cwm it appears I was mislead as I read on few posts that newest versions don't work or not recommended for Canadian variant but it appears u might be right and I'm now seeing more and more report that it is installable. I'll have to check it out. Thanks
You flashed a recovery for the LG Thrill 4G. At what point in time did you assume it was the same phone as the I747M? You have bricked your phone. It needs JTAG service. Samsung will probably cover it under warranty, or you can pay someone that has the equipment to do it. You have no other options at this point. When you get it back from repairs, make sure you only flash AT&T/Bell/Telus/Rogers I747(M) software to the phone....
Ya i got the phone back from Samsung after waiting 3 weeks. They had to change the motherboard on the phone. Yes, it was the wrong instructions i followed which screwed me over! Since than i re-rooted how i did the first time i got the phone. Just a few days ago i saw the new CyanogenMod 10 M1 Rom, which i wanted to install. And again like last time in order to install it i had to upgrade my CWM to the newest version. This time i did not rush into it like last time and consulted with my buddy who is an expert in Android. The problem i had last time was i downloaded the new CWM in an .img file, and this time i ended up finding the newest CWM in a .tar and used Odin to flash it successfully. Than i just installed the rom and was good to go. My main reason for wanting to install a custom rom was i was getting absolutely HORRIBLE battery life from my S3. I ended up buying a juice pack which greatly helped me out. But now that i have CM10 my battery life is phenomenal, + the juice pack i now go maybe 2 days without having to charge. Now my sister who has the Wind Mobile S3 T999V wants me to upgrade her rom to the same as mine. I have found the T-Mobile CWM for her phone, and all the relevant software, but i am still hesitant to install the CWM on her phone. The T-Mobile CWM 6.0.1.2 is compatible with the Wind Mobile S3 T999V right? Or do i have to use a different version?
just to be clear about where you went wrong (im sure its been said already)
the guide you followed to install cwm is from the lg thrill forum. so the command dd if=... of=... had the wrong device id which is the most common cause of a brick
its actually pretty difficult to mess up your phone as long as you don't use mods designed for other devices
jefferson9 said:
just to be clear about where you went wrong (im sure its been said already)
the guide you followed to install cwm is from the lg thrill forum. so the command dd if=... of=... had the wrong device id which is the most common cause of a brick
its actually pretty difficult to mess up your phone as long as you don't use mods designed for other devices
Click to expand...
Click to collapse
Yes, i know that. I realized after i had done everything that the instructions where for another phone. Now im trying to find the CWM 6.0.1.2 for my sister phone T-Mobile S3 T999V that is in a .tar file already. Any suggestions on where i can get it?
I use cwm 5.8 .0.4 i think and it works fine go to the dev stickies and its there
Sent from my SAMSUNG-SGH-I747 using xda premium
JB calhoun said:
I use cwm 5.8 .0.4 i think and it works fine go to the dev stickies and its there
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Ya for my sisters phone i have that version as a flashable tar, however to install CM 10 M1 i need to install CWM 6.0.1.2.
Did u try rom manager
Sent from my SAMSUNG-SGH-I747 using xda premium
HI I HAVE A GALXY 2 GT-I9100. IFLASHED CWM TOUCH AND I THINK IT BRICK THE PHONE OUT BECASUE OF THE KERNAL NOW I CANT DO ANYTHING CAN SOMEBODY PLEASE TELL ME HOW TO GE TI BACK UP
FIRST I DID THIS ONE
http://www.youtube.com/watch?v=55JTQ...HCZ6Xly1BrqSIA
THEN WHEN I COULDNT GET A ROM TO FLASH AND GET IT TO COME BACK UP I TRIED THIS
http://galaxys2root.com/galaxy-s2-ha...-on-galaxy-s2/
AND IT STILL DIDNT WORK
Ok first off if you have a I9100 you are in the wrong forum because judging by your profile it says you have tmobile. This is the forum for the sprint variant with the model number d710. The forum I think you are looking for is here
Edit: I saw that you actually did post there... and it looks like you need to try this link below. My bad.
http://forum.xda-developers.com/showthread.php?t=1721229
It's pretty easy just make sure you follow the instructions.
TheSilverStig said:
Ok first off if you have a I9100 you are in the wrong forum because judging by your profile it says you have tmobile. This is the forum for the sprint variant with the model number d710. The forum I think you are looking for is here
Click to expand...
Click to collapse
its the sprint one i typed the wrong thing its the d710
Good luck
ok there is no coming back from a true brick... So if it wont turn on or your pc wont recognize it then yes it is truly bricked and you may need to contact JTag service which I hear is like $50. Also you are in the wrong forum for your phone. I would post this in the GALXY 2 GT-I9100 forum and see who can help you
playya said:
ok there is no coming back from a true brick... So if it wont turn on or your pc wont recognize it then yes it is truly bricked and you may need to contact JTag service which I hear is like $50. Also you are in the wrong forum for your phone. I would post this in the GALXY 2 GT-I9100 forum and see who can help you
Click to expand...
Click to collapse
thats a typo o ment the d710
What happens when you press the power button? Does it say galaxy s2? If so you should be able to get the phone into download mode and do an odin restore of ff18 that I'm linking below. Its a one click and is pretty easy if you just follow the instructions.
http://forum.xda-developers.com/showthread.php?t=1721229
What you probably did is flashed the i9100 kernel which screwed your phone since the boot loader is now corrupted.
Sent from my SPH-D710 using xda app-developers app
dmonger11b said:
What you probably did is flashed the i9100 kernel which screwed your phone since the boot loader is now corrupted.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
If that is the case for the OP, then they should check out this link by crawrj:
http://forum.xda-developers.com/showthread.php?t=1865102
i m new to Android , i have s3 came from dubai. i dont know from where it belongs orignaly but baught from dubai. on its back its model no is I9300 which is international model but when i see its ram its 2Gb. i searched its imei no. it says my phone is T999 Galaxy S III
now i installed stock rom from sammmobile with odin for t999 .. its runing Good. but i am confused about my orignal model no of S3 . please help me
Someone has done a Transplant Surgery. Put the motherboard of T999 into a I9300 case.
You need to treat the phone as a T999 despite what it says on the case.
We seem to be seeing a lot of these "Franken-phones".:silly:
Bass_Man25 said:
We seem to be seeing a lot of these "Franken-phones".:silly:
Click to expand...
Click to collapse
Probably a lot of people are replacing the housing (few bucks on ebay and elsewhere) so they can sell it as "like new" or something. Thats my guess anyway.
Perseus71 said:
Someone has done a Transplant Surgery. Put the motherboard of T999 into a I9300 case.
You need to treat the phone as a T999 despite what it says on the case.
Click to expand...
Click to collapse
is there any way to know its body is changed or not ? i think its a refubrished phone ? should i return this phone because shopkeeper challenged me that its not a refubrished phone
DocHoliday77 said:
Probably a lot of people are replacing the housing (few bucks on ebay and elsewhere) so they can sell it as "like new" or something. Thats my guess anyway.
Click to expand...
Click to collapse
Doc! Good to hear from you man
Farooq Ch said:
is there any way to know its body is changed or not ? i think its a refubrished phone ? should i return this phone because shopkeeper challenged me that its not a refubrished phone
Click to expand...
Click to collapse
You just confirmed it by flashing t999 firmware in Odin, otherwise it would've failed or bricked the phone, it was either the motherboard or housing as Doc said
Sent from my SGH-M919 using Tapatalk
I wouldn't bother with trying for a return if it were me. You know it's a T999, so as long as you treat it as such, you should be fine. Up to you of course, but seems like it'd be a hassle and not much fun or return. And it could be that it is new and simply was a mistake at the factory. New employee grabs wrong box of parts type scenario. ...
Sent from my SM-N900T using Tapatalk
serio22 said:
Doc! Good to hear from you man
You just confirmed it by flashing t999 firmware in Odin, otherwise it would've failed or bricked the phone, it was either the motherboard or housing as Doc said
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
when this phone came it was rooted and model no showing in the about phone was " gt i9300 ". now i flashed stock rom 4.3 for t999 it shows t999 in about phone.. ? is this possible that t999 having rom for gt i9300 ? or gt i9300 have rom for t999?
It's easy enough to change what it reads in the about phone menu. I believe simply changing the build.prop value will do that.
Sent from my SM-N900T using Tapatalk
DocHoliday77 said:
It's easy enough to change what it reads in the about phone menu. I believe simply changing the build.prop value will do that.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
This^^ very easy to do do, I am currently running a ROM for i-9505 and changed it to show my original M919.. Now this two phones you can flash Roms vice versa, i9300 and t999, will brick!!
Sent from my SGH-M919 using Tapatalk
DocHoliday77 said:
It's easy enough to change what it reads in the about phone menu. I believe simply changing the build.prop value will do that.
Click to expand...
Click to collapse
Good to see you back Doc!
@op Best if you treat the phone as T999. I know you can make it look like I9300. But don't ever accidentally flash any of the I9300 stuff.
Perseus71 said:
Good to see you back Doc!
@op Best if you treat the phone as T999. I know you can make it look like I9300. But don't ever accidentally flash any of the I9300 stuff.
Click to expand...
Click to collapse
i have tried flashing i9300 rom when i didnt know the orignal model .. nothing hapend i tried many time to flash i9300 stock rom but it didnt brick my phone . it just get off and dont show any thing .. i tried some methods from internet it went to download mode again ... i think flashing other roms for all s3 model dont brick your phone. ? i dont think flashing t999 to my mobile confirms it that it is t999 motherboard.
If it's a t999, only T999 firmware will flash. Official firmware from any other model should fail.
And you cannot just flash any other S3's roms. I9300 and any US model are quite different from each other. The most compatible is the I747 from ATT. Other models require more work to port to our T999.
Sent from my SM-N900T using Tapatalk
Woah. This thread just opened my eyes. I bought a I9300 phone off of ebay in a "unopened - new" condition. It came in the original box and everything (which I now know he/she just repackaged it). When I got it, I tried to flash a stock I9300 rom on it. It failed, saying "wrong dev" type. And I soft bricked it.
Now, I thought this was all my fault. I booted into download mode and it said "T999" so I thought I installed the wrong bootloader and messed it up. I opened a support thread, which had over three pages of replies. Everyone told me to get a new motherboard because I installed the wrong bootloader. Everytime I tried to flash a stock I9300 rom, it said "wrong dev_type" in download mode. Nothing flashed. I thought my phone was permanently screwed up so I returned it to the seller and he refunded me. So I didn't even have to return it... could have just flashed a T999 stock rom (maybe..).
NOW I realize, my phone was probably ACTUALLY a T999. I could have probably fixed the soft brick by just flashing a stock T999 rom. Woah. I was just flashing the WRONG stock rom the whole time? Because I thought I had a I9300?
Maybe I'm getting this all wrong, but nobody in the 3 page support thread even brought up the idea of me having a T999. This is just mind blowing.
Regardless, I now have a brand new T999 phone. That I purchased as a "T999 phone" not a "I9300-actually-a-T999-phone".
Farooq Ch said:
i have tried flashing i9300 rom when i didnt know the orignal model .. nothing hapend i tried many time to flash i9300 stock rom but it didnt brick my phone . it just get off and dont show any thing .. i tried some methods from internet it went to download mode again ... i think flashing other roms for all s3 model dont brick your phone. ? i dont think flashing t999 to my mobile confirms it that it is t999 motherboard.
Click to expand...
Click to collapse
Well I guess recoveries have been updated to prevent the bricks between this phones, but this was definitely a problem before, saw too many people bricking their phones because they flashed i9300 ROMs on t999.. Either way it just won't work
Sent from my SGH-M919 using Tapatalk
I have a Tmobile Galaxy S4 SGH-M919, I have tried every rooting method I can fine and so far all I have done is made a brick, I need this phone working asap, and rooted so I can go onto Crickets service
PLEASE HELP
I can root Sprint, but when it comes to Tmobile apparently I'm an idiot
wolfen1086 said:
I have a Tmobile Galaxy S4 SGH-M919, I have tried every rooting method I can fine and so far all I have done is made a brick, I need this phone working asap, and rooted so I can go onto Crickets service
PLEASE HELP
I can root Sprint, but when it comes to Tmobile apparently I'm an idiot
Click to expand...
Click to collapse
This the method I used for rooting when I had 4.3
http://forum.xda-developers.com/showthread.php?t=2611175
Check my signature for a link to how I rooted with 4.4.2
Depending on the version of Android you have on that phone, it will trip the Knox flag. Which won't affect the performance of the phone, but will indicate you messed with your phone. There may be other rooting methods that work, but this one worked for me.
BTW, I found that method by using Search on this forum and Google.
Rob
wolfen1086 said:
I have a Tmobile Galaxy S4 SGH-M919, I have tried every rooting method I can fine and so far all I have done is made a brick, I need this phone working asap, and rooted so I can go onto Crickets service
PLEASE HELP
I can root Sprint, but when it comes to Tmobile apparently I'm an idiot
Click to expand...
Click to collapse
The safe root method is how i rooted with 4.3 but it is my understanding that you need your phone to be unlocked to use a different carrier. Unlocked and rooted are 2 different things.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Unlocked sop I can use whatever carrier I want.
Rooted Because I want control over my pohone and not somebody else saying what I can and cant do with it.
I can get it to bot in cwm recovery but thats all it won't rot the rom so I can see it its rooted or not. I followed eth entire instructions provided and used oden like it said to and all I suceded in doing was makeing a damn brick out of a phone I got to have running tomorrow morning
rlichtefeld said:
This the method I used for rooting when I had 4.3
http://forum.xda-developers.com/showthread.php?t=2611175
Check my signature for a link to how I rooted with 4.4.2
Depending on the version of Android you have on that phone, it will trip the Knox flag. Which won't affect the performance of the phone, but will indicate you messed with your phone. There may be other rooting methods that work, but this one worked for me.
BTW, I found that method by using Search on this forum and Google.
Rob
Click to expand...
Click to collapse
Problem is I'm with Tmobile, my phone is a SGH-M919
wolfen1086 said:
Unlocked sop I can use whatever carrier I want.
Rooted Because I want control over my pohone and not somebody else saying what I can and cant do with it.
I can get it to bot in cwm recovery but thats all it won't rot the rom so I can see it its rooted or not. I followed eth entire instructions provided and used oden like it said to and all I suceded in doing was makeing a damn brick out of a phone I got to have running tomorrow morning
Click to expand...
Click to collapse
If you can get into Download mode (Power Off, then Volume Down+Power Button), then you'll need to download the Stock Rom and transfer it to your phone via ODIN. Do you know if you were 4.2, 4.3, or 4.42 before you bricked it? You can download the images from Sammobile.com
Rob
rlichtefeld said:
If you can get into Download mode (Power Off, then Volume Down+Power Button), then you'll need to download the Stock Rom and transfer it to your phone via ODIN. Do you know if you were 4.2, 4.3, or 4.42 before you bricked it? You can download the images from Sammobile.com
Rob
Click to expand...
Click to collapse
Yes I do I was 4.3
going to Samsung now to try to get the stock rom and start over, the only thing I have not tried yet is CF autoroot, if that don't work I guess its back on t mobile with their payment lies
wolfen1086 said:
Yes I do I was 4.3
going to Samsung now to try to get the stock rom and start over, the only thing I have not tried yet is CF autoroot, if that don't work I guess its back on t mobile with their payment lies
Click to expand...
Click to collapse
If you have access to ClockWork Mod Recovery, wipte the cache and dalvik and see if that lets it boot.
If not, just download a rom, any rom from the dev section that you want to try and put it on a micro SD card. Put the SD card in your phone.
Do a full wipe (data, system, cache, dalvik) in recovery and flash the downlaoded ROM file. Your phone should boot right up.
You'll want a TouchWiz based rom if you still need to perform the SIM unlock proceedure so you can use it on the Cricket network. But once step at a time here...
wolfen1086 said:
Unlocked sop I can use whatever carrier I want.
Rooted Because I want control over my pohone and not somebody else saying what I can and cant do with it.
I can get it to bot in cwm recovery but thats all it won't rot the rom so I can see it its rooted or not. I followed eth entire instructions provided and used oden like it said to and all I suceded in doing was makeing a damn brick out of a phone I got to have running tomorrow morning
Click to expand...
Click to collapse
Ok. You didn't mention your phone was unlocked in the OP.
Sent from my SGH-M919 using XDA Premium 4 mobile app
wolfen1086 said:
Problem is I'm with Tmobile, my phone is a SGH-M919
Click to expand...
Click to collapse
If you look at my signature, you'll see that I've got a SGH-M919 also and I'm on T-Mobile with a phone purchased from T-Mobile.
I've provided links that worked for me.
Rob
Kriptik210 said:
Ok. You didn't mention your phone was unlocked in the OP.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thats cause it wasn;t rooted before, hopefully it is now, cause my wife just went to Cricket to see if she can get her Iphone and mine on their network
I finally got the phone rooted but I screwed it up so bad I had to install a different rom to make it work, so not I'm roted and running wicked rom .Next I installed, updated and ran region away, it said it didn;t know if it worked or not, but I was told that it does unlock so hopefully it did.
I havea different S4 here ( SGHM919) that I'm gonna try the cf auto root on when the battery is fully charged, cause both my sons have S4's and they want to keep the rom they have now just be unlocked
If you were looking at cwm recovery then you most likely have root.
Pp.
Sent from my Touchwiz device that never forgets apps.
PanchoPlanet said:
If you were looking at cwm recovery then you most likely have root.
Pp.
Sent from my Touchwiz device that never forgets apps.
Click to expand...
Click to collapse
And if you don't you can easily get root with CWMrecovery
Sent from your phone. You should be more careful where you leave that thing.
wolfen1086 said:
Thats cause it wasn;t rooted before, hopefully it is now, cause my wife just went to Cricket to see if she can get her Iphone and mine on their network
I finally got the phone rooted but I screwed it up so bad I had to install a different rom to make it work, so not I'm roted and running wicked rom .Next I installed, updated and ran region away, it said it didn;t know if it worked or not, but I was told that it does unlock so hopefully it did.
I havea different S4 here ( SGHM919) that I'm gonna try the cf auto root on when the battery is fully charged, cause both my sons have S4's and they want to keep the rom they have now just be unlocked
Click to expand...
Click to collapse
When I used Region away it says somewhere that it doesn't unlock your phone to where you can use other carriers. So you might want to find out lol
Sent from my SGH-M919 using XDA Premium 4 mobile app
Google is your friend.
Pp.
Sent from my Touchwiz device that never forgets apps.
Thank you gentlemen, my phone is working again, rooted, currently running wicked rom, all the other phones are rooted with the stock roms for the kiddies unless they want to have a better rom
Region away works perfectly on mine even though it says it doesn't know if it did.
I was going to use triangle away, but it says something about bricking my phone and I really don't give a damn about the counter so ........
PanchoPlanet, Google is NOT my friend when it comes to phones XDA id my friend when it comes to phones
Now to go look for the stock memo pad that comes with the S4, I like that one best its simple and works
I too prefer Memo Pad, it's quick and simple, my reference to Google was that its quicker than the XDA search and more accurate. Good to hear your back on track.
Pp.
Sent from my Touchwiz device that never forgets apps.
wolfen1086 said:
Thank you gentlemen, my phone is working again, rooted, currently running wicked rom, all the other phones are rooted with the stock roms for the kiddies unless they want to have a better rom
Region away works perfectly on mine even though it says it doesn't know if it did.
I was going to use triangle away, but it says something about bricking my phone and I really don't give a damn about the counter so ........
PanchoPlanet, Google is NOT my friend when it comes to phones XDA id my friend when it comes to phones
Now to go look for the stock memo pad that comes with the S4, I like that one best its simple and works
Click to expand...
Click to collapse
If Google is not your friend, then maybe his big brother may be - Google Advanced Search:
https://www.google.com/advanced_search
where you can seach specific sites, specific words or phrases.
Rob
I found Smemo on line, took a while since I'm on oxycodone for pain due to a hernia operateing, but I got it, placed it in eth rom and reflashed it
Now I'd love to find a theme for Wicked V10 that would change teh color of the phone dialpad, I HATE white dialers, makes me remember when I was a kid back in teh 60' when my mom had nothing but white so she could see if it was clean, and sanitized, degermed, and all that, ( yes I was an outside type, and brought it all inside )
Oh and all I can say guys, is thanks for trying to help me I WILL figure it out for the firmware and hardware and software that I have, experimenting with a phone that I totally bricked today, gotta re-instal the entire os on it, so I'm gonna experiment with various versions of the SGH-M919 software, if I find out what works on what I'll post it for you guys to check and make sure I did right
Hello everyone i am in a peculiar situation i recently got s3 from my friend he said that it is I9300 but when i received it i came to know that it is T999 and not I9300 . My problem here is it came with android version 4.1.1 build number : I9300ZSEMC1 i didn't understand why it came with i9300 firmware ( i cannot ask my friend as he does not have much technical knowledge ) everything is working fine occasionally touch does not respond and i have bit of hard time switching on wi fi and weird battery drain problems what i want to know is , is these because of the i9300 firmware being present in t999 and whether is it advisable to update it further from 4.1.1 version to t999 latest stock firmware or to stick with the present version . If it is advisable to update to t999 based stock firmware i want to know whether it will work in indian carriers and wont have any problems and also can someone guide me for the right firmware link / build number to go with. :fingers-crossed:
I didn't know the firmware would actually flash across models.
Sent from my SGH-T999 using Tapatalk
tokenpoke said:
I didn't know the firmware would actually flash across models.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
But it did ! Its a dual core version with 2 gb ram i verified it in download mode it stated as T999 and yet i wonder how is it running I9300 firmware !
toxicated2 said:
But it did ! Its a dual core version with 2 gb ram i verified it in download mode it stated as T999 and yet i wonder how is it running I9300 firmware !
Click to expand...
Click to collapse
Isn't the I9300 the 1gbp ram version?
Anyway, if certified in download mode you could just flash t999 firmware.
If that doesn't sound safe you can also put a t999 recovery on it and try doing a backup and installing a t999 rom
Sent from my SGH-T999 using Tapatalk
tokenpoke said:
Isn't the I9300 the 1gbp ram version?
Anyway, if certified in download mode you could just flash t999 firmware.
If that doesn't sound safe you can also put a t999 recovery on it and try doing a backup and installing a t999 rom
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I was thinking of using root_66 firmware for t999 will i end up locking the phone or will it work in indian network carriers after flashing tmobile firmware ?
toxicated2 said:
I was thinking of using root_66 firmware for t999 will i end up locking the phone or will it work in indian network carriers after flashing tmobile firmware ?
Click to expand...
Click to collapse
Sounds kinda like some of the "frankenphones" we've heard about over the last several months. Or it could also be a fake/chinese knock off. If I were you, I would see if there were any way to send it back to whoever sold it. If you plan to keep it though, understand anything you do is AT YOUR OWN RISK! The only absolutely safe course of action is to do nothing to it. If you try to flash it via Odin, and it allows it to flash, but you chose the wrong firmware, it WILL brick. There is honestly no possible way to know for sure what is up with the device.
If I had to guess, something is lying to you about what you are running. If your current firmware version is from an I9300, then that is most likely what you have. That firmware WILL NOT work on any Qualcomm, US model S3's. This tells me that its probably an I9300, and someone screwed with something, (or was careless when trying to copy Samsung), in the bootloader. Because it tells you it is a T999 in download mode, it will probably not let you flash the I9300 firmware. But if you try to flash the T999 firmware, there is a very good possibility you will brick it.
It is up to you what you want to try, but understand you are taking a bigger than normal risk since you already know the device isnt normal to begin with.
One way you can try to determine what motherboard it uses, (though this is by no means a for certain way to know), is go to the SIM unlock thread in General and try to follow those instructions. Also try the GPS fix thread in the Q&A sticky roll up. If I am not mistaken, both use dialer codes that are specific to Qualcomm devices. If they work, its a better chance of it being a T999. If they do not work, its more likely to be an I9300.
DocHoliday77 said:
Sounds kinda like some of the "frankenphones" we've heard about over the last several months. Or it could also be a fake/chinese knock off. If I were you, I would see if there were any way to send it back to whoever sold it. If you plan to keep it though, understand anything you do is AT YOUR OWN RISK! The only absolutely safe course of action is to do nothing to it. If you try to flash it via Odin, and it allows it to flash, but you chose the wrong firmware, it WILL brick. There is honestly no possible way to know for sure what is up with the device.
If I had to guess, something is lying to you about what you are running. If your current firmware version is from an I9300, then that is most likely what you have. That firmware WILL NOT work on any Qualcomm, US model S3's. This tells me that its probably an I9300, and someone screwed with something, (or was careless when trying to copy Samsung), in the bootloader. Because it tells you it is a T999 in download mode, it will probably not let you flash the I9300 firmware. But if you try to flash the T999 firmware, there is a very good possibility you will brick it.
It is up to you what you want to try, but understand you are taking a bigger than normal risk since you already know the device isnt normal to begin with.
One way you can try to determine what motherboard it uses, (though this is by no means a for certain way to know), is go to the SIM unlock thread in General and try to follow those instructions. Also try the GPS fix thread in the Q&A sticky roll up. If I am not mistaken, both use dialer codes that are specific to Qualcomm devices. If they work, its a better chance of it being a T999. If they do not work, its more likely to be an I9300.
Click to expand...
Click to collapse
I decided to go ahead with flashing root66 firmware and selected the latest 4.3 can't express how nervous i was to find out the outcome of it and then finally when the process was over to my surprise i did not face any bootloops or any other problem infact the network seemed to be working well and no problems as far now happy !! Thanks for the help @DocHoliday77 @tokenpoke
toxicated2 said:
I decided to go ahead with flashing root66 firmware and selected the latest 4.3 can't express how nervous i was to find out the outcome of it and then finally when the process was over to my surprise i did not face any bootloops or any other problem infact the network seemed to be working well and no problems as far now happy !! Thanks for the help @DocHoliday77 @tokenpoke
Click to expand...
Click to collapse
There is a chance that someone modified the model number in the phone to access certain apps or something.
I remember modifying a phone to do that go some exclusive app a couple years ago.
Sent from my SGH-T999 using Tapatalk