Database Info

[Q] Android M - Notification and Syncing Issues

Hi folks, I know what i'm doing, so I flashed the images and it all worked...BUT some major things are missing. I cant drop down the notification drawer (nor do I get any notifications) Also, nothing Google syncs. I tried manually syncing/logging out and logging back in and nothing seems to work, so 1) Suggestions? 2) Is there a dedicated forum for this? I cant seem to find anything online. I also tried flashing it again and to no avail.
Help me XDA, you're my only hope to not going mad on my phone.

JustinMorinC said:
Hi folks, I know what i'm doing, so I flashed the images and it all worked...BUT some major things are missing. I cant drop down the notification drawer (nor do I get any notifications) Also, nothing Google syncs. I tried manually syncing/logging out and logging back in and nothing seems to work, so 1) Suggestions? 2) Is there a dedicated forum for this? I cant seem to find anything online. I also tried flashing it again and to no avail.
Help me XDA, you're my only hope to not going mad on my phone.
Click to expand...
Click to collapse
Try downloading the image again and use the back ports, the ones directly connected to the motherboard. If you can't fix it and/or find an answer anywhere, remember that android M is beta; report it to the android developers and wait.
Just some personal history on this kind of occurrence (tl;dr some times the same hardware can behave differently on the same conditions):
My brother and I had once the same phone, the LG Optimus 2X. We bought the same phone, at the same store, on the same day, a promotion; quite the upgrade from my motorola milestone (droid). His would always have problems with custom roms that mine never did, some times was the other way around, but the developers fixed over time given the pertinent logs. It also happened Installing mac on my assembled pc, I got to have problems other people with the exact same hardware configuration never did and I didn't had problems that other people had.

mikeszf said:
Try downloading the image again and use the back ports, the ones directly connected to the motherboard. If you can't fix it and/or find an answer anywhere, remember that android M is beta; report it to the android developers and wait.
Just some personal history on this kind of occurrence (tl;dr some times the same hardware can behave differently on the same conditions):
My brother and I had once the same phone, the LG Optimus 2X. We bought the same phone, at the same store, on the same day, a promotion; quite the upgrade from my motorola milestone (droid). His would always have problems with custom roms that mine never did, some times was the other way around, but the developers fixed over time given the pertinent logs. It also happened Installing mac on my assembled pc, I got to have problems other people with the exact same hardware configuration never did and I didn't had problems that other people had.
Click to expand...
Click to collapse
Thats a great idea! I'm using a laptop so I will change ports. Does it make a difference when it says that ...exceeded maximum size... or what ever it said, id that normal? Update should be out this week I think as well!

No LTE after flashing custom kernel. Corrupted NV items?

Hello everyone.
I recently attempted to install a custom kernel (ElementalX) on my Nexus 5 D820. During this process, I encountered a bootloop while installing TWRP, which is probably the event that has caused the nightmare my phone has been in the past few weeks. Essentially, ever since then, LTE has not been working on my phone, and the rest of the cellular connectivity has been quite bad. Actually, LTE does work, but only for about 10 minutes. After this, if it is turned on, it will crash ALL cellular connectivity, including phone calls and texts, until I turn it off.
Initially, I believed that the custom kernel was the cause. I therefore flashed stock ROM back, thinking it would solve the problem (spoiler alert: it didn't). I then tried flashing many different stock ROMs, from KitKat to Lollipop and pretty much any variety of Marshmallow offered. This still didn't fix the problem. After this, I tried flashing individual radios from http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095, which still did not fix the problem.
I then realized that the problem wasn't in any of the files normally affected by flashing a new ROM and started reading up on the EFS partition. From what I can gather so far on my phone, I believe that I have a slightly corrupted EFS partition and that this is causing the stability issues on my phone. I tried restoring from a good qcn file as suggested here http://forum.xda-developers.com/goo...efs-backup-t2769023/post60421668#post60421668 and that has still not fixed my problem. I tried about 4 or 5 different qcn files, restoring in different order, wiping the block partitions like suggested here http://forum.xda-developers.com/lg-g3/general/request-3g-2g-lte-d850-t3300908 and that still didn't work.
But I didn't give up just there! I read from this post http://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059 that you could edit NV items individually and figured that maybe I could try to edit the LTE NV items to their default values. Turns out, they were at their default values and they are fine.
At this point, I thought I had tried everything, but while attempting an NV item backup using Qualcomm NV Tools in EFS professional, I noticed an odd error that kept happening. All of the NV items would back up properly, BUT, the backup process would crash for NV items 33799 to 33802 and 33810 to 33812, every time, no matter what. Also, exactly when I tried reading these NV items, the phone cellular network goes down for about 10 seconds, as it normally does when LTE is activated. I therefore believe that these NV items may be corrupt and that cellular network stops working whenever they are read, which for some reason only occurs when LTE is turned on (I'm far from an expert in this field, correct me if what I'm saying makes no sense).
At this point, I've pretty much given up on fixing the phone, but thought I would reach out to xda-devs to see if anyone had any experience with this. Not having LTE is not a huge deal, but I would be quite happy if I could bring it back.
What I'm asking: If anybody with a Nexus 5 D820 could try doing an NV Backup using Qualcomm NV Tools and see if NV items 33799 to 33802 and 33810 to 33812 crash their phone, that would be much appreciated. If I know at least that this is a problem unique to my phone, it can point me in the right direction. On the other hand, if it's widespread across Nexus 5 devices, my problem may be something else completely.
What I'd really, really, really appreciate: If a kind soul could give me a full EFS backup of their working phone, I would be extremely grateful. I'm pretty sure that this would fix all my problems, and I would be forever grateful to the kind person that does this. Of course, you may wipe your ESN/MEID/IMEI before sending the file.
tl;dr
LTE doesn't work since flashing kernel. Probably corrupt EFS partition. If some can check if NV items 33799 to 33802 and 33810 to 33812 can be backed up on Qualcomm NV Tools, that would be great. If someone can send me a full EFS backup of their Nexus 5, that would be amazing.

I dont know if it is still relevant for you but i got the same issue..
I got two Nexus 5 D821 (dont ask why two of them )
Wanted to move a full backup from the first one to the second...
I didnt know about the efs partition and what it is so i also told twrp to backup it from my first device too... and restoring it on the second device screwed my imei (showed 0)...
SO DO NOT BACKUP EFS ON ONE PHONE AND MOVE WITH IT TO ANOTHER ONE!!!! EVEN IF IT IS THE SAME PHONE TYPE!!!!
I managed to get my imei back somehow with editing NV items, restoring backups from QPST files and so on... (Worked at least 20 hours so far)
The only advantage that I have is that the first phone i came from is still untouched on his efs, so i try to backup the nv data and got the same errors as you!
I am currently working on this and got the same errors backing up nv items from the untouched nexus...
So probably thats not the problem, just skip these values and try to restore the nv as parts
If you need the nv backups you can contact me at [email protected]
Perhaps I am able to help

Brother, did you solve the problem?

Taking Security To The Next Level...

Im new here but seeking advice from whoever can help.
Im very interested in setting up the most secure Nexus 5 possible.
Since Copperhead OS stopped supporting nexus 5.
Ive done most instructions found here torproject website blog mission-impossible-hardening-android-security-and-privacy
Comes to a point where you DD your Modem img To Blank. but i see its still repairable or the chip still has access to all components for radio transmission.
ive been searching everywhere but cant find anything about this. i wanted to Remove the Qualcomm WTR1605L chip and and the boot process pointing to it.
so there physically has only wifi connection.
Is this possible?
will removing the chip cuase errors or brick the phone?
any profession help would be Great!

Okay still couldn't find info on this phone to tablet set up so will attempt the removal and see if any errors are fixable.
Will updates this post with images and issues

[FIX] PSA: SIM CARD/Data & WIFI not working, because of which phone reboots or enters crash dump mode

PSA:
THIS IS NOT A SOFTWARE ISSUE.
So no need to wipe/ reset your phone or msm flash. NO NEED.
It is related to hardware.
There is a really easy fix for this and it might seem stupid but its worked for me a lot of other people according to my research.
So when you come across this, all you need to do is press your phone on the back side in various places (i dont know where exactly) and then sim card and wifi both should start working.
I dont know why or how this happens, but it just works. it worked for me, after 2 days of trying to resolve this issue with various software solutions, went as far are copying the persist partition from another oneplus 6 and flashing it on mine.
so yes this works

Question IMEI / fingerprint problems... Any fix?

So today I'm doing the usual flashing of new roms to try them out and I run into a problem. During device setup, Google Fi fails to activate giving error code B042, and also errors out when it's time to register my fingerprint. Didn't think much of it at first, but now I've tried everything I can think of with no luck. Eventually I notice both IMEIs are listed as all zeros. I've wiped data multiple times, reflashed many factory and custom rom versions both with Android flash tool and manually, and always get the same issue with Fi activation and fingerprint scanner not working. I talked with Google techs and they just tell me to take it to Best Buy where it was purchased. I'm thinking a partition must have corrupted or something that doesn't restore during a typical reflash. Can anyone comment on what's going on, and if there's a way to go about fixing it myself. I do have both IMEIs listed on the box if there's a way to go about restoring them, but I doubt that would do anything with the fingerprint problem if even possible. Any insight would be greatly appreciated. Been on these forums for a decade and this may be my first time posting since I've always been able to work through problems myself, but I'm totally stuck on this one. Oh and the Pixel 7 pro I just bought to mess around with root and roms as a second phone, and my main S22u is still working fine, so not exactly an emergency or anything. Thanks in advance.

oncestruck said:
So today I'm doing the usual flashing of new roms to try them out and I run into a problem. During device setup, Google Fi fails to activate giving error code B042, and also errors out when it's time to register my fingerprint. Didn't think much of it at first, but now I've tried everything I can think of with no luck. Eventually I notice both IMEIs are listed as all zeros. I've wiped data multiple times, reflashed many factory and custom rom versions both with Android flash tool and manually, and always get the same issue with Fi activation and fingerprint scanner not working. I talked with Google techs and they just tell me to take it to Best Buy where it was purchased. I'm thinking a partition must have corrupted or something that doesn't restore during a typical reflash. Can anyone comment on what's going on, and if there's a way to go about fixing it myself. I do have both IMEIs listed on the box if there's a way to go about restoring them, but I doubt that would do anything with the fingerprint problem if even possible. Any insight would be greatly appreciated. Been on these forums for a decade and this may be my first time posting since I've always been able to work through problems myself, but I'm totally stuck on this one. Oh and the Pixel 7 pro I just bought to mess around with root and roms as a second phone, and my main S22u is still working fine, so not exactly an emergency or anything. Thanks in advance.
Click to expand...
Click to collapse
Sounds like your EFS partition got corrupted...
I haven't done anything with my P7P, it's stock, so can't offer any advice other than a google search to get you started... here

If the mod will erase it not state it. You mess with that you are on your own? Broke the op as well. Just delete it.