Related
Hello This was my first time installing a custom rom ( it seemed harmless and easy .. i was wrong )
Ok i looked all over XDA and GOOGLE
if Possible Just Post Links To threads That Have same question but answered :3
What i Did:
rooted phone -everything worked-
Fallowed All the Instructions That the Custom Rom told me to do
Made Sure that The ROM Supported my Phone
Installed it -Said Everything worked and to reboot-
Never rebooted couldnt boot No lights no nothing
Its lifeless :"( - grandma is gonna kill me -_- -
What I Have
Had CWM recovery
Have kais and odin installed
Have all My Backups on SD and laptop
What I tried:
I tried Booting into samsung recover
and CWM recovery
left battery out for 20 minutes
Contacted samsung -no reply-
Details About ROM i used:
OMEGA v4.0 rom
Had Rooted phone + busy box installed
Sorry cant spell for shiz Please help if you could id would mean the world to me
Link to the rom you flashed?
Sent from my SGH-T999 using Tapatalk 2
Reply Places
1st:
http://forum.xda-developers.com/showthread.php?t=1663656&highlight=omega
2nd:
http://forum.xda-developers.com/showthread.php?t=1663656&highlight=omega
do you have the T999 version of the s3? the roms you linked are for the international version, if you flash the international version it'll brick your phone...
follow this thread to fix it!
http://forum.xda-developers.com/showthread.php?t=1727401&highlight=international
Testimonyy said:
do you have the T999 version of the s3? the roms you linked are for the international version, if you flash the international version it'll brick your phone...
follow this thread to fix it!
http://forum.xda-developers.com/showthread.php?t=1727401&highlight=international
Click to expand...
Click to collapse
Nope So I Hard bricked my phone should i lie to Samsung and Tell them its hardware issue and hope they cant get it to start either?
GarettMcCarty said:
Nope So I Hard bricked my phone should i lie to Samsung and Tell them its hardware issue and hope they cant get it to start either?
Click to expand...
Click to collapse
Look in to a jtag service.. I think it's about 65 bucks
Sent from my SGH-T999 using Tapatalk 2
well my friend bricked his galaxy nexus when he tried rooting it and brought it back to the carrier to get a replacement. maybe you'll get lucky. he said that it just stopped working and had no idea what happened.
I did this too when I got my s3 but I just sent it into Samsung and they fixed it up.
Sent from my SGH-T999 using xda premium
Testimonyy said:
do you have the T999 version of the s3? the roms you linked are for the international version, if you flash the international version it'll brick your phone...
follow this thread to fix it!
http://forum.xda-developers.com/showthread.php?t=1727401&highlight=international
Click to expand...
Click to collapse
Yes thats My model sorry Miss read So Shouldn't i have No issues?
the ROM you flashed is for the international model but since you have the T999 model, it'll brick your phone. follow the thread, should be able to fix it.
Testimonyy said:
the ROM you flashed is for the international model but since you have the T999 model, it'll brick your phone. follow the thread, should be able to fix it.
Click to expand...
Click to collapse
I Cant boot into recovery though? its literally DEAD
Please Close I just told tmobile i was on fb and it crashed there sending me a new one > ive learned from my mistakes
Please Note: No other method listed in the GN2, GS3 forums work for this particular problem. I, as well as a few others have had this happen when flashing different ROMs. I have no idea what causes it but I do have an idea as to how to fix it. I just can't because what I need seems to be disabled in the phone.
Also, I did make a backup of my EFS and a restore does not fix this particular problem.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
Problem #3:
And probably the biggest problem: ADB does not recognize the phone. ADB debugging is enabled on the phone in Developer Options but the icon on the notification button doesn't appear. Nor does ADB recognize the phone in recovery. So therefor I cannot transfer files this way either. "nvbackup/nvrestore" can not be used because of this either.
The following methods have all been tried and have failed. Yes, I know what I am doing,
http://forum.xda-developers.com/showthread.php?t=1867442
http://forum.xda-developers.com/showthread.php?t=1852255
http://forum.gsmhosting.com/vbb/f606/tutorial-galaxy-s3-backup-restore-imei-without-root-1513909/
I fell victim to #1 the IMEI wipeout I had to take my phone back for a replacement
Sent from my SPH-L900 using xda premium
Me too. ..
Sent from my MASSIVE Galaxy Note® II...*
mackentosh said:
I fell victim to #1 the IMEI wipeout I had to take my phone back for a replacement
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
but how did it happened ? can u please explain steps what u did that wiped yr imei?
t3project said:
Please Note: No other method listed in the GN2, GS3 forums work for this particular problem. I, as well as a few others have had this happen when flashing different ROMs. I have no idea what causes it but I do have an idea as to how to fix it. I just can't because what I need seems to be disabled in the phone.
Also, I did make a backup of my EFS and a restore does not fix this particular problem.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
Problem #3:
And probably the biggest problem: ADB does not recognize the phone. ADB debugging is enabled on the phone in Developer Options but the icon on the notification button doesn't appear. Nor does ADB recognize the phone in recovery. So therefor I cannot transfer files this way either. "nvbackup/nvrestore" can not be used because of this either.
The following methods have all been tried and have failed. Yes, I know what I am doing,
http://forum.xda-developers.com/showthread.php?t=1867442
http://forum.xda-developers.com/showthread.php?t=1852255
http://forum.gsmhosting.com/vbb/f606/tutorial-galaxy-s3-backup-restore-imei-without-root-1513909/
Click to expand...
Click to collapse
i got the same problem with tmobile ver the problem is the partition i did tried to repartition in odin with gt-7100 pit file it did not work
can you see your storge and see your internal sd space
sorry for my english
An fyi when u get ur baseband back 3g will not work. I was able to get mine all back and working but I was always on 1x. T3 hit me up in gtalk.
Sent from my SPH-L900 using Tapatalk 2
gotojanoo said:
but how did it happened ? can u please explain steps what u did that wiped yr imei?
Click to expand...
Click to collapse
Well I was testing a rom for someone, I wont tell which rom but he said it was the "in call recorder" he added. He's got it fixed now but it did wipe everything. I managed to restore it back to stock with no root but it bricked after that. Now I see why carriers dont like to unlock bootloaders cause of people bricking their phone and taking them back
Sent from my SPH-L900 using xda premium
t3project said:
Please Note: No other method listed in the GN2, GS3 forums work for this particular problem. I, as well as a few others have had this happen when flashing different ROMs. I have no idea what causes it but I do have an idea as to how to fix it. I just can't because what I need seems to be disabled in the phone.
Also, I did make a backup of my EFS and a restore does not fix this particular problem.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
Problem #3:
And probably the biggest problem: ADB does not recognize the phone. ADB debugging is enabled on the phone in Developer Options but the icon on the notification button doesn't appear. Nor does ADB recognize the phone in recovery. So therefor I cannot transfer files this way either. "nvbackup/nvrestore" can not be used because of this either.
The following methods have all been tried and have failed. Yes, I know what I am doing,
http://forum.xda-developers.com/showthread.php?t=1867442
http://forum.xda-developers.com/showthread.php?t=1852255
http://forum.gsmhosting.com/vbb/f606/tutorial-galaxy-s3-backup-restore-imei-without-root-1513909/
Click to expand...
Click to collapse
You care to clarify which ROM you flashed in particular caused this to happen so that we don't replicate your problem? I want to assume it's your own ROM but just want to make sure.
mackentosh said:
Well I was testing a rom for someone, I wont tell which rom but he said it was the "in call recorder" he added. He's got it fixed now but it did wipe everything. I managed to restore it back to stock with no root but it bricked after that. Now I see why carriers dont like to unlock bootloaders cause of people bricking their phone and taking them back
Click to expand...
Click to collapse
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
ffolkes said:
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
Click to expand...
Click to collapse
i did flash the s3 rom and after that i lost everythng my phone i need to know how to restor the orgenal sd card cuz im looking with rootexplore it sdcard0
when i go to setting storge it only show 266mb used and 0.00 avilabel any body can help please
mackentosh said:
Well I was testing a rom for someone, I wont tell which rom but he said it was the "in call recorder" he added. He's got it fixed now but it did wipe everything. I managed to restore it back to stock with no root but it bricked after that. Now I see why carriers dont like to unlock bootloaders cause of people bricking their phone and taking them back
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Which ROM had the "In Call Recorder"? I've been looking for a replacement to that functionality after dropping HTC/ Qualcomm with the 2WCR patch on the kernel. ..
Sent from my SPH-L900 using xda app-developers app
You cant flash a s3 rom the partitions are different. Even the partitions forbthe international note 2. Tmo. Att. Verizon and sprint note 2 are different.
Try flashing the stock tar from sex tape or viper boy. This should fix those issues. Then update the phones prl. Profile. Software. And firmware. And see if u have 3g and everything else.
Then start over.
Sent from my SPH-L900 using Tapatalk 2
ffolkes said:
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
Click to expand...
Click to collapse
it wasnt a rogue rom. it was two seperate private roms that were never released to the public
there is a very simple fix to this, i've fixed 2 phones this morning already with it. i'll post it up in a few
gotojanoo said:
but how did it happened ? can u please explain steps what u did that wiped yr imei?
Click to expand...
Click to collapse
it didnt actually wipe our imei. it repartitioned the phone.
t3project said:
it wasnt a rogue rom. it was two seperate private roms that were never released to the public
there is a very simple fix to this, i've fixed 2 phones this morning already with it. i'll post it up in a few
Click to expand...
Click to collapse
Good to know it wasn't released here publicly. Happy to hear you found a solution to the problem too.
dc13 said:
You cant flash a s3 rom the partitions are different. Even the partitions forbthe international note 2. Tmo. Att. Verizon and sprint note 2 are different.
Try flashing the stock tar from sex tape or viper boy. This should fix those issues. Then update the phones prl. Profile. Software. And firmware. And see if u have 3g and everything else.
Then start over.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Try this.
ffolkes said:
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
Click to expand...
Click to collapse
I said I was testing a rom which means I was the only person he released it to at the time. I dont want to reveal the rom or the dev because I dont want any negativity towards him he's a great dev and your probably running his rom right now. So dont worry there isnt a rogue rom floating around
Sent from my SPH-L900 using xda premium
t3project said:
it wasnt a rogue rom. It was two seperate private roms that were never released to the public
there is a very simple fix to this, i've fixed 2 phones this morning already with it. I'll post it up in a few
Click to expand...
Click to collapse
whats the fix cuz im going thru this problem right now ...i cant get any service (radios)
EDIT: NVM I JUST FLASHED TO STOCK RECOVERY THEN FLASHED STOCK LJ1 THRU ODIN AND ALL IS WELL NOW
mccurt29 said:
whats the fix cuz im going thru this problem right now ...i cant get any service (radios)
EDIT: NVM I JUST FLASHED TO STOCK RECOVERY THEN FLASHED STOCK LJ1 THRU ODIN AND ALL IS WELL NOW
Click to expand...
Click to collapse
simple, wasnt it? lol..................
mackentosh said:
I said I was testing a rom which means I was the only person he released it to at the time. I dont want to reveal the rom or the dev because I dont want any negativity towards him he's a great dev and your probably running his rom right now. So dont worry there isnt a rogue rom floating around
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Was it mine? I can tell you that if any of the previous stuff happened to you, it wasn't from the ROM. Could have been a bad download, coinsidence, etc. The ROM flash wouldn't have caused it.
Sent from my SPH-L900 using Tapatalk 2
I tried to put i9300 android 4.1.1. on my Att i747 sg3 and now I can't start the phone.
I was trying to upgrade the android version whole day, because I can't upgrade it through my phone when I check for upgrades.
The thing is I'm in europe and my phone of course we don't have a att carrier here, so it's not finding an update.
So in the end I tried to use mobile odin Lite, and put on i9300 version on it, so now it's not working.
When I try to start it shows me SAMSUNG and after that it turns off.
I hope someone has an idea how to fix it through my laptop ;/
Merry Christmas to all!
Well try this... open in download mode.... which is volume down key-power button and home button..... download odin ffor pc.... and latest firmware deom sammobile.com
Steps.
1.do not connect fone yet. Download odin and read instructions. Which as far as i remember was attacthing the frimware file to pda... then coonect fone in download mode as mentioned above... and flash that furmware.. should be fine..:thumbup:
Sent from my GT-I9300 using xda app-developers app
going to have to send it to samsung or jtag service by flashing a international rom you have hard bricked it
justf0g said:
I tried to put i9300 android 4.1.1. on my Att i747 sg3 and now I can't start the phone.
I was trying to upgrade the android version whole day, because I can't upgrade it through my phone when I check for upgrades.
The thing is I'm in europe and my phone of course we don't have a att carrier here, so it's not finding an update.
So in the end I tried to use mobile odin Lite, and put on i9300 version on it, so now it's not working.
When I try to start it shows me SAMSUNG and after that it turns off.
I hope someone has an idea how to fix it through my laptop ;/
Merry Christmas to all!
Click to expand...
Click to collapse
Your phone is hard brick. Need to send it to service or byt jtag
jerrycoffman45 said:
going to have to send it to samsung or jtag service by flashing a international rom you have hard bricked it
Click to expand...
Click to collapse
norbarb said:
Your phone is hard brick. Need to send it to service or byt jtag
Click to expand...
Click to collapse
This isn't necessarily true.
He specifically stated he could see the Samsung logo which means it is not a hard brick.
OP please report back if you are able to enter Download mode.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
jerrycoffman45 said:
going to have to send it to samsung or jtag service by flashing a international rom you have hard bricked it
Click to expand...
Click to collapse
No, he's not. If he's seeing any sign of life, it's not hard bricked.
---------- Post added at 11:12 PM ---------- Previous post was at 11:11 PM ----------
norbarb said:
Your phone is hard brick. Need to send it to service or byt jtag
Click to expand...
Click to collapse
Check the definition of hard brick, cause you have obviously missed something in that particular explanation.
Can you get into recovery with power,home, and vol up?
If it opens in download.... it is never bricked or if stuck on samsung logo not bricked... just open download mode and flash stock rom via pc odin
Sent from my GT-I9300 using xda app-developers app
I used heimdall to flash stock rom (extracted the varios bin and img files from N7100XXDMB2_N7100OXEDMC2_SER), and missed out sboot and recovery. Once it finished, I tried restarting the phone -> and it wouldn't do anything. Now I cant enter the download mode.
I tried a home-made USB JIG (300k ohms b/w pin 4 (the left out pin) and pin 5 (ground)), and it wouldn't kick the download mode either (does nothing).
I am seriously stuck and have no clue on what to do. If it helps, when I try to boot (with any combination of keys), the indicator (left) blinks red once.
Begging for help right now... Please tell me what to do. I love my phone, and I have a decent understanding of Computers/Electronics - so it's okay if you go all technical
More Info:
Extra Info: Verified that the USB JIG is doing the same thing, i.e after 3 seconds or so, the indicator blinks red... (and so on after every 5 seconds in a loop thereafter).
Good chance of SDS
You have messed up bootloader so won't get download mode
But if you have heimdall and some techy here is guide to flash bootloader blindly, if you succeed to flash it, you will get download mode and subsequently use odin to flash stock rom
http://forum.xda-developers.com/showthread.php?t=1220181
Goodluck!
Sent from my GT-N7100 using xda premium
You need jtag. This is not sds issue.
You will need jtag to flash back bootloader.
Sent from my GT-N7100 using xda premium
dr.ketan said:
You have messed up bootloader so won't get download mode
But if you have heimdall and some techy here is guide to flash bootloader blindly, if you succeed to flash it, you will get download mode and subsequently use odin to flash stock rom
http://forum.xda-developers.com/showthread.php?t=1220181
Goodluck!
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I am going to try this... Looks like I will need a lot of good luck for this to actually work..
UtkarshGupta said:
You need jtag. This is not sds issue.
You will need jtag to flash back bootloader.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I have never actually used jtag to debug anything! Is it worth buying one just for this purpose? Also, I'm not able to find any wiki on how to use jtag specially to download a particular bootloader (Learning JTAG and its usage as a whole seems very tedious)...
cheenu_sri said:
I am going to try this... Looks like I will need a lot of good luck for this to actually work..
Click to expand...
Click to collapse
No luck
cheenu_sri said:
I have never actually used jtag to debug anything! Is it worth buying one just for this purpose? Also, I'm not able to find any wiki on how to use jtag specially to download a particular bootloader (Learning JTAG and its usage as a whole seems very tedious)...
Click to expand...
Click to collapse
You have to attach the wires directly to the nand or internal memory chip or whatever it is(could be memory controller if there is any). Then you have to connect it to a box? I don't know much about it. You can check on the internet. You have to flash sboot.bin I guess
Sent from my GT-N7100 using xda premium
Off-topic
On a side note (not sure if I am violating forum policies), I am still within warranty period - is there a way Samsung can pinpoint what caused this? Or can I still get it repaired with some generic reasons?
cheenu_sri said:
On a side note (not sure if I am violating forum policies), I am still within warranty period - is there a way Samsung can pinpoint what caused this? Or can I still get it repaired with some generic reasons?
Click to expand...
Click to collapse
Well if it were sds or it's symptoms then yeah.
But you could try maybe they would just consider it sds or something else.
And don't worry. Talking about Samsung isn't against the forum rules
Sent from my GT-N7100 using xda premium
Best answer if samsung guys ask you, tell them it was happened when I got OTA and after getting update device never started, there are cases reported bootloader can't update while on ota and device fail to boot further.
Just don't show them you are technically sound, and behave like noob, they will install it with jtag.
Sent from my GT-N7100 using xda premium
Thanks for the suggestions!
dr.ketan said:
Best answer if samsung guys ask you, tell them it was happened when I got OTA and after getting update device never started, there are cases reported bootloader can't update while on ota and device fail to boot further.
Just don't show them you are technically sound, and behave like noob, they will install it with jtag.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
UtkarshGupta said:
Well if it were sds or it's symptoms then yeah.
But you could try maybe they would just consider it sds or something else.
And don't worry. Talking about Samsung isn't against the forum rules
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Thanks for those suggestions I will try my luck at this tomorrow. Looks like whether I get it repaired free or not, I can't use my phone for a couple of weeks
Thanks again guys! Really appreciate it!
If it is just sw issue, you will get back in few hrs,(basically it takes same time like we flashing with odin, few minutes) and under warranty you should get it free.
Sent from my GT-N7100 using xda premium
UtkarshGupta said:
You have to attach the wires directly to the nand or internal memory chip or whatever it is(could be memory controller if there is any). Then you have to connect it to a box? I don't know much about it. You can check on the internet. You have to flash sboot.bin I guess
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
n7100 can do JTAG? with JTAG box can fix n7100?
Depends on your service centre. Last time I messed up and I was lucky enough to get the motherboard free of cost under warranty. Anyways good luck
Sent from my GT-N7100 using Tapatalk 2
mps5566 said:
n7100 can do JTAG? with JTAG box can fix n7100?
Click to expand...
Click to collapse
Hi
Many of new exynos model have a predisabled jtag access by samsung...so,not supported by all jtag-box..
But .i can repair hard bricked N7100 Without Jtag...Plz see : http://forum.gsmhosting.com/vbb/9306319-post324.html
This is my post about i9300,...but i can do it for N7100 too
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