Hi,
I have an LG V20 H910-10c (Nougat 7.0) and I am having an issue that I am praying 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!
Please Help Me and Thank You!
Dave
duplicate thread, original here
https://forum.xda-developers.com/v20/help/lgsmartcard-service-error-t3860491
thread closed
Related
I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.
not_su said:
I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.
Click to expand...
Click to collapse
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.
Rhymey said:
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Thanks - that's exactly what I've been trying to do. I haven't tried reflashing back to stock with Odin though. Hmmm...
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.
Click to expand...
Click to collapse
Bell, up here in the Great White North. I don't think locked bootloader is an issue - I was on the previous version of Danvdh's ROM, and everything was hunkydory. I just made the unfortunate decision to encrypt. Big mistake.
May try flashing back to stock. Nothing to lose, at this stage...
Thanks!
Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!
not_su said:
Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!
Click to expand...
Click to collapse
Good to hear. Should be able to flash to the rom once again no problem now that it's unencrypted!
Hello,
I have a MB525 that I purchased retail in the United States so it was never locked to any carrier. Currently I'm a T-Mobile customer and have no interest in changing that. I have to say I love this phone, mainly because it seems indestructible. Even years later the battery life is still good, but the stock 2.2.2 Froyo has become something of a problem because many of the Apps I would like to use have started requiring newer versions of Android.
I can't stay in the past forever, but I'm not quite ready to give up on this device so I started looking around at my options, and would you believe I found lots of other people who have this device and have worked very hard to produce updated Android OSes for it, and who have reported reasonably good success updating the device. I figured, Its already out of warranty, so I can't void a warranty I don't have. I also figured I'm a reasonably intelligent individual and have enough experience with Unix like operating systems that even if I get in trouble, I'll be able to ask the right questions to get out of trouble. Guess what point I have gotten to?
I started following the guide wikiDOTcyanogenmodDOTorg/w/Install_CM_for_jordan The Framaroot Gimli exploit worked great. I installed bootmenu 6.1 and Clockwork Mod Recovery. Fantastic. At this point, I was able to enter CMR and backup my mostly still factory ROM. If I understand correctly this is a nandroid backup. I copied that backup off of my SD Card to my PC. From this point I felt reasonably confident I could try things and in a worst case scenario restore to this backup.
Now I happen to have a stock ROM that seems to be a bit rare online, Blur_Version.34.4.806.MB525.Latam.en.01, so I figured at this point I'd do a service and create a backup using CWM after having done a factory reset. So I booted into the stock recovery, did a factory reset, restarted, and the OS was in a like new state. Perfect. Rebooted into CWM, and made a second backup of the factory reset state. I copied this off the SD Card to the PC. Now I figured I was ready for real fun.
I figured, I might as well put the most recent Android version I could find that people were reporting success with. This appeared to be @quarkx Kitkat build. The thread is almost a year old and has 500+ replies and so I guessed that most of the major kinks would have been worked out by now. I followed the directions on quarx2kDOTru and installed cm-11-20141015-NIGHTLY-mb52x.zip from Quarx2k.ru, and low and behold it worked. CM11 booted and everything looked great. WiFi worked. Gapps worked. Play store started installing my apps.
There was one small problem. The phone refused to connect to T-Mobile at all. So I did the reasonable thing. I searched and learned about base band switching, and consulted T-Mobile on what would be the correct APN settings. Occasionally it would connect to AT&T for emergency calling, but it never connected to T-Mobile no matter what I did. From my home I was normally getting excellent signal on the stock ROM, so I am reasonably certain that the actual signal in the area was not the problem, and that this had to be some kind of configuration or software issue. A wiser person probably would have gotten on the forum and asked for help, but wisdom be damned, I wanted to do it for myself.
So more research and at some point I thought, Well, I'll go back to the Stock ROM so the phone will be usable again, and I'll take another crack at CM11 again later. It was at this point that I realized that CMR had been replaced with Team Win Recovery Project. This recovery looked to be more feature rich and easier to use, so I accepted that. I backed up my CM11 install. then went to restore my original backup. Well you might have guessed by now that TWRP and CMR don't use exactly the same backup formats. I saw no obvious way to get back to my backup and couldn't find information that would allow reinstalling CMR. This was the first warning signal I foolishly ignored.
At this point I started looking around for slightly earlier builds of CM11 that might not have had the the problem connecting to T-Mobile. Here is where things get fuzzy about how things got into this state, since the work was spread over two days at this point. Somehow between all the flashing backing up and restoring, the device got to a state where the OS never actually finished could do here is yank the battery and reboot into TFRP.
At this point, attempting to restore would just result in the messages 'E: Unable to mount '/cache' and 'E: Unable to mount '/data' in the terminal. So After searching around I learned that I probably needed to format /cache and /data because somehow they were broken. Terminal commands, I can handle this. I start reading up and find the correct command and parameters for the format, and I type into the terminal inside TWRP and low any behold format can't be found. I start looking around the directories in my file system from inside TWRP and I've got a complete directoty structure, but no files in any directories other than on /sdcard. Well fuuuu.
Not sure what made me even try, but copying any file from my sdcard into /data somehow put /data into a state where a TWRP restore would work. So at this point I was able to restore the CM11 backup, and my phone now boots into CM11, 11-20141007-NIGHTLY-mb526. But.... the cellular network still doesn't work.
But now I am wiser and I am back to the point where a wiser person would have asked for help. So... Help?
Is 11-20141007-Nightly-mb526 the best rom an appropriate rom for my device? I'm guessing I missed something because other discussions on this forum mention newer builds, and also, my device is definitely a 525 not a 526.
Is my baseband version EPU93_U_00.60.03 right? The baseband selector allows me to pick from three T-Mobile settings: 3.4.2.-107-4, 3.4.2.-107-9, and 6.xx.0, none of which seems to allow me to connect to the cell network.
Thanks in advance for any assistance offered.
Sorry for the long potato.
Here is what I did to fix my problem.
I started with the original backup of my stock rom, and I used the unyaffs.exe from this thread: http://forum.xda-developers.com/showthread.php?t=1199416 to convert my CMR backup into individual files. I then went into those files, and found \system\etc\motorola\bp_nvm_default\ and pulled out the original radio firmware from my device. From there I used advice from several pages to create my own update.zip, copied it to my SD card and I booted into TWRP and installed the zip there. Reboot and Voila, It connected right at startup to T-Mobile with the normal speeds I get from my home.
Bonus, I attached my zip in case anyone else comes across this and needs it.
My Device has an FCC ID of IHDP56LC1 if that helps anyone match their hardware.
Hi,
I have an old G2 which had lineageOS on it, and I wanted to go completely google free and uninstall google play services and stuff, but it seemed my device wasn't rooted (by checking for # in a terminal). I'm completely new to rooting and flashing and everything. Basically I decided I was going to ignore the fact that my brother had already changed things on the phone and I was just going to try and follow a guide to root it and then put whatever ROM I wanted on. Apparently my phone was encrypted, and this needed to be changed before I could do anything so I tried to do a factory reset. When I did this, I ended up in TWRP, which is apparently installed and tried to do a factory reset in that. It prompted me to install Super User or something which seemed like an easy way to root so I said yes. The problem is, the phone never loads. I left it for a good 2 hours to do the factory reset, then it seemed it was not doing anything so I restarted and messed around more. The result is, it is just stuck looking like it's loading up (I assume that's called a bootloop).
So my question is how can I get this phone back into usable condition, I'm not fussed about finishing what I started necessarily, I just need a usable phone. There seems to be good news in that I can access TWRP (v2.8.6.1), which I guess would be useful if I knew how to use it.
Thanks for any help
EDIT/SOLVED: I managed to get it working by going into TWRP, wiping cache and dalvik, installing a new build of lineageos i had already downloaded, not installing superuser, wiping the cache and dalvik again, and rebooting system, and a fresh start of lineage finally loaded. Doubt that's relevant to many people but thought I'd share anyway.
brokemyG2 said:
Hi,
I have an old G2 which had lineageOS on it, and I wanted to go completely google free and uninstall google play services and stuff, but it seemed my device wasn't rooted (by checking for # in a terminal). I'm completely new to rooting and flashing and everything. Basically I decided I was going to ignore the fact that my brother had already changed things on the phone and I was just going to try and follow a guide to root it and then put whatever ROM I wanted on. Apparently my phone was encrypted, and this needed to be changed before I could do anything so I tried to do a factory reset. When I did this, I ended up in TWRP, which is apparently installed and tried to do a factory reset in that. It prompted me to install Super User or something which seemed like an easy way to root so I said yes. The problem is, the phone never loads. I left it for a good 2 hours to do the factory reset, then it seemed it was not doing anything so I restarted and messed around more. The result is, it is just stuck looking like it's loading up (I assume that's called a bootloop).
So my question is how can I get this phone back into usable condition, I'm not fussed about finishing what I started necessarily, I just need a usable phone. There seems to be good news in that I can access TWRP (v2.8.6.1), which I guess would be useful if I knew how to use it.
Thanks for any help
Click to expand...
Click to collapse
you can access the twrp with the power off button and volume less when the lg logo looses the power on and you press again:fingers-crossed:
---------- Post added at 10:04 AM ---------- Previous post was at 10:02 AM ----------
brokemyG2 said:
Hi,
I have an old G2 which had lineageOS on it, and I wanted to go completely google free and uninstall google play services and stuff, but it seemed my device wasn't rooted (by checking for # in a terminal). I'm completely new to rooting and flashing and everything. Basically I decided I was going to ignore the fact that my brother had already changed things on the phone and I was just going to try and follow a guide to root it and then put whatever ROM I wanted on. Apparently my phone was encrypted, and this needed to be changed before I could do anything so I tried to do a factory reset. When I did this, I ended up in TWRP, which is apparently installed and tried to do a factory reset in that. It prompted me to install Super User or something which seemed like an easy way to root so I said yes. The problem is, the phone never loads. I left it for a good 2 hours to do the factory reset, then it seemed it was not doing anything so I restarted and messed around more. The result is, it is just stuck looking like it's loading up (I assume that's called a bootloop).
So my question is how can I get this phone back into usable condition, I'm not fussed about finishing what I started necessarily, I just need a usable phone. There seems to be good news in that I can access TWRP (v2.8.6.1), which I guess would be useful if I knew how to use it.
Thanks for any help
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=HL1wOPe5pLc
Original thread "https://forums.oneplus.net/threads/root-op5-twrp-dissaster.742632/"
Video of current STATUS "https://youtu.be/GBWbid59f1E"
Current state of my problem -- STUCK in a screen at Drive Screen "an empty modal opens" Also looking for -- OnePlus 5 OxygenOS 4.5.15 rom --
OP5 EUROPE (if this helps to know what kind of phone I got, I know there are some differences in countries, dont know if it happens with OP specifically)
Currently trying to fix this using:
twrp-3.2.1-0
OnePlus5 Oxygen 4.5.15
-----------------------------------------------------------------------------------------------------------------
After reading plenty of other Threads with similar problems, I am clueless of whatelse to do but to exhibit how I disgraced my phone in hopes for somebody to help me.
I know I am 100% guilty of all that happened but I still somehow hope to get help.
Now the proper what happened.
After the purchase of some apps that seemed to encourage me to root my phone from Android Store, to get more features, I decided to give it a go.
So I got myself:
twrp-3.1.1-0
The Rom from Cyanogen
SuperSu v2.79-20
Granted myself access to booting and usb debugging after becoming a developer (granted by the university of tap your phone screen like a monkey smashing buttons, I figure this is even an inside joke from actual Devs)
I followed a tutorial that said next thing was installing twrp and stuffing my rom and my super su in my phone after rooting it, here is when things turn dark after installing the rom.
I saw my data was wiped and thought I had erased its memory, and instead of just putting back the things that I had to install I clicked on another tutorial of a had that had a similar problem (I can provide links later if requested).
In this tutorial the person, said that I should go to Advanced Settings -- WIPE and try and reformat my SYSTEM and my DATA, (heres when I wish my future-self would have come and stopped me because after this it all spiraled into madness)
After this happened my phone said I had no OS, so I didnt know what to do, I had no idea, I tried recovery mode but there was nothing to recover.. , I tried plenty of things really. reformating, downloading more ROMS , when I tried to install any of this Roms a new surprise awaited for me, my phone didnt know it was a OnePlus5 anymore it decided asume a misterious identity now he was " " instead.
I googled this, and a guy had a work around in wich I had to go into the rom and into the META-INF --COM -- google -- android -- updater-script
and inside this very archive delete the script that validated wich phone I had, this solution wouldnt work with any rom I had because they all said "updating the img was unsuccesful" at this point I was asking myself only one thing "WHAT IMAGE?!?!" a second ago there was no OS at all and now there was an image to update?.
I kept trying roms until one worked the stable official version, now I managed to install the rom rebooted, to find that the OS seems to have been installed, but.. when I introduce my pin things begin guetting funny again...
My SIM doesnt seem to be recognized its called "Slot 2" and when I enter the pin it and "SWIPE UP" as the phone suggests it gets stuck at a panel called "Drive".
I am guessing I am having an issue with the drivers but this is only a guess, I really have no Idea how to fix this, I tried to look up if somebody else was strugging with a FREEZE at DRIVE.
but it seems that nobody else fell into the spiral of foolishness I did, please help me find a way into a solution.
When I try to recover from the phone and install from "internal storage" doesnt allows me as there was no such thing.
use codeworkx twrp
Use a Keurig and just breathe
try flashing a twrp recovery. then boot to recovery. then push via adb a recent oneplus rom. then install the rom. then reboot to system and see if it is working.
Yes this post is correctly dated. I've had this device a LOOOONNNGGG time.
The device has been rooted since shortly after I bought it new years ago. I've had very few problems since... which is why it's never been replaced.
I believe I have the stock ROM, sorry it's been a while.
When I start the device it gets stuck at the splash screen with the sprint logo.
I can get the device to "download mode" but I don't know what to do once there and I'm not sure I can do anything from here.
I can get the device to "android system recovery."
I know I installed TWRP when I rooted and installed the rooted ROM but when I boot to recovery it doesn't go there.
I've wiped the "cache partition" but the problem remained. I'm not sure what else to do from here and still be able to salvage data.
I'm trying to salvage the data on the internal storage. I'm pretty sure I could successfully "wipe data/ factory reset" and get it to "function" again but that's not the priority. I'm going to replace it regardless of success or failure. Data recovery is the priority here. (pictures and videos of my young children as well as less important stuff like contacts.)
I have an old laptop with an old version of ubuntu I can use or a newer one with windows 7 to work with. I mention this in case it makes this easier to help?
Thank you very much if you try to take a stab at this or refer someone that might!
Update:
So I managed to install TWRP via Odin.
I booted to this recovery and my data partition appears to be empty?
When I try to back up I get the error message "unable to mount '/data'"
I tried doing a wipe, not one of the fancy extra options ones just the regular wipe and it failed.
Any guidance will be extremely appreciated.
Edit:
So I've come to the conclusion that the data isn't accessible because of encryption and my pass code. Is there any way to enter it via recovery and access this info?
Is anybody out there?
Edit 2:
I hope this helps someone someday. I haven't solved the problem but I think I'm making progress.
First I had an old version of TWRP. I installed the latest for my device and tried backing up again. I'm not sure but I think it's working. TWRP dosen't seem to need my password for the backup. I imagine I'll just need it to access the data later.
Edit 3:
No sooner did I save the last edit and my backup failed.
Process ended with error : 255