Related
I currently have "stock rom" and "franco kernel r72"...
i searched everywhere before getting 4.2.2 update and followed the instruction:
1. Download stock kernel from here:
http://forum.xda-developers.com/show....php?t=2024982
2. Flash it in recovery.
3. Boot into android.
4. Go from root explorer to system/lib/hw and*
i) Delete power.msm8960.so
ii) Remove .fkbak extension from power.msm8960.so.fkbak so it looks like, power.msm8960.so
iii) Fix the permissions to rw-r--r--
5. Reboot to recovery
flash the update from recovery and install the best kernel out there again.
Click to expand...
Click to collapse
but even after following all these instructions I continue to get error on "power.msm8960.so" file.
so I checked the file and the "power.msm8960.so.fkbak" turned out to be damaged by recent trial of Minco ROM...
(power.msm8960.so.fkbak's modified date turned out to be the same day I installed the minco rom)
simply saying: franco kernel backed up not the original but one that was edited by minco rom (correct me if im wrong)
now that Im back to stock rom but with a wrong backup file of power.msm8960.so, I'm stuck and need the original file...
can anyone (with a stock kernel) send me a original backup of "power.msm8960.so" located in "system/lib/hw" ???
so that I can replace my wrong backup.... thank youuuu
I have been trying to get the KitKat leak working in a safestrap rom slot for days. Each time it failed, and I concluded that it was currently incompatible with the hijack Hashcode was using. So, I tried flashing my KK rom to the stock slot, and then I immediately flashed supersu. Voila, KitKat with root on my locked at&t moto x!
The interesting thing is that this method should work for any rom that is compatible with the stock kernels (because locked bootloader wont allow any other kernel). Hopefully this will 'open the floodgates' to flashing AOSP roms on locked devices that can run safestrap.
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE. With that said, this doesn't touch your bootloader, and you should be able to restore back to stock if there is a problem.
Here are the steps I followed on my locked ATT moto x starting with the at&t stock .51 rom:
1) extract ext4 filesystem image from leak's system.img
2) used android kitchen (thanks dsixda) to cook a flashable rom and fixed some symlinks with help from the updater-script found in dhacker29's 4.4 rom
3) root (pwnmymoto - thanks jcase)
4) install safestrap (thanks Hashcode)
5) copied the rom I cooked to sdcard
6) copied supersu flashable zip to sdcard (thanks chainfire)
7) booted to SS TWRP recovery
8) switched to stock rom slot
9) flashed my cooked rom
10) immediately flashed supersu
11) rebooted into bootloader
12) flashed kitkat kernel: fastboot flash boot boot.img
13) cleared cache and userdata
(I left the modem from the 4.2.2 .54 update)
Rebooted to kitkat with root!
I haven't tested bluetooth, but wifi and gps work. Strangely, the safestrap 'recovery or continue' screen is still there, but the /ss directory is empty. (I would like to know how to manually remove ss, as it is almost certainly not working now.)
I would be happy to share my flashable 4.4 rom, but I noticed that the original leak was taken down. What/where is the smart place to get this up?
I found a place to upload the rom: http://forum.xda-developers.com/showthread.php?p=47451659#post47451659
Hopefully the instructions there are clear...
Can I ask how you extracted from the system.img? I tried to follow the guide that uses ext4_unpacker, but it won't open it. It just says unknown file format. Guessing you did it on a Linux machine?
Ctrl-Freak said:
I have been trying to get the KitKat leak working in a safestrap rom slot for days. Each time it failed, and I concluded that it was currently incompatible with the hijack Hashcode was using. So, I tried flashing my KK rom to the stock slot, and then I immediately flashed supersu. Voila, KitKat with root on my locked at&t moto x!
The interesting thing is that this method should work for any rom that is compatible with the stock kernels (because locked bootloader wont allow any other kernel). Hopefully this will 'open the floodgates' to flashing AOSP roms on locked devices that can run safestrap.
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE. With that said, this doesn't touch your bootloader, and you should be able to restore back to stock if there is a problem.
Here are the steps I followed on my locked ATT moto x starting with the at&t stock .51 rom:
1) extract ext4 filesystem image from leak's system.img
2) used android kitchen (thanks dsixda) to cook a flashable rom and fixed some symlinks with help from the updater-script found in dhacker29's 4.4 rom
3) root (pwnmymoto - thanks jcase)
4) install safestrap (thanks Hashcode)
5) copied the rom I cooked to sdcard
6) copied supersu flashable zip to sdcard (thanks chainfire)
7) booted to SS TWRP recovery
8) switched to stock rom slot
9) flashed my cooked rom
10) immediately flashed supersu
11) rebooted into bootloader
12) flashed kitkat kernel: fastboot flash boot boot.img
13) cleared cache and userdata
(I left the modem from the 4.2.2 .54 update)
Rebooted to kitkat with root!
I haven't tested bluetooth, but wifi and gps work. Strangely, the safestrap 'recovery or continue' screen is still there, but the /ss directory is empty. (I would like to know how to manually remove ss, as it is almost certainly not working now.)
I would be happy to share my flashable 4.4 rom, but I noticed that the original leak was taken down. What/where is the smart place to get this up?
Click to expand...
Click to collapse
Glad to see locked BLs getting some love. Any chance of KK screenshots? No one seems to have uploaded them on any thread. How has your experience been with it so far?
freak4dell said:
Can I ask how you extracted from the system.img? I tried to follow the guide that uses ext4_unpacker, but it won't open it. It just says unknown file format. Guessing you did it on a Linux machine?
Click to expand...
Click to collapse
This took me a day to figure out. I used simg2img in ubuntu.
anirudh412 said:
... How has your experience been with it so far?
Click to expand...
Click to collapse
The only material problem I am having is battery life - it seems noticeably worse that the att .54 ota version.
Hi xda and omni community my question is about delta updates OTA.I wnt to ask 2 simple questions.Today i flashed for first time the latest nightly of omni rom and i am curious how OTA works.When the new nighlty will come out i pressume i go to system updates and i install it from there and if that happens its like a "dirty install" so i dont lose any data on my phone or its new from scratch?And last,currenlty i use PhilzTouch for custom recovery this should work with OTA or i need to flash TWRP?
Thanks
asbanoglou said:
Hi xda and omni community my question is about delta updates OTA.I wnt to ask 2 simple questions.Today i flashed for first time the latest nightly of omni rom and i am curious how OTA works.When the new nighlty will come out i pressume i go to system updates and i install it from there and if that happens its like a "dirty install" so i dont lose any data on my phone or its new from scratch?And last,currenlty i use PhilzTouch for custom recovery this should work with OTA or i need to flash TWRP?
Thanks
Click to expand...
Click to collapse
You won't lose any data unless something really horrible goes wrong.
Unofficial CWM recoveries might work but are untested and not officially supported. Actually, I think some of the newest features (such as secure verification of ZIPs) require TWRP
Official CWM releases will NOT work as they block extendedcommands scripts from anything but ROM Manager
TWRP is the only tested/officially supported configuration for OpenDelta. Bug reports against any other recovery configuration are considered invalid.
I flashed a few nightlies via OpenDelta now, no problems encountered.
Handy little feature: Put extra zips you want to flash after update into /sdcard/OpenDelta/FlashAfterUpdate/ - they'll be flashed automatically after update (in alphabetical order). No need to flash custom kernels or SuperSu manually
I noticed that die File in the OpenDelta folder will bloat after applying all that stuff that the Updater do...
So is there a chance that omni will add an option to automatical delete this file after some days, so that it will save space?
_TechAddicted said:
I noticed that die File in the OpenDelta folder will bloat after applying all that stuff that the Updater do...
So is there a chance that omni will add an option to automatical delete this file after some days, so that it will save space?
Click to expand...
Click to collapse
Ehm. Where is the Rom.zip if something goes wrong?
What will you flash if you deleted the content of /OpenDelta directory?
GALAXY NOTE N7000 // KITKAT 4.4.2 // OMNI
AA1973 said:
Ehm. Where is the Rom.zip if something goes wrong?
What will you flash if you deleted the content of /OpenDelta directory?
GALAXY NOTE N7000 // KITKAT 4.4.2 // OMNI
Click to expand...
Click to collapse
Hm... That's right.
It redownload the Zip file.
I have no problem with the way OpenDelta does that stuff!
I really love this Rom and OpenDelta. :laugh:
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
this is beta release. for t900 only.
I'll write full instruction later. For full description see http://forum.xda-developers.com/show....php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
for stock firmware only. for now. use stock firmware as primary. you can flash cm as additional.
Installation:
1. https://yadi.sk/d/9t2yfkIPc7yPj - this is modded recovery. flash via odin (updated 19/10. Thanks to @arcadia2uk for fix flashing bug)
2. https://yadi.sk/d/TtXcwe6Hc54cR - patched stock kernel
https://yadi.sk/d/r2lnH3N3c54eF - multirom main program
flash through modded recovery patched kernel and multirom.
uninstallation:
https://yadi.sk/d/r9ZLm0vCc68um - flash this uninstaller through recovery, then flash original twrp
known issues:
- 1920x1200 resolution in twrp
- in List Roms installed roms dont shown
- in multirom boot menu touchscreen downt work. use buttons (vol-,vol+,power)
multirom apk from play store doesnt support this release.
reserved
more reserved
bonuzzz said:
this is beta release. for t900 only.
I'll write full instruction later. For full description see http://forum.xda-developers.com/show....php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
for stock firmware only. for now. use stock frimware as primary. you can flash cm as additional.
Click to expand...
Click to collapse
Nice, I have to try this later on. I noticed that after having installed CM11, I can no longer flash touchwiz (I deleted my back-up, as I no longer needed it...), why I probably have to start all over and use Odin to re-install stock and then install multi ROM on top of it. I will look into it once I get some time over.
When you are saying "stock firmware", could this be any customized touchwiz ROM?
PS the link to the MultiROM decription does not work, here is the correct one http://forum.xda-developers.com/showthread.php?t=2011403
arcadia2uk said:
Nice, I have to try this later on. I noticed that after having installed CM11, I can no longer flash touchwiz (I deleted my back-up, as I no longer needed it...), why I probably have to start all over and use Odin to re-install stock and then install multi ROM on top of it. I will look into it once I get some time over.
When you are saying "stock firmware", could this be any customized touchwiz ROM?
Click to expand...
Click to collapse
yes, every touchwiz rom
I have to recompile cm kernel to support multirom. I'll do it later. It depends on Valera's decision whether support t900 or not.
bonuzzz said:
this is beta release. for t900 only.
Installation:
1. https://yadi.sk/d/Sm4V4SMDc54ay - this is modded recovery. flash via odin
uninstallation:
https://yadi.sk/d/Sm4V4SMDc54ay - flash this uninstaller through recovery, then flash original twrp
Click to expand...
Click to collapse
It doesn't seem correct that the modded recovery and the installer has the same d/l link?
---------- Post added at 11:35 PM ---------- Previous post was at 10:52 PM ----------
bonuzzz said:
yes, every touchwiz rom
I have to recompile cm kernel to support multirom. I'll do it later. It depends on Valera's decision whether support t900 or not.
Click to expand...
Click to collapse
When trying to flash the recovery with Odin there's an error message saying that the MD5 Hash value is invalid, recovery_mr_t900.tar.md5 is invalid.
I recompiled recovery and refreshed links. try again to flash.
bonuzzz said:
I recompiled recovery and refreshed links. try again to flash.
Click to expand...
Click to collapse
Odin is still diplaying the message that md5 is invalid.
Maybe a file w/o md5 would work?
arcadia2uk said:
Odin is still diplaying the message that md5 is invalid.
Maybe a file w/o md5 would work?
Click to expand...
Click to collapse
unpack archive and try to flash recovery.img with flashify. maybe change version of odin. i use 3.09.3
bonuzzz said:
unpack archive and try to flash recovery.img with flashify. maybe change version of odin. i use 3.09.3
Click to expand...
Click to collapse
I renamed the tar file by taking away the .md5, that worked.
The boot with the stock ROM went fine. However, I tried install my cm11 by restoring a backup and got stuck, or so I thought it actually came to life after having looked a SOD for 5 min. so I guess it went well. Next problem is that when I'm on the MultiROM boot menu it doesn't give me the option to select the alternative ROM, but makes the countdown and then boots internal. There is no possibility for me to select my alternative ROM as the blue strip does not react to touch. Well, I hope you understand what I mean...
---------- Post added at 09:59 AM ---------- Previous post was at 09:29 AM ----------
bonuzzz said:
unpack archive and try to flash recovery.img with flashify. maybe change version of odin. i use 3.09.3
Click to expand...
Click to collapse
It might also be linked to the fact that the recovery is trying to validate the ROM as a v2awifi, while it should be v2wifixx on the T-900.
I assume the recovery.img need to be modified?
---------- Post added at 10:19 AM ---------- Previous post was at 09:59 AM ----------
It's actually as simple as touch mode that is disabled in the bootmenu, and you have to use up/down keys to select and power key to confirm your ROM choice (I bet it says this in the OP already...)
Now when that is cleared out it seem to be running great, but as I need to test drive another T-900 Rom I have to uninstall it as I need original TWRP to flash that ROM, due to the naming convention.
After all this gave me the opportunity to test the uninstaller that also worked well
.
So the only issue is the Recovery naming convention the T-900 should be v2wifixx.
This is how I came to have the v2wifixx:
TWRP 2.8.0.0 downloaded from http://www.techerrata.com/browse/twrp2/v2wifixx where I selected openrecovery-twrp-2.8.0.0-v2wifixx.img.tar and flashed it with Odin 3.07. This is the most common version for T-900 owners, as they followed the posted instructions HERE. It's also the version for which Valeria ported the cm-11.
I dont have t900, so i dont know these details
v2wifixx or v2awifixx?
bonuzzz said:
I dont have t900, so i dont know these details
v2wifixx or v2awifixx?
Click to expand...
Click to collapse
v2wifixx is the one. (no a after the 2)
But as I mentioned, apart from the small glitches you mention in the OP everything runs smoothly, and what a relief it is to quickly transfer between different ROMs. Great work, I just wished we had a decent touchwiz ROM for the T-900... Thank you, Great work (but I'm getting used to it ) With this, the only thing I had wished for is a 64G internal SD, rather than the 32G I have, unfortunately you can't perform miracles Bonuzzz.
I've been looking into MultiROM before, bet never saw the need for it, but after this experience I have also installed it on my HTC One (m8) which allows me to test ROMs quickly and smoothly, what a difference it makes.
Updated 10/18/2014 08:40am EST
Temporary work around:
1. backup you TouchWiz ROM* (TW),
2. install cm11(s) prior to MultiROM and make a backup,
3. recover your TW, and
4. proceed with MultiROM install after Bonuzzz's instructions in post 1
Once a fixed recovery is available, simply flash this new recovery image and you're good to go. As of that point you can update cm11 nightly's on the go.
HOW to Updating/changing ROMs
Primary ROM (Internal)
- Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs) (note: don't forget fixed kernel)
- Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
Secondary Android ROMs
- If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
- Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
- Select "Flash ZIP" and flash ROM's ZIP file.
* I installed Bonuzz's Custom ROM 1.0.1 (for the P-900) and flashed his MultiROM kernel (see post 1) on top of it. And with no other modifications it seems to work perfectly well. I have only encountered a single minor issue, auto screen-rotation didn't work, but mine is always locked in landscape anyway. I froze the TouchWiz launcher and using Google Now Launcher instead, it couldn't be done w/o freeze, and also fixed an issue with incorrect cropping of my wallpaper. After all everything is good, and as always a great performance by Bonuzzz. Thank you/arc
reuploaded recovery. try again.
bonuzzz said:
reuploaded recovery. try again.
Click to expand...
Click to collapse
It looks like you accidentaly re-uploaded the same file, I have the same error message saying:
This package is for device: v2wifixx; this device is v2awifi.
E:Error executing updater binary in zip '/tmp/mr_update.zip'
Click to expand...
Click to collapse
arcadia2uk said:
It looks like you accidentaly re-uploaded the same file, I have the same error message saying:
Click to expand...
Click to collapse
you talked about multirom file but wrote recovery. i tried to find problem in wrong place.. redownload again
bonuzzz said:
you talked about multirom file but wrote recovery. i tried to find problem in wrong place.. redownload again
Click to expand...
Click to collapse
I sent you an e-mail about the problem a few minutes ago
Am I correct to assume that the only way to install cm-11 with gapps is by flashing a backup under MultiROM?
Or, at least until you can get the Advanced/MultiROM/List ROMs option corrected, since that seems to be to only place where you can flash a .zip on top of an existing ROM, and this install option only allow you to make a simple flash, or have I missed something?
bonuzzz said:
reuploaded recovery. try again.
Click to expand...
Click to collapse
Do I feel that you're abandoning this project, when you're this close....