looking 100% safe unlock method via efs for galaxy europa and yas used boards but has anyone unlocked one recently without bricking phone
serialkillazzs said:
looking 100% safe unlock method via efs for galaxy europa and yas used boards but has anyone unlocked one recently without bricking phone
Click to expand...
Click to collapse
I've just unlocked mine by using the instructions in this thread: http://forum.xda-developers.com/showpost.php?p=12099386&postcount=6
I also just used the method posted above http://forum.xda-developers.com/showpost.php?p=12099386&postcount=6 and it worked.
100% safe? I'm not sure if it is.. I made sure I knew where my receipt was before trying just in case I screwed it up and had to take it back for warranty
EDIT:JUST TRIED TO DO IT ON MY BF'S PHONE
pretty sure I did the exact same instructions, but something must have went wrong, now his phone has no baseband no imei no service, sound doesn't work, won't factory reset or turn off. OOPS!
um I guess I'm screwed then -_-
fix for missing IMEI
I (stupidly) didn't make a backup of stl5 before attempting to get the unlock code from efs/mits/perso.txt and ended up with a phone that would boot correctly but had lost IMEI, wifi, BT, and kept rebooting every 5-10 minutes
How I managed to fix it:
Rooted the phone with Universal Androot
Battery pulled the phone and then booted
Connected with adb shell
-su
# dd if=/dev/block/stl5 of=/sdcard/stl5.rfs
# dd if=/sdcard/stl5.rfs of=/dev/block/stl5
# reboot
Waited a few minutes, then battery pulled again. When the phone booted, my IMEI, wifi and BT were all back again.
Massive thanks to posts by BlocK240 (http://forum.xda-developers.com/showpost.php?p=12187545&postcount=20) and FDAD (http://forum.xda-developers.com/showpost.php?p=12172648&postcount=1900) which I based this fix on
I hope this helps someone else whose i5500 got bricked in this way. Of course, I accept no responsibility if your phone gets even more fscked.
chancooluk said:
I've just unlocked mine by using the instructions in this thread: http://forum.xda-developers.com/showpost.php?p=12099386&postcount=6
Click to expand...
Click to collapse
hi there,
i'm just wondering how did you find the unlocking code? the link above just says that the guy finally done it. i'm new to all this, please if you can help me how to find the unlocking code on my galaxy europa. i have rooted phone and i have terminal installed. do i write word to word code on the terminal interface? how do we do it? please help me.
thanks.
Bricked my i5500
No it bricked mine
hello to all
well my problem is the same as many people...
I brick my i5500... its flash samsung on screen and turn off all time
when I put him in download mode and flash again whit Odin Downloader nothing hapens....only the same story...
please help...it must be some way to put it in work again but i cant find on forum
thanks in advance .....
Unfortunately this method too bricked my Europa and following slickandy's instructions I was still unable to fix the missing IMEI number. I had to return it to the original store and they luckily gave me a new one, I think I'll just purchase an unlock code from my service provider.
I, too, tried the "safe" method on a standard i5500. I'm somewhat familiar with Linux(everyday user for over a decade now), so figured no harm could come from just mounting and reading stl5.
How wrong I was. Lose IMEI, no phone connection, refused to shutdown(would restart after a few seconds with corrupt date and time).
This was a standard, unmolested phone, aside from the suggested method of root. No badly typed commands, just everything in the guide.
Don't do it. Codes are available for £9 on eBay. It's cheaper and safer to go down that route.
Dont use the stl5 method. Too risky.
Use the new bml5 method. That is 100% safe.
http://forum.xda-developers.com/showpost.php?p=17148825&postcount=334
Author of the OP should mention the bml5 method now to prevent unnecessary bricking.
Cheers
slickandy said:
I (stupidly) didn't make a backup of stl5 before attempting to get the unlock code from efs/mits/perso.txt and ended up with a phone that would boot correctly but had lost IMEI, wifi, BT, and kept rebooting every 5-10 minutes
How I managed to fix it:
Rooted the phone with Universal Androot
Battery pulled the phone and then booted
Connected with adb shell
-su
# dd if=/dev/block/stl5 of=/sdcard/stl5.rfs
# dd if=/sdcard/stl5.rfs of=/dev/block/stl5
# reboot
Waited a few minutes, then battery pulled again. When the phone booted, my IMEI, wifi and BT were all back again.
Massive thanks to posts by BlocK240 (http://forum.xda-developers.com/showpost.php?p=12187545&postcount=20) and FDAD (http://forum.xda-developers.com/showpost.php?p=12172648&postcount=1900) which I based this fix on
I hope this helps someone else whose i5500 got bricked in this way. Of course, I accept no responsibility if your phone gets even more fscked.
Click to expand...
Click to collapse
Hi, it happenned something similar to me. I got the unlock number, but when I rebooted the phone, it did not ask for it but the phone was actually unlockedl. However the IMEI was lost (all zeros). Fortunately I did not lose any connectivity, everything looks OK but IMEI is still zeros.
Now I doubt whether to test your method or not. Is it safe? I really would like to recover my IMEI to avoid future problems, but I would not like to brick a phone that actully works...
Thanks for sharing your results!
Related
Hello,
I reciently rooted my samsung galaxy s2. I tried a few roms so i could get used to the system or restoring etc. However i encountered a problem whilst having a peek at an alpha jellybean rom, where i noticed that my CWM app on the phone had vanished? I attempted the restore using the 3 button combo and found that i kept recieveing E: can't mount/ E: can't cache messages whilst on the restore screen. i could find my latest restore on my sd card however it wouldnt restore. I believe the CWM was removed from my phone which caused it to not work. I was then stuck in a bootloop. no matter what i done, boot to a stock rom via odin, try the different CF roms i and try to put CWM back on to the phone? I read a post on here from someone who had the same problem, who was told it looked as though there is a problem with the partitions. i followed a tutorial and used odin to put Latona 20110114.pit on the phone. it said i would get a blank screen once this has done and i needed to remove then place the battery back in the phone then put it into download again. This didnt happen!! I done as instructed and now my phone wont go into recovery mode, download mode or even boot loop. I fear i have completely bricked my phone so i am trying to use oneclick heimdall to sort it however my PC keeps saying i need admin rights to install it which i have.
Can someone please help me out. I am new to this so please go easy on me.
many thanks
If you have no signs of life from the phone, it's probably cactus.
You might as well try a jig (but unlikely to work; still try one tho). Only option is service centre & hope they can't tell/don't care you've been messing with it & fix it under warranty or JTAG repair by a 3rd party repairer, at your cost obviously; will be cheaper than having Samsung/an authorised repairer fix it if they refuse warranty service which they're quite within their rights to do.
edinsam said:
i followed a tutorial and used odin to put Latona 20110114.pit on the phone.
Click to expand...
Click to collapse
First result of searching suggests that's meant for the I9003. Good job.
HA
Hello,
Awe well then. never mind eh, whats done is done! Its totally bricked so i thought i would chance my luck by sending it back to O2 for repair. I was reading the only other way to get the phone running again was to take it to bits and hook it up for some stock flashing. so heres hopping they sort it!
lesson learnt!!!
I know there are lots of posts about bicks, but after a week searching I could not find any fix for my problem.
I have a S-Off, rooted GSM Evo 3D running Yoda ICS ROM and 4ext Recovery. One day, I was charging it when it hung, I restarted the phone, but it went directly to the bootloader (I didn't touch anything), as I was unaware of what was happening, I simply power it off (using the menu option), when I tried to power it on again, I got no success, only a dim red light appeared, and it is this way eversince.. I cannot power it on, go to the bootloader or anything, the computer recognizes it as QSUSB-DLOAD but there is no partition on it (I tried both Linux and Windows). I tried some unbricking methods without success. I am in Brazil, I tried to call HTC but they said I have to send the device to the origin country (mine is from Rogers, I believe it is Canada), but I don't even know where to send and I'd prefer to fix it by myself if possible. I am open to suggestions anyone could help?
Thanks a Lot!!
AW: [Q] Hard Brick evo 3D
Does adb detect the device?
In that case you could try to run a ruu...
If he can get it into recovery mode then yes. Most of the time its usually something that the end user has done to make it get bricked. I am not saying he actually did something. We also don't know what he has done with his . Phone changing your cid is a good way to brick it. Pulling the battery during a ruu update, flashing a CDMA firmware etc things like that are guaranteed brick makers. However there's only one solution I know of should you not be able to boot into recovery. Try and Google up JTAG. I'm fuzzy on the details about how it works but it can restore your hboot. If you know somebody that knows how to do it, that's your best shot. Otherwise, you will have to send it into HTC Canada or you could try to buy the JTAG hardware and learn how to use it to restore your phone. If anybody has a solution for him please feel free to chime in. Sorry about your phone though. I wish you the best of luck on getting it restored.
Quantenhall said:
Does adb detect the device?
In that case you could try to run a ruu...
Click to expand...
Click to collapse
No, it does not detect the phone. I was searching more thoroughly and found some places here in Brazil that do jtag repairs, I think I will give it a shot.
Thanks!
RonaldoPA said:
No, it does not detect the phone. I was searching more thoroughly and found some places here in Brazil that do jtag repairs, I think I will give it a shot.
Thanks!
Click to expand...
Click to collapse
Just to let you guys know, I did the jtag repair and it worked for about a week, I put back my cfw and yesterday, out of nothing it stopped work again. It was working normally, I left it on the table, checked the time and went do other things, later (about 2 hours) I took the phone to set the alarm for the next day and it didn't turn on...
If someone has any ideas, I appreciate!
Thanks in advance.
RonaldoPA said:
Just to let you guys know, I did the jtag repair and it worked for about a week, I put back my cfw and yesterday, out of nothing it stopped work again. It was working normally, I left it on the table, checked the time and went do other things, later (about 2 hours) I took the phone to set the alarm for the next day and it didn't turn on...
If someone has any ideas, I appreciate!
Thanks in advance.
Click to expand...
Click to collapse
Try using this to unbrick the phone (aimed specifically for DLOAD error, but has worked for other cases): http://forum.xda-developers.com/showthread.php?t=1522351. Afterward, use a combination of both the official instructions from Unlimited.io and this video tutorial to achieve S-OFF. The instructions give you an idea of how-to, the video actually gives you a better sense for the timing. The timing is very specific that needs to be done just right (might take quite a few times to get it done).
If you have an HTC Evo V 4G with Virgin Mobile USA, then you can use this flashable RUU to return to stock (I extracted this from the RUU.exe; just ensure that your bootloader is LOCKED. You can check this by Holding Pwr+Vol Down during boot; top of the screen should say LOCKED). If your phone skips loading into your bootloader and boots into the main OS, pull the battery to bypass quickboot (or turn it off in the settings). To flash the RUU, move the file to the root of your SD card, boot into bootloader, and follow the directions on screen.
brick evo 3d
when i update mwakiousSGS2rom_v.3.0.03 to my evo 3d . this is my bi mistake .and after that my mobile is of ..so pls what can i do .help me
(Mods, sorry if I am creating a new thread of something that is already established but I couldn't really figure it out)
So I have a t-mobile vibrant running 2.2 which was previously running 4.2.1 rooted... recently the phone just turned off at night when I was sleeping and then next thing you know it doesn't make calls or sends texts and gives me notification that it is unable to connect to the network. I Tried to troubleshooting is several different ways and nothing worked out but finally figured it out that the IMEI number was messed up and it had reset it self to Dev IMEI and obviously that didn't match the IMEI that is in the back of the phone.
So after extensive research on how to fix it I just ended up taking a chance by unrooting and returning to stock and thankful it saved my phone.
The real questions, before I rooted the phone I didn't know that once I root the phone I was supposed to back up the /efs folder so in case the above mentioned scenario was to occur. Now if someone can please help me, before I root the phone again, what are the steps I should take to assure that I don't run into a similar problem again and if I do run into that problem what resources should be backed up so I can resolve the issue without much pain.
I would truly appreciate all you help.
Thanks.
NSingh95 said:
(Mods, sorry if I am creating a new thread of something that is already established but I couldn't really figure it out)
So I have a t-mobile vibrant running 2.2 which was previously running 4.2.1 rooted... recently the phone just turned off at night when I was sleeping and then next thing you know it doesn't make calls or sends texts and gives me notification that it is unable to connect to the network. I Tried to troubleshooting is several different ways and nothing worked out but finally figured it out that the IMEI number was messed up and it had reset it self to Dev IMEI and obviously that didn't match the IMEI that is in the back of the phone.
So after extensive research on how to fix it I just ended up taking a chance by unrooting and returning to stock and thankful it saved my phone.
The real questions, before I rooted the phone I didn't know that once I root the phone I was supposed to back up the /efs folder so in case the above mentioned scenario was to occur. Now if someone can please help me, before I root the phone again, what are the steps I should take to assure that I don't run into a similar problem again and if I do run into that problem what resources should be backed up so I can resolve the issue without much pain.
I would truly appreciate all you help.
Thanks.
Click to expand...
Click to collapse
I've never heard of having to backup the /efs folder after rooting...has anyone else?
I've rooted and unrooted my device a-helluva-lotta times and I've not only never had this problem, but I've never backed up
my /efs folder afterwards.
Hi All,
I thought I’d share this as I’ve been pulling my hair out with trying to find answers to this, and sending it to old Sammy was the next option.
After trying everything on every forum, trying the QPST method, trying to use someone else's efs folder (which changed the serial as well) and every other complicated as hell method everyone had suggested, nothing worked expect his which I’ve not found mentioned anywhere as a solution to this (or any other) problem
In the Samsung Kies application under "Tools" there is "Firmware Upgrade and Initialisation,"
With your device unplugged (it will say not available for this model if its plugged in, don't plug it in until it tells you to when in download mode) select this and run the what it tells you to do,
After this is finished you will have a completely fresh install of the latest officially released firmware (for your original build eg. carrier branded) with original serial number and imei number :laugh:
It’s really silly how simple this is yet has not been mentioned or attempted by anyone else, or if it has, not mentioned by anyone else.
I crap you not…
Thanks,
[edit:] just as a note, I got into this problem by not backing up the efs, the world would be a much nicer place if everyone just backed up their efs :laugh:
This has been posted before and does not work in many cases .
Although the method can be useful to restore to original firmware .
jje
Yes, flashing a stock rom will sometimes fix the problem of the efs folder not being mounted or read. It won't fix a corrupt partition or damaged files.
The stock rom you flashed didn't contain any efs data so it isn't any substitute for a backup, you were very lucky it worked.
To my tests this work only when efs is completely empty while upgrade if not it doesn't work
sent from the state where Marijuana is NOT illegal !
Same problem
hello guys,
Well I'm to tell the story of how my aunt damaged apparently her phone
At first the phone is a samsung galaxy S3 from movistar (locked), and she bought a freaking iphone 5 to give the S3 to his husband and there it starts the problem he's in another company so she goes to a store to unlock the phone, the guys on the store supposedly unlocked the phone. So when she arrives home, she puts the sim into the phone and SORPRISE it says emergency calls only and not registered in network. After a week she calls me and hands me over the phone.
My surprise was when I put it in recovery mode, it says flash count 3, and then i did all these terrible things with thephone.
1) Flash it to a stock movistar rom 4.1.2.
2) Sorprise the IMEI sayd null.
3) Searching in the web, found the ariza patch, and I patched it without saving the efs (big mistake).
4) The phone imei's became 0049.
5) So I flash it back to the rom they put in the store and the imei went back I make sure it was the one on the back of the phone.
6) I still stuck in the emergency call not registered in the network thing.
7) Now I rooted the phone erased the whole content of the efs directory (this time with a back up).
8) Did the tutorial thing with samsung kies and I'm back with the movistar rom with the 0049 IMEI.
I don't what to do at this point besides going to samsung and send it to repair I really hope they can fix it at a low price.
Sorry for my english, I'm trying to improve it.
Best Regards
Andy Serrato... the spaniard
Start by reading the stickied faqs and guides EFS/IMEI sticky for one or just pay for a repair .
Galaxy S3(GT-I9300) having the same problem! HELP HELP HEEEELP PLEASE!!
Very unfortunately. this didn't solve my problem, the phone's Serial number is still that auto generated junk, and the EMEI is 00499901640000 as before. I had 4.1.2 on my S3 and Kies has updated it to 4.3 without resolving the issue!
can anyone give an idea on how to surely resolve this issue please. its about 3 months now ever since my phone got screwed up!
Pay for a repair
Perfect
I cannot believe this worked, but it did.
I messed up somehow by trying to flash the wrong cwm.tar file (for i9305) I needed i9300 of course and odin stopped halfway and got stuck, i then pulled the cable out and everything got very messy,.. i kept getting lots of errors etc. i somehow managed to install an old cm11 rom which worked lovely. BUT I had no baseband, no imei, no network, no number, nothing, #*06# or whatever it is, wouldn't work. nothing.
I then started to figure out how the efs filesystem worked, then foundout kies has an emergency thing where i guess they look into there database what your imei was when the phone was built. this would not work because I was using a custom rom (i think) but then I stumbled upon this post. thank goodness!!!!!
It's just restarted and internet, signal, imei is back, baseband version is back. all in order.
however, i think i was also very lucky, but for those of you who are in the position i was in, but this doesn't work, I do think there are ways to get an old efs going again and modify it to your "should be" imei,
if anyone needs an IMEI, I can give you one from a phone i had stolen in vietnam, (not sure its even legal to give it out but whatever)
thank you
Nev
EFS recovery
DonkeyDuck said:
Hi All,
I thought I’d share this as I’ve been pulling my hair out with trying to find answers to this, and sending it to old Sammy was the next option.
After trying everything on every forum, trying the QPST method, trying to use someone else's efs folder (which changed the serial as well) and every other complicated as hell method everyone had suggested, nothing worked expect his which I’ve not found mentioned anywhere as a solution to this (or any other) problem
In the Samsung Kies application under "Tools" there is "Firmware Upgrade and Initialisation,"
With your device unplugged (it will say not available for this model if its plugged in, don't plug it in until it tells you to when in download mode) select this and run the what it tells you to do,
After this is finished you will have a completely fresh install of the latest officially released firmware (for your original build eg. carrier branded) with original serial number and imei number :laugh:
It’s really silly how simple this is yet has not been mentioned or attempted by anyone else, or if it has, not mentioned by anyone else.
I crap you not…
Thanks,
[edit:] just as a note, I got into this problem by not backing up the efs, the world would be a much nicer place if everyone just backed up their efs :laugh:
Click to expand...
Click to collapse
WOW! This worked! I had been struggling for 3 months with my Note 2. Been flashing rom after rom and got stuck in boot cycle. Actually broke down and brought phone to a cell repair shop. She said it just needed a new battery. $50 later got my phone back. She had put stock AT&T rom on it but lo and behold, my sim card didn't work and my IMEI was null. I brought it back and she had it for a week and then said there was a hardware problem AND my USB port wasn't working and it would cost more to fix than it was worth, so she gave it back to me no charge. So I spent next months trying other roms. reading up on EFS folder, even learned some ADB stuff. To no avail. And BTW, my usb port seems to work fine. Finally this afternoon after Turkey Dinner, I stumbled across your forum message. And 15 minutes later I was downloading a repair and the son of a gun fixed everything. I verified it with a Sim card - perfect ! Apparently Samsung has a database of phone serial numbers and what IMEI code goes with them. Fanatastic! Thank you. I will be writing a serious neg review of that cell phone repair place soon.
kangerX said:
To my tests this work only when efs is completely empty while upgrade if not it doesn't work
sent from the state where Marijuana is NOT illegal !
Click to expand...
Click to collapse
I have tried the method posted in the thread ..... but EFS didn't recovered ........ so i decided to follow your procedure
like making empty EFS folder.... so how can i do that ...and if so will it work .....as someone here mentioned that Download firmware package doesn't contains any EFS contains .... help me out :good:
DonkeyDuck said:
Hi All,
I thought I’d share this as I’ve been pulling my hair out with trying to find answers to this, and sending it to old Sammy was the next option.
After trying everything on every forum, trying the QPST method, trying to use someone else's efs folder (which changed the serial as well) and every other complicated as hell method everyone had suggested, nothing worked expect his which I’ve not found mentioned anywhere as a solution to this (or any other) problem
In the Samsung Kies application under "Tools" there is "Firmware Upgrade and Initialisation,"
With your device unplugged (it will say not available for this model if its plugged in, don't plug it in until it tells you to when in download mode) select this and run the what it tells you to do,
After this is finished you will have a completely fresh install of the latest officially released firmware (for your original build eg. carrier branded) with original serial number and imei number :laugh:
It’s really silly how simple this is yet has not been mentioned or attempted by anyone else, or if it has, not mentioned by anyone else.
I crap you not…
Thanks,
[edit:] just as a note, I got into this problem by not backing up the efs, the world would be a much nicer place if everyone just backed up their efs :laugh:
Click to expand...
Click to collapse
i love u so much right now,.. worked like a charm,.. and after thjat i was able to unlock my phone,... thanks so much i would love to give u 10000 thanks
I cant get past entering my model number,, I read it right from under the battery and it still keeps telling me to enter the model number. G550T1 doesnt change from G550T1 no matter how many times you type it... I give up.. If I could just get a twrp backup for mine I may be able to fix it. It's metropcs! flashing to the T-Mobile twrp backup by mistake thinking it was the metropcs one is what got me in this situation... Should have paid better attention...
UPDATE: It took my numbers and I'm trying it now, wish me luck
Well I got it to take my model number and did the whole software thing. Everything is all back to stock but it didnt fix the problem.. Still no net work and says theres no sim card.
Which shop samsung
Which shop samsung or repair shop bro.
Please tell.?????? me I am facing too problem.
stwischu said:
WOW! This worked! I had been struggling for 3 months with my Note 2. Been flashing rom after rom and got stuck in boot cycle. Actually broke down and brought phone to a cell repair shop. She said it just needed a new battery. $50 later got my phone back. She had put stock AT&T rom on it but lo and behold, my sim card didn't work and my IMEI was null. I brought it back and she had it for a week and then said there was a hardware problem AND my USB port wasn't working and it would cost more to fix than it was worth, so she gave it back to me no charge. So I spent next months trying other roms. reading up on EFS folder, even learned some ADB stuff. To no avail. And BTW, my usb port seems to work fine. Finally this afternoon after Turkey Dinner, I stumbled across your forum message. And 15 minutes later I was downloading a repair and the son of a gun fixed everything. I verified it with a Sim card - perfect ! Apparently Samsung has a database of phone serial numbers and what IMEI code goes with them. Fanatastic! Thank you. I will be writing a serious neg review of that cell phone repair place soon.
Click to expand...
Click to collapse
Right I'm really sorry to have to burden all you lovely helpful people with this, as I know there's dozens of threads, of which I have sifted and sifted through for the past 2 days. Most of them have been helpful and I am now 95% fixed, but here is the down low:
Mid-last week, I finally decided to stick a custom rom on my old, laggy Galaxy S3. Up until this point I had been running on stock 4.1.2 Firmware, rooted, with things like Bloatfree cleaning the device up a bit.
I did some research and landed on the latest Paranoid Android build, based on 4.4.4. All was rosey for a little under a week with no problems whatsoever until this Monday afternoon. I was doing nothing other than opening Snapchat when my S3 turned itself off, only to get stuck on the bootscreen.
It took me all day yesterday just to get the thing to boot again, I must of tried 4 different stock roms, searching for ages to find CWM that would flash via Odin and any fix just to get it past boot. After finally getting it into Recovery it kindly let me know that "E:Failed to Mount /EFS".
Since that happened I have managed to get the phone booted up into a stock 4.3 rom, exited factory mode and got it rooted with busy box and terminal. It has become a WiFi-only Tablet, essentially.
I am at the last hurdle, where I have no network connectivity and my IMEI is wrong. I of course have my correct IMEI on the back of the phone which I wish to reintroduce to the phone. I do not have an EFS backup.
TL;DR
Phone on Stock 4.3 ROM SGS3INT-XXUGMK6-BTU-20131216, rooted with busy box, root explorer and terminal. Always had stock kernel.
IMEI incorrect, with no backup of EFS.
I have tried:
EFS Professional - EFS Format errors on mount read/write
NVitems_reader_writer, though I can not get my device to stay in RMNET + DM + MODEM mode to be able to connect via COM port as a serial device.
A few of the other simpler methods from the forums
Any help is much appreciated, and while I have read that modifying the IMEI number is frowned upon and illegal practice, I am simply trying to restore it to it's original state, no tom foolery here.
Regards
Dan
Take it to a repair centre, they can recode it for a small charge. Make sure it works on 4.3 before you pay them.
boomboomer said:
Take it to a repair centre, they can recode it for a small charge. Make sure it works on 4.3 before you pay them.
Click to expand...
Click to collapse
Unfortunately I have tried that with every local shop, and they don't seem to think they can do anything about it, and there is no other official Samsung repair centres nearby! Seems like a problem that independents don't come across too often.
On the methods you've tried you've stated this "A few of the other simpler methods from the forums",
Does this mean you tried flashing the latest modem.bin for your device through Odin or through the recovery?
Saad_ said:
On the methods you've tried you've stated this "A few of the other simpler methods from the forums",
Does this mean you tried flashing the latest modem.bin for your device through Odin or through the recovery?
Click to expand...
Click to collapse
I have tried flashing an XXEMG4 modem onto it and unfortunately hasn't made any difference. My IMEI is currently posted as one of the generic 0049 numbers when *#06# is dialed.
As far as I can tell, my best bet would be finding a way to get the serial port working through NVitem_reader_writer, as I have generated my correct IMEI file to add to the phone, but it won't successfully switch to RMNET + DM + MODEM to be able to connect to my computer in that way!
Dan
D4 BCK said:
I have tried flashing an XXEMG4 modem onto it and unfortunately hasn't made any difference. My IMEI is currently posted as one of the generic 0049 numbers when *#06# is dialed.
As far as I can tell, my best bet would be finding a way to get the serial port working through NVitem_reader_writer, as I have generated my correct IMEI file to add to the phone, but it won't successfully switch to RMNET + DM + MODEM to be able to connect to my computer in that way!
Dan
Click to expand...
Click to collapse
Is there a driver I could be missing for it to connect as a USB modem instead of a serial port when trying this?
Dan
I have a similar problem, efs restored, imei is showing right but cant get any signal, saying emergency calls only. After flashing stock.
Well, after 3 different phone shops and 2 gruelling weeks, the phone is back in action.
I gave very detailed notes on everything I did to the 3rd guy and he eventually managed to get it working again for a nice £15.
I'm unsure if he did anything else, but for anyone who ends up with this problem in the future, rolling the latest stock ROM will not always work. My phone was successfully recovered by rolling back all the way to 4.0.4. I'm sorry I can't give more information as I've already rooted and stuck SlimROM on it to get it back to how I like it, though this time I have been clever enough to actually create a proper full nandroid backup. I had done a backup before, but in my relative noobness years ago it was not a full backup.
D4 BCK said:
Well, after 3 different phone shops and 2 gruelling weeks, the phone is back in action.
I gave very detailed notes on everything I did to the 3rd guy and he eventually managed to get it working again for a nice £15.
I'm unsure if he did anything else, but for anyone who ends up with this problem in the future, rolling the latest stock ROM will not always work. My phone was successfully recovered by rolling back all the way to 4.0.4. I'm sorry I can't give more information as I've already rooted and stuck SlimROM on it to get it back to how I like it, though this time I have been clever enough to actually create a proper full nandroid backup. I had done a backup before, but in my relative noobness years ago it was not a full backup.
Click to expand...
Click to collapse
A nandroid does not back up the efs unless you are using philz or twrp and you specifically tell it to. There is no way in CWM.
Not sure if you new that or not since you said a full backup but just thought I would pipe in just incase so you don't have troubles next time.
D4 BCK said:
Well, after 3 different phone shops and 2 gruelling weeks, the phone is back in action.
I gave very detailed notes on everything I did to the 3rd guy and he eventually managed to get it working again for a nice £15.
I'm unsure if he did anything else, but for anyone who ends up with this problem in the future, rolling the latest stock ROM will not always work. My phone was successfully recovered by rolling back all the way to 4.0.4. I'm sorry I can't give more information as I've already rooted and stuck SlimROM on it to get it back to how I like it, though this time I have been clever enough to actually create a proper full nandroid backup. I had done a backup before, but in my relative noobness years ago it was not a full backup.
Click to expand...
Click to collapse
hey, i have this similar problem right now. So, what i have to do is rolling back all the way to 4.0.4? will it work? but i haven't coded the right IMEI.. do i have to? btw when you have that failed to mount efs, did you use the tutorial that uses adb shell and mke2fs?
D4 BCK said:
I have tried flashing an XXEMG4 modem onto it and unfortunately hasn't made any difference. My IMEI is currently posted as one of the generic 0049 numbers when *#06# is dialed.
As far as I can tell, my best bet would be finding a way to get the serial port working through NVitem_reader_writer, as I have generated my correct IMEI file to add to the phone, but it won't successfully switch to RMNET + DM + MODEM to be able to connect to my computer in that way!
Dan
Click to expand...
Click to collapse
Hi everybody,
I am trying the same, changing imei by using nv items reader. I have the problem that i got a phone from a friend that has a 0049 IMEI, I dont know what he or someone else did to that phone to kill the imei.
The phone: Galaxy S3 I9300
Buildnumber: JSS15J.I9300XXUGNG3 (Android 4.3)
Baseband: I9300XXUGNA8
Rooted with Odin using CF-Auto-Root-m0-m0xx-gti9300
I am stuck at the same part, i cant get the phone in rmnet + dm + modem mode. what I did is: *#0808# - tip "RMNET + DM + MODEM" - tip "OK" - it says "8 saved!" (but it is not saved, when i go into the *#0808# it switched back to MTP)
When i do this when the phone is connected to my computer there is an unplug sound and a plug sound. So I think the phone tries to get in RMNET + DM + MODEM mode but it does not get it. I can activate all other Modes shown in this menu, only the one i need does not get activated.
What can I do to access this mode?
Thanks for your help in advance.
vuli111 said:
Hi everybody,
I am trying the same, changing imei by using nv items reader. I have the problem that i got a phone from a friend that has a 0049 IMEI, I dont know what he or someone else did to that phone to kill the imei.
The phone: Galaxy S3 I9300
Buildnumber: JSS15J.I9300XXUGNG3 (Android 4.3)
Baseband: I9300XXUGNA8
Rooted with Odin using CF-Auto-Root-m0-m0xx-gti9300
I am stuck at the same part, i cant get the phone in rmnet + dm + modem mode. what I did is: *#0808# - tip "RMNET + DM + MODEM" - tip "OK" - it says "8 saved!" (but it is not saved, when i go into the *#0808# it switched back to MTP)
When i do this when the phone is connected to my computer there is an unplug sound and a plug sound. So I think the phone tries to get in RMNET + DM + MODEM mode but it does not get it. I can activate all other Modes shown in this menu, only the one i need does not get activated.
What can I do to access this mode?
Thanks for your help in advance.
Click to expand...
Click to collapse
Discussion is against the rules, and also illegal.
Changing to rmnet + dm + modem Mode is illegal?
Changing imei, which what your post stated, is illegal -don't ask for help here.
Take it to a repair centre and pay them to restore your efs folder.
I did not ask for help to change the imei.
I asked for help to get in the rmnet mode. Is this illegal too??