Okay. So. After some trouble with houstonn's latest rom's lately (getting stuck on boot), I decided I'd give one more try for the 4/30 release. Clean wipe, flashed it, flashed minimal apps. Stuck on boot. WOOP WHO CARES?
This time was different - I couldn't access recovery. So I tried like 30 more times to access recovery. Couldn't do it. LGNPST back to the ICS stock bin (11c). Get my OTA update to 4.1.2, rooted with this method http://forum.xda-developers.com/showthread.php?t=2006946. After that, I tried to access recovery mode again. Couldn't do it. So, I was like "what the hell, maybe FreeGee will help." So I continued on to unlock the bootloader with FreeGee and with CWM. Installed quickboot and chose to restart to recovery. SAME THING. Black Screen after LG logo. Can't get into recovery.
Now I'm LGNPSTing back to stock to repeat process. Any ideas on what's going on?
Edit: Running into quite a few problems with LGNPST. Gets stuck at 85% and won't boot even after power cycle.
Edit 2: TeenyBin AltBin let me format my partitions and then the LGNPST worked. Got the OTA. Rooted again, used FreeGee, except this time with TWRP 2.5.0.0. Wouldn't reboot afterwards, so moved on to TeenyBin AltBin again. The phone booted up and everything runs fine. One thing to note: I had some wifi problems when I just TeenyBinAltBin'd and used a restore point for stock 4.1.2 which is why I was so adamant to LGNPST like normal. Still can't flash any of the newer ROMs of houstonn's, but I can others. On the good side, I still have a phone. Hopefully if anyone else has the issue, they can follow this and resolve it.
Related
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
nashdude said:
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
Click to expand...
Click to collapse
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
I ran into something similar when I tried installing CWM 6.x.x. I chickened out and decided to run CM10 from SD instead, and I'm so happy on the performance now that I do!
I did the "unbrick" thing with "repart.img" to get the Tablet back to "out of the box" state and sighed of relief when it worked!
Yeah, I was afraid of that. I really didn't wanna go through the process of unbricking, but I guess there's no help for it.
troy9829 said:
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
Click to expand...
Click to collapse
Power + 'n' doesn't work on my NT either, I have to turn the device off, insert the SD with CWM, then plug in the (still turned-off) NT to a wall charger and allow it to boot up that way - then (and only then) do I boot into recovery, and without touching any buttons. Hopefully that helps
Dang, whoever thought this would be such a booger of a deal?!?
Okay, first off, let me apologize for coming off like a noob, but it seems there's so much information out there that everything's kinda bleeding together, so let me tell you where I'm at.
I've unbricked and restored the NT to stock 1.4.2
I tried rooting, but the only root I can find that is flashable from SD is the 5.5 CWM which is older than the CWM 6.xxx that every CM10 version calls for. So I went ahead and did the root, so now I have a stock NT with root access. This is where I'm getting stuck...
I'm at this point...
http://forum.xda-developers.com/showthread.php?t=1640958&highlight=cwm+1+4+2
...and it apparently requires you to reboot into CWM in order to install CWM?!?
I've found the CWM 6+ files I think I need, but when I try to follow the instructions, my NT won't kick over into recovery---it keeps booting straight to the rooted 1.4.2 stock rom. I've found guides that take you from stock 1.4.3 to CM10, some that take you from 1.4.2 to root, and I even found Indirect's CM7 (without the instructions on how to get CWM on there in the first place!). I even downloaded Rom Manager and tried to boot into recovery that way, but it said there was my device wasn't supported.
I've been staring at this dang screen for three hours, trying to find a step by step, and I'm coming up empty. Maybe I'm just too frustrated at this point and need a breather.
What I need to know is how to install CWM 6+ on a NT that's either rooted or stock 1.4.2 (I still have the unbrick SD card) so that I can boot into CWM. From there, I can make my way through installing CM10. Help. Please. Am about to chew the lining out of my cheek.
I don't know if this might be helpful? http://forum.xda-developers.com/showthread.php?t=2037368
Sent from my NookColor using Tapatalk 2
Not yet. I was expecting OTA to kick in, updating my current 1.4.2 to 1.4.3, but it hasn't. Honestly starting to think my NT doesn't want to be rehacked LOL
Okay, so here's what I'm doing at the moment...
I'm at rooted stock. I moved CWM 6.0.1.2, CM10, and gapps over to internal SD.
I booted into recovery with an older version CWM SD card (SD card image with Win32 > turned off NT > insert SD > plug in USB to autoboot)
While in recovery (from SD), I flashed CWM 6.0.1.2 , CM10 (meghd00t), and gapps-jb-20121011.
I reboot...
WE HAVE JOY!
Now to check to see if the thing's gonna run right (got a whole lotta "XYZ has stopped" error messages upon boot up)
Dangit, keep getting those error messages about Gapps stopping and Google Play, and other stuff. Not allowing me to do hardly anything I need to. I can't even boot into recovery from the home page---it still loads straight to the Rom. In order to get into recovery, I need to use the SD that I made to get into recovery in the first place. Going to wipe dalvik and the other caches to see if that helps...
After wiping the caches, I boot into CM10 with no error messages. I DL'd a game from my Gmail account, and it appears to be working properly. Thanks for the suggestions and for letting me vent
I just went thru this similar ordeal too. It took me over 3 weeks to finally find a recovery & cm10 combo. What I found is that I couldn't get ANY version of twrp to act right. Indirect's flashing tool was invaluable. I finally used it to flash a cwm 6.x from Laverne's thread. It seems that not all versions of cwm 6.x are compatible with certain cm10 roms too & by chance I hit a combo that finally worked! I'm staying with what I got for a while!
Sent from my Nexus 7 using Tapatalk 2
Hey all.
So just a few hours ago, I was running rooted stock, as per the guide in the development section. I then installed twrp, and attempted to flash a ROM, which resulted in my phone not booting.
Since then, I got into recovery, attempted a factory reset (which didn't work), and ended up using Odin to restore to stock.
So now I'm sitting on the stock image, unsure if I have root. Everything seems to work fine, but is slow. Also, I cannot enable wifi (the switch goes on for a split second, then back to off).
Is there a way I can uninstall twrp, and go back to complete and total stock?
If it's relevant, I get a constant "This device has detected an application attempting unpermitted actions..." error.
Thanks guys!!!
UPDATE: It still has root access.
UPDATE 2: I'm finding some similar issues people were having with the T-Mobile version (http://androidforums.com/t-mobile-g...connect-wifi-prevention-information-help.html) though I'm not sure whether I can follow those solutions. I will wait until someone can advise me on this.
It sounds like you didn't installed the complete stock image, that the stocked rooted image is installed. Have you done factory reset?
wolfgrrl said:
It sounds like you didn't installed the complete stock image, that the stocked rooted image is installed. Have you done factory reset?
Click to expand...
Click to collapse
I tried the factory reset option from within twrp recovery, which doesn't fix any of these issues I'm having with constant security alerts or Wifi.
Got it fixed by doing this:
http://forum.xda-developers.com/showthread.php?t=2301259
I got my Optimus G a few days ago and since then decided to put a custom ROM on so I can get Android 4.3. I've tried two methods, rooting, unlocking, etc. with Stock and then flashing a different rom. As well, I've simply used LGNPST to put TeenyBin on before flashing a custom ROM.
I've tried with several ones, from CyanogenMod to SlimBean to Carbon and a few others. For the majority of them, it boots up correctly after being flashed, but the first time I reboot the phone after this it will never start up. It just freezes at the "Google" screen, or for some ROMs it shows this briefly then turns black. Either way, it never successfully boots up once it's been restarted a single time.
I've tried all the options in the Recovery mode, formatting, wiping, clearing cache/Dalvik cache, etc. But no matter what it still doesn't make it past boot.
I can successfully put back Stock on it with LGNPST, but I want to get 4.3 and I can't find a solution that will continue to work after the phone reboots. Any idea how to solve this?
dabomb18359 said:
I got my Optimus G a few days ago and since then decided to put a custom ROM on so I can get Android 4.3. I've tried two methods, rooting, unlocking, etc. with Stock and then flashing a different rom. As well, I've simply used LGNPST to put TeenyBin on before flashing a custom ROM.
I've tried with several ones, from CyanogenMod to SlimBean to Carbon and a few others. For the majority of them, it boots up correctly after being flashed, but the first time I reboot the phone after this it will never start up. It just freezes at the "Google" screen, or for some ROMs it shows this briefly then turns black. Either way, it never successfully boots up once it's been restarted a single time.
I've tried all the options in the Recovery mode, formatting, wiping, clearing cache/Dalvik cache, etc. But no matter what it still doesn't make it past boot.
I can successfully put back Stock on it with LGNPST, but I want to get 4.3 and I can't find a solution that will continue to work after the phone reboots. Any idea how to solve this?
Click to expand...
Click to collapse
I Had Exactly The Same Problem,I Wiped Internal Storage(I Had Took A Backup First)
Then Flashed Stock 20j Via LGNPST
Then Rooted It And Downloaded FreeGee App And Unlocked Bootloader And Installed Recovery.
And Now I Don't Have That Issue.
Regards,
acervenky,
XPT
acervenky said:
I Had Exactly The Same Problem,I Wiped Internal Storage(I Had Took A Backup First)
Then Flashed Stock 20j Via LGNPST
Then Rooted It And Downloaded FreeGee App And Unlocked Bootloader And Installed Recovery.
And Now I Don't Have That Issue.
Regards,
acervenky,
XPT
Click to expand...
Click to collapse
Thanks for the reply acervenky. I did what you said and got it rooted successfully, but then when I unlocked the Bootloader using FreeGee0.5 it said it worked successfully. However, when I tried rebooting it got stuck on the LG logo and I had no luck getting into the bootloader screen.
Edit: In the past, I followed different guides that would supposedly unlock your phone using the FreeGee app from the Play store, but those didn't work either when I tried them. Generally they would say successful, but even then most of the time it wouldn't work afterwards.
Okay somehow I got it working!
I'm not sure what steps along the way fixed it, but essentially I re-flashed a few times, either 20j stock or TeenyBin [Alt]. Eventually, wiping, formatting, etc. and installing my custom ROM SlimBean worked. The difference was that this time it works now when I reboot, so I don't have a gimp form of 4.3.
Thank you again acervenky, I'm not sure how but installing 20j seems to have done the trick. On the plus side, when I continued to reflash 20j it would always keep my data, allowing me to mess around without having to worry about losing all my settings.
dabomb18359 said:
Okay somehow I got it working!
I'm not sure what steps along the way fixed it, but essentially I re-flashed a few times, either 20j stock or TeenyBin [Alt]. Eventually, wiping, formatting, etc. and installing my custom ROM SlimBean worked. The difference was that this time it works now when I reboot, so I don't have a gimp form of 4.3.
Thank you again acervenky, I'm not sure how but installing 20j seems to have done the trick. On the plus side, when I continued to reflash 20j it would always keep my data, allowing me to mess around without having to worry about losing all my settings.
Click to expand...
Click to collapse
Glad That It Helped,Just Press The Thanks Button Instead Of Replying.
It Means A Lot :highfive:
Regards,
acervenky,
XPT
Hi All,
Today I decided to "update" TWRP to 2.8. I backed up the old recovery using Flashify, and then performed the update using the same. After a reboot I was treated to Download Mode with a 'Could not do normal boot' error.
I am quickly remembering that I used safestrap back when I originally did this after I got a Secure Magiccode Check Fail via ODIN in an attempt to fix things.
Is there any way for me to atone for sins, and undo the error of my ways?
So, I turned off the phone completely for about 30 minutes to an hour. After that, I started to charge it, and the battery icon came up. I turned it back on, and it jumped right into safestrap and continued working normally as if I had not mangled it. No idea why this happened, but hopefully this can help someone else.
You say TWRP, then safestrap. Those are two completely different things. Safestrap is for LOCKED BOOTLOADER devices. TWRP is for MDK ONLY. Be lucky that you didn't brick it.
Hey guys, I was running stock ZVC (with stock recovery and bootloader) until just a few minutes ago, when I finally gave in and told the phone to apply the OTA update that was pushed out last week (the "ZVE" one). It started doing its thing, but next time I looked back at the device it was in recovery mode, just sitting there at the menu prompt...
I've since tried rebooting and powering off about half a dozen times, but it just keeps looping back to recovery mode. I also tried wiping the cache and rebooting, with no luck... It still loops back to recovery mode. I don't know what went wrong, but I'm assuming it could be related to one of two things that I didn't think about until afterwards:
1) The phone was rooted via Kingoroot, and root was still active when I tried to apply the update.
2) Just a FEW programs were frozen via TitaniumBackup (as well as Android's own app management system, using the "disable" feature), but these weren't system- or kernel-critical apps. They were things like LG Health, Sprint Money, etc...
Can anyone suggest a fix? Right now it just keeps rebooting into stock recovery and I've never had to deal with an issue like this, so I'm not sure what to do. I was obviously running the stock ROM, so I'm not set up to flash stuff. Although if it can be done with the default recovery, I suppose I could obviously do that... Once again, everything was stock on the phone except for Kingoroot, which was still enabled during the update.
I'm in a pickle here, guys. It's not like I'm any different than everyone who "needs their phone for work," but yeah, I need my phone for work... If I have to wipe data/factory reset, there's probably no way to pull some data off of the phone via PC first, is there? I suppose it's not that big of a deal, but I have some data and some program data that I hadn't gotten around to backing up yet, because I didn't think I'd need to until before I attempted to flash a new ROM or custom recovery.
Any help would be HUGE. Thanks...
EDIT: I took it into the Sprint store today a couple hours after I posted this, and they said I'd have to send it in to LG for warranty service. I don't know if the Sprint tech person knew what she was doing or not (because she had to use Google to figure out how to put the phone into download mode, even though she owns the same model), but she said that she couldn't establish a connection between the PC and the phone...
Now I'm not sure if that's the case, or if she just didn't have the right drivers installed, or if she was even in the right mode (I think she was using some Sprint-made flashing tool, but she did get it into download mode). She also seemed bored and like she just didn't wanna deal with it, so I don't know...
Assuming I can flash back to an earlier build like ZVB (and assuming I can even find it online), is that done from download mode or from recovery? By the way, we also tried just doing a factory reset and that didn't work either; just keeps rebooting to recovery...
Thanks...
EDIT 2: Fixed by flashing to stock via these instructions. Had to select Board DL and use a different key sequence as described here.