DOWNLOAD AND INSTALL AT YOUR OWN RISK.
This will temporarily disable Safestrap, but once appled, you can restore Safestrap, and your previous Safe system should still be intact.
This is the Motorola update that is being soak tested. To install it, I unfroze all apps, used Voodoo Root Keeper to backup root, and installed from SD card.
To install from SD:
1. Download the file and place it at the root of the SD. After backing up root with Voodoo and unfreezing all apps, prepare to shut down the phone. You should temp-unroot with VooDoo at this point.
2. When turning the phone on, press and hold vol-up and vol-down at the same time. When you have the bootloader menu, press vol-down and then vol-up to get to Motorola recovery.
3. Reveal the recovery options by pressing vol-up and vol-down at the same time when the android and exclanation mark appears.
4. Choose to install a zip from SD, and choose the update. Power button serves as select, volume buttons to move selection.
5. When the update finishes and your phone reboots, restore root from Voodoo, and re-freeze any bloat. You can also restore Safestrap now.
Direct Download of Update Package:
http://omniimpact.com/android/motorola_updates/Blur_Version.6.13.215.XT894.Verizon.en.US.zip
Recommended Software:
- AntTek App Manager
- Voodoo OTA Root Keeper
NOTE: If you lose Root accidentally, that is OK, just re-root the same way you did before.
NOTE 2: Did you delete or modify your system apps instead of just freezing them? This update will fail. You need to take these packages from the original firmware and use them to replace yours. The zip file contains just the packages you need extracted from skylarmb's very useful ROM.
Sent from my DROID4 using XDA
All i did was use voodoo to temp unroot and installed update. Worked fine for me. But if this post was here before i did anything i would've followed it. I am having one issue tho. Play store wants to force close a bit. Not alot but it never did before
Sent from my DROID4 using xda premium
These directions are gathered from several locations and are designed to cover most situations. If you have not frozen bloat applications, you don't need to do the unfreezing part. My goal was to try to answer everything important in one place, such as keeping root, restoring safestrap, and bypassing the system integrity check.
Sent from my DROID4 using XDA
I have been able to get all the way the the install part but it keeps aborting because of an invalad signature. I also read that you need to installing fro the sdcard-ext. While in recovery I have no option to navigate to my ext card... any thought? Thanks everyone
Sent from under a rock
Motorola's recovery ONLY shows the external sd card, sd-ext is just what Android calls it. If you are failing in a bad signature, have you made sure to unfreeze all apps? The patch checks that the initial system is intact before installing, so all the original software has to be there.
Sent from my DROID4 using XDA
any chance to get the original system files? i deleted mine and TB couldn't restore them ;_;
Sent from my DRIOD 4 Husky Edition
Here is a copy of my /system/app folder. Some stuff is frozen, but everything is in there. Let me know if the file is corrupted, I zipped and uploaded it from my phone. The frozen stuff has _fro appended to the file name.
http://omniimpact.com/android/motorola_updates/systemappfolder.zip
Sent from my DROID4 using XDA
Thanks for the instructions. Everything installed fine for me and root was easy to restore. The battery life has been great the last 2 days, but haven't used it a ton yet.
thanks a lot for the files! I'm still having update issues though
Code:
Update location: /cache/Blur_Version.6.13.215.XT894.Verizon.en.US.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified
I:verify_file returned 0
Installing update...
installing motoflash extensions
installing NV updater extensions
installing omapdevtype updater extension
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
Verifying current system...file "/system/app/BackupAssistanceClient.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to stat "/data/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/app/BackupAssistanceClient.apk", "fd7e227c5c96c613ec46c2ed3ffe47785c9576e3", "691854fac80eefce82740d7204de4e22c1a0d9e1")
assert failed: apply_patch_check("/system/app/BackupAssistanceClient.apk", "fd7e227c5c96c613ec46c2ed3ffe47785c9576e3", "691854fac80eefce82740d7204de4e22c1a0d9e1")
E:Error in /cache/Blur_Version.6.13.215.XT894.Verizon.en.US.zip
(Status 7)
Installation aborted.
i think it's saying a checksum failed on BackupAssistanceClient.apk. how does one go about fixing this?
Make sure you have removed _fro from the apks related to backup assistant if you are copying them over. Also, I just realized, it might be an updated version (omg! Unlisted updated component!) Grab skylarmb's stock rooted rom, unzip it, and use the apk from there. It's a bit more of a pain than just a single zip of the folder, but it should have the upgradeable version of the apk.
Sent from my DROID4 using XDA
i "deforsted" the apps you mentioned. i'm going to also try and get those original apks as well.
Sent from my DRIOD 4 Husky Edition
I find it odd that the update could conflict with itself. If that is the case, Verizon has a serious oversight since that means any partially applied update would brick a phone (instead of just resuming where it left off). Let me know how it works out.
Sent from my DROID4 using XDA
what you said did the trick! the update is finally patching right now. I had to replace the system files one by one until they all passed the verification step.
omniuni said:
DOWNLOAD AND INSTALL AT YOUR OWN RISK.
This will temporarily disable Safestrap, but once appled, you can restore Safestrap, and your previous Safe system should still be intact.
This is the Motorola update that is being soak tested. To install it, I unfroze all apps, used Voodoo Root Keeper to backup root, and installed from SD card.
To install from SD:
1. Download the file and place it at the root of the SD. After backing up root with Voodoo and unfreezing all apps, shut down the phone.
2. When turning the phone on, press and hold vol-up and vol-down at the same time. When you have the bootloader menu, press vol-down and then vol-up to get to Motorola recovery. Once the Android and ! appear, press vol-up and vol-down at the same time to reveal the menu.
3. Choose to install a zip from SD, and choose the update. Power button serves as select, volume buttons to move selection.
4. When the update finishes and your phone reboots, restore root from Voodoo, and re-freeze any bloat. You can also restore Safestrap now.
Direct Download of Update Package:
http://omniimpact.com/android/motorola_updates/Blur_Version.6.13.215.XT894.Verizon.en.US.zip
Recommended Software:
- AntTek App Manager
- Voodoo OTA Root Keeper
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
You forgot a key step... I bolded it above.
---------- Post added at 05:47 AM ---------- Previous post was at 05:25 AM ----------
Root is not working on mine any longer...
I ran the Voodoo OTA Root Keeper and backed up root before doing anything and all 5 checkboxes were green, confirming that I had backed up root...now that I am updated, I went back into Voodoo OTA Root Keeper and Device Rooted and Root Permission Granted are grey...hitting Restore Root says "Voodoo OTA Root Keeper has been granted Superuser Permissions" followed by "root su restored" yet the checkboxes don't change to green, and I can't run anything requiring root because my device "is not rooted."
Please help!
Edit - Also, opening the safestrap apk causes a force close...
I had zero apps frozen, and zero issues applying the update. I did make a complete nandroid backup before updating...
I am sorry, I updated the directions; if you check the way OTA rootkeeper works, you are supposed to temp-unroot BEFORE you apply the update. You are still OK, though. Just re-run the original root exploit and you will get root back. The patch does not prevent the original root method from working.
http://forum.xda-developers.com/showthread.php?t=1522911
Sent from my DROID4 using XDA
omniuni said:
I am sorry, I updated the directions; if you check the way OTA rootkeeper works, you are supposed to temp-unroot BEFORE you apply the update. You are still OK, though. Just re-run the original root exploit and you will get root back. The patch does not prevent the original root method from working.
http://forum.xda-developers.com/showthread.php?t=1522911
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
Ok, re-rooting worked. I also updated my binary SU and reinstalled safestrap. I rebooted and am running another nandroid backup for safety.
Thanks!
Really noob question here... I just got my droid 4 and was going to apply this update, the post says update 219, the file is update 215...?? Will this file take me to 219 or keep me at 215?
Thanks!
Sent from my DROID4 using XDA
A good question deserves a good answer about a really dumb thing:
Motorola names their updates based on the verion that you are coming FROM and not what you are going TO. In a sense, I guess this is because they are incremental updates, or in other words, they each assume the last one was installed. By naming this way, you can always tell what the next update to apply is based on what revison you are currently running with little danger of accidentally missing one because you forget it and messing up your phone.
TL;DR;
It will upgrade you to 219.
Sent from my DROID4 using XDA
Thanks for the prompt reply, I'm used to letting dev put updates into roms and just flashing, never done one this way. I always learn something new in the forums!
Sent from my DROID4 using XDA
Anything worth a crap in this update?
I've looked but can't find anything that would make it worth the trouble.
Sent from my DROID4 using Tapatalk 2
Related
I thought it might be useful to put all the info into one thread.
I hope it's completely needless to say that I don't take any credit, since I haven't contributed anything to make that possible
This guide is for rooting your CURRENTLY installed firmware, flashing custom roms, or if you want to upgrade to Gingerbread
If you are NOT S-OFF yet, you either need to get / use an XTC Clip, or use a software exploit / hack (AlpharevX).
The basic differences between both approaches are the following:
AlpharevX:
"Software" S-OFF using an exploit
Bootloader S-OFF
It will flash a hacked HBOOT that sets your device S-OFF.
If you flash an unmodified RUU, or anything that replaces this HBOOT, you will lose S-OFF
-> Not a problem if you stay with custom roms!
Completely free and great solution!
XTC Clip:
Complete "hardware" S-OFF
All locks removed including sim and cid lock.
Permanent solution (radio S-OFF)
-> You can flash anything and won't lose S-OFF
Costs money, or you need to find someone that owns a Clip to do this for you
UPDATE:
Hawkysoft posted about a rare occurrence that has been reported after using AlpharevX:
If you get a security warning in hboot, you will need an XTC Clip to get you running again!
Of course you might also send your phone to repair, but you'll most likely need to pay for that.
So if you experience this problem, either get someone with an XTC Clip to help you out, or buy an "XTC Clip Pay as you go", which is a very cheap variant that comes only with one use (rechargeable) and costs around 30USD.
See the following tutorial to set your device S-OFF with AlpharevX: GUIDE -> S-OFF
And pause at the point where you should install CWMR (ClockworkMod Recovery) to consider the following options:
Do you want to switch to a custom rom after S-OFF?
-> continue with the guide above installing CWMR
Do you want to keep your official firmware and replace your official recovery with CWMR?
--> continue with the guide above installing CWMR,
but before you install a custom rom, make a backup of your current firmware in CWMR!
Do you want to keep your orig firmware AND the official recovery?
--> don't continue with the guide above and follow this guide instead
Be it Froyo or Gingerbread doesn't matter.
If you insist you only want to root your Froyo rom and not upgrade to Gingerbread immediately, please scroll further down.
A rooted Froyo rom is NOT necessary for flashing and afterwards rooting Gingerbread!
If you need further details about flashing custom roms just scroll down.
If you haven't done so already (you didn't get an OTA or you didn't do it manually yet) and you want to upgrade to Gingerbread, here's a short guide on how to flash it first..
How to install the Gingerbread update
download one of the Gingerbread Roms
http://forum.xda-developers.com/showthread.php?t=1033922
This link is for the Incredible S only of course, but the following works also for the Desire S, but then please use a rom for your phone
ATTENTION: If you are NOT S-OFF yet and you are planning to using AlpharevX, you MUST use an ruu compatible with AlpharevX! Check that first!
start the RUU installer
[*]go into your tmp folder to get rom.zip from the extracted files of the RUU installer:
Access the tmp folder by clicking on start/run and put %tmp% into the textbox. Or for windows 7 put this into this search textbox in the "start menu"
Look for the most recent folder (sort by date). In that folder look for rom.zip or simply do a search.
After acquiring rom.zip from your tmp folder you can exit the RUU installer
[*]Put rom.zip onto your sdcard and name it PG32IMG.zip.
boot into the bootloader.. (press and hold vol.down + press power) it will automatically start to install it and ask you if you want to proceed.
After a reboot remove PG32IMG.zip from your sdcard (otherwise it would ask you to reinstall the update each time you boot into the bootloader)
use morelocales2 from the market if you need additional languages
finished. Now follow the steps below for rooting the fw
Guide below partly out of date!
It works, but there are easier methods available now.Work in progress
What you need if you want to root your Gingerbread rom:
an incredible S / Desire S that is S-OFF
Gingerbreak OR SuperOneClick newest version
Busybox
UPDATE:
Some users reported that they weren't able to root using SuperOneClick or Gingerbreak.apk no matter what they tried.
After I reflashed my IS I also run into problems. Although it's not unusual that it doesn't work the 1st time, I decided to do it manually.
I have attached a zip with all the files needed and a script that you could try which does everything for you.
It doesn't do any magic or different than SuperOneClick, but if you do it this way you get to see what's actually happening and if it fails and where / why.
When using this you also don't need to reboot between the tries, reinserting / remounting your sdcard is sufficient.
Please report any bugs.
How to use:
make sure usb debugging is enabled
make a backup of your sdcard's content or use another fat32 formatted sdcard where you don't care to possibly lose its content.
download the zip file: View attachment 596033
extract the zip and open a shell/command prompt and change into that directoy
on Linux start runexploit.sh, on Windows start runexploit.cmd
if Gingerbreak doesn't finish and you ONLY get to see lots of "sendmsg() failed?" without any other messages in between, you should try any of the following options:
hit ctrl + c to abort, unmount / remount your sdcard and start over. It could take a few tries
Doublecheese reported it took him 8-9x
WHILE Gingerbreak is running and printing "sendmsg() failed?" forever, pull and take out your SDcard completely and reinsert it
this worked well for vontdeux, jkolner and me
Thanks to Vontdeux, Doublecheese, jkolner and everyone else afterwards for the feedback!
now, after you see '#', you can hit ctrl + c or close the shell
run root.sh on Linux or root.cmd on Windows from the same directory. This will install su, SuperUser.apk and busybox
when it's finished you're done and have root
then it's very recommended to get "rom manager" from the market, open it and install clockworkmod recovery for installing custom roms, backing up your system et.c.
Files:
Big thanks to Chainfire for GingerBreak and CLShortFuse for SuperOneClick!
SuperOneClick: http://forum.xda-developers.com/showthread.php?t=803682
OR Gingerbreak: get the latest version here: http://forum.xda-developers.com/showthread.php?t=1044765
Busybox installer: https://market.android.com/details?id=stericson.busybox
Steps:
make sure usb debugging is enabled
make a backup of your sdcard's content or use another fat32 formatted sdcard where you don't care to possibly lose its content.
use the latest SuperOneClick which might be easier.
start the application and select "GingerBreak" as exploit.
But respect the info and warning of the creator of the Gingerbreak.apk:
Chainfire said:
WARNING: Apparently on some devices the root exploit causes the SD card (internal or external) to be formatted. Also, if it gets stuck but you do see the card mounting/unmounting, try formatting your SD card yourself and try again (or use a different SD card) often this works (a fix for both issues is being looked at)
Click to expand...
Click to collapse
click root check Chainfire's post if you run into problems (also with SuperOneClick because it uses his exploit): http://forum.xda-developers.com/showthread.php?p=13086954#post13086954
after it's finished your phone will reboot and you're essentially done.
Alternatively, don't use SuperOneClick but follow the guide of Chainfire from the beginning to install Gingerbreak on your device and root your phone: http://forum.xda-developers.com/showthread.php?p=13086954#post13086954
(optional) get the busybox installer mentioned above, start the application and install/update your busybox installation.
(optional, but highly recommended) Now for the ultimate pleasure get Rom Manager from the market and use it to install a "custom recovery": ClockWorkMod Recovery
What you need if you want to root your Froyo rom:
an Incredible S / Desire S that is S-OFF
SuperOneClick newest version
(optional, but highly recommended) Busybox installer app
Files:
Update: apparently the current SuperUser app is crashing for some users.
If you experience these problems see the next section
Big thanks to CLShortFuse for SuperOneClick!
SuperOneClick:: http://forum.xda-developers.com/showthread.php?t=803682
Busybox installer: https://market.android.com/details?id=stericson.busybox
Steps:
use the latest SuperOneClick
start the application and select "psneuter" as exploit.
click root
after it's finished you might need to reboot for getting Superuser app to pop up when needed.
(optional) get the busybox installer mentioned above, start the application and install/update your busybox installation.
(optional, but highly recommended) Now for the ultimate pleasure get Rom Manager from the market and use it to install a "custom recovery": ClockWorkMod Recovery
So how to flash custom roms?:
it's extremely easy
put your favorite custom rom onto your sdcard
install rom manager if you haven't done so already
open rom manager and click "install ClockworkMod Recovery
next click "install rom from sdcard"
select your custom rom you put on your sdcard
select to backup your currently installed rom just in case you want to revert back
Most of the time you also need to check wipe cache and data (follow the instructions of the creator of that custom rom to find out if you need to do that or not. If you wipe your data, all your current settings will be lost however so make a backup!)
wiping Dalvik Cache is always a good idea and won't harm your settings
after pressing ok, Rom manager will boot into Recovery, backup your current rom (if you told it to), wipe (if you told it to), install the custom rom and reboot
Solution for SuperUser crashing:
All thanks go to rmk40 who patched SuperUser for us running newer versions of Sense:
http://forum.xda-developers.com/showthread.php?t=886999
rmk40 said:
The latest official build of Superuser does not work with newer Sense ROMs (such as Vision 1.72+, anything released recently). HTC has started utilizing a relatively new feature of sqlite; a journaling mode called WAL (write-ahead logging). It's actually smart. WAL journaling should improve sqlite throughput, which represents a large amount of Android's IO and benefits applications across the board. The downside is it broke Superuser because it's actually special in its' use of sqlite.
Click to expand...
Click to collapse
How to install the patched version
Update 5/14: Fixed a serious bug in the replace_su script that made it pretty much useless
If you didn't root your phone yet
You might want to patch SuperOneClick before using it the first time.
Either download the patched su and SuperUser.apk, or just use the already patched version of SuperOneClick attached to this post. View attachment 591017
If you already rooted your phone:
Usually the first app requesting root access does work with the unpatched version, so you can use this to gain root access on the shell to replace SuperUser and su with the patched versions. If SuperUser doesn't pop up, open Superuser and remove all apps you already whitelisted for su access and try again
To keep it simple, I have attached an archive with a script to do this for you: View attachment 595753
make sure USB Debugging is enabled (in settings/apps/development)
extract replace_su.zip on your windows or linux pc
open a terminal and change into that directory
on windows run replace_su.cmd, on linux run replace_su.sh
the script needs root access so you need to press allow when SuperUser pops up on the phone
If you already installed a custom recovery and want to do it that way:
Just download rmk40's flashable zip: http://forum.xda-developers.com/showthread.php?t=886999
put it onto your sdcard
reboot into recovery by starting rom manager and selecting reboot into recovery
if this doesn't work because SuperUser fc, shutdown your phone completely (fast boot disabled in settings/power). Press and hold vol-down and press power. From the bootloader menu: select "recovery"
use ClockworkMod to flash the zip. "install/flash zip from sdcard.."
you can also just replace those files (SuperUser.apk and su) in your SuperOneClick directory and then re-run SuperOneClick.
Here's the "patched" SuperOneClick View attachment 591017
Update 5/14: Fixed an error in the replace_su script.
Update 5/10: updated because of a request to re-add the Froyo rooting info
Update 5/09: updated because of SuperUser crashing issue
Update 4/27: updated due to new version of SuperOneClick now supporting Gingerbreak
Update 4/26: updated because of Gingerbreak, which makes this much shorter and easier. Thanks very much Chainfire for all the hard work!
Update 4/24: thanks very much to Hawkysoft for pointing out that psneuter doesn't work for Gingerbread and further instructions)
So if you are already gingerbreaded, please scroll down
Update 4/23: OFFICIAL CLOCKWORKMOD RECOVERY NOW AVAILABLE!!
Big thanks to Koush and Hawkysoft!
Hawkysoft said:
time has arrived, after supplying all the info, koush did a hell of a job with creating this
download rommanager from the market
and install the recovery for the Incredible S
WARNING DO NOT PARTITION SDCARD <- THIS WILL BRICK YOUR DEVICE, A FIX IS ON THE WAY
all thanks go out to koush offcourse
i tested:
backup, whipe data, restore, reboot... all worked
bugs found:
sdcard > if you do parition this, you will end up jtaggin your device cuz its bricked! (the fix is on the way)
backup time > in the folder it shows a wrong time that it has been created atleast for me it does.. it shows a 3 hour difference idk how its set but its not a big deal in my opinion
Click to expand...
Click to collapse
Please check the post by Hawkysoft!
http://forum.xda-developers.com/showthread.php?t=1046759
Nice, thanks!
OTA Updates
TimMun said:
Nice, thanks!
Click to expand...
Click to collapse
Thanks for the thanks
NP
Does anyone know if your phone would still get OTA Updates after doing it this way?
I guess so, but then of course you would need to repeat those steps after you installed an official update.
madmaxx82 said:
Thanks for the thanks
NP
Does anyone know if your phone would still get OTA Updates after doing it this way?
I guess so, but then of course you would need to repeat those steps after you installed an official update.
Click to expand...
Click to collapse
I don't know the answer to this question but first I would like to actually see an update
TimMun said:
I don't know the answer to this question but first I would like to actually see an update
Click to expand...
Click to collapse
Haha, it was really funny coincidence. After I s-offed the phone I got an OTA
BTW: If anyone wants to be S-OFF and doesn't mind visiting me in Austria, I'd help you out. For free of course
well if u use stock rom and rooted that one, you will get notified that there is an update, but im not totaly sure if it installs (especially when u use custom recovery, than its a nogo)
timbo007up said:
well if u use stock rom and rooted that one, you will get notified that there is an update, but im not totaly sure if it installs (especially when u use custom recovery, than its a nogo)
Click to expand...
Click to collapse
Thanks, so if it doesn't work you'd need to reflash the original recovery first..
If you do it you will fail and end flashin a standard rom with hboot xD
Been there.... Better first update than flash the recovery or you will be busy for a few ^^
Sent from my HTC Incredible S using XDA Premium App
Hawkysoft said:
If you do it you will fail and end flashin a standard rom with hboot xD
Been there.... Better first update than flash the recovery or you will be busy for a few ^^
Sent from my HTC Incredible S using XDA Premium App
Click to expand...
Click to collapse
Ahh thanks for the warning
Since the custom recovery is installed already anyway when there's an OTA update available, wouldn't the following work?
If I get notified about an available OTA update, I could flash a complete RUU, then get the OTA and afterwards re root + reflash the custom recovery?
Newbies question: if you just want root in order to use i.e. titanium I suppose you don't need to install PG32IMG right?
Sent from my HTC Incredible S using XDA App
nikant said:
Newbies question: if you just want root in order to use i.e. titanium I suppose you don't need to install PG32IMG right?
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
Correct. Its only needed to flash custom roms.
Sorry for newb question... What does S-OFF mean?
Read the rooting topic in the dev section,
But to make it easy for you: S-OFF means Security Off.
Which allows us to (over)write system files
timbo007up said:
Correct. Its only needed to flash custom roms.
Click to expand...
Click to collapse
And nandroid Can't live without it... of course especially if you flash custom roms, but also if you don't, titanium is just not always 10.000% enough
There is another recovery available from GOAPK with Reboot function that works.
can you confirm that it fully works with backin up and restoring?
since the current one failes at restoring
;p
testing it...
first try to backup FAIL <- Error while generating md5 sum!
second time as well this is a major failing recovery
I am going to try porting clockwork myself from scratch tonight
Sent from my HTC Incredible S using Tapatalk
With this recovery in the first post, I had an error at the time of restoration, with the one I posted, an error of md5 sum, but with the tutorial as an attachment, the worries of md5 sum is adjusted by 5 minutes
So I can now restore quietly after each crash, as I try to adapt a framework-res.apk to my Incredible S
Just at it now
creating md5 sums failed.. restore of course also failes..
I just restored a previously created backup with the one from llnhhy successfully
So we have a recovery that has all the functions, but has trouble creating md5 sum, and another that did not have the reboot function with a problem of restore, by mixing the two should do it .. .
Here are instructions on how to upgrade from Android 2.3.6 Gingerbread (build 6.13.219) to Android 4.0.4 Ice Cream Sandwich (build 6.16.206). This is an official build pulled from a Motorola server.
WARNING!!! ONCE YOU INSTALL THIS UPDATE, YOU CANNOT REVERT TO 6.13.219 OR 6.13.215 VIA FASTBOOT. ATTEMPTING TO DO SO WILL RESULT IN A BRICK. YOU MAY ALSO BE TAKEN OFF THE OFFICIAL VERIZON UPGRADE PATH. USE AT YOUR OWN RISK.
Android 4.0.4 System Version 6.16.206
Blur_Version.6.13.219.XT894.Verizon.en.US.zip (354.9 MB)
Blur_Version.6.13.219.XT894.Verizon.en.US.crc (10 bytes)
DOWNLOAD
INSTRUCTIONS:
(If you have never edited your build.prop file or modified the contents of your /system folder, you can most likely skip step 1.)
If you have an external SD card:
Flash the 6.13.219 fastboot file (instructions here) and, if desired, use the Droid 4 Utility to obtain root (instructions here)
(To keep root) Open Superuser, click the Settings icon, and update the su binary
Download/extract D4ics6.16.206.zip and copy only Blur_Version.6.13.219.XT894.Verizon.en.US.zip to your phone's external SD card
(To keep root) Install OTA RootKeeper, select "Protect root", then "Temp. un-root", then "Restore root"
Power off your phone, then hold the volume up, volume down, and power buttons at the same time until you see the bootloader menu
Use the volume down button to navigate to "Recovery" then use the volume up button to select it
When you see the android/triangle, press both volume buttons together
Select "apply update from sdcard" then press the power button
Select the zip file and wait for the installation to finish
Reboot
(To keep root) Open OTA RootKeeper and select "Restore root"
If you do not have an external SD card (root required):
Flash the 6.13.219 fastboot file (instructions here) and use the Droid 4 Utility to obtain root (instructions here)
(To keep root) Open Superuser, click the Settings icon, and update the su binary
Download/extract D4ics6.16.206.zip and copy the enclosed zip and crc files to your phone's internal storage (do not change the file names)
Install ROM Manager
Install ES File Explorer, go to Settings, and check "Root Explorer" and "Mount File System"
Move the zip and crc files from internal storage to the /cache folder
(To keep root) Install OTA RootKeeper, select "Protect root", then "Temp. un-root", then "Restore root"
Open ES File Explorer again, navigate to the /cache folder, click on the zip file, and open with ROM Manager
Select "OK" when you see the Reboot and Install message and wait for the installation to finish
Reboot
(To keep root) Open OTA RootKeeper and select "Restore root"
I wonder if there is a way to use the kexec exploit to make a rom out of this, with custom kernel.
There is no kernel source available to compile custom kernels for Motorola ICS builds, even if kexec were working on CDMA/LTE variants, which it isn't yet, so there is no work being done to debug or fix the current release of the kexec exploit until the ICS 3.0 kernel source drops.
Say you install this leaked ics and the OTA ics comes out... then the OTA ics is by far better then leaked current ics.... I know there is not a way to predict the future... what then do you'll think there will be a way to obtain said OTA update.....?
Sent from my DROID4 using XDA
So, I'm struggling to figure out how an OTA can prevent downgrading by fastboot files. The only thing I can think of is that it updates the kernel in such a way that it isn't compatible with the previous builds and the locked bootloader keeps one from reverting the kernel change. Is that correct? The other thing I don’t understand is how it prevents future updates. I can't figure out any mechanism for that. I would love to get ICS early, but not if there is no way to upgrade in the future.
lorddunlow said:
So, I'm struggling to figure out how an OTA can prevent downgrading by fastboot files. The only thing I can think of is that it updates the kernel in such a way that it isn't compatible with the previous builds and the locked bootloader keeps one from reverting the kernel change. Is that correct? The other thing I don’t understand is how it prevents future updates. I can't figure out any mechanism for that. I would love to get ICS early, but not if there is no way to upgrade in the future.
Click to expand...
Click to collapse
Someone correct me if I'm wrong, but when you start flashing with a fastboot file, there are a certain number of specific partitions that are flashed individually. It's my understanding that this update changes the partitions in some way, so if you try to flash a Gingerbread file, it will expect certain partitions that aren't there any more.
OTA updates are always from one specific version to another. If VZW decides to make the official ICS build anything other than 6.16.200, then when the next update is released however long down the line, it will only push to devices running that particular build.
Doesn't fastboot allow you to change partition sizes? You could try that (don't you have a bricked D4? )
Also, even though we don't have source for the newer kernels, would it be possible to use the kernel from the leak (no changes), or is this just not possible w/out source?
podspi said:
Doesn't fastboot allow you to change partition sizes? You could try that (don't you have a bricked D4? )
Click to expand...
Click to collapse
I'm sure it wouldn't be too difficult for a developer to create a fix similar to the one Timmy10shoes developed for the Bionic.
And VZW sent me a replacement so I was only without my D4 for a day
What version of kernel is included in this rom?
So have people been able to successfully install ICS and keep root with this method? Does safe strap install?
JKingDev said:
So have people been able to successfully install ICS and keep root with this method? Does safe strap install?
Click to expand...
Click to collapse
Yep. I upgraded and kept root. I haven't tried safestarp cuz there's no point right now since there are no roms for the leak yet but I don't see why it wouldn't work.
I upgraded with root intact and I installed Droid 4 Bootstrap recovery and it works.
I made a backup of the ICS install successfully but have not tried restoring it yet.
Grizzy3 said:
Yep. I upgraded and kept root. I haven't tried safestarp cuz there's no point right now since there are no roms for the leak yet but I don't see why it wouldn't work.
Click to expand...
Click to collapse
Thanks! I upgraded and have been running this and it is working great. Well worth the risk. Cant wait to see hashcode's CM builds based on this kernel.
Safe strap would not be too useful without ROMs to flash but it would be useful to backup/restore so I can try modifying system files/bloat removal and have a back to use in case something goes wrong. I did a mod to make the external sdcard the regular sdcard directory and I want to figure out how to add percentage to the battery indicator. There is a mod for this made for the razr with a similar leaked ICS build so I might try it.
JKingDev said:
Thanks! I upgraded and have been running this and it is working great. Well worth the risk. Cant wait to see hashcode's CM builds based on this kernel.
Safe strap would not be too useful without ROMs to flash but it would be useful to backup/restore so I can try modifying system files/bloat removal and have a back to use in case something goes wrong. I did a mod to make the external sdcard the regular sdcard directory and I want to figure out how to add percentage to the battery indicator. There is a mod for this made for the razr with a similar leaked ICS build so I might try it.
Click to expand...
Click to collapse
I actually don't think the safestrap we have now would work on the leak because they had to release a new safestrap specifically for the razr ics leak. But if you do try it let us know if it works out.
Did anybody lose root?
Sent from my DROID4 using XDA
I lost root. Apparently if you don't update the SU binary before you save root on the 2.3 rom, you may not be able to restore it when you upgrade to 4.0.4.
detox702 said:
I lost root. Apparently if you don't update the SU binary before you save root on the 2.3 rom, you may not be able to restore it when you upgrade to 4.0.4.
Click to expand...
Click to collapse
How do you update the SU binary?
GermanGuy said:
How do you update the SU binary?
Click to expand...
Click to collapse
Open the SU app and go to preferences. Down towards the bottom you will see an option to check for updates.
Droid 4 4.0.4
jy3ng4 said:
Here are instructions on how to upgrade from Android 2.3.6 Gingerbread (build 6.13.219) to Android 4.0.4 Ice Cream Sandwich (build 6.16.206). This is an official build pulled from a Motorola server.
WARNING!!! ONCE YOU INSTALL THIS UPDATE, YOU CANNOT REVERT TO 6.13.219 OR 6.13.215 VIA FASTBOOT. ATTEMPTING TO DO SO WILL RESULT IN A BRICK. YOU MAY ALSO BE TAKEN OFF THE OFFICIAL VERIZON UPGRADE PATH. USE AT YOUR OWN RISK.
Android 4.0.4 System Version 6.16.206
Blur_Version.6.13.219.XT894.Verizon.en.US.zip (354.9 MB)
Blur_Version.6.13.219.XT894.Verizon.en.US.crc (10 bytes)
DOWNLOAD
INSTRUCTIONS:
(If you have never edited your build.prop file or modified the contents of your /system folder, you can most likely skip step 1.)
If you have an external SD card:
Flash the 6.13.219 fastboot file (instructions here) and, if desired, use the Droid 4 Utility to obtain root (instructions here)
(To keep root) Open Superuser, click the Settings icon, and update the su binary
Download/extract D4ics6.16.206.zip and copy only Blur_Version.6.13.219.XT894.Verizon.en.US.zip to your phone's external SD card
(To keep root) Install OTA RootKeeper, select "Protect root", then "Temp. un-root", then "Restore root"
Power off your phone, then hold the volume up, volume down, and power buttons at the same time until you see the bootloader menu
Use the volume down button to navigate to "Recovery" then use the volume up button to select it
When you see the android/triangle, press both volume buttons together
Select "apply update from sdcard" then press the power button
Select the zip file and wait for the installation to finish
Reboot
(To keep root) Open OTA RootKeeper and select "Restore root"
If you do not have an external SD card (root required):
Flash the 6.13.219 fastboot file (instructions here) and use the Droid 4 Utility to obtain root (instructions here)
(To keep root) Open Superuser, click the Settings icon, and update the su binary
Download/extract D4ics6.16.206.zip and copy the enclosed zip and crc files to your phone's internal storage (do not change the file names)
Install ROM Manager
Install ES File Explorer, go to Settings, and check "Root Explorer" and "Mount File System"
Move the zip and crc files from internal storage to the /cache folder
(To keep root) Install OTA RootKeeper, select "Protect root", then "Temp. un-root", then "Restore root"
Open ES File Explorer again, navigate to the /cache folder, click on the zip file, and open with ROM Manager
Select "OK" when you see the Reboot and Install message and wait for the installation to finish
Reboot
(To keep root) Open OTA RootKeeper and select "Restore root"
Click to expand...
Click to collapse
I found a Droid 4 Utility jellybean. The utility is very easy to use. But it flashes 4.1.2. I need 4.0.4. How can I downgrade to 4.0.4 on an HTC Droid 4? Please help?
This is for the Motorola Droid 4, try a HTC forum
Sent from my Amazon Kindle Fire using Tapatalk
See also: How to upgrade from one leaked ICS build to another on the Droid 4
See also: How to root Android 4.0.4 ICS on the Droid 4
Here are instructions on how to upgrade from Android 2.3.6 Gingerbread (build 6.13.219) to Android 4.0.4 Ice Cream Sandwich on the Motorola Droid 4 (XT894). These are official builds pulled from a Motorola server.
WARNING!!! ONCE YOU INSTALL THIS UPDATE, YOU CANNOT REVERT TO 6.13.219 OR 6.13.215 VIA FASTBOOT. ATTEMPTING TO DO SO WILL RESULT IN A BRICK. YOU MAY ALSO BE TAKEN OFF THE OFFICIAL VERIZON UPGRADE PATH. USE AT YOUR OWN RISK.
Android 4.0.4 System Version 6.16.215: DOWNLOAD
Previous leaked Android 4.0.4 ICS builds:
6.16.213: DOWNLOAD
6.16.212: DOWNLOAD (can only be used with installation method #1)
6.16.211: DOWNLOAD (can only be used with installation method #1)
6.16.208: DOWNLOAD
6.16.206: DOWNLOAD
6.16.200: DOWNLOAD
INSTRUCTIONS:
(If you have never edited your build.prop file or modified the contents of your /system folder, you may be able to skip step 1.)
Method 1: If you have an external SD card:
Flash the 6.13.219 fastboot file (instructions here) and, if desired, use the Droid 4 Utility to obtain root (instructions here)
(To keep root) Open Superuser and update the su binary
Download/extract one of the files above and copy only Blur_Version.6.13.219.XT894.Verizon.en.US.zip to your phone's external SD card
(To keep root) Install OTA RootKeeper, select "Protect root", then "Temp. un-root", then "Restore root"
Power off your phone, then hold the volume up, volume down, and power buttons at the same time until you see the bootloader menu
Use the volume down button to navigate to "Recovery" then use the volume up button to select it
When you see the android/triangle, press both volume buttons together
Select "apply update from sdcard" then press the power button
Select the .zip file and wait for the installation to finish
Reboot
(To keep root) Open OTA RootKeeper and select "Restore root"
Method 2: If you do not have an external SD card (root required):
Flash the 6.13.219 fastboot file (instructions here) and use the Droid 4 Utility to obtain root (instructions here)
(To keep root) Open Superuser and update the su binary
Download/extract one of the files above and copy the enclosed .zip and .crc files to your phone's internal storage (do not change the file names)
Install ROM Manager
Install ES File Explorer, open it, go to Settings, and check "Root Explorer" and "Mount File System"
Move the zip and crc files from internal storage to the /cache folder
(To keep root) Install OTA RootKeeper, select "Protect root", then "Temp. un-root", then "Restore root"
Open ES File Explorer again, navigate to the /cache folder, click on the .zip file, and open with ROM Manager
Select "OK" when you see the Reboot and Install message and wait for the installation to finish
Reboot
(To keep root) Open OTA RootKeeper and select "Restore root"
Method #2 (if you don't have an external SD card) won't work for the 6.16.208 build as I don't have the .crc file. If anyone has it please let me know
EDIT: Got it - the .208 file has been modified to include the .crc so both installation methods will work now.
I see a lot of people saying they've went the leaks for the Droid 4, other than wanting ICS what would be the real benefit to going this route and getting kicked off the upgrade path vs staying on GB and using safestrap to use one of the other ICS roms that are available?
collins521 said:
I see a lot of people saying they've went the leaks for the Droid 4, other than wanting ICS what would be the real benefit to going this route and getting kicked off the upgrade path vs staying on GB and using safestrap to use one of the other ICS roms that are available?
Click to expand...
Click to collapse
I believe the leak has a working global mode, which means you can use the phone on GSM networks
collins521 said:
I see a lot of people saying they've went the leaks for the Droid 4, other than wanting ICS what would be the real benefit to going this route and getting kicked off the upgrade path vs staying on GB and using safestrap to use one of the other ICS roms that are available?
Click to expand...
Click to collapse
In addition to what gtmaster said, there are various things that do not work right now on the ICS ROMs since they are running off the GB kernel. Data is not always solid, I believe there are issues with the camera and video recording as well. If you want a fully functioning ICS experience your only option is the ICS leaks right now. Also, it seems pretty likely that there will be a way to get back on the upgrade path. Something involving partially flashing the .219 fastboot file or some such thing to trick the OTA into thinking you are still on stock GB. No guarantees though. Personally I'm waiting. Eclipse is good enough for me until the OTA drops. Not that it's not tempting!
Sent from my DROID4 using Tapatalk 2
Got the .crc file for the .208 leak (thanks Hooks405) so you can now install it without an external SD card.
kwyrt said:
In addition to what gtmaster said, there are various things that do not work right now on the ICS ROMs since they are running off the GB kernel. Data is not always solid, I believe there are issues with the camera and video recording as well. If you want a fully functioning ICS experience your only option is the ICS leaks right now. Also, it seems pretty likely that there will be a way to get back on the upgrade path. Something involving partially flashing the .219 fastboot file or some such thing to trick the OTA into thinking you are still on stock GB. No guarantees though. Personally I'm waiting. Eclipse is good enough for me until the OTA drops. Not that it's not tempting!
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
I can confirm that we are able to get back on the update path. I had updated from .219 to the .206 leak a few weeks ago, and last night ended up messing my /system partition permissions up and wasn't able to boot up properly anymore. At first, I thought my phone was doomed but I wasn't ready to throw in the towel just yet.
I fastbooted the .219 package and was able to flash a patched kernel from the .208 leak to make the leaked .208 OTA update think I was on .219 with everything intact. It proceeds to update the /system files without a hitch and you are good to go; it is very unlikely that this won't work going forward with any future OTA updates. There's a thread on droidforums.net outlining the steps; it's pretty straigtforward.
www.droidforums.net/forum/droid-4-r...k-200-aka-upgrading-200-206-instructions.html
Root access is of course *temporarily* lost, but I found a method to re-root the device on ICS 4.0.4. See the thread in this forum for more details.
Hmmm...definitely make a tutorial on how to go to the leak and then back! Or do you mean you were still on the ICS leak but able to get it to update just the system?
Rick#2 said:
Root access is of course *temporarily* lost, but I found a method to re-root the device on ICS 4.0.4. See the thread in this forum for more details.
Click to expand...
Click to collapse
What thread are you talking about? Mind posting the link?
-----
http://forum.xda-developers.com/showthread.php?t=1707214
its your birthday, its your birthday!
Added 6.16.211, 6.16.212, and 6.16.213 to the OP
Can I use method 1 if I'm on a eclipse? Or do I have to go back to stock gb then go to ics
Sent from my DROID4 using XDA
Method 1 requires stock GB .219 which you will have if you do the first step listed with fastboot.
Is there any way to root build 213 without using VooDoo's RootKeeper?
Somehow Rootkeeper did not keep my root once I flashed 4.0.4 build 213.
It was my fault because I backed up root, temp un-rooted, then restored root, but then received a couple calls from work and later on flashed ICS so somehow I lost a protected root version.
I tried using the 4.0.4 root method in the link below but it did not root build 213.
http://forum.xda-developers.com/showthread.php?t=1707214
raw33 said:
Is there any way to root build 213 without using VooDoo's RootKeeper?
Somehow Rootkeeper did not keep my root once I flashed 4.0.4 build 213.
It was my fault because I backed up root, temp un-rooted, then restored root, but then received a couple calls from work and later on flashed ICS so somehow I lost a protected root version.
I tried using the 4.0.4 root method in the link below but it did not root build 213.
http://forum.xda-developers.com/showthread.php?t=1707214
Click to expand...
Click to collapse
You should be able to use jsnweitzel's Droid 4 Utility to root ICS. I lost root going from .212 to .213 and the utility worked for me. I did have to run the ICS root script a couple of time before it worked though.
kwyrt said:
You should be able to use jsnweitzel's Droid 4 Utility to root ICS. I lost root going from .212 to .213 and the utility worked for me. I did have to run the ICS root script a couple of time before it worked though.
Click to expand...
Click to collapse
Yep, that worked perfectly. Just needed to update my Utility tool to the newest version.
Added the 6.16.215 leak to the OP
If you are on a ICS leak now and want to move to another check out this new tool here: http://forum.xda-developers.com/showthread.php?t=1779810
You can use this to restore stock Gingerbread if you are on a modified GB or to go from one ICS to another.
This is the original D4 tool with additions created by several others and repackaged-edited by me.
UPDATE NOTICE: If you downloaded the tool on 06/20 from about 10pm eastern till noon the next day the script was an old version. It is correct now. Just download again.
06/22 9 AM Eastern - updated superuser binary to most recent version.
06/23 12:30 PM Eastern - updated links for 6.16.213 (thanks again droidian1441)
06/25 10:30 PM Eastern - Revised script, that includes a data save option for restoring GB and the best change. The flashing of the GB files and the ICS Kernel to jump from one ICS to another is now all in one. Removed the push file to sdcard (some thought you could do this after you started flashing the system).
06/30 11 AM Eastern - add new link to download all files.
07/01 10:30 Eastern - Updated Superuser (3.1.3) + binary and VoodooRootKeeper (2.0.3) to latest versions. Update ICS root for Dan Rosenburg's root script, this will install superuser and busybox. The other root method didn't seem to install busybox in proper location and resulted in some malfunctions of root only apps. If you installed the previous root script, use voodoo to temporary unroot, then uninstall superuser. Run the new script and you should be good. Note on the latest version of superuser scroll to the left for the update binary menu. Also contains a temporary unroot and OTA protect root.
Some users have reported driver trouble especially after moving to ICS and trying to root.
Go here to get the driver update tools: https://motorola-global-portal.custh...p/30,6720,8302
Some have reported that the USB utility didn't fix there trouble and had to download motocast, which downloaded new drivers.
Thanks again to 1898trouble07 (droidforums) for the data save tip.
I am on longer putting a full version out. It was was just too big to maintain updates. Everything you need is here. You just have to download a few things and move around a couple of files.
First read this entire post at least twice, skipping any step will be BAD!. Then download everything you need for this.
1. All downloads are listed here: http://d-h.st/users/jsnweitzel/?fld_id=3413#files
Other download links below.
1. Get the Tool Here: https://docs.google.com/open?id=0Byw...URLSjQ5V29pYk0
or here: https://www.dropbox.com/s/132a5i038luy4vu/Droid4withICSfix-rootLITE (3).zip
or here: https://docs.google.com/open?id=0Byw...XV2N2N3cTBoQW8
This is a double zip extract until you see the .bat files and a "files" folder. Double click the script to run the tool.
2. Get the GB 219 Fastboot files here: http://sbf.droid-developers.org/cdma...1FF_01.xml.zip
or here: https://docs.google.com/open?id=0Byw...WswcF91MkxkODA
3. If you are just restoring GB this is all you need. Extract the fastboot zip files and copy them to "files" folder of the tool.
If you are just restoring GB, rooted and running the data save option...It might mess up your root. I don't really know for sure. It will erase the superuser binary and the backup if you are running the rootkeeper, but should keep superuser installed. Therefore you may be in a half rooted stuck state and running the root again may not work. I don't have a phone on GB to test this out. To be extra cautious you may want to run the unroot, restore GB then root again. Let me know what you experience and I can update the post.
If you want to go to ICS and are on GB. Then download (see item one below) the D4213 and put it on your external sdcard Boot to recovery and flash from external. You don't have to be rooted. but if you are the easy way to keep root is to use voodoo's rootkeeper. Protect root, temporarily unroot, reroot, flash the ota, then restore root. If you mess up just use the tool to run the ICS root.
If you are moving from one ICS to another keep reading. Downloading the following two files.
1. Get the ICS OTA currently 6.16.213 ICS here: https://docs.google.com/open?id=0Byw...jVSanRzaTZ5alU
This is a double zip to open until you see the folder named D4213, then copy this file to the external sdcard of your phone.
2. Get the matching Kernel 6.16.213 (boot.img) here: https://docs.google.com/open?id=0Byw...1J0VFBCY1NBM2M
Unzip this folder and copy the boot.img to the "files" folder of the tool. It must be named "ICSFIX" for the tool to work.
If you are going from one ICS to another this is the basic procedure. This uses a fair amount of your pc resources. Don't have a bunch of other programs running. Set the phone to MTP for USB and be sure debugging is on (system setting, developer options).
Be sure you charge your battery first. This is a long process be patient. You will get several errors (INFO validation type) if you are on ICS and flash the GB files. Just let it finish.
1. Charge your battery to 100% and have a high quality usb cable. Sometimes the process fails so you might have to do it twice. When in fastboot mode the battery will not charge.
2. Put the D4213 zip on your external sdcard; just copy and paste with windows.
3. Boot to bootloader and select fastboot (power down, hold both volume buttons and press power, release power, select ap fastboot). You can use the tool for this step but will have to manually do it later.
4. Select menu 16 and flash the GB files plus the boot.img of 213. This will take a while just let it finish and follow the prompts when ask to press a key to continue. You will get some errors (Info validation type). Just let it run and finish.
5. Your phone will reboot and attempt to update (android with spinning ball).
6. Let it run until the screen goes blank and the red "M" appears.
7. Then force a power down and boot to the bootloader.
9. Select recovery. When you see the android with the red exclamation press both volume buttons. Select apply update from external storage and chose the 213 zip.
10. Once complete reboot.
11. ENJOY
12. Root ICS if you want.
If you use this to install vodoo's root keeper make sure your screen is unlocked. If not it seems to hang up sometimes. You should immediately get a superuser request.
Finally this is windows only. If someone writes the linux script I can add it in later. Let me know if you have any issues, suggestions, questions or problems.
As usual doing any of this is at your own risk and may render your phone to be a nice paperweight.
Here is the full menu of the tool:
1. Fastboot GB to stock and ERASE DATA (You can use this to restore stock Gingerbread if you are on a modified GB)
2. Fastboot GB to stock and SAVE DATA
3. Root GB
4. Unroot GB
5. Install Voodoo Rootkeeper
6. Install Safestrap for GB
7. System Pull
8. Overclock for GB
9. Boot to Fastboot
10. Boot to Recovery
11. ADB Shell
12. Reboot phone
13. Flash the ICSFIX Kernel (This is not necessary to jump from one ICS to another, use menu 16. Left in for advanced users only)
14. Install Safestrap for ICS
15. Droid 4 ICS Root
16. D4 ICS Fix (Jump from one leak to another) and SAVE DATA
Thought fastboot back to gb after going to the leaked ics caused a brick?
Sent from my DROID4 using xda premium
twizzles said:
Thought fastboot back to gb after going to the leaked ics caused a brick?
Click to expand...
Click to collapse
Yes, but not completely. The phone will still be able to go into fastboot mode which then allows you to flash the necessary files for the upgrade to work.
Gotcha. Thanks a lot
Sent from my DROID4 using xda premium
What are the necessary files to flash via fastboot after downgrading to gingerbread from ICS?
If you are on GB and want to do a stock restore this will do it for you. If you are on a ICS leak it's one of the steps you need to move up.
Now I will feel more comfortable in flashing the update!, thanks man. Great job.
Sent from my DROID4 using XDA
stereokid said:
What are the necessary files to flash via fastboot after downgrading to gingerbread from ICS?
Click to expand...
Click to collapse
You can't go back to GB if you are on a ICS leak. You can upgrade to a newer leak. Here are the instructions: http://www.droidforums.net/forum/dr...k-200-aka-upgrading-200-206-instructions.html
Same ones can be used to go up to 208. The tool has everything you need.
If im on 206 do i have to flash to 208 in order to flash the new 211 version? And whats in the updates? Enough to take the risk yet again of flashing a leak?
Sent from my DROID4 using xda premium
You can go right up to 211. I haven't changed the tool yet so you will have to replace the 208 files with the 211 files. I will be modifying the tool soon for 211.
Is there an eta for the tool update by any chance? Thanks
Sent from my DROID4 using xda premium
I have started working over the script, with an idea to simplify a step too. But will test on my own phone before I post. You can use the tool as-is if you rename the boot.img and the ota. There is one little hiccup in the script after pushing the boot.img (kernel), but it's doesn't affect the process. Hope to have it up in a few hours.
The new tool is up with some instructions too. The Lite version is good to go, the other is still uploading.
Is it possible to use this tool to flash up from gb? I'm currently using eclipse on safestrap (I know id need to remove safestrap) but didn't know if this will only work with those already on the leaks or if we can use straight from gb
Sent from my DROID4 using XDA
This tool can restore your phone to stock GB. If you have the GB Fastboot files and the latest ICS OTA you can use the lite version and just put add the files to files folder.
If you want to move to ICS you might be able to uninstall your rom, safestrap and fix the logwrapper renaming. I think I saw a thread about that somewhere.
For anyone trying to download I was having some issues setting up the links for gdrive. Just haven't used it before for file sharing. All should be good now.
jsnweitzel said:
This tool can restore your phone to stock GB. If you have the GB Fastboot files and the latest ICS OTA you can use the lite version and just put add the files to files folder.
Click to expand...
Click to collapse
If you can, you might want to edit that first sentence to specify that it can restore your phone to stock GB _if you haven't upgraded to ICS_.
Thanks for the suggestion...just saw that 212 is coming. Will be updating once I get a copy.
Ok I just updated the OP, with all the downloads you need. But it's late I am a bit tired. Let me know if something is out of sorts or a link is broke or wrong. It was just too much to keep the full tool up to date and upload.
Link to the tool is broken unfortunately
jgardner said:
Link to the tool is broken unfortunately
Click to expand...
Click to collapse
Not sure what happened there. I did the link over. Try it now:https://docs.google.com/open?id=0BywuYGr-7VrYcURLSjQ5V29pYk0
Some users on droidforums.net had trouble when they just clicked the link. Not sure why, but it worked if they did a copy and paste to the browser.
my bionic will reboot fail to update and then reboot and say update failed i unfroze all the bloatware and still no go
i'm actually having the same issue. im not sure if it has to do with rom tool box as its the app that i used to install custom icons on my status bar or just the fact that im rooted but i can't seem to update to 905...i know i'm on the OTA path as when i go to the updater it shows i have an update for 905 from 902......
yup thats exactly my case as well
Your best best is too fxz to stock and follow these directions.
http://forum.xda-developers.com/showpost.php?p=27832332&postcount=1
Coming from a RAZR, I did the following.
1. Root device on 905
2. Place update in /cache with es
3. Ensure rom manager is installed
4. Click the zip that you placed in the /cache folder.
5. Click reboot and install from the rom manager menu.
6. Allow root permissions
7. It'll boot into stock recovery and boom.
Sent from my DROID BIONIC using Tapatalk 2