Imei null baseband unknown - Galaxy S 5 Q&A, Help & Troubleshooting

First of all Ive been reading for yours looking for a solution.
My case: I was using Sixerperience V3 from Geiti94, I flashed wrong build prop and lost signal after that. I have a previous EFS folder backup.
What I did:
1) try to flash modem using Odin (more sthan 3times)
2) Flash firmware using Odin
3) Flash firmware using odin
4)install again Sixexperience
5) TRY SOME CODES I FOUND
THE MOST EXTRANGE THING. AFTER THE BUILD.PROP FLASH AND TILL NOW PHONE REFUSE TO REBOOT OR TURN OFF. IT ALWAYS GET STUCKED IN THE PROCESS WHEN I SELECT IT. IF I DONT TOUCH NOTHING IT REBOOTES ITSELD
PLEASE WHAT MORE CAN I DO. CAN I DAMAGE HARDWARE BECOUSE OF BUILPROP
THANKS

Related

Bootloop while flashing JW4

Hey, I tried flashing JW4 stock rom via ODIN which I downloaded from sammobile.
The name of the file is I9000XXJW4_I9000OXAJW4_XEU.zip and on extracting there were 2 files called JW4_JW4_JW4.tar & SS_DL.dll. I selected the tar file in PDA and flashed. The process passed but am stuck with bootloop. Plz help
I also flashed a jw4. But that was without the dll.
Anyway, after i flashed and it booted up i got a doozen errors telling me it couldnt mount different partitions.
So i gave it up as a bad one and found a thread here at xda with different stock roms and ended up with jw5.
No complications whatsoever. Yet
just google for "stock roms i9000 xda" and you should stumble over the thread i believe.
Good luck
Sent from my GT-I9000 using Tapatalk
I faced exactly the same problem: bootloop after flashing XXJW4 and many mount errors in the screen. I concluded that this firmware is not standalone in the sense that you cannot flash and repartition the device using it. Following this logic I performed these steps, leading me to a successfully recovered and fully functional XXJW4 phone:
Flash it with a full stock firmware, e.g. XXJVU (mark "repartition" as well).
Flash XXJW4 as you have done it, but make sure "Repartition" is not selected. That is, just select the tar file in the PDA field and leave the rest with the default options.
Another huge problem Got Black Screen Of Death. Am able to get my phone on to download mode but odin is not detecting my phone. HELP ME What to do?
bindaasathar said:
Another huge problem Got Black Screen Of Death. Am able to get my phone on to download mode but odin is not detecting my phone. HELP ME What to do?
Click to expand...
Click to collapse
Use another USB port. You can flash deodex version of JW4 which doesn't have any problems
bootloops
Factory Reset / Cache Wipe /
use by the Pitfile from JW 1 and flash the JW 4 ,that`s it !!
LG.G.
jpabloae said:
I faced exactly the same problem: bootloop after flashing XXJW4 and many mount errors in the screen. I concluded that this firmware is not standalone in the sense that you cannot flash and repartition the device using it. Following this logic I performed these steps, leading me to a successfully recovered and fully functional XXJW4 phone:
Flash it with a full stock firmware, e.g. XXJVU (mark "repartition" as well).
Flash XXJW4 as you have done it, but make sure "Repartition" is not selected. That is, just select the tar file in the PDA field and leave the rest with the default options.
Click to expand...
Click to collapse
great job. thanks for this
bindaasathar said:
Hey, I tried flashing JW4 stock rom via ODIN which I downloaded from sammobile.
The name of the file is I9000XXJW4_I9000OXAJW4_XEU.zip and on extracting there were 2 files called JW4_JW4_JW4.tar & SS_DL.dll. I selected the tar file in PDA and flashed. The process passed but am stuck with bootloop. Plz help
Click to expand...
Click to collapse
Your PDA file might be missing the dbdata.rfs file, see here: http://forum.xda-developers.com/showthread.php?p=24182099&highlight=dbdata#post24182099, which can cause boot loops.

IMEI NULL - no sim detected. tried many tutorials nothing helped!

Hi
it's my dad's phone and has been dead for a while now...
I have an I9500 and after upgrading to a new version (stock on the air upgrade done by my dad) it shows IMEI null and no sim card detected.
I tried these steps:
1) root, philz recovery
2) install latest modem
3) restore EFS (dont have a working backup so didnt help)
4) back to stock rom as recommended here by some folks.
5) edited the efs file (a bad efs with null imei) using HexEditor and wrote my IMEI on 0x800000 address.
6) flashed cm
nothing works!
plz help!
Your phone IMEI is listed under the battery in the phone. But I'm not sure how you re-enter it.
I lost my IMEI when I was on a custom rom 5.1.0, got it back by flashing 4.4.4 stock via ODIN
My phone is an I9505
Take the phone to Samsung and have them fix it, as you've done everything you could to resolve the problem yourself. After all, if their OTA update did screw the phone up, they should be responsible for fixing it.

dm-verity verification failed

2 days ago i flashed twrp on my pure stock note 4, i did backup my rom including EFS using twrp and then flash kyubi rom with nameless kernel, it all went well. just now i wipe data ,system, cache on twrp and restore my backup stock rom and it went well too...and then i try to flash stock rom using odin so i can get back the stock recovery mode for OTA update when MM releases.. the flashing was a sucess and phone booted but my data inside werent wipe.
so i went to recovery mode and saw this dm-verity verification failed on the bottom i proceed to wipe data and reboot my phone, its all working now no problems except i cant reset my phone with the setting inside it will just bring me to recovey mode and stay there with that message.
now i did some research, some saying will bootloop and stuffs but mine is all ok no problem except i cant reset it inside the settings..
anyone can help me get rid of that message/problem?
If you format everything in advance format in twrp and then flash stock firmware this message will go away.
got the same problem. Then I went to a local store. They helped me. Here are steps
1. Pull out your battery, check your serial number (S/N:....)
2. Download smart switch, enter emergency software recovery..... Enter your serial number
3. Turn off your phone. Enter download mode or sth ( I don't remember it clearly. just power + vol down or up. just try it)
4. Smart switch will recognize your phone. Choose a firmware to download. then wait
5. Enjoy stock firmware
Use kies3 reinstall drivers, then use emergency recovery in kies to reinstall your current firmware or opt to update to latest or most recent release or version then follow kies instructions
rooted s5 smg900r4
Hello everyone
I have found a way to fix dm-verity and DRK issues and it works like official, meaning no errors in stock recovery and OTA works with Official firmware, the problem is related to corrupted/deleted 3 files on /efs partition. I have tested it on SM-N910C so I guess it works on other Exynos variants, perhaps even on snapdragon if the partition layout is similar? Kies won't restore DRK or dm-verity check because it doesn't write to EFS. I can fix yours if someone is interested via Team Viewer, you will need the following:
1. PM contact me for Skype ID
2. Stock rom, rooted (any root method)
3. Adb debugging enabled and drivers installed (Kies or SmartSwitch)
After repair you can enter your stock recovery and confirm there is no DRK/dm-verity red letters error.
Regards,
magix01
please guide us the proceedure here .. i have a phone with same problem & i have to update it to MM ...
dork997 said:
If you format everything in advance format in twrp and then flash stock firmware this message will go away.
Click to expand...
Click to collapse
Mine still says fail. but it also says "need to check drk first" could anyone possibly help me im stuck.the phone loads up and everything. but when i try to root or anything or flash any other firmware than n910pvpu5dqi5 it fails about 4 seconds in to flashing on odin. ive downloaded every possible firmware specific to the SM-N910P but only one worked.
im a big noob with the note 4 this is my first luckily its not my daily phone yet. im very familiar with the note 3 n900t but im finding they are very different. any advice would be appreciated!
Sir, please reply
When i unlocked my bootloader on my redmi phone this warning comes, but after clicking power button it will successfully boot to system but i m confused did i flash any rom in it, is it safe or not
Manish_k said:
Sir, please reply
When i unlocked my bootloader on my redmi phone this warning comes, but after clicking power button it will successfully boot to system but i m confused did i flash any rom in it, is it safe or not
Click to expand...
Click to collapse
If you just unlocked your bootloader and thats it, your rom should still be the stock one.

IMEI & baseband 'Unknown' after installing ROM

Ever since I've flashed latest SuperMan-Rom V1.5.1 using TWRP 2.0.3-0, Since then I lost IMEI, baseband etc, I can't even able to place/receive any calls. Baseband version is 'Unknown' and IMEI & IMEISV (slot 1 & slot2 ) are 'Unknown' too. Any ideas how to resolve this? Thanks in advance.
http://forum.xda-developers.com/showthread.php?t=3379516
Tapped on my Echoe'd out G935F
You wiped your basband. Did you install incorrect CSC files. Same thing happened to me with the Superman Rom. Got to back up your efs in the future.
How do I make sure if I use to correct firmware or CSC files? Thanks for your help
iali76 said:
How do I make sure if I use to correct firmware or CSC files? Thanks for your help
Click to expand...
Click to collapse
So check this out. Try this. Go download your odin for your phone. You can download anyone. Just makensure it is newer or the same as what you have. After you add everything to Odin, click option tab and make sure Phone EFS Clear and Phone Bootloader Update are checked. Then flash the odin rom. Lmk if that works.
Psyscope said:
So check this out. Try this. Go download your odin for your phone. You can download anyone. Just makensure it is newer or the same as what you have. After you add everything to Odin, click option tab and make sure Phone EFS Clear and Phone Bootloader Update are checked. Then flash the odin rom. Lmk if that works.
Click to expand...
Click to collapse
No luck so far, as I checked both buttons to install the firmware I downloaded from Sammobile site. So my phone origin county is Vietnam, any idea which firmware should I use?
Did you backup EFS before install the ROM?
pigmich said:
Did you backup EFS before install the ROM?
Click to expand...
Click to collapse
No, I did not.
Go download smart Switch, boot your phone to download mode. In samsing smart switch click more emergency firmware initialization then click the other tab.... itll ask for your model numeber then a window below will ask for your serial. When it accepts it, it will attempt to restore it. It will show you the rom that came with your phone. Right that down. Let it do its thing. There is another thread on this forum you will need the binary for your phone.
---------- Post added at 05:18 PM ---------- Previous post was at 05:16 PM ----------
Likewise if you can get into twrp, use the file manager to delete everything in the efs folder. And actually you dont need the original rom. Just download apdn or apdu. But you will nees the binary too.
Psyscope said:
Go download smart Switch, boot your phone to download mode. In samsing smart switch click more emergency firmware initialization then click the other tab.... itll ask for your model numeber then a window below will ask for your serial. When it accepts it, it will attempt to restore it. It will show you the rom that came with your phone. Right that down. Let it do its thing. There is another thread on this forum you will need the binary for your phone.
---------- Post added at 05:18 PM ---------- Previous post was at 05:16 PM ----------
Likewise if you can get into twrp, use the file manager to delete everything in the efs folder. And actually you dont need the original rom. Just download apdn or apdu. But you will nees the binary too.
Click to expand...
Click to collapse
'SM-G935FD' does not support initializing, Please contact our service center.
Your best bet is that guide to restore your imei and baseband. Do that.
Tapped on my Echoe'd out G935F
So guys if you are getting a DRK error after flashing the Odin restore? GO ahead and try flashing Chainfire's root. This will get the phone to boot up, that is after you flash the Binary and then the Odin rom, the flash chainfire. Remember, you will have to flash Chainfire going forward forever, every time you use Odin to restore them room. Otherwise, youtherwise you will get a device root key error and refuse to boot up.
Psyscope said:
You wiped your basband. Did you install incorrect CSC files. Same thing happened to me with the Superman Rom. Got to back up your efs in the future.
Click to expand...
Click to collapse
LOL. Same thing happend to me, the superman rom 1.5 has incorrect CSCs, ATT and TMobile CSC are for S820 version. I realized it after 1.5.1 came out.
Anyway, I tried all possible method to fix it but no good. Hope someone could help us.
P1226R said:
LOL. Same thing happend to me, the superman rom 1.5 has incorrect CSCs, ATT and TMobile CSC are for S820 version. I realized it after 1.5.1 came out.
Anyway, I tried all possible method to fix it but no good. Hope someone could help us.
Click to expand...
Click to collapse
Did you flash the Binary of the Rom?
Follow the directions in this rom. See after you flash the Binary Odin, if your IMEI shows up. If it does flash the Odin Full restores, any , it doesn't matter. You will get a DRK error or you should, then Flash Chainfire
http://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
After this if you get DRK errors, Flash Chainfires CF-Root.
Psyscope said:
You wiped your basband. Did you install incorrect CSC files. Same thing happened to me with the Superman Rom. Got to back up your efs in the future.
Click to expand...
Click to collapse
Psyscope said:
Did you flash the Binary of the Rom?
Follow the directions in this rom. See after you flash the Binary Odin, if your IMEI shows up. If it does flash the Odin Full restores, any , it doesn't matter. You will get a DRK error or you should, then Flash Chainfire
http://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
After this if you get DRK errors, Flash Chainfires CF-Root.
Click to expand...
Click to collapse
Thanks for your suggestion, I've tried flash Binary(exactely followed the steps), Kies urgent recovery, but nothing help, im going to try edit my broken EFS file.
Wait, you don't restore it with Kies, you have to use Smart Switch, then choose more... Emergency Firmware Initialization... Then enter your model number and then it will ask for your serial.
So when you flash the Binary, there is a secret menu, top left corner, click it and then you should see all these menu buttons, choose settings. It will look like stock Android. Go down to backup and reset, and fully wipe through that. Then flash the Binary, see if you get an imei in the IMei screen remember you have to type *#06# in the screen keypad. If you see your imei, good, power down, boot into download mode, and flash the Full Odin Rom.... If you get DRK error, flash Chain Fire CF-Root.
---------- Post added at 02:02 AM ---------- Previous post was at 02:01 AM ----------
*********Disclaimer********** If you get your device working, you willl always need to flash Chainfire CF-Root to get it booting, no matter which Odin rom you flash. Don't ever uncheck oem unlock, then you will not be able to flash Chainfire and your device is bricked for good.
---------- Post added at 02:03 AM ---------- Previous post was at 02:02 AM ----------
One other thing when you are flashing in Odin, make sure you check Phone EFS Clear and also Phone Bootloader Update
Psyscope said:
Wait, you don't restore it with Kies, you have to use Smart Switch, then choose more... Emergency Firmware Initialization... Then enter your model number and then it will ask for your serial.
So when you flash the Binary, there is a secret menu, top left corner, click it and then you should see all these menu buttons, choose settings. It will look like stock Android. Go down to backup and reset, and fully wipe through that. Then flash the Binary, see if you get an imei in the IMei screen remember you have to type *#06# in the screen keypad. If you see your imei, good, power down, boot into download mode, and flash the Full Odin Rom.... If you get DRK error, flash Chain Fire CF-Root.
---------- Post added at 02:02 AM ---------- Previous post was at 02:01 AM ----------
*********Disclaimer********** If you get your device working, you willl always need to flash Chainfire CF-Root to get it booting, no matter which Odin rom you flash. Don't ever uncheck oem unlock, then you will not be able to flash Chainfire and your device is bricked for good.
---------- Post added at 02:03 AM ---------- Previous post was at 02:02 AM ----------
One other thing when you are flashing in Odin, make sure you check Phone EFS Clear and also Phone Bootloader Update
Click to expand...
Click to collapse
I did everything you said, first I recovered by using Smartswitch, then checked OEM Unlock and flashed binary. After boot in Binary I checked the secret menu and did a wipe in settings from that secret menu. Then I flashed the Binary again via Odin. I dialed *#06# after reboot but imei is still missing. While stay in the Binary screen about 3 mins, the screen became black and display "CP CRASH UPLOAD MODE".
I appreciate your help bro... maybe it will be solved in next few weeks, I feel tired with flashing and flashing, maybe it's time to go with IOS series lol.
P1226R said:
I did everything you said, first I recovered by using Smartswitch, then checked OEM Unlock and flashed binary. After boot in Binary I checked the secret menu and did a wipe in settings from that secret menu. Then I flashed the Binary again via Odin. I dialed *#06# after reboot but imei is still missing.
I appreciate your help bro... maybe it will be solved in next few weeks, I feel tired with flashing and flashing, maybe it's time to go with IOS series lol.
Click to expand...
Click to collapse
LOL don't stop there, but take a break. That is what I did, god I flashed so many times.
When you are rested......
Next step Flash the regular Odin Restore rom, this is different from the binary. BTW, try taking your SIM card out of the phone when you do this. If your phone boots up after the Odin restore, see what your baseband is. If it doesn't root it, then install twrp. I went into TWRP and used the file manager to delete everything in the efs files. I think something gets backed up or stored there from the bad csc files we flashed. No matter how often we flash, they are still there. Delete everything in the efs folder. Then go back to download mode.... Flash Binary.... Then Flash Odin Restore Rom.... Then Chainfire Auto-CF root.
While doing all this, check these options in Odin Clear Phone EFS, and Phone Boot Loader, I have also wiped the NVRAm option and Also repartitioned.
Psyscope said:
LOL don't stop there, but take a break. That is what I did, god I flashed so many times.
When you are rested......
Next step Flash the regular Odin Restore rom, this is different from the binary. BTW, try taking your SIM card out of the phone when you do this. If your phone boots up after the Odin restore, see what your baseband is. If it doesn't root it, then install twrp. I went into TWRP and used the file manager to delete everything in the efs files. I think something gets backed up or stored there from the bad csc files we flashed. No matter how often we flash, they are still there. Delete everything in the efs folder. Then go back to download mode.... Flash Binary.... Then Flash Odin Restore Rom.... Then Chainfire Auto-CF root.
While doing all this, check these options in Odin Clear Phone EFS, and Phone Boot Loader, I have also wiped the NVRAm option and Also repartitioned.
Click to expand...
Click to collapse
Thank you very much bro, I will try more tonight. I always backup my EFS in the internal storage, but yestarday I flashed superman 1.5 accidently wiped the entire internal storage lol... I was like what the f....
I will let you know the result. Again, thank you so much for the help
And if you are able try to restore through Samsung Smart Switch. It won't work after the restore, but honestly all are an attempt to repair what was done with Superman Rom.
After the Odin Restore, try Chainfire. The rom may look to be chain rebooting. Force it restart yourself.

IMEI number lost after flashing ROM (no backup)

I know there might be another similar topic but I couldn't find any help so far.
Basically two days ago I flashed custom ROM on my phone, I didn't make any backup. At first it worked perfectly. I decided to flash ROM again and formated my phone and found out that EFS partition was lost. I didn't get any mobile data and my IMEI number was lost (0000000). I've read that IMEI is actually stored on some chip so is there any way to restore it back? My phone is Samsung Galaxy A5 2017. Any help will be appreciated.
Trying to flash latest stock rom from sammobile but after flashing it with odin it starts bootlooping and saying "no command" again and again. When holding power + home + volume up I can NOT access recovery. Any solutions, please?
Anyone? Is there any solutions for my problem??
Is it possible to downlaod EFS file for my phone and somehow change IMEI in the file?
just flash stock rom, i did on my galaxy ace i flashed custom rom and imei gone, after stock flashed via odin imei back.
Thanks for your answer! I tried indeed flashing latest stock rom from sammobile with latest odin. But when I bootet phone up it said "no command" with dead android logo and kept bootlooping. I can try different version of rom, maybe it helps.
Still my problem is unsolved. Any clues what to do would be great.
You probably flashed a wrong firmware which is not for your variant.
Can you remove your battery? If so remove it and put it back and enter download mode by pressing volume down,power and home button. Afterwards, find the firmware which is for the specific variant of the phone. Only get the "HOME_CSC" version or else you will lose all you data. In odin, if it says added, flash the stock firmware and see if it boots to the system. If you could give me your variant, I could help and give you an even more detailed guide.

Categories

Resources