Related
Hi,
I just noticed this was ready to download on my phone today. I downloaded and went to install, but the ClockWordMod Recovery doesn't let me install the update saying, "Image Verification Failed". I assume the problem is that the phone is rooted, and searching through the forums I heard this update isn't really anything big, just removing some German apps or something.
Is there anyway I can stop this update from notifying me? Or anyway to install? My phone is rooted but I'm not bothered about keeping it rooted as at the moment, there is nothing I need the phone to be rooted for. So, either way is fine for me.
Thanks!
If you want to unroot it, just flash generic ruu, more info here http://theunlockr.com/2010/06/07/how-to-unroot-the-htc-desire/
Than simply check for updates and update it
Or wait for few hours for rooted version of this rom
Hi!
I have a branded Desire and installed the update via Recovery. I had to disable the verification to do that (Goldcard inside). But all I got was a boot loop and my phone was derooted. I tried much (e.g. delete my data) and after a couple of hours I found the simple solution: Simply install the update again. Then I rooted my phone and restored the NANDROID Backup I made before I started the update because all of my data was gone.
Then I installed the Update again and this time it worked at the first time. All data was still there. I rooted it again and everything is fine. Don't know why my phone got a boot loop after first try but second try was perfect!
My suggestion: copy the zip from the download folder to the SDcard (made to a Goldcard!!!!) root and to the PC. Just if you need it more than once. Then make a Backup in the Bootloader. Then Install the update via Recovery. If anything goes wrong install the update again!
So I've been trying to fix this problem for about 6 hours now and still no luck.
I am very new to this stuff which is probably why I made the mistake. Basically I was trying to install CyanogenMod 10 custom ROM on my phone and I kept receiving this "status 7 error" I did some research on how to fix that, and that's when the problem occurred.
I read that I should clear my Dalvik cache, /system, and do a factory settings wipe. I did all that, continued to get the error, and when I rebooted I was stuck on the boot screen, my theory is that it had something to do with the clearing of the /system, but I don't know.
I can still get into download mode and into the CW recovery, but that's about it. I tried flashing the stock firmware through Odin, but the firmware I downloaded is just a .zip, and there is not .tar when you extract it, so I cant use Odin. I am at a total loss here, please help me.
Thanks a lot in advance.
Have you tried re-downloading the ROM, and flashing the new zip? Your current zip may be corrupt.
LordDiabeetus said:
Have you tried re-downloading the ROM, and flashing the new zip? Your current zip may be corrupt.
Click to expand...
Click to collapse
Where would I download the zip to? I can only access the files that are on my phone through CW. I cannot or at least I do not know how to transfer files to my phone in its current state.
Thanks for the reply.
apolanco115 said:
Where would I download the zip to? I can only access the files that are on my phone through CW. I cannot or at least I do not know how to transfer files to my phone in its current state.
Thanks for the reply.
Click to expand...
Click to collapse
Do you have a spare MicroSD laying around? Use that, if your computer has an SD slot. If you don't have a MicroSD with the adapter to plug it into a normal SD slot, you can find cheap 2 GB ones with an adapter on the cheap. If your computer doesn't has an SD slot, and you have no external tools, the ADB may be able to help you, or you could find an adapter. Simply re-download the zip (or a zip for a different ROM) on the computer, and move it to the external SD. Stick said MicroSD into your phone. When you choose to install a zip in the recovery, there should be an option to choose from an external SD, if it mounted correctly.
LordDiabeetus said:
Do you have a spare MicroSD laying around? Use that, if your computer has an SD slot. If you don't have a MicroSD with the adapter to plug it into a normal SD slot, you can find cheap 2 GB ones with an adapter on the cheap. If your computer doesn't has an SD slot, and you have no external tools, the ADB may be able to help you, or you could find an adapter. Simply re-download the zip (or a zip for a different ROM) on the computer, and move it to the external SD. Stick said MicroSD into your phone. When you choose to install a zip in the recovery, there should be an option to choose from an external SD, if it mounted correctly.
Click to expand...
Click to collapse
I will try that right now, thank you!
apolanco115 said:
I will try that right now, thank you!
Click to expand...
Click to collapse
Did it work out for you?
LordDiabeetus said:
Did it work out for you?
Click to expand...
Click to collapse
I'm backing up the stuff on my SD and formatting to FAT32. It's taking a while, but It's almost done.
apolanco115 said:
I'm backing up the stuff on my SD and formatting to FAT32. It's taking a while, but It's almost done.
Click to expand...
Click to collapse
Alright. Let me know if it works for you. If reflashing the other ROM doesn't work, try another one.
Personally, I would recommend CyanogenMod 10.1.
LordDiabeetus said:
Did it work out for you?
Click to expand...
Click to collapse
When I tried this, It said
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Erro in /sdcard/SGH-T999_T999UVDLI8-OTA-T999UVALH2_TMB_341017054.zip
(Status 7)
Installation aborted.
How do I fix this?
apolanco115 said:
When I tried this, It said
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Erro in /sdcard/SGH-T999_T999UVDLI8-OTA-T999UVALH2_TMB_341017054.zip
(Status 7)
Installation aborted.
How do I fix this?
Click to expand...
Click to collapse
Seems like that certain ROM is broken. The build.prop file is missing. This is an important file, and it holds data about your phones model, ect. Try flashing a different ROM.
LordDiabeetus said:
Seems like that certain ROM is broken. The build.prop file is missing. This is an important file, and it holds data about your phones model, ect. Try flashing a different ROM.
Which is odd seeing as it is CyanogenMod. Never had a problem with it. Is this CM 10 stable, or a CM 10 nightly?
Click to expand...
Click to collapse
I was trying to install the stock firmware before now I tried a different rom, CyanogenMod 10.1 nightly, and I'm getting
assert failed: getprop("ro.product.device") =="d2tmo" || getprop("ro.build.product") == "d2tmo"
E: Error in /sdcard/cm-10.1-20121224-NIGHTLY-d2tm0.zip
(Status 7)
Installation aborted.
apolanco115 said:
I was trying to install the stock firmware before now I tried a different rom, CyanogenMod 10.1 nightly, and I'm getting
assert failed: getprop("ro.product.device") =="d2tmo" || getprop("ro.build.product") == "d2tmo"
E: Error in /sdcard/cm-10.1-20121224-NIGHTLY-d2tm0.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Uh, it seems like your build.prop is missing or corrupt.
Try using Odin again, and flash the stock from this thread: http://forum.xda-developers.com/showthread.php?t=1949687
That's the last I can think of. Good luck.
LordDiabeetus said:
Uh, it seems like your build.prop is missing or corrupt.
Try using Odin again, and flash the stock from this thread: http://forum.xda-developers.com/showthread.php?t=1949687
That's the last I can think of. Good luck.
Click to expand...
Click to collapse
Thank you so much for your help. A website like was precisely what I spent about 3 hours looking for. I was able to flash the stock back on and now my phone boots normally thank you once again.
No problem man, glad to help! From now on, make sure you make a backup before you flash, either from recovery, or another app, or from your desktop!
Sent from my SGH-T999 using xda app-developers app
Same Exact Issue
Hey there, I'm having the same exact issue with the same phone.
I have a Galaxy S3 T999 and I'm stuck at my stuck at the Samsung start up screen. I rooted my phone today and I'm not really having trouble understanding all of this, but I am new to it.
Everything was going fine until I decided to try and install a new rom to my phone.
I installed Titanium Back-up and ROM Manager/Recovery mode (whatever it's called)
[[sorry for not being that detailed -for my situation is exactly like the one before me so I'm sparring every detail and I'd just be repeating everything above]]
After researching for hours and following every step, I ended up getting an error (the same as his) Error 7 or something like that when trying to install new rom (It was a Pac Rom version and I really expected it to work) and now the only thing I can do with my phone is go into download mode and recovery mode...
Being cautious that something like this would happen I backed up my whole phone's state with the recovery app but OF COURSE that didn't work because when I try to restore/backup, I get a md5 mismatch.... (and when I researched that, many people had the same 'mismatch error' when trying to restore last rom but the only way of fixing that is renaming and/or deleting some files in my phone -which I cannot access due to the lack of function after the start up screen...)
I really just want any rom to work at this point, I haven't been this frustrated in a long time.
I researched everything before taking every step but apparently staying up all night until 10 a.m. the next day doing what I thought was "Backing Up" my phone so nothing went wrong was a COMPLETE waste of time because EVERYTHING went wrong. :good:
Please HELP
(I don't have extra sd card, can't I just use the sd card I already have....)
Oh, and now my phone won't even turn on
it being dead is probably the most likely cause but for some reason it's not charging plugged up to my computer or wall charger....
what now????
kayrealist said:
Hey there, I'm having the same exact issue with the same phone.
I have a Galaxy S3 T999 and I'm stuck at my stuck at the Samsung start up screen. I rooted my phone today and I'm not really having trouble understanding all of this, but I am new to it.
Everything was going fine until I decided to try and install a new rom to my phone.
I installed Titanium Back-up and ROM Manager/Recovery mode (whatever it's called)
[[sorry for not being that detailed -for my situation is exactly like the one before me so I'm sparring every detail and I'd just be repeating everything above]]
After researching for hours and following every step, I ended up getting an error (the same as his) Error 7 or something like that when trying to install new rom (It was a Pac Rom version and I really expected it to work) and now the only thing I can do with my phone is go into download mode and recovery mode...
Being cautious that something like this would happen I backed up my whole phone's state with the recovery app but OF COURSE that didn't work because when I try to restore/backup, I get a md5 mismatch.... (and when I researched that, many people had the same 'mismatch error' when trying to restore last rom but the only way of fixing that is renaming and/or deleting some files in my phone -which I cannot access due to the lack of function after the start up screen...)
I really just want any rom to work at this point, I haven't been this frustrated in a long time.
I researched everything before taking every step but apparently staying up all night until 10 a.m. the next day doing what I thought was "Backing Up" my phone so nothing went wrong was a COMPLETE waste of time because EVERYTHING went wrong. :good:
Please HELP
(I don't have extra sd card, can't I just use the sd card I already have....)
Click to expand...
Click to collapse
So what I did was I used the link above your post to download a rom that I could flash with Odin and that worked. This was the link btw http://forum.xda-developers.com/showthread.php?t=1949687
HI guys so i have been at this for a few hours now i was going to update my roms to 4.2.2
did a full backup and then did a wipe and the problem started the roms was not good so installation was aborted. when i connected the computer to phone after putting it in download mode so i could load stock roms and then load up back up the computer doe not recognize the phone.
THe CWM version 5.5.0.4 does not allow me to look at my sd card for some reason.... is my phone done?
so the backup was saved on teh phone thats why i moved it using file explorer to sd card ...
any way i can talk to my phone well make my computer talk to my phone.....i know it used to connect to me computer with no issues.
systemdude2 said:
HI guys so i have been at this for a few hours now i was going to update my roms to 4.2.2
did a full backup and then did a wipe and the problem started the roms was not good so installation was aborted. when i connected the computer to phone after putting it in download mode so i could load stock roms and then load up back up the computer doe not recognize the phone.
THe CWM version 5.5.0.4 does not allow me to look at my sd card for some reason.... is my phone done?
so the backup was saved on teh phone thats why i moved it using file explorer to sd card ...
any way i can talk to my phone well make my computer talk to my phone.....i know it used to connect to me computer with no issues.
Click to expand...
Click to collapse
Your recovery version is pretty old, considering cwm 6.0.3.6 is the newest...
So is there anyway to fix this ?
Download ROM Manager from the PlayStore and let it install the latest CWM, or download GooManager and have it install TWRP.
So far as the computer, you'll need to be more specific about 'talk to'.
Might need drivers, might need a new cable, can't tell from what you said.
I think if he wiped already he wont be able to download from the play store, if im reading the OP correctly, you already wiped the device, you flashed the 4.2.2 or 4.2 and it aborted..correct?
Step 1. Okay here's what you can do since the PC isnt reading your phone, reboot or restart your pc put phone in odin/download mode and see if it reads it now. If it does Odin a stock rooted rom, then get goomanger from the play store and install open script recovery which will give you the twrp recovery, then you can attempt the flash again of the 4.2 based rom.
Step 2. If it still isnt reading after a pc restart load your old rom on an sd card and try to flash the old tw rom with that older cwm recovery and see if you can get back at least to a tw rom. If that doesnt work then pull the battery out your phone let it sit for 2min, put the battery back in and get into odin/download mode, and see if pc recognizes the device and connection, if it doesnt, download kies and it might help with the connection issue.
Did that help bro. Let me know?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Op stated the he made a full backup. Should be able to boot directly into recovery and restore the backup?
thanks for the info everyone . the operating system is gone so no luck on play store.
mrkevo3000 yes the roms got aborted half way its weird why it would do that.... my phone has always had issues.
just like that as i am typing this my phone is now recognized by odin so i will what you said load up stock and the reflash my backup and then update cwm.
I will try and update and againg to 4.2.2 and let you know what happens.
I have seen so many flavors any preference one somethiong that might work on i747m ?
ill update this after recovering my phone and attempting reflash.
Also for some reason my sd card is not recognized by cwm and it is only looking at internal again never did this to me before thats why i got stuck.
Last time i attempted a update for some reason my apn settings were locked and could not be changed.
I did the same stupid thing myself. Really can not believe I did it but i was rushing and didn't read what it was, thinking i was doing something else. Was not worried as I had my trusty nandriod backup -.- . I guess I can consider myself lucky as i took it to telus hoping they would buy my story and they sent it to the samsung repair center. Worried all week that if they checked it would be clear i had voided the warranty and i would be paying a high repair cost or buying a new phone. Well I got the phone back an hour ago and they fixed it.... no charge. I guess I can consider myself very lucky.
systemdude2 said:
thanks for the info everyone . the operating system is gone so no luck on play store.
mrkevo3000 yes the roms got aborted half way its weird why it would do that.... my phone has always had issues.
just like that as i am typing this my phone is now recognized by odin so i will what you said load up stock and the reflash my backup and then update cwm.
I will try and update and againg to 4.2.2 and let you know what happens.
I have seen so many flavors any preference one somethiong that might work on i747m ?
ill update this after recovering my phone and attempting reflash.
Also for some reason my sd card is not recognized by cwm and it is only looking at internal again never did this to me before thats why i got stuck.
Last time i attempted a update for some reason my apn settings were locked and could not be changed.
Click to expand...
Click to collapse
I would use odin 1.85 and odin a rooted stock 4.1.2 rom.. then go to the playstore and download goomanger and get the teamwin recovery, by hitting menu inside goomanger app, and installing the open script recovery which will install the teamwin recovery, you can flash any pure google rom with that recovery, before you do make a nandroid of your current setup and then flash away, get into a habit of doing at least one back and check the md5 hash of the roms before you flash away... download using your pc instead of phone browsers, sometimes mobile browsers corrupt the files.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Please need help eMMc dump for i747 At&t s3
danvee said:
Download ROM Manager from the PlayStore and let it install the latest CWM, or download GooManager and have it install TWRP.
So far as the computer, you'll need to be more specific about 'talk to'.
Might need drivers, might need a new cable, can't tell from what you said.
Click to expand...
Click to collapse
Hello good morning i am in need of your help. I need a eMMC dump of a rooted AT&T sgh i747
Run this as root from a working SGH-i747:
Code:
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
Please help me out really need the help. let me know if you can. Thank you for even reading my request.
i was running cm12 with no probs on htc one m9
then by mistake i installed the new update and it was cm13.
after the phone rebooted i got google play error saying i need to update google play.
downloaded the latest gapps6 but when trying to install in recovery mode from internal phone memory (as sd card for some reason is not mounted anymore) it gives an error E: FAILED TO MAP
is there a way to go back to cm12 or fix these faults on cm13?
Linx78 said:
i was running cm12 with no probs on htc one m9
then by mistake i installed the new update and it was cm13.
after the phone rebooted i got google play error saying i need to update google play.
downloaded the latest gapps6 but when trying to install in recovery mode from internal phone memory (as sd card for some reason is not mounted anymore) it gives an error E: FAILED TO MAP
is there a way to go back to cm12 or fix these faults on cm13?
Click to expand...
Click to collapse
Install gapps immediately after rom installation, do not allow a full boot..
There is also an issue with the SD and the way it's read, this is an android M issue.
dladz said:
Install gapps immediately after rom installation, do not allow a full boot..
There is also an issue with the SD and the way it's read, this is an android M issue.
Click to expand...
Click to collapse
that's the problem, i didn't realize it's cm13 (thought it's another cm12 nightly) till rebooted the phone...
now it won't allow me to install anything at all giving that e: map... error.
Linx78 said:
that's the problem, i didn't realize it's cm13 (thought it's another cm12 nightly) till rebooted the phone...
now it won't allow me to install anything at all giving that e: map... error.
Click to expand...
Click to collapse
Ask in the forum mate, where u got the rom from.
dladz said:
Ask in the forum mate, where u got the rom from.
Click to expand...
Click to collapse
i'm really sorry if i posted in wrong place... (please direct me in the wright way)
the rom itself was downloaded automaticaly on the phone as an update and i pressed the option update, so the phone rebooted itself into recovery installed it and then i rebooted the phone myself not even looking what was installed... the rest you already know...
Linx78 said:
i'm really sorry if i posted in wrong place... (please direct me in the wright way)
the rom itself was downloaded automaticaly on the phone as an update and i pressed the option update, so the phone rebooted itself into recovery installed it and then i rebooted the phone myself not even looking what was installed... the rest you already know...
Click to expand...
Click to collapse
You will have to have downloaded the rom from xda surely? The Rom you downloaded initially I assume was cm 12.1, then you updated to cm 13, that thread is in the original android development section, I'm sure you can find your way there as you've been there before. The thread is now called cm13 I believe..
Also make sure you're on the latest TWRP recovery, I'm guessing you are but it'd be nice to be sure.
Might also be worth downloading G apps from the cm13 thread then rebooting to recovery, flashing the rom again and installing gapps whilst once complete, don't allow a reboot.
Wiping cache and dalvic will be fine, don't perform a full wipe just incase you can't install the rom again.
If you get stuck, you can push files to your phone using recovery and the push command..
Not 100% but I think storage works via TWRP, could be wrong about that and I've not tested it with cm13.
Either way you have a way back..
---------- Post added at 06:55 PM ---------- Previous post was at 06:55 PM ----------
Install from your internal memory not your SD card. Get the necessary files on your internal memory instead.
thank you very much, will try there.
yes, you are right, got rom from xda and i'm on latest recovery, but no matter what i do, even after wiping cashe still getting the bloody
E: failed to map file
Installation aborted
Linx78 said:
thank you very much, will try there.
yes, you are right, got rom from xda and i'm on latest recovery, but no matter what i do, even after wiping cashe still getting the bloody
E: failed to map file
Installation aborted
Click to expand...
Click to collapse
i can't post anything there... not enough posts...
did i brick my phone now? or is there a way to clean install? recovery mode won't work...
Linx78 said:
i can't post anything there... not enough posts...
did i brick my phone now? or is there a way to clean install? recovery mode won't work...
Click to expand...
Click to collapse
No it'a not bricked..
Are you installing from internal or external memory?
Connect your phone to your computer and go to recovery, then mount storage in recovery, copy G apps to internal memory.
Make more posts in here, i think you need ten
I tried it and found Android 6.0 is having issues with my PC, not recognizing my SD Card, not even the Internal SD !!! :S I know it is pure Super fast but i cant live without connecting my phone to PC.
Also I tried to flas Gapps just after installing MM (not reboot and with Aroma) and the installation freezes, so im stuck with pure Android no Google Apps, so I did return to Lollipop VipeOne 3.5.0 with a full backup made with TWRP.
Sorted. Avoid it til it'a fixed like me unless you want to be a Guinea pig.
dladz said:
Sorted. Avoid it til it'a fixed like me unless you want to be a Guinea pig.
Click to expand...
Click to collapse
sorry, i did copy everything onto internall memory, still no luck...
also the cm13 updated the recovery aswell, and i can't even do a factory reset...
please is there a way to go back to cm12.1?
once again i can't install anything in recovery mode.
Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.
dladz said:
Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.
Click to expand...
Click to collapse
that wasn't my post, some else posted here too...
i'm stuck, adb won't install anything too
LLegion said:
I tried it and found Android 6.0 is having issues with my PC, not recognizing my SD Card, not even the Internal SD !!! :S I know it is pure Super fast but i cant live without connecting my phone to PC.
Also I tried to flas Gapps just after installing MM (not reboot and with Aroma) and the installation freezes, so im stuck with pure Android no Google Apps, so I did return to Lollipop VipeOne 3.5.0 with a full backup made with TWRP.
Click to expand...
Click to collapse
i wanted to ask how to go back to cm12.1 from cm13?
i don't have any backups, nor my recovery is allowing to install anything as per post above...
adb method is not working either, just says waiting for the device when rebooted to download and nothing else.
also my firmware is 2.10..... is that an issue?
dladz said:
Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.
Click to expand...
Click to collapse
i also tried install recovery through adb, didn't work, just says waiting for the device and nothing happens
Linx78 said:
i also tried install recovery through adb, didn't work, just says waiting for the device and nothing happens
Click to expand...
Click to collapse
Nah i'm on 2.10 that's fine.
At this point it appear to be an issue with CM13 rather than anything else, I'm not up to speed with Android 6.0 so I think it would be best if you asked in the thread, you've made over 10 posts now so i'm assuming you can post there.
See what they say, let them know what you've done so far, someone will have either been through it or will know what to do.
Sorry i can't be of more help mate.
PS: Just thought of something, if you have connectivity to your computer / laptop, update your recovery if you haven't already, chances are it's an issue with cm13 but might be worth a try.
I had similar problem - Google Services crashing after unintentional update to CM13.
I realized that I need to install new GApps to fix the issue but GApps installation in recovery was constantly failing.
I used to have some recovery there, I even don't know which one, but during update to CM13 the recovery has been changed to some kind of CM recovery.
After installing TPRW recovery (ir forked for me from the TPRW Manager App from play store) I was able to install Nano GApps.
It solved the issue with Google Services crashing, now I got some Wizard crashing. The issue with crashing wizard is solved by going to privacy setting and allowing the wizard all rights. Later I realized that many other applications were crashing on start as well. I solved it for each of them by uninstalling and installing from Play Store again.
So, I got a Samsung Galaxy A5 2017 (SM-A520F)
I've recently installed Nougat 7.0 after having another OS. I also rooted that OS, but I got some problems like camera not starting etc..
Then I come back installing Nougat and everything works fine. But I would like to root it as well. I install TWRP ricovery and everything it's fine. Then I install Super SU and there everything it's fine, it says "done", but it also come up with a message like "Couldn't mount /data". And when I boot my phone it says "Unable to restart. Verification failed bla bla..." and there is also a reset button. But if I use it, it brings me back to TWRP and there... it can't wipe everything and there's again "couldn't mount /storage" or something similar.
Now, I also tried using different recoveries like TWRP 3.1-0-0 unofficial, different installations of TWRP 3.0-2-0 but still, nothing. I then tried using another installation of nougat, the september one, nothing again. Finally, I used another SuperSU and nothing. Is there any solution?
I also forgot to mention that previously I had nougat and I successfully rooted it! But, camera and other things didn't work.
Sorry for my bad english, I'm italian thanks in advance!
Have you tried the cwm a520f recovery?
This worked for me.
Also try installing the "no-verity-no-encrypt_ashyx.zip"
Hi7m3up said:
Have you tried the cwm a520f recovery?
This worked for me.
Also try installing the "no-verity-no-encrypt_ashyx.zip"
Click to expand...
Click to collapse
I've just tried, the installation doesn't reports error but it doesn't work anyway: same error.
When this happened to me it seemed to be when I used supersu v2.79 size 5.62 Mb however when I downloaded it from another site the size of the zip file changed to 5.67 Mb (same version v2.79)
Also I found although I'm not 100% that when I used twrp recovery that the same thing happened to me each time and I used cwm recovery to root then changed to twrp after root was gained.
It might be worth mentioning I think I pressed the factory reset when the no-verity-no-encrypt screen appeared and changed recovery to cwm it took me a few goes to get root but I'd start with supersu file make sure it's 5.67mb
AN1MuSS said:
I've just tried, the installation doesn't reports error but it doesn't work anyway: same error.
Click to expand...
Click to collapse
That's because you need to FORMAT your data partition after flashing.