Database Users

Weird no IMEI & baseband unknown issue + sim card not recognised

Hi to all
I hope one or more of the very knowledgeable people out there can help me. Have a qualcomm SM-N9005 32gb European SIM model which was in a constant boot loop. Ocassionally, it would get to the the set-up screen but always go back into its loop boot once a few key presses had been made. It was on one of the 4.3 roms at the time - don't know which one.
So I put in it into download mode, flashed the stock 4.4.2 N9005XXUENB7_N9005OXAENB1_BTU rom via odin and this has solved (most of) the boot loop issues.
However, the phone is now showing as having:-
no IMEI
no baseband
no sim (despite there being a working sim in there).
If I go back into download mode, it seems an additional line has been added to the several that show at the top after flashing the stock Kitkat rom - this is "UDC START".
I don't have an EFS backup so can't restore that to get the IMEI/baseband back.
I am at a loss. I have tried a hard/factory reset - no joy. I know this kind of problem has been reported in the past and I have looked at many threads but no-one seems to have exactly the same problem and not many successful outcomes.
Can someone please give me a 'dummies walk through' of what to do - my phone expertise isn't the best, as you can see!
Many many thanks to anyone and everyone who can help.
Cheers :good:

largeruk said:
Hi to all
I hope one or more of the very knowledgeable people out there can help me. Have a qualcomm SM-N9005 32gb European SIM model which was in a constant boot loop. Ocassionally, it would get to the the set-up screen but always go back into its loop boot once a few key presses had been made. It was on one of the 4.3 roms at the time - don't know which one.
So I put in it into download mode, flashed the stock 4.4.2 N9005XXUENB7_N9005OXAENB1_BTU rom via odin and this has solved (most of) the boot loop issues.
However, the phone is now showing as having:-
no IMEI
no baseband
no sim (despite there being a working sim in there).
If I go back into download mode, it seems an additional line has been added to the several that show at the top after flashing the stock Kitkat rom - this is "UDC START".
I don't have an EFS backup so can't restore that to get the IMEI/baseband back.
I am at a loss. I have tried a hard/factory reset - no joy. I know this kind of problem has been reported in the past and I have looked at many threads but no-one seems to have exactly the same problem and not many successful outcomes.
Can someone please give me a 'dummies walk through' of what to do - my phone expertise isn't the best, as you can see!
Many many thanks to anyone and everyone who can help.
Cheers :good:
Click to expand...
Click to collapse
Have you try to look at this >>http://forum.xda-developers.com/showthread.php?t=2567133, http://forum.xda-developers.com/showthread.php?t=2627291, https://www.youtube.com/watch?v=Pai4BH3AWq8, http://forum.xda-developers.com/galaxy-s2/general/imei-baseband-guide-t1596842, http://forum.xda-developers.com/galaxy-s2/general/guide-recover-imei-9-steps-t1264021
please make some research first before attempting to follow the guide. I know some of them are not for our phone and im not sure it will work for you, but if you can do more research and keep on trying, maybe there is a way

Help Broken phone ?

Hello i have a problem with a friends LG G2 I flashed it lolipop 5.1 and then i wiped the whole internal storage clean and installed new firmware on it i tried flashing 4.4 the second time then the phone did not boot up and the screen was stuck to an error message cant quite remember it.
Anyway my friend sent it to lg and they said to him that the phone was double flashed and it could not be fixed... I need to know if i can recover the phone and if so detailed steps if possible.
Thank you very much (The phone has access to TWRP recovery.)

Please guys it is very important i need help with the matter

It can be unbricked. Your problem was probably flashing wrong bootstack since you got security boot error.
First, if you can get into download mode, do tot/kdz. There is guide here on xda
http://forum.xda-developers.com/showthread.php?t=2432476

Rooted Samsung Galaxy S4 has Nonresponsive Touchscreen

Hello all. Today I decided to root my Samsung Galaxy S4, model SM-S975L. I followed a post from these forums to the T, and everything was going great, until my phone went to sleep and then locked. After it was locked, the touch screen stopped responding. I gave it a reboot and it worked until locked yet again, and again and again and again. I then attempted to use a USSD code that was supposed to bring up some kind of fix to the touch screen firmware, I believe, and the code didn't do anything. Got a pop up that said it was running the USSD code and then nothing happened, it just disappeared. I was also unable to update the su binary when I downloaded SuperSU. Don't know if this is related. Below is the link I used to root my phone. Any help would be wonderful!
https://forum.xda-developers.com/showpost.php?p=66590962&postcount=223

Judging by that guide, you did not root your device, you installed a completely different firmware.
Not only that, but it is an old version too.
I suggest you download this version and in the configuration screen select "STOCK KERNEL".
It's pretty much the same process as with the other version.

I forgot to mention I rooted my device with the PC version of KingoRoot, and when I used a root checker app it did say it was rooted.
But say I go this route, am I to also install open gapps? And does it need to be a different version?

So my touch screen stopped working again, this time during the AROMA installer. Managed to get through that with the volume keys and power button. Then it took me back to the screen from TWRP where it says I successfully installed the zip. But my phone is locked and my touch screen is not working. What to do? Please, anybody... I don't want to just pull the battery because I still need to wipe the cache and dalvik and doing that to your phone isn't good for it anyways, from my understanding. Please, I don't want to make it even worse if I can avoid it!

rainygreeneyes said:
So my touch screen stopped working again, this time during the AROMA installer. Managed to get through that with the volume keys and power button. Then it took me back to the screen from TWRP where it says I successfully installed the zip. But my phone is locked and my touch screen is not working. What to do? Please, anybody... I don't want to just pull the battery because I still need to wipe the cache and dalvik and doing that to your phone isn't good for it anyways, from my understanding. Please, I don't want to make it even worse if I can avoid it!
Click to expand...
Click to collapse
Then flash any other ROM that does not have the word "Optimized" or "Aroma" in its name.
You can also flash the official Lineage ROM, I assume it should work.

I attempted to unroot by flashing the original firmware for my Galaxy S4 and ended up soft bricking it, I think. It says "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." Kies is not recognizing the phone. Am I correct in thinking it is soft bricked? If so, how can this be fixed? Please explain as if you were explaining to a child, I am clearly not very good at this.

rainygreeneyes said:
I attempted to unroot by flashing the original firmware for my Galaxy S4 and ended up soft bricking it, I think. It says "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." Kies is not recognizing the phone. Am I correct in thinking it is soft bricked? If so, how can this be fixed? Please explain as if you were explaining to a child, I am clearly not very good at this.
Click to expand...
Click to collapse
try flashing it with Odin again, Kies isn't needed, just connect it to PC(while in that screen) and flash the stock rom with Odin, it should recognize it.

(Soft?)-Bricked My S7 with a Flashfire Update, Need Help to Fix It?

So I've been rooting me phone for a while and have managed to never f*** up, till now, and I sincerely hope you guys can help me.
After rooting my S7 a while back, I just recently noticed SuperUser telling me that I didn't have root anymore, so I decided to follow these instructions to re-root my phone:
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I successfully followed all the steps to get root, but when I opened Flashfire it told me I could install a new update while maintaining root, so since my android is at 6.0.1, I did that and it bricked my phone.
On boot it says "Startup Failed - Use the Verizon Software Repair Assistant . . . " and on top it also says "Custom binary blocked by SECURE BOOT." I have tried going into recovery mode and deleting the system cache, but that doesn't do it. So is there any way to get the phone to properly boot while not deleting my data? I was rooting my phone precisely so I could use Titanium Backup again, so I don't have any backups stored anywhere. I have heard that flashing a recovery image with Odin can work, but would that delete my files? Someone please lend me your expertise.
My phone is a Verizon S7.

Fixed
I am surprised that no one responded to me, but what's important is that, miraculously, I managed to un-brick the phone myself without losing any data! What I did was, as my last hope (since Odin wasn't able to flash the stock image, a la the traditional soft-brick fix), decide to follow the on-screen instructions my phone was giving me and to download and run something called the "Verizon Software Repair Assistant," which can be found in the top google results after searching for the quoted name (xda doesn't let me post the link).
After putting my phone into download mode, I plugged it in, ran the software and let it work overnight. Checking on it in the morning, I found my phone, not only completely functional and working, but updated to Android 7.0 (it was 6.0.1 previously before the failed Flashfire OTA update) and still holding all of my data intact.
So, the interesting thing that I learned is that flashing to stock via Odin to fix a soft-bricked phone should not be the default resolution for potentially most people, as the carrier's default (in my case, Verizon's) repair utility managed to completely fix my phone without any side effects or data loss.
Is there anyone who could chime in on why the Repair Utility did not wipe my phone's memory, even though it warned it would?
**Note**
Verizon links to the Windows version of the repair assistant on their site, but to get the Mac version (which I used), the only way you can get it is by changing the end of the url they mention within the thread from "Win" to "Mac."

Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here

*Detection* said:
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
Click to expand...
Click to collapse
I guess I am not acquainted with this forum enough then, thanks!

Most likely the cause of the fault would be updating via FlashFire and keeping root. When the update was flashed, it most likely flashed the stock kernel and patched it for root, which is not a compatible root for our devices. Flashing the root kernel with Odin probably would have made the phone boot normally.

OTA update bootlooped S8. Need Advice

So I have a SM-G950W (BMC (Bell) originally but using unlocked on RWS (Rogers)) . Nothing has ever been flashed before except for OTA updates.
I upgraded to the Oreo OTA update and my phone got stuck in a bootloop. Ive tried wiping Cache and Factory resetting and no dice.
I decided to flash the official firmware with odin. I downoaded BMC/RWC/XAC and have tried flashing each of those through the newest Odin (1.13.1). This always ends successfully.
On bootup I get to the Samsung logo and the LED blinks red and the phone reboots. This happens indefinitely.
Ive tried wiping factory and cache again after this and it did not help. If I flash the HOME_CSC instead of CSC It gives me an encryption error and wants me to factory reset, after that I get the same red led bootloop result.
Any ideas on what I can do/ Am I missing any steps?
EDIT: Unsure if this is related but in the recovery menu it says this at the bottom:
fail to open recovery_cause(No such file or directory)
Reboot Recovery Cause is [UNKNOWN]
No support SINGLE-SKU
File based OTA
Supported API: 3
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (No such file or directory)
[libfs_merger] Error fetching verity device number: no such device or address
[libfs_merger] Couldnt get verity device number!
[libfs_merger] Error removing device mapping: no such device or address
Successfully verified dmverity hash tree

Same issue with SM-G950U1
Hi Mike, I have the same issue that you are reporting and in the recovery menu, it says the same as yours at the bottom. I didn't find any solution for having the phone stop rebooting. Please, if you have found any solution share it. I'll do the same if I can get the phone out of the boot looping. What I have done so far is flash the phone with the last official firmware downloaded with SamFirm.
I'm not sure but the problem might be related to the firmware. I'm now downloading an older firmware (with android 7.0) to check if the phone starts ok with that firmware. I'll let you know if I have good news.
Regards!
EDITED:
I found a solution!!
Hey, just want to share how I stopped the bootlooping.
You will need to flash your phone following this post https://forum.xda-developers.com/galaxy-s8+/how-to/snap-guide-flashing-standard-fw-carrier-t3627255 and download Firmware from Updato. Do not download the last version of the Firmware, because it will continue doing the bootloop. I've downloaded the following firmware:
Galaxy S8 / SM-G950U1 / 7.0 Nougat(Android ) / December 26, 17
And the phone has started!
Remember to use the last version of Odin from this post https://forum.xda-developers.com/showpost.php?p=75703449&postcount=276
If not you will not be able to flash your phone.
Hope you can fix the phone as I have done!
Let me know when you fix it.
Best!

Hey Mike,
You are not alone. Samsung apparently has messed up another OTA again. I have the same issue after Oreo update. Showed my phone to a certified Samsung repair shop and they said they had several people showing up that day with the same issue and they were not able to fix it. The best bet to contact Samsung Customer Support and they will assist you in sending your phone to a repair center.
I hope there was a faster way to fix the issue.

Hey Mike, I have updated my first answer with a workaround to fix the bootlooping. Let me know if it works in your case that I think was the same as mine.
Regards!

Hey Guys. Having the same exact issue for G955U1. I would to know if what gorito17 suggest fix the issue besides him.