hey everyone,
i keep updating almost every week when a new FXP version is released by copying the update.zip to the sd-card, reboot to recovery mode and apply the zip. this is a neat and simple process, as i dont have to reinstall/restore apps and userdata.
now my question is, when is it recommended to (re)apply the boot.img via fastboot, that is also in every FXP package. i did the the first time after i unlocked my play, but never since then. if i understood it correctly, the boot.img contains the kernel. so how often is the boot.img updated and when is it strongly recommended to reapply it? do i need to reinstallt apps/user date everytime i get a new boom.img?
thx!
Boot.img is the kernel
You need to flash it before every update it doesnt wipe your data
Flash it with: fastboot flash boot boot.img (put kernel in same folder as fastboot)
Related
Hi guys, first time poster here, hope i've got the right sub-forum.
So i've ran into some issues whilst attempting to flash the maXimus v2.2 custom rom to my HOX. Here's what i've done so far:
Unlocked bootloader via HTCdev
Installed Clockwork Mod + SuperSU
Created a Backup using Nandorid, as well as a Titanium apps backup.
I then attempted to flash to maXimus v2.2 by doing the following:
Copy ROM zip file onto HOX
Boot into Clockwork Mod Recovery
wipe data factory reset
wipe dalvik cash
Install zip from SD card
All seemed to go okay, but i'm now stuck in a boot loop. I think the problem is that I didn't copy boot.img to my phone before the flashing process, as I was over-reliant on the tut I was using and it didn't mention this.
to rectify the situation, i've tried rebooting into bootloader and sending the fastboot erase cache and fastboot reboot-bootloader commands, but still stuck in the bootloop.
My question is two part - firstly, how do I escape this situation? Secondly, when I go to reflash my HOX, where do I get the boot.img file from?
Thanks in advance, i've tried to be as detailed as possible but this is my first time flashing a custom ROM so if I missed anything out please let me know!
loz_the_guru said:
Hi guys, first time poster here, hope i've got the right sub-forum.
So i've ran into some issues whilst attempting to flash the maXimus v2.2 custom rom to my HOX. Here's what i've done so far:
Unlocked bootloader via HTCdev
Installed Clockwork Mod + SuperSU
Created a Backup using Nandorid, as well as a Titanium apps backup.
I then attempted to flash to maXimus v2.2 by doing the following:
Copy ROM zip file onto HOX
Boot into Clockwork Mod Recovery
wipe data factory reset
wipe dalvik cash
Install zip from SD card
All seemed to go okay, but i'm now stuck in a boot loop. I think the problem is that I didn't copy boot.img to my phone before the flashing process, as I was over-reliant on the tut I was using and it didn't mention this.
to rectify the situation, i've tried rebooting into bootloader and sending the fastboot erase cache and fastboot reboot-bootloader commands, but still stuck in the bootloop.
My question is two part - firstly, how do I escape this situation? Secondly, when I go to reflash my HOX, where do I get the boot.img file from?
Thanks in advance, i've tried to be as detailed as possible but this is my first time flashing a custom ROM so if I missed anything out please let me know!
Click to expand...
Click to collapse
Enter to HBOOT in the Bootloader
Unzip the Android_Fastboot KIT V2.2.zip and run the Install Boot.img.bat after you get OK, Reboot your HOX and it will not be in bootloop
Hero! All sorted now, many thanks!
Quick question - do I have to run install boot.img.bat every time I flash, or is my phone now good to just go via install Zip from SD card each time?
flash everytime until we are s-off
Hi, (not sure if I'm in the right section of the forum, sorry if I'm not)I'm new to this forum and rooting. I have currently installed CM 10.1.2 on my HTC One X.
Everytime I try to install a new ROM it gets stuck on the boot animation after installation is done.
I follow the steps like flash boot.img, wipe caches, flash rom.zip...
Am I doing something wrong?
Thanks in advance
Well, let's see...
First off, you go into recovery and wipe data/factory reset as well as dalvik cache.
Now you install the rom zip from recovery.
Now boot into bootloder > fastboot
Now find the boot.img that was/is INSIDE the rom zip that you are trying to install.
Flash it using fastboot flash boot boot.img
Reboot and it should boot fine, if not go into recovery and once more wipe everything, and flash the boot.img again.
Again, just to make sure,
You extract the boot.img from the ZIP that contains the rom you want to install, and put it inside the folder with your adb and fastboot.
I just flashed ota 35 from baidu site and it changes partition layout some how on my qhd 9076 and installs colors stock recovery, which wont allow any zip, not including oppo updater script (which arent present in our normal zip´s (gapps/super su etc.) but worse it wont allow flashing twrp through fastboot any more... it says flashed ok but still only stock recovery present
And there´s no gapps in update zip from oppo, so it levees you locked with stock recovery, no gapps, no super su binaries!!!
This suks big time, dunno what oppo is thinking/making with this sort of update
was lucky i had x9006x9076coloros_2.0.0i_full-.zip on my sd? solved it and it allowed me to flash twrp through fastboot again and restore backup.
**edit: what....? never had to use that command before, but thanks a lot Entropy512 **
So this means, every time you update ota from baidu now, you have to unlock bootloader, first, then fastboot twrp, then install gapps + super su, phyy :silly:
spoonymoon said:
I just flashed ota 35 from baidu site and it changes partition layout some how on my qhd 9076 and installs colors stock recovery, which wont allow any zip, not including oppo updater script (which arent present in our normal zip´s (gapps/super su etc.) but worse it wont allow flashing twrp through fastboot any more... it says flashed ok but still only stock recovery present
And there´s no gapps in update zip from oppo, so it levees you locked with stock recovery, no gapps, no super su binaries!!!
This suks big time, dunno what oppo is thinking/making with this sort of update
was lucky i had x9006x9076coloros_2.0.0i_full-1.zip on my sd? solved it and it allowed me to flash twrp through fastboot again and restore backup.
Click to expand...
Click to collapse
fastboot oem unlock
Google mandated a move to Nexus-style (locked by default but user-unlockable) bootloader locking with 4.4
Entropy512 said:
fastboot oem unlock
Google mandated a move to Nexus-style (locked by default but user-unlockable) bootloader locking with 4.4
Click to expand...
Click to collapse
Oem unlock don't make any difference, still locked, wont flash twrp, even it claims both oem unlock and flashing twrp.img went ok....but still stock recovery!?
They must have made some partition changes in 35, because when flashing through twrp, it gives two errors can't wipe data , but it don't give any flashing fail error, then when booting up it fc setup and won't continue , then booting into recovery again it's stock! ! Then flashing 35 through stock recovery, there's no errors and system boots up!
As said don't flash 35 you'll regret it
Think 34 is also similar in what you described.
To Entropy512......
What do you think will happen if we delete the new ´recovery dir (just including install_recovery.sh file) completly and replaced boot image from older ota version´s ? eks. from 33 which is not locked, i know because i flashed it and all ok and then put in 35 ota??
would it work you think? i dont have the guts to try...hehe
thx in advance
Try this. Download tantrums recovery flasher, unpack the zip on your computer, then in the "rec" folder go to "oppo" and extract the one other than "stock"
Now copy the modded recovery into the folder which contains fastboot.exe
And then "fastboot boot recovery.img"
the modded recovery will boot and then via that recovery, flash the tantrums recovery flasher. Aroma installer will start, then select twrp and flash what ever you like!
Hi folks,
can i go straight to this? my tab is rooted. IF i was to unroot then download the full rom from google, and flash the system, recovery and boot, would this be ok, what i mean is, it doesnt have to be iterative to the latest version does it?
What I did was the flash the bootloader 4.05 and Scrosler's Stock Rooted Busybox 5.1.1 ROM http://forum.xda-developers.com/nexus-7-2013/development/rom-stock-rooted-5-1-1-lmy47v-root-t3098137. Follow his instructions or if you want to dirty flash, use TWRP to first wipe the 2 caches, flash the bootloader and then ROM, wipe caches again and boot to system. The first boot is very long.
You need to flash the bootloader as well since it got updated.
No need to unroot, you're flashing the system image..
Bootloader boot and system will do it, I'd recommend a clean install though. Flash all partitions or run flashall file letting it wipe the tablet.
ok thanks folks. didnt realise the bootloader had to be done too. I guess this also applies to my N5 when im updating that too?
SO .... if i was making instructions to flash my devices for future updates, would the following suffice?
dont unroot
dont remove TWRP
fastboot flash bootloader bootloader-hammerhead-hxxxxxxxx.img
fastboot flash radio radio-hammerhead-xxxxxxxxxxxxxxxxxxx.img (do i need to even do this?)
fastboot flash boot boot.img
fastboot flash system system.img
boot to recovery and wipe dalvik cache
scrosler's ROM is standard 5.1.1. The beauty of it is that your phone will be rooted and busybox installed (with a trim). Just use TWRP to wipe whatever partitons you want (the 2 caches and also data if you want a clean install), then add bootloader and then ROM zips to the queue. Install them, then wipe the 2 caches again and boot to system. You might have to install SuperSu again from Play Store but you will be rooted.
It couldn't be simpler
Is it safe to take the ota with magisk or do I have to unroot and flash stock recovery?
I am on stock room and custom kernel atm
EnIXmA said:
Is it safe to take the ota with magisk or do I have to unroot and flash stock recovery?
I am on stock room and custom kernel atm
Click to expand...
Click to collapse
Hello, as Magisk changes boot image it will fail... The safetest method I think will be to download factory image, unzip, remove -w from flash-all.bat and then execute it... Then root again...
What did you do for the previous months updates?
You need to download the system image for the April update. You will need to extract the zip. Once you so that. Open up the flash. Bat file and erase the -w from the text then re-save it. Make sure you have twrp and your kernel stored locally on your phone. Reboot bootloader and run the .bat file. This process will not wipe your phone. After it's installed it will reboot your phone. Reboot bootloader and flash twrp.img through ADB. From there flash twrp.zip and your choice of kernel. Let your device reboot, then reboot into twrp and flash Magisk.
This should work as long as this update doesn't break twrp like February did. As always, you do this at your own risk.
MacTheRipperr said:
What did you do for the previous months updates?
You need to download the system image for the April update. You will need to extract the zip. Once you so that. Open up the flash. Bat file and erase the -w from the text then re-save it. Make sure you have twrp and your kernel stored locally on your phone. Reboot bootloader and run the .bat file. This process will not wipe your phone. After it's installed it will reboot your phone. Reboot bootloader and flash twrp.img through ADB. From there flash twrp.zip and your choice of kernel. Let your device reboot, then reboot into twrp and flash Magisk.
This should work as long as this update doesn't break twrp like February did. As always, you do this at your own risk.
Click to expand...
Click to collapse
Thanks. I bought the phone 2 weeks ago with the March security patch