Database Info

[Q] Unknown Baseband/IMEI, No Data, No WiFi, No Bluetooth

Hi,
I just unlocked bootloader of my Oneplus One 64GB Global Version and flashed TWRP Recovery, I forgot to take backup of EFS, and installed custom ROM (ColorOS) via fastboot,
Everything worked correctly but I lose network, there is no network, even if SIM card installed, WiFi never turns ON, bluetooth turns on but not discoverable, even after make it visible, nor it can find other bluetooth devices nearby,
Baseband version and IMEI number is unknown, After disaster I came to know that I must backup efs partition, On xda guys are saying that modemst1.bin and modemst2.bin are that files which I didnt backed up and they are unique to each devices, so I somebody's else backup won't be helpful
This didn't worked for me
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
So now, I have not network on my phone and not any backup, so are there any chance here to get it work back
I have attached some screenshots taken from this device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

hey have u fixed it??
i am in the same situation

nick.joshi said:
hey have u fixed it??
i am in the same situation
Click to expand...
Click to collapse
Go to service center

did they replaced your device?

nick.joshi said:
did they replaced your device?
Click to expand...
Click to collapse
the guys in service center were not able to fix this, they asked me give device to them and that they will further send device to company. And it will take about 15 - 20 days, I didn't give phone to them, do not expect anything from guys on service center, they can't help you,
And please tell me too when you devices got fixed or replaced

manjeet.imaniac said:
the guys in service center were not able to fix this, they asked me give device to them and that they will further send device to company. And it will take about 15 - 20 days, I didn't give phone to them, do not expect anything from guys on service center, they can't help you,
And please tell me too when you devices got fixed or replaced
Click to expand...
Click to collapse
so u have ur phn with you only without any network and imei?

bro i have fixed my issue.
pm me i'll try to fix urs too

How did you fix it? Can you explain here? My issue is different though, I did nothing with my phone.

countvampy said:
How did you fix it? Can you explain here? My issue is different though, I did nothing with my phone.
Click to expand...
Click to collapse
you lost your EFS.
Search for EFS restore

Kidovzky said:
you lost your EFS.
Search for EFS restore
Click to expand...
Click to collapse
You sure? It will be great if you could point out something. I have tried the guide from "markbencze"
I have also submitted a ticket to Oneplus in the meanwhile.
---------- Post added at 04:11 PM ---------- Previous post was at 03:52 PM ----------
Kidovzky said:
you lost your EFS.
Search for EFS restore
Click to expand...
Click to collapse
Also, shouldn't flashing to stock or any other ROM clear and rebuild all the system files?

Same Problem Here.
I did exactly like what you did. Flash color os after unlocking the device, and now i lose my imei :crying:
anyone can help? Thanks.

efs corruption is a *****.
unfortunately i am not aware of any fix for it, happens when flashing a rom on occasion. i did it to a note before and it broke my heart. only way is if you have a backup of your efs.tar file and putting it into the efs file generated in the androids home directory file.

Had the same issue.. Recovered Wifi with "fastboot erase modemst1" and "fastboot erase modemst2", but still no data. Have you solved?

There is a thread for that :
http://forum.xda-developers.com/oneplus-one/general/imei-wifi-baseband-thread-t3076640
You can put your imei back.

Bro same issue... If u can help me.

VS987 with internation SIM Questions

Hi There,
I have a Verizon G5 and I'm using it overseas. There are 2 issues I would like to ask:
1) Phone does not update itself via OTA or PC with regular ways. Current version is VS98710B. How can I update it? (I don't have Verizon service)
2) I see that most recent update (VS98714A) brings an issue that; when the phone is reset, it can only be used again with entering the gmail account/password associated with that phone. What if I give/sell the phone to someone else? How can a different person use it again?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance!

enesdemi said:
Hi There,
I have a Verizon G5 and I'm using it overseas. There are 2 issues I would like to ask:
1) Phone does not update itself via OTA or PC with regular ways. Current version is VS98710B. How can I update it? (I don't have Verizon service)
2) I see that most recent update (VS98714A) brings an issue that; when the phone is reset, it can only be used again with entering the gmail account/password associated with that phone. What if I give/sell the phone to someone else? How can a different person use it again?
Thanks in advance!
Click to expand...
Click to collapse
Have you tried taking the sim out and then upgrading over wifi?

Yes, but it does not update over wifi as well..

enesdemi said:
Yes, but it does not update over wifi as well..
Click to expand...
Click to collapse
You can try make a update via LGUP (without delete you'r data)

PtrohorZahar said:
You can try make a update via LGUP (without delete you'r data)
Click to expand...
Click to collapse
I tried LGUP but it does not recognize my phone. I think I need find a way to make it see the phone.

i cant say much about update, i had that issue as well.
and about google lock, if you reset your phone from settings menu and give it to someone its fine, but if you reset it from android recovery (before phone starts up) than you have to activate it using previous google account. its same as apple does it

enesdemi said:
I tried LGUP but it does not recognize my phone. I think I need find a way to make it see the phone.
Click to expand...
Click to collapse
2 days ago i update my LG G5 VS987 via LGUP. All was great
I make zip archive with all needs programms to update our phone. If you wanna it, send me a message - [email protected]

fromgeorgia said:
i cant say much about update, i had that issue as well.
and about google lock, if you reset your phone from settings menu and give it to someone its fine, but if you reset it from android recovery (before phone starts up) than you have to activate it using previous google account. its same as apple does it
Click to expand...
Click to collapse
Thank you for this information!

PtrohorZahar said:
2 days ago i update my LG G5 VS987 via LGUP. All was great
I make zip archive with all needs programms to update our phone. If you wanna it, send me a message - [email protected]
Click to expand...
Click to collapse
Thank you!, I will try LGUP again then

Edited build.prop and now the phone is bricked.

Alright, so here's what happened.
Finally updated hardware and went from a nexus 6p to a pixel xl.
It's running 8.0.
So I decided it was time to get the phone up to the same customization that I had on my 6p.
One of my first things, after rooting of course, was adding qemu.hw.mainkeys=1 to build.prop in order to get rid of the soft keys. Same exact thing I've done on literally all of my android phones ever.
Rebooted.
I now get this sweet messaging saying "Can't load Android system..." (See Picture) and so on. Suggesting Try again and Factory data reset.
So I'm like whatever, I can just pull build.prop to my computer. So I find some guides on how to do that and boot to the bootloader.
But then adb devices shows:
"List of devices attached"
And then nothing. So adb can't find my phone.
Here's what I tried in trouble shooting.
Disconect Cable
adb kill-server
adb start-server
Plug back in.
Still nothing.
I even tried a different USB port.
So now I'm like "Okay, I'll take the bullet and factory reset."
So I did.
After setup, I get about 30 seconds (without softkeys) of phone time before my the System UI crashes and the phone shuts off.
Upon reboot, I'm faced with the same "Can't load Android system screen..." (See picture again if you want) and we're back to square one.
So...
Can't adb pull on build.prop because adb can't find my phone.
Can't boot into the regular system and edit build.prop from there because the phone isn't rooted (cause the only way to boot into the system is to factory reset).
Can't root the phone because adb can't find my phone.
And lastly, can't flash factory images because adb can't find my phone.
That's all the trouble shooting I've tried. If anyone can help me out here, I would be super grateful, cause right now, I have a really expensive paperweight.
Thanks in advance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

hello, try flashing through fastboot following this post:
https://forum.xda-developers.com/showpost.php?p=70041042&postcount=3
here if you want to unlock the bootloader:
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886

Yup. That worked. Thank you!

Any idea why adding qemu.hw.mainkeys=1 to build.prop killed my rom?

burt1215 said:
Any idea why adding qemu.hw.mainkeys=1 to build.prop killed my rom?
Click to expand...
Click to collapse
Because the UI has to have nav keys, unless your Pixel has hardware keys, you'll probably have to keep the softkeys.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
Because the UI has to have nav keys, unless your Pixel gas hardware keys, you'll probably have to keep the softkeys.
Click to expand...
Click to collapse
I've hidden the softkeys on my Nexus 4, Nexus 5, and Nexus 6P. And on every operating system since ICS.
What's different now? Is it the Pixel XL or Oreo?

burt1215 said:
I've hidden the softkeys on my Nexus 4, Nexus 5, and Nexus 6P. And on every operating system since ICS.
What's different now? Is it the Pixel XL or Oreo?
Click to expand...
Click to collapse
To be honest, I've never heard of it being an issue either, I was just speculating, however unlikely it may be.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
To be honest, I've never heard of it being an issue either, I was just speculating, however unlikely it may be.
Click to expand...
Click to collapse
Ha. No worries.
After fixing my phone, I decided to edit build.prop again, cause it's not stupidity unless you try the same thing multiple times while expecting different results right?
Anyway, same exact thing happened.
This time I fixed it without wiping my phone, but it leads me to believe that build.prop can't be edited... but I'm still not sure why.

burt1215 said:
Ha. No worries.
After fixing my phone, I decided to edit build.prop again, cause it's not stupidity unless you try the same thing multiple times while expecting different results right?
Anyway, same exact thing happened.
This time I fixed it without wiping my phone, but it leads me to believe that build.prop can't be edited... but I'm still not sure why.
Click to expand...
Click to collapse
Are you booting to recovery and wiping cache and dalvik/ART cache(obviously not factory reset or wipe data, just the caches)? It's usually required when modifying system files.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
Are you booting to recovery and wiping cache and dalvik/ART cache(obviously not factory reset or wipe data, just the caches)? It's usually required when modifying system files.
Click to expand...
Click to collapse
I edited build.prop and rebooted the system.
Got the same error as the picture in the original post.
Booted into TWRP and pulled build.prop onto my computer.
Edited the file, pushed it back in and rebooted into the system without any errors.

burt1215 said:
I edited build.prop and rebooted the system.
Got the same error as the picture in the original post.
Booted into TWRP and pulled build.prop onto my computer.
Edited the file, pushed it back in and rebooted into the system without any errors.
Click to expand...
Click to collapse
Strange, at least it works.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

stock mmcvlk0p table for SHIELD K1 16GB

Hello.
I've run into some troubles with my device, and apparently what's wrong with it is incorrect mmcblk0p values. I did something wrong with it. And now I want to try restoring it back to the default state since I can't boot into any ROM due to boot looping. Both stock and TWRP recoveries are still accessible.
Another problem that might've come along with it is that whenever I select "continue" in the bootloader menu, it says "cold booting linux".
Thanks in advance.
EDIT:
I ask for the file from the new version of the Nvidia Shield Tablet, 16GB specifically. The one that came out without the pen.
HERE'S THE INSTRUCTION ON HOW TO COPY THE FILE:
1. Enter TWRP
2. Mount System if necessary
3. Advanced -> File Manager
4. Path to the file - /dev/block/mmcblk0p24 (you can simply copy it straight to /sdcard)
IN CASE YOU HAVE mmcblk0p25 AS WELL, MENTION IT!
That's it! Nothing bad is going to happen to your device. Simply copy the file!
It also would be very nice of someone to fully upload the "/blocks" folder. It could be very useful for restoring the tablet for other people!

Nvidia Shield K1 16GB
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Try flashing stock factory ROM from twrp. You can find stock factory images here on XDA or on nvidia website. Search for nomoreota and kill switch here on XDA to see if you need to flash a patch immediately after you flash the stock factory image to prevent nvidia kill switch hard bricking your device.

jemail said:
Try flashing stock factory ROM from twrp. You can find stock factory images here on XDA or on nvidia website. Search for nomoreota and kill switch here on XDA to see if you need to flash a patch immediately after you flash the stock factory image to prevent nvidia kill switch hard bricking your device.
Click to expand...
Click to collapse
My device doesn't have killswitch, I'm using the newer
K1 version. And I tried flashing stock images multiple times. It doesn't help. I'm pretty sure all I need is the stock mmcblk0p, mmcblk0p24 in particular, since I modified exactly that. I remember that the new values I get when I use "cat /proc/partitions" in recovery or adb shell on PC differ from original ones.

lilmonkw said:
My device doesn't have killswitch, I'm using the newer
K1 version. And I tried flashing stock images multiple times. It doesn't help. I'm pretty sure all I need is the stock mmcblk0p, mmcblk0p24 in particular, since I modified exactly that. I remember that the new values I get when I use "cat /proc/partitions" in recovery or adb shell on PC differ from original ones.
Click to expand...
Click to collapse
I only have the OG nVidia Shield Tablet. But here is my mmcblk0p24 (512KB)
https://mega.nz/file/Z0t30KAT#XC4JuGKYTT74K1b3hUl1aCr61G_xID_zdFfLbnoKfoo
Hopefully someone with the K1 can upload the necessary files.
Good Luck.

jemail said:
I only have the OG nVidia Shield Tablet. But here is my mmcblk0p24 (512KB)
https://mega.nz/file/Z0t30KAT#XC4JuGKYTT74K1b3hUl1aCr61G_xID_zdFfLbnoKfoo
Hopefully someone with the K1 can upload the necessary files.
Good Luck.
Click to expand...
Click to collapse
Thanks, I also hope for someone with K1 to come in

lilmonkw said:
Thanks, I also hope for someone with K1 to come in
Click to expand...
Click to collapse
Post a request with the information you posted here, in some of the shield tablet development threads, look for the threads that have the most recent activity. In particular threads that user steel01 has started or has posted in.
I know someone who has a K1 shield but I can't get to it due to covid lockdown. When I finally do get access to it I'll get the block files, but I can't promise when that will be.
Good luck.

Here's the file. My shield is now finally working. Thanks for helping me out, Scavenger87!

Samsung Galaxy Note 2 Lineage OS Not Working

Hello everyone, I have recently been trying to gain compatibility with Lineage OS 16(Android 9 Pie) along with Open GApps, following all the steps of many tutorials, however it does not work at all. Unfortunately, I am inexperienced with this as this is my first time rooting a phone. I loaded the phone into TWRP, however loading the OS shows the loading screen, but then just goes back into TWRP. I apologize if someone has already made a post on this, however I couldn't find anyone having this problem on this device. I used Kingoroot since I didn't have a data cable on myself at the time, so that could be an issue with the bootloader...? I'm really not sure, and help would be much appreciated.
I didn't do this on the Note 2 forum because it is not hard to say that forum is barely viewed, and it could take weeks for me to get a response.

Before I deleted the original OS, it was on Android Kit Kat

hypixel said:
Before I deleted the original OS, it was on Android Kit Kat
Click to expand...
Click to collapse
I have issue too except i didnt use Kingroot but use odin.
i tried to flash the rom and got the following error msg. I attached screenshot. Does anyone have any solutions to this?
The zip file is lineage-16.0-20200101-unofficial-t0lte.zip
My phone is SGH-T889. It specifically says the zip file is for this model but somehow it doesnt recognise my phone model. Did i wipe something that wipe that along??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Much thanks

Ok, i resesrch some and got rid of the Error 7 msg by deleting the "assert" lines in the updater.script
But now i get Error 6. Anyone with any ideas?

Android_noop said:
I have issue too except i didnt use Kingroot but use odin.
i tried to flash the rom and got the following error msg. I attached screenshot. Does anyone have any solutions to this?
The zip file is lineage-16.0-20200101-unofficial-t0lte.zip
My phone is SGH-T889. It specifically says the zip file is for this model but somehow it doesnt recognise my phone model. Did i wipe something that wipe that along??
View attachment 5263095
Much thanks
Click to expand...
Click to collapse
Have you tried different roms, or only this one?

hypixel said:
Have you tried different roms, or only this one?
Click to expand...
Click to collapse
Only this one

Android_noop said:
Ok, i resesrch some and got rid of the Error 7 msg by deleting the "assert" lines in the updater.script
But now i get Error 6. Anyone with any ideas?
View attachment 5263799
Click to expand...
Click to collapse
Hey, I found out that the issue (at least for me) was that my phone did not have enough storage/the partitions were creating the issue. I am not sure how to solve this, but you may be having the same issue

hypixel said:
Hey, I found out that the issue (at least for me) was that my phone did not have enough storage/the partitions were creating the issue. I am not sure how to solve this, but you may be having the same issue
Click to expand...
Click to collapse
Did u wipe before install?
If one wipes then installs, there should be enough storage space right?

Android_noop said:
Did u wipe before install?
If one wipes then installs, there should be enough storage space right?
Click to expand...
Click to collapse
Yes, I did wipe, however I think the issue is that the phone is creating partitions. This phone was bought many years ago, so it is also possible that the storage is innsuficient for newer versions of Android.

hypixel said:
Yes, I did wipe, however I think the issue is that the phone is creating partitions. This phone was bought many years ago, so it is also possible that the storage is innsuficient for newer versions of Android.
Click to expand...
Click to collapse
Well how did people install this OS onto their note2 on youtube??

Android_noop said:
Well how did people install this OS onto their note2 on youtube??
Click to expand...
Click to collapse
I think that they bought higher storage models