Develop Bugs

Can't get stock working with messed up EFS

Alright, so I just started using my OG on ringplus and decided to root with framaroot (I think I used gandalf mode). Anyways later on the phone started showing Demigod kernel issues (On stock zvc). So I went with Teenybin and flashed the unlocked bin using LGNPST. Same kernel issue. However custom roms don't show this issue. Now, the problem is I need to go back to stock so I can get to diag mode since my esn info got corrupted. Now this wouldn't be a problem since I'm alright with cdma workshop or DFS (I only want to repair the ESN), but of course I need to go back to stock. Any help is appreciated. Thanks!
EDIT: I should probably add that I have tried several roms, and several different bins (including full sized ones) yet I always come back with the same black screen with the Demigod kernel error. One more thing is that I have all the information that needs repairing, just can not use it until I get a working stock image.

Do custom stock roms work such as optimus DE or lifeless?
Also theres a guide somewhere on how to activate diag mode on aosp roms. Id link you but im on my phone. Should come up easily on searching the forums. i know theres a link to it in the irc chatroom.
Sent from my Sprint LG Optimus G on Page Plus.

Strangely aosp roms work fine minus service. I did try the guide, but for some reason I couldn't edit any of the efs settings even after I flashed the efs recovery zip they had. DFS and cdma workshop just bring up failed or errors when in diag mode. So far I tried DE, but I'll have to try Lifeless and see what happens. It's just so weird how the demigod kernel issue keeps appearing on stock and stock based roms, the phone freezes and reboots to a black warning screen.

Cody92 said:
Strangely aosp roms work fine minus service. I did try the guide, but for some reason I couldn't edit any of the efs settings even after I flashed the efs recovery zip they had. DFS and cdma workshop just bring up failed or errors when in diag mode. So far I tried DE, but I'll have to try Lifeless and see what happens. It's just so weird how the demigod kernel issue keeps appearing on stock and stock based roms, the phone freezes and reboots to a black warning screen.
Click to expand...
Click to collapse
Maybe try a stock rom with a custom kernel made for it like viper?
Sent from my Sprint LG Optimus G on Page Plus.

DQEight said:
Maybe try a stock rom with a custom kernel made for it like viper?
Click to expand...
Click to collapse
Where is viper? I didn't know it was made for this hardware...
Cody92 said:
Strangely aosp roms work fine minus service. I did try the guide, but for some reason I couldn't edit any of the efs settings even after I flashed the efs recovery zip they had. DFS and cdma workshop just bring up failed or errors when in diag mode. So far I tried DE, but I'll have to try Lifeless and see what happens. It's just so weird how the demigod kernel issue keeps appearing on stock and stock based roms, the phone freezes and reboots to a black warning screen.
Click to expand...
Click to collapse
Try this thread... If you flash the teeny bin it will give you an unlocked boot and recovery.
http://forum.xda-developers.com/showthread.php?t=2230106
I think that might fix your problem. Grab the teeny and not the full. The full is huge and will erase your info and is not necessary.
Try that out and come back. I am all but sure it is related to the bootloader/recovery.

dopy25 said:
Where is viper? I didn't know it was made for this hardware...
Try this thread... If you flash the teeny bin it will give you an unlocked boot and recovery.
http://forum.xda-developers.com/showthread.php?t=2230106
I think that might fix your problem. Grab the teeny and not the full. The full is huge and will erase your info and is not necessary.
Try that out and come back. I am all but sure it is related to the bootloader/recovery.
Click to expand...
Click to collapse
I probably should have said when I used LGNPST I used teenybin originally. I just downloaded it again now and flashed teenybin once more but got the same problem. I've tried lifeless and another stock based rom, but I still get the demigod crash. I used both TWRP and Philz touch to install stock roms. When I use an aosp rom and get into diag mode through the terminal I still can't use cdma ws or dfs to edit anything. I'm thinking stock might solve this, but that demigod error follows me everywhere. This problem is such a pain.

Viper Is here
http://forum.xda-developers.com/showthread.php?t=2486990

Alright I tried the lifeless stock rom and ended up with the demigod crash before booting up. I also received it when I tried the viper kernel. One more weird thing happened though. When I tried going into diag mode from the terminal on cm11 (4.4.4) windows didn't recognize it and I got the demigod crash. Could it maybe be that the dll for the lgnpst program is messed up so whenever I try to flash teenybin it corrupts the bootloader (I've done this too many times)? I'll try downloading and reinstalling lgnpst to see if it helps.

Alright, so I tried playing around with it a bit more and only got more problems. So after reinstalling lgnpst it seemed to make a difference, but still have similar problems. I ended up flashing a full bin of zvb after messing with teenybin for a bit, but it kept freezing followed by a reboot (tried factory resetting it too). Then I flashed the full zvc with more issues. It kept restarting again. So I flashed the unlocked teenybin and the power started acting weird, working sometimes (I've had this before when messing with it earlier). After I finally got it started from being connected to a charger for a while the phone got stuck on a new demigod error. This one said "Watchdog bark detected" and the screen was a weird yellow tint. Custom roms still work though for some reason. The last part is the meid and imea info shows up as unknown after flash the zero efs file with twrp. This phone is starting to get real annoying.
UPDATE: Alright, so after I flashed to zvb without success I figured there wasn't much hope on downgrading. However, I found there are some older ics bins. I downloaded the zv7 bin and flashed it. So far the phone has not crashed. I'm not quite sure why, but the jelly bean stock firmware causes my phone to crash. I will add more details if I can get it back working on Ringplus.
Some more details: So for some reason the zero out efs isn't working for me. All of the imei and esn info all shows as unknown on my phone. Stock hasn't crashed yet, but the spc seems to be corrupted or something. My old spc code and all 0's don't work. Cdma ws, cdmadevterm, and anything else I use to get into diag stuff always freezes when attempting the read for the phone. I hope my efs isn't corrupted beyond repair.

Any ideas? Short of replacing the logic board, I'm not really sure what to try. I've used 2 different computers to try and mess with the efs, but like I said the programs would hang. Could it maybe have anything to do with Windows 8.1, should I try with 7? I'm getting ready to give up on this phone, it's been bugging me for too long.

Alright, just thought I'd give an update since I finally got around to working on it one more time. I should mention that when I first had this problem I ordered another ls970 with a broken screen just to replace the logic board, well when I rooted it the same thing happened while it was being unlocked (or possibly before). So I figured I would just not root it or mess with the bootloader. Unfortunately that wasn't the problem. After ordering one last ls970 with a broken screen (they're pretty cheap at least), I replaced the logic board. It worked for a while, than the same problem problem occurred. I never tried rooting or unlocking it. I needed to update the profile through the settings, but that should not have done this. I can only think of 2 possibilities. My Google account managed to backup something from the other ones that caused the problem or something with updating the profile with Ringplus caused it. I'm just going to give up on it this time, working with esn fix didn't work and it would take way too long if it did.

[Q] Battery drainage because of mobile data

Hi Guys,
I am new to this forum and got a small question. My girlfriend has an Oppo Find 7a. You guys probably know that the stock ROM is ColorOS. In my opinion it's crappy as hell, lots of bugs and issues, so I decided to flash Dirty Unicorns 5.02 on it. I did that yesterday and all is working fine so far, except that the battery drained from 100% to 64% last night (in 8 hours). See the photos attached. According to the photos it seems clear that the issue is the mobile data usage. I've checked the settings and it seems mobile data loses connection, connects again and loses connection everytime. Probably this is the cause of the battery drainage. Somewhere on this forum I read something about flashing Alucard 1.1a kernel on it to fix this issue. I want to try this in the evening, but does anyone know the correct type of this kernel as I found different alucard 1.1a download links?

Can someone please help me out with this? Yesterday evening I just flashed the Alucard 1.1a kernel via the custom recovery. I also removed dalvik/cache and rebooted after that. The Oppo boot logo appeared, but it stayed like this for 20 minutes. I'm not sure if I have to wait any longer to make it work or if the phone is just not booting up anymore with this kernel. Any advice?

GRDD_ said:
Can someone please help me out with this? Yesterday evening I just flashed the Elucard 1.1a kernel via the custom recovery. I also removed dalvik/cache and rebooted after that. The Oppo boot logo appeared, but it stayed like this for 20 minutes. I'm not sure if I have to wait any longer to make it work or if the phone is just not booting up anymore with this kernel. Any advice?
Click to expand...
Click to collapse
before flashing DU did you flash proper modem and trustzone firmware?

treacherous_hawk said:
before flashing DU did you flash proper modem and trustzone firmware?
Click to expand...
Click to collapse
Nope, actually I didn't. I wasn't aware of the fact that this was necessary. I had ColorOS 2.0.0i on it and flashed DU directly on it.
Can you maybe tell me what the proper modem and trustzone firmware is? And can these still be installed now even if DU is already flashed on it?

GRDD_ said:
Nope, actually I didn't. I wasn't aware of the fact that this was necessary. I had ColorOS 2.0.0i on it and flashed DU directly on it.
Can you maybe tell me what the proper modem and trustzone firmware is? And can these still be installed now even if DU is already flashed on it?
Click to expand...
Click to collapse
well you can do a clean flash again but this time you have to follow this for how and why to flash modem and TZ firmware:
https://plus.google.com/+BoskoTrkulja/posts/CENAM1a7Zob
you can get the modem and tz firmware here:
https://www.androidfilehost.com/?fid=95916177934529695

Sir, have my thanks! You are my hero of today. Thanks a bunch. I'm going to try this

treacherous_hawk said:
well you can do a clean flash again but this time you have to follow this for how and why to flash modem and TZ firmware:
you can get the modem and tz firmware here:
Click to expand...
Click to collapse
So, one more thing If I may ask. What is the best thing to do from here on:
1. Flash modem, flash firmware, flash DU (directly over the DU rom that is installed now without doing a factory reset / wipe)
2. Flash modem, flash firmware, perform a factory reset / full wipe and then flash DU.
And will the newly flashed modem and firmware stay on the phone when i do a full wipe?

GRDD_ said:
So, one more thing If I may ask. What is the best thing to do from here on:
1. Flash modem, flash firmware, flash DU (directly over the DU rom that is installed now without doing a factory reset / wipe)
2. Flash modem, flash firmware, perform a factory reset / full wipe and then flash DU.
And will the newly flashed modem and firmware stay on the phone when i do a full wipe?
Click to expand...
Click to collapse
do a clean wipe, then flash modem, then firmware (in bootloader) and then rom along with gapps.

treacherous_hawk said:
do a clean wipe, then flash modem, then firmware (in bootloader) and then rom along with gapps.
Click to expand...
Click to collapse
Alright, I will do it in that order then. Thanks again. Much appreciated.

treacherous_hawk said:
do a clean wipe, then flash modem, then firmware (in bootloader) and then rom along with gapps.
Click to expand...
Click to collapse
It's been a few weeks, but I finally had the time to do this. I've done a full wipe in TWRP and then flashed the modem on it. This showed succesful. It took about 10 minutes before the phone booted up afterwards. After that all seemed fine, so i've put the phone in bootloader via a command in cmd and installed the firmware. This also went succesful, but now I still have the same issues on the Oppo regarding the provider issue as mentioned earlier. The data connection is still being lost very often and it still seems to be draining battery (although less than before). Is there something else I can do to fix this ?

GRDD_ said:
It's been a few weeks, but I finally had the time to do this. I've done a full wipe in TWRP and then flashed the modem on it. This showed succesful. It took about 10 minutes before the phone booted up afterwards. After that all seemed fine, so i've put the phone in bootloader via a command in cmd and installed the firmware. This also went succesful, but now I still have the same issues on the Oppo regarding the provider issue as mentioned earlier. The data connection is still being lost very often and it still seems to be draining battery (although less than before). Is there something else I can do to fix this ?
Click to expand...
Click to collapse
If you have recently done a clean install, give it some time to settle down. For Data connection issue, make sure to check your APN and also try a different sim or this sim in some other phone, could be signal reception issue.

treacherous_hawk said:
If you have recently done a clean install, give it some time to settle down. For Data connection issue, make sure to check your APN and also try a different sim or this sim in some other phone, could be signal reception issue.
Click to expand...
Click to collapse
I will give the battery thing some time to settle down then. About the data connection issue; This was not an issue on coloros, but I will check apn and try another sim. Thanks again!

I've changed the APN settings, as they stood on some kind of roaming setting. It's now been set to live.vodafone and seems to be functioning better already . If I still run into some issues I'll let it know. Thanks for helping me out

Lollipop Roms drop connection when screen turns off

I recently tried to upgrade to CM 12.1 for my T Mobile S4 being used on the Wind Network in Canada. But when ever the screen turns off it will lose connection to the cellular network, when i turn it back on i get a bunch of notifications, sometimes it will buzz 2 or 3 times for the same notification. I tried searching but can't find anything pertaining to this. i also tried other builds, Slim LP, Resurrection and the GPE but still all show the same issue
Has anyone seen this before let alone know how to fix it?

icewolf293 said:
I recently tried to upgrade to CM 12.1 for my T Mobile S4 being used on the Wind Network in Canada. But when ever the screen turns off it will lose connection to the cellular network, when i turn it back on i get a bunch of notifications, sometimes it will buzz 2 or 3 times for the same notification. I tried searching but can't find anything pertaining to this. i also tried other builds, Slim LP, Resurrection and the GPE but still all show the same issue
Has anyone seen this before let alone know how to fix it?
Click to expand...
Click to collapse
lollipop is known to be buggy with network on our device. Sometimes I even get sim card removed message and after a couple dozen reboots will my sim be recognized again. I suggest to stick with the rom that works flawlessly for you and skip lollipop, for now atleast.

And that's why I only root my phone, and run it stock. Roms always do this, no matter what anyone says. And I said this in my other thread, but ppl try to day otherwise. I told you guys lollipop roms are buggy for our phones. 4.4.4 for the win. Just uninstall bloatware and ur good to go.
Sent from my SGH-M919 using XDA Free mobile app

epicboy said:
lollipop is known to be buggy with network on our device. Sometimes I even get sim card removed message and after a couple dozen reboots will my sim be recognized again. I suggest to stick with the rom that works flawlessly for you and skip lollipop, for now atleast.
Click to expand...
Click to collapse
So it's not just me with the SIM Card problem either. I got that so many times on lollipop and I tried to flash a 4.4.4 ROM again and it would still give me the SIM Card not detected. I was going to get it repaired again and I flashed stock MetroPCS tar and it got rid of the problem. I don't knowant if I would root again and just flash a 4.4.4 ROM and use xposed. I don't want that SIM Card problem to happen again. It's annoying.

j21098 said:
So it's not just me with the SIM Card problem either. I got that so many times on lollipop and I tried to flash a 4.4.4 ROM again and it would still give me the SIM Card not detected. I was going to get it repaired again and I flashed stock MetroPCS tar and it got rid of the problem. I don't knowant if I would root again and just flash a 4.4.4 ROM and use xposed. I don't want that SIM Card problem to happen again. It's annoying.
Click to expand...
Click to collapse
In my experience. After flashing a kitkat rom and rebooting a couple times the problem is fixed.

epicboy said:
In my experience. After flashing a kitkat rom and rebooting a couple times the problem is fixed.
Click to expand...
Click to collapse
I stayed with it for about a week before flashing stock firmware. Rebooted many times while I had it and it still happened. I've been on stock firmware for over 3 weeks and no problem at all.

j21098 said:
I stayed with it for about a week before flashing stock firmware. Rebooted many times while I had it and it still happened. I've been on stock firmware for over 3 weeks and no problem at all.
Click to expand...
Click to collapse
In my experience it worked. I was on a touchwiz kitkat rom. Were you on AOSP kitkat when it still didn't wirk?

epicboy said:
In my experience it worked. I was on a touchwiz kitkat rom. Were you on AOSP kitkat when it still didn't wirk?
Click to expand...
Click to collapse
No, I tried MD 1.3 and the stock T-Mobile ROM. Also forgot to mention I had a really bad problem with the Play Store. I couldn't install anything at all. I'd always get error 905 and this other number I forgot. No matter what I tried I couldn't get a fix, clearing cache, data, dalvik, uninstalling updates, reboots after each one and nothing fixed. Stock Firmware seemed to fix all the problems I had

Nv Rebuild ... Custom. How to restore...

Hello this is my 1st post on this forum, i have a 7105 lte no operator and im from portugal. Ive tried cm rom and after that Dn4 rom, all works great except for gps. I was in the change i gess that afected my gps lock, i have read and the only thing i think that haven,t tried was the nv rebuild but, say a custom and won,t allow me to reset. I havs tried with stock rom, with dn4, with root and without same thing.... can anyone help me?.

Choco Man said:
Hello this is my 1st post on this forum, i have a 7105 lte no operator and im from portugal. Ive tried cm rom and after that Dn4 rom, all works great except for gps. I was in the change i gess that afected my gps lock, i have read and the only thing i think that haven,t tried was the nv rebuild but, say a custom and won,t allow me to reset. I havs tried with stock rom, with dn4, with root and without same thing.... can anyone help me?.
Click to expand...
Click to collapse
Flash stock ROM again.
Sent from my GT-N7100 using Tapatalk

Allready did that multiple times. Also my nv rebuild says custom and dont allow me to acess it

Like this... this post resumes my problem... HELP
d0ctorj3kyll said:
Hi
XDA newbie, still learning where everything is! I posted this question in the general help thread but got no replies, then I found this section so please pardon the repost
I have a rooted Galaxy Note 2 N7105 (t0lte I think) running Samsung Stock software 4.4.2. I have previously installed various version of CyanogenMod and Ditto Note, and somewhere along the line have lost my GPS functionality! Running CWM recover, not sure what version off the top of my head. The exact issue is that when I turn GPS on, it shows the "searching" symbol endlessly and will not lock to any satellites.
I have tried reflashing the modem and every GPS fix app that I've seen suggested on forums, and it still will not lock my location by GPS. Power saving (wi-fi and mobile network) location still works.
From my research, I believe the NV Rebuild method (listed here http://forum.xda-developers.com/showthread.php?t=2211690) is what I need to do in order to fix the problem. However when I access the hidden dialer menu and select NV Rebuild it tells me "Not Support in Custom Binary!" Other people have had this issue and posted asking for help in the thread, but nobody replied or helped them.
As I mentioned, I am running stock Samsung software, not a custom ROM. The phone is rooted, and I do have a few Xposed modules installed. I also used Triangle Away and my bootloader shows the device status as Samsung Official. It also showed Official in settings when I tried to run the NV Rebuild. As far as the information went, this should be all I needed to make NV Rebuild work, but it still gave the custom binary error.
Does anyone have any suggestions for how to get around this? Do I need to completely unroot my phone and reflash a vanilla copy of Samsung 4.4.2 before it will work, or is there a workaround to make the service menu read my phone as official and run the NV Rebuild?
Any thoughts or ideas would be HUGELY appreciated as this issue has been driving me mental! (Please let me know if you need further information and I will try to provide it ASAP)
Thanks in advance!
Click to expand...
Click to collapse
Helpppp

Choco Man said:
Helpppp
Click to expand...
Click to collapse
Try lineageOS 14.1. My GPS was dead after going back to kitkat after lineage. NV rebuild also not support in custom binary. Found the solution here https://forum.xda-developers.com/ga...nt-n7105/rom-lineageos-n7105-t3538310/page136
From lineage I did only a format(not wipe or factory reset, I dont know what is the difference) in TWRP 3.2.3 and flashed zip of the omnirom kitkat, and GPS was working, then format and flashed official FTM ROM. Maybe not need to go via omnirom, for me it was clear that kitkat is not getting the fix and it was easier to flash a zip kitkat than an image from Odin.

chitz852 said:
Try lineageOS 14.1. My GPS was dead after going back to kitkat after lineage. NV rebuild also not support in custom binary. Found the solution here https://forum.xda-developers.com/ga...nt-n7105/rom-lineageos-n7105-t3538310/page136
From lineage I did only a format(not wipe or factory reset, I dont know what is the difference) in TWRP 3.2.3 and flashed zip of the omnirom kitkat, and GPS was working, then format and flashed official FTM ROM. Maybe not need to go via omnirom, for me it was clear that kitkat is not getting the fix and it was easier to flash a zip kitkat than an image from Odin.
Click to expand...
Click to collapse
Your solution gains my interest. I am using GT-N7105 too. The road of Roms I have been through is Lineage 14.1 -> Resurrection Remix 5.8.5 -> Stock 4.4.2
When I went back to the Stock rom, GPS totally unable to detect any satellite using any GPS tools app. IMEI blank but Baseband is still there, the weird thing is the phone network signal works without issue. :angel:
Have been trying many ways to fix GPS including reflash stock rom but still failed. I went back to resurrection remix 5.8.5 and GPS works without issue but IMEI is still blank.
Any recommended omni rom as you mentioned? and what is official FTM rom? A stock rom?

[D855 32 GB] Reboot problems (brick or hardware defect?)

Hello guys,
I managed again to brick my phone.
I flashed Fulmics as I wanted to swap from those not fully stable nougat roms. Well, I have no idea what caused my problem - Fulmics run without prolbems for a 2 or 3 days including xposed etc.
Then today I changed my ChromePie options and that's when the reboots began. I don't know if this the real cause was though.
So I tried to flash another rom but always got random reboot even in recovery after few minutes/seconds. So I went all the way back to stock rom (4.4.2) with LG Flash tool - which worked after a few tries. Then I installed MM rom via .kdz file and flash tool 2014, which also worked after a few more tries. But then the reboots started again. Can't say if the 4.4.2 rom was without boots because I updated to 6.0 quite quickly.
The strange thing is that after some reboots phone won't boot again and I have to take and leave out the battery for some time to boot the phone again.
Any solutions for my problems?
Best regards

..bumped into the same 1/2 year ago. Didn't want to put to much effort so,..went to stock and back, worked for me.
Good luck.

Gerhard.M said:
..bumped into the same 1/2 year ago. Didn't want to put to much effort so,..went to stock and back, worked for me.
Good luck.
Click to expand...
Click to collapse
Which stock and how did you go back?
As mentioned I already went back to stock but the issue kept occuring.

Hi, got the same problem with my G3
wi fi and bluetooth didn't work and phone loop rebooted
Here below the steps I followed to solve
1) First attempt (didn't solve): had cloudy rom, got back to stock official but still rebooting, tried fulmics and other rom but problem persisted.
2) second attempt (didn't solve): went back to stock and changed battery (found somewhere in internet), now I have a brand new battery but a phone still loop rebooting
3) third attempt (SOLVED): found that the wi-fi / bluetooth chip (one for both) copuld have unwelded and solved so (it appears I can't post outside link, delete spaces to have the correct link):
youtube .com / watch?v=1zWpzYh2DPI&t=15s"
youtube .com/ watch?v=6_0jzp65eLY&t=256s
Now i'm on fulmics and no more loop reboot
Hope you can solve
[sorry for my english]

frosty234 said:
Which stock and how did you go back?
As mentioned I already went back to stock but the issue kept occuring.
Click to expand...
Click to collapse
http://stockroms.net/file/LGG3/D855/European/BIN_LGD855AT-00-V10e-EUR-XX-JUL-08-2014-32G-0.zip
http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/D855/
used flashtool
have to say restoring and/or flashing isn't always that stable. I've experienced it sometimes needs a 2nd try.
Hopefully it isn't a hardware issue in your case.

So I tried all of oyur suggestions but nothing seems to work.
On the contrary I ended up in a status where I can't even flash a new firmware.
In LG Flash Tool 1.8.1 I get the error
"Donwload Fail!!!"
PID: NULL
IMEI: NULL
MODEL:
DLL: D855
BIN: LGD855AT.....
SWV:
SWOV:
Model Information Check Fail!
000000000
Click to expand...
Click to collapse
In LG Flash Tool 2014 (flashing MM with kdz file) phone shuts down in middle of process.
But I can still access Download Mode.

No more ideas?
I really think I finally broke my phone... But the fact that I can still access download mode keeps my hopes up.

So, after 2 months I just tried to reawaken my phone. Still the exact same problem. It just keeps shutting down aber some while, but just when I start flashing something. If it stays connected to computer whitout doing anything it can stay on for like ever.
Can anyone confirm that this could be a hardware defect?