No need to use the LG Updater tool again. Just boot into recovery, wipe data/cache (I'm assuming you don't care about anything and want to get the phone into factory fresh state), then reboot and let Android recreate everything. I don't know specifically how NROM does the bootanimation, but one method is to put it in /data. All the update procedures from Sprint and LG do not touch /data because that is your personal information and your installed applications, so if the animation is in /data, wiping it clean should get rid of it. It is a good idea to wipe data/cache anyway because it has your personal info.
[How-To] Simplified UNROOT and return to STOCK
- Thread starter sfhub
- Start date
I just downloaded NROM 1.5.2 and checked. Yes, it is putting the bootanimation in /data/local.
If you wipe data/cache from recovery it will definitely get rid of the animation.
If you wipe data/cache from recovery it will definitely get rid of the animation.
Got rid of it. I am finally good to go and exchange it for another Optimus S which I am sure will have VD. What next?
I cant seem to flash the stock recovery image, says something about a bad block in recovery and then out of space. I can flash thunderc and xionia no problem though.
In the revert/force flash thread referenced in the first post, it gives you the substitutions for Force Flash VC in the reference section. Just follow the Force Flash V9 instructions and substitute what is mentioned in the reference section.
Though the chance for some type of failure is not high, I always suggest you make a backup before flashing.
Are you sure you are using the one linked from the first post?
Have you unzipped the file to get the recovery.img file?
Could you give the commands you are using the flash and the output of the commands?
I just downloaded the stock v9 recovery linked in the first post and the checksum matches what is expected.
My guess is you specified something other than the "recovery" partition on the phone or you are trying to flash the zip file (renamed to recovery.img)
The command is
I have unzipped everything from the first post to the root of my sdcard. I'm just hoping its not a problem with my device but its weird that the unofficial recovery images flash without issue.
Can you type in an adb (root) shellI have unzipped everything from the first post to the root of my sdcard. I'm just hoping its not a problem with my device but its weird that the unofficial recovery images flash without issue.
and post the output.
Here it is:
dev: size erasesize name
mtd0: 00700000 00020000 "boot"
mtd1: 07c20000 00020000 "cache"
mtd2: 00700000 00020000 "recovery"
mtd3: 00140000 00020000 "splash"
mtd4: 00700000 00020000 "FOTA_STO"
mtd5: 09e80000 00020000 "system"
mtd6: 0a4e0000 00020000 "userdata"
mtd7: 00080000 00020000 "misc"
mtd8: 00180000 00020000 "persist"
#
dev: size erasesize name
mtd0: 00700000 00020000 "boot"
mtd1: 07c20000 00020000 "cache"
mtd2: 00700000 00020000 "recovery"
mtd3: 00140000 00020000 "splash"
mtd4: 00700000 00020000 "FOTA_STO"
mtd5: 09e80000 00020000 "system"
mtd6: 0a4e0000 00020000 "userdata"
mtd7: 00080000 00020000 "misc"
mtd8: 00180000 00020000 "persist"
#
There were two explanation that I was looking at.
First was there might be different sized recovery partitions on different models. However your recovery partition is the same size as other phones.
The second explanation is that the recovery.img is a full backup of the entire mtd2 partition, even the portions that are empty. So the reason you are probably seeing the error is you actually do have a bad block (memory) in your recovery partition and the reason you see it flashing the v9 recovery.img is because it is exercising the entire range of memory in your recovery partition, whereas the other recoveries are only as big as the recovery needs, and/or they are smaller in general, so they are avoiding the bad block(s).
You can try an updated flash_image to see if that helps (I didn't look at the source to see if it handles stuff differently, so I'm not saying it will behave differently)
http://files.mysticmidnight.net/zefie/files/cell/LGLS670/tools/flash_image.zip
You can also just try rebooting to recovery and seeing if the V9 recovery comes up. There is a chance the important parts of the recovery.img were already written before hitting the bad block, so even though there is a write error, it isn't relevant. Do not use "adb reboot recovery" as I believe that will write stuff to the misc partition which might get you into a loop if your recovery is bad. I think using Power Down / Home + Vol- + Power will be ok.
I can also post a minimal recovery.img with the empty blocks removed to see if that avoids the bad blocks. Let me know if that is something you want to try.
You could also just run the V8->V9 update.zip. It should create the recovery partition by patching the boot partition. It should work in theory, but again, I haven't traced the exact mechanisms it is using to handle the various reboots and writing of flash memory, so couldn't tell you for sure it wouldn't get you into a boot loop.
There might be a way to format the recovery partition and lock out the bad block, but I don't know enough about the MTD tools to advise you on that.
I'm just warning you in advance about potential problems. I'm not saying any of these are likely.
So IMO the problem is with the flash memory on your device.
So let me get this straight: my phone is vd updated from lg tool and rooted so to unroot I just have to manually flash the v9 stock recovery, then use the lg updater tool to flash vd again and then follow directions 3-4?
Yes. As a side bonus, if you were planning on returning your phone but changed your mind, your system is still rootable.
If you are already running stock recovery, you could just flash V9 or VD, whichever is appropriate for your unit (new or old LCD).
If you are already running stock recovery, you could just flash V9 or VD, whichever is appropriate for your unit (new or old LCD).
I'm trying to manually flash v9 stock recovery and I tried it on terminal and it says cant read flash image and when I try it using adb shell its saying it doesn't have a path and adb is not recogninzed as an internal or external command? I have this phone on e bay and I need to unroot it today
Ok I flashed the v9 stock recovery and it worked, but my phone is still rooted and I still have the thunder rom. I don't know what to do next?
Did you run KP500 and force flash ZV9 (or VD if you have the new LCD)?
I don't see how you can still have Thunder ROM if you Force Flashed V9 successfully.
can't you just force flash back to zvc? when I done it it gave me complete stock rom and recovery. be easier I think if you want to go back to stock.
1) Force flash often (but not always) leaves your existing recovery in place
2) Force flash doesn't touch your /data so your apps and personal info are still there
3) Force flash doesn't touch your NVRAM so your Sprint login and phone # are still there
Certainly you can skip steps if they aren't important for your needs.
Similar threads
Latest posts
-
-
Wi-Fi Calling not always working even though WiFi Signal is very good
- Latest: fallingOutOfLoveWfithTech
-
-
Question Why ? do my gmail emails get deleted after 2 weeks on my android mobile ?
- Latest: RemusGhostofRome
Trending Posts
-
[Chatter] "Where everybody knows your name ..."
- Started by zero neck
- Replies: 53K
-
-
S24 pictures... show us how they look!- Started by Walter Wagenleithner
- Replies: 388
-
-
News Glance is coming to the US, whether we like it or not- Started by AC News
- Replies: 2
Facebook
Twitter
Instagram