Develop Bugs

[GUIDE] Update CM without losing custom /system changes (ex Swype, keymap)

There's a really simple way to prevent CyanogenMod from overwriting your custom /system changes during an update. Create the file '/system/etc/custom_backup_list.txt' with a list of files within /system that you don't want to be overwritten.
For example, to prevent CM from wiping out Swype, open adb shell and type this:
Code:
mount -o remount,rw /system
cd /system/etc
echo lib/libSwypeCore.so >custom_backup_list.txt
echo app/Swype.apk >>custom_backup_list.txt
cd /
mount -o remount,ro /system
If you use teferi's custom keymap, do this:
Code:
mount -o remount,rw /system
cd /system/etc
echo lib/libSwypeCore.so >custom_backup_list.txt
echo app/Swype.apk >>custom_backup_list.txt
echo usr/keylayout/vision-keypad.kl >>custom_backup_list.txt
echo usr/keychars/vision-keypad.kcm.bin >>custom_backup_list.txt
cd /
mount -o remount,ro /system
Then the next time you flash CM, your changes to /system will still be there. If you want to see why this works, take a look at /system/bin/backuptool.sh
Hope this helps

Thanks! This is great; now I can easily keep my Email.apk that doesn't require me to enter a alphanumeric password every time I want to use the phone.

CM probably needs to overwrite build.prop but I've been changing the LCD density in this file. Is there a way to use a seperate file to override the lcd density so that i can let CM overwrite build.prop but still maintain lcd density after a flash?

Whatever commands you put in /data/local/userinit.sh will run at boot. So in adb shell, type this for a density of 215:
Code:
cd /data/local
echo setprop qemu.sf.lcd_density 215 >userinit.sh

awesome! thank you!
Don't suppose you would know how to get the CM update to not install/auto delete after installation apks like ADWLauncher and wifi calling?

Thank you!
This may be the long lost solution to my Swype and Cyan Problems. The new Release Candidates are destroying my swype and not liking it's return after installing the new Cyan. So, if this can basically help me update without losing much, it's a god send. Especially the LCD density.
You're a genius.
Thank you.
Hmm, seems the issue is still persistent. Thanks though.

Should userinit.sh and custom_backup_list.txt survive the upgrade or should they both be included in the backup list file?
Sent from my HTC Vision using XDA App

If you look at the actual script, it seems that it ignores the backuptool if .installscript exists, and in practice, I've noticed that nothing gets saved when flashing via ROM Manager. Is this, in fact, what's happening, and is there a way around it?

sundar2012 said:
awesome! thank you!
Don't suppose you would know how to get the CM update to not install/auto delete after installation apks like ADWLauncher and wifi calling?
Click to expand...
Click to collapse
You can put the following in /data/local/userinit.sh:
mount -o rw,remount /system
for apk in ADWLauncher.apk MS-HTCVISION-KNT20-02.apk
do
rm -f /system/app/$apk
done
for package in com.android.launcher
do
pm uninstall $package
done
mount -o ro,remount /system
exit 0
Click to expand...
Click to collapse
I haven't tried this for removing the Wifi Calling app, so ymmv. I remove a much larger set of apps myself (facebook, email, live wallpapers, amazon mp3 store, DSPManager, FileManager, Browser). http://wiki.cyanogenmod.com/index.php?title=Barebones has a list of apps that can be removed safely.

@cparekh -- what e-mail app is that? Or did you just use the pre-OTA's Email.apk app?

Rc4 has the trackpad wake fm radio and speaker led fixed its workng very smooth better than rc3
Sent from my HTC Vision using XDA App

sundar2012 said:
awesome! thank you!
Don't suppose you would know how to get the CM update to not install/auto delete after installation apks like ADWLauncher and wifi calling?
Click to expand...
Click to collapse
Just delete them from the cmupdate.zip before flashing. Cwm recovery doesn't require sig so u don't have to worry about resigning it.
OP: nice find, I'm sure ill use it at some point.

This is driving me crazy because I know I have used this command before but i cannot get it to work now... What is the deal?
Code:
$ mount -o remount,rw /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Rooted using gfree on this phone. On my previous phone I used wpthis and did not have a problem. Anyone know what I need to do to mount rw?

cparekh said:
Thanks! This is great; now I can easily keep my Email.apk that doesn't require me to enter a alphanumeric password every time I want to use the phone.
Click to expand...
Click to collapse
I need that apk
Sent from my HTC Vision using XDA App

Used this method to when going from stock to CM 6.1.1 and could not get it to work. I had to push/install manually from ADB.
Anyone had any luck? I did what the OP said then flashed. Was I supposed to do anything after flashing wiping and then flashing (CM & gapps)?

rraxda said:
This is driving me crazy because I know I have used this command before but i cannot get it to work now... What is the deal?
Code:
$ mount -o remount,rw /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Rooted using gfree on this phone. On my previous phone I used wpthis and did not have a problem. Anyone know what I need to do to mount rw?
Click to expand...
Click to collapse
Make sure you have root in the shell by typing su.

cparekh said:
Thanks! This is great; now I can easily keep my Email.apk that doesn't require me to enter a alphanumeric password every time I want to use the phone.
Click to expand...
Click to collapse
IConrad01 said:
@cparekh -- what e-mail app is that? Or did you just use the pre-OTA's Email.apk app?
Click to expand...
Click to collapse
chubb16 said:
I need that apk
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I am also interested in that apk

How can I backup progress on Angry Birds? Drives me nuts starting back over when I reflash CM

Titanium backup. You can use it to restore the app and the data. Usually i just restore the data to a fresh install.

[GUIDE] Flash any recovery easily on the phone using flash_image

Background
To update (flash) a recovery image onto your phone allows you to update or replace your recovery environment on your phone. There are a number of ways to flash a new recovery image, some of the more commonly used methods are using a tool such as ROM Manager or using development tools such as Fastboot. There is also a third method using a standalone utility "flash_image" which allows the flashing of recovery using the terminal emulator on the phone.
flash_image is not a new tool, it has been used on Android since the beginning, many custom ROMs include the utility as part of the ROM itself though not all stock ROMs (including the stock ROM on the G2) include it.
Requirements
1. A permanently rooted (with S-OFF) phone
2. The flash_image binary
3, A recovery image that is compatible with your phone and ROM
3. A terminal emulator application on the phone or use of an ADB shell
Overview:
1. Get the flash_image binary and recovery image onto your phone
2. Copy or move the flash image binary to your system and make executable
3. Use flash_image to update your recovery environment
Stage 1: Get flash_image and recovery image on your phone
1. Download the flash_image binary (not needed if you are running a custom ROM that includes this binary)
2. Download the recovery image you wish to use
You can either directly download the files onto your phone or onto your PC and transfer to your phone. Probably the easiest way to do this is to connect your phone to your computer via USB and mount USB storage, then copy the files to your SD Card. Alternatively you can use ADB Push, bluetooth file transfer or several other methods.
Stage 2: Copy or move the flash image binary to your system and make executable
In terminal emulator:
su
mount -o remount, rw /system
cd /sdcard (or wherever you downloaded/copied the file)
cp flash_image /system/bin
cd /system/bin
chmod 777 flash_image
Click to expand...
Click to collapse
Stage 3: use flash_image to update your recovery environment
In terminal emulator:
su (not needed if using the same terminal session used in the steps above)
cd /sdcard (or wherever you downloaded/copied the recovery image)
flash_image recovery recovery.img (use the appropriate file name for the image file you are flashing)
Click to expand...
Click to collapse
Reboot into recovery and verify that the correct recovery environment is installed
Notes
Any of the commands that call for using a terminal emulator on the phone should work fine using an ADB shell if you prefer.
This was tested on G2 but I can't think of why it would not work on Desire Z or any other phone for which this version of flash_image works. Obviously different phones have different compatible recovery images.
I've attached a zip file containing the flash_image binary that I extracted from the CM 6.1 update zip. I suspect most custom ROMs already have flash_image.
If you are wondering "Why should I use this method over using ROM Manager?" you could be using a recovery image that ROM manager doesn't support, for example ClockWorkMod Recovery 3.x which is required for some experimental ROMs.
If you are wondering "Why should I use this method over using fastboot?" The two main reasons are you can't use fastboot if you are not with a computer with working ADB and using fastboot requires that you have previously flashed the engineering HBOOT.
This is my first guide so I'm open to suggestions or feedback.

Nice one
Though I would suggest that
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
could be simplified to :
Code:
mount -o remount,rw /system
Edit - actually /system isn't even on /dev/block/mtdblock3, and it's not a yaffs2 file system, I suspect that's come from another phone model ?

"dd" will do exactly the same, but no need to install extra stuff since its already there.

dhkr123 said:
"dd" will do exactly the same, but no need to install extra stuff since its already there.
Click to expand...
Click to collapse
I wouldn't have a problem using dd myself. But I would have thought it was much more risky, since instead of typing something relatively user-friendly like "recovery", you're typing in /dev/xyz/abc or similar, which if you get it slightly wrong could be disastrous ?

Excellent, worked for me, flashed CW 3.0 without fastboot

steviewevie said:
Nice one
Though I would suggest that
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
could be simplified to :
Code:
mount -o remount,rw /system
Edit - actually /system isn't even on /dev/block/mtdblock3, and it's not a yaffs2 file system, I suspect that's come from another phone model ?
Click to expand...
Click to collapse
Interesting, I've been using that command since forever (since I first rooted my G1 in early 2009) and it definitely does work on my G2 as well as my wife's MT4G.
I just tried "mount -o remount,rw /system" on my phone and it does not work, mount gives me the "Usage:" messages which seems to mean it wants more parameters.

steviewevie said:
I wouldn't have a problem using dd myself. But I would have thought it was much more risky, since instead of typing something relatively user-friendly like "recovery", you're typing in /dev/xyz/abc or similar, which if you get it slightly wrong could be disastrous ?
Click to expand...
Click to collapse
Unless you run wpthis before dd, you're perfectly safe. The radio partitions are all protected by the power-on write protect feature of the eMMC AS WELL as the linux kernel write protect on low addresses. Worst you can do is blow away your system, data, cache, misc, boot, or recovery partitions, and these are trivial to recover from.

raitchison said:
Interesting, I've been using that command since forever (since I first rooted my G1 in early 2009) and it definitely does work on my G2 as well as my wife's MT4G.
I just tried "mount -o remount,rw /system" on my phone and it does not work, mount gives me the "Usage:" messages which seems to mean it wants more parameters.
Click to expand...
Click to collapse
Depends on whether or not the mount command can tell the associations between the devices and mount points, which is determined by either system configuration, or what mount command you are using (i.e. android's mount or busybox mount).

raitchison said:
Interesting, I've been using that command since forever (since I first rooted my G1 in early 2009) and it definitely does work on my G2 as well as my wife's MT4G.
I just tried "mount -o remount,rw /system" on my phone and it does not work, mount gives me the "Usage:" messages which seems to mean it wants more parameters.
Click to expand...
Click to collapse
Sorry, there should have been an extra space, this works on my phone :
Code:
mount -o remount, rw /system
I don't have a "/dev/block/mtdblock3" on my system. My system partition is mounted on /dev/block/mmcblk0p25, and it is ext3 not yaffs2.
What ROM are you running ? I am running the stock DZ 1.34 ROM. I wonder if you are running Gingerbread ?

steviewevie said:
Sorry, there should have been an extra space, this works on my phone :
Code:
mount -o remount, rw /system
I don't have a "/dev/block/mtdblock3" on my system. My system partition is mounted on /dev/block/mmcblk0p25, and it is ext3 not yaffs2.
What ROM are you running ? I am running the stock DZ 1.34 ROM. I wonder if you are running Gingerbread ?
Click to expand...
Click to collapse
I'm running the Stock G2 T-Mobile post-OTA ROM, definitely not Gingerbread.
Edit: I just tried your method and it works, I will update the guide because your way is simpler and sounds like a safer choice.

you could just rename the CW 3.x.x recovery to the exact named recovery slap it in the cloclwork download folder after you delete the old one and flash it with CW just a quicker trick for GB roms

Not sure that's actually quicker, at least I don't think it would be for me, especially if you are changing recoveries with any frequency (like if tying out Gingerbread ROMs then going back to a 2.2 ROM) because you'd need to constantly rename your recovery images. With my method you would only need to leave the two files named as they are, or for expediency you could rename to recovery.img and recovery3.img then when you wanted to switch you could just execute:
flash_image recovery recovery.img
Click to expand...
Click to collapse
or
flash_image recovery recovery3.img
Click to expand...
Click to collapse
Depending on which recovery you wanted at that point & time.
As I said in the guide, there are already a number of options available, using ROM Manager and fastboot are the most commonly seen in guides but your method and mine are other options for people for whom they work better.

Works!!!
Hi my friends!
It worked for me flawlessly. I was using virtuos 0.9 on my desireZ

Great description, but file did not work for me
It's a very good description that a novice like me can follow. And, I am sure the provided file works for many of you, since many of you reported it to work. After following this guide, and not getting it to work (Stopping Signal error), I decided to find another binary file for flash_image, and the other flash_image file worked for me on my Sprint CDMA Hero. My phone currently has aospMod v0.9.9.2 | AOSP 2.2.1(12/10/2010), if it matters.
One can download a flash_image from here http://cyanogen-files.carneeki.net/flash_image.zip
Then unzip and place on sdcard - follow all the steps in the original post of this thread.
It is my understanding that this file is not unique for different android phones, but if I am incorrect, someone please reply to this thread to correct me.
Again, great job in summarizing the steps.
Regards,
Sanjiv

so darn easy! thank you!

Also usable for splash screen ??
Just curious,
Anybody tried to use flash_image to flash a custom splash screen ?
Something like :
flash_image splash1 customsplash.img

very good post for a newbie like me, just want to make sure, do i need to do the stage 2 every time I flash the recovery?

jaoyina said:
very good post for a newbie like me, just want to make sure, do i need to do the stage 2 every time I flash the recovery?
Click to expand...
Click to collapse
No, you only need to do stage 2 once, whenever you update/change recoveries from that point forward just use stage 3.

Is there a way I can reflash a recovery without access to the ROM?
I'm stuck at the HTC splash screen, so I'm basically stuck in my current (broken) recovery.

sanjivp2000 said:
One can download a flash_image from here (..)[/URL]
Click to expand...
Click to collapse
The flash_image in the start post did not work for me, the one above did.
Also, my HTC Hero was missing the cp command.
Instead, I used: cat /sdcard/flash_image > /system/bin/flash_image
Successfully flashed recovery again

[GUIDE] How to add Flash_Image to rom using terminal

Okay, so i know several of you, like myself, have been trying to flash the recovery 3.x using flash_image through terminal but keep getting an error. This is because the rom you are using doesn't have the flash_image file in the /system/bin folder. I found these instructions on another section of the xda forums.
Disclaimer: I'm not responsible for any damage done to your phone. do this at your own risk..
1. Download and extract the file i have attached.
2. Copy the file to the root of your sdcard.
3. Open the terminal and type in these commands.
su [hit enter]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system [hit enter]
cp /sdcard/flash_image /system/bin [hit enter]
Now your able to flash recovery 3.x from terminal using these commands
su [hit enter]
flash_image recovery /sdcard/(recovery name).img (recovery name is whatever you have your recovery 3.x named)
i hope this helps at least one person...
Happy Flashing

Thanks bud, saved me the trouble .

No problem...like I said , if it helps at least one person im happy to know it was worth my time...

1. Make sure you have Rom Manager Installed (Free in Market).
2. rename "recovery3......img" with "recovery-clockwork-2.5.1.4-glacier.img"
3.put this "recovery-clockwork-2.5.1.4-glacier.img" on sdcard/clockworkmod/download/koush.tandtgaming.com/recoveries/
4. Open Rom Manager and choose 2.2.1.4 from "All ClockworkMod Recoveries"
that earlest !!! then ClockworkMod Recovery v3..... will now be installed on your phone.

ls1xtreme said:
Okay, so i know several of you, like myself, have been trying to flash the recovery 3.x using flash_image through terminal but keep getting an error. This is because the rom you are using doesn't have the flash_image file in the /system/bin folder. I found these instructions on another section of the xda forums.
Disclaimer: I'm not responsible for any damage done to your phone. do this at your own risk..
1. Download and extract the file i have attached.
2. Copy the file to the root of your sdcard.
3. Open the terminal and type in these commands.
su [hit enter]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system [hit enter]
cp /sdcard/flash_image /system/bin [hit enter]
Now your able to flash recovery 3.x from terminal using these commands
su [hit enter]
flash_image recovery /sdcard/(recovery name).img (recovery name is whatever you have your recovery 3.x named)
i hope this helps at least one person...
Happy Flashing
Click to expand...
Click to collapse
Great guide! Will add this to my post on how to flash cwr3.

ls1xtreme said:
I found these instructions on another section of the xda forums.
Click to expand...
Click to collapse
Source would be nice.

neidlinger said:
Source would be nice.
Click to expand...
Click to collapse
Sorry but I honestly don't remember...i just did a google search for "flash_image with terminal"or something like that...

Thanks for help working excellent

says.file not.found
Sent from my HTC Glacier using XDA App

suwei said:
1. Make sure you have Rom Manager Installed (Free in Market).
2. rename "recovery3......img" with "recovery-clockwork-2.5.1.4-glacier.img"
3.put this "recovery-clockwork-2.5.1.4-glacier.img" on sdcard/clockworkmod/download/koush.tandtgaming.com/recoveries/
4. Open Rom Manager and choose 2.2.1.4 from "All ClockworkMod Recoveries"
that earlest !!! then ClockworkMod Recovery v3..... will now be installed on your phone.
Click to expand...
Click to collapse
YOU NEED TO MAKE THAT A THREAD IT WORKED LIKE A CHARM TEN MINUTES LATER I AM RUNNING CM7 I CANT BELEIVE OT WAS AS SIMPLE AS THAT THUMBS UP THANKZZ
Sent from my HTC Glacier using XDA App

rich2thad said:
says.file not.found
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Where exactly is it giving u this message???
Oops...didn't realize u had figured it out...

after the second command it gives me an messege saying
cp not found

JXTONY said:
after the second command it gives me an messege saying
cp not found
Click to expand...
Click to collapse
I wonder if this procedure requires busybox?

Okay I have tried multiple methods as posted in this section and I cannot get to Clockwork recovery 3.xxx... I did it once before and then reverted back to the version flashable via Rom Manager. It takes me straight to fastboot when I try to reboot into recovery. Any clues what I'm doing wrong? I'm running CM6 currently and I'm slightly annoyed that I got it to work once but can't again
Sent from my HTC Glacier using XDA App

Geoi1006 said:
Okay I have tried multiple methods as posted in this section and I cannot get to Clockwork recovery 3.xxx... I did it once before and then reverted back to the version flashable via Rom Manager. It takes me straight to fastboot when I try to reboot into recovery. Any clues what I'm doing wrong? I'm running CM6 currently and I'm slightly annoyed that I got it to work once but can't again
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Have you tried to go into Rom Manager and flash the latest recovery for your phone? You can also try my method of installing ClockworkMod Recovery. It can be found HERE. If you have ADB/Fastboot set up you can also try pushing a new recovery img to your phone. If you dont have ADB set up you can use MY GUIDE to get it set up.
It sounds like your phone cant find the recovery img (could be missing).
Hit me with a PM and I can help walk ya through it if you need.

help. i downloaded the file and flashed it. i was able to boot to clockwork 3.0 and flash cm7. now when i choose 2.5.1.4 it says "an error occurred while flashing your recovery". not sure what to do. i can still get 2.5.1.2, but it won't let me get back to 2.5.1.4 which should be 3.xxx. i would like to flash to a newer nightly, but can't get the clockwork 3.xxx.

cveez11 said:
help. i downloaded the file and flashed it. i was able to boot to clockwork 3.0 and flash cm7. now when i choose 2.5.1.4 it says "an error occurred while flashing your recovery". not sure what to do. i can still get 2.5.1.2, but it won't let me get back to 2.5.1.4 which should be 3.xxx. i would like to flash to a newer nightly, but can't get the clockwork 3.xxx.
Click to expand...
Click to collapse
If you are on iced glacier try going into your settings/applications/Rom Manager and uninstall updates. Then go back to Rom Manager and try flashing 2.5.1.4

i am on cm7 nightly 24. i thought i would try to uninstall updates anyway. i went settings, applications, manage applications and rom manager is not there. i went to the market, thinking i would uninstall and reinstall rom manager and it only gives me the option to open. no uninstall. not sure what to do now,

There its a new zip I posted in the cm7 thread a page or so back
Sent from my HTC Glacier

i deleted the file i had. downloaded the latest file, flashed it and i still get the same error message.

[Q] CM9. can't mount /system rw

Whenever I try and mount system as writable I get
Mount: operation not permitted
The error occurs whether I use adb or terminal.
Sorry! Realized after posting I'd gone into the wrong forum! Could a mod move it please? Or delete it and I'll make a new one?

Maybe try to download the ICS rooting.zip and run the macro using fastboot.

Open up terminal emulator and type:
su
mount -o remount,rw / system
Sent from my SPH-D710 using xda premium

bmxrideher said:
Open up terminal emulator and type:
su
mount -o remount,rw / system
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
This won't work on the a100. You still need the mempodroid exploit.

Works on mine. It's only a small price to pay to have the CM9 goodness on my tablet and it's R/W until next reboot.
Sent from my SPH-D710 using xda premium

bmxrideher said:
Works on mine. It's only a small price to pay to have the CM9 goodness on my tablet and it's R/W until next reboot.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
This method doesn't work on my tablet.
Isn' there any other method to acquire r/w?

bellaale said:
This method doesn't work on my tablet.
Isn' there any other method to acquire r/w?
Click to expand...
Click to collapse
Either of the ICS root methods in the dev section should fix it

bellaale said:
This method doesn't work on my tablet.
Isn' there any other method to acquire r/w?
Click to expand...
Click to collapse
You might try "busybox" after the su and before the mount command, e.g.: 'busybox mount -o remount,rw /system'
Busybox knows about these things.

AZBOLIVE
just type in "su" enter it then type commands as normal.
your permissions wont let you at present,
letting the system know to run su works good.
hope it helps!

[TOOL](OneClick)Updated 7-8-13 ATT ROOT RECOVERY ODIN LOKIFYED

UPDATED 7-8-13
WHAT THIS TOOL DOES:
1.ROOTS YOUR GALAXY S4 (motochopper exploit created by djrbliss)
2. PREPS FOR RECOVERY
3. INSTALLS CWM OUDHS 1.0.3.4 (7/8) RECOVERY(credit to shabbypenguin)
4. INSTALLS TWRP 2.6.0.0 (credit to dees_troy)
5. Flash phone back to stock using odin
(Full Version Only)
#FOR AT&T I337 ONLY WARNING MADE#
Heres a pretty amateur video I threw together:
https://www.youtube.com/watch?v=NlK3r81kQPw&feature=youtube_gdata_player
Ive updated this to a 3 way all in one tool. Tool can root device (using motochopper by djrbliss) and install either cwm or twrp. Great tool for all those just getting started. Both CWM OUDHS 1.0.3.5 and TWRP 2.5.0.2 are auto loki. They will apply loki patch to all compatible roms and kernels flashed. You can also flash back to stock via Odin
##EDIT I HAVE RECEIVED VERIFICATION THAT TWRP WILL NOT AUTO PATCH. THIS CAME FROM DEES_TROY HIMSELF. IF YOU USE TWRP BE SURE TO FLASH A LOKI KERNEL AFTER ANY NON LOKI ROM FLASH##
A huge thanks to djrbliss for his genius
And huge thanks to dees_troy and shabbypenguin for the recoveries
Also thanks to mostyle for the script help
Instructions:
1. Download 3way tool zip
2. Unzip on desktop and open tool.
3. Connect I337 via usb with usb
debugging enabled.
4. Click Run_Me.bat select number for option you desire and enjoy!
Use this tool at your own risk. I am not responsible for any level of destruction to your phone blah blah blah
Downloads:
Full Version
https://mega.co.nz/#!o0dXHLoY!BNo2eFNQsuPN2-ivpVGo7Vk_V7ckHorY9WlK0PTqbSM
Slim Version (no odin to stock)
https://mega.co.nz/#!Q9FByZrD!CUK7RTDUzzzrH-n3rXjylhkOyy9B1gx9zHNfaKkbVJg
#EDIT# ADDED PREP FOR RECOVERY OPTION. WILL REMOVE KNOX APKS AND install-recovery.sh FOR YOU.Mirrors are welcome. Have a nice day! Dont forget to hit the THANKS button!
If youd like to buy me a beer:beer: I wont complain
Thanks for the beer:beer:list:
Scanss2k
LSUtigers03

O.K
I like to try it :fingers-crossed:

I installed the OUDHS Recovery yesterday and now either one of these will install.I'd love to have Loki'd TWRP. My phone has the same UCUAMDL

If you use either of these please let me know if it works for you.

Respond to sholsten
You mean Neither will work,
It didn't work on mine.

Ill recheck script when I get home. Worked on test devices prior to posting. Please post error messages here. ^^^^ already have yours

pakxelaos said:
Respond to sholsten
You mean Neither will work,
It didn't work on mine.
Click to expand...
Click to collapse
Neither seemed to have have installed on mine. It has the same one I installed in my above post yesterday.

sholsten said:
Neither seemed to have have installed on mine. It has the same one I installed in my above post yesterday.
Click to expand...
Click to collapse
What message did you get on tool after it ran

pakxelaos said:
Respond to sholsten
You mean Neither will work,
It didn't work on mine.
Click to expand...
Click to collapse
Did uninstall the recovery.sh file?

Fixed
On the line that issues the remount command there occurs 'Permission denied.'
In your batch file change line 25:
adb remount
Click to expand...
Click to collapse
so that it reads:
adb shell su -c "mount -o rw,remount /system"
Click to expand...
Click to collapse
Of course this assumes you are rooted..
EDIT:
Still getting an error 'Failed to open aboot for reading'
I'm investigating.. Hang on.

Will change and repost in a few

You could just install goomanger and install twrp thats been lokified directly from your rooted s4
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

bhp090808 said:
What message did you get on tool after it ran
Click to expand...
Click to collapse
Finished Rebooting into TWRP
Have a nice day!
adb is not recognized as an internal or external command, operable program or batch file.
Press any key to continue

Here's the fixed script..
Just had to su -c all of your commands...
db kill-server
adb start-server
adb shell su -c "mount -o rw,remount /system"
adb wait-for-device
adb push loki_flash /data/local/tmp
adb push openrecovery.lok /data/local/tmp
ECHO.
ECHO Doing the hard stuff.............
ECHO.
adb shell su -c "mount -o rw,remount /system"
adb shell su -c "chmod 755 /data/local/tmp/loki_flash"
adb shell su -c "./data/local/tmp/loki_flash recovery /data/local/tmp/openrecovery.lok"
Click to expand...
Click to collapse
Hope that helps. Tested it here and it works fine..

mostyle said:
Just had to su -c all of your commands...
Hope that helps. Tested it here and it works fine..
Click to expand...
Click to collapse
Will update and repost in a few thx
EDIT
Ok updated script new links are up let me know if its working for you now

MrPlNK said:
You could just install goomanger and install twrp thats been lokified directly from your rooted s4
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
How do you find the correct TWRP?

Just tried this with TWRP worked beautifully, thank you very much!! :good:

djoutrages said:
Just tried this with TWRP worked beautifully, thank you very much!! :good:
Click to expand...
Click to collapse
Make sure to thank mostyle for the script assist. Thanks bro

Tested both on my 32GB S4. Both working with no issues at all. Appreciate the work that went into this.

So if I understand this will allow you to flash a Rom that has not been Loki'd and it will loki it and allow it to boot with either TWRP or CWM?