Database Info

[Q] FUBAR'd (Status 7)

i seem to have fubar'ed my nexus s (uk version) i updated to ics, didnt like it so tried to restore to a backup i made earlier today...
at the moment when i turn on my phone it shows
fastboot mode- No Boot or Recovery img
lock state - unlocked
I can enter recovery. but cannot restore.
tried wiping cache,dalvik etc.
When hitting restore it returns with:
... system.img not found. skipping restore of /system/
also does the same with
data.img
cache.img
sd-ext.img
i have no idea what to do... if you could help it would be greatly appreciated.

Try flashing a rom. U can mount SD card within recovery.
Sent from my Nexus S 4G using xda premium

yeah tried flashing ...
gets stuck on google screen

Do you have a One Click return to stock available for your model? It wouldn't hurt to start fresh. I did that on my NS4G last week. Does your PC recognize the phone?
Sent from my SPH-D710 using Tapatalk

looking into the unbrickable mod atm... my phone seems to have no .img files.
tried restoring to stock and still the same issue... it says it cant find .img so skips them then when i try to re boot it sticks on the google screen

After trying to apply from zip (cm7, that i have used numerous times before)
i get this ---
Installing update...
assert failed: getprop("ro.product.device") =="crespo" ll getprop("ro.build.Product") == "crespo" ll getprop("ro.product.board") == "crespo"
E:Error in /sdcard/update-cm-7.0.3-NS-signed.zip
(Status 7)
Installation aborted.
i havent the faintest idea what to do...

Tried re-flashing CWM recovery?

yup tried re flash,
i think i need to replace the .img files... i just dont know how
it says that
system.img not found
data.img not found
cache.img not found
sd-ext.img not found.
it skips the restore of these say restore complete. yet there is obviously nothing to restore.
there must be a way of fixing this???

Do you have the latest version of CWM flashed? (5.0.2.0)

yeah re installed/reflashed (5.0.2.0)
it seems to be working
*~~~~~~*
Facepalm
*~~~~~~*
Such a noob
I have had a similar problem before, and even advised on that exact thing.
lesson learned.
KEEP RECOVERY.IMG UP TO DATE
Thank you for pointing out the obvious.
I'm such a ****

No problem flex59, best way to learn is the long and hard way . I had a similar status 7 problem on my move up to ICS. Figured the latest recovery will save me wasted hours down the track eventually, and hopefully someone elses.

To downgrade from ICS, you need to flash the full GB 2.3.6 ROM first...
I downgraded from OTA ICS 4.0.3 due to battery, Wifi & lag issues as well. A NANDroid backup does NOT contain the bootloader and radio AFAIK. Here's what I did.
Find the appropriate FULL ROM here and download and copy to your SD card.
Download this flashable Superuser here and copy to your SD card.
Make sure you are familiar with and set up for fastboot and have the latest CWM recovery img file. You will have to reinstall CWM. These instructions are assuming that CWM recovery is already installed on your device.
1. Make sure the full ROM and SU zip are on the root your SD card.
2. I did a full wipe of data, cache, dalvik.
3. Go into CWM recovery and flash the full ROM. Now flash the SU zip.
4. At this point, the full ROM flashed GB2.3.6, stock recovery, bootloader and radio back. But you should be rooted due to step 3.
5. Boot into Android. I installed ES File Explorer from the market. In ES File Explorer settings, select both root settings “Root Explorer” and “Mount File System” to navigate and modify root files. Allow permissions in SuperUser.
6. Navigate to /system/etc and rename (tap&hold on file) install-recovery.sh to install-recovery.sh.bak (this file reinstalls the stock recovery at every boot)
7. Using fastboot on your computer, flash CWM recovery again.
8. NOW using CWM, restore your GB 2.3.6 NANDroid backup.
Like nothing ever changed.

[Q] Rogers Galaxy Note I717R - Installing Avatar ROM Error

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

[Q] Can't install P.A.C. All-in-one

So...
I meant to install the PAC All-In-One ROM.
Darktitor specified that I had to flash a stock ROM through Odin. After making sure that I could flash a CF-Root DDLF2 instead of my stock XWLF2, I put my phone in Download Mode and flashed DDLF2 through Odin. I went in recovery mode, wiped data and formatted /system. I then tried installing the ROM (P.A.C. All-in-one, as I already specified elsewhere) through the "Install zip from SD card" button, but it displays the following errors: "assert failed: getprop ("ro.product.device") == "galaxysl" | | getprop ("ro.build.product") == "galaxysl"", repeated for GT-I9003 and GT-I9003L (yeah, it IS a Galaxy SL), and E:Error in /sdcard/i9003 blah,blah,blah (the filename of the ROM, obviously).
What should I do now?
EDIT: The signature verification for the update also fails.
MOAR EDIT: Same problem both with Dhiru's Alpha 7 and the LEMON build.

Try not to format the /system before flash.when u format the /system,build.prop was remove and the signature verification will failed.just wipe data/factury reset,wipe cache and then flash the rom./system will be formated automatically during the flash.
Sent from my GT-I9003 using xda premium

zhiyong said:
Try not to format the /system before flash.when u format the /system,build.prop was remove and the signature verification will failed.just wipe data/factury reset,wipe cache and then flash the rom./system will be formated automatically during the flash.
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
I managed to solve the problem on my own, but thank you very much! (I just had to flash XXKPE and DDLF2 before installing PAC.)

Please help ! Assert failed status 7

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

Troubles installing TWRP + Cyanogenmod 12.1

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?