Related
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Seriously???
pastorbob62 said:
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Click to expand...
Click to collapse
Not to be negative or anything but I think this is the least responsive forum on this site. I have spent hours searching for possible solutions to various problems I've encountered over the past several months, asked several questions and received little if any help. I was only able to get back from a bricked phone to where I am now by using information found on other websites. Pretty sad if you ask me.
In contrast, whenever I have asked a question on my tablet's forum I've received fast workable solutions/answers to my problems/queries. The threads are informative, well organized and contain answers to any situation I have encountered.
Granted, my current problem with my phone is my own fault for trying to customize it. And I suspect part of the problem is due to the age of this phone thus most of the "experts" have moved on to other ventures. It is also hindered by the lack of information available from Huawei and the service providers.
All of that said, if anybody has any suggestions for how I can repair the ESF partition or whatever is causing this lack of mobile service issue I would be extremely grateful. It isn't the end of the world since i have a new phone (Consumer Cellular) that I am currently using but it would be great to get this one working since it's much faster and more streamlined than my stock Consumer Cellular version.
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
Thank you very much for your reply. It seems that you have found the answer to my problem. But unfortunately, I don't have a copy of the original stock ROM. My phone is the -51 version and any links I have found to the stock ROM are broken. There is a version I found but it is for Venezuela and I don't think it will work. I am leery to try it and totally brick my phone. My backup is apparently corrupted. I backed up my new working phone with Disk Image and attempted to restore it to the broken phone but all that did was cause it to come up to the ATT logo screen for a few seconds and then shut down. It wouldn't do anymore than that. So I restored the Stallion 3.5 image I made and am back to a great fast tablet with no phone service. I also tried backing up my IMEI on the working phone and restoring it to the broken phone but that had no effect.
It is my understanding that the -Pro version of the ROM will work, but I don't have the stock image of that either. I suspect it work might since I was able to use the -Pro version of GB on it. All of my internet searches have only turned up custom ROMs and other desperate people looking for fixes for similar problems or worse. I agree 100% with your assessment of Huawei's lack of meaningful support. It really is a shame, because these phones aren't half bad when they have been customized and OC'ed a little.
I have just about given up on it and resigned myself to using it as an MP3 player for my car system. I have learned my lesson and am leaving the working phone stock. It is rooted and I have cleaned off all of the bloatware, and set it up so most apps run from my SD card, so it really isn't half bad. At least it works.
Again, thank you for your reply and advice.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
ggunzio said:
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
Click to expand...
Click to collapse
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Blefish said:
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Click to expand...
Click to collapse
i have exactly the same phone than you, because i installed that backup too. After installed it, the IMEI SV is 36, after installing B518 it says it is 18, but before it was 17, and i had 3g signal, but not now.
My question is, wich SV is your phone reporting?
Thank you
I also have a problem like this, but I think it's a bit more severe. My phone got stuck while charging. Couldn't reboot. Was getting stuck on the aurora loading screen(using DZO 5u20). Than reinstalled whole rom. But now I don't any signal and the phone doesn't even see a SIM card. Showing 'baseband unknown' and the IMEI and IMEI SV are also unknown. Not 0's but just unknown. Is this is a similar problem? And can something be done to fix it.
I had some backups on my sd card, untill the sd-card got fried in the phone a couple of months ago.
Here's the story
1. this phone wouldn't boot up after the OTA update, the screen read "firmware upgrade encountered an issue.
please use software repair assistant & try again."
2. used odin 3.09 to reflash pit and the latest nc4 official firmware (I know it can't be rooted, but that's the only choice I have).
3. phone came back alive, worked for t-mobile and verizon sim cards.
Problem:
after a few hours or maybe a day, or maybe a restart, phone won't detect sim card, baseband version shows unkwown, hardware
version is empty, imei, network, MIN, PRL version, ERI version, imeisv, iccid are all "unknown".
What I have done:
phone will be back to normal if I flash the firmware again, I've use odin 3.09 and kies 3 many times.
I also tried flashing different modems, for ex, MI9, MJE, NC2 even NC4. But phone will keep restarting, sometimes the phone is working after
a few restarts. But eventually I will have the same problem again.
I was wondering if someone could point me to the right direction?
nicedog said:
Here's the story
1. this phone wouldn't boot up after the OTA update, the screen read "firmware upgrade encountered an issue.
please use software repair assistant & try again."
2. used odin 3.09 to reflash pit and the latest nc4 official firmware (I know it can't be rooted, but that's the only choice I have).
3. phone came back alive, worked for t-mobile and verizon sim cards.
Problem:
after a few hours or maybe a day, or maybe a restart, phone won't detect sim card, baseband version shows unkwown, hardware
version is empty, imei, network, MIN, PRL version, ERI version, imeisv, iccid are all "unknown".
What I have done:
phone will be back to normal if I flash the firmware again, I've use odin 3.09 and kies 3 many times.
I also tried flashing different modems, for ex, MI9, MJE, NC2 even NC4. But phone will keep restarting, sometimes the phone is working after
a few restarts. But eventually I will have the same problem again.
I was wondering if someone could point me to the right direction?
Click to expand...
Click to collapse
When you flashed the different modems, did you check settings/about the phone to verify that the modem flash " took"? Recommend entering Odin from power off, especially when flashing modems. FWIW, I'm not at all sure this will fix your problem, but it's worth a shot.
cam30era said:
When you flashed the different modems, did you check settings/about the phone to verify that the modem flash " took"? Recommend entering Odin from power off, especially when flashing modems. FWIW, I'm not at all sure this will fix your problem, but it's worth a shot.
Click to expand...
Click to collapse
Yes I did. The baseband version showed MI9 when my phone was still working properly.
nicedog said:
Yes I did. The baseband version showed MI9 when my phone was still working properly.
Click to expand...
Click to collapse
OK. Hopefully someone else will chime in with some suggestions.
one more thing I've done many times so far is, sometimes a full reset will bring it back to normal too.
settings -> backup and reset -> factory data reset.
I don't mind bricking my phone, but maybe someone knows other possible way, say, flashing EFS? I don't even know what that is.
I've been searching for the right solution but I haven't found one yet.
Never ever give up!
I'm the OP and I finally got it working. I simply ran EFS Professional v2.1.73, did a backup and restore of the EFS. That's it!
Did you figure out what efs is?
Sent from my SM-N900V using XDA Premium 4 mobile app
It didn't last long, and using EFS profession for EFS backup/restore never worked again.
I then saw this page the other day,
http://forum.xda-developers.com/showthread.php?t=2610757
So I used odin to flash
pit
official kitkat rom
I also checked these two,
erase nand
erase EFS
the phone booted up fine, I then turned it off and entered recovery mode, did a data and cache wipe, then booted up the phone again, that brought back my imei, my sim card worked again.
Unfortunately I'll lose it again once I flash a custom rom, or perhaps even a reboot.
I'm still searching for a permanent solution. But at least now I can use my sim card with a stock rom
Rom based on which region?
nicedog said:
It didn't last long, and using EFS profession for EFS backup/restore never worked again.
I then saw this page the other day,
http://forum.xda-developers.com/showthread.php?t=2610757
So I used odin to flash
pit
official kitkat rom
I also checked these two,
erase nand
erase EFS
the phone booted up fine, I then turned it off and entered recovery mode, did a data and cache wipe, then booted up the phone again, that brought back my imei, my sim card worked again.
Unfortunately I'll lose it again once I flash a custom rom, or perhaps even a reboot.
I'm still searching for a permanent solution. But at least now I can use my sim card with a stock rom
Click to expand...
Click to collapse
Can you please tell the stock rom based on which CSC ? or country ?
I'm having the same issue. Lost baseband and imei, but never got it recovered. even with stock.
I use this one,
ALL_VZW_N900VVRUCNC4_N900VVZWCNC4_1487472_REV03_user_low_ship_MULTI_CERT.tar.md5
http://www.trueandroid.com/2014/05/n900vvrucnc4-android-442-kitkat.html
Same boat brother, this is what I've posted. So far I'm a week in this situation, battery pull brings it back, any mod like Xposed with module where you have to reboot looses the baseband, IMEI etc. I have backup of the EFS and restored it multiple time with no joy.
Need some advice guys for Verizon my Note 3, I'm currently stock NC4 ready to. flash this bad boy ROM, after root access with TowelRoot, installation of BusyBox and Supersu no SafeTrap yet. Once I reboot in this state, I have the Baseband unknown under Settings-About Phone status all unknown info on IME etc etc. Off course I loose 4G signal all together. I may reboot again and it comes back. I know about EFS partition corruption and have multiple backup of My note 3 EFs partition. Even with restore it would still happen. I have exhausted all my knowledge learned throughout the years from you guys. But, I'm asking some help again. I am very familiar with all the terms about flashing/rooting so please feel free to throw some genius on how I can fix this thing.
Sent from my SM-N900V using Tapatalk
I have searched everywhere with no luck. My I337Z was 4.4.2 (after OTA) working well, no root, no unlock. Suddenly IMEI and Baseband go null. So what I did first was to restore it to factory settings, which didnt work and also some native apps like Contacts stopped working (not opening). I tried to restore it through KIES, it put my phone in Emergency mode, no escape there...I then went to the Factory files http://forum.xda-developers.com/showthread.php?t=2448794 which got my phone back to 4.2.2 and working...but still no Signal nor IMEI nor Baseband. I flashed MODEM and now it doesn't have any sound, wifi either....I went through KIES again and was able to catch the files it downloads when initializing the device, flash the System, MODEM and CSC, but same results and it is still on 4.2.2. Also when trying to flash Bootloader I get FAIL(Auth) code (I suppose because my BL is not unlocked)
My request:
I am thinking if someone can make a backup of System partition, I could put it into my phone as RESTORE through TWRP (not installed yet) I might be able to revive this device.
EDIT: I am looking build i337ztuubne2 since my bootloader is now ne2 because of the OTA
Suggestions are welcome!! Thanks!!!
MAGICPERF said:
I have searched everywhere with no luck. My I337Z was 4.4.2 (after OTA) working well, no root, no unlock. Suddenly IMEI and Baseband go null. So what I did first was to restore it to factory settings, which didnt work and also some native apps like Contacts stopped working (not opening). I tried to restore it through KIES, it put my phone in Emergency mode, no escape there...I then went to the Factory files http://forum.xda-developers.com/showthread.php?t=2448794 which got my phone back to 4.2.2 and working...but still no Signal nor IMEI nor Baseband. I flashed MODEM and now it doesn't have any sound, wifi either....I went through KIES again and was able to catch the files it downloads when initializing the device, flash the System, MODEM and CSC, but same results and it is still on 4.2.2. Also when trying to flash Bootloader I get FAIL(Auth) code (I suppose because my BL is not unlocked)
My request:
I am thinking if someone can make a backup of System partition, I could put it into my phone as RESTORE through TWRP (not installed yet) I might be able to revive this device.
Suggestions are welcome!! Thanks!!!
Click to expand...
Click to collapse
KIES 2.6 or 3? You had to be root to get to TWRP. Did the Z model ship with 4.2? I would be surprised, but don't really know. try 3. Start in download mode. I use cricket as well but never a cricket device. I will be in our cricket retailer today, the guys are pretty much ignorant to anything more than activating but possibly one may have a Z/s4 we could pull a nandroid from. Doubtful.
Sounds like you need a warranty replacement. Lesson learned? Always backup EFS!
halfevildruid said:
KIES 2.6 or 3? You had to be root to get to TWRP. Did the Z model ship with 4.2? I would be surprised, but don't really know. try 3. Start in download mode. I use cricket as well but never a cricket device. I will be in our cricket retailer today, the guys are pretty much ignorant to anything more than activating but possibly one may have a Z/s4 we could pull a nandroid from. Doubtful.
Sounds like you need a warranty replacement. Lesson learned? Always backup EFS!
Click to expand...
Click to collapse
First, the phone came with 4.2.2, so I used the files that kies 2.6 downloaded (haven't tried with kies 3) but the phone had 4.4.2 when it started acting up. It was updated OTA. As of now, I am rooted with twrp installed, no issues there. Now, if you could extract a nandroid from one of them, would be great! I do want to be on KitKat and not JB. I can flash it through odin 4.2.2 with no WiFi, sound nor calls. I think because the baseband is for KitKat and not for JB
Hi, I followed the DirtySanta tutorial, used the US996 DeODEXed Rom. I knew this was a possibility but thought that I could get back to stock using the KDZ, unfortunately my phone is now seen as US996. I've tried modifying both the build.prop, and KDZ but I still can't get LGUP to flash back to stock. Is there anything I can do?
Service Unavailable is probably due the frequency signal issue.
Remember that Wind runs in AWS bands, while the US996 runs on regular bands (Bell, Rogers, Telus)
I'm sure the phone works fine if you use a Rogers SIM on it.
so, the trouble / solution is figuring out how to flash back the Tmobile / Wind modem back into the phone.
also set the phone to use the proper AWS bands 1700 / 2100, or the new LTE band 66
AllGamer said:
Service Unavailable is probably due the frequency signal issue.
Remember that Wind runs in AWS bands, while the US996 runs on regular bands (Bell, Rogers, Telus)
I'm sure the phone works fine if you use a Rogers SIM on it.
so, the trouble / solution is figuring out how to flash back the Tmobile / Wind modem back into the phone.
also set the phone to use the proper AWS bands 1700 / 2100, or the new LTE band 66
Click to expand...
Click to collapse
T-Mobile H918 supports LTE Band 66, try and flash a H918 ROM maybe? Or access the hidden menu and enable AWS, but you'll lose LTE and only have 4G that way.
See here to access the hidden menu but change 915 in the command to 996 or the model the phone is showing as.
https://forum.xda-developers.com/v20/how-to/access-hidden-menu-h915-t3515098
Edit: Let me know if it works, and you get LTE back (not just 4G) I really want to know to root my H915 as well. You used the [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151, right?
Second edit: If you're going to try to flash an H918 ROM I'd strongly suggest you flash an H918 kernel that is suggested in the dirty santa thread, I think the Konverged is what people are using. No hard evidence either way flashing an H918 ROM would work but it may not as the boot image is a 996.
Thanks guys. I flashed the Konverged kernel earlier, it helped crash-wise but nothing on the signal end. Last night I extracted the files from the H91510e kdz and tried to flash the modem that was included but that hasn't helped, I want to try the CDMATool but it isn't recognising my account so I'll wait for a bit. I tried to use the hidden menu but it doesn't seem to do work on this firmware unfortunately.
Splinter77 said:
Thanks guys. I flashed the Konverged kernel earlier, it helped crash-wise but nothing on the signal end. Last night I extracted the files from the H91510e kdz and tried to flash the modem that was included but that hasn't helped, I want to try the CDMATool but it isn't recognising my account so I'll wait for a bit. I tried to use the hidden menu but it doesn't seem to do work on this firmware unfortunately.
Click to expand...
Click to collapse
Try this, make sure USB Debugging is enabled. Turn off phone. Remove the battery. Put battery back in. Hold the volume up button and plug in USB cable. It may boot into download mode or it may boot into the dirty santa corrupt screen. If it does boot into the corrupt screen , let go of up button, press the power button then IMMEDIATELY press the volume up button. Either way you should be in download mode. You want download mode, not fastboot. Make sure LGMobileDriver_WHQL_Ver_4.1.1.exe drivers are installed.
Download LG Support Tool. http://www.mylgphones.com/lg-software-tools-download the 'Download and install LGMobileSupportTool.exe' link. Install and run it. If you've already installed the drivers hit cancel when they go to install.
Then go to 'Options' 'Upgrade Recovery' Make sure you have the IMEI number from under the battery and put it in no dashes or spaces. It should download and install the firmware if you've done the tap 'About Phone' 'Developer Options' 'Enable USB Debugging' but I'm sure you know this.
If all goes well you should be back on stock firmware.
Hope it works, it should but I'm not 100% sure.
The good news is that it recognized my phone as H915, but unfortunately half way through the setup it through a weird error. Part of me is thinking of restoring my twrp backup and trying uppercut again. I'm hoping that will get the program to see my phone correctly.
EDIT: I tried the KDZ installer again, without trying to restore the TWRP backup and my phone is back to stock and getting a signal. Thanks again to the both of you.
Splinter77 said:
The good news is that it recognized my phone as H915, but unfortunately half way through the setup it through a weird error. Part of me is thinking of restoring my twrp backup and trying uppercut again. I'm hoping that will get the program to see my phone correctly.
EDIT: I tried the KDZ installer again, without trying to restore the TWRP backup and my phone is back to stock and getting a signal. Thanks again to the both of you.
Click to expand...
Click to collapse
What I suggested worked without the TWRP backup? Or another way?
your best bet is to somehow find a way to install the stock rom through TWRP then you can install the KDZ. Cause I had the same issue as you, i have a Verizon V20 with the US996 rom and it wouldnt let me flash the verizon KDZ until I installed NotSoStock rom thats based on the Stock Verizon Rom
EDIT: Just saw you got back to Stock. Disregard this lol
KedarWolf said:
What I suggested worked without the TWRP backup? Or another way?
Click to expand...
Click to collapse
I didn't use the TWRP backup at all in the end. Your method didn't fully install, but it made the phone see itself as an H915 again which allowed uppercut/LGUP to install the KDZ so it was a big help
Congrats! on the recovery, this is a good reference thread for anyone trying to recover from a bad root, and needs to get back to stock.
Splinter77 said:
The good news is that it recognized my phone as H915, but unfortunately half way through the setup it through a weird error. Part of me is thinking of restoring my twrp backup and trying uppercut again. I'm hoping that will get the program to see my phone correctly.
EDIT: I tried the KDZ installer again, without trying to restore the TWRP backup and my phone is back to stock and getting a signal. Thanks again to the both of you.
Click to expand...
Click to collapse
did you use the upgrade option in the lg up tool of refurbish
If you guys still have issues with service disabled i was able to fix my device by using the hidden menu options on this thread and selected (device reset R&D only) once i selected this option i finaly recived service
mmjs14 said:
If you guys still have issues with service disabled i was able to fix my device by using the hidden menu options on this thread and selected (device reset R&D only) once i selected this option i finaly recived service
Click to expand...
Click to collapse
@mmjs 14
Are you saying you have a rooted 915 with everything working?
guess not lol
I am having the same issue with an h910, but the service only works sometimes. Many times it is searching (and draining the battery in the process), but sometimes it will get service and be OK. Quite frustrating, and no way to revert because no kdz available. Anyone else with h910 having this problem?
Hi,
I'm not sure if I'm off topic here or not. I have an LG V20 H910-10c (Nougat 7.0) and I am having an issue with a Service not working after using DirtySanta to Root my phone and I am praying that someone can help me out with. I have already tried a Factory Wipe/Reset and Wipe Dalvik/ART & Cache and have Formatted Data to remove Encryption, etc..
Timeline: The phone worked fine in all aspects before Rooting it.
After Rooting it, I had this issue.
I then tried a Factory Reset and got stuck in a TWRP Bootloop.
I fixed the Bootloop issue with a Reset (Yes then Yes).
The issue is still there.
ISSUE: When I boot into Android, I get the following message;
"LGSmartcardService has stopped"
.....and I cannot use my External SD Card (TWRP sees it fine, I Flashed SuperSU from it).
I have Googled my brains out and simply cannot find any suggestions, except to perform a Factory Reset, which I did and that's what put me into the Bootloop and I reset the way you said and now it boots up okay, except that error message is still there.
I have not put any apps on the phone or anything. It's factory fresh (except for Rooting it).
I hope I'm not violating any rules by posting this, but the page I used to Root it has a REAL SMALL downloadable file called "V20-Root.zip" that contains everything, including the Batch files with the steps that they perform in them. I did NOT use the ROM, as that's ONLY for Sprint users and my phone is an AT&T model (Unlocked and my Carrier is MetroPCS). But I put it here, just in case someone wishes to bless me by taking a look and seeing if there's something to note. I am not a coder by any means. I do understand some basics, but I couldn't see anything that would cause this sort of problem. I did NOT install the ROM listed, because it's for Sprint users ONLY and I have an AT&T (Unlocked, using MetroPCS) H910. Here's the link to the page:
https://tinyurl.com/yacdendm
I really need my Ext SD Card to be seen! I use it extensively and it would be a real hindrance not to have it! Plus this is my ONLY phone (no landline) and I am disabled and must run everything, including my home network and laptop, etc. from it and I need its space for things I have to have available on my phone to do things that I need to do, so any help would be appreciated GREATLY!
I do need to be Rooted, so going back to factory with whatever Mpdel # ROM an LG Tool sees me as might make me unable to Root again.
Please Help Me and Thank You!
Dave
Hi all, as the title says, my efs folder is inaccessible. Firstly let me explain. I bought a phone, it had the Paul pizz rom in it and I didn't like it. So I flashed the resurrection remix rom. It didn't have all the bells n whistles I wanted, so I tried the official res remix rom. Somehow I ended up with an efs problem. I ended up with an efs invalid argument error and from what I read, I did the whole adb efs fix. The error was gone. I ended up flashing a repair firmware back to bog5 and started from scratch. I worked my way back up to installing the modest rom and it works 99% flawlessly and I am happy enough to keep it. Here is the catch, I used kingo root and have ended up with a bad keyboard lag that's driving me nuts. It is unknown to me if the kingoroot caused the efs corruption or if it was just a bad flash going from one rom to another. I have tried several root browsers, made sure they all had root privileges, and no matter what, I can NOT get access to what's hidden in my efs folder. They always say it's empty. Now, here is the kicker, I got another note 4 for my son. Downgraded from 6.01 to 5.01 bog5, then up to 5.11 and flashed the modest rom on his. Instantly his phone has access to the efs folder. My note 4 works, can make calls, text etc. Imei is shown in settings, all info shows in settings as normal except one thing, on my phone it says configuration version not available whereas on my sons phone it gives a configuration version. I just can't figure out how to gain access to the efs folder to try to fix this extremely annoying lag. I DID make a complete backup of my system from when it had the Paul pizz rom, so the efs partitions should be intact there but I don't know if that would help or even where to start. Can someone please help?
Well, I just fixed my phone and thought I would share what happened. It seems that the guy that loaded the paulpizz rom on the phone before I bought it used a different version of twrp. He used a version for n910f, whereas when I began my rom search, I used one for a n910v because thats what the phone is. I was having a hard time with it so I reverted to stock, rooted, installed verizon twrp, and bam! No efs access. The difference in recovery programs is what screwed me up in the first place. I figured it out when I tried to restore his rom backup I made. The efs files were not working when it restored. I remembered what version of rom it was, and tried a twrp for 910f, and voila! So, now I have all functions working as blazing speeds, can actually access the efs folder, and no more damned lag! Big thumbs up button to me!