Related
BETA~
"Before you download please read 2nd post"
This is the first stage of flash-patch development, this will be used to get AOSP/Vanilla builds onto our INC's in an easy suitable way that fits us all. No more rebuilding or packing a whole new zip
I will be updating the patch as we get more fixes. v0.1 is released and you can grab them below.
Download AOSP FlashPatch v0.2:
http://ziggy471.com/incredibledoes/AOSP-FP-v0.2-signed.zip
Click to expand...
Click to collapse
What the patch does:
- flashes INC's necessary system files
- flashes INC's boot.img
What to come:
- Sense ROM support
Click to expand...
Click to collapse
How to install:
- download flash-patch (posted above)
- download an AOSP/Vanilla rom
- full wipe required
- flash the AOSP/Vanilla ROM but DO NOT REBOOT after install
- flash the patch over the AOSP/Vanilla ROM
- now reboot
That's pretty much it for now, later I will clean up the install and add more fixes to it... Please report back the ROM tested and/or if it failed.
ID
Click to expand...
Click to collapse
OKAY, this is a beta form flash-patch. This Patch will flash over any AOSP/Vanilla build "IF" the update/r-script is not asked to read the board of your device...?!
EXAMPLE:
- CyanogenMod builds have a getprop in the script which will not let you flash. If the script has something like this:
Code:
assert(getprop("ro.product.device") == "passion" || getprop("ro.build.product") == "passion" || getprop("ro.product.board") == "passion");
then the installation will fail because the board does not match.. you can simply edit these your selves by editing the update/r-script...
BEFORE:
assert(getprop("ro.product.device") == "passion" || getprop("ro.build.product") == "passion" || getprop("ro.product.board") == "passion");
AFTER:
assert(getprop("ro.product.device") == "inc" || getprop("ro.build.product") == "inc" || getprop("ro.product.board") == "inc");
Click to expand...
Click to collapse
You can test out AOSP/Vanilla ROMS from any device like Droid, Desire, EVO, Nexus etc... as long as the script does not require the 'getprop' then you should be fine.
PLEASE NOTE: No telling on which roms are supported, only way to find out is to look around the forums and give it a flash... If tested and worked please post ROM/Developer so I can update OP.
"HOW TO EDIT update/r-script" 2 different ways~
NOTE: There is 2 different scripts "update-script" and "updater-script" you will see that I write "update/r-script" because there of the two different scripts. Updater-script comes with an "updater-binary" I never edit the binary so you can leave it alone... just edit the update or updater-script.
Click to expand...
Click to collapse
1- unzip the downloaded ROM
2- open folder META-INF >> com >> google >> android >> update/r-script
3- Open the update/r-script using an xml reader (For WINDOWS use notepad++) (For LINUX use gedit) or something similar...
4- Change the getprop "<device>" to getprop "inc"
5- save and replace the old update/r-script with the one you just saved
6- sign .zip and flash (If I remember correctly Clockwork recovery does not need a signed update.zip so signing the .zip is not required)
Click to expand...
Click to collapse
1 easy step:
This is the easiest way to edit the update/r-script... Completely remove the "assert getprop"
~EXAMPLE from CyanogenMod for N1~
Before:
ui_print("Welcome to CyanogenMod-6.1.0-RC1-N1!");
assert(getprop("ro.product.device") == "passion" || getprop("ro.build.product") == "passion" || getprop("ro.product.board") == "passion");
assert(getprop("ro.bootloader") == "0.33.2012" ||
getprop("ro.bootloader") == "0.33.0012" ||
getprop("ro.bootloader") == "0.35.2017" ||
getprop("ro.bootloader") == "0.35.0017");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
run_program("/tmp/backuptool.sh", "backup");
show_progress(0.500000, 0);
format("MTD", "system");
mount("MTD", "system", "/system");
show_progress(0.500000, 40);
Click to expand...
Click to collapse
After:
ui_print("Welcome to CyanogenMod-6.1.0-RC1-N1!");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
run_program("/tmp/backuptool.sh", "backup");
show_progress(0.500000, 0);
format("MTD", "system");
mount("MTD", "system", "/system");
show_progress(0.500000, 40);
Click to expand...
Click to collapse
Click to expand...
Click to collapse
If you want to learn how to sign .zips follow this thread>>> http://forum.xda-developers.com/showthread.php?t=537937
0.2:
- fixed data
- cleaned install
- audio fixed
- build.prop edits
- tethering now works
0.1:
- initial release
you know, I just started using ShadowROM and am loving it! I finally found a great AOSP rom that works wonderfully for me exactly how I want it. I really thought that I was going to stop flashing roms every day finally because I found an AOSP that I love! And then BAM, I read this thread and my choices of roms to try and test just grew 10 times larger....Thank You ID, really...Thanks >0.
Haha, no just kidding. This patch is awesome, I can't wait to start finding and testing out ROMS for other devices. Way to go ID!
Yay! Just what I have been waiting for! This stuff pretty much opens up a whole new world of tinkering for us! Thanks ID!!!
2 questions before I screw up my night:
1. given that its supposedly hard to sign files if you just have macs... would toggling signature verification in ClockworkMod do away with the need to sign the file? **** delete ****
2. If I do create a nandroid of the ROM after flashpatching it, will it be restorable as normal or do I have to flashpatch it everytime i.e. does the flashpatch get embedded in the nandroid?
Thanks
EDIT: Just noticed Q1 answered in OP
khanam said:
Yay! Just what I have been waiting for! This stuff pretty much opens up a whole new world of tinkering for us! Thanks ID!!!
2 questions before I screw up my night:
1. given that its supposedly hard to sign files if you just have macs... would toggling signature verification in ClockworkMod do away with the need to sign the file? **** delete ****
2. If I do create a nandroid of the ROM after flashpatching it, will it be restorable as normal or do I have to flashpatch it everytime i.e. does the flashpatch get embedded in the nandroid?
Thanks
EDIT: Just noticed Q1 answered in OP
Click to expand...
Click to collapse
clockworkmod recovery.img Im pretty sure it does not need a signed.zip but if you use amon_ra then you need to sign the .zip
Q2: Nandroid will restore as normal, no need to re-apply the patch.
well, i thought i edited my getprop stuff but cyanogen 6.1 from nexusone failed due to getprop bootloader =0.33.2012 and a few others...
you can also just delete the assert in the update/r script.
I THINK you can also turn off the script asserts in CWM
and sigining files on a mac is super easy.
http://www.addictivetips.com/mac-os/auto-sign-tool-for-android-developers-on-mac/
just drag and drop. easier than in ubuntu
Just tried to use this patch w/ a Droid X rom http://www.mediafire.com/file/drixq6ry6ja83oq/DX-2315-Deodexed.zip and it didn't work. ID maybe you can take a look at it when you get a chance. Thanks!
Porting the rom using the Android Kitchen works. Wifi, BT, etc... doesn't work.
touchpro247 said:
Just tried to use this patch w/ a Droid X rom http://www.mediafire.com/file/drixq6ry6ja83oq/DX-2315-Deodexed.zip and it didn't work. ID maybe you can take a look at it when you get a chance. Thanks!
Porting the rom using the Android Kitchen works. Wifi, BT, etc... doesn't work.
Click to expand...
Click to collapse
dx has that ninjablur BS
this is only for aosp roms.
touchpro247 said:
Just tried to use this patch w/ a Droid X rom http://www.mediafire.com/file/drixq6ry6ja83oq/DX-2315-Deodexed.zip and it didn't work. ID maybe you can take a look at it when you get a chance. Thanks!
Porting the rom using the Android Kitchen works. Wifi, BT, etc... doesn't work.
Click to expand...
Click to collapse
Apparently I have stayed in the Inc area too much as I was just wondering if there are kitchens like their used to be for WinMo...
es0tericcha0s said:
dx has that ninjablur BS
this is only for aosp roms.
Click to expand...
Click to collapse
Ok, I'll just add the files needed to port it then. Thanks!
es0tericcha0s said:
you can also just delete the assert in the update/r script.
I THINK you can also turn off the script asserts in CWM
and sigining files on a mac is super easy.
http://www.addictivetips.com/mac-os/auto-sign-tool-for-android-developers-on-mac/
just drag and drop. easier than in ubuntu
Click to expand...
Click to collapse
Thanks!
So, obviously, Cyanogenmod for the Nexus works. Just removed the assert from the update/r script for both the bootloader and the device. Once that was fixed
1. install rom
2. run Inc's zip
3. ziggy kernel
4. Gapps
rebooted and running.
Not sure why, but wifi isn't working with it and I've tried the Kernels recommended in the Inc Cyanogen thread.
I got lithium mod to work using patch. Thank you.
Sent from my ADR6300 using XDA App
es0tericcha0s said:
you can also just delete the assert in the update/r script.
I THINK you can also turn off the script asserts in CWM
and sigining files on a mac is super easy.
http://www.addictivetips.com/mac-os/auto-sign-tool-for-android-developers-on-mac/
just drag and drop. easier than in ubuntu
Click to expand...
Click to collapse
oh wow! thanks man!
I get error 6 in clockwork recovery. I deleted the assert. When I opened update binary it wasn't in English just symbols so I didn't no what to edit. The error report say bad line on 62. Idk lituimmod ended up not working.
Sent from my ADR6300 using XDA App
papi92 said:
I get error 6 in clockwork recovery. I deleted the assert. When I opened update binary it wasn't in English just symbols so I didn't no what to edit. The error report say bad line on 62. Idk lituimmod ended up not working.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Just leave the binary alone...
ID
I didn't touch the binary and It still wouldn't install I get the same error.
Sent from my ADR6300 using XDA App
updated 2nd post with two ways to edit the script...
papi92 said:
I didn't touch the binary and It still wouldn't install I get the same error.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
reboot recovery
Hi
Firstly, I'm new here, so please don't be too harsh
I tried to install SentinelROM into my i9305, but failed.
I followed the exact instructions by putting the ROM in my internal storage
I'm using CWM v5.5.0.4
When I chose the zip file (the ROM) using "choose zip from internal sdcard", this happened:
Code:
-- Installing: /emmc/sentinelrom_v4_75_i9305.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "
m3" || getprop("ro.build.product") == "m3" ||
getprop("ro.product.device") == "m3xx" || g
etprop("ro.build.prouct") == "m3xx" || g
etprop("ro.product.device") == "i9305" || getpro
p("ro.build.product") == "i9305" || getpr
op("ro.product.device") == "GT-I9305" || getprop
("ro.build.product") == "GT-I9305"
E:Error in /emmc/sentinelrom_v4_75_i9305.zip
(Status 7)
Installation aborted.
I copied the above information exactly as shown on my phone
FYI, I do not have external storage (micro sd card)
Please advise
Try using a newer version of CWM or use Philz Touch Recovery!
It's based on the latest build of CWM and it has extra features like touchscreen support!
Here, look for the I9395 version of it and then flash it either with Odin (or Mobile Odin) or flash the zip through CWM.
Hope it helps
Sent from my GT-I9305 using xda premium
Copy the downloaded SentinelROM zip to your Internal Storage.
Boot into your custom recovery
Back up your stock ROM
Enter custom recovery
Factory Reset and wipe Cache and Dalvik Cache
Format System Partition
Install the ROM
jjpro45 said:
Try using a newer version of CWM or use Philz Touch Recovery!
It's based on the latest build of CWM and it has extra features like touchscreen support!
Here, look for the I9395 version of it and then flash it either with Odin (or Mobile Odin) or flash the zip through CWM.
Hope it helps
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
I followed you advice and the ROM has been successfully installed on my i9305
I used Philz Touch Recovery to install it
Thank you very much!! :good::good:
This thread can now be closed :victory:
JJEgan said:
Copy the downloaded SentinelROM zip to your Internal Storage.
Boot into your custom recovery
Back up your stock ROM
Enter custom recovery
Factory Reset and wipe Cache and Dalvik Cache
Format System Partition
Install the ROM
Click to expand...
Click to collapse
Thank you, but this was exactly what I did and then the problem occurred
As it is now solved, I think the problem was due to CWM
I've successfully installed it using Philz Touch Recovery
I was afraid to post this is Development Forum because it isn´t "Development" in any way. It´s the product of several hours of comparing others work, copy´n´paste, pack/unpack Roms and a lot(!) of frustration..
You may download, test, report and, most important, fix bugs of this. Pretty please!
You are using this at your own risk. I am in no way responsible for bricks...think twice before your doing anything.
What is he talking about ?
My Goal was to get i9505 4.3 AOSP based Roms working on our i9295.
Oh! What is working ?
- Display
- Hardware Keys
- Camera (Pictures)
Nice! What´s the Problem ?
- WLan is broken (I have no Idea) -- Medar has provided a fix here -- Thank you very much!
- Video recording (nope, no Idea)
I want to try, what do I have to do ?
- Download a i9505 AOSP based Rom (4.3 of course)
- Download the Patch
- Reboot into Recovery
- Wipe Data/Factory Reset
- Install the AOSP based Rom of your choice
- Install the Patch
- Wipe Cache, -> advanced- Wipe Dalvik Cache
- Install your Gapps
- Reboot into System
- Done!
--Optional
- Get angry about the bugs
- Fix them
- Tell us
I have tested this on Cyanogenmod "cm-10.2-20131206-NIGHTLY-jfltexx" build and SlimRoms "Slim-jfltexx-4.3.build.2.2-OFFICIAL-1762" build. But it should work on more Roms.
ALL Credits for this go to :
- LeJay for the initial unofficial CM Build
- spegelius for the more up-to-date CM Build
- Cyanogenmod
- WinMerge
- Notepad++
- My Wife for her Laptop
- and in advance to anybody working on a better Version/Bug Fixes
This is so nice I'll try it, new hope for ower active
Wow, i really like the idea behind this project! Thank you so much ohwarumbloss!
Gesendet von meinem GT-I9295 mit Tapatalk
considering the s4 GPE is getting 4.4.2 now... and we are trying to get 4.3 on our 4.2 device... I think this phone has been abandoned ... We are like 3 revisions behind.
Globel said:
considering the s4 GPE is getting 4.4.2 now... and we are trying to get 4.3 on our 4.2 device... I think this phone has been abandoned ... We are like 3 revisions behind.
Click to expand...
Click to collapse
Only 2 versions, and we're scheduled to receive 4.3 on December 24. I think the 4.3 to 4.4 has been a problem because Google released them not even 6 months apart from each other, so while companies were finalizing their 4.3 versions, they dropped 4.4.
mrmartin86 said:
Only 2 versions, and we're scheduled to receive 4.3 on December 24. I think the 4.3 to 4.4 has been a problem because Google released them not even 6 months apart from each other, so while companies were finalizing their 4.3 versions, they dropped 4.4.
Click to expand...
Click to collapse
Would you be kind and reveal the source of the scheduled update for S4 Active International? Thanks.
Globel said:
considering the s4 GPE is getting 4.4.2 now... and we are trying to get 4.3 on our 4.2 device... I think this phone has been abandoned ... We are like 3 revisions behind.
Click to expand...
Click to collapse
Never cared very much about Samsung. Or HTC ... Or whatever.
I have a full functional Cyanogenmod on my HTC Wildfire (4.3) which is really old
Spegelius' build of 4.3.1 10.2 is rock stable.
What we really need is a Developer who likes outdoor activities
Greetings
Thomas
PS: spend some days on building my own CM to learn but failed, yet. But Spegelius seems to be pretty successful so let's hope the best
Sent from my GT-I9295 using xda app-developers app
Hi
Using Slim-jfltexx-4.3.build.2.2-OFFICIAL, your patch and Camera JB+ I've manage to record 480,720 and 1080p videos with no lag. The only problem that I've found so far is no wifi conection. Thanks
medar said:
Would you be kind and reveal the source of the scheduled update for S4 Active International? Thanks.
Click to expand...
Click to collapse
Sorry, I was talking about the AT&T version. I neglected to remember that this was a i9295 thread. However, considering even AT&T is getting an update out, that means Samsung had to have done the legwork already to release an update sometime soon.
It would be cool if the patch can be developed to be used with any I9505 ROM on our I9295
Wifi fix for this patch
Flash this over recovery to fix wifi.
Don't forget to click thanks.
moviecut said:
Wow, i really like the idea behind this project! Thank you so much ohwarumbloss!
Gesendet von meinem GT-I9295 mit Tapatalk
Click to expand...
Click to collapse
Thanks
I like the fact that it seems to work, slowly, but we're getting activity for our active
medar said:
Using Slim-jfltexx-4.3.build.2.2-OFFICIAL, your patch and Camera JB+ I've manage to record 480,720 and 1080p videos with no lag. The only problem that I've found so far is no wifi conection. Thanks
Click to expand...
Click to collapse
Did you try the WiFi fix provided by medar?
gtchuah said:
It would be cool if the patch can be developed to be used with any I9505 ROM on our I9295
Click to expand...
Click to collapse
4.4 needs real Development but for 4.2 and 4.3 I think, there should be a way.
I don't use Sammy anymore, CM10.2 runs fantastic on my Device.
But, for 4.2 Sammy, you may start with a backed up boot.img from i9295 and restore it after you flashed i9505 Rom. There's nothing you can lose but a lot to win. And, don't we all need a Bootloop here and there, sometimes?
Seriously, worst case would be that you need Odin to flash a working recovery after a fail. Still, it's your own risk
medar said:
Flash this over recovery to fix wifi.
Don't forget to click thanks.
Click to expand...
Click to collapse
Awesome, thanks
Nice to see this!
Sent from my GT-I9295 using xda app-developers app
@ohwarumbloss: could you include a link to medar's fix in the original posting? Otherwise I fear people won't find it when the thread grows
pen² said:
@ohwarumbloss: could you include a link to medar's fix in the original posting? Otherwise I fear people won't find it when the thread grows
Click to expand...
Click to collapse
Yes, doing it right now
I am a fan of MIUI ROM. Coming to SGS4A, there is no porting of this MIUI ROM to SGS4A anymore.
This patch comes to my delight that there may be hope. Hence, with this patch, I'm planning to flash I9505's MIUI ROM (miuiandroid_multi_jfltexx_3.12.13_jb-4.2) to I9295 and flash the patch to see whether it works or not.
However, to my dismay, when I flash the MIUI ROM with CWM 1.2, I encountered the following messages:
assert(getprop("ro.product.device") == "jflte" ||
getprop("ro.build.product") == "jflte" ||
getprop("ro.product.device") == "jfltexx" || getprop("ro.build.product") == "jfltexx" ||
getprop("ro.product.device") == "i9505" || getprop("ro.build.product") == "i9505" ||
getprop("ro.product.device") == "GT-I9505" || getprop("ro.build.product") == "GT-I9505" ||
getprop("ro.product.device") == "jgedlte" || getprop("ro.build.product") == "jgedlte" ||
getprop("ro.product.device") == "i9505g" || getprop("ro.build.product") == "i9505g" ||
getprop("ro.product.device") == "GT-I9505G" || getprop("ro.build.product") == "GT-I9505G")
The installation aborted.
What should I do? Appreciate your expert advice.
hy
I am a fan of MIUI ROM too.. please post back if u made miui working on i9295 thx
Posted this to SlimRom forums: http://forum.slimroms.net/topic/100-galaxy-s4-active/?p=4479
Anyways, got a SlimRom build done and it seems to work. Merry christmas .
gtchuah said:
I am a fan of MIUI ROM. Coming to SGS4A, there is no porting of this MIUI ROM to SGS4A anymore.
This patch comes to my delight that there may be hope. Hence, with this patch, I'm planning to flash I9505's MIUI ROM (miuiandroid_multi_jfltexx_3.12.13_jb-4.2) to I9295 and flash the patch to see whether it works or not.
However, to my dismay, when I flash the MIUI ROM with CWM 1.2, I encountered the following messages:
assert(getprop("ro.product.device") == "jflte" ||
getprop("ro.build.product") == "jflte" ||
getprop("ro.product.device") == "jfltexx" || getprop("ro.build.product") == "jfltexx" ||
getprop("ro.product.device") == "i9505" || getprop("ro.build.product") == "i9505" ||
getprop("ro.product.device") == "GT-I9505" || getprop("ro.build.product") == "GT-I9505" ||
getprop("ro.product.device") == "jgedlte" || getprop("ro.build.product") == "jgedlte" ||
getprop("ro.product.device") == "i9505g" || getprop("ro.build.product") == "i9505g" ||
getprop("ro.product.device") == "GT-I9505G" || getprop("ro.build.product") == "GT-I9505G")
The installation aborted.
What should I do? Appreciate your expert advice.
Click to expand...
Click to collapse
Here´s what you need to do :
- get a tool like 7zip to unpack your downloaded Rom
- after you extracted it, navigate to /META-INF/com/google/android
- get Notepad++ and open the "updater-script"
- delete all lines that include "assert(getprop("ro.product.device") =="
- save the "updater-script"
- use 7zip (or similar) to include
Code:
[I] -META-INF
-system
-boot.img
-file_contexts (if there is such a file)[/I]
- into one .zip File again (like i.e. myrom.zip)
- Place your zip on your SD Card...reboot into recovery...do what you have to do
Don´t forget steps from opening Post, of course.
As always, you´re all alone with this, proceed with caution and at your own risk !!!
Good luck!
spegelius said:
Posted this to SlimRom forums: http://forum.slimroms.net/topic/100-galaxy-s4-active/?p=4479
Anyways, got a SlimRom build done and it seems to work. Merry christmas .
Click to expand...
Click to collapse
Can´t wait to try that out, this is great News !!! Going to be busy with da Family but maybe 26./27. of December I´ll be ready
Merry Christmas to you all
This is what I did from the beginning:
- Using Odin3 v3.07 to flash the original "I9295XXUBMK3"
- Using Odin3 v3.07 to root with "CF-Auto-Root-jflte-jfltexx-gti9505"
- Using Odin3 v3.07 to install "CWM-Recovery-gt-i9295_v1-2"
- Extract "miuiandroid_multi_jfltexx_3.12.13_jb-4.2" and open "\META-INF\com\google\android\updater-script" with Notepad
- Deleted "assert(getprop("ro.product.device") == "jflte".....till..... "GT-I9505G");"
- Re-zip "miuiandroid_multi_jfltexx_3.12.13_jb-4.2"
- Copy "miuiandroid_multi_jfltexx_3.12.13_jb-4.2.zip" and "patch.zip" to phone's root folder
- Reboot into Recovery
- Wipe Data/Factory Reset
- Wipe Dalvik Cache
- Install "miuiandroid_multi_jfltexx_3.12.13_jb-4.2.zip"
- Wipe Data/Factory Reset
- Wipe Dalvik Cache
- Install "patch.zip"
- Wipe Data/Factory Reset
- Wipe Dalvik Cache
- Reboot
During installation:
-- Installing: /sdcard/0/miuiandroid_multi_jfltexx_3.12.13_jb-4.2.zip
Finding update package...
Opening update package...
Installing update...
Formatting system...
Installing system files...
Creating system links...
Set permission...
Update Boot image...
Install from sdcard complete.
-- Installing: /sdcard/0/patch.zip
Finding update package...
Opening update package...
Installing update...
Flasing Patch
Flashing Boot Image...
Don t forget to wipe caches!
Install from sdcard complete."
When I reboot, it just stops at the startup screen, ie, "Samsun Galaxy S4 Active I-9295" indefinitely... no bootloop whatsoever.
What went wrong? And how do I rectify that?
Thanks a million for your help.
gtchuah said:
This is what I did from the beginning:
- Using Odin3 v3.07 to flash the original "I9295XXUBMK3"
- Using Odin3 v3.07 to root with "CF-Auto-Root-jflte-jfltexx-gti9505"
- Using Odin3 v3.07 to install "CWM-Recovery-gt-i9295_v1-2"
- Extract "miuiandroid_multi_jfltexx_3.12.13_jb-4.2" and open "\META-INF\com\google\android\updater-script" with Notepad
- Deleted "assert(getprop("ro.product.device") == "jflte".....till..... "GT-I9505G");"
- Re-zip "miuiandroid_multi_jfltexx_3.12.13_jb-4.2"
- Copy "miuiandroid_multi_jfltexx_3.12.13_jb-4.2.zip" and "patch.zip" to phone's root folder
- Reboot into Recovery
- Wipe Data/Factory Reset
- Wipe Dalvik Cache
- Install "miuiandroid_multi_jfltexx_3.12.13_jb-4.2.zip"
- Wipe Data/Factory Reset
- Wipe Dalvik Cache
- Install "patch.zip"
- Wipe Data/Factory Reset
- Wipe Dalvik Cache
- Reboot
During installation:
-- Installing: /sdcard/0/miuiandroid_multi_jfltexx_3.12.13_jb-4.2.zip
Finding update package...
Opening update package...
Installing update...
Formatting system...
Installing system files...
Creating system links...
Set permission...
Update Boot image...
Install from sdcard complete.
-- Installing: /sdcard/0/patch.zip
Finding update package...
Opening update package...
Installing update...
Flasing Patch
Flashing Boot Image...
Don t forget to wipe caches!
Install from sdcard complete."
When I reboot, it just stops at the startup screen, ie, "Samsun Galaxy S4 Active I-9295" indefinitely... no bootloop whatsoever.
What went wrong? And how do I rectify that?
Thanks a million for your help.
Click to expand...
Click to collapse
The Kernel inside the "Patch.zip" is a 4.3 Kernel.
But you try to use a Miui port based on a 4.2..
This means you need another Kernel.
One way could be to backup your Galaxy S4 active Sammy ROM after you flashed CWM recovery, then install the Miui port, go straight back to ->backup & restore ->advanced restore->choose your backup and restore "boot.img".
Then wipe cache & dalvik cache and reboot.
This may work, it should, but there is no guarantee.
Good luck
Sent from my GT-I9295 using xda app-developers app
I've sucessfully flashed several ROMs to my htc One m7ul, I've followed the convert your device to a google plus edition changing my model name and I've been able to install other m7ul based roms on my device (AOKP for example) but when i download the pacman roms from the official Pacman site under their Other and Stable section for the m7ul and try to install it (after making a wipe) i get the following in my log:
+------------------------------------------------------------------------------------------------+
Installing '/sdcard/Download/pac_m7ul_4.3-build(rest cut off?)
Checking for MD5 file . . .
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.product.device") == (rest cut off?)
getprop("ro.product.device") == "m7ul" | (rest cut off?)
E: Error excuting updater binary in zip '/sdcar (rest cut off?)
Error flashing zip '/sdcard/Download/pac_m7ul_4 (rest cut off?)
Updating partition details . . .
+------------------------------------------------------------------------------------------------+
the "(rest cut off)" being where i think theres more text to the error but due to the screen formatting it looks like its being cut, I'm using TWRP recovery, have an unlocked bootloader and have s-off, Can anyone help me?
I've been able to install the ROM by using AndroidKitchen to extract the updater-script and edit it. The homescreen is very buggy, no wallpaper display, bootloop issues. I'm Changin the kernels to try and help but im not sure if this is a rom issue or a kernel issue. Does anyone have this ROM installed? and if so what kernel are you using?
All the steps below are done at your OWN risk, and I take no responsibility blah blah blah
I will use explicit directory names and have referred to using Notepad++ and 7Zip. Both of which are free. But are not important to the actual process, just simplify the explanation for me. I will also be using Windows.
Both the above assumptions can be easily transferred to their UNIX or Mac equivalents.
1. Download the latest build from Lineage for the XT897
https://download.lineageos.org/xt897
2. Extract a copy of the file "/system/build.prop"
3. Open the build prop in a text editor
4. Do a global Find & Replace (case sensitive just to be sure)
xt897 to xt907
XT897 to XT907
5 Add and / or replace the following lines into the build prop (location in the file is not important, I personally add any new to the end and replace the values for existing)
Code:
ro.hdmi.enable=false
ro.cm.device=xt907
ro.product.device=RAZR M
ro.product.name=XT907
ro.build.product=scorpion_mini
ro.product.model=RAZR M
ro.boot.modelno=XT907
6. extract the attached vendor_motorola_xt907_proprietary.zip to C:\temp\xt907\
you should now have the directory structure of:
Code:
c:\temp\xt907\etc\firmware\
within the last directory should be two files
atmxt-r1.tdat
atmxt-r2.tdat
7. Add the etc\firmware directories at c:\temp\xt907\ to the zip, under the system directory.
you should now have within the zip
Code:
\system\
build.prop
\etc\firmware\
atmxt-r1.tdat
atmxt-r2.tdat
8. extract "\META-INF\com\google\android\updater-script" file from the zip to c:\temp\xt907\
9. Open the "c:\temp\xt907\updater-script" file in your text editor
NB: when editing this file, I would ensure that all line endings are "newline" not "CR-NL". In Notepad++ do a replace of "\r\n" with "\n"
10. Change the first line
FROM:
Code:
[COLOR="Red"][strike]assert(getprop("ro.product.device") == "xt897" || getprop("ro.build.product") == "xt897" || getprop("ro.product.device") == "asanti_c" || getprop("ro.build.product") == "asanti_c" || abort("This package is for device: xt897,asanti_c; this device is " + getprop("ro.product.device") + "."););[/strike][/COLOR]
TO:
Code:
[COLOR="SeaGreen"][B]assert(getprop("ro.product.device") == "moto_msm8960_jbbl" || getprop("ro.build.product") == "moto_msm8960_jbbl" || getprop("ro.product.device") == "xt907_jbbl" || getprop("ro.build.product") == "xt907_jbbl" || getprop("ro.product.device") == "xt901" || getprop("ro.build.product") == "xt901" || getprop("ro.product.device") == "solstice" || getprop("ro.build.product") == "solstice" || getprop("ro.product.device") == "xt905" || getprop("ro.build.product") == "xt905" || getprop("ro.product.device") == "smq_u" || getprop("ro.build.product") == "smq_u" || getprop("ro.product.device") == "scorpion_mini_u" || getprop("ro.build.product") == "scorpion_mini_u" || getprop("ro.product.device") == "XT907_JBBL" || getprop("ro.build.product") == "XT907_JBBL" ||getprop("ro.product.device") == "Moto Razr M" || getprop("ro.build.product") == "Moto Razr M" || getprop("ro.product.device") == "scorpion_mini" || getprop("ro.build.product") == "scorpion_mini" || abort("This package is for device: moto_msm8960_jbbl,xt901,solstice,xt905,smq_u,scorpion_mini_u,xt907_jbbl,scorpion_mini; this device is " + getprop("ro.product.device") + "."););[/B][/COLOR]
11. Add the following lines to the end of the updater-script file
Code:
ifelse(is_mounted("/system"), unmount("/system"));
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
package_extract_dir("system", "/system");
unmount("/system");
12. Save the file (take note of NL characters for line ending), & replace the one in the zip that you originally extracted it from ie "\META-INF\com\google\android\updater-script"
13. Rename the zip from something like "lineage-13.0-20170325-nightly-xt897-signed.zip" to "lineage-13.0-20170325-nightly-xt907-PORTED.zip"
14. reboot to TWRP
15. Make a backup!!!
16. Do a clean install and flash the appropriate GApps
17. Reboot & enjoy
Lineage do a weakly build for the XT897, and I think I previously use to dirty flash the ones I made. You can also see the change logs etc for the XT897 to know what to expect.
I have started to build my own XT905/XT907 ROMS from the source for the XT897, so it has been a while sionce I did the above, but I have modified the source to basically do the above steps. I actually still do the build prop file manually as its easier than modifying/maintaining the source. I also think you should be able to dirty flash it over an existing ZIP that was built using the above system.
Hi there. I've got a Razr M (XT907) that I used as my daily phone. It's currently running a nightly build of CyanogenMod 12.1 on Android Version 5.1.1.
Was looking through these instructions and two quick questions.
Main one -- I understand this post is a few months old, but this write-up seems to be for Lineage 13.0 whereas the newest version of the Lineage nightly is 14.1. Is that [significantly] relevant?
Also, "qtmxt-r1.tdat" and "qtmxt-r2.tdat" don't exist in my \etc\firmware directory, though an "atmxt-r1.tdat" and "atmxt-r2.tdat" do. Is that just a typo?
Kudos in advance!
-Dan
ProoN said:
Main one -- I understand this post is a few months old, but this write-up seems to be for Lineage 13.0 whereas the newest version of the Lineage nightly is 14.1. Is that [significantly] relevant?
Click to expand...
Click to collapse
I haven't explicitly checked, but the steps are the same. The only thing that may of changed is you should also search the build.prop for "asanti"/"asanti_c" or such and change to "scorpion_mini" and also check for "PHOTON Q" and change to "RAZR M". Also check that there are no duplicates of the build.prop's I added at the end.
I currently build my own LOS13 from source, so haven't performed the above since they switched to Nougat; maybe once when they first switched. Without the customisations of Xposed, LOS is to vanilla for me.
ProoN said:
Also, "qtmxt-r1.tdat" and "qtmxt-r2.tdat" don't exist in my \etc\firmware directory, though an "atmxt-r1.tdat" and "atmxt-r2.tdat" do. Is that just a typo
Click to expand...
Click to collapse
Typo corrected. thanks.
I also improved/updated step 11
And also realised the GAPPS should now be for 7.x
Alriiiiight. So, I've got the latest nightly build of Lineage OS, edited all files according to the instructions up there and am ready to *try* to install/flash this onto my device.
The XT907 is currently running a nightly build of CyanogenMod 12.1 on Android 5.1.1.
From how it sounds, I just need to boot into recovery (I've got TWRP) and install via micro SD, correct? It just installs atop CyanogenMod? I'm not really sure how it works.
This is my daily phone and I just don't want to mess anything up.
ProoN said:
Alriiiiight. So, I've got the latest nightly build of Lineage OS, edited all files according to the instructions up there and am ready to *try* to install/flash this onto my device.
The XT907 is currently running a nightly build of CyanogenMod 12.1 on Android 5.1.1.
From how it sounds, I just need to boot into recovery (I've got TWRP) and install via micro SD, correct? It just installs atop CyanogenMod? I'm not really sure how it works.
This is my daily phone and I just don't want to mess anything up.
Click to expand...
Click to collapse
What version of TWRP do you have? An older version wont be able to flash the latest ROMs
Are you running the JBBL?
1st you need to make a nandroid (ie BACKUP) of everything you have
Wipe cache, dalvik, data & system (you do not need to wipe internal SD)
Then flash the LineageOS zip file
Then flash the correct (ie same) version of GApps (I use OpenGapps pico personally) 7.x if you have latest LineageOS
Then flash your chosen method for root (optional, either Masgisk or SuperSU, I personally prefer Magisk but have not tested either with LOS 14.1 I run LOS 13.0)
Then reboot. Give it 10min to boot the first time.
If it fails, restore your backup.
Good luck.
I keep backups of all my data, generally once a week or so. Data loss on the device isn't a huge deal, I'm more concerned about the phone itself being inoperable once I [attempt to] flash Lineage onto it, lol.
My device is currently running TWRP v2.8.5.0. And if I remember correctly, any later versions of it wouldn't work for some reason -- I tried a few. Though, I haven't tried any other recovery programs as this version of TWRP worked fine for flashing CyanogenMod on here at the time (2015..)
Also, I'm not sure what JBBL is .. exactly.
Kudos for the quick replies though, much appreciated.
ProoN said:
I keep backups of all my data, generally once a week or so. Data loss on the device isn't a huge deal, I'm more concerned about the phone itself being inoperable once I [attempt to] flash Lineage onto it, lol.
Click to expand...
Click to collapse
If you take backups (nandroid and sdcard etc), this phone seems pretty safe to flash ROM zips through TWRP (but never say never... and it is possible if someone gives you a zip explicitly trying to kill your phone)
ProoN said:
My device is currently running TWRP v2.8.5.0. And if I remember correctly, any later versions of it wouldn't work for some reason -- I tried a few. Though, I haven't tried any other recovery programs as this version of TWRP worked fine for flashing CyanogenMod on here at the time (2015..)
Click to expand...
Click to collapse
I am pretty sure you will need to update TWRP again to flash these newer ROMs. For the latest see: https://forum.xda-developers.com/droid-razr-m/general/twrp-3-1-1-xt907jbbl-t3652141
ProoN said:
Also, I'm not sure what JBBL is .. exactly.
Click to expand...
Click to collapse
If you haven't taken the KitKat OTA or flashed the update manually, then chances you are on a JBBL (ie JellyBean Bootloader). Unless you bought the phone with KitKat pre-installed.
The phone was completely stock when I got it. There was a thread on here on how to unlock the bootloader, flash custom recoveries and OS's which is how I managed to get CM installed. How can I tell if JBBL is on here? Also, which version of Gapps would work for what I'm trying to do? (Lineage 14.1 on Android 5.1.1)
Sorry for so many questions. Kudos once again for the replies
ProoN said:
How can I tell if JBBL is on here?
Click to expand...
Click to collapse
"Settings > About phone > Kernel version" then search and read XDA ( eg https://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
https://forum.xda-developers.com/showthread.php?t=2226729
https://forum.xda-developers.com/showthread.php?t=2758398
https://forum.xda-developers.com/showthread.php?t=2345558)
ProoN said:
Also, which version of Gapps would work for what I'm trying to do? (Lineage 14.1 on Android 5.1.1)s
Click to expand...
Click to collapse
Lineage 14.1 is Nougat. Nougat is 7.X so you would get that (eg ARM, 7.1, PICO from open gapps)
Will flashing Lineage OS on here update the Android system entirely from 5.1.1 to 7.x.x? I guess that's my main confusion here.
ProoN said:
Will flashing Lineage OS on here update the Android system entirely from 5.1.1 to 7.x.x? I guess that's my main confusion here.
Click to expand...
Click to collapse
You are OT,best to ask your question here https://forum.xda-developers.com/showthread.php?t=2259645
Alright. So here's a not-so-newbie question. I went ahead and updated TWRP from v2.8.5.0 to v3.1.1-0 -- it was on another thread you had posted (the JBBL version seems to work on mine.)
Instead of trying to flash Lineage 14.1, I went along with the instructions for 13.0, edited the files and parameters accordingly, booted into TWRP and tried to install via zip and am getting this error
"Invalid zip file format!"
"Error installing zip file '/sdcard/lineage-13.zip"
Also have a copy of the zip file on the external_sd which reports the same error. I've tried this on both Windows and OSX with different zip programs and get the same error. Not sure what's happening here.
ProoN said:
Also have a copy of the zip file on the external_sd which reports the same error. I've tried this on both Windows and OSX with different zip programs and get the same error. Not sure what's happening here.
Click to expand...
Click to collapse
So, clearly your zip file is corrupted by your doing/zip application, not the actual steps I have above. I personally use 7Zip (freeware), and have had no corrupted zips issues. And it actually is a pretty newbie question If you want help, put the actual TWRP log up here, what you have posted tells us nothing.
Alright, making progress here. ..kind of.
I was originally extracting the archive entirely, editing and moving where necessary and then re-zipping. I'm not entirely sure why that method doesn't work when trying to install, but it doesn't.
So yeah. I've got TWRP 3.1.1-0 on my device now (JBBL version.) I followed the steps above as far as I'm aware but am getting a different error now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I used Notepad++ as well, though there wasn't a single instance of \r\n that was replaced when following the instructions
ProoN said:
Alright, making progress here. ..kind of.
I was originally extracting the archive entirely, editing and moving where necessary and then re-zipping. I'm not entirely sure why that method doesn't work when trying to install, but it doesn't.
So yeah. I've got TWRP 3.1.1-0 on my device now (JBBL version.) I followed the steps above as far as I'm aware but am getting a different error now.
[SCREENSHOT]Sheeze! a link to the image or a little bit of a trim may of been in order. There is actually a feature under "Advanced" (I think) to copy the log to your SDCard (ie as text)
Click to expand...
Click to collapse
The line "This package is for devices with a 4.1 bootloader" is basically telling you that you do not have a JBBL. ie you have a KKBL.
JBBL=4.1
KKBL=4.4.2
If you search these forums, there have been recent posts regarding installation zips (ie flashable) that can switch you back and forth between JBBL and KKBL for an xt907. eg https://forum.xda-developers.com/showpost.php?p=73317190&postcount=13
ProoN said:
I was originally extracting the archive entirely, editing and moving where necessary and then re-zipping. I'm not entirely sure why that method doesn't work when trying to install, but it doesn't.
Click to expand...
Click to collapse
FYI: some of the reasons it could fail include (but are not limited to): Re-ziping can change the compression method (ie from simple STORE to compressed) and the zip file may (I dont think this one does) include some files which are case sensitive, while if re-zipped on Windows, chances are you are not on a case sensitive file system.
I did a quick look over...but I might have missed it. Does any of this required an unlocked bootloader? Mine is currently locked.
DragonFire1024 said:
I did a quick look over...but I might have missed it. Does any of this required an unlocked bootloader? Mine is currently locked.
Click to expand...
Click to collapse
Look, read and think. The answer is staring you in the face.
Is there any chance you could upload a copy of the zip you managed to port to the XT907? I've tried this several times on XP and Windows 7 with WinRAR and 7Zip. I can't get it to work at all.
ProoN said:
Is there any chance you could upload a copy of the zip you managed to port to the XT907? I've tried this several times on XP and Windows 7 with WinRAR and 7Zip. I can't get it to work at all.
Click to expand...
Click to collapse
are you talking MM or N? Are you getting errors in TWRP? if so, what? and please dont post a screen shot/photo, copy the log in TWRP to your SD (an option in twrp) and post the text