So I flashed my wife's phone to TWRP without making a backup of the stock recovery just before T-Mobile released their OTA MM update and now I am tired of seeing the "update available" icon on the screen all the time. Does anybody have a flashable version of the update readily available that will not destroy any of her data partition (i.e. keep apps untouched, but update the firmware) or a link to it? Maybe a copy of the stock recovery so I can flash it back temporarily? Or a third option, make the downloaded update.zip file flashable? I have the update.zip file from her phone if needed if that last one is a viable option; it is only a 147 mb file as opposed to the 1.1 gb the returntostock.zip is.
There is a "Skinny" ROM available that is flashable through TWRP. It's the T-Mobile MM ROM with some minor tweaks.
As far as the data partition, I flashed it clean to avoid any bugs so I don't know how a dirty flash would work.
This time, make sure you do a nandroid backup in TWRP before doing any other flashing.
Related
If you are looking for the Odin-Flashable Image go here. These update files are based on that image.
These are recovery-flashable zips for the untouched Jelly Bean image that Nardholio provided.
They are as Samsung provided them with all the crap. I stripped the recovery though since i don't think anybody would want to loose theirs.
If you flash using TWRP (dunno about CWM), it detects that your current system is un-rooted and asks if you want to install SuperSU. If you want root, just let him do it.
I've split the update into three files:
JB stock modem (md5: 932407773cb6e0e5bd133da49ba8a442) as provided by Nardholio. This is just a mirror. Didn't touch that.
JB stock bootloader (md5: 2a980ce6d3f109f56e86b663f03fd761) that came with the update. Seems like it's purely optional. You only need to flash this once (if you want it) as it is usually not overwritten by any updates.
and the actual JB stock image (md5: b70f44d4619391c8f0f4debaa6239fc3)
cache/data wipe is required for the image.
if you just want the bootloader/modem there's no need to wipe.
The Odin image also came with an empty persist partition. None of these updates touches persist as you might want to flash back and have a ROM that relies on those files.
I've tested all the images and they work fine for me. But, certainly, they come without warranty. Flashing things, especially bootloader and modem, always come with the risk of bricking your phone. Be aware of it and don't blame me.
Hi
On flashing the new bootloader i am not getting any network...do i need to unlock again?
edit: Got network after trying several different SIMs. weird eh?
kilr00y said:
If you are looking for the Odin-Flashable Image go here. These update files are based on that image.
These are recovery-flashable zips for the untouched Jelly Bean image that Nardholio provided.
They are as Samsung provided them with all the crap. I stripped the recovery though since i don't think anybody would want to loose theirs.
If you flash using TWRP (dunno about CWM), it detects that your current system is un-rooted and asks if you want to install SuperSU. If you want root, just let him do it.
I've split the update into three files:
JB stock modem (md5: 932407773cb6e0e5bd133da49ba8a442) as provided by Nardholio. This is just a mirror. Didn't touch that.
JB stock bootloader (md5: 2a980ce6d3f109f56e86b663f03fd761) that came with the update. Seems like it's purely optional. You only need to flash this once (if you want it) as it is usually not overwritten by any updates.
and the actual JB stock image (md5: b70f44d4619391c8f0f4debaa6239fc3)
cache/data wipe is required for the image.
if you just want the bootloader/modem there's no need to wipe.
The Odin image also came with an empty persist partition. None of these updates touches persist as you might want to flash back and have a ROM that relies on those files.
I've tested all the images and they work fine for me. But, certainly, they come without warranty. Flashing things, especially bootloader and modem, always come with the risk of bricking your phone. Be aware of it and don't blame me.
Click to expand...
Click to collapse
Do you know where to find official Jelly Bean but not the latest one?
I think it was 4.0.4.
I need to test something with bluetooth related (as I am writing in other my post it might be worst in 4.1.2).
Regards
flashed modem and image. couldn't get Wi-Fi to work until i flashed the bootloader though.
froze a couple of times within the first 30min of playing with it, but whatever was causing it seems to have "healed" because it hasn't happened at all today.
much appreciated
Any idea where to get the stock recovery?
Just for completeness.... Both in update.zip form (unsigned):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/JB-stock-recovery.zip
-- Recovery
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/JB-stock-system.zip
-- System & Kernel
(This is not the same form as kilr00y posted in the OP... His is a version that's been converted. This is the full filesystem, extracted to the block device. This shows up as official on the downloader. It is not pre-rooted. ... This also differs from an ODIN flashable version of this. Heimdall might be able to flash the resultant image, but this is meant to be flashed through recovery)
I've got a Nexus 5 on Lollipop that's completely stock except for running franco kernel. Haven't touched it for awhile. If I check and there are any OTA updates available, will they install successfully?
No, you must have stock kernel, stock recovery, and unroot
micens said:
No, you must have stock kernel, stock recovery, and unroot
Click to expand...
Click to collapse
Thanks.
Is there a way to manually flash the OTA, or to install it one way or another, without having to revert to stock kernel and unroot and then re-root and re-install franco again?
Edit flash-all file and remove "-w".
Save the file and flash it from fastboot
.psd said:
Is there a way to manually flash the OTA, or to install it one way or another, without having to revert to stock kernel and unroot and then re-root and re-install franco again?
Click to expand...
Click to collapse
As of Lollipop, the OTA method has changed and instead compares the checksum/hash of the entire /system partition, as well as the boot and recovery partitions. The "old" pre-Lollipop method was to check the specific files it cares about rather than sum of the entire partition.
The best way for you to update is download the factory image, extract it then flash the boot and system images using fastboot while your device is booted into the bootloader. You may also want to flash the new bootloader and/or radio. Don't flash the userdata image as it will wipe your /data partition (which the internal storage also resides in), unless that is something you want.
After that, boot into your custom recovery and simply flash the latest SuperSU and if you want to, a Lollipop version of the kernel you want. Files required by SuperSU/root access reside in the /system partition, which prevents an OTA update, and is overwritten when flashing a factory system image. A KitKat kernel won't boot on Lollipop, and a custom kernel also prevents OTA.
OTAs are really only for those who have absolutely no software modifications (and are not informed enough to be able to flash manually) and is honestly the worst way of updating.
In an attempt to stop anyone else from making a "pls halp me" thread I decided to make one myself.
Before I go further let me reiterate the importance of regular backups. Before you do anything, make a full backup of your device in a usable state^. This serves as somewhere you can revert to if you accidentally tap something that screws everything up.
^ - If you're trying to recover from what appears to be a softbrick you should start by flashing and/or booting into recovery or fastboot at least.
Being overly excited about finally getting Lollipop (I don't check for updates often) I immediately went and installed the first update available OTA, forgetting that I had for some reason refused to update my E8 since unboxing it. I've since successfully updated from 1.09 to 2.33 (Kit Kat 4.4.2 to Lollipop 5.0) and installed the Xposed Framework, here's some issues I ran into and what I did to solve them.
PROBLEM: Update takes you to your custom recovery mode without doing anything else.
Having already rooted and installing TWRP the OTA update failed, only taking me to TWRP's recovery screen instead of performing the update.
SOLUTION: Flash the stock recovery.img extracted from the downloaded .zip update in the Downloads folder on the Internal Storage
You can probably find the OTA/RUU update .zip you need from this thread or let your E8 check and download the update .zip which you can then find in the Download folder on the Internal Storage. Transfer it to your PC and extract recovery.img from 'firmware.zip' in the update .zip file. Using fastboot, flash the extracted stock recovery image and reboot. You can now restart the update which will properly complete. Once your phone has booted back up into Lollipop and completed the update you should flash back your custom recovery of choice using fastboot.
PROBLEM: ROOT LOST AFTER UPDATE
This shouldn't be a surprise. OTA updates will unroot your device.
SOLUTION: Install SuperSU in recovery, NOT Play Store.
Download the latest SuperSU installable .zip and copy it to your phone. Boot into recovery and install.
My E8 is a single-sim M8sX but I believe these steps should work with any other variant.
Hello,
I have the Xt1562 Indian version running 5.1.1 - which I have rooted and also have TWRP as recovery.
The OTA upgrade gets downloaded but fails. I then reverted to stock recovery but still the OTA upgrade fails.
How can I upgrade to Marshmallow on this without losing my data or apps or contacts?
Thanks,
Padam
Ota fails since you're rooted. You can try TWRP flashable MM rom and dirty flash it without wiping /data
Ota is possible only if you are in stock firmware and stock recovery. Fast boot flash stock firmware and get ota or directly flash updated firmware. Githup has all stock firmware files.
Never use stock update via TWRP , you may brick your device.
During giving fast boot commands , skip fast boot erase user data will not wipe data , but while doing this I have some FC s. Otherwise backup all your files , apps data and flash firmware.
Hi there !
I have U11 2.31.400 version
-Bootloader Unlocked
-TWRP installed
- Root with Masgik
Now i want get OTA update
-First, NO RUU, i tried Restore NANDoid backup and Flash stock recovery (same version)
(https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=1564536856)
-> Not work
-I tried flash stock Firmware ( got 35_RU_Partition_not_support firmware error)
Anyone can tell me how to got OTA with out RUU??
Hi there
I think we're in the same situation.
I also unlocked my phone, installed TWRP and Magisk on stock system and did a NANDroid Backup before doing so.
In order to get the OTA I restored stock recovery (which i had to extract from OTA, since i forgot to back it up) and started OTA.
--> Red Triangle!
Even after restoring stock NANDroid the OTA wouldn't install.
My mistake i think was that i didn't kept the stock system read only when i did the backup in twrp and swiped to allow modifications.
According to some threads here, even mounting the system r/w would break OTA functionality.
So since i also have no RUU for my device, i don't have the chance either to go back to stock. Maybe you did that mistake too.
The only way i can think of now, is to go temporary S-OFF, change CID and MID (to 401 international for example), flash Firmware and run the RUU for it.
But i'm not sure it'll still work after flashing the firmware.
Can anyone maybe confirm this way would work?
Thanks
Edit: Hi, in case you're still having this problem, here's a solution:
Reverting to stock