Related
dear xda members ,,,
i changed my kernel to franco kernel ,,, and now i want to go back to stock kernel 1.29.415.11 ,, but when ever i install the stock kernel the phone goes into boot loop ,, i think i need the stock kernel boot.img but i cant find it
please help ,,,
hwoarang626 said:
dear xda members ,,,
i changed my kernel to franco kernel ,,, and now i want to go back to stock kernel 1.29.415.11 ,, but when ever i install the stock kernel the phone goes into boot loop ,, i think i need the stock kernel boot.img but i cant find it
please help ,,,
Click to expand...
Click to collapse
Are you using a ROM ? If so, go to the ROM's page and use the boot.img meant for that ROM.
I'm using stock
hwoarang626 said:
I'm using stock
Click to expand...
Click to collapse
You have to find and install stock kernel modules zip file in recovery after flashing the boot image. You can use venom flasher of viper forum to revert to stock
Sent from my HTC One X using Tapatalk 2
i could not get what you told me ,,, i only need the stock kernel and boot.img for 1.29.415.11
hwoarang626 said:
i could not get what you told me ,,, i only need the stock kernel and boot.img for 1.29.415.11
Click to expand...
Click to collapse
Under android dev thread you will find all official RUUs released. Find the one matching your 415.11 code.download it.
Once downloaded, run it. When the first screen comes up, open an explorer, change dir to %tmp%, you will see two newly created directories. In one of them, find the file ROM.zip and copy it somewhere else. Now exit ruu setup. Open ROM.zip file and in it there are the IMG files you seek. However installing only boot.IMG won't work. They need their modules files to work properly. That's what I meant by flashing the modules zip in recovery.
Sent from my HTC One X using xda premium
eyosen said:
Under android dev thread you will find all official RUUs released. Find the one matching your 415.11 code.download it.
Once downloaded, run it. When the first screen comes up, open an explorer, change dir to %tmp%, you will see two newly created directories. In one of them, find the file ROM.zip and copy it somewhere else. Now exit ruu setup. Open ROM.zip file and in it there are the IMG files you seek. However installing only boot.IMG won't work. They need their modules files to work properly. That's what I meant by flashing the modules zip in recovery.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
i did what you said ,,, but i cant find the stock kernel to apply from recovery ...
hwoarang626 said:
i did what you said ,,, but i cant find the stock kernel to apply from recovery ...
Click to expand...
Click to collapse
Stock kernel is the boot.img and cannot be apply from recovery. It must be flash in fastboot mode - fastboot flash boot boot.img or use any kernel flasher. And you need to flash the stock modules too.
ckpv5 said:
Stock kernel is the boot.img and cannot be apply from recovery. It must be flash in fastboot mode - fastboot flash boot boot.img or use any kernel flasher. And you need to flash the stock modules too.
Click to expand...
Click to collapse
that is my question .. i flashed the boot.img from fast boot ,, but then i need the modules to flash from recovery right ???
where can i get the modules .. ????
and thank you so much for your help ...
hellooooooo
where are modules.zip? ?
please help
Newbie here, my Dhd is s-on, ive been flashing and custom rom and kernels to it via cwm and as always i have to flash the boot.img both rom/kernel to fully installed it. Now I want to update my kernel to the newest pacharx release for better battery. but It doesnt have the boot.img which im use to flashing.. when i extract here is what i get:
zImage
unpackbootimg
modclean.sh
mkbootimg.sh
mkbootimg
dd
how do i install this kernel?
i tried flashing the zImage but it doesnt work... please help
You do not extract anything from that zip, just flash it whole from the recovery as you would any boot.img
Sent from my Desire HD using xda app-developers app
ilans93 said:
You do not extract anything from that zip, just flash it whole from the recovery as you would any boot.img
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
i've already done that but since im on s-on i cant flash the rom via cwm, it needs to be in fastboot... i used to flash kernel with boot.img files on it,but now im just lost with this kernel i want to flash because i cant find the boot.img..
anythingbutipod said:
i've already done that but since im on s-on i cant flash the rom via cwm, it needs to be in fastboot... i used to flash kernel with boot.img files on it,but now im just lost with this kernel i want to flash because i cant find the boot.img..
Click to expand...
Click to collapse
That IS a kernel, not a ROM. Just flash it via fastboot then... You can also do it via ADB if you know how to, if not, use the search bar
ilans93 said:
That IS a kernel, not a ROM. Just flash it via fastboot then... You can also do it via ADB if you know how to, if not, use the search bar
Click to expand...
Click to collapse
I know how to.flash via fastboot and abd, my question is what file should i flash since theres no boot.img file in the kernel... Sorry newbie here
anythingbutipod said:
I know how to.flash via fastboot and abd, my question is what file should i flash since theres no boot.img file in the kernel... Sorry newbie here
Click to expand...
Click to collapse
According what I've read in other posts you can't flash a raw kernel.zip with s-on.
It has also been pointed out that a boot.IMG is Rom specific, so they most likely wouldn't be interchangeable between different roms
Sent from my HTC Desire HD using xda app-developers app
anythingbutipod said:
I know how to.flash via fastboot and abd, my question is what file should i flash since theres no boot.img file in the kernel... Sorry newbie here
Click to expand...
Click to collapse
boot.img is a kernel so don't search for a boot.img in a kernel.zip - it's the same thing only not compressed. ranger4740 is correct. You shouldn't use boot.img from one ROM and put it on another, but that's not what you asked for... As for the fact that you can't flash a kernel.zip with S-ON, I didn't know about that so I can't help you there... Sorry :/ Try asking your question in the kernel thread...
ilans93 said:
boot.img is a kernel so don't search for a boot.img in a kernel.zip - it's the same thing only not compressed. ranger4740 is correct. You shouldn't use boot.img from one ROM and put it on another, but that's not what you asked for... As for the fact that you can't flash a kernel.zip with S-ON, I didn't know about that so I can't help you there... Sorry :/ Try asking your question in the kernel thread...
Click to expand...
Click to collapse
Ok, i also tried to do some research and read some forums, seems my only way to s-off my dhd, which i will be researching next... Thanks:fingers-crossed:
My desired rom has already updated with the kernel that i wanted flash ,so my battery life is now great, although there a bug in battery charging where in it notifies late yet it charges the phone batt. (not that big if a deal for me). Also i created an aroma zip file to install all system update on my phone since the original update flashes the kernel... Thanks for the replies "learn a lot from all those researches i made" :victory:
I'm looking for the boot IMG for our tmobile s6-edge-plus I don't have the stock kernel can someone help it needs to be our firmware thank you for any help
alusher said:
I'm looking for the boot IMG for our tmobile s6-edge-plus I don't have the stock kernel can someone help it needs to be our firmware thank you for any help
Click to expand...
Click to collapse
Here... Not flashable just the zipped boot.img
Find someone who can do boot.img and recovery for xperiu L1
Custom recovery isn't required if you use Magisk to root, but custom kernel is no exception.
I tried to modify stock kernel with Magisk Manager but it failed.
Currently I don't have Linux PC so building custom kernel may be a problem.
mingkee said:
Custom recovery isn't required if you use Magisk to root, but custom kernel is no exception.
I tried to modify stock kernel with Magisk Manager but it failed.
Currently I don't have Linux PC so building custom kernel may be a problem.
Click to expand...
Click to collapse
Use Android Image Kitchen by @osm0sis to convert the boot.elf (boot.img) and fotakernel.elf (recovery.img) to standard aosp .img format then test using fastboot (Bootloader must be unlocked) Check out other "mediatek" xperia device threads also.
I tried before.
It didn't work as it cannot unpack the boot.img extracted using Flashtool sin converter
@bigrammy
Do you help a create boot.img And recovery.img
Bro please helping very very thanxxxxx
mingkee said:
I tried before.
It didn't work as it cannot unpack the boot.img extracted using Flashtool sin converter
Click to expand...
Click to collapse
HEKER510 said:
@bigrammy
Do you help a create boot.img And recovery.img
Bro please helping very very thanxxxxx
Click to expand...
Click to collapse
Upload the boot.sin and fotakernel.sin only to a NO spam file host like mega or G-drive and I will take a look when I get some time.
bigrammy said:
Upload the boot.sin and fotakernel.sin only to a NO spam file host like mega or G-drive and I will take a look when I get some time.
Click to expand...
Click to collapse
Actually, you can download full ROM using Flashtool with xperifirm, and extract boot and recovery using SIN extractor.
Currently I am at work and I will upload them to android file host later Monday
mingkee said:
Actually, you can download full ROM using Flashtool with xperifirm, and extract boot and recovery using SIN extractor.
Currently I am at work and I will upload them to android file host later Monday
Click to expand...
Click to collapse
Bro do you created boot.img and recovery.img
Very very thanxxxx bro
mingkee said:
Actually, you can download full ROM using Flashtool with xperifirm, and extract boot and recovery using SIN extractor.
Click to expand...
Click to collapse
Did you Really type that. :laugh: :laugh:
I have enough #***# on my PC without adding even more unnecessary Gig's for a device I don't even own.
As you will know there are many variants country to country single sim dual sim etc so I will need the boot from the testers variant and not just one I made guess at.
bigrammy said:
Did you Really type that. :laugh: :laugh:
I have enough #***# on my PC without adding even more unnecessary Gig's for a device I don't even own.
As you will know there are many variants country to country single sim dual sim etc so I will need the boot from the testers variant and not just one I made guess at.
Click to expand...
Click to collapse
G3313 (single SIM)
Kernel
https://androidfilehost.com/?fid=962021903579487242
MD5: af6470e932b1231cf207343a97eeee76
Recovery
https://androidfilehost.com/?fid=673791459329055867
MD5: 871ca7cc7c688b722f7fe38597ff18cb
mingkee said:
G3313 (single SIM)
Kernel
https://androidfilehost.com/?fid=962021903579487242
MD5: af6470e932b1231cf207343a97eeee76
Recovery
https://androidfilehost.com/?fid=673791459329055867
MD5: 871ca7cc7c688b722f7fe38597ff18cb
Click to expand...
Click to collapse
Here is the boot.img to test.
It has not been modified in anyway so encryption and verity are still enabled as they are in the stock .elf
IF it boots then we will move on.
Bootloader unlock is required just for clarity and anyone thinking of testing it.
I have successfully modified the kernel and mine is rooted.
The next one will be dual SIM version and it will come later.
Here is mine https://androidfilehost.com/?fid=673791459329055871
---------- Post added at 09:54 AM ---------- Previous post was at 09:40 AM ----------
bigrammy said:
Here is the boot.img to test.
It has not been modified in anyway so encryption and verity are still enabled as they are in the stock .elf
IF it boots then we will move on.
Bootloader unlock is required just for clarity and anyone thinking of testing it.
Click to expand...
Click to collapse
Use Notepad ++ to edit default.prop
ro.secure=0
ro.debuggable=1
Save and repack.
That's it.
mingkee said:
I have successfully modified the kernel and mine is rooted.
The next one will be dual SIM version and it will come later.
Click to expand...
Click to collapse
So I need not of wasted my time after all
I am well aware of how to root a kernel and do all things regarding sony and mediatek and I think you somehow got your wires crossed.
I suggested to you how to modify the kernel.elf but you said you tried and failed that's why I offered to HELP I don't even have the L1 hence the reason for not going for the full on modification of the kernel until it was fully tested.
Anyway now your underway I will leave you all to get on with it.
Good Luck :good:
Unfortunately, I am still unable to make TWRP for L1 at this time.
Moreover, it appears that modified stock image doesn't work for other L1 variations, and all I have is US version. I uploaded all three variations and see the results.
It looks like SIM cannot be read with modified image.
where is tutorial on XDA on how to twrp recovery create please link brothersss very thankx
HEKER510 said:
where is tutorial on XDA on how to twrp recovery create please link brothersss very thankx
Click to expand...
Click to collapse
I found there's a YouTube video to tell how to compile.
https://youtu.be/WkulPr_uUqI
Linux machine required.
mingkee said:
I found there's a YouTube video to tell how to compile.
https://youtu.be/WkulPr_uUqI
Linux machine required.
Click to expand...
Click to collapse
hm i windows machine (((((((((
i find this https://www.youtube.com/watch?v=799eopwzQYg
this is good tutorial How to make Cwm or Twrp recovery for any Android device
https://www.youtube.com/watch?v=rFnG7fso9HE
How backup stock recovery ?
I am install apk flashfire and open and click backup stock recovery but failed
How to stock recovery bro?
Where is it?
I recently bought a Chinese phone from a relatively unknown manufacturer, so I was unable to find any TWRP images that match the device, I was wondering if it was possible to extract the boot image directly from a GSI ROM. My end goal is to install Magisk so if there is a better way to go about this please let me know.
can you tell model and brand
Hsnmastoor said:
can you tell model and brand
Click to expand...
Click to collapse
Thank you for replying,
The phone is the Cubot X20 pro, it is running the Unofficial Pixel Experience GSI ROM.
XDA-Developer30 said:
Thank you for replying,
The phone is the Cubot X20 pro, it is running the Unofficial Pixel Experience GSI ROM.
Click to expand...
Click to collapse
your welcome its mediatek download stock rom extract it and port twrp with hovatek twrp porter
Hsnmastoor said:
your welcome its mediatek download stock rom extract it and port twrp with hovatek twrp porter
Click to expand...
Click to collapse
Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek
If you wish to root your Mediatek Android phone, we'd dropped a guide on rooting using Magisk and stock boot.img at https://www.hovatek.com/forum/thread-21427.html , no custom recovery is required. Se
forum.hovatek.com
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
LinhBT said:
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
Click to expand...
Click to collapse
Thank you for the reply, I forgot to mention that I used Hsnmastoor's method successfully.
LinhBT said:
Due to my understanding, GSI have no boot.img , it uses stock boot image ( along with all other needed partitions ). So if your purpose is to root using Magisk, just find the correct boot.img of the current stock firm on your device before GSI and patch it with Magisk!
Click to expand...
Click to collapse
I use the boot.img file from the stock rom of my device, I patch it with magisk but I always end up in bootloop
how can i root my device?
elmapq said:
I use the boot.img file from the stock rom of my device, I patch it with magisk but I always end up in bootloop
how can i root my device?
Click to expand...
Click to collapse
And your device is...???
LinhBT said:
And your device is...???
Click to expand...
Click to collapse
Tecno Spark 6 ke7
LinhBT said:
And your device is...???
Click to expand...
Click to collapse
I have a Vortex V22 MTM6761 There is no stock rom. It has unofficial GSI Pixel experience plus 13.0 running on it. I too would like to root. How can I retrieve the boot.img file from the GSI rom? Or how can I pull it from the phone via terminal and fastboot? All help is greatly appreciated! Happy Saint Patricks Day!
For devices which powered by MediaTek SOC, after flash the patched boot.img, you will need to flash patched blank vbmeta.img in order to bypass AVB with follow command :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
in which vbmeta.img is a patched blank vbmeta of your device
LinhBT said:
For devices which powered by MediaTek SOC, after flash the patched boot.img, you will need to flash patched blank vbmeta.img in order to bypass AVB with follow command :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
in which vbmeta.img is a patched blank vbmeta of your device
Click to expand...
Click to collapse
Thank you for the quick reply. I'm not sure I quite understand your message.
Flashing a vbmeta.img will give me a boot.img? I have a GSI PixelExperience 13.IMG file. The command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img was flashed along with it. It was running a different rom prior to flashing the GSI PixelExp 13.IMG
All I want to do is Root the device. I've been told over and over I need the boot.img partition to modify for Root access, but I can't get unless i'm in Root or have access to the current ROM BOOT.IMG, Correct?
Why is the BOOT.IMG or Payload.BIN missing from GSI IMG ROMS? is there another way to convert or pull from a ROM like that?
defcondoc said:
Thank you for the quick reply. I'm not sure I quite understand your message.
Flashing a vbmeta.img will give me a boot.img? I have a GSI PixelExperience 13.IMG file. The command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img was flashed along with it. It was running a different rom prior to flashing the GSI PixelExp 13.IMG
All I want to do is Root the device. I've been told over and over I need the boot.img partition to modify for Root access, but I can't get unless i'm in Root or have access to the current ROM BOOT.IMG, Correct?
Why is the BOOT.IMG or Payload.BIN missing from GSI IMG ROMS? is there another way to convert or pull from a ROM like that?
Click to expand...
Click to collapse
Yep, I think u misunderstanding me from my very first msg. What I meant back there was : GSI ROM is what called Generic System Image. Which means, it has ONLY system.img that you will need to flash into system partition of the device. Therefore, if you need the boot image in order to patch it with Magisk or else, you will need to extract the boot.img of the CURRENT ROM which is already running on your device ( and normally, it should be stock ROM ). Cuz to be in short, GSI ROM does not have any boot.img for you to seek for, my friend!
.
LinhBT said:
Yep, I think u misunderstanding me from my very first msg. What I meant back there was : GSI ROM is what called Generic System Image. Which means, it has ONLY system.img that you will need to flash into system partition of the device. Therefore, if you need the boot image in order to patch it with Magisk or else, you will need to extract the boot.img of the CURRENT ROM which is already running on your device ( and normally, it should be stock ROM ). Cuz to be in short, GSI ROM does not have any boot.img for you to seek for, my friend!
Click to expand...
Click to collapse
Thank you for the message my friend. I understand that part of it. There is no stock ROM, at least I don't think there is on it. It is a a/b system but I've tried to go back to factory reset but it does not work and goes into a boot loop. So I load the GSI pixel experience rom to get it working again.
So what you are saying is, if I do not have the stock ROM, I cannot get the BOOT.IMG, Correct? So I am pretty much out of luck to get a boot.img from a GSI? Is there another generic ROM I could use that would have a boot.IMG? Ive tried a dozen ROMS and the latest pixel experience 13 unofficial rom was the only one that worked. Maybe Im trying the wrong ROM's. I do know I need A/B versions of them, I think.
If anyone else might know a way to help get me out of this situation, I would greatly appreciate. Thank you my friends!
defcondoc said:
Thank you for the message my friend. I understand that part of it. There is no stock ROM, at least I don't think there is on it. It is a a/b system but I've tried to go back to factory reset but it does not work and goes into a boot loop. So I load the GSI pixel experience rom to get it working again.
So what you are saying is, if I do not have the stock ROM, I cannot get the BOOT.IMG, Correct? So I am pretty much out of luck to get a boot.img from a GSI? Is there another generic ROM I could use that would have a boot.IMG? Ive tried a dozen ROMS and the latest pixel experience 13 unofficial rom was the only one that worked. Maybe Im trying the wrong ROM's. I do know I need A/B versions of them, I think.
If anyone else might know a way to help get me out of this situation, I would greatly appreciate. Thank you my friends!
Click to expand...
Click to collapse
You need to understand the basic core point is : GSI is ALWAYS system image only my friend. Boot.img can be found only on FULL ROM, not GSI. And there's always stock ROM for ANY DEVICES, what you need to do is just Google with keywords : Your-Device-Full-name Stock ROM Download. Then choose the correct one which is currently running on your device and download it. Boot.img will be right there on the zip.
LinhBT said:
You need to understand the basic core point is : GSI is ALWAYS system image only my friend. Boot.img can be found only on FULL ROM, not GSI. And there's always stock ROM for ANY DEVICES, what you need to do is just Google with keywords : Your-Device-Full-name Stock ROM Download. Then choose the correct one which is currently running on your device and download it. Boot.img will be right there on the zip.
Click to expand...
Click to collapse
Thank you! I do realize the obvious. If I was able to find it, I wouldn't be asking for help. I have rooted close to a hundred phones with stock ROM's going back over a decade.
What I'm asking is, What if the stock rom cannot be found? There is no other alternative way? I challenge finding this particular stock ROM.
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB.
I have searched over and over for months on various search engines and found nothing. Maybe the ROM is uploaded somewhere in a different language other than English. I would be absolutely stunned if the stock rom was found on the internet.
Can I extract boot.img from terminal via fastboot or other linux or win program?
I have 2 models I cannot find stock ROM's for:
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB - manufacture date year 2022
Moxee M2160 Model MH-T6000 2APQU-MH-T6000 Q6006_V1.0 - manufacture date year 2022
Can anyone find anything? I have scoured the web for months!
I can't believe there is nothing available for these phones.
Please let me know if you can find a stock ROM. I would love to learn where and how you found them. As I've have found nothing for months and months.
Thank you!!!
defcondoc said:
Thank you! I do realize the obvious. If I was able to find it, I wouldn't be asking for help. I have rooted close to a hundred phones with stock ROM's going back over a decade.
What I'm asking is, What if the stock rom cannot be found? There is no other alternative way? I challenge finding this particular stock ROM.
Vortex V22 Model 2ADLJ-V22 MT6761V/WBB.
I have searched over and over for months on various search engines and found nothing. Maybe the ROM is uploaded somewhere in a different language other than English. I would be absolutely stunned if the stock rom was found on the internet.
Can I extract boot.img from terminal via fastboot or other linux or win program?
Click to expand...
Click to collapse
You CAN extract the boot.img via terminal ONLY IF you're on a ROOTED devices!