Do not use anymore, there is a full SBF available. Flash using RSD Lite or via moto-fastboot.
This is the official ICS OTA update for the NonEFIGS region.
By means of spoofing firmware version as 651.167.21.XT910.NonEFIGSRetail.en.EU in build.prop user mbartosik managed to download 672.180.41.XT910.NonEFIGSRetail.en.EU OTA update from the QA environment.
If you want to thank user mbartosik, please go to this post and press "Thanks" button.
Download:
URL: Blur_Version.651.167.21.XT910.NonEFIGSRetail.en.EU .zip
MD5: c57e495e901f58b0a070bd57c53eb397
Installation:
If you're on a GB build other than 651.167.21.XT910.NonEFIGSRetail.en.EU, flash this SBF prior to continuing with this OTA update. It is recommended to reset the phone to factory defaults in order to avoid FCs and battery drain.
If you're on a clean (no root, no modifications to the system partition, stock recovery) 651.167.21.XT910.NonEFIGSRetail.en.EU (GB 2.3.6), drop the update onto your external microSDHC card, go to recovery and proceed with update. It is recommended to reset the phone to factory defaults in order to avoid FCs and battery drain.
If you're on an ICS leak:
Put the update in your external microSDHC card.
Reboot to AP Fastboot.
Flash this kernel (also courtesy of user mbartosik): moto-fastboot flash boot boot_new_41.img
Flash system_signed from this SBF (unzip it): moto-fastboot flash system system_image
Reboot to recovery, wipe cache and proceed with update.
Note: Only use moto-fastboot in order to avoid preflash validation error when flashing the GB 2.3.6 system_signed.
Bugs:
Apps which use extended GPS commands (e.g. GPS Test and GPS Status & Toolbox) won't report visible satellites etc. This can be fixed by flashing newer U_04.12.00R radio image (again, courtesy of user mbartosik) using BootMenu Manager recovery. Beware, this may impact your 2G, 3G, WiFi and Bluetooth performance - in case of problems, you can revert to U_04.10.00R radio which is shipped with this update by flashing this image (as usual, courtesy of user mbartosik).
Original thread (contains screenshots): http://forum.android.com.pl/f472/wy...d-date-mon-jul-16-11-15-45-cst-2012-a-203392/
Can someone tell us the languages that are included? Much appreciated!
So is this supposed to be the "official ICS"? thx Vatazhka
how do we install it if we are on eclipse or some other custom rom?
romdroid. said:
So is this supposed to be the "official ICS"? thx Vatazhka
how do we install it if we are on eclipse or some other custom rom?
Click to expand...
Click to collapse
you must install service soft by rsd (ICS) and go to second point of OP
for autor
If we are to charge any leaks ICS fastboot package for 651.167.21.XT910.NonEFIGSRetail.en.EU, we also need EternityProject's FastBoot flashME
romdroid. said:
So is this supposed to be the "official ICS"? thx Vatazhka
how do we install it if we are on eclipse or some other custom rom?
Click to expand...
Click to collapse
I only set up the thread - all kudos to mbartosik for pulling the OTA and sharing the patched kernel.
I'm not sure which partitions are being modified by custom firmwares, so flashing the ICS SBF prior to proceeding with the new kernel and GB system might be a safe bet. In theory, you should then flash the attached kernel and 2.3.6 system image, then apply OTA from the stock recovery. However, I stumbled upon preflash validation error when trying to flash system from NonEFIGS 2.3.6 over the leaked 676.226.3.
With regard to FlashME.bat - I don't use Windows. The FlashNIX.sh seems to be a clone of tools shipped within the ICS SBF. I will publish step-by-step tutorial once I get over the preflash validation error.
Sent from my XT910
The steps are really simple to do.
You just need an working ADB on your PC
Fastboot flash boot boot_new.img
Fastboot flash system system_signed
Boot in Recovery, wipe data & cache and apply the update.
All you guys need is the system signed of the based GB Fastboot and the linked boot.img :thumbup:
Sent from my CustomiZed XT910
Is it possible to update to this version from 651.73.30.XT910.NonEFIGSRetail.en.EU (2.3.5)? This is the latest officialy available (non-branded) version in my country (Czech Republic). Thx for the answer.
aaatoel said:
Can someone tell us the languages that are included? Much appreciated!
Click to expand...
Click to collapse
Dansk
Deutsch
English (U.K. & U.S)
Espanol (Espana & Espados Unidos)
Greek
Francais (Canada & France)
Italiano
Nederlands
Norsk bokmal
Polski
Portugues (Brasil & Portugal)
Suomi
Svenska
Turkce
HSD-Pilot said:
The steps are really simple to do.
You just need an working ADB on your PC
Fastboot flash boot boot_new.img
Fastboot flash system system_signed
Boot in Recovery, wipe data & cache and apply the update.
All you guys need is the system signed of the based GB Fastboot and the linked boot.img :thumbup:
Click to expand...
Click to collapse
Well, ADB in this context is only useful to enter AP fastboot mode... I followed this procedure using fastboot binary from the ICS SBF, but an attempt to fastboot flash system system_signed gave me preflash validation error (And yes, I was using the correct SBF.) - any suggestions?
Edit: It seems that the fastboot binary bundled within ICS SBF file is defective. I used moto-fastboot binary from this post and successfully flashed system image!
Besides that, how to update the recovery? Is partition dump the only way?
It should be the same procedure, like we used on EU Leaks. Only the Files have to be changed.
http://forum.xda-developers.com/showthread.php?p=28006523
Sent from my CustomiZed XT910
Can someone tell me what are the differences between 676.226.3.XT910.Retail.en.EU and 672.180.41.XT910.NonEFIGSRetail.en.EU (except numbers, date build, localization and preinstalled apps)? Your feelings in use, speed, smooth or that is something working or not.
I am on retail.en.eu ICS 4.0.4... Is there way to install non EU on my RAZR via fastboot? Or any other? Default ROM in my RAZR was nonEU 2.3.6, so I want to switch to nonEU again. With official ICS nonEU my warranty will back
do u think there will be a fastboot file availabe so we can flash it?
febanovsky said:
I am on retail.en.eu ICS 4.0.4... Is there way to install non EU on my RAZR via fastboot? Or any other? Default ROM in my RAZR was nonEU 2.3.6, so I want to switch to nonEU again. With official ICS nonEU my warranty will back
Click to expand...
Click to collapse
Υes you can, its easy (already done it) :
See the video and follow the instructions steb by step
http://www.youtube.com/watch?v=aCyJcMTwMt8&feature=plcp
But you need to change some files (3&4).
So, the correct files that you will need are:
1) http://forum.xda-developers.com/attachment.php?attachmentid=1080638&d=1337846142 (extract to desktop)
2) SPDREM_U_01.6.5.1-167_SPU-15-M2-1-CEE_1C.91P_0A.6C_RTCEE_CFC_HWp2b_SIGNED.xml.zip (Europeans NonEFGIS) from here: http://sbf.droid-developers.org/umts_spyder/list.php (you will need system_signed archive, copy to desktop )
3) https://hotfile.com/dl/167461766/1e24d34/Blur_Version.651.167.21.XT910.NonEFIGSRetail.en.EU.zip.html (copy to external sd)
4) http://www.mediafire.com/?gqq7qm6j0nq6mmf (rename it: boot_new.img & cope to desktop)
You will need those commands cmd (you can copy and paste)
cd desktop
eprj-mfastboot flash boot boot_new.img
eprj-mfastboot flash system system_signed
(thanks to frastgr)
Vatazhka said:
Well, ADB in this context is only useful to enter AP fastboot mode... I followed this procedure using fastboot binary from the ICS SBF, but an attempt to fastboot flash system system_signed gave me preflash validation error (And yes, I was using the correct SBF.) - any suggestions?
Besides that, how to update the recovery? Is partition dump the only way?
Click to expand...
Click to collapse
fastboot will not work to system_signed
use instead
Code:
moto-fastboot flash system system_signed
Cheers
Edit:
What do we have here?
Moto-fastboot
lol
achillesgk said:
Υes you can, its easy (already done it) :
See the video and follow the instructions steb by step
http://www.youtube.com/watch?v=aCyJcMTwMt8&feature=plcp
But you need to change some files (3&4).
So, the correct files that you will need are:
1) http://forum.xda-developer...8&d=1337846142 (extract to desktop)
2) SPDREM_U_01.6.5.1-167_SPU-15-M2-1-CEE_1C.91P_0A.6C_RTCEE_CFC_HWp2b_SIGNED.xml.zip από εδώ: http://sbf.droid-developer...pyder/list.php (you will need system_signed archive, copy to desktop )
3)https://hotfile.com/dl/167...en.EU.zip.html (copy to external sd)
4) http://www.mediafire.com/?gqq7qm6j0nq6mmf (rename it: boot_new.img & cope to desktop)
You will need those commands cmd (you can copy and paste)
cd desktop
eprj-mfastboot flash boot boot_new.img
eprj-mfastboot flash system system_signed
(thanks to frastgr)
Click to expand...
Click to collapse
I need file from step 3, please
achillesgk said:
Υes you can, its easy (already done it) :
See the video and follow the instructions steb by step
http://www.youtube.com/watch?v=aCyJcMTwMt8&feature=plcp
But you need to change some files (3&4).
So, the correct files that you will need are:
1) http://forum.xda-developer...8&d=1337846142 (extract to desktop)
2) SPDREM_U_01.6.5.1-167_SPU-15-M2-1-CEE_1C.91P_0A.6C_RTCEE_CFC_HWp2b_SIGNED.xml.zip από εδώ: http://sbf.droid-developer...pyder/list.php (you will need system_signed archive, copy to desktop )
3)https://hotfile.com/dl/167...en.EU.zip.html (copy to external sd)
4) http://www.mediafire.com/?gqq7qm6j0nq6mmf (rename it: boot_new.img & cope to desktop)
You will need those commands cmd (you can copy and paste)
cd desktop
eprj-mfastboot flash boot boot_new.img
eprj-mfastboot flash system system_signed
(thanks to frastgr)
Click to expand...
Click to collapse
links from step 1-4 is broken
romdroid. said:
links from step 1-4 is broken
Click to expand...
Click to collapse
found it
link from step 3 in 1 post my mistake - https://hotfile.com/dl/167461766/1e24d34/Blur_Version.651.167.21.XT910.NonEFIGSRetail.en.EU.zip.html
link from 1 step: http://forum.xda-developers.com/attachment.php?attachmentid=1080638&d=1337846142
Thanks, do we still need to download -> " SPDREM_U_01.6.5.1-167_SPU-15-M2-3_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Servic e1FF_fastboot.xml.zip" and unpack it as this tutorial? http://forum.xda-developers.com/showthread.php?p=28006523
Because it's stated 2.3.6 I think we will brick, or?
I wonder if it will work because I am on custom rom..?
romdroid. said:
Thanks, do we still need to download -> " SPDREM_U_01.6.5.1-167_SPU-15-M2-3_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Servic e1FF_fastboot.xml.zip" and unpack it as this tutorial? http://forum.xda-developers.com/showthread.php?p=28006523
Because it's stated 2.3.6 I think we will brick, or?
I wonder if it will work because I am on custom rom..?
Click to expand...
Click to collapse
My battery is charging (60%), I will try soon.
Related
Hi,
I just wanted to know if I can update my atrix (Bell) to 2.3.4 (official) if I have an unlocked bootloader and Rom Manager (CWM 4.0.1.5) without brick my phone ?
Thank you in advance
Yes, download official OTA to your PC.
moto-fastboot boot.img, system.img, radio.img... reboot --- >>> done
You are on official OTA withut screwing up your bootloader.
Thank you very much, but where can I donwload it ???
And "moto-fastboot boot.img, system.img, radio.img... reboot --- >>> done" does not tell me much
belig1234 said:
And "moto-fastboot boot.img, system.img, radio.img... reboot --- >>> done" does not tell me much
Click to expand...
Click to collapse
Get moto-fastboot from here -
http://forum.xda-developers.com/showthread.php?t=1138092
Download Bell GB radio from here -
http://www.multiupload.com/0ZECKA3QZ1
Download ATT system and boot from here (they will work fine on your phone) -
http://forum.xda-developers.com/showthread.php?t=1163342
You can also use the flashing instructions form the above thread, except add the radio from first step, and your instructions will look like this:
1. extract moto-fastboot to your C: drive
2. place the downloaded radio.img, system.img and boot.img in the moto-fastboot folder
3. boot your phone into fastboot mode by holding down the bottom volume button while pressing power, press volume button up, wait for it to say "starting fastboot protocol".
4. connect your phone to your PC (make sure the USB drivers are installed)
5. go to moto-fastboot folder, right click while holding shift, select "open command prompt here"
6. type in "moto-fastboot devices" ENTER, make sure your phone is recognized.
7. then:
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
moto-fastboot flash radio radio.img
moto-fastboot -w
moto-fastboot reboot
8. Done.
Oh god, thank you so much, I love you (no homo) !!
well, it doesn't seem to work.. what about if i do the OTA update... Will I get bricked ?
Anyways with android 2.3.4 I'll always be able to unlock the bootloader again...
belig1234 said:
well, it doesn't seem to work.. what about if i do the OTA update... Will I get bricked ?
Anyways with android 2.3.4 I'll always be able to unlock the bootloader again...
Click to expand...
Click to collapse
Could you elaborate which step exactly didn't work? I am sure it's fixable.
P.S. I also found an easier way of updating. There is a CWM update file of a 2.3.4 - http://forum.xda-developers.com/showthread.php?t=1195922
This one is slightly modded, but very easy - just flash it through CWM, wipe data and reboot.
belig1234 said:
Anyways with android 2.3.4 I'll always be able to unlock the bootloader again...
Click to expand...
Click to collapse
Once your bootloader is unlocked, you cannot lock it again. Once unlocked, always unlocked.
CaelanT said:
Once your bootloader is unlocked, you cannot lock it again. Once unlocked, always unlocked.
Click to expand...
Click to collapse
Is there some way to make it not show "unlocked"? I thought there was.
jiggytom said:
Is there some way to make it not show "unlocked"? I thought there was.
Click to expand...
Click to collapse
You can SBF flash to 2.2.2, and the "Unlocked" text will disappear from the boot screen, that is if you don't HARD BRICK.
This is the only way, but THERE IS A VERY HIGH CHANCE OF HARD BRICKING.
So, I don't recommend it unless you know what you are doing.
What is the condition you might hard brick? I have an ATT attrix that the wifi/Bluetooth chip is faulty and I need to get a replacement. Worst case is I return it with the unlocked bootloader.
Sent from my MB860 using XDA App
jiggytom said:
What is the condition you might hard brick? I have an ATT attrix that the wifi/Bluetooth chip is faulty and I need to get a replacement. Worst case is I return it with the unlocked bootloader.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
If you have previously updated to official 2.3.4 OTA, then you will hardbrick. (flashed more than just the radio, system, boot partitions)
xploited said:
If you have previously updated to official 2.3.4 OTA, then you will hardbrick. (flashed more than just the radio, system, boot partitions)
Click to expand...
Click to collapse
I originally unlocked with pudding and then ran the HKTW build. After that I used custom roms via cwm...never did an official update. So I should technically be safe right?
If I sbf to 1.8.3, can I get back to 2.3.4 using cwm? I don't lose the unlock right?
Sent from my MB860 using XDA App
jiggytom said:
I originally unlocked with pudding and then ran the HKTW build. After that I used custom roms via cwm...never did an official update. So I should technically be safe right?
If I sbf to 1.8.3, can I get back to 2.3.4 using cwm? I don't lose the unlock right?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yes, technically, you are safe.
If you sbf to 1.8.3 you will have to reflash pudding. SBFing messes up the unlock.
Thanks for your help!!!!
xploited said:
Could you elaborate which step exactly didn't work? I am sure it's fixable.
Click to expand...
Click to collapse
Hum it tells me : 'Moto-fastboot devices' is not recognized as an internal or external command, operable program or batch file.
P.S. I also found an easier way of updating. There is a CWM update file of a 2.3.4 - http://forum.xda-developers.com/showthread.php?t=1195922
Click to expand...
Click to collapse
Do I really need tenfar's recovery ? Or can I just install it on CWM 4.0.1.5 ?
Thank you a lot for you time... !!
belig1234 said:
Hum it tells me : 'Moto-fastboot devices' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
Which version of moto-fastboot did you download? Please, list the files which are located in your moto-fasboot folder. Are you sure you have launched the command prompt from the moto-fasboot folder?
When you start, your command prompt should read:
C:\moto-fastboot
belig1234 said:
Do I really need tenfar's recovery ? Or can I just install it on CWM 4.0.1.5 ?
Thank you a lot for you time... !!
Click to expand...
Click to collapse
Yes, you need Tenfar's Unlocked recovery, or romracer's unlocked recovery.
xploited said:
Which version of moto-fastboot did you download? Please, list the files which are located in your moto-fasboot folder. Are you sure you have launched the command prompt from the moto-fasboot folder?
When you start, your command prompt should read:
C:\moto-fastboot
Yes, you need Tenfar's Unlocked recovery, or romracer's unlocked recovery.
Click to expand...
Click to collapse
I donwloaded it where you told me to ( http://forum.xda-developers.com/showthread.php?t=1138092
List of the files in moto-fastboot folder ;
1.META-INF (folder)
2.boot.img
3.bp.img
4.date.img
5.motofasboot32
6.radio.img
7.system.img
8.webtop.img
By the way, if I install the new version with the OTA, will it brick my phone ?
Thank you very much for you time it's very appreciated... !!
belig1234 said:
I donwloaded it where you told me to ( http://forum.xda-developers.com/showthread.php?t=1138092
List of the files in moto-fastboot folder ;
1.META-INF (folder)
2.boot.img
3.bp.img
4.date.img
5.motofasboot32
6.radio.img
7.system.img
8.webtop.img
By the way, if I install the new version with the OTA, will it brick my phone ?
Thank you very much for you time it's very appreciated... !!
Click to expand...
Click to collapse
Download this exact version of moto-fastboot - http://forum.xda-developers.com/attachment.php?attachmentid=635584&d=1308928440
(remove the one you currently have except for the .img files).
Extract it to C: directory and then do the "moto-fasboot" commands, they will work.
Updating via OTA will most likely work, but it will mess up the bootloader (you will not longer be Unlocked) + you won't be able to flash back.
So, the way i proposed is safer. For starters, you can flash the boot.img and system. img only via moto-fastboot (It's all you really need).
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
moto-fasboot -w
moto-fastboot reboot
You will then have a fresh 2.3.4 stock system. If everything is alright, you can update the radio.img as well, and webtop.img if you use it.
THESE STEPS PROBABLY DON'T WORK, SO DO NOT USE THEM!!
So, I've been thinking about how a number of people with Photons that accidentally flashed the 2.3.5 US Cellular SBF and lost 4G would like to get it back.
You will need to exact the CG*.smg files from 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_6-CM-release-keys-signed-Sprint-US
Plus obtain a bootstrap flashable .zip of stock 198_6 or a stock nandroid system.img of 198_6.
You can use MotoAndroidDepacker.exe by Skrilax_CZ version 1.3 to unpack the SBF into the CG*.smg files.
You will also need 1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US if you are not totally stock Electrify, and if you want to recover from messing this up.
Finally, you will need the leaked Blur_Version.45.3.6.MB855.Sprint.en.US.zip OTA.
Here's the general idea laid out...
1. Charge your battery to 100% full capacity
2. Make sure you are on the stock 2.3.5 USCC SBF (use RSD if necessary)
3. Enter stock recovery and select wipe data/factory reset
4. Boot back into Android, skip the setup wizard
5. Shutdown device and start up in Fastboot
6. Run: moto-fastboot flash webtop CG61.smg
7. Run: moto-fastboot reboot
8. Wait for device to boot back into Android
9. Shutdown device and start up in Fastboot
10. Run: moto-fastboot flash preinstall CG65.smg
11. Run: moto-fastboot reboot
12. Wait for device to boot back into Android
13. Enable USB mass storage mode and copy root + APK files to microSD card
14. Root, sideload Superuser APK
15. Sideload Bootstrap APK
16. Ensure battery is charged to 100% again (for RSD bailout)
17. Enter Bootstrap recovery mode
18. Select wipe data/factory reset
19. Restore Nandroid system.img of 198_6 or install a stock 198_6 .zip file
20. Reboot into stock recovery
21. Apply official 2.3.5 Sprint update.zip which will update the 2.3.4 files to 2.3.5 as well as flash the new AP20 and bp.img radio!
Note: Use http://sourceforge.net/projects/ext2read/ to open CG60.smg CG61.smg and CG65.smg
Note: Do not do moto-fastboot flash system CG60.smg or you will get Failed to boot 4 error
So, any thoughts if this would be a feasible process?
I think, this is possible.
Except that fastboot flash webtop.?
It's bad, that sbf depacker doesn't work with photon sbfs.
attaching good depacker
The reason I added the step to flash the webtop image is because the 2.3.5 update.zip performs an assertion check on a bunch of files in the webtop partition. So, they have to match or else the patching will fail and the radio update at the end will never happen.
I also noticed that the update script checks the boot and recovery's md5sum, so those will also have to be flashed in through a custom bootstrap .zip file.
olegfusion said:
attaching good depacker
Click to expand...
Click to collapse
If this is able to re-pack the SBF, then there is no need for the fastboot stage! One can just replace the codegroups within the SBF and then flash that. Not sure if there is anything preventing replacement there though.
brianez21 said:
If this is able to re-pack the SBF, then there is no need for the fastboot stage! One can just replace the codegroups within the SBF and then flash that. Not sure if there is anything preventing replacement there though.
Click to expand...
Click to collapse
I don't this can simply repack. It will allow the repack to happen, but it fails instantly upon trying to flash it through RSD. And I didn't make any modifications. Just unpacked the stock 2.3.5 SBF, and then compiled it again.
Might be some sort of signature check failing then...? Not sure.
Does anyone here have a good understanding of how RSD/the Photon's flashing process works?
brianez21 said:
Might be some sort of signature check failing then...? Not sure.
Does anyone here have a good understanding of how RSD/the Photon's flashing process works?
Click to expand...
Click to collapse
Would have to be. I don't think there is anything different about the recompiled SBF I created. Compared it to the original one and they are exactly the same size.
Hi
Link to particular files will be appreciated, have some files already, got some files by searching, but some file still missing. can anyone point me to right direction ?
A guide below is obsolete, just use the fastboot file to flash LATAM ICS over anything: http://forum.xda-developers.com/showthread.php?t=1753383
PS. You can still use the part of the guide below and read thru this thread on how to restore the block18.
A few people have already asked in another thread, so I've decided to post a little more elaborate guide.
This post is just a compilation of knowledge/files from other threads/forums, it wouldn't have been possible without FrAsErTaG, Leisures and Igorls1. Many thanks to pedrotorresfilho for getting us a link to the official LATAM ICS OTA. If you find this post useful, click on the usernames above to buy them a beer.
This applies to you if you have an American (LATAM/USA/Canada) *GSM* Razr XT910 and flashed the other region ICS leak with the secure kernel (so you can't just flash LATAM Gingerbread onto you device). If you don't have an American GSM Razr -- this thread does not apply to you (tho might be helpful).
If you do not have a backup of your block18, you might as well stay on your current ICS leak. If you do have a backup of your block18 then read along.
Before proceeding, make sure that:
You have a GSM Droid RAZR (not CDMA)
Your phone is from Latin America or Canada (and NOT Europe, Middle East, Asia or Oceania)
You have a backup of the block18 (and it is on your external sdcard and it's called mmcblk1p18-back)
You are currently running T-mo or en.eu ICS leak
If any of the above is not true or you are not sure/don't know about any of the above, DO NOT PROCEED!
The overview of what you need to do is:
Download all the files
Prepare your phone to apply LATAM ICS OTA
Apply LATAM ICS OTA
Root LATAM ICS OTA
Restore your CID/block18
1. Download all the files
1.1. You will need to grab all 3 files from here: http://www.mediafire.com/?0syxru14b655fat,j2gq00ehmjqodtm,i47d1lx499ttw77 then you will need to unrar them. Make sure there are no errors during unrar, otherwise redownload. When you unrar these files place them in the folder called "update to ICS br".
1.2. Grab the cdrom.zip file here: http://www.multiupload.nl/HL56KM413P and unpack it. You should have the cdrom.img file.
1.3. [Optional] I have slightly modified the rooting script you can grab it from the attachment or download it here: http://www.multiupload.nl/DWON0FR7HK I will go into detail why I've created it further down this page.
1.4. The method below has not been tested by me with the new OTA (same filename) which has been released 3rd week of June. If you want to try it out, make sure you grab the new OTA from here and copy it to the folder "update to ICS br" (see 1.1 above).
2. Prepare your phone to apply LATAM ICS OTA
2.1. Copy the file Blur_Version.651.167.3370.XT910.Brasil.en.BR.zip from the folder "update to ICS br" (see 1.1 above) and file cdrom.img (see 1.2 above) to your *external* (removable, located next to the sim-slot) sdcard.
2.2. Get your phone in AP Fastboot mode: power it down, then press Vol Up, Vol Down and Power button until you see a menu. Scroll down to AP Fastboot with the Vol Down key and select AP Fastboot with the Vol Up key.
2.3. In Windows (works fine in VMWare Fusion if you're on Mac) go to the folder "update to ICS br" and run the file "Fix Update.bat" there. It will flash the patched boot and recovery images to your phone (very quickly) and then it will also flash the system image from the GB Rom which is required by the OTA. Your time will vary but it can take up to 20-30 minutes to flash the system image, be patient and DO NOT interrupt this process.
2.4. If you don't see any errors -- power down your phone and proceed further.
3. Apply LATAM ICS OTA
3.1. Press Vol Up, Vol Down and Power button until you see a menu. Scroll down to Recovery with the Vol Down key and select Recovery with the Vol Up key. Once you see a green robot on your screen press Vol Up and Vol Down keys simultaneously.
3.2. Select "Clean Cache" from the menu and run it.
3.3. [OPTIONAL] Select "Wipe Data/Factory reset" from the menu and run it. The instructions I followed didn't include this step, however my phone wouldn't boot into ICS without wipe. If you don't mind restoring your apps, wipe.
3.4. Select "Install update from SD card", select the file Blur_Version.651.167.3370.XT910.Brasil.en.BR.zip and let it update.
3.5. When the update has successfully completed, select Reboot from the menu and...
3.6. Press Vol Up and Vol Down keys as the phone is about to reboot untill you see a menu. Scroll down to BP Tools with the Vol Down key and select BP Tools with the Vol Up key.
3.7. Your phone should now boot into ICS. Give it a good few minutes to boot and if it's stuck in the pulsing M logo, rerun steps 3.1, 3.2, 3.3, 3.5, 3.6 (in short: clean cache, wipe data and reboot but do not reapply update).
4. Root LATAM ICS OTA
Now that your phone has shiny new ICS running on it, it's time to root it. I've mentioned above that I have modified the original rooting script and there's a reason for that. With the original script you may run into issues with the su/busybox locations/permissions with *some* apps (like LuckyPatcher). I would highly recommend you perform step 1.3 and grab my modified rooting script.
The rooting method below only works if your CID is erased. If you erase your CID without having the block18 backup you will forever have to start up your phone with the BP Tools and you will not have USB Storage working. Do not use this rooting method if you do not have the block18 backup!!!
Another rooting method for the XT910 ICS builds is posted here: http://forum.xda-developers.com/showthread.php?t=1707431.
4.1. [OPTIONAL] Extract the files from the newroot.zip (see step 1.3 above) into "update to ICS br\ROOT" folder. You will need to overwrite files already there.
4.2. Go into Settings -> Developer on your phone and enable "USB Debugging".
4.3. In Windows run the file "Root.bat" from the folder "update to ICS br\ROOT". When you run this file, you will be prompted to boot into AP Fastboot, boot with BP Tools (twice) and then boot into AP Fastboot again. You will then still need to boot with BP Tools into ICS. See step 2.2 on how to boot into AP Fastboot and step 3.6 on how to boot with BP Tools.
4.4. You should be back into the ICS world with the root now. You can verify you have root by locating/running the Superuser app from the drawer.
5. Restore your CID/block18
5.1. Make sure you have the "cdrom.img" (see step 2.1) and "mmcblk1p18-back" (your block18 backup) on your external SD card.
5.1.1. As FrAsErTaG pointed out it's crucial to confirm the cdrom.img is correct before flashing it. The MD5 hash should be: f0c13bbc8cf294478562a85c9d255beb. Check if the MD5 hash is correct with the following command:
PHP:
md5sum /sdcard-ext/cdrom.img
5.2. Run command prompt in Windows (Start -> run program/search -> type cmd and hit Enter), use the cd command to switch to the "update to ICS br" folder and type in (better yet copy/paste) the following commands:
PHP:
adb shell
su
dd if=/sdcard-ext/cdrom.img of=/dev/block/mmcblk1p16
cat /mnt/sdcard-ext/mmcblk1p18-back> /dev/block/mmcblk1p18
If you cannot drop into adb shell (your prompt will change) or if you get an error after running su or dd commands -- abort everything and DO NOT attempt any commands after the failed one.
5.3. If you do not see any errors -- power down your phone and then power it up -- you should no longer see the CID error message and should be able to boot without BP Tools, yay!
PS. If you find the step 5.2 confusing -- post here. I assumed everyone reading knows their way around Windows folders with cd, but maybe I'm wrong.
PPS. After you've rooted I highly recommend you download the Titanium Backup and buy a Titanium Backup Pro key to freeze bloatware and backup/restore your apps. It's a great app and the developer is awesome!
stangri said:
PS. If you find the step 5.2 confusing -- post here. I assumed everyone reading knows their way around Windows folders with cd, but maybe I'm wrong.
Thanks to: igorls1 for the mediafire link, FrAsErTaG and Leisures for the rooting script/files.
Click to expand...
Click to collapse
Nice, really nice posting stangri!
Btw. I didn't get the 5.2 step. Lol
I had linked your post in the ota thread, may I link to this one?. Its much better and clear.
Congrats!
Enviado de meu XT910 usando o Tapatalk 2
btw mediafire links are my too xD
And the dd cdrom was figured out by myself, also you need to warn flashing wrong cdrom will brick, you also should check md5 sum of CDROM after its transferred to sdcard.
Sent from my XT910 using XDA
FrAsErTaG said:
And the dd cdrom was figured out by myself, also you need to warn flashing wrong cdrom will brick, you also should check md5 sum of CDROM after its transferred to sdcard.
Sent from my XT910 using XDA
Click to expand...
Click to collapse
Could you please explain how to check the md5 on the cdrom.img in the external sd? I can't seem to find it in OP's post. Thanks, will try this in the morning.
cygnae said:
Could you please explain how to check the md5 on the cdrom.img in the external sd? I can't seem to find it in OP's post. Thanks, will try this in the morning.
Click to expand...
Click to collapse
from adb shell
type
md5sum /sdcard-ext/cdrom.img
Click to expand...
Click to collapse
Can we to root retail eu with your script ?
nespresso33 said:
Can we to root retail eu with your script ?
Click to expand...
Click to collapse
Yes, leisures patched it to work on EU leak.
actually it does not work on the eu leak...i get preflash verification failed on boot403.img , and everything fails after that.
Killer2k8 said:
actually it does not work on the eu leak...i get preflash verification failed on boot403.img , and everything fails after that.
Click to expand...
Click to collapse
you have to erase your CID before running the root package.. but dont do that unless you have a mmcblk18 backup
i have a backup from when i was on 2.3.6, i still have the backup, but how can i erase the cid when i have no root?
Killer2k8 said:
i have a backup from when i was on 2.3.6, i still have the backup, but how can i erase the cid when i have no root?
Click to expand...
Click to collapse
fastboot flash allow-mbmloader-flashing-mbm.bin
fastboot reboot-bootloader
fastboot erase cid
Sent from my XT910 using XDA
pedrotorresfilho said:
I had linked your post in the ota thread, may I link to this one?. Its much better and clear.
Click to expand...
Click to collapse
Thanks, of course feel free to link it.
thanks! i am now rooted.
BUT for others:
AFTER: in Root.bat
echo If the id is 0 / root then continue, otherwise ctrl+c to cancel and start over
@pause
adb wait-for-device
Put:
adb shell mount -o rw,remount /system
Or else it will fail.
I now have root, restored my cid...everything is again smooth ) Thanks!
Killer2k8 said:
thanks! i am now rooted.
BUT for others:
AFTER: in Root.bat
echo If the id is 0 / root then continue, otherwise ctrl+c to cancel and start over
@pause
adb wait-for-device
Put:
adb shell mount -o rw,remount /system
Or else it will fail.
I now have root, restored my cid...everything is again smooth ) Thanks!
Click to expand...
Click to collapse
You are the first person to have issues with the script.. interesting...
Sent from my XT910 using XDA
yeap....i`m happy it worked till the end really smooth! Thank you again!
I don't have mmcblk18 backup.
I am on eu leak, can I do a backup now ?
nespresso33 said:
I don't have mmcblk18 backup.
I am on eu leak, can I do a backup now ?
Click to expand...
Click to collapse
only if you have root, if you don't sit tight there is another root method but it is not released yet, expect it to appear after the official release.
It is being postponed to allow it to work on the final release and not be patched and ultimately delay the final release of ICS.
Killer2k8 said:
thanks! i am now rooted.
BUT for others:
AFTER: in Root.bat
echo If the id is 0 / root then continue, otherwise ctrl+c to cancel and start over
@pause
adb wait-for-device
Put:
adb shell mount -o rw,remount /system
Or else it will fail.
I now have root, restored my cid...everything is again smooth ) Thanks!
Click to expand...
Click to collapse
Oh, my bad man, I forgot the adb remount command in my rooting script -- it is now fixed, thanks!
stangri said:
Oh, my bad man, I forgot the adb remount command in my updated script -- it is now fixed, thanks!
Click to expand...
Click to collapse
Lol sounds odd. " I forgot the adb remount command in my updated script"..
Uploaded? Outdated?
Enviado de meu XT910 usando o Tapatalk 2
Edit: Linked in ICS Retail.BR thread. Thanks man
Hello guys,
Let me preface this with the fact that I have been searching this forum for the past hour and could not find anything pertinent for my situation.
I've updated to the latest GSM OTA (the Vodafone EU one) and all was great, decided to reboot my phone and got into a bootloop. I don't have a recovery to boot from and going to be short on battery soon.
The way I see it, I'm stuck with a bricked phone until the RSD package for the OTA is released. Is that correct? am I missing anything?
Can anyone point me to a relevant thread where I can catch a break?
Cheers!
tuxcomputing said:
Hello guys,
Let me preface this with the fact that I have been searching this forum for the past hour and could not find anything pertinent for my situation.
I've updated to the latest GSM OTA (the Vodafone EU one) and all was great, decided to reboot my phone and got into a bootloop. I don't have a recovery to boot from and going to be short on battery soon.
The way I see it, I'm stuck with a bricked phone until the RSD package for the OTA is released. Is that correct? am I missing anything?
Can anyone point me to a relevant thread where I can catch a break?
Cheers!
Click to expand...
Click to collapse
Fixed, please close.
How did you fixed it?
Sent from my XT910 using xda premium
Please tell us how you fixed this, i have same problem but i already screwed it up more by trying to flash back to ics after i was stuck at boot on JB vodafone. Now i have bricked phone and i wait for Fastboot files, which we dont know when will come out
Got the same problem here
Alright, here goes.
I am not responsible to whatever happens to your phones. This process is described for the Vodafone OTA.
Also, you will lose root
I'm guessing your phones are in a constant bootloop right about now. If they are, you have to make sure you still have some battery left so that on AP Fastboot it shows battery OK. If you don't, follow the guides here to get more juice or get a 'factory cable' and charge your phone.
To download:
- Fastboot from here: http://dfiles.eu/files/bih3tmg7b
- OTA kernel (here: http://d-h.st/xat )
- The whole OTA here ON YOUR SDCARD
- original ICS RSD Image here
Process:
Extract the fastboot somewhere accessible like c:/fastboot
Extract the kernel and the original ICS files on your desktop
Copy the OTA kernel (boot_3.0.8-g7198280) to your c:/fastboot folder
Copy 'system_signed' from the original ICS archive to your fastboot folder
Open the command prompt (search for cmd.exe in your programs)
Navigate to c:/fastboot (use "cd .." to excape a folder and "dir" to list the files in a folder )
Go to AP fastboot on your phpne and do the following from the command prompt:
fastboot flash boot boot_3.0.8-g7198280.img
fastboot flash system system_signed
fastboot reboot-bootloader
Now restart your phone and enter recovery the normal way volUp+volDown + power button then select Recovery, then volUp+volDown to see the menu.
Do a factory reset
Flash the OTA (that should be on your card)
Reboot
Ta-da!
If after the whole process you get a flash failure when rebooting your phone, use this guide to get rid of that: http://forum.xda-developers.com/showthread.php?t=1634223
If this helped you, please show the 'Thanks' button some love. Also, post here if you run into trouble, DO NOT PM!
tuxcomputing said:
Alright, here goes.
I am not responsible to whatever happens to your phones. This process is described for the Vodafone OTA.
Also, you will lose root
I'm guessing your phones are in a constant bootloop right about now. If they are, you have to make sure you still have some battery left so that on AP Fastboot it shows battery OK. If you don't, follow the guides here to get more juice or get a 'factory cable' and charge your phone.
To download:
- Fastboot from here: http://dfiles.eu/files/bih3tmg7b
- OTA kernel (here: http://d-h.st/xat )
- The whole OTA here ON YOUR SDCARD
- original ICS RSD Image here
Process:
Extract the fastboot somewhere accessible like c:/fastboot
Extract the kernel and the original ICS files on your desktop
Copy the OTA kernel (boot_3.0.8-g7198280) to your c:/fastboot folder
Copy 'system_signed' from the original ICS archive to your fastboot folder
Open the command prompt (search for cmd.exe in your programs)
Navigate to c:/fastboot (use "cd .." to excape a folder and "dir" to list the files in a folder )
Go to AP fastboot on your phpne and do the following from the command prompt:
fastboot flash boot boot_3.0.8-g7198280.img
fastboot flash system system_signed
fastboot reboot-bootloader
Now restart your phone and enter recovery the normal way volUp+volDown + power button then select Recovery, then volUp+volDown to see the menu.
Do a factory reset
Flash the OTA (that should be on your card)
Reboot
Ta-da!
If after the whole process you get a flash failure when rebooting your phone, use this guide to get rid of that: http://forum.xda-developers.com/showthread.php?t=1634223
If this helped you, please show the 'Thanks' button some love. Also, post here if you run into trouble, DO NOT PM!
Click to expand...
Click to collapse
I tried your method but I get a:
Preflash validating failure
when writing the system_signed to the device
pirondello said:
I tried your method but I get a:
Preflash validating failure
when writing the system_signed to the device
Click to expand...
Click to collapse
That's weird. Prolly the flash was messed up somewhere..
Try this before "fastboot flash boot boot_3.0.8-g7198280.img":
extract recovery_signed and allow-mbmloader-flashing-mbm.bin from the ICS folder and put them into the fastboot folder
do this
fastboot flash mbm allow-mbmloader-flashing-mbm.bin
fastboot reboot-bootloader
fastboot flash recovery recovery_signed
Let me know if that works
tuxcomputing said:
That's weird. Prolly the flash was messed up somewhere..
Try this before "fastboot flash boot boot_3.0.8-g7198280.img":
extract recovery_signed and allow-mbmloader-flashing-mbm.bin from the ICS folder and put them into the fastboot folder
do this
fastboot flash mbm allow-mbmloader-flashing-mbm.bin
fastboot reboot-bootloader
fastboot flash recovery recovery_signed
Let me know if that works
Click to expand...
Click to collapse
Unfortunately still the same problem, can't flash the system_signed file.
Really appreciate your help, thank you anyway!
tuxcomputing said:
That's weird. Prolly the flash was messed up somewhere..
Try this before "fastboot flash boot boot_3.0.8-g7198280.img":
extract recovery_signed and allow-mbmloader-flashing-mbm.bin from the ICS folder and put them into the fastboot folder
do this
fastboot flash mbm allow-mbmloader-flashing-mbm.bin
fastboot reboot-bootloader
fastboot flash recovery recovery_signed
Let me know if that works
Click to expand...
Click to collapse
Well i give you thumbs up and thanks for you helping hand, however it still doesnt work gives preflashvalidation failure on system_signed flashing. If you have some more ideas it would be really nicce to try, meanwhile i think we will just have to wait for fastboot files. Verizon version for xt912 got FF already maybe we will get ours in a week or so.
Use this method .. Hsd pilot again nailed it to save our asses ..
It should definatly unbrick your mobile because i tried it on same version and i am back on jellybean ..
http://forum.xda-developers.com/showthread.php?t=2194825
Hit the thx to hsd pilot on the op and me if ya think i helped ya to share link :thumbup:
Thx in advance btw
Sent from my Droid Razr HD (4GLTE) using Tapatalk 2
Edit: Always refresh before you reply
anurag.dj2u said:
Use this method .. Hsd pilot again nailed it to save our asses ..
It should definatly unbrick your mobile because i tried it on same version and i am back on jellybean ..
http://forum.xda-developers.com/showthread.php?t=2194825
Hit the thx to hsd pilot on the op and me if ya think i helped ya to share link :thumbup:
Thx in advance btw
Sent from my Droid Razr HD (4GLTE) using Tapatalk 2
Click to expand...
Click to collapse
Didn't work for me. Flashing went fine but when trying to enter recovery I get "Invalid Flash Mode (S) (Boot Failure)
HSD-Pilot said:
Edit: Always refresh before you reply
Click to expand...
Click to collapse
Sorry again :thumbdown:
Sent from my Droid Razr HD (4GLTE) using Tapatalk 2
No, you was first, i mean myself
HSD-Pilot said:
No, you was first, i mean myself
Click to expand...
Click to collapse
TeddyOFLove said:
Well i give you thumbs up and thanks for you helping hand, however it still doesnt work gives preflashvalidation failure on system_signed flashing. If you have some more ideas it would be really nicce to try, meanwhile i think we will just have to wait for fastboot files. Verizon version for xt912 got FF already maybe we will get ours in a week or so.
Click to expand...
Click to collapse
For your information, I managed to unbrick my phone. Problem seemed to be my CID.IMG. After erasing it, I could enter recovery and installl JB from ext-sdcard. Now I have to use BP Tools tools to boot, because as soon as I restore CID, the device doesn't boot.
Really strange, because my phone is actually from Europe (d/a/ch), Switzerland. Maybe it's due to the fact that I switched to the chinese JB Ota leak before updating to the EU leak.
Hi,
After much read of guides, I post here my SIMPLE guide for OTA upgrades when your Moto G is unlocked and you use systemless root and TWRP.
This guide is safe and works!
For example, with this guide you can upgrade from STOCK MPJ24.139-23.4 to MPJ24.139-63:
Warning: I assume you know the concepts "fastboot", "systemless root" and TWRP.
For the original stock firmware search here for your exact MODEL and VERSION: http://mirrors.lolinet.com/firmware/moto/athene/official/
1) Reboot to TWRP and make a FULL BACKUP of your current firmware. Use the SD-Card and not the internal memory.
2) To Apply the OTA you need to restore BOOT.IMG and SYSTEM.IMG.
2a) If you rooted your device, for sure your BOOT.IMG isn't the original one. You can:
- Option 1: Restore it from an original backup of your firmware (if you backup it prior to root).
- Option 2: Download the STOCK and ORIGINAL firmware for your device, extract "boot.img" and flash it in the fastboot mode using "fastboot flash boot boot.img".
2b) If you use Systemless SuperSU then your system partition can be untouched. In case of doubt, or if the patch shows an error, you can restore it...
- Option 1: Restore it from one backup of your firmware (only if you backup it prior to root).
- Option 2: Download the STOCK and ORIGINAL firmware for your device, extract "system.img_sparsechunk.0-7" and flash them in the fastboot mode using these 8 commands (execute one, wait until completes, then execute the next one):
Code:
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
3) Boot to the TWRP Custom Recovery (you don't need to restore the original Recovery partition).
4) Download the OTA (Blur_Version.24.24.4.athene.retail.en.US.zip) or copy it from the downloaded directory. Copy the ZIP file to a computer, extract the file "/META-INF/com/google/android/updater-script" and edit it... Remove these three lines (this only removes the check of the running build, because you like to execute it inside TWRP):
Code:
getprop("ro.build.thumbprint") == "6.0.1/MPJ24.139-63/64:user/release-keys" ||
getprop("ro.build.thumbprint") == "6.0.1/MPJ24.139-23.4/4:user/release-keys" ||
abort("Package expects build thumbprint of 6.0.1/MPJ24.139-63/64:user/release-keys or 6.0.1/MPJ24.139-23.4/4:user/release-keys; this device has " + getprop("ro.build.thumbprint") + ".");
After that, copy (repack) this edited file to the ZIP file of the OTA. I suggest to change the name of the ZIP, for example to "Blur_Version.24.24.4.athene.retail.en.US-TWRP.zip". Now, you can run this patch file running TWRP.
5) Copy the patch OTA file to the SD-CARD, boot to the TWRP and apply the OTA... After several minutes the task completes. Reboot and check if the update is done and all works well. Your data needs to be already there...
6) Reboot into the fastboot mode and reflash the TWRP Custom Recovery using "fastboot flash recovery twrp-3.0.2-0-athene.img". Then boot in the recovery mode and do another Backup (for save untouched "system.img" and "boot.img" partitions).
7) Now you can re-root using the TWRP mode and SuperSU 2.78 in Systemless mode (remember to execute "echo SYSTEMLESS=true>>/data/.supersu" prior to install the SuperSU.zip)
I hope this helps you!
This guide only uses the minimum and required steps.
:good:
If you like to download one already patched OTA, then download it from here (join the two files first!):
Part 1: http://www.sendspace.com/file/dkws7p
Part 2: http://www.sendspace.com/file/xaompg
Part 1: http://www.sendspace.com/file/e3of46
Part 2: https://www.sendspace.com/file/a3tl4r
CRC:
filename=Blur_Version.24.24.4.athene.retail.en.US-TWRP.zip
size=508332365
crc32=AFEC5752
Thank you, I was wondering about just this. Will come In handy.
Do you need to resign the zip with signapk?
Thanks for you guide!
I used it to update my Lenovo P2 to Nougat.
I would love to unlock my phone, alas, I am on an amazon variant of the G4, so it cannot be done. I would love to try out the OS listed here.
Indianvixen9 said:
I would love to unlock my phone, alas, I am on an amazon variant of the G4, so it cannot be done. I would love to try out the OS listed here.
Click to expand...
Click to collapse
I've heard this from a few people. I got the Amazon variant little more than a week ago. Unlocked BL and rooted lickety splits, no issues.
I consider myself pretty tech savvy, but the post might as well have been in Swahili. Can it be dumbed down any further?
The links at the end of your post for the two patched ota downloads aren't any good, would you please upload them again? Thanks
t0mm13b said:
Do you need to resign the zip with signapk?
Click to expand...
Click to collapse
No, just re-zip! :victory:
Dbush72 said:
The links at the end of your post for the two patched ota downloads aren't any good, would you please upload them again? Thanks
Click to expand...
Click to collapse
Done! :highfive:
Thank you for the reply and refreshing the download links
As far as I can tell you are flashing this via TWRP which is why the zips dont need signed is that correct?
I have an xt1625 non-amazon version that im working with.
I tried flashing Blur_Version.25.11.12.athene.retail.en.US on top of ATHENE_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml which didnt work with this error:
E3005: "EMMC:/dev/block/bootdevice/by-name/boot:
has unexpected contents
I also tried flashing Blur_Version.25.11.12.athene.retail.en.US on top of ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml
Failed with the same error as last time
I also tried flashing Blur_Version.24.31.48.athene.retail.en.US on top of ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml which does seem to pass the version checks but gives this error:
"eom/app/BRApps2/oat/arm/BRApps.odex" has unexpected contents.