Related
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
Hello every body
I have a problem during installing a new ROM
i have samsung galaxy SL i9003 and i this phone was in CM 10.1 alpha 8
I tried to upgrade my phone to CM10.2 Rom
and this is the link of the ROM : http://forum.xda-developers.com/showthread.php?t=2431402
first i return to DDLF2 then go to recovery mode
i do wipe data / factory rest
After that when i select the Rom zip folder from Sdcard to install
the phone tell me :
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "captivate" ||
getprop.("ro.build.product") || ... (and so on)
E:Error in /sdcard/#whateverpackage#.zip
Status 7
Installation aborted.
there is any help ??
don't format system after flashing ddlf2. directly install 10.2 over it.
procedure =
1) flash ddlf2
2) root it
3) go to recovery and directly install 10.2.
4) wipe data/reset. (optional)
(don't format anything or else it will give you that error)
hope this helps you.
maxs8007 said:
don't format system after flashing ddlf2. directly install 10.2 over it.
procedure =
1) flash ddlf2
2) root it
3) go to recovery and directly install 10.2.
4) wipe data/reset. (optional)
(don't format anything or else it will give you that error)
hope this helps you.
Click to expand...
Click to collapse
Thank you very much
i will try and tell you
but in the link of The ROM the installation instruction is :
1. Flash CWM Compatible Kernel (CF ROOT)
2. Reboot to Recovery.
3. Wipe Data / Factory Reset.
4. Select the ROM zip from your SD Card and flash.
5. The device will reboot and finish flashing.
6. Reboot to Recovery Again.
7. Flash Google Apps.
8. Reboot
so wipe data/factory rest is before installing the ROM zip and that what i did
flash cf root for ddlf2 first. and you posted on the wrong section.
Sent from my Nexus 4 using xda app-developers app
format system and sdcard bro !!!
dr_amjad said:
Hello every body
I have a problem during installing a new ROM
i have samsung galaxy SL i9003 and i this phone was in CM 10.1 alpha 8
I tried to upgrade my phone to CM10.2 Rom
and this is the link of the ROM : http://forum.xda-developers.com/showthread.php?t=2431402
first i return to DDLF2 then go to recovery mode
i do wipe data / factory rest
After that when i select the Rom zip folder from Sdcard to install
the phone tell me :
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "captivate" ||
getprop.("ro.build.product") || ... (and so on)
E:Error in /sdcard/#whateverpackage#.zip
Status 7
Installation aborted.
there is any help ??
Click to expand...
Click to collapse
Ok,i just encountered this problem just right now ,with clean install ,so after i clicked wipe data /factory reset , i clicked instal zip from rom ,chosed rom ,after this phone restarted and entered again in CWM ,when i chosed again install zip from sd etc... encountered this error ,so i go back in main menu and chose wipe data /factory reset again ,and after this it worked like a charm to install the rom ,no error was displayed. I hope it will work for you to !
LoLaTiOn said:
format system and sdcard bro !!!
Click to expand...
Click to collapse
formatting the system will remove the baseband which wont allow 10.2 to install. i'd encountered the same problem 2 days back and i'd solved the way I mentioned above.. to cross check the error again (2nd time) I formatted the system after clean flash of ddlf2 and I got the same error.. just installing 10.2 directly over ddlf2 won't cause any problem.
---------- Post added at 09:11 AM ---------- Previous post was at 09:05 AM ----------
dr_amjad said:
Thank you very much
i will try and tell you
but in the link of The ROM the installation instruction is :
1. Flash CWM Compatible Kernel (CF ROOT)
2. Reboot to Recovery.
3. Wipe Data / Factory Reset.
4. Select the ROM zip from your SD Card and flash.
5. The device will reboot and finish flashing.
6. Reboot to Recovery Again.
7. Flash Google Apps.
8. Reboot
so wipe data/factory rest is before installing the ROM zip and that what i did
Click to expand...
Click to collapse
"wiping date/factory reset " won't cause any problem. just don't format any thing.. if you want you can format SD Card for your satisfaction.. but don't format system or else that will lead to that error.
hey bro flash only cf-root or bam kernel and don't format system if the installation failed you will have to flash DDLF2 again.
THE SAME ERROR occur again ~~!!
I tried more that 10 times to return to DDLF2 then upgrade my phone to cm10.2 dhirru Rom 4.3 android and the same error appear in every time !!
ASSERT FAILED status 7
Now moment i returned to DDLF2 and upgrade my phone to cm10.2 alpha 8 dhirru ROM and it success upgrading
It's the only Rom which flashing occur Successfully
So , there is NO HELP ?!
Asset failed. Mean either wrong rom or wrong phone.
I saw your error show "captivate". Are you sure you in the right forum..? Btw. Here is galaxy sl gt-i9003 and 9003L
Sent from my Galaxy Nexus using Tapatalk 4
i had the same error while installing cm10.2 it gave me the same error(status 7).device only would go in recovery mode.after that i downloaded the rom again and it worked.the download was corrupt.so download again and try. :fingers-crossed:
@chongns : I am sure that it's a right Rom and Right phone ~~ !
dr_amjad said:
@chongns : I am sure that it's a right Rom and Right phone ~~ !
Click to expand...
Click to collapse
you try bypass the assert check by delete those line in rom zip file, the file is updater-script in folder
"CM10.1-GalaxySL-JDQ39E-Alpha7/META-INF/com/google/android"
Code:
assert(getprop("ro.product.device") == "galaxysl" || getprop("ro.build.product") == "galaxysl" ||
getprop("ro.product.device") == "GT-I9003" || getprop("ro.build.product") == "GT-I9003" ||
getprop("ro.product.device") == "GT-I9003L" || getprop("ro.build.product") == "GT-I9003L");
open up the zip without unzip it, just open with winrar than edit than save.
this is a try, never try it before for our phone.
---------- Post added at 08:20 PM ---------- Previous post was at 08:15 PM ----------
dr_amjad said:
@chongns : I am sure that it's a right Rom and Right phone ~~ !
Click to expand...
Click to collapse
just found out the ROM download site having 2 type of CM10.2, one is for LG Optimus black others one for GT-i9003
makesure you download the correct one
@chongns : Thanks very much for help
Every thing now i being OK
I download the Rom Again and download gapps
Then i tried to flash the rom and tell me the same error ( status 7 )
then i do Wipe Data / Factory Reset one time and repeat it again
Then i choose the ROM zip and it flashed OK
all what i do that i did Wipe Data / Factory Reset twice followed by each other
Thanks very much for helping me
dr_amjad said:
@chongns : Thanks very much for help
Every thing now i being OK
I download the Rom Again and download gapps
Then i tried to flash the rom and tell me the same error ( status 7 )
then i do Wipe Data / Factory Reset one time and repeat it again
Then i choose the ROM zip and it flashed OK
all what i do that i did Wipe Data / Factory Reset twice followed by each other
Thanks very much for helping me
Click to expand...
Click to collapse
although, you have flash through, but that still weird to have error status 7.
btw, the correct step should be factory reset than flash the zip, yous is flash the zip than factory reset.......
chongns said:
although, you have flash through, but that still weird to have error status 7.
btw, the correct step should be factory reset than flash the zip, yous is flash the zip than factory reset.......
Click to expand...
Click to collapse
yes
i did first Wipe Data / Factory Reset two times each one follow the other then i flashed the Rom zip
Working method (tried several times with different roms):
-flash DDLF2
-flash cfroot
-recovery mode (the green one)
-flash your rom, then you'll be bringed to the new version of cwm (the blue one)
-wipe data/factory reset
-format system
-flash the rom
Hi all:
I'm also getting this issue lately, and I use to solve it going to mounts and storage and mounting all the filesystems, then try again.
Looks like the updater script can't mount the file systems automatically or something lately and so it gives that error.
Hope this solves your issue.
BTW, I also saw it extrange that the assert of the zip you were flashing indicated captivate, our device codename for CyanogenMod is galaxysl, not captivate, make sure you're flashing the right zip. (Also, captivate is not p970 either, so you should have mistakenly downloaded the zip from somewhere else).
Sent from my GT-I9003 using xda premium
Simply copy the file to internal SD card and flash it. Problem solved for me.
Sent from my GT-I9003 using xda app-developers app
sam_777 said:
Simply copy the file to internal SD card and flash it. Problem solved for me.
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
Here's the solution to this problem
Hi there,
I'm just trying to install TWRP and Cyanogenmod 12.1 (cm-12.1-20151230-NIGHTLY-taoshan / open_gapps-arm-5.1-nano-20151225), and having some problems.
Sorry for the long mail, at the end I have put a short summary of the current status of my Xperia L (C3105).
I succeeded to unlock the bootloader, afterwards I installed the stock rom (C2105_15.3.A.1.17_1272-2171 R2B_Generic DE). So far, so good.
However, all attempts to install TWRP and/or Cyanogenmod have failed so far.
At first I tried to install TWRP (latest version) via the app method (TWRP manager app form Google app store). The app reported a successful flash, but somehow I could not get to recovery when I rebooted while rocking the vol up/down buttons. Also the notification light does not any more turn purple when booting up.
Afterwards I flashed the above stock rom again because it was not clear for me whether the phone was stucked in a boot loop. I guess that this also re-installed the stock recovery again? Anyhow, since then and up to now even when I reboot and constantly press the volume buttons (both) while the phone is booting up, it still boots into android and not into the recovery.
So I guess that the recovery is not correctly installed at the moment.
I tried also with the XDA recovery-installer-taoshan-1.3.apk to install another version of TWRP (an older one), but this did not work as well, with a very similar behaviour, but afterwards I was not either to boot anything, neither the recovery nor the android system, but was possible to boot into fastboot mode so that I could re-flash the stock rom.
Now, even when I neglect the recovery and try to install cynogenmod with the command "adb sideload update.zip" (obviously with exact file name instead of update.zip), it always says the following:
ADB server didn't ACK
* failed to start daemon *
adb server is out of date. killing...
*daemon started successfully *
error: closed
I have to say that after flashing the stock rom and connecting the phone to the computer, I denied to re-install the PC companion software, because from my perspective all drivers etc should be installed. But I do not want to exclude that this could also be an issue here.
I just tried to install the universal ADB drivers, seleted repair drivers, but still the ADB connection seems to not work properly.
My device manager reports for the driver "Sony so0103 ADB Interface Driver".
Just to summarize:
- I have rooted the phone successfully (also re-rooted after flashing the stock rom)
- the bootloader is unlocked (confirmed via service menu)
- recovery does not work
- above mentioned stock rom is installed
- stock rom is booting fine
Does anyone have a suggestion of how to solve the problems and what the next steps should be? I would also very much appreciate any hint on what I have possibly done wrong in order to learn from it.
Many thanks in advance and my best regards,
Henning
Just a note:
If I remember well, I'm not sure if the ADB drivers were successfully installed. The last time when I used ADB successfully, it was with linux, and this time I tried with windows, because the flashtool seems to work only with windows (or I just do not know how to operate it in linux on the shell).
Should I just try to re-install TWRP with the app method, and without rebooting flash cyanogenmod using the "adb sideload update.zip" command? Or is there any other command which would be preferred?
I have also busybox and a terminal emulator installed, could also direclty flash it from the phone ...
Thanks in advance!
Cheers,
Henning
While using the app, when it reboots, open the app again and click TWRP again.. it'll work.. or it may be an incomplete download. delete twrp.tar from the internal SD and try again
Hi,
I hope someone could help me quickly:
I again installed TWRP 2.8.7.0 via the TWRP manager app method.
Afterwards I flashed with Flashtool the extracted boot.img from the CM-12.1 zip file.
This time I finally could boot into the recovery!
But now my problem is that the CM zip file will not be installed by TWRP.
Before the install, I wiped cache, dalvik cache, system, data (made a backup also).
Any suggestions? Is my TWRP 2.8.7.0 buggy, or the CM zip file, or is there anything I could have missed?
Many thanks in advance and sorry to bother you again!
Cheers,
Henning
Here is the log that I get from TWRP:
Installing '/sdcard/.....'
Checking for MD5 file ...
Skipping MD5 check: no MD5 file found
This package is for device: C2105,C2104,c2105,c2104,taoshan; this device is .
E:Error executing updater binary in zip '/sdcard......'
Error flashing zip '/sdcard/......'
Updating partition details...
...done
xleng said:
Here is the log that I get from TWRP:
Installing '/sdcard/.....'
Checking for MD5 file ...
Skipping MD5 check: no MD5 file found
This package is for device: C2105,C2104,c2105,c2104,taoshan; this device is .
E:Error executing updater binary in zip '/sdcard......'
Error flashing zip '/sdcard/......'
Updating partition details...
...done
Click to expand...
Click to collapse
obviously twrp manager app is ****ty
either use corphishs app to get my twrp versions or do the following:
1. in twrp go to
advanced->terminal command->ok
there enter :
setprop ro.build.product taoshan
setprop ro.product.name taoshan
2. flash the rom you want
3. get the app and a better twrp ;-P
Sent from my Xperia T using XDA Free mobile app
Many thanks for the quick reply!
I will try in a minute and report the results.
One question, I think that I may have already wiped system before I took the backup in TWRP.
In case I would reboot or switch off now (e.g. in order to put the SDCARD into the computer and put another version of TWRP and/or CM on it), would I be able to boot into the recovery again or would I hard-brick the device then?
I just tried to modify the update file on the computer and re-load it via sideload, but for some reason sideload could not be activated ... I will try now with your suggestion
Thanks in advance!
Still the same error .... (
I also tried to set other variables, like:
setprop ro.product.model taoshan
setprop ro.product.brand taoshan
setprop ro.product.name taoshan
setprop ro.product.device taoshan
setprop ro.product.board taoshan
setprop ro.product.manufacturer taoshan
Does not work ... it seems that the device recognized is still empty / ""
It's really weird. when I execute the shell command "getprop ro.product.name" I get "taoshan", but the updater-script does not recognize this for any reason. Probably it's the TWRP which is faulty as you indicated.
Now i just rebooted the device and connect via flashboot in order to flash the stock FTF again via flashtool.
Now I'm on stock rom again and lucky that the device is not broken (though we still have another xperia L around here from my wife, before she got a windows phone ) - hope that sooner or later I could use one of them as a debugging / experimental device though
Well, it's late for today, I will resume most likely tomorrow evening and would like to thank you once more for your very valuable hints!
Tomorrow i will try to install your version of TWRP - it is this one, correct? :
http://forum.xda-developers.com/xperia-l/development/app-recoveries-recovery-installer-t3187915
I guess this is the TWRP that you've installed as well on your device?
By the way, while I'm getting used to the process of flashing stock roms, rooting, installer recoveries etc, do you have any recommendations on certain custom ROM / GAPPS combination?
May I ask what you're using at the moment?
Just thinking about whether I will continue with CM or might switch to RR or something else ...
Cheers,
Henning
I'm just thinking if the updater-script itself has a bug:
In the first line I have:
Code:
assert(getprop("ro.product.device") == "C2105" || getprop("ro.build.product") == "C2105" || getprop("ro.product.device") == "C2104" || getprop("ro.build.product") == "C2104" || getprop("ro.product.device") == "c2105" || getprop("ro.build.product") == "c2105" || getprop("ro.product.device") == "" || getprop("ro.build.product") == "" || getprop("ro.product.device") == "taoshan" || getprop("ro.build.product") == "taoshan" || abort("This package is for device: C2105,C2104,c2105,c2104,taoshan; this device is " + getprop("ro.product.device") + "."););
I'm just wondering if the problem is because the abort() command is part of the assert() function, but I#m not sure about the syntax.
Cheers,
Henning
xleng said:
I'm just thinking if the updater-script itself has a bug:
In the first line I have:
Code:
assert(getprop("ro.product.device") == "C2105" || getprop("ro.build.product") == "C2105" || getprop("ro.product.device") == "C2104" || getprop("ro.build.product") == "C2104" || getprop("ro.product.device") == "c2105" || getprop("ro.build.product") == "c2105" || getprop("ro.product.device") == "" || getprop("ro.build.product") == "" || getprop("ro.product.device") == "taoshan" || getprop("ro.build.product") == "taoshan" || abort("This package is for device: C2105,C2104,c2105,c2104,taoshan; this device is " + getprop("ro.product.device") + "."););
I'm just wondering if the problem is because the abort() command is part of the assert() function, but I#m not sure about the syntax.
Cheers,
Henning
Click to expand...
Click to collapse
no thats all ok...
i dont know why the terminal command didnt work for you... you must have done it wrong!
yes the twrp is the one from me... and no i dont use it because i have no longer XL since my is broken...
Sent from my Xperia T using XDA Free mobile app
Hi,
I have downloaded and installed your app, as well as the latest CM-12.1 version (2016-01-19) with the corresponding GAPPS nano package.
I applied the following procedure:
1) flashed TWRP
2) rebooted to fastboot mode, extracted and flashed the boot.img from the CM-package
3) rebooted to recovery, then I recognized that probably the boot.img has overwritten the TWRP recovery, since it was the CM recovery that started
4) tried to flash CM-12.1, which failed after the verification, with the message that it can't be installed on top of incompatible data; what I've noticed was that the CM recovery did not allow me to wipe the system, don't know if that could have caused the problem.
Trying further ....
Cheers,
Henning
Hi,
I repeated the same steps just without flashing the boot.img file, when rebooting to recovery TWRP was there, and was able to flash the latest CM-12.1 which is currently booting!
Many thanks to all contributors of this ROM and to SdtBarbarossa for advice!!!
Cheers,
Henning
PS: Probably I will comment on something later ...
I installed both CM and GAPPS directly after each other, e.g. without an intermediate boot into android.
Now I have messages telling me that the google apps have been closed after each start-up.
I think I probably need to re-flash CM, then reboot, and then flash GAPPS again, right?
Even the google app store was not working, and I could also not install the TWRP with the apk file because it didn't recognize the device.
Installing stock rom again for tonight, tomorrow I will flash CM again ...
Even if the app doesn't recognize your device, flash it.. It works 100% .. and after flashing gapps you should try factory resetting .. It might work..
Good point with the favtory Reset! Thanks!
Hi,
CM-12.1 works now very well (I noticed the flashlight bug which I believe has been reported several times already, but that's not really troubling me) ...
Overall, it's really an awesome ROM! Very fast and responsive (much much faster UI feeling than with the initial SONY stock ROM), and really great to see a recent android version running that smoothly on this little device!
Many thanks again to all contributors of this ROM! Really a great piece of work!
Cheers
Henning
xleng said:
Hi,
I have downloaded and installed your app, as well as the latest CM-12.1 version (2016-01-19) with the corresponding GAPPS nano package.
I applied the following procedure:
1) flashed TWRP
2) rebooted to fastboot mode, extracted and flashed the boot.img from the CM-package
3) rebooted to recovery, then I recognized that probably the boot.img has overwritten the TWRP recovery, since it was the CM recovery that started
4) tried to flash CM-12.1, which failed after the verification, with the message that it can't be installed on top of incompatible data; what I've noticed was that the CM recovery did not allow me to wipe the system, don't know if that could have caused the problem.
Trying further ....
Cheers,
Henning
Click to expand...
Click to collapse
I'm facing the same issue not able to flash.
Can you give step by step instructions?
Hi, what is your device status at the moment? What did you do so far?
Thought to create a clean thread on errors like error executing updater binary
Error executing Updater Binary??
I recently thought to Flash any Custom Rom because stock android is really boring,I flashed Blisspop 6.0 [Marshmallow] I got error :- Error Executing Updater binary !
Steps to Resolve Problems !
1] Download WinZip
2] Download NotePad++ :good:
Process
1] Open downloaded Custom rom with Winzip
2]Go to META-INF --> Com --> Google --> Android
3] You will see "Updater-Binary" and "Updater-Script"
4] Open Updater-Script with Notepad++
5] After Opening you will see something like this you have to delete that !
assert(getprop("ro.product.device") == "YUPHORIA" || getprop("ro.build.product") == "YUPHORIA" || abort("This package is for device: YUPHORIA; this device is " + getprop("ro.product.device") + ".");
6] Save File and close it and also close WinZip it will ask you few options choose update zip changes !
7] Copy that updated file to your mobile
8] Reboot into Recovery
9] Flash Zip without any Error :good:
NOTE:-Use latest TWRP [3.0.0-0] link -
https://www.androidfilehost.com/?fid=24407100847292507
Hit - Thanks
thank you for the solution
yuphoria Stock android 5.1 to cyanogen os12.1
I bought yuphoria of stock android5.1. After an update i got technical issue i cant record a video and also i cant play hd videos can i update it from stock android to cyanogen 12.1..it its then please help before updat i have to root my yuphoria or directly i have to install cyanogen os please help
your problem can be solved
Hussainam said:
I bought yuphoria of stock android5.1. After an update i got technical issue i cant record a video and also i cant play hd videos can i update it from stock android to cyanogen 12.1..it its then please help before updat i have to root my yuphoria or directly i have to install cyanogen os please help
Click to expand...
Click to collapse
if you have already installed cm 12.1 tere is no other updates rather than 12.1 [stock]
you can try downgrading your device to cm12 it can fix all your problems [if not try custom rom]
I have a easy tool to do the flashing. So much easier!
problem while flashing lineage lettuce ROM on YU YUPHORIA
i have tried above steps and update the updater-script file to remove base-band check but if i again trying to flash the ROM then below error occurs
"could not find 'META-INF\com\google\android\update-binary" in the zip file
please help me regarding the above issue.
my yuphoria phone only starts upto cynaogen screen and then restarts. also it isnot recognised by laptop
Hi
I rooted my "moto g 2015" by TWRP 8.12
And officially unlocked bootloader by motorola unlock code.
It also was originally locked to VIRGIN CANADA pre-paid plan, then I unlocked it by SIM Unlock PIN to use it worldwide.
ANDROID 5.1.1
kernel : 3.10.49-gd291414
BUILD; LPI23.72-43
baseband : M8916_2020613.22.03.21.29R OSPREY_BELLCA_CUST
sys ver: 23.41.43.osprey_retca.retca.en.ca bwaca
it wants to update itself with 23.46.4.en.CA notification using this file "Blur_version.23.41.43.osprey_retca.retca.en.CA.ZIP" (Located in CACHE folder, 31.5MB in size)
why the notification number is different that blur version number, i've no idea!
however after downloading and rebooting automatically it stuck on "E:Error ..." in TWRP bootscreen.
the contents of 2 important files are;
updater-script; (partial)
------------------------------
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "max_batch_time=0,commit=1,data=ordered,barrier=1,errors=panic,nodelalloc");
getprop("ro.build.fingerprint") == "motorola/osprey_retca/osprey_umts:5.1.1/LPI23.72-43/46:user/release-keys"
|| getprop("ro.build.fingerprint") == "motorola/osprey_retca/osprey_umts:5.1.1/LPI23.72-47.4/6:user/release-keys"
|| abort("Package expects build fingerprint of motorola/osprey_retca/osprey_umts:5.1.1/LPI23.72-43/46:user/release-keys or
motorola/osprey_retca/osprey_umts:5.1.1/LPI23.72-47.4/6:user/release-keys;
this device has " + getprop("ro.build.fingerprint") + "."); getprop("ro.product.device") == "osprey_umts"
|| abort("This package is for "osprey_umts" devices; this is a "" + getprop("ro.product.device") + ""."); ui_print("Verifying current system...");
show_progress(0.100000,0); apply_patch_check("/system/app/3c_main/3c_main.apk",
metadata;
--------------
post-build=motorola/osprey_retca/osprey_umts:5.1.1/LPI23.72-47.4/6:user/release-keys post-timestamp=1440023071
pre-build = motorola/osprey_retca/osprey_umts:5.1.1/LPI23.72-43/46:user/release-keys pre-device=osprey_umts
whats the problem, and how can i fix it, so the update go on as it supposed to?
either by phone itself or with help of my pc.
I attached a jpg of the error message.
I'm suspecting its something about UMTS vs RECTA !
and mobile falls into a reboot cycle, until i manually remove the mentioned update zip file from cache folder.
Thank you for any help.
crossing my fingers
Sorry for answering late, but you can't update via OTA with a custom recovery, go on the firmware thread and download your firmware and flash the stock recovery present in the file or download the update there if it is available.
@Henriquefeira is correct, TWRP cannot flash stock image or OTA update, only stock recovery can do that properly... you best bet really is to get the full factory image for the latest release and flash it manually via fastboot, then reinstall TWRP and root. This will not effect your unlock state, either bootloader or carrier unlock.