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.
Related
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!
First off I am on mdk and rooted and up until today have been running hd 10.2. I had been having some weird things happen with twrp 2502 so I went into goo and tried to update to the newest version of twrp. it downloaded and went through with everything and I rebooted into recovery. once I got into recovery it was showing I was still on 2502, but it was asking for a password which I had never seen before. I backed out and tried to boot into my rom again and it got stuck on the samsung custom screen. pulled the battery a few times and still kept getting stuck. went back into recovery and tried to restore a known good backup that I had restored before, but it keeps failing. I had rls12 on my phone so I tried installing it dirty since I cant wipe anything due to the whole password thing in twrp which said it was succesful but still gets stuck on the samsung custom screen. it sits there for about 10 seconds and loops. I tried about 10 more times to get my backup restored and it finally finished and booted into the rom. I left it this way for an hour or so and did some stuff with my phone, tried to update twrp again which did the same thing again and still shows 2502. after the reboot I am back to the same problem of not being able to do anything in twrp except restore or dirty flash, I cant get the usb to mount in twrp so I cant try putting another rom on the phone unless I go and buy a micro sd adapter.
I am in the process of downloading a stock mdk rom to try and flash in odin, but is there anything I can try before I go through with this, or is it pretty much my only option.
after some more research I think I figured out what caused all this. I wiped the data partition with the old version of twrp which screwed it up pretty bad. Apparently the older versions of twrp were known to have this problem. I kept trying to restore, but trying to restore kept failing on the data partition. After about 25 attempts of trying to restore just the data partition I was able to get it to work finally, and then I restored the the others and got it to boot back into the rom. like an idiot I rebooted the phone back into recovery after it finished and had the same problem again. another couple hours wasted trying to restore the data partition and it worked again and this time i was able to get twrp to update and then went back to recovery and formated the data partition again and it seems to have fixed the problem. Now to figure out why hd rls 12 wont install.
Hello,
I'm a rather experienced Android user. Before I flashed my S3 for the first time, I made sure to back up my EFS. After about a year and a flash of the newest ArchiDroid version, I couldn't get any signal all of a sudden. It worked the days before, and I flashed nothing new or installed anything. I read online about what that might have caused, and it seems like the problem of a lost EFS partition was the problem. I restored my EFS, rebooted, and the phone won't turn on now. It is stuck on the flashing "SAMSUNG" logo on start-up. Thinking I did something, I tried to boot into Clockwork recovery, but it only shows the ClockworkMod logo for about a second, then it reboots again. What should I do?
Try flashing a full stock firmware with Odin, but sudden failure could be nand wear.
Thanks for the reply, I flashed stock firmware with Odin. No errors, but I'm still stuck at the flashing "SAMSUNG" logo.
Boot into recovery and factory reset.
Alright, got into recovery.
Got an error: "E:Failed to mount /efs". How do I restore my EFS with my efs.img now?
EDIT: Managed to get my phone back to work, However, still no signal. Mobile data and phoning does not work.
Format the efs partition then restore your backup, check the permissions then factory reset again.
Edit. If your efs backup was really old, ie. efs v1, then you might have to flash a firmware from before EMG4 to get the efs read, then update to 4.3.
Alright, I know enough to be dangerous. I rooted my Samsung tab a 10.1 by installing twrp and then super su, all went fine. I then began to try and make a nandroid back up. It kept saying unable to mouth data, so I read a little and I changed data format. This caused a boot loop. Went in and changed back data format and used twrp to reset. All was fine again. I then attempted to use titanium backup. I recited a message backup was successful and reboot. I rebooted and now a boot loop. I then tried to reset with twrp and my file is gone. So, I downloaded what I thought was the right firmware to flash with Odin but just made that worse. Does anyone have a download for a rom I can flash with Odin to get this thing going. I have downloaded a couple and the either don't work or are the wrong one. SM-T580.
tlstaggs said:
Alright, I know enough to be dangerous. I rooted my Samsung tab a 10.1 by installing twrp and then super su, all went fine. I then began to try and make a nandroid back up. It kept saying unable to mouth data, so I read a little and I changed data format. This caused a boot loop. Went in and changed back data format and used twrp to reset. All was fine again. I then attempted to use titanium backup. I recited a message backup was successful and reboot. I rebooted and now a boot loop. I then tried to reset with twrp and my file is gone. So, I downloaded what I thought was the right firmware to flash with Odin but just made that worse. Does anyone have a download for a rom I can flash with Odin to get this thing going. I have downloaded a couple and the either don't work or are the wrong one. SM-T580.
Click to expand...
Click to collapse
Alright, I was using an olsee version of odin, got the new one and I was able to flash a rom. It says tab a 6 on boot up bit it is functional. Now my question? Can anyone recommend a custom rom that is nebiew friendly. I'm food at following directions and problem solving but I about had a panic attack, I just got this $300 thing. Sigh off relief for at least getting it functional again.
Hmm
Ok so I have flashed a stock rom, 6.0.1, flashed TWRP, and installed SuperSU. all is working well again. However I am still getting "unable to mount data" message in TWRP when i try to make a backup. If i uncheck data on the list it backs up fine. This is what got me in that boot loop pickle before when i tried to change the data format. What data format? Idk, im scared to jack with it anymore, and im done with titanium backup, it has burned me in the past, though i think what went wrong there was when i backed everything up i then went and change data format and after all that restored and the backup was in a different data format. Idk newbie guess. I am just trying to getting a reliable nandroid backup. Anymore ideas? Perhaps i should just leave it alone and be happy with just having root.
Its my daughters bog standard, cheap chinese MTK6580 phone (uhappy up580 if it matters)
It came with stock 5.0 a few years back so I flashed TWRP, rooted it, ported a CRdroid 5.1 rom for it and was working fine. Yesterday on boot every app refused to start, or stopped, or froze including stock launcher and settings so I couldnt do anything at all. Booted to TWRP and wiped cache and dalvik but although TWRP said completed, it hadnt.
So decided to wipe EVERYTHING including data and again TWRP said it had but upon reboot the faulty rom was still there, not working.
Tried to flash a backup that ended in tar error, fixed that and it flashed the backup fine, rebooted but it hadnt.
Tried to TWRP flash a new rom, said it had but it hadnt,
Used SPFlash tools to flash the stock 5.0 rom, THAT said it completed after the usual time and procedure, rebooted but it hadnt
Used SPFlash tools to completely format and wipe the phone which also said it had completed but it hadnt.
I CANNOT wipe this phone using any method I know of! or install or flash anything! Just this same custom rom that was fine for years and just went wrong. Does ANYONE know how I can somehow wipe this phone or flash a new rom? Tried flashing a TWRP with SP tools AND a TWRP .img and they all said completed but obviously, nothing did.... I've accidently bricked phones easier than I can deliberately wipe this one
Any help greatly appreciated.
emmc is weared out. therefore it is read only
aIecxs said:
emmc is weared out. therefore it is read only
Click to expand...
Click to collapse
Gah... exactly what I suspected but hoped not
cheers