Related
---------------------------------------------------------------------------
I HAVE CEASED UPDATING THIS THEAD.
The old information contained below will remain for posterity, but will no longer be updated. From this point forward, all updates to this information will be found at http://www.randomphantasmagoria.com/firmware/nexus-s
---------------------------------------------------------------------------
Below is a list of all available OTA and full ROM packages for the Nexus S, model I9023.
THIS IS FOR I9023 ONLY. IF YOU HAVE ANOTHER VARIANT, PLEASE FIND THE THREAD FOR YOUR VARIANT.
Typical disclaimer where I tell you that all of this stuff is at your own risk and I'm not responsible if you mess up your phone, yadda yadda.
These updates are 100% stock and are NOT rooted.
HOW TO FLASH
I'm not giving instructions on how to flash ZIP files or fastboot images. If you don't know how to do that, you probably shouldn't be looking for stuff in this thread. There are plenty of threads on how to flash fastboot images or how to flash zips through recovery. Do a little reading before proceeding.
The recovery-flashable full ROM packages will only flash if your phone has no ROM, any custom ROM, or a stock ROM that's older than the version you're trying to flash. For instance, the 2.3.4 full ROM package will flash over the stock 2.3.3 ROM, but not over the stock 2.3.6 ROM.
With fastboot images, you can flash any version over any other version.
WHAT HAPPENS IF I GET AN ERROR WHILE FLASHING?
If you get an error flashing a recovery-flashable full ROM package, it means that you are running a stock ROM that's newer than the version you're trying to flash. If you're trying to downgrade, then you must install ClockworkMod recovery, then wipe system, boot, data, cache, and Dalvik cache. You will then be able to flash the older version. Optionally, you can also flash fastboot images of a version older than the version you're trying to flash.
If you get an error flashing an incremental update, it means one of four things. Either you don't have an I9023, you aren't running a stock ROM, you have changed something with your stock ROM (this includes build.prop changes, radio or bootloader changes as well), or you're running Android 4.X and trying to update manually. These incremental updates only work if you are running a completely, perfectly stock ROM exactly the way Google provides it, with the right radio and the right bootloader. There are no exceptions to this rule. Furthermore, Android 4.X ROMs can no longer be updated manually in stock recovery. See below.
A NOTE ABOUT ANDROID 4.X OTAs
Beginning with Ice Cream Sandwich, Google has made a change to stock recovery that prevents you from flashing future OTA updates manually. Instead you are now required to wait for the OTA notification on your phone and then tap "Reboot and Install."
If this pisses you off, you have the option of unlocking your bootloader, installing either a stock Gingerbread recovery or ClockworkMod recovery, and then flashing the OTA updates manually.
LATEST VERSION
The latest Android version available for I9023 is Ice Cream Sandwich version 4.0.4, build IMM76D.
BUILD REFERENCE
GRI40 - Android 2.3.3
GRI54 - Android 2.3.3
GRJ22 - Android 2.3.4
GRK39F - Android 2.3.6
IML74K - Android 4.0.3
IMM76D - Android 4.0.4
FULL ROMS
FASTBOOT IMAGES
If you're comfortable with fastboot, you can flash these images to return your phone back to raw stock.
Generally the best way to do this is to perform the following steps:
Put all six fastboot images in one folder, unlock your bootloader, perform the fastboot flashes, then lock the bootloader:
fastboot oem unlock
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
FLASHING FASTBOOT IMAGES WILL ERASE ALL OF YOUR PHONE'S DATA AND WILL RETURN YOU TO A FACTORY STOCK, UNROOTED STATE.
Android 2.3.3/GRI40/XXKB1 Radio/KA3 Bootloader
Official factory fastboot images, must be flashed using fastboot on an unlocked bootloader. Contains recovery, radio, and bootloader.
THESE IMAGES MUST BE FLASHED USING BOOTLOADER VERSIONS I9023XXKA3 OR I9023XXKL1
Android 2.3.3/GRI54/XXKB3 Radio/KA3 Bootloader
Official factory fastboot images, must be flashed using fastboot on an unlocked bootloader. Contains recovery, radio, and bootloader.
THESE IMAGES MUST BE FLASHED USING BOOTLOADER VERSIONS I9023XXKA3 OR I9023XXKL1
Android 2.3.4/GRJ22/XXKD1 Radio/KA3 Bootloader
Official factory fastboot images, must be flashed using fastboot on an unlocked bootloader. Contains recovery, radio, and bootloader.
THESE IMAGES MUST BE FLASHED USING BOOTLOADER VERSIONS I9023XXKA3 OR I9023XXKL1
Android 4.0.4/IMM76D/XXKI1 Radio/KL1 Bootloader
Official factory fastboot images, must be flashed using fastboot on an unlocked bootloader. Contains recovery, radio, and bootloader.
THESE IMAGES MUST BE FLASHED USING BOOTLOADER VERSIONS I9023XXKA3, OR I9023XXKL1
RECOVERY-FLASHABLE ROMS
Android 2.3.3/GRI40/XXKB1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Android 2.3.3/GRI54/XXKB3 Radio/KA3 Bootloader
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.
Android 2.3.4/GRJ22/XXKD1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Android 4.0.3/IML74K/XXKI1 Radio/KL1 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Android 4.0.4/IMM76D/XXKI1 Radio/KL1 Bootloader
Unofficial, unsigned, must flash through ClockworkMod recovery. Contains recovery, radio and bootloader.
Courtesy of XDA forum member kibmcz.
INCREMENTAL UPDATES
The links provided here are to Google's official update package for each version. Sometimes Google provides a small incremental update package for upgrading between versions, other times they just provide full ROM packages for bigger version upgrades. For instance, Google pushed a small incremental update to upgrade from 2.3.4 to 2.3.6. If your phone was running 2.3.1, there is no 2.3.1 to 2.3.6 incremental update, so Google would push the 2.3.6 full ROM package.
If you don't see an upgrade path from your version to your desired version, it means you need to use a full ROM package above instead.
Android 2.3.3 (Build GRI40/XXKB1 Radio/KA3 Bootloader)
2.3.3 (GRI40) -> 2.3.4
Android 2.3.3 (Build GRI54/XXKB3 Radio/KA3 Bootloader)
Neither of these following OTA updates actually work. Both of them require an unknown radio, and will fail if you try to flash them on a phone running 2.3.3/GRI54 with the XXKB3 baseband. The 2.3.3->2.3.4 update has since been pulled by Google and the link is only provided here for posterity and reference. The only way to properly update 2.3.3/GRI54 is to flash a full ROM over it.
2.3.3 (GRI54) -> 2.3.4 (Update requires an unknown radio and will NOT update build GRI54 with XXKB3 radio.)
2.3.3 (GRI54) -> 4.0.4 (Update requires an unknown radio and will NOT update build GRI54 with XXKB3 radio.)
Android 2.3.4 (Build GRJ22/XXKD1 Radio/KA3 Bootloader)
2.3.4 -> 2.3.6
2.3.4 -> 4.0.4
Android 2.3.6 (Build GRK39F/XXKF1 Radio/KA3 Bootloader)
2.3.6 -> 4.0.3
2.3.6 -> 4.0.4
Android 4.0.3 (Build IML74K/XXKI1 Radio/KL1 Bootloader)
4.0.3 -> 4.0.4
Reserved & subscribed
Sent from my Nexus S using xda premium
There is no dangers with this? And would the battery be that bad with incremental update to 4.0.3?
Send with my Nexus S.
Marc. said:
There is no dangers with this? And would the battery be that bad with incremental update to 4.0.3?
Send with my Nexus S.
Click to expand...
Click to collapse
Please read the first post. These are the updates directly from Google. No matter if you use the full or incremental update, you will end up with the same ROM in the end.
Sent from my Nexus S using Tapatalk
Android 2.3.3/GRI54/XXKB3 Radio/KA3 Bootloader
Hello i need help, i need to unroot the device and i have i9023 GRI54
Android 2.3.3/GRI54/XXKB3 Radio/KA3 Bootloader
which is currently not available if any one can provide me the stock zip to flash through cwm so ill be able to go back to factory device (unrooted)
Thanks & Regards,
Why do you need GRI54? Is there some reason you need to run 2.3.3 instead of 2.3.6 or 4.0.3?
oldblue910 said:
Why do you need GRI54? Is there some reason you need to run 2.3.3 instead of 2.3.6 or 4.0.3?
Click to expand...
Click to collapse
This device came with Android 2.3.3/GRI54/XXKB3 Radio/KA3 Bootloader. To get the warranty back i need to unroot the device with stock recovery and after that ill lock the bootloader. If any other updated verion of stock rom can get warranty back then it will also help, kindly tell which one should i flash.
Thanks
MrXelerate said:
This device came with Android 2.3.3/GRI54/XXKB3 Radio/KA3 Bootloader. To get the warranty back i need to unroot the device with stock recovery and after that ill lock the bootloader. If any other updated verion of stock rom can get warranty back then it will also help, kindly tell which one should i flash.
Thanks
Click to expand...
Click to collapse
These are all official over-the-air updates from Google. Flashing any of these will not void your warranty, and they'll all unroot the device since they're stock.
The Android 4.0.3/IML74K is exactly the same file as for the i9020t right?
Azure465 said:
The Android 4.0.3/IML74K is exactly the same file as for the i9020t right?
Click to expand...
Click to collapse
That's correct.
oldblue910 said:
These are all official over-the-air updates from Google. Flashing any of these will not void your warranty, and they'll all unroot the device since they're stock.
Click to expand...
Click to collapse
Like if i flash this Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader
So it will also get me back to stock device + ill get the warranty back? and they will never know about the device that it was ever rooted?..
Actually im new to android and im loving it, im a little confused about Radio thing.. like i currenty have XXKB3 and the firmware that is listed above ^ is having XXKF1, will this create any conflict? i mean if i have waited for OTA update from google, so i would have got the same update 2.3.6 with XXKF1 Radio? and it would also have the same build number GRK39F instead of GRI54?
Thanks
Hi if i install this for my Nexus si9023 did i update via OTA?
my is rooted
i want to install this file ZD3PyN0t.zip
MrXelerate said:
Like if i flash this Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader
So it will also get me back to stock device + ill get the warranty back? and they will never know about the device that it was ever rooted?..
Actually im new to android and im loving it, im a little confused about Radio thing.. like i currenty have XXKB3 and the firmware that is listed above ^ is having XXKF1, will this create any conflict? i mean if i have waited for OTA update from google, so i would have got the same update 2.3.6 with XXKF1 Radio? and it would also have the same build number GRK39F instead of GRI54?
Thanks
Click to expand...
Click to collapse
To be clear, you are not getting the warranty "back". You are tricking customer support into thinking you never voided your warranty by flashing a custom ROM. I hope you understand the difference.
Anyways, flashing any of the files in this thread will bring you back to stock. That means stock radio, bootloader and build. However, it will be still necessary to lock the bootloader (fastboot oem lock), otherwise it's pretty easy to see that you've tinkered with the device.
As for your second question, the builds above are the official builds from Google. If you have the i9023 (easily recognizable by the SLCD screen) these are the builds that you would get with OTA. Don't look at all the build/radio/bootloader names, they usually change with each new version.
naimhack said:
Hi if i install this for my Nexus si9023 did i update via OTA?
my is rooted
Click to expand...
Click to collapse
I think I understand you are asking if you will still receive OTA updates after flashing any of the above files. If so, the answer is yes.
You will loose root by flashing any of the above, though.
Ok, 1 question. What if i flash 4.0.3, can i flash back to 2.3.6? Because i read somewhere that this could be tricky to do, you can mess up your phone. Is that true?
Sent from my GT-I5800
alen1901 said:
Ok, 1 question. What if i flash 4.0.3, can i flash back to 2.3.6? Because i read somewhere that this could be tricky to do, you can mess up your phone. Is that true?
Sent from my GT-I5800
Click to expand...
Click to collapse
Yes you can flash back. You would have to unlock your bootloader (which will wipe all your data), and then install ClockworkMod recovery.
Go into CWM recovery, wipe data, cache (you MUST wipe data and cache if you're downgrading), wipe Dalvik, system and boot as well. Once you've done that, you can flash the full 2.3.6 ROM package from the original post.
hi...i using 2.3.3 , baseband i9023XXKB3, build GRI54 , plan to upgrade to ICS..
what should i do if i wish to provide this ROM to u as u menton, Still need ROMs for:
Android 2.3.3/GRI54/XXKB3 Radio/KA3 Bootloader
s199531 said:
hi...i using 2.3.3 , baseband i9023XXKB3, build GRI54 , plan to upgrade to ICS..
what should i do if i wish to provide this ROM to u as u menton, Still need ROMs for:
Android 2.3.3/GRI54/XXKB3 Radio/KA3 Bootloader
Click to expand...
Click to collapse
Thanks for offering to help!! I'll PM you instructions later on.
original GRI54 ROM
First of all, thanks for this useful thread!
I'd also like to know how to grab the original stock ROM from my Nexus S (I9023, Android 2.3.3, GRI54) just in case I wanted to revert my phone back to its original state. I know 2.3.6 is better than 2.3.3 but maybe I will need it for any reason in the future. My problem is, that if I unlock the bootloader (in order to install Clockwork recovery), I will loose my current configuration (apps, settings, etc.) since the /data partition will be wiped. And the original stock recovery will also be gone once I install Clockwork.
So my question is: can I boot into Clockwork recovery without flashing it to the recovery partition in order to access its backup feature, so that I can make a full backup of my original (current) system? Of course, the bootloader is still locked, so the real question is whether I can use a command like this with a locked bootloader:
fastboot boot recovery.img
I think it should work because this won't modify the system since I only boot the custom recovery.
Thanks in advance.
oldblue910 said:
Thanks for offering to help!! I'll PM you instructions later on.
Click to expand...
Click to collapse
waiting ur pm..
is it i have to post 10time b4 i can use pm function??
After almost a full day of flashing I now have a 100% successful method of flashing any stock JB Firmware
With this method I have been able to successfully flash any stock JB Firmware from 10.4.2.9 all the way through to 10.6.1.27.5 without issue.
unfortunately you can not go back to ICS bootloader or firmware (there is a signature mismatch issue here).
Try this at your own risk, I will not be responsible for a bricked device.
Recommend doing NVFlash first so your tablet is Unbrickable
NVFlash for ICS bootloader
NVFlash for JB bootloader
Warning:
If you flash an incorrect recovery to a 4.2 bootloader there is about a 90% chance that fastboot flash commands will now just freeze the tablet - When you attempt to flash via fastboot everything will seem to go ok on the command prompt but you will not see the blue progress bar on the tablet when flashing & the reboot command will not reboot the tablet after the flash command & nothing will have flashed to the tablet.
If this is the case try this solution.
Please read below for how to check your bootloader version and confirm your flashing the correct recovery.
Requirements:
Must be unlocked (Method 1 seems to work fine for locked devices but must be unlocked for Method 2 to flash custom recovery).
Must have working fastboot
Working adb in recovery (optional). I use adb in this method for rebooting but this can be done manually with vol- & power.
Always make a backup first.
Files Needed:
Download the stock JB firmware you wish to flash from either the Asus website or from the Index thread here, be sure to download the correct SKU version you wish to use On your tablet you can check what SKU your using by going to settings>about tablet, scroll down to build number and you can see SKU version..
If using method 2 download the TWRP recovery you require, Here is a link to the TWRP thread. When you download a version of TWRP it will have a name like "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - You can rename to something shorter for flashing if you like, I rename like so "twrp-2.5.0.0-4.2.blob".
What recovery to flash for bootloader version: example for TF300T model:
Check & confirm what bootloader your on - boot to bootloader menu (vol- & power) and look at the text in top left, your bootloader version number is there.
JB 4.1 firmwares
If current bootloader = 10.4.2.9 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.13 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.17 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.18 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
If current bootloader = 10.4.2.20 - JB 4.1 - recovery to flash = TWRP "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" or CWM
JB 4.2 Firmwares
If current bootloader = 10.6.1.8 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.4.4.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device. Also flashing 2.5.0.0-tf300t-4.2 on the 10.6.1.8 bootloader results in a split-screen issue.
If current bootloader = 10.6.1.15.3 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device.
If current bootloader = 10.6.1.27.1 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device.
If current bootloader = 10.6.1.27.5 - JB 4.2 - recovery to flash = ONLY TWRP "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" - flashing a non-4.2 version of TWRP or any version of CWM will brick device.
My Notes about TWRP 2.4.4.0-4.2:
TWRP 2.4.4.0-4.2 will not mount my sandisk 64gb micro SDXC UHS-1 class 10 card, but previous versions of TWRP have no issue. I believe this is a UHS-1 issue. TWRP 2.5.0.0-4.2 has fixed this bug and and can now mount 64gb micro SDXC UHS-1 class 10 card again.
Method 1
Unzip the firmware zip you downloaded, there will be another zip file inside.
Example:
Lets say you choose WW 10.4.2.20 firmware. (same method apply's for any firmware version and SKU you choose - US, WW, JP, TW, CN)
[*]Unzip "WW_epaduser_10_4_2_20_UpdateLauncher.zip"and you will find another zip inside "WW_epad-user-10.4.2.20.zip".
[*]Now unzip the WW_epad-user-10.4.2.20.zip and you will find a "blob" file.
[*]Now copy the blob file to your android-sdk\platform-tools folder.
Now to the flashing:
With your device loaded in android go to settings, developer options and make sure they are on & usb debugging is on.
[*]Plug device into PC with usb cable & boot to fastboot.
Using adb commands
Open command prompt (run as admin) & cd to you android-sdk\platform-tools folder.
Check your PC can see your device
Code:
adb devices
You should get a list with you device s/n, if not then adb is not setup.
Next
Code:
adb reboot-bootloader
or
Manually boot to fastboot
Hold vol- & power button to boot to bootloader then connect to PC.
Fastboot will start automatically when connected to PC on the 4.2 bootloaders. On 4.1 bootloaders you will need to select the usb icon using vol- to highlight the usb icon and vol+ to select.
Note:
In bootloader NEVER select the Wipe Data icon or you will brick.
Once in fastboot open command prompt & cd to you android-sdk\platform-tools folder and type command
Code:
fastboot devices
and again here you should get a list with you device s/n, if not then fastboot is not setup.
[*]If OK we can now flash the system blob we put in the platform-tools folder
Code:
fastboot -i 0x0b05 flash staging blob
This will take about 10 minutes to send & write system, you will see a progress bar on device when system is writing.
[*]When complete
Code:
fastboot reboot
This method should work fine but have found that sometimes the device will get stuck at the boot animation, if this happens method 2 works fine every time.
Method 2
Unzip the firmware zip you downloaded, there will be another zip file inside.
Example:
Lets say you choose WW 10.4.2.20 firmware. (same method applys for any firmware version and SKU you choose - US, WW, JP, TW, CN)
[*]Unzip "WW_epaduser_10_4_2_20_UpdateLauncher.zip"and you will find another zip inside "WW_epad-user-10.4.2.20.zip".
[*]Place a copy of the WW_epad-user-10.4.2.20.zip on your microSD card.
[*]Now on PC unzip the WW_epad-user-10.4.2.20.zip and you will find a "blob" file.
[*]Now copy the blob file to your android-sdk\platform-tools folder.
[*]Now copy the "twrp-version.blob" file you downloaded to your android-sdk\platform-tools folder.
--Make sure you have the correct twrp version for the firmware your flashing.
Now to the flashing:
With your device loaded in android go to settings, developer options and make sure they are on & usb debugging is on.
[*]Plug device into PC with usb cable & boot to fastboot.
Using adb commands
Open command prompt (run as admin) & cd to you android-sdk\platform-tools folder.
Check your PC can see your device
Code:
adb devices
You should get a list with you device s/n, if not then adb is not setup.
Next
Code:
adb reboot-bootloader
Manually boot to fastboot
Hold vol- & power button to boot to bootloader then connect to PC
Fastboot will start automatically when connected to PC on the 4.2 bootloaders. On 4.1 bootloaders you will need to select the usb icon using vol- to highlight usb icon and vol+ to select.
Note:
In bootloader NEVER select the Wipe Data icon or you will brick.
Once in fastboot open command prompt & cd to you android-sdk\platform-tools folder and type command.
Code:
fastboot devices
and again here you should get a list with you device s/n, if not then fastboot is not setup.
[*]If OK we can now flash the system blob we put in the platform-tools folder.
Code:
fastboot -i 0x0b05 flash staging blob
This will take about 10 minutes to send & write system, you will see a progress bar on device when system is writing.
[*]Once this has completed type in the command prompt.
Code:
fastboot reboot-bootloader
You can now check that your bootloader has upgraded/downgraded, look at the text in the top left of the bootloader screen and make sure it's changed to the firmware version you just flashed.
[*]Now again depending on the bootloader version go to fastboot.
Next
[*]In the below command I am using "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" for JB firmware 10.4.2.20, and shortened the name "twrp-JB.blob" so just change command according to TWRP version needed.
Code:
fastboot -i 0x0b05 flash recovery twrp-JB.blob
[*]Once this has completed type in the command prompt.
Code:
fastboot reboot-bootloader
[*]Now this time in bootloader select the "RCK" icon to enter twrp recovery.
[*]In twrp recovery select "Wipe".
[*]Here I do a complete wipe (cache, Dalvik cache, Factory Reset, System, Internal Storage & Format Data) I don't believe Internal Storage & Data Format are necessary but I like a full clean flash.
[*]Once you have done full wipe type in command prompt.
Code:
adb reboot-bootloader
or manually reboot to bootloader, hold vol- and power button.
[*]Now again in bootloader select the "RCK" icon to enter twrp recovery.
[*]In twrp recovery disconnect your device usb cable from PC.
[*]Select "Install" & select the firmware zip you copied to your external sd card and slide to flash/install.
[*]Once completed reboot, you will get message at top of recovery saying there is no OS installed are you sure you want to reboot - slide to confirm yes, another message will popup asking if you want root permissions installed - I select NO "Do not install" you can probably select yes here if you want twrp to root.
The device will reboot, you'll see a progress bar as the signature is being matched, it will reboot again when done.
Now device will boot with the stock JB bootloader & firmware you have chosen.
Done.
You can now flash twrp, then flash any custom rom for that firmware.
As I have said I have done this with all stock WW JB firmware available and can confirm that the bootloader does change and system will boot and run without any issues. But try at own risk.
Firmware I have done this with: Only tried with WW SKU
10.6.1.27.5
10.6.1.27.1
10.6.1.15.3
10.6.1.8
10.4.2.20
10.4.2.18
10.4.2.17
10.4.2.13
10.4.2.9
More Info:
Downgrading from CROMi-X back to CROMi-3.4.6
Upgrading from ICS to JB
If you this information is helpful please hit the thanks button.
Nice work and thanks for sharing it PJC21. Looks like you've got quite a bit of time invested in this info. :thumbup:
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
Thank you for the detailed information. Couldn't one just flash the stock .zip file from TWRP, reboot, reinstall TWRP recovery from fastboot and then wipe in TWRP as you would do when upgrading? I have done that between JB releases before, but I guess the bootloader didn't change.
jimpmc said:
Thank you for the detailed information. Couldn't one just flash the stock .zip file from TWRP, reboot, reinstall TWRP recovery from fastboot and then wipe in TWRP as you would do when upgrading? I have done that between JB releases before, but I guess the bootloader didn't change.
Click to expand...
Click to collapse
Yeah quite possibly, I didn't even think to try it that way :laugh:
However if just flashing the system blob via fastboot then rebooting, my devices will get to the boot animation screen and just sit there.
I do prefer being on the correct bootloader before flashing the firmware though and this way allows for that.
Maybe consider making this two parts.
1. with twrp recovery installed
2. with stock recovery installed
Good info and needed!
Note: I should have added with twrp, fastboot, or adb to flash I always loose root and data. With stock if I am using the same version or anything numerically higher I keep root and data but going to a lower numeric I loose root and data.
I hope this is understandable.
I can confirm that this method 101 % works. :good:
I have migrated from custom ROM 4.2.1 to factory 4.2.1.
After final reboot I lost root, but rooting afterwards gave me rooted factory 4.2.1. No problems at all.
Thanks for this.
Q-Logic said:
I can confirm that this method 101 % works. :good:
I have migrated from custom ROM 4.2.1 to factory 4.2.1.
After final reboot I lost root, but rooting afterwards gave me rooted factory 4.2.1. No problems at all.
Thanks for this.
Click to expand...
Click to collapse
+1 works
Sent from my GT-I9100 using xda app-developers app
OK, I have a question. I see this works with full ROMs from Asus, good. What about TWRP backups?
So, before I upgraded to 4.2.1, I took a TWRP backup of 4.1.1 latest v20 build. If I restored that backup via TWRP, would it work? Would the bootloader revert to the older one (with the USB icon)? My backup did include the boot partition, but I didn't know if this would brick the device.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Just to make sure ...
Have you actually downgraded from 4.2.1 to 4.1.1?
I'm on 4.2.1 (10.6.1.8; Energy Rom) at the moment and eager to browse all those nice custom roms that are based on 10.4.x.x. like cm 10.1 & co.
Since the 4.2 upgrade rearranged the file system i'm afraid of messing it up when reverting to pre-multiuser-versions ...
Also i'd love to have this nvflash brickproof thingie ...
You think I could give this a go?
MrsColumbo said:
Have you actually downgraded from 4.2.1 to 4.1.1?
I'm on 4.2.1 (10.6.1.8; Energy Rom) at the moment and eager to browse all those nice custom roms that are based on 10.4.x.x. like cm 10.1 & co.
Since the 4.2 upgrade rearranged the file system i'm afraid of messing it up when reverting to pre-multiuser-versions ...
Also i'd love to have this nvflash brickproof thingie ...
You think I could give this a go?
Click to expand...
Click to collapse
To be honest - I'm not sure, I didn't downgrade, let pjc21 say did he. I would be afraid to do mess with file system just like you.
But I would be interested to try this if his downgrading method works.
funnel71 said:
OK, I have a question. I see this works with full ROMs from Asus, good. What about TWRP backups?
So, before I upgraded to 4.2.1, I took a TWRP backup of 4.1.1 latest v20 build. If I restored that backup via TWRP, would it work? Would the bootloader revert to the older one (with the USB icon)? My backup did include the boot partition, but I didn't know if this would brick the device.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
I'm not sure here, but would think no as the new update has a different file system arrangement. I myself would not try this as I really have no idea what would happen.
MrsColumbo said:
Have you actually downgraded from 4.2.1 to 4.1.1?
I'm on 4.2.1 (10.6.1.8; Energy Rom) at the moment and eager to browse all those nice custom roms that are based on 10.4.x.x. like cm 10.1 & co.
Since the 4.2 upgrade rearranged the file system i'm afraid of messing it up when reverting to pre-multiuser-versions ...
Also i'd love to have this nvflash brickproof thingie ...
You think I could give this a go?
Click to expand...
Click to collapse
Yes I have downgraded from 4.2.1 (10.6.1.8) to 4.1.1 (10.4.2.20) and I have also downgraded through all the JB firmware back to the first JB firmware that came out 10.2.4.9 -28/08/2012- not that many people would want to go back that far but I was attempting to go all the way back to an ICS bootloader & firmware so I could access NVflash and become brickproof as my tab came with JB pre-loaded. When attempting to go from a JB bootloader & firmware to an ICS one there is a signature mismatch which I have not looked into as yet and am not sure it would even be possible to modify this to get a match. I will have a look when I get the time and look at the differences between the JB & ICS signatures to see if it might be possible to modify these.
Works fine
pjc21 said:
Yes I have downgraded from 4.2.1 (10.6.1.8) to 4.1.1 (10.4.2.20) and I have also downgraded through all the JB firmware back to the first JB firmware that came out 10.2.4.9 -28/08/2012- not that many people would want to go back that far but I was attempting to go all the way back to an ICS bootloader & firmware so I could access NVflash and become brickproof as my tab came with JB pre-loaded. When attempting to go from a JB bootloader & firmware to an ICS one there is a signature mismatch which I have not looked into as yet and am not sure it would even be possible to modify this to get a match. I will have a look when I get the time and look at the differences between the JB & ICS signatures to see if it might be possible to modify these.
Click to expand...
Click to collapse
Witch much satisfaction I can confirm this working. Had to sideload the update zip, though, 'cause I forgot to copy it to my external micro sd card. in the course I ****ed up the update (progress indicator not progressing, so i did a vol-+power-reset, subsequently rom did not load), but adb-d recovery again, inserted micro sd and did the update (downdate) to 10.4.2.20. running cm 10.1 nightly now.
Yeah, this brickproof mod sounds really good. I wouldn't want to miss up on jb's smoothness, though. IMHO JB and ICS are worlds apart. Maybe those guys give it a go with a 4.2-brickproof-mod one fine day
Thanks pjc21 for this outstandig work. This is what Android OS is about: being able to explore all possibilities of a fine piece of hardware you actually own instead of being led on a leash by a corporation. :good::good::good:
This worked pretty easy, returning from 4.2.1 ( 10.6.1.8) I flashed the 4.1.1 (10.4.2.20) blob through fast boot,then flashed twrp 2.3.3.0 in fast boot, rebooted into recovery restored my 4.1.1 backup and all is well.
pjc21 said:
Yes I have downgraded from 4.2.1 (10.6.1.8) to 4.1.1 (10.4.2.20) and I have also downgraded through all the JB firmware back to the first JB firmware that came out 10.2.4.9 -28/08/2012- not that many people would want to go back that far but I was attempting to go all the way back to an ICS bootloader & firmware so I could access NVflash and become brickproof as my tab came with JB pre-loaded. When attempting to go from a JB bootloader & firmware to an ICS one there is a signature mismatch which I have not looked into as yet and am not sure it would even be possible to modify this to get a match. I will have a look when I get the time and look at the differences between the JB & ICS signatures to see if it might be possible to modify these.
Click to expand...
Click to collapse
Please update us on your progress. Everything I've read says that going back to ICS for NVFlash cannot be done if the tablet came with JB. Thanks.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
wetbiker7 said:
Please update us on your progress. Everything I've read says that going back to ICS for NVFlash cannot be done if the tablet came with JB. Thanks.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
He stated you cannot go back to ICS in the first post,, but you can switch JB firmware pretty easy.
treo4life said:
He stated you cannot go back to ICS in the first post,, but you can switch JB firmware pretty easy.
Click to expand...
Click to collapse
Exactly. But........ he also said he was going to try and modify the signatures to see if he can get them to match. If he can succeed, it will be a huge breakthrough.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
That's true, don't know if he is going to try to tackle that one though.. would be nice to have the option...
Sent from my EVO using xda premium
treo4life said:
That's true, don't know if he is going to try to tackle that one though.. would be nice to have the option...
Sent from my EVO using xda premium
Click to expand...
Click to collapse
No doubt. Hopefully he'll continue working on it.
Sent from my LG-LG855 using Xparent SkyBlue Tapatalk 2
I just received my new tablet ... Need to downgrade to 4.1.1 to be able to run AOSP Rom.
Thanks for the procedure. I will give it a try.
Welcome to the “All Things” Razr I Index thread. This Index thread contains basic information about the Motorola Razr I a.k.a. XT890 to get you started. It won’t contain any KERNEL and ROM Development, because of the numerous kernels and roms people can make. It would just flood this thread if it happens.
All the work that is presented in this thread belong to their rightful owners. I just sorted them and linked the threads in here.
Everything that u do to your phone it totally your own responsibility. Nobody here or elsewhere can be held account for a failure in flashing, device bricked or a rom problem if u tempered with your own device. But maybe we can help if u ask nicely.
This Index thread contains the following in this order:
A. GENERAL DISCUSSIONs
B. GENERAL (DEV) TOOLs
C. UNLOCK BOOTLOADER and ROOT
D. RECOVERYs
E. FIRMWAREs
F. MODs
G. WARNINGs, BRICKED DEVICEs SOLUTIONs/DISCUSSIONs
H. DOWNGRADE TO ICS
I. FROM STOCK TO CUSTOM ROM
J. FROM CUSTOM ROM TO STOCK (with RELOCK BOOTLOADER)
Some important notes:
When using 3rd party software to alter your device u warranty may be voided. In every country this is different. Before going ahead, read your legal rights!!!
Each thread/sections can contain “important” notes
Do your research before doing anything
Read the information the owner of the thread gives u
Highly recommended to have a look at the ‘warnings, bricked devices solutions/discussions’ threads before using RSD-Lite and fastboot commands like flashing manual firmware versions.
Last note:
If u find something missing that should definitely be in this Index thread, please share.
If u find anything wrong and u know the answer, please share.
Can someone have a look at the downgrade section. That’s the only one I don’t know for sure.
A. GENERAL DISCUSSIONs
Are recommended discussions about new firmware and features
RAZR I Help Guide (2013)
Motorola 4.4 (2014)
FM Radio (2013)
RAZRi XT890 USB OTG Capabilities
B. GENERAL (DEV) TOOLs
Contains threads with information about tools that you may need for your device
Motorola USB drivers
Motorola Device manager (driver)(Windows)
Motorola Device manager (driver)(Mac)
Motorola usb drivers for all devices. It also installs the device manager that checks for updates for your device. You can delete the program and still use the drivers. If u want the drivers alone, search the internet. No valid official link yet.
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer
In different threads are different methods to acquire those tools. If u have them ones installed right, u don’t need them twice. It isn’t bad to have them multiple times though.
Motorola mFastboot (fastboot file sized > 100mb)
Put the mFastboot executable as 'mfastboot' in the directory where adb and the normal fastboot file are stored
RSD-Lite
Motorola Tools [Specially for Noobs] (November, 2012)
RSD-Lite in this thread is outdated(5.7), use the newest 6.1.x series from here
If one version doesn’t work, try another. 1 of the 3 should work for you!
ALWAYS USE YOUR CURRENT FIRMWARE OR HIGHER! DON’T DOWNGRADE WITH RSD-LITE. Downgrading with RSD-Lite will cause a soft-brick or if really screwed up a hard-brick. See ‘warnings, bricked devices solutions/discussions’ for more information.
[How to] Change Radio Firmware (February, 2013)
Flashing the radio can do more harm than good, but can also be rewarding, be careful
[DEVS only] Unpacking RAZR i boot images (November, 2012)
C. UNLOCK BOOTLOADER and ROOT
Threads about the bootloader and getting root access.
How To Update/Unbrick/Root Razr I To Jelly Bean (With Review) (Maart, 2013)
Makes use of video’s, a tad outdated.
Unlock the Bootloader on Your RAZR i (Oktober, 2012)
If this doesn’t work, your device isn’t supported (can happen). At this moment u can only achieve root access with the method: TwerkMyMoto, if your bootloader can’t be unlocked.
[Root] TwerkMyMoto 1.0 (no unlock root)(Jellybean) (november, 2013)
Doesn’t require unlocked bootloader
RAZR i Root 2 (Jellybean 4.1.2) (January, 2013)
RAZR i Root (ICS) (December, 2012)
D. RECOVERYs
The recovery’s can behave at every device differently. So a user can have no problems with CWM and almost can’t use TWRP. But it is the same the other way around. Try them and see which one u like and works for u.
To enter Fastboot mode to get to the Recovery
After booting up fastboot mode, navigate with volume - down to the recovery and select it with volume + up
[RECOVERY] Installer for CWM 6.0.1.9 / CWM 6.0.3.6 / TWRP 2.6.3 / STOCK (February, 2014)
To enter stock recovery, press volume up and down at the same time when the Android appears.
CWMR or TWRP install easy 19-Sep-13 (September, 2013)
E. FIRMWAREs
The Unofficial Thread of Official OTA Updates (April, 2013)
Motorola Razr i XT890 Firmware (up-to-date)
F. MODs
Recommended to make a backup before applying
[MOD] Collections of mods for Omar-Avelar Rom (April, 2013)
[MOD] Changing the brightness curve in stock JellyBean (September, 2013)
[Tool] Swap Internal SDcard With External SDcard no init.d need UPDATE (December, 2012)
Enabling USB Mass Storage on the Razr I (Needs root access) (November, 2012)
G. WARNINGs, BRICKED DEVICEs SOLUTIONs/DISCUSSIONs
Downgrade problems JB -> ICS | Black screen green led | service required code currupt
Downgrading from JB to ICS with a locked bootloader is bad. According to a lot of users it will give u a bricked device. This is because RSD-Lite can also flash the motoboot (bootloader), gpt.bin (partition table) and motobp (radio?) and those 3 may never be downgraded only upgraded. Can only be resolved at a service station.
With an unlocked bootloader it is possible, but then again, don’t flash the motoboot, gpt.bin and motobp!
WARNING - Avoiding Bricked Phones + RSD Lite Tutorial (April, 2013)
Recommend to read before attempting to downgrade
RSD-Lite tutorial, not a downgrade tutorial
Unbricking JB to ICS downgraded hardbricks (Maart, 2013)
This is a unbrick method when u have the following message: Service Required Code Corrupt or black screen - green light. But be careful. This fix can help most of the problems, but not all because of the firmware differences. If it doesn't work for you, have a look at the one below. The owner and thread is still worth mentioning because of the finding of a possible fix, the many devices the owner saved and the discussion about the problem that came along.
Unbricking "Service Required Code Corrupt" (May, 2013)
A better documented unbrick method as the one above, but the same. Still won’t help everybody. But won’t harm your device more than it can and already is if u need this. Only for downgrade problems, everything other needs RSD-Lite or Jellybean versions of the files.
Other issues/discussions
Locked Bootloader, can't access Recovery
If u have a locked bootloader and u can’t access the recovery anymore and even RSD-Lite (latest version) with stock firmware (JB) won't work, there is no possible way to resurrect it, yet. Most of the time it means that you have a bad sector in your EMMC (flash memory) and with a locked bootloader it can’t be erased/written to.
PDS Partition Fix (July, 2014)
In TWRP recovery u can erase PDS. Never do it! Will be fixed when 4.4 is out.
Issue Locked bootloader
If u have any issue with your phone (bootloop, stuck on bootlogo) and u have a locked bootloader, try the following:
Reboot to stock recovery
Do a "factory reset"
If that doesn't solve it, flash your original firmware (JB) with RSD-Lite! Make sure u use one of the latest versions of RSD-Lite, 6.1.x. 6.1.5 is the latest (Augustus, 2014)
Unlocked bootloader
If u have any issue with your phone (bootloop, stuck on bootlogo) and u have a unlocked bootloader, try the following (all staps are on there own. If one doesn't work, try another):
Reflash your custom ROM if u use one (don't wipe) (Renews your system partition, stays of your data)
Wipe your data/cache in recovery (does what it says)
Wipe partitions system/data/cache and flash new rom (reflash whole new system)
Do a nandroid restore if u have a nandroid backup of the rom (restore a previous nandroid)
Do a RSD-Lite flash, use latest versions of your stock firmware and RSD-Lite. (reflash to complete stock)
H. DOWNGRADE TO ICS
If u still want to downgrade from JB to ICS for whatever reason, those are the most save methods, because we disable the flashing of the ‘motoboot’, ‘gpt.bin’ and 'motobp'. There are 2 methods, 1 is by RSD-Lite with a modified xml file and the other one is flashing all the files manually. CANNOT BE DONE WITH LOCKED BOOTLOADER only unlocked!!!
RSD Lite:
Follow and read one of the tutorials for RSD-Lite and download your ICS Stock version of your device!
Set everything up and before flashing remove the following lines from the included XML file of the firmware u want to flash:
Code:
“<step operation= “flash” partition= “gpt” filename= “gpt_signed” MD5= “*****”>”
“<step operation= “flash” partition= “motoboot” filename= “motoboot” MD5= “*****”>”
“<step operation= “flash” partition= “motobp” filename= “motobp” MD5= “*****”>”
U maybe need to delete the following line also:
Code:
“<step operation= “getvar” var=”max-download-size”
U should be good to go!
Manually:
For manually flashing we need “mFastboot”. See GERNERAL (DEV) Tools for more information.
Download your firmware and extract it.
Now use the following commands in a command prompt. Make sure they are correctly spelled and return an “OKEY”!
Code:
[LIST]
[*]mfastboot flash boot boot_signed
[*]mfastboot flash recovery recovery_signed
[*]mfastboot flash system system_signed
[*]mfastboot erase cache
[*]mfastboot erase userdata
[/LIST]
I. FROM STOCK TO CUSTOM ROM
See threads that are mentioned above for more details.
Backup your important data from your phone to PC or elsewhere
Get ADB, Fastboot and your device drivers working
Unlock your bootloader with the above method
Install one of the recovery’s
Install a Rom and/or kernel from one of the threads in the Development section of the Razr I Board through custom recovery.
J. FROM CUSTOM ROM TO STOCK
See threads that are mentioned above for more details. If u want to relock too, have a look here (only for jellybean)
Backup your important data from your phone to PC or elsewhere
Get RSD-Lite working
Download the latest official android firmware for your device. (Always jellybean, unless u had ICS installed before the custom rom and to be on the safe side, never used a Jellybean version, then u can try ICS too)
Flash through RSD-Lite
Enormous post hazou! THank's a lot for all your work!
(work on rom, work on thread... etc)
Excellent job!
Thanks for this guide !
A question :
I'm whith KTR rom 2.2 ( JB 4.1.2 ) and, as all users, i have the unlocked phone screen when i boot my razr I.
If i do the step H. of the guide in order to downgrade to ICS, can i change the unlocked screen whith another one, and after reflash KTR rom ( JB ) in order to don't have anymore this unlocked screen at boot ???
elreydelaplaya said:
Thanks for this guide !
A question :
I'm whith KTR rom 2.2 ( JB 4.1.2 ) and, as all users, i have the unlocked phone screen when i boot my razr I.
If i do the step H. of the guide in order to downgrade to ICS, can i change the unlocked screen whith another one, and after reflash KTR rom ( JB ) in order to don't have anymore this unlocked screen at boot ???
Click to expand...
Click to collapse
To flash a working logo image u need the bootloader (motoboot) from ICS. But if u flash the motoboot from ICS coming from a jellybean rom (is using the motoboot from jellybean) u will brick your device. (unless as stated, u have never bean on stock JB or installed the firmware from stock JB and u flashed from stock ICS to KTR-rom. So u have the stock ICS bootloader. But i think nobody in this world has that anymore.)
The bootloader and its necessary files may never be downgraded!! I will make a point in the guide to address your question.
So, to answer your question. No u can't!
OK , thanks hazou !
There is definitively no solutions to remove this shi...of bootscreen ....
hey, I wanted to flash the stock rom with the rsd tool and I got my phone bricked, green light flashing, no code error message. Is there any solution for that problem?
edit: ok, I made a stupid mistake by accidentally downloading the ICS stock rom instead of the JB... f**k
bongofred said:
hey, I wanted to flash the stock rom with the rsd tool and I got my phone bricked, green light flashing, no code error message. Is there any solution for that problem?
edit: ok, I made a stupid mistake by accidentally downloading the ICS stock rom instead of the JB... f**k
Click to expand...
Click to collapse
Always read as much as you can and do lots of research to prevent a brick.
waj3k said:
Always read as much as you can and do lots of research to prevent a brick.
Click to expand...
Click to collapse
yep sure, I got it unbricked with the tut hazou linked in his post, so everything is fine
THX!
Nice thread. Thank you! This helps so much!
Motorola RAZR i xt 890 stuck at bootloader is unlocked
Please help!!!
My Motorola razr i xt 890 is stuck at AP Fastboot Flash Mode(secure boot)
and there are options like:
Normal Poweup
Recovery
Factory
BP tools
Switch Console [NULL: null]
Power Off
Now when I select any of the options from above it shows the screen saying "warning bootloader is unlocked" and after that it remains in the same condition.I can't access any of the options.
Please help me....
anuragtripathi said:
Please help!!!
My Motorola razr i xt 890 is stuck at AP Fastboot Flash Mode(secure boot)
and there are options like:
Normal Poweup
Recovery
Factory
BP tools
Switch Console [NULL: null]
Power Off
Now when I select any of the options from above it shows the screen saying "warning bootloader is unlocked" and after that it remains in the same condition.I can't access any of the options.
Please help me....
Click to expand...
Click to collapse
i have the same problem.
I managed to enter after many power + volume up press and it rebooted after many minutes, to the rom.
and it worked!
the only problem is that I can't make the antenna work. it's not working
I have a Nexus 4 with TWRP and root, I have 4.4.2 and want to get to 4.4.4. Unfortunately, I can't update to 4.4.3 OTA. It says the update downloads, I hit restart, and it fails in TWRP. When I reboot, it says I'm up to date for a couple hours and then says I have an update again.
I'm not sure if it's because I have a custom recovery or what but if I need to revert I'd need help with doing that since I did all this about a year ago and don't remember how I did it. I also vaguely remember deleting something in the cache to stop update available messages. I'm not sure if that's to blame, but I'm positive the updates are downloading at the very least. They're just failing to install.
I'm sure this has been answered a number of times but I'm having trouble navigating some of the topics.
Hey,
Download the stock nexus 4 factory image and flash only the system image through fastboot. This will revert your system partition to stock and it will allow the installation of the ota to continue without any loss of user data. You can wait for the next update prompt or you can just download the ota from the ota thread and flash it yourself through TWRP.
Devices:
LG Optimus 2X P990
LG Nexus 4
LG Optimus 2X:
ROM: Tonyp TheROM Build 26 New Bootloader
Kernel: Kowalski Kernel M1 New Bootloader 2.6.39.4 W/ RAM Hack
Bootloader:ICS Bootloader
Recovery: TWRP 2.6.0.0 For New BL
Baseband: 1035.21
Nexus 4:
ROM: Stock 4.4.4 W/ Root (Xposed, GPU Drivers, Dalvik/Bionic Patches)
Kernel: Franco r213
Bootloader: Stock Bootloader (Unlocked)
Recvoery: PhilZ Touch CWM-Based Recovery
Radio:Radio (1.03)
ninjames said:
I have a Nexus 4 with TWRP and root, I have 4.4.2 and want to get to 4.4.4. Unfortunately, I can't update to 4.4.3 OTA. It says the update downloads, I hit restart, and it fails in TWRP. When I reboot, it says I'm up to date for a couple hours and then says I have an update again.
I'm not sure if it's because I have a custom recovery or what but if I need to revert I'd need help with doing that since I did all this about a year ago and don't remember how I did it. I also vaguely remember deleting something in the cache to stop update available messages. I'm not sure if that's to blame, but I'm positive the updates are downloading at the very least. They're just failing to install.
I'm sure this has been answered a number of times but I'm having trouble navigating some of the topics.
Click to expand...
Click to collapse
The update process usually goes through even if you have TWRP.
You can try flashing the stock recovery through fastboot.
Which is the stock Nexus 4 factory image? You mean what it launched with, or do you mean the factor 4.4.2 image since that's what I'm on? Also I'm not sure how to flash through fastboot at this point. Will that remove my custom loader or just remove my root?
You can get the latest factory image from here https://developers.google.com/android/nexus/images
Flashing only the recovery will not remove root. It'll only replace the custom recovery (loader).
Sent from my Nexus 4
---------- Post added at 10:44 PM ---------- Previous post was at 10:34 PM ----------
You can follow this guide http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Flash only the recovery (refer section D, sl no.12 in the above guide)
Sent from my Nexus 4
I don't believe the reason for your OTA failure is a custom recovery, it is most likely a modification to the system partition. You should extract the system partition image from the factory image and flash that through fastboot, which will remove your root but you can get that back by flashing the SuperSU zip. Then after restoring back to a stock /system partition, take your OTA like normal.
Devices:
LG Optimus 2X P990
LG Nexus 4
LG Optimus 2X:
ROM: Tonyp TheROM Build 26 New Bootloader
Kernel: Kowalski Kernel M1 New Bootloader 2.6.39.4 W/ RAM Hack
Bootloader:ICS Bootloader
Recovery: TWRP 2.6.0.0 For New BL
Baseband: 1035.21
Nexus 4:
ROM: Stock 4.4.4 W/ Root (Xposed, GPU Drivers, Dalvik/Bionic Patches)
Kernel: Franco r213
Bootloader: Stock Bootloader (Unlocked)
Recvoery: PhilZ Touch CWM-Based Recovery
Radio:Radio (1.03)
I'm not sure how to do what you just described. How do I extract a system partition image and how do I flash things through fastboot? Also what version of the system image? The one I'm on? The one it launched with? So what I want to do is flash a factory image, yes? I can't just do that through TWRP? I thank you guys for your help thus far but as to the specifics of what I need to do, I'm not finding much by searching, it all implies specific levels of knowledge that I don't have.
I appreciate the help thus far and going forward.
ninjames said:
I'm not sure how to do what you just described. How do I extract a system partition image and how do I flash things through fastboot? Also what version of the system image? The one I'm on? The one it launched with? So what I want to do is flash a factory image, yes? I can't just do that through TWRP? I thank you guys for your help thus far but as to the specifics of what I need to do, I'm not finding much by searching, it all implies specific levels of knowledge that I don't have.
I appreciate the help thus far and going forward.
Click to expand...
Click to collapse
So, have you got your adb and fastbooot drivers set up?
Sent from my Nexus 4
I think so, yeah. Sorry for the delay in my posting but I'd really like to get this figured out in advance of 5.0 so I can, you know, use it.
So I mean, I'm willing to wipe everything, go back to stock, whatever I need to do to set myself up for getting all the OTAs all the way to 5.0. I just need a little bit of help with that ... I backed up all my stuff, so.
Why don't you just go ahead and flash android lollipop? Since you've already backed up all your data, you can start afresh.
1. Download the factory image from Google's developer site.
2. Extract the contents to the folder android/SDK/platform tools.
3. Connect your phone via USB, boot into bootloader and check if it is recognized by using a command prompt and using command fastboot devices, it should return a value.
4. Run the file flash-all.bat which you can find from the extract.
5. It'll take care of the rest and you'll be good to go.
But it'll wipe all data and bring it to an out of the box state.
Sent from my Nexus 4
Will that work? Don't I need to be on the latest build for that?
And by using "command fastboot devices" what exactly does that mean? What's the step-by-step once I get it all plugged in and all of that?
ninjames said:
Will that work? Don't I need to be on the latest build for that?
And by using "command fastboot devices" what exactly does that mean? What's the step-by-step once I get it all plugged in and all of that?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=ZK6hYVuKNlw - This one works perfect just replace the file he tells you with
https://dl.google.com/dl/android/aosp/occam-lrx21t-factory-51cee750.tgz < Factory 5.0
Hope this helps
Hit The Thanks if it did
I couldn't really figure out that video .. he was talking about installing APKs and stuff and I didn't know which file from the factory image I was supposed to use? So I extracted it into a directory with the fastboot stuff as per another guide, hit flash all and it said it all worked ... and it did! So ya'll got me started and I stumbled my way to the finish. THANKS SO MUCH!
https://yadi.sk/d/v93-GFXngmcbq
Hi ,
Can i restore stock US retail 4.4.4 and update this OTA.
thanks
eugineprakash said:
Hi ,
Can i restore stock US retail 4.4.4 and update this OTA.
thanks
Click to expand...
Click to collapse
Yes thats how it usually works!
Are there any issues with upgrade?
AgentChaos said:
Yes thats how it usually works!
Click to expand...
Click to collapse
Are there any issues with upgrade?bcos iam currently in cm12.1 my bootloader version 41.19
I am planing to restore 4.4.4 us retail without downgrade my bootloader after that i am going upgrade from OTA in above thread.
Are there any issues with upgrade?Please guide me if i wrong.
Thanks,
eugineprakash said:
Are there any issues with upgrade?bcos iam currently in cm12.1 my bootloader version 41.19
I am planing to restore 4.4.4 us retail without downgrade my bootloader after that i am going upgrade from OTA in above thread.
Are there any issues with upgrade?Please guide me if i wrong.
Thanks,
Click to expand...
Click to collapse
I have been unable to install the update. Was with custom recovery and root and tried to install it and failed. Did factory reset, install stock recovery, download again the OTA from phone an try to install it and did not work.
Used the guide to go back to the stock firmware (though I already had it)
Try to install it using stock recovery, threw and error. (books.apk blabla).
Don't know what problems could yo be facing but man, this has been tough.
EDIT:
Just figured it out! The problem was exactly that I was already using the stock ROM and deleted some system APKs.
After trying going back to the really stock one once again (first I did not flash system images) it is installing correctly!
Btw this is my mirror for those who prefer using MEGA servers.
https://mega.co.nz/#!qJIE0SAY!u5-ezdk4o9OWfEKWVAJtW1KKQrV82NhiG1-myqlwOJ4
working confirm Thanks
Joandvg6 said:
I have been unable to install the update. Was with custom recovery and root and tried to install it and failed. Did factory reset, install stock recovery, download again the OTA from phone an try to install it and did not work.
Used the guide to go back to the stock firmware (though I already had it)
Try to install it using stock recovery, threw and error. (books.apk blabla).
Don't know what problems could yo be facing but man, this has been tough.
EDIT:
Just figured it out! The problem was exactly that I was already using the stock ROM and deleted some system APKs.
After trying going back to the really stock one once again (first I did not flash system images) it is installing correctly!
Btw this is my mirror for those who prefer using MEGA servers.
http s:/ / mega . co . nz/ #!qJIE0SAY!u5-ezdk4o9OWfEKWVAJtW1KKQrV82NhiG1-myqlwOJ4
Click to expand...
Click to collapse
working confirm Thanks
Where can I get the stock 4.4 so I can upgrade? I need stock recovery too.
I have problems to update too. XT1032, Retail US. As a first information, I have KK 4.4.4
I managed to download the update from my mobile (zipfile Blur_Version.210.12.61.falcon_umts.Retail.en.US, I already transferred to my PC thanks to Root Explorer), but when I go to "install now" and reboot, trying to install from zip file, pops a message from my recovery (PhilzTouch) Error Status 7. My phone is rooted by SU v2.46
So, what are the exactly step-by-step guide. I will appreciate that. Greetings from Chile
tifossi88 said:
I have problems to update too. XT1032, Retail US. As a first information, I have KK 4.4.4
I managed to download the update from my mobile (zipfile Blur_Version.210.12.61.falcon_umts.Retail.en.US, I already transferred to my PC thanks to Root Explorer), but when I go to "install now" and reboot, trying to install from zip file, pops a message from my recovery (PhilzTouch) Error Status 7. My phone is rooted by SU v2.46
So, what are the exactly step-by-step guide. I will appreciate that. Greetings from Chile
Click to expand...
Click to collapse
Change your recovery por el Stock Recovery for Kitkat 4.4.4
newellj79 said:
Where can I get the stock 4.4 so I can upgrade? I need stock recovery too.
Click to expand...
Click to collapse
This is the 4.4.4 Retail US (Last Build released)
https://mega.co.nz/#!ZIxQGJSJ!dnHim2zF3vDIenrvw24NeTDAeneA8m5BEidoD6hz4_k
That's the one I flashed following the guide to flash stock firmware in this forum and then updated with the OTA I posted before (I suppose the one of the topic is the same)
Finally, it's out!
kykemejia said:
Change your recovery por el Stock Recovery for Kitkat 4.4.4
Click to expand...
Click to collapse
Followed your steps:
- Flashed my phone (XT1032) with Retail US 4.4.4 Stock (RETAIL_XT1032_4.4.4_KXB21.14-L1.61_cid9_CFC.xml) using CMD, fastboot, typing list of files, etc.
- Updated some Motorola apps. Noticed Super SU is already included and installed by default, no way to uninstall it.
- Downloaded to my computer the OTA file (Blur_Version.210.12.61.falcon_umts.Retail.en.US), then moved OTA file to SD Card
- Turn off mobile
. Reboot in stock recovery, with the robot and the exclamation sign.
- Try to apply update from SD card with the file previously loaded on it (Blur_Version.210.12.61.falcon_umts.Retail.en.US)
- At verifying update package, update stops popping a message. The message in yellow is:
Package expects build fingerprint of motorola/falcon_retuglb/falcon_umts:4.4.4/KXB21.14-L1.61/62:user/release-keys or motorola/falcon_retuglb/falcon_umts:5.0.2/LXB22.99-36/35: user/release-keys; this device has motorola/falcon_retuglb/falcon_umts:4.4.2/KXB
Installation aborted.
Click to expand...
Click to collapse
What should I do in that case? Feel free to answer me in spanish for PM.
Is this any different from the February Canada release?
tifossi88 said:
Followed your steps:
- Flashed my phone (XT1032) with Retail US 4.4.4 Stock (RETAIL_XT1032_4.4.4_KXB21.14-L1.61_cid9_CFC.xml) using CMD, fastboot, typing list of files, etc.
- Updated some Motorola apps. Noticed Super SU is already included and installed by default, no way to uninstall it.
- Downloaded to my computer the OTA file (Blur_Version.210.12.61.falcon_umts.Retail.en.US), then moved OTA file to SD Card
- Turn off mobile
. Reboot in stock recovery, with the robot and the exclamation sign.
- Try to apply update from SD card with the file previously loaded on it (Blur_Version.210.12.61.falcon_umts.Retail.en.US)
- At verifying update package, update stops popping a message. The message in yellow is:
What should I do in that case? Feel free to answer me in spanish for PM.
Click to expand...
Click to collapse
In the SU menu you can find a way to delete the root, but I don't think that is causing the error.
Can you please tell me the version of recovery your phone have? You may have installed a kit kat 4.4.2 recovery or one with a different build number and that's causing the error.
IKXB21.14-L1.61
In the recovery menu, you should see the .61. I got the same problem as you and was using .32.
Did full factory reset, and installed stock again (w/o updating anything at all), when I checked the recovery, it was .61 and it updated perfectly.
In case you are really sure you got the actual last kitkat update firmware, you can try to extract the recovery.img and flash it using moto tool,
(rename it to StockKitkatrecovery.img and replace the one it brings with this one)
Joandvg6 said:
In the SU menu you can find a way to delete the root, but I don't think that is causing the error.
Can you please tell me the version of recovery your phone have? You may have installed a kit kat 4.4.2 recovery or one with a different build number and that's causing the error.
IKXB21.14-L1.61
In the recovery menu, you should see the .61. I got the same problem as you and was using .32.
Did full factory reset, and installed stock again (w/o updating anything at all), when I checked the recovery, it was .61 and it updated perfectly.
In case you are really sure you got the actual last kitkat update firmware, you can try to extract the recovery.img and flash it using moto tool,
(rename it to StockKitkatrecovery.img and replace the one it brings with this one)
Click to expand...
Click to collapse
I solved my problem by myself, thanks anyway. The issue for me, was updating some apps once in 4.4.4. You should not to do it.
Explanation for dummies, as me, in order to get Lollipop 5.0.2:
1) Flash your phone (XT1032) with Retail US 4.4.4 Stock (RETAIL_XT1032_4.4.4_KXB21.14-L1.61_cid9_CFC.xml), as it follows:
A) Extract the Retail US 444. Stock zip file (475 MB)
B) Download this file too: (1,5 MB) https://www.dropbox.com/s/nlbrn71wfqyup4u/mfastboot-v2.zip?dl=0 , and unzip it inside the same folder as you extracted Retail US Stock zip file. All files together in the same path.
C) Put your phone on fastboot (turn off, and then press Vol-and Power 3 secs, and release both buttons). Connect your phone to USB port.
D) Inside the folder containing all all these files, press **** + right click and choose "open file command", and a CMD window will open.
E) Once in CMD window, execute one by one:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
F) After reboot, unplug phone from USB port.
G) Done, you have now Stock Retail US 4.4.4 installed on your phone, Turn it on and set all things in order to go to home screen.
2)Once in the main screen , don't update your apps, no matter if they are even from Google or Motorola, don't do it
3) Download to your PC the OTA file (372 MB) Blur_Version.210.12.61.falcon_umts.Retail.en.US
4) Connect again your phone to USB port , and move OTA file to your phone SD Card
5) Once done previous step, go to Stock Recovery Mode. It is:
A)Turn Off your phone
B) Press Power and Vol- for 3 secs, then release
C) Select with vol- recovery option, and confirm it with vol+ button
D) Android Robot with exclamation sign will show up on the screen
E) Press vol+ and vol- for 5 secs, then press power once and release all the 3 buttons at the same time
F) Recovery Stock will appear you now.
6) Apply update from SD card with the file previously loaded on it (Blur_Version.210.12.61.falcon_umts.Retail.en.US). Select OTA file on "apply update from zip file".
7) Process will take up to 10-15 minutes aproximately. Voilá, you will have Lollipop 5.0.2 on your RetailUS mobile.
Hope it will be useful for dummies, like me. Thanks.
Greetings from Chile.
Perfect
I had same issue and after all these steps my phone updated perfectly.
Many thanks.:good:
Really great help. Many thanks :victory:
Can anyone give me the link of IKXB21.14-L1.61 recovery?
Anyways, I downloaded and now uploading only the IKXB21.14-L1.61 recovery.
Link of IKXB21.14-L1.61 Recovery
eugineprakash said:
Are there any issues with upgrade?bcos iam currently in cm12.1 my bootloader version 41.19
I am planing to restore 4.4.4 us retail without downgrade my bootloader after that i am going upgrade from OTA in above thread.
Are there any issues with upgrade?Please guide me if i wrong.
Thanks,
Click to expand...
Click to collapse
You cannot downgrade the 41.19 bootloader to the 41.13. If you try to do that you WILL hardbrick your phone. However you can downgrade from Lollipop to Kitkat 4.4.4 (I know because I am on the 41.19 bootloader and was on cm 12.1 but restored to 4.4.4 successfully).
You have to flash the firmware for your phone except for the gpt.bin and motoboot.img. Flash all the other files in the firmware for your phone without those two and you should be fine.
xt1028 Moto G
I'll never flash stuffs with Motorola recovery! Today I did a factory reset with the stock recovery and damn! it deleted all my files in the internal SD! IT would have never happened if I would have factory reset with TWRP!
I'll wait for lost101's zip!