Related
Before I do anything else to screw this up!
I'm sitting at an exclamation in a triangle
here what I did..
1. installed stock/rooted rom
2. used clean flash to put on stock recovery
3. ran OTA Keeper to back up root
4. downloaded and started OTA update
it then rebooted and began but then Red Exclamation In A Triangle
anyone know where I should go or what I should do from here?
Thanks.
If your pc detects the phone- you'll prob have to do an ruu.exe to get it totally stock and then start over.. I did it earlier but I was having a diff problem (stuck in hboot)-- never got triangle/exclamation. I used the ruu from scottsroms (1.02.605.6).
yeah ok... I'll look into that. I haven't turned it back on yet.. Thanks
Just realized i forgot to "un-root" with the OTAKeeper app... I'm hoping that's what I did wrong. It booted back to where i was and said the update failed. So... I'm a tryin' again.
Thanks for the reply.. One can feel soooo alone when making mistakes
There's some other information in the OTA threads in "general" of others that have had the red triangle and were able to work around it.. I didn't read the specifics but check in there.
das0527 said:
7. Enjoy OTAed, unlocked, rooted kickassness of my Rezound while bouncing off the walls waiting for ICS.
Click to expand...
Click to collapse
Why wait?
I'm going to run through those steps later and check out the other threads. I'm able to get back to my phone as the update looks to of just been aborted....
If you guys don't have wives, keep it that way, I want to work on this all day but...... so I'll check in later and post how it goes. I don't see why those steps won't work though... Thanks a ton guys.
I planned on waiting until the official build of ICS & Sense is released OTA, especially after today's news about the new features in Sense 4.0, which I'm actually extremely impressed with.
Cool- well I'm sure you've already read elsewhere- but you can't really go wrong w/ any of the custom ics roms in the dev section. If you can handle a very occasional screen flicker every once in a while they're pretty much perfect.
reggie cheeks said:
Before I do anything else to screw this up!
I'm sitting at an exclamation in a triangle
here what I did..
1. installed stock/rooted rom
2. used clean flash to put on stock recovery
3. ran OTA Keeper to back up root
4. downloaded and started OTA update
it then rebooted and began but then Red Exclamation In A Triangle
anyone know where I should go or what I should do from here?
Thanks.
Click to expand...
Click to collapse
Did you lock the bootloader?
Sent from my ADR6425LVW using xda premium
No. I didn't. That was my mistake. Dumb of me. I'm gonna do the ruu and start over later, I'm out n about.
Sent from my ADR6425LVW using Tapatalk
Why lock the bootloader? There are a bunch of us who were able to successfully OTA without doing so. My radios are all updated as well as the OS. If you debloated, you need to reenable the bloat prior. No need to unroot either.
esheesle said:
Why lock the bootloader? There are a bunch of us who were able to successfully OTA without doing so. My radios are all updated as well as the OS. If you debloated, you need to reenable the bloat prior. No need to unroot either.
Click to expand...
Click to collapse
Had Ineffabilis from 12/29, was great, put Clean ICS on it from 1/24, worked well except for the bluetooth pain in the patookie. (and I use bluetooth ALOT)...
I flashed back to GB, I have Team Bamf on mine right now because it included the kernel. I am getting ready to put clean rom on it with the new main ver but I would like to put the new radio's on it first.
Can I put the new radio's on it without going through the steps above (flash stock, re lock, ruu, ota update, unlock, flash, etc) and if so how?
Thanks!
Figured it out. Gonna make a post.
esheesle said:
Why lock the bootloader? There are a bunch of us who were able to successfully OTA without doing so. My radios are all updated as well as the OS. If you debloated, you need to reenable the bloat prior. No need to unroot either.
Click to expand...
Click to collapse
Right now I'm on Vigor Stock Rooted WWE 1.02.605.6 Deodexed . That's my mistake, right? I've got all the bloat.
Sent from my ADR6425LVW using Tapatalk
It's possible the deodexed part of it is the problem.
Do you have a nandroid made from right after you flashed Amon Ra recovery? Also, did you flash a stock recovery or do you still have Amon Ra? It won't work unless you have stock recovery.
If you don't have a nand, you can either run RUU (if you don't have the updated mainver issue) or have a look in this thread:
http://forum.xda-developers.com/showthread.php?t=1467329
con247 has made a stock ROM with the OTA in it so you don't have to download the update.
There aren't any instructions on what to do with the file you download and I didn't use his method so I can't really help but hopefully you'll get it. I don't remember it being spelled out in the thread anywhere which is why I decided it was just as easy for me to use my nand and flash a stock kernel and recovery and download it myself.
I had stock recovery and kernel at the time I ran the update. I've since went back to amon and I've downloaded vigor ota stock rooted and I was about to try that.
Oh and...I'm pretty sure my earliest back up was not my original, I think I made the mistake of flashing a Rom before my first backup
I do however really wish I had some instructions for the vigorotastockrooted.
& one last thing.. Ive never had mainver update.
Sent from my ADR6425LVW using Tapatalk
Yeah, I wish there were instructions for that stock + OTA too.
The OTA will update your mainver but to the official release that is in the OTA. Just so you know, I can now not flash the dbs kernel I was using before because I'm getting a "mainver is older" message.
I was trying to reflash kernels because my wifi is not working now, when I select "turn on wifi" that changes to "error". I had restored my nand of the Innedfabilis ROM I made right before reverting to stock and updating with the OTA. Just mentioning it since I'm posting here to try to help you and I guess it's just full disclosure.
Hmm. I'm thinking of sticking pre-ota as well, at least until I feel more confident about it. Thanks
Edit.... I ended up using con's vigorOta and xtreme tools (for simpler lock/relock) to update . Thanks for the help/insight!
Sent from my ADR6425LVW using Tapatalk
Hello everyone. I recently purchased the Rezound to test it out and see if I liked it. I have made the decision to send it back and keep my upgrade. I restored a nandroid backup that I made of stock rooted. I thought I was golden and would only need to remove the root apps and re-lock the phone. I went to turn the wifi on and received the "error". I've tried the steps at this link (http://forum.xda-developers.com/showpost.php?p=21442702&postcount=3) but I cannot get into recovery to do steps 1 through 3 first. My update to 2.01.605.11 happened immediately once I activated the phone so I am on the newest version.
Is there a way I can get my phone back to 100% stock out of the box? I understand that it will show as "re-locked", but from what I have read that wont be a problem when I return it. I came from the Droid X2 where we could SBF back to stock through RSD.
I should have known better than to begin rooting and modding before I was sure I was going to keep the phone.
Thank you all in advance for your help with this and I hope you all have a blessed day.
Romans8vs1 said:
Hello everyone. I recently purchased the Rezound to test it out and see if I liked it. I have made the decision to send it back and keep my upgrade. I restored a nandroid backup that I made of stock rooted. I thought I was golden and would only need to remove the root apps and re-lock the phone. I went to turn the wifi on and received the "error". I've tried the steps at this link (http://forum.xda-developers.com/showpost.php?p=21442702&postcount=3) but I cannot get into recovery to do steps 1 through 3 first. My update to 2.01.605.11 happened immediately once I activated the phone so I am on the newest version.
Is there a way I can get my phone back to 100% stock out of the box? I understand that it will show as "re-locked", but from what I have read that wont be a problem when I return it. I came from the Droid X2 where we could SBF back to stock through RSD.
I should have known better than to begin rooting and modding before I was sure I was going to keep the phone.
Thank you all in advance for your help with this and I hope you all have a blessed day.
Click to expand...
Click to collapse
The RUU is the closest we have to SBF. Can you do a battery pull and get into HBOOT? If so then you can still run the RUU after you deal with the mainver problem. http://forum.xda-developers.com/showthread.php?t=1467099
Here is the stock rooted rom. If you dont want to mess with the mainver and ruu.
http://forum.xda-developers.com/showthread.php?t=1467329
Thanks guys. I kept fooling with my phone while waiting on your replies. I now have followed steps 1 and 2 in the link I provided above. I formatted my system in recovery as it stated. I am now in recovery but cannot select either of my two nandroid backups. I'm afraid to shut down or reboot. What now?
I'm ready to go back to my X2 where I know what I am doing!
Romans8vs1 said:
Thanks guys. I kept fooling with my phone while waiting on your replies. I now have followed steps 1 and 2 in the link I provided above. I formatted my system in recovery as it stated. I am now in recovery but cannot select either of my two nandroid backups. I'm afraid to shut down or reboot. What now?
I'm ready to go back to my X2 where I know what I am doing!
Click to expand...
Click to collapse
In the Vigor rom collection on the development selection they now have posted the most recent RUU based on the OTA so you can flash that and you will be back to stock. Just have to be relocked and on stock recovery.
I'm not sure if I'm the only one who is having this problem but I've searched around and can't fix the issue. I recently had CM9 but went back to complete stock, on 2.3.4 (which isn't up to date). When I go to update from the settings menu, I get a communication failed text box, which then in turn makes me wait 24 hours before checking again.
I've done multiple battery pulls and stopped the running process for the software update to no avail. Can anyone help me with this?
Remember, I'm on the stock AT&T rom.
Sent from my SAMSUNG-SGH-I777 using XDA
myownwitness said:
I'm not sure if I'm the only one who is having this problem but I've searched around and can't fix the issue. I recently had CM9 but went back to complete stock, on 2.3.4 (which isn't up to date). When I go to update from the settings menu, I get a communication failed text box, which then in turn makes me wait 24 hours before checking again.
I've done multiple battery pulls and stopped the running process for the software update to no avail. Can anyone help me with this?
Remember, I'm on the stock AT&T rom.
Sent from my SAMSUNG-SGH-I777 using XDA
Click to expand...
Click to collapse
Are you rooted? And why update to 2.3.6 uckk6? Its got a few really bad bugs.
Sent from my SGH-I777 using XDA App
Not rooted. I just want to get my phone up to date so when the ICS update rolls out I'll be able to get it.
Sent from my SAMSUNG-SGH-I777 using XDA
myownwitness said:
Not rooted. I just want to get my phone up to date so when the ICS update rolls out I'll be able to get it.
Sent from my SAMSUNG-SGH-I777 using XDA
Click to expand...
Click to collapse
If*
Sent from my SGH-I777 using XDA App
Thank you for your helpful information.
Sent from my SAMSUNG-SGH-I777 using XDA
I think others were having trouble updating as well... I'd suggest flashing a custom rom, or if you want to stay with stock, using Entropy's Back to Stock packages (I'm not going to link that for you cause I'm too lazy and you should be able to find it.)
jcracken said:
I think others were having trouble updating as well... I'd suggest flashing a custom rom, or if you want to stay with stock, using Entropy's Back to Stock packages (I'm not going to link that for you cause I'm too lazy and you should be able to find it.)
Click to expand...
Click to collapse
Might give it a try. Trouble is, not having a rooted phone and going back to stock means I lose all applications and data with them. Eh. Thanks
Download stock rom (if u can get a tar file it most likely has everything u need, do some Googling just make sure its for the i777). Get mobile odin pro. Use mobile odin pro to flash the .tar and it gives u the option to root right there within the app before u flash. Profit. Just giving my two cents and what worked for me . If u do this though and don't remove any system apps it should allow u to ota upgrade. Haven't tried myself but that sounds like it'd work fine.
Sent from my GT-I9100 using Tapatalk
Phalanx7621 said:
Download stock rom (if u can get a tar file it most likely has everything u need, do some Googling just make sure its for the i777). Get mobile odin pro. Use mobile odin pro to flash the .tar and it gives u the option to root right there within the app before u flash. Profit. Just giving my two cents and what worked for me . If u do this though and don't remove any system apps it should allow u to ota upgrade. Haven't tried myself but that sounds like it'd work fine.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I already did this except for rooting about 3 weeks ago. From what you're saying, if I root my phone from its current state I should be able to receive OTA updates? I'm willing to root just to see but I don't see how that would fix the "communication failed" errors for updates.
Sent from my SAMSUNG-SGH-I777 using XDA
FYI I have a rooted stock ROM, and I'm having difficulty doing an OTA update also. Different error (mine is "interrupted" after reboot). I posted it here because it seemed more related to that thread and I had other Q's about the process.
You guys are in panic mode, wait till we actually get an ANNOUNCEMENT for ICS from AT&T, then try to go back to stock using the methods we have.
No reason to do so right now, since AT&T will probably take a long time before pushing it.
We have a possible sources dropping on March 15th from i9100 but you will be required to be rooted to flash the possible ICS Roms that will be available after that date.
LiLChris06 said:
You guys are in panic mode, wait till we actually get an ANNOUNCEMENT for ICS from AT&T, then try to go back to stock using the methods we have.
No reason to do so right now, since AT&T will probably take a long time before pushing it.
We have a possible sources dropping on March 15th from i9100 but you will be required to be rooted to flash the possible ICS Roms that will be available after that date.
Click to expand...
Click to collapse
I don't think you understand. First of all, in no way am I in panic mode. Secondly, my phone is a few updates behind since I just recently brought it back to stock from CM7. All I am trying to do is bring it up to date.
Sent from my SAMSUNG-SGH-I777 using XDA
ota issue
You might want to check the (Guide)How to flash custom binaries.....on this forum. Creepycrawly has posted a reply towards the end of the thread that might be helpful. Believe its on one of the last two pages.
As has been said many times in other threads, even on a stock ROM if you have rooted and removed even one item of bloatware or made any other mods you will not be able to download an OTA update.
I have not rooted my phone. And as I said earlier, I restored my phone to complete stock meaning no bloatware has been removed. I'm still at a loss for what to do
Sent from my SAMSUNG-SGH-I777 using XDA
You were on CM9 (in a later post you say CM7), but you went back to stock UCKH7. Now you are unable to update over the air to UCKK6. You are mainly interested in having the phone ready to receive the update over the air to ICS, whenever that occurs. You have not rooted the phone since you returned to stock but you are willing to try root if it will help the update happen. You were also concerned about loosing apps and their data since you are not rooted. I recapped all this because on stock you should be able to run the update. To help you solve the problem, need to know all the facts.
I've done the following, although it has been several months ago, about a week or two after UCKK6 first released. From running a custom rom, I did a wipe data/factory reset, flashed stock UCKH7 plus root, and ran the over the air update to UCKK6 successfully, retaining root on UCKK6. I just did this to test it out, so after completing the test, I used my nandroid backup to return to the custom rom I was on.
I would assume that you did a wipe data/factory reset either before or after you flashed back to stock? If not, there could be traces left over that could interfere with the update process. I'm not sure if there could be traces left even after a wipe data/factory reset, but the Cyanogen Mod file structure is so very different than stock that it wouldn't be inconceivable.
Next, I would wonder how soon after flashing back to stock you tried to run the update, and if not immediately, what action could have possibly placed or removed files that would intefere with the process.
I'm pretty certain that if you were to wipe data/factory reset with a format and then flash stock again, and then try to run the update immediately, it would succeed. So there has to be something in the file system preventing it. You may not find it easy to correct that something manually. You may just have to do a wipe data/factory reset, and maybe a format, and then start all over with a fresh install.
Of course, that is the reason for rooting first. Root, then back up everything with titanium backup, SMS backup, export contacts, etc. and save all that to your computer. Then you can restore stuff after.
Thanks creepy,
I'm in the process of doing what you said. I rooted my phone, backed up everything I thought needs to be backed up and flashed the stock rom (2.3.4 kernel version 2.6.35.7 baseband version I777UCKH7). I still need to do a factory format in order to see if that will fix the update problem.
Question. Is the firmware version(s) above the latest AT&T software? According to Kies, it is. But I am reading other places that the latest software is android 2.3.6.
Did exactly as creepy stated. Brought the phone back to stock software and did a factory reset. Without ANY customization and as soon as the phone booted up, I did the software update and had the same thing, "Communication failed" (says there is an update available but servers are busy).
I give up.
Well, I don't have any new ideas. Maybe if I get some time in the next few days I'll try it on my phone to see what happens. It has been a while since I tried it. Maybe the server behaves differently now?
creepyncrawly said:
Well, I don't have any new ideas. Maybe if I get some time in the next few days I'll try it on my phone to see what happens. It has been a while since I tried it. Maybe the server behaves differently now?
Click to expand...
Click to collapse
From what I've been reading on AT&T forums (http://forums.att.com/t5/Samsung/Sa...2-3-6-OTA-update-now-live/td-p/2996495/page/3) I don't think so. I've been trying every combination I can think of to make this thing work but I honestly have no idea. I was extremely surprised when I brought the phone back to complete stock and no root and still couldn't get the update.
If ICS ever comes to AT&T GS2, I'll wait a month or so to keep trying then I might resort to going to an AT&T store to get a replacement. Who knows
I figured I would try out some of these custom roms and so far it's not a good experience lol, so I have safestrap..enabled it and flashed the rom. When I go back to toggle it to go back to stock it gives a error when it restores data or something like that.
I made a backup so if I can just go back to stock .181 and then I'll restore that backup.
Any help on what I need to do? I finally got it to boot into Gummy but the data was not connecting, just trying to go back to where I was with the stock OS.
Thanks in advance
try matt l groffs droid razr utilty,you can find it on xda,i had done something wrong when i rooted my razr so when .181 came out the ota kept failing until i downloaded the utility,it returned my phone to stock .173 then i got the update to .181.you can also root with the utility,good luck!
collins521 said:
I figured I would try out some of these custom roms and so far it's not a good experience lol, so I have safestrap..enabled it and flashed the rom. When I go back to toggle it to go back to stock it gives a error when it restores data or something like that.
I made a backup so if I can just go back to stock .181 and then I'll restore that backup.
Any help on what I need to do? I finally got it to boot into Gummy but the data was not connecting, just trying to go back to where I was with the stock OS.
Thanks in advance
Click to expand...
Click to collapse
I'm not exactly sure this will work, but try quickly toggling to the unsafe system and restoring the backup. If that doesn't work you'll have to fastboot back to .181 with Matllgroff's Utility or RSD Lite.
Sent from my DROID RAZR using XDA
I got Gummy to finally grab internet but can't get it to toggle back to non safe or whatever you call it. I'm not apposed to going back to stock via RSD but just wished there were a less time consuming process lol
collins521 said:
I got Gummy to finally grab internet but can't get it to toggle back to non safe or whatever you call it. I'm not apposed to going back to stock via RSD but just wished there were a less time consuming process lol
Click to expand...
Click to collapse
I'm not sure you know what I mean.
Step 1. Boot into Safestrap
Step 2. Go in to "safe boot menu"
Step 3. Select "Quick Toggle Safe System Dangerous"
Step 4. Restore your nandroid backup.
The downside of this is that you'll have to reinstall Gummy next time if you want to use it again.
Hope I helped.
Ya reinstalling isn't a big deal, when I said I finally got Gummy to grab internet I mean it finally connected to the web
Sent from my DROIDRAZR using XDA
Is this common? Happened to me last nite and could never get y data to restore so I could disable safestrap. Had to use Matts 1.7 utility http://www.droidrzr.com/index.php/t...y-17-for-ics-and-those-who-want-to-go-to-ics/ to get back to ICS 6.16.211. Wish I would have found this post first.
Thanks!
Please I need answers to this issue, not people blaming me for being such a noob. I reprogrammed a Verizon Droid Razr for my colleague here in Nigeria, we both work for a CDMA network. The phone was fine, voice, text and data working until yesterday he told me the phone lost network. I asked him what happened before then and he told me he did an update (the ICS update), so everything went back to Verizon defaults and I needed to reprogram again. I got to reprogram it today but there was no data so I figured I would go back to GB 6.12.181 which the phone was on before the update. I chose DroidRAZR Utility 1.6 which I have on my laptop to do the job. After this my woes began. The phone now stops at the Motorola logo and after that goes blank. I tried again but it was the same response, and I discovered that the recovery changed too, and where I should hit both volume buttons to get the option to wipe all I see is automatic update inside recovery. I tried to remove the sdcard, but I guess the update file he received is in the internal storage. How can I get the phone working again, whether on ICS or GB, whichever would work. Or do we have a total brick? Please I need urgent answers. Thank you all.
Pls people, Help Me!
After Upgrading to ICS you CANNOT downgrade back to 2.3 again, part of ICS does NOT allow downgrading, if its CDMA and you can get to bootstrap you could flash the ROM again, use the sdcard in another device to copy the rom, but it MUST be ICS you CANNOT install GB anymore
lashton said:
After Upgrading to ICS you CANNOT downgrade back to 2.3 again, part of ICS does NOT allow downgrading, if its CDMA and you can get to bootstrap you could flash the ROM again, use the sdcard in another device to copy the rom, but it MUST be ICS you CANNOT install GB anymore
Click to expand...
Click to collapse
Thanks for your reply lashton. Please can you point me to a guide on how I can restore the phone to ICS. It is stuck on Invalid Flash Mode now and the battery is low, but I want to make a factory cable to use tomorrow and see if I can get the phone working again. I just need to know this is possible to restore to ICS.
Thanks.
What you have is soft brick. And yes you will be able to go back to ics but now gingerbread. Look online there are plenty of people that have soft bricked their phones thinking they could just go back to GB. Lol including me. Happy digging! =)
Sent from my DROID RAZR using xda app-developers app
Chuckleb0ne said:
What you have is soft brick. And yes you will be able to go back to ics but now gingerbread. Look online there are plenty of people that have soft bricked their phones thinking they could just go back to GB. Lol including me. Happy digging! =)
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
Please dear sir Chuckleb0ne, kindly guide me on how to do this since you have experienced it before. I have only till tomorrow to get this working as the phone has my friend's official company line on it, he must be able to use it for calls tomorrow. Down on my knees, tears streaming down my eyes... pleading for help...
OK. I managed to construct a factory cable and it supplied power to the phone, so far so good. I tried to use Droid Utility 1.7 to unbrick (option 2) but it didn't work, I mean the fastboot flash went through but I still cannot go further than the Invalid Flash Mode screen, no matter what. I can't even go into recovery. That's a major issue, I think. If I could get into recovery I could sideload the ICS zip I copied on the sdcard with the Utility tool. I next tried option 1, which is Prepare for sideloading ICS on any GB. It didn't work either. Please people, what next before I go crazy. We do not have Verizon here so their support is out of the question, or even returning the phone. I must fix this, with your help, because I have run out of ideas here. Help needed!
Try to boot through BP Tools. The phone must be unplugged. If you can reboot that way then just rewrite the boot .img, I want to say its option 9? Kinda sounds like what happened with my phone, but after I saw the dead android with the door open I believe I could still get into stock recovery and side load .211.
Guys, I got it back on. I used DroidRazr Utility 1.6, 1.7 and this file - Blur_Version.6.12.181.XT912.Verizon.en.US.zip, all three in combination. the blur file on my sdcard, fastboot restore to 181 with Utility 1.6, move into recovery, wipe data and cache, fastboot 211 boot.img from Utility 1.7, back to recovery, flash the blur file on sdcard... ladies and gentlemen, we have a working Droid RAZR on ICS 211. Happy mode activated...
Nice job ezeuba! I'm trying to find a way to get my RAZR back to GB because I HATE ICS. I've been using it for 2 days and I want to smash my phone. I keep finding people saying that it is not possible, although I have found 1 or 2 references stating that it may be possible but is very risky. I am willing to take any risk at this point as my phone is pretty much useless to me now anyway and it is at very high risk of being utterly destroyed. It amazes me how fast you can go from love to hate with a device. This fiasco reminds me of the day I "upgraded" from Windows XP to Vista. At least Microsoft left me the option to go back...
Question: When you did "fastboot restore to 181 with Utility 1.6", were you back to a working GB 181? Were you forced to move "up" to ICS or was it your choice? Thanks in advance for any information!
See! Once you do a little digging you come up with a solution. And now you probably feel incredible for doing it yourself.
Sent from my DROID RAZR using xda app-developers app
emsjo said:
Nice job ezeuba! I'm trying to find a way to get my RAZR back to GB because I HATE ICS. I've been using it for 2 days and I want to smash my phone. I keep finding people saying that it is not possible, although I have found 1 or 2 references stating that it may be possible but is very risky. I am willing to take any risk at this point as my phone is pretty much useless to me now anyway and it is at very high risk of being utterly destroyed. It amazes me how fast you can go from love to hate with a device. This fiasco reminds me of the day I "upgraded" from Windows XP to Vista. At least Microsoft left me the option to go back...
Question: When you did "fastboot restore to 181 with Utility 1.6", were you back to a working GB 181? Were you forced to move "up" to ICS or was it your choice? Thanks in advance for any information!
Click to expand...
Click to collapse
To answer your question first, no I didn't have a choice to stay on Gb or move up to ICS. I only did fastboot to 181 with Utility 1.6 in order for the phone to even boot up to recovery. Prior to that I only had "Invalid Flash Mode" error, no recovery, nothing. So, after fastbooting 181 I got to recovery, wiped data and cache, went back to Utility, 1.7 this time, and flashed boot.img for 211, then went back into recovery and sideloaded the downloaded 211 update file on my sdcard. After that could I get full boot to ICS on the phone. No need dreaming of reverting back to GB, it's not possible, at least for now with a locked bootloader.
Chuckleb0ne said:
See! Once you do a little digging you come up with a solution. And now you probably feel incredible for doing it yourself.
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
You are right. Nothing a bit of research would not solve, if you are really determined to get it to work. It was your assurance that it was certain to work that fired me up. I was afraid the phone was dead and about to be buried.
Thanks.
Thanks ezeuba! Fortunately ICS is starting to grow on me. I was able to load the old Gmail app which was my main issue and find some other workarounds for various other issues.