SM-G920I wrong model number (SM-G925F) - Galaxy S6 Q&A, Help & Troubleshooting

Hi everyone.
I've been reading this forum since a long time ago, until I finally decided to register a couple days ago, so I'm new here. (Hello world).
Please forgive me for my bad english, but it's not my native language. I'm from México.
I have an issue with my S6 (flat). The thing is that I've flashed succesfully (I think) a custom rom a few hours ago and I'm still testing it. Everything looks fine so far except for one weird issue that I haven't find to be disturbing no one but me even through I've searched for it, just one guy who reported this to be happen on a S3.
The problem is that me model number has changed to one from a S6 Edge, mine was SM-G920I and suddendly changed (after the flash) to SM-G925F.
The guy that posted this issue on its S3 said that you can modify its model number by rewritting its code with Root Explorer, but I dunno if this solution also applies to my case.
If someone can help me, I'd be very thankful.
Regards.

Don't worry about it. The custom ROM you installed was based on the edge firmware that's why.
I am using Back to N0t3 ROM and so my model number is now that of the Note 5.
If it worries you then you can edit the build prop entry "ro.product.model" and change it back.

Obagleyfreer said:
Don't worry about it. The custom ROM you installed was based on the edge firmware that's why.
I am using Back to N0t3 ROM and so my model number is now that of the Note 5.
If it worries you then you can edit the build prop entry "ro.product.model" and change it back.
Click to expand...
Click to collapse
Thanks a lot for your reply.
I was planning 'bout reflashing my rom, thinking that maybe something went wrong in the process, and I was stuck waiting for someone to answer my cuestion to move on installing apps etc. but now that I know that there's nothing to worry about, I can continue modding.
Can you please explain me the route to find the entry to change the model number? I know there's nothing to worry about, but I'm a little perfectionist hehe.
Regards from México.

Gallitho said:
Thanks a lot for your reply.
I was planning 'bout reflashing my rom, thinking that maybe something went wrong in the process, and I was stuck waiting for someone to answer my cuestion to move on installing apps etc. but now that I know that there's nothing to worry about, I can continue modding.
Can you please explain me the route to find the entry to change the model number? I know there's nothing to worry about, but I'm a little perfectionist hehe.
Regards from México.
Click to expand...
Click to collapse
Use a text editor or Root Explorer.
Navigate to /system and edit the build.prop file point said earlier and reboot. Make sure you dont edit anything else and don't make typos, else you can have an issue with booting (which can be so solved by putting back the original build.prop or reflashing the ROM).

davebugyi said:
Use a text editor or Root Explorer.
Navigate to /system and edit the build.prop file point said earlier and reboot. Make sure you dont edit anything else and don't make typos, else you can have an issue with booting (which can be so solved by putting back the original build.prop or reflashing the ROM).
Click to expand...
Click to collapse
Thanks a lot pal! Got it the right way again!!

Related

Restoring imei and efs on an unbrickable infuse?

Hi, the title says it all. Is it possible to restore imei and efs on a samsung infuse with unbrickable mod applied? Or unbrickable mod only possibility is to reflash the firmware? I mean i know that unbrickable mod is used to be able to get the phone on download mode but. Is it able to flash something to fix imei? Because i have tried just about everything to restore my Infuse imei with no luck. I know there are advanced tools to do so, But i was curious since Unbrickable mod go so deep in terms of changing that sequence i may be able to repair my imei somehow with it.
I posted an EFS repair file sometime back. It's either in a zip or a tar.
Do you have an idea on where is the file located(what thread)? My imei shows as null. I guess ill be able to fix it with that file right?
By the way, pretty cool to find another old school guy in terms of pcs. My first computer was an atari 400. Had a lot of fun with machine language and basic also. Every time i managed to draw a simple line with commands or maybe just saving programs using an old school tape recorder which was the old version of what we call cds and dvds nowadays ha ha... Oh that brought me some memories ha ha
Hey Truckerglenn, sorry for bothering you but i went thru every post you have made(all 19 pages) and i didnt find an efs file. Maybe its been deleted or something. The only thing close to that issue i found is the Restoring a dd backup with Odin (A fix for a badly broken EFS) thread but no file there. Maybe you can help me find it
Nevermind Glenn, i already found it. In case someone needs it heres the link to that thread:
http://forum.xda-developers.com/showthread.php?t=1438113
Didnt worked for me, but maybe some lucky guys will be able to fix theirs with that file....
Sorry that it didn't work.
If you had an Atari400, then you'll remember the Happy boards that we used to put in the old 1050 drives. They made such a racket, but you could copy any copy protected disk.
Hey Truckerglenn, finally i managed to make it work!!! Wohoo! Im very happy, So when i was going to give up, i decided to give it a try again and heres what i did for the rest of the forum in case they have the same situation and want to give it a try:
I openned ODIN and clicked efs clear, I know its not recommended but i didnt have anything to lose so, I used the infuse unbrick files to take it back to FROYO, pit, pda and phone. Then i use your efs file and dropped it in the csc box. The phone flashed. And when it went into recovery i gave it a factory reset and rebooted. When it turned on Make shure enough it looked like nothing happened. But a couple seconds later the phone did have its signal and the baseband version was back also. I know its weird, but it worked for me. So if you have a phone showing no imei and baseband unknown why not give it a try??? You could not damage it any further than you already have!!!!!!!!!!!!
Great glad it worked. It'd been so long, that I'd forgotten the steps that I used. But now that you mentioned it, I do remember having to wipe the efs from within hemidal or odin.
I'm planning my escape from the digital world!
enelyam said:
Hey Truckerglenn, finally i managed to make it work!!! Wohoo! Im very happy, So when i was going to give up, i decided to give it a try again and heres what i did for the rest of the forum in case they have the same situation and want to give it a try:
I openned ODIN and clicked efs clear, I know its not recommended but i didnt have anything to lose so, I used the infuse unbrick files to take it back to FROYO, pit, pda and phone. Then i use your efs file and dropped it in the csc box. The phone flashed. And when it went into recovery i gave it a factory reset and rebooted. When it turned on Make shure enough it looked like nothing happened. But a couple seconds later the phone did have its signal and the baseband version was back also. I know its weird, but it worked for me. So if you have a phone showing no imei and baseband unknown why not give it a try??? You could not damage it any further than you already have!!!!!!!!!!!!
Click to expand...
Click to collapse
I'm glad you got this sorted out, enelyam.
I'm gonna post a link to this thread in the HOW TO thread I started so it can be reference for anyone else later.
Thanks for posting your results.
Add a [SOLVED] to your thread title so some other unfortunate soul (not wise enough to have 10 EFS folder back ups like me) who borked their phone later can find it too.
Thank you all got my imei back.
I have already hit the thanks button but felt compelled to write it here as well.
I was really hoping this would work for me, but when I dial in *#06# I get a "IMEI NULL/NULL" pop up. Any other ideas that could possibly work for me? I really don't want this phone to end up being just a music device.
didnt work for me either
lemonz23 said:
I was really hoping this would work for me, but when I dial in *#06# I get a "IMEI NULL/NULL" pop up. Any other ideas that could possibly work for me? I really don't want this phone to end up being just a music device.
Click to expand...
Click to collapse
I have tryed everything and didnt work for me either, my only hope is to go to my moms tomorrow, my lil brother has a worrking infuse, i'll try something maybe ill be able to fix mine..

Sph P100 NOT FOUND ON QSTP

i did a search on this form and i couldnt find nothing similar. to make a long story short when i bought this tablet i was able to put it on DIAG using launcher pro and a few other steps of coarse. and i u was able to read this device on QSTP and i used to get this on QSTP FFA6550-ZRF6500 same one as my Epic 4G. mow here is what happened i was flashing a stock tar ROM with Odin and by accident i checked the clear EFS on Odin and after i a succesfull process after my tab rebooed of caorse y lost all my 3g activation from the tab and when i went to QSTP to load all my activation again it was not able to be detected it on QSTP anymore. now if i go to device manager on windows or QSTP configuration its shows on what port the tab its connected on but under phone number it says NO PHONE. iam wondering what did got wiped? radio or what did i lost? or how can i get back this FFA6550-ZRF6500 or what ever its the right one into this tab? i know it used to have FFA6550-ZRF6500 but i dont know if there is another one for this tab or not. if anyone has any info please let me know thanks in advance..
im pretty sure this is the wrong forum. this is galaxy tab plus. i think youre looking for original tab.
by accident you clicked clear EFS? this place gets better everyday.
chrisrotolo said:
im pretty sure this is the wrong forum. this is galaxy tab plus. i think youre looking for original tab.
by accident you clicked clear EFS? this place gets better everyday.
Click to expand...
Click to collapse
well whats wrong with checking clear EFS? i have done that onmy Epic and all it dis was wiped all the info but it got it back after. but on my sph p100 it didnt happened
It disturbs me that in every one of your posts you are mixing up the names of critical tools and systems. I would take a step back, read and understand the systems and processes you need to work with, and then try again.
You sound, to me, like you are rushing to be one of the cool kids without doing your due diligence
robyr said:
It disturbs me that in every one of your posts you are mixing up the names of critical tools and systems. I would take a step back, read and understand the systems and processes you need to work with, and then try again.
You sound, to me, like you are rushing to be one of the cool kids without doing your due diligence
Click to expand...
Click to collapse
well all iam doing its looking for a solution to my problem. before i eve posted this thread i search the whole forum for a similar topic even when i posted the topi the forum have a few sugestions about maybe similar or close topic i went to all 5 and none of them were similar to mines. so thats why i posted on here. iam rushing anyone or rushing my self to anything. iam only looking for an answer if there is one. simple as that. at leat iam honest to specify what happened. not like others that justify by saying>>>>> nahhhhhhh i naver dodne hat before i dont know what happened bla bla bla. <<<<< at least i was honest to describe the best i could on how everything started..
latinlover515 said:
well all iam doing its looking for a solution to my problem. before i eve posted this thread i search the whole forum for a similar topic even when i posted the topi the forum have a few sugestions about maybe similar or close topic i went to all 5 and none of them were similar to mines. so thats why i posted on here. iam rushing anyone or rushing my self to anything. iam only looking for an answer if there is one. simple as that. at leat iam honest to specify what happened. not like others that justify by saying>>>>> nahhhhhhh i naver dodne hat before i dont know what happened bla bla bla. <<<<< at least i was honest to describe the best i could on how everything started..
Click to expand...
Click to collapse
Well, to be honest your writing style makes it incredibly hard to figure out what you are even talking about, and of course you aren't going to find what you need when you aren't even using the right terms. It's QPST, not QSPT or any thing other than QPST.
robyr said:
Well, to be honest your writing style makes it incredibly hard to figure out what you are even talking about, and of course you aren't going to find what you need when you aren't even using the right terms. It's QPST, not QSPT or any thing other than QPST.
Click to expand...
Click to collapse
oh **** lol. my bad i didnt notice that. yes thats what i ment QSTP to flash or edits phone. sorry about that. its sucks having bad eyes like in my case. thanks robyr.
and you're in the wrong device forum as no tab plus has qualcomm chips, I imagine you have the Original 7" Tab correct?
I would still be willing to help, but I havent used the QSTP tool that much. We are familiar with Odin. you say you have no 3G, so you're ROM boots up? Can you check if you have an IMEI or an /EFS folder present? If not you may have a very difficult time recovering if its possible at all.
What do you use QSTP for? flashing radios?
More clear info and we can try to help, although Id start by searching you're devices thread.
chrisrotolo said:
and you're in the wrong device forum as no tab plus has qualcomm chips, I imagine you have the Original 7" Tab correct?
I would still be willing to help, but I havent used the QSTP tool that much. We are familiar with Odin. you say you have no 3G, so you're ROM boots up? Can you check if you have an IMEI or an /EFS folder present? If not you may have a very difficult time recovering if its possible at all.
What do you use QSTP for? flashing radios?
More clear info and we can try to help, although Id start by searching you're devices thread.
Click to expand...
Click to collapse
thanks chrisrotolo for you reply. well i have a sprint version of the galaxy tab 7 inches. sph p100. when i first got it i was able to put it on diag mode to be able to flash it to my boost mobile account. and qhen i sued QPSt i was abel to edit the phone or what ever its called on the tablet and i had it working for over a year. but i was doing a clockwork and recovery flash trough ODIN and i dont know how the hell y checked clear EFS and the damn activation disapeared and when i tryed to reflash it again to my account but QSTP wasnt able to detected. it does show up on the device manager and it shows as the modem and the port wich its using. just like it used to before this whole thing started. but now on QPST it not showing up. this whole,thing its stupid. i dont know what the hell it got wiped when the clear EFS was checked. i had done this clear EFC crap on my spint Epic and i dont have that issue am able to go back to QPSt like nothing ever happened. its just this damn tablet its now showing up as a phone like it used to.. iam about to smash it..
welp... here you are.. http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-tab-imei-efs-repair/
googled it in about 2-3 seconds flat. Restoring IMEI with a box is the probably the best way to go.
I just had my Tab Plus JTAG'ed because I flashed a custom boot loader. ( I was aware I was doing so)
I highly recommend this site. If you're in a rush you can choose rush option. This guy is great, send him an email Im sure he can help.
do you have any /efs folder or nv_data.bin or nv_data.bak files anywhere?
Enjoy. Research a bit more and be careful flashing huh?
Peace.
chrisrotolo said:
welp... here you are.. http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-tab-imei-efs-repair/
googled it in about 2-3 seconds flat. Restoring IMEI with a box is the probably the best way to go.
I just had my Tab Plus JTAG'ed because I flashed a custom boot loader. ( I was aware I was doing so)
I highly recommend this site. If you're in a rush you can choose rush option. This guy is great, send him an email Im sure he can help.
do you have any /efs folder or nv_data.bin or nv_data.bak files anywhere?
Enjoy. Research a bit more and be careful flashing huh?
Peace.
Click to expand...
Click to collapse
ok thanks man ill give thata a try. and no i dont have any nv data files. i even try doing a back up from my phone my Epic 4g to see if i could use that and i coudnt even back up the efs it came out blank. is there a posible way that i can do this my self? lokking for some nv data file that i can flash trugh oding or how ever its done

Touchscreen not working after root, but S-Pen works fine

I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
Thanks,
Reffu
Hi,
same issue here. Today the touchscreen stopped working suddenly after i flashed the Android Revolution HD 5.0 Rom yesterday. However, the S-Pen is still working fine. Installing other ROMs and the Stock ROM via Odin did not help. Issue allso appears in Touch-enabled-Recovery.
I see no reason, why this should be a hardware issue, although my N8000 came back from service a few days ago, where they also replaced the screen and digitizer.
Had anyone this issue before and was abled to resolve it?
Greets
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
to read this as a Note 10.1 newbie is not very encouraging. are there any similar facts between all of you like
which Note model do you have
how did you jaibreak (which method)
which rom did you have before
which rom do you have now
how did you flash a new rom
...
is there a way to find out whether the touchscreen is really "dead for touch"?
This is a bit scary - my Note 10.1 is arriving today, and I plan to root it at a minimum. I actually don't mind Touchwiz all that much on my Note 2 (which is running CleanROM ACE), so I think I might just root the 10.1 for now.
So restoring completely back to stock (via Odin) doesn't fix it? That is really odd that ROM-ing this thing might cause a hardware failure...
jiggyman said:
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
kkretch said:
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
Click to expand...
Click to collapse
Did anyone solve this, I'm having the same problem.
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
Just curious - did you just root, or did you root and install a ROM?
I am only rooted so far - haven't felt the need to ROM yet - partially due to worries about this happening. I bought a refurb from Best Buy and only get 90 days of warranty.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
If they say you got a new one, you got one. They'll tell you otherwise if there's an issue over the phone.
But I wouldn't be afraid of ROMs, but to be more diligent and wise when it comes to choosing them. It's like choosing a poisonous mushroom versus an edible one to make stroganoff or stir fry. If you know what to avoid for the next time and follow the correct process to doing the root and flashing, there will not be an issues.
This is from someone who has soft-bricked my first tablet and learned how to unbrick my SIM-less Captivate and Note 10.1. It's how you apply the method and how much attention you practice not getting stuck into these situations is what matters. Especially since I bricked my tablet via experimentation and un-bricked it on the same day with ease.
It's not some big complex deal of rocket science or something only the mere geniuses can do, its how you perceive yourself and how you act. If you believe that you will suck and brick it to kingdom come , it will happen intentionally or subconsciously.
In this case, it was a freak accident where the file/s accessed and deleted the wrong files which allowed for capacitive touchscreen use, and it should be reported to x developers if you have not done so already.
I have rooted and used the Revolution HD rom, the Rom where you customize the colors of the bar/other things, and on the Captivate, the AOKP Collective. I further customized the latter with the Xperia launcher as it zips.
Did anyone find a repair for this besides replacement? My Note 2 is doing the same thing now.
Has anyone found a fix for the touch screen not working yet??
Anyone have any ideas?
Technicians input for touch problem
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain that follows the instructions on the mod sites exactly as shown step by step will never have a problem, all those that do end up with paper weights or bricks didn't follow the instructions in numerical order.
Believe it or not even if after you have modded a rom and brought it back to standard they know it has been modded as they have a list of problems associated with repairs after roms have been modded so you are only fooling yourself they don't.
Same as the smoker that tells his Dr he has given up even though all the symptoms prove he really didn't.
So in my expert opinion if you play with modding and stuff it up why should you be eligible for a warranty claim ? The manufacturer has sold you or supplied a working item that you decided to f_ck around with and because of your stupidity expect some one else to pay for it.
I am not saying don't mod your phone with all the great roms out there but please to save yourself a lot of pain and cost some poor smuck trying to run a business in these economic times a lot of out of pocket from sending items back for replacement or warranty plus the time it takes to do all the paperwork and such, please please please read the instructions 300% or triple check you are doing everything exactly as the instructions say and you will be enjoying all the new benefits of that customised rom and laughing at all the noobs stuffing up their brand new device from not doing so.
I know this won't fix your problem but reread that last bit it was your problem as you are to clever to follow some one else's instructions
anyone have solution regarding this issue, mine have issue also, can anyone spare how to fix it without changing hardware?
---------- Post added at 06:47 AM ---------- Previous post was at 06:28 AM ----------
i hope anyone can solve my issue with touch not responding
WOW.. on TOPIC Flashing .pit might help ???
Gardum said:
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain
Click to expand...
Click to collapse
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
erica_renee said:
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
Click to expand...
Click to collapse
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
popohunters said:
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
Click to expand...
Click to collapse
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
erica_renee said:
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
Click to expand...
Click to collapse
thanks sir, im done the flashing with pit files+ official firmware but touch screen is still missing, is there a modem file for touch screen maybe i missed it while its in downloading process before i brick the touch screen
any hope out there?????
confused and need help
i have a n8000 , base band version N8000XXCLL1, my touch screen stoped responding while playing a game , only Spen works , tried resetting , but no help, I'm a no-voice when it comes to programing and need a step by step guide >>>> many thanks in advance for all your help
reffu said:
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
I got the same problem after rooting my phone.... I used the following method and got ride of that Problem. ..
type this star code in in it Phone dialler *#2663#
Now you should see "TSP"
<update>
TAP on TSP ......it will take 5 seconds only....
......
NOW ENJOY ☺☺
Click to expand...
Click to collapse

Strange efs/imei problem, wont flash to stock

so I have a SR I just put a new (used, off ebay but new to me) motherboard in, and it works fine except for no imei/baseband, so obviously no data/voice/etc.
the efs folder seems to be fine...imei folder is in there, keystr file is there...I don't understand what the problem is.
the worst part is, only certain roms will flash...I cannot flash to stock, I've tried with odin and from recovery, a couple different stock versions of GB, ICS, and still no luck. It actually flashes, then does the "android is upgrading" screen, but then bootloops on the optimizing apps part. I've tried to flash to stock probably 20 times now, wiped everything, fixed permissions, etc...without fail it bootloops every time.
the only roms Ive gotten to flash are slim and jedi...no stock rom will flash, nor avatar and a couple others I've tried. but slim and jedi flash and boot right up...just have blank imei/baseband.
I've scoured threads for days trying to figure out what to do here...nobody seems to have my exact problem, and everything I've found about restoring efs/imei/baseband has involved flashing to stock...which I can't do.
anyone have any ideas?
Have you tried flashing different radios (baseband)?
http://forum.xda-developers.com/showthread.php?t=1785999
causticfix said:
so I have a SR I just put a new (used, off ebay but new to me) motherboard in, and it works fine except for no imei/baseband, so obviously no data/voice/etc.
the efs folder seems to be fine...imei folder is in there, keystr file is there...I don't understand what the problem is.
the worst part is, only certain roms will flash...I cannot flash to stock, I've tried with odin and from recovery, a couple different stock versions of GB, ICS, and still no luck. It actually flashes, then does the "android is upgrading" screen, but then bootloops on the optimizing apps part. I've tried to flash to stock probably 20 times now, wiped everything, fixed permissions, etc...without fail it bootloops every time.
the only roms Ive gotten to flash are slim and jedi...no stock rom will flash, nor avatar and a couple others I've tried. but slim and jedi flash and boot right up...just have blank imei/baseband.
I've scoured threads for days trying to figure out what to do here...nobody seems to have my exact problem, and everything I've found about restoring efs/imei/baseband has involved flashing to stock...which I can't do.
anyone have any ideas?
Click to expand...
Click to collapse
Take a look at this thread, it may help. http://forum.xda-developers.com/showthread.php?p=25172599#post25172599
thanks for the replies...
I've flashed UCM1 and UCLL3 radios, they flash fine but no change...still can't flash to stock and no imei/baseband/service.
That fix thread was one of the first I found, but as I still have my keystr file in the efs folder, I didn't think it would apply to me...I suppose I could make an external backup of my efs, delete it and try one of those methods from scratch.
read through the restore to stock sticky http://forum.xda-developers.com/showthread.php?t=1652398 and go through the trouble shooting sections, if that doesn't help u could have bad hw
causticfix said:
so I have a SR I just put a new (used, off ebay but new to me) motherboard in, and it works fine except for no imei/baseband, so obviously no data/voice/etc.
the efs folder seems to be fine...imei folder is in there, keystr file is there...I don't understand what the problem is.
the worst part is, only certain roms will flash...I cannot flash to stock, I've tried with odin and from recovery, a couple different stock versions of GB, ICS, and still no luck. It actually flashes, then does the "android is upgrading" screen, but then bootloops on the optimizing apps part. I've tried to flash to stock probably 20 times now, wiped everything, fixed permissions, etc...without fail it bootloops every time.
the only roms Ive gotten to flash are slim and jedi...no stock rom will flash, nor avatar and a couple others I've tried. but slim and jedi flash and boot right up...just have blank imei/baseband.
I've scoured threads for days trying to figure out what to do here...nobody seems to have my exact problem, and everything I've found about restoring efs/imei/baseband has involved flashing to stock...which I can't do.
anyone have any ideas?
Click to expand...
Click to collapse
Hey, Im facing the exact same problem! just that my imei turned to 0 and basband to unknown after i upgraded to cynogenmod 10.1-rc.2.
It was working fine till suddenly one day i lost network. I tried everything like you did. So far ive had no luck fixing my efs!
What you can do is download QTPS and in it there is a RF NV Item manager to rewrite your efs. For that you need to put you phone into DIAG mode unfortuantely i cant get to that on 10.1nightly cynogenmod that im using.
I m stuck. I know for sure flashing roms or radios wont help at all. the same boot loop problem happens when I flash using odin, it use to work perfectly fine earlier.
Some how the nv_data.bin and such files are missing from my efs>imei folder that contain the imei data.
If you find something please lemme know too [email protected]
Vgkiller said:
Hey, Im facing the exact same problem! just that my imei turned to 0 and basband to unknown after i upgraded to cynogenmod 10.1-rc.2.
It was working fine till suddenly one day i lost network. I tried everything like you did. So far ive had no luck fixing my efs!
What you can do is download QTPS and in it there is a RF NV Item manager to rewrite your efs. For that you need to put you phone into DIAG mode unfortuantely i cant get to that on 10.1nightly cynogenmod that im using.
I m stuck. I know for sure flashing roms or radios wont help at all. the same boot loop problem happens when I flash using odin, it use to work perfectly fine earlier.
Some how the nv_data.bin and such files are missing from my efs>imei folder that contain the imei data.
If you find something please lemme know too [email protected]
Click to expand...
Click to collapse
Just factory reset when it boot loops
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Vgkiller said:
Hey, Im facing the exact same problem! just that my imei turned to 0 and basband to unknown after i upgraded to cynogenmod 10.1-rc.2.
It was working fine till suddenly one day i lost network. I tried everything like you did. So far ive had no luck fixing my efs!
What you can do is download QTPS and in it there is a RF NV Item manager to rewrite your efs. For that you need to put you phone into DIAG mode unfortuantely i cant get to that on 10.1nightly cynogenmod that im using.
I m stuck. I know for sure flashing roms or radios wont help at all. the same boot loop problem happens when I flash using odin, it use to work perfectly fine earlier.
Some how the nv_data.bin and such files are missing from my efs>imei folder that contain the imei data.
If you find something please lemme know too [email protected]
Click to expand...
Click to collapse
will do.
also, you may know this already, but just in case, be aware the skyrocket doesn't use nv_data.bin...I thought it did too when I first started searching around about this, and when i couldnt find it I was pretty freaked out...but then i found out the skyrocket actually uses 3 encrypted partitions rather than a nv_data file. so if you have at least some files in your efs/imei folder you may be in a better spot than it seems. of course if its totally empty, you'll likely have a lot more work to do.
I'll update if I have any luck.
causticfix said:
will do.
also, you may know this already, but just in case, be aware the skyrocket doesn't use nv_data.bin...I thought it did too when I first started searching around about this, and when i couldnt find it I was pretty freaked out...but then i found out the skyrocket actually uses 3 encrypted partitions rather than a nv_data file. so if you have at least some files in your efs/imei folder you may be in a better spot than it seems. of course if its totally empty, you'll likely have a lot more work to do.
I'll update if I have any luck.
Click to expand...
Click to collapse
Yes I have two files in my imei folder i,e keystr and mps_code.dat!
I tired changing them from root explorer! pasted someones else's efs folder! but still I cant fix my imei is stays 0.
i donno how to get to diag mode with this rom, otherwise i could have tried my luck with QPTS.
Incase you have broken your imei without backing it up, there is another way. And yes it is legal.
Here's the tutorial http://goo.gl/wtW29 and here's the needed tools (software & hardware) http://goo.gl/54mtk.
lingowistico said:
Incase you have broken your imei without backing it up, there is another way. And yes it is legal.
Here's the tutorial http://goo.gl/wtW29 and here's the needed tools (software & hardware) http://goo.gl/54mtk.
Click to expand...
Click to collapse
I actually have octopus box as well as the z3x samsung tool installed, however, they're both server activation based...the software is useless without an $89 (octopus) to $120( (z3x) activation.
I'd rather not spend that kind of money for something I'll likely only need once, so I'm gonna do as much as I can in the way of free solutions, and if I have no luck there I'll probably just send it to mobiletechvideos for their $40 efs/imei repair. I'm guessing they use one or more of these repair box programs themselves anyway, and will do the same job for only $40.
thanks for the suggestion anyway though..
causticfix said:
I actually have octopus box as well as the z3x samsung tool installed, however, they're both server activation based...the software is useless without an $89 (octopus) to $120( (z3x) activation.
I'd rather not spend that kind of money for something I'll likely only need once, so I'm gonna do as much as I can in the way of free solutions, and if I have no luck there I'll probably just send it to mobiletechvideos for their $40 efs/imei repair. I'm guessing they use one or more of these repair box programs themselves anyway, and will do the same job for only $40.
thanks for the suggestion anyway though..
Click to expand...
Click to collapse
There's this polish guy who probably also has all the same boxes and he takes €10 for imei repair by remote desktop.
http://forum.samdroid.net/f70/repair-imei-s2-5729/
And finally you could try helping the op of this thread to add compatibility for skyrocket, this would be free.
lingowistico said:
There's this polish guy who probably also has all the same boxes and he takes €10 for imei repair by remote desktop.
http://forum.samdroid.net/f70/repair-imei-s2-5729/
And finally you could try helping the op of this thread to add compatibility for skyrocket, this would be free.
Click to expand...
Click to collapse
Isn't there any way to fix my imei on my own ?
Mt efs folder also looks good now with all the files it should have but still the imei remains unaffected.
Also i'd like to know that the qualcom nv tool showed my esn as dead and mied as 000....000 does the dead thing mean it isnt repairable ?
I tried using QPTS but this is where I get stuck.. (img attatched)
Vgkiller said:
Isn't there any way to fix my imei on my own ?
Mt efs folder also looks good now with all the files it should have but still the imei remains unaffected.
Also i'd like to know that the qualcom nv tool showed my esn as dead and mied as 000....000 does the dead thing mean it isnt repairable ?
I tried using QPTS but this is where I get stuck.. (img attatched)
Click to expand...
Click to collapse
Obviously there is since some random polack can do it for you on his PC, the problem is the lack of knowledge.
Those who know won't tell you how, because they want € for it :crying:
lingowistico said:
Obviously there is since some random polack can do it for you on his PC, the problem is the lack of knowledge.
Those who know won't tell you how, because they want € for it :crying:
Click to expand...
Click to collapse
This totally defeats the purpose of this forum then. Its sad.
Vgkiller said:
This totally defeats the purpose of this forum then. Its sad.
Click to expand...
Click to collapse
People want money for it because it's mostly used for making stolen phones work again.
That means real life risks like fines, jail etc.
Of course there are lots of examples when people experiment with this or that and delete their imei accidentally, or want to change the imei for some other reason. But these are more rare.
An update...
I managed to finally get flashed to stock...still null/null imei & baseband unknown. Efs folder is still there with files, keystr file is on...not sure what else I can do myself at this point so, I guess its time for the Polish dude or mobiletechvideos.
Hi People,
Did any1 found any solution?
talk2sharn said:
Hi People,
Did any1 found any solution?
Click to expand...
Click to collapse
unfortunately not for me. I finally got the polish dude to try restoring the imei remotely...he used like 3 or 4 different programs, nothing worked.
so, i just got a broken SR with a cracked lcd off ebay for $50 and used the motherboard from it.
causticfix said:
unfortunately not for me. I finally got the polish dude to try restoring the imei remotely...he used like 3 or 4 different programs, nothing worked.
so, i just got a broken SR with a cracked lcd off ebay for $50 and used the motherboard from it.
Click to expand...
Click to collapse
Ohkies.
Did you ask the polish guy about the reason why he was not able to fix your mobile. Coz, I'm just having similar problem like yours. I tried working with all the local samsung service centre guys, nothing worked. One guy said that my mobile IMEI is locked in some database, so it is not picking or detecting my SIM, hence locked. I know that my mobile is unlocked and is valid, I ignored his comments.
I assume you changed your MotherBoard of the mobile with the new cracked SR's, so that it could take new IMEI instilled in new board. Is it so?
Also, please suggest me about any alternatives on how to fix this problem.:crying:

Stuck without a phone due to a "non-standard" Galaxy S Duos 2

Hi everyone,
I'm a little in trouble and I'd need some help 'cause I'm getting an headache.
I temporary have to use a Galaxy S Duos 2, and given its really old OS I tried to flash it with something more recent. Problem is, there is something weird in the device preventing me to flash it.
In short, I'm stuck on two problems:
1) All the resources I've tried are either for the GT-S7580, kylepro, single SIM or for the GT-S7582, kyleprods, dual sim. Guess what? Mine is a GT-S7582, kylepro, dual sim. What the hell?
2) All the roms I've tried fail during the installation 'cause of an error on the sha1 of the system folder. I've tried everything, wiped the folders in the suggested order, restored the file system...nada.
So, any idea what's going on, and how to get out of this situation? I'd absolutely need to make the device work, but I'm clueless. I've even thought to reinstall the stock rom, but I've got no idea which version is the correct one for my device version.
Uh, just to add as much info as I can: I'm using Odin3 v3.12.10 and TWRP 3.2.1-0-kylepro
Help, please?
Well, exactly like last time I posted and asked for some help, I got totally ignored. Luckily, after a while yesterday I've done some thinking and I've found the possibile cause of the problem, tried and...yes, it worked; posting here in case someone else would ever find itself stuck on something similar in the future.
In short, the root of the problem is that for whatever reason the phone was thinking to be a kylepro instead of a kyleprods. I tried to correct the build.prop file, but there is no chance to do it from inside TWRP so I ended up tweaking the updater-script file. The procedure is explained on line in different sites, I cannot give a link as the forum system does not allow me to do it.
you can post the link with a minor mentioned edit, would be helpful for others who might face the same in future

Categories

Resources