Baseband not found - E 2015 Q&A, Help & Troubleshooting

I have no idea how or why this happened, but I've just been trying to get CM 13 working on my XT1526 lately and everything was normal, for some reason I can't get google services to work on CM but that was just normal for me. Then just yesterday I booted my phone up to be met with a bootloop when it booted just fine after changing nothing the day before. I went into the bootloader to see that my baseband was missing so I'm at a loss. I've tried flashing complete stock, restoring a working stock, and flashing CM with no luck. Anyone got any ideas about this? Is my phone just a paperweight now?
EDIT: Alright, I don't know what changed, but I reflashed CM again and it's suddenly not bootlooping anymore. Like I planned to do I also copied over stock apn-conf.xml and that apparently was the ticket to making google services work for some reason. +1 stat to self help, heh.
EDIT2: Nevermind...google services still not working properly on CM, but at least I'm not bootlooping anymore I guess...

Related

Kernel/mainver issues??

I finally broke down and did the relock/ruu/OTA routine yesterday.
I had a terrible time getting Amon Ra to reflash from fastboot, it kept giving me a "mainver is older error" and the install failed. I finally got that working (I'm not even sure how, I tried like 10 different versions).
I reflashed an AR BU I made on Friday of the setup in my sig and everything seemed to be working perfect, but I hadn't noticed that WiFi was giving an error because I almost never use WiFi.
Then it occurred to me that WiFi tethering was not going to work and I do use that once in a great while so I decided to reflash the dsb kernel as I knew that would fix it.
When I went to fastboot to do that, I get the same mainver error and the kernel refused to reinstall. Now, I'm like WTF I never should have messed with this thing, it ran perfect and I should have just left it alone..............
At that point, not sure what to do next I decided to try a different kernel even though I was 99% sure it would error out again.
I grabbed a copy of the latest incredikernel as I had been planning on trying that anyway (I really wanted the fast charge from any source feature) and went to fastboot once again.
Much to my surprise, THAT kernel flashed just fine and everything including WiFi etc works perfectly.
Does anybody know why some installs give the mainver error and others don't??
At this point, I am 100% done flashing for a while. The phone flies, doesn't boot loop and all my apps and themes work perfectly. I may not flash again until I get a new phone (my Wife says "fat chance of that")

[Q] NT16gb unbrick issues

So, I bricked my NT16gb. I was doing some playing around trying to get cm10 running off SDcard. Somehow this caused me to get stuck in a CWM bootloop. I used the method here: http://forum.xda-developers.com/showthread.php?t=1663836 to restore to stock. After that I resized my partitions back to where I had them and restored a known good cwm backup. Everything seems fine... EXCEPT that now my clock is wrong (easy to fix manually, but doesnt seem to use network provided times...) but I can't for the life of me get the Google Market to connect. Everything else has internet except for the market.
Any Ideas?
I've also since tried: Reinstalling my rom and Gapps, formatting /system and reinstalling my rom and gapps. No change though.
*edit*
Rofl. Wouldn't you know... I've been messing with this for a couple hours now... As soon as I finish posting here, I go to mess with it some more and wouldn't you know... it starts working.
I'm guessing that fixing my date somehow fixed my issues...
Mod please delete.

[Q] I probably did something I shouldn't have... Help?

I had android 4.4 Omnirom on my phone earlier today and yesterday. Today there was an update for the nightly. I decided to download it and updated through the recovery as a normal update would've. However, after waiting for almost an hour for the android is upgrading prompt to go away, I figured it was stuck in a boot loop. Well it turns out it more than likely was so don't say I'm impatient :d. So I forced it to shut down and it rebooted, but it didn't get past the Omni logo for almost an hour as well. So I decided to downgrade to the previous nightly. That didn't fix anything. After that, I tried to restore to cm 10.2 but it wouldn't let me for some reason. So I figured I was screwed. I downloaded Odin and attempted to restore to the stock rom. Well, Odin failed. So I was literally desperate and out of nowhere decided to try to downgrade the kernel. I attempted a downgrade to AJK 4.9 mic swap and it worked. So I installed MIUI after that (I'm too lazy to try adb) and it loaded up fine. I was so happy that at least something worked. After that I noticed the back and search buttons were not functioning. I decided to restore to cm 10.2 and it worked. Everything SEEMS fine but I'm not too sure if everything is. Can anyone tell me if my process is correct? Or if I messed up everything
Thanks!
I had to wipe the caches after i flashed the nightly to get it to boot.
The CM nightlies didnt work for me either. Something about the build.prop in Omni calling my phone both the ATT and ST version of the phone. I did what you did. Flashed AJ 4.7 i had, rebooted the Recovery, and Nandroid restored.
I liked Omni and ill be back but that battery life right now Ugh. Good luck Entropy and Co!

Continues lossing data

I have an HTC DNA on Straight talk, and I keep loosing data like every 3 days, I have tried different ROMs and am now running KitKat stock, thinking that it's related to software, but it still happens, I have to call them and they do different things and get it going again.
Does anyone else have the same issue or have any idea what's causing this.
I was running TWRP, but have changed to CWM to see if it would help, but it still happened.
I'm am running the deodex debloated KitKat.

Need help, endless reboots

Was running the unofficial lineage 14.1 rom, was getting frustrated with all the gps problems so I decided to try fulmics. Well cell service didn't work on fulmics, so I wanted to switch back and tough out the gps problems until lineage team got things fixed. Recovery seems to be working fine, but any rom I try to install simply endless reboots before every getting to the initial set up. I am at a loss, I am thinking I didn't have the new lg bootloader as I was told to have before trying to install fulmics. How the hell can I fix my phone? I always thought as long as recovery worked I would be fine, but that doesn't seem to be the case. Anyone help before I have to go out and buy a new phone tomorrow?
jamesvmccann said:
Was running the unofficial lineage 14.1 rom, was getting frustrated with all the gps problems so I decided to try fulmics. Well cell service didn't work on fulmics, so I wanted to switch back and tough out the gps problems until lineage team got things fixed. Recovery seems to be working fine, but any rom I try to install simply endless reboots before every getting to the initial set up. I am at a loss, I am thinking I didn't have the new lg bootloader as I was told to have before trying to install fulmics. How the hell can I fix my phone? I always thought as long as recovery worked I would be fine, but that doesn't seem to be the case. Anyone help before I have to go out and buy a new phone tomorrow?
Click to expand...
Click to collapse
PMd you.
I found a fix, I completely wiped everything and first flashed just the stock 7.0 lg bootloader, now everything is working fine. Thanks for the message though!
jamesvmccann said:
I found a fix, I completely wiped everything and first flashed just the stock 7.0 lg bootloader, now everything is working fine. Thanks for the message though!
Click to expand...
Click to collapse
No problem ?
Same Problem
I have the exact same problem. I flashed the LineageOS ROM, then flashed Fulmics ROM, then tried to go back to Lineage—and now every ROM just reboots endlessly, but I can boot into recovery and access TWRP just fine.
It looks like jamesvmccann found a fix, by "completely wiped everything and [then] flash[ing] just the stock 7.0 lg bootloader." I'm afraid I don't know where to download the stock 7.0 lg bootloader. This is a h830, so that may matter as well.
Any additional help would be greatly appreciated.
Managed to fix this problem myself
The stock h830 bootloader was linked in this forum post.
I booted into TWRP and flashed the stock bootloader. It has a different bootflash.
H850 keeps booting into Recovery
Hello everyone, I have a H850 and my phone does not want to boot into the OS. It keeps booting into Recovery mode. I tried flashing only the H850 bootloader and then installing a ROM, and it doesn't work. I've formatted everything except the SD card and still no joy. What else can I do to restore my H850?
Please Help!
KCKitsune said:
Hello everyone, I have a H850 and my phone does not want to boot into the OS. It keeps booting into Recovery mode. I tried flashing only the H850 bootloader and then installing a ROM, and it doesn't work. I've formatted everything except the SD card and still no joy. What else can I do to restore my H850?
Please Help!
Click to expand...
Click to collapse
I had same problem factory reset few times within twrp seem to work after a while. I take it your backup not working? If all else fails flash kdz in lgup
Sent from my LGE LG-H830 using XDA Labs

Categories

Resources