Database Info

[Q] Blu One M Sim issues.

I followed instructions to flash my one m using roms here, through trial and error i found a couple that worked but i ended up just going with cyanogenmod because it was familiar. when i booted it up i had an issue with my camera and micro sd, it said i didn't have storage/sd and the camera would fc, the gallery as well. the file manager seemed to access everything just fine though. i tried second party cameras/galleries to the same effect. so w/e my phone worked it didn't bug me too much at first...
then i noticed there were updates for the rom so i flashed the latest one and suddenly i needed to unlock my sim. that had been referenced in a thread here so based on that thread i entered 12345678 and wham it locked. i tried flashing a kitkat rom and the the stock blu one m rom here and neither helped. i took it to my metro store and they said i needed a new sim so i bought one and no dice. it won't even let me access the sim settings. it also doesn't show my imei anywhere in the phone info anymore.
i'm not really sure what to do at this point. i made a few backups at one point but i think i accidentally deleted them because i am super smart....

[Trouble] N8000: SIM lost after wrong recovery flash

Hi,
I flashed the new TWRP2.8.6.0 on my N8000 (before I had 2.8.5.x).
Accidently I flashed the "p4noterf" instead of "n8000" version (with Odin 3.09).
When my SIM-card was not detected, I recognized the error.
Then I flashed TWRP 2.86.0 "n8000"-Version, but SIM was still not recognized.
After that I restored different ROMS (OMNI 5.1; CM12..) from which I had backups, including EFS/IMEI and all other stuff.
Also I wiped (factory, cache, dalvik, system, data) and restored the ROMS again (including EFS...).
But whatever I do: SIM is gone / not detected.
I would be grateful for any help/advice :laugh:!

Me too. I was fiddling with my old 10.1 and decided to give it a run on Lollipop 5.1. I updated the CWM to TWRP and sim recognition was lost. IMEI is blank and mobile network is non existent.
Could any kind soul please advise?
Update: Going back to 4.4.2 stock does show the mobile network signal but there is a notification for SIM card to be inserted. IMEI is back but SIM is still not recognised.

3ftguru said:
Update: Going back to 4.4.2 stock does show the mobile network signal but there is a notification for SIM card to be inserted. IMEI is back but SIM is still not recognised.
Click to expand...
Click to collapse
Perhaps yous can try to restore EFS now (once again) - now that you are back to stock.
There is a thread in a German forum that in 1. step going back to stock saved IMEI. Then, as second step to restore EFS brought SIM back again... Hopefully this helps
Best wishes:good:

Tried using EFS Pro to backup and restore again but it didn't work. Interesting enough, my ROM version stated by EFS Pro is pnote and not N8000. So now downloading and flashing a confirmed N8000 stock rom to see if it works.
Update: Another rom still show p4note which means somewhere in EFS the n8000 is replaced with p4note. Anyone got any idea how to edit back?

3ftguru said:
Update: Another rom still show p4note which means somewhere in EFS the n8000 is replaced with p4note. Anyone got any idea how to edit back?
Click to expand...
Click to collapse
Interesting, indeed.
There's a thread on XDA named "Recover your IMEI in 9 steps". I think it's a description of the problem we are faced with or something very close to, at least.
Unfortunately I am not allowed to post links here :crying: If you PM me I can send it to you.
The logic is the same I found in the German thread: go back to Stock and then change/manipulate EFS.
The crucial file in EFS folder seems to be nv_data.bin perhaps the needed information is in there. There is also a ".bak" and ".md5" of this file.
On my working S3 nv_data.bin changes constantly, date of the file is always "new", not older than a few hours. On the non working N8000 the file date is constant and from early April.
I hope to have some time to explore and test something this weekend .
A further idea might be to (also) go back to n8000 stock recovery - perhaps twrp messed something there.
Again, I can not post the link, just seaarch for the term in www.

Back again!
Hi,
finally SIM is back again :good:
1. Flashed n8000 Stock recovery (probably unnecessary, is inculded in stock rom)
2. Flashed Stock ROM; rather old version (4.1.2) from sammobile: N8000XXCMI2_N8000OXACMI2
2a: Got endless boot loop
3. Booted to stock-recovery --> factory reset (or factory wipe?)
4. Booted to sys and SIM was there :laugh:
Ev. it matters which ROM is chosen, probably older ones (close to production date) are the better choice.
@3ftguru: Hope this will work for you too!
UPDATE: DO NOT USE AUTOMATIC UPDATE (OTA by Samsung) after flashing!
This broke my n8000 again, got an endless "Samsung N8000" Start logo after that.
I could not get into recovery, could not shut it down, only bootload was accessible.
Then I flashed same ROM again with odin - nothing changed.
Finally flashed 4.4.2 - and it's back again - SIM o.k., can get into recovery ... ufffffff!
This is the file I used form sammobile: N8000XXUDNE4_N8000OXADNE4

My device type is listed as p4note and not N8000 anymore even after flashing an old 4.1.2 Samsung ROM. Scratching my head on this one.
Anyone knows how to convert back to n8000 for device type?

Same problem. It brokes after installing TWRP.
---------- Post added at 05:47 PM ---------- Previous post was at 05:46 PM ----------
xd_surfer_g said:
Hi,
finally SIM is back again :good:
1. Flashed n8000 Stock recovery (probably unnecessary, is inculded in stock rom)
2. Flashed Stock ROM; rather old version (4.1.2) from sammobile: N8000XXCMI2_N8000OXACMI2
2a: Got endless boot loop
3. Booted to stock-recovery --> factory reset (or factory wipe?)
4. Booted to sys and SIM was there :laugh:
Ev. it matters which ROM is chosen, probably older ones (close to production date) are the better choice.
@3ftguru: Hope this will work for you too!
UPDATE: DO NOT USE AUTOMATIC UPDATE (OTA by Samsung) after flashing!
This broke my n8000 again, got an endless "Samsung N8000" Start logo after that.
I could not get into recovery, could not shut it down, only bootload was accessible.
Then I flashed same ROM again with odin - nothing changed.
Finally flashed 4.4.2 - and it's back again - SIM o.k., can get into recovery ... ufffffff!
This is the file I used form sammobile: N8000XXUDNE4_N8000OXADNE4
Click to expand...
Click to collapse
So do you use TWRP at old ROM?

Have found solution:
1. Install stock ROM (older) - sim will be working
2. Install TWRP 2.6.3.1
3. Flash something - and sim will be working, too

CyanoFresh said:
Have found solution:
1. Install stock ROM (older) - sim will be working
2. Install TWRP 2.6.3.1
3. Flash something - and sim will be working, too
Click to expand...
Click to collapse
doesnt work for me whether i got use pit to repartition or just a 4.0.4 stock rom to flash. The SIM just doesnt get recognised.
Guess I just have to use it as a N8010 instead.

3ftguru said:
doesnt work for me whether i got use pit to repartition or just a 4.0.4 stock rom to flash. The SIM just doesnt get recognised.
Guess I just have to use it as a N8010 instead.
Click to expand...
Click to collapse
Try this 4.4.2 rom:
Thread (Ukrainian language) - http://www.ex.ua/91621823
direct download - http://www.ex.ua/load/171252309
torrent - http://www.ex.ua/torrent/171252309
Flash N8000XXUDNH2_N8000OXEDNH1_N8000XXUDNH2_HOME.tar.md5 by Odin. Try to factory reset. it should work

Thank you so much for this thread an especially for this posting!!!
I had the same problem, maybe flashed a wrong recovery/firmware/rom or whatever but I lost access to the SIM card in my N8000. After I follow your steps below now I'm back in stock rom with SIM-access and can reconfigure my tablet.
xd_surfer_g said:
Hi,
finally SIM is back again :good:
1. Flashed n8000 Stock recovery (probably unnecessary, is inculded in stock rom)
2. Flashed Stock ROM; rather old version (4.1.2) from sammobile: N8000XXCMI2_N8000OXACMI2
2a: Got endless boot loop
3. Booted to stock-recovery --> factory reset (or factory wipe?)
4. Booted to sys and SIM was there :laugh:
Ev. it matters which ROM is chosen, probably older ones (close to production date) are the better choice.
@3ftguru: Hope this will work for you too!
UPDATE: DO NOT USE AUTOMATIC UPDATE (OTA by Samsung) after flashing!
This broke my n8000 again, got an endless "Samsung N8000" Start logo after that.
I could not get into recovery, could not shut it down, only bootload was accessible.
Then I flashed same ROM again with odin - nothing changed.
Finally flashed 4.4.2 - and it's back again - SIM o.k., can get into recovery ... ufffffff!
This is the file I used form sammobile: N8000XXUDNE4_N8000OXADNE4
Click to expand...
Click to collapse

Tried the Ukrainian ROM but still didn't work.
Now I suspect is that I have accidentally made some changes to the EFS or had damaged the SIM port physically. Otherwise I should have been able to achieve the ROM recognizing the sim card.
Sent from my SM-N910G using Tapatalk

Not working
Sim card comeback after i was reinstall rom 4.4.2, but sim card not working when I install cm12.1 .:crying:

Recovery phone
I thing sim card will working if you recovery phone, file recovery boot with odin:
https:// drive.google.com/file/d/0B_SHfdpTGxm6cHhweGRCR05jYlE/view
After reinstall cm 12.1, 13 for Note 10.1 - N8000.
Good luck.

xd_surfer_g said:
Hi,
finally SIM is back again :good:
1. Flashed n8000 Stock recovery (probably unnecessary, is inculded in stock rom)
2. Flashed Stock ROM; rather old version (4.1.2) from sammobile: N8000XXCMI2_N8000OXACMI2
2a: Got endless boot loop
3. Booted to stock-recovery --> factory reset (or factory wipe?)
4. Booted to sys and SIM was there :laugh:
Ev. it matters which ROM is chosen, probably older ones (close to production date) are the better choice.
@3ftguru: Hope this will work for you too!
UPDATE: DO NOT USE AUTOMATIC UPDATE (OTA by Samsung) after flashing!
This broke my n8000 again, got an endless "Samsung N8000" Start logo after that.
I could not get into recovery, could not shut it down, only bootload was accessible.
Then I flashed same ROM again with odin - nothing changed.
Finally flashed 4.4.2 - and it's back again - SIM o.k., can get into recovery ... ufffffff!
This is the file I used form sammobile: N8000XXUDNE4_N8000OXADNE4
Click to expand...
Click to collapse
Hi there, i had flashed cm12.1 for N8000 and didnt backup efs. So even after returning to stock rom, i couldn't find my SIM. My IMEI was lost, and baseband version was showing unknown. So, can I use your method to restore my IMEI and SIM problem? Please reply fast as I need it within a few days. Thank you.

[Q] MTK rom, installation aborted

The Afterlife6.0 was said to be compatible with my Nitro 401D which has the aame MTK no.
However, whenever I try to flash it (using cwm) it says installation aborted. It doesnt say any status about it eg Status 6 or Status 7 but i still used the fix for one which is trying to change the name in the updater script to fit the name of my phone but when I looked, it doesnt have that particular line for checking the name. And the other one was changing the directory of the lines in it but I didnt want to change it because i wasnt so sure about the directories myself.
Ive tried downloading from another source, still didnt work. Now Im wondering maybe its my phone so Ive been considering using SP flash to force it in(? Im still not quite sure what it does tho) and also change my custom recovery (currently cwm) to twrp or ctr. Maybe my phone cant flash anything at all so ive been also considering trying to flash a small file or like a test rom, are there any of those?
What should I do next? Im scared of forcing it in causr it says that if the phone has the wrong preloader my phone can never be recovered..

rexel325 said:
The Afterlife6.0 was said to be compatible with my Nitro 401D which has the aame MTK no.
However, whenever I try to flash it (using cwm) it says installation aborted. It doesnt say any status about it eg Status 6 or Status 7 but i still used the fix for one which is trying to change the name in the updater script to fit the name of my phone but when I looked, it doesnt have that particular line for checking the name. And the other one was changing the directory of the lines in it but I didnt want to change it because i wasnt so sure about the directories myself.
Ive tried downloading from another source, still didnt work. Now Im wondering maybe its my phone so Ive been considering using SP flash to force it in(? Im still not quite sure what it does tho) and also change my custom recovery (currently cwm) to twrp or ctr. Maybe my phone cant flash anything at all so ive been also considering trying to flash a small file or like a test rom, are there any of those?
What should I do next? Im scared of forcing it in causr it says that if the phone has the wrong preloader my phone can never be recovered..
Click to expand...
Click to collapse
Your Device name and SOC?

MTKcROM said:
Your Device name and SOC?
Click to expand...
Click to collapse
My device name is Arc Mobile Nitro 401D but I dont know what SOC means (system on a chip if i guessed right) and or what it refers to but if it refers to the MtkXXXX then its mtk6572

rexel325 said:
My device name is Arc Mobile Nitro 401D but I dont know what SOC means (system on a chip if i guessed right) and or what it refers to but if it refers to the MtkXXXX then its mtk6572
Click to expand...
Click to collapse
Do you install CWM successfully? Did you try another custom rom?

MTKcROM said:
Do you install CWM successfully? Did you try another custom rom?
Click to expand...
Click to collapse
From everything I have done on trying to root this phone, I guess MTKdroid tools installed CWM in the process. It is rooted now tho, checked with rootchecker basic. I havent tried any other roms since Afterlife 6.0 is the only one i found.

UPDATE:
Apparently, the CWM wasn't properly installed, my bad :crying:
I tried to install another ROM like Lollifox (will try MIUI later, still downloading) but I don't think I ported it successfully tho because it just showed installation aborted, no Status whatsoever.
I have now flashed Afterlife6.0. However, its now stuck at boot but a while ago it was on boot loop but after wiping caches and doing a hard reset, its now on boot forever. By boot I mean it just shows the Sony logo (supposedly the Arc Mobile logo before I flashed the rom) then the logo disappears and then its just a black screen (a black screen as in its still turned on and not a black screen as you would see when a phone is off).
I'll try to flash my stock rom and root it again so that I could flash other roms for now while waiting for your reply.

try stock rom on the official site. than try to update cwm and try rooting again.

I already fixed it by flashing the stock tho so no worries I guess.
I successfully ported Lollifox but I encountered a problem where I couldn't save anything because my phone doesn't recognize my SD card. It can be seen in the settings/storage though but what the rom can't do is recognize that the "SD card" is internal not external. Its sort of hard to explain, I have 2 storages: Internal memory and Phone storage. The internal memory is the default place where apps go while the Phone storage acts like the SD card of this phone but its internal as well ( at least that's how it acts on the stock ROM). I tried unmounting it (apparently I have that option on Lollifox but its internal so I don't know how that's possible) and remounting it but no dice. Also, since it doesn't recognize the SD card, it kind of explains why there's no USB mass storage option when I connect it.
I tried to port the MIUI and did the 2 ways of porting it told in the site where the rom came from but whenever I flash it, it boots up and gets stuck at the logo of MIUI.
I'm leaning away from Afterlife 6.0 now cause I can't really see it would be a better ROM (and you got to give it that the themes of MIUI and Lollifox are pretty AF) but I think its more suitable (still can't flash it tho) . Can anyone give thoughts on the best rom for this or a fix for these problems?

rexel325 said:
sometimes you need to format the phone memory at the beginning for one time after you install new ROM. Try that and restart the phone. One time i did this like this problem. Sorry for my english.
Click to expand...
Click to collapse

Solved
I think I already solved my own problem though. I just had to do a few tweaks and do a little bit of trial and error myself. However, I still couldn't flash Afterlife (also tried porting it myself and Im suppose to do a logcat or something but I lack free time) but I still have a rom flashed don't worry. Kind of feel sorry it feels like a waste of a thread.
Now Im asking for this thread to be closed(or atleast I think thats how it works cause I dont seem to have that option myself)
Thank you

cm13 setup STUCK AT 'JUST A SEC' SCREEN (URGENT!!!)

Hi guys
I was trying to install the official cm13 nightly with gapps on twrp
and at the end of the setup, I am stuck at the last step which is Just a Sec screen
Any help would be appreciated thanks.

hjrry said:
Hi guys
I was trying to install the official cm13 nightly with gapps on twrp
and at the end of the setup, I am stuck at the last step which is Just a Sec screen
Any help would be appreciated thanks.
Click to expand...
Click to collapse
try a different gapps package? did you clear cache and dalvik, plus do a factory reset before installing?

Nitefire77 said:
try a different gapps package? did you clear cache and dalvik, plus do a factory reset before installing?
Click to expand...
Click to collapse
Yes did everything you mentioned and latest 6.0 gapps pico package
any idea what that screen is about?

hjrry said:
Yes did everything you mentioned and latest 6.0 gapps pico package
any idea what that screen is about?
Click to expand...
Click to collapse
Try a different GAPPS package, maybe a larger one. Just to see. For one, some people complained of missing features like notification bar pulldown with the very smallest GAPPS package. Now this isn't a reason it shouldn't install, but try a different package to see if it make a difference in completing the installation.

hjrry said:
and at the end of the setup, I am stuck at the last step which is Just a Sec screen
Click to expand...
Click to collapse
Same thing here, using a 2014811 (Wt88047, Redmi 2 WCDMA).
Tried ""nightly" 20160512, 20160517 and 20160519. Did the usual Wipes, tried also with no wifi and no SIM card.
Nothing seems to help, I am stuck at "Just a Sec..."
The SKIP option does not work.
The back button works and let me get back until the Language selector.
D.

plasticdoc said:
Same thing here, using a 2014811 (Wt88047, Redmi 2 WCDMA).
Tried ""nightly" 20160512, 20160517 and 20160519. Did the usual Wipes, tried also with no wifi and no SIM card.
Nothing seems to help, I am stuck at "Just a Sec..."
The SKIP option does not work.
The back button works and let me get back until the Language selector.
D.
Click to expand...
Click to collapse
First, restore your backup. You did make a backup, right?
Then re-flash after you download a different GAPPs package. Some say Open Gapps works great for them, while others say Slim GAPPS is best. We don't know why some don't work for some people but work for others.
If that doesn't fix your issue, then try this:
Download the unofficial CM13 found here in this forum and try it.
Also, download Resurrection Remix (Marshmallow) and try it.
Both are variants of CM13 anyways. Just trying to see if something is wrong with your phone and you can't flash any ROM whatsoever or if it's something your phone doesn't like about official CM13.
The unofficial CM13 is CM13 with just a few of the Resurrection Remix tweaks thrown in, like permissions to download Moto apps from the Google Store, etc. It's 90% CM13, 10% RR.
If none of those CM13 variants work, you can alway try AOSP Mokee (Marshmallow).
IF NONE of those work, either your phone is severely messed up or you are doing something wrong.

ChazzMatt said:
Download the unofficial CM13 found here in this forum and try it.
Click to expand...
Click to collapse
Right. This one installed without any problems.
Still, I would like to be able to install the "official" one.
I wonder, what may be the bug in that keeps it "freezing" at the "Just a Sec..." message.
D.

plasticdoc said:
Right. This one installed without any problems.
Still, I would like to be able to install the "official" one.
I wonder, what may be the bug in that keeps it "freezing" at the "Just a Sec..." message.
D.
Click to expand...
Click to collapse
I don't know. Not everything with our phones is completely logical. Occasionally more of an art than science. Same reason one GAPPs package works well for someone but won't install for another person. Open GAPPS vs Slim Gapps.
Here's a personal example... My wife and I both have XT1225 with CM12.1 and yet hers can't run BHB27 kernel. Occasionally I'll get it to install, and run OK for a day or two but then next time I reboot it it does endless bootloops. I even tried different governors and I/O schedulers. Nada.
Mine is a Puerto Rico (unlocked Claro) XT1225 I flashed to India 5.0.2 before flashing to CM.
Her's is a Mexico direct-from-China-Motorola factory XT1225 I flashed to India 5.0.2 before flashing to CM.
Later I flashed Puerto Rico XT1225 radio over both.
There's just some difference there in her XT1225 which does not like BHB27 kernel.
Maybe if I did an exhaustive formatting of the entire internal memory and reinstallation of everything on her phone, it would work. But instead I take the easy way out and she's just running CM12.1 with default CM kernel, and that's running well. So, I go with what works.

phone app not working
unfortunately telephone has stopped working.

wajid1213 said:
unfortunately telephone has stopped working.
Click to expand...
Click to collapse
What does that have to do with this thread? > cm13 setup STUCK AT 'JUST A SEC' SCREEN (URGENT!!!)
I don't even think you are using this phone, to be honest. So, why did you post here? You posted same thing in another thread, for ANOTHER PHONE, not even related to Quark.
You seem to be using this phone: Xiaomi Redmi 2 -- since all your other posts before this and after this are over there.
http://forum.xda-developers.com/search.php?searchid=422491957

[Completed] Samsung A3 (SM-A300FU) Cyanogenmod 13 not working but 12.1

I have been running Cryogenmod 12.1 for my Samsung SM-A300FU but its UNOFFICIAL and a preview the webpage i got it off says 'Wifi and Camera NOT WORKING'. I guess thats what i get for following my mates advice.
Because of this, i looked at CM13 (Android 6) which i got off the XDA site and i have made sure it is for my phone and model, the SM-A300FU. Of course, being my luck it didnt work. I get the error of 'Executing updater binary in zip' and i have wiped my phone then tried to install it and i have also tried to completly remove all OS and files then install it which apparently fixed it for people, but not me of course. In a desperate measure i even bluetoothed the ROM to another phone then back into my SM-A300FU to get it onto the internal storage but that obviously didnt change anything.
Finally, i gave up and tried to downgrade back to Android 5.0.2 although this isnt a CM zip. Once again, this ROM doesnt work. It just gives me an error saying it failed, no reason in particular.
I have a few issues for a whole range of files. Any help in fixing any or all of these would be much appreciated.
Links to the files I sites i downloaded the files from:
CM 12.1 UNOFFICIAL (Not meant to work fully) - https://forum.xda-developers.com/samsung-a-series/orig-development/rom-cyanogenmod-12-1-samsung-galaxy-a3-t3273323
CM 13 (Doesnt install) - https://forum.xda-developers.com/samsung-a-series/orig-development/rom-cyanogenmod-13-0-unofficial-samsung-t3326297
Android 5.0.2 ROM (Doesnt install) - http://www.youmobile.org/blogs/entry/-Firmware-Download-Samsung-Galaxy-A3-SM-A300FU-Official-Android-5-0-2-Lollipop-update-Rolling-out
So to reitterate: I installed the CM 12.1 ROM without issues but it turns out to be a mod that doesnt work fully meaning its unsuitable for me. I downloaded CM 13 but this gets an error. I downloaded a Android 5.0.2 ROM which has an error it doesnt even tell me about.

XDA Visitor said:
I have been running Cryogenmod 12.1 for my Samsung SM-A300FU but its UNOFFICIAL and a preview the webpage i got it off says 'Wifi and Camera NOT WORKING'. I guess thats what i get for following my mates advice.
Because of this, i looked at CM13 (Android 6) which i got off the XDA site and i have made sure it is for my phone and model, the SM-A300FU. Of course, being my luck it didnt work. I get the error of 'Executing updater binary in zip' and i have wiped my phone then tried to install it and i have also tried to completly remove all OS and files then install it which apparently fixed it for people, but not me of course. In a desperate measure i even bluetoothed the ROM to another phone then back into my SM-A300FU to get it onto the internal storage but that obviously didnt change anything.
Finally, i gave up and tried to downgrade back to Android 5.0.2 although this isnt a CM zip. Once again, this ROM doesnt work. It just gives me an error saying it failed, no reason in particular.
I have a few issues for a whole range of files. Any help in fixing any or all of these would be much appreciated.
Links to the files I sites i downloaded the files from:
CM 12.1 UNOFFICIAL (Not meant to work fully) - https://forum.xda-developers.com/sa...m-cyanogenmod-12-1-samsung-galaxy-a3-t3273323
CM 13 (Doesnt install) - https://forum.xda-developers.com/sa...-cyanogenmod-13-0-unofficial-samsung-t3326297
Android 5.0.2 ROM (Doesnt install) - http://www.youmobile.org/blogs/entr...ial-Android-5-0-2-Lollipop-update-Rolling-out
So to reitterate: I installed the CM 12.1 ROM without issues but it turns out to be a mod that doesnt work fully meaning its unsuitable for me. I downloaded CM 13 but this gets an error. I downloaded a Android 5.0.2 ROM which has an error it doesnt even tell me about.
Click to expand...
Click to collapse
Greetings and welcome to assist. Which recovery are you using ? Have you tried to update to the latest ? Also if that doesn't work try using odin to go back to latest stock then reflashing custom recovery
Why not make an account and let the experts here
https://forum.xda-developers.com/samsung-a-series
guide you
Good Luck
Sawdoctor