Download link for OTA Update - EVO 4G General

For anybody that is interested, here is the download link for the latest HTC update:
http://liveimage.htc.com/OTA_Supersonic_1.47.651.1-1.32.651.6_releaseqsvd1kamjri8pglf.zip
This might be interesting for an insight on how to be able to root the phone again.

So what would happen if I... lets say... replace the "recovery.img" file with the current clockwork.img one, renaming it to "recovery" and flash this update?
I have full root and am using Bugless V0.3.
Do we have to wait for a root/nand unlock for this new update before flashing a custom recovery/rom with it?
What are the difference between the updates that are 150mb and 30mb?

Related

[Q] System update 1.82.720.1

I received this OTA update on my HTC Desire Z. I'm from India.
Can anyone tell me how to update my phone with this update? I'm currently running the stock OS but with permanent root.
My phone details are
Android version : 2.2
Kernel version : 2.6.32.21-g9d69527
Build Number : 1.34.720.6
Forgot to mention why I'm asking this question. When I tried to update this new FOTA I got an error. Installation aborted.
Thanks
by clicking on accept?? maybe restart first ? probably a app is blocking the update, maybe you can do a whipe first?
I even tried updating it via clockwork mod by manually selecting the zip file. During that I got signature failure. Installation aborted
OTA updates do not work reliably on rooted phones, the problem you are having is beacuse of Clockwork what you should do is try to flash the stock htc recovery and then try to update,this worked for me but do remember you will loose root possibly forever (or atleast until a root comes out for 1.82 if at all) and all the advantages that go with it.
here is a tutorial for flashing recover images
http://forum.xda-developers.com/show...ht=flash_image
this is the default htc recovery image you can use in the above guide
http://www.sendspace.com/file/gu11ed
Thanks, the link doesn't work, can you fix this please?
Also wondering if I really lose my root etc, isn't using this guide: http://forum.xda-developers.com/showthread.php?t=985584 not a way to get back perm root etc?
If you don't want to loose root but you want the latest Sense, I suggest using VirtuousROM
Here: http://forum.xda-developers.com/showthread.php?t=837042
here you go
http://www.mediafire.com/?93fef9ac9webd4j
about the root i don't know it may or may not work, the thing is you can't be sure because no official root for 1.82 has been announced, i would tread with caution.

[Q] Version Rollback

I am having horrible issues after an OTA upgrade (see my post in general). Is it possible to download the rom and flash it from .13 back to .10?
I think you´ll need to download a full 3.1 ROM, flash it trough CWM and flash the update to .10
gasparzim said:
I think you´ll need to download a full 3.1 ROM, flash it trough CWM and flash the update to .10
Click to expand...
Click to collapse
Any idea where to get that ROM? I've been at this all day, my brain is dead.
here
HTML:
http://forum.xda-developers.com/showthread.php?t=1174789
is the .10 but you can update it to .11
You need to decrypt it with xor
HTML:
http://www.box.net/shared/mrg7y7k7zoib3peztxi2
extract the update.zip file and copy it to your micro SD (external) and use power+vol down to flash it.

Update to 2.3.6 and keep root

If you haven't already done so, install Rom Manager and flash Clockworkmod Recovery. It doesn't replace the actual recovery partition or the files that restore it so it won't affect flashing the update.
If you received an OTA notice don't flash it. You can go into /system/cache and copy it, or download it from the links in other threads. Place the update zip (no need to rename it) on the root of your sd card.
To install the update you must be fully stock (root is okay). That means any changed or deleted system files (including bootanimation.zip) will prevent the update from flashing. You will get a status 7 error. If you used Bloat Freezer you must defrost all before flashing the zip or it will error.
Also, have available whatever zip you used to root your Nexus one (i.e., su.zip or superboot, etc.) and put on the root of your sd card.
Once your system is back to stock reboot into CWM recovery and select flash zip from sd card. Then flash the 2.3.6 update file. Then DO NOT reboot yet. Now flash your root zip. After you have flashed both the udpate and the root zip you can reboot your phone. No need to wipe anything.
When your phone reboots you will have 2.3.6 and it will still be rooted. No bootloader gymnastics necessary.
I am using stock (almost) version of GRJ22 , but unfortunatelly I got the status 7 error when I tried to apply the update via clockworkmod recovery. I guess that's because I have already integrated some system apps into ROM using Titanium Backup.
So, if I flash stock vanilla GRJ22, then SU, then GRK39F (the incremental update) and finally SU again, won't that do the job??
Thanks..
Nikos_s3 said:
I am using stock (almost) version of GRJ22 , but unfortunatelly I got the status 7 error when I tried to apply the update via clockworkmod recovery. I guess that's because I have already integrated some system apps into ROM using Titanium Backup.
So, if I flash stock vanilla GRJ22, then SU, then GRK39F (the incremental update) and finally SU again, won't that do the job??
Thanks..
Click to expand...
Click to collapse
Yes, that will do nicely. Just need to get back to GRJ22 stock before you can flash the udpate. The updater-script does an assert and checks the md5 checksum of every system file before it allows the update to flash. If it doesn't find all stock files or checksums don't match what it is looking for, you get a status 7 error and the line above will show which file it stopped on. So you can look at those messages and keep restoring files it wants (if only a few) without having to flash completely back to stock.
I guess that would take much time, as almost all of my google apps are integrated into ROM...so I will try to follow the procedure I wrote earlier and if that won't work, I will try a ready stock,rooted ROM (Fireb33 has done it already)..
thanks mate..
Why so complicated?
You can update to 2.3.6 AND keep root even much more simple:
1.) Update from OTA to 2.3.6 (and loose root).
2.) Flash Superboot from Madaco and get back root.
Done in 3 minutes.. No need to flash, recover, overwrite and/or whatever, no need for ADB, no messing:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/
Bexton said:
You can update to 2.3.6 AND keep root even much more simple:
1.) Update from OTA to 2.3.6 (and loose root).
2.) Flash Superboot from Madaco and get back root.
Done in 3 minutes.. No need to flash, recover, overwrite and/or whatever, no need for ADB, no messing:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/
Click to expand...
Click to collapse
That's only for those who have the bootloader unlocked?
_raz_ said:
That's only for those who have the bootloader unlocked?
Click to expand...
Click to collapse
Well, yep. That method indicates your (phones) bootloader is unlocked. But as it's the N1, unlocking the bootloader is just 19 (up to 25) characters away -> "fastboot(-linux) oem unlock".
Edit: By the way, i looked up that post from an android platform engineer:
Code:
groups.google.com/group/android-platform/msg/b7d83992dd92accb?dmode=source
The N1 is just made for that.
tried superboot but wifi down
I flashed the update for 2.3.6 and then superboot but my wifi gives an error when I try to turn it on.
New Superboot file for GRK39F?
Is there a new Superboot file for the new OTA update?
jboxer said:
If you haven't already done so, install Rom Manager and flash Clockworkmod Recovery. It doesn't replace the actual recovery partition or the files that restore it so it won't affect flashing the update.
If you received an OTA notice don't flash it. You can go into /system/cache and copy it, or download it from the links in other threads. Place the update zip (no need to rename it) on the root of your sd card.
To install the update you must be fully stock (root is okay). That means any changed or deleted system files (including bootanimation.zip) will prevent the update from flashing. You will get a status 7 error. If you used Bloat Freezer you must defrost all before flashing the zip or it will error.
Also, have available whatever zip you used to root your Nexus one (i.e., su.zip or superboot, etc.) and put on the root of your sd card.
Once your system is back to stock reboot into CWM recovery and select flash zip from sd card. Then flash the 2.3.6 update file. Then DO NOT reboot yet. Now flash your root zip. After you have flashed both the udpate and the root zip you can reboot your phone. No need to wipe anything.
When your phone reboots you will have 2.3.6 and it will still be rooted. No bootloader gymnastics necessary.
Click to expand...
Click to collapse
I want to update to gingerbread and looking for the proper guidance going forward. I've done some looking around the forums but i'm still unclear if i need to unroot or install a stock build, etc. What i know is the phone is rooted and sim unlocked. How can i check to see if the bootloader is open/locked?
Current specs:
android version 2.2.1
Baseband 32.41.00.32U_5.08.00.04
Kernal Version 2.6.35.9-cyanogenmod
Mod Version: Cyanogenmod-6.1.1-N1
Build: FRG83D
edit:
Please treat me like an idiot and walk me through this process. It's be utterly frustrating and I'm a stone's throw away from busting out my Nokia 3390 (equipped with led disco keypad).
If your bootloader is unlocked you will see an unlocked padlock on the boot up screen...

[GUIDE] Easily switch between last updated stock (OTA support) and custom software

If you regularly install/test custom firmwares, ROMs and mods on your HTC One, it can be quite annoying and time-consuming if you want to go back to the latest stock software with official manufacturer OTA support (for example, to check if the latest official OTA update has been released for your region). Flashing the RUU is arguably the easiest and fastest way, but many of us have only older RUU's available which means having to download some quite big OTA updates every time. To avoid this inconvenience, i've done some research about the various methods to return to the latest stock version as hassle-free and as quickly as possible and i've come up with the following solution. This idea is not ground-breaking and might not be new to some (or most) of you, but i believe this guide should be useful for "noobs" or those who never thought of or didn't know how to handle OTAs and also to find the easiest and fastest way to swap any custom software (ROM/firmware) on your HTC One with the last 100% stock installation right before you flashed a custom recovery.
The procedure described below tries to eliminate the need to look for and flash stock firmware and stock ROMs uploaded by others, which may not necessarily exactly match with the original stock software of your phone especially since there exists dozens of HTC One variants. Using downloaded stock firmware/ROM from others might cause incompatibilities, degradation in performance, lost of signal, poor reception, etc. Ideally, you want to be able to flash whatever ROM/firmware and at any time, if you wish, you should be able to switch back to your own stock ROM and firmware. This is usually done by flashing your RUU (Rom Update Utility) according to your phone's MID and CID. However, most of you would need to go through an annoying and time-consuming update process to download several OTAs before finally reaching the current latest stock version. But here's a solution!
Minimum requirements:
1. Your HTC One's bootloader must be unlocked.
If your device is already S-OFF and if you relocked/locked your bootloader, then you can unlock the bootloader without having to use the official htcdev website. Just follow this guide to set the Bootloader as UNLOCKED: http://forum.xda-developers.com/showthread.php?t=2497712
2. You need to find your device's RUU (decrypted is even better as it allows going through the process faster) or your 100% stock software backup (firmware and ROM). If you made a nandroid backup after unlocking the Bootloader, it won't work since some data was wiped from your phone's memory during the unlocking process from the official htcdev website.
It's advised to use the RUU to restore which is specifically designed for a set of devices according to their MID and CID, rather than trying your luck at finding a compatible stock firmware and ROM for your HTC One variant. Here's a thread with a collection of RUUs and stock firmware/ROMs: http://forum.xda-developers.com/showthread.php?t=2428276
3. Your device should be S-OFF.
This is not an absolute requirement but S-OFF makes the whole procedure much easier. For the purpose of this guide, it will be assumed that your device is S-OFF.
Advantages of this method:
1. You will save time by being able to restore back to the latest 100% stock version very quickly (some OTA updates are around 400 MB which can take some time to download). You will only have to download the OTA's one time and then back up these OTA's to use later for updating/restoring your stock software.
2. You won't need an internet connection to update to your last stock version backup. The update process to previously downloaded (and backed up) OTA's will not require an internet connection. However, you will have to download any newer OTA's if available.
3. You will not have to rely on other sources to find your latest stock firmware and stock ROM. Therefore, you can be certain that you're getting a perfectly matching firmware and ROM for your specific HTC One model (the restored firmware and ROM will be exactly as if you never tampered with your device, with official manufacturer OTA support).
4. You will not have to downgrade if using an older RUU or older stock firmware/ROM, and then have to update it again via OTA. Your HTC One will be restored to 100% stock with the same software version just before you flashed a custom firmware/ROM.
5. If you absolutely need to run the RUU to go back to 100% stock, then you will not have to run the RUU process more than once (which will wipe all your nandroid backups as well as all your data, assuming you have a decrypted RUU, otherwise you will have to run the RUU twice only).
Procedure:
To summarize, if you want to go back to 100% stock using the method in this guide, all you will have to do is restore your nandroid backup and flash the firmware from the latest OTA. You will then get stock software with full OTA support within a few minutes from a custom installation. The method itself consists of handling official OTAs and extracting the most recent firmware in order to restore. But you will need a starting point where your device is 100% stock and able to receive and install official OTAs from the manufacturer. Let's assume that your HTC One is 100% stock. Whatever means you used to reach 100% stock, you will need it again. So, keep that RUU (preferably try to find your decrypted RUU zip) or stock files handy.
Check if you have any OTA update available:
No update available
If no OTA updates are available for your device, you can flash your custom recovery and then do a nandroid backup (very important). Then, you can root, flash a custom ROM and if you're S-OFF, you can even flash custom firmware.
Going back to stock: if you want to check for OTA availability at any time or you just want to go back to 100% stock, the easiest and safest way is to run your RUU. But if you found your decrypted RUU zip, you can go back to stock even faster; first restore your nandroid backup and then extract firmware.zip from the decrypted RUU zip and flash it. That's it. You're now back to 100% stock. You can check if there are any available OTAs and then go back to using custom ROMs again if you like.
Update available
Here is the more interesting part of this guide:
1. You will need the original firmware.zip file for your current stock software version. If you ran the RUU to go back to stock, extract rom.zip (follow this guide: http://forum.xda-developers.com/showthread.php?t=2497614) and then extract firmware.zip from the decrypted RUU rom.zip file. If the RUU rom.zip is not decrypted, it will give you an extraction error about all the files contained within being corrupt. In that case, you should try to find a decrypted version of the same RUU or decrypt it yourself (requires Linux, as decrypting an RUU is currently not possible on other OS). Use Winrar/Winzip to open the firmware.zip and extract recovery.img and place it in your adb folder.
2. Check for software update in the Settings menu. If you get OTA update notification, accept it. Note the file size of the OTA download, as it'll be useful to easily identify it later when searching in your device's internal memory. Let it download but do not install it. Select the option "Install Later" when prompted.
3. In the Settings menu, disable fastboot and enable USB Debugging.
4. Flash custom recovery. Root your device. Boot up to Android.
5. Install ES File Explorer from the Play Store (it's free) and give it root permission from its settings. Use ES File Explorer to search for the OTA on your phone. I found Root Explorer to be much faster at searching files although it's a paid app. You will usually find the downloaded OTA in your /sdcard/Download/ folder or /data/data/com.android.providers.downloads/cache/ folder. The OTA will have the keyword "OTA" in its filename and it will be a single zip file. You can also confirm that it's the OTA file by its file size from the earlier OTA pop-up notification. If you still can't find your OTA zip, you can search for "OTA" or "zip" through ES File Explorer or Root Explorer (much faster). Then go through the search results. Here's the original filename of one of my OTA's: OTA_M7_U_JB_50_S_HTC_Europe_2.24.401.2-1.29.401.2_R_P_release_325145_signedn3pctn48i51c9iue.zip. When you've found the OTA, copy it using ES File Explorer to the /sdcard/ location on your phone. Then plug in a USB cable to your HTC One and copy the OTA to a safe place on your PC hard drive.
6. Now, connect your phone via USB, reboot and go to your bootloader. We'll be flashing recovery.img from step 1. Use command "fastboot erase cache" then "fastboot flash recovery recovery.img" and finally "fastboot reboot". Now, you have 100% stock again with OTA support. The SuperUser/SuperSU app will still be visible on your phone but it won't work since the su binary will have been wiped during the stock recovery restore process.
7. Check for OTA software update again from the Settings menu. Install the downloaded file through the update notification menu. But if the update re-downloads, cancel it. Instead, you can manually flash it by copying the OTA zip to the phone's internal memory (don't have to rename the OTA zip but for simplicity, rename it to update.zip) and go to your Bootloader. Select Recovery using the Power button and then press the Power and Volume Up buttons to load the stock recovery menu. Then, select 'apply from phone storage' and navigate the menu as you would in a custom recovery to find update.zip and select it to install. It will follow the official update procedures and will reboot a few times before going back to your homescreen. Check attachments below for the stock recovery menu and options.
8. When your phone reboots, check for OTA again. If update is found, download it but choose "Install Later".
9. Then, just follow the same steps above; 4 through 8. Redo the same steps to copy the OTA to your PC and extract firmware.zip. The principle is that you should backup all the successive OTAs until there are no more updates available. The very last OTA's firmware.zip is the most important file. Keep it separately from the other firmwares. You should also save the previous complete OTA zips to be able to update quickly if you ever need to run RUU again.
10. After you've made a backup for the last OTA zip file, check for software update and install the already download OTA zip through the normal update notification menu. If the OTA update re-downloads, cancel it and do a manual flash for the OTA update that you saved previously, as explained in step 7. Note that an official OTA will update both the firmware and ROM.
11. Then, flash a custom recovery and make a complete nandroid backup to secure your last updated stock ROM. Copy the nandroid backup to your PC. Keep the nandroid backup and the last firmware.zip file (extracted from the last downloaded OTA zip file) safely as these two files are the only ones you will need to restore quickly back to 100% stock with OTA support, unless you were to run the RUU, in which case, you'll have to install all the OTA zip files successively.
12. Now, you can flash whatever you like on your HTC One. If you're S-OFF, you can flash custom firmware as well.
Going back to stock: if you want to check quickly if any OTA's are available or just want to easily go back to 100% stock software, all you have to do is first, restore the last nandroid backup of the stock ROM and then flash the firmware.zip from the last OTA update that you downloaded. That's it. Now, you can check and update easily to any new OTA that might have been released while your device was on custom ROM/firmware. Obviously, you can also backup any available OTA's, by following the same steps above.
I will probably expand this guide further if there is any interest in it.
If this guide was helpful to you, just press the "THANKS" button!
Hi, I found the guide useful, specially now with the upcoming 4.4 OTA. I'm confused thou, I heard you can't apply an OTA having a custom recovery, is this true? If so, shouldn't you have to flash stock recovery after loading a nandroid backup from recovery to be able to receive OTA's?
Arjen_Arg said:
Hi, I found the guide useful, specially now with the upcoming 4.4 OTA. I'm confused thou, I heard you can't apply an OTA having a custom recovery, is this true? If so, shouldn't you have to flash stock recovery after loading a nandroid backup from recovery to be able to receive OTA's?
Click to expand...
Click to collapse
You need to have 100% stock ROM and stock recovery in order to successfully apply an official OTA update. In order words, if you have custom recovery, you won't be able to update. You need to flash in the following order: stock nandroid backup, stock recovery, then download/install any new OTA.

Downloading OTA and turning into flashable zip + couple questions

Hi, everybody!
I have a couple questions and couldn't find clean answers.
I have an unlocked and rooted Moto G5 Plus (XT1683, build number NPNS25 . 137-15-5 - POTTER_BRAZILDSDS_CUST).
As you all may know, after a root process, you're not fully stock anymore.
1 - I have received the OTA August update (NPNS25.137-15-11) and i'm planning on installing it after restoring my device to stock. Since the update may not show up immediately after restoring the device, i'd like to download it and make it a flashable zip or something like that instead of waiting for a update notification that could take sometime to come back again.
Also, I couldn't find this OTA on the internet. How can i do that?
2 - I know I can find stock images/firmware at https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/ but I still have some doubts.
As said, my device's build number is NPNS25.137-15. At the link above, the firmware is named as NPN25-137-15. Also, I've found some people talking about NPN25 instead NPNS25. Are they all mistyping or is it really a different Moto G5 Plus version?
About the last NPN25.137-15 (Last updated 10-09-2017) file in the link: Is it the August update?
3 - What's up with all these variants for just one device? NPNS25-137-15, NPNS25-137-13, NPNS25-137-35, NPNS25-137-69. XT1681, XT1683, XT1685 in just one country. What a mess!
I know this questions may sound lame but I couldn't find solid answers and I don't intend to mess anything up. Better safe than sorry, right?
So you are currently rooted, correct?
Install a root file manager and make sure you can access /.
Download the OTA update.
Once it is finished downloading, you will find it in the /cache directory; copy it to your device storage, then to PC.
Since you don't want to take the update right away, reboot into recovery and wipe /cache; this will remove the ota file from /cache so that you don't accidentally auto update.
If you would be so kind, please upload the OTA and share the link.
I can make a TWRP flashable zip with it, as I have with other recent OTA files:
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
*edit*
You said your current build is NPNS25.137-15-5?
The closest available fastboot file available currently is NPN25.137-15, which means that I would also need the OTA file from NPN25.137-15 to NPNS25.137-15-5 for the current file to be of any use.
You could use the fastboot file to flash back to NPN25.137-15 and pull that OTA, or maybe even a larger OTA that goes from NPN25.137-15 directly to NPNS25.137-15-11.
Hi, thanks for your help!
Yes, i'm rooted and on NPNS25.137-15-5 right now. I'll upload the OTA file tonight when i'll be in no rush!
The closest available fastboot file available currently is NPN25.137-15, which means that I would also need the OTA file from NPN25.137-15 to NPNS25.137-15-5 for the current file to be of any use.
You could use the fastboot file to flash back to NPN25.137-15 and pull that OTA, or maybe even a larger OTA that goes from NPN25.137-15 directly to NPNS25.137-15-11.
Click to expand...
Click to collapse
-That means that NPNS25.137-15 is an updated version from NPN25.137-15?
Anyway, i'll upload the OTA file tonight!
Q9Nap said:
So you are currently rooted, correct?
Install a root file manager and make sure you can access /.
Download the OTA update.
Once it is finished downloading, you will find it in the /cache directory; copy it to your device storage, then to PC.
Since you don't want to take the update right away, reboot into recovery and wipe /cache; this will remove the ota file from /cache so that you don't accidentally auto update.
If you would be so kind, please upload the OTA and share the link.
I can make a TWRP flashable zip with it, as I have with other recent OTA files:
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
*edit*
You said your current build is NPNS25.137-15-5?
The closest available fastboot file available currently is NPN25.137-15, which means that I would also need the OTA file from NPN25.137-15 to NPNS25.137-15-5 for the current file to be of any use.
You could use the fastboot file to flash back to NPN25.137-15 and pull that OTA, or maybe even a larger OTA that goes from NPN25.137-15 directly to NPNS25.137-15-11.
Click to expand...
Click to collapse
I have uploaded the 93-8 OTA (March 2018 security patch)..if you could please convert it into a flashable ZIP we'd greatly appreciate it!
https://drive.google.com/file/d/1EihHeSrnj03usOKrLkZkWqdEjeMeIZQb/view?usp=sharing

Categories

Resources