Hello everyone!
I just found a temporary solution to the soft reboot problem when using Google Maps.
After searching I found this on a Galaxy Tab 7 forum, and decided to try it out... and it works!!!
I extracted and pushed the file manualy to the lib folder (fixing the permissions, of course)... and it work like a charm!
No more soft reebots.
Note I use the 6.14.4 version of Google Maps
I tested this solution on this following rom's:
[ROM][JB4.2.2][unofficial]PAC-man ROM v22.2.0 [BETA][CM/AOKP/PA]~12-05-13~
[ROM] [JB 4.2.2 JDQ39E] CM10.1 Beta 6 --- Kernel 3.4
[ROM] [JB 4.2.2 JDQ39] Unofficial ROOT-BOX Beta 6 --- kernel 3.4
I hope my solution helps everyone until this problem gets a more final fix.
Enjoy!!!
View attachment libsensorservice.zip
IMPORTANT! I remove the flashble zip and added a new one. Extract and push it manualy to \system\lib and change the permissions to (rw-r--r--)
THIS IS NOT A FLASHABLE ZIP
IF YOU PREFER A FLASH ZIP YOU CAN FIND IT HERE.. many thanks to Krislibaeer that made this file!!!
http://forum.xda-developers.com/showpost.php?p=41485703&postcount=12
(If it helped you, please press thanks)
thanks for that now i know where the problem is
the new changes to get gyroscope/photosphere working on other devices then google devices breaks gmaps and other apps like this
I see that its flashable
But with you file and source got failed
As he wrote, you must change this file manually, ZIP is only a source of the correct lib.
sv2hqx said:
I see that its flashable
But with you file and source got failed
Click to expand...
Click to collapse
thats the wrong updater script
Code:
assert(getprop("ro.product.model") == "GT-P3100" ||
getprop("ro.product.name") == "espressorfxx" ||
getprop("ro.product.device") == "espressorf" ||
getprop("ro.product.model") == "GT-P3110" ||
getprop("ro.product.model") == "GT-P3113" ||
getprop("ro.product.name") == "espressowifixx" ||
getprop("ro.product.device") == "espressowifi" ||
getprop("ro.product.model") == "GT-P5100" ||
getprop("ro.product.name") == "espresso10rfxx" ||
getprop("ro.product.device") == "espresso10rf" ||
getprop("ro.product.model") == "GT-P5110" ||
getprop("ro.product.model") == "GT-P5113" ||
getprop("ro.product.name") == "espresso10wifixx" ||
getprop("ro.product.device") == "espresso10wifi");
mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
package_extract_dir("system", "/system");
set_perm(0, 0, 0644, "/system/lib/libsensorservice.so");
unmount("/system");
i provide a new one
do not flash this it can cause damages on the phone
please take the link down
I've just tried to replace "libsensorservice.so" that you provided in "/system/lib/" and the phone doesn't reboot anymore. I have to come back to my backup!
I have upgraded to PAC-Man v22.2.0 and in recovery after the fresh installation I copied the file to the right location (zip didn't worked for me too).
I am trying right now...
gMaps and Ingress works
SFCMouco said:
Hello everyone!
I just found a temporary solution to the soft reboot problem when using Google Maps.
After searching I found this forum http://forum.xda-developers.com/showpost.php?p=40701377&postcount=2090 and decided to try it out... and it works!!!
I extracted and pushed the file manualy to the lib folder (fixing the permissions, of course)... and it work like a charm!
No more soft reebots.
Note I use the 6.14.4 version of Google Maps
I tested this solution on this foluing rooms:
[ROM][JB4.2.2][unofficial]PAC-man ROM v22.2.0 [BETA][CM/AOKP/PA]~12-05-13~
[ROM] [JB 4.2.2 JDQ39E] CM10.1 Beta 6 --- Kernel 3.4
[ROM] [JB 4.2.2 JDQ39] Unofficial ROOT-BOX Beta 6 --- kernel 3.4
I hope my solution helps everyone until this problem gets a more final fix.
Enjoy!!!
View attachment 1966705
(If it helped you, please press thanks)
Click to expand...
Click to collapse
Worked for me. Pushed the lib-file to the /system/lib directory. Set permissions to 644. Downloaded the newest Google MAPS. Working like hell ....... :good:
dece27 said:
I've just tried to replace "libsensorservice.so" that you provided in "/system/lib/" and the phone doesn't reboot anymore. I have to come back to my backup!
Click to expand...
Click to collapse
nevertheless thanks again to show this post to get fixed the issue
i upload the new file now it is compiled with carbon source so try and give feedback --> few minutes it is ready
gmaps_fix
sv2hqx said:
I see that its flashable
But with you file and source got failed
Click to expand...
Click to collapse
Dont flash the zip file... I take that one down and put a new one. Just extract the file and push manuly the file changing the permissions to rw-r--r--
I push it manually and works
Updated maps too and works perfect
SFCMouco said:
Dont flash the zip file... I take that one down and put a new one. Just extract the file and push manuly the file changing the permissions to rw-r--r--
Click to expand...
Click to collapse
here i made a flashable zip gmaps_fix
krislibaeer said:
here i made a flashable zip gmaps_fix
Click to expand...
Click to collapse
Does this work with your AOKP rom?
krislibaeer said:
here i made a flashable zip gmaps_fix
Click to expand...
Click to collapse
Good work! I've flashed on CM 10.1 Beta 6.1 by davidteri91 and it works very well; thanks a lot
Melombine said:
Does this work with your AOKP rom?
Click to expand...
Click to collapse
If you use the now flash file and push it manualy... Yes it does!
SFCMouco said:
If you use the now flash file and push it manualy... Yes it does!
Click to expand...
Click to collapse
Yeah, works like charm! Thanks, because I really have use for the Google Maps now that I have my driving licence
Thanks!
Inviato dal mio GT-P3110 con Tapatalk 2
"Just extract the file and push manuly the file changing the permissions to rw-r--r--"
Well, flashable zip works, but how can i change the permission. I have root explorer and can do that in system but not on my sd card because I have to do it because when i copied without changing permission I have a reboot and have to restore a Backup or flash the zip.
Someone knows how to copy it manually? Thanks.
Thanksss!
Enviado desde mi MB526 usando Tapatalk 2
KingKuno said:
"Just extract the file and push manuly the file changing the permissions to rw-r--r--"
Well, flashable zip works, but how can i change the permission. I have root explorer and can do that in system but not on my sd card because I have to do it because when i copied without changing permission I have a reboot and have to restore a Backup or flash the zip.
Someone knows how to copy it manually? Thanks.
Click to expand...
Click to collapse
with my flashable zip it fix the permission and all works well
just the other flashable zip had a wrong updater-script
Related
Hi all,
Not sure whether anyone ever created this, whether it already exists, or even whether it's useful, but nevertheless I **proudly** present to you:
Building an ODIN package using a cwm-installable script!
If you want to do it using ADB (either through dos or cygwin), please go to this topic:
The making of ... an ODIN installable package
Simple, single step, effective and based on the original files of XXKPS (adsp.mbn, amss.mbn, cache.img.ext4, preload.img.ext4) running this zip will create an Odin package.
It takes only 6 to 7 minutes to build the file!
It does not include the cache or preload of your ROM (so your data is safe when distributing these files as far as I know!!).
This way you can easily share any ROM you have created by combining parts of other ROMs. For instance, if you installed Cranium ROM, added Feamod to it, did the 14-button mod and added the ICS mod too - build the Odin md5 zip with this package and share your custom modded ROM with the community!!
Download
XXKPS or XXKPS - thanks broodPlank!
XXKPU - thanks broodPlank!
XXKQ1 - thanks broodPlank!
XXKQ7 - thanks broodPlank!
XXKQB or XXKQB - thanks broodPlank!
XXKQE - thanks broodPlank!
XXKQI - thanks broodPlank!
DXLD3 - thanks [FONT="]somboons!
[/FONT] ** Please upload this file to mirrors and post them when available
Instructions
Please make sure you have installed Feamod Recovery
Build your ROM, add all mods, make it the way you want to share it
Check whether the internal sdcard has enough space (at least 2 GB)
Copy the zip to your internal or external sdcard
Reboot into recovery (Poweroff, then press Vol-Up and Poweron)
Select "install zip from sdcard" and browse to the location you used in step 4
Select the zip... it will start building the Odin package immediately
Please allow the system to build the zip in step 7 - this will take several minutes!
Other Stock ROMs
Like broodPlank did, you can also make a CWM installer for Odin packages that create other Stock ROMs:
Download BuildOdinCWM-noBaseRom.zip
Download the Stock ROM of your choice
Extract the following files from the Stock ROM:
adsp.mbn
amss.mbn
cache.img.ext4
preload.img.ext4
Click to expand...
Click to collapse
Zip all files and folders back up and ready
If you want to use another name for your new Odin package, please replace "MyOdinpack" with whatever name you like the following files in the scripts folder:BuildOdin.sh
MD5Odin.sh(make sure to use a text editor that can handle Unix files like Notepad++ or UltraEdit)
Please share your new creations, like broodPlank did
Enjoy!!
Regards,
Nika.
If anyone has an idea how to check from a shell or cwm script:
* Check for free diskspace
* Check for files already available, to avoid overwrite (preferably with choice to remove or backup files)
It would be much appreciated. If you have seen cwm script on other devices that can do that kind of stuff, just let me know and I'll check them out myself
Regards,
Nika.
that's very helpful and should save time spent on transferring cwm backup to pc and doing everything manually but u should've just added it to the OP of the other "making of an odin file" thread, we'd still pump up ur thanks meter u don't have to worry . opening new threads for every lil thing just causes pollution (no hard feelings)
rayiskon said:
that's very helpful and should save time spent on transferring cwm backup to pc and doing everything manually but u should've just added it to the OP of the other "making of an odin file" thread, we'd still pump up ur thanks meter u don't have to worry . opening new threads for every lil thing just causes pollution (no hard feelings)
Click to expand...
Click to collapse
I really don't care about the thanks meter, trust me. I decided to do it this way to avoid making the other thread too complex. Will add a reference in the OP of the other thread though and one in this to make sure others know where to go if they want to do this through adb...
Very nice! This will save me allot of time . Very nice post again nikagl, you make allot of handy scripts!
Hey, I made the XXKPU version (because I'm using XXKPU now for broodROM RC3) of your awesome flashable:
http://www.mediafire.com/?4c7y7p9o43uhj68
broodplank1337 said:
Hey, I made the XXKPU version (because I'm using XXKPU now for broodROM RC3) of your awesome flashable:
http://www.mediafire.com/?4c7y7p9o43uhj68
Click to expand...
Click to collapse
Thanks! Added it to OP. Just wondering, would it make a difference? What are these files for anyway (adsp.mbn, amss.mbn, cache.img.ext4 and preload.img.ext4? There's hardly any difference as far as I can see (mounted ext4)
Still thinking of making a tool that converts the actual cwm files others post (ie. the actual system files) into an Odin package directly but didn't yet find a way to create an ext4 file other than by dd-dumping it
nikagl said:
Thanks! Added it to OP. Just wondering, would it make a difference? What are these files for anyway (adsp.mbn, amss.mbn, cache.img.ext4 and preload.img.ext4? There's hardly any difference as far as I can see (mounted ext4)
Still thinking of making a tool that converts the actual cwm files others post (ie. the actual system files) into an Odin package directly but didn't yet find a way to create an ext4 file other than by dd-dumping it
Click to expand...
Click to collapse
I have no clue what adsp.mbn, amss.mbn and preload.img.ext4 are for but I know that cache.img.ext4 has the CSC Configuration inside, I tweaked the sec_csc.zip file and inserted custom apps, it worked
Changed the updater script to this (commented lines because this is a test)
# assert(getprop("ro.product.device") == "GT-P1000" ||
# getprop("ro.build.product") == "GT-P1000" ||
# getprop("ro.product.device") == "GT-I9000" ||
# getprop("ro.build.product") == "GT-I9000" ||
# getprop("ro.product.device") == "SC-02B" ||
# getprop("ro.build.product") == "SC-02B" ||
# getprop("ro.product.device") == "GT-I9003" ||
# getprop("ro.build.product") == "GT-I9003" ||
# getprop("ro.product.device") == "GT-I9001" ||
# getprop("ro.build.product") == "GT-I9001"
# );
ui_print("*** Mounting /system and /data... ***");
show_progress(0.250000, 0);
mount("ext4", "EMMC", "/dev/block/mmcblk0p15", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p17", "/data");
ui_print("*** Installing CSC Data... ***");
show_progress(0.500000, 0);
# mount("ext4", "EMMC", "/dev/block/mmcblk0p15", "/system");
# package_extract_dir("system", "/system");
ui_print("*** Installing Additional Apps... ***");
show_progress(0.750000, 0);
package_extract_dir("data", "/data");
show_progress(0.1000000, 0);
ui_print("*** Unmounting /system and /data... ***");
unmount("/system");
unmount("/data");
ui_print("Done...");
Click to expand...
Click to collapse
Installs CSC and 2 extra apps
I will test it first after a stock install but if it works fine I will integrate it into broodROM RC3, so I can add extra apps without having them to be system apps
And for creating .ext4 files, if you use DiskInternals Linux Reader you can save it as .img but if you just choose .img.ext4 and verify the file afterwards it seems to be an correct file (haven't tested it tho)
Uploading both packages to sourceforge.net
edit:
http://sourceforge.net/projects/bro...ckage in CWM/BuildOdinCWM-nikagl.zip/download
and
http://sourceforge.net/projects/bro...in CWM/BuildOdinCWM_XXKPU-nikagl.zip/download
Those mbn should be modem binaries.
Sent from my GT-I9001 using XDA App
Made a new one for XXKQ1
http://sourceforge.net/projects/bro...in CWM/BuildOdinCWM_XXKQ1-nikagl.zip/download
All versions can be found here:
https://sourceforge.net/projects/broodrom/files/Build Odin package in CWM/
broodplank1337 said:
Made a new one for XXKQ1
http://sourceforge.net/projects/bro...in CWM/BuildOdinCWM_XXKQ1-nikagl.zip/download
All versions can be found here:
https://sourceforge.net/projects/broodrom/files/Build Odin package in CWM/
Click to expand...
Click to collapse
added them
nikagl said:
added them
Click to expand...
Click to collapse
Good I think sourceforge is a really nice host for such things, always location near you for whole europe
broodplank1337 said:
Good I think sourceforge is a really nice host for such things, always location near you for whole europe
Click to expand...
Click to collapse
Agree although i wonder how long they will allow it as these are not really sources...
nikagl said:
Agree although i wonder how long they will allow it as these are not really sources...
Click to expand...
Click to collapse
Yeh, I had that in mind to, but there are many roms and (actually closed source) files hosted on sourceforge. They don't seem to care that much
Can't you just create a backup and flash it with odin?
Sent from my GT-I9001 using xda premium
FlorisNL said:
Can't you just create a backup and flash it with odin?
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
nope it's not that easy, its still easy tho. use the CWM method or dump/tarball/md5sum the partitions yourself
broodplank1337 said:
nope it's not that easy, its still easy tho. use the CWM method or dump/tarball/md5sum the partitions yourself
Click to expand...
Click to collapse
Well... I guess it should be possible, but it will take just as long and you'll need to move the files, rename them, replace some with the stock (empty) files to avoid data into the odin package, and add the others. Then tar/md5 them and in the end you'd have the Odin package... sounds to me the cwm-method from this thread is much easier
nikagl said:
Well... I guess it should be possible, but it will take just as long and you'll need to move the files, rename them, replace some with the stock (empty) files to avoid data into the odin package, and add the others. Then tar/md5 them and in the end you'd have the Odin package... sounds to me the cwm-method from this thread is much easier
Click to expand...
Click to collapse
Yup, thats true. I will use this method for my Custom Rom
Sent from my GT-I9001 using xda premium
I have deodexed XXQ1 atm, if i follow this post, i can have a md5 Odin file to share XXQ1 Deodexed with others?
PD: The file called "MyOdinpack.tar.md5" into BuildOdin folder, its the md5 image to flash via Odin?
alexis! said:
I have deodexed XXQ1 atm, if i follow this post, i can have a md5 Odin file to share XXQ1 Deodexed with others?
PD: The file called "MyOdinpack.tar.md5" into BuildOdin folder, its the md5 image to flash via Odin?
Click to expand...
Click to collapse
Yep thats the package
Tried Searching using string - assert failed: getprop("ro.product.device") == "GT-S5830" with no luck so time to create post.
What i have done already.
I have downloaded and installed kies updated firmware to Gingerbread 2.3.6.
I have put ClockWorkMod 4.0.0.9 (forum.xda-developers.com/showthread.php?t=1168417)
Now i try to root fone via recovery following steps E on Hubix Thread (forum.xda-developers.com/showthread.php?p=12874680), downloaded upd_1.zip put on root of SD card searched for it using the "install zip from SD card" option within CWM, when i press to install i get an error
Opening Update Package...
Installing Update...
assert failed: getprop("ro.product.device") == "GT-S5830" || getprop("ro.build.product") == "GT-S5830" || getprop("ro.product.device") == "GT-S5570" || getprop("ro.build.product") == "GT-S5570" || getprop("ro.product.device") == "GT-S5670" || getprop("ro.product.product") == "GT-S5670" || getprop("ro.product.device") == "GT-B7510" || getprop("ro.product.product") == "GT-B7510"
E:Error in /sdcard/upd_1.zip
(status 7)
Installation aborted.
Click to expand...
Click to collapse
My phone details are
Model Number: GT-S5830
Android Version: 2.3.6
Baseband Version: S5830NEKT2
Kernel Version: 2.6.35.7-perf-CL772922 [email protected] #1
Build Number: GINGERBREAD.XWKT5
Click to expand...
Click to collapse
Hope thats enough information, any ideas how to solve the problem?
Thankyou in advance
maybe its a corrupt file or something? I'd download that file again and try again if you haven't already. I know sometimes you have to try installing superuser around 3 times for some phones using CWM so maybe you have to do that also?
PakAttack1994 said:
maybe its a corrupt file or something? I'd download that file again and try again if you haven't already. I know sometimes you have to try installing superuser around 3 times for some phones using CWM so maybe you have to do that also?
Click to expand...
Click to collapse
Tried a few times now even, downloaded gganon's root.zip file (forum.xda-developers.com/showthread.php?t=1282011) with no luck. Ill charge up the laptop and try from there just in case my PC is screwing something up.
Ok so im on laptop now tried downloading the various .zip files and tried installing 5 times per zip and still get the problem that is shown in my first post, any other ideas ?
It mentions that if Step E doesn;t work, try step D. If that doesnt work, try the link below and install "AceGingerRoot.zip" instead of “upd_1.zip”, as described in the link...let me know what happens.
http://acetips.wordpress.com/2011/09/29/root-ace-froyo-gingerbread/
or if that doesnt work, try this....
http://forum.xda-developers.com/showthread.php?t=1282011
PakAttack1994 said:
It mentions that if Step E doesn;t work, try step D. If that doesnt work, try the link below and install "AceGingerRoot.zip" instead of “upd_1.zip”, as described in the link...let me know what happens.
http://acetips.wordpress.com/2011/09/29/root-ace-froyo-gingerbread/
or if that doesnt work, try this....
http://forum.xda-developers.com/showthread.php?t=1282011
Click to expand...
Click to collapse
AceGingerRoot.zip worked perfectly thanks for all your help
------------------------------------------------------------------------------
Edit: Now get same problem when trying to install custom ROM forum.xda-developers.com/showthread.php?t=1360889 any ideas ?
Edit2: Nevermind updated CWM to 5.0.2.6 and install went fine
awesome, glad it worked.
Please reup AceGingerRoot.zip. The one I have found can't root my ace. And all of them are 980kb. But AceGingerRoot.zip that has been posted here is about 1000kb
AceGingerRoot.zip
PakAttack1994 said:
It mentions that if Step E doesn;t work, try step D. If that doesnt work, try the link below and install "AceGingerRoot.zip" instead of “upd_1.zip”, as described in the link...let me know what happens.
Click to expand...
Click to collapse
This file was the key for me- rooting a Galaxy Ace GT-S5830 on 3.2.6- and that after a day or so searching, running, re-running other stuff and wondering WtF was going wr(on)g. I hope an extra endorsement here helps some other android newbie.
The links seem a moving target, but a Google search on the file name eventually found me one that worked.
What a hassle. I've never been accused of being the swiftest pencil in the box, but if anyone's got a quicker way, please post. And thank you, thank you, thank you...
Managed to lose root today. Updated SuperSU and chose to update binary via CWM instead of normal. Didn't work and I've posted about that on its relevant thread here.
As I said in my post there I tried reflashing the update.zip, but got a status 7 error, to which I then tried AceGingerRoot.zip which was apparently successful in changing the binary from v1.27:SUPERSU (0) binary back to the old v2.3.1-ef (0) binary.
The problem is that I've still not got any root access. So the su files are all in the xbin folder, but apparently aren't readable.
TIA for your help/advice.
HI..... my question is ... how i put this kernel(http://forum.xda-developers.com/showthread.php?t=1823671) in cm10 ...... i want that my build when finshided say kernel:francoblabblabala
thanks
You can manually put it in the ZIP and modify the updater-script to flash this to /dev/block/platform/sdhci-tegra.3/by-name/LNX.
sgt. Meow said:
you can manually put it in the zip and modify the updater-script to flash this to /dev/block/platform/sdhci-tegra.3/by-name/lnx.
Click to expand...
Click to collapse
thanks for the answer..... I don't wanna flash the kernel in recovery or something like that,,,,
i want build my rom whit that kernel........ You know how?
I have make 1 build...... And now i'm going to made some modifications and one is the kernel...... I hope put my rom over here..... Thanks my friend for the answer
You can put it in the ROM ZIP too if that's what you were asking.
But how?? Thanks
Sent from my Nexus 7 using xda app-developers app
Just put the boot.img in the ROM ZIP and edit the updater-script to include these lines:
Code:
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
assert(getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper" ||
getprop("ro.product.device") == "tilapia" || getprop("ro.build.product") == "tilapia");
run_program("/sbin/sh", "-c", "mkdir /system/etc/init.d");
set_perm_recursive(0, 0, 0755, 0755, "/system/etc/init.d");
unmount("/system");
assert(package_extract_file("boot.img", "/dev/block/platform/sdhci-tegra.3/by-name/LNX"));
That's how Franco does it. You could also try dd'ing the contents of boot.img to /dev/block/platform/sdhci-tegra.3/by-name/LNX, but I don't know the exact syntax for that. You can check other kernel ZIPs and see how they install the kernel in recovery. Add the boot.img to your ROM ZIP and then edit the updater-script to include the required lines. That should do it!
Thanks you are great!!! I think that if a want add .apk is something similar??
Sent from my Nexus 7 using xda app-developers app
Yes, but for apps you don't have to change anything in the updater-script.
sgt. meow said:
Yes, but for apps you don't have to change anything in the updater-script.
Click to expand...
Click to collapse
OK ITS JUST PUT THE APPS IN SYSTEM/APP AND GIVE PERMISSIONS?
i hope don't be a fastidious man..... but you know some build.prop tweaks?? i'm copy a few tweaks for internet but......tweaks(build.prop) really makes better the performance and the battery? or just are lie?
to edit the zip of cm10, i will uncompress and edit and compress again?
thanks!!
If you are on Ubuntu, just drag and drop the files you need. And I don't think tweaks really help a lot. Just my opinion though.
alonsoch said:
to edit the zip of cm10, i will uncompress and edit and compress again?
thanks!!
Click to expand...
Click to collapse
No need. Just open the zip via Winrar and edit the file.
Hi everyone, I have the boost Mobile moto g running stock 4.4.4. I'm rooted and have twrp on my phone I'm trying to install bliss pop 5.1.1 but keeps giving me a error. Can anyone help me please?
read FAQ and xda rules before posting.
dustiNcyde419 said:
Hi everyone, I have the boost Mobile moto g running stock 4.4.4. I'm rooted and have twrp on my phone I'm trying to install bliss pop 5.1.1 but keeps giving me a error. Can anyone help me please?
Click to expand...
Click to collapse
Remove the assert lines in the updater-script.
Sent from my Moto G using Tapatalk
I'm sorry idk how to do that? I'm new to all this.
dustiNcyde419 said:
I'm sorry idk how to do that? I'm new to all this.
Click to expand...
Click to collapse
1. Open the ROM zip with WinRAR (or similar program).
2, Navigate to the updater-script.
Code:
[I]META-INF [B]>[/B] com [B]>[/B] google [B]>[/B] android [B]>[/B] updater-script[/I]
3. Open updater-script with Notepad++ (or similar program).
4. Remove (delete) all lines that begin with "assert".
Code:
[I][B]assert[/B](getprop("ro.product.device") == "xt1031" || getprop("ro.build.product") == "xt1031" || getprop("ro.product.device") == "xt1032"...[/I]
5. Save, and flash ROM.
ATTACK said:
1. Open the ROM zip with WinRAR (or similar program).
2, Navigate to the updater-script.
Code:
[I]META-INF [B]>[/B] com [B]>[/B] google [B]>[/B] android [B]>[/B] updater-script[/I]
3. Open updater-script with Notepad++ (or similar program).
4. Remove (delete) all lines that begin with "assert".
Code:
[I][B]assert[/B](getprop("ro.product.device") == "xt1031" || getprop("ro.build.product") == "xt1031" || getprop("ro.product.device") == "xt1032"...[/I]
5. Save, and flash ROM.
Click to expand...
Click to collapse
do i need to be on the lollipop bootloader or no?
dustiNcyde419 said:
do i need to be on the lollipop bootloader or no?
Click to expand...
Click to collapse
No. That's why your going to remove the assert lines.
Sent from my XT1031
ATTACK said:
No. That's why your going to remove the assert lines.
Sent from my XT1031
Click to expand...
Click to collapse
I tried it on multiple ROMs and it won't work just get a failed message when I try and install the rom
dustiNcyde419 said:
I tried it on multiple ROMs and it won't work just get a failed message when I try and install the rom
Click to expand...
Click to collapse
Could you please, screenshot or type exactly what it the error states.
Sent from my XT1031
you have to update the bootloader or change some codes in the Rom,else you cant flash lolipop
there is no error message it acts like its going to flash then just says faild
Yo people !
With the new Incremental update for YNG1TAS2I3 for CM 12, when i try to update via TWRP i get an error
Package build print not verified as in attachment
Just wanted to confirm from experts
Deleting those lines from the updater-script solves the problem ?
getprop("ro.build.fingerprint") == "oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS17L:user/release-keys" ||
getprop("ro.build.fingerprint") == "oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys" ||
abort("Package expects build fingerprint of oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS17L:user/release-keys or oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
Or a better fix
Will flashing the stock CM12 recovery and flashing the incremental update help me ?
Can any one please upload and link me to the official CM12 recovery.img file
The Official CM recovery link is dead !
PS: Thank you Cynogen & OnePlus for the newest updates !
There was the exact same question asked and answered today....
http://forum.xda-developers.com/showthread.php?t=3137841
Lutzchker said:
that one isn't clear. If you did it succesfully can you help?
Click to expand...
Click to collapse
Either update the full ROM (not the Delta file) or choose a different .zip
Oh, and also the official OTA can not be installed from TWRP, only from Cyanogen recovery.
I'll rom whole build. Thanks again
Why not simply format system and then flash? Always works for me and all the data is there alogn with the settings. All i need to do is change dpi, build new host files by adaway, flash xposed zip and tada! it works as it should! the whole process takes not more than 3 minutes.