Related
Hello
I am totally new to android, i just bought my s3 couple of days ago.
There are still some questions where i cant find the answers.
I just rooted my phone, odin, cwm, super SU no problem, i did a nandroid backup just in case. Backed up some apps with titanium backup.
I thought about backing up my efs. But i cant find the option in cwm.
Now i read something about bricking. And apparently there are soft and hardbricks. So softbricks are the bricks, which wouldnt let you start android but let you access the recovery mode right ?? And hard bricks are the bricks where the phone doesnt respond to anything.
I want to know what causes which brick. Is it true that the s3 has a separate partition only for the download mode, which makes it really hard to hardbrick since you cant mess with this partition? And why do some people still encounter hardbricks, when for example the flash custom roms ?
Shadowspsp said:
Hello
I am totally new to android, i just bought my s3 couple of days ago.
There are still some questions where i cant find the answers.
I just rooted my phone, odin, cwm, super SU no problem, i did a nandroid backup just in case. Backed up some apps with titanium backup.
I thought about backing up my efs.
But i cant find the option in cwm.
>>>>
Nitrality app on the market many custom roms do an auto backup of EFS .
Now i read something about bricking. And apparently there are soft and hardbricks. So softbricks are the bricks, which wouldnt let you start android but let you access the recovery mode right ?? And hard bricks are the bricks where the phone doesnt respond to anything.
I want to know what causes which brick. Is it true that the s3 has a separate partition only for the download mode, which makes it really hard to hardbrick since you cant mess with this partition? And why do some people still encounter hardbricks, when for example the flash custom roms ?
Click to expand...
Click to collapse
Softbrick generally firmware or files conflict but more usual is not following the instructions . Mostly recoverable by recovery mode or download mode .
Hardbrick no recovery and no download mode often a NAND problem
Cause is mostly users totally ignoring the instructions and flashing the wrong firmware for the phone or messing with PIT files .
Custom rom it should be almost impossible to hard brick a phone by flashing one
However it becomes more common as more and more users want an instant fix and refuse to read the instructions and its beyond them to read the custom rom thread for known faults fixes etc .
jje
Shadowspsp said:
Hello
I am totally new to android, i just bought my s3 couple of days ago.
There are still some questions where i cant find the answers.
I just rooted my phone, odin, cwm, super SU no problem, i did a nandroid backup just in case. Backed up some apps with titanium backup.
I thought about backing up my efs. But i cant find the option in cwm.
Now i read something about bricking. And apparently there are soft and hardbricks. So softbricks are the bricks, which wouldnt let you start android but let you access the recovery mode right ?? And hard bricks are the bricks where the phone doesnt respond to anything.
I want to know what causes which brick. Is it true that the s3 has a separate partition only for the download mode, which makes it really hard to hardbrick since you cant mess with this partition? And why do some people still encounter hardbricks, when for example the flash custom roms ?
Click to expand...
Click to collapse
I mess around with my android phones a lot but never had a soft or hard brick. My old nexus one had a soft brick after repartitioning the internal memory. The only hard brick I heard of with the S3 was someone who flashed a wrong firmware on his us/canadian version of the S3 (flashed rom which was intended for the international version). Others than that you need to really try hard to hard-brick your phone I guess
Shadowspsp said:
Hello
I am totally new to android, i just bought my s3 couple of days ago.
There are still some questions where i cant find the answers.
I just rooted my phone, odin, cwm, super SU no problem, i did a nandroid backup just in case. Backed up some apps with titanium backup.
I thought about backing up my efs. But i cant find the option in cwm.
Now i read something about bricking. And apparently there are soft and hardbricks. So softbricks are the bricks, which wouldnt let you start android but let you access the recovery mode right ?? And hard bricks are the bricks where the phone doesnt respond to anything.
I want to know what causes which brick. Is it true that the s3 has a separate partition only for the download mode, which makes it really hard to hardbrick since you cant mess with this partition? And why do some people still encounter hardbricks, when for example the flash custom roms ?
Click to expand...
Click to collapse
Install Rom Toolbox from Google Play to backup you EFS folder, it will make 2 files (1 .img and 1 .tar file). Store both files on to your pc for safekeeping.
JJEgan said:
Softbrick generally firmware or files conflict but more usual is not following the instructions . Mostly recoverable by recovery mode or download mode .
Hardbrick no recovery and no download mode often a NAND problem
Cause is mostly users totally ignoring the instructions and flashing the wrong firmware for the phone or messing with PIT files .
Custom rom it should be almost impossible to hard brick a phone by flashing one
However it becomes more common as more and more users want an instant fix and refuse to read the instructions and its beyond them to read the custom rom thread for known faults fixes etc .
jje
Click to expand...
Click to collapse
Thanks !
There is one thing i still dont really get, you said some users flash a wrong rom for their phone can cause a hardbrick.
This root method simply installs ClockworkMod Recovery to the recovery partition and installs Superuser zip file, very safe to do. *With Galaxy S2, recovery partition was part of the kernel and was a bit dangerous but with Galaxy S3, Samsung has made recovery parition separate from the kernel, making it much safer just like how Galaxy Nexus works
Click to expand...
Click to collapse
So why does flashing a wrong rom cause a hardbrick, does installing a custom rom changes files in this separate partition? If the recovery partition is untouched, doesnt it mean you can always access recovery mode even if you flashed some junk onto your phone?
Shadowspsp said:
Thanks !
There is one thing i still dont really get, you said some users flash a wrong rom for their phone can cause a hardbrick.
So why does flashing a wrong rom cause a hardbrick, does installing a custom rom changes files in this separate partition? If the recovery partition is untouched, doesnt it mean you can always access recovery mode even if you flashed some junk onto your phone?
Click to expand...
Click to collapse
No, if people flash the wrong PIT file it messes up the partitions on the phone and they are no longer accessible. That is called a hard brick. Can only be fixed in a service center. In post 4 is info about backup of the EFS folder.
Shadowspsp said:
Thanks !
There is one thing i still dont really get, you said some users flash a wrong rom for their phone can cause a hardbrick.
So why does flashing a wrong rom cause a hardbrick, does installing a custom rom changes files in this separate partition? If the recovery partition is untouched, doesnt it mean you can always access recovery mode even if you flashed some junk onto your phone?
Click to expand...
Click to collapse
Wrong rom its usually flashing non SGS3 firmware or flashing SGS3 firmware on USA version.
Taking firmware from another forum and flashing it in error .
As said very very hard to hard brick this phone .
jje
Shadowspsp said:
I want to know what causes which brick
Click to expand...
Click to collapse
The only real type of brick is hardbrick. the expression soft brick was invented for situations where you cannot access recovery but are able to restore access to recovery with download mode, or some sort of trick.
If something goes wrong, you can end up with either type of brick. There is no way to predict what will happen if you give the phone a reason to brick, really. In general the main causes for bricking are:
1) Flashing stuff that is not right for your exact phone model
A mistake that has been made by a number of USA SGS3 users, who wanted a ROM made for the international model. Unfortunately the result was usually; Bricked, as in hard brick. To prevent this is is smart to familiarize yourself with the manufacturer version number (in our case GT-i9300 or GT-i9300T) with all phones you ever want to flash anything on, and check if the code corresponds.
It's the same **** in every model range. Flash something for another version and you're in trouble.
2) Corrupted downloads
Sometimes http file transfer doesn't get the files you want to flash across error-free. Usually, this will only give weird errors, for instance a bootloop. Sometimes you may end up with softbrick. If you have a really bad day; Brick. To prevent this it is very important to look for the MD5 checksum of each file, and check if the file is still exactly the same at your end. There is a free app in the market that allows you to do this while booted in android, so you can easily check it right after any download is finished.
3) Powerloss while flashing
Again, usually you can revert to working order with download mode. Still it is very risky. To minimise the chance for this to happen, make sure you only start flashing with your battery at least about half full, and have the battery installed complete with cover, etc. Some people use 30% as the limit. It depends a bit on the size of the ROM you want to backup and/or flash. Backing up and flashing one of those nice 700MB samsung roms might eat into your battery quite a bit.
There may be more reasons but these are afaik the 3 main ones. All easily preventable.
Flashing ROMs for years and found it safe to do so.
Until last week...
there is another hardbrick which I actually experienced on my second device, a Galaxy S2:
http://forum.xda-developers.com/showthread.php?t=1756242
http://www.xda-developers.com/android/hard-brick-bug-on-galaxy-s-ii-and-note-leaked-ics-kernels/
Unsafe kernels/libraries on newer ICS-Roms are obviously able to destroy the system partitions, including the bootmanager, so a hardwarechange is necessary to revive the phone.
Until now, no information available, if our S3 is immune against this one. Several other devices are affected!
New here. (also apologies for probable duplicate topic)
I've rooted a phone in the past with no problem. This time round was with an S2, and I flashed an insecure kernel on it, got a green pass on Odin however it's now stuck on the boot screen with the yellow triangle.
I can access recovery mode and download mode but it will never boot properly, always stuck on the yellow triangle. What's the best course of action from here?
Need a lot of help with this guys as I'd rather not have a bricked phone ><
ikradex said:
New here. (also apologies for probable duplicate topic)
I've rooted a phone in the past with no problem. This time round was with an S2, and I flashed an insecure kernel on it, got a green pass on Odin however it's now stuck on the boot screen with the yellow triangle.
I can access recovery mode and download mode but it will never boot properly, always stuck on the yellow triangle. What's the best course of action from here?
Need a lot of help with this guys as I'd rather not have a bricked phone ><
Click to expand...
Click to collapse
Seriously dude? Use some common sense please and give relevant information on what you have. What model/variant do you have, rom are you on, what kernel have you flashed?
How do you expect anybody to be able to help you if you dont give such basic info???
Are you sure the kernel supports the rom/version you have installed?
ikradex said:
New here. (also apologies for probable duplicate topic)
I've rooted a phone in the past with no problem. This time round was with an S2, and I flashed an insecure kernel on it, got a green pass on Odin however it's now stuck on the boot screen with the yellow triangle.
I can access recovery mode and download mode but it will never boot properly, always stuck on the yellow triangle. What's the best course of action from here?
Need a lot of help with this guys as I'd rather not have a bricked phone ><
Click to expand...
Click to collapse
Maybe because you wiped all data....so...there's no ROM to boot up to.
Try flashing one via Odin
gastonw said:
Maybe because you wiped all data....so...there's no ROM to boot up to.
Try flashing one via Odin
Click to expand...
Click to collapse
Wiping data doesnt wipe rom , It just wipes appdata, ie settings etc. All that happens is a factory reset so when you next boot its back to default. For example you would need to re-enter google account and re-install apss either manually or from a backup.
You can only wipe rom by formatting system partition.
TheATHEiST said:
Wiping data doesnt wipe rom , It just wipes appdata, ie settings etc. All that happens is a factory reset so when you next boot its back to default. For example you would need to re-enter google account and re-install apss either manually or from a backup.
You can only wipe rom by formatting system partition.
Click to expand...
Click to collapse
Thought you had me in ignore.
So there's no way you can wipe your OS via recovery? Good to know that, it's like ROM over ROM then. The new one clears the old one.
gastonw said:
Thought you had me in ignore.
So there's no way you can wipe your OS via recovery? Good to know that, it's like ROM over ROM then. The new one clears the old one.
Click to expand...
Click to collapse
I did have you on ignore but I still see little boxes saying this comment has been ignored etc which was actually more annoying so I removed ignore.
Yes you can wipe OS via recovery but only by formatting system/deleting partition etc. All the "wipe" options do is remove files that have been created by rom like app settings/cache etc.
Your confusion was probably also the reason why you made a big thing in a previous topic about you trying to avoid wiping data, because you thought it wiped rom? :silly:
Wiping data/factory reset in cwm is one of the best ways to get rid of system issues, Its basically like doing a clean install of Windows on a PC. After you have wiped you can simply restore your needed apps from a backup using Titanium Backup. Other things like sms/mms etc can be also backed up easily and contacts will be synced via Google account.
TheATHEiST said:
I did have you on ignore but I still see little boxes saying this comment has been ignored etc which was actually more annoying so I removed ignore.
Yes you can wipe OS via recovery but only by formatting system/deleting partition etc. All the "wipe" options do is remove files that have been created by rom like app settings/cache etc.
Your confusion was probably also the reason why you made a big thing in a previous topic about you trying to avoid wiping data, because you thought it wiped rom? :silly:
Wiping data/factory reset in cwm is one of the best ways to get rid of system issues, Its basically like doing a clean install of Windows on a PC. After you have wiped you can simply restore your needed apps from a backup using Titanium Backup. Other things like sms/mms etc can be also backed up easily and contacts will be synced via Google account.
Click to expand...
Click to collapse
hum...okay.
I actually know what Factory Reset does, I mean..."factory"..."reset", kinda......gives it away.
And yes, it made sense to me that you could wipe the ROM you are on before installing a new one, just like the format c:/s days in win98.
You learn something every day, speaking of which, how come no one recommends noobs to root their device with exynos abuse? It's because they're noobs and wouldn't be able to handle/understand the exploit?
I still don't do factory resets because I don't need to, and I avoid needing to perform it.
TheATHEiST said:
Seriously dude? Use some common sense please and give relevant information on what you have. What model/variant do you have, rom are you on, what kernel have you flashed?
How do you expect anybody to be able to help you if you dont give such basic info???
Are you sure the kernel supports the rom/version you have installed?
Click to expand...
Click to collapse
Thanks for the reply Figured if someone was willing to help me I'd give them the information they wanted.
Have Samsung Galaxy S II (GT-I9100) (couldn't tell you what "variant" it is). I was following this guide. It told me to get an insecure kernel from here. The guide said it didn't really matter which kernel I picked so I picked the first one (GT-I9100_BGKF5_insecure) and used Odin to flash it. Got a green pass and the phone began reboot but it's now stuck on the yellow triangle (the warning message that you've flashed an insecure kernel).
I couldn't tell whether there would be compatibility issues as the thread just seems to be one big list of kernels and nothing else. AFAIK the phone was running ICS.
Looking at the replies, I keep seeing factory reset. Is that a liable option to restore my phone back to its original state. I don't care as long the phone works again. If not can someone run through how to fix my predicament I heard if I can access download and recovery mode I should be able to fix it.
ikradex said:
Thanks for the reply Figured if someone was willing to help me I'd give them the information they wanted.
Have Samsung Galaxy S II (GT-I9100) (couldn't tell you what "variant" it is). I was following this guide. It told me to get an insecure kernel from here. The guide said it didn't really matter which kernel I picked so I picked the first one (GT-I9100_BGKF5_insecure) and used Odin to flash it. Got a green pass and the phone began reboot but it's now stuck on the yellow triangle (the warning message that you've flashed an insecure kernel).
I couldn't tell whether there would be compatibility issues as the thread just seems to be one big list of kernels and nothing else. AFAIK the phone was running ICS.
Looking at the replies, I keep seeing factory reset. Is that a liable option to restore my phone back to its original state. I don't care as long the phone works again. If not can someone run through how to fix my predicament I heard if I can access download and recovery mode I should be able to fix it.
Click to expand...
Click to collapse
Of course, you're not bricked yet.
Before trying your back up, why don't you flash a stock ROM via odin and take a long breath?
This is JB leak.
These are ICS, look for 4.0.3 unbranded.
gastonw said:
Of course, you're not bricked yet.
Before trying your back up, why don't you flash a stock ROM via odin and take a long breath?
This is JB leak.
These are ICS, look for 4.0.3 unbranded.
Click to expand...
Click to collapse
I know this is leading onto another thread but my phone now is having trouble connecting to my computer. Keep getting "USB not recognized" error. Installed/Uninstalled kies & drivers then installed drivers again alone and still won't recognize it
Tried another usb port? another pc/laptop? sure kies is not running in background? reinstalled kies?
Don't worry, your pc WILL see your device.
Sent from the little guy
I'm an android user with a little experience and managed to mess things up beyond my understanding.
I used Odin to root my son's Note and tried to flash a rom using CWM, after making a backup of course. Then after a little research i switched to TWRP. Along the way I tried out a better candidate for his phone.
Somehow, mucking while about, his baseband and IMEI became unknown. I read some posts and tried backup and playing with his EFS folder; but the folder was empty. TWRP backup points are post-incident. I reflashed CWM to try and find the original backup, but none were found.
Is there a way to Odin my way out of this? Or am I the proud owner of a shiny paperweight?
p.s. Does the sim card need to be in while flashing? I let him take it out and use it in a backup phone while i was trying the above repairs.
Thanks in advance for reading this, and any advice you can offer
Hi guys,
Ok so I have managed to get my GT-I9300 (inter) network free stuck in a boot loop, after trying to put it back to stock I somehow lost my EFS folder and now get an error "E: Faild to mount EFS (invalid argument)"........yes everyone face palm as Im another one of them. However I have got a copy of my EFS folder that I made with Ktool, but its at this point im stuck.
Im really sorry to be posting another about this issue but after spending hours searching I can't find an answer, lots about people not having a back up but nothing for those that have.
What i need to know is how do I get the back up onto my phone?
I have the stock firmware and the back up EFS folder, but Im stuck as to what to do to "mount" the EFS and replace all this. I have downloaded EFS prof but the phone won't connect to it, it also won't connect to the Kies package either.
I admit I am a noob and should of stuck with the crayons rather than messing with things that i didn't really know, but its done now and i would really love to get your help (in simple talk if possible).
Rather than someone typing out the instructions again why not follow the guide in general stickies on how to return to stock?
Once the phone boots again you can root and copy the efs backup onto the phoen again.
Cheer, will look there. Hadn't found that section in my search, will give it a go and keep my fingers crossed
boomboomer said:
Rather than someone typing out the instructions again why not follow the guide in general stickies on how to return to stock?
Once the phone boots again you can root and copy the efs backup onto the phoen again.
Click to expand...
Click to collapse
Gone through the stickies, and followed the steps to return to stock. But due to the EFS issue its still stuck in bootloop, I flashed the stock recovery tar and then the stock rom.
Mmmmm I need to get the efs off the pc onto the phone again without having to have the phone boot
Obvious question, did you do a factory reset in recovery? Also, did you go from an EMG rom back to an earlier version when flashing stock?
You shouldn't need to flash a recovery, a stock rom downloaded from sammobile includes everything you need.
The only way to restore the efs folder in recovery would be to flash a custom recovery, like Philz, and then use AromaFM to copy the files to the phone.
Hi, yes tried the reset but it did nothing still stuck on bootloop. Erm EMG?? I had just put "I9300_Omega_v46.1_XXUFME7_md5_1C591CA15E556884E4B6AFC89E5A682F" on and then went back to stock.
Odd, a full stock flashed using odin should solve the efs mounting problem.
Did you remove kies before using odin? Did odin give any errors?
If in any doubt use this guidance to flash your stock rom, read it carefully and follow each step exactly:
http://forum.xda-developers.com/showthread.php?t=1671969
Which stock rom are you trying to flash?
Im using this one BTU-I9300XXEMG4-20130724164355, I didnt remove Kies didn't know that could cause a problem. Thanks for the link will check that over, I'm just a bit gutted that I backed up as always and I'm still getting the issue ahhhhhhh.
boomboomer said:
Odd, a full stock flashed using odin should solve the efs mounting problem.
Did you remove kies before using odin? Did odin give any errors?
If in any doubt use this guidance to flash your stock rom, read it carefully and follow each step exactly:
http://forum.xda-developers.com/showthread.php?t=1671969
Which stock rom are you trying to flash?
Click to expand...
Click to collapse
You my friend are my hero (also the guy that wrote the guide)................followed the steps and the phone has booted no problem......I can not add my imei back with ktool once rooted again!!!!!
Glad to hear it worked, flashing a full stock rom often fixes the imei problem but if not then you have your backup to restore.
Easiest way to root is CF Auto Root, make sure you follow the guide exactly.
boomboomer said:
Glad to hear it worked, flashing a full stock rom often fixes the imei problem but if not then you have your backup to restore.
Easiest way to root is CF Auto Root, make sure you follow the guide exactly.
Click to expand...
Click to collapse
I might just take a break from messing, the misses gives me the dead eye every time I pick the ohone up now :crying:
One last question to you sir, the firmware of the guide has put me on 4.0.4, and its not letting me update off Kies. Is this because the build is old or not official. If I download the most upto date firmware off sammobile will I have to up date the kernal again too??
model number - GT-I9300
Android version - 4.0.4
baseband - I9300xxle8
Kernel version - 3.0.15-554452-user
build number - IMM76D.I9300XXALE8
cheersagain
Kernel is included
Ideally you should have used the guide to flash the EMG4 rom you'd already downloaded. Don't leave it long on that old firmware as it doesn't protect against SDS.
Oh, don't use kies as it's a waste of time.
boomboomer said:
Ideally you should have used the guide to flash the EMG4 rom you'd already downloaded. Don't leave it long on that old firmware as it doesn't protect against SDS.
Oh, don't use kies as it's a waste of time.
Click to expand...
Click to collapse
Well its all gone a bit strange to be honest, after getting the phone to boot finally I went ahead and flashed the newer firmware I9300XXEMG6_I9300PHNEMG2_I9300CEEMG2_HOME.tar.md5 . The phone went straight back to bootloop!!!
So currently re doing what i did to get it running in the first place, problem is that leaves the phone in factory mode and the ktool says it is restoring my efs but it doesnt seem to do anything!
so after more grief off her im stuck again.
I have writen down PDA:ME7 PHONE:ME7 CSC:ME7 (eur) which i think is off the last working firmware but not sure which one it is!
Now you can get the phone to boot the problem is mostly done. You should find several threads in this forum on restoring the efs and factory mode (the two are related) also about bootloops with corrupt efs partition.
Well tried all of what i can and understand, still nothing! Stuck with the 004999010640000/01 imei, its out of factory mode and everything works bar the network connection. Managed to restock and set counter to No, all official and ready for warrenty fix....that is unless anyone has any ideas.
This thread answers all the efs questions, if you have now flashed an EMG stock then the efs partition is probably corrupt. As you have a backup this shouldn't stop you from getting it working.
http://forum.xda-developers.com/showthread.php?t=2393289
In particular, this post:
http://forum.xda-developers.com/showpost.php?p=44734012&postcount=99
boomboomer said:
This thread answers all the efs questions, if you have now flashed an EMG stock then the efs partition is probably corrupt. As you have a backup this shouldn't stop you from getting it working.
http://forum.xda-developers.com/showthread.php?t=2393289
In particular, this post:
http://forum.xda-developers.com/showpost.php?p=44734012&postcount=99
Click to expand...
Click to collapse
Thanks again for all your help, I had followed these as best i could but no joy. I think I've 100% killed it. Like I say managed t get it back to stock and use the fantastic triangle away package....thus phone is as untouched......so swallowed the I told you so pill off her and took it to the service centre (which happens to only be 3miles from my house bonus). They did all the checks and accepted it under warrenty, down side i just have to wait up to two weeks its return!!!
Lots of lessons learnt, I origionally just wanted to delete the bloat ware and got carried away, thinking I was not a noob and some sort of phone god the roming followed.
Thanks again for all your help, I will read so much more about what to do if I do go down this line again.
Hello.
I really didn't want to make a thread but i've been bouncing of dead lnks and failed search results or outdated incorrect info all day and i can't seem to get the information i need. I'm sorry if i haven't done everything i can before this psot but i have rtied, i really have!
My issue:
I have a Samsung Galaxy Ace GT-S5830i which was running so slow it was terrible. I found a nice slimline rom that i read about and was happy to use.
I used Samsung recovery to then run CWM ClockWorkRec5830i, which i used to install 'update' which gave me Superuser access and rooted my phone (i think, if i understand) then i made a backup of my phones stock image, then i used it to wipe the phone, clear cache, and finally install my new rom.
...so far so good.
The rom installed, the phone rebooted, everything was working (really fast and really well, i was VERY pleased) however i have hit my issue:
IMEI data was gone. *#06# showed nothing, so i went back into Samsung recovery, loaded ClockWorkRec5830i and restored my phone back ro original using my backup. The IMEI returned! All was well again, so i got Galaxy Toolbox from Play store, ran it with Superuser access and created a backup of the EFS file.
I returned my phone back to the new rom that i had chosen and again installed Galaxy Toolbox to use the 'restore EFS' option.
The IMEI is still blank using *#06# which has me very confused.
I can open the EFS backup file in Hex workshop and the serial number data is is there. I can use Galaxy Toolkit device info and see the IMEI in there, so i don't understand what i have done wrong for the IMEI not to be showing in the phone.
Can anyone help or educate me please. I do generally want to learn more about why i haven't realised the mistake may.
I love learning this stuff but it can be overwelming sometimes until someone comes along and calls you an idiot and tells you the obvious lol! Please, "I'm an idiot" hehee.
Thankyou
Drew (United Kingdom)
DrewKrew said:
Hello.
I really didn't want to make a thread but i've been bouncing of dead lnks and failed search results or outdated incorrect info all day and i can't seem to get the information i need. I'm sorry if i haven't done everything i can before this psot but i have rtied, i really have!
My issue:
I have a Samsung Galaxy Ace GT-S5830i which was running so slow it was terrible. I found a nice slimline rom that i read about and was happy to use.
I used Samsung recovery to then run CWM ClockWorkRec5830i, which i used to install 'update' which gave me Superuser access and rooted my phone (i think, if i understand) then i made a backup of my phones stock image, then i used it to wipe the phone, clear cache, and finally install my new rom.
...so far so good.
The rom installed, the phone rebooted, everything was working (really fast and really well, i was VERY pleased) however i have hit my issue:
IMEI data was gone. *#06# showed nothing, so i went back into Samsung recovery, loaded ClockWorkRec5830i and restored my phone back ro original using my backup. The IMEI returned! All was well again, so i got Galaxy Toolbox from Play store, ran it with Superuser access and created a backup of the EFS file.
I returned my phone back to the new rom that i had chosen and again installed Galaxy Toolbox to use the 'restore EFS' option.
The IMEI is still blank using *#06# which has me very confused.
I can open the EFS backup file in Hex workshop and the serial number data is is there. I can use Galaxy Toolkit device info and see the IMEI in there, so i don't understand what i have done wrong for the IMEI not to be showing in the phone.
I love learning this stuff but it can be overwelming sometimes until someone comes along and calls you an idiot and tells you the obvious lol! Please, "I'm an idiot" hehee.
Thankyou
Drew (United Kingdom)
Click to expand...
Click to collapse
Don't consider yourself idiot at all lol. You have explained everything so clearly.
Well,
This problem is so much common with this phone. Don't know why !
Many people including me facing this problem.
Sometimes you just reboot your phone and you will see ur IMEI is gone. Reboot again and its back. -_-
Its really strange issue actually.
You already knew all methods to get IMEI back. This is comman issue with this phone. Suffer it.
Maybe @iamareebjamal have figured this prob out.
Sent from my GT-S5830i using Tapatalk 2
The rom i found was great. It performed so much faster, did not take up much of the very limited memory on the handset, it was the perfect solution to my needs but whenever i use it i cannot make any calls etc due to no IMEI (*#06# shows a complete blank box) and i have tried rebooting the phone so so many times, repeating the process of installing the rom again and again and not once can i ever get it to show IMEI in *#06#. I could understand if the EFS backup also showed that the imei had reset or become corrupt, but it looks fine in Hex Workshop, shows up in device info on Galaxy Toolbox app, i just can't conclude anything from it's behaviour.
Using my original phone's backup the IMEI is restored instantly, and i have taken the EFS backup whilst running the phone on it's original state.
Could it be because something is not right in the rom? Is the rom changing something that i could possibly correct myself? Or something in the rom not suitable for my model and version of the GT-S5830i handset (compatibility issue)?
I really want to be able to use this rom and other's seem to be able to use it without issue which just makes me more determined to find the cause and correct my issue. I also see that many people do lose their IMEI and the EFS backup/restore method seems to work perfectly for them, because they seem to have their IMEI turned to blank values when checking in HexWorkshop whereas mine is still showing as expected.
I cannot make sense of this scenario at all lol.
I appreciate ANY and ALL advice
The rom is was trying was MEHDI ROM v2. I am in the United Kingdom using a GT-S5830i on o2 newtwork with no network locks or restrictions.
Make a new backup of your IMEI(make sure it is lost by once or twice rebooting) . And open via Hex Workshop.
If you see your IMEI in there, then reflash stock ROM and flash this Custom ROM without wiping anything.
If it doesn't solve your issue now too
Try restoring the efs partition before Media Scanning starts and Reboot the phone after media scanning is started.
These all are hit and trial methods. I've myself never found a fully satisfying solution
If nothing works, you'll have to try any other ROM.
DrewKrew said:
Hello.
I really didn't want to make a thread but i've been bouncing of dead lnks and failed search results or outdated incorrect info all day and i can't seem to get the information i need. I'm sorry if i haven't done everything i can before this psot but i have rtied, i really have!
My issue:
I have a Samsung Galaxy Ace GT-S5830i which was running so slow it was terrible. I found a nice slimline rom that i read about and was happy to use.
I used Samsung recovery to then run CWM ClockWorkRec5830i, which i used to install 'update' which gave me Superuser access and rooted my phone (i think, if i understand) then i made a backup of my phones stock image, then i used it to wipe the phone, clear cache, and finally install my new rom.
...so far so good.
The rom installed, the phone rebooted, everything was working (really fast and really well, i was VERY pleased) however i have hit my issue:
IMEI data was gone. *#06# showed nothing, so i went back into Samsung recovery, loaded ClockWorkRec5830i and restored my phone back ro original using my backup. The IMEI returned! All was well again, so i got Galaxy Toolbox from Play store, ran it with Superuser access and created a backup of the EFS file.
I returned my phone back to the new rom that i had chosen and again installed Galaxy Toolbox to use the 'restore EFS' option.
The IMEI is still blank using *#06# which has me very confused.
I can open the EFS backup file in Hex workshop and the serial number data is is there. I can use Galaxy Toolkit device info and see the IMEI in there, so i don't understand what i have done wrong for the IMEI not to be showing in the phone.
Can anyone help or educate me please. I do generally want to learn more about why i haven't realised the mistake may.
I love learning this stuff but it can be overwelming sometimes until someone comes along and calls you an idiot and tells you the obvious lol! Please, "I'm an idiot" hehee.
Thankyou
Drew (United Kingdom)
Click to expand...
Click to collapse
May these help you..
As about these issue i do flash a Custom Kernel after flashing Rom with no IMEI Number
So After Flashing any Custom Kernel my IMEI Gets back
You can try it with any kernel
I use to flash Rafael.Baugis Kernel flash both its Modules and E3Boot.img
may be try changing kernel..
try any custom kernel...it helps me every time..
i have wiered problem, i can't use custom kernel on stock rom...or stock kernel on custom rom, both of these combination makes my imei disappear every time.
go to this thread for all the explanation
DrewKrew said:
Hello.
I really didn't want to make a thread but i've been bouncing of dead lnks and failed search results or outdated incorrect info all day and i can't seem to get the information i need. I'm sorry if i haven't done everything i can before this psot but i have rtied, i really have!
My issue:
I have a Samsung Galaxy Ace GT-S5830i which was running so slow it was terrible. I found a nice slimline rom that i read about and was happy to use.
I used Samsung recovery to then run CWM ClockWorkRec5830i, which i used to install 'update' which gave me Superuser access and rooted my phone (i think, if i understand) then i made a backup of my phones stock image, then i used it to wipe the phone, clear cache, and finally install my new rom.
...so far so good.
The rom installed, the phone rebooted, everything was working (really fast and really well, i was VERY pleased) however i have hit my issue:
IMEI data was gone. *#06# showed nothing, so i went back into Samsung recovery, loaded ClockWorkRec5830i and restored my phone back ro original using my backup. The IMEI returned! All was well again, so i got Galaxy Toolbox from Play store, ran it with Superuser access and created a backup of the EFS file.
I returned my phone back to the new rom that i had chosen and again installed Galaxy Toolbox to use the 'restore EFS' option.
The IMEI is still blank using *#06# which has me very confused.
I can open the EFS backup file in Hex workshop and the serial number data is is there. I can use Galaxy Toolkit device info and see the IMEI in there, so i don't understand what i have done wrong for the IMEI not to be showing in the phone.
Can anyone help or educate me please. I do generally want to learn more about why i haven't realised the mistake may.
I love learning this stuff but it can be overwelming sometimes until someone comes along and calls you an idiot and tells you the obvious lol! Please, "I'm an idiot" hehee.
Thankyou
Drew (United Kingdom)
Click to expand...
Click to collapse
Hey, did you solved your problem? i had the same problem once and it was just that the backup made with galaxytoolbox didn't match. So the best solution is to do a backup again and you will have to open the new file and edit it with the HEX editor and input your imei number manually. Here the thread with the info http://forum.xda-developers.com/showthread.php?t=2064034&page=1 and this video is great, but it's in spanish. http://www.youtube.com/watch?v=1kbY0EZYsXE Hope this solves your problem.
I cannot use the galaxy toolbox for my restoring unfortunately as the galaxy toolbox is not working with my current rom, if you know of another program that can help me fix it, i would appreciate it.
Thanks,
Fab
fabiolaec said:
Hey, did you solved your problem? i had the same problem once and it was just that the backup made with galaxytoolbox didn't match. So the best solution is to do a backup again and you will have to open the new file and edit it with the HEX editor and input your imei number manually. Here the thread with the info http://forum.xda-developers.com/showthread.php?t=2064034&page=1 and this video is great, but it's in spanish. http://www.youtube.com/watch?v=1kbY0EZYsXE Hope this solves your problem.
Fab
Click to expand...
Click to collapse
Thanks for the replies, but unfortunately i have not yet resolved the problem.
I have gone over the process again and again, repeating it the same way, trying slightly different ways, the outcome is always the same. Everytime i try i take a EFS backup (taken while the phone is restored to running on it's original stock rom and setup, with the IMEI all working and displaying via *#06#) the EFS file shows the IMEI in Hex Editor. Everytime. It's always there.
Then, as soon as i flash a rom and reboot the phone i have no IMEI. I use the good EFS backup and restore the EFS to the phone (which has the IMEI data intact) but the phone still will not display the IMEI via *#06# and if i check the EFS again it is still showing the IMEI as being in the EFS backup and still good.
So i have no idea why the phone is not seeing the IMEI because apparently it IS still there!
I'm installing roms by using the recovery method to 'apply update', using Samsung basic recovery mode, but could i use the CWM recovery to install? Would that have a different effect? Is it safe to use CWM to install roms as the guide i read said to only install roms using Samsung restore as CWM adds a risk of crashing or bricking the phone?
So many people are able to successfully flash a GT-S5830i and i just do not know enough yet about phone roms to feel confident to do more daring things with different methods for fear of making a critical mistake. So much of the information i have read contradicts itself, and other information neglects to explain certain things or simply assumes you know about bootloaders, CSC files and the like...
I've modified so many gadgets before and am fairly confident with doing such things it's just i can't seem to educate myself correctly over the modifying of these Samsung Android phones.
I just bought a Samsung Galaxy S GT-i9000 today and wanted to remove some of the bloatware so that's my next phone to read up on.
I have been put off a bit because of the issue of losing IMEI. It seems to be a big risk with this model, do other Samsung models have issues with IMEI loss?
Thankyou to all who are taking time to post. I read and appreciate every post, and am enjoying learning about this new topic to me.
Perhaps i shouls restore back to my original working setup, then install the rom using recovery (or via CWM recovery - i have no idea which is safest and the correct method as i read conflicting information) then install the rom without resetting/wiping anything? Would that help?
When i select roms should i be making sure they contain a compatible baseband or something?
I don't understand this area.
DrewKrew said:
Perhaps i shouls restore back to my original working setup, then install the rom using recovery (or via CWM recovery - i have no idea which is safest and the correct method as i read conflicting information) then install the rom without resetting/wiping anything? Would that help?
When i select roms should i be making sure they contain a compatible baseband or something?
I don't understand this area.
Click to expand...
Click to collapse
About recovery use CWM
If you do not wipe then there will some problem occur may be like the phone will not boot after flashing Rom so must do wipe
And about baseband and all don't worry you can use any stock Rom for flashing Roms.
DrewKrew said:
Thanks for the replies, but unfortunately i have not yet resolved the problem.
I have gone over the process again and again, repeating it the same way, trying slightly different ways, the outcome is always the same. Everytime i try i take a EFS backup (taken while the phone is restored to running on it's original stock rom and setup, with the IMEI all working and displaying via *#06#) the EFS file shows the IMEI in Hex Editor. Everytime. It's always there.
Then, as soon as i flash a rom and reboot the phone i have no IMEI. I use the good EFS backup and restore the EFS to the phone (which has the IMEI data intact) but the phone still will not display the IMEI via *#06# and if i check the EFS again it is still showing the IMEI as being in the EFS backup and still good.
So i have no idea why the phone is not seeing the IMEI because apparently it IS still there!
I'm installing roms by using the recovery method to 'apply update', using Samsung basic recovery mode, but could i use the CWM recovery to install? Would that have a different effect? Is it safe to use CWM to install roms as the guide i read said to only install roms using Samsung restore as CWM adds a risk of crashing or bricking the phone?
So many people are able to successfully flash a GT-S5830i and i just do not know enough yet about phone roms to feel confident to do more daring things with different methods for fear of making a critical mistake. So much of the information i have read contradicts itself, and other information neglects to explain certain things or simply assumes you know about bootloaders, CSC files and the like...
I've modified so many gadgets before and am fairly confident with doing such things it's just i can't seem to educate myself correctly over the modifying of these Samsung Android phones.
I just bought a Samsung Galaxy S GT-i9000 today and wanted to remove some of the bloatware so that's my next phone to read up on.
I have been put off a bit because of the issue of losing IMEI. It seems to be a big risk with this model, do other Samsung models have issues with IMEI loss?
Thankyou to all who are taking time to post. I read and appreciate every post, and am enjoying learning about this new topic to me.
Click to expand...
Click to collapse
I'm not sure if you missed this step.
I did efs backup on stock rom and tried to restore with galaxy toolbox on the new rom and IT DIDN'T WORK....
you have to copy your imei number manually (or directly from the sticker) and once you are in the NEW ROM, make a backup of the IMEI. of course if you open it with the hex editor it will be EMPTY.
Then in this new back up file newly created you have to manually input your IMEI number using the HEX EDITOR.
This should work.
Rgds,
Fab
Backup imei of gts5830i
Hi i have just rooted my glaxay ace gts5830i &
want to install custom rom bt i want to first
backup its IMEI bt i don't know much abut
it ....
i heard glaxay toolbox in playstore backup the
IMEI bt in some cases it might no able to
backup ...is there any other way plz tell me i
also tried EFS pro...bt not able to backup bcuz
it didn't show my model name even on
refresh... plz help me to backup its imei...
sahil chandel said:
Hi i have just rooted my glaxay ace gts5830i &
want to install custom rom bt i want to first
backup its IMEI bt i don't know much abut
it ....
i heard glaxay toolbox in playstore backup the
IMEI bt in some cases it might no able to
backup ...is there any other way plz tell me i
also tried EFS pro...bt not able to backup bcuz
it didn't show my model name even on
refresh... plz help me to backup its imei...
Click to expand...
Click to collapse
Don't ask the same question in two different threads.
Galaxy toolbox works almost every time.
Did anyone having a similar issue manage to resolve it or can suggest other steps to follow?
I am having the exact issue but for the life of me can not make the IMEI appear even though galaxy toolbox reports it is fine. Here is my post from another thread, before I found this one.
Flashed ROM, all working fine except as above, no network connection (mobile connection). Wifi, etc all working. IMEI is blank when I do *#06#
Have tried
1. reboots, sim out, reboots, etc
2. tried using galaxy toolbox to backup imei/efs and then restoring after flash. nope no help.
3. tried backing up imei and editing with hex editor but the image already has correct imei. galaxy tool box does report correct imei.
4. just tried flashing rafel kernal using instructions but after doing so, phone does not boot past samsung screen.
5. reflashed back to stock room and crap radio still not working lol
so any suggestions? i need a kernel and then one that works with this rom.
Click to expand...
Click to collapse
Since the above, tried thunderbird kernal and I am still without IMEI.
I would just like to ask. Is it possible, at some point I have deleted EFS partition? Should I be able to see this EFS partition somewhere? Browsing through PC, on SD card or through CW recovery?
My only idea is that I have deleted efs partition so galaxy toolbox has no where to restore to BUT the app itself reports correct IMEI as does the hex value with a backup file.
Ideas, rants and possible suggestions welcome!
Thanks
cyrax.net said:
Did anyone having a similar issue manage to resolve it or can suggest other steps to follow?
I am having the exact issue but for the life of me can not make the IMEI appear even though galaxy toolbox reports it is fine. Here is my post from another thread, before I found this one.
Since the above, tried thunderbird kernal and I am still without IMEI.
I would just like to ask. Is it possible, at some point I have deleted EFS partition? Should I be able to see this EFS partition somewhere? Browsing through PC, on SD card or through CW recovery?
My only idea is that I have deleted efs partition so galaxy toolbox has no where to restore to BUT the app itself reports correct IMEI as does the hex value with a backup file.
Ideas, rants and possible suggestions welcome!
Thanks
Click to expand...
Click to collapse
Follow my restoring guide check my sign.
Hitesh2626 said:
Follow my restoring guide check my sign.
Click to expand...
Click to collapse
Thanks Hitesh but I beleive I have tried all the methods. Check my reply here...
I solved my issue by flashing kernel again...see...
my post