Hello Everyone.
Noob here and first time to perform a root of my Galaxy Note I717R (Rogers).
Anyway, I found this forum and was hoping to get the Avatar ROM to my Note. The forum link is here:
http://forum.xda-developers.com/showthread.php?t=2131085
I have already installed CWM and have already proceeded to CWM Recovery Mode.
In the Recovery Mode, I have performed the options:
* backup and restore
* wipe data / factory reset
* wipe cache partition
I have also copied the following files as posted on the forum on my phone's internal SD:
* cm-1.3b_111_20130224_quincyatt.zip
* gapps-jb-20121212-signed.zip
Now, when I select the option "install zip from sdcard | choose zip from internal sdcard" and choose the file "cm-1.3b_111_20130224_quincyatt.zip" and selecting "Yes - Install cm-1.3b_111_20130224_quincyatt.zip", I am getting the error:
assert failed: getprop("ro.product.device") == "SGH-I717" || getprop("ro.build.product") == "SGH-I717" || getprop("ro.product.device") == "quincyatt" || getprop("ro.build.product") == "quincyatt"
E:Error in /emmc/cm-1.3b_111_20130224_quincyatt.zip
(Status 7)
Installation aborted.
I am quite unsure of how to resolve this or get around this. Any help would be appreciated. Thanks.
Update:
I copied the zip file to the external sd card and tried to re-install from there but I got the same errors as above.
~BB
I have same problem
BatutaBunsing said:
Hello Everyone.
Noob here and first time to perform a root of my Galaxy Note I717R (Rogers).
Anyway, I found this forum and was hoping to get the Avatar ROM to my Note. The forum link is here:
http://forum.xda-developers.com/showthread.php?t=2131085
I have already installed CWM and have already proceeded to CWM Recovery Mode.
In the Recovery Mode, I have performed the options:
* backup and restore
* wipe data / factory reset
* wipe cache partition
I have also copied the following files as posted on the forum on my phone's internal SD:
* cm-1.3b_111_20130224_quincyatt.zip
* gapps-jb-20121212-signed.zip
Now, when I select the option "install zip from sdcard | choose zip from internal sdcard" and choose the file "cm-1.3b_111_20130224_quincyatt.zip" and selecting "Yes - Install cm-1.3b_111_20130224_quincyatt.zip", I am getting the error:
assert failed: getprop("ro.product.device") == "SGH-I717" || getprop("ro.build.product") == "SGH-I717" || getprop("ro.product.device") == "quincyatt" || getprop("ro.build.product") == "quincyatt"
E:Error in /emmc/cm-1.3b_111_20130224_quincyatt.zip
(Status 7)
Installation aborted.
I am quite unsure of how to resolve this or get around this. Any help would be appreciated. Thanks.
Update:
I copied the zip file to the external sd card and tried to re-install from there but I got the same errors as above.
~BB
Click to expand...
Click to collapse
I have the same problem... I wanted to install CM 10.1 and gapps but got the same status 7... let me know if u could fix it...
Has anyone been able to solve this?
I have tried flashing the stock ATT via odin to chnage the phone to a 717 not a 717r and still doesn't work
Using the newest TWRP as my recovery
Whenever I find some spare time I use to switch rom. Flashollic Me!
Increment CM digits are always no task at all because developers are taking good care so that flash process is done right.
But when try to decrements cm digits - do not have options. Back to DDLF2 via mighty odin is the only way to start. No flash-able zip files to step back! There should exist some easy way to do the job. This is a way to do this but I believe more easier way exists.
From cm11 rebboot to recovery
Flash cm-Ker-10.2over11-BuildBox.zip from cwm
Reboot to recovery again
Clean user data, etc, etc
Flash any cm10 (I tried cm10.2) rom
If that well known error "status 7" appears go ahead and flash again.
Flash gapps accordingly (gapps for 4.1, 4.2, 4.3)
Reboot.
Yes, not caught by mighty odin. Bye bye odin. See you later in deep needs.
This is not my work. I moved things from here to there. No Dev thing.
The zip structure is taken from the work of David Rodero
The boot.img is from BuildBox
All credit goes to @rodero95 and @buildBox
Finally, good luck to all flashers.
another method:
open cm10(10.1 or 10,2).zip\META-INF\com\google\android
edit the updater-script
delete the device assert script
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");
then mount sdcard0 ,sdcard1 in cwm recovery and then chose the zip and flash. work for me
Hi guys,
Can you help me please?, I having problems to upgrade my xt925 to CM12.1. The error log says that I have a xt926 and the update process abort.
Please see the attached image. Thanks in advance for your support.
xt925 to cm12.1
rodrigo_ruiz_rr said:
Hi guys,
Can you help me please?, I having problems to upgrade my xt925 to CM12.1. The error log says that I have a xt926 and the update process abort.
Please see the attached image. Thanks in advance for your support.
Click to expand...
Click to collapse
I had a similar problem, but in my case the log said that my device was not a xt925 because i had cm11 for msm8960, the solution was to delete this line:
Code:
[I][B]assert(getprop("ro.product.device") == "xt925" || getprop("ro.build.product") == "xt925" || getprop("ro.product.device") == "vanquish_u" || getprop("ro.build.product") == "vanquish_u" || abort("This package is for device: xt925,vanquish_u; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
assert(getprop("ro.boot.secure_hardware") == "1" || abort("This package is for devices with 4.4 bootloader"););[/B][/I]
in the updater-script file inside the folder cm-12.1-20150810-NIGHTLY-xt925.zip\META-INF\com\google\android of your zip file, so it won't try to verify your device name and instead will install it as it is
REMEMBER USE THIS UNDER YOUR OWN RISK, DON'T BLAME ME FOR A NICE PAPER WEIGHT
I ALREADY HAD A KITKAT BOOTLOADER FROM A STOCK FIRMWARE and i tried this on a old device, so no harm if bricked, also i was sure that i downloaded the correct cm12.1 version for my mobile and, at last but not least, i knew how to unbrick it in case something went wrong
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?
assert(... abort("This package is for device: xt925,vanquish_u; this device is ...)
Hi,
I hope you recognize the title meaning.
Working with all recovery I have: WTRP 2.6.0.0, PhilZ Touch 6.41.6 (CWM 6.0.48), CWM 6.0.3.6 and trying to install cm-12.1-20160822-NIGHTLY-xt925.zip I cannot because of above assert fail.
Of course, I have the right device: RAZR HD XT925 vanquish_u.
PhilZ Touch 6.41.6 doesn't display what this device is from the expression:
abort("This package is for device: xt925,vanquish_u; this device is " + getprop("ro.product.device") + ".");
As long as I understand I don't have the right recovery environment for this install - upgrade from Android 4.4.4 (cm-11) to Android 5.1.1 (cm-12.1).
Is there an easy fix because comment out //assert(... abort( ... doesn't work.
If not, which is the hard way?
Thanks.
There are two assert statements
There are two assert statements in updater-script.
Essentially they verify the device and the bootloader as seen below by the massage that should be displayed in case a verification fails :
abort("This package is for device: xt925,vanquish_u; this device is " + getprop("ro.product.device") + ".");
abort("This package is for devices with 4.4 bootloader");
My setup satisfies both conditions, so I've just deleted both assert statements.
The .zip files installation was possible, the system booted but the actual installation process didn't ended at least in a half hour - there was only logo on the screen.
I'm trying to install the system from cm-12.1-20160822-NIGHTLY-xt925.zip
Can I do something more?
Thanks.
The right ROM cm-13.0-20160425-NIGHTLY-xt925_lbbl
It turned out there was a double mistake with the ROM I've tried to install.
I found it finding pure by chance cm-13.0-20160425-NIGHTLY-xt925_lbbl.
So, my RazR HD XT925 is product.device == moto_msm8960 and
my devices is with 4.1 bootloader contrary to what I thought
product.device == xt925 with 4.4 bootloader.
I've learned the new ROM installation doesn't change the already installed bootloader.