Hey,
I'm pretty new here, so don't hate on my lack of knowledge^^
Maybe I'm even in the wrong sub-forum
(I think there was a sub-forum dedicated to moto x, but this isn't a device-specific issue, so here should be fine - no?)
Got the following problem:
My moto x (2nd gen) is stuck in a loop. I get to the logo-screen, then it goes to "Encryption unsuccessful" and when I click "Reset", it restarts and fails upon trying to reset.
How I got here:
1) A while ago I wanted to encrypt the phone for the lulz (using its' own encryption-tool)
Followed the simple steps, as in having it charged up, but the encryption did not go through.
Don't remember having it to reset at first, it just booted, even though it had bugs after that:
-whenever I charged it, I had problems turning it back on after charging, had to turn off and back on for it to actually work.
-those notifications on top which one can normally open via sliding down, that sliding down did not work after that.
Eventually I did a hard-reset and it fixed the sliding-problem.
Charging also worked fine at first until it did not.
2) I ended up stuck in a boot-loop that went to the logo-screen back and forth (got to logo-screen, restarted, got to logo-screen, restarted, ...)
Tried to soft-/hard-reset using the VOL- and POWER combo.
The hard-reset itself threw some errors at me, something like "can't delete [whatever]".
Still, after a few tries it eventually went past the logo-screen to the encryption-step.
After another few failed resets and emptied cache via recovery-screen, it somehow ignored the encryption-step and turned on the phone (was a fresh version).
3) Worked fine for 1 whole evening, no crashes/glitches/anything until I had to charge it up.
Then it was back to the broken state.
Note: during 2) I tried to boot with a custom recovery-mode(TWRP), but couldn't get it running.
Then I tried to flash it, but anything I tried to install failed.
I had my suspicions, but eventually I got it straightened out: my phone isn't rooted, and the bootloader is locked.
I did get the code to root it via some steps and the motorola service, but the code did not work as it wanted me to unlock the phone first.
From what I've read, to do that I need to get into the settings and unlock/root it...
Funny thing: I can not turn on the phone to get into the settings.
So - anyone got ideas?
Warranty is gone since apparently my tinkering with the locked bootloader and unrooted phone still was visible and they voided the warranty.
Not sure I broke much/anything with that, though, since it DID work at some point after that (even if it was for a few hours before needing recharging)
Therefore I'm open to any suggestions since the alternative stop would be throwing it into the bin^^
Can I unlock the bootloader without having a working system?
Can I root it somehow without having to get into settings (since I can not turn it on in the first place)?
I did a fair share of reading, but most times the guides just assumed that I already rooted it, or forwarded me to a guide where it said "go into settings and spam the build to get advanced options, then simply root/unlock that damn thing". Tried to find a way to unlock/root it without being able to turn it on, but did not get lucky with the search.
If I could unlock and root it, I probably could go from there. Guides are pretty specific and seem to work for most.
Also, I would try the original android version first before searching for any custom systems.
(that is the smartest way to do, right? since I'm just a user and dont plan on doing more hacking/breaking)
Hope all that above wasn't too much to read
Thx for any advice in advance.
Edit:
Well, after what feels like 50 restarts it miraculously did not send me to the "Encryption unsuccessful" but instead booted like it should (as a fresh version, though - so had to backup).
Now I've turned on the thing in the settings so next time it breaks, which I expect to happen by tomorrow, I can flash that sucker.
Still - anyone knows how to enable all that stuff one normally does via settings some way that does not involve successfully booting it?
I mean, there should be a way to root/unlock it without having to turn it on first, right?
Edit2:
As expected, the flashing part was pretty easy, so I'm now sitting with a fresh android 6.0.
Two days in and it's still working fine, haven't had any complications (except battery draining faster then at the very beginning, but I think that's due to it hanging too much on the usb-cable during all those sessions of me trying to fix it - and generally I've had it charge over night a few times to often)
Still would appreciate any advice on how to unlock developer mode and usb-debugging within the bootloader or recovery-mode.
Related
I can laugh about it now, but...
First let me say that I am new to rooting, but not to toys Here's my train wreck comedy of errors, maybe someone can tell me how all of this was even possible?
I started by rooting using Doomlord's rooting script. That went super-easy. Then I decided I wanted to do a nand backup, so following the instructions here I went and installed ROM manager and used it to flash Clockwork Recovery Mod. CWR wouldn't load when I tried to get to recovery mode to do my backup so I asked around and I discovered that my Atrix was not unlocked. It all goes downhill from there.
Following all the unlocking instructions in the Pudding sticky, I used RSDLite, and the IHOP sbf (since I'm on Bell Canada). Well that looked like it was working, but when RSD showed me at 100% reboot after it was all done, the program stopped showing any further status to say it was complete. I've seen this happen a lot before doing other smartphone activities, and I knew it wasn't going to proceed further. So after giving it another 10 minutes just in case, I unplugged from my PC. And yes, of course, now RSD protests that it wasn't done. Typical. I shut down my phone and rebooted. Time for the Fastboot stage.
(at this point I want to point out that BriefMobile's guide is wrong. you do NOT skip to instruction #13 if you are on gingerbread because that does not work. I ran into a couple of other people who reported the same problem with his guide)
(also at this point, I want to clarify that all my USB drivers needed for this to work were installed, and many of the links provided by Pudding sticky are out of date and don't work. or both so I had to get software from other sources and cross my fingers)
So, now onto the fast boot. But wait! Briefmobile guide (linked as the guide to use in Pudding sticky) never informed me I need to put my sim card back in now. or not. I decided since NO instruction is being given either way, I left it out. Fastboot works fine until I enter the "fastboot oem unlock ###" part. Then the cmd window showed zero progress. Once again I wait 20 minutes this time. Nothing. Finally I sigh "here we go again" and unplug, knowing I am now going to be soft bricked, and I was right. I am now showing "unlocked" at bootup, but I am also now stuck in the logo boot-loop. Tried to reflash, that didn't work. Tried to fastboot boot again, that didn't work.
Finally I caved in and did a factory reset/wipe. My phone is now restored to 2.3.6 but I am now also rooted and unlocked like I wanted to be when I started all of this.
The problem is that none of this went anything nearly as smooth as others claimed it would be. Every step of the way caused errors. RSD didnt work properly in the end, and neither did the fastboot. The instructions for Bell Atrix 2.3.6 are all extremely outdated and/or irrelevant in some cases. Before all this happened I was considering flashing custom ROMS. Now I am absolutely terrified to do so, and would rather just use TiBU to freeze some bloatware and leave it at that. How did this all go so terribly wrong? Are days like this normal in the custom ROM scene?
no ideas anyone? I'm still baffled how my phone went through the train wreck that happened in the above post but still manages to be unlocked and rooted after the factory reset and 2.3.6 re-installed OTA. I still have root, and the phone is still unlocked.
omnius1 said:
Fastboot works fine until I enter the "fastboot oem unlock ###" part. Then the cmd window showed zero progress. Once again I wait 20 minutes this time. Nothing. Finally I sigh "here we go again" and unplug, knowing I am now going to be soft bricked, and I was right. I am now showing "unlocked" at bootup, but I am also now stuck in the logo boot-loop. Tried to reflash, that didn't work. Tried to fastboot boot again, that didn't work.
Finally I caved in and did a factory reset/wipe. My phone is now restored to 2.3.6 but I am now also rooted and unlocked like I wanted to be when I started all of this.
The problem is that none of this went anything nearly as smooth as others claimed it would be. Every step of the way caused errors. RSD didnt work properly in the end, and neither did the fastboot.
Click to expand...
Click to collapse
Yep, sounds a little like the night I had when I unlocked the bootloader. If it helps, I've done a little bit of rom flashing since and have had exactly zero problems there. (I'm not a new-rom-every-week kind of gal, just wanted something more functional than stock.)
So that SBF was known to cause a soft-brick; RSD Lite would predictably choke on itself and your phone would display "failed to boot" with a bunch of options. You enter the fastboot oem unlock command and keep going. My fastboot procedure went as advertised, but upon reboot it did stick for ~15 minutes on the startup screen and I had to do a battery pull. After that, up it came and everything was peachy.
Did you pull the battery and attempt another reboot before doing the factory reset? Just curious.
Yeah, second battery pull was because both the phone and the PC cmd window became non responsive after I executed the final stage of the OEM unlock procedure.
The phone went into bootloop. Wouldn't reboot. Had to hard factory reset with the 3 finger salute
Huh. Well, unlocking the bootloader also causes a factory reset, so in this case your end outcome was the same. Sorry it was such a pain in the meantime.
Seriously, though, that's the hardest part. Installing CWM recovery and other roms is a piece of cake, just do plenty of reading before changing anything.
well looks like I got all the final kinks worked out. I froze all of my bloatware with TiBU including Motoblur Launcher and I'm now running my phone using Launcher 7. Everything's pretty zippy now and I think I may have just extended my phone as a keeper for the rest of this year
Ok, so I have a serious problem... My phone is locked and when I touch the text bar to enter the password, no keyboard comes up. Important information:
- I just upgraded to jelly bean (the official one that came out today)
- as far as I can tell, everything is working fine, i just can't unlock it
- when I touch the text bar, it makes a noise, but no keyboard comes up
- was working fine immediately after the upgrade
- I got done fixing some settings and locked the screen
- this may have something to do with changing the default keyboard to Google Keyboard (it was acting a little funny immidiately after, like it was crashing)
- I have Android Lost installed, the unlock function isn't working, but others do work
- phone is encrypted
Unless someone has some ideas for me within the next couple hours, I'm going to wipe the phone. Obviously, I would prefer to not do that.
==========================
EDIT:
I've managed to use Android Lost to make some backups of some stuff, but I'm still trying to figure out how to unlock the screen. I've found that I'm able to install apps remotely from google play if that gives gives anyone some ideas.
=============================
EDIT2:
I had another idea. If this is a problem with the keyboard, is there a way for me to change it remotely? Can I install another one via the store?
Alright... I gave up on trying to get passed the lock screen and tried doing a factory reset. I was afraid of the super brick issue, so instead of doing a wipe in recovery mode, I used Kies to reflash it. However, that did nothing. The phone started back up and acted like nothing happened. It asked me for the same password, then got to the lock screen and had the same keyboard issue.
I've tried various roms, but nothing seems to wipe the encrypted information properly. At some point, I got it to forget the password, but it still thinks that one exists. I even rooted it and tried shostock3, but when it boots, it asks for a password. The old password doesn't work, so I can't get passed it. I tried entering the "wrong" password many times and it said it would wipe the phone, but it just restarted to the SAMSUNG boot screen and just sat there. I pulled the battery after half an hour...
I should note that stock gingerbread seems to work fine...
Does anyone have any ideas on how to wipe the encrypted data?
If you can push apps to it, try pushing an app like no lock or something.
Short answer: No.
It is probable that encryption information is stored in the efs (encrypted file system) folder. That's where the imei and other critical stuff is stored. I don't believe anyone who posts here in the I777 forum really has a grasp on how phone encryption works though. I've only seen one other person post here who had an issue with an encrypted phone, and he was unable to solve his problem as far as I know.
If you have a proper backup of the efs partition from before the phone was encrypted, it is possible that you could solve the problem by restoring that partition. But I'm not even sure you could write to that section of the phone memory with adb with the phone in it's current state. Edit: if you can boot into stock gingerbread normally, then you can restore an efs backup, if you have one.
I'm guessing you could send it to Samsung and they could fix it for you probably.
I finally got it working. I'm not sure what combination of things did it, but I had to restore it to stock jelly bean (via kies) to get it to wipe the encryption. I guess the stock rom knows how to properly wipe it when you keep entering the wrong password. After I got it all cleaned up, I put shostock3 back on. When the battery charges back up, I'm going to try encrypting it again (in shostock).
However, now I found another issue (may or may not be a real problem). I wanted to check if the phone was still unlocked, so I dialed *#SIMLOCK# and it says "Connection problem or invalid MMI code."
Tada!
Creepy, my good friend, would be referring to me and as you know SCIU I didn't ever get it to unlock the phone. Oddly enough a stock ICS rom (my mom now has my phone right up the road so I may try this to see if it will work and then go back to ShoStock3) works fine. I have nothing hidden from the phone storage, everything shows up, it is actually unlocked and rooted though not a custom bios err firmware/ROM because when that is put on there the encryption issues come back and the password is asked for. If the correct password is entered (and my KEYBOARD comes up but I didn't change it from the Android/Samsung one) it proceeds to enter whatever it is supposed to (my guess is the POST area like on a computer when it is entering Windows/Linux, etc.) but the screen stays black (ShoStock logo doesn't even appear if I remember correctly or it does show then goes to black loading screen with the Samsung logo and that is it, perm stuck). However I did try flashing back to Gingerbread ROMs and ICS ROMs though not through official KIES.
SCIU I may have to give this a try if my mom don't mind it and see if that helps fix the problem. Thanks for starting this thread. I am sorry I didn't respond to the PM you sent me (my LGOG, Triple OG, OG, TRIPLE OG, Optimus G AT&T Phone has screen cracked twice and is unresponsive on two different phones so I sent that in to warranty repair [rapid heating and cooling issues]) and haven't been on XDA for a week. If there is anything else you need to ask or bounce ideas off of me then I am all for it.
As far as encryption goes, the process works the same as any other encryption algorithms used (MD5/HASH/SHA-!, etc.) using a basic replica of most file systems although mobile storage tends to work a tad differently. Unfortunately, the freezer trick, brute force, nor any other cracking methods I was able to try at home worked to get it to open up. I tried getting into the EFS area of the phone but never could get to the directory or have it display.
Again thanks SCIU and as I stated I may give this a try if my mom don't care.
Eagle
i've the same problem here but i cann't use kies when my phone is locked .... so what can i do??
rawan-omer said:
i've the same problem here but i cann't use kies when my phone is locked .... so what can i do??
Click to expand...
Click to collapse
You can get the full stock jelly bean Odin flashable tar in the Download Repository. See link in my signature. According to sciguy125, flashing stock jb and then inputting repeatedly the wrong password will clear it. I'm not sure how many times it takes, 5 or 10 I think. I've never worked with an encrypted phone. I'm just repeating what I have read others say. I've seen the above posted by at least one other person. You should be able to flash the stock firmware using Odin. The one you want is I777UCMD8
my phone screen is locked (with word password) , Huawei, and the keyboard doesnt show up when i click the box? tried reseting it, cant go to settings whatsoever! i didnt damage my phone in any way either. need help asap!!
moselyy said:
my phone screen is locked (with word password) , Huawei, and the keyboard doesnt show up when i click the box? tried reseting it, cant go to settings whatsoever! i didnt damage my phone in any way either. need help asap!!
Click to expand...
Click to collapse
Friend, this is the forum for the S2 (Samsung), so you won't find anything about Huawei devices here - best to ask your question in the forum for your device.
That being said if you are rooted and have a custom recovery, simply power the device off and boot into recovery and perform a factory reset from there. If that doesn't work do a full wipe (this means wiping /system), then re-flash the ROM/gapps.
me too!!! do you have some tips for me?? i almost fainted when i knew that the keyboard isnt working.... i do have a lot of important files in my phone.
Easy, you fools! JUST KIDDING lol Connect an external keyboard. Restart the phone with the keyboard plugged in and you'll have one chance to input the pass every time you restart. Good luck, bosses!
my phone screen is locked (with word password) , SAMSUNG GALAXY TAB 3V, and the keyboard doesnt show up when i click the box? tried reseting it, cant go to settings whatsoever! i didnt damage my phone in any way either. need help asap!
My sumsang keyboard has stopped I cannot do nothing because is secure by password can you help please
I got the same problem but everything on my phone is fine except it doesn't let me enter the password I dnt wanna factory reset it cause I got important pictures in it any suggestions on how to get my keyboard working.
Solution that worked for me
Hello all,
I usually don't post things around, but something told me to do this, since I don't see any threads talking about this solution.
My solution was the following:
Went to google play store on my computer via chrome. Logged in to the user attached to my play store and re-installed all keyboard apps I have.
That worked beautifully and hope this helps other people!!
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
anticlotto_ said:
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
Click to expand...
Click to collapse
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
CROSSFREEZE said:
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
Click to expand...
Click to collapse
Thank you for your reply! I have tried hard resetting multiple times, but I had removed some bloatware apps (I will quarantine them next time instead because I don't wanna go through this ever again) and I have tried the kdz method to only be stuck at 15% every time when I followed instructions to the pixel. I have tried to do it on windows 7 and windows 8. I have also tried the fastboot method by lelus, and that manages to "work" but I am still stuck at the tmobile boot screen afterwards. I have gotten the hang of the process of getting into the fastboot, but what do I do from there? I chose to flash ics xloader and uboot, but the process goes by so fast, I'm not even sure it is doing anything. The LG Tool has really gotten me nowhere, it just gives me a lovely error and then cannot continue the upgrade recovery process.
It said somewhere that after I flash through the fastboot I then have to try the kdz method, so I am going to do that now and see if it works. I don't know if there would be a difference between flashing a jb kdz or an ics kdz, but I will just do ics to be on the safe side.
I am quite happy to say that flashing the ics kdz was successful, and my phone is now up and running.
My p769BK is stuck on the LG screen. /: months
Sent from my LG-MS770 using xda app-developers app
im terrible with fastboot, i used the unlock the bootloader for noobs with an offline flash.
heres what i did to get out of bootloops....
alright, this is all from memory but the offline flash didnt work as well for me when stuck in weird bootloops.
Step one-going back to online flash---->
A---
the easiest way i found was to go to C:/windows/system32/drivers/ect/hosts
right click>open with notepad
there should be two lines at the bottom
"127.0.0.1 csmg.lgmobile.com
127.0.0.1 csmgdl.lgmobile.com"
i would cut them out and paste them in a text doc in the same folder for reference later...
but either way you should remove them from the hosts file and save
B----
Make sure your small server is closed! once you minimize it it should go down to your status bar (shttps)
Step two-LGMS---->
make sure you have LG mobile support installed or install it.
open lg mobile support
install needed drivers for your phone
power your phone off/remove the battery
put battery back in
connect it to your computer holding down the volume up button
S/W UPDATE mode should pop up, if it doesn't preform and hardreset and try again til it works (it will)
then in the top right corner there should be a button or two click them both until you see
"restore update" or Update restore or something to that effect
select that
and let it ride man
i got my phone ****ed many times and just had to keep redoing this until it worked. if your bootloader is truely unlocked you can probably go through all that again and get CM10 working, i did but im still working through kinks.....
GOOD LUCK feel free to ask any more Q's about this process if you run into any problems
So I have spent a lot of time running around trying to solve this. I think describing my problem will hopefully eliminate chasing dead ends.
The Problem:
My android OS is the one right before Lollipop. I have ALWAYS had the same PIN to get into my phone for years (7355608 The bomb code from Counter-Strike lol). Randomly (So it seemed) my Phone decided I didn't need a lock screen any more and it was gone. When i noticed this I went back into the options and set it back again. using the same PIN i always have. I try to get into my phone and the PIN does not work. I have found while digging around that I am not the only one with this issue. My phone is the Samsung Galaxy Note 3.
Added: The Update to Lollipop is waiting to be installed lol. Cant click on it since I cant get into my phone. But I dont think updating will help me at all anyways.
Additional Details:
I have a GMail account on my phone. I know the password. I had used USB Debugging Mode at one time and have the "developers options" opened. Doesn't seem to help because until you can unlock the PIN it wont connect to the PC to see or have any access to files or anything. I CAN NOT do a hard reset as there is valuable information to the point where i would pay to have this problem solved. My phone is NOT rooted or "unlocked" (unlocked as in stuck on one carrier)
What I Have Tried:
Android Device Manager - Doesn't nothing, when I use the LOCK phone it just tells me "You already have a PIN none was set"
AROMA - Starting on this but my phone is not rooted so I am not familiar with Android and every one that wrote a guide seems way to vague so I'm still researching this attempt on my on. AROMA is installed but apparently needs CWM (ClockworkMod) and installing that while locked out is where I currently am in this attempt.
Update: I don't understand what they mean by "Flashing" (I'm just going to throw it at a strobe light) and found out CWM is not needed if I can Flash it...
http://forum.xda-developers.com/showthread.php?t=2225695
XDA - XDA apparently has this method of using USB Debugging Mode and the Android Studio. But when I run the commands in the prompt it just tells it cant find the drive or something (I am thinking this is due to it not actually connecting the drive to the PC so it is being blocked from accessing what is needed to connect properly.
Repeated Failed attempts - This only works for Pattern Lock. Not PIN lock. FAILED.
I am willing to do anything to my phone to get my data back. Thanks.
Final Note: I just need all the data from the phone. If there is a way to get my data from the phone and then do a hard reset then I dont mind doing the reset. My goal is to get the irreplaceable information. Worst case I will buy a new phone and wait until this technology is old and easy to hack lol
http://forum.xda-developers.com/showthread.php?t=2244741&page=3
Well, I just got this phone this week. It was actually a gift in fact since I broke my last phone a week before this.
As soon as I got used to the new phone. I started playing with it's guts. I rooted it with Kingroot, since it has never failed me before. Installed Xposed Framework, and flashed the 5.1.1 stuff for it to run. I had to flash TWRP to flash the Xposed Framework stuff (for some reason I couldn't get the sideload to work). Got a few modules for it. Got all my usual apps such as Facebook, ES FM, Instagram, etc. Got a few games. Spent some hours playing the games. You know, all the stuff you do when you get a new phone.
Then, I decided it was time to switch from Kingroot to SuperSU, as I do with every phone I root with Kingroot (and there were a few). I did it the same way as I have before, using w0lfdroid's method (I can't post links yet). The Kingroot app didn't automatically uninstall, but SuperSU was working. So, I uninstalled Kingroot manually with ES FM. That caused a lot of "unfortunately, com.kingroot.kinguser has stopped" dialogs that never stopped coming, and I decided a reboot might fix it.
I was wrong, the reboot did NOT fix it. It turns on, goes to the LG logo screen, goes to the Metro PCS screen, dims the background, [all of that within a minute and then] vibrates once, and then no sign of anything else. However, the phone does seem to be alive. When I plug it into USB the MTP starts working. It's also listed in adb's devices list. I can even use adb. I used adb to boot it into bootloader/fastboot, and it's even listed in fastboot's devices. It does still charge.
That damned Kingroot, I'll never use it again to shortcut through rooting. It has always worked, and I've been able to swap it with SuperSU everytime before this one. I just don't want to risk this happening again.
I'm lost on what I should do about this. What would you fella's do?
_____________________
I do have a warranty on it, but I've obviously voided that above. I could lock the bootloader back with fastboot (using "fastboot oem lock") so they don't see anything significant right away, but they could always dig in to see that I've done a lot of changing. Hell, all they would have to do is boot into recovery and see TWRP... xD
Well, I just locked it back ("fastboot oem lock" ) and I think my phone is actually coming back on, it's currently on the "Android is starting" screen optimizing app 12 of 151.
I'm just hoping the lock command doesn't reset my device like the unlock command obviously does... I guess I'll edit this with my results in like an hour when this is done (not literally an hour)!
EDIT 1: 10 minutes later, it seems to be stuck on "Starting apps." after it finished optimizing.
EDIT 2: 10 more minutes later, I'm pretty sure it was indeed frozen on "Starting apps.", so I took the battery out. I turned it back on only to see it still freezing on the Metro PCS screen... Well damn.
EDIT 3: Yet another 10 minutes later, still stuck on the Metro PCS screen...
EDIT 4: I no longer have USB debugging access, since I re locked the bootloader (which seems to have reset it, again). So now I also do not have access to fastboot. I think I screwed myself...
unbricking
@ goatitalone can help you unbrick your device. I still have the files if he is OK with it I can help you too or if he can write a tutorial on here that would be great. @ goatitalone?
I have same exact problem howisit fixed?
Magik1 said:
I have same exact problem howisit fixed?
Click to expand...
Click to collapse
do you still have adb? if you do i can send a twrp backup
its been listed kingroot will brick you, currently the oneclick is compatible with our devices. you should have done some searchign before tinkering with your device in my opinion, if youre smart enough to unlock your bootloader .. you should be smarter in researching root methods.
youll have to reflash your device, contact goitalone - as noone that he's helped will help you with getting those files.
as for it being an ms3302 device.. i havent seen that device under our series.
Use this to unbrick http://forum.xda-developers.com/android/development/stock-firmware-rom-unbrick-lg-k7-k330-t-t3432878