Hello. This is my first time posting here, but I've used this a fair amount on previous phones to get root and rom's on. Sorry the links aren't links, as a new member I'm not allowed to post outside links.
I recently bought an Xperia Z2 online. I've spent the last few days trying to install cyanogenmod on the phone to no avail. Currently. So I'll outline the full process I'm using. I initially unlocked the phone using fastboot and sony official unlock method. I don't know fully if that carries over, or if it's problem if not. Then I flash on D6503_17.1.2.A.0.314_UK_Generic.ftf with the flashtools program. Using this video link watch?v=oEWheFGJRJ0, including all their specified files, I then root the phone, which is all fine. Then using another of his videos, watch?v=ubwdracEvyc , I install TWRP recovery, however his link is broken and I instead use the most updated zip file in the xzdualrecovery tab of nut.xperia-files.com. Downloading the latest xperia z2 nightly build from cyanogenmod website, I then load that onto the sd card, backup my system then do a full reset+wipe. It's here that I run into my erros. After clicking install from zip and selecting the CM12 nightly build, it begins running through the script and will then abort installation with the error
"This build is for D6502, D6503.. Sirius; This phone is "Castor"
Castor being the xperia z2 tablet. Loading on the Castor CM build will soft brick the phone and require a fresh restart from stock rom.
Loading up CM12's script file and removing the checks for phone version, I then get the following script install problem with no error code or message.
Installing update...
E: installation aborted
I've tried this with another rom with literally the same 2 issues.
Does anyone know what is going on and how I can fix it to install CM.
thallazar said:
Hello. This is my first time posting here, but I've used this a fair amount on previous phones to get root and rom's on. Sorry the links aren't links, as a new member I'm not allowed to post outside links.
I recently bought an Xperia Z2 online. I've spent the last few days trying to install cyanogenmod on the phone to no avail. Currently. So I'll outline the full process I'm using. I initially unlocked the phone using fastboot and sony official unlock method. I don't know fully if that carries over, or if it's problem if not. Then I flash on D6503_17.1.2.A.0.314_UK_Generic.ftf with the flashtools program. Using this video link watch?v=oEWheFGJRJ0, including all their specified files, I then root the phone, which is all fine. Then using another of his videos, watch?v=ubwdracEvyc , I install TWRP recovery, however his link is broken and I instead use the most updated zip file in the xzdualrecovery tab of nut.xperia-files.com. Downloading the latest xperia z2 nightly build from cyanogenmod website, I then load that onto the sd card, backup my system then do a full reset+wipe. It's here that I run into my erros. After clicking install from zip and selecting the CM12 nightly build, it begins running through the script and will then abort installation with the error
"This build is for D6502, D6503.. Sirius; This phone is "Castor"
Castor being the xperia z2 tablet. Loading on the Castor CM build will soft brick the phone and require a fresh restart from stock rom.
Loading up CM12's script file and removing the checks for phone version, I then get the following script install problem with no error code or message.
Installing update...
E: installation aborted
I've tried this with another rom with literally the same 2 issues.
Does anyone know what is going on and how I can fix it to install CM.
Click to expand...
Click to collapse
try reflashing a Stock FTF using flashtool then try again, if you run furthur into issues then im not quite sure what you can do.
Related
Noobie here. But I have been ultra careful in checking and rechecking all the methods for preparing my Xperia Mini and flashing custom roms (I've read many threads on XDA and watched loads of YouTube videos).
Here's my problem. Using CWM, I flashed the correct MIUI rom for my st15 mini. I then went immediately to flash the correct kernel for this.
In CWM the only option is to flash a '.zip' file... but as the kernel I placed onto the SD card is a '.img' file... CWM didn't not find it in the list of files available to flash.
After seaching everywhere to try to find out what I'd done wrong, I had no choice but to tell CWM to exit and close down the phone.
Now, the phone starts itself and gets stuck on the SE boot screen. And it's impossible to get back into CWM. Sony's program for restoring the system recognizes the phone but instructs me to launch it before it will restore (which, of course, I can't do). Flashtools also recognizes it but doesn't seem to want let me flash anything to it.
Clearly the problem is the phone cannot now find a kernel to boot with.
ANY help on fixing the problem - and letting me know where I went wrong in flashing - would be very much appreciated.
Okay, so this is what happened:
1) I received the OTA update and everything went fine with upgrading the my T-mobile Springboard tab to ICS 4.0.3
2) I then got brave and went ahead with rooting and installing SU using the technique described in "Root Stock T-Mobile Springboard" by xdajunkman. That worked fine and I was able to get CWM recovery installed.
3) I then tried to install the [ROM][ICS] [Unofficial] Root-ready Huawei/Springboard International ROM and downloaded the dload folder to my SDCard, etc. I tried using the dload folder with the ulmt.cfg file in it and that failed with a "Installation aborted" message. I then removed that file and tried to go into CWM and tried "Install from zip" approach. Same thing...installation aborted message.
4) So, then I did the next stupid thing...in CWM, I formatted my /system, /data, and /cache. That was a big mistake! I now have officially bricked by tab.
5) I tried to get rid of CWM recovery by extracting the recovery.img file from the stock rom zip file. I fastboot flashed that to the recovery and recovery2 partitions. I then thought, let me try extracting the update.zip from the stock rom zip and put that on the root of my sdcard and tried to install that. No go...it just says, update failed with a big red "FAIL" message in the center.
6) I then tried to install CM10, to see if that would work. I downloaded the TWRP recovery and also the CM10 ROM .zip file, along with the google apps zip. I flashed the TWRP recovery using fastboot. That worked fine. I was also able to install the CM10 Rom, or at least it reported back "Successful". Same with the google apps zip. But then when I reboot, it only gets to the T-mobile Splash screen and stays there forever.
Please help! I tried to install the Stock Rom using the TWRP recovery, but again, it reports "Installation aborted." So, what am I doing wrong or what can I do to fix this?
Thanks.
[UPDATE] -
Okay, so I actually tried installing CM10 again using the TWRP recovery since it said that it was "Successful." And sure enough, it was successful, it seems. Once I installed it, rebooted the tablet and waited on the T-mobile Springboard screen for about 10 minutes, it launched CyanogenMod. I then set up the tablet with CM10. I had received the unlock code from T-mobile and so my tablet was sim unlocked. I put a AT&T sim card and sure enough it got signal and I was able to surf the web and make phone calls. I downloaded the speed test app from the Play Store and noticed that I was getting about 1.5Mbps download and about 600kbps upload. Not bad. The problem I noticed is that I can't receive calls. I can call out, but when someone tries to call me, the tablet doesn't acknowledge an incoming call. The caller just goes straight to voicemail. I do get a voicemail alert.
So, I don't know whether that is an issue with the CM10 build or a problem in my network / APN settings.
I would like to get the rooted T-mobile International stock ROM on there so that I can try it with that. I'll keep you all posted.
Thanks!
9 times out of 10, I get installation aborted errors because of a botched download. Try downloading the file again, and if available, verify that the MD5 sum of your downloaded file matches the one provided by the developer.
And if I'm not mistaken, TWRP recovery and CWM recovery aren't capable of flashing the T-Mobile stock recovery. If you have TWRP working properly, I would continue trying to flash one of the unlocked ROMs available. I highly recommend HWMOD's ICS (available here)
Best bet would be to fastboot flash the recovery img from the hauwei site update.zip. Then do the standard pop the stock hauwei update.zip on the sd card and do the normal upgrade method. That should full wipe the phone and then you can start tinkering with it again. Also huawei posted the offical root on their site.
nightanole said:
Best bet would be to fastboot flash the recovery img from the hauwei site update.zip. Then do the standard pop the stock hauwei update.zip on the sd card and do the normal upgrade method. That should full wipe the phone and then you can start tinkering with it again. Also huawei posted the offical root on their site.
Click to expand...
Click to collapse
I don't want to mix up the T-mobile images with the Huawei images. Even though I've screwed things up already. But, if you read my previous post, I've got CM10 working, but no incoming calls.
Hello guys,
as a last resort I turn to you for help. Have been searching for the answer for the last 2 days. I am running CWM-based Recovery v.6.0.1.1 and have a rooted x10 together with an unlocked bootloader. I flashed the recovery without any problems and installed miui v4 but an older file which was very unstable (without any problems). Then I decided to install the newer version so i downloaded it, placed it on my sdcard and in the same recovery flashed rom. Unfortunately I had my usb cable plugged in all the time (during installation). Installation got stuck in the middle and nothing could be done so i removed the battery and started the phone again (this time without the usb cable). When I tried to reinstall that rom again it gave me status 7 error installation aborted, assert failed:getprop,error in sdcard and things like that. So I tried the ROM which had already worked on my phone but received exactly the same message. What is more usb storage mounting in the recovery doesnt work anymore (but it already worked!). Now the problem is that I don't have any system installed and when i try to flash the recovery again, flashtool does not recognize my phone (so does windows) and so it leads me nowhere. I think this is definitely problem with the recovery, after the failed attempt to install rom when i had to remove the battery it does not behave normally. Is there any way that I can maybe install another recovery from .zip - i do not even know whether it will install or just sends me another error. Any help would be greatly appreciated
SqU33z3R said:
Hello guys,
as a last resort I turn to you for help. Have been searching for the answer for the last 2 days. I am running CWM-based Recovery v.6.0.1.1 and have a rooted x10 together with an unlocked bootloader. I flashed the recovery without any problems and installed miui v4 but an older file which was very unstable (without any problems). Then I decided to install the newer version so i downloaded it, placed it on my sdcard and in the same recovery flashed rom. Unfortunately I had my usb cable plugged in all the time (during installation). Installation got stuck in the middle and nothing could be done so i removed the battery and started the phone again (this time without the usb cable). When I tried to reinstall that rom again it gave me status 7 error installation aborted, assert failed:getprop,error in sdcard and things like that. So I tried the ROM which had already worked on my phone but received exactly the same message. What is more usb storage mounting in the recovery doesnt work anymore (but it already worked!). Now the problem is that I don't have any system installed and when i try to flash the recovery again, flashtool does not recognize my phone (so does windows) and so it leads me nowhere. I think this is definitely problem with the recovery, after the failed attempt to install rom when i had to remove the battery it does not behave normally. Is there any way that I can maybe install another recovery from .zip - i do not even know whether it will install or just sends me another error. Any help would be greatly appreciated
Click to expand...
Click to collapse
Flash tool recognize your phone? if yes flash any stock firmware and start over
quintas84 said:
Flash tool recognize your phone? if yes flash any stock firmware and start over
Click to expand...
Click to collapse
When I want to flash .tft file and i go to flash mode it does not recognize my phone in windows even though I have installed all the necessary drivers. It starts to flash but then says flashing aborted (this did not happen before, i could flash without any problems). Another problem is that i do not have any rom installed right now so i cannot even switch debugging on and if i remember right, i left debugging off in my previous rom.
Use Sony Update Service. Download from Sony site and install on PC. Follow the instruction, and this will reflash Stock Rom and Kernel (GB 2.3.3). Then, with latest Flashtool, first Root phone again, then flash whatever you want (custom kernels, roms..). You don't need to unlock bootloader again. It remains unlocked.
Sent from my X10i using xda premium
Dzufa said:
Use Sony Update Service. Download from Sony site and install on PC. Follow the instruction, and this will reflash Stock Rom and Kernel (GB 2.3.3). Then, with latest Flashtool, first Root phone again, then flash whatever you want (custom kernels, roms..). You don't need to unlock bootloader again. It remains unlocked.
Sent from my X10i using xda premium
Click to expand...
Click to collapse
Omg - I found solution to my problem - I just changed usb port and it started to flash even using flashtool. Still, many thanks since it helped me find solution
I know this has been mentioned elsewhere for other Xperia Models, typically newer than the Z U, but I am running in to an issue where my two z ultras are trying to use the same mac address.
I wondered if there was a device specific work around for the z ultra and / if this is being addressed.
Running the latest nightly CM12 builds.
Cheers in advance.
http://d-h.st/agR
Download this zip and flash, it is a fix for when the mac address changes after flashing a custom rom.
Regards
Hi,
Thanks for the post, but unfortunately I am getting a package verification error and a footer error when I attempt to flash the package in recovery.
You are using cyanogenmod recovery, right? If so, you have to use TWRP or CWM to flash it, cm recovery have signature check and you can't turn it off, all custom recoveries have it disabled by default.
Regards
Thanks for the heads up teddy. I was using CM recovery. Installed TWRP and flashed the zip/update. However, CM12 goes tits up with TWRP every time I update CM12 and only seems to play nice with CM recovery. Gapps seems to be the issue with none stop force stops. Seems in order for this to work I have to flash TWRP, flash the mac address zip and then flash CM recovery back every time I want to update via nightly.
You can flash TWRP to the FOTAKernel partition if you don't want to flash it everytime you update rom and if you flash it, it should work like CM recovery and it will be booting instead of CM recovery. Just download an app called Rashr and install TWRP from the app I assume the fix is working for you, isn't it?
Regards
I did use rashr to install TWRP and that's when the issues arose.
Unfortunately the nightly update came through after installing TWRP so I did the update for 30th and the phone was in an unusable state via gapps force closes as mentioned. So I flashed back to CMr via the update and haven't installed the update yet.
Until I have a workable solution to the recovery issue I won't be proceeding. It will be too much hassle each time the updates arrive.
I don't think that gapps are force closing because of the recovery installed, that would be weird. Have you tried flashing another gapps? Because I have also used CM12 with TWRP and gapps and I haven't got that sort of problems, even now I am using CyanideL (CM12-based) with TWRP and on my configuration it is OK. I will try using CM12 nightlies with TWRP tomorrow and I will write you back if I found a solution
Regards
Yes, I was using the signed gapps dated late last year, but when I came across the issue I reflashed the whole of CM12 with the more recent ones dated April I think. I still had the same problem, which is when I read up and saw it was attributed to using a non-CM recovery and reset everything back to CM12 nightly + CMr, I did however keep the most recent gapps. Let me know how you get on.
I am trying to flash my HTC One M7. I bought this device from T-Mobile.
I am using ClockworkMod Recovery v6.0.4.8 (recovery-clockwork-6.0.4.8-m7.img). However, whenever I try to flash anything, it give me an error. I am using Cyanogenmod snapshot build (cm-11-20141112-SNAPSHOT-M12-m7.zip). Aso tried latest nightly build.
Steps I am following:
Wipe data/factory reset -> Yes - wipe all user data
install zip -> install from sdcard -> select the zip file
Log:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I get same error whenever I try to flash anything. Either it being UPDATE-SuperSU-v2.zip or GAAPPS. I have also tried TWRP (twrp-2.8.6.0-m7.img) still same error. Right now, except recovery, hboot and fastboot nothing else is working. When I try to boot the devices, it shows the initial HTC boot screen and gets stuck there.
I am following the instructions from here: wiki.cyanogenmod.org/w/Install_CM_for_m7
What's might be reason for it or where am I going wrong?
Use a different rom. Or a more updated one.
zelendel said:
Use a different rom. Or a more updated one.
Click to expand...
Click to collapse
Found the issue. It was due to safari auto-unzip file after download. I was making a zip of the file again.
I used chrome to download the file and voila it worked perfectly.