[CWM/KERNEL]Stock Kernel with ClockworkMod[4.0.2.A.0.42] - Xperia Play Android Development

Credits:
- DooMLord -> his recovery sources on github, and his guidance on assisting me with setting up the build environment and for his kernel.sin unpacker.
- Sony Ericsson -> the kernel with this.
I wanted the stock kernel because of battery drain issues present in many custom kernels, mine included, because although I used the semc sources to compile my kernel, it still had worse battery drain than stock.
I have unpacked the zImage from the kernel.sin in the 4.0.2.A.0.42 and then made that and a modified ramdisk into a boot.img, which you can flash.
This is for people who want to stay with the stock kernel, but want clockworkmod recovery.
Kernel string version:
Code:
2.6.32.9-perf
[email protected] #1
Download: http://dl.dropbox.com/u/13729847/semc/kernels/stockCWM/boot.img
MD5: 1ad7e6db6258b73555f0e6ae73fe4fd6
To flash, use the command:
Code:
fastboot flash boot boot.img
If you are on linux:
Code:
./fastboot -i 0x0fce flash boot boot.img
Don't forget to say thanks if you use this!

Yo installed it the custom recovery works fine and now testing UPDATE-looks like its not starting up for me ill try a reflash UPDATE-its not working properly the system wont start man

Super interested in this since I went back to Stock rom moments ago so I can play FIFA 12. Will this work with the new HK 4.0.2.A.0.58 rom released as I have just put that on.

matknny said:
Super interested in this since I went back to Stock rom moments ago so I can play FIFA 12. Will this work with the new HK 4.0.2.A.0.58 rom released as I have just put that on.
Click to expand...
Click to collapse
wait now dat i think about it i have the same firmware as urs it doesnt work on it weird

matknny said:
Super interested in this since I went back to Stock rom moments ago so I can play FIFA 12. Will this work with the new HK 4.0.2.A.0.58 rom released as I have just put that on.
Click to expand...
Click to collapse
Yes, .42 and .58 use the same kernel.

Will this provide root? I only install Doom's for root & recovery, so if this does I'll use this instead. Thanks.

alreadyused said:
Will this provide root? I only install Doom's for root & recovery, so if this does I'll use this instead. Thanks.
Click to expand...
Click to collapse
No root, but you can flash RootXperia.zip in clockworkmod (search it on google: rootxperia.zip).

Done but having booted after installing and rebooted into recovery (which worked) then restarted to phone it wont boot. Black screen after Sony Logo.
Update: Boots after 15 minutes no battery but now android market is keep coming up unsuccessful
Update 2: It just will not boot so I had no choice but to flashtool 4.0.2.a.0.58 back to default. :-(

matknny said:
Done but having booted after installing and rebooted into recovery (which worked) then restarted to phone it wont boot. Black screen after Sony Logo.
Update: Boots after 15 minutes no battery but now android market is keep coming up unsuccessful
Update 2: It just will not boot so I had no choice but to flashtool 4.0.2.a.0.58 back to default. :-(
Click to expand...
Click to collapse
Actually had market problems myself too, it is very wierd :/

Doesn't work at all for me - fastbooted it left it for a bit
came back and got the red blinking light.
What is the trick to get a stock kernel.sin to a working boot.img ? (Spent most of this afternoon failing to get it to work). All I really want is ro.secure=0 (or ro.debuggable=1). fastbooting CWM is ok for me.

unrandomsam said:
Doesn't work at all for me - fastbooted it left it for a bit
came back and got the red blinking light.
What is the trick to get a stock kernel.sin to a working boot.img ? (Spent most of this afternoon failing to get it to work). All I really want is ro.secure=0 (or ro.debuggable=1). fastbooting CWM is ok for me.
Click to expand...
Click to collapse
Small how-to for creating insecure kernel
1) Unpack kernel.sin to get zImage and ramdisk (tools posted in my other thread)
2) unpack ramdisk
3) edit default.prop and set ro.secure=0 & ro.debuggable=1 then save file
4) repack ramdisk (cpio.gz)
5) repack into boot.img, using zimage + new packed ramdisk, using correct mkbootimg arguments
6) flash using fastboot
7) enjoy
PRO TIP:
Use ONLY LINUX FOR ALL OF THIS ELSE DEVICE WONT BOOT
Sent from my R800i using XDA App

DooMLoRD said:
Small how-to for creating insecure kernel
1) Unpack kernel.sin to get zImage and ramdisk (tools posted in my other thread)
2) unpack ramdisk
3) edit default.prop and set ro.secure=0 & ro.debuggable=1 then save file
4) repack ramdisk (cpio.gz)
5) repack into boot.img, using zimage + new packed ramdisk, using correct mkbootimg arguments
6) flash using fastboot
7) enjoy
PRO TIP:
Use ONLY LINUX FOR ALL OF THIS ELSE DEVICE WONT BOOT
Sent from my R800i using XDA App
Click to expand...
Click to collapse
Thats pretty much exactly what I did. (I did the initial split under windows though I will try again.)
I used the mkbootimg arguments from SE's building kernel blogpost.

help please
please help me somebody i have a problem i cant seem to fix , i flashed the doom kernel then flashed 4.3 icream sandwhich rom exactly like it said to do in the instructions re-booted ,It all booted up fine i played about with the rom for a few hours as you do then i went back to my backed up stock rom ,but heres where the problem happens on restoring my stock rom for some reason my camera doesnt work and playing youtube videos doesnt work and also when i try downloading from the market it just sits there for ever saying downloading but nothings happening i would be really greatfull if somebody can help me resolve this problem thanks..

are you asking this in all thread's?
flash stock rom with flashtool

help
@nickholtus where do i get the stock rom i cant find it plz help and also how do i use this flash tool thing help please somebody i need my phone working again because im going away for the week.

download flashtool
install drivers (in flashtool folder)
download stock (see development .42 .58 or .62)
flash with flashtool

DooMLoRD said:
Small how-to for creating insecure kernel
1) Unpack kernel.sin to get zImage and ramdisk (tools posted in my other thread)
2) unpack ramdisk
3) edit default.prop and set ro.secure=0 & ro.debuggable=1 then save file
4) repack ramdisk (cpio.gz)
5) repack into boot.img, using zimage + new packed ramdisk, using correct mkbootimg arguments
6) flash using fastboot
7) enjoy
PRO TIP:
Use ONLY LINUX FOR ALL OF THIS ELSE DEVICE WONT BOOT
Sent from my R800i using XDA App
Click to expand...
Click to collapse
Hey Doom, I'm trying to follow this, and I'm getting stuck
I downloaded the R800x 2.3.3 (3.0.1.E.0.88) TFT from here: http://forum.xda-developers.com/showpost.php?p=19438024&postcount=12
I unzipped it using xarchiver (installed on arch linux/available on sourceforge)
I ran unpack-kernelsin.pl, and I get two errors (that don't exit out of the perl script):
1) ramdisk written... gzip: no such file or directory
2) cpio: premature end of image
When I try to cpio-ing the ram disk, my computer just sits... How long should I wait, I have a netbook (i know, not the best for doing compiling) and the longest i've let it sit is about 10 minutes (i'm about to let it sit overnight to see if it'll work itself out)
If you could give me any pointers, that'd be outstanding
Thank you,
Pax

paxChristos said:
Hey Doom, I'm trying to follow this, and I'm getting stuck
I downloaded the R800x 2.3.3 (3.0.1.E.0.88) TFT from here: http://forum.xda-developers.com/showpost.php?p=19438024&postcount=12
I unzipped it using xarchiver (installed on arch linux/available on sourceforge)
I ran unpack-kernelsin.pl, and I get two errors (that don't exit out of the perl script):
1) ramdisk written... gzip: no such file or directory
2) cpio: premature end of image
When I try to cpio-ing the ram disk, my computer just sits... How long should I wait, I have a netbook (i know, not the best for doing compiling) and the longest i've let it sit is about 10 minutes (i'm about to let it sit overnight to see if it'll work itself out)
If you could give me any pointers, that'd be outstanding
Thank you,
Pax
Click to expand...
Click to collapse
for such things send me p.m.

Related

[Q] How to root Xperia GO

Any idea how to root Sony Xperia Go?
You already got yours? Cool.
Well I think it's a bit early, just wish the Xperia community was bigger.
So nice phones but Sony aren't that big in US.
superoneclick?? unlock root??
Yes, i got it....
Have try superoneclick and many more from the forum but no one work for this...... Need help to root, and i cant find any firmware or rom for this.... But i hope some one will fix this soon
Sent from my ST27i using xda premium
One way is unlocked bootloader and try make a cuslom kernel with recovery but i don't know how make custom kernel
you tried flashtool?? maybe it's supported since its an xperia phone
Sent from my E15i using xda premium
And Sony haven't posted anything?
Any idea?
I have try everything on this forum but cant find any one to work. Hope someone will come with working root to xperia go soon
Sent from my ST27i using xda premium
How to root Xperia GO
pajoneer said:
Any idea how to root Sony Xperia Go?
Click to expand...
Click to collapse
Whether you are on GB or ICS? Have you tried this? It also has a tutorial for rooting ICS. But in either case, you need have your GB ROM.
I dont have the ROM and i cant find any
Sent from my ST27i using xda premium
pajoneer said:
Any idea how to root Sony Xperia Go?
Click to expand...
Click to collapse
- Reflash your phone with current firmware using Sony Update Service
- Copy the blobs Update Service caches from the update to local directory
- Use Flashtool to decrypt and recreate the tft from the blobs
- Unzip the ftf and unpack the boot image together with to kernel
- Edit /default.prop and set ro.secure=0
- Repack the root initramfs file system
- Create a new boot image with the root filesystem and the kernel
- Unlock the boot loader
- fastboot the new image (no need to flash it)
- "adb shell" to the phone, you are now the root user
- remount /system read-write
- add busybox, su and whatever you like
Check www.youtube.com/watch?v=bB77gWRUI_A for details about getting your original image.
See http://developer.sonymobile.com/wp/2011/05/06/how-to-build-a-linux-kernel/ about building the boot image.
Search this forum about how to unpack the .sin-files
kuisma said:
- Reflash your phone with current firmware using Sony Update Service
- Copy the blobs Update Service caches from the update to local directory
- Use Flashtool to decrypt and recreate the tft from the blobs
- Unzip the ftf and unpack the boot image together with to kernel
- Edit /default.prop and set ro.secure=0
- Repack the root initramfs file system
- Create a new boot image with the root filesystem and the kernel
- Unlock the boot loader
- fastboot the new image (no need to flash it)
- "adb shell" to the phone, you are now the root user
- remount /system read-write
- add busybox, su and whatever you like
Check www.youtube.com/watch?v=bB77gWRUI_A for details about getting your original image.
See http://developer.sonymobile.com/wp/2011/05/06/how-to-build-a-linux-kernel/ about building the boot image.
Search this forum about how to unpack the .sin-files
Click to expand...
Click to collapse
Thanks!
But now to next problem... If i run Sony PC Companion I will get anser NO FW found for your device???? (i select repair)
and if i use Sony Update Service i dont get any repar or reinstall it says you already have the last FW........
holst75 said:
If i use Sony Update Service i don't get any repair or reinstall it says you already have the last FW........
Click to expand...
Click to collapse
Ah, strange. Update Service is supposed to reinstall the same version already installed. Maybe Sony not yet updated their servers.
Still I believe you can work around this. The nice thing about Sony Xperia is that when you unlock its bootloader, you can boot your phone over usb using fastboot without having to flash the image. I.e. a single one-time-boot of your image, without any permanent modifications of your phone.
This means you can always try booting another boot image than the original. It don't have to work perfect, just brining the devices up so you can access it via usb and "adb shell". It need to use the same disk devices (mount right partition at right mount point), so try using a image from another Xperia and hope for the best. You can check the mount points using the command "mount" in the shell, compare with the mount points of some other Xperia you can get the ROMs to.
So download a Xperia ROM from XDA, edit ro.secure=0, recompile the boot image again and try fastboot the phone (do not flash it!). If it boots, don't care if everything things isn't working properly, just transfer su and busybox to /system/bin and then halt and restart the phone - this time from the internal flash (= original image), and you got the phone using its original image, but with the su and busybox you need to become root.
Again - do not flash your image, only boot the phone with it. If you flash it, and don't got the original image to restore back, your phone is bricked.
Problem solved.
I have downloaded firmware from Sony ...link will be soon ... but i have problem with rooting system, Please, can somebody help me with them?
I hope we can root woth out unlock bootloader.....
Sent from my ST27i using xda premium
holst75 said:
I hope we can root with out unlock bootloader.....
Click to expand...
Click to collapse
Myself I actually prefer the official way instead of hacks I don't know what side effects they may or may not have, but that's me. I'm sure it's possible using some exploit, but I can't help you there, sorry.
Hi guys,
I created ftf from blobs and unzip ftf.
I used Nero Young guide to make custom rom (kernel), but when I need to add boot.img to my kitchen folder, I can't find it.
I tried to follow this guide http://developer.sonymobile.com/wp/2011/05/06/how-to-build-a-linux-kernel/, but without success. I also try SIN2IMG, mkbootimg... but nothing
Can someone tell me another way to make boot.img, or upload boot.img for ST27i.
driversax said:
Hi guys,
I created ftf from blobs and unzip ftf.
I used Nero Young guide to make custom rom (kernel), but when I need to add boot.img to my kitchen folder, I can't find it.
I tried to follow this guide http://developer.sonymobile.com/wp/2011/05/06/how-to-build-a-linux-kernel/, but without success. I also try SIN2IMG, mkbootimg... but nothing
Can someone tell me another way to make boot.img, or upload boot.img for ST27i.
Click to expand...
Click to collapse
Could you post your FTF ?
pajoneer said:
Could you post your FTF ?
Click to expand...
Click to collapse
There you go:
sendspace.com/file/vks58a
sendspace.com/file/f1uvog

[DEV] Kernel ICS Sony Xperia Go ST27i

Hi Guys,
i got a problem, it is somehow not possible to build a kernel.elf with the mkelf.py from sony, i got the correct header values with objdumb -x from the stock kernel, no chances to get it booting.
i then went on with just building a boot.img, this looks to be working fine, since the official sony ICS updated has not hit Germany, and with the FTF files provided i do not get WIFI working properly, neither with the stock kernel from those ftf, there must be regional changes to the wifi frequenzies ????
my unlocked kernel just boots fine, but as said i am not able to test anything properly since WiFi will not work....
i have attached the boot.img to this thread, flash it with
fastboot.exe flash boot boot.img
unlock bootloader required....
to get su(root), busybox and superuser you need to follow the guide provided here: http://forum.xda-developers.com/showthread.php?t=1839865
there is no recovery included yet,
please let me know if this works for you
cheers
it seemed it would not show up the signal"SONY"
it seemed it would not show up the signal"SONY".
I flashed the boot.img in fastboot mode,
when i pressed the power button,it showed "XPERIA",
I did not know how

[Q] how to convert zImage to boot.img

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

Help with Kernel-compiling for i9100

Hi everyone,
I need some help while I try to compile my first kernel (for experiments) with the Linaro-Toolchain. I followed a youtube instruction and it works well till the point to handle a stock/original boot.img file (with $ abootimg -x boot.img)
INFO: I´m playing with the slimkernel source, Linaro toolchain and mint 17.
Well before bothering you, i tried 1000 different ways to get this boot.img. But:
- extracted stock fimware only contains a boot.bin (and size does not match)
- a boot.img form a custom kernel zip brings me "no Android Magic value. giving up"
- downloadable boot.img are for all other phones excluding i9100...
Do you have any idea how to get this f****g boot.img which is working to get the kernel compiled, or do you know what i did wrong with that??
Thanks in advance
Ambador
Have you tried to extract a boot.img from a slimrom zip?
Yes I did but gave me the same result. I tried different kernels, roms and everytime while typing abootimg x -boot.img the fail appears.
Ambador said:
Yes I did but gave me the same result. I tried different kernels, roms and everytime while typing abootimg x -boot.img the fail appears.
Click to expand...
Click to collapse
I don't know really what you are doing atm because you are compiling a kernel from the kernel sourcecode. But I think that you are going to replace the zImage in the boot.img because kernel compiling doesn't include ramdisk right? Did you ever tryed to use dsixda-kitchen, It's usefull and also easy to use with kernel extracting.
Sorry if I got you wrong.
I used that kitchen already, but gave me the same missing android magic issue.
I tried an other thing, cuz im currently using apolo 7.1 kernel:
this kernel has a zimage only. So is it a possible way to get the kernel source, make a change (add an scheduler which is not in kernel) to see if it will work, compile the zimage with linaro and just replace it in the kernel.zip??

[stock 8.0][Unlocked bl][34.4.A.2.19; ...32; ...85] Root and Recovery (3 clicks)

Thanks to serajr here - https://forum.xda-developers.com/showpost.php?p=75505302&postcount=2973 Go directly to that post and give thanks.
You need:
Stock O ftf (best to use Flashtool/Xperifirm)
Modded boot img for 34.4.A.2.19 - https://mega.nz/#!AgtQ2Sob!JjLRcUVjuy6FNanjGY49g-YYmkcda04witfHp4hwvmo
Modded boot img for 34.4.A.2.32 - https://mega.nz/#!Z1tzEJbZ!e9ET_RtUpKjXRwnJa_TDsMrVwvT-hPxmk06KtryHOuc
Modded boot img for 34.4.A.2.85 - https://mega.nz/#!p5UwAabR!_ofmr_WdId9RdH48Xb3cZtSIzsQ6qcTJTAFYcKHFWJE
Kernel elf file to use with rootkernel [34.4.A.2.85] - https://mega.nz/#!M102lYTZ!9bj2KE-vbNWlej3Dw0NuiXJcfpgiy16svSHud73bLfw
Modded boot img for 34.4.A.2.107 - https://mega.nz/#!Nls0EQBR!Cc4lVcA85f8YeNTo8nMqsuwLzveW5duSbyeZDlI5kDE
Kernel elf file to use with rootkernel [34.4.A.2.107] - https://mega.nz/#!Zp10CASK!iGLE94Tj1SSk1U2p4KLpVrcGmD68C3YvqKMXD6VPFjI
Modded boot img for 34.4.A.2.118 - https://mega.nz/#!14VkzCCB!GK-KEv0A-ZyhysXc1-IusyJjJEB-D5ZWOLm1DRt31tA
Kernel elf file to use with rootkernel [34.3.A.2.118] - https://mega.nz/#!Ylcm1SwA!GuX9dfd2HAqLXy1jom-C6mgP0s4jYXl9qSySkvb_mtA
TWRP - https://forum.xda-developers.com/x-compact/development/ub-twrp-v3-2-1-xperia-x-compact-t3793837
1. Flash stock ftf from Xperifirm via Flashtool
2. After flash, connect in fastboot (before booting phone) and type in command line 'fastboot flash boot boot.img' (this assumes that your modified boot img is in the current directory,and is named 'boot.img'; otherwise, you need to edit the command accordingl)
3. Then type 'fastboot flash recovery twrp-3.2.1.img' (same note as above)
Done
Now, you can flash Magisk, (or whatever), and have root access.
If you want Drm fix, flash serajr's zip here - https://forum.xda-developers.com/attachment.php?attachmentid=4404527&d=1517335127
If you want to restore your own ta with munjeni tool, you will need to patch boot img yourself with rootkernel tool here - https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
How to get stock kernel elf and patch your boot img with rootkernel:
1. Download and build stock ftf from Xperifirm via Flashtool
2. Go to Flashtool > tools > sin editor, and navigate to stock kernel sin file, in the downloaded firmware folder. Click on sin file and choose 'exrract data', and it will create a kernel elf.
3. Follow the guide by serajr. You need only to put the kernel elf into rootkernel folder, then open a command prompt there and run 'rootkernel kernel.elf boot.img'. Answer all questions 'yes', unless you want to skip drm fix and restore your own ta, (if that's the case, you need your target file in that folder renamed to TA.img). After script runs, you will have a new boot img that you can use to follow the guide.
Done...
Magisk, MicroG, and Xposed tested... (update - I haven't tried yet, but I've read that Xposed not working on ...85; update 2 - confirmed, bootloop; update 3 - Xposed fix now available here - https://forum.xda-developers.com/x-compact/themes/xposed-fix-118-t3870673)
I made a patched boot img with rootkernel tool and uploaded it. Link in op. Don't forget to thank serajr...
Can confirm the above method worked for me. I used the TA.img instead of drm fix, and i get root and security test still have widefine and fidokeys enabled.
Just slight reminder for linux user, you need to add execute permission on both `rootkernel` and `bootimg`, otherwise rootkernel tool will fail with permission issue.
levone1 said:
I made a patched boot img with rootkernel tool and uploaded it. Link in op. Don't forget to thank serajr...
Click to expand...
Click to collapse
With which options is your modified boot image prepared?
maluus said:
With which options is your modified boot image prepared?
Click to expand...
Click to collapse
Dm-verity disable - yes
Force encrypt disable - yes
Drm fix - yes
For Drm fix you still have to flash serajr zip. If you want to restore ta with munjeni tool, you will need to patch boot yourself.
Op updated for 3-click root...
SuperSU,Xposed
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Arsis said:
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Click to expand...
Click to collapse
...
Arsis said:
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Click to expand...
Click to collapse
Boot img just enables modification by disabling Sony security stuff, but you still need to flash whatever mod you want. So after flashing boot and recovery img, then flash supersu (or whatever), and you should have root.
I can't say about drm fix, since I've never used it before, but I don't think it will show fido provisioned, etc, because it simply recreates the drm functions through a different method, (not with ta).
I was able :laugh::good: Xposed release link
levone1 said:
Boot img just enables modification by disabling Sony security stuff, but you still need to flash whatever mod you want. So after flashing boot and recovery img, then flash supersu (or whatever), and you should have root.
I can't say about drm fix, since I've never used it before, but I don't think it will show fido provisioned, etc, because it simply recreates the drm functions through a different method, (not with ta).
Click to expand...
Click to collapse
Oh, well. Thank you! It's working now.
Hello,
i flashed on my sony with oreo this boot.img and twrp and im stuck on sony logo. Any ideas what could be wrong? I tried android 34.4.A.0.364 singapure and UK versions and neither of these works with this twrp.
I have the newest platform-tools and flashing went well.
Thanks
Stephenhs said:
Hello,
i flashed on my sony with oreo this boot.img and twrp and im stuck on sony logo. Any ideas what could be wrong? I tried android 34.4.A.0.364 singapure and UK versions and neither of these works with this twrp.
I have the newest platform-tools and flashing went well.
Thanks
Click to expand...
Click to collapse
Can you try running the tool and creating the boot.img yourself? I use the singapore ftf and doesn't have problem booting the system (with the boot img I created myself). I do not put twrp on boot img though. I boot twrp from fastboot when needed
I created boot.img and everything works Thanks a lot!
I dont understang the part that says :
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:
Code:
/system/vendor/etc/fstab.qcom
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.target.rc
(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)
how to do that!? im noob...
Kianush said:
I dont understang the part that says :
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:
Code:
/system/vendor/etc/fstab.qcom
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.target.rc
(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)
how to do that!? im noob...
Click to expand...
Click to collapse
Post linked in op has special instructions for us with Xc - skip that part.
https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
hello guys, i've created a boot.img whit the tool of rootkernel whit my ta.backup but it does not work. the boot it's ok but if i chek my drm keys they say not provisioned. my ta.backup load 2.097.152 byte like the post shows. can someone help me? thanks
update:
sorry guys, i've done again the kernel patch whit my ta backup and this time goes perfect. i don't know why the first time didn't work but now it's ok!
I tried the 3 click method, without doing any boot image myself, but impossible to decrypt with TWRP (or reboot to system).
Wxfdswxc said:
I tried the 3 click method, without doing any boot image myself, but impossible to decrypt with TWRP (or reboot to system).
Click to expand...
Click to collapse
Twrp - https://forum.xda-developers.com/x-compact/development/twrp-3-2-1-decryption-t3751998
As for rebooting to system, can't say for sure... Root method involves only changing boot img, so shouldn't affect system. Any errors in fastboot, etc?
Original flash should be clean flash official stock ftf from Xperifirm. First boot could be 10 minutes...

Categories

Resources