Well gentle man. I failed to back up my /efs folder. I lost my imei and can only get an edge connection. This is just a friendly reminder to please back up your /efs folder. I did not know about doing this until it was too late. I'm my s3 was not salvageable. But still works with Wi-Fi.
Sent from my SGH-T999 using Tapatalk 2
I thought we couldn't back that up yet?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
corythug said:
I thought we couldn't back that up yet?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Inapplicable advice. Sorry.
Diviance said:
Provided you are rooted (which, if you aren't the folder isn't really in danger) you can use Root Explorer to copy it directly to the sdcard, or download dropbox and stick it in the dropbox folder and cloud back it up too.
Or Spideroak. Or Box.
Click to expand...
Click to collapse
Oooh ok, thanks. What directory is it located if you don't mind?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
It is in the root of your phone. It is the file called efs.
Sent from my SGH-T999 using Tapatalk 2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SGH-T999 using Tapatalk 2
Which is weird because I have the file bit have no way of fixing it
Sent from my SGH-T999 using Tapatalk 2
Ah, seems my advice from above is not applicable to the S3 series. Samsung moved where the IMEI is actually located or something because, from what I have found, it is not located in /efs.
So uh, for the moment aside from literally backing up every single partition on your device I do not know of a working method of backing up your IMEI to prevent corruption.
dont feel to bad mac your not alone. quick question what recovery did you flash cwm touch? twrp
deeznutz1977 said:
dont feel to bad mac your not alone. quick question what recovery did you flash cwm touch? twrp
Click to expand...
Click to collapse
We need to focus on finding what is causing this so it can be avoided. It seems to be related to flashing a recovery. Please post any details that we can use to find a pattern.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
its a known issue with all of the lte sgs 3's. backing up /efs wont help as there is no nv_data.bin which contains the imei number.
heres an ongoing thread about it http://forum.xda-developers.com/showthread.php?p=28710945
mobilehavoc said:
We need to focus on finding what is causing this so it can be avoided. It seems to be related to flashing a recovery. Please post any details that we can use to find a pattern.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Bump...a lot of people don't know about backing up their IMEI. This post should be stickied or something.
mobilehavoc said:
We need to focus on finding what is causing this so it can be avoided. It seems to be related to flashing a recovery. Please post any details that we can use to find a pattern.
Click to expand...
Click to collapse
I've flashed half a dozen CWM recovery versions so far and haven't "lost my imei" yet, and don't see why it would.
(FWIW, I'm currently using http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.7-d2att.img for ATT and simply dd'd it over partition 18 like all the rest. CWM-flashable versions shouldn't make any difference, though)
zmore said:
I've flashed half a dozen CWM recovery versions so far and haven't "lost my imei" yet, and don't see why it would.
(FWIW, I'm currently using http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.7-d2att.img for ATT and simply dd'd it over partition 18 like all the rest. CWM-flashable versions shouldn't make any difference, though)
Click to expand...
Click to collapse
DD is much safer as you're just doing a block copy from one device to the other so it's a kernel level copy that is pretty safe as long as you're targeting the right partition. However flashing things could go wrong and it could overwrite a partition or unmount it or something that could lead to these issues
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Okay so I have T-Mobile. I rooted using Odin. I installed cwm via Odin. On the 23rd of last month. What caused me to lose imei was that I flashed an updated cwm via Rom manager. The cwm I.flashed was the one that wouldn't let you restore any back ups from your back up restore file. But I flashed the aokp release 3 as well..I did a complete wipe. Then installed from as card. Then had no signal
Sent from my SGH-T999 using Tapatalk 2
MacTheRipperr said:
Okay so I have T-Mobile. I rooted using Odin. I installed cwm via Odin. On the 23rd of last month. What caused me to lose imei was that I flashed an updated cwm via Rom manager. The cwm I.flashed was the one that wouldn't let you restore any back ups from your back up restore file. But I flashed the aokp release 3 as well..I did a complete wipe. Then installed from as card. Then had no signal
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I lost mine when i pushed the clockworkmod touch then flashed it then aokp. btw i still have calls and edge
Is this a carrier specific issue?
Sent from my SCH-I535 using xda app-developers app
I did pretty much the same exact thing.
Sent from my SGH-T999 using Tapatalk 2
MacTheRipperr said:
Okay so I have T-Mobile. I rooted using Odin. I installed cwm via Odin. On the 23rd of last month. What caused me to lose imei was that I flashed an updated cwm via Rom manager. The cwm I.flashed was the one that wouldn't let you restore any back ups from your back up restore file. But I flashed the aokp release 3 as well..I did a complete wipe. Then installed from as card. Then had no signal
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Did you flash CWRT 5.8.4.7? I'm still on 5.8.4.5 and have flashed many things without losing my IMEI. Could the new CWR be the source of the problem?
Sent from my SGH-T999 using xda premium
I had the cwm used in the very first root method. I updated to the one right before touch and bam everything was gone.
Sent from my SGH-T999 using Tapatalk 2
Related
For some month's ago i had a Galaxy S Plus and i liked it, but i wanted to flash a custom ROM on it. So i updated it with Odin to the newest stock firmware, and i innstalled Clockworkmod so i could flash a custom ROM.
So i flashed the custom ROM (MoonRom) on it using AROMA innstaller and it went successfully. And i used the ROM for one day, and it was fast, and so on, and had a funny sound when u pressed on the dialer keypad, like a water drop sound
I liked the ROM, but i wanted it back to stock (warranty reasons) .So i put to phone into download mode and i used Odin + the pit file and flashed it back to stock firmware and wiped out and formatted everything on it using recovery mode.
And later i used the phone dialer, and the keypad sounds from the custom ROM was still there, after i reflashed it????
I was extremely confused i flashed a billion stock firmwares on there and that water drop sound when u tapped the dialer keypad was still there. I had formatted it and everything and it was still there after flashing back????
I know own a Galaxy S II, and i will never flash somethign custom on there i am afraid that if i do that and then reflash back. Something on the old rom will ble left.
After that i gave my mom the phone. And i was extremly confused...
Maybe the keypad sound is left on the sd card?
Sent from my WT19i using xda premium
xdevilium said:
Maybe the keypad sound is left on the sd card?
Sent from my WT19i using xda premium
Click to expand...
Click to collapse
i flashed it with and without the sd card. But it was still there...
CWM won't always be able to wipe everything, on my phone it can't wipe the boot partition
Sent from my WT19i using xda premium
Please hit the thanks button if I helped
I will still not flash anything custom on there...
Eirik2306 said:
I will still not flash anything custom on there...
Click to expand...
Click to collapse
As you wish
Sent from my WT19i using xda premium
Please hit the thanks button if I helped
Strange, but I wouldn't give up Roms just because of a water drop sound. To each his own.
Agree with the guy above me. Stock, the phone has way too much bloatware.
xdevilium said:
CWM won't always be able to wipe everything, on my phone it can't wipe the boot partition
Sent from my WT19i using xda premium
Please hit the thanks button if I helped
Click to expand...
Click to collapse
So do you know any way to get the keypad sounds back??? And also the keyboard sounds are also left from the custom ROM.
If you flashed back using Odin then its impossible that the sounds remain.
I can make you a flash package that should enable the stock samsung sounds if you really want it? You just have to tell me what firmware you will be running i.e. Gingerbread or ICS?
Jarmezrocks said:
If you flashed back using Odin then its impossible that the sounds remain.
I can make you a flash package that should enable the stock samsung sounds if you really want it? You just have to tell me what firmware you will be running i.e. Gingerbread or ICS?
Click to expand...
Click to collapse
Hello I sold the phone to my mom, and she dont want me to play around with her phone. But thanks for suggestion
I made this post just to try sort things out why the old rom sounds is still there, and i used ODIN + the pit filed when i flashed the Galaxy S Plus.
Eirik2306 said:
I made this post just to try sort things out why the old rom sounds is still there, and i used ODIN + the pit filed when i flashed the Galaxy S Plus.
Click to expand...
Click to collapse
User error. If you used odin, nothing will remain from a previous flash.
Sent from my SPH-D700 using XDA
Thanks for this, please, share more of your opinions -___-
Sent from my GT-I9100 using XDA
Don't mean to be rude or anything but why should we care whether you will or won't flash another custom rom again?
Sent from my GT-I9100 using xda premium
On a place were people come to FLASH ...................
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SGH-I777 using xda premium
beston94 said:
Don't mean to be rude or anything but why should we care whether you will or won't flash another custom rom again?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
This.
Edit:By the way my uncle is a giraffe,hope it helped.
Sent from my GT-I9100 using Tapatalk 2
Flashing roms, tinkering, working out issues and resolving them, making device better is what XDA is about and where the enjoyments is, If you dont like that or dont have the aptitude, patience to learn why are you even here or have a Android device?
My suggestion is to get a Nokia 3310 or an iPhone, Or at least do not come here and bore us with stories about why you dont want to flash your phone.
trell959 said:
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
LMFAO
----------------------
GTI9100
HydrogenICS 12.05
fluxi xx.01_rc4
Cool story bro , now please give me back my 2 mn lost on this useless topic.
I want to uninstall clockwork completely, remove all instances of it and move to twrp. What is the best way I can do this? right now I see that cwr is using roughly 3gb of my storage (8gb) model, so I need to know the correct procedure to removing it. Thanks
Sent from my Nexus 7 using Tapatalk 2
ikn0wagh0st said:
I want to uninstall clockwork completely, remove all instances of it and move to twrp. What is the best way I can do this? right now I see that cwr is using roughly 3gb of my storage (8gb) model, so I need to know the correct procedure to removing it. Thanks
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
download the twrp package and flash it with fastboot.
Alternatively: go to twrp thread, follow directions.
thracemerin said:
download the twrp package and flash it with fastboot.
Alternatively: go to twrp thread, follow directions.
Click to expand...
Click to collapse
I know how to install twrp, I just want to know the correct process to remove all instances of clockwork mod from my device so I can free up some space
Sent from my Nexus 7 using Tapatalk 2
ikn0wagh0st said:
I know how to install twrp, I just want to know the correct process to remove all instances of clockwork mod from my device so I can free up some space
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
CWM lives in the recovery partition which doesn't show up as part of your storage, how is it using up so much space?
thracemerin said:
CWM lives in the recovery partition which doesn't show up as part of your storage, how is it using up so much space?
Click to expand...
Click to collapse
No idea..I have one backup and its taking up almost 3 gigs of space.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using Tapatalk 2
ikn0wagh0st said:
No idea..I have one backup and its taking up almost 3 gigs of space.
<clip>
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
That's nandroid backups, those have nothing to do with CWM other than you made them with it, just delete the folder. CWM itself is exactly 6635520 bytes and isn't on a partition you can look at in a file explorer.
cool. I just installed twrp, deleted the clockwork folder and freed up a bunch of space. I have no idea why clockwork was taking up so much space. I had one backup. That's it. My twrp backup is 500megs.
Sent from my Nexus 7 using Tapatalk 2
ikn0wagh0st said:
cool. I just installed twrp, deleted the clockwork folder and freed up a bunch of space. I have no idea why clockwork was taking up so much space. I had one backup. That's it. My twrp backup is 500megs.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
No Idea, there have been some odd things reported with the new v6 versions of CWM, could be some sort of bug. It sounds almost like it backed everything up 2 or 3x in 1 backup based on my rough math.
My back up is 20 mb, is that wrong
Sent from my Nexus 7 using Tapatalk 2
desiresiscool said:
My back up is 20 mb, is that wrong
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Sounds like it was never able to finish. I would re-do that backup
Sent from my Nexus 7 using XDA Premium HD app
desiresiscool said:
My back up is 20 mb, is that wrong
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Yes your backup should definitely be larger than that. I have several I will open them and see what size they are, I'm guessing 500 mb to 1 GB approximately. Will update soon with the total.
Sent from my ADR6425LVW using xda premium
desiresiscool said:
My back up is 20 mb, is that wrong
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
clintkev251 said:
Sounds like it was never able to finish. I would re-do that backup
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Your backup should be the total size of the stuff in your device - the compression, i'm not sure how heavy the compression CWM uses for Nandroids is, but 20mb is way too small to be the full thing.
I recently let the ota update of mf3 on my galaxy s4 I then proceeded to root it only to get the wifi tether Apk but was unable to do so. I ultimately I noticed the device only shows roughly 800mbs of storage available with only 8 gbs used including the 6.38gb system memory I have a 64gb micro sd with Everything on it instead of on my devices storage in the graph under storage in settings free space is half of the graph although in its own category it only shows 800mbs free
Sent from my SAMSUNG-SGH-I337 using xda premium
Have you tried factory reset?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I was told I could not factory reset after rooting mf3 that it would or I guess could brick the phone and then there would be nothing I could do to recovery at that point.
Sent from my SAMSUNG-SGH-I337 using xda premium
Okay then, try using any file explorer and look for huge files, etc.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I use Smanager and there is NOTHING on this phone I've been through every file and I can't seem to find a thing
Sent from my SAMSUNG-SGH-I337 using xda premium
Rooting does not mess with your storage. You did something wrong
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can see that the available space is only 765mb but up top it appears to have a ton of available space
Sent from my SAMSUNG-SGH-I337 using xda premium
Rab2cab said:
View attachment 2219967
You can see that the available space is only 765mb but up top it appears to have a ton of available space
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
That's your internal sd card. Android uses a bunch of it.
I don't think it's the root that did it it's just the root keeping me from doing a factory reset I had root before with mdl and at one point been running the Google edition rom then used Odin to go back to factory had root again but just stuck with touch wiz after that I'm assuming something got gunked up somewhere that is keeping an extra system software that I can't seem to get to or remove since at no point since having the phone did I even have mov/pics/music/apps ect to account for all the missing storage
Sent from my SAMSUNG-SGH-I337 using xda premium
Never should have gotten the ota. Now you have to live with a neutered system.
Yeah I Def regret letting the ota go through but I'm stuck for now the misc files showing 6.38gb is the the system files im still missing oh like, 6+gb somewhere
Sent from my SAMSUNG-SGH-I337 using xda premium
Does anyone know for sure that if I do a factory reset through the phone that it will screw it up once I gained root I did nothing else I didn't try and make a back up or recovery
Sent from my SAMSUNG-SGH-I337 using xda premium
Every phone that I have factory reset with root has just lost root. Where did you read that doing so will brick you?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
I read on here that once you root the new mf3 version there is no current way to go back to stock
Is that not true? I don't want to try and screw myself
Sent from my SAMSUNG-SGH-I337 using xda premium
Hmm... I will do some research into this. It just sounds a bit off to me.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Rab2cab said:
I was told I could not factory reset after rooting mf3 that it would or I guess could brick the phone and then there would be nothing I could do to recovery at that point.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Doing a factory reset on your phone has nothing to do with the root, it will not brick it. I know this from my own experience with the MF3. You will simply just lose root. Period.
OK great does it matter that before I did the ota update that I had twrp recovery and when the phone boots up it still has the custom boot screen with the unlocked lock?
Sent from my SAMSUNG-SGH-I337 using xda premium
Rab2cab said:
OK great does it matter that before I did the ota update that I had twrp recovery and when the phone boots up it still has the custom boot screen with the unlocked lock?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
It shouldn't matter from what I have read. I'm not sure myself, but again based on what I read you should be just fine.
Well its official I cannot retire back to factory through the phone I tried under the account-restore/backup option and reboot with volume up both throw it in Odin mode saying cannot boot normal blah blah blah leaving me to boot volume down to get phone to reboot properly I guess I'll have to wait
Sent from my SAMSUNG-SGH-I337 using xda premium
Hi guys, new to the forum and a total noob rooting and custom roms etc. I have a note 3 SM-N9005 which i have just "successfully?" rooted with supersu flashed with clockwork recovery and am now running CM11 I installed the google apps package and it all seems to be running well apart from a few glitches. Does all this sound right? And how does it update? I'm aware that I am not running an official CM version but when that becomes available how do i get that running? Do I have to go through the process again?
Thanks in advance for the first of many stupid questions
Sent from my SM-N9000 using Tapatalk
Sent from my SM-N9000 using Tapatalk
You said you have SM-N9005 but the signature is SM-N9000. What is the problem.
Cyanogen build is reporting wrong is all. Nothing to worry about. Build.prop just needs changed... Now to answer the question. .
If you stay on the base you're on now you can dirty flash new builds over. But if you are changing cm from different devs you'll need to wipe and install from scratch.
You're better wiping and installing from scratch as it tends to solve 99% of issues.
Sent from my SM-N9005 using XDA Premium 4 mobile app
radicalisto said:
Cyanogen build is reporting wrong is all. Nothing to worry about. Build.prop just needs changed... Now to answer the question. .
If you stay on the base you're on now you can dirty flash new builds over. But if you are changing cm from different devs you'll need to wipe and install from scratch.
You're better wiping and installing from scratch as it tends to solve 99% of issues.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the response! I followed the instructions outlined in this post
ibtimes.co.uk/android-4-4-2-kitkat-arrives-galaxy-note-3-via-cyanogenmod-11-rom-how-install-1431052
I used the rom in the download link and used the programs they suggested to install it. What is the version of the rom they have listed?
Sent from my SM-N9000 using Tapatalk
Sirnick2 said:
Thanks for the response! I followed the instructions outlined in this post
ibtimes.co.uk/android-4-4-2-kitkat-arrives-galaxy-note-3-via-cyanogenmod-11-rom-how-install-1431052
I used the rom in the download link and used the programs they suggested to install it. What is the version of the rom they have listed?
Sent from my SM-N9000 using Tapatalk
Click to expand...
Click to collapse
This build is the one that Ibtimes listed
EDIT: Also for builds with some additional features, there is temasek's build, ProBAM and BAM - but obviously it is up to you which one you choose and to which one you prefer. - Pong's build was the first main build here at xda, and he's been doing daily updates to fix errors, a lot of people seem happy and content with that build right now, so unless you are looking for something different, you could stay on it without any major issues
radicalisto said:
This build is the one that Ibtimes listed
EDIT: Also for builds with some additional features, there is temasek's build, ProBAM and BAM - but obviously it is up to you which one you choose and to which one you prefer. - Pong's build was the first main build here at xda, and he's been doing daily updates to fix errors, a lot of people seem happy and content with that build right now, so unless you are looking for something different, you could stay on it without any major issues
Click to expand...
Click to collapse
Thanks. I had a look at PROBAM and flashed that on. I really like it. The only problem I had was with instruction number 7 select recommended kernel for first install.
What does this mean? The ROM is working fine and I couldn't find an option on cwm recovery. Lol I can just imagine the heads shaking reading this
Thanks
Sent from my SM-N9000 using Tapatalk
Sirnick2 said:
Thanks. I had a look at PROBAM and flashed that on. I really like it. The only problem I had was with instruction number 7 select recommended kernel for first install.
What does this mean? The ROM is working fine and I couldn't find an option on cwm recovery. Lol I can just imagine the heads shaking reading this
Thanks
Sent from my SM-N9000 using Tapatalk
Click to expand...
Click to collapse
Can't select a kernel on installing that. Well not that I seen anyway, it includes a custom CM kernel - wouldn't worry about it too much.
But when custom kernels for CM do come round, flashing is pretty simple, just boot into recovery and flash the .zip. -- just be careful setting voltages etc cause what works for others won't work for you sometimes and may bootloop your phone. (it can be fixed) - As for the shaking heads, I wouldn't worry too much, we all started somewhere
Cheers radicalisto you've been a big help
Sent from my SM-N9000 using Tapatalk
Also since I've started playing around with rooting and flashing my phone displays the wrong model number SM-N9000 instead of 9005. What is up with that?
Sent from my SM-N9000 using Tapatalk
Sirnick2 said:
Also since I've started playing around with rooting and flashing my phone displays the wrong model number SM-N9000 instead of 9005. What is up with that?
Sent from my SM-N9000 using Tapatalk
Click to expand...
Click to collapse
This question i've asked in the post #2
Sent from my Nexus 7 using Tapatalk
vndnguyen said:
This question i've asked in the post #2
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Any ideas?
Sent from my SM-N9000 using Tapatalk
Sirnick2 said:
Any ideas?
Sent from my SM-N9000 using Tapatalk
Click to expand...
Click to collapse
Go to Play Store, search for an app Check Fus, run it and post the screenshot. I will tell you what model do you have
Or use my app to check for the Model: Phone INFO
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N9000 using Tapatalk
Your phone is likely black N9005 for Australia XSA region
May be something wrong with your build.prop file. Check it and modify as need
Sirnick2 said:
Sent from my SM-N9000 using Tapatalk
Click to expand...
Click to collapse
Use my app Phone INFO to check for the phone info instead.
Thanks
Sent from my SM-N9000 using Tapatalk
Sirnick2 said:
Thanks
Sent from my SM-N9000 using Tapatalk
Click to expand...
Click to collapse
So what info did you get?
Can you post some screenshots from my app?
Thanks.
Sent from my Nexus 7 using Tapatalk
Sorry vngnguyen, I'm not to concerned with it any more
Sent from my SM-N9000 using Tapatalk
Looking for stock rom. I'm bricked with download mode stuck at bootlogo. I made a backup prior bit cannot flash anything at all. I tried flashing .pit file still nothing. If I flash pit file with stock rom, I may get somewhere?
Sent from my SM-G920T using Tapatalk
adrwill2000 said:
Looking for stock rom. I'm bricked with download mode stuck at bootlogo. I made a backup prior bit cannot flash anything at all. I tried flashing .pit file still nothing. If I flash pit file with stock rom, I may get somewhere?
Sent from my SM-G920T using Tapatalk
Click to expand...
Click to collapse
I had the same problem on a different phone if you go into the TW RP or CWM you should be able to do a factory reset that's the only way I was able to fix my other phone not being able to flash anything after brick so give that a shot and let me know what happens
DanHutchins said:
I had the same problem on a different phone if you go into the TW RP or CWM you should be able to do a factory reset that's the only way I was able to fix my other phone not being able to flash anything after brick so give that a shot and let me know what happens
Click to expand...
Click to collapse
I can't get Into recovery mode either. It gets stuck at the Grand prime splash screen with download mode in the upper left hand corner.
Sent from my SCH-I545 using Tapatalk
There is another thread on this phone not sure if it will help still unable to get a stock rom for this version of the phone
I seen someone else shared a link to a stock rom on another thread on here..
NullByte04 said:
I seen someone else shared a link to a stock rom on another thread on here..
Click to expand...
Click to collapse
They did but not for the SM-S920L. There is still no rom including stock for this phone.
I'm not sure what that rom is. It was posted in the dev forum and op offered almost no details. All I know is that the file name is SM-S920L3.tar and it weighs in at 1.4GB.
bfoos said:
I'm not sure what that rom is. It was posted in the dev forum and op offered almost no details. All I know is that the file name is SM-S920L3.tar and it weighs in at 1.4GB.
Click to expand...
Click to collapse
In that case they must have put it up just recently. Things are starting to look up for us after all.
Maybe, I'm not going to be the guinea pig here and risk my phone on some unknown rom without a custom recovery available to backup and restore my phone should something go wrong.
bfoos said:
Maybe, I'm not going to be the guinea pig here and risk my phone on some unknown rom without a custom recovery available to backup and restore my phone should something go wrong.
Click to expand...
Click to collapse
I agree....
DanHutchins said:
I agree....
Click to expand...
Click to collapse
Anyone tried it yet...?
Sent from my SM-S920L using Tapatalk
Oh and i got mine running again. Must have been bad connection. I switched to the laptop and bam, stock recovery installed. Sometimes it's the little things.
Sent from my SM-S920L using Tapatalk
adrwill2000 said:
Anyone tried it yet...?
Sent from my SM-S920L using Tapatalk
Click to expand...
Click to collapse
I am in same boat as you not wanting to be the guinea pig.
I happened to pick up a 2nd device...I'll try it if someone can provide a link?
Sent from my SM-S920L using Tapatalk
adrwill2000 said:
I happened to pick up a 2nd device...I'll try it if someone can provide a link?
Sent from my SM-S920L using Tapatalk
Click to expand...
Click to collapse
Here you go...
http://forum.xda-developers.com/gra...-download-sm-s920l-straight-talk-usa-t3265004
Cool. I'm downloading right now. I'll let you guys know how it goes.
Sent from my SM-S920L using Tapatalk
Anyone have any news on recovery and custom ROM for this phone?
adrwill2000 said:
Cool. I'm downloading right now. I'll let you guys know how it goes.
Sent from my SM-S920L using Tapatalk
Click to expand...
Click to collapse
Thanks, man! I'm having a few issues that I can live with with my phone, but if this works ok, I might just flash it. Oh, and I spoke with a few Straight Talk CS reps and they say that neither Tracfon, nor Samsung are going to release a stock ROM for 5.0.2. Perhaps some day we'll get an update to 5.1.1.
Ok so I it flashed in about 3 minutes for me with a pass. I noticed a set bit warranty: cache and system. I pulled the battery and then powered back on and got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-S920L using Tapatalk
adrwill2000 said:
Ok so I it flashed in about 3 minutes for me with a pass. I noticed a set bit warranty: cache and system. I pulled the battery and then powered back on and got this:
Sent from my SM-S920L using Tapatalk
Click to expand...
Click to collapse
adrwill2000 said:
I factory reset and wiped cache and tried it again and got the same results. However this time after wiping cache it did boot up but there is one problem as you shall see here:
this is for a core prime. SM-G360M international model.
Sent from my SM-S920L using Tapatalk
Click to expand...
Click to collapse
Edit: model number