Database Users

No Mobile Service

Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.

Seriously???
pastorbob62 said:
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Click to expand...
Click to collapse
Not to be negative or anything but I think this is the least responsive forum on this site. I have spent hours searching for possible solutions to various problems I've encountered over the past several months, asked several questions and received little if any help. I was only able to get back from a bricked phone to where I am now by using information found on other websites. Pretty sad if you ask me.
In contrast, whenever I have asked a question on my tablet's forum I've received fast workable solutions/answers to my problems/queries. The threads are informative, well organized and contain answers to any situation I have encountered.
Granted, my current problem with my phone is my own fault for trying to customize it. And I suspect part of the problem is due to the age of this phone thus most of the "experts" have moved on to other ventures. It is also hindered by the lack of information available from Huawei and the service providers.
All of that said, if anybody has any suggestions for how I can repair the ESF partition or whatever is causing this lack of mobile service issue I would be extremely grateful. It isn't the end of the world since i have a new phone (Consumer Cellular) that I am currently using but it would be great to get this one working since it's much faster and more streamlined than my stock Consumer Cellular version.

I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.

Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
Thank you very much for your reply. It seems that you have found the answer to my problem. But unfortunately, I don't have a copy of the original stock ROM. My phone is the -51 version and any links I have found to the stock ROM are broken. There is a version I found but it is for Venezuela and I don't think it will work. I am leery to try it and totally brick my phone. My backup is apparently corrupted. I backed up my new working phone with Disk Image and attempted to restore it to the broken phone but all that did was cause it to come up to the ATT logo screen for a few seconds and then shut down. It wouldn't do anymore than that. So I restored the Stallion 3.5 image I made and am back to a great fast tablet with no phone service. I also tried backing up my IMEI on the working phone and restoring it to the broken phone but that had no effect.
It is my understanding that the -Pro version of the ROM will work, but I don't have the stock image of that either. I suspect it work might since I was able to use the -Pro version of GB on it. All of my internet searches have only turned up custom ROMs and other desperate people looking for fixes for similar problems or worse. I agree 100% with your assessment of Huawei's lack of meaningful support. It really is a shame, because these phones aren't half bad when they have been customized and OC'ed a little.
I have just about given up on it and resigned myself to using it as an MP3 player for my car system. I have learned my lesson and am leaving the working phone stock. It is rooted and I have cleaned off all of the bloatware, and set it up so most apps run from my SD card, so it really isn't half bad. At least it works.
Again, thank you for your reply and advice.

Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance

ggunzio said:
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
Click to expand...
Click to collapse
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.

Blefish said:
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Click to expand...
Click to collapse
i have exactly the same phone than you, because i installed that backup too. After installed it, the IMEI SV is 36, after installing B518 it says it is 18, but before it was 17, and i had 3g signal, but not now.
My question is, wich SV is your phone reporting?
Thank you

I also have a problem like this, but I think it's a bit more severe. My phone got stuck while charging. Couldn't reboot. Was getting stuck on the aurora loading screen(using DZO 5u20). Than reinstalled whole rom. But now I don't any signal and the phone doesn't even see a SIM card. Showing 'baseband unknown' and the IMEI and IMEI SV are also unknown. Not 0's but just unknown. Is this is a similar problem? And can something be done to fix it.
I had some backups on my sd card, untill the sd-card got fried in the phone a couple of months ago.

[Q] Soft Brick

Yesterday I noticed that there was no network service on the phone in my room and thought a reboot might solve the problem. I rebooted and it got stuck in the "Android is upgrading" screen. This is what I've tried so far:
-Factory resets
-Flashing a couple other ROMs I had in the SD Card
-Flashing Factory Images - The only factory image that booted was 4.2.2, but without IMEI or network connectivity. Any attempt to upgrade or flash a different factory image results in being stuck at the bootlogo.
-Using adb to do wipes and flash a custom ROM after flashing a factory image.
Any ideas on what I should do? I'm not sure if I can take it to warranty because even though it's only a few months old, I bought it from someone else on eBay, and the receipt is on that person's name. Any help or insight is very much appreciated. Thanks.

If flashing a factory image doens't solve the problem, it might be a hardware failure.
Try to send it back to LG/Google. The name on the receipt can be anybody.

Yeah I am having the same issue 3 days after my year mark, Google basically told me contact lg.
Sent from my Nexus 4 using Tapatalk

I have read other posts where anything newer than 4.2.2 will not boot if the imei is messed up.

[Help] No service | Radio Off | Others no problem

Hey guys!
After few days trying to fix the problem on my Nexus 6P, I still can't make it run properly so I decide to create a new thread asking you guys and this is my last hope for it. I had been using stock android 6.0.1 until I decided to upgrade to OTA 7.1.1 because I hate the notification on the statusbar. My phone worked fine, everything was OK on 6.0.1. After upgrading to android 7.1.1, my phone couldn't get any mobile signal. It still can detect the simcard, the sim toolkit app still shows but I can't use the network. Everything else works properly just like before upgrading. I tried to flash stock 7.1.2 n2g47o image from google; some custom roms like chroma, pure nexus, ressurection remix, flyme, ... and also tried to select automatic band but it is still the same. When I select automatic or any other band, it shows "select [band] unsuccessful". The service state shows "radio off" and I can't turn it back on in *#*#4636#*#*. Please help me! Thank you guys a lot.

tbmoc96 said:
Hey guys!
After few days trying to fix the problem on my Nexus 6P, I still can't make it run properly so I decide to create a new thread asking you guys and this is my last hope for it. I had been using stock android 6.0.1 until I decided to upgrade to OTA 7.1.1 because I hate the notification on the statusbar. My phone worked fine, everything was OK on 6.0.1. After upgrading to android 7.1.1, my phone couldn't get any mobile signal. It still can detect the simcard, the sim toolkit app still shows but I can't use the network. Everything else works properly just like before upgrading. I tried to flash stock 7.1.2 n2g47o image from google; some custom roms like chroma, pure nexus, ressurection remix, flyme, ... and also tried to select automatic band but it is still the same. When I select automatic or any other band, it shows "select [band] unsuccessful". The service state shows "radio off" and I can't turn it back on in *#*#4636#*#*. Please help me! Thank you guys a lot.
Click to expand...
Click to collapse
Try the flash all bat with stock rom and then relock your boot loader
Sent from my Pixel XL using Tapatalk

Are you with verizon, 7.1.1 has images for verizon only and except, may flashing one of those will fix your issue and use the flash all bat to wipe completely your phone.

bennyboy2120 said:
Try the flash all bat with stock rom and then relock your boot loader
Click to expand...
Click to collapse
coremania said:
Are you with verizon, 7.1.1 has images for verizon only and except, may flashing one of those will fix your issue and use the flash all bat to wipe completely your phone.
Click to expand...
Click to collapse
Thank you guys and sorry for not saying, I flashed both 7.1.1 (NUF26N, Mar 2017, Verizon Only) and 7.1.2 (N2G47O, May 2017) with flash-all.bat follow the instruction here https://developers.google.com/android/images but it remains the same. I read on Nexus Community that Google developers released images that fix signal problems from Feb 2017. I'm downloading this 7.1.1 (NMF26F, Dec 2016. All carriers except Verizon) and will give it a try even when it was released on Dec 2016.

tbmoc96 said:
Thank you guys and sorry for not saying, I flashed both 7.1.1 (NUF26N, Mar 2017, Verizon Only) and 7.1.2 (N2G47O, May 2017) with flash-all.bat follow the instruction here https://developers.google.com/android/images but it remains the same. I read on Nexus Community that Google developers released images that fix signal problems from Feb 2017. I'm downloading this 7.1.1 (NMF26F, Dec 2016. All carriers except Verizon) and will give it a try even when it was released on Dec 2016.
Click to expand...
Click to collapse
Again try relock on the boot loader and tell me if it helps
Sent from my Pixel XL using Tapatalk

tbmoc96 said:
Thank you guys and sorry for not saying, I flashed both 7.1.1 (NUF26N, Mar 2017, Verizon Only) and 7.1.2 (N2G47O, May 2017) with flash-all.bat follow the instruction here https://developers.google.com/android/images but it remains the same. I read on Nexus Community that Google developers released images that fix signal problems from Feb 2017. I'm downloading this 7.1.1 (NMF26F, Dec 2016. All carriers except Verizon) and will give it a try even when it was released on Dec 2016.
Click to expand...
Click to collapse
Hope you will fix it, if you got no success may you try flashing back to 6.0.0
Edit: check you imei, I will hope for you it doesn't show 0, then may you're f****d without a backup of your efs partition.

bennyboy2120 said:
Again try relock on the boot loader and tell me if it helps
Click to expand...
Click to collapse
The guide has the re-lock part so I'm 100% sure I tried to re-lock the bootloader. Not only the Google guide but on other topics on xda and Nexus Community someone re-locked the bootloader and they fixed the problem. Therefor, I followed them to re-lock but still no service
coremania said:
Hope you will fix it, if you got no success may you try flashing back to 6.0.0
Click to expand...
Click to collapse
I also tried to flash back to 6.0.0 first release firmware and 6.0.1 to get vendor for chroma / purenexus , still the same

coremania said:
Hope you will fix it, if you got no success may you try flashing back to 6.0.0
Edit: check you imei, I will hope for you it doesn't show 0, then may you're f****d without a backup of your efs partition.
Click to expand...
Click to collapse
My imei still there, I also have EFS backup ;(

tbmoc96 said:
My imei still there, I also have EFS backup ;(
Click to expand...
Click to collapse
I guess you flashed the backup, apn reset? Or flashing lineage?
Edit: take a look here, maybe deleting via fastboot and restoring with twrp will help
http://www.theandroidsoul.com/fix-e...d-wifibluetooth-issues-restoring-twrp-backup/
Sadly this problem ends up to hardware on other threads, hoping not for you

coremania said:
I guess you flashed the backup, apn reset? Or flashing lineage?
Edit: take a look here, maybe deleting via fastboot and restoring with twrp will help
http://www.theandroidsoul.com/fix-e...d-wifibluetooth-issues-restoring-twrp-backup/
Sadly this problem ends up to hardware on other threads, hoping not for you
Click to expand...
Click to collapse
I lost the network right after I upgraded my phone through OTA ;( I flashed stock firmware right after that so I guess it's not come from EFS partition. I backed up all things with TWRP after I had finished the flash-all.bat process. I'm checking out the thread, maybe there's a way out?
Yesterday I brought my phone to Huawei service center in my country but they don't officially sell the Nexus 6P in my country so they didn't take the phone because they don't have anything to fix its problem.

I would try, seems that you got nothing to loose

I'm having the same problem.
I've tried everything you did and when I select automatic bands in 4636 it does successfully, but still no signal.
Also, when I search for network in the mobile settings it always error.
I noticed that my GPS also stopped working. I only can use apps like Maps if I'm connected to a Wi-Fi.
Since the GPS stopped working this makes me believe it's an antenna problem.
If I selected WDCMA Only my network goes to Global instead of what I've selected.
I have the xt1511 (US Nexus Version), but since Nexus is always unlocked I know it isn't a CDMA/GSM trouble.

My wife's 6P started doing this about a month ago where she would randomly lose service for a minute. Today she lost it completely and it seems like there is an issue internally with the radio. I've tried multiple sim cards, factory resets, flashing the latest factory image, trying an old radio version etc. It seems like there has to be some kind of defect. I would hang on to the phone just in case there ends up being a class action lawsuit. Her phone is exactly one year and one month old.

Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing...
Now what?, we dont know if its a hardware problem or is it a software one.
Should I take it to a service center in the us? I have no warranty.
Update 06-12-17: so i kept readying and I saw someone solved the issue installing a factory image from febuary. I did it flashed it, then went into recovery and made factory reset. and it worked!!!! signal is backkkk! im soo happy!!!
Update 2 06-12-17: yeah i was happy, and soo i was going back to normal, i installed twrp, and root, phone boot up and again bye bye signal.
Update 06-14-17: Turns out that since I got to Colombia a month ago, this country has like a national IMEI list. Since I didn't subscribe my device the carrier blowies my phone and that why I had no service... Soo this ends my journey with the no service problem. They fixed it

Humanreflect said:
Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing... Now what?, we dont know if its a hardware problem or is it a software one. Should I take it to a service center in the us? I have no warranty.
Click to expand...
Click to collapse
Is your phone a H1511 or 1512? You didn't mention it explicitly but you may have changed the LTE bands using a hidden menu. Apparently this is a known bug with the hidden menu itself. Several people have had luck flashing an older version of Chroma and switching the band back to Auto. There is a link to the ROM for the 6P in this Nexus Help Forum. If you never used this menu before, you may just be able to access the menu and try setting to Auto first before flashing the ROM. You should get a confirmation that AUTO mode is selected. You also didn't explicitly mention whether the phone worked properly for a while AFTER your battery repair, OR was a direct result of your repair... which could mean it was damaged.

v12xke said:
Is your phone a H1511 or 1512? You didn't mention it explicitly but you may have changed the LTE bands using a hidden menu. Apparently this is a known bug with the hidden menu itself. Several people have had luck flashing an older version of Chroma and switching the band back to Auto. There is a link to the ROM for the 6P in this Nexus Help Forum. If you never used this menu before, you may just be able to access the menu and try setting to Auto first before flashing the ROM. You should get a confirmation that AUTO mode is selected. You also didn't explicitly mention whether the phone worked properly for a while AFTER your battery repair, OR was a direct result of your repair... which could mean it was damaged.
Click to expand...
Click to collapse
In my case I have a 1511 and I've tried this Chroma fix. No success.

v12xke said:
Is your phone a H1511 or 1512? You didn't mention it explicitly but you may have changed the LTE bands using a hidden menu. Apparently this is a known bug with the hidden menu itself. Several people have had luck flashing an older version of Chroma and switching the band back to Auto. There is a link to the ROM for the 6P in this Nexus Help Forum. If you never used this menu before, you may just be able to access the menu and try setting to Auto first before flashing the ROM. You should get a confirmation that AUTO mode is selected. You also didn't explicitly mention whether the phone worked properly for a while AFTER your battery repair, OR was a direct result of your repair... which could mean it was damaged.
Click to expand...
Click to collapse
its the 1511 version. Yes the phone worked perfectly after the repair. I was in the US, and three weeks ago I came to colombia. Suddenly it stoped working a couple of days again. I tried the chroma rom. Selected the Auto band. but it did nothing, rebooted and everything but didnt work.
Earlier today i installed a older factory image and it work, i thought it was solved, then i flashed twrp, rooted and lost service again... tried the factory images again and nothing...

Humanreflect said:
Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing...
Now what?, we dont know if its a hardware problem or is it a software one.
Should I take it to a service center in the us? I have no warranty.
Update 06-12-17: so i kept readying and I saw someone solved the issue installing a factory image from febuary. I did it flashed it, then went into recovery and made factory reset. and it worked!!!! signal is backkkk! im soo happy!!!
Update 2 06-12-17: yeah i was happy, and soo i was going back to normal, i installed twrp, and root, phone boot up and again bye bye signal.
Update 06-14-17: Turns out that since I got to Colombia a month ago, this country has like a national IMEI list. Since I didn't subscribe my device the carrier blowies my phone and that why I had no service... Soo this ends my journey with the no service problem. They fixed it
Click to expand...
Click to collapse
Well, I've just checked your latest update today.
What did you do to include your device in this national list? And how did you find out about this list? I need to check if Brazil has it as well. Do you still have signal without problem?
Thanks.

Debuffer said:
Well, I've just checked your latest update today.
What did you do to include your device in this national list? And how did you find out about this list? I need to check if Brazil has it as well. Do you still have signal without problem?
Thanks.
Click to expand...
Click to collapse
Hey, i went to my carrier. And they tol me it was blocked. And they un blocked it.
It was imei blocked because ut wasebt in that imei national list. Soo it didnt work with any carrier.

you've fixed your phone
Humanreflect said:
Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing...
Now what?, we dont know if its a hardware problem or is it a software one.
Should I take it to a service center in the us? I have no warranty.
Update 06-12-17: so i kept readying and I saw someone solved the issue installing a factory image from febuary. I did it flashed it, then went into recovery and made factory reset. and it worked!!!! signal is backkkk! im soo happy!!!
Update 2 06-12-17: yeah i was happy, and soo i was going back to normal, i installed twrp, and root, phone boot up and again bye bye signal.
Update 06-14-17: Turns out that since I got to Colombia a month ago, this country has like a national IMEI list. Since I didn't subscribe my device the carrier blowies my phone and that why I had no service... Soo this ends my journey with the no service problem. They fixed it
Click to expand...
Click to collapse
I can not have a case if you are not resolve. Im vietnames my english very bad sory!. Help me

"Unfortunately" error after IMEI repair

Hello everyone,
Couple of months ago I was trying something with my SM-N900 and I really messed things up and didn't backup my efs back then, I ended up visiting a repair shop that was able to fix it and restore my IMEI. Now I notice that I get Unfortunately [app name] has stopped, especially with Facebook Messenger and Google services. I am really terrified of flashing anything, and repair shops are crazy expensive here. I tried cleaning apps' cache, rebooting, factory reset. Please, is there a way to fix this?

HeroTK said:
Hello everyone,
Couple of months ago I was trying something with my SM-N900 and I really messed things up and didn't backup my efs back then, I ended up visiting a repair shop that was able to fix it and restore my IMEI. Now I notice that I get Unfortunately [app name] has stopped, especially with Facebook Messenger and Google services. I am really terrified of flashing anything, and repair shops are crazy expensive here. I tried cleaning apps' cache, rebooting, factory reset. Please, is there a way to fix this?
Click to expand...
Click to collapse
Have you tried a fresh Odin flash to stock?

ShaDisNX255 said:
Have you tried a fresh Odin flash to stock?
Click to expand...
Click to collapse
I am worried that it will mess up my IMEI, I don't know why.

Flashing a stock rom has never messed up the imei on any Samsung phone I have used. It’s usually a custom rom or kernel that messed up my imei.

audit13 said:
Flashing a stock rom has never messed up the imei on any Samsung phone I have used. It’s usually a custom rom or kernel that messed up my imei.
Click to expand...
Click to collapse
How can I know the right stock rom? Because I really don't know the exact region of my phone so it's a bit confusing for me.

Do you where where the phone came from? If it is running a stock ROM now, install samsungphoneinfo from the Play Store to find the csc which will tell you carrier.
Stock firmware is here for the sm-n900: https://www.sammobile.com/firmwares/galaxy-note3/SM-N900/

My divice is dying!!!

Yah, I'm serious! I'll tell you in detail.
Weeks ago, when I tried to flash stock rom, I made a big mistake that made my deivice hard bricked and then I found the reason in this thread: https://in.c.mi.com/thread-1095941-1-0.html.
I immediately brought my device to Mi Support Center, they made it alive but other problems came and I posted this thread: https://forum.xda-developers.com/mi-a1/help/help-soft-brick-t3860620 (thanks for people who tried to help me)
I found that my device lost persist partition, so that I flashed it, done, however, I relized that my device lost IMEI and BASEBAND, too.
I tried to restored my IMEI by QCN file but I only got sim 1 IMEI, I flashed BASEBAND and my deivice stuck in bootloop.
After a long time, I asked for someone to help but they couldn't do anything and then I found some problems.
1. IMEI dosen't show anything now and BASEBAND is unknown.
2. I can't flash Android 8.1 or higher versions on my device, it only accepts 8.0 and lower versions. If I flash 8.1, it continuously reboot when Android One logo shows up. But nothing happens when I flash 8.0.
Three days ago, I brought my device to Mi Support Center again, they said my mainboard is broken, it need replacing but I denied because the cost is too expensive, about $145. I took it back, tried to flash 8.0 version and installed update, sadly, my device is locked now and I can't flash anything. I think I can flash 8.0 via testpoint method, but the important thing is that I don't know what's exactly happenning with my device.
Why I can't flash 8.1 version and can I take my IMEI back?
I'm tired to find the answers days and I'm thinking to sell my death device with a cheap price about $40 for screen and camera only.
Someone help me, please!
By the way, I'm in Vietnam.

manhnl311 said:
Yah, I'm serious! I'll tell you in detail.
Weeks ago, when I tried to flash stock rom, I made a big mistake that made my deivice hard bricked and then I found the reason in this thread: https://in.c.mi.com/thread-1095941-1-0.html.
I immediately brought my device to Mi Support Center, they made it alive but other problems came and I posted this thread: https://forum.xda-developers.com/mi-a1/help/help-soft-brick-t3860620 (thanks for people who tried to help me)
I found that my device lost persist partition, so that I flashed it, done, however, I relized that my device lost IMEI and BASEBAND, too.
I tried to restored my IMEI by QCN file but I only got sim 1 IMEI, I flashed BASEBAND and my deivice stuck in bootloop.
After a long time, I asked for someone to help but they couldn't do anything and then I found some problems.
1. IMEI dosen't show anything now and BASEBAND is unknown.
2. I can't flash Android 8.1 or higher versions on my device, it only accepts 8.0 and lower versions. If I flash 8.1, it continuously reboot when Android One logo shows up. But nothing happens when I flash 8.0.
Three days ago, I brought my device to Mi Support Center again, they said my mainboard is broken, it need replacing but I denied because the cost is too expensive, about $145. I took it back, tried to flash 8.0 version and installed update, sadly, my device is locked now and I can't flash anything. I think I can flash 8.0 via testpoint method, but the important thing is that I don't know what's exactly happenning with my device.
Why I can't flash 8.1 version and can I take my IMEI back?
I'm tired to find the answers days and I'm thinking to sell my death device with a cheap price about $40 for screen and camera only.
Someone help me, please!
Anyway, I'm in Vietnam.
Click to expand...
Click to collapse
Do a data format, then install anything.

justboryata said:
Do a data format, then install anything.
Click to expand...
Click to collapse
How to flash something when bootloader is locked? Anyway, that's not point, I can flash via testpoint method, the point is why I can't use 8.1 and can I take my IMEI back, thanks!

manhnl311 said:
Yah, I'm serious! I'll tell you in detail.
Weeks ago, when I tried to flash stock rom, I made a big mistake that made my deivice hard bricked and then I found the reason in this thread: https://in.c.mi.com/thread-1095941-1-0.html.
I immediately brought my device to Mi Support Center, they made it alive but other problems came and I posted this thread: https://forum.xda-developers.com/mi-a1/help/help-soft-brick-t3860620 (thanks for people who tried to help me)
I found that my device lost persist partition, so that I flashed it, done, however, I relized that my device lost IMEI and BASEBAND, too.
I tried to restored my IMEI by QCN file but I only got sim 1 IMEI, I flashed BASEBAND and my deivice stuck in bootloop.
After a long time, I asked for someone to help but they couldn't do anything and then I found some problems.
1. IMEI dosen't show anything now and BASEBAND is unknown.
2. I can't flash Android 8.1 or higher versions on my device, it only accepts 8.0 and lower versions. If I flash 8.1, it continuously reboot when Android One logo shows up. But nothing happens when I flash 8.0.
Three days ago, I brought my device to Mi Support Center again, they said my mainboard is broken, it need replacing but I denied because the cost is too expensive, about $145. I took it back, tried to flash 8.0 version and installed update, sadly, my device is locked now and I can't flash anything. I think I can flash 8.0 via testpoint method, but the important thing is that I don't know what's exactly happenning with my device.
Why I can't flash 8.1 version and can I take my IMEI back?
I'm tired to find the answers days and I'm thinking to sell my death device with a cheap price about $40 for screen and camera only.
Someone help me, please!
By the way, I'm in Vietnam.
Click to expand...
Click to collapse
These files were dangerous dude and they brick parts of your motherboard like imei and baseband. So if you need a fix replace it

billis2020 said:
These files were dangerous dude and they brick parts of your motherboard like imei and baseband. So if you need a fix replace it
Click to expand...
Click to collapse
I can buy a new one with the cost to replace to the whole mainboard. In fact, I accept the thing that I can't use SIM anymore, I just don't know why I can't upgrade to 8.1 or higher