After flashing 44S modem , i get no signal - ONE Q&A, Help & Troubleshooting

Hello
i am on different Lollipop ROMs, and after succesfully flashing the 44S modem , despite the sensor problems. I have no signal afterwards ...
If i then flash the COS12 modem i get it right back :/
I have tried wiping dalvick / cache, tried rebooting , restoring default APN.,.... nothing works, please help

Related

[Q] boot loop every rom

So uhh, I unlocked the bootloader.
Flashed CWM Recovery.
and now I was on the point to install a rom..
factory wipe + cache wipe
format system
flash rom (tried cwm and Beanstalk)
flash gapps ("Gapps_Standard" from http://forum.xda-developers.com/show....php?t=2012857) (also tried those by developers)
wipe dalvik
reboot > bootloop.
Also tried to wipe everything again.
well, no luck
keep getting bootloop.
help please?
P.S.
I know how to flash a rom...
P.P.S
Moto G 4.4.2 Repack (stock) works.
But no wifi...
Me too bro....
Jur13n said:
So uhh, I unlocked the bootloader.
Flashed CWM Recovery.
and now I was on the point to install a rom..
factory wipe + cache wipe
format system
flash rom (tried cwm and Beanstalk)
flash gapps ("Gapps_Standard" from http://forum.xda-developers.com/show....php?t=2012857) (also tried those by developers)
wipe dalvik
reboot > bootloop.
Also tried to wipe everything again.
well, no luck
keep getting bootloop.
help please?
P.S.
I know how to flash a rom...
P.P.S
Moto G 4.4.2 Repack (stock) works.
But no wifi...
Click to expand...
Click to collapse
Yeah Bro I have this exact problem, except i made a backup and my wifi is working fine now. One thing tho i cannot connect to google servers and when i boot up it says inconsistent UID's device may not work properly format your data partition(formatted it and yah nothing)
cated resionit
Jur13n said:
So uhh, I unlocked the bootloader.
Flashed CWM Recovery.
and now I was on the point to install a rom..
factory wipe + cache wipe
format system
flash rom (tried cwm and Beanstalk)
flash gapps ("Gapps_Standard" from http://forum.xda-developers.com/show....php?t=2012857) (also tried those by developers)
wipe dalvik
reboot > bootloop.
Also tried to wipe everything again.
well, no luck
keep getting bootloop.
help please?
P.S.
I know how to flash a rom...
P.P.S
Moto G 4.4.2 Repack (stock) works.
But no wifi...
Click to expand...
Click to collapse
For no-wifi problem try to flash the rom from page 9 in repack thread. Work for me.

Corrupt efs

Hey guys. Is there any way I can tell if my phone's efs is corrupt?
Thanks!
Not really. What are your symptoms / why are you asking?
Well my Sim gets recognized but I can't call anyone and it says that the phone is in airplane mode. Also I can't change the preferred network type and it stays on LTE/GSM (PRL)
Rooted or not?
Yup, rooted
When you do anything in recovery do you get any errors about persist?
No, I don't think so
Have you tried to wipe / flash stock cache image?
How do I do that?
Recovery / fastboot
Well I've tried to flash to stock, when I flashed stock KitKat the imei would show incorrect but I could turn on the radio, but now with lollipop the imei is correct but the radio can't be turned on
Wipe cache from recovery
Just did it and nothing changed
Dunno then. Can only really suggest flashing back to stock kk again and if the same as before, contact lg support.
OK thanks anyways!

Bootloop after flashing stock rom in yureka plus

I was running cm14.1 nightly build(7.1.1) on my yu yureka plus, when i came across the "android n data toggle fix" on xda. I flashed that zip and since then my phone gave erratic reboots. So I tried to restore to an nandroid backup took a week ago but no luck. So I tried to flash resurrection remix 5.6, which sent my phone into a bootloop, but it started up as i plugged the phone into my PC (weird). Then I tried to hard reset the devices numerous time, even removed the battery for 5 min but still no luck. Next I flashed the official stock rom (cm12.1) via fastboot. It loaded up pretty quickly, but when i reached the welcome screen, it sent the phone into a reboot and got stuck again in bootloop. I tried several roms but no luck. I even flashed official modem, appsboot, hyp etc partitions multiple time and even reflashed the recovery (even tried different versions, including stock). PLease Help
romeovictor said:
I was running cm14.1 nightly build(7.1.1) on my yu yureka plus, when i came across the "android n data toggle fix" on xda. I flashed that zip and since then my phone gave erratic reboots. So I tried to restore to an nandroid backup took a week ago but no luck. So I tried to flash resurrection remix 5.6, which sent my phone into a bootloop, but it started up as i plugged the phone into my PC (weird). Then I tried to hard reset the devices numerous time, even removed the battery for 5 min but still no luck. Next I flashed the official stock rom (cm12.1) via fastboot. It loaded up pretty quickly, but when i reached the welcome screen, it sent the phone into a reboot and got stuck again in bootloop. I tried several roms but no luck. I even flashed official modem, appsboot, hyp etc partitions multiple time and even reflashed the recovery (even tried different versions, including stock). PLease Help
Click to expand...
Click to collapse
After flashing stock via fastboot, have you tried booting to recovery and factory resetting then wiping cache and Dalvik/ART cache? Try flashing the stock kernel if you're using stock ROM. If you're using a CM ROM then flash the CM stock kernel for your model.
Sent from my SM-S903VL using Tapatalk
ok so here's what happened
After I used fastboot image to flash the stock rom (i believe stock kernel is present in the rom too, since it has a boot.img), it took 10 minutes to boot upto the welcome page and then rebooted. I wiped cache and dalvik cache too and retried the process, but no luck
Droidriven said:
After flashing stock via fastboot, have you tried booting to recovery and factory resetting then wiping cache and Dalvik/ART cache? Try flashing the stock kernel if you're using stock ROM. If you're using a CM ROM then flash the CM stock kernel for your model.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
ok so here's what happened
After I used fastboot image to flash the stock rom (i believe stock kernel is present in the rom too, since it has a boot.img), it took 10 minutes to boot upto the welcome page and then rebooted. I wiped cache and dalvik cache too and retried the process, but no luck
Thanks for your reply dude
Anyways, the problem is solved.
The problem was never with the device, rather it was the battery that was faulty. When I kept the device plugged in to PC, it worked for sometime and when I pulled the wire out, it shut itselft down. Same was the case when I tried to multitask when connected to PC. But when I connected it to wall charger, it allowed me to multitask . Hope to buy a replacement battery soon.
Once again, thank you for your reply

Phone stuck in bootloop even after flashing stock rom!

Hello. My new phone got stolen. I currently have a phone named symphony W17 ( MT6572 ). I had flashed stock rom using sp flash tool, but its stuck in bootloop. I tried clearing data and dalvik cache from recovery but no luck, Its stuck in the bootloop. Please help me!
Most often we face a bootloop just after flashing a stock or custom ROM over an old one not having immediately cleared cache / data before a reboot. This might be a major factor behind the bootloop issue on your device.
xXx yYy said:
Most often we face a bootloop just after flashing a stock or custom ROM over an old one not having immediately cleared cache / data before a reboot. This might be a major factor behind the bootloop issue on your device.
Click to expand...
Click to collapse
But i cleared both cache and data and still its stuck in bootloop! Not just that I also did format whole flash using sp flash tool but the issue never goes. Please help me

Fix Bootloop when flashing custom rom

Whenever I flash a custom rom for this phone with TWRP, I get a Bootloop. I'm wiping all data and I switch partitions so that it flashes on partition A, but the issue still persists. Any solutions?

Categories

Resources