[Q] FASTBOOT Update command - Android Software/Hacking General [Developers Only]

I was just wondering if I took an update.zip that just contained the Google Talk with video update (talk 1.3) and ran fastboot update would that foobar anything? I know I could install CWM, but I've had issues in the past with corruption and wanted to avoid flashing any recoveries.
Phone is a MyTouch4G (stock 2.3.4) with S-OFF if anyone is curious, but my question is more generic on whether fastboot update only works if the update.zip contains system updates.

Related

[Q] quick soft-brick question

Hey guys, thanks very much for helping me out in advance.
I tried to upgrade my US Wifi Xoom from 3.1 (rooted) to 3.2 via the method posted by stachre here.
I made the mistake of putting the update.zip in the xoom's memory instead of the SD card's and updated it with CW Recovery.
I have a quick question as to what I should do next to recover from softbrick. This is I do not quite understand the whole flashing business. I tried following the instructions to flash stock 3.1 here but I didn't do anything about the 3.1 bootloader that it says is required, is that simply the bootloader fix that is in this post?
Should I:
1) flash 3.1 stock image and the bootloader fix? (I'm leaning towards this)
2) can i take advantage of this and just upgrade using the stock 3.2 image? will I need to use the 3.1 bootloader fix?
3) can i flash clockwork recovery via fastboot and then redo the update.zip?
4) is it easiest to flash 3.1 stock, "fastboot oem lock" then OTA and reroot once in 3.2?
What does "fastboot oem lock" really do?
cheers!

firmware update question

I have a rooted stock Sensation. I have heard that to update to the latest firmware, I need to flash the stock recovery P58img file (or whatever it is called) and then revert back to the clockwork mod recovery. As we all know, trying to apply the firmware update with the clockwork mod recovery prevents the update from even attempting to install.
I downloaded the stock p58 file someone kindly provided me and tried the update, but it always freezes 1/3 of the way through the update and I have to pull the battery to restore it to normal.
Does anybody have an idea why this is happening? I read most of the update thread, but I didn't see the solution unless I missed it.
Listerine said:
I have a rooted stock Sensation. I have heard that to update to the latest firmware, I need to flash the stock recovery P58img file (or whatever it is called) and then revert back to the clockwork mod recovery. As we all know, trying to apply the firmware update with the clockwork mod recovery prevents the update from even attempting to install.
I downloaded the stock p58 file someone kindly provided me and tried the update, but it always freezes 1/3 of the way through the update and I have to pull the battery to restore it to normal.
Does anybody have an idea why this is happening? I read most of the update thread, but I didn't see the solution unless I missed it.
Click to expand...
Click to collapse
You haven't provided any real details.
PG58IMG.zip can be used to update a multitude of things on the phone, Recovery, Radio, Firmware.
Can I ask why you want to update the Firmware and what you expect to get out of the update ?
There is a thread on a cut down update (no HBOOT Update) from the latest RUU, is that what you're referring to ? http://forum.xda-developers.com/showthread.php?t=1385439
I have also read that installing the latest RUU (with the firmware update) changes the HBOOT which can affect how it's then used.
You need to ask for more in details
gol_n_dal said:
You haven't provided any real details.
PG58IMG.zip can be used to update a multitude of things on the phone, Recovery, Radio, Firmware.
Can I ask why you want to update the Firmware and what you expect to get out of the update ?
There is a thread on a cut down update (no HBOOT Update) from the latest RUU, is that what you're referring to ? http://forum.xda-developers.com/showthread.php?t=1385439
I have also read that installing the latest RUU (with the firmware update) changes the HBOOT which can affect how it's then used.
Click to expand...
Click to collapse
Sorry. so the pg58img I used was a stock recovery file. I had heard using that would allow me to install the update, but after flashing it during the installation of the update it failed.
I wanted to install the firmware because I had read that it improved system performance and reduced bugs.
I saw the update that you were referring to, but the thread mentioned how after updating there would be no visual changes or any indicators to let me know that the firmware had actually updated, and I didn't like that aspect of it.

[Q] Stuck at Google logo!

Hi!
I rooted my Nexus few months back from now with Fastboot recovery. I got my Android ICS update 4.0.4 last week, I tried downloading it, I downloaded it, then it said rebooting for install. But my Nexus S freezes at Google logo with my unlocked lock sign. I have tried installing it many times, but all in vein.
Please somebody help!
nixhead said:
Hi!
I rooted my Nexus few months back from now with Fastboot recovery. I got my Android ICS update 4.0.4 last week, I tried downloading it, I downloaded it, then it said rebooting for install. But my Nexus S freezes at Google logo with my unlocked lock sign. I have tried installing it many times, but all in vein.
Please somebody help!
Click to expand...
Click to collapse
If you're rooted, why dont you just use the rooted method to install the update. Someone made the update flashable. Its in the development section.
either way, pull the battery to see if you still have your recovery(volume up and power button)... if so, then restore to your latest restored point, hoping that you did make a backup
Then download the newest ICS update and just flash it the rooted way.
But if you insist on the official, unroot and then get the update via stock recovery method
good luck
Are you using the latest version of CWM?
If you've got a modified system image (including root), you should not use official upgrade packages. If you want to update the rooted system, you can use unofficial packages (in CWM). To boot a system, please start your recovery and flash a proper (4.0.4, unrooted or rooted, signed or unsigned) system image. If you erase the data partition all of your data is lost!
If you have stock recovery, then only signed images can be flashed. To be able to flash unsigned images you'll need CWM, which can be flashed through fastboot.
By the way official firmware can be downloaded from Google. Important! All of your data (including USB storage area) will be lost after the full upgrade with fastboot!

Need help updating to Lollipop? DON'T MAKE A NEW THREAD, come here!

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.

Oreo 2.31.400.6 Red triangle when boot to Recovery (how to get OTA)

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

Categories

Resources