Database Develop

[Q] Rooted and installed the ICS Rom. Can I go back to Stock if necessary?

Hello. First off, I want to thank everyone for their hard work here. I have followed many tutorials and have seen many great conversations to keep noobs like me from making mistakes when trying to delve into the world of ROMs and rooting. However, I did encounter some troubles while installing the ICS rom onto my bionic (running on .902). I think I may have accidentally overwritten the stock rom backup that I made with safe strap or whatever that app is (I'm sorry, like I said, I am a complete noob). Is there a way to restore the phone to stock, as in before I even touched it, even if the backup I made during the process is gone by my mistake?
I'm sure this has been asked a million times, and if so, I apologize, but as I noob, I have no idea how to even begin to search for clues. Walkthroughs would be nice, but links are fine too, since I'm sure there are plenty of the same questions out there.
Thanks!!!

Pete's motorola tools check it out you will find what you need there just google Pete's tool bionic
Sent from my XT875 using XDA App

Also I believe if you disable safe mode it will boot up rooted stock from don't quote me on that I am not for sure. Also I believe there is a unroot method in development not sure if it is for 902 or not though..
Sent from my XT875 using XDA App

Thanks for the info!

No problem here to help
Sent from my AXI0M IONIC using XDA App

R3l3as3DRoot and for3v3r root will take you back to 886
Sent from the Evil Empire

Thanks! Can that be used after the .902 update? Is it possible to do a dual-boot type deal between stock and the ICS version I have installed? I've seen mentions of dual-boot around here, but I can't get a clear grasp on whether it is possible or not, or if so, how to do it. Thank you very much!

Lonepalm said:
Thanks! Can that be used after the .902 update? Is it possible to do a dual-boot type deal between stock and the ICS version I have installed? I've seen mentions of dual-boot around here, but I can't get a clear grasp on whether it is possible or not, or if so, how to do it. Thank you very much!
Click to expand...
Click to collapse
Yeah I'm sure you can.
Get on stock .902(here).
Install SafeStrap.
Backup Stock Rom by Toggling "SafeMode"
Boot up ICS.
When you want to go to Stock .902 undo "SafeMode" and the Stock Rom should boot up on Reboot

Thanks for the answer! Hopefully I can give this a shot soon!

Lonepalm said:
Thanks for the answer! Hopefully I can give this a shot soon!
Click to expand...
Click to collapse
Yeah those instructions above are correct. I just came back from the AOKP ICS Rom to stock. 902. Worked fine. I have all my apps and stuff too.
Sent from my DROID BIONIC using Tapatalk

Don't know what I'm doing wrong here, but when I plug my phone in to my PC, the phone realizes it, but doesn't seem like the PC does. Also, when I open RSD Lite and try to load the file, it doesn't do anything after clicking "Start". Please help me try to diagnose what I may be doing wrong if you can! Thank you!

Lonepalm said:
Don't know what I'm doing wrong here, but when I plug my phone in to my PC, the phone realizes it, but doesn't seem like the PC does. Also, when I open RSD Lite and try to load the file, it doesn't do anything after clicking "Start". Please help me try to diagnose what I may be doing wrong if you can! Thank you!
Click to expand...
Click to collapse
Enable Usb Debugging and Unknown Sources. Download Motohelper drivers
Sent from my DROID BIONIC using Tapatalk

I'm sorry I probably should be a little more specific. I have both of those enabled and I do have the Motohelper drivers installed. I am following the steps here: http://forum.xda-developers.com/showthread.php?p=22758211#post22758211
On step 8, I do not see a file named FXZ or a file with that extension, but I figured it was the file with the name that the zip file had. I chose that file after clicking "..." and hit Start, but it doesn't do anything.
I am running the ICS version cyanogen mod 9.0.0-rc0-droid_bionic-kang build number alpha_2012_02_10
I already have SafeStrap installed (used that to get this rom on). So, looks like I'm stuck on or around step 8 from the other steps posted. Once I can get past that, I can continue with the steps posted in this thread!
Thanks!!!

Lonepalm said:
I'm sorry I probably should be a little more specific. I have both of those enabled and I do have the Motohelper drivers installed. I am following the steps here: http://forum.xda-developers.com/showthread.php?p=22758211#post22758211
On step 8, I do not see a file named FXZ or a file with that extension, but I figured it was the file with the name that the zip file had. I chose that file after clicking "..." and hit Start, but it doesn't do anything.
I am running the ICS version cyanogen mod 9.0.0-rc0-droid_bionic-kang build number alpha_2012_02_10
I already have SafeStrap installed (used that to get this rom on). So, looks like I'm stuck on or around step 8 from the other steps posted. Once I can get past that, I can continue with the steps posted in this thread!
Thanks!!!
Click to expand...
Click to collapse
SafeStrap disables ADB(that Im sure of) which will not let RSD run(im pretty sure) you have to select the xml file
Sent from my DROID BIONIC using Tapatalk

Yes, the XML file is the one I select. However, it will not do anything in RSD. Is there anything I can do to enable ADB in order to let RSD run?

Update: I found a way to do it. I think things are going okay so far. Looks like it is installing. If it does install successfully, I would like to do everything perfectly right going forward.
So, after this is installed, I will want to:
1. Get root access again using Motofail? I assume doing this return to stock will remove root access.
2. Install SafeStrap. Once that is done, I toggle Safemode to enabled, which will backup my stock rom and protect it from being overwritten?
3. Then, flash ICS from the zip files on my sdcard?

Lonepalm said:
Update: I found a way to do it. I think things are going okay so far. Looks like it is installing. If it does install successfully, I would like to do everything perfectly right going forward.
So, after this is installed, I will want to:
1. Get root access again using Motofail? I assume doing this return to stock will remove root access.
2. Install SafeStrap. Once that is done, I toggle Safemode to enabled, which will backup my stock rom and protect it from being overwritten?
3. Then, flash ICS from the zip files on my sdcard?
Click to expand...
Click to collapse
Yes sir.
Sent from my DROID BIONIC using Tapatalk

RAZR recovery on Droid 4?

Anyone tried using the RAZR recovery on the Droid 4? Lookin to do up the Arctic rom, but would feel much better if I could get a nandroid.
EDIT: This is the link to the RAZR recovery I was mainly thinking of: http://forum.xda-developers.com/showthread.php?t=1385283

jgardner said:
Anyone tried using the RAZR recovery on the Droid 4? Lookin to do up the Arctic rom, but would feel much better if I could get a nandroid.
EDIT: This is the link to the RAZR recovery I was mainly thinking of: http://forum.xda-developers.com/showthread.php?t=1385283
Click to expand...
Click to collapse
Why not do the nandroid with safestrap?

I didn't think safestrap was working with the D4?

jgardner said:
I didn't think safestrap was working with the D4?
Click to expand...
Click to collapse
I dont know whats going on lol.....everyone is coming with all these different stories. I used the root exploit that was out and used the safestrap for recovery. I dont think I did anything different than anyone else. And then i took a chance flashing a Razr rom

Oh yeah, the original utility had the safestrap didn't it? The latest utility doesn't anymore (although I think it works).
Sent from my DROID4 using Tapatalk

jgardner said:
Oh yeah, the original utility had the safestrap didn't it? The latest utility doesn't anymore (although I think it works).
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I took it out until Hashcode brings it out for Droid 4. I've been corresponding with him and if the maker of Safestrap tells you it isn't safe to use on Droid 4 yet then you usually should listen.
All up to your risk though.

I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?

Briteyez83 said:
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Click to expand...
Click to collapse
Not yet. There is a reason we have warnings on these...
I hope we get fastboot yet. You cannot just "make them" they have to be leaked.
FYI Motorola does Fastboot files, not SBF now.

mattlgroff said:
Not yet. There is a reason we have warnings on these...
I hope we get fastboot yet. You cannot just "make them" they have to be leaked.
FYI Motorola does Fastboot files, not SBF now.
Click to expand...
Click to collapse
Im new to root even though i have learned pretty quick. Finally after much pain and suffering got my X's bootloader unlocked and rooted some time in Nov. What does leaked mean and what is the difference between fastboot files and sbf?
---------- Post added at 02:27 AM ---------- Previous post was at 02:24 AM ----------
As far as the warnings i didnt see the warning to not use safestrap till i got on here and it was to late. I figured since i was able to boot into recovery and make a backup i would be ok

Briteyez83 said:
Im new to root even though i have learned pretty quick. Finally after much pain and suffering got my X's bootloader unlocked and rooted some time in Nov. What does leaked mean and what is the difference between fastboot files and sbf?
Click to expand...
Click to collapse
You would be Man of the Year if you did that. You mean you bootstrapped it, right?
Leaked means they have to trickle out from Motorola/Verizon somehow.. either on purpose or by "accident" somebody on the inside putting them out there for use by our wonderful devs.
As for SBF vs fasboot, i dont know exactly the difference but think of them as different types of "recovery" that can be used to fully restore your phone to factory condition.

Briteyez83 said:
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Click to expand...
Click to collapse
Which FASTBOOT error are you seeing? It should be referencing one of the partitions.
Sent from my DROID4 using XDA App

greekchampion04 said:
You would be Man of the Year if you did that. You mean you bootstrapped it, right?
Leaked means they have to trickle out from Motorola/Verizon somehow.. either on purpose or by "accident" somebody on the inside putting them out there for use by our wonderful devs.
As for SBF vs fasboot, i dont know exactly the difference but think of them as different types of "recovery" that can be used to fully restore your phone to factory condition.
Click to expand...
Click to collapse
Yes, i mean bootstrapped and you mean woman of the year, right? My bf said the difference between the two is SBF your makinga mirror image of everything and doing a complete system dump and fastboot is just cutting the power for a split sec. It will clear your immediate cache but some memory is still there.

Briteyez83 said:
Yes, i mean bootstrapped and you mean woman of the year, right? My bf said the difference between the two is SBF your makinga mirror image of everything and doing a complete system dump and fastboot is just cutting the power for a split sec. It will clear your immediate cache but some memory is still there.
Click to expand...
Click to collapse
I cant help unless I know what your error message says when you turn on the phone. :/
Sent from my DROID4 using XDA App

Send me your email addy in a message and ill send you a pic of it

Briteyez83 said:
Send me your email addy in a message and ill send you a pic of it
Click to expand...
Click to collapse
Ok, so it's WEBTOP that is behaving badly.
Let me see if I can get an RSD Lite file for you to try. Do you know how to use that?

Hashcode said:
Ok, so it's WEBTOP that is behaving badly.
Let me see if I can get an RSD Lite file for you to try. Do you know how to use that?
Click to expand...
Click to collapse
No, i dont. Im new to root, just rooted in nov. If you give me something thst would fix it that would be awesome.

Unfortunately, the fix isn't exactly a simple one.
It comes in 3 parts (assuming you're on Windows):
1. You'll need to download and install RSD Lite which is what is used to flash the fastboot restore files from Motorola:
http://dev-host.org/ug07spima1mq/RSDLite5.5.rar
2. Download and install the Motorola USB drivers to recognize your phone in fastboot mode:
http://www.mediafire.com/?z5qpc8v3xza25e6
3. I'm setting up a mini WEBTOP fastboot restore file based on the latest RAZR fastboot files (I say small.. but it's still quite a large download). The version is slightly off from the D4's but it might be close enough, and I think it's worth a shot:
[ Getting this file setup will take me about an hour, but you can get steps 1 and 2 ready for now ]
ALSO KEEP THE PHONE POWERED OFF FOR NOW TO SAVE BATTERY. FASTBOOT WILL NOT PROGRAM WITH A LOW BATTERY.

Hashcode said:
Unfortunately, the fix isn't exactly a simple one.
It comes in 3 parts (assuming you're on Windows):
1. You'll need to download and install RSD Lite which is what is used to flash the fastboot restore files from Motorola:
http://dev-host.org/ug07spima1mq/RSDLite5.5.rar
2. Download and install the Motorola USB drivers to recognize your phone in fastboot mode:
http://www.mediafire.com/?z5qpc8v3xza25e6
3. I'm setting up a mini WEBTOP fastboot restore file based on the latest RAZR fastboot files (I say small.. but it's still quite a large download). The version is slightly off from the D4's but it might be close enough, and I think it's worth a shot:
[ Getting this file setup will take me about an hour, but you can get steps 1 and 2 ready for now ]
ALSO KEEP THE PHONE POWERED OFF FOR NOW TO SAVE BATTERY. FASTBOOT WILL NOT PROGRAM WITH A LOW BATTERY.
Click to expand...
Click to collapse
Thank you so much. My bf is leaving his laptop here so that i can do this since he is building the main cpu right now. Ill makev sure i let you know if this works or not after ive finished. I was going to have verizon send me a new one since i just bought my D4 on the 17th and i have 14 days. But i just dont want to risk my warrenty getting voided. Once again thank you.

Briteyez83 said:
Thank you so much. My bf is leaving his laptop here so that i can do this since he is building the main cpu right now. Ill makev sure i let you know if this works or not after ive finished. I was going to have verizon send me a new one since i just bought my D4 on the 17th and i have 14 days. But i just dont want to risk my warrenty getting voided. Once again thank you.
Click to expand...
Click to collapse
If it works, I'll create a new thread with the instructions as I believe there are a few in your situation.

Yes there is quite a few. Ill let you know as soon as i can

[Q] LG Thrill GB w/ClockworkMod Recovery

(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick

Rick Tillery said:
(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick
Click to expand...
Click to collapse
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD

The Dark Lestat said:
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD
Click to expand...
Click to collapse
Thank you for your help!
Rick

Trojan?
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick

There is no virus, Lestat would never do that
Sent from my LG-P925 using XDA

Just my .02 .....Get rid of Symantec !! They are known for scaring people into a virus frenzy.. Yes, it is possible that it is seeing it as a potential virus because shttp is a workaround from the usual porting of windows ip services. ...
Correct me if i'm wrong somebody please !!
Get yourself Comodo and save your money...
Regards,
Dwayne
PS: somebody on here has written a script that just uses shttp temporarily while
your doing the flash procedure, and then reverts your host files back automatically after your done. You should try it.

dwaynedman said:
Just my .02 .....Get rid of Symantec !!
Click to expand...
Click to collapse
Symantec isn't really a choice on work PC.
Get yourself Comodo and save your money...
Click to expand...
Click to collapse
I'm sorry I can't give the link yet, but if you'll Google you'll see Comodo classifies shttp3.exe as "ApplicUnwnt.Win32.ServerWeb.SmallHTTP.~A" or "UnclassifiedMalware" (I guess depending on the version). A number of scanners find issues with shttp3.exe. I'm not saying it is infected, only that it is doing something suspicious.
Rick

Rick Tillery said:
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick
Click to expand...
Click to collapse
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.

Back to square one
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick

The Dark Lestat said:
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.
Click to expand...
Click to collapse
Thank you, sir. I hope it didn't seem accusing.
Rick

Rick Tillery said:
Thank you, sir. I hope it didn't seem accusing.
Rick
Click to expand...
Click to collapse
It's cool, my friend.
Sent from my Samsung Galaxy S II w/ CM9

Rick Tillery said:
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick
Click to expand...
Click to collapse
Is it safe to ignore the su version update?
Short of this, can I override the MD5 checksum? I realize that image could be corrupt, but if I'm just going to replace it with the GB release, does that matter?
Rick

You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne

dwaynedman said:
You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne
Click to expand...
Click to collapse
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick

Rick Tillery said:
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick
Click to expand...
Click to collapse
Remove your battery and keep the phone unplugged
Launch the mobile updater tool
Hold the volume+ button plug the phone in and keep holding the volume+ till the computer downloads the drivers your phone is now in download mode
Once the phone is picked up go to customer support on the LG updater tool and click on recovery phone put your imie number in click check (make sure its the right model) an let the updater tool do its job. Once its done flashing launch into recovery volume- plus power plus 3D button do a complete wipe and factory reset and reboot your phone ... you'll lose cwm and root and be back to full stock
Sent from my LG-P925 using XDA

Bricked?
No joy. Following the steps, the upgrade stopped at 6%. Trying a number of times, it eventually forced me to exit the program (no more restarts). Rerunning the updater (and downloading the 420 MB image yet again on a VERY slow connection) I tried again and again, with different combinations of battery and plug order with power and volume buttons, but nothing worked. Checking elsewhere I found some issues had been reported with Windows Vista/7, so I tried on an XP machine. Now the "Start Updating" bar is red (it was always gray with W7). But now when I try to restore (or even update for that matter), it asks for my S/N (it never did that before) and then says it is "no longer able to upgrade." Reading around, it seems this is an indication of the device being bricked.
Rick

It sounds like you are very close to getting it working Rick.
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Should Rick be trying to run LG Updater as administrator ? I didn't, but it might not hurt.
Regards & Luck,
Dwayne

http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Sent from my ****ty supported LG Thrill

dwaynedman said:
It sounds like you are very close to getting it working Rick.
Click to expand...
Click to collapse
I wouldn't have believed you early this morning, but now maybe...
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Click to expand...
Click to collapse
I tried a bunch of different combinations...none seemed to make the app happy. I finally punted Windows 7 and moved to an XP machine, only to get the "no longer able to update" message. At that point I assumed I was screwed (effectively bricked).
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Click to expand...
Click to collapse
It never really vibrated, but I was able to get back into CMR. Unfortunately NONE of my backups work at all. They all have MD5 checksum failures. I tried a trick I found online and got past that step, only to have it say a failure restoring /system. So much for CMR.
JReeher said:
http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Click to expand...
Click to collapse
Which step? As I mentioned above, I can't even get the first step of the first section (updating the su binary). And if I start at the 3rd section, Symantec prohibits me from using shttp3.exe (I tried to unquarantine it, but it gives a permission error, even as Administrator, when I try to run it), so I'll have to use a different machine.
I was able to reinstall the CM7 3/15 release, so that's something. I was going to restore the stock recovery backup I made, but even that doesn't seem to work. I'm having issue with backups :-(
Rick

i have never been able to restore a backup. i dont know why... but i have tried several times in several different instances.
---------- Post added at 11:56 AM ---------- Previous post was at 11:50 AM ----------
rick tillery, if you want to get your phone back to alive and well i'd suggest doing this:
http://forum.xda-developers.com/showthread.php?t=1558723&page=3
4th post i think

Official Motoblur ICS for the Droid 4 possibly leaked

Just saw this thread at droidforums: http://www.droidforums.net/forum/droid-4-roms/208767-stock-motoblur-ics-droid4.html
Can anyone confirm if this is legit?
EDIT: Removed link to the update file for everyone's safety. This is not an update you want to install. It will take you off the update path and attempting to flash one of the currently available fastboot files will result in a brick.

I pulled the same thing by the cake method earlier today but was afraid to flash a unknown.

I tried, based on the instructions on the page, and as usual, cheesecake won't work for me. I get the "account needed" prompt. I'll try again tomorrow.

Thanks!
I'm downloading it now. I hope this works with Safestrap and I get to keep root. Or at least be able to re-root again. Have to be carefull. Need GSM to work

The day after I sold my T-Mo Sensation, and the day before I get my VZW Droid 4. Looks like the gods have decided not to smite me today.

Booted Safestrap. Flashed stock 215.
Can't update to 219 So no wonder I couldn't update to ICS... Here I go again...

It sounds like a couple of people over on DroidForums HAVE gotten this to load. To paraphrase what hashcode said over there, be very very careful with this guys. There are quite a few Razr owners now stuck outside of the upgrade path and unable to use fastboot to restore after flashing an ICS leak. I think I am going to hold off on this one personally. What I am REALLY hoping to see is some improvements to CM9, AOKP, and Gummy come out of this. Particularly the data issues.

Trying it the Cheesecake way and its downloading. Anyone tried it yet? Curious if Safestrap survived. As long as it works I'll be glad. Hope the different baseband fixed audio over UMTS/HSDPA.

Die Bruine said:
Trying it the Cheesecake way and its downloading. Anyone tried it yet? Curious if Safestrap survived. As long as it works I'll be glad. Hope the different baseband fixed audio over UMTS/HSDPA.
Click to expand...
Click to collapse
You are a brave man Try using OTA RootKeeper. It worked with the last update. I would be very interested to see if it works with the ICS update as well.

Ok guys, I installed it. Voodoo OTA RootKeeper did NOT work for me, and attempting to flash the 6.13.219 fastboot file resulted in a brick.
I would strongly advise not installing this update.

SGMD1 said:
Ok guys, I installed it. Voodoo OTA RootKeeper did NOT work for me, and attempting to flash the 6.13.219 fastboot file resulted in a brick.
I would strongly advise not installing this update.
Click to expand...
Click to collapse
Really sorry to hear that. Thanks so much for the information though. Did you try the .215 fastboot file? I'm guessing the result would be the same but might be worth a shot.

Can you tell us why you tried to install the fastboot file? You didn't like ICS or is it because of root priviliges? I've tried like 15 times. It just won't update. So now I temp unrooted, uninstalled Safestrap and hope for the best. Next step woul be to fastboot 219 and try on a fresh clean install. The only thing I can think of is that my build.prop gets in the way. Anyone mind posting a stock .219 build.prop?
XDA app on XT894

kwyrt said:
Really sorry to hear that. Thanks so much for the information though. Did you try the .215 fastboot file? I'm guessing the result would be the same but might be worth a shot.
Click to expand...
Click to collapse
Downloading .215 as we speak, but I'm not getting my hopes up. No big deal though, VZW is overnighting me a warranty replacement and I've got an old phone I'm using for the day.
EDIT: .215 failed at 6/18 as well.
Die Bruine said:
Can you tell us why you tried to install the fastboot file? You didn't like ICS or is it because of root priviliges? I've tried like 15 times. It just won't update. So now I temp unrooted, uninstalled Safestrap and hope for the best. Next step woul be to fastboot 219 and try on a fresh clean install. The only thing I can think of is that my build.prop gets in the way. Anyone mind posting a stock .219 build.prop?
Click to expand...
Click to collapse
There were a several things with this ICS build that were a bit disappointing (native ICS screenshot function didn't work, no "Charge only" mode when connected via USB to PC) but no root access was the dealbreaker. I knew flashing the .219 file was a risk based on what happened with the RAZR ICS leaks but I just figured I'd be the guinea pig
I had the same problem you did when attempting to install it, so I flashed the clean .219 fastboot file and then the ICS update was successful.

build.prop
Die Bruine said:
Can you tell us why you tried to install the fastboot file? You didn't like ICS or is it because of root priviliges? I've tried like 15 times. It just won't update. So now I temp unrooted, uninstalled Safestrap and hope for the best. Next step woul be to fastboot 219 and try on a fresh clean install. The only thing I can think of is that my build.prop gets in the way. Anyone mind posting a stock .219 build.prop?
XDA app on XT894
Click to expand...
Click to collapse
Here is the build.prop file... it is compressed into a zip archive since .prop cannot be attached.
****EDIT: THIS IS THE .215 build.prop

build.prop 219
rumgool said:
Here is the build.prop file... it is compressed into a zip archive since .prop cannot be attached.
****EDIT: THIS IS THE .215 build.prop
Click to expand...
Click to collapse
Okay... here is the 219 build.prop zipped

You gotta be kidding me pffffff. Those guys at Motorola check eeeeeeverything. Thnaks for the build.prop btw rumgool. But now it hangs on Motorola_XT894....3gp. Unbelievable...
Finally got it going. But like you said, had to flash SBF. That's some pretty scary **** . I'm used to Milestone / Droid 1 flashing and I've flashed a Razr before. This one takes twice as long. So for you wanting to flash SBF, don't be alarmed. It takes a while, a very loooong while.

Question: Why would the update prevent flashing via fastboot? I'm only familiar with SBFs, but the point of those were that no matter how bad things got, you could wipe everything out and start over. Is that no longer the case

GSM working!!!!!!
Yes!!!! audio over 3G GSM!!!!
Finally. Don't know what works and what doesn't. But audio works and you have GSM settings right from the get go. Now I'm gonna eat, then I'm gonna play and after that I'll tell you what I think of it.
Thanks guys!

podspi said:
Question: Why would the update prevent flashing via fastboot? I'm only familiar with SBFs, but the point of those were that no matter how bad things got, you could wipe everything out and start over. Is that no longer the case
Click to expand...
Click to collapse
The new fastboot files are nothing like the old sbf's. Wrong radio, different build number and many other things can cause it to fail. Then your stuck in fastboot mode with a soft brick.
Sent from my DROID4 using Tapatalk

This is a really nice build! I am not at all sorry to have risked being stuck, to be honest.
Everything appears to work very well so far and I am posting from Chrome Beta.
Still looking for the downside...

Update from zip aborted

In an attempt to go from ICS 206 to 215, I followed the instructions step by step and using the utility, when I get to the step where it says instill zip file from SD card, I navigate to "D4.6.16.215.zip", apply it, and it says update aborted.
My phone will now no longer boot beyond the M Dual Core screen. It is simply blank. Does anyone have any ideas?

i was about 5mins away from doing the same thing you did before glad i saw this gonna, i'm gonna wait until you find a fix (im on .213)

icebear8 said:
i was about 5mins away from doing the same thing you did before glad i saw this gonna, i'm gonna wait until you find a fix (im on .213)
Click to expand...
Click to collapse
Well I'm back working again, but it's still on 206 even though I went through the flashing process to 215. I haven't even thought about updating my phone since installing 206 when it came out. I have read many threads that talk about "unsticking" to get from 206 to 208, but they're over a month old. I can't follow the instructions associated with unsticking because a) they're written for the razr and thus are ridiculously confusing, and b) the one thread that tries to explain how to use unstuckICS for D4 users makes even less sense.
I posted about where to get unstuckICS on another forum and someone directed me back to the Droid4withICSfix-rootLITE tool, which I already had. Step 16 seems to flash (with a TON of error that are supposedly to be expected) but then I can't apply any zip updates. All attempts abort.
This is all so maddening because nothing I try is working. At least my phone isn't a paper weigh. So I have that going for me... which is nice.

strakajagr said:
Well I'm back working again, but it's still on 206 even though I went through the flashing process to 215. I haven't even thought about updating my phone since installing 206 when it came out. I have read many threads that talk about "unsticking" to get from 206 to 208, but they're over a month old. I can't follow the instructions associated with unsticking because a) they're written for the razr and thus are ridiculously confusing, and b) the one thread that tries to explain how to use unstuckICS for D4 users makes even less sense.
I posted about where to get unstuckICS on another forum and someone directed me back to the Droid4withICSfix-rootLITE tool, which I already had. Step 16 seems to flash (with a TON of error that are supposedly to be expected) but then I can't apply any zip updates. All attempts abort.
This is all so maddening because nothing I try is working. At least my phone isn't a paper weigh. So I have that going for me... which is nice.
Click to expand...
Click to collapse
Literally the tool does nothing. I run it. Everything in step 16 essentially errors out. Ultimately the phone reboots having accomplished zero. I am "stuck" on 206.

strakajagr said:
Literally the tool does nothing. I run it. Everything in step 16 essentially errors out. Ultimately the phone reboots having accomplished zero. I am "stuck" on 206.
Click to expand...
Click to collapse
here is a boot.img i got from Droid forums https://www.dropbox.com/s/zwl0e6jx767aksb/boot-6-16-215.img try using this one and rename it to ICSFIX

icebear8 said:
here is a boot.img i got from Droid forums https://www.dropbox.com/s/zwl0e6jx767aksb/boot-6-16-215.img try using this one and rename it to ICSFIX
Click to expand...
Click to collapse
Tried that. Same result. I have to believe this has something to do with the 206 build that I'm on, though I don't know why that latest utility doesn't address this since the 206 sticking thing seems to be a problem that was addressed so long ago.

\how did you get back to normal when you soft bricked? so i know i can get back if i get the same problem. i might try this just to see if it works for me
---------- Post added at 12:34 AM ---------- Previous post was at 12:22 AM ----------
icebear8 said:
\how did you get back to normal when you soft bricked? so i know i can get back if i get the same problem. i might try this just to see if it works for me
Click to expand...
Click to collapse
VRZ_XT894_6.5.1-167_DR4-1_M1-219_1FF_01.xml.zip this is the fastboot GB 219 files correct? my files are all over the place lol

I just booted to recovery and did a data wipe/factory reset, and I was back to stock 206. I didn't use that xml file because I'm not upgrading from GB.

well i just bricked my self on the update lol

Not sure why you guys are having trouble. I used the tool yesterday to go from 213 to 215. Basically we are flashing the GB files, then the boot.img for 215, letting it reboot and attempt to update, it will stick at the moto boot logo, then flashing the update in stock recovery. The only thing that might be of issue is if you are running safestrap, menu 16 is designed to not over write your data. I haven't tried running safestrap and using menu 16 to update. You can try the old method of flashing the GB files, Flashing the boot.img and then recovery update flash.

jsnweitzel said:
Not sure why you guys are having trouble. I used the tool yesterday to go from 213 to 215. Basically we are flashing the GB files, then the boot.img for 215, letting it reboot and attempt to update, it will stick at the moto boot logo, then flashing the update in stock recovery. The only thing that might be of issue is if you are running safestrap, menu 16 is designed to not over write your data. I haven't tried running safestrap and using menu 16 to update. You can try the old method of flashing the GB files, Flashing the boot.img and then recovery update flash.
Click to expand...
Click to collapse
In terms of names - are you using boot.img or ICSFIX.img for the name of boot on .215?

Right, but you're not dealing with upgrading from 206, which is supposedly the pain in the ass build to upgrade from.

strakajagr said:
Right, but you're not dealing with upgrading from 206, which is supposedly the pain in the ass build to upgrade from.
Click to expand...
Click to collapse
I`m going to update from 213 to 215, and still need an anwer: ICFIX.img or boot.img?
Thanks in advance.

mrAdvo said:
I`m going to update from 213 to 215, and still need an anwer: ICFIX.img or boot.img?
Thanks in advance.
Click to expand...
Click to collapse
You should be able to rename to boot.img and upgrade from .213 to .215. As for the .206 upgrade you may have to follow the full upgrade process outlined in the ics upgrade thread in which you have to flash the gb fastboot before upgrading to the next build. It seems to have worked for most people going from leak to leak.
Sent from my DROID4 using xda app-developers app

If your using the modified D4 tool I made then you should name it ICSFIX. However I think we can shorten the process further and will try to work on that tonight.
Sent from my DROID4 using Tapatalk 2

azrael293 said:
You should be able to rename to boot.img and upgrade from .213 to .215. As for the .206 upgrade you may have to follow the full upgrade process outlined in the ics upgrade thread in which you have to flash the gb fastboot before upgrading to the next build. It seems to have worked for most people going from leak to leak.
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Wait, are you saying that you can just flash the boot.img without having to fastboot GB?! Cause if that is the case, I wasted a ton of time last night going from 213 --> 215

podspi said:
Wait, are you saying that you can just flash the boot.img without having to fastboot GB?! Cause if that is the case, I wasted a ton of time last night going from 213 --> 215
Click to expand...
Click to collapse
Going by the tool you would have to flash the fastboot of the GB files then proceed to flash the current leak. Same as with all the previous leaks. What I meant by flashing it as boot.img is that name format should work, tho jsnweitzel said that with his tool it should be named as icsfix.img instead. he replied right after I had posted and I'd go with his response since it is his code/tool. lol

azrael293 said:
Going by the tool you would have to flash the fastboot of the GB files then proceed to flash the current leak. Same as with all the previous leaks. What I meant by flashing it as boot.img is that name format should work, tho jsnweitzel said that with his tool it should be named as icsfix.img instead. he replied right after I had posted and I'd go with his response since it is his code/tool. lol
Click to expand...
Click to collapse
Ok, I was just afraid for a moment I had wasted a bunch of nail-biting time or something
I think a lot of people get tripped up at the boot.img --> ICSFIX.img step. Especially because the instructions tell you to rename it to ICSFIX, not ICSFIX.img (which Windows may or may not do for you automatically, depending on your settings).
That being said, it is still incredibly easy to move from one leak to the other with the utility, it is incredibly awesome.(Thanks jsnweitzel!)