The device is the LG LU6200 (gfs)
device was rooted and on LU6200_162_CN_Yang_0704 ROM. '(ICS)
Today, the gf was prompted to update/upgrade system by LG and she chose to do so after feeling harassed by the update notices. now the devices goes directly into CWM after booting from LG screen (it won't load normally). She tried restoring from zip, but it has no effect; it reboots into CWM after the bootup page. We restore using every backup file available, tried wiping cache, data, and dalvik, then restoring, tried going into advanced restore and restoring boot (presumably the boot.img), tried re-installing the ROM, but to no avail.
I'm guessin the official update clashed with the bootloader...?
also worth mentioning, before installing CWM, Power+Vol up usually brought up the restore factory screen. Afterwards, it went into CWM.
I'm planning on re-flashing v142 .kdz with the upgrading tool on Sunday since I don't see her until then, but could use any advice/suggestions in the meanwhile.
thanks!
Related
I've previously used LGMDP to install clockworkmod and haven't had any problems. I upgraded to V20g using LG's update utility and that's been fine, though it's T_Mobile branded. I've tried to install the unbranded European V20e through LGMDP and that's where the problems started.
At the end of the V20e flash, I got errors when it tried the NV restore. Items 1 to 158 have a status of NV_FAIL_S. After that, the phone won't boot. It gets stuck on the Android boot animation.
I've tried NV Restore with previous backups that I know have been OK before, but it still fails the same way.
If I use LGMDP to flash T-Mobile V20g, then flash clockworkmod (still getting NV errors), I can run clockwordmod & restore my backup from before I started this. After that, the phone boots & seems normal. I've got a signal, anyway.
I'm still a bit worried that something isn't right, though. It still refuses to restore the NV. I've tried going back to V10g using LGMDP and it fails to restore the NVs and the phone won't boot.
So, has clockworkmod restored everything I need and is there any way to fix this so I can use LGMDP again?
I think I've resolved this now, so I'll post what I've done in case anyone finds this in a search.
I already had a V20g KDZ file for my provider, which I got by following the instructions here. I looked for an alternative flash app and found details of KDZ Updater here.
V20g flashed successfully with that software. After that, I've tried LGMDP again and can do an NV Restore with no errors now, so things look like they're back to normal.
I still can't flash V20e with this software, though, I still get stuck on the Android boot animation.
I had changed baseband 3-4 times. In last 3 attempts, I also got these errors. But my phone rebooted normally after these errors. I had fully working phones in all the cases. Don't know why there were errors?
Same thing here. Hundred something NV_FAIL_S errors but phone seems ok though.
You have to do factory reset after flashing new ROMs.
This may solve bootloop.
droidaem said:
You have to do factory reset after flashing new ROMs.
This may solve bootloop.
Click to expand...
Click to collapse
ive never heard of this one before. isnt it just wipe cache, dalvik cache, etc, in recovery?
I decided to try again with V20e but used the kdz file and KDZ Updater this time. Same thing happened, stuck on Android boot animation.
So I put clockwork on, wiped cache & dalvik, tried again, same problem. Reboot into clockwork, factory reset, reboot, same problem. Finally, I booted into clockwork, went to Advanced and Fix Permissions. After that it booted fine.
While installing clockwork through LGMDP I didn't get any errors. I've also tried an NV Restore with no problems. No idea what went wrong the first time.
So I have been following the unofficial cm-10.2 ROM. I have dirty flashed probably 3 times without issue. I flash the ROM, a pinlock removal zip and gapps. Then wipe dalvik/cache and reboot. I started doing this with twrp 2.6.
So this morning I grab the latest update, backup, flash.l, reboot.... nothing.
Stuck at LG logo to a black screen. I can get into bootloader, blindly vol down twice and into recovery, now twrp 2.5, so I try to recover by backup, reboot.... black screen.
So I try wiping/factory reset, clean flash, reboot.... black screen...
Now I am a little concerned. I read up and find out about TeenyBin, so I setup my machine to flash the standard zip and that doesn't really work, it flashes fine, reboots but is stuck at LG logo and the tool reports disconnected, so the tool fails kind of. So I try the alternate, same sort of thing, but now it says Google instead of LG and is stuck there. I can get into bootloader, can see text now (nice!) and get into recovery, still 2.5. Tried restoring, wiping/flashing, nothing working..... stuck at Google logo.
So, then I went and formatted internal storage. Bingo! Now I can flash/restore/whatever and I can reboot and get into ROM!
Woah, woah, woah... Not so fast.
So now if I wipe anything, cache/dalvik/system/ANYTHING it soft bricks. I have to again format internal, then flash. That doesn't seem right to me. Sure, I have a functioning phone, but updating is a bigger ***** now that I have to completely format before flashing.
So my question to you all, how do I fix this? Do I need to completely go back to stock image and reroot? I appreciate all your suggestions.
daveerickson said:
So I have been following the unofficial cm-10.2 ROM. I have dirty flashed probably 3 times without issue. I flash the ROM, a pinlock removal zip and gapps. Then wipe dalvik/cache and reboot. I started doing this with twrp 2.6.
So this morning I grab the latest update, backup, flash.l, reboot.... nothing.
Stuck at LG logo to a black screen. I can get into bootloader, blindly vol down twice and into recovery, now twrp 2.5, so I try to recover by backup, reboot.... black screen.
So I try wiping/factory reset, clean flash, reboot.... black screen...
Now I am a little concerned. I read up and find out about tinyrom, so I setup my machine to flash the standard zip and that doesn't really work, it flashes fine, reboots but is stuck at LG logo and the tool reports disconnected, so the tool fails kind of. So I try the alternate, same sort of thing, but now it says Google instead of LG and is stuck there. I can get into bootloader, can see text now (nice!) and get into recovery, still 2.5. Tried restoring, wiping/flashing, nothing working..... stuck at Google logo.
So, then I went and formatted internal storage. Bingo! Now I can flash/restore/whatever and I can reboot and get into ROM!
Woah, woah, woah... Not so fast.
So now if I wipe anything, cache/dalvik/system/ANYTHING it soft bricks. I have to again format internal, then flash. That doesn't seem right to me. Sure, I have a functioning phone, but updating is a bigger ***** now that I have to completely format before flashing.
So my question to you all, how do I fix this? Do I need to completely go back to stock image and reroot? I appreciate all your suggestions.
Click to expand...
Click to collapse
Give CWM a shot and see if it does the same thing?
Does anyone know what is wrong here? I wanted to get back to stock by flashing Amazon's stock .bin (changed to .zip) in twrp. I've done this before and had no issues. In twrp I wiped everything and then flashed the .zip. Then I booted into the Amazon OS and everything appeared fine. I'm on 14.3.2.5. For one, I cannot factory reset. After trying to do so, it reboots to the Kindle logo and just permanently hangs there. If I try to update it manually to 14.4.5.5, once again, it just hangs on the Kindle logo. It appears I have no recovery or something. What I don't understand is that I've done this in the past with no issue. Where I am now is that I am able to boot without issue into 14.3.2.5, but cannot update. What can I do?
edit: http://forum.xda-developers.com/showpost.php?p=55759790&postcount=204 fixed it. It restored my stock recovery and I was able to update and factory reset after doing it.
Hi all,
Sigh. So it looks like I bricked my Samsung Tab E Verizon. I rooted it with King root and when I removed it, it is now in a endless boot loop. I've tried all sorts of things to try and recover it.
I used SkipSoft to set it up to be flashed but odin fails everytime. I was using the new ROMS found on this Forum. I've tried putting it into download mode and manually flash it and that didn't work. I can't Re-Root it as it won't stay on long enough to Root and they always fail. Right now I'm at a loss.
Can anyone help?
Thanks.
Do you have custom recovery or default? if you have default you can hold the home button and vol up button then the power button to get into recovery, once your done with that you can wipe cache and reboot, if that STILL does not work then factory reset your phone and re wipe cache, i know losing data sucks but its better then a brick. (this will work 99% of the time because the default recovery automatically re-installs stock rom)
If you have a custom recovery, then i recommend wiping everything including dalvik cache etc, making sure EVERYTHING is squeakly clean (execpt recovery obviously) , and find the driver for your samsung phone and download it on your computer and install, once you are done with that, put your phone into download mode, find your original STOCK rom for your phone, download it and flash it with odin, from there IF successfull you should have a fresh boot of your stock rom, then you can re-root and go on with your day.
Also make sure once you re-gain root access backup your rom so you will always have a plan b if everything goes bad. i cannot recommend this enough, even if you are an expert with flashing, there is always that small percentage things will go wrong and you should always have that backup ready.
Hi!
Thank you very much for the reply. You know, that was one of the things i tried initially when it happened. When I tried it, it wouldn't go into recovery mode. I then went on the odyssey of hell in trying to recover it.
When I read your post I was thinking; "Yeah I tried that", but then I thought I would give it another shot. I went into Factory Reset, it then actually went into the recovery menu. I deleted the cache and set it to data/factory reset and it's still looping. I get an error saying; "E:failed to mount /preload (no such directory)". I then tried to run update from external storage and it's telling me that it's disabled. I tried to update from ADB and it's disabled. I tried to apply from cache and it says; "APPLY_CACHE is depreciated". It's still looping.
Urghhhhhhhhh.......
hey guys just looking for some help. ive been modding and flashing phones from 2014, but its always gone really smoothly, so my diagnostic ability is lacking.
it started with flashing twrp. my bootloader is unlocked, usb debugging on, device is showing in adb and fastboot, and i can flash twrp without any issues. hoowever when i go to boot twrp, only the stock recovery boots. i tried to flash twrp using the XiaoMiTool v2, but the same thing happened. i eventually got around this by just booting twrp instead of trying to flash it. so i got in, took a full back-up and started installing a custom rom.
the first one i tried was ParanoidAndroid Quartz. i wiped cache, dalvik and storage then transferred it to my phone, tried to flash and got "zip verification failed". so i turn off zip verification and tried again. it flashed perfectly with zero errors. however, when i reboot the phone it would only boot to stock recovery and not twrp (expected) or the new rom. i tried that a few times, then tried LineageOS, and MSM Xtended 10. all of them had the same issue, the flashed without a hitch, then wouldnt boot.
i also tried flashing a new fw-vendor and it just straight up failed. Then i decided to cut my losses and restore my twrp backup, and that came back with the error, "extractTarFork() process ended with error: 255"
Software before i began these attempts was completely stock, so i dont know what is going wrong, but as of now, my phone is bricked, i cant install a new rom or restore my back-up.
any help is appreciated guys. thanks
You can figure out this problem with
1 Copy backup folder to computer
2- Format Data - Yes , Wipe Everything
3- Install ROM that you have installed before and boot
4- Go to TWRP, format data yes reboot recovery
5- Paste backup folder to internal storage and restore