I currently have my bootloader unlocked, S-OFF, TWRP recovery, and rooted stock verizon software (Most recent mini-update pushed from VZW around Thanksgiving). My question is whether my current configuration will allow me to accept the new 4.3 OTA update from verizon when it starts to roll out. Is custom recovery going to be a problem? I haven't messed with the stock software, other than adding superuser app. Thanks.
For all the other updates, stock recovery was necessary. I wouldn't see why the 4.3 update would be any different.
I still suggest waiting until the devs take the update and make a flashable Rom from it.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
kdj67f said:
For all the other updates, stock recovery was necessary. I wouldn't see why the 4.3 update would be any different.
I still suggest waiting until the devs take the update and make a flashable Rom from it.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Is it possible to flash or adb stock recovery back?
Yes, the stock recovery and files are posted here. I have reflashed the stock recovery and ota'd myself. As easy as flashing a custom recovery. You might want to read all the other ota threads here...
Sent from my HTC6500LVW using XDA Premium 4 mobile app
flyinfool2 said:
Is it possible to flash or adb stock recovery back?
Click to expand...
Click to collapse
yes, very.
search you'd find this thread.. http://forum.xda-developers.com/showthread.php?t=2485319
there you find this:
"
Arrow 1.10.605.10 Stock [Firmware/Radio] [Kernel] zips
Full Firmware, Boot.img, and Radio updates
Ok, so you now have the latest stock software.
You likely want to have the firmware and radios updated that came along with the OTA.
If that is the case, I have supplied the firmware.zip here that will update the firmware and radios to the latest version.
How to flash the Full firmware/radio zip:
Separate Radios, Recoveries, and Kernels are also available below,
if you are on a custom rom or don't need/want the full firmware!
Download the appropriate firmware version for your stock based rom:
1.10.605.10 firmware.zip
1.10.605.15 firmware.zip
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip
It will say that the update did not finish, to flush again, repeat the above step:
fastboot flash zip firmware.zip
Quote:
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
fastboot reboot-bootloader (this reboots the device to bootloader)
That's it, you're done. You can now reboot and will be running the latest firmware and radios.
If you have any questions or issues, let me know.
Stock m7vzw
Kernels, Radios, Recoveries!
Kernel Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
****In case anyone wants just the stock kernel and modules:
1.10.605.10 stock kernel
1.10.605.15 Insecure stock kernel - R/W enabled
Flash in Recovery, wipe cache and dalvik, reboot.
Radio Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
I went ahead and made these baseband zips as well.
Basebands/Fastboot Flashable:
These radio.zips must be flashed the same way as the firmware zip at the top of this post.
With the exception that it will not need to be reflushed/reflashed a second time during the process."
http://www.androidfilehost.com/?fid=23212708291682230 - flash in recovery
Great info, Thanks!
flyinfool2 said:
I currently have my bootloader unlocked, S-OFF, TWRP recovery, and rooted stock verizon software (Most recent mini-update pushed from VZW around Thanksgiving). My question is whether my current configuration will allow me to accept the new 4.3 OTA update from verizon when it starts to roll out. Is custom recovery going to be a problem? I haven't messed with the stock software, other than adding superuser app. Thanks.
Click to expand...
Click to collapse
You have to have stock recovery to OTA. But can I ask why you'd want to OTA anyway? Devs will have a rooted stock zip in no time after the update is pushed. There is literally no reason to OTA. A lot of ppl, for whatever the reason, think it's important to have the official OTA. If you want stock unrooted backups I get that. I do that sometimes in case of emergencies. Other than that you really don't need to OTA. You can reflash stock recovery easy enough and OTA if you want but I wouldn't. Since you have an unlocked bootloader and all then at most you would have to flash superuser again but the general rule is never OTA.
---------- Post added at 09:25 AM ---------- Previous post was at 09:24 AM ----------
andybones said:
yes, very.
search you'd find this thread.. http://forum.xda-developers.com/showthread.php?t=2485319
there you find this:
"
Arrow 1.10.605.10 Stock [Firmware/Radio] [Kernel] zips
Full Firmware, Boot.img, and Radio updates
Ok, so you now have the latest stock software.
You likely want to have the firmware and radios updated that came along with the OTA.
If that is the case, I have supplied the firmware.zip here that will update the firmware and radios to the latest version.
How to flash the Full firmware/radio zip:
Separate Radios, Recoveries, and Kernels are also available below,
if you are on a custom rom or don't need/want the full firmware!
Download the appropriate firmware version for your stock based rom:
1.10.605.10 firmware.zip
1.10.605.15 firmware.zip
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip
It will say that the update did not finish, to flush again, repeat the above step:
fastboot flash zip firmware.zip
Quote:
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
fastboot reboot-bootloader (this reboots the device to bootloader)
That's it, you're done. You can now reboot and will be running the latest firmware and radios.
If you have any questions or issues, let me know.
Stock m7vzw
Kernels, Radios, Recoveries!
Kernel Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
****In case anyone wants just the stock kernel and modules:
1.10.605.10 stock kernel
1.10.605.15 Insecure stock kernel - R/W enabled
Flash in Recovery, wipe cache and dalvik, reboot.
Radio Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
I went ahead and made these baseband zips as well.
Basebands/Fastboot Flashable:
These radio.zips must be flashed the same way as the firmware zip at the top of this post.
With the exception that it will not need to be reflushed/reflashed a second time during the process."
http://www.androidfilehost.com/?fid=23212708291682230 - flash in recovery
Click to expand...
Click to collapse
Well damn andy. Dropped the knowledge bomb on him
Yeah it's not worth OTA'ng, especially given the experience vzw S4 owners had with getting their root exploits and such closed...
Flashable OTA update question
So my One is unlocked and S-off. I manually updated to firmware version .15, however, my ROM is still version .10. (I could not download the version .15 ROM version as it was taking way too long) I keep getting the constant nag about the software update. I want to stay current, but dont want to lose ROOT or worse.
First, how do you use a flashable rom file to update your current rom? I dont what to have to backup and flash a new rom and restore all my settings everytime if I can avoid it. Is there a way to just update like what the OTA does?
Here was my thought. I would make a backup and clean install the current version (.15) of a custom, stock ROM. This would prevent future OTA's correct? Then, I would just update with flash-able files as they are released to keep my ROM up to date and ROOT privileges, etc safe?
Or would it be possible to update my current .10 ROM to .15, disable all OTA's and then flash updates as they are released?
BreakingVZW said:
You have to have stock recovery to OTA. But can I ask why you'd want to OTA anyway? Devs will have a rooted stock zip in no time after the update is pushed. There is literally no reason to OTA. A lot of ppl, for whatever the reason, think it's important to have the official OTA. If you want stock unrooted backups I get that. I do that sometimes in case of emergencies. Other than that you really don't need to OTA. You can reflash stock recovery easy enough and OTA if you want but I wouldn't. Since you have an unlocked bootloader and all then at most you would have to flash superuser again but the general rule is never OTA.
---------- Post added at 09:25 AM ---------- Previous post was at 09:24 AM ----------
Click to expand...
Click to collapse
This is my wifes phone, so she is not concerned with having any custom operating ROM. For me however, I have always been a hacker at heart, and I love to run different ROMS on my own phone. For her phone, I just want the ability to run the most recent stock software, with root, so that I can make backups and freeze unnecessary apps to my liking. If a rooted stock zip is just around the corner, then I see no need to take the OTA update as you stated. Thanks for the insight. I just didn't realize that I could get the same result (an updated stock, rooted update) without taking the OTA. I appreciate the help! :good:
What can I do in the meantime to prevent my wife from accidentally accepting the OTA (it just began pushing on her phone)? I know the update wont take without stock recovery installed, but is there an easy way to prevent the repeated download and prompt for install?
EDIT: I found another thread with a flashable file to stop OTA...thanks all
For whatever reason I can't get the OTA to apply. It gets about 25 to 30% of the way through the installation and then gives me the red Triangle/Exclamation point. I first tried after flashing back to the 1.10.605.15 recovery and after that failed I flashed the full 1.10.605.15 firmware with the same result. Any ideas?
wpsantennas said:
For whatever reason I can't get the OTA to apply. It gets about 25 to 30% of the way through the installation and then gives me the red Triangle/Exclamation point. I first tried after flashing back to the 1.10.605.15 recovery and after that failed I flashed the full 1.10.605.15 firmware with the same result. Any ideas?
Click to expand...
Click to collapse
I have that. Haven't figured it out yet either. I did the stock recovery too. s-off and unlocked.
Had the same exact problem as WPSantennas and paganhobbit. Endded up using this thread http://forum.xda-developers.com/showthread.php?t=2475216 to return to S-On, Locked Bootloader at 1.10.605.8 (For mine to work right on this tutorial I had to skip the 2nd 'fastboot oem rebootRUU' after failing for it work.) I think the latest OTA doesn't really like if you have modified or deleted their stock bloat apps for some reason. IMO, The update is not impressive at all and I'd advise to stay at 4.2.2 but this is may be good to do if you want to bump to KitKat in the future. Hope this helps!
EDIT: Here's the link to the RUU I used since the link on the original was dead: http://www.android-edge.com/Login/uploads/PN017IMG_M7_1.10.605.8.zip
I ended up RUU-ing as well, going back to .10. Then it updated to .15 and the 4.3 update without a problem. I didn't re-lock or go S-On to do this. I had tried three different "official stock recovery" files I found, but 4.3 wouldn't update successfully with any of them.
A new problem is it doesn't seem to want to remember my WiFi connections for some reason now. If I go out of range and come back, I have to re-enter the WPA2 key all over again. I suspect it's Verizon's ploy to make me use more data
I have the latest full stock base for the Galaxy Tab Pro 12.2 Wifi (SM-T900) and want to make a bootloader package that can be flashed in ODIN.
Inside of the full stock tar file is:
boot.img
recovery. img
system. img
cache.img
hidden.img
sboot.bin
Which is the bootloader, and what do I need to do to the file, if anything, so that it can be flashed individually in ODIN? Also, should there be a modem file? Alternatively, is it possible to create a zip of these things (bootloader, modem) that's flashable in TWRP?
Thanks in advance for any help.
trav06 said:
I have the latest full stock base for the Galaxy Tab Pro 12.2 Wifi (SM-T900) and want to make a bootloader package that can be flashed in ODIN.
Inside of the full stock tar file is:
boot.img
recovery. img
system. img
cache.img
hidden.img
sboot.bin
Which is the bootloader, and what do I need to do to the file, if anything, so that it can be flashed individually in ODIN? Also, should there be a modem file? Alternatively, is it possible to create a zip of these things (bootloader, modem) that's flashable in TWRP?
Thanks in advance for any help.
Click to expand...
Click to collapse
I'm not quite sure which one is bootloader. Sometimes you can't flash each one individual ly with odin(ex like creating an odin tar that just has system). Modem files are only on lte devices. Most times you don't need them for custom roms. Anyway, you can extract each IMG and create and tar the IMG up. There are a few commands and guides to tar something and add md5 to them.
As for a flash able zip yes and no. Bootloader can't be flashed in twrp most times since I have never seen anything like that. You usually have to flash bootloader with odin. Modems don't need to be flashed since twrp doesn't mess with it most times. But you can create an flash able zip of kernel, recovery and I'm unsure of system.img(may need to extract or adjust updater scipt. Though I dont fully know).
Usually the twrp flashable in ArchiKitchen so it can help with the updater scipt stuffs. Just don't add any options such as root and busybox to it. I've never seen a flashable bootloader in twrp so it's highly unlikely of it being possible.
Hope this helps!
trav06 said:
I have the latest full stock base for the Galaxy Tab Pro 12.2 Wifi (SM-T900) and want to make a bootloader package that can be flashed in ODIN.
Inside of the full stock tar file is:
boot.img
recovery. img
system. img
cache.img
hidden.img
sboot.bin
Which is the bootloader, and what do I need to do to the file, if anything, so that it can be flashed individually in ODIN? Also, should there be a modem file? Alternatively, is it possible to create a zip of these things (bootloader, modem) that's flashable in TWRP?
Thanks in advance for any help.
Click to expand...
Click to collapse
Hi
The bootloader tar package for flashing in ODIN:
1) boot.img
2) sboot.bin
Use 'Total Commander' (google it) to make tar package (bootloader).
Any luck with the port?
shayind4
I downloaded the stock untouched 10c firmware zip, and the 10c partitions zip and extracted them. I got bin files and I renamed the modem from bin to IMG and bootloader I'm not quite sure which file is it. IIRC its the aboot.bin which I'd rename to IMG.
In twtp I tried flashing just the modem and its asking which partition boot or recovery to flash it. I chose neither cause modem obviously doesn't belong there.
Can I use flashify for the modem IMG and bootloader one? Once I know which one is bootloader?
Or what's the best way? I'm downgrading both since I've heard res-remix 5.4.1 (android 5.1) will let data work with them
Why are you trying to downgrade? 10m had best battery life, 10r was most stable. 20b is both
Hello,
I installed Android 6 GPE RUU from @graffixnyc on my M8, then I installed TWRP recovery. Now theres an OTA Update. The only solution to update without a loosing data is flashing the orignal recovery and then installing the ota. Correct?
But what recovery should I use? I found several images in this forum but I'm not sure which is correct.
Recovery needs to match your OS number or main version number.
You can find recovery.img in the firmware.zip in the OTA zip file
Found the image in an OTA package. Thank you
My phone is Asus Zenfone 2 (ZE551ML, Z00AD).
As described in another thread, I was unsuccessfully trying to unlock my bootloader. In the process, I also lost the stock recovery.
I learned how to flash stock recovery to repair it.
My firmware version is WW-2.20.40.198. I haven't been able to find the stock recovery file for that exact firmware version. However, I have been able to get a hold of the WW-2.20.40.196 stock recovery file. I was told on XDA-Developers that this would be fine, so I flashed it via Fastboot.
It seems to be working, although I haven't tried to actually flash firmware through adb yet.
I'm now unsure of which firmware to flash through adb, WW-2.20.40.196 or WW-2.20.40.198.
I have two conflicting ideas.
On the one hand:
1. Since the recovery file I flashed with fastboot was 196, then perhaps I should also flash the 196 firmware file?
Or maybe:
2. If I flash the 198 file, perhaps it will also restore the 198 stock recovery? In that case, perhaps I can just flash the 198 firmware?