Hi People,
I have extracted the original boot.img from the Stock Image,
unpack the boot.img using "unmkbootimg".
Then edit "fstab.shamu" and change
wait,check,formattable,forceencrypt=/dev/block/platform/msm_sdcc.1/by-name/metadata
to
"wait,check,formattable,encryptable=/dev/block/platform/msm_sdcc.1/by-name/metadata"
Then repack it using "mkbootimg" into "boot_encryptable.img" (attached zip)
7a0356f9d30055e10f91da482166204c boot_encryptable.img (md5sum)
dd09de69ebda0432e8febe33c9c1758edd0f89b253eaf8f9057490918a373715 boot_encryptable.img (sha256sum)
I have tested with my own nexus 6 and its working.
Please use it at your own risk.
I cannot guarantee anything apart from it works for me.
Probably a stupid question but can I just flash the attached file in recovery?
That is not a flashable zip.
its a boot.img.
you need to do
"fastboot flash boot boot_encryptable.img" (replace with where you put the image file)
Is this boot permissible? Has anyone tried flashing SuperSU on top of it?
Thanks.
I have a question related to similar stuff:
http://stackoverflow.com/questions/32975426/android-m-custom-boot-image-for-nexus-6
I thought .img can now be flashed in the newer twrp by using the correct setting in twrp recovery by tapping the area where it says zip
Sent from my Nexus 6 using Xparent Blue Tapatalk 2
Related
Hello, i am a newbie and i want to flash a ROM for my EVO 3D, i have hboot 1.50 with S-ON unlocked Bootloaders and Rooted. So, i will flash a ROM for my firmware and confirmed it works and no need to flash Kernel, but when i go to FLASH GUI app it only shows Kernel Image and Recovery Image... I want to flash a Full ROM, which of the options do i need to choose? Thanks.
You cannot flash roms through that. You need a recovery such as twrp
Sent from my PG86100 using xda premium
patrao_n said:
You cannot flash roms through that. You need a recovery such as twrp
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
I have recovery.img in root of my sdcard which i used for install su-2.3.6.3.zip for root and unlock bootloaders with htcdev.com
luis4ever said:
Hello, i am a newbie and i want to flash a ROM for my EVO 3D, i have hboot 1.50 with S-ON unlocked Bootloaders and Rooted. So, i will flash a ROM for my firmware and confirmed it works and no need to flash Kernel, but when i go to FLASH GUI app it only shows Kernel Image and Recovery Image... I want to flash a Full ROM, which of the options do i need to choose? Thanks.
Click to expand...
Click to collapse
Taken from the guide I posted in my OP of the Flash Image GUI EVO 3D thread:
HTC Unlock - Hboot 1.5 Users Guide for ROMs with a Kernel (boot.img file):
1) Unlock using HTC method for Hboot 1.5 users
2) Load this application, Flash Image GUI, onto the device, either through the Market or the link provided in this OP.
3) Download ROM .zip file to the sdcard on the device.
4) Open up Flash Image GUI, select Browse and select the ROM .zip file, downloaded to /sdcard in the previous step.
5) Flash Image GUI will provide a warning, reminding that the ROM .zip file will *need* to be flashed in the custom recovery afterward.
6) Flash Image GUI will index the full ROM .zip file searching for the kernel and kernel modules. Once located, the Flash Image button should be enabled.
7) Select the Flash Image button and Flash Image GUI will load the kernel modules and kernel from inside the ROM zip file.
8) Select reboot recovery.
9) Inside the custom recovery, load/flash the ROM zip file.
10) Reboot to normal Android mode and all should work including Wifi!
Click to expand...
Click to collapse
Edit: 2nd question posted same time I replied to 1st question
luis4ever said:
I have recovery.img in root of my sdcard which i used for install su-2.3.6.3.zip for root and unlock bootloaders with htcdev.com
Click to expand...
Click to collapse
If you boot into the recovery, use the same method as used for the su-2.3.6.3.zip for the ROM .zip file and it will load.
The confusion occurs if the ROM contains a kernel. If so, Flash Image GUI can be used with the guide I posted above.
Alternative methods involve using fastboot to load the recovery, such as: fastboot boot c:\recovery.img
If that doesn't answer your question, feel free to post back! Thanks for the support!
This is what happens:
1.- Go to open flash GUI and starts.
2.- now kernel is preselected and chache and dalvik too.
3.- i press browse button select meanromv2.17.651.5.zip
4.- it says is a too large file for recovery or kernel image.
5.- it asks if it is a valid ROM zip file and it can locate kernel modules etc.
6.- i press yes and it says extracting zip file: meanrom.zip locating for kernel modules, peleas be patient, etc.
7.- extracted zip file in Application data.
8.- kernel continues preselected and cache too.
9.- what is the next? Press flash? And then? Reboot lnto recovery and navigate to zip file and press power button to install? Wipe data?
PD: As far as i know the kernel from the Stock and this ROM is the same. Thanks.
luis4ever said:
This is what happens:
1.- Go to open flash GUI and starts.
2.- now kernel is preselected and chache and dalvik too.
3.- i press browse button select meanromv2.17.651.5.zip
4.- it says is a too large file for recovery or kernel image.
5.- it asks if it is a valid ROM zip file and it can locate kernel modules etc.
6.- i press yes and it says extracting zip file: meanrom.zip locating for kernel modules, peleas be patient, etc.
7.- extracted zip file in Application data.
8.- kernel continues preselected and cache too.
9.- what is the next? Press flash? And then? Reboot lnto recovery and navigate to zip file and press power button to install? Wipe data?
PD: As far as i know the kernel from the Stock and this ROM is the same. Thanks.
Click to expand...
Click to collapse
Steps 7 and 8 are where more detail is needed.
Although, all this confusion might be avoided by answering one question: Does this ROM contain a kernel? If not, you can skip using Flash Image GUI and directly load the ROM from the custom recovery, since you mentioned it is compatible with stock kernel you're currently using.
If this ROM does contain a kernel then answer to all questions in number 9 should be Yes. You'll know more about the kernel included in the ROM as Flash Image GUI adds three lines of text above the Flash button detailing where the kernel was located inside the ROM .zip file and what type of kernel setup the ROM is using.
Hope that helps!
joeykrim said:
Steps 7 and 8 are were more detail is needed.
Although, all this confusion might be avoided by answering one question: Does this ROM contain a kernel? If not, you can skip using Flash Image GUI and directly load the ROM from the custom recovery, since you mentioned it is compatible with stock kernel you're currently using.
If this ROM does contain a kernel then answer to all questions in number 9 should be Yes. You'll know more about the kernel included in the ROM as Flash Image GUI adds three lines of text above the Flash button detailing where the kernel was located inside the ROM .zip file and what type of kernel setup the ROM is using.
Hope that helps!
Click to expand...
Click to collapse
If this guy tries and gives you advice about flash gui don't listen to him...He doesn't know what he's talking about.
gilbydakid said:
If this guy tries and gives you advice about flash gui don't listen to him...He doesn't know what he's talking about.
Click to expand...
Click to collapse
WTF dude? R u serious? Hope not. Joeykrim knows what he's talking about. Period.
Now, for the OP, I have a guide/flashing notes in my signature that should help clear up your Hboot 1.50 flashing issues. Also have detailed flashing "scenarios" that include using Jk's FlashImage app.
Sent from my PG86100 using Tapatalk
mpgrimm2 said:
WTF dude? R u serious? Hope not. Joeykrim knows what he's talking about. Period.
Now, for the OP, I have a guide/flashing notes in my signature that should help clear up your Hboot 1.50 flashing issues. Also have detailed flashing "scenarios" that include using Jk's FlashImage app.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Thanks, i falshed the ROM with no problems.
Deleted, starting to sound like a xda prick.
Yes it was a joke.
S3nt from my 3D wond3rland
Hi there guys,
I am having an issue and was wondering if someone could point me in the right direction, maybe to a tutorial or some decent info on this.
Anyways, I have been tinkering around and teaching myself about building kernels, and roms and just a short while ago finished compiling my first kernel. I have the zImage, and i have tried adding the zImage to Koush's AnyKernel updater.zip but when i try and flash it says failed but is not displaying any errors (Using TWRP recovery) Or I am doing this wrong and need to unpack and repack boot.img with the new zImage?
Any help is greatly appreciated, Thanks!:good:
(edit) I am building on Fedora 17
You answered your own question.
Unpack the boty.img and repack with new zImage
So I was in the right ball park at least.
Sent from my SGH-T989 using Tapatalk 2
Will fastboot boot boot.img work on the galaxy note for testing a kernel? In case I have a borked kernel I want to take precautions so I don't brick my device.
Sent from my SAMSUNG-SGH-T879 using Tapatalk 2
No to fastboot.
With a broken kernel you should still be able to button combo into recovery and just flash a working kernel .zip
Or..at the very least be able to boot download mode and use Odin to flash the kernel.
I have gotten the boot.IMG all packed back up and when I flash it, my phone just hangs up at the white Samsung logo screen and does not go any further. Does something in the ramdisk have to be edited?
Tapa-a-Talkit it... Galaxy Note...4.2.1
In the process of pushing AOSP I have compiled myself, I seem to have removed the previous image I have TWRP, but no backed up image. I do have a system.img that I built myself on my laptop, and a zipped version of it. What are my options? Is there some way I can use Odion to push an image to the phone? Do I need to make a different version of my image?
sansari123 said:
In the process of pushing AOSP I have compiled myself, I seem to have removed the previous image I have TWRP, but no backed up image. I do have a system.img that I built myself on my laptop, and a zipped version of it. What are my options? Is there some way I can use Odion to push an image to the phone? Do I need to make a different version of my image?
Click to expand...
Click to collapse
You use twrp to flash the zip file. ... You use Odin to return to stock flash recovery radios etc ... ROMs are flashed in recovery. .... Read and follow directions in cm thread etc flash gapps
Sent from my SM-N900P using Xparent BlueTapatalk 2
Based on our official TWRP with some fixes and features
Changelog: 7-13
Add USB-OTG support
Brightness setting persists through reboots
EFS Backup and restore
Double tap to wake
Code:
Install:
In fastboot mode
fastboot flash recovery recovery.img
Download
Recovery flashable version here
Credits: Dees_Troy
dr87 said:
Based on our official TWRP with some fixes and features
Changelog: 7-13
Add USB-OTG support
Brightness setting persists through reboots
EFS Backup and restore
Double tap to wake
Mount and unmount issues *may* be fixed (I haven't been able to reproduce them)
Code:
Install:
In fastboot mode
fastboot flash recovery recovery.img
Download
Credits: Dees_Troy
Click to expand...
Click to collapse
Awesome job bro! Running like a champ!!
Sent from my One using XDA Premium 4 mobile app
Thanks a lot!
Now I can run Mahdi without problems!
thanks for this- but it's still not working- will i need to reflash madhi? i just fastbooted the recovery across and it boots into the recovery no worries and recognises all partitions but rom won't boot...
***edit*** it just booted up, about 5th attempt.. no boot animation though...ignore me...
Flashed recovery.img, bootet into recovery, no partitions..
Klarooo said:
Flashed recovery.img, bootet into recovery, no partitions..
Click to expand...
Click to collapse
Which rom were you running when you rebooted into recovery?
Stock, so CM11s.
mine still is not good. i treid to reboot to get it to hold the no hardware buttons. didn't reboot. tried about 10 times. eventually booted intot this new recovery and reflashed rom and booted it up. it's a bloody weird looking boot- no boot animation- made me think it was screwed again.
did you have to do anything to get it working again? Wipe entire device or just data partition?
Working good here, but I had no issues with the official build. I have an international version, 64GB OPO.
It's nice to see some additional features added, though.
Just helping out, packaged in a flashable zip for those with current CWM or TWRP recoveries, tested and working, enjoy everyone.
Flashed with the zip in the post above, worked flawlessly, was able to backup my EFS partition which is what I was looking to do. Thanks!
Chris123NT said:
Flashed with the zip in the post above, worked flawlessly, was able to backup my EFS partition which is what I was looking to do. Thanks!
Click to expand...
Click to collapse
Guys i wonder when you press efs restore is it
fastboot format modemst1 & st2
or
fastboot erase modemst1 & st2
or may be both? in that case in what order?
I flashed the one in OP, but the system does not see any partition ?
Can I flash 15th without bricking the phone
[EDIT] I tried a second time, and now it´s ok, partitions are there and backup is currently running
Any chance at adding F2FS support direct for this recovery for the ONE Plus?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Looks like the official .img version has been incremented to 2.7.1.1
More here: http://techerrata.com/browse/twrp2/bacon
A flashable zip for v2.7.1.1 would be nice.
Changelog? Hopefully they fixed those Partitions issues
2.7.1.1-Bacon Recovery Flashable zip
Mikey said:
2.7.1.1-Bacon Recovery Flashable zip
Click to expand...
Click to collapse
Question - now I ask this to see how you may do this and possibly help others from waiting for a zip. Now are you simply renaming the image file from TWRP to recovery.img and placing it inside an already created zip file for flashing. A zip file that of course was created for an earlier version of TWRP lets say
playya said:
Question - now I ask this to see how you may do this and possibly help others from waiting for a zip. Now are you simply renaming the image file from TWRP to recovery.img and placing it inside an already created zip file for flashing. A zip file that of course was created for an earlier version of TWRP lets say
Click to expand...
Click to collapse
Correct, easy huh
Delete the twrp.img......drag and drop the new img into the zip......dont uncompress the zip and compress it again.
I was rooted using supersu. Because I wanted to pass safety net I decided to unroot, but the supersu uninstaller gave me an error. So I unrooted using a zip file, which worked. However did this not restore to original boot image, which is why I am still not passing safety net.
Does anybody know where I could find the stock boot image and can I flash it simply through twrp?
Thanks in advance!
Edit: Or does dirty flashing the stock firmware fix it, too?
I recently flashed an original Boot.img to install Magisk on my Note 4. You basically just have to open a downloaded firmware (of course the one you are using at the moment), open it with 7zip and extract the boot.img file. You can then flash that with ODIN.
TheGoD said:
I recently flashed an original Boot.img to install Magisk on my Note 4. You basically just have to open a downloaded firmware (of course the one you are using at the moment), open it with 7zip and extract the boot.img file. You can then flash that with ODIN.
Click to expand...
Click to collapse
Where would I find the original boot.image in the rom once I downloaded it?
mcfiish said:
Where would I find the original boot.image in the rom once I downloaded it?
Click to expand...
Click to collapse
Extract the AP file with 7-Zip. But you can't flash a .img file with odin. You'd have to convert it to a .tar.md5
Sent from my [device_name] using XDA-Developers Legacy app
Can I use TWRP instead of Odin without any problems?
themanoirish said:
Can I use TWRP instead of Odin without any problems?
Click to expand...
Click to collapse
I would think so. But I'll admit I've never done it with a Samsung device.
Sent from my [device_name] using XDA-Developers Legacy app
themanoirish said:
Can I use TWRP instead of Odin without any problems?
Click to expand...
Click to collapse
TWRP does have an install image option under... Well, install.
Thank you*jd1639 and jhill110 for the input. I'm not the most experienced at all this yet and I usually find myself in the deep end of the pool. I've already managed to soft brick my phone last year and just end up extra cautious since then. I just didn't want to end up wiping TWRP off my phone with a stock boot image with no way to flash it back on at the moment. Sorry I couldn't quote you two, my account is new and I can't use external links or quotes until the tenth post.