Related
Hello,
I was wondering if someone could explain me, how BRICK happens or what to do to stay away from brick.
I searched for this question, but cannot find proper answers...
Thx in adv
TwinHeadedEagle said:
Hello,
I was wondering if someone could explain me, how BRICK happens or what to do to stay away from brick.
I searched for this question, but cannot find proper answers...
Thx in adv
Click to expand...
Click to collapse
It depends what device you have. Different things can cause different devices to brick. Usually a "bricked" device is caused by a bad kernel (more so by over clocking or overvolting), (If you have an HTC device) a bad HBoot, flashing a leak that is incomplete or flashing an update (RUU, Odin, whatever) for the wrong device, or flashing a package for the wrong device or one that is improperly coded.
You CANNOT brick your device by flashing custom roms and recoveries or anything like that, and permanent, unfixable, hard bricks are VERY rare and are usually because someone did something stupid.
If you're worried about installing a custom ROM or something, don't worry, it won't brick you.
TwinHeadedEagle said:
Hello,
I was wondering if someone could explain me, how BRICK happens or what to do to stay away from brick.
I searched for this question, but cannot find proper answers...
Thx in adv
Click to expand...
Click to collapse
Bricks happen when you try something not meant for your phone.
Sent from my U8150 using XDA
Thank you so much for clarifying this to me...
I am not total beginner, i possess Galaxy GT-I9001, for 4 months and i installed CWM last week, with complications, i used Odin 4.03 what one guy instructed to me, beside 4.43. First 4.03 failed and my phone failed to boot, I was worrying i could lose the phone. Then i used 4.43 from the Wiki tutorial what fixed the things...
Now i want to Root the phone, so this previous experience scared me, now i am not confident about it so I used to ask here...
So to clarify:
- rooting
-CWM
-flashing - installing custom ROMS
in proper way and following instructions won't brick my phone?
Is it possible that the dev/alpha/beta ROM versions could brick my phone?
How hard brick happens I am interested?
Is soft brick always fixable?
Sorry for bothering with this stupid questions, I am just not too confident, and i don't wanna destroy the phone, i've got no money for another
Thanks again and sorry if bad English
bricked= corrupted bootloader
a really bricked phone is like "dead' and the only way to solve this problem is to flash a new-and-happy bootloader by hardware tools like Medusa jtag jig also you can't solve bricked phone by PC software if yo do so then your phone is not really bricked
I don't know anything about hard/soft bricked what's that ??
you can't brick a phone by flashing a beta rom if you don't touch bootloader but you can destroy or cause hardware damage by flashing a rom/kernel not made for your phone so that's very important to know !
to prevent bricking your phone:
1. never use a flashing tool not made for your phone
2.when flashing bootloader made for your phone only use a stable PC connection/cable and is better to use a laptop on battery
3.about ROM Manager :if you don't see your phone in list never use it to flash recovery/rom
rooting means to get root access this is like your Administrator account in Windows OS well, it happens because by default phones come out from manufacturer with root disabled to protect the phone and their business
CWM is a custom recovery in fact this is a little OS that works like Safe Mode in Windows it can help you to flash a rom/update/theme etc
CWM recovery is different compared to stock recovery because it gives you the chance to flash custom things to your phone I mean you have to give a package a digital signature in order to flash it to your phone and stock recovery is restrictive it allows you to flash only signed-by-manufacturer things like roms/updates/themes and here is the place where CWM comes it allows to flash self-signed packages
Follow tutorials and you won't brick your phone. Stick to your device forum. E.g ,Just because something worked on the galaxy ace doesn't mean you can use that tutorial on a galaxy mini.
Soft bricks can be fixed,those are just installation errors.
Sent from my U8150 using XDA
I was wondering how to remove CWM and to restore original recovery...
I suppose i have to flash my stock ROM, am i right?
Do i need to wipe all data before flashing my custom ROM, just to add i have 2.3.3 i only did CWM nothing else is changed.
One thing isn't clear, when I flash CWM is my stock ROM changed?
TwinHeadedEagle said:
I was wondering how to remove CWM and to restore original recovery...
I suppose i have to flash my stock ROM, am i right?
Do i need to wipe all data before flashing my custom ROM, just to add i have 2.3.3 i only did CWM nothing else is changed.
One thing isn't clear, when I flash CWM is my stock ROM changed?
Click to expand...
Click to collapse
Why would you want to remove cwm? Its a custom recovery, without it you can't go custom. Use cwm to create a nand backup. To go back to stock recovery, you are correct, but make sure you have correct files etc in Odin. Pulling out your USB cable in Odin without completed will brick your phone, I know cuz I did it. The wrong files can do the same. CWM doesn't change the ROM, just the recovery. I have also heard of bricks from Samsung kies mini. Yes you need to wipe/ factory data reset when flashing a new ROM. If you are only updating a custom ROM, going from (ROM name) v 1.2 to (ROM name) v 1.3 it is not always necessary to do factory data reset but follow the instructions per developer of ROM/thread. Get root, put custom ROM on sd, in recovery make a nand backup, wipe cache, wipe dalvik cache, factory data reset, install zip from sd, reboot.
Also sometimes when flashing a ROM it might not boot first time. Don't panic, pull battery out/in 3 button to recovery, install zip again, reboot and enjoy.
Hope this helps....if so hit thanks button!
sent courtesy of the pony express
TwinHeadedEagle said:
I was wondering how to remove CWM and to restore original recovery...
I suppose i have to flash my stock ROM, am i right?
Do i need to wipe all data before flashing my custom ROM, just to add i have 2.3.3 i only did CWM nothing else is changed.
One thing isn't clear, when I flash CWM is my stock ROM changed?
Click to expand...
Click to collapse
No,your stock rom is not changed,just your recovery. You'll need clockworkmod do install custom roms since stock recovery lacks the features needed to install non-manufacturer roms.
If you are concerned about altering your current rom,you can make a backup using clockworkmod recovery, and store it somewhere like your PC.
Yes,just to be safe, it is better to wipe data. Unless it's an update of the same rom which again, isn't always guaranteed. Just to be sure your safe,backup your apps and clear everything.
Clockworkmod is removed in the bootloader by swapping it out with something else(like amon-ra).
Sent from my U8150 using XDA
Ok, thanks
I am planning to use custom roms, but it's not important at this time, I am satissfied with current...
I only need to know how to restore stock recovery, if the phone is somehow damaged and needs to be taken to the service warranty is lost with CWM installed?
Thank you and Sorry again if i am too noob, and asking stupid questions, i just need detailed explanations from people that experienced this, and apparently I've got it
TwinHeadedEagle said:
Ok, thanks
I am planning to use custom roms, but it's not important at this time, I am satissfied with current...
I only need to know how to restore stock recovery, if the phone is somehow damaged and needs to be taken to the service warranty is lost with CWM installed?
Thank you and Sorry again if i am too noob, and asking stupid questions, i just need detailed explanations from people that experienced this, and apparently I've got it
Click to expand...
Click to collapse
It is possible to reset the phone fully to stock. This removes clockworkmod recovery and your custom rom and allows you to claim warranty. So far only Sony is the one I'm aware void your warranty permanently if you unlock your bootloader using their 'official' method. They keep you on record,so even if you relock it you're outside warranty.
Sent from my U8150 using XDA
How To Unbrick my Kindle Fire?
Hello, I'm a Noobie,
I think I bricked my Kindle Fire. “kindle fire” stays on the screen when I turn it on. I can see the device on my computer as ‘Removable Disk (G’ however I am unable to access the drive. Am I BRICKED for good? Kindle running 6.3.1.; PC running Window 7. Please help…..
lcharrisej said:
Hello, I'm a Noobie,
I think I bricked my Kindle Fire. “kindle fire” stays on the screen when I turn it on. I can see the device on my computer as ‘Removable Disk (G’ however I am unable to access the drive. Am I BRICKED for good? Kindle running 6.3.1.; PC running Window 7. Please help…..
Click to expand...
Click to collapse
Redownload the rom with a stronger internet connection, flash it again.
Sent from my U8150 using XDA
@ Allanitomwesh
You didn't tell me how to reset phone fully to stock
I am assuming you haven't started playing with your phone.
Dial *#1234# and write down the three ID Strings PDA, CSC & PHONE ID
They'll be useful later. Just for paranoia, use adb to save your IMEI details (adb is for windows PC's don't worry)
Install Samsung Keis in same PC. Make sure it recognises your phone. Always check this before running Odin.
Always do a full backup (apps, data,settings) before resetting to stock or just any flashing.
Odin will install custom roms on your phone,and it will also take you back to stock if need arises. This is done by 'flashing' stock rom into your phone.
You can follow this tutorial
http://forum.xda-developers.com/showthread.php?t=1345671
Where the rom is the stock one. You can get the right one here http://www.sammobile.com/firmware/?page=1&t=2 Clockworkmod and root access will be lost.(those come with custom roms,don't worry)
When using Odin, a few tips,
1.always run as administrator (right click on icon>run as administrator)
2.Odin runs better without sim card and SD card. You can take them out before entering download mode
3.NEVER EVER interrupt a flashing process,its a guaranteed soft brick.It takes about 10 minutes. If you're impatient, walk away. Also for paranoia,better to have a ups.
4. Perform factory reset before and after flashing. * Menu* Settings* Privacy* Factory data reset* Reset phone& Erase everything. Before and after.
If your rom doesn't boot try this
http://forum.xda-developers.com/showthread.php?t=1660596
Sent from my U8150 using XDA
Would someone help me? I just installed CM10 Jelly bean for Iconia A500 and flashed the corresponding GApss right after. Now I'm stuck on Acer logo and can't go to recovery. Help.
xmond said:
Would someone help me? I just installed CM10 Jelly bean for Iconia A500 and flashed the corresponding GApss right after. Now I'm stuck on Acer logo and can't go to recovery. Help.
Click to expand...
Click to collapse
Ask here for better assistance
http://forum.xda-developers.com/forumdisplay.php?f=1211
Sent from my U8150 using XDA
Thanks
Allanitomwesh said:
Redownload the rom with a stronger internet connection, flash it again.
Sent from my U8150 using XDA
Click to expand...
Click to collapse
Thanks for your response, I however cannot access my Kindle Fire. It shows up on my computer as 'G:' drive. I can go to TWRP on the device but there's nothing to restore. I think I wiped out everything. There is a message that says "E:failed to mount /sdcard (Invalid argument)" I'm Bricked for good aren't I?
lcharrisej said:
Thanks for your response, I however cannot access my Kindle Fire. It shows up on my computer as 'G:' drive. I can go to TWRP on the device but there's nothing to restore. I think I wiped out everything. There is a message that says "E:failed to mount /sdcard (Invalid argument)" I'm Bricked for good aren't I?
Click to expand...
Click to collapse
Not necessarily, but it does sound like you went abit overboard with clearing data.
Try and restore stock rom on your kindle. The method where you lose root preferably.
Sent from my U8150 using XDA
Hey guys!
Each phone company has its own policies and ways to void users' warranties when installing custom firmwares/roms on their phones.
Unfortunately, I didn't give myself enough time to read about Samsung's crap being very busy lately.
You're pretty lucky if you bought a phone with a 4.2.2 firmware (I9500 in my case). You do have a binary counter as much as I can recall, but it's not as big of a deal as KNOX (and warranty bit, you can find that in your download mode) which was introduced in the OTA (i.e 4.3 firmware).
I strongly recommend not to update your phone to 4.3, and I will list the reasons why; but I want to give some tips beforehand.
Make a full nandroid backup if you're planning to change roms. It is very important to have your factory firmware with you; you will need it at some point. Keep it in a safe place.
Backup your EFS folder and keep it in a safe place too. Your EFS has your IMEI, MAC address, serial number and many other important things. There are many ways to backup your EFS folder.
Do NOT use a custom recovery to back it up for you.
Open Dialer, write *#1234# and take a screenshot of (or write down) the version numbers of AP, CP and CSC (which correspond with PDA, PHONE (MODEM) and CSC respectively).
Keep at least 2-3 GB free in your internal storage before flashing any rom.
Some ROMs like MIUI are flashed through ODIN. What happens is that CWM is installed by flashing the .tar file supplied by MIUI and CWM in-turn flashes the ROM. Do not use that method. Flash the zip file from your custom recovery instead. Don't forget to wipe cache/data before flashing the rom.
Click to expand...
Click to collapse
You are lucky if you have 4.2.2. Why? Read on.As mentioned earlier, Samsung introduced a new KNOX security system to which our knowledge is limited so far. The flash counter has been replaced with that annoying KNOX. We don't know where the Boolean flag is store yet (some people claim it is an eFuse); but the truth is still unknown (to my limited knowledge anyway ).
The new update to 4.3 added a line in the Odin Mode, which is "Warranty bit: 0x[0|1]".
* A bit of 0x0 means that KNOX is still active.
* A bit of 0x1 means that KNOX is inactive.
The Warranty bit gets triggered (0x1) when you flash a custom recovery, custom ROM or root. [Some even say that it happens even if you flash a stock firmware through ODIN (someone please confirm that).]
More information about the KNOX behavior can be found here.
Enough about KNOX, now what is your advantage?
Being on a 4.2.2 firmware does trigger your binary counter when flashing custom ROMs. For I9505 users, it is easy to reset using Triangle Away. For us I9500 users, we don't really have one yet (maybe never), but we can still flash official firmwares or custom ROMs, and Samsung probably will not even bother looking at the counter. Worst cases, you could upgrade to 4.3 which will eliminate the flash counter but will get you in a bigger hole, the KNOX monster.
No matter what you go through, do not update to the official 4.3. Use a custom ROM instead. Most (if not all) of the 4.3 custom ROMs have KNOX security disabled. So you will have a 4.3 ROM without the KNOX (Warranty bit) hassle.
In-case you need an official firmware, find yours on Sammobile or Samsung-Updates and choose the 4.2.2 one.
Click to expand...
Click to collapse
Errors with IMEI, serial number, etc. ("Emergency calls only" error).You may face times when you flash different ROMs that either a bad flash corrupted your EFS or simply something in your modem got messed up. Check your system status after each flash (Settings -> About -> Status).
An IMEI that is either 0 or starts with 0049, signifies an error and will leave your phone in a state where you can make "Emergency calls only".
In-case of an IMEI with 0049, I would suggest flashing your modem again. Remember the first nandroid backup you did? Go to your recovery (PhilZ touch or CWM) -> Custom Backup and Restore and choose modem. This should fix your issue.
If the solution above does not do it for you, restore the EFS you had backed up before.
Q: I did not have any backup of my factory firmware. What should I do now?
A: Try to find your Factory CP (modem). A collection of modems could be found here. Otherwise, you can find some informative things in here which will tell you more details about your country specific firmware.
Click to expand...
Click to collapse
I will keep on adding more things but for the time being, I hope this was informative and helped you in anyway.
Please let me know if I said anything wrong or missed any important details.
Thank you!
Best regards,
Claude
Reserved.
Reserved 2.
Reserved
Some useful information thanks
I wish this post existed before which would basically prevent me from buying S4. I was told about this issue however I was naive and decided to buy S4 from the store thinking that all the new devices have 4.2.2 and the old bootloader. To my surprise when I took the new device from the box and loaded to download mode it already had the bootloader with the KNOX.
anubius said:
I wish this post existed before which would basically prevent me from buying S4.
Click to expand...
Click to collapse
Yeah, luckily I'm still on 4.2.2 with custom rom (foxhound) because I was really happy with it and therefore I didn't read the S4 at all but today I decided to upgrade to Kitkat and discovered this new Knox crap.
Is it possible for me to format the phone, put it on 4.2.2 stock and then root and flash custom rom again? Because my internal sd is full of old folders and files from previous roms.
PedroFlaxh said:
Yeah, luckily I'm still on 4.2.2 with custom rom (foxhound) because I was really happy with it and therefore I didn't read the S4 at all but today I decided to upgrade to Kitkat and discovered this new Knox crap.
Is it possible for me to format the phone, put it on 4.2.2 stock and then root and flash custom rom again? Because my internal sd is full of old folders and files from previous roms.
Click to expand...
Click to collapse
Even if you manage to install an 4.2.2 rom Knox will still be 0x1. But users from European Union like you are not affected by Knox 0x1. Rooting your device does not lead to warranty void.
PedroFlaxh said:
Yeah, luckily I'm still on 4.2.2 with custom rom (foxhound) because I was really happy with it and therefore I didn't read the S4 at all but today I decided to upgrade to Kitkat and discovered this new Knox crap.
Is it possible for me to format the phone, put it on 4.2.2 stock and then root and flash custom rom again? Because my internal sd is full of old folders and files from previous roms.
Click to expand...
Click to collapse
From what I've read it is impossible to downgrade to older version since new bootloader prevents it. Your only option is to join the dark side by installing CWM and install custom roms but you will have 0x1. However as mentioned in the previous post the warranty should still work since you are in EU, however you never know with Samsung. Time will tell.
Hi guys
recently bought a s6 from ebay which was frozen on S6 logo. Basically managed to clear cache and factory reset from recovery but that didn't work, anyway I DL the O2 firmware and odin and put it into download mode I get a fail on odin when trying to install the rom
The phone has knox 1 and also has red writing SW Rev. Check Fail. Device: 3 Binary: 1.
I'm unsure what to do and if theres any chance for me to recover.
Many thanks
Mav
it failed because you flashed an incompatible Firmware.
where did it stopped flashing in odin? In sboot.bin?
If thats the case, you need to download proper firmware/country for your device.
Let me know what country is ur fone made of.
Hi thanks for your reply.
I managed to get it working by installing root and unikernel, it boots into O2 the firmwarw is 5.1.1
Only problem now is imei is 3500000000006
And it wont make calls dont know if imei is corrupt ir they sold me a stolen or lost phone?
I may install tw recovery and custom rom and see if that works.
Any suggestions?
Hi
Ive managed to sort out and get it to work infact typing on it now. Its currently rooted custom rom and twrp. I e managed also to restore original imei number so overall im quite pleased with myslef lol.
Anyway one last problem i have is ive tried all sims but none work i know ita picking up signal as the bar shows top right. Also chexk my settings.
Ive tried automatically and manually going to register networks but it says unable to connect try again later. I know uts not my area as my wifes s6 works perfectly. Sim also def works. The phone also picks up when a new sim has been inserted so i dont think its sim slot.
Any ideas guys
OK new update if anyone can help I'd really appreciate.
Installed new vador rom Imei reverted back and serial number is all zeros
Is this something to do with baseband if so how can I fix read somewhere about ariza patch but that was s3 4 etc.
Thanks
Mav
1. Your EFS is corrupted. The IMEI you see is a generic one, phone will be useless for network provider only wifi will work.
2. The one thing that caused this is by flashing an old bootloader to your phone. Thats why youve encountered Check Fail error on Download mode.
Happened to me also but got it fixed in the end.
OK thanks for the info how do I fix? I do have my wife's s6 but that's not rooted and don't want to root can I restore the efs
Many thanks
Mav
Been searching for ages can anyone please point me in the right direction for a fast download of stock o2 5.1 rom? I believe I may need this one G920F_O2U_G920FXXU2BOGC_G920FTEF2BOG1.zip at the moment rapid gator is going to take 10 hours lol.
Thanks
BTW is anyone out there on the s6 forums hardly getting any help really want to try and sort this thanks
maverick7777 said:
Been searching for ages can anyone please point me in the right direction for a fast download of stock o2 5.1 rom? I believe I may need this one G920F_O2U_G920FXXU2BOGC_G920FTEF2BOG1.zip at the moment rapid gator is going to take 10 hours lol.
Thanks
BTW is anyone out there on the s6 forums hardly getting any help really want to try and sort this thanks
Click to expand...
Click to collapse
I think I know one thread that has a firmware downloader with ultra fast download speed you may try searching it.
I dont know if it will help, but you may be able to successfully flash the firmware but many of those who have problems were unable to boot the phone due to corrupted efs data.
Here's my way of fixing it (if you still have intact efs). http://forum.xda-developers.com/showpost.php?p=63693480&postcount=28
But if its already wiped, there's no way you can retrieve it unless bringing it to samsung or any repair shop.
Anyways, mine was fixed (IMEI) using Octopus box repair tool. Since I cant do anything to recover my generic imei.
batuzai04123 said:
I think I know one thread that has a firmware downloader with ultra fast download speed you may try searching it.
I dont know if it will help, but you may be able to successfully flash the firmware but many of those who have problems were unable to boot the phone due to corrupted efs data.
Here's my way of fixing it (if you still have intact efs). http://forum.xda-developers.com/showpost.php?p=63693480&postcount=28
But if its already wiped, there's no way you can retrieve it unless bringing it to samsung or any repair shop.
Anyways, mine was fixed (IMEI) using Octopus box repair tool. Since I cant do anything to recover my generic imei.
Click to expand...
Click to collapse
Thanks silly question but how do I know if my efs is ok or corrupted?
at the moment the phone works perfect it is rooted, twrp recovery and vador rom but it just wont connect to networks. I know its not stolen or lost.
maverick7777 said:
Been searching for ages can anyone please point me in the right direction for a fast download of stock o2 5.1 rom? I believe I may need this one G920F_O2U_G920FXXU2BOGC_G920FTEF2BOG1.zip at the moment rapid gator is going to take 10 hours lol.
Thanks
BTW is anyone out there on the s6 forums hardly getting any help really want to try and sort this thanks
Click to expand...
Click to collapse
As far as i know if your EFS partition is corrupt and you do not have a back up of the EFS partition to restore which you probably dont as you bought this as broken then sim capability is dead, im not sure of any other way to fix this unless you have the intact efs partition
Hi
How can I tell if the efs is corrupt it shows a baseband it now shows the correct ime I
It just won't connect to network it says try again.
I can post a screen print of efs folder on es Explorer if anyone knows what it should look like
Here are screen prints but I think I'm speaking to myself lol
Hi there i spent months on fixing issues like this (i now have a tool that takes care of all this) , best thing you can do is flash to a rom where the original imei came back do a backup of the efs, flash to a orginal rom ( latest rom) make sure its the right one for your device, connect to kies, install the rom again root and restore the efs failing that the imei is blocked use checkmend.com the uk version if your from the uk, message me if you need help
maverick7777 said:
Thanks silly question but how do I know if my efs is ok or corrupted?
at the moment the phone works perfect it is rooted, twrp recovery and vador rom but it just wont connect to networks. I know its not stolen or lost.
Click to expand...
Click to collapse
Your rom, recovery and kernel doesnt have to do with corrupted efs.
Only way is to bring it to repair service using box tools to re enter/validate your imei so that you can connect to your network provider. There is no other way around other than retrieving your efs and installing it or thru repair service.
You may now relax yourself at finding ways to connect, I assure it wont help trying to flash and flash and flash stuff to your phone.
---------- Post added at 08:46 AM ---------- Previous post was at 08:37 AM ----------
Uhm can you send sms or make calls? It seems you have a valid Imei
Ok ive tried all stock roms including o2 and a uk btu one but no luck they all do the same thing get frozen on Samsung logo then I flash unikernel and it boots.
When checking my efs folder I can see no modem file I'm now wondering could that be the fault? so I downloaded modem and BL for 5.02 and 5.11 both will not flash via odin I get a fail message and on device check fail device: 3 binary: 1 messgage in red?????.
So I'm a little lost, I was wondering if I managed to root my wifes s6 which is virtually new could I back up her efs folder then copy it into mine and just amend the imei to my original would that work? also is there a way of rooting my wifes phone without triggering knox?
Any other suggestions guys I really don't know what bootloader was on it to start with or rom is there any way for me to find this out?, also another weird thing when the o2 uk roms install they install german apps?
Thanks guys
Ive repaired EFS Partitions with scripts downloaded from links at xda.
For example i trashed my EFS partition on my note 3 so it caused hard reboots after android booted up and it couldnt be fixed with anything else than the EFS partition repair scripts.
Edit: friend repaired his Note 4 also.
Thanks but where can I find these scripts as I've looked everywhere and if I did find how do I go about doing it. At the moment when I try to flash modem and bootloader it fails.
EFS brick
maverick7777 said:
Thanks but where can I find these scripts as I've looked everywhere and if I did find how do I go about doing it. At the moment when I try to flash modem and bootloader it fails.
Click to expand...
Click to collapse
hi my friend,
i have exactly the same issue as u, i'm really hopeless, did you get any solution so far??????????????????????????
i hate being using my s6 as an ipad mini, holding two phones in my pockets
ketman5001 said:
hi my friend,
i have exactly the same issue as u, i'm really hopeless, did you get any solution so far??????????????????????????
i hate being using my s6 as an ipad mini, holding two phones in my pockets
Click to expand...
Click to collapse
Same with me also need help
Good day everyone, just got my note pro WiFi version? Already rooted and has custom kernel civz, tablet feels slow so I'm planning on changing rom maybe lineageOS but I'm concerned about the procedure because I'm not sure where I'm standing with every change done to this device, any help is appreciated I just don't want to brick this device trying to flash a new rom.
Currently it's running stock rom 5.0.2, 3.4.39 civz kernel and knox 2.3, if someone could provide a step by step on what should I do or check in this device to be on the safe road id really appreciate it. Btw I don't even know what recovery I have or how do I access it.
Bump
honestly most samsung devices are the same so id suggest getting the full stock system and using odin to revert to stock, from there start by getting a custom recovery and seeing what else you need to set up your rom
someone correct me if im wrong
heres the page for official stock "images"
https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P900/
xxjahasotoxx said:
honestly most samsung devices are the same so id suggest getting the full stock system and using odin to revert to stock, from there start by getting a custom recovery and seeing what else you need to set up your rom
someone correct me if im wrong
heres the page for official stock "images"
https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P900/
Click to expand...
Click to collapse
someone told me that I just need to install twrp as it is and start flashing roms, dont know if this the best way to do it what do you think?
It could work just keep in mind that you don't know exactly what the previous owner did to it so if they installed a custom kernel you'll be stuck with that, could be a good thing could be a bad thing
You could always give it a shot and if it gives you problems go back to stock then TWRP then start rom-ing
Edited in 2022 to make it look a bit better!
*WARNING* *TAKE A NANDROID BACKUP OF EFS AND BASEBAND BEFORE STARTING*
Hello people, first I want to say that this is my first guide so it doesn't really look professional but I am doing my best to be clear as possible.
In this guide I will be showing you how to repair your IMEI for free/without Z3X box
So lets get into it.
Its better to start fresh in stock rom
So flash the stock rom first
Now we are really starting,
Step 1) flash TWRP and flash Magisk (if you weren't rooted yet)
Step 2) now search for a custom rom for your phone download it before doing something or just download on pc and move it later
Step 3) now go to mount and select efs or else your efs will be empty at the next step
Step 4) now go to file manager and goto /EFS
Just delete everything in it OR YOU CAN LEAVE Privo data and factory app, you have a backup anyways. *WARNING: DO NOT DELETE THE EFS PARTITION IT SELF, IT WILL MAKE YOUR PHONE NOT BOOTING ANYMORE ONLY DELETE THE FILES INSIDE OF IT SO DELETE ALL FILES*
Step 5) now flash the custom rom for s7 edge i would recommend kingrom, do full wipe at the aroma. You may try to skip this step. There have been comments saying that this guide also works without this step.
Step 6) now reboot your phone, first reboot may take 5-10/15 minutes please be patient and make sure you put your phone in the charger if your battery is low now when your phone is in the welcome screen look or your signal is returned if not just setup your phone sometimes it may take a while for the signal to appear. If your signal is returned then go to phone app and dial *#06# and look or the IMEI matches the IMEI of the box of your phone (make sure you have the original box if you don't have this then open the back of your phone (if you can), there is a sticker label with your s/n and IMEI. If you cannot open the back of your phone, then you will have to trust that the IMEI is right. If everything is functional then you're done with this guide. The next steps are more ''checking'' if everything is alright.
Step 7) If your s/n is ok skip to step 8 if its not right then download a root explorer and go to /efs/factoryapp and edit the serial no file with a text editor and enter your s/n there now save it and IMEI and s/n should be alright
Step 8) Now, for IF the IMEI is correct and everything is fully functional, then delete the earlier made backup of EFS and baseband and make a new one with the working partition, then save it somewhere safe on an external drive, the cloud or on an USB, or just a pc that you will never reset or wipe its data.
Congratulations on getting past step 8. I hope this guide has helped you and that it worked for you. If not then I'm sorry for not being able to assist you. This guide is just me sharing what I did to solve this issue. Good luck on solving your problem if this guide did not work.
If the IMEI is not correct or this guide doesn't work then I can't help you any further except for if you have any questions, however I found a guide for the Samsung galaxy s7/Edge (if you have s8 then click same link because the thread has a link to s8) by Cubz (thanks to Cubz for his guide)
Link: https://www.google.com/amp/s/forum....ow-to-fix-check-drk-imei-issues-t3379516/amp/
S7/E/8 only and some other models as long its an s7 (edge) or s8/+
******* Some tips when you follow the guide*******
1) When you flash combination firmware and it gives you errors then dial *#1234# and look at the cp it should have UX in it (X could be 1,2 or 3 download the correct firmware with the correct bootloader version. You can upgrade from u1 to u2 and u2 to u3 but not downgrade from 3 to 2 or 2 to 1
2) If it didn't work then flash back to stock and fully delete everything in efs folder then retry (this is actually just guide B) its better to follow the guide above
3) If you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
The first method was tested and worked on SAMSUNG GALAXY S7 EDGE SM-935F it may work on other Samsung devices and maybe other android devices but I cannot guarantee that it works on your device
** I take no responsibility for any damaged device, make sure you take a back up so you can go back to the state before you started following this guide!**
If the device gets bricked then always flash back to stock, if you cant enter download mode then just wait until your battery drains and then when you put it in the charger it may start up automatically so enter download mode fast or if you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Happy flashing and please confirm in the comments below if it worked for your device or not
Guys please comment or it works on your device or not!
It works for me. But I have to manually change CSC on my phone after original rom flash to fix Network. TGP rom have that option.
I followed your guide and my model name changed from G930F to G930FD and my IMEI is just bunch of zeroes wtv
SOLVED AT LAST - MISSING IMEI and EFS DAMAGED SOLUTION
Hi Guys,
First off, please take GOOD note - I am NOT a techy, just an old boring flashaholic who works in an office and likes pyjamas more than partying. This is my account of me fecking up my phone and finally reaching a solution after three days and most of two nights to a missing IMEI, messed up EFS and non-working phone - hoping that it might help anyone as desperate as I was. You do what you do with your phone and that's your business and I'm not responsible if you mess it up, but my hope is that you have have a brain (that's all I have) and you get some helpful piece of info here as I did from a whole ton of posts I read that finally led me to this.
Next - I am not sure what landed me in this mess. I've seen Superman Rom mentioned a couple of times..I didn't use that but I did use Batman Rom which is by the same Dev. It was great to use, too, so I'm not faulting the Dev by any means. What did happen, though, is that when I flashed other ROMS, maybe 3 or 4 of them following, the Batman splash screen was always there before the new ROM's boot sequence, so there were clearly some residual things of it in there ...so perhaps the same coding is in there and could have had something to do with it, I don't know. The breaking point came when I flashed Sac23 Rom hoping to get Pie on my phone. It was cool but I decided to revert to Resurrection Remix - always my favourite overall - and all of a sudden I get errors.
What should have been a routine "Restore" of my backed up RR ROM via TWRP gave "Error mounting EFS". Reboot, wipe, retry. No joy, same again. A couple of tries to restore the EFS from the backup in TWRP didn't work either.
Next go to is flash "original firmware" (more on this wording later). I had that on my PC (not a phone backup, just the firmware so it's clean copy with no data).
Get Odin out, download mode, correct files in correct boxes, all that standard stuff you can find guides on most places - no joy.
Error showing was "Fail at pm.bin" or something like that. Install aborted.
Try again. This time "Fail at cm.bin" Install aborted. Reboot from recovery also fails. Oh sh1t.
Several more attempts made. I have five different Odin vers. I have seven different firmware vers. I have two USB ports and about 8 Samsung cables. Not a single combination I tried worked.
The XDA heroes will know what to do, I thought. I read and read. And read. And CubZ (who is a hero even if he IS from Lancashire ), says MAKE SURE YOUR PHONE IS RUNNING ORIGINAL SOFTWARE. Well...I kinda did that mostly already...but maybe I need to go RIGHT back to the rubbishy 6.0.1 version that came actually ON my phone when I got it....almost 2 years ago? Who remembers that stuff?? I'm about 18 ROMS down the line now. I was desperate. I'm telling you...I even got out my bank statements to trace when my first payment to my current provider was...I read about firmware numbers and country codes, and I chose one from Sammobile with a build date, country code, unbranded code (which my phone always was) and correct phone model (of course!) as I needed. And it WAS .."the ORIGINAL" firmware.
This time I swear Odin failed me a second BEFORE I pressed the start button! No joy.
Have a flask of coffee and a few valium sandwiches and off I go back to XDA again. I read a loooong series of "Missing IMEI" stuff and there's CubZ again with an IMEI/EFS fix guide guide...brilliant! And it WAS brilliant, and clearly he helped tons of people (kudos, man). But I had messed up MY phone in the time-honoured "right royal" way - worse than his guide could help me. My IMEI was Unknown, my EFS was empty, My SIM wasn't being recognised, no network info or signal...nothing. But genius that he is, he CubZ DID post a Combination file that gave me a base to keep trying on when firmware after firmware had failed almost immediately with errors either of pm.bin/abort or cm.bin/abort.
I almost wore the print out on CubZ guide, I read it so much and tried so many times. Then...I see people saying things about U1, U2 and U3 firmwares. Turns out you shouldn't mix the two. I got that snippet from CubZ too. More research and the little coffee-fuelled connections in my brain are like.....ok....
My ORIGINAL firmware has in its name "U1" and there are similar ones with "U2". Might that be it? My phone has been screaming "DEVICE 2 FIRMWARE 1" (or something like that) at every aborted 'original firmware' installation via Odin and download mode that I've tried, including the EXACT firmware that was on my phone the day it was unwrapped and I danced happily round the room with it.
So if DEVICE 2....FIRMWARE should be 2 maybe? Back to Sammobile. There are firmwares with the same model number, country code, branding info as mine..but with a "U2" where mine said "U1". But...they were Oreo and Nougat where mine was "originally" Marshmallow.
It's now day three in the Big Mother House. My valium and coffee and running out and my communication with the outside world has ceased. I've had about five hours sleep, my food is running low and I cannot call for takeaway cos I ficked my phone up good and proper. I even....get this....start looking up PAID services to fix this. I KNOW, right!!??
I pick up a Nougat firmware from Sammobile...careful to match model, country, branding AND U2 - wondering if I can match it up with CubZ's Combi file as a base to appease Odin......and then maybe revert to my 'original' stock from that to start another attempt at the IMEI/EFS thing.
It loaded. Odin was pleased with my sacrifice. And lo and behold, it had restored the whole lot WITHOUT me having to go any further with stock ROM reversions. It frickin' worked. I got my signal back. My SIM card was detected. My phone number was showing. My IMEI was showing. My E-Frickin-S was mended. I feel like Judd Nelson at the end of Breakfast Club.
So here's the semantic bit that I hadn't known and that is unclear in many many posts. My phone is now working 100% on stock firmware....but is is NOT REALLY the ORIGINAL software - it's the MODEL......COUNTRY......BRANDING.....LANGUAGE - specific firmware but it is Nougat where my original was Marshmallow, and it is a U2 firmware where my original FW was U1. THAT was the killer difference, it seems. Thanks to all of you who posted anything - many many of you - who helped me get this. It's a compatibility issue detail I've never seen or had issues with before.
I now have G930FXXS2DRDI_G930FXEU2DRB5_XEU
Where G930F is the model number, XEU is the country code for UK and Ireland (even though UK is a nation and not a country - just sayin' ) and the U2 sits there hiding in the middle of the second section of the name.
Which gives unzipped files as follows: NOTE - THESE ARE NOT LINKS.
AP_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship_meta.tar.md5
BL_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship.tar.md5
CP_G930FXXU2DRB6_CL648265_QB8952207_SIGNED.tar.md5
CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar.md5
HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar.md5
It's Nougat, but that's okay for now; I got my IMEI, EFS, SIM, BIN, probably ENT, RAC, SUV and BMX too, everything
And now, with my working phone, I am gonna phone the local Chinese Takeaway for food, answer all my emails that popped and binged and tinkled at me when it became resurrected, and leave CubZ with huge thanks and all of you guys with the hope that this helps somebody out there.
And maybe look at backing this sucker up and reverting to my Oreo RR ROM I love so much..... I HATE Touchwiz!!!!
Good luck!
:good::good::good:
I was also on similar problem and i lost my efc
Baseband unkwn
Imel null
No signal
I was on s9 port rom by teamexykings and when i update i did dirty flash and my phobe stuck on samsung logo somehow it was boot but it was keeps rebooting than i boot my phone in twrp
When i was trying to wipe system data and dalvic cache
In wipe menu i was shocked to see that it showed internal storage 0mb
I had this problem 1st time
And i have to format my phone to boot properly
U know my big mistake is that i haven't taken a back up of my all apps and my data
After 10-15 min latter it boots
But 2nd shocked was that
I lost my signal my imei my baseband vesrsion unknown
I was so scared to lost my imei
Than i searchon google and i have read lot of articals about restoring efc partition
And than i found similar thread like u have explained
It's really work for me
And this article will help most of device of samsung
And xda user
What i have done
In twrp i mount efc partition
Than in advance menu
File manager
Efc
And i have deleted all of file in efc
(Remember not efc partition it self)
Except privo
Privo data and factory app
Than reboot
After boot my phone i got signal back
I was so happy that it was very easy to do
Your guide will help for many device
shabbir143 said:
I was also on similar problem and i lost my efc
Baseband unkwn
Imel null
No signal
I was on s9 port rom by teamexykings and when i update i did dirty flash and my phobe stuck on samsung logo somehow it was boot but it was keeps rebooting than i boot my phone in twrp
When i was trying to wipe system data and dalvic cache
In wipe menu i was shocked to see that it showed internal storage 0mb
I had this problem 1st time
And i have to format my phone to boot properly
U know my big mistake is that i haven't taken a back up of my all apps and my data
After 10-15 min latter it boots
But 2nd shocked was that
I lost my signal my imei my baseband vesrsion unknown
I was so scared to lost my imei
Than i searchon google and i have read lot of articals about restoring efc partition
And than i found similar thread like u have explained
It's really work for me
And this article will help most of device of samsung
And xda user
What i have done
In twrp i mount efc partition
Than in advance menu
File manager
Efc
And i have deleted all of file in efc
(Remember not efc partition it self)
Except privo
Privo data and factory app
Than reboot
After boot my phone i got signal back
I was so happy that it was very easy to do
Your guide will help for many device
Click to expand...
Click to collapse
You deleted all files and folders from EFS Mounted partition? how is it possible working?
You are awesome man!
I just deleted the files in EFS, restarted without installing custom rom and my IMEI was fixed.
I'm definitely donating. How to donate to you?
Thanks for your great work!
cisekpro23 said:
You deleted all files and folders from EFS Mounted partition? how is it possible working?
Click to expand...
Click to collapse
I think samsung phones are capable of regnerating their efs. But its not working for me on samsung galaxy s6. Guess I am screwed.
Hey everyone, I'm sorry for not responding to anyone in this thread. I've been inactive for a long time. I want to thank everyone for trusting the guide and I hope it has worked for you if you tried following the steps. If you have any questions feel free to ask me.
Also I have edited my guide to improve the reading experience because I see my English was absolutely horrible at the time when I wrote the guide.
oh no. i accidentally deleted the efs partition and it can't mount anymore what im gonna do now. im fvcked up please somebody help me
vigilante said:
Edited in 2022 to make it look a bit better!
Hello people, first I want to say that this is my first guide so it doesn't really look professional but I am doing my best to be clear as possible.
In this guide I will be showing you how to repair your IMEI for free/without Z3X box
So lets get into it.
Its better to start fresh in stock rom
So flash the stock rom first
Now we are really starting,
*WARNING* *TAKE A NANDROID BACKUP OF EFS AND BASEBAND BEFORE STARTING*
Step 1) flash TWRP and flash Magisk (if you weren't rooted yet)
Step 2) now search for a custom rom for your phone download it before doing something or just download on pc and move it later
Step 3) now go to mount and select efs or else your efs will be empty at the next step
Step 4) now go to file manager and goto /EFS
Just delete everything in it, you have a backup anyway *WARNING: DO NOT DELETE THE EFS PARTITION IT SELF, IT WILL MAKE YOUR PHONE NOT BOOTING ANYMORE ONLY DELETE THE FILES INSIDE OF IT SO DELETE ALL FILES*
Step 5) now flash the custom rom for s7 edge i would recommend kingrom, do full wipe at the aroma
Step 6) now reboot your phone, first reboot may take 5-10/15 minutes please be patient and make sure you put your phone in the charger if your battery is low now when your phone is in the welcome screen look or your signal is returned if not just setup your phone sometimes it may take a while if your signal is returned then go to dialer and dial *#06# and look or the imei matches the imei of the box (make sure you have the origional box if you dont have this then open the back of your phone, there is a sticker label with your s/n and imei if imei is not good then skip to step 9
Step 7) now if your s/n is ok skip to step... if its not right then download a root explorer and go to /efs/factoryapp and edit the serial no file with a text editor and enter your s/n there now save it and imei and s/n should be alright
Step 8) Now, for IF the IMEI is correct and everything is fully functional, then delete the earlier made backup of EFS and baseband and make a new one with the working partition, then save it somewhere safe on an external drive, the cloud or on an USB, or just a pc that you will never reset or wipe its data.
Step 9) now for if the IMEI is not correct or this guide doesn't work then I can't help you any further except for if you have any questions, however I found a guide for the Samsung galaxy s7/Edge (if you have s8 then click same link because the thread has a link to s8) by Cubz (thanks to Cubz for his guide)
Link: https://www.google.com/amp/s/forum....ow-to-fix-check-drk-imei-issues-t3379516/amp/
S7/E/8 only and some other models as long its an s7 (edge) or s8/+
******* Some tips when you follow the guide*******
1) when you flash combination firmware and it gives you errors then dial *#1234# and look at the cp it should have UX in it (X could be 1,2 or 3 download the correct firmware with the correct bootloader version you can upgrade from u1 to u2 and u2 to u3 but not downgrade from 3 to 2 or 2 to 1
2) if it didn't work then flash back to stock and fully delete everything in efs folder then retry (this is actually just guide B) its better to follow the guide above
3) if you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
The first method was tested and worked on SAMSUNG GALAXY S7 EDGE SM-935F it may work on other Samsung devices and maybe other android devices but I cannot guarantee that it works on your device
** I take no responsibility for any damaged device, make sure you take a back up so you can go back to the state before you started following this guide!**
If the device gets bricked then always flash back to stock, if you cant enter download mode then just wait until your battery drains and then when you put it in the charger it may start up automatically so enter download mode fast or if you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Please donate and like this thread if you found this helpful, I have experienced this problem my self and it costed me €60! I said NO its too expansive so then I found this solution and now I am sharing it to the world, I could have let this guide cost €61 but my guides and solutions are free a support would be great for finding this out
Happy flashing and please confirm in the comments below if it worked for your device or not
Click to expand...
Click to collapse
oh no. i accidentally deleted the efs partition and it can't mount anymore what im gonna do now. im fvcked up please somebody help me
bamcarpio123 said:
oh no. i accidentally deleted the efs partition and it can't mount anymore what im gonna do now. im fvcked up please somebody help me
Click to expand...
Click to collapse
Have you created a back up of your efs partition? I have clearly written it in the guide with all caps. If you haven't made a back up, please do so to avoid getting into this situation in the future.
*WARNING* *TAKE A NANDROID BACKUP OF EFS AND BASEBAND BEFORE STARTING*
Click to expand...
Click to collapse
Anyways, I'm sorry to hear you got your self in this situation. Even though it has been a long time since I did this kind of stuff, I still remember that it's possible to fix this issue. I am sure that I have been in this situation before my self and that I somehow managed to get it back. Try to back up all your data, then flash stock rom with CSC file and not Home CSC
vigilante said:
Have you created a back up of your efs partition? I have clearly written it in the guide with all caps. If you haven't made a back up, please do so to avoid getting into this situation in the future.
Anyways, I'm sorry to hear you got your self in this situation. Even though it has been a long time since I did this kind of stuff, I still remember that it's possible to fix this issue. I am sure that I have been in this situation before my self and that I somehow managed to get it back. Try to back up all your data, then flash stock rom with CSC file and not Home CSC
Click to expand...
Click to collapse
I'm sorry for being so stupid because I continued without performing a backup in TWRP, I forgot to back up the EFS, and when I panicked because I was already screwed up, I deleted the efs folder—which is incorrect. I deleted the efs partition before I saw this thread. And now it always says, "failed to mount /efs (invalid argument)" and I've done everything, and it seems like everything is done, I have no idea what to do. I haven't slept for four days and there is still no hope. but my phone is still okay with the stock firmware, but it always restarts. I did almost everything but still nothing
My phone's current csc code is THL (Thailand), but the original is XTC (Philippines), which is my nation, thus I'm curious why THL? of course I flash the right firmware which is the csc is XTC but if I check the CSC the CSC is still THL. I tried to change the csc using tools, but it cannot be change. There may be no hope. I'm worried about losing my phone, yet I'm to blame.
If I lose my IMEI, it won't matter. But the thing is my phone is always restarting every minute.
(can someone know how to disable auto-reboot so i can still use my phone even the EFS is damaged?)
ALSO THANKYOU FOR YOUR REPLY! I APPRECIATE IT!
EDIT: OH I FIX THE EFS PARTITION. NOW MY PROBLEM IS HOW TO GET OUT FROM THIS DARKNESS. HOW CAN I FIX THE IMEI AND BASEBAND WHAT EVER? HMM. BUT I WON'T GIVE UP
bamcarpio123 said:
My phone's current csc code is THL (Thailand), but the original is XTC (Philippines), which is my nation, thus I'm curious why THL? of course I flash the right firmware which is the csc is XTC but if I check the CSC the CSC is still THL. I tried to change the csc using tools, but it cannot be change. There may be no hope. I'm worried about losing my phone, yet I'm to blame.
Click to expand...
Click to collapse
Try to download this tool if you haven't already: https://samfirmtool.com/
I like to use this tool when flashing stock rom because I can download specific versions of stock ROMS and also enter the correct region in it. And to top it off the download is really quick (depending on your download speed of course)
Enter your device model number and at region enter the csc you need. It should download the correct files with the right csc. However, I did find this thread saying it is impossible to change your csc to XTC, but it is always worth a try.
If the CSC is XTC then try to follow this guide again to fix your EFS.
If it is not XTC then try to install a custom rom for your phone that has an aroma installer that allows you to pick a CSC, it might also help with the EFS problem but I am not sure.
EDIT: OH I FIX THE EFS PARTITION. NOW MY PROBLEM IS HOW TO GET OUT FROM THIS DARKNESS. HOW CAN I FIX THE IMEI AND BASEBAND WHAT EVER?
Click to expand...
Click to collapse
Since you have mentioned that your EFS partition is fixed, try to follow the guide again but correctly this time. Maybe it will work this time.
Can you tell me how you checked what your CSC is? And which phone do you have? In case this didn't work.
.
.
vigilante said:
Try to download this tool if you haven't already: https://samfirmtool.com/
I like to use this tool when flashing stock rom because I can download specific versions of stock ROMS and also enter the correct region in it. And to top it off the download is really quick (depending on your download speed of course)
Enter your device model number and at region enter the csc you need. It should download the correct files with the right csc. However, I did find this thread saying it is impossible to change your csc to XTC, but it is always worth a try.
If the CSC is XTC then try to follow this guide again to fix your EFS.
If it is not XTC then try to install a custom rom for your phone that has an aroma installer that allows you to pick a CSC, it might also help with the EFS problem but I am not sure.
Since you have mentioned that your EFS partition is fixed, try to follow the guide again but correctly this time. Maybe it will work this time.
Can you tell me how you checked what your CSC is? And which phone do you have? In case this didn't work.
Click to expand...
Click to collapse
My phone is Samsung Galaxy J8. Before i start to flash custom rom, I took a snapshot of the device's hardware information and discovered that the csc is really XTC. I have completed all the necessary steps. I did everything right, but nothing actually changed. I'm so exhausted that I might just give up. I appreciate your assistance.
If I can't retrieve the imei, it's fine, but unfortunately my phone is always restarting
EDIT: MY PHONE IS NOW FIXED. THE SIMS ARE NOW WORKING, THE SIGNAL IS BACK AND I FEEL SO HAPPY. HOW DO I FIX? WELL I USED THIS METHOD, I DELETE ALL THE FILES FROM EFS FOLDER (NOT THE PARTITION JUST THE FILE INSIDE OF IT) THEN I FLASH THE LATEST STOCK ROM WHICH IS ANDROID 10 BUT THE CSC FILE IS FROM ANDROID 9 AND AFTER THAT I USED TFT SAMSUNG MODULE WHICH IS VERY HELPFUL AND LEGIT TOOL AND ITS 100% FREE!. THEN I FIX THE IMEI AND BASEBAND USING THAT TOOL AND YES THAT SOFTWARE IS A BEAST. AND NOW ITS WORKING PROPERLY. IT TOOK ME 2 WEEKS TO SOLVE THE PROBLEM BUT IN REALITY ITS VERY SIMPLE HAHAHA! IT SAVES ME FROM SPENDING MONEY JUST TO SAVE MY PHONE BUT I DO NOT KNOW THAT I AM THE ONE WHO WILL FIX MY PHONE HAHA HOW COOL IS THAT. JUST DON'T GIVE UP NO MATTER WHAT HAPPENS!
#FVCKTHATZ3XBOX
THANKS TO THIS METHOD AND TO SIR VIGILANTE.
EVERYTHING IS POSSIBLE JUST DONT GIVE UP EVEN YOU'RE TIRED.