Hi!
I am at the moment using latest build of FlashKernel but thinking about first reverting back to stock kernel, so I instead can flash latest ElementalX Kernel for 8.1.0 (March update.)
Now to the question..
How is the exact procedure and way to do this actually? I've tried google it but can't really find anything that tells me how-to do it. Anyone around here that can shed & share some light on this?
xFirefly93 said:
Hi!
I am at the moment using latest build of FlashKernel but thinking about first reverting back to stock kernel, so I instead can flash latest ElementalX Kernel for 8.1.0 (March update.)
Now to the question..
How is the exact procedure and way to do this actually? I've tried google it but can't really find anything that tells me how-to do it. Anyone around here that can shed & share some light on this?
Click to expand...
Click to collapse
Flash the stock boot.img to the "boot" slot. That is to say:
Download the full image or ota from Google. Extract it and locate the boot.img. You may have to extract a second zipped file to find it , I forget. Fastboot flash boot path\to\boot.img where "path\to\" is the path to where the extracted boot.img file is located on the computer. Be aware that recovery lies within the boot.img so if you had twrp installed and still want it then it'll have to be reflashed with the two-step process (boot the .img and flash the .zip)
Related
All the forums that I could find are talking about updating from a stock rom to the ODEX rom. I am wondering if i need to update my bootloader if i am upgrading to the asus rom.
I have TWRP 2.4.1.0 and i am on the ASUS stock ics update 30. I have downloaded the ASUS stock firmware V10.6.1.14.8 which stores the 4.2.1 rom. If i do a wipe on everything from TWRP then mount and install the rom from an external sd card, will I brick my device without doing the same bootloader update that is done for the ODEX rom. Correct me if I am wrong but I believe that the firmware package comes with the bootloader needed for the rom.
data90 said:
All the forums that I could find are talking about updating from a stock rom to the ODEX rom. I am wondering if i need to update my bootloader if i am upgrading to the asus rom.
I have TWRP 2.4.1.0 and i am on the ASUS stock ics update 26. I have downloaded the ASUS stock firmware V10.6.1.14.8 which stores the 4.2.1 rom. If i do a wipe on everything from TWRP then mount and install the rom from an external sd card, will I brick my device without doing the same bootloader update that is done for the ODEX rom. Correct me if I am wrong but I believe that the firmware package comes with the bootloader needed for the rom.
Click to expand...
Click to collapse
Before you update to the latest firmware, I would recommend that you use NVFlash as a backup for recovering if you brick your device. You can find the information here: http://forum.xda-developers.com/showthread.php?t=1901479
If you update the latest Asus firmware, V10.6.1.14.8, it will also update your bootloader with the latest version. Good luck.
Thank you for the idea of NVFlash but unfortunately I have one too many updates to utilize that wonderful software. If I was able to use it, then I would have dove in head first and then informed the populace of my findings. So lets see if I give my self a ~$450 paper weight.
data90 said:
All the forums that I could find are talking about updating from a stock rom to the ODEX rom. I am wondering if i need to update my bootloader if i am upgrading to the asus rom.
I have TWRP 2.4.1.0 and i am on the ASUS stock ics update 30. I have downloaded the ASUS stock firmware V10.6.1.14.8 which stores the 4.2.1 rom. If i do a wipe on everything from TWRP then mount and install the rom from an external sd card, will I brick my device without doing the same bootloader update that is done for the ODEX rom. Correct me if I am wrong but I believe that the firmware package comes with the bootloader needed for the rom.
Click to expand...
Click to collapse
You are correct. The Asus firmware has the correct bootloader, recovery and rom. If you flash it from TWRP it will install the stock recovery. So you loose TWRP and root too. You're basically back to a stock system, except you're unlocked.
berndblb said:
You are correct. The Asus firmware has the correct bootloader, recovery and rom. If you flash it from TWRP it will install the stock recovery. So you loose TWRP and root too. You're basically back to a stock system, except you're unlocked.
Click to expand...
Click to collapse
When I went to flash the firmware from twrp it kept failing. (and i accidentally wiped the os from the device) So I flashed ics back onto it and then tried upgrading again from the stock recovery, but i kept getting the dead android. I also got the device to recognize that there was an update zip on the device so that it would send it into an updating state by itself, but that also produced the android with the caution sign.
Any ideas?
data90 said:
When I went to flash the firmware from twrp it kept failing. (and i accidentally wiped the os from the device) So I flashed ics back onto it and then tried upgrading again from the stock recovery, but i kept getting the dead android. I also got the device to recognize that there was an update zip on the device so that it would send it into an updating state by itself, but that also produced the android with the caution sign.
Any ideas?
Click to expand...
Click to collapse
There are a lot things that could be wrong. However, most likely are: 1. A wrong signed firmware, for example you have a US bootloader but you try to update with WW firmware. 2. You have a currupted zip file. 3. You forgot to unzip it once because there is a zip inside the other zip file. If non of the above are applied to you, you could try this.
1. Copy a second zip file to your Root directory on your Internal SD
2. Reboot your device
3. After rebooted, you should see the notification on your lower right corner with the new update
4. Just click on the updated notification and follow the instructions as it walk you through the updated precesses.
Please report back. If it does not work, you need to rename your second zip file and use the stock recovery to update the firmware. There is a link some where on this website will walk you through the processes. Good luck.
LetMeKnow said:
There are a lot things that could be wrong. However, most likely are: 1. A wrong signed firmware, for example you have a US bootloader but you try to update with WW firmware. 2. You have a currupted zip file. 3. You forgot to unzip it once because there is a zip inside the other zip file. If non of the above are applied to you, you could try this.
1. Copy a second zip file to your Root directory on your Internal SD
2. Reboot your device
3. After rebooted, you should see the notification on your lower right corner with the new update
4. Just click on the updated notification and follow the instructions as it walk you through the updated precesses.
Please report back. If it does not work, you need to rename your second zip file and use the stock recovery to update the firmware. There is a link some where on this website will walk you through the processes. Good luck.
Click to expand...
Click to collapse
I second LetMeKnow.
Download the firmware again unzip it once and put it into the root of your microSD card. The card should be formatted as FAT32.
If the recovery does not automatically recognize it, rename the file to EP201_768_SDUPDATE.zip.
As far as I can see you are on the .30 ICS so nvflash won't work for you.
I do realize I need to get both the stock recovery and kernel back in order to install a OTA update and that's easy but in my case, I'd have to disable Xposed (or it's modules), revert back stock navbar with Softkeyz and even get stock GPU binaries and uninstall/disable ViPER audio fx?
Excuse my ignorance but I am a first timer on this position - also if this could be asked on a thread, I'd ask for a moderator to move it (I ran a search but would like a personal answer on this one).
Bump, can anyone give me a solid answer?
Guys?.. (spam is unintentional, it's a simple question)
If you deleted apps or did mods to your build.props download your firmware from http://sbf.droid-developers.org/phone.php?device=14, you can find your firmware in "Settings" "About" "System Version" once you see it find the same version in the link i gave you and download it. Extract it to your folder that has fastboot and mfastboot and just flash the system.img, NOTE: to this while in bootloader mode. Example: mfastboot flash system system.img If you have other mods such as modifying systemui then find someone to upload stock ui so you can replace. If you don't know how to revert back to stock kernel in the same zip firmware you downloaded move the boot.img into your fastboot and mfastboot folder and open command window here and type in fastboot flash boot boot.img. This will give you stock kernel as well.
serophia said:
If you deleted apps or did mods to your build.props download your firmware from http://sbf.droid-developers.org/phone.php?device=14, you can find your firmware in "Settings" "About" "System Version" once you see it find the same version in the link i gave you and download it. Extract it to your folder that has fastboot and mfastboot and just flash the system.img, NOTE: to this while in bootloader mode. Example: mfastboot flash system system.img If you have other mods such as modifying systemui then find someone to upload stock ui so you can replace. If you don't know how to revert back to stock kernel in the same zip firmware you downloaded move the boot.img into your fastboot and mfastboot folder and open command window here and type in fastboot flash boot boot.img. This will give you stock kernel as well.
Click to expand...
Click to collapse
Thanks.
I see but I didn't remove or modded anything, only the stuff mentioned above. Just wondering if I'd have to flash the firmware again.
rogeriorp said:
Thanks.
I see but I didn't remove or modded anything, only the stuff mentioned above. Just wondering if I'd have to flash the firmware again.
Click to expand...
Click to collapse
Just to be safe just flash the system.img and the stock recovery and boot.img and you should be good to go. I have a moto X and all i flashed was stock recovery, system.img and disabled xposed and was able to flash my 4.4.3 ota via stock recovery.
I remember reading a post during the 11.5 update that explained this really well. I installed the new CM12S file the day it came out using TWRP, had to re-root the phone, and install FK kernel again, but I keep getting CM12S update notices 10 times a day. Isn't there a way I can just flash the stock Kernel or something so my phone will let me install CM12S using the OTA method? Then root, change the kernel, etc. and all that fun stuff again later? Any reply would be GREATLY appreciated, THANKS!
You can extract the kernel (boot.img) from the ROM zip and flash with fastboot.
Code:
fastboot flash boot boot.img
Transmitted via Bacon
Also, how can I tell what were the previous versions of Android that my phone had (STOCK)?
For example: there were several 5.1.1 versions or 5.0. versions - how do I know which one do I need?
Thanks.
The easiest way to have a routed rom would be to flash a stock rom from Google, flash twrp, and flash supersu from twrp.
audit13 said:
The easiest way to have a routed rom would be to flash a stock rom from Google, flash twrp, and flash supersu from twrp.
Click to expand...
Click to collapse
Sorry if I didn't explain myself - my phone is rooted and I have a custom ROM. What I want to do is to go back to stock ROM but keep it rooted.
Thanks.
Flash a stock rom, then just root the stock rom. There is no other way unless you flash a stock pre-rooted rom.
audit13 said:
Flash a stock rom, then just root the stock rom. There is no other way unless you flash a stock pre-rooted rom.
Click to expand...
Click to collapse
So you can't keep it rooted while flashing stock?
And how do you know which versions are for your phone (if I don't want to go back to the latest Marshmallow for example)?
You can only keep root when flashing stock if you find a prerooted stock image.
Google search for nexus factory images.
audit13 said:
You can only keep root when flashing stock if you find a prerooted stock image.
Google search for nexus factory images.
Click to expand...
Click to collapse
Yes, I know that I need to Google for factory image, but there are several images with the same release. For example, there are three 5.1.1. (LMY48B, LMY48I and LMY48M). Same with 6.0.0. and 4 X 6.0.1 version. How do you know which one is for my device?
Thanks.
Any stock image for hammerhead will work on a hammerhead device. The reason it will delete root is you will have to flash system, and unless the system image you flash is prerooted, no more root.
wangdaning said:
Any stock image for hammerhead will work on a hammerhead device. The reason it will delete root is you will have to flash system, and unless the system image you flash is prerooted, no more root.
Click to expand...
Click to collapse
Thanks!
Just trying to understand that difference between the different versions, or are these simply system updates, from XXX29K to XXX29S for example?
Changes in the android version 5.0->5.1->6.0 are fairly large system updates. Within 5.1.1 they are security patches.
If you have a rooted phone and talk about flashing, you should know this. Else you are a menace to your phone...
Root is a system modification - if you delete or reinstall the System partition, you'll lose root. But re-root is easy.
I recommend to read tutorials and get some knowledge before trying to root, flash or before asking those questions, where Senior xda-members just shake their heads.
The simple way to do what you seem to want is to back up all your important stuff (photos, etc.), install MMB29V (the latest March 1st 6.0.1 security version), install TWRP 3.0.0.0, and from TWRP flash SuperSU v2.70. It will take slightly longer than it's taken me to type this, but not much...
After that, when a new monthly security version comes out, flash system.img, boot.img & radio.img, and repeat the TWRP & SuperSU steps. No data loss.
My phone won't boot, I tried to unroot using the supersu zip then installed what I thought was the stock boot.img. I have already extracted the boot.img.lz4 from the stock firmware but I can't flash that. I changed the file name and removed the .lz4 and flashed it but now I'm stuck on "Could not do normal boot invalid kernel length".
Can someone please share their stock boot.img, please. I was running android 8.0
EDIT: wasn't able to fix the problem but flashed lineage os over stock rom.