Database Info

[HowTo] How to update the System Software on rooted OTA phone with custom recovery

The OTA Update:
Your phone will download the OTA update as a zip file in the Download folder.
------------------------------------
The Problem:
------- quote by jackdowsan -------
I downloaded the file, placed it in my zip, went to cwm recovery and tried intall zip from sd card, it failed saying something about signature verification....
What are my options? I am on stock with root and custom recovery..
------------------------------------
The Solution:
I was in the same situation and I've resolved it by extracting the original OTA recovery.img from the OTA Update zip and flashed it through fastboot. Then I've updated the system software successfully and flashed back the ClockworkMod recovery.
If somebody needs a step by step guide, please see below:
WARNING! You may loose your root access after this procedure. Do not worry. You can root it again the same way you did before, or much easily by using the application Voodoo OTA RootKeeper (free, no ads, on the market). Just install it before you start and then again after the process to restore your root access.
1. Send the system software update archive located in your phone's download folder to your PC. Open it and inside you'll find another archive - firmware.zip. Open it and extract the original OTA recovery.img. Put it in the same folder with the fastboot.exe file.
2. On your HTC One X, enable USB debugging by going to Menu>>Settings>>Applications>>Development>>USB debugging and check-mark the box.
3. Turn OFF your smartphone using the Power button.
4. Press and hold Volume DOWN button and then immediately press Power button. Select Fastboot mode from the menu that appears on the screen.
5. Connect your phone to your PC using the USB cable that came with it.
6. Open a Command Prompt Window on your Desktop, go to the folder with your fastboot.exe and then type in the following commands. It will flash recovery on your phone.
fastboot flash recovery recovery.img
7. When the flashing is done, simply enter the following command into Command Prompt Window to reboot your phone.
fastboot reboot
8. You have successfully installed the original OTA Recovery on your HTC One X. Start the phone update again and it'll successfully update to 1.29.401.11. Your job is done!
9. Once everything is completed you can put ClockworkMod Recovery again by following the steps above but instead of using the OTA recovery.img file use the ClockworkMod recovery.img.
Cheers,
P.S. Sorry if this thread is not in the right place. Please move it if it's necessary. I'm still new here

Thanks a ton, would try this today

Just tried it, something did not go right, firtly, I had a little different update file then yours, I had
OTA_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7-1.28.401.9_release_259295wbmgoi0p47wgsfl6
which is like 34.5mb or something....
I extracted it and got recovery.img from firmware.zip and followed your guide, but after fastboot reboot, when I entered my phone, I still see it on 1.28.401.9
what could be wrong? I saw the fastboot recovery command executed just fine...what else can it be?
Thanks!

This solution should work on any OTA phone with custom recovery and root access.
So you flashed the OTA recovery.img, restarted the phone and in the normal mode you started the System Software update, right? My phone installed the update with no problems and it was showing the new version. The thing I lost was the root access but I explained how to gain it back.
If an experienced developer is reading this thread they may be able to advise us why the solution did not work with your phone.

Back to stock

I rooted, and loaded cm9 rom. I prefer stock rom but when I restored my backup there was no wifi (apparently a common issue). Anyway, I am looking for a way to get back to stock rom. I downloaded firmware from Asus but dont know if that is what I need or what to do with it. I am using the twrp recovery
Thanks for any help

All you have to do is download the full Asus ZIP from my thread and flash in CMW and it will restore your fully stock ROM without recovery
http://forum.xda-developers.com/showthread.php?t=1680570

ok thanks now to figure out how to get cwm into my tablet-- right now trying to install sdk

i installed something called eclipse.. I plug in tablet and get to fastboot mode then-- nothing happens- anyone know how one "flashes". Obviously techno noob here

this worked
Terminal Emulator Method
Install Android Terminal Emulator on your tablet.
Download the ClockworkMod Recovery image file directly to your tablet, preferably in the root of the /sdcard directory. Take note of where the file is saved. Rename the file to cwm-touch.blob.
Launch Android Terminal Emulator on your tablet.
Enter the commands below. If you did not save/move/copy the image file to the /sdcard directory, you need to replace /sdcardin the second command below with the correct directory where you saved the recovery image file to.
su
dd if=/sdcard/cwm-touch.blob of=/dev/block/mmcblk0p4
Reboot your tablet. The blob file will be automatically installed as your tablet reboots.

voodoo_dr said:
i installed something called eclipse.. I plug in tablet and get to fastboot mode then-- nothing happens- anyone know how one "flashes". Obviously techno noob here
Click to expand...
Click to collapse
You can uninstall Eclipse. It has nothing to do with Android or flashing anything. It's an Integrated Development Environment, which is kind of like a word processor for programmers. The only relation it has to Android is that it supports the Java programming language, so a lot of Android developers use it. If you're not going to be writing apps or messing with Android source code, it's probably best if you uninstall Eclipse, just because you won't use it, and it's taking up storage space.
Also, what were you expecting to happen when you put the tablet in fastboot mode? It just opens up a serial connection with a host (in this case, your computer) and allows the host to access the tablet via fastboot (sounds confusing, I know; it's not particularly fast, and doesn't have much to do with booting anything; it's like ADB but for low-level [hardware] flashing) and run commands. The tablet itself does nothing except display the message that it's in fastboot mode. Once the tablet says that, you run fastboot on the computer.

thanks for the reply. Now I have a brick---tried to install stock rom and hangs on asus with the wheel going round and round. It deleted my cwm so now no recovery on tablet. When I go into fastboot, it doesnt seem to recognize my tablet adb devices--nothing comes up

In my device manager I see no adp drivers- the only driver which keeps installing when I plug in the tablet and go to fastmode is the asus bootloader interface so I cant do anything with the tablet--- no recognition of device with adb devices command Help please

If you're in fastboot, ADB won't recognize the tablet. You need to use the fastboot commands with fastboot.
What to do:
-download the CWM blob on your computer
-put the CWM blob in the directory on your computer with the fastboot program
-boot the tablet into fastboot, and flash CWM
-boot into CWM, and restore the nandroid backup you should have made.
Alternately, if you didn't make a nandroid backup, you can boot into recovery, push the Asus stock ROM to /sdcard on your tablet via ADB (I'm assuming ADB works in the stock recovery), then reboot into recovery, and it should flash the update automatically. This will erase ALL your data, including /sdcard.

is cwm blob recovery.img?

I'm not sure if flashing .img files works with this tablet, but you could try. If it doesn't work, go to the place you got the recovery (as long as it's not from ROM Manager, and you're positive it's not the TF201's recovery), and there should be a file that ends in .blob. That's the one you need.

then I just place it in the same directory and click on fastboot? or is there more to it? seems to be having trouble with drivers mtp driver not installing???

I don't use Windows, so I don't know about the drivers. There's a thread in the development section with all the Windows drivers you need, though.
You put the blob in the directory where fastboot is. You open the command line (open Run, and type "cmd" [no quotes]) and run the fastboot command from there.

got it thanks cwm is back

[Q] Problems Flashing Recovery on Asus TF300T

I have tried literally every method that I've found on the net to flash recovery on my Asus TF300T, and nothing works. The tablet stays at "Starting Fastboot USB Download Protocol" when I plug it into my computer. When I open a command prompt and enter in the command lines, it just keeps saying "Fastboot is not recognized as an internal or external command". The guides say that after entering the commands, a blue installation bar should appear on my tablet, but nothing happens at all. I don't know what else to do. I updated to the OTA 4.1.1 firmware as soon as I got the tablet I can't root nor can I find a way to flash any type of recovery. Can anyone help? Thanks in advance...

Installing TWRP.
I added the file to the message. The latest version of Android SDK Tools pulled adb and fastboot and made a command file to install it, so as not to type it manually.
This archive should be unpacked in the root of drive C. Folder was adb-t. In this folder, copy the file to your custom recovery tablet model and its version of the android, rename it to twrp.blob. We go on the tablet mode fastboot, connect the tablet to the computer and launch twrp.bat.
Installs the custom recovery, expect to fill the display screen tablet and press the space bar (any key) on the keyboard to restart the tablet. Remove the cables from the tablet.
Attention! The current archive file contains the last (2.3.1.0) custom recovery (twrp.blob) for TF300T with JB. If you have a TG or some version of android - do not forget to replace twrp.blob of the edition you need.

Thank You!
BrateloSlava said:
Installing TWRP.
I added the file to the message. The latest version of Android SDK Tools pulled adb and fastboot and made a command file to install it, so as not to type it manually.
This archive should be unpacked in the root of drive C. Folder was adb-t. In this folder, copy the file to your custom recovery tablet model and its version of the android, rename it to twrp.blob. We go on the tablet mode fastboot, connect the tablet to the computer and launch twrp.bat.
Installs the custom recovery, expect to fill the display screen tablet and press the space bar (any key) on the keyboard to restart the tablet. Remove the cables from the tablet.
Attention! The current archive file contains the last (2.3.1.0) custom recovery (twrp.blob) for TF300T with JB. If you have a TG or some version of android - do not forget to replace twrp.blob of the edition you need.
Click to expand...
Click to collapse
Oh, man! You have no idea how grateful I am to you!!! I have been trying to get this done FOREVER, and this finally got the job done...thank you sooooooooooo much! It is appreciated!

Need help restoring device, big problem, read inside

Could someone please help me with this? I have posted a thread over on Android Forums with all the problems.
http://androidforums.com/asus-eee-p...restoring-device-big-problem-read-inside.html
Also, I have posted on here in the past about this, but I honestly am a giant noob at android and did not know what they were telling me to do.
Any help would be really great, thanks!

Since you can still boot your OS, you should be in good shape.
Try installing GooManager from the Play Store.
After installed, open it and grant root permissions.
Next, tap the menu key in the top right (3 stacked boxes) and then choose the Install OpenRecovery Script. This will install TWRP recovery which is far superior to any CWM I have ever run.
See if that installs properly (if yes, you will end up in TWRP recovery during a reboot)
TWRP allows you to see the internal and external memory to flash new ROMs.

frederuco said:
Since you can still boot your OS, you should be in good shape.
Try installing GooManager from the Play Store.
After installed, open it and grant root permissions.
Next, tap the menu key in the top right (3 stacked boxes) and then choose the Install OpenRecovery Script. This will install TWRP recovery which is far superior to any CWM I have ever run.
See if that installs properly (if yes, you will end up in TWRP recovery during a reboot)
TWRP allows you to see the internal and external memory to flash new ROMs.
Click to expand...
Click to collapse
I will try this out when I get home. Thank you. I will report back with what happens.
Edit: Also congratulations on 100 thanks.

format your micro SD and only put the ROM you want in it. Now install twrp as other guy said and reboot into twrp recovery in go to wipe and wipe (dalvik, cache, internal memory, system and everything else expect micro SD). Then do a clean installation of ROM and you should be good to go.. if that doesn't work then try easy flash
Sent from my Transformer using xda app-developers app

frederuco said:
Since you can still boot your OS, you should be in good shape.
Try installing GooManager from the Play Store.
After installed, open it and grant root permissions.
Next, tap the menu key in the top right (3 stacked boxes) and then choose the Install OpenRecovery Script. This will install TWRP recovery which is far superior to any CWM I have ever run.
See if that installs properly (if yes, you will end up in TWRP recovery during a reboot)
TWRP allows you to see the internal and external memory to flash new ROMs.
Click to expand...
Click to collapse
This did not work, I still boot into cwm when the device restarts after downloading it.

Here is another thing to try:
If you can boot and want to try TWRP, here is another way to install it so long as you are rooted:
Download the 2.3.2.3 blob from HERE
Place the recovery blob in the /sdcard/ directory. We are going to pretend the downloaded file is called TWRP.blob
Open a terminal window and enter these commands
Code:
su
cd /sdcard/
ls
dd if=TWRP.blob of=/dev/block/mmcblk0p4
reboot recovery
the ls will tell you if the blob is indead where it is supposed to be, if it can be seen, you should be good to go on to the dd command, if you don't see the file, do not procede.
Make sure to change TWRP.blob to the actual name and location of the file you downloaded
Let me know how it goes

frederuco said:
Here is another thing to try:
If you can boot and want to try TWRP, here is another way to install it so long as you are rooted:
Download the 2.3.2.3 blob from HERE
Place the recovery blob in the /sdcard/ directory. We are going to pretend the downloaded file is called TWRP.blob
Open a terminal window and enter these commands
Code:
su
cd /sdcard/
ls
dd if=/TWRP.blob of=/dev/block/mmcblk0p4
reboot recovery
the ls will tell you if the blob is indead where it is supposed to be, if it can be seen, you should be good to go on to the dd command, if you don't see the file, do not procede.
Make sure to change TWRP.blob to the actual name and location of the file you downloaded
Let me know how it goes
Click to expand...
Click to collapse
I cannot connect the device to my computer at all. I have usb debugging enabled and everything. It freezes for a couple of seconds when I plug the device in, and then says that installing the drivers has failed in windows. I am trying to run adb and it says no devices are connected.

BloodyRory said:
I cannot connect the device to my computer at all. I have usb debugging enabled and everything. It freezes for a couple of seconds when I plug the device in, and then says that installing the drivers has failed in windows. I am trying to run adb and it says no devices are connected.
Click to expand...
Click to collapse
You don't need to do this on your PC, so long as you can boot you can do it on your tablet.

frederuco said:
You don't need to do this on your PC, so long as you can boot you can do it on your tablet.
Click to expand...
Click to collapse
Ah, sorry, long time since I've done this. Alright, well I've gotten into terminal emulator and I've typed that exactly, switching over my directory to my microsd though and changing the file name to the exact one. I'm getting a "cannot open for read: No such file or directory" error when I do this. I have also tried moving the file to /sdcard/ and I have named the file twrp.blob, and neither of these have helped.

Did you issue the su command and get a popup for root access?

frederuco said:
Did you issue the su command and get a popup for root access?
Click to expand...
Click to collapse
Yes, that was the first thing I did. I did exactly as you said. I've tried changing file names, changing directories and everything but for some odd reason I'm getting the same error.
Edit: and yes, I'm changing those when I enter them in terminal as well.

Strange.
I'll have to troubleshoot this in a bit. I'll let you know what I find.

frederuco said:
Strange.
I'll have to troubleshoot this in a bit. I'll let you know what I find.
Click to expand...
Click to collapse
Thank you. Here is an image of what I have typed in case it is an error on my part.
http://i.imgur.com/lyJU8MR.jpg

Nope, error is on my part. Remove the "/" after the if=
It should be
dd if=TWRP.blob of=/dev/block/mmcblk0p4
Will update the other posts above.

frederuco said:
Nope, error is on my part. Remove the "/" after the if=
It should be
dd if=TWRP.blob of=/dev/block/mmcblk0p4
Will update the other posts above.
Click to expand...
Click to collapse
And it appears that I am still in clockworkmod when the device boots up.

BloodyRory said:
And it appears that I am still in clockworkmod when the device boots up.
Click to expand...
Click to collapse
Try a normal reboot at the end instead of reboot recovery and see if that works.
If not, run through this and download one of the flashable .zip files (it is version 2.2.X.X) and see if that works. If so, then run through GooManager to get the 2.3.2.3.

Stock MF3 to MJ9 through sideload for those that can't update through OTA

Here is the OTA file thanks to the user: OTA update file from here http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
I have more instructions at the bottom but you take the OTA file and change the file type from .cfg to .zip and you use that (no other modifications to the file)
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked. I had to google how to run adb and where to get it. You can get adb from developer.google.com download the SDK (which will be in a zip). Extract the SDK and then run the sdkmanager.exe, after that choose the android SDK tools and platform tools. ADB will be in platform tools. Then you open up a command line window and you navigate to the folder that was created when you unzipped the SDK. Once you get there, you then navigate to the platform-tools folder (which is created when you run sdkmanager and install the androidsdk platform-tools). Once you get to platform tools use the command dir to see if adb.exe is there (which it should) then run adb devices (have your phone connected) and it should show a device connected. After that put your phone in recovery and then do the adb sideload and it will be waiting for you to run the command on the command line. Then on the computer you run the adb sideload blah.zip (it's posted on the first post also) and then.....wait everything should work.
I created this so we won't hijack the MJ6 to MJ9 thread and that way that can stay on topic for those users.

Good work, but you should fix your link to be http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
It's the truncated "..." version and doesn't work currently.

Ota link
raidel00 said:
Here is the OTA file thanks to the user: OTA update file from here http://forum.xda-developers.com/show...&postcount=325
I have more instructions at the bottom but you take the OTA file and change the file type from .cfg to .zip and you use that (no other modifications to the file)
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked. I had to google how to run adb and where to get it. You can get adb from developer.google.com download the SDK (which will be in a zip). Extract the SDK and then run the sdkmanager.exe, after that choose the android SDK tools and platform tools. ADB will be in platform tools. Then you open up a command line window and you navigate to the folder that was created when you unzipped the SDK. Once you get there, you then navigate to the platform-tools folder (which is created when you run sdkmanager and install the androidsdk platform-tools). Once you get to platform tools use the command dir to see if adb.exe is there (which it should) then run adb devices (have your phone connected) and it should show a device connected. After that put your phone in recovery and then do the adb sideload and it will be waiting for you to run the command on the command line. Then on the computer you run the adb sideload blah.zip (it's posted on the first post also) and then.....wait everything should work.
I created this so we won't hijack the MJ6 to MJ9 thread and that way that can stay on topic for those users.
Click to expand...
Click to collapse
Your link is short. http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325

Bimboy said:
Good work, but you should fix your link to be http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
It's the truncated "..." version and doesn't work currently.
Click to expand...
Click to collapse
silrosriv said:
Your link is short. http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
Click to expand...
Click to collapse
Ok...fixed it. Thanks for pointing it out!:good:

Help!
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted

does this wipe the device? or does it keep all your apps / data?

Update
I just chatted with someone at Samsung. The OTA has been pulled for issues by AT&T.

silrosriv said:
I just chatted with someone at Samsung. The OTA has been pulled for issues by AT&T.
Click to expand...
Click to collapse
probably due to some users having some issues with mms

silrosriv said:
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Interesting....It worked so smooth for me I don't know what else to say.

jherring002 said:
does this wipe the device? or does it keep all your apps / data?
Click to expand...
Click to collapse
If you do it by sideloading it from the computer it will not wipe the device. If you do it by running it from the SD card....it will wipe the device.

silrosriv said:
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
I get the same error. At this point, I may odin to stock and try again. Or, just forget it and root again and stay on MF3.

dwanhala said:
I get the same error. At this point, I may odin to stock and try again. Or, just forget it and root again and stay on MF3.
Click to expand...
Click to collapse
You might want to hold off for a while. It has been reported that the S4 4.3 OTA has been pulled due to "problems". AT&T is supposed to offer the OTA again at a later unspecified date. I would wait until the "problems" are ironed out and try for the OTA when it is re-released...if you still want it.

scott14719 said:
You might want to hold off for a while. It has been reported that the S4 4.3 OTA has been pulled due to "problems". AT&T is supposed to offer the OTA again at a later unspecified date. I would wait until the "problems" are ironed out and try for the OTA when it is re-released...if you still want it.
Click to expand...
Click to collapse
Yup. I chatted with someone at Samsung. The OTA has been pulled for issues by AT&T.
I think I'll jist wait for it to come back.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

It's working pretty good on my phone. I quit using the lookout security app though. It's not really needed. I know they pulled galaxy s3 update.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

silrosriv said:
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Had the same problem when I tried to sideload the update. I was on MF3 and was rooted. What worked for me was to delete all busybox files and unroot using SuperSU and odin back to stock, just in case. After that, I was able to sideload and the phone booted up with no problems.

It works pretty good on my phone also. Was on mj6 and it was having random FC's also random vibrating but now on mj9 I don't have those problems anymore.
Sent from my SAMSUNG-SGH-I337 using xda premium

Thanks
Sent from my SAMSUNG-SGH-I337 using Tapatalk

I was getting the same error. What I did was re-load mf3 (via odin) and then sideload this update.

scott14719 said:
You might want to hold off for a while. It has been reported that the S4 4.3 OTA has been pulled due to "problems". AT&T is supposed to offer the OTA again at a later unspecified date. I would wait until the "problems" are ironed out and try for the OTA when it is re-released...if you still want it.
Click to expand...
Click to collapse
Yeah, at this point I just rooted again (which of course set my device status back to official from the custom that it had changed to when I unrooted) and I'll wait to see if AT&T is going fix the problems before proceeding.

finally
I can't believe it
- Restore my S4 AT&T to 4.2.2 stock with Odin all the 4 files in MF3 using (download mode)
- Sideloaded to 4.3 ...MJ9 File with the Framework using (recovery mode)
Now my phone is even rooted with SuperSU (starting the root with vroot and converting it to SuperSU)
with the following sort video tutorial that found on youtube this morning
youtube.com/watch?v=isHYNqWCfSc