Develop Bugs

[Q] No IMEI - no baseband - Tried almost everything

Hi everyone.
As i read on so many posts, my SGN one night just drop the signal. The day after, still with no signal, i checked that had no IMEI and unknown baseband.
I had tried so many "solutions" for this to work and still nothing.
It came (when i bought it, second handed from ebay) with slimbeam rom installed. I did nothing weird to it, just simply drop signal and lost IMEI and baseband. I flashed 4.0.4, 4.2.2 from google developers web, i changed the radio for a DOCOMO one, but still nothing.
As my english is not too good, i attached a photo that explain how is my phone actually.
Please, any help will be much appreciatted as i got $300 spend on this Galaxy Nexus.

Why would you use a docomo radio? Is it a docomo phone? Have you tried flashing any other radios?

Check to make sure the contact pins that read the sim card are not damaged.

bodh said:
Why would you use a docomo radio? Is it a docomo phone? Have you tried flashing any other radios?
Click to expand...
Click to collapse
One of the solutions i've read says that with this radio the signal get fixed, but didn't work

Dmwitz said:
Check to make sure the contact pins that read the sim card are not damaged.
Click to expand...
Click to collapse
My problem isn't with the sim card, it's with no IMEI and baseband at all. Thanks anyway.

I think i just killed it.
I was trying another "solution" i found on the web, and now the phone don't turn on.
I installed an APK from the market called GSII_REPAIR and after it says to reboot the phone, now it doesn't turn on.
I read that this app is for the galaxy S2 but appear on the search for my problem's fix.

kakaroto said:
I think i just killed it.
I was trying another "solution" i found on the web, and now the phone don't turn on.
I installed an APK from the market called GSII_REPAIR and after it says to reboot the phone, now it doesn't turn on.
I read that this app is for the galaxy S2 but appear on the search for my problem's fix.
Click to expand...
Click to collapse
First I would put it in odin dl mode and flash stock, that should get the phone to boot again. I understand your english isn't that good but can you explain what you have tried. Im basically wondering if you have tried to play with the nv_data.bin file in the /factory directory as this may be able to make the phone get some functionality back.
The reason for the the possible softbrick is cause the gsII repair was probably deleting and replacing the wrong files ... I would probably say that this is a corrupt EFS directory and would work on the techniques out there to repair that ... either that or you have the same problem I have where it is a hardware issue and there is no real fix possible .... One method that may work the best is to try and use QPST and manually input your IMEI into nv_data.bin file ... many possibilities I just don't know what you have tried

cmaag said:
First I would put it in odin dl mode and flash stock, that should get the phone to boot again. I understand your english isn't that good but can you explain what you have tried. Im basically wondering if you have tried to play with the nv_data.bin file in the /factory directory as this may be able to make the phone get some functionality back.
The reason for the the possible softbrick is cause the gsII repair was probably deleting and replacing the wrong files ... I would probably say that this is a corrupt EFS directory and would work on the techniques out there to repair that ... either that or you have the same problem I have where it is a hardware issue and there is no real fix possible .... One method that may work the best is to try and use QPST and manually input your IMEI into nv_data.bin file ... many possibilities I just don't know what you have tried
Click to expand...
Click to collapse
I try to turn it on ODIN mode, and recovery mode and doesn't turn on at all.
In the same post that i saw the app, say that i can do it manually by messing with those files (nv_data.bin) but at the end mentions a nv_data file that i havent saw on the factory folder. because of that i try with the app.

kakaroto said:
I try to turn it on ODIN mode, and recovery mode and doesn't turn on at all.
In the same post that i saw the app, say that i can do it manually by messing with those files (nv_data.bin) but at the end mentions a nv_data file that i havent saw on the factory folder. because of that i try with the app.
Click to expand...
Click to collapse
so if you can't get it into odin or bootloader you have either hard bricked your phone or the battery is dead ... usually you can still get it to trickle charge if you plug it in ... if the nv_data.bin file was not in the /factory partition then i would think in some way the EFS has been corrupted or you weren't using a file manager with root access since the file is a hidden file ... biggest thing now is getting it to boot which I can only think of flashing through the bootloader or odin but i don't know everything that is possible ... someone else would probably have to help you if you can't get into either of those

Please Help me With my NOTE 2 ROOT ISSUES

I rooted my note 2 this saturday however as I did so it messed up my phone.
I created a topic here. http://forum.xda-developers.com/showthread.php?p=41721811#post41721811
I received replies however it wasn't help that I could use for someone with my rooting capablities.
The original problem
http://forum.xda-developers.com/newr...e=1&p=32466314
I followed the directions outlined in the topic I linked to above to root my Samsung Galaxy Note 2.
However once the rooting process was done my phone came back on and it was completely unable to read the sim card.
Not only that it wouldn't stay on. After 5 minutes the screen would go black however the power would still be on as I can see my led light flashing that I'm receiving messages and alerts.
To hopefully fix this I went ahead and unrooted my phone using the same application in the topic linked to above and the results are that it still won't read my sim and it the power issue is the same.
Can someone please help me out with this and provide the instructions I need to return my phone back to what it once was.
Then can someone also provide a reliable way of rooting the Samsung Galaxy Note 2 that won't cause my phone to become unresponsive.
Thanks
Click to expand...
Click to collapse
Whats happening now
I am not very advanced at all when it comes to flashing and rooting.
It's hard for me to just go and flash my phone that's why I had used that simple program that I linked to in the OP.
I just looked in the settings on my phone it it says
Mobile Network Type = Unknown
Service State = Out of service
My phone number = Unknown
IMEI = Unknown
IMEISV = Unknown
Device Status = Modified
I could really use some exact instructions on what stock rom for the note 2 is best and step by step instructions on how I flash it on.
I could also use some help with finding step by step instructions on how to root my note 2 successfully without running into this problem again.
Thanks
Click to expand...
Click to collapse
and my last post in my previous topic
So I followed the instructions http://forum.xda-developers.com/show....php?t=2052779 there to try and un-root my phone however I am still with the same results.
The phone reads my IMEI number as unknown and it still cannot read my sim card at all. My power comes on but once it goes inactive it stays off and to turn it back on I have to take the battery out, replace it, then power back on only for it to do the same thing and the process to be repeated once more.
I could really use some step by step instructions say for instance is there another way I can go about restoring stock ware on the phone. If so where are the links to the programs I need to download and what is the sequence I use those programs exactly to restore my phone back to stock. What commands and instructions need to be done within those programs.
I would like to root my phone once it's been returned back to a working functioning status as I cannot make calls or anything right now. I was looking at putting Cyaneogen Mod on it however if there is a better software I would appreciate if you could point it out. What programs do I use and how do I use those programs exactly so that I don't end up with the same result that I have right now where I
m unable to do anything with my phone.
I really hope someone helps me at the level I'm asking. I know it's a lot but I will be really grateful for the assistance.
Click to expand...
Click to collapse
I can really use some step by step instructions on what to do including links to whatever programs I need to use as well as how I use those programs exactly. Please please please someone help me as I can't afford to buy a new phone right now.

Bump.
Please don't forget about me. I really need help here.

Ok rooting is so stupid simple that id never even thought about using one of those root toolbox things. First you get the root file on your pc. I believe this is specific for your carrier and exact model of your phone. You can find this file on in the specific forum for model and carrier on this very site. Then you get odin also on your pc, also found on this site. Then follow 2-3 very simple instructions on how to flash it using odin. The exact instructions escape me since ive only done once or twice because I have never needed to go back to stock. The instructions will be found wherever odin and the root file are. Once everything listed is on your pc, from start of root process to finished is maybe 30seconds max.
Ive seen ALOT of issues where someone has screwed the pooch with those toolboxes.
You may have flashed the wrong root which has in turn wiped your carrier settings. If you can atleast turn your phone on and get to your app drawer then go into superuser or supersu app whichever app was installed and try removing root.
As far as all those settings are concerned there maybe a way to re inpit the necessary info. Like I said before, find the note specific to your carrier forum here and do a bit of reading. Thats how I stumble upon everything I know about my phone.
Another thing you could try is if your phone is still in usable state as far aswifi is concerned you could download goomanager (recovery installalation and rom tool) use that to install a new recovery, first thing id try from is a factory reset which can be done in recovery. Choose that option and reboot and see of your setting are good. If not then flash all new stock rom. With a new recovery you can flash an all stock plus rooted properly version of 4.1.2. The stock version is around 850megs so best to do that fron the pc as well. Once the download is done you can transfer that to the goomanager folder on internal memory load the app and choose the option flash roms, then check the box for the stock rom and click option order and flash on bottom and phone should reboot to recovery. Once in recovery there options for factory reset, wipe cache, wipe dalvik cache and then flash roms. Choose to factory reset again then wipe the caches then choose flash option till it where the rom is and click done it will do the rest.
Hope this gives you what you need. If there is something ive left out please someone else chime in here.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Dont know if this will help but
http://forum.xda-developers.com/showthread.php?t=2255943
sent from my T.A.R.T.I.S
(Time And Relative Tarts In Space)

Maybe try and flash back to factory image first. You can use Odin for clean factory image. You will lose all your personal files but at this point I would start from a fresh new flash.
Sent from my HTC One X using xda premium

[Q] Failed Sprint Note 2 Root Stuck in Loop, Dev not answering

I attempted a root on Samsung Note 2 Sprint version (in white). Followed all steps, however phone got stuck in a reboot loop right after I put the option 2 (root only) Odin step in. Sprint ver LPH889 (I believe that is what Odin is calling it, option 72). Toolkit used was ADB 4.1.0.
Original symptoms were that the Android updater was looping trying to load everything; being new I made it worse and tried recoveries and reloads which also failed. Now it boots, goes to splash, circling blue oval image and...it stays there.
Good news: I have access to download mode and recovery reset mode (including sideloading).
Bad news: every thread I've followed has given me an issue.
I have recovery access but I need some idea of where to go from here and searches have shown near but not exact symptoms. I have unplugged it from the pc, removed the battery, done a factory reset, attempted to reflash via Odin (root) attempted to reflash stock via Odin and so far I am still stuck in a reboot loop. Windows detects the phone but shows a problem in device manager because possibly it won't stop rebooting. Any help you can provide is appreciated and if at all possible I need to recover some form of working phone here, and soon. My girl needs it for work and Sprint's network in my area barely works from day to day (which they admit but don't credit my account for). This phone has problems sending/receiving calls, they claim it's fine, and I was forced to try a root to get some form of working device. That failed too.
I'm a newb at this...it's been years since I flashed a phone (Razor v3), so...any help would be appreciated, otherwise I have to crawl to sprint/samsung and get it replaced, which I don't want to do. Thanks.

doesitwork? said:
I attempted a root on Samsung Note 2 Sprint version (in white). Followed all steps, however phone got stuck in a reboot loop right after I put the option 2 (root only) Odin step in. Sprint ver LPH889 (I believe that is what Odin is calling it, option 72). Toolkit used was ADB 4.1.0.
Original symptoms were that the Android updater was looping trying to load everything; being new I made it worse and tried recoveries and reloads which also failed. Now it boots, goes to splash, circling blue oval image and...it stays there.
Good news: I have access to download mode and recovery reset mode (including sideloading).
Bad news: every thread I've followed has given me an issue.
I have recovery access but I need some idea of where to go from here and searches have shown near but not exact symptoms. I have unplugged it from the pc, removed the battery, done a factory reset, attempted to reflash via Odin (root) attempted to reflash stock via Odin and so far I am still stuck in a reboot loop. Windows detects the phone but shows a problem in device manager because possibly it won't stop rebooting. Any help you can provide is appreciated and if at all possible I need to recover some form of working phone here, and soon. My girl needs it for work and Sprint's network in my area barely works from day to day (which they admit but don't credit my account for). This phone has problems sending/receiving calls, they claim it's fine, and I was forced to try a root to get some form of working device. That failed too.
I'm a newb at this...it's been years since I flashed a phone (Razor v3), so...any help would be appreciated, otherwise I have to crawl to sprint/samsung and get it replaced, which I don't want to do. Thanks.
Click to expand...
Click to collapse
What method are you using to root.....I used the "toolkit" and had no problems at all.
http://forum.xda-developers.com/showthread.php?t=1957155....try this if you haven't already

vel7wil said:
What method are you using to root.....I used the "toolkit" and had no problems at all.
http://forum.xda-developers.com/showthread.php?t=1957155....try this if you haven't already
Click to expand...
Click to collapse
I thought it would to but I did not want to dig through 70+ pages of the thread when searching failed...unless I really needed to. Most of it is old and doesn't apply.
I was directed by the referenced Youtube vid. I used the options referenced for the phone in this thread with that toolkit. I backed up existing files (not as one unit, but internal files and I think OS), went for the option 2, followed the instructions and things went great through odin...until android went to update and started looping with the 'updating files' percentages. At that point I tried to restore to basic and started clearing caches and such and that is how I got to where I am.
When that failed I started looking at the leaked stock flash and that failed on shoot.ini which that guy never addressed because he thought his international version was all versions (that's why I choose 'doesitwork?' as screen name ). So i'm down to sideloading or something. I really need guidance, and I emailed the toolkit author but I'm still waiting on a reply.
Any thoughts?

doesitwork? said:
I thought it would to but I did not want to dig through 70+ pages of the thread when searching failed...unless I really needed to. Most of it is old and doesn't apply.
I was directed by the referenced Youtube vid. I used the options referenced for the phone in this thread with that toolkit. I backed up existing files (not as one unit, but internal files and I think OS), went for the option 2, followed the instructions and things went great through odin...until android went to update and started looping with the 'updating files' percentages. At that point I tried to restore to basic and started clearing caches and such and that is how I got to where I am.
When that failed I started looking at the leaked stock flash and that failed on shoot.ini which that guy never addressed because he thought his international version was all versions (that's why I choose 'doesitwork?' as screen name ). So i'm down to sideloading or something. I really need guidance, and I emailed the toolkit author but I'm still waiting on a reply.
Any thoughts?
Click to expand...
Click to collapse
When used the toolkit a year ago, I found that I had to turned off all firewalls and antivirus apps for it to work properly. Once I did that it worked fine....give it a shot...can't hurt......might even be able to repair what you've done so far.....Good Luck!!!

I'll give this my best shot...download a rooted rom from the development section and place it on your SD card.
Download toolkit from here (I take no credit for this) http://d-h.st/iu0
Put phone in download mode.
Open ODIN and uncheck "auto reboot". Then click "PDA" and add the .tar file (recovery).
Plug phone into PC (make sure to have samsung drivers installed).
Once ODIN sees the phone you can click "start".
When the recovery flash is complete, pull your battery to ensure power down.
Boot into recovery : volume up, home, power all at the same time.
Flash rooted rom.

Toolkit is an extra and unnecessary step.
http://rwilco12.com/downloads.php?d...ung Galaxy Note II (SPH-L900)/Stock ROMs/MC2/
Grab the one click flavor of choice. Use the one with 1090526 in the name as that's the full version.
Open in windows, put phone in download mode and flash. Easy Peasy.
Let me know if you have any issues with this.

Sorry for the late reply, I had some issues with the "catchpa".
The one click fix worked like a charm, thank you! I will soon be making a contrib to the site. It's a shame I couldn't root as easily :laugh: .
I know the level of work that goes into this stuff and the desire to keep on top of new gear while maintaining support for the old and I appreciate the community coming to my aid, so again, thank you!

---------- Post added at 08:14 AM ---------- Previous post was at 07:36 AM ----------
[/COLOR]
doesitwork? said:
Sorry for the late reply, I had some issues with the "catchpa".
The one click fix worked like a charm, thank you! I will soon be making a contrib to the site. It's a shame I couldn't root as easily :laugh: .
I know the level of work that goes into this stuff and the desire to keep on top of new gear while maintaining support for the old and I appreciate the community coming to my aid, so again, thank you!
Click to expand...
Click to collapse
It is usually a pretty common courtesy to hit the "thanks button" when someone helps you out.
I am not at all trying to be mean, just letting you know.

garwynn said:
Toolkit is an extra and unnecessary step.
http://rwilco12.com/downloads.php?d...ung Galaxy Note II (SPH-L900)/Stock ROMs/MC2/
Grab the one click flavor of choice. Use the one with 1090526 in the name as that's the full version.
Open in windows, put phone in download mode and flash. Easy Peasy.
Let me know if you have any issues with this.
Click to expand...
Click to collapse
hello @garwynn im trying to do this same thing.. its been so long since ive odin'd, how would i put TWRP on this now after these steps? i tried goomanager and that didnt work. (couldnt find recovery) and i tried flashing in stock recovery and got a fail . im kind of lost right now and am wondering if there is another way or do i have to do the toolkit? thanks
edit: for some reason, the tool kit links have been pulled by a mod. ..but this video helped me get twrp back. phew. zedomax to the rescue.. http://www.youtube.com/watch?v=7leb9OznhqY

Blu Advance 4.0 L A010U ROMs

Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance

I am really surprised no one has replied yet, but again I am facing the same problem and I've been searching the Internet for one month now and I found absolutely nothing for this phone (specifically for version A010U).
So I am going to post a different question in the hopes that someone will read it and help us out:
I have two Blu Advance 4.0 L A010U phones, which are identical except for the color (white and green). They were manufactured a month apart one in 10/2015 and one in 9/2015.
Unfortunately after only a couple of months of light use and for no apparent reason (did not drop it, or wet it, etc) it started going through a boot loop. It will start, show the "bold like us" logo then restart again without making it to the operating system at all. Like I said I've been looking for over a month to find a ROM (stock or modded) to reflash but with no luck. Then I had an idea. Since I have the other identical phone that's working fine, is there a trick I can do using the working phone to create a ROM that I can use in my broken one. By the way, the non working phone will allow me to get into the recovery menu, but unfortunately nothing happens if I wipe the cache or even if I reset to factory defaults.
Anyone knows what's causing that "boot loop", how to fix it and where to find a ROM or even "extract" or "create" one using a working Advance 4.0 L ???
Thank you very much!

Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.

Deuler93 said:
Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
Click to expand...
Click to collapse
I just got ahold of a couple of these devices myself and am in the process of going through all the in's and out's of them....I'm a Samsung nerd so I haven't messed with something like these in a while but I got one (that was supposedly dead bricked per the lady friend of mine I got them from) at least able to boot into factory mode and recovery via ADB and just as I'm posting this I'm in adb shell going through the device's internal memory.....so we'll see what all I find and can pull out of this one and possibly know enough to post an intelligible reply with solutions next time
The boot looping sounds like a common problem with these and when I get to that point I'm going to get rid of the stock bootanimation.zip ASAP and try something else. I get the idea that these things aren't exactly power houses built for much so the littlest thing or small bug in their coding could lead to this kind of crap happening.
Hopefully you figure yours out before I toss these out the window! lol
Cheers y salud!
---------- Post added at 02:27 AM ---------- Previous post was at 02:20 AM ----------
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
Forgot to add a couple things about your post, sorry! I beleive (and I just started digging into this phone) that the no command part is the locked bootloader these phones appear to have. I think it was a combo of holding both volume buttons down from a powered off state then pressing power button on that came up with the option for factory mode or recovery (which led to the sad 'no command' droid), i went into factory mode and theres an option for Tp Upgrade which Im assuming is F/W or something similar but I just hooked up to the PC and in that mode it's reading the internal and external memory of the phone and that's about where I'm at so far.

Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.

I can't wait to try it, thank you! And btw, were you able to get root successfully and if so, how?

Deuler93 said:
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
Click to expand...
Click to collapse
Hey Deuler93 -
You have my respect for digging out that BLU ROMs link and sharing with the rest of us. I downloaded the one for my Advance and used SP flash tool to flash the phone that was stuck on a boot-loop. Of course first I had to download and install the MediaTeK drivers for USB connectivity with my PC. Everything worked flawlessly, no glitches what so ever. All these links are easily found and widely available online if anyone is interested I can share here too. I just hope that this boot-loop was due to some software glitch and not hardware failure. Everything seems to work fine for now, keepint my fingers crossed it will NOT happen again.
Well, one less headache to worry about. By the way we're not that far, if you're ever in the Chicago area, I owe you a beer or something. Thank you!

Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.

I got temporary root using the kingroot apk. But it messed things up and I don't trust it anymore. None of the other mentioned methods worked for me either, maybe try the PC kingroot method

well this helps one thing
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.

What might happen if a ROM is used for another blu phone. ??
A similar phone as well.
Plz advise.

Damn! This thread just keeps going!
I haven't even looked here in a while, so I will bunch my commentary here. I'm also salaried now, so I bought into a OnePlus X (onyx), a more expensive cheapo device, so I do not use the 4.0L anymore.
As for rooting tools, I used the Kingroot APK successfully in the stock environment. I never tried flashing something SuperSU myself, but it could work. Is flashing a SU app possible from the fastboot interface?
And to Steve's question - it is technically possible to flash a ROM for a different device onto your own device, but is considered a bad idea due to the possibility of introducing incompatibilities and missing proprietary requirements. I feel like this would hold especially true to stock ROMs because the manufacturer probably has no interest in supporting anything more than the device that they are manufacturing for. Doing so removes many possible "compatibility" issues from even having to be considered, but I digress. In short, try to find a ROM made for your device and your device only.

Did you find the zip file for the recovery
Marya Wynter said:
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
Click to expand...
Click to collapse
i root my blu advance 4.0l a010u with the kingoroot PC apk, but i got some issues with the lock screen and some apps, so, i need some advice..
i was looking for a zip to use it via recovery but i can't find any..

Recover IMEI
srspinho said:
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
Click to expand...
Click to collapse
You dont need root to recover imei all you have to do is type *#*#84666364#*#* in your dialer and you will be entered in EngineerMode then go into connectivity ,CDS information and radio information phone 1 or 2 then you will see AT+ type something eg.A then backspace and select the first thing you see. Put a space after AT+ and then put you imei code here "IMEI" between these "" You can find your imei by removing your battery it willl be there. After sending command reboot and imei is back.

links are down....check this instead
Hey guys, links here seems to be down .
Maybe this link would be useful for you all... stock firmware can be downloaded and useful help on videos is available too... Enjoy

A505F Emergency Calls Only

Hello everyone!
I'm really new here. I hope this is the right place to ask.
Last year I bought an A505F from the internet. Unfortunately I got (kind of) scammed, since the device was from abroad and it was rooted. As I further found out, the current IMEI is from another phone. So I couldn't sell it because people really look at that stuff (smh why didn't I ). So I decided to make the best of it.
Last week I decided to Update the firmware. I don't know spesifically what kind of firmware there was before. After a bit research and hoping not to break anything, I downloaded the official firmware, matching the version on the phone, from Sammobile (A505FDDS2ASI5) and flashed it with Odin. I tried but didn't succeed to flash the latest firmware at that time. Some italian guy on youtube said that the firmware you want to flash has to match with some version of something on the phone. So I did that. Spesifically I extracted the zip, and assigned the BL, AP, CP and CSC (not HOME) files each to their corresponding field in the gui and hit Start to flash it after I put the phone into download mode. It successfully loaded the firmware. After I did that, I upgraded the phone via OTA to Android 10. I was very happy that I finally had Android 10 on my A50 and could do this fancy multi-tasking gesture from the navigation bar . Because I was the whole time at home, connected to WiFi, I didn't notice the problem. When I went out, I saw that I have no service. No call, no mobile data, etc. So my investigation continued. I then found out that there is something with the modem (?), the CP file I am flashing (?), that it has to be up to date and that OTA updates don't update that? So I went ahead and downloaded the latest firmware from Sammobile (A505FDDU5BTJ2) and flashed it as described before. Both times I carefully selected the version matching my region (TR). Unfortunately that didn't help either.
So now I am stuck with the latest firmware and an "Emergency Calls Only" warning, not being able to do anything. The IMEI is still there. I can check it with *#6...
When I go into Network Operators under Mobile networks and hit "select manually", I get "Error while searching for Network". And when I hit "select automatically", I get "Unable to connect. Try Later."
Other than that, everything seems to be okay with the phone.
I would really appreciate any help. I'm out of town thus, not gonna be able to give it to some service.
Also, all this firmware, partition, modem, etc.pp.-world... it's really exhausting to understand. Everybody is saying something else. There really should be a unifying approach to this..
Sorry for the long post

tensarflow said:
tensarflow said:
Hello everyone!
I'm really new here. I hope this is the right place to ask.
Last year I bought an A505F from the internet. Unfortunately I got (kind of) scammed, since the device was from abroad and it was rooted. As I further found out, the current IMEI is from another phone. So I couldn't sell it because people really look at that stuff (smh why didn't I ). So I decided to make the best of it.
Last week I decided to Update the firmware. I don't know spesifically what kind of firmware there was before. After a bit research and hoping not to break anything, I downloaded the official firmware, matching the version on the phone, from Sammobile (A505FDDS2ASI5) and flashed it with Odin. I tried but didn't succeed to flash the latest firmware at that time. Some italian guy on youtube said that the firmware you want to flash has to match with some version of something on the phone. So I did that. Spesifically I extracted the zip, and assigned the BL, AP, CP and CSC (not HOME) files each to their corresponding field in the gui and hit Start to flash it after I put the phone into download mode. It successfully loaded the firmware. After I did that, I upgraded the phone via OTA to Android 10. I was very happy that I finally had Android 10 on my A50 and could do this fancy multi-tasking gesture from the navigation bar . Because I was the whole time at home, connected to WiFi, I didn't notice the problem. When I went out, I saw that I have no service. No call, no mobile data, etc. So my investigation continued. I then found out that there is something with the modem (?), the CP file I am flashing (?), that it has to be up to date and that OTA updates don't update that? So I went ahead and downloaded the latest firmware from Sammobile (A505FDDU5BTJ2) and flashed it as described before. Both times I carefully selected the version matching my region (TR). Unfortunately that didn't help either.
So now I am stuck with the latest firmware and an "Emergency Calls Only" warning, not being able to do anything. The IMEI is still there. I can check it with *#6...
When I go into Network Operators under Mobile networks and hit "select manually", I get "Error while searching for Network". And when I hit "select automatically", I get "Unable to connect. Try Later."
Other than that, everything seems to be okay with the phone.
I would really appreciate any help. I'm out of town thus, not gonna be able to give it to some service.
Also, all this firmware, partition, modem, etc.pp.-world... it's really exhausting to understand. Everybody is saying something else. There really should be a unifying approach to this..
Sorry for the long post
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Did you find any solution yet?
Facing the same problem...