Related
Ok so I got the samsung galaxy light from metro running 4.4.2 and I decided to root my phone got myself rooted but I used some**** that changdd my phone from metro to tmobile and I guess my pho j e is locked now and its on 4.2.2 and im a iphone guy and dont really understandwhat I did but any help with gettjng my phone back would really be awesome
themilkboy08 said:
Ok so I got the samsung galaxy light from metro running 4.4.2 and I decided to root my phone got myself rooted but I used some**** that changdd my phone from metro to tmobile and I guess my pho j e is locked now and its on 4.2.2 and im a iphone guy and dont really understandwhat I did but any help with gettjng my phone back would really be awesome
Click to expand...
Click to collapse
What?
I have a Galaxy Light, and I'm fairly knowledgeable about the device. But I don't understand gibberish. You need to tell us exactly what you did, and try to speak in English without typos.
Ok
Lol sorry, I rooted my phone, well I put twrp on my phone the flashed it with I guess a flash for tmobile and on jellybean instead of kitkat. I tried to flash the radio but dont think it did anything. And now I reboot my phone and its asking for the sim pin
themilkboy08 said:
Lol sorry, I rooted my phone, well I put twrp on my phone the flashed it with I guess a flash for tmobile and on jellybean instead of kitkat. I tried to flash the radio but dont think it did anything. And now I reboot my phone and its asking for the sim pin
Click to expand...
Click to collapse
Which TWRP did you flash? Did you flash T-Mobile firmware? I need to know EXACTLY what you did.
Ok
I used twrp 2.7.0.0-gardaltetmo.tar. The flashed a supers u update -v 1.94.zip, then I wanted to know how to unroot incase I needed to know and used SGH-t399-stock-MJA.ZIP
themilkboy08 said:
I used twrp 2.7.0.0-gardaltetmo.tar. The flashed a supers u update -v 1.94.zip, then I wanted to know how to unroot incase I needed to know and used SGH-t399-stock-MJA.ZIP
Click to expand...
Click to collapse
Don't use T-Mobiles firmware on your MetroPCS phone.
This is what you need to do.
And for the love of all that is good in this world, next time DO A BACKUP before flashing things. You installed TWRP, which gives you the ability to make a complete backup of your system exactly as it is at that point in time. If you had done a back-up before you screwed up your phone, it would have taken you but a few minutes to unscrew it.
I apologize for being harsh, but it seems to me like you really need to read and research a lot more. I always (well, usually...almost bricked my tablet the other day) read everything I can find about something potentially risky before doing it. Let this be a learning experience for you. Read as much as you can, understand what it is you are actually doing rather than just following some guide, and if you don't understand, just ask. I and most of us here would rather you asked a noobish question instead of going blindly ahead and screwing your phone up. Playing around with root and recovery and flashing without understanding it is like thinking you can perform open heart surgery with a meat cleaver because you've seen every episode of ER, Scrubs, and Grey's Anatomy.
thanks
ok thanks alot btw. just now got the files downloaded but im in twrp and the files are on my pc how could i get them to my phone? and i dont have a sd card either
themilkboy08 said:
ok thanks alot btw. just now got the files downloaded but im in twrp and the files are on my pc how could i get them to my phone? and i dont have a sd card either
Click to expand...
Click to collapse
Hm. I didn't think about that. I think you might need to get an SD card. Go on Amazon or eBay and pick one up. An 8GB one can be had for literally a few bucks, but a 64GB class 10 one for $35 is an awesome thing too.
Ok
Ok, and with the back up download how do I get the in twrp. Should I put it in a zip file or leave it how it is
ok im a retard
Planterz said:
Hm. I didn't think about that. I think you might need to get an SD card. Go on Amazon or eBay and pick one up. An 8GB one can be had for literally a few bucks, but a 64GB class 10 one for $35 is an awesome thing too.
Click to expand...
Click to collapse
ok so i cannot figure out how to do this.
i have the sgh-t399n galaxy light- with no os installed, i have twrp on my phone. and i have a backup a sd card. but when i go to restore in twrp the backup isnt there, and ive tried going threw the file options to move it to where is it suposed to go but no such luck. i thought maybe a terminal command would work but i have no clue what command to use. if you could help one more time that would be awesome
You can always use Samsung Kies 3 to flash your phone back to stock. You need your serial number though, and for some reason it is not printed on the back of the device(at least for me). A call to tech support should get that sorted anyway.
Alternatively, you can do this with Odin to a very similar effect. Search Google for something like "T399NUVUANK3 tar" to get the file you need, my personal backup is corrupt so I can't share.
fddm said:
You can always use Samsung Kies 3 to flash your phone back to stock. You need your serial number though, and for some reason it is not printed on the back of the device(at least for me). A call to tech support should get that sorted anyway.
Alternatively, you can do this with Odin to a very similar effect. Search Google for something like "T399NUVUANK3 tar" to get the file you need, my personal backup is corrupt so I can't share.
Click to expand...
Click to collapse
Ugh... I own a t399n and I'm doing some real development on it. . I've made a stock odex and deodexed rooted zip files for the t399n and haven't posted them yet. . If you're in a bad way still hit me up and I'll have you up and running in no time. Fun things coming for metro users. Who says you have to pay for a high end device to have a high end device? He he he....
Do you have a backup I bicked my samsung galaxy light metropcs then I unbricked it by restoring a backup for the samsung galaxy light that I found online. Search fresh backup for samsung galaxy light sgh t399n.
Planterz said:
Which TWRP did you flash? Did you flash T-Mobile firmware? I need to know EXACTLY what you did.
Click to expand...
Click to collapse
You're quite uppity, aren't you? I had no trouble understanding exactly what he did.
reholli said:
You're quite uppity, aren't you? I had no trouble understanding exactly what he did.
Click to expand...
Click to collapse
Are you seriously giving me crap about a post from over a year ago? Nice contribution to the discussion.:good: I have no idea if the OP ever fixed his phone, but at least I tried to help.
Planterz said:
Are you seriously giving me crap about a post from over a year ago? Nice contribution to the discussion.:good: I have no idea if the OP ever fixed his phone, but at least I tried to help.
Click to expand...
Click to collapse
And the age of the post, with respect to your attitude, is relevant how?
reholli said:
And the age of the post, with respect to your attitude, is relevant how?
Click to expand...
Click to collapse
I just love getting an email alert at 4am because someone quoted me to post absolutely nothing of substance.
It's relevant because IT WAS A YEAR AGO! I don't remember why I was so cranky that day. I did apologize to him for it. Did you notice that I also still did my best to help him? Do you have a solution to his problem? Does he even still have this phone, given that it was a year ago? If you want to fixate on my posts, fixate on the hundreds of times I've been thanked for helping others, especially going above and beyond helping people find the perfect device for them. I'm not here to be grumpy, I'm here to help people, and get help when needed. Why are you here? To pester me? Look, I respect my elders, and you're clearly older, but at the same time don't presume to talk down to me. Try reflecting on yourself and your motive in making a useless post, bumping a thread dead for several months (a severe breach of netiquette), purely to insult another member.
Come to think of it, my email alert wasn't because I was quoted (I have that feature turned off). I got the alert because I'm still subscribed to this thread, having done so in case there were new posts that might enable me to help the OP. I suppose I should unsubscribe, giving the fact that nobody has posted anything of use or substance in 7 months or so.
Hello People
Again, I'm with problems with my S3 since the one time decided to test a custom ROM which turned out to screw my IMEI and got to it back working with BOX in repair service.
I n order to see if the BOX fix did actually solve my signal problem, it was suggested to me in a previous post that I flash the same stock rom via ODIN. Before that, I backed up current EFS as well.
Unfortunately, it seems the problem wasn't entirely solved. Same as before: both my IMEI and S/N are untouched (S/N does not coincide with S/N in the back of phone) and though it says I have a full signal, I'm not registered in network and i can't make or receive calls, sms, etc. Even though I restored the EFS folder, nothing happens.
I really wish not to go back to repair service again. What else can I do about this? Many thanks and excuse my rant. Hope I was thorough and clear on the problem. I also have a EFSv2_basebands_opt4.zip file I downloaded somewhere in xda . Would that help?
Many thanks.
rhrs1987 said:
Hello People
Again, I'm with problems with my S3 since the one time decided to test a custom ROM which turned out to screw my IMEI and got to it back working with BOX in repair service.
I n order to see if the BOX fix did actually solve my signal problem, it was suggested to me in a previous post that I flash the same stock rom via ODIN. Before that, I backed up current EFS as well.
Unfortunately, it seems the problem wasn't entirely solved. Same as before: both my IMEI and S/N are untouched (S/N does not coincide with S/N in the back of phone) and though it says I have a full signal, I'm not registered in network and i can't make or receive calls, sms, etc. Even though I restored the EFS folder, nothing happens.
I really wish not to go back to repair service again. What else can I do about this? Many thanks and excuse my rant. Hope I was thorough and clear on the problem. I also have a EFSv2_basebands_opt4.zip file I downloaded somewhere in xda . Would that help?
Many thanks.
Click to expand...
Click to collapse
Flash a patched modem and kernel from here >> https://drive.google.com/folderview...sharing&tid=0B6MIUd7HJudAbU5YaGkzOUowMG8#list << see if that works if it doesyou will always need to use the patched files.
Thanks tallman43! I'll try that. Also, I noticed now that the EFS folder is EMPTY :/. and the backup .tar I made with CWM says it's 0 bytes? wtf?
still, in phone info, imei and s/n are there. weird?
THANK YOU
Flash a patched modem and kernel from here >> https://drive.google.com/folderview?...kzOUowMG8#list << see if that works if it doesyou will always need to use the patched files.
Click to expand...
Click to collapse
Your recommendation worked like a charm. My signal is up and running normally. MANY THANKS tallman43.
Lastly, even if I sometime I decide to try out a custom ROM (unlikely at the moment, but who knows?), I still have to flash patched kernel&modem? or in case of factory reset (I will be selling the phone soon) ?That custom really messed up my phone...
rhrs1987 said:
Your recommendation worked like a charm. My signal is up and running normally. MANY THANKS tallman43.
Lastly, even if I sometime I decide to try out a custom ROM (unlikely at the moment, but who knows?), I still have to flash patched kernel&modem? or in case of factory reset (I will be selling the phone soon) ?That custom really messed up my phone...
Click to expand...
Click to collapse
Yes you will always need them.
tallman43 said:
Flash a patched modem and kernel from here >> https://drive.google.com/folderview...sharing&tid=0B6MIUd7HJudAbU5YaGkzOUowMG8#list << see if that works if it doesyou will always need to use the patched files.
Click to expand...
Click to collapse
tallman43 said:
Yes you will always need them.
Click to expand...
Click to collapse
I would still like to solve the problem at its roots: to fix the "not registered in network" problem whenever factory reset or stock ROM flash via odin is done. That is simply not normal. I might be selling the phone soon and the new user won't most probably know he/she would have to apply a patched kernel or etc.. ( let alone about rooting the phone).
Basically, bring the phone back to it's original sound state before I tried out the custom ROM. What can I do about that?
Hope I'm not being annoying.. just trying to get to the bottom of things
rhrs1987 said:
I would still like to solve the problem at its roots: to fix the "not registered in network" problem whenever factory reset or stock ROM flash via odin is done. That is simply not normal. I might be selling the phone soon and the new user won't most probably know he/she would have to apply a patched kernel or etc.. ( let alone about rooting the phone).
Basically, bring the phone back to it's original sound state before I tried out the custom ROM. What can I do about that?
Hope I'm not being annoying.. just trying to get to the bottom of things
Click to expand...
Click to collapse
There is nothing you can do without your original efs backup.Only a service repair can fix it.
tallman43 said:
There is nothing you can do without your original efs backup.Only a service repair can fix it.
Click to expand...
Click to collapse
Understood. I think I have the original EFS in my SD, though I tried replacing it once and it didn't work out... I suppose I'll have to make do. Thanks for everything man
Flashing modem with Ariza patch was bad idea. Your efs folder is screwed up now and you are addicted to constantly flash this dirty workaround.
If anyone have problems with registering in network please check your device serial number first. It must be the same as on the sticker under battery. If it's not then type *#0011# and check info under IMEI CERT. If there is FAIL info then you should use any box ie Z3X to correct phone's serial number. It takes only few minutes and is cheap. It's better long-term way than patching and permanently destroying your efs informations.
If you have backup then you should flash normal modem and restore original efs partition. Then find any GSM service center with box and tell them to fix serial number. It shouldn't cost more then 5-10 dollars.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
SirKunon said:
Flashing modem with Ariza patch was bad idea. Your efs folder is screwed up now and you are addicted to constantly flash this dirty workaround.
If anyone have problems with registering in network please check your device serial number first. It must be the same as on the sticker under battery. If it's not then type *#0011# and check info under IMEI CERT. If there is FAIL info then you should use any box ie Z3X to correct phone's serial number. It takes only few minutes and is cheap. It's better long-term way than patching and permanently destroying your efs informations.
If you have backup then you should flash normal modem and restore original efs partition. Then find any GSM service center with box and tell them to fix serial number. It shouldn't cost more then 5-10 dollars.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
Click to expand...
Click to collapse
I have never flashed the Ariza patch nor have I even mentioned it on my previous posts explaining the problem. Fixing the s/n issue is indeed adviseable, but paying to correct s/n using box here where I live is ASTRONOMICALLY expensive. They should answer for never having fixed it, but they won't. Here is a hell of a lot more than 5-10 dollars, unfortunately.
Believe me , I'm no happier in applying this sorry fix every time I want to factory reset or upgrade, etc; it's the only option I have left at the moment.
Those files you have flashed, I mean kernel and modem are patched with Ariza's method. It is called Ariza patch and it is latest solution you should take to resurrect your phone because it is a destructive one.
Sorry to hear that you can't repair it as it should be especially if you want to sell this device.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
SirKunon said:
Flashing modem with Ariza patch was bad idea. Your efs folder is screwed up now and you are addicted to constantly flash this dirty workaround.
If anyone have problems with registering in network please check your device serial number first. It must be the same as on the sticker under battery. If it's not then type *#0011# and check info under IMEI CERT. If there is FAIL info then you should use any box ie Z3X to correct phone's serial number. It takes only few minutes and is cheap. It's better long-term way than patching and permanently destroying your efs informations.
If you have backup then you should flash normal modem and restore original efs partition. Then find any GSM service center with box and tell them to fix serial number. It shouldn't cost more then 5-10 dollars.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
Click to expand...
Click to collapse
SirKunon said:
Those files you have flashed, I mean kernel and modem are patched with Ariza's method. It is called Ariza patch and it is latest solution you should take to resurrect your phone because it is a destructive one.
Sorry to hear that you can't repair it as it should be especially if you want to sell this device.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
Click to expand...
Click to collapse
oh... well, that I didn't know :$ SirKunon. I understand and totally agree with you on everything. I'll see maybe if I can find some place cheaper for getting it repaired... Many thanks
hi i was wondering if you guys can help me,i have your problem but i have an efs backup,but i cant seem to be able to restore my imei,i tried Ktool,efs professional,nothing seems to work,i should mention that the efs backup was from a Samsung 4.1.2 stock now my phone is on CM11
thanks
rhrs1987 said:
Hello People
Again, I'm with problems with my S3 since the one time decided to test a custom ROM which turned out to screw my IMEI and got to it back working with BOX in repair service.
I n order to see if the BOX fix did actually solve my signal problem, it was suggested to me in a previous post that I flash the same stock rom via ODIN. Before that, I backed up current EFS as well.
Unfortunately, it seems the problem wasn't entirely solved. Same as before: both my IMEI and S/N are untouched (S/N does not coincide with S/N in the back of phone) and though it says I have a full signal, I'm not registered in network and i can't make or receive calls, sms, etc. Even though I restored the EFS folder, nothing happens.
I really wish not to go back to repair service again. What else can I do about this? Many thanks and excuse my rant. Hope I was thorough and clear on the problem. I also have a EFSv2_basebands_opt4.zip file I downloaded somewhere in xda . Would that help?
Many thanks.
Click to expand...
Click to collapse
May i ask a few questions about your problem?
Which version were you using when you desided to use a custom rom?
Was your phone ever rooted before installing a custom rom (when you were on official)
Did you upgrade your phone before? (Official via ota or odin)
thewalekk said:
May i ask a few questions about your problem?
Which version were you using when you desided to use a custom rom?
Was your phone ever rooted before installing a custom rom (when you were on official)
Did you upgrade your phone before? (Official via ota or odin)
Click to expand...
Click to collapse
I was on 4.2.2 leaked version ROM some guy installed at a repair service some time ago when the phone belonged to my mother. I was actually rooted using the CF AutoRoot method, with Philz CWM recovery. I decided to change to a custom 4.3 without having changed first to a stock 4.3.
The problem came when, within the custom ROM's aroma installer, I ticked an option to upgrade the modem to some build I can't remember now and my signal became screwed up. I informed this in the developer's custom rom discussion thread about the issue to which he replied that the problem was that the EFS folder tried to convert from v1 to v2 and failed (this was when I learned of the whole efs version folder change since build XXX (don't remember).
I download a stock unbranded 4.3 ROM and flashed it via ODIN, believing that would solve the issue; it didn't. Finally, I became desperate and took it to a repair service where they used box. Apparently, late did I notice s/n was not the same as the one in the back of phone. I'm guessing that would solve the problem? I don't know.
i am sorry for your loss . i wish you had all that info you learned before a try and fail. now that your imei number is a clon number, and once a box tempers with that you cant go back even if you have your orijinal efs folder or backup. you should always have that 2 patched modem and kernel files on your sd card just incase. you can use custom 4.3 with the patched files and get a signal but you will always have some lags after some time because of the kernel. and lucky you samsung stopped updating s3 officially because patched files are only for 4.3. if you dont have a desire to use custom 4.4.4 kitkat roms then you are good to go and when it comes to sell the device, the price will be much lower then an original s3.
thewalekk said:
May i ask a few questions about your problem?
Which version were you using when you desided to use a custom rom?
Was your phone ever rooted before installing a custom rom (when you were on official)
Did you upgrade your phone before? (Official via ota or odin)
Click to expand...
Click to collapse
thewalekk said:
i am sorry for your loss . i wish you had all that info you learned before a try and fail. now that your imei number is a clon number, and once a box tempers with that you cant go back even if you have your orijinal efs folder or backup. you should always have that 2 patched modem and kernel files on your sd card just incase. you can use custom 4.3 with the patched files and get a signal but you will always have some lags after some time because of the kernel. and lucky you samsung stopped updating s3 officially because patched files are only for 4.3. if you dont have a desire to use custom 4.4.4 kitkat roms then you are good to go and when it comes to sell the device, the price will be much lower then an original s3.
Click to expand...
Click to collapse
Well, actually, IMEI didn't get cloned; of that I'm certain. IMEI is just the same as it was before I took it for the first time to repair service. It was the S/N that got changed somehow. Should I get them to correct the S/N, and use the original EFS folder (I found it, i think), would that correct all problems?
S/N number is the same with imei number as when you dial *#06# . And as i said before you cant go back even if you have your original efs folder. Dial *#06# and check your imei number from an " imei check site " you can find on google search. That will tell you what i mean.
There are: IMEI, device serial number and Android serial number. First two numbers are on the sticker in battery Bay. They must be correct because are used to authorize IMEI certificate.
Samsung's IMEI begins from 35.....
Serial number usually from RF......
If you see serial number in HEX format in phone's info section, something like f1abcadef1.. than it is android not device serial number and this mean troubles with authorize SIM card in operator network, even if it shows proper signal power.
I don't know there is any secret code to display serial number but there is plenty of phone's info apps in playstore which displays this alphanumeric string.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
It's been a while my S3 has been dead now, virtually rendering it into a WiFi tablet. Let me give a backstory.i had originally bought the phone and it was running 4.0.4, rooted. I wanted to go onto a different software so I came across Cyanogenmod. I flashed it with the automatic tool on pc. It had been quite some time I was running it, until I decided that I wanted to go back to stock. I was a complete noob back then, and where I may now a lot more stuff about phones now, there is still alot to learn. Anyway, I decided to flash a rom called "Back to noot", using twrp. The flash had gone successfully however I booted up to find that I had the infamous circle with the line through it, where the signal should be. I did some more digging and had concluded that my efs had been corrupted. As I was a complete noob, I didn't know what the efs partition was and I hadn't made a backup of it. So I was without a phone basically. Recently though I flashed the latest stock 4.3 rom onto it. My IMEI and baseband are back. However my IMEI isn't correct, the last couple of digits are incorrect, resulting in me having to face the "not registered on network". This is where I am now. I'm without my correct IMEI. Can anyone please help me restore my original IMEI? I have seen on some forums where some people have flashed down to 4.0.4 to successfully recover their phone. However sammobile now requires a premium account to download a 4.0.4 rom for the i9300, weirdly. Can anyone help me to restore the IMEI? Thanks.
You can download firmware for the i9300 on fw.updato.com . Search for the i9300 and filter by version to find the one you want. I am not sure if it is possible to restore your imei without an efs backup though. Good luck
Are you referring to the digits after the "/"?
I've never heard that dowgrading the stock ROM would change the imei.
audit13 said:
Are you referring to the digits after the "/"?
I've never heard that dowgrading the stock ROM would change the imei.
Click to expand...
Click to collapse
The entire IMEI is correct until I reach a certain point.
After the 3rd dash on the back of the phone, the digits follow "182/9". However when dialing *#06# on the phone itself the digits "4344/15". This is what I feel is causing the "not registered on network" error. I never knew downgrading can restore the phone. Ive seen on a forum that someone had recovered their phone by rolling from a higher firmware down to 4.0.4
Sent from my S6 Edge+ using XDA Labs
Was the phone purchased brand new, used, or refurbished?
If the phone is running a stock 4.3 ROM, you can't flash an older ROM as the phone will not allow flashing an older bootloader.
audit13 said:
Was the phone purchased brand new, used, or refurbished?
If the phone is running a stock 4.3 ROM, you can't flash an older ROM as the phone will not allow flashing an older bootloader.
Click to expand...
Click to collapse
The phone was purchased used. If I cannot flash an older version of Android does this mean it's no hope?
Sent from my S6 Edge+ using XDA Labs
It's very unusual that the imei would change on its own. It would be even more unusual for the imei to change when flashing one stock ROM over another. I suppose it is possible but I have never come across a situation where such a thing has happened.
Since the imei on the label does not match the imei in the phone and it was a used purchase, I tend to believe the phone is a "frankenphone" in that it was put together with parts from different phones.
Did you check to see if the imei from dialling *#06# belongs to an s3?
audit13 said:
It's very unusual that the imei would change on its own. It would be even more unusual for the imei to change when flashing one stock ROM over another. I suppose it is possible but I have never come across a situation where such a thing has happened.
Since the imei on the label does not match the imei in the phone and it was a used purchase, I tend to believe the phone is a "frankenphone" in that it was put together with parts from different phones.
Did you check to see if the imei from dialling *#06# belongs to an s3?
Click to expand...
Click to collapse
Actually I haven't checked to see if it does. Do you know how I can?
Sent from my S6 Edge+ using XDA Labs
Type the imei #s in here: https://swappa.com/esn?ref=mobilenations&data1=UUwpUvbUpU2855846YYw
Sent from my S6 Edge+ using XDA Labs
ABADAZZPLAYER said:
Not sure if it's been done properly but that's what came up
Sent from my S6 Edge+ using XDA Labs
Click to expand...
Click to collapse
Please remove your imei from the post. Enter the first 15 numbers.
audit13 said:
It's very unusual that the imei would change on its own. It would be even more unusual for the imei to change when flashing one stock ROM over another. I suppose it is possible but I have never come across a situation where such a thing has happened.
Since the imei on the label does not match the imei in the phone and it was a used purchase, I tend to believe the phone is a "frankenphone" in that it was put together with parts from different phones.
Did you check to see if the imei from dialling *#06# belongs to an s3?
Click to expand...
Click to collapse
Not if he flashed a firmware or rom based earlier than 4.3 and the phone has been 4.3. Efs changed at 4.3 and going backwards kills the efs partition because 4.2 or earlier can't read the new encryption.
There is a possibility that flashing earlier firmwares can write the imei back in, I've read something about this before. If all else fails then why not try it.. Its borked anyway.
Kies emergency recovery is another method but won't work if the phone was rooted.
I think have an efs of a now dead phone. It was a btu i9300 https://drive.google.com/file/d/1MiFFyCCeh1PFuQVZa-M4woreaofcDmrb/view?usp=drivesdk
shivadow said:
Not if he flashed a firmware or rom based earlier than 4.3 and the phone has been 4.3. Efs changed at 4.3 and going backwards kills the efs partition because 4.2 or earlier can't read the new encryption.
There is a possibility that flashing earlier firmwares can write the imei back in, I've read something about this before. If all else fails then why not try it.. Its borked anyway.
Kies emergency recovery is another method but won't work if the phone was rooted.
I think have an efs of a now dead phone. It was a btu i9300 https://drive.google.com/file/d/1MiFFyCCeh1PFuQVZa-M4woreaofcDmrb/view?usp=drivesdk
Click to expand...
Click to collapse
Is this efs dead or working?
Sent from my S6 Edge+ using XDA Labs
How you use it, no clue. I've never had to. It's from a phone that was eventually killed in an accident.
The files are as they were extracted. I zipped them up myself. It is not in anyway suitable to be flashed as is but if you can get the os working and root it you can copy the files to the correct folder, set the permissions and see what happens..
I thought seeing as I have no use for it someone else can, if they can.
shivadow said:
How you use it, no clue. I've never had to. It's from a phone that was eventually killed in an accident.
The files are as they were extracted. I zipped them up myself. It is not in anyway suitable to be flashed as is but if you can get the os working and root it you can copy the files to the correct folder, set the permissions and see what happens..
I thought seeing as I have no use for it someone else can, if they can.
Click to expand...
Click to collapse
I'll give this a try. Who knows maybe this could work. If it does , lots of thanks to you lol
Sent from my S6 Edge+ using XDA Labs
The phone was successfully recovered by flashing the XXUGMK6 ROM, then flashing the Patched UGMK6 Kernal and Baseband that zuluman had given. However the phone only accepted one SIM card from a couple that I had tried, and the phone thought I was in a roaming state, meaning I couldn't use mobile data. Other than that the text message and phone calling functionality, which was the main focus of the repair, has been successful.
Sent from my S6 Edge+ using XDA Labs
I have replaced my S3's broken screen with a new one. The think is now i have "baseband unkown" and "IMEI unknown" and i can't make any calls. I have no network. I have read numerous threads here on xda and elsewhere but nothing seems to work. I haven't backed up the efs folder nor the IMEI. I don't even have the original screen with the IMEI on it. (If i only i knew back then) . I don't even know what version of I9300 i have. I think is the Exynos one. I have installed many Stock roms with different firmware and custom Roms but nothing works. I even tried to flash different modems but still nothing. Is there a way to find my IMEI and restore my baseband? Now i am on lineageos 14.1.
There is only 1 model of the GT-i9300.
If you flashed the latest stock ROM with Odin and the imei does not reappear, it likely that the EFS folder has been corrupted. This can be corrected by flashing the phone via jtag but you will need the original IMEI.
audit13 said:
There is only 1 model of the GT-i9300.
If you flashed the latest stock ROM with Odin and the imei does not reappear, it likely that the EFS folder has been corrupted. This can be corrected by flashing the phone via jtag but you will need the original IMEI.
Click to expand...
Click to collapse
So basically it's a lost cause. I don't have the IMEI. Is there a way to read the IMEI that is hardcoded on the board?
MrGoochi said:
So basically it's a lost cause. I don't have the IMEI. Is there a way to read the IMEI that is hardcoded on the board?
Click to expand...
Click to collapse
Not that I know of.
Do you have the original box, receipt, or cell contract? The IMEI is sometimes printed on these items.
audit13 said:
Not that I know of.
Do you have the original box, receipt, or cell contract? The IMEI is sometimes printed on these items.
Click to expand...
Click to collapse
No, it is an old phone that i don't use. I just happened to need it for a few days until my phone was fixed. Anw thanks for the info and the help. :good:
Hi, as said in the title, my Motorola XT910 is stuck on the logo, and will not boot, even after charging, and letting it do its thing overnight. I tried everything I could, including trying to wipe the cache via recovery mode, and I do not have access to it via adb in any ways. The only communication I can establish between it and my computer is via fastboot. The RSD Software doesn't recognize it either, though it appears on the computer as "ADB Device". Biggest problem is, I have seen threads from years ago on other forums, all over the internet with people having this issue, some had it fixed via a factory reset, some had to send it back. Obviously, I cannot send it back to motorola, as for the factory reset, I really cannot do it, since my whole objective of making this phone function again was to recover old very important videos and photos on it, which is rendered impossible due to android not starting.
I really hope someone has a solution (does anyone still even come by these threads ?).
Thanks in Advance,
Dylan.
LaMontreBelge said:
Hi, as said in the title, my Motorola XT910 is stuck on the logo, and will not boot, even after charging, and letting it do its thing overnight. I tried everything I could, including trying to wipe the cache via recovery mode, and I do not have access to it via adb in any ways. The only communication I can establish between it and my computer is via fastboot. The RSD Software doesn't recognize it either, though it appears on the computer as "ADB Device". Biggest problem is, I have seen threads from years ago on other forums, all over the internet with people having this issue, some had it fixed via a factory reset, some had to send it back. Obviously, I cannot send it back to motorola, as for the factory reset, I really cannot do it, since my whole objective of making this phone function again was to recover old very important videos and photos on it, which is rendered impossible due to android not starting.
I really hope someone has a solution (does anyone still even come by these threads ?).
Thanks in Advance,
Dylan.
Click to expand...
Click to collapse
RSD lite doesn't work with most Windows 10 machines, use Windows 7. http://forum.xda-developers.com/showpost.php?p=59348530&postcount=6
If you want to save data you need to modify the .XML file if using RSD Lite
Lots of issues can cause a boot loop, bad battery, bad app, bad hardware... even a bad charger or USB cable.
Try [Utility] - = MotoFlashPro =
Hi, thanks for replying, I took note of the software not functionning with windows 10, do you think it will work if I run 7 in VmWare and pass the phone through or do I absolutely have to use a physical 7 machine ?
Also, I really cannot make a factory cable like the one pictured in the post you linked, since none of my cables permit such a modification (the fifth pin does not have a spot to solder onto).
About the bootloop, well I'm not sure it really is one, since it doesn't loop at all, it just stays on the starting screen.
It shouldn't be a battery problem since even when giving power straight to the battery terminals, it does not boot, though the fastboot thing says "battery ok".
It shouldn't be a bad app either since last time I used the phone, like 3 years ago before I broke the screen which I replaced recently, it worked perfectly fine, and obviously I could not install an app in the meantime. The battery just ran down to 0 volts but I managed to make it work again. And what do you mean by bad charger ? Something like not powerful enough perhaps ?
LaMontreBelge said:
Hi, thanks for replying, I took note of the software not functionning with windows 10, do you think it will work if I run 7 in VmWare and pass the phone through or do I absolutely have to use a physical 7 machine ?
Also, I really cannot make a factory cable like the one pictured in the post you linked, since none of my cables permit such a modification (the fifth pin does not have a spot to solder onto).
About the bootloop, well I'm not sure it really is one, since it doesn't loop at all, it just stays on the starting screen.
It shouldn't be a battery problem since even when giving power straight to the battery terminals, it does not boot, though the fastboot thing says "battery ok".
It shouldn't be a bad app either since last time I used the phone, like 3 years ago before I broke the screen which I replaced recently, it worked perfectly fine, and obviously I could not install an app in the meantime. The battery just ran down to 0 volts but I managed to make it work again. And what do you mean by bad charger ? Something like not powerful enough perhaps ?
Click to expand...
Click to collapse
Hi again, quick update, I plugged it into my Windows Xp machine as I do not have a windows 7 computer, and it appeared. Also, could you please tell me what to change in the xml file in order to keep the data ?
Please, are you there ? I really need this help with the XML file, what do I need to edit ? I got the phone to be recognized in windows, even in rsd lite, i just need to know what to edit in the file
LaMontreBelge said:
Please, are you there ? I really need this help with the XML file, what do I need to edit ? I got the phone to be recognized in windows, even in rsd lite, i just need to know what to edit in the file
Click to expand...
Click to collapse
I've never had to use RSD Lite, and you might be better off waiting for him to respond incase I'm wrong (haven't touched this phone in a while). But I've done some digging and heard you can remove the line near the end of that XML file that goes something like
Code:
<step operation="erase" partition="userdata"/>
and it should skip the data wipe. I don't think it's necessary to remove the ones for cache and stuff. It might be a bad idea.
Smu1zel said:
I've never had to use RSD Lite, and you might be better off waiting for him to respond incase I'm wrong (haven't touched this phone in a while). But I've done some digging and heard you can remove the line near the end of that XML file that goes something like
Code:
<step operation="erase" partition="userdata"/>
and it should skip the data wipe. I don't think it's necessary to remove the ones for cache and stuff. It might be a bad idea.
Click to expand...
Click to collapse
Thanks for the info, I will indeed wait for him to reply, but i just checked in the XML file, and I do not have that line anywhere in the file. Does that mean it is incomplete or does this one just default to not erasing ? Also, this is the only file I could find that is a perfect match for my french market xt910.
LaMontreBelge said:
Thanks for the info, I will indeed wait for him to reply, but i just checked in the XML file, and I do not have that line anywhere in the file. Does that mean it is incomplete or does this one just default to not erasing ? Also, this is the only file I could find that is a perfect match for my french market xt910.
Click to expand...
Click to collapse
Also, I just checked in the other file I found, for an english-languaged model this time, it does have these lines, but is only 560mb instead of the 800 something of my french file
LaMontreBelge said:
Thanks for the info, I will indeed wait for him to reply, but i just checked in the XML file, and I do not have that line anywhere in the file. Does that mean it is incomplete or does this one just default to not erasing ? Also, this is the only file I could find that is a perfect match for my french market xt910.
Click to expand...
Click to collapse
Huh, yeah I don't really know then. The model I have is the XT912 (Verizon). I just got this info from a thread for a newer Moto. It could very well just simply not wipe, but I wouldn't go ahead and try incase you end up actually wiping it permanently. I'm not an expert at all, so I'd just wait until he gives you advice. Does this French firmware have similar lines like that for cache or other partitions? It might be in a completely different format then what I'm looking at. But I doubt it's corrupt.
Smu1zel said:
Huh, yeah I don't really know then. The model I have is the XT912 (Verizon). I just got this info from a thread for a newer Moto. It could very well just simply not wipe, but I wouldn't go ahead and try incase you end up actually wiping it permanently. I'm not an expert at all, so I'd just wait until he gives you advice. Does this French firmware have similar lines like that for cache or other partitions? It might be in a completely different format then what I'm looking at.
Click to expand...
Click to collapse
Actually I think the xt912 is pretty much identical unless I'm mistaking something. But either way, I do appreciate your cautiousness about the subject. Yes exactly I really cannot afford to lose the data that remains on the phone. Actually yes it does seem to have fairly similar lines, here have a look, on the left is the french firmware and the right the international. Now, I do not know what the files you're used to working with look like, but they may very well have similar if not identical lines.
Edit: I just re-read your question and realized I completely misunderstood what you asked. No, the french version doesn't have formatting lines at all. Deeply sorry for this misunderstanding.
LaMontreBelge said:
Actually I think the xt912 is pretty much identical unless I'm mistaking something. But either way, I do appreciate your cautiousness about the subject. Yes exactly I really cannot afford to lose the data that remains on the phone. Actually yes it does seem to have fairly similar lines, here have a look, on the left is the french firmware and the right the international. Now, I do not know what the files you're used to working with look like, but they may very well have similar if not identical lines.
Edit: I just re-read your question and realized I completely misunderstood what you asked. No, the french version doesn't have formatting lines at all. Deeply sorry for this misunderstanding.
Click to expand...
Click to collapse
I've noticed the left one is a "1FF" firmware. Which from what I've looked up, is supposed to not have the erasing lines. While the "CFC" ones are. Which is why the right one has those. But I've noticed the left firmware has what seems to be Gingerbread. I don't know if dirty flashing an older firmware will cause issues, if it's even possible. I've found an old thread on droidforums where someone tried to go back to ICS from that JB leak and ended up bricking. I don't think I can post links because I haven't posted 10 times unless they changed something.
Smu1zel said:
I've noticed the left one is a "1FF" firmware. Which from what I've looked up, is supposed to not have the erasing lines. While the "CFC" ones are. Which is why the right one has those. But I've noticed the left firmware has what seems to be Gingerbread. I don't know if dirty flashing an older firmware will cause issues, if it's even possible. I've found an old thread on droidforums where someone tried to go back to ICS from that JB leak and ended up bricking. I don't think I can post links because I haven't posted 10 times unless they changed something.
Click to expand...
Click to collapse
Actually, the phone is still on gingerbread (2.3.5) as I never found updates when it still worked, so this shouldn't be an issue (hopefully) and okay, thanks for the info, so it means my file is sound, right?
LaMontreBelge said:
Actually, the phone is still on gingerbread (2.3.5) as I never found updates when it still worked, so this shouldn't be an issue (hopefully) and okay, thanks for the info, so it means my file is sound, right?
Click to expand...
Click to collapse
I believe the file should be good unless you somehow got a bad download or something. But it seems 2.3.5 and 2.3.6 have different bootloader versions, and it looks like the firmware on the left doesn't have the "mbm" stuff. The last thing you need is a hard brick, so I'd be pretty hesitant to flash unless someone who has more knowledge tells you it's okay. I'm guessing you'd have to find a French CFC firmware and edit out that userdata wipe line (if that even works) or find a 1FF 2.3.5 firmware with an identical bootloader.
Smu1zel said:
I believe the file should be good unless you somehow got a bad download or something. But it seems 2.3.5 and 2.3.6 have different bootloader versions, and it looks like the firmware on the left doesn't have the "mbm" stuff. The last thing you need is a hard brick, so I'd be pretty hesitant to flash unless someone who has more knowledge tells you it's okay. I'm guessing you'd have to find a French CFC firmware and edit out that userdata wipe line (if that even works) or find a 1FF 2.3.5 firmware with an identical bootloader.
Click to expand...
Click to collapse
Alright, then I won't flash it, just in case. Also, do you have any way to check if the bootloader version is different ? If yes, I could check it. And alright, I'll try finding another file that happens to be on 2.3.5. Thanks again for the info sir.
LaMontreBelge said:
Alright, then I won't flash it, just in case. Also, do you have any way to check if the bootloader version is different ? If yes, I could check it. And alright, I'll try finding another file that happens to be on 2.3.5. Thanks again for the info sir.
Click to expand...
Click to collapse
I hyperlinked a link I found with some info on that. I just looked at the build number of the versions listed in that doc, looked at the bootloader version next to it, and looked at the firmware's filename. In your case, "6.5.1-167" has bootloader version "0A.6C" while 2.3.5 with the build number "6.5.1_73" has bootloader version "0A.66". My source was this Doc https://docs.google.com/document/d/1CWZU-4i7jWO26RXJ7YFJV-Ze-mJrDaTuCuVI-ZwxDBE/. I honestly don't know if the bootloader matters, but I wouldn't want to risk it in case it makes the situation worse. Hopefully shadow can help you out.
https://forum.xda-developers.com/t/index-motorola-droid-razr-2012.3023837/post-58684547
Here's a pinned thread with some firmwares if it helps any.
Smu1zel said:
I hyperlinked a link I found with some info on that. I just looked at the build number of the versions listed in that doc, looked at the bootloader version next to it, and looked at the firmware's filename. In your case, "6.5.1-167" has bootloader version "0A.6C" while 2.3.5 with the build number "6.5.1_73" has bootloader version "0A.66". My source was this Doc https://docs.google.com/document/d/1CWZU-4i7jWO26RXJ7YFJV-Ze-mJrDaTuCuVI-ZwxDBE/. I honestly don't know if the bootloader matters, but I wouldn't want to risk it in case it makes the situation worse. Hopefully shadow can help you out.
Click to expand...
Click to collapse
Okay, i just took a look at the doc linked, and I have no idea how you found it, but it is mind boggling. All the roms, listed, just like that. Thank you so much. And yes indeed the bootloader is different, and I wouldn't risk it. I'll keep looking for the 2.3.5 ROM, but for now it seems like a lost cause. Perhaps they have it over on the Motorola forums. I'll make a thread later today.
Smu1zel said:
I hyperlinked a link I found with some info on that. I just looked at the build number of the versions listed in that doc, looked at the bootloader version next to it, and looked at the firmware's filename. In your case, "6.5.1-167" has bootloader version "0A.6C" while 2.3.5 with the build number "6.5.1_73" has bootloader version "0A.66". My source was this Doc https://docs.google.com/document/d/1CWZU-4i7jWO26RXJ7YFJV-Ze-mJrDaTuCuVI-ZwxDBE/. I honestly don't know if the bootloader matters, but I wouldn't want to risk it in case it makes the situation worse. Hopefully shadow can help you out.
Click to expand...
Click to collapse
Also, in the document there is a link that leads to an archive, but no files are downloadable, do you happen to have any of them by chance ?
Smu1zel said:
https://forum.xda-developers.com/t/index-motorola-droid-razr-2012.3023837/post-58684547
Here's a pinned thread with some firmwares if it helps any.
Click to expand...
Click to collapse
This thread does indeed help a little bit, but the firmware center link does not, as it is where i got my 2.3.6 ROM from, and as far as I know, is the only french one. Honestly I do not care if it's an English one, I just want to make sure that it won't mess up the phone
LaMontreBelge said:
Also, in the document there is a link that leads to an archive, but no files are downloadable, do you happen to have any of them by chance ?
Click to expand...
Click to collapse
Yeah I think those links might be out of date. Go under "XT910" and look at some of the links. Also I found that doc under that section.
https://forum.xda-developers.com/t/index-motorola-droid-razr-2012.3023837/post-58684547
I hope I'm not leading you down a wrong path, hopefully he responds soon. Maybe the bootloader doesn't matter, I don't know.