Related
I've spent nearly two weeks trying to figure out what happened to my phone and how to restore it. After OTA 4.1.1 (I forced this clearing gsf), in a weak coverage area toggled airplane mode. It wouldn't come back out.
Fastboot flash, CWM, TWRP, dd command, Odin, re-partitioning, nand erase all - any attempt to flash radio-cdma.img hangs or fails.
I can confirm that many of the dire warnings about hard-bricking your device... Well, let's just say that with everything that I've tried, even the bolder attempts in the end, did not brick my device. Odin would always get me back.
Baseband Unknown
IMEI Unknown
My Phone Number Unknown
Everything!!! UNKNOWN
I found some threads on here mentioning CDMA tools and I've downloaded and attempted a couple, it seems that my pc has to have all the supporting programs to make a connection to my phone. The problem is these posts are not specific to my device but the S3 and it seems like a whole lot of trouble when there isn't a 'known' path and specific files for my VZW GNX.
I have also ran emmc check several times and memory checks out good. Sim card has also been replaced.
So I sit here today with 4.1.1 installed (less the radio-cdma.img). I can Odin the older stock images found here on XDA by deleting the radio-cdma.img within. Then use fastboot to flash the 4.1.1 images individually to have a Wi-Fi only device.
I'm willing to try anything. Any takers?
Your meid is smoked. You will need to completely reprogram phone. A restore won't do it Cuz its the serial of the device from factory. You can't fix unless you have msl
*Shaolin Shadowboxing*
Thank you for the reply!
Could you point me in the right direction? Is this done using CDMA tools? I've seen places that mention it can be done via the handset dialpad (other devices). I've found threads that give suggestions on how to contact your carrier to get them to give you the msl... and I've also seen posts that state that Verizon's MSL is almost always 000000. My brain is turning to mush! :cyclops:
Thanks again
JediNinjafication said:
Your meid is smoked. You will need to completely reprogram phone. A restore won't do it Cuz its the serial of the device from factory. You can't fix unless you have msl
*Shaolin Shadowboxing*
Click to expand...
Click to collapse
Verizon msl is usually 000000 you will need either the box device came in or the numbers under battery. The sticky part us going to be the MSID number you'll have to put in. If you have the ORIGINAL nandroid you made immediately after you unlocked bootloader, that one might work but no guarantees. The dialer code is *#*#msl#*#* with msl being the 000000. I believe that's it...could be *#*#spc#*#* with spc being spc and then have to enter msl. The MSID is mobile subsidy identification. Sometimes its NAM. Your MIN would be your phone number..mobile identification number.
If you get into the MEID it will have a couple numbers to enter. The numbers you will need will be your ESN hex and dec. I have all the dialer codes and can pm you a link if you like. Once you finish with the MEID repair that's where the NAM MIN thing will be needed. Unfortunately, the NAM/MSID isn't the same as your number and won't accept all 0's but once the meid is back you might be able to restore but am not positive on that. Can call Verizon and have them refresh phone I believe once meid is restored.
*Step Away From The Toolkit And NoROM Gets Hurt*
I tried the dialer code *#*#000000#*#*
The phone did nothing although as soon as I completed it went the field cleared. I'm on my own. Verizon told me a week ago they were sending me a refurb. Called yesterday and there was no record of another phone being sent out. Rep told me my Sim card was not activated in their system and a ticket was opened to have it unlocked on their network. It should be fixed on their end today. However, I still think I'm going to have to get radio-cdma flashed on my phone. Using getprop (from app market) it appears at some point I may have flashed GSM radios. I say this because there are GSM listings from the getprop output.
Any suggestions?
Sent from my Galaxy Nexus using xda app-developers app
I'd probably return everything to stock first. ##XXXXXXX# and *#*#XXXXXX#*#* codes depend a device's factory ROM.
I'm not convinced it's your MEID though. That alone wouldn't stick your phone without signal and you'd still be able to flash a radio. I'd also be careful not to mess with IMEIs or MEIDs unless you're absolutely certain that's the problem. If you're hell bent on it or you're doing it for fun, not caring of you wreck it, look up MEID repair and read up before messing around.
It wouldn't hurt to try and install a new radio via CDMAWS or a similar program. Just don't change anything you're not familiar with. You can really screw things up with programs like that if you mess around.
Sent from my Galaxy Nexus using Tapatalk 2
I'm pretty sure that my problem is due to flashing GSM on my device. I have not had any luck finding out how to go back. I'll check out CDMAWS... first time hearing about it.
untruestory said:
I'd probably return everything to stock first. ##XXXXXXX# and *#*#XXXXXX#*#* codes depend a device's factory ROM.
I'm not convinced it's your MSID though. That alone wouldn't stick your phone without signal and you'd still be able to flash a radio. I'd also be careful not to mess with IMEIs or MEIDs unless you're absolutely certain that's the problem. If you're hell bent on it or you're doing it for fun, not caring of you wreck it, look up MEID repair and read up before messing around.
It wouldn't hurt to try and install a new radio via CDMAWS or a similar program. Just don't change anything you're not familiar with. You can really screw things up with programs like that if you mess around.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
stwandell said:
I'm pretty sure that my problem is due to flashing GSM on my device. I have not had any luck finding out how to go back. I'll check out CDMAWS... first time hearing about it.
Click to expand...
Click to collapse
Pretty much meid smoked.
Wrong quote..trying to quote above. Just to ensure try *#06# and if it comes back with a string of numbers then you still have the meid. If blank...smoked
Sent from my Galaxy Nexus using Xparent Purple Tapatalk 2
stwandell said:
I've spent nearly two weeks trying to figure out what happened to my phone and how to restore it. After OTA 4.1.1 (I forced this clearing gsf), in a weak coverage area toggled airplane mode. It wouldn't come back out.
Fastboot flash, CWM, TWRP, dd command, Odin, re-partitioning, nand erase all - any attempt to flash radio-cdma.img hangs or fails.
I can confirm that many of the dire warnings about hard-bricking your device... Well, let's just say that with everything that I've tried, even the bolder attempts in the end, did not brick my device. Odin would always get me back.
Baseband Unknown
IMEI Unknown
My Phone Number Unknown
Everything!!! UNKNOWN
I found some threads on here mentioning CDMA tools and I've downloaded and attempted a couple, it seems that my pc has to have all the supporting programs to make a connection to my phone. The problem is these posts are not specific to my device but the S3 and it seems like a whole lot of trouble when there isn't a 'known' path and specific files for my VZW GNX.
I have also ran emmc check several times and memory checks out good. Sim card has also been replaced.
So I sit here today with 4.1.1 installed (less the radio-cdma.img). I can Odin the older stock images found here on XDA by deleting the radio-cdma.img within. Then use fastboot to flash the 4.1.1 images individually to have a Wi-Fi only device.
I'm willing to try anything. Any takers?
Click to expand...
Click to collapse
Try this if you can http://forum.xda-developers.com/showthread.php?t=1743939
Did you do the *#06# I already think its gonna come back blank but ....what the hell right
Sent from my Galaxy Nexus using Xparent Purple Tapatalk 2
JediNinjafication said:
Did you do the *#06# I already think its gonna come back blank but ....what the hell right
Sent from my Galaxy Nexus using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
Does he have the samsung drivers installed? If so does his computer recognize his phone when plugged in either adb or fastboot? Cause if he does then you can easily go back to stock 4.0.4 IMM76k using my link in above post
MEID definitely smoked. *#06# yields nothing. I have tried flashing back to stock IMM76K but cannot get past radio-cdma flash... it hangs. If I remove the radio-cdma image it stock flashes no problem... but I still don't have MEID when doing that. I believe I flashed GSM ROM or radios at some point. I say this because when in terminal emulator and type getprop, the output has several gsm entries. Verizon is sending me another SIM card. But before I put it in I believe I need to have the GSM stuff off the phone. I'm not quite sure how to do that.
My screen is cracked, Verizon and Samsung can do nothing for me. I'm on my own on this. I have two rumor touch (sprint) that work fine. I also have HTC EVO 4g (Sprint)... been looking at activating on Verizon, but have had no luck getting CDMA tools to recognize phones... even after wiping drivers and re-installing multiple times.
I'm stuck using a very basic Samsung Knack flip at the moment... Sucks big time. Cash is short so I'm trying to make do with what I have.
Still needing help guys and gals!
And thank you all so much for your ideas and suggestions! I have learned a lot!
Sent from my Galaxy Nexus using xda app-developers app
Do you have the box that came with device so can reapply meid? You'll need your msl in order to edit. If have a backup of original stock after you unlocked bootloader..that one might reapply your info. Otherwise you need that mls
Sent from my Galaxy Nexus using Xparent Purple Tapatalk 2
Hi, Guys!
I have the same problem On Samsung Galaxy S3 LTE GT-i9305 - by mistake flashed with ODIN "phone " section ( that means I flashed RADIO ) - as a result No IMEI, NO RADIO-GSM, BASEBAND unknown...(((
Somebody found solution?
Thanks in advance!
My brother is having the same problem with his Galaxy Nexus. Anybody found a fix for this problem?
I just started having this issue the other day as well (baseband/IMEI, etc all unknown). Phone was just sitting on my desk when I noticed it didn't have service. After being unable to flash the cdma radio, I am trying to get the phone back to stock. However, I am unable to flash the stock image because there is a version check for the cdma radio. Is there a way to flash the stock image without the cdma radio check?
ackurv said:
I just started having this issue the other day as well (baseband/IMEI, etc all unknown). Phone was just sitting on my desk when I noticed it didn't have service. After being unable to flash the cdma radio, I am trying to get the phone back to stock. However, I am unable to flash the stock image because there is a version check for the cdma radio. Is there a way to flash the stock image without the cdma radio check?
Click to expand...
Click to collapse
Any luck with yours. I just started having the same problem. My phone freezes and I have no service. I am trying to return to stock using this GUIDE but my phone freezes whenever I try to Flash the CDMA Radio. If I skip that step it doesn't install the stock version and I'm stuck in Paranoid 3.2 and unable to return to the store in the current condition due to warranty issues. If I can make it stock I will go get a new one.
jaymazz13 said:
Try this if you can http://forum.xda-developers.com/showthread.php?t=1743939
Click to expand...
Click to collapse
Just wanted to let others know that I was on a JRO03O rom, decided to return to stock 4.1.1 and must have screwed up something because after getting back up and running I had the same issues as OP. No baseband, IMEI, *#06# was blank, etc. I was about to embark down the path JediNinjafication linked to, but it looked extremely intimidating. Jaymazz's link to Vabeachfc3s reset tool worked like a champ, put me back at at 4.0.4 and all the radio stuff started working right away! Phone updated itself to 4.1.1 shortly thereafter, and it's still going strong.
Rooted my AT&T Samsung Galaxy Note ii (SGH-I317)
Installed custom ROM and now get no service.
Upon checking Settings -> Mobile Network
It says: INSERT SIM card Insert SIM card to access network services
About Devices has all the correct information except:
Baseband version says: UNKNOWN
How do I fix this?
Did my SIM card somehow and need to get a new SIM and call AT&T to reactivate another SIM?
My guess is that I would need stock ROM image to fix this but cannot find it.
I did find Stock Rooted I317UCALJ2 (http://forum.xda-developers.com/showthread.php?t=1986556)
image but still no Service.
Any help would be appreciated as my phone is a BRICK now and useless.
thanks
i have the exact same problem and can't seem to find an answer...
restore stock rom and still nothing...
did you flash a ROM & Radio for the international Note II (N7100 or N7105)? check your phone for an IMEI number; if it's not there, then you'll have to fix that first. you aren't the first to have this problem and i've read other posts where users were able to correct the problem.
I like how no one responded for 2 months.
Worst case scenario flash stock and triangle away to 0 flash counter amd take it back. Lol. Say it stopped working.
Sent from my SGH-I317 using xda app-developers app
Your comment makes a lot of sense... I'm running root on stock and didn't have a problem. I've recently installed CMW thru Odin which I'm pretty sure I did right but then...I installed a kernel to be able to overclock... could the kernel have mess up my radio? I'm not able to pull up my imei... Can you point me to the right directions in order to restore my stock Rogers kernel?
Sent from my SGH-I317M using xda premium
---------- Post added at 01:59 AM ---------- Previous post was at 01:49 AM ----------
That is indeed my worst case scenario but I would really wish to avoid that as I really want to could fix this on my own... I know it's possible with the help of people like you guys, I'm new to android and I still went ahead and bought the premium version of this app to support this community
Sent from my SGH-I317M using xda premium
I have been here. Installed the CrashRom which was probably not meant for 1317s. Though I loved the ROM, my model number was displayed as 7100, IMEI was null and mobile network would display insert sim message.
If you watched the installation of the rom.. you would have noticed that at the end it rewrites your modem/radio files. Thankfully even after a wipe, the all important NV folder was there.
I was able to find the original AT&T rom at stockroms and also the original modem files for the 1317. I did a full wipe and installed this rom back..and thankfully the radio was back online. Didn't have to flash the modem. Now with a working phone, I wanna read well before I flash my rom again.
Hope this helps. Though I am a newbie.. If you need any further information.. feel free to send me a message.
iZack187 said:
Your comment makes a lot of sense... I'm running root on stock and didn't have a problem. I've recently installed CMW thru Odin which I'm pretty sure I did right but then...I installed a kernel to be able to overclock... could the kernel have mess up my radio? I'm not able to pull up my imei... Can you point me to the right directions in order to restore my stock Rogers kernel?
Sent from my SGH-I317M using xda premium
---------- Post added at 01:59 AM ---------- Previous post was at 01:49 AM ----------
That is indeed my worst case scenario but I would really wish to avoid that as I really want to could fix this on my own... I know it's possible with the help of people like you guys, I'm new to android and I still went ahead and bought the premium version of this app to support this community
Sent from my SGH-I317M using xda premium
Click to expand...
Click to collapse
-----------------------------------------------------------------------------------
If you look in the development section in the All in One forum link, there is a link to the stock rogers ROM and radio.
I don't know if you have done this but it hasn't been mentioned in the post so I thought I would mention it.
I had the same happen to me. The radio just quit. I had a circle with a slash through it. I Odin flashed the stock tar and no luck in fact it got worse and I had to get phone replaced. I have a ton of flashing experience and this was a first for me. I think like someone mentioned above it was a mix match ROM with some pieces from the international version although it was posted as an AT&T ROM. I still have to send it back but after seeing that someone above fixed theirs I am sending a PM
Sent from my GT-I9300 using Xparent ICS Tapatalk 2
Yeah that's exactly what happened to me, lol, installed the CrashRom. But thanks to this failure of epic proportions, I've learnt so much and I've succeeded in restoring my Rogers modem files
Now I got my nandroid backup, and if I mess up again, I got my Rogers stock ROM, radios, and kernel with me at all times
Sent from my SGH-I317 using xda premium
I know from past experience using ODIN for the Droid Charge, we had to pull the SIM before flashing. People were getting their SIMs fried sometimes. The remedy was to remove until the flash was complete. Avoid touching the contacts though.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
I wanted to bump this as I am having the same issue. I tried using Odin to reinstate the stock rom and radio and still nothing.
So this happened to me and after I unrooted and factory reset I had no luck, called Att and got a new one. But I don't know why it stopped reading my sim, it. Worked in my iPhone 5. Strange
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
I flashed the Bell Root66 file to my Bell Note II and now I have NO Modem, NO IMEI Number and cant figure out how to get it back. I have flashed the Bell CSC after installing to try and remedy the issue with no luck. I have tried to return my phone to stock for 2 days now (the install counter shows 21 times!). I NEED HELP with this please guys!
I am in Toronto and am on Bell Mobility. After 2 days and 21 flashes I am no further ahead and could use some guidance please!
iZack187 said:
Yeah that's exactly what happened to me, lol, installed the CrashRom. But thanks to this failure of epic proportions, I've learnt so much and I've succeeded in restoring my Rogers modem files
Now I got my nandroid backup, and if I mess up again, I got my Rogers stock ROM, radios, and kernel with me at all times
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
cortez.i said:
did you flash a ROM & Radio for the international Note II (N7100 or N7105)? check your phone for an IMEI number; if it's not there, then you'll have to fix that first. you aren't the first to have this problem and i've read other posts where users were able to correct the problem.
Click to expand...
Click to collapse
can u give any links to these forums, yes i install n7100 rom on my i317 and yes i don't have a imei.
Well my friend ...I've got to tell you up front ...that the likelihood of getting your device repaired on your own is remote at best...
You have damaged the device partitions ...and likely do not have a usable backup of the EFS folder..
The EFS contains the IMEI number used for restoration purposes...
I'm not going to tell you that a repair cannot be done..as a select few users were able to fix a bricked device...but I will suggest your best solution ...IMHO
Contact the good folks at :
mobiletechvideos.com
And let them know what you did..
They offer a complete restoration service to repair your device correctly ...and can likely do the job in about a week...
They are located in Texas, USA I believe ...and they have an excellent reputation for quality service...
Your choice of course...but if I were in your situation...I'd send the device to them in a second...
Time is money...at least for me...and although I could probably fix it...I don't have a RIFF BOX...or a JTAG ...
Others will post up with links to help you...and after you have a chance to look them over ...you can decide..
Very sorry for the damaged phone....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
t989D problem
I have a similar problem. I installed Superandroid 4.3 on a telus/koodo s2 t989D. I had to update the radio to flash the rom. I used CWM for that.
Now the info I have on the phone is
model sgh t989
android version 4.3
baseband t989uvmc6 .
The phone is not reading my SIM at all. It shows my carrier but no signal strength at all. I have read the above post. My IMIE number is still there.
Any help
Hi everyone... I rooted my samsung galaxy note 2 to android revultion HD and to my avail... I can't make phonecalls and text obviously i didn't know anything about Efs back up it said recommended but wasn't check at this time i was just hitting next,next ect. ect. and then the phone starts up working and rooted! I get extremely happy then i try to make a phone call but nope mobile network is avalabile i check my baseband (Unknown) Imei(Unknown) take in mind i'm exteremly new to this and had no clue about the EFS or Imei number ect. I am tech savy with other products such as Jtag (For xbox 360) but this was my first root and i know i messed up... So let me sum everything up. I Have a two-year contract with verizon and Total Full Coverage, But i'm assuming this voids warrenty right... I called verizon and made up a story saying... I left my phone at work and it was stolen for about a week i then told everyone at work if it wasn't returned a week later that i would be tracking the phone with the police and that the phone was returned the next morning on my desk... and that i was missing the simcard and everything was wiped... They simple told me to come in and they will replace the sim card for free... Now my phone is still rooted... I'm going to stock flash it with odin or at least try... Will simply getting a new sim card work or do i need a whole new phone?... and should i even unroot it stock?... or take it in with SuperUs and said thats how i found it when i got it back stolen...? Please help...
SuicideSkater said:
Hi everyone... I rooted my samsung galaxy note 2 to android revultion HD and to my avail... I can't make phonecalls and text obviously i didn't know anything about Efs back up it said recommended but wasn't check at this time i was just hitting next,next ect. ect. and then the phone starts up working and rooted! I get extremely happy then i try to make a phone call but nope mobile network is avalabile i check my baseband (Unknown) Imei(Unknown) take in mind i'm exteremly new to this and had no clue about the EFS or Imei number ect. I am tech savy with other products such as Jtag (For xbox 360) but this was my first root and i know i messed up... So let me sum everything up. I Have a two-year contract with verizon and Total Full Coverage, But i'm assuming this voids warrenty right... I called verizon and made up a story saying... I left my phone at work and it was stolen for about a week i then told everyone at work if it wasn't returned a week later that i would be tracking the phone with the police and that the phone was returned the next morning on my desk... and that i was missing the simcard and everything was wiped... They simple told me to come in and they will replace the sim card for free... Now my phone is still rooted... I'm going to stock flash it with odin or at least try... Will simply getting a new sim card work or do i need a whole new phone?... and should i even unroot it stock?... or take it in with SuperUs and said thats how i found it when i got it back stolen...? Please help...
Click to expand...
Click to collapse
Hi,
Just explaining. EFS is kind of a folder that contains the IMEI number and other MAC addresses of WIFI or Bluetooth. What happened when you rooted and flashed a ROM is that the EFS folder has been modified. There are many reasons why this happens. So, changing a new SIM won't work. You would have to fill the IMEI number and the other MAC addresses to make phones calls and etc.,
Regarding whether to leave the phone with root or not, It depends on you whether you can make up a convincing story to avoid charges for re-instating the IMEI number back by Samsung.
You can change it to Stock if you want to, but Verizon can easily find out that you had rooted it since IMEI number won't be wiped by any other way..
prabukannappan said:
Hi,
Just explaining. EFS is kind of a folder that contains the IMEI number and other MAC addresses of WIFI or Bluetooth. What happened when you rooted and flashed a ROM is that the EFS folder has been modified. There are many reasons why this happens. So, changing a new SIM won't work. You would have to fill the IMEI number and the other MAC addresses to make phones calls and etc.,
Regarding whether to leave the phone with root or not, It depends on you whether you can make up a convincing story to avoid charges for re-instating the IMEI number back by Samsung.
You can change it to Stock if you want to, but Verizon can easily find out that you had rooted it since IMEI number won't be wiped by any other way..
Click to expand...
Click to collapse
Oh thats not good.... What would you do in my situation.... I'm taking my phone up to verizon tommorow... to see if they can provide me with what i need to do.... and if they find out it was rooted will they not help me at all and just tell me to pay full price for a new phone (keep in mind the galaxy note 2 is $800 still) also i have total full coverage... + that convincing story... and its my first phone with verizon aka first problem... please tell me they will fix it without charging me....
Have you flashed a N7100 rom on a N7105 or vice versa as that will make baseband unknown and can be fixed.
Sent from my GT-N7105 using xda premium
Nope it doesn't look like i did... My model number is GT-N7100 and the Rom i put on it was this Samsung Galaxy Note 2 (N7100)
Jelly Bean (Android 4.1.2)
Download Android Revolution HD 19.0... Both N7100 any ideas? i would love to get this fixed... If its not fixable please provide suggestions anyone that helps me fix this problem or provides good enough info i will give $5-10 paypal... its not much... but i'm a college student.. trying to make a living... Thanks so much guys...
This is what happens when you don't even read the thread, but just download the file and keep pressing next. I guess you learned that you should READ before you flash. You might wanna try flashing the original firmware from Sammobile. But I guess you're in a pretty big problem now.
http://forum.xda-developers.com/showthread.php?p=42794146
[EFS/IMEI][ME6/MF2]Please Read Before Flashing
Sent from my GT-N7100 using XDA Premium 4 mobile app
---------- Post added at 10:00 AM ---------- Previous post was at 09:57 AM ----------
You flashed a dmg1 modem rom ...flash a dmg1/me6/mf2 modem..I use mf1
Sent from my GT-N7100 using XDA Premium 4 mobile app
Guys! I fixed it! well at least i have no more problems with it and its back to normal i called my house phone with it and it rang... so its fixed Lol... Anyways to anyone else that has the trouble i did (also to you guys telling me that i should have read first i followed serveral guides i studied up on rooting for weeks because i was afraid never once did i see anything about backing up the efs folder.. first time i saw it was after i flashed a rom.. it should be noted in adam outler no you verizon post... because thats the root method i followed and it work except i didn't hit efs backup because last time i did that my rom failed to download and stayed at 0% which i'm led to believe because i didn't wipe the cache... but what i did to fix my problem was download Odin 3.07... Download Samsung Galaxy note 2 i605 stock Load The .pda and download the samsung pit file started Odin and bam it did all the work phone started back up like it was opened out the box i am now going to think twice about rooting next time... But one more thing guys my phones working find and all but Odin popped up Fail on one Box and then in the dialog is said <ID:0/003> Can't open the serial(COM) port. This is not big its because i switched my usb ports?... Right idk? here is a picture View attachment 2194422
SuicideSkater said:
Guys! I fixed it! well at least i have no more problems with it and its back to normal i called my house phone with it and it rang... so its fixed Lol... Anyways to anyone else that has the trouble i did (also to you guys telling me that i should have read first i followed serveral guides i studied up on rooting for weeks because i was afraid never once did i see anything about backing up the efs folder.. first time i saw it was after i flashed a rom.. it should be noted in adam outler no you verizon post... because thats the root method i followed and it work except i didn't hit efs backup because last time i did that my rom failed to download and stayed at 0% which i'm led to believe because i didn't wipe the cache... but what i did to fix my problem was download Odin 3.07... Download Samsung Galaxy note 2 i605 stock Load The .pda and download the samsung pit file started Odin and bam it did all the work phone started back up like it was opened out the box i am now going to think twice about rooting next time... But one more thing guys my phones working find and all but Odin popped up Fail on one Box and then in the dialog is said <ID:0/003> Can't open the serial(COM) port. This is not big its because i switched my usb ports?... Right idk? here is a picture View attachment 2194422
Click to expand...
Click to collapse
Hi,
The first mistake you have done is that your phone model is not N7100. It is different for Verizon. That's the reason your IMEI number got screwed up when you flashed a rom of N7100.
The Fail in Odin is not a big deal as it might have been because there could have been two usb connections made or as you said changing usb ports.
Please verify whether the ROM supports your Verizon model before flashing.
Also, There will be still a counter and status that would indicate that you've rooted before If you want to reset these counters then search in the forum and you'll be able to find out.
prabukannappan said:
Hi,
The first mistake you have done is that your phone model is not N7100. It is different for Verizon. That's the reason your IMEI number got screwed up when you flashed a rom of N7100.
The Fail in Odin is not a big deal as it might have been because there could have been two usb connections made or as you said changing usb ports.
Please verify whether the ROM supports your Verizon model before flashing.
Also, There will be still a counter and status that would indicate that you've rooted before If you want to reset these counters then search in the forum and you'll be able to find out.
Click to expand...
Click to collapse
Thank you good sir! Yes i believe the program is called triangle away and you have to be rooted to access it.... I was going to do it while i was rooted but they want $2.50 for it.... just to reset counters.. i've seen plenty get warrantys restored even tho they didn't reset the counter verizon/samsung doesn't have time to check every single phone its just to be extra safe
SuicideSkater said:
Thank you good sir! Yes i believe the program is called triangle away and you have to be rooted to access it.... I was going to do it while i was rooted but they want $2.50 for it.... just to reset counters.. i've seen plenty get warrantys restored even tho they didn't reset the counter verizon/samsung doesn't have time to check every single phone its just to be extra safe
Click to expand...
Click to collapse
You don't have to pay as the dev also posts the app for free in XDA. See the link below:
http://forum.xda-developers.com/showthread.php?t=1494114
SuicideSkater said:
Thank you good sir! Yes i believe the program is called triangle away and you have to be rooted to access it.... I was going to do it while i was rooted but they want $2.50 for it.... just to reset counters.. i've seen plenty get warrantys restored even tho they didn't reset the counter verizon/samsung doesn't have time to check every single phone its just to be extra safe
Click to expand...
Click to collapse
You make out like resetting the counters is easy or something. It isn't and it's reasonable price for the app.
I suggest you go to the Verizon Note II forum next time unless you want to break your phone again.
Sent from my GT-N7100
I had similar problem. May be you haven't deleted it. The #4 comment is kinda right. By mistake I wiped my internal storage without backup or without writing down the baseband and build numbers. I had to flash numerous stock roms until I was able to make phone calls and receive msgs. Also on stock roms that were not for my phone the imei # was different from the one on the box, starting with 0049 or something.
Sent from my GT-N7100 using Tapatalk 4
Armazia said:
This is what happens when you don't even read the thread, but just download the file and keep pressing next. I guess you learned that you should READ before you flash. You might wanna try flashing the original firmware from Sammobile. But I guess you're in a pretty big problem now.
Click to expand...
Click to collapse
+1
GT N7105 with XDA Premium......that is all......
First of all
Flash stock and the might sort the baseband out
If that doesnt work just send it in after unrooting. I had a similiar problem but I acted dumb and said it just happened and they took it in and repaired within 12 days.
Sent from my GT-N7100 using xda app-developers app
---------- Post added at 07:16 PM ---------- Previous post was at 07:13 PM ----------
Oh and btw just say it happened via Kies if they ask and if that doesnt work then put in the washing machine and give it (My cousin hard bricked his so he gave it water damage and he sent it in although he had to pay 75 pounds
Sent from my GT-N7100 using xda app-developers app
EFS backup
The moral is to backup the efs folder ASAP, at least before you try anything 'drastic' to your phone
lost imei
I also lost my imei the first time i flashed custom rom on my note 2. but i simply flash older modem and its working fine since then.. ohh and i als made efs backup using terminal emulator..
Hello all,
I am a noob so be gentle.
I have a Samsung Galaxy S3 from AT&T. Inside the battery compartment the label says SGH-I747. I can't boot the phone so that is all I know about the model # at present. I am looking at the following link: http://forum.xda-developers.com/showthread.php?t=2549068. It mentions all over the place that it will work with the SGH-I747 but the debrick files that are supposed to work for this model reference SGH-I747U. Are they the same?
Your help is appreciated
Can you get the phone into download or recovery mode?
Thanks for your reply. The phone is not in my possession at the moment (should have it on Monday). I will check back when it returns and reply with more details.
garyh140 said:
Hello all,
I am a noob so be gentle.
I have a Samsung Galaxy S3 from AT&T. Inside the battery compartment the label says SGH-I747. I can't boot the phone so that is all I know about the model # at present. I am looking at the following link: http://forum.xda-developers.com/showthread.php?t=2549068. It mentions all over the place that it will work with the SGH-I747 but the debrick files that are supposed to work for this model reference SGH-I747U. Are they the same?
Your help is appreciated
Click to expand...
Click to collapse
The at&t phone is model # I747 baseband I747UCUEMJB (on my current modem).
Do not be concerned with the difference between I747 and I747U they are the same where you should be concerned is with the difference between I747/U Vs. I747M
Flashing the wrong bootloader will eternally brick your phone until it gets jtag'ed.
so be careful and ask questions when you aren't sure.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
The at&t phone is model # I747 baseband I747UCUEMJB (on my current modem).
Do not be concerned with the difference between I747 and I747U they are the same where you should be concerned is with the difference between I747/U Vs. I747M
Flashing the wrong bootloader will eternally brick your phone until it gets jtag'ed.
so be careful and ask questions when you aren't sure.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks!!
I need to bring this phone back to life when it returns and I will need more help then.
Background:
I Used auto root some time ago to get something to work that never did. I totally forgot about it then took an OTA update Last Saturday to what I thinks was 4.3 that ended up in hangs and continuous reboots. Not sure why this failed because I have taken one other OTA that was successful. I was dumb enough to call AT&T who in turn called Samsung Support. They asked me to take it to Best Buy for reflashing. That was a waste of 2 hours of my life and a massive fail. Called AT&T Back who again called Samsung. Samsung asked me to send the Phone to them for re-flashing and they knew it was out of warranty. Dummy me thought well if it is out of warranty I don't need to worry about if it is rooted or not. Besides who should know better how to and have the resources to re-flash it back to stock than Samsung. So I sent it to them. We all know the rest of the story. They found it was rooted and wouldn't touch it. So now you know why it is not in my possession till Monday.
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