Hello,
is there an OTA package which i can flash with a stock recovery (my phone i locked, i don't like to have an unlocked bootloader)?
I am on 4.0.2 right now...
No, you need to be rooted or unlocked to flash the OTA package. Just wait for the official one, it will probably be pushed sometime during easter
I'm still waiting for the OTA aswell
I was pretty sure that the OTA process just downloads a file which will be flashed via the stock recovery. So if someone would have this stock OTA package (update.zip) i can just place in the internal storage and reboot into stock recovery. At least on my HTC Hero at 1.5 -> 1.6 it was working this way...must have remembered something wrong there...
bluefisch200 said:
Hello,
is there an OTA package which i can flash with a stock recovery (my phone i locked, i don't like to have an unlocked bootloader)?
I am on 4.0.2 right now...
Click to expand...
Click to collapse
Haven't tried it myself (since I am rooted and unlocked) but I recon that you can unlock (and loose ALL your data), root, flash the onetime CWM Recovery, flash the 4.0.4 stock image (by which you will loose root), relock (and loose ALL your data again).
At the end you would be completely stock again. That can all be done through the GNEX toolkit by Mskip that can be found here: Link.
You can download the official Google image from here: Link
bluefisch200 said:
I was pretty sure that the OTA process just downloads a file which will be flashed via the stock recovery. So if someone would have this stock OTA package (update.zip) i can just place in the internal storage and reboot into stock recovery. At least on my HTC Hero at 1.5 -> 1.6 it was working this way...must have remembered something wrong there...
Click to expand...
Click to collapse
that was probably right with the htc hero, also on my htc desire..because the ota package was picked by the stock recovery from the sdcard
but the stock recovery on our galaxy nexus with ics, expect the ota to be on the /cache partition..without root u can't write in that partition, only the os itself can write there
bluefisch200 said:
Hello,
is there an OTA package which i can flash with a stock recovery (my phone i locked, i don't like to have an unlocked bootloader)?
I am on 4.0.2 right now...
Click to expand...
Click to collapse
If you are on yakju, root using this method (note you only need temp root, so only do up to step 6), then place the update file from here to /cache and reboot into stock recovery and flash.
efrant said:
If you are on yakju, root using this method (note you only need temp root, so only do up to step 6), then place the update file from here to /cache and reboot into stock recovery and flash.
Click to expand...
Click to collapse
Thank you
Btw. it's easier to just root the OS (go above step 6) instead of only go to 6...for the cp command you will need busybox...i have seen "cat" somewhere but i couldn't figure out how it works...but i seems to be that you can copy files without installing busybox since cat is supported from android at stock...
bluefisch200 said:
Thank you
Btw. it's easier to just root the OS (go above step 6) instead of only go to 6...for the cp command you will need busybox...i have seen "cat" somewhere but i couldn't figure out how it works...but i seems to be that you can copy files without installing busybox since cat is supported from android at stock...
Click to expand...
Click to collapse
Correct, that is why I used cat in my directions instead of cp, as you would not have busybox installed if you are not root...
I'm still on 4.0.1
Is there any way to force an OTA update to 4.0.2 or 4.0.4 without rooting. Or manually install an update with a .zip update through stock recovery rather than CWM. I am unable to get any OTA updates it says my system is up to date which it clearly isnt.
Merio90 said:
Is there any way to force an OTA update to 4.0.2 or 4.0.4 without rooting. Or manually install an update with a .zip update through stock recovery rather than CWM. I am unable to get any OTA updates it says my system is up to date which it clearly isnt.
Click to expand...
Click to collapse
No..................
Sent from my Galaxy Nexus using Tapatalk
Related
If you've received the OTA update only, please comment.
Sent from my Galaxy Nexus using Tapatalk
Yes it does. You will need to re-root then re-flash CWM
And if I'm just using the stock ROM, just rooted?
Sent from my Galaxy Nexus using Tapatalk
It will still remove root, so you just need to re-root afterwards. You won't lose any data though as it doesn't re-lock fastboot or anything. Literally took 2 minutes.
Is there a guide to rerooting without unlocking fastboot, as I assume this differs from the original rooting process for this phone using the modified img and bat file?
CJSnet said:
Is there a guide to rerooting without unlocking fastboot, as I assume this differs from the original rooting process for this phone using the modified img and bat file?
Click to expand...
Click to collapse
Unfortunately no, you'll need the bootloader unlocked for the superboot method until there is a better root solution available
KiNG OMaR said:
Unfortunately no, you'll need the bootloader unlocked for the superboot method until there is a better root solution available
Click to expand...
Click to collapse
What I meant is that this OTA does not lock the bootloader. The bootloader is therefore unlocked. All I'm asking for is a step-by-step guide to rerooting from that state, with it unlocked.
Hmm this is weird. I was prompted to install the OTA fix. I just have the stock Google ROM, rooted and that's it. It rebooted, showed the wireframe hexagon animation for a second, and went to an android with a /!\ exclamation mark. I had to remove the battery.
Now I can't update and it has disappeared from the update page in phone settings. Check for update doesn't bring it back.
Is there a place to download the update patch?
Same thing happened to mine. I just found a zip of the update here and flashed it via CWM. You will still need to re-root and re-flash CWM.
ferris2375 said:
Same thing happened to mine. I just found a zip of the update here and flashed it via CWM. You will still need to re-root and re-flash CWM.
Click to expand...
Click to collapse
And here it is! Just rename to update.zip and place in the SD Card root folder, then reboot into recovery and install update.zip:
http://android.clients.google.com/p....signed-yakju-ITL41F-from-ITL41D.11bbbccb.zip
Hi guys, i need to learn something.
I use Bigxie [ROM] [OTA] [GSM] Android 4.2.2 JDQ39: Rooted Busybox Deodexed
and want to update 4.3 with similar;
Fireb33 [ROM] [JB] [JWR66Y] Galaxy Nexus 4.3 stock (deodexed, rooted, busybox)
So do I need to vipe anything or just download and flash via Twrp?
And better for me is: can i just download an "update.zip" (for same root-busybox-deodexed stock rom) instead a huge rom file?
Will i lose any data with any way?
I have root and un-lock my Galaxy Nexus today and flash IMM76D which is download from Google developer page (https://developers.google.com/android/nexus/images)
after finish all the step and updated to Android 4.0.4 Google official rom, I have received Android 4.0.4 System Update by OTA, and ask me reboot the phone !
after rebooting, Build number is updated to IMM76I. and the Baseband version is I9250XXLA2.
But I can not go into CWM anymore after updated by OTA. that's it is normal case......????????????
why un-root after updated by OTA ???????
Sent from my Galaxy Nexus using Tapatalk 2
Your meant to pull the battery out when your flashing the ROM .. geeeez some people don't read instructions anymore!
Remember! Pull your battery out whilst flashing!
Rename the OEM recovery restore file, reflash CWM recovery, and you should be good to go.
Gnex toolkit should help, if you don't have it already.
hki_peter said:
I have root and un-lock my Galaxy Nexus today and flash IMM76D which is download from Google developer page (https://developers.google.com/android/nexus/images)
after finish all the step and updated to Android 4.0.4 Google official rom, I have received Android 4.0.4 System Update by OTA, and ask me reboot the phone !
after rebooting, Build number is updated to IMM76I. and the Baseband version is I9250XXLA2.
But I can not go into CWM anymore after updated by OTA. that's it is normal case......????????????
why un-root after updated by OTA ???????
Click to expand...
Click to collapse
Everything is in the OTA update instruction thread...
efrant said:
Notes:
6) As with all stock updates from Google, these updates will change the permissions on the su binary so, in effect, you will lose root (for those who have it). Install supercurio's OTA Rootkeeper BEFORE you do all this, or, for those with an unlocked bootloader or CWM installed, just re-flash ChainsDD's Superuser zip file found here in CWM, or manually change the permission via ADB (mount the system and chmod 4755 /system/bin/su) while booted in CWM.
Click to expand...
Click to collapse
Recovery gets replaced to stock-version up on updating so cwm will need to be re-flashed after...
Sent from my Galaxy Nexus using xda premium
Tjotte said:
Recovery gets replaced to stock-version up on updating so cwm will need to be re-flashed after...
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yup. That is in there as well...
efrant said:
Notes:
5) For those of you that don't know, there are two files that re-flash the stock recovery on every boot (/system/recovery-from-boot.p and /system/etc/install-recovery.sh). You need to make sure that these files are either deleted or renamed, or else CWM will disappear when you reboot. These files serve no purpose other than re-flashing the stock recovery on every boot. So, if you've recently gotten an OTA and applied it, your CWM is gone...
Click to expand...
Click to collapse
zeekiz said:
Your meant to pull the battery out when your flashing the ROM .. geeeez some people don't read instructions anymore!
Remember! Pull your battery out whilst flashing!
Click to expand...
Click to collapse
What's the intention here? There's no need for this if you're not helping/explaining. What if he did and brick his phone? Would that make you happy?
Am I correct that the only images I need to flash to get back to OTA-updateable are:
Boot
System
(I already have stock Recovery, Radio, Bootloader)
I ask because I installed BusyBox recently (in a stock JB 4.1.1 install), and I want to get rid of it now, but I've heard that it leaves files in bin that break OTA
Matt08642 said:
Am I correct that the only images I need to flash to get back to OTA-updateable are:
Boot
System
(I already have stock Recovery, Radio, Bootloader)
I ask because I installed BusyBox recently (in a stock JB 4.1.1 install), and I want to get rid of it now, but I've heard that it leaves files in bin that break OTA
Click to expand...
Click to collapse
Yes.
efrant said:
Yes.
Click to expand...
Click to collapse
Thanks!
Hi I m really new to this so excuse me ...
i got many updates by flashing with fastboot prerooted system.img i was on 2.19.40.18 prerooted but i would like to go to a stock no rooted to be able to apply OTA now
I tried an erase of my phone, but i came back to prerooted ...
I tried to install tethered TWRP and to install the.zip from asus download page but it was stuck on updating IFWI .... ( 2.19.40.20 zip file from asus )
What can i do ?
Plz help me
You need to go into the SuperSU settings, scroll to near the bottom and choose "Full unroot."
I did all on this post : http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
I did unroot, flashed all 4 line before but i think my recovery is corrupted, it end in error with the green guy instantly and flashin via fastboot recovery.img isnt doing anybetter ...
I m really stuck ..
i was trying an adb sideload with a stock rom is this a good idea ? i got error protocol fault ...
shinjy87 said:
i was trying an adb sideload with a stock rom is this a good idea ? i got error protocol fault ...
Click to expand...
Click to collapse
Protocol fault is because you don't use latest ADB. Google it.
i successfully did this but now adb is stuck on serving 13 % and on the phone : verifying update package , it stopped like 15 min ago ...
Here's what I did to go from pre-rooted system back to stock.
1. Download the official latest image from Asus http://www.asus.com/support/Download/39/1/0/13/Lk0Sg1Ulh0Ph49Hl/32/
2. Rename the zip to MOFD_SDUPDATE.zip
3. Unroot via SU
4. Uninstall Xposed and modules if you have them busybox etc. (uninstall.bat for xposed it's easy)
5. Copy MOFD_SDUPDATE.zip to an SD card and insert into phone or copy to internal memory
6. Boot into recovery by holding power and volume up
7. If you get dead android press power button and volume up button and release.
8. Auto installs new image
I went this route after unrooting via SU and uninstalling xposed framework still wouldn't let me run OTA updates for some reason. I imagine I did something along the road or removed a system app or something. It wouldn't let me manually sideload or update and would error out halfway through the process. I cleared fastboot cache and even reset the device to no avail. I was on 2.19.40.18. I installed the 2.19.40.20 image then the OTA update to .22 yesterday.
If I root the device again which is likely I'll use method 3 and the rootkit tool.
i will try your way, installing the 22 now.
But i dont remember in recovery the auto installs new image ?
error in recovery trying to update the .22 like you said, i need to put the .20 before the .22 ?
shinjy87 said:
error in recovery trying to update the .22 like you said, i need to put the .20 before the .22 ?
Click to expand...
Click to collapse
I installed the 2.19.40.20 full system image (1.1GB) from Asus yesterday. They didn't have the full image for .22 up but they do now. I was on the .18 pre-rooted image. When you hold power and volume up choose recovery and it should install the MOFD_SDUPDATE.zip automatically (mine did). I had issues trying to manually update the phone from .18 to .20 and .22 via ADB (the patches are like 30MB). It would start the update with the android robot then fail about halfway.
Download the correct system image for your device. The new update is available as a full image now so download the .22 image from Asus and then rename it to MOFD_SDUPDATE.zip. Copy it to an SD card and insert it back into your phone. Phone is powered off so hold power and volume up to get the recovery screen. It will say Normal in a big green arrow. Change it to recovery via the volume buttons then hit power button and it should find and automatically install the MOFD_SDUPDATE.zip image.
FYI this is on a ZE551ML 4GB/64GB US WW firmware based phone. I imagine the other models are the same or very similar.
I wish I could articulate this better. Hopefully someone more knowledgeable comes along and lends a hand.
Hi, want to ask.
Previously i root by using Method 1 (PRE-ROOTED SYSTEM.IMG).
can i use your method to revert to stock rom and root again using Method 3 (1 CLICK ROOT TOOL)?
wlbwlb said:
Hi, want to ask.
Previously i root by using Method 1 (PRE-ROOTED SYSTEM.IMG).
can i use your method to revert to stock rom and root again using Method 3 (1 CLICK ROOT TOOL)?
Click to expand...
Click to collapse
Yes.
Induced_Apathy said:
Yes.
Click to expand...
Click to collapse
Thank, another question. will it wipe all my data?
wlbwlb said:
Thank, another question. will it wipe all my data?
Click to expand...
Click to collapse
Flashing the entire system image you want to wipe everything anyways in this case. If you mean using the one click rootkit (method 3) to root then no it will not.
Yea. I'm hoping someone finds a way to return this to a "never been rooted" device where the OTA actually works.
madmike23 said:
Yea. I'm hoping someone finds a way to return this to a "never been rooted" device where the OTA actually works.
Click to expand...
Click to collapse
Flash the .18 pre-rooted, then don't update SuperSU binary. Take OTAs as needed.
If OTA doesn't show up, download the OTA and adb sideload into stock recovery.
Harfainx said:
Flash the .18 pre-rooted, then don't update SuperSU binary. Take OTAs as needed.
If OTA doesn't show up, download the OTA and adb sideload into stock recovery.
Click to expand...
Click to collapse
I've done that before, with any OTA, it'll give me the error droid when installing. That's when I said screw it, and try to unroot. And now I'm stuck with that error no matter what.
madmike23 said:
I've done that before, with any OTA, it'll give me the error droid when installing. That's when I said screw it, and try to unroot. And now I'm stuck with that error no matter what.
Click to expand...
Click to collapse
What does the recovery log say?
Harfainx said:
What does the recovery log say?
Click to expand...
Click to collapse
Only thing that caught my attention is: Unable to open '/sdcard/MOFD_SDUPDATE.zip': No such file or directory.
This was last attempt unrooted and this morning's OTA
So, I have a Sprint HTC 10. It was rooted, and then an OTA update came out about a week or so ago, version 1.80.651.10.
I unrooted and installed it, since I have TWRP it seems to take over the install process, but more or less does install it correctly.
Once my phone rebooted, it complained that the download was corrupt like it always does (likely due to TWRP) but this has happened before and the update always actually does install successfully. Going to system settings I can confirm that I am on version 1.80.651.10.
However, this time, it seems hell-bent on assuming that the update didn't install. It keeps putting an update notification in the notification bar that refuses to go away. If I go to check for updates, it confirms that I am up to date and the notification disappears.... for a short while, but then appears again asking me to install the update.
How can I get rid of this annoying thing? I haven't even gotten around to re-rooting my phone yet, as been confirmed by root and safetynet checkers, the ROM is basically at stock right now.
Cyber Akuma said:
So, I have a Sprint HTC 10. It was rooted, and then an OTA update came out about a week or so ago, version 1.80.651.10.
I unrooted and installed it, since I have TWRP it seems to take over the install process, but more or less does install it correctly.
Once my phone rebooted, it complained that the download was corrupt like it always does (likely due to TWRP) but this has happened before and the update always actually does install successfully. Going to system settings I can confirm that I am on version 1.80.651.10.
However, this time, it seems hell-bent on assuming that the update didn't install. It keeps putting an update notification in the notification bar that refuses to go away. If I go to check for updates, it confirms that I am up to date and the notification disappears.... for a short while, but then appears again asking me to install the update.
How can I get rid of this annoying thing? I haven't even gotten around to re-rooting my phone yet, as been confirmed by root and safetynet checkers, the ROM is basically at stock right now.
Click to expand...
Click to collapse
If you have twrp installed it wont update the firmware only software. You need to flash firmware seperatly with fastboot.
So I would need to extract the firmware or something out of the OTA file and flash that manually? What partitions would the firmware be updating?
And I am assuming this would overwrite TWRP and I would have to reinstall it?
Cyber Akuma said:
So I would need to extract the firmware or something out of the OTA file and flash that manually? What partitions would the firmware be updating?
And I am assuming this would overwrite TWRP and I would have to reinstall it?
Click to expand...
Click to collapse
Correct.:good:
Can somebody please explain how to flash the firmware with fastboot?
So I have to flash the OTA with TWRP, afterwards I have to extract the firmware file out of the OTA.zip and flash it with fastboot. But which commands are necessary in fastboot?
To get this out of the way, you can only flash firmware over fastboot if you're S-OFF. Otherwise, you'll need to restore completely to stock via custom recovery or RUU then update by OTA.
The best guide I've found for this is at http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520.
kjjejones42 said:
To get this out of the way, you can only flash firmware over fastboot if you're S-OFF. Otherwise, you'll need to restore completely to stock via custom recovery or RUU then update by OTA.
The best guide I've found for this is at http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520.
Click to expand...
Click to collapse
Thats not true. You flash in ruu mode when S - ON. If your are S - Off you can do it from download mode. I think you are a little confused with that thread. Those firmwares are modified and for S -Off phones only.
yldlj said:
Thats not true. You flash in ruu mode. If soff you can do it from download mode.
Click to expand...
Click to collapse
Ah, you're right! Sorry. To flash while S-ON, the CID and MID must match the zip + the bootloader must be locked, right?
kjjejones42 said:
Ah, you're right! Sorry. To flash while S-ON, the CID and MID must match the zip + the bootloader must be locked, right?
Click to expand...
Click to collapse
Im not sure about locked or relocked bootloader, i think it will work with unlocked but i could be wrong.
yldlj said:
Im not sure about locked or relocked bootloader, i think it will work with unlocked but i could be wrong.
Click to expand...
Click to collapse
I just had another thought, correct me if I'm wrong. You can flash the OTA manually through the stock recovery as a ZIP.
The OTA ZIP can either be downloaded in various places online, or you can download it on the phone as usual then find it in /data/data/com.htc.updater/files (if your device is rooted). More info at http://forum.xda-developers.com/showpost.php?p=66548846&postcount=3.
You can then flash the OTA through recovery if you have;
* 100% unmodified system (can be restored from TWRP backup)
* Stock recovery
kjjejones42 said:
I just had another thought, correct me if I'm wrong. You can flash the OTA manually through the stock recovery as a ZIP.
The OTA ZIP can either be downloaded in various places online, or you can download it on the phone as usual then find it in /data/data/com.htc.updater/files (if your device is rooted). More info at http://forum.xda-developers.com/showpost.php?p=66548846&postcount=3.
You can then flash the OTA through recovery if you have;
* 100% unmodified system (can be restored from TWRP backup)
* Stock recovery
Click to expand...
Click to collapse
Correct. Also unmodified boot. But if your flashing unmodified system image, boot and stock recovery you may aswell just boot to android and take the ota.