Hi, i have been trying to find a compatible updater-script for my phone to be able to flash a modified stock rom using android kitchen. The way android kitchen modify the update-script to updater-script is not working with my philz touch recovery latest version installed, even if i checkmark the option to use the old update-script method the installation goes thru inside the recovery but i am unable to start the system, it loops on the samsung logo.
any ideas where i can find a compatible updater-script and updater-binary ? i dont know what else i can provide as information to be more clear on the issue. I know a lot of ppl if not all who try to create custom roms are having, searching google did not help and searching the forums either because the results are not for my device specific SGH-M919V and i sure dont want to brick the phone. So far i was able to remove knox, bloatware i personnaly dont want to have in my rom. I am not a coder but i can understand the logics of some scripts.
Related
Hi,
I don't know if this is the correct section to get this question answered, but I'll try:
I have a new tablet, which is not really known at the moment. I managed to root it and next step would be to port Clockworkmod Recovery to it. Since I only found guides where I always have to repo sync the entire CyanogenMod github (which is 19GB+ as I heard), I searched for an alternative where I could save some traffic
I found a clockworkmod recovery from another tablet and wondered if it was just possible to unpack it, modify the recovery.fstab and repack it again.
Is this possible or do I have to modify more than the recovery.fstab? If yes, could you point me to the right direction?
Regards
dump your stock recovery
unpack the stock recovery and save the vold.fstab somewhere.
upload the stock recovery here
http://builder.clockworkmod.com/
get the output and flash`it
if the key`s are not working, unpack the new cwm, and the old recovery, and put the keys from the old recovery.
if you get some mount points erros, you will have to upload also the saved vold.fstab on the clockwork site when you cook the image.
if this does not offer you a good result, you will need to find a similar device (processor, resolution) that has allready a cwm, and try it
the recovery file is ramdisk/sbin/recovery
Hi,
thanks for showing me a way. Unfortunately builder.clockworkmod.com says it didn't find Android magic. This makes sense, as the image is a uImage with lzma compressed data inside. It seems koush's builder handles only "plain" recoveries...
Bad luck
I guess I'll try your second advice and search for a CWM for a similar device, unpack it, replace the fstab file and repack it again.
Thanks again!
hello I have made the porting on http://jenkins.cyanogenmod.com/job/recovery/lastBuild/console
I end up having a zip archive, how can I make my tablet to read that. I have installed cwm recovery and it is rooted. Let me know how can install it and replace my recovery with this.
BTW I have the original stock firmware of my tablet.
let me know thanks
Hello,
I installed a faux kernel patch to spoof my kernel or something to use a particular rom (the rom required it for Canadian users). However, my phone is no longer considered jfltecan (which is what it originally was) and I cannot install jfltecan roms. How do I remove this kernel spoof thing. I tried flashing the original kernel for my phone via odin which did nothing.
you likely need to edit your build.prop. it likely says your device is an i9505 or similar variant.
there are 3 lines in the build.prop that should look like this:
ro.product.model=SGH-I337M
ro.product.name=jfltecan
ro.product.device=jfltecan
adjust them accordingly. here's a thread on the topic:
http://forum.xda-developers.com/showthread.php?t=1948558
Also a lot of aosp ROMs have get prop lines in the updater script. When you download a ROM extract it, go into the updater script and delete the get prop lines or change it to the device that you have. Then rezip and flash. Just stay away from i9500 ROMs and you'll be fine.
Hi,
I have a small question. I own a Canadian Samsung 4 SGH-i337m, after reading the main guide for running other carrier rom on this address
http://forum.xda-developers.com/showthread.php?t=2295557
As the guide mention that I didn't need the loki kernel and I could use my carrier kernel.
I used to backup my kernel with SGS kernel flasher to do the job, but it's not working for s4.
I wanted to backup my stock kernel and apply it after the installation of a cursom rom and apply it through TWRP. As I understood it, kernel is the boot.img, and I read somewhere that the way to create this is to copy the boot.img + copy the /sytem/lib/modules files. If I look to the file prepared by iB4STiD in the file MDOB-I337M-VMK6-FIX-4.1 present here, it seems that it's the case.
There is still flashify as a solution but you can't use the file into recovery.
Does someone know how to do it, or point me out where to find a guide where I can do what I want.
thanks in advance,
youpiyo said:
Hi,
I have a small question. I own a Canadian Samsung 4 SGH-i337m, after reading the main guide for running other carrier rom on this address
http://forum.xda-developers.com/showthread.php?t=2295557
As the guide mention that I didn't need the loki kernel and I could use my carrier kernel.
I used to backup my kernel with SGS kernel flasher to do the job, but it's not working for s4.
I wanted to backup my stock kernel and apply it after the installation of a cursom rom and apply it through TWRP. As I understood it, kernel is the boot.img, and I read somewhere that the way to create this is to copy the boot.img + copy the /sytem/lib/modules files. If I look to the file prepared by iB4STiD in the file MDOB-I337M-VMK6-FIX-4.1 present here, it seems that it's the case.
There is still flashify as a solution but you can't use the file into recovery.
Does someone know how to do it, or point me out where to find a guide where I can do what I want.
thanks in advance,
Click to expand...
Click to collapse
What type of ROM are you using? You have to be using a compatible kernel. AOSP ROM's won't work with a stock kernel, and you can't cross Android version between system and kernel. Using any custom kernel developed for your phone with this guide will work okay however.
Thank you for your answer.
in order to answer your question I was trying to flash the hyperdrive to my phone with compatibility pack. But after reboot I go back directly to download mode. So I figured that it was the boot partition that wasn't adapted to my phone.
So yes, I understand that if you flash a rom based on code as cyanogenmod you will need a custom kernel. but for a rom that is based on stock as hyperdrive rom, unless I'm mistaken, I would imagine that the stock kernel should work.:cyclops:
Is there a way to back it up?
youpiyo said:
Thank you for your answer.
in order to answer your question I was trying to flash the hyperdrive to my phone with compatibility pack. But after reboot I go back directly to download mode. So I figured that it was the boot partition that wasn't adapted to my phone.
So yes, I understand that if you flash a rom based on code as cyanogenmod you will need a custom kernel. but for a rom that is based on stock as hyperdrive rom, unless I'm mistaken, I would imagine that the stock kernel should work.:cyclops:
Is there a way to back it up?
Click to expand...
Click to collapse
My best guess is find out which partition it is and use the dd command OR download the ODIN of your firmware version and extract the boot.img. However, it would be easier to just use a custom kernel designed for your phone as if you back it up like that you either have to make it into a flashable zip or use heimdall to restore it every time.
Sent from Black<3's I337 running Foxhound ROM
Thanks for your answer.
That's weird as a nandroid is doing the job,that is hard to find how to backup a kernel.
anyway, I guess my best chance is to download a custom kernel and apply it after installation of the cutom rom. At first boot re apply a backup kernel with an app as flashify.
thanks youpi
Hi guys.
Ive been trying to deodex my g900i stock lollipop rom but have had trouble making my own flashable cwm zip to replace the system apps and so fourth. I think I just dont have the correct META folder and always seem to end up boot looping. Thanks in advanced
I dont think its the meta problem..probably i also suffered bootloop because of the wrong oat2dex.jar used in deodexing..please recheck that.
I been searching with no real luck finding answers. Id like to install safestrap to my unmodified g955u1 system image without root like they are offering with pie and oreo. Im currently on a v1 bootloader and would kinda like to keep it that way. I inderstand i can root and ins t all but im trying to avoid root because i dont want to loose the regular abilities.
My main reason for any modifications are two reasons ..
One it would be nicw to have a custom recovery
Two.. For some reason i cant install anything in vr. It will download and attempt onstallation with a fail...
I also found a post that offers a zip that is said to create your own modified rom with use of but im un able to understan how i would use said zip or install files from this zip without a safestrap installed. Any advise would be highly appreciated.