Database Users

Nexus4, sudden signal loss

Good evening, I'm having issues with my nexus .
Days ago a friend of mine told me about the Xenon HD rom, and I decided to try it (Im a CM user).
Today, I made a backup with TWRP and flashed the rom, I tested it for a few hours and I did not liked it, so I decided to go back to the previous rom, so I restored the backup. I realized that all my applications were not installed, so then I decided to do a Factory Reset and restore the backup again, my apps were still missing.
So I decided and start from scratch, doing another factory reset and installing CM on it, I factory reset it and I realize that my phone did not have any signal!
Wifi and everything is working but iit is not receiving any signal!
Can anyone help? I even tested it with a simcard from another company and nothing!
Are there any settings that may have been moved? Some option? please help me!

Flash boot loader radio again
Nexus ⁴ paranoid android

If you are coming from a Android 4.3 stock rom to 4.2.2 then you need to flash this selecting the first option and flash it before flashing a Android 4.2.2 rom: http://forum.xda-developers.com/showthread.php?t=2147194
Sent from my Nexus 4 using Tapatalk 4

andyabc said:
If you are coming from a Android 4.3 stock rom to 4.2.2 then you need to flash this selecting the first option and flash it before flashing a Android 4.2.2 rom: http://forum.xda-developers.com/showthread.php?t=2147194
Click to expand...
Click to collapse
Hi, thanks for your answer, I just wanted to let you know that I went from an custom 4.2.2 (cm) to another 4.2.2 (xenonhd) and again to a 4.2.2 rom... Is there any way to check if my radio is ok?

I just flashed the radio&bootloader file and nothing
Im really lost here!
Please help me!

Do you recommend to make a system wipe and restore afactory image from the Nexus 4 Toolkit?

Please help me, I just returned it to stock using the toolkit and nothing...

Check your SIM card...remove it and reboot your phone then attach your SIM again and reboot...
Sent from my Nexus 4 using Tapatalk 4 Beta

vista_vz said:
Check your SIM card...remove it and reboot your phone then attach your SIM again and reboot...
Click to expand...
Click to collapse
Done and nothing!
Please help me out here!

donchele said:
Done and nothing!
Please help me out here!
Click to expand...
Click to collapse
Upgrade your phone to 4.3 and latest radio(using Google factory image) if problem persists call Google...
Sent from my Nexus 4 using Tapatalk 4 Beta

vista_vz said:
Upgrade your phone to 4.3 and latest radio(using Google factory image) if problem persists call Google...
Click to expand...
Click to collapse
Done! and nothing!

donchele said:
Done! and nothing!
Click to expand...
Click to collapse
Take soon card out. Then reboot . when phone is on , put Sim card in . if their is no , need to restart popup then its your Sim ,Sim tray, or sim reader
★Nexus⁴★PA3.94★Matr1x 10.5★LTE★

anyone else?

If you already flashed the factory image
Just let it be, insert your sim card and let the phone on for awhile
That happened to me with PA in 4.2.2 you got to wait a bit
Sent from the outside of the Eternity Gate at Holy Terra on a Paranoid Nexus

ofteno said:
If you already flashed the factory image
Just let it be, insert your sim card and let the phone on for awhile
That happened to me with PA in 4.2.2 you got to wait a bit
Click to expand...
Click to collapse
I dont think this will help that much, Its like waiting for it to fix itself, Thanks pal
At this point, my phone is fully stock and ready to go to the US for a claim process...
I just want to make sure everything is as stock as it should be, please take a look at the following and let me know:
Bootloader
Recovery
Anything else should be done? do you think that google will find out that the phone was rooted or something?

donchele said:
I dont think this will help that much, Its like waiting for it to fix itself, Thanks pal
At this point, my phone is fully stock and ready to go to the US for a claim process...
I just want to make sure everything is as stock as it should be, please take a look at the following and let me know:
Bootloader
Recovery
Anything else should be done? do you think that google will find out that the phone was rooted or something?
Click to expand...
Click to collapse
Glad yo help you out.
I know, it isn't logical but it works
Sent from the outside of the Eternity Gate at Holy Terra on a Paranoid Nexus

ofteno said:
Glad yo help you out.
I know, it isn't logical but it works
Sent from the outside of the Eternity Gate at Holy Terra on a Paranoid Nexus
Click to expand...
Click to collapse
I will try this tomorrow, please if anyone can take a look at the pictures and confirm that everythis is as stock as it shoul...
thanks

For 4.3 its good
Rooting i don't think so
About other think i really dont know
Sent from the outside of the Eternity Gate at Holy Terra on a Paranoid Nexus

Good day, I just wanted to let you guys know that the weirdest thing just happened to me.
I just came from my office and thought about going and turning on my phone, I did, and enabled airplane mode, (also turned on and off nfc) when I disabled it, my phone detected the network signal! I even received a sms, I also made a call! and thought, wow! it fixed itself up! I was literally dancing in my room and changing my simcard... (because I did all the above with a replacement chip that I have) and when I finally put my chip back, I made a call and it lost the signal again... It is now again without signal... I’m beginning to think this is a hardware problem...

Any update on this?
I've had the same problem for a few weeks now, the 3G/H signal just drops out, rebooting, airplane mode switching, returning to stock, different apn's, changing radios, replacing sims have all had no effect.
It's getting embarrassing now, seems to be such a common problem and yet no acknowledgement from Google about the issue which I believe to be deep in the settings/software and relating to the hardware in the original batch of Nexus phones.
I could arrange a return and get a replacement but I've read that even replacements have the same issue.
Apart from throwing the thing against the wall is there any other fixes out there?
If it helps I'm on 02 UK pay monthly, surrounded by cell towers, the phone is rooted and running stock 4.3
Just checking it now and I have H and 4 full blue bars - Ok update twitter.. nope, ok go to the play store..nope...
Fricken piece of Junk

[Q] KitKat Rom on T Mobile Lg G2

I've tried this two times and both I had the same result. I downgraded back to 4.2.2 with the D80110g_00.kdz for the tmobile g2. Then I rerooted it and added philz touch recovery. I flashed with the kitkat baseband in the cloudystock 1.1 fourm, then the rom with the patched 801 kernel after. Everything boot's up ok, and the phone works. But when I turn off the screen and back on its all grayed out with yellow lines. I have the reboot the phone for the screen to show up again. Can someone tell me what I am doing wrong?

Do the same process except do not use 80110g. Find the 80110c kdz.
Sent from my LG-D801 using xda app-developers app

Thank you, that fixed the problem. Another question I have is that when I flash the baseband, do I have to keep reflashing it when I move to another kitkat rom?

JPrinceStar said:
Thank you, that fixed the problem. Another question I have is that when I flash the baseband, do I have to keep reflashing it when I move to another kitkat rom?
Click to expand...
Click to collapse
baseband stays the same when flashing other roms. Pretty sure the rom zips don't touch baseband unless specified otherwise. Glad it worked for ya btw
Sent from my LG-D801 using xda app-developers app

Problem came back, turn off screen and its grayed out when back on unless reboot. I dont have this problem when I root 4.2.2. Am I flashing the files in the wrong order, or am I missing something.

JPrinceStar said:
Problem came back, turn off screen and its grayed out when back on unless reboot. I dont have this problem when I root 4.2.2. Am I flashing the files in the wrong order, or am I missing something.
Click to expand...
Click to collapse
Doesn't seem like you are flashing in wrong order. If you boot up and everything runs...it's probably just due to the fact this isn't an official release and there may be bugs
Sent from my LG-D801 using xda app-developers app

v2.2v said:
Doesn't seem like you are flashing in wrong order. If you boot up and everything runs...it's probably just due to the fact this isn't an official release and there may be bugs
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
I have the exact issue...here is a picture of what it looks like, maybe this will help so that people can see what we talking about

batmanonastick said:
I have the exact issue...here is a picture of what it looks like, maybe this will help so that people can see what we talking about
Click to expand...
Click to collapse
same issue here. Cannot run any stock KK roms at all. I've flashed so many times and have had to return to stock. I wish this problem could be identified.

Did anyone out there figure this out?

I'm having the same problem on my device, tried several stock ROMs but nothing works even when using different basebands.

I have this problem as well and no, you're not doing anything wrong. Devs have absolutely no idea why this is happening. It seems that this is only happening with users that bought the phone and have the G build pre-installed. People that bought the phone earlier with the C build don't have this problem.
I gave up and just flashed the official KK TMO ROM with root installed. I lost my recovery but hopefully devs can get recovery on stock KK. If anything, I can always KDZ back to 4.2.2 and re-install the recovery if I want to go back to AOSP ROM's.
FWIW, I bought the G2 a week ago. When did you get yours?

I think you hit the nail on the head with G build comment. I got my phone about a month ago from TMO and it came pre-installed. I wonder if something in the actual hardware is ever so slightly different with the latest G2s...

I flashed with the C build and it didn't fix it also, guess I'll stay on 4.2.2 till there is a official kitkat root.

Anyone around in this thread with the line problem willing to test a kernel?

mackster248 said:
I have this problem as well and no, you're not doing anything wrong. Devs have absolutely no idea why this is happening. It seems that this is only happening with users that bought the phone and have the G build pre-installed. People that bought the phone earlier with the C build don't have this problem.
I gave up and just flashed the official KK TMO ROM with root installed. I lost my recovery but hopefully devs can get recovery on stock KK. If anything, I can always KDZ back to 4.2.2 and re-install the recovery if I want to go back to AOSP ROM's.
FWIW, I bought the G2 a week ago. When did you get yours?
Click to expand...
Click to collapse
How do you find if you have G or C build? I thought all tmobile g2's are c build. I am getting mine tomorrow, hope it is shipped with JB rom - if so, i think it will be better to stay. After reading a bit, i heard many say tot method is working fine as explained here.
Which rom (xd thread?) are you using? Does wifi calling work?

sam298 said:
How do you find if you have G or C build? I thought all tmobile g2's are c build. I am getting mine tomorrow, hope it is shipped with JB rom - if so, i think it will be better to stay. After reading a bit, i heard many say tot method is working fine as explained here.
Which rom (xd thread?) are you using? Does wifi calling work?
Click to expand...
Click to collapse
If you go to software you can see the build, it either ends with C or D. Most likely D since you'll just be getting it. And it will be JB not KK. There's a new AutoRec file that gives KK users recovery, but since you'll be getting the D version, you'll most likely have the white line glitch issue. There's a way around it, just PM me for further questions and I'll help ya out.

v2.2v said:
Do the same process except do not use 80110g. Find the 80110c kdz.
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
KennyJive said:
same issue here. Cannot run any stock KK roms at all. I've flashed so many times and have had to return to stock. I wish this problem could be identified.
Click to expand...
Click to collapse
JPrinceStar said:
Did anyone out there figure this out?
Click to expand...
Click to collapse
SeVIIn said:
I'm having the same problem on my device, tried several stock ROMs but nothing works even when using different basebands.
Click to expand...
Click to collapse
i really want to root but this is making me nervous. Only things i want to change is the camera mod and sound mod really.
dr87 said:
Anyone around in this thread with the line problem willing to test a kernel?
Click to expand...
Click to collapse
I am in the same boat as most these people.. bought my phone a week ago, i am rooting as i type. Will probably have the issue and completely willing to test a kernel. Should i flash your rom as well first?
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
mackster248 said:
If you go to software you can see the build, it either ends with C or D. Most likely D since you'll just be getting it. And it will be JB not KK. There's a new AutoRec file that gives KK users recovery, but since you'll be getting the D version, you'll most likely have the white line glitch issue. There's a way around it, just PM me for further questions and I'll help ya out.
Click to expand...
Click to collapse
Hmmm.. so i have a completely stock g2 non rooted (working on rooting right now actually) but when i go into settings, my build number ends with an 'A' ?? not c, d or g.... what does this mean? Man, rooting seemed so much easier on my HTC or samsung phones! No complaints though, i love this phone

frettfreak said:
i really want to root but this is making me nervous. Only things i want to change is the camera mod and sound mod really.
I am in the same boat as most these people.. bought my phone a week ago, i am rooting as i type. Will probably have the issue and completely willing to test a kernel. Should i flash your rom as well first?
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
Hmmm.. so i have a completely stock g2 non rooted (working on rooting right now actually) but when i go into settings, my build number ends with an 'A' ?? not c, d or g.... what does this mean? Man, rooting seemed so much easier on my HTC or samsung phones! No complaints though, i love this phone
Click to expand...
Click to collapse
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.

mackster248 said:
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
Click to expand...
Click to collapse
yeah it did ship with KK. pretty sure i have seen the thread regarding the autorec app. But will let you know! Thanks!

mackster248 said:
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
Click to expand...
Click to collapse
Mackster I'm on 4.2.2 which is rooted, is there anyway I could use a custom kitkat rom without getting the white lines? I dont want to keep downgrading everytime it happens.

Non-Verizon sim, broken sms with 5.0 root

So I've replicated this problem three or four times, after which I've given up on updating to 5.0 until I have some solid solutions. Whenever I try to flash one of the rooted OA8 roms here on xda I lose the ability to send sms, that is literally the only thing that is broken (4g works, calls work, phone activates to towers fine.) My process for flashing these roms has been full wipe > flash rom > reboot download > odin OA8 kernel; that's coming from rooted NK2. I've talked to another user on here who has the same problem and our common thing is that we're both on non-verizon sims (straight talk in my case.) I've tried updating the PRL, wiping cache/dalvik, factory reset. Downgrading back to 4.4.4 fixes it every time, so it's definitely not a network issue. What's the issue here? I realize that those of us with non-verizon plans are the minority here, but if anyone who knows more about this than me has some suggestions, throw them down here.

Same problem for me.
Havent been able to send sms or mms while on lollipop. kitkat works fine. wish they would fix this. i love using lollipop.

0verdose said:
Havent been able to send sms or mms while on lollipop. kitkat works fine. wish they would fix this. i love using lollipop.
Click to expand...
Click to collapse
Have you tried a factory reset that might help nvm just reread and saw u did

djdrews4357 said:
Have you tried a factory reset that might help nvm just reread and saw u did
Click to expand...
Click to collapse
Yeah honestly I'm thinking it's something the rom devs will have to fix on their end, if possible. I've been rooting for a while, on a number of phones, and haven't run into anything like this before. I'm afraid it's out of my little bit of android knowledge

wareju said:
Yeah honestly I'm thinking it's something the rom devs will have to fix on their end, if possible. I've been rooting for a while, on a number of phones, and haven't run into anything like this before. I'm afraid it's out of my little bit of android knowledge
Click to expand...
Click to collapse
I had the same problem, however it was only for sending mms while on wifi. Have you tried using a different app?

Yeah, stock vzw app and google's messenger neither worked for me

[Q] Issues after updated to Lollipop 5.0.2

My daughter's G2 (AT&T) is not working right after OTA to Lollipop. The typical issue is battery drain, next is the Google calendar sync and Contact sync issue and then the apps startup lagging. She did try factory reset, but that did not fix any issues at all.
Is there any way to revert back to KitKat or work around to all these issues ? She is very frustrated for the update.
Thanks,
Ching-Ho Cheng

Flash back to Kit-Kat
Follow this thread
http://forum.xda-developers.com/showthread.php?t=2662445

EricCamino121 said:
Follow this thread
http://forum.xda-developers.com/showthread.php?t=2662445
Click to expand...
Click to collapse
Thank you, I will take a look.

Is there no other solution aside from flashing back to Kitkat? I'm also getting the same issue after upgrading to Lollipop... already did a reset twice and it only works for 1-2 weeks till I get the same issue again

silkenhut said:
Is there no other solution aside from flashing back to Kitkat? I'm also getting the same issue after upgrading to Lollipop... already did a reset twice and it only works for 1-2 weeks till I get the same issue again
Click to expand...
Click to collapse
Well, you could try to see or there might be a newer lollipop version available for the g2 else you could always try some custom roms or only flash dorimanx kernel as lollipop went much better when I flashed that kernel. but I suggest to disable root on your daughters phone.
If these 3 things don't solve it well, then she has to go back to kitkat.
Sent from my LG-D802 using Tapatalk

[H918] Random Reboots on Custom Roms

So, I had a day 1 v20 that began randomly rebooting back in december. Thought it was a hardware issue and finally got around to replacing it the other day. Now, after getting the replacement v20 set up on a custom rom (AICP) I'm seeing random reboots again. I've tried every single custom rom available for the h918 and they all experience reboots. When i've asked about the issue in the threads it seems as if I'm the only one. It appears to be a custom-rom only problem that apparently no one else is experiencing? The kernel panics are being caused by the modem, and it started happening when I upgraded to the 10j base. This replacement also came with 10j. Am I just super unlucky with two duds or is there really something going on here?
TLDR; Anyone else with a h918 with 10j bootloader/modem running custom roms and seeing random reboots?

What kernel do you use? If you use Konverged, it seems to give random reboots after a while of use. I noticed that right away though.

Biff627 said:
What kernel do you use? If you use Konverged, it seems to give random reboots after a while of use. I noticed that right away though.
Click to expand...
Click to collapse
Have always left kernel stock.

Are you making sure that you are wiping data when flashing a rom? Clean install should help. What other things do you use? When does it crash? Maybe a root app is causing this???

Biff627 said:
Are you making sure that you are wiping data when flashing a rom? Clean install should help. What other things do you use? When does it crash? Maybe a root app is causing this???
Click to expand...
Click to collapse
This is a fresh replacement device with a clean rom install. There was no data to wipe. Happens even without any apps installed and it's completely random and cannot be reproduced. The only thing I know is the modem is causing the kernel panics.

trobertson said:
This is a fresh replacement device with a clean rom install. There was no data to wipe. Happens even without any apps installed and it's completely random and cannot be reproduced. The only thing I know is the modem is causing the kernel panics.
Click to expand...
Click to collapse
Welll would this help at all? https://www.androidfilehost.com/?fid=673368273298927322 Its the modem and radio for H918? Not sure if this could help at all. I have a VS995 device. And I havent seen anyone else with this issue. If you do flash this... Backup yours first.

Biff627 said:
Welll would this help at all? https://www.androidfilehost.com/?fid=673368273298927322 Its the modem and radio for H918? Not sure if this could help at all. I have a VS995 device. And I havent seen anyone else with this issue. If you do flash this... Backup yours first.
Click to expand...
Click to collapse
The phone came with stock 10j.. flashing this wouldn't change anything.

trobertson said:
The phone came with stock 10j.. flashing this wouldn't change anything.
Click to expand...
Click to collapse
Does the KDZ have 10j included? If not maybe try that to downgrade and reroot from there

Biff627 said:
Does the KDZ have 10j included? If not maybe try that to downgrade and reroot from there
Click to expand...
Click to collapse
There is a 10i kdz that I can try.. the kdz's are full stock flash files. Bootloader modem system efs etc

trobertson said:
There is a 10i kdz that I can try.. the kdz's are full stock flash files. Bootloader modem system efs etc
Click to expand...
Click to collapse
Im just wondering if for some reason the 10J is messing with it somehow. What rom are you using and what other roms have you used in the past that give you this issue?

Biff627 said:
Im just wondering if for some reason the 10J is messing with it somehow. What rom are you using and what other roms have you used in the past that give you this issue?
Click to expand...
Click to collapse
Aicp, rr, cm-remix, stock Lineage.

trobertson said:
Aicp, rr, cm-remix, stock Lineage.
Click to expand...
Click to collapse
So things that already have issues :silly:
All jokes aside. I would recommend trying Weta to see if that helps. Very stable rom

Biff627 said:
So things that already have issues :silly:
All jokes aside. I would recommend trying Weta to see if that helps. Very stable rom
Click to expand...
Click to collapse
The entire point here is that I don't want to run stock or anything based on stock. I would simply chalk it up to the Lineage base but since I'm one of a serious minority having this problem I'm led to believe it's something simpler that can be fixed. Possibly related to 10j as most custom ROM users are still running 10d firmware

trobertson said:
The entire point here is that I don't want to run stock or anything based on stock. I would simply chalk it up to the Lineage base but since I'm one of a serious minority having this problem I'm led to believe it's something simpler that can be fixed. Possibly related to 10j
Click to expand...
Click to collapse
Anything not based on stock will give you issues. One reason why I like stock based roms is because the second screen will actually work... I would atleast test a stock based rom to see how it goes. If it works and doesnt crash, Then something is wrong with the rom or your could be flashing it wrong :/ Idk, just an idea to test. Non stock roms will Always give you issues. Always
If you still have issues on a stock based rom, then I would downgrade with the kdz and try again. Its probably crashing since the modem is 10j and the rom isnt really fit for that.

Biff627 said:
Anything not based on stock will give you issues. One reason why I like stock based roms is because the second screen will actually work... I would atleast test a stock based rom to see how it goes. If it works and doesnt crash, Then something is wrong with the rom or your could be flashing it wrong :/ Idk, just an idea to test. Non stock roms will Always give you issues. Always
If you still have issues on a stock based rom, then I would downgrade with the kdz and try again. Its probably crashing since the modem is 10j and the rom isnt really fit for that.
Click to expand...
Click to collapse
I never used the second screen, it's more of a nuisance for me. Everything it did can be replaced by gestures and lockscreen settings on custom. Only thing I miss is notifications but that's why we have ambient display.
I might try downgrading to the 10i firmware to see what happens. Unfortunately there are no 10d flashables. Otherwise this ROM is flawless.

trobertson said:
I never used the second screen, it's more of a nuisance for me. Everything it did can be replaced by gestures and lockscreen settings on custom. Only thing I miss is notifications but that's why we have ambient display.
I might try downgrading to the 10i firmware to see what happens. Unfortunately there are no 10d flashables. Otherwise this ROM is flawless.
Click to expand...
Click to collapse
Not to shoot down your opinion, but why would you get it if the Second screen is a nuisance to you?? Im also pretty sure camera is screwed on custom roms.... I just dont have that appeal. Its better safe than sorry to check and see if a stock rom works fine than to downgrade and it still doesnt work :/ Idk thats my 2 cents

Biff627 said:
Not to shoot down your opinion, but why would you get it if the Second screen is a nuisance to you?? Im also pretty sure camera is screwed on custom roms.... I just dont have that appeal. Its better safe than sorry to check and see if a stock rom works fine than to downgrade and it still doesnt work :/ Idk thats my 2 cents
Click to expand...
Click to collapse
It was between this and the axon 7. I didn't want a fullHD screen so that eliminated a lot of the other options.

trobertson said:
It was between this and the axon 7. I didn't want a fullHD screen so that eliminated a lot of the other options.
Click to expand...
Click to collapse
Note 7 chaos force you to this phone as well? I prefer the second screen tbh. I haven't touched a custom rom since my note 2 and I had issues with them then. But hey, if it ends up working then more power to ya

Biff627 said:
Note 7 chaos force you to this phone as well? I prefer the second screen tbh. I haven't touched a custom rom since my note 2 and I had issues with them then. But hey, if it ends up working then more power to ya
Click to expand...
Click to collapse
Not a Samsung fan. Especially with KNOX. I buy phones first based on the chances of development producing workable custom ROMs and second based on hardware features.
Back to the main topic: I just managed to flash the 10i modem alone so we'll see what happens. I'm working on extracting the 10d modem as well.

Biff627 said:
Note 7 chaos force you to this phone as well? I prefer the second screen tbh. I haven't touched a custom rom since my note 2 and I had issues with them then. But hey, if it ends up working then more power to ya
Click to expand...
Click to collapse
UPDATE: Flashing the 10i modem made no difference, still having random reboots (although they seem less frequent), I will try the 10d modem once I find a way to extract it from the TOT files posted on this forum.