gt-i9300 bootloop after flashing with odin official firmware - Galaxy S III Q&A, Help & Troubleshooting

I have a gt-i9300 with ap I9300BUALE6 cp unknown csc I9300VFGALE6 on android 4.0.4 problem was that i wanted to reflash the software because my sim card/wifi didnt work (doesnt see any wifi networks) also wont see any sd card and baseband was unknown.
Downloaded from sammobile latest firmware for vodafone germany I9300XXUGNH4_I9300VFGGNH2_VD2.zip and i flashed with odin v3.12.7 hit AP box and extracted the firmware zip file, selected the md5 and it flashed succesfully but the phone now is unable to enter on android, im stuck with samsung logo and blue led.
What can i do? I also reflashed again and entered android system recovery <3e> hit wipde data/factory reset and also wipe cache partition but i am still in bootloop. There is an e:failed to mount /efs (invalid argument) error, i had this also with 4.0.4.
Is there any way i can fix this? did i flash the wrong rom? what can i do to bring it to life?

I think the EFS folder is where the imei and MAC address information is located. Do you have a backup of this folder? If not, you may have to have the phone reflashed at a repair shop that can also restore the imei.

i dont have a backup of efs folder.
cant i reflash it without going to a repair shop?

@Zedgor: since you flashed firmware for Germany, this repair-tool might help, at least to get a booting system. You loose your data by repartition and cannot go back to outdated 4.0 afterwards, due to 'new' bootloader.

Related

Phone not booting (Is it soft brick?)

Hei,
I was running 4.3.1 Dirty Unicorns and wanted to flash Smartdroid.
So, flashed Devil recovery and tried to flash the ROM.
It gave me message that there's an error in the zip file.
I was just playing with the options available in the recovery and selected some option, which I don't remember now.
After that, the went into bootloop. "Samsung Galaxy S3 I9300" appears on the screen and the phone reboots again and again.
This loop continued.
The phone could be put in Download mode.
Then, I flashed CWM 6.0.4.4 and flashed 4.1.2, which I downloaded some time back.
It went on well. I could boot the phone and had set it up.
However, I couldn't connect to network.
The IMEI was some default one.
Rooted the phone and tried to restore the backup of efs folder using HC-Ktool.
After restore, when I booted the phone, it didn't boot.
"Samsung Galaxy S3 I9300" appears on the screen and the phone reboots again and again.
I tried flashing the ROM again, CWM again etc etc.
Nothing worked.
In one occasion, after installing CWM 6.0.4.4, I restored from NANDROID backup. Restore was successful.
But, it wouldn't boot.
Same "Samsung Galaxy S3" appears on the screen and the phone reboots again and again.
Once, I flashed Dirty Unicorns ROM from zip via CWM. Still the same.
What is happening and how to solve it?
Any help is greatly appreciated.
Regards,
Babloo
Wipe Data/Factory Reset -> Download mode
Flash latest Android 4.3 from Sammy through Odin, preferably XXUGMK6 or newer.
Hei,
This worked!!!
Thanks.
Why flashing 4.1.2, Dirty Unicorns didn't work and this one worked?
If you can explain, that will be helpful to all.
Now, though the phone is booting, the efs folder is corrupted.
IMEI number is not what it should be.
I have a backup of the efs folder taken using HC-Ktool long back.
So, the ROM on which efs folder was backedup will be different that the ROM I have now. (Does it make any difference?)
Can I just root and restore that efs folder using HC-Ktool?
Thanks for the help!!
Regards,
Babloo
Edit:
If I flash CWM Recovery 6.0.4.4 and restore the NANDROID backup that I took before I started screwing my mobile, will everything be fine?
Sounds like you tried to flash a corrupt file, always check the md5 before you flash.
EFS is totally separate to the rom, format the partition, restore your backup then factory reset should return your imei on the current rom.
Nandroid will not fix the efs, unless you used a custom backup process that included the partition -the default settings would not do this.
Hei,
"format the partition, restore your backup"
For this, can I just root the phone and use Ktool to restore backup?
If you suggest any other procedure, pls give me more info.
-Babloo
Hei,
After the previous post, I could restore my phone from NANDROID backup that I took yesterday, before the whole mess.
After that, I tried to restore the efs folder using HC-Ktool from efs.img.
It gives the message that restore is completed.
But, after reboot, the IMEI remains the same wrong one (the generic 004999...)
The size of efs.img is 20.48 MB.
I tried to restore using the terminal method.
With the command "unmount /efs" I get error message "sh: unmount: not found"
How can I restore the efs and get back my IMEI?
When I tried to "open" the img file in Windows, it couldn't open. It says that the file is corrupted.
Could it have been really corrupted or it is just that Windows is unable to open it?
I restored the efs using the same backup file.
Why is it not working now?
-Babloo
You are trying to skip essential stages and hurry to finish, but your partition is still corrupt -you can't restore anything to a corrupt partition.
Search and read someone who has succeeded doing the same thing, follow their guide exactly.
Hei,
boomboomer said:
You are trying to skip essential stages and hurry to finish, but your partition is still corrupt -you can't restore anything to a corrupt partition.
Search and read someone who has succeeded doing the same thing, follow their guide exactly.
Click to expand...
Click to collapse
I have been searching for a proper procedure to format the efs partition since your post.
Whatever I found didn't work for me.
Can you please point me to any post that you know?
-Babloo
Guys,
Any ideas?
-Babloo

[Q] I9300 Root Problem

Hi,
I have root my Samsung 9300I phone cf-auto-root-i9300 by ODIN v.3.0.7 .While rooting procesess Odin says RESET then it reset my phone than i have shutdown my phone before ODIN "PASS" text showed. Then i have installed CWM latest version with ODIN. I have open CWM and wipe all data after then try to install HD Revulotion ROM but its says bad error. Installing can not be contiune. I think rooting is not done properly because CWM saying rooting is missing. So i cant do anything because i have no OS all of my data wiped. I have stucked. What i have to do ?
Please help.
Try using older ODIN version or search for CF-Root-SGS3-v6.3 version of root.
Alsoyou mount it as on PDA button?

Unbrick Galaxy S3 (TWRP & Download Working)

Hello All,
i'm trying to help my friend to unbrick a S3, it just stuck at Samsung Logo forever. I tried to root it, install TWRP, flashed a custom rom (stable as per reviews), reboot it and no go, redo everything again with a stock rom, and still no go. Can anyone help? Thanks in advance.
One thing i found out that when i boot to recovery mode (original android) it does have a error message saying "E: failed to mount /efs (Invalid argument)" will this be the cause ?
rayzx said:
One thing i found out that when i boot to recovery mode (original android) it does have a error message saying "E: failed to mount /efs (Invalid argument)" will this be the cause ?
Click to expand...
Click to collapse
Hi rayzx,
according to what I know, "EFS" is the partition that holds the IMEI (International Mobile Equipment Identity) of your phone. This IMEI number is unique to your phone (Dual-SIM Phones have two IMEI Numbers though). Flashing and reflashing ROMs only will not help here, since flashing (proper) ROMs will/should leave the EFS partition untouched anyways. If that partition gets destroyed / corrupted (commonly referred to as "IMEI-Brick") you will have a hard time restoring it - unless you have a complete backup of the (Stock) ROM INCLUDING its EFS partition. You would have to flash it back up onto the device. Without having that kind of backup, special (expensive) equipment and licensens for doing this are required. Since tampering with the EFS Partition (or tampering with the IMEI) is illegal in most (if not all) contries, the only and easiest way I see is sending the device in for repair to SAMSUNG or a specialized & licensed repair shop - as far as I remember you would need to povide/send the phone itself and the sticker belonging to the phone with its IMEI Number clearly visible.
@rayzx: damaged efs-data don't prevent booting. So take latest firmware & Odin from sammobile.com, flash it. If Odin finshes with 'succeeded', boot into recovery and exec factory reset. Phone should boot then. If you see a factory IMEI 0049..., try KIES-repair function.
If this fails: service center (as said above).
rp158 said:
@rayzx: damaged efs-data don't prevent booting. So take latest firmware & Odin from sammobile.com, flash it. If Odin finshes with 'succeeded', boot into recovery and exec factory reset. Phone should boot then. If you see a factory IMEI 0049..., try KIES-repair function.
If this fails: service center (as said above).
Click to expand...
Click to collapse
Agreed..
Sent from my HTC One M9 using Tapatalk
I think your emmc is dead i had the same probleme but i could get into recovery.. try to glash a pit file if odin stuck u need to change the motherboard

Help! My IMEI was set to default of 0049xx and I can't connect to my network carrier.

After having my phone in a bootloop, i figured that my /efs folder was corrupted as it won't mount, so I tried the fix in a website that used adb with mk2fs command thing (I don't know what it is so I just followed the instructions). and I don't have any backups of the /efs folder. I know my IMEI code from the back of the battery in my phone. I've tried most solutions here including QPST, reverting to stock, and using root explorer to transfer the nv_data (I don't have the .nv_data file with the .). I'm currently running Paranoid Android ROM of android 6.0.1.
Did you try flashing a stock rom to see if that solves the problem?
Flash Modem DDEMG2.zip to get your imei. Then flash Patched_XXUGMK6_modem.zip to get mobile signal

i9300 - can't mount anything (\system, \sdcard, \external_sd, etc)

Just woke up to see my phone on the Samsung Galaxy i9300 logo.
(I had just flashed LineageOS the previous day)
I was able to get into recovery CWM but nothing could mount, so I tried TWRP. Same thing. Couldn't sideload too (because you couldn't sideload to anywhere duh).
Tried flashing stock rom and repartitioning. Failed. And now the phone says Firmware upgrade failed etc instead of the logo.
Can't get into recovery anymore.
Can get into odin mode, but Odin doesn't recognize the phone.
SDS?
EDIT:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
You can still flash a stock ROM when you see the "upgrade failed" screen.
Did you try using different USB cables and ports to flash the stock ROM? Tried using Odin 3.07 with and without a pit file?
If you can get to download mode try another cable and install the pc drivers while the phone is connected in download mode or install kies for your operating system, stop the processes and try again.
Make sure your stock firmware is the correct one for your device/region/variant and that the md5 hash matches.
The problem you are having is caused by a borked recovery. It is very possible that the partition is corrupt, inevitably causing the death of your phone.
Beamed in by telepathy
Odin 3.07 / 3.09 and Heimdall don't recognize the phone.
The usb cable seems fine considering I used to flash the day before and if I remove the battery the phone is still on while connected to the usb cable.
I already ordered a new phone but if I can get this one fixed that'd be great. The new phone may come with a usb cable so I will try that.
I guess I was stupid enough to flash TWRP and SuperSU on top of LineageOS.
EDIT:
Before getting to this point I was able to flash stock rom while the Firmware upgrade has failed... logo showed. However I can't flash stock rom because the phone can't mount anything, not even /system. So it fails as soon as it tries to write something.
New usb cable - couldn't flash but was detected by odin.
Deleted hidden.img from the stock rom and now it flashes!
Let's hope it works.
Update: it did not.
After flashing it booted to recovery, said something about missing sd card and a countdown to 20s. After that was over it went to the recovery menu and I got a bunch of the same errors: couldn't mount /system /cache (no such file or folder found).
I put back my sdcard but I couldn't get to recovery, also, instead of the samsung galaxy logo I got a white screen. I could still get to download mode, and get recognized by odin and heimdall, but can't flash anymore ANYTHING.
Either There's no PIT file or stuck at Get pit for mapping if I do include one.
I've tried 3 different versions of odin.
I've tried heimdall under windows and linux with root without success (Either couldn't set up interface or there's no pit file).
I'm gonna try 1.85 odin tommorow. I lost all hope at this point. ****ed up my partitions.
RIP I9300.
Idk if that may work but you may have a go to just try flashing stock rom with a box. Gsm service points shouldn't take much for it
KayleMaster said:
Update: it did not.
After flashing it booted to recovery, said something about missing sd card and a countdown to 20s. After that was over it went to the recovery menu and I got a bunch of the same errors: couldn't mount /system /cache (no such file or folder found).
I put back my sdcard but I couldn't get to recovery, also, instead of the samsung galaxy logo I got a white screen. I could still get to download mode, and get recognized by odin and heimdall, but can't flash anymore ANYTHING.
Either There's no PIT file or stuck at Get pit for mapping if I do include one.
I've tried 3 different versions of odin.
I've tried heimdall under windows and linux with root without success (Either couldn't set up interface or there's no pit file).
I'm gonna try 1.85 odin tommorow. I lost all hope at this point. ****ed up my partitions.
RIP I9300.
Click to expand...
Click to collapse
Your emmc Nand Flash chip died. I had same problem with my n7100 last month. Had to change motherboard.
I took it to a service center. The told me the screen was dead because of the white screen. It was white cus corrupted BL or something, but definitely not the screen, considering you can go into download mode and you can clearly see it's functioning.
I laughed all the way through the front door.
Correct the screen is not the issue. The nand will be borked.
Beamed in by telepathy

Categories

Resources