Related
Ok the web just glitched on me so this is the second time of me writing this novel and patience has grown very thin. First i would never be asking for this help if i didnt already do my 5 days of research and exhaust all solutions i can see. And since this is my second time writing this im sorry but im going to give the short version. I did the fatal mistake of lg style reset while i was rooted i know its a rookie mistake i thought i was completely unrooted and didnt double check it before i continued. i cant boot into recovery at all or if i can its just a black screen. when i boot normally it goes to the lg logo then to a black screen. i can access emergency mode however i cant get my pc ( running xp sp3 ) to recognize the device. I can get it to be recognized when i boot it normally to the black screen and even gain acces to root through adb, When in emergency i get nothing though and i have attempted recovery and flashing through adb, kdz, romtools, lgmdp and a few more randoms i could find in the forums ( i have done a lot of research ) when i do establish root though i cant seem to push or pull files, flash, mount or anything besides adb shell, the rest is filled with error: 0's and sbin/sh "whatever" not found, etc. since i can establish root it leads me to believe this can be fixed. THANK YOU in advance for any help you can throw my way and I'm sorry if this post is vague, poorly written ( like i said second time going through this ) or gets under your skin i know better that you veterans hate reading these posts and im only asking for help because now i am at my wits end. Thank you again
hey it would be nice if you could tell something about lg style reset and that rooted thing..... I don't have any info. about bricking the device like this.... ;-)
just wanted to know as a word of caution....
Sent from my LG-P500 using xda premium
I m not aware if lg p500/optimus one clockwork mod recovery will work on optimus v.
If recoveries of both phones are same you can follow http://forum.xda-developers.com/showthread.php?t=1318750 to install custom recovery of lg p500/optimus one from emergency mode.
fundoozzz said:
hey it would be nice if you could tell something about lg style reset and that rooted thing..... I don't have any info. about bricking the device like this.... ;-)
just wanted to know as a word of caution....
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Rooting is the process of essentially gaining Administrator rights to your phone ( So you can access files and gain privilages you wouldn't normally have ) Think of it like a computer and your signed in as a guest when you root your signed in as the Admin, Hope that helps. LG style reset is the factory reset of the phone from the recovery menu to restore the phone to its original state, Which is a huge no no while rooted or a custom recovery is installed.
mak.3736 said:
I m not aware if lg p500/optimus one clockwork mod recovery will work on optimus v.
If recoveries of both phones are same you can follow http://forum.xda-developers.com/showthread.php?t=1318750 to install custom recovery of lg p500/optimus one from emergency mode.
Click to expand...
Click to collapse
I attempted that and its a no go. The main problem being i can not get my phone to be recognized by the computer while it is emergency mode and i can not even select an image or anything. I booted it normally ( into the black screen i get after LG logo ) And i dont recieve a pop up with image and i recieve a error everytime i attempt to backup my nv its doesnt seem to be found, Nothing, but the device does get recognized at least.
AbattoirX said:
I attempted that and its a no go. The main problem being i can not get my phone to be recognized by the computer while it is emergency mode and i can not even select an image or anything. I booted it normally ( into the black screen i get after LG logo ) And i dont recieve a pop up with image and i recieve a error everytime i attempt to backup my nv its doesnt seem to be found, Nothing, but the device does get recognized at least.
Click to expand...
Click to collapse
Are you able to connect to phone from lgmdp when booted normally ( into the black screen you get after LG logo ).
If yes then
dont back up nv
no need the pop up window, press on "select image" in lgmdp and browse to recovery extracted folder for "image folder"
then press "start or download"
fix-black-screen-custom-recovery-custom-roms
I'd've posted it here on xda, too, but it's quite enough manainance dealing with it in one forum already.
the problem is that lg started shipping the optimus v with cheaper hitachi screens instead of the novatek screen it was released with. so the older custom recoveries and roms use a kernel that isn't configured to use the hitachi screen and you only get to see the backlight with no display.
edit:
mak.3736 said:
I m not aware if lg p500/optimus one clockwork mod recovery will work on optimus v.
If recoveries of both phones are same you can follow http://forum.xda-developers.com/showthread.php?t=1318750 to install custom recovery of lg p500/optimus one from emergency mode.
Click to expand...
Click to collapse
the p500 kernel is incompatible (different chipset.) so the recovery won't work even it the mtd map is the same.
bummer, as that's be a nice easy fix.
Mak Thank you for the progress i have made so far i did manage to get the phone connected through lgmpd as i have before however this was the first time when connected it went straight to emergency ready ( in the lgmpd screen ) I am going ahead to assume that is good i was never able to get it that far. The problem i face now when i press the "select image" button nothing happens, as long as the button is pushed down the word ready in the bottom left disappears and when released the word reappears, However i dont recieve the option to browse any menu for the image. Is there a specific folder i should have extracted to? I'll continue my research too if i find out the problem i wil post it immediately, Thank you again for your help i'm not there yet but definately making progress.
Squid, I knew about that topic too i remember reading it during my research, It must of slipped my mind before i even though about posting this. I'm Sorry ill be more careful about making these posts in the future
Also Squid since the chipsets are different i assume thats a no go, Would it still hurt to try? i'm running on hopes and dreams at the moment. Also when booted normally to my black screen i can obtain root access via adb leading me to believe if i can do that a fix is present somewhere
AbattoirX said:
...snip
Also Squid since the chipsets are different i assume thats a no go, Would it still hurt to try? i'm running on hopes and dreams at the moment. Also when booted normally to my black screen i can obtain root access via adb leading me to believe if i can do that a fix is present somewhere
Click to expand...
Click to collapse
yes, a no-go. when I flashed a p500 kernel to my v for experimental purposes, it wouldn't boot right for a day even after putting a working kernel back on it. it had to sit with the battery pulled for a few minutes between boots or it would just freeze on the lg logo.
if you follow the adb instructions to install a compatible recovery (currently, BobZhome IHO recovery is advised) in the thread I linked to, you should be fine.
AbattoirX said:
Mak Thank you for the progress i have made so far i did manage to get the phone connected through lgmpd as i have before however this was the first time when connected it went straight to emergency ready ( in the lgmpd screen ) I am going ahead to assume that is good i was never able to get it that far. The problem i face now when i press the "select image" button nothing happens, as long as the button is pushed down the word ready in the bottom left disappears and when released the word reappears, However i dont recieve the option to browse any menu for the image. Is there a specific folder i should have extracted to? I'll continue my research too if i find out the problem i wil post it immediately, Thank you again for your help i'm not there yet but definately making progress.
Click to expand...
Click to collapse
yes, as long as pressing the "select image" button ready in the bottom left disappears. But when you release button you should get a window poped up to select image folder.
Try again to connect in emergency mode and see.
AbattoirX said:
when i do establish root though i cant seem to push or pull files, flash, mount or anything besides adb shell, the rest is filled with error: 0's and sbin/sh "whatever" not found, etc.
Click to expand...
Click to collapse
I did follow those instructions previously ( 2 days ago i believe ) When i attempted that i was not able to push the needed files to my sd card unfortunately and i did try multiple times using Xionia recovery. I understand user error so I'll try again with a fresh mind just to be certain and get back to all of you.
AbattoirX said:
Rooting is the process of essentially gaining Administrator rights to your phone ( So you can access files and gain privilages you wouldn't normally have ) Think of it like a computer and your signed in as a guest when you root your signed in as the Admin, Hope that helps. LG style reset is the factory reset of the phone from the recovery menu to restore the phone to its original state, Which is a huge no no while rooted or a custom recovery is installed
Click to expand...
Click to collapse
I know what rooting is....infact I myself is on CM 6.5.8
what I didn't knew was that factory reset with custom recovery can brick our device..
but I feel this is not true as many people had done factory reset when they had problems after restoring nandroid backup....
I know a corrupted /system partition will cause the 'system/bin/sh not found' with adb if you're booting into the rom, I hadn't seen that booting into recovery.
if you have an older optimus v (2.2.1 froyo original, pv5 baseband) you can
Code:
adb reboot bootloader
to get to the bootloader and use fastboot to flash the recovery or even the whole system.
2.2.2 optimus v with pv7 firmware has the bootloader locked, so trying to reboot into the bootloader just tries to boot to the normal ROM.
My apologies Fundoozzz i was not insulting your intelligence just covering all basis, And from what i understand when you choose lg style reset from recovery it is the same as perform the factory reset from the settings menu which i guess your not suppose to. I by no means am not an expert on any of this obviously, I'm just simply relaying the information i have read on these and android forums as well as my personal experience.
Squid, I purchased this in the beginning of sept. and as i understand the revamped the Optimus in August?? So yes im running the later version and to double back on the posts I tried to push files again and attempted fastboot before still with the sbin/sh not found error....I am still hopeful that this is not a paper wieght however it very well could be thank you both again
have you tried booting into the blacked recovery before using adb?
(hold home+vol down while pressing power until lg logo goes black)
it sounds like your rom was corrupted (so adb is fairly useless there,) and recovery might be working but you just can't see it if you do have a newer OV.
to force reboot to recovery without the button-smashing,
adb reboot recovery
while you're booted normally.
then try adb again.
please cut/paste the errors you're getting with the commands you're using, here in this thread..
Well all be cheese and crackers, Thank you Squid it did the trick to actually push the image to my sd card here are the commands that I used....
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner>cd c:\android\platform-tools
C:\Android\platform-tools>reboot recovery
'reboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Android\platform-tools>adb shell
~ # reboot recovery
reboot recovery
C:\Android\platform-tools>adb push vm670nh_recovery.img /sdcard/
2608 KB/s (4200448 bytes in 1.572s)
C:\Android\platform-tools>
Now before i move further just to humor me all i need to do is push the flash_image and reboot to recovery and i should be good from there to flash a new rom. I ask only so i dont mess this up any worse than i have
if you're in the recovery, flash_image is already in the PATH.
Code:
adb shell
flash_image recovery /sdcard/vm670nh_recovery.img
exit
adb reboot recovery
then you should be ready to see your recovery.
format cache, data, and system.
install the rom.zip as usual.
THANK YOU VERY MUCH, How I wasn't able to obtain this I'm not too sure lack of knowledge or user errors possibly regardless I am now in CWM recovery and will format and flash my new rom. Any suggestions by the way? I was considering CM7 but i heard mixed reviews about it on the Optimus v. Oh well I'll do some research Thank you again Squid if i can repay this debt let me know, Lets face the facts in reality you just saved me over a hundred dollars and countless more headaches. Thank you again to everyone, much appreciated!
AbattoirX said:
THANK YOU VERY MUCH, How I wasn't able to obtain this I'm not too sure lack of knowledge or user errors possibly regardless I am now in CWM recovery and will format and flash my new rom. Any suggestions by the way? I was considering CM7 but i heard mixed reviews about it on the Optimus v. Oh well I'll do some research
Click to expand...
Click to collapse
I really enjoy the IHO cm7 flavors, all of them.
I advise giving one a whirl, froyo just doesn't compare to gingerbread for my personal use.
They use more battery than harmonia, but the features! the features!
Thank you again Squid if i can repay this debt let me know, Lets face the facts in reality you just saved me over a hundred dollars and countless more headaches. Thank you again to everyone, much appreciated!
Click to expand...
Click to collapse
if you're financially solvent, I have a donate button in the sidebar... I like to help people out, but my woman really appreciates it when I get more from helping than warm fuzzies.
the thanks are appreciated, though, and if your income is like mine, don't send any money
Well if a promise is worth anything in this day and age, when I am slightly more financially stable I'll send enough for a six pack your way or some flowers so your girl won't mind you helping us for a while longer Thanks again and I'll load up CM7 now
Well easy come and easy go back to a new LG screen. So after managing to get the recovery working i went to flash CM7 on the Optimus using information here http://androidforums.com/optimus-v-all-things-root/366620-cm7-installation-my-optimus-v.html Anyway I am now experiencing this problem, I get stuck back at the lg screen again. I did wipe the cache data system 3 times to be safe before flashing the rom and i only have access to emergency mode and this screen ( regular boot and recovery mode come up and end the exact same way ). I'll explain what i see step by step...
1. The black and silver LG Logo
2. A green Android guy next to a box with arrow coming out and these words come up on the screen. " with out the numbers of course "
(1) Android Recovery
(2) Do Not Pull Battery
(3) Formatting Data:...
(4) Formatting cache:...
(5) Factory Reset...
(6) Rebooting...
3. Then reboots back to the black and silver LG Logo screen.
4. Finally stops and freeze's up on the screen with a pinkish/reddish LG symbol with LG next to it and www.lgmobile.com written underneath it.
Question being is this some sort of recovery boot loop? And if it is what can be done about it? Furthermore many if not all files on the phone so far seem to be " read only " .... well i guess I'm ready for round two!
Had my Prime 2 days, got it rooted.
After ICS install and camera update it worked for a while. Then it rebooted and it's stuck in a bootloop. I can't even power it off.
Yes, I've used the reset pinhole.
I've rebooted into Asus recovery but all I get is the "dead droid" screen. I'm assuming it's because I don't have my SD card in.
Any suggestions?
I'm thinking that if I can get my hands on the stock ICS zip direct from Asus I might be able to run that.
I suspect, from this thread that the issue might be that the Launcher has gotten corrupted.
Update:
Ran the battery till the unit shut off and didn't reboot.
Charged the battery for 4+ hours, unplugged it and tried to boot up. Same story, bootloop.
ADB sees my Prime and can issue commands.
Any suggestions? I'm getting desperate here.
Edit again: I can pull a logcat, any suggestions what I'm looking for? I'm not sure what subset of Linux commands are in Android, can I do a kill -9 if I identify a rogue process?
I'm pretty sure top won't work, and a lot of my Linux knowledge is pretty rusty.
Same here
I'm stuck in boot. I rooted it from zedo's instructions (that guy is a whoot!). Afterwards I installed "VM Heap Tool"(by martino), restarted the tab from the VM app and it got stuck in the boot screen.
I'm stuck and don't know what to do. I don't really know codes, so I'm pretty much up a creek without a paddle.
Any help would be MUCH appreciated!
Bumble-Bee has solved this issue for you on IRC but I figured we should post the solution to *your* specific problem here for others. Hopefully it helps them if they run into a simular issue.
With a boot loop try shutting down the tablet by holding power for 30 seconds. If it doesn't shut down then hold power for 30 seconds and after it vibrates hold power and volume down. This should get you into the recovery process.
The first thing to do in trying to resolve this issue (and what solved it for Col_kernel) was to do a data wipe using the recovery menu. Directions on how to perform this can be found here . this will solve the majority of bootloop issues.
The second thing to try to do is to perform a recovery using a signed zip from Asus. the ICS 9.4.2.11.1 is the latest one as of this thread and can be downloaded at the link provided there. Download that and place it on a microsd card. Load the card into your prime and boot into recovery and perform a recovery.
after that, start asking for help
I tried both solutions suggested and they didn't work for me, however I modified the services.jar in systems\framework. Looks like it tries to recover and then goes to an android on his back with an exclamation mark. I can't get adb to recognize my device either. I'm assuming my only options are to send it back to Asus or wait til I can flash at this point?
I should have said that I have already done the reset. Also, I cannot install anything on the tablet, since I cannot even access it. My PC won't even recognize it.
Update: I just spoke with Asus support. They said that if all these options are exhausted, I should return the tablet. That's what I'm going to do today. [good thing I have all my apps backed up. #TiBu!]
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
wells79 said:
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
Click to expand...
Click to collapse
Odd. I had the same issues. I started rooting mine on my mac, then finally moved to my pc. It rooted flawlessly on my pc.
So, I don't know if it was the root with a corrupted file, or the VM Heap Tool that I activated in it that caused it to get stuck in bootloop. But... I didn't restart the tablet until after the VM Heap Tool. In other words, it could have done the same thing without the VM Heap, I just wouldn't have known it, because I didn't restart it right after the root.
Make sense?
I installed CM7 Alpha Final (SD card version) and was working on getting the interface back to how I had it on the previous version. I used CWM to install "transparent status bar icons.zip" from this thread...
http://forum.xda-developers.com/showthread.php?t=1471066
Upon installation I went to reboot and now I'm stuck on the CyanogenMod7 boot screen and looping endlessly.
If anyone has any idea how I can fix this, I'd really appreciate some help.
Thanks!
Retcon:
I just remembered that I did NOT have this installed on the previous version on CM7. On CM7 i had a standard theme dock, so I think I installed something that just wasn't compatible with CM7 at all. What do I do now?
Thanks.
Most likely that transparent icons xip was not built for cm7 and rather was built for stock firmware. They are not compatible. Reinstall cm7.
What method can I use to reinstall? Since I'm in a bootloop I can't get to CWM. Or is there some kind of "safe mode" I can boot into?
Sent from my T-Mobile G2 using xda premium
Turn the unit on, when you get to the n screen, hold the power button until it turns off. Repeat 8 times and you will be forced into CWM.
If you have adb installed on your pc, plug it in, turn it on and check devices. If you are listed, do an adb shell reboot recovery and that will put you into recovery instantly.
I tried the 8-boot method two different ways...
1. Pressed the power button and released. When I saw the N screen, I pressed again and held until the unit powered down.
2. Pressed and HELD the button through it powering on and not releasing until it shut back down again.
Does it matter which of the above ways I do it? I wasn't able to get it to work. Does it have to be exactly 8 times? I don't think I stopped short but I might've done it more than 8...
Regarding the ADB method, I went ahead and installed the SDK but I'm not seeing my devices in ADB DEVICES. Since this is a new computer, I think I just don't have the right drivers installed. I went to Indirect's root thread to get those drivers but his dropbox link is disabled due to high traffic. Is there somewhere else I could get the appropriate driver? And once I have the correct driver and can see my device in ADB DEVICES (I'm assuming I'll be able to see it even though I'm bootlooping the whole time?), what is the code/line to get it into recovery?
Thanks for your help thus far. I really appreciate someone taking the time the time to help me out.
Oh, and a correction to my original post - I used the internal root method, not SD.
I found a working link for the drivers.
http://www.mediafire.com/?w6y5ld1jeuh65i1
I installed them and I can access my tablet now. I can see my device and its responding to commands.
So all I need now is the command to get into CWM. I tried "adb reboot [bootloader:recovery]" which I saw in the cmd window, but it just gave me a standard reboot.
Thanks!
EDIT: I tried "adb reboot recovery" and that did it. I'm back in business! Thanks for the help, Know-Fear. Although in my n00bishness, step-by-step handholding would've been nice, your replies gave me enough for me to at least know what general direction to look in. I still couldn't get the 8-boot method to work, but maybe that's just a dexterity issue. The adb method worked perfectly once I stumbled my way to the command line.
Make sure when you reinstall you do a partition wipe.
Glad you got it working thus far. Hopefully no more problems will arise after the new install.
Hello.
I have been reading around on the forums and havent been able to find a suitable fix for my phone.
First of all- Im not a huge fan of updating apps and such due to not having the best success with compatibility after the updates. Also I am NOT a developer or anything, have never rooted my phone or flashed ROMs because I never really understood it and didnt want to brick my phone. That being said im not a idiot when it comes to technology either. I know how to use linux a decent amount tho i dont because I own a mac and havnt had a "x86" computer for sometime
Back in December I was having problems with my phone so I took it to Sprint and got a replacement. I dont usually use my phone for internet while im at home (because I use my computer) and overlooked the setting that updates apps over wifi.
So fast forward a few months- I went to Europe for the first time this winter for a ski vacation and when i connected to wifi over there, my phone just started updating everything and started making my phone act wierd. It would freeze up for a while after boot after entering my password and it would take 15-30 minutes to unfreeze. I got used to it working like that. Besides i was only using my phone for basic internet stuff and taking pictures. I wasnt making any phone calls or anything. The day before i came home I tried to connect to a wifi network and in the network settings under wifi it said "error" and then immediately shut off and rebooted. That was the last time my phone was usable. From then on it is just stuck in a continuous boot loop. I have to remove the battery to stop it. When it tries to boot it goes through the animation process to the "now" part of the "welcome to the now network" animation during boot. I have messed around with the safe mode and other boot options in the boot menu but nothing seems to work.
I DONT WANT to hard reset my phone yet because ALL MY PICs are on the Internal memory of the phone from my trip. I know now that this was a stupid idea to have them on the internal memory. My SD card was getting full and had like 7 gigs internally so i saved all my pic there. My phone was also encrypted with the pattern password (yes i enabled it).
Is there any way to get my pictures off the phone? I dont know what build version, kernel etc... or any of the other technical information is.... Please help!!!! thank you :crying:
help
Hello ,
I have Installed Custom ROM in my Photon 4g MB855 Here is What I installed using( *How to install Jelly beans 4.1.2 Custom on Motorola Photon 4g )
and After installation I stuck at Motorola M logo .
So I could not even go Back Because whenever I try to install any stock or SBF file in RSD I get this error ..
*Failed To Re Enimerate*
And I also tried to Erase my Recovery and Install A custom TWRP like another Recovery manager but i get this error in FastBoot.
Erasing Recovery FAILED <Remote 00180001>
Writing Recovery FAILED <Remote 00180002>
I've read somewhere that its because your device is not unlocked and I also tried to install Pudding Unlock via RSD but failed to re-enumerate ..
RSD show my device as *SE FLASH SUNFIRE* ..
NOTE: I had made a BACKUP before flashing the Custom Rom and Now When I go to Recovery and Restore I cant see the BackUp .. But When I attach that SD card and There is BackUp .. That BackUp (2.3.5) Consists ..It Consists Following FIles..
Data.img
System.img
Cache.img
I'm totally confused How to Unlock my Photon (If it is) Please Help me getting my Phone BACK!
Does anyone have any suggestions for me at all?????
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