First, I'm an idiot,,,got new to android,,had no idea about flashing,, so I just randomly picked a Rom, and turned out its a GT-N7100 ROM, now my phone has no signal at all,,, anyone know how to flash back ? or I have to wait a att ROM come out?
BTW, Im with Rogers.
Thanks:laugh:
your gonna have to wait till either someone makes a odin back with a stock rom or makes a stock rom you can flash via recovery.
EDIT: did you make a backup?
this reminds me of the following youtube video:
http://www.youtube.com/watch?v=wwleOote5M0
Can you give a link to the firmware you flashed? It'd be useful to know if it contained a modem and/or kernel (or not.)
If it contained a modem, you'll need another modem. If it contained a kernel, you'll need another kernel. We have those. Regardless, you'll need to talk someone into getting you a system image (someone that has the same phone as you and has already rooted.)
Also, do you have CWM recovery installed? Is the existing firmware (as trashed as it might be) rooted? Can you use adb?
im an idiot
garyd9 said:
this reminds me of the following youtube video:
http://www.youtube.com/watch?v=wwleOote5M0
Can you give a link to the firmware you flashed? It'd be useful to know if it contained a modem and/or kernel (or not.)
If it contained a modem, you'll need another modem. If it contained a kernel, you'll need another kernel. We have those. Regardless, you'll need to talk someone into getting you a system image (someone that has the same phone as you and has already rooted.)
Also, do you have CWM recovery installed? Is the existing firmware (as trashed as it might be) rooted? Can you use adb?
Click to expand...
Click to collapse
nope,, I didnt back up anything,,
heres the ROM link I used.
http://forum.xda-developers.com/showthread.php?t=1925402
...
I just opened the file you linked to.. it includes a modem, kernel, etc.
I know you won't be happy with this, but until an ODIN image shows up, you're kind of out of luck. If someone you know has the same phone, you could ask them to do a backup to an external memory card, and then you restore that backup to your device. Assuming the modem wasn't flashed when you installed, that would get you back into business. If a modem was flashed, you'll need to get someone to extract a modem (and I'm not sure how to go about doing that.)
garyd9 said:
Please answer ALL of these questions. I can't help you if you don't answer them all...
Does your phone work now, with the exception of connecting to the mobile network?
Are you familiar with adb? If so, are you able to get a shell via adb?
When you plug your phone into your computer, are you able to copy files to/from the phone?
Which custom recovery do you have installed? CWM recovery or TWRP?
Is your phone rooted? (it probably is with a custom firmware - assuming the phone works at all.)
Click to expand...
Click to collapse
sorry buddy,,,
right now, the phone has no signal, asking for a sim card, which Ive already inserted it.
noepe, I donno what adb is, I tried google it, but I think its too complicate for me.
I'm able to copy files into or from my phone( SD card)
i rooted my phone through this:
http://forum.xda-developers.com/showthread.php?t=1923956
donno if i successed,,, but it has a superSU on my screen after I done it,(guess it count as rooted?) and I may used the TWRP
thank you for your help....
now Im back to my old Iphone 4
I updated that post. Basically, I can't think of anything you can do right now.. until an ODIN dump is available - or if someone gets you a backup you can restore. However, a backup won't flash the proper modem (and it appears you also overwrote the modem.)
garyd9 said:
I updated that post. Basically, I can't think of anything you can do right now.. until an ODIN dump is available - or if someone gets you a backup you can restore. However, a backup won't flash the proper modem (and it appears you also overwrote the modem.)
Click to expand...
Click to collapse
so, if theres a ATT ROM avaiable in the future,,,I can use my phone again by flashing the ATT ROM?
callmejoe1 said:
so, if theres a ATT ROM avaiable in the future,,,I can use my phone again by flashing the ATT ROM?
Click to expand...
Click to collapse
Was the phone originally from AT&T or Rogers?
callmejoe1 said:
First, I'm an idiot,,,got new to android,,had no idea about flashing,, so I just randomly picked a Rom, and turned out its a GT-N7100 ROM, now my phone has no signal at all,,, anyone know how to flash back ? or I have to wait a att ROM come out?
BTW, Im with Rogers.
Thanks:laugh:
Click to expand...
Click to collapse
Welcome to club i've been here for 6 days... it's a crappy feeling especially when its your work phone :[
garyd9 said:
Was the phone originally from AT&T or Rogers?
Click to expand...
Click to collapse
with rogers,but I heard ppl say ATT AND ROGERS‘s ROM can be equivalent , are they ?
callmejoe1 said:
with rogers,but I heard ppl say ATT AND ROGERS‘s ROM can be equivalent , are they ?
Click to expand...
Click to collapse
Perhaps - perhaps not. Until one actually flashes from the other, we don't know. (Many will tell you that they've done it with a different phone model - my answer to that is simply that it was a different phone model. Until its tried with THIS one, we can only guess.)
I think the biggest stumbling block for you right now is the modem. We have a stock kernel and recovery. A "near" stock system partition image can also be made from another device with a simple command. I have to be honest, though, that I have no clue how to extract the modem from these LTE phones.
A recovery (and kernel) can easily be flashed with ODIN (or with dd from a rooted shell.) Same for the system partition (which is, basically, the OS.) Getting a system image might be annoying, as you'd need to find someone with a roger's phone to make it for you, upload it, etc.
The modem, however... I'm not sure how to go about getting that for you. I've never had to create a modem image...
If/when a ODIN package appears, you can use a program that will, basically, reflash your entire phone to stock. Modem, kernel, recovery, bootloader, etc. Everything. Normally, users wouldn't see those ODIN packages, but there are a couple of websites that have access to some samsung servers where they a put. Once they are put there, we can get it...
Take care
Gary
Mobiletechvideos. Have them Jtag it for you.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Just me happy you don't have the note 1 if you would have made that same mistake you could have bricked your phone
envision said:
Just me happy you don't have the note 1 if you would have made that same mistake you could have bricked your phone
Click to expand...
Click to collapse
Yup your very lucky
I firmly believe you cna just flash your modem and kernel on top and it will be fine ,.
im hella busy this weekend but im sure we can get you fix withou a single $$ injected on your part
DAGr8 said:
I firmly believe you cna just flash your modem and kernel on top and it will be fine ,.
im hella busy this weekend but im sure we can get you fix withou a single $$ injected on your part
Click to expand...
Click to collapse
Looking forward to this remedy as this is the reason I am jumping from att Galaxy S 3 to the note2. Want my international dev community back!
Unfortunately so far down here in Southern Florida Miami beach there is no white Note 2 anywhere.
For those that have the ATT version of the Note 2, if you've mistakenly flashed the ROM, I highly suggest visiting your nearest AT&T Device Support Center. Since I've previously worked in those centers, they have a propietary Samsung flashing tool that allows them to flash to the stock ROM, even if it's rooted. Granted they'll be able to tell if you've rooted it or not (which may or may not void the warranty, depending on who you talk to), as long as the phone can turn on and go to firmware recovery mode, the flashing works almost 100% of the time and it's a free service.
However, as I got my Note 2 yesterday, I've contacted my nearest DSC and they said that they don't have the ability to flash the Note 2 yet and they may have that ability to do so in the next few weeks or possibly by the end of the year (if you can wait that long). Being that the associates are just corporate drones, if they can't fix it, they'll more than likely replace your phone under warranty (which I don't suggest since the replacements are refurbished, and besides you should be within the 14 day return period for a new phone).
Sorry if it doesn't help the ones who have the Rogers versions.
DAGr8 said:
I firmly believe you cna just flash your modem and kernel on top and it will be fine ,.
im hella busy this weekend but im sure we can get you fix withou a single $$ injected on your part
Click to expand...
Click to collapse
would you mind if you can post the link for the modem and kernel please?
thank you
DAGr8 said:
I firmly believe you cna just flash your modem and kernel on top and it will be fine ,.
im hella busy this weekend but im sure we can get you fix withou a single $$ injected on your part
Click to expand...
Click to collapse
Im having the same problem. I hope you can roll out a fix!
Related
Anyone have these yet by chance?
I am sure it is coming. I would like to get my hands on it also.
Would be nice to have as I've already screwed it up.
liquidblue1985 said:
Would be nice to have as I've already screwed it up.
Click to expand...
Click to collapse
did you flash the n7100 stock firmware?
JoJo2211 said:
did you flash the n7100 stock firmware?
Click to expand...
Click to collapse
Nope. Downloading that right now actually. The only issue I'm having is that it's not recognizing the baseband.
It would be nice to be able to flash the Tmobile modem.
gedster314 said:
It would be nice to be able to flash the Tmobile modem.
Click to expand...
Click to collapse
Yeah. I'm pretty much stuck at this point. I have a custom recovery installed, root and on an international rom but I cannot get cell service. Wifi works, but that's about it.
I believe it has to do with the isis security.
Was thinking about going to TMO and getting a non-isis sim card to try.
liquidblue1985 said:
Yeah. I'm pretty much stuck at this point. I have a custom recovery installed, root and on an international rom but I cannot get cell service. Wifi works, but that's about it.
Click to expand...
Click to collapse
+1 I need the modem or a stock tar to odin asap, hope it drops soon...
The non-ISIS sim card did not change anything.
Looks like I need the stock rom also.
:/
luser01 said:
I believe it has to do with the isis security.
Was thinking about going to TMO and getting a non-isis sim card to try.
Click to expand...
Click to collapse
If anyone can help out with getting a flashable radio for this it'd be greatly appreciated. I've looked around on how to extract the radio from the current version with no luck.
As far as the ROM, a user linked one here:
http://forum.xda-developers.com/showpost.php?p=33242968&postcount=67
I've restored that through custom recovery/nandroid and it works fine. But without the radio... I'm lost.
I get a MD5 mismatch when I try to restore it with nandroid.
Downloaded it twice. anyone else had luck?
liquidblue1985 said:
If anyone can help out with getting a flashable radio for this it'd be greatly appreciated. I've looked around on how to extract the radio from the current version with no luck.
As far as the ROM, a user linked one here:
http://forum.xda-developers.com/showpost.php?p=33242968&postcount=67
I've restored that through custom recovery/nandroid and it works fine. But without the radio... I'm lost.
Click to expand...
Click to collapse
luser01 said:
I get a MD5 mismatch when I try to restore it with nandroid.
Downloaded it twice. anyone else had luck?
Click to expand...
Click to collapse
Had the same thing. Best bet is to go into the md5 file with a text editor and just delete everything and save the file. Recopy the md5 file over and reflash. Not sure why it was causing this error because I even re-ran the md5's myself and they were the same.
Also, just got off the phone with Samsung, they pretty much said the phone is not in their system yet and they do not have access to the firmware at this point. Their suggestion was to go back to t-mobile and get an exchange unit.
I will try that..
I called Samsung last night and they gave me the same run around.
liquidblue1985 said:
Had the same thing. Best bet is to go into the md5 file with a text editor and just delete everything and save the file. Recopy the md5 file over and reflash. Not sure why it was causing this error because I even re-ran the md5's myself and they were the same.
Also, just got off the phone with Samsung, they pretty much said the phone is not in their system yet and they do not have access to the firmware at this point. Their suggestion was to go back to t-mobile and get an exchange unit.
Click to expand...
Click to collapse
Just hoping now that maybe someone with enough knowledge sees this and can extract a flashable baseband... I'd really hate to go and buy another unit.
liquidblue1985 said:
Just hoping now that maybe someone with enough knowledge sees this and can extract a flashable baseband... I'd really hate to go and buy another unit.
Click to expand...
Click to collapse
You should find a store with one on the shelf, and not much supervision... and root it/extract a nand image hehehe. Though that would mean you would have be able to do all that and I have no idea how to extract a baseband image that is the power of the xda dev gods!
How hard is it to extract a baseband image?
Could someone that has one do it easily?
MikeBrWade said:
You should find a store with one on the shelf, and not much supervision... and root it/extract a nand image hehehe. Though that would mean you would have be able to do all that and I have no idea how to extract a baseband image that is the power of the xda dev gods!
Click to expand...
Click to collapse
I'm not sure if this is what you're looking for in particular buuut...
http://forum.xda-developers.com/showthread.php?t=1954597
It was (and still is) posted on the N7100 dev forum. It's the T-Mobile boot.img in tar format. Read through the thread for more info.
That is for people that messed up the rooting.
I flashed a full ITL rom that had the modem in it.
All I need is the modem and I am good to go.
/Waits
anoneemooz said:
I'm not sure if this is what you're looking for in particular buuut...
http://forum.xda-developers.com/showthread.php?t=1954597
It was (and still is) posted on the N7100 dev forum. It's the T-Mobile boot.img in tar format. Read through the thread for more info.
Click to expand...
Click to collapse
luser01 said:
That is for people that messed up the rooting.
I flashed a full ITL rom that had the modem in it.
All I need is the modem and I am good to go.
/Waits
Click to expand...
Click to collapse
Oh so wait. You're using a T-Mobile Note 2 and managed to flash an international ROM with everything working and functional (except for signal/sms/data/call) ? No reboots?
I ask because I've been wanting to somehow "convert" my T-Mobile Note 2 to an international Note 2 (as in, be able to flash the updates the international version gets instead of waiting on T-Mobile). I'm not US based so I don't need it to work with T-Mobile SIM anyhow...
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
hi everyone.. i just bought Samsung Galaxy Note II 4G on first december, from Optus Australia..
and last night i try to root, and flashing Omega v7.3 Rom from N7100, it is work well but the IMEI and Signal is gone, and also the S-pen is not working..
and i try use N7105 custom rom http://forum.xda-developers.com/showthread.php?t=1985200
and also my signal is still not detected, but my S-Pen is working back..
somebody please help me...
how to fix my signal problem
benatis said:
and flashing Omega v7.3 Rom from N7100
Click to expand...
Click to collapse
Why in first case did you flash a ROm which isn't intended to be for your device?
Well you killed your EFS partition (bricked)
I hope you mad a EFS backup BEFORE you flashed. So you can restore it and all will be fine.
You could try the Stock Firmware via Mobile Odin if it fixes your EFS problem. No Guarantee here, sometimes it dsoes work and sometimes not.
Good luck to you
Higgins12 said:
Why in first case did you flash a ROm which isn't intended to be for your device?
Well you killed your EFS partition (bricked)
I hope you mad a EFS backup BEFORE you flashed. So you can restore it and all will be fine.
You could try the Stock Firmware via Mobile Odin if it fixes your EFS problem. No Guarantee here, sometimes it dsoes work and sometimes not.
Good luck to you
Click to expand...
Click to collapse
hmm.. i never used Samsung device before.. this is my first Samsung device i have ever..
different with my old HTC devices..
i will try ODIN now... use Stock ROM....
-----
and also, i have tried to wipe data from CWM, why my Note2 device still can boot?
i mean, like not wiped the data completely
benatis said:
hmm.. i never used Samsung deviced before.. this is my first Samsung device i have ever..
different with my HTC devices
Click to expand...
Click to collapse
I believe the reason you are experiencing this issue is because this new firmware you flashed doesn't contain a custom radio and the n7100 firmware did. You will need to find a n7105 radio, flash that through CWM or TWRP and you should be back in business mate.
chrisaw said:
I believe the reason you are experiencing this issue is because this new firmware you flashed doesn't contain a custom radio and the n7100 firmware did. You will need to find a n7105 radio, flash that through CWM or TWRP and you should be back in business mate.
Click to expand...
Click to collapse
where i can download n7105 radio ???
and how to flash the radio?
where i can download the stock Radio, Firmware, and rom of N7105 ???
i Have tried Odin, and flash Stock rom... but i dont know how to wipe data and chache from odin..
i just flash it..
and now, my Signal is appear... lol...
thanks for everyone...
Would be glad to help you but you seem to have skipped the first rule : read, read, read before you do anything else. You even admitted that this is your first Samsung device, so why did u assume that everything should have been htc like ?
Anyhow, you can try to flash the newest 4.1.2 update for the 7105, even though I fear that your problem is your efs folder, and since this is unique for each device, no flashing any rom will put it back in place.
http://forum.xda-developers.com/showthread.php?t=2027586
Good luck,
P_
pakalrtb said:
Would be glad to help you but you seem to have skipped the first rule : read, read, read before you do anything else. You even admitted that this is your first Samsung device, so why did u assume that everything should have been htc like ?
Anyhow, you can try to flash the newest 4.1.2 update for the 7105, even though I fear that your problem is your efs folder, and since this is unique for each device, no flashing any rom will put it back in place.
http://forum.xda-developers.com/showthread.php?t=2027586
Good luck,
P_
Click to expand...
Click to collapse
yah.. i have flash that ROM just now..
but, why my signal is verry in poor level? only showing 2 bar?
im sorry, im not experienced with samsung devices
Since you said that the phone is from Australia and Optus you may want to flash its original firmware back in place :
http://www.sammobile.com/firmware/?page=3&model=GT-N7105&pcode=OPS&os=1&type=1#firmware
If you do not use the phone in Australia you may want to find a firmware (if available) for your device/geographical region.
P_
benatis said:
i Have tried Odin, and flash Stock rom... but i dont know how to wipe data and chache from odin..
i just flash it..
and now, my Signal is appear... lol...
thanks for everyone...
Click to expand...
Click to collapse
I am facing the same problem you had before, however when i try to Odin the stock 4.1.1 firmware back to the phone, it stops at the Samsung logo when restarting. I have to force back to recovery mode to flash the omega back to have it start again. Can you please tell me the steps you did on putting back to stock firmware? thanks
If you haven't yet reflashed the EFS partition (don't do that, ever ! unless you have a good reundant set of backups), you actually don't need to reflash to stock firmware at all (and I doubt that it'd do any good anyways. It just puts back a generic EFS with the files set at default values, but certainly can't put back the data you had in your own device's EFS, this is unique to each phone).
Just head on over to the Galaxy S2 forums and look for a thread called "Restore your IMEI in 9 steps" (something like that. There's actually quite a number of threads describing the same procedure, you can find them by searching "samsung restore imei" in all forums, works just as well).
I had the same problem the other day (and no backup of course, silly and impatient me... ), it worked like a charm..
It's topics like this that i know that People Will get Hurt on. Come on, read and study before doing anything on a smartphone. There's a reason why android doesn't come with administrator rights from factory.
Sent from my GT-N7100 using Tapatalk 2
Hi,
This is for a Canadian T889V (note 2) from Wind Mobile.
A few weeks ago I tried to use the online form to get an unlock code from Wind (they let you have the code after 6 months for $10), and the code didn't work, I called their customer support multiple times, and all I got was, try the same code again (tried it rooted/unrooted/completely stock, etc, etc...), and I'm down to the last unlock attempt.
They also suggested I call Samsung, which I did, but the Samsung rep just told me to call Wind again.
So, in the end, my situation is that I have 1 unlock attempt left, I have a pure stock phone (running 4.1.1, Baseband T889VVLALJ4 (I used Odin to flash image from SamMobile)) that has the flash counter tripped to 4, but at the Odin screen, it says:
Product name: SGH-T889V_NA_VTR (I thought Wind was supposed to be GLW)
Custom Binary Download: yes (4 counts)
Current Binary: Samsung Official
System Status: Official
Click to expand...
Click to collapse
I have tried what was suggested in this thread: http://forum.xda-developers.com/showthread.php?t=2014982 at least 10 times, I got the PERSO_NV_INIT is SUCCESSFUL message at the end at least 7 times, and in all attempts, when I put in the rogers SIM card from my iPad (only other micro SIM I have), it asks for an unlock code.
So now, I think my only option left is to try a third party unlocking service, and hope that it works... does anyone have any suggestions for such service?
Also, is it possible to reset the unlock counter at all/if this fails horribly, am I stuck with Wind for good?
Thanks,
StackUnderflow said:
Hi,
This is for a Canadian T889V (note 2) from Wind Mobile.
A few weeks ago I tried to use the online form to get an unlock code from Wind (they let you have the code after 6 months for $10), and the code didn't work, I called their customer support multiple times, and all I got was, try the same code again (tried it rooted/unrooted/completely stock, etc, etc...), and I'm down to the last unlock attempt.
They also suggested I call Samsung, which I did, but the Samsung rep just told me to call Wind again.
So, in the end, my situation is that I have 1 unlock attempt left, I have a pure stock phone (running 4.1.1, Baseband T889VVLALJ4 (I used Odin to flash image from SamMobile)) that has the flash counter tripped to 4, but at the Odin screen, it says:
I have tried what was suggested in this thread: http://forum.xda-developers.com/showthread.php?t=2014982 at least 10 times, I got the PERSO_NV_INIT is SUCCESSFUL message at the end at least 7 times, and in all attempts, when I put in the rogers SIM card from my iPad (only other micro SIM I have), it asks for an unlock code.
So now, I think my only option left is to try a third party unlocking service, and hope that it works... does anyone have any suggestions for such service?
Also, is it possible to reset the unlock counter at all/if this fails horribly, am I stuck with Wind for good?
Thanks,
Click to expand...
Click to collapse
Hi
I am also with wind and recently obtained the code same way you did. I am rooted running jedix 16 at the time with twrp as my custom recovery. So i am on 4.1.2 and the code worked right away. I dont think you should be on 4.1.1 to do it.
Sent from SGH-T889v Canadian Wind Mobile
vseslija said:
Hi
I am also with wind and recently obtained the code same way you did. I am rooted running jedix 16 at the time with twrp as my custom recovery. So i am on 4.1.2 and the code worked right away. I dont think you should be on 4.1.1 to do it.
Sent from SGH-T889v Canadian Wind Mobile
Click to expand...
Click to collapse
The first time I tried it I used the code on Jedi Master 10 (which is based on 4.1.2 if I'm not mistaken), I also tried the code on 4.1.2 stock (**MA3 base band), and 4.1.1 (**LJ4 baseband).
Right now I think my main priority should be figuring out if its possible to reset the unlock attempts counter (and/or finding other unlocking procedures to bypass the code/counter completely).
I think I just screwed myself even more, I took it to a shady place to see if its possible to get it unlocked, they did some weird voodoo crap which I think bricked by modem. (any attempts to get it into service mode shows a blank screen)
I tried reflashing everything and restoring an old EFS from long ago, but the baseband version in settings->about phone says Unknown, and it kept saying no SIM card even if I use my original SIM....
Did anyone encounter this before? how to fix this? do I need to get the hardware fixed? is Samsung likely to help?
Edit: I'm fairly sure they used and NsPro
You could probably just flash a new baseband and all will be well... Also the RIL needs to match the baseband as well for it to work and come up in about phone, so try downloading get RIL from the play store and see if it detects a non matching RIL (it needs to match the baseband) also it requires root
Sent from my Nexus 4
stewi21 said:
You could probably just flash a new baseband and all will be well... Also the RIL needs to match the baseband as well for it to work and come up in about phone, so try downloading get RIL from the play store and see if it detects a non matching RIL (it needs to match the baseband) also it requires root
Sent from my Nexus 4
Click to expand...
Click to collapse
Hi, thanks for the response,
I downloaded getRIL and gave it superuser permission, and it said my device is unsupported.
Also, what do you mean flash a new baseband? I restored an nandroid backup all the way back from Janurary and that didn't store phone functionality.
Thanks,
Dang... That's a shame, It is probably because the nandroid doesn't backup the modem/baseband, by the fact that you made a nandroid I'm assuming you have a custom recovery?
Sent from my Nexus 4
stewi21 said:
Dang... That's a shame, It is probably because the nandroid doesn't backup the modem/baseband, by the fact that you made a nandroid I'm assuming you have a custom recovery?
Sent from my Nexus 4
Click to expand...
Click to collapse
I have TWRP, I've tried using Odin to flash the stock .tar.md5 file from sammobile, and that didn't work. So I've re-rooted after that and recovered an old backup.
Strangely, I have modem.emmc.win and modem.emmc.win.md5 in the backup directory, but no modem option in TWRP when trying to restore that backup...
well that makes everything a lot easier, dont worry about ODIN, its a pain in the a$$
grab a modem from here http://forum.xda-developers.com/showthread.php?t=2061031 (see if you can find one that matches your ROM, otherwise just try any)
flash it in recovery, clear cache and dalvik and reboot and you should be sweet
stewi21 said:
well that makes everything a lot easier, dont worry about ODIN, its a pain in the a$$
grab a modem from here http://forum.xda-developers.com/showthread.php?t=2061031 (see if you can find one that matches your ROM, otherwise just try any)
flash it in recovery, clear cache and dalvik and reboot and you should be sweet
Click to expand...
Click to collapse
I tried both modems (4.1.1 and 4.1.2) from Wind (GLW) to no avail, it still says Baseband unknown and it still wont recognize any SIM cards...
If I go to a store with an NsPro, will they be able to fix it?
What's an nspro? Also if you don't mind losing your data, flashing a whole stock rom package through Odin should get you going if all else fails
Sent from my Nexus 4
---------- Post added at 09:57 AM ---------- Previous post was at 09:54 AM ----------
You should be able to grab a complete Odin package over on samfirmware
Sent from my Nexus 4
stewi21 said:
What's an nspro? Also if you don't mind losing your data, flashing a whole stock rom package through Odin should get you going if all else fails
Sent from my Nexus 4
---------- Post added at 09:57 AM ---------- Previous post was at 09:54 AM ----------
You should be able to grab a complete Odin package over on samfirmware
Sent from my Nexus 4
Click to expand...
Click to collapse
It's a thing that came up in research that repairs IMEI damage (I think but I'm not sure), in any case I already tried flashing an entire stock ROM (multiple times, 4.1.2 and 4.1.1) through Odin, and it didn't work.
Have you tried different packages, from memory some don't include the baseband and bootloader and stuff like that (It's been a while since my Samsung captivate)
Sent from my Nexus 4
stewi21 said:
Have you tried different packages, from memory some don't include the baseband and bootloader and stuff like that (It's been a while since my Samsung captivate)
Sent from my Nexus 4
Click to expand...
Click to collapse
Yes, I've tried the stock from this post:
http://forum.xda-developers.com/showthread.php?t=2061031
And a rooted version from this post:
http://forum.xda-developers.com/showthread.php?t=1975560
StackUnderflow said:
Yes, I've tried the stock from this post:
http://forum.xda-developers.com/showthread.php?t=2061031
And a rooted version from this post:
http://forum.xda-developers.com/showthread.php?t=1975560
Click to expand...
Click to collapse
At this point if I bring it back to Wind (and by extension, Samsung) I think it's fairly obvious I voided my warranty, but if I pay (not sure how much though), would they be able to fix it?
I'm not sure sorry, because I bought my captivate off XDA and the time I bricked it I had to mail it to adam outler and get it made unbrickable
try downloading an ODIN package from samfirmware and flashing it, because the .zip packages you linked wouldnt flash the modem and RIL. Also GLW is Wind on samfirmware, so just search T889V and choose the newest GLW package, youll need to make an account to download it
stewi21 said:
I'm not sure sorry, because I bought my captivate off XDA and the time I bricked it I had to mail it to adam outler and get it made unbrickable
try downloading an ODIN package from samfirmware and flashing it, because the .zip packages you linked wouldnt flash the modem and RIL. Also GLW is Wind on samfirmware, so just search T889V and choose the newest GLW package, youll need to make an account to download it
Click to expand...
Click to collapse
I already tried that (if you mean http://www.sammobile.com/firmwares/), and I think it's the exact same one as the teshxx download (factory image, exact same size and file name inside the zip, I haven't done an md5sum due to being on Windows),
I reflashed rooted injected stock ROM, did triangle away, and unrooted, and I'll bring it to Wind and see if they will fix it for me tomorrow.
Thanks for your help!
I think I'm actually having the same problems as this guy:
http://forum.xda-developers.com/showthread.php?t=2195869
I also tried QPST, and got the same exception as him...
And by page 4 the 2nd post down, http://forum.xda-developers.com/showthread.php?t=2195869&page=4 he took it to Samsung, and they did some software voodoo to bring it back to life... Fortunately there's a Samsung repair center in my city, and hopefully I'll have the same luck as he did (they aren't open tomorrow though).
One last thing before you do that (lucky you've got a repair centre!) this post says the efs is backed up when you install Cyanogenmod http://forum.xda-developers.com/showthread.php?p=30716302
So you might be able to recover it
Sent from my Nexus 4
stewi21 said:
One last thing before you do that (lucky you've got a repair centre!) this post says the efs is backed up when you install Cyanogenmod http://forum.xda-developers.com/showthread.php?p=30716302
So you might be able to recover it
Sent from my Nexus 4
Click to expand...
Click to collapse
When I restored the old backup (didn't work), I had the efs check box checked in TWRP, and I assume that efs should be in the stock ROM (that's how the OP of that thread did it)
First off I NEVER have had rom issues before this, it all started with a failed encryption attempt that soft bricked my phone. instead of re posting what i wrote here is a link to the 2 pg thread in which i received help and thus this is where i am at.
http://forum.xda-developers.com/showthread.php?t=2701706
OK now ever since then i have never been able to update to a new rom. I believe it let me do it once and i believe i am using an older version of S3Rx.
I believe it may be due to how I updated to 4.3 I would like to get 4.4 as i believe kit kat (tell me if im wrong) will probably be the last android os the S3 will support so i basically want to get the most out of it as i can and also be able to try other roms in general like i used to. Because i currently do not have a sd card I have yet to try anything drastic as i normally use my sd card for backups and rom installs because if something happens to the phone i have the sd card backup.
So in all What should I DO, I have fears of using Odin as the one time it failed on me i bricked a phone and I cant really afford to hard brick this one like i did the other. Although the only thing I can think of being a dumb leach user and non dev. Would be to use odin with the most recent root66 then go from there? Although again lol all i can think of is the above.
Thanks for reading and i hope like the last time I will recieve help to bring back the life to this device. TIA!!
Can you give a little more info on why you can't flash, like an error message or something?
serio22 said:
Can you give a little more info on why you can't flash, like an error message or something?
Click to expand...
Click to collapse
for some reason using twrp and cwm they fail with twrp it normally fails instantly and with cwm it will fail sometime during the install.
I need to put a rom on my phone and ill give exact error. I havce been trying to use the likewise port from att http://forum.xda-developers.com/galaxy-s3-t-mobile/development/rom-likewise-s5-4-1-tw-4-4-2-ne4-t2879647 I normally use an sd card as i have the 12gb model and some roms are large but i should still be able to succeed (we will see from the error message)
thanks for replying
Alright. Also make sure you are using the latest recoveries
serio22 said:
Alright. Also make sure you are using the latest recoveries
Click to expand...
Click to collapse
HRM i guess im ok i just installed the latest S3Rx as i wanted to see what made it stop so i chose this rom (because i needed to update anyway) and it had aroma so I thought perfect ill know when it fails but it worked out ive downloaded and tried to install likewise several time at first i thought i got a bad download but ive tried again and for some reason. I have yet to try a 4.4 (i wanted to try likewise so thats why i chose it) so without trying other roms my issue has something to do with going to 4.4 from 4.3 IDK though as i have not tried other roms but no one else seams to have this issue with this rom port?
Any 4.4 rom suggestion to try to find out what the issue is?
currently installed base-band modem should have no impact on rom installation only the fact i wont get signal right?
I just cant think of any reason why i am having the issue?? any ideas anything i should check to make sure its right on my mobile? BTW thanks for coming back to help as this is possibly a stupidity problem which is hard to help how do you help stupid lol?
Try S3rx 4.4.2 or do you mean aosp/cm?.. And correct, baseband/modem won't matter on ROM installation.. I'm sure it's not stupidity, believe me we all get issues we cannot understand at times and the next time you try, problem is gone lol
serio22 said:
Try S3rx 4.4.2 or do you mean aosp/cm?.. And correct, baseband/modem won't matter on ROM installation.. I'm sure it's not stupidity, believe me we all get issues we cannot understand at times and the next time you try, problem is gone lol
Click to expand...
Click to collapse
i personally prefer touchwiz so no aosp or cm and the latest version of s3Rx i though is what i just installed but its only 4.3 not 4.4
http://forum.xda-developers.com/showthread.php?t=2326763
installing that works but i still cant get to 4.4 im going to search for one that has aroma maybe it will work do you have any suggestions on a good touchwiz based rom on the latest version of android?
To me Likewise looked the best but trying to get that rom working is what prompted this OP.
I still have yet to try again after this recent rom update as I havent had the time and the battery level is not high enough yet to start as i will need to create a new backup and delete my old ones as i have the 12 gb model and currently no sd card.
I will post back when that has been done to show my results. In the mean time ill be searching for another possibly suitable rom like i already said something with aroma and if you have a preference ill try that first.
S3rx 4.4.2 http://forum.xda-developers.com/showthread.php?t=2848080 try that and see if it works
Sent from my SGH-T999 using Tapatalk
serio22 said:
S3rx 4.4.2 http://forum.xda-developers.com/showthread.php?t=2848080 try that and see if it works
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
it wont change my modem? and it will be OK I NEVER have used a rom other than roms made specially for t-mobile i was always under the impression that's a bad idea? I know att and t-mobile are sometimes compatible though but Ive still always been weary so before i do it you want me to use an att rom on my t-mobile?
Anythi8ng special i should know before i do it (besides thew obvious like make a backup and follow op directions) because im not on att i dont want another soft brick (cant afford to have that happen right now either) and a HARD brick would totally mess me up. (i just paid this off lol)
serio22 said:
S3rx 4.4.2 http://forum.xda-developers.com/showthread.php?t=2848080 try that and see if it works
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
it wont change my modem? and it will be OK I NEVER have used a rom other than roms made specially for t-mobile i was always under the impression that's a bad idea? I know att and t-mobile are sometimes compatible though but Ive still always been weary so before i do it you want me to use an att rom on my t-mobile?
Anythi8ng special i should know before i do it (besides thew obvious like make a backup and follow op directions) because im not on att i dont want another soft brick (cant afford to have that happen right now either) and a HARD brick would totally mess me up. (i just paid this off lol)
EDIT:
AT&T I747 users should update bootloaders and modem to NE4 http://forum.xda-developers.com/gala...pdate-t2808654 I747M and T999 users need to be on 4.3 firmware or ROM will not boot.
Click to expand...
Click to collapse
after reading this it makes me for comfortable so ill try it out Im currently on S3Rx 4.3 so wish me luck I sure hope it works!!
Edit: well I tried it it installed fine but the screen would not display i could feel the phone vibrate as to start up although like i said no boot screen no Samsung loading screen basically yeah I'm having problems with 4.4.X
You don't need to change anything and it won't change your modem, you just need to be on 4.3 firmware
serio22 said:
You don't need to change anything and it won't change your modem, you just need to be on 4.3 firmware
Click to expand...
Click to collapse
ill try again but the rom you said to try installed fine no problems but after restart no display????? it vibrated so IDK if it even booted. I am really confused I have never had problems like this. Especially with this phone as it has been easy from the start not the case with other devices i have used.
So ill try again maybe a reboot will get it working IDK but i guess ill try it again cross your fingers
BeatnikBandit said:
ill try again but the rom you said to try installed fine no problems but after restart no display????? it vibrated so IDK if it even booted. I am really confused I have never had problems like this. Especially with this phone as it has been easy from the start not the case with other devices i have used.
So ill try again maybe a reboot will get it working IDK but i guess ill try it again cross your fingers
Click to expand...
Click to collapse
That means you are not on 4.3 firmware, so update your firmware and try again
serio22 said:
That means you are not on 4.3 firmware, so update your firmware and try again
Click to expand...
Click to collapse
my phone says its 4.3 but like you said it must be an issue how do i update my firmware again?
BeatnikBandit said:
my phone says its 4.3 but like you said it must be an issue how do i update my firmware again?
Click to expand...
Click to collapse
You could be on a 4.3 ROM, but have a 4.1.x bootloader.. Download latest 4.3 firmware for your device and flash it with Odin
So yes i must be on 4.1.2 as that was the last time i flashed with odin so i believe you help3ed me with my main isssue now this is something i would like to be sure of:
Can i simply flash the following posted on the s3rx page or will i have to use odin i prefer not to as well i don't know much about it and it scares me as idk how to if possible backup in case of error as the only unfixed problem i have ever had was a while rooting a galaxy s 4g (the one that came with inception) and i walked away and the cord was unplugged and there was an error that it still has about firmware upgrade failure connect to kies and neither kies nor odin will connect to it so its currently in the same situation. So i am fearful of using odin unless it must be done.
Complete 4.3 T999, T999L and T999V bootloader and modem packages.
After flashing DO NOT try to install any older bootloaders or use any other odin.tar other then the latest 4.3 or you will brick your phone.
T999 ONLY, T999 ONLY, T999 Only
T999 ONLY, T999 ONLY, T999 Only
Complete MJC bootloader and modem
http://www.mediafire.com/download/5c..._modem_4.3.zip
Complete NC2 bootloader and modem *Added 3-22-14* Thanks to @Synthetic.Nightmare
http://www.mediafire.com/download/fc..._modem_4.3.zip
Click to expand...
Click to collapse
Would this be enough (would probably use NC2) or will i be better of using the latest root66 with odin? and if so can you give me some tips on odin usage as i would get the latest odin and the latest root66 rom and flash it hoping it works I would try to learn more also but yeah.
It's better to flash the full firmware with Odin imo, but it should be fine. And yes, use nc2
So i think the best cleanest way is to use odin although i have a few questions
First the latest version of odin should work right so 3.09 or 3.10?
Can a backup before this? is there a way to do it?
Lastly the best rom to flash is root 66 NC2 fot t999
Then i will be on a 4.3 bootloader and will be able to use 4.3+ roms?
I have the drivers the latest odin and the root66 image can you direct me on how to do it as a refresher?
I appreciate all your help!!
Please go to Android development an look at [baseband] an just go to first page should help with everything
I believe the root66 thread has instructions