I went to my phone settings today to check for the jellybean OTA update thinking it wouldn't work since my T-Mobile Samsung Galaxy S3 is rooted & has clockwork mod.
Well it said update available, I selected it & it downloaded the update & then needed to reboot.
When the screen came back on there was the android with the spinning cube in his stomach & a progress bar below.
The progress bar only got about halfway done before the screen changed to android on his back with a red triangle in his stomach.
At the top of screen was a list with the 1st one being reboot phone. I rebooted & when phone started back up it said, "update failed, phone has been returned to original state"
What can I do short of completely un-rooting my phone to get jellybean & then re-rooting?
Waste of time. Just wait for the official jb update
Sent from my SGH-T999 using xda premium
Jaaz420 said:
I went to my phone settings today to check for the jellybean OTA update thinking it wouldn't work since my T-Mobile Samsung Galaxy S3 is rooted & has clockwork mod.
Well it said update available, I selected it & it downloaded the update & then needed to reboot.
When the screen came back on there was the android with the spinning cube in his stomach & a progress bar below.
The progress bar only got about halfway done before the screen changed to android on his back with a red triangle in his stomach.
At the top of screen was a list with the 1st one being reboot phone. I rebooted & when phone started back up it said, "update failed, phone has been returned to original state"
What can I do short of completely un-rooting my phone to get jellybean & then re-rooting?
Click to expand...
Click to collapse
That's not even the jelly bean update.
You need to start reading dude, he is right, it is not even a jb update...sheez...
Greetings,
I have a Telus SGH-i1317M that I previously rooted. Since then I was always getting the "Your device has been modified. Software updates are not available" scolding when checking for OTA. Lo & behold this morning I was offered to download 4.3 so I did. However the installation failed.
Once the download completed, I was asked to reboot to start the installation. I'm afraid the little android guy fell down at 26% and was promptly stabbed in the heart by an angry looking red exclamation mark.
Any suggestions?
Hey there all.
I was going to upgrade to the OTA Lollipop update to give it a test but something went wrong.
I'm running a Vodafone Australia model D855 (v10e if I recall).
Firstly I downloaded and started the install of the OTA update. Upon restarting, the phone would boot into TWRP instantly. No big deal. Decided to flash CloudyG3 instead of stock as I couldn't be bothered trying to fix the OTA update. So I did a full wipe, flashed the baseband and then flashed the ROM. Reboot and it's still going straight to TWRP. So I ran the fix for it that clears the FOTA and Misc folders but even that didn't fix it.
At this stage I decided to use PC Suite to try repairing the phone back to KitKat and start again. Upon running a repair the phone would start some sort of flashing even though PC Suite wasn't detecting anything. Now it won't even boot to recovery, just keeps looping the LG logo.
I've tried installing a .TOT fix (using the European v10e .TOT dated July 8th 2014 AND the Hong Kong v10b .TOT dated July 1st 2014) but that fails showing DOWNLOAD FAIL (Model is different, check phone model or DLL). I'm also using the LGD855_20140526_LGFLASHv160 DLL file.
The other thing I tried was a .kdz fix but it kept showing an error "No connection to server" and clicking ok would close it. The phone would then get stuck at 18% flashing.
Any help here would be appreciated. I'm currently at a loss as to how to fix this.
SOLVED: I tried the .kdz fix again but instead of clicking "OK" when the "No connection to server" message came up I just let it go. I checked the background window and the flash was still going through. I watched the phone and it went through all the way eventually. A few reboots later it's back to the home screen and I'm ready to properly flash a Lollipop ROM.
Hi,
I hope someone can help me. My HTC 1 (UK, Unlocked) was rooted and had TWRP. The 1.80.401 update is now out, so I did the following:
-Restored Stock System
-Restored Stock Recoverd
-Factory reset the phone
-Download the update
Now after the download, the phone reboots and the OTA is applied, but it gets to 25% then displayed a strange red exclamation mark. I can reboot, and the phone still works but the software hasnt been upgraded.
Could someone please help me? I have no idea what the issue is.
Many thanks
same issue here
Flash The 1.80 RUU
Hi, in early September I started checking the OTA update notification to MM in my recently purchased ZENFONE 2 551ML (4/64GB): NOTHING - then I tried to do it manually, I downloaded the file from the ASUS website (V4.21.40.134) and follow the instructions, once I copied the zip file in the internal memory I found the notification and: did the update started? No, the phone rebooted and after a few seconds I saw a broken green robot with the word ERROR, ok, back to Lollipop, I double checked and saw a note "Before attempting the manual update, please make sure you are updated to V2.20.40.194 or later via the System Update app." while I still have WW 2.20.40.184 - ok, so I downloaded this update (that I should have received OTA having it being released in July - but I didn't), nay no, I had to download the WW 2.20.40.196 release (as the 194 wasn't available), I tryed to do the update but I got the very same error and the same broken green robot after rebooting - and lucky again it wasn't started anything so I could go back to dear old LOLLIPOP.
Note, the phone is not ROOTED I was waiting the MM upgrade to do so.
CAN SOMEONE HELP? (I COME FROM 5 YEARS OF SAMSUNG AND HUAWEI UPDATING / ROOTING / MODDING WITHOUT ANY KIND OF PROBLEMS)
This may possibly be more than you need. But, it will work for you. https://www.asus.com/zentalk/in/thread-100891-1-1.html
Sent from my ASUS_Z00AD using Tapatalk
mikeletron said:
Hi, in early September I started checking the OTA update notification to MM in my recently purchased ZENFONE 2 551ML (4/64GB): NOTHING - then I tried to do it manually, I downloaded the file from the ASUS website (V4.21.40.134) and follow the instructions, once I copied the zip file in the internal memory I found the notification and: did the update started? No, the phone rebooted and after a few seconds I saw a broken green robot with the word ERROR, ok, back to Lollipop, I double checked and saw a note "Before attempting the manual update, please make sure you are updated to V2.20.40.194 or later via the System Update app." while I still have WW 2.20.40.184 - ok, so I downloaded this update (that I should have received OTA having it being released in July - but I didn't), nay no, I had to download the WW 2.20.40.196 release (as the 194 wasn't available), I tryed to do the update but I got the very same error and the same broken green robot after rebooting - and lucky again it wasn't started anything so I could go back to dear old LOLLIPOP.
Note, the phone is not ROOTED I was waiting the MM upgrade to do so.
CAN SOMEONE HELP? (I COME FROM 5 YEARS OF SAMSUNG AND HUAWEI UPDATING / ROOTING / MODDING WITHOUT ANY KIND OF PROBLEMS)
Click to expand...
Click to collapse
According to the ASus site, you need to be at least ver 184 to upgrade to MM. So according to the asus site you are good to go for MM.
I did upgrade to MM from 194 though. Here is the link for 194.
Since you are saying that you did not find 194, you might be looking in the wrong directory.
Here is the link for the MM update. I am sure you have the correct firmware.
Dead robot with red triangle and error message sometime happened when you were trying to go to recovery or the phone trying to go to the recovery. To go to the recovery from the dead robot.
You need to press and hold the power button, and quickly press and release the volume-up button. The phone should go to the recovery if you still have the stock recovery. Sometime you need to click that volume-up button several times while you holding the power button to go into the recovery mode.
Since you are familiar with samsung and Huawei, you could use adb reboot recovery to go the recovery mode. However, if you see the dead robot and error you have to go through the above method.
Once you were in the recovery, you can use adb sideload to install the MM firmware.
mikeletron said:
Hi, in early September I started checking the OTA update notification to MM in my recently purchased ZENFONE 2 551ML (4/64GB): NOTHING - then I tried to do it manually, I downloaded the file from the ASUS website (V4.21.40.134) and follow the instructions, once I copied the zip file in the internal memory I found the notification and: did the update started? No, the phone rebooted and after a few seconds I saw a broken green robot with the word ERROR, ok, back to Lollipop, I double checked and saw a note "Before attempting the manual update, please make sure you are updated to V2.20.40.194 or later via the System Update app." while I still have WW 2.20.40.184 - ok, so I downloaded this update (that I should have received OTA having it being released in July - but I didn't), nay no, I had to download the WW 2.20.40.196 release (as the 194 wasn't available), I tryed to do the update but I got the very same error and the same broken green robot after rebooting - and lucky again it wasn't started anything so I could go back to dear old LOLLIPOP.
Note, the phone is not ROOTED I was waiting the MM upgrade to do so.
CAN SOMEONE HELP? (I COME FROM 5 YEARS OF SAMSUNG AND HUAWEI UPDATING / ROOTING / MODDING WITHOUT ANY KIND OF PROBLEMS)
Click to expand...
Click to collapse
Just download the zip from Asus.com then rename to mofd_sdupdate.zip, put it in the root directory of internal storage, reboot your phone to recovery then it will do everything automatically. Use this method to update to lastest 5.0, then MM. No need to type adb commands