Related
Hi,
I'm awfully sorry to bother you, but I'm really stuck.
Been using my XZ for over a year now. Everything stock.
I then unlocked the bootloader, rooted it and flashed the latest stable release of CM (didn't use the flashtool for any of this)
CM was totally fine for me except for the camera app.
So I searched the board for a ROM that is better suited for my needs and found this:
http://forum.xda-developers.com/xperia-z/development/rom-existenz-ultimate-1-0-0-light-dark-t2779949
And this is where my problems began -->
Flash official Sony's 4.2.2 10.3.1.A.2.74 or 10.3.1.A.2.67 with flashtool (http://forum.xda-developers.com/show....php?t=2162907)
Even after hours and hours of tying, I cant get this working.
What I did so far:
Installed flash-tool; java development kit, android development kit, adb & fastboot drivers (via several different methods)
Windows (Win 7 64 Bit) recognizes my device as Sony Sa0107 when connected in normal mode.
And it recognizes it as S1 Device when connected in fastboot mode.
So, when I start the flashtool and get to the point where flashtool prompts me to connect my device in fastboot mode this happens:
it says that it didn't recognize my device and I have to search for the device in a list. I click on the XZ entry and flashtool then gets stuck. Just shows the screen where it says you to connect in fastboot.
I even tried to create cwm flashable zip to get around using the flashtool...but this didnt work out..
Has anyone any idea what I could have done wrong?
J26M377 said:
Hi,
I'm awfully sorry to bother you, but I'm really stuck.
Been using my XZ for over a year now. Everything stock.
I then unlocked the bootloader, rooted it and flashed the latest stable release of CM (didn't use the flashtool for any of this)
CM was totally fine for me except for the camera app.
So I searched the board for a ROM that is better suited for my needs and found this:
http://forum.xda-developers.com/xperia-z/development/rom-existenz-ultimate-1-0-0-light-dark-t2779949
And this is where my problems began -->
Flash official Sony's 4.2.2 10.3.1.A.2.74 or 10.3.1.A.2.67 with flashtool (http://forum.xda-developers.com/show....php?t=2162907)
Even after hours and hours of tying, I cant get this working.
What I did so far:
Installed flash-tool; java development kit, android development kit, adb & fastboot drivers (via several different methods)
Windows (Win 7 64 Bit) recognizes my device as Sony Sa0107 when connected in normal mode.
And it recognizes it as S1 Device when connected in fastboot mode.
So, when I start the flashtool and get to the point where flashtool prompts me to connect my device in fastboot mode this happens:
it says that it didn't recognize my device and I have to search for the device in a list. I click on the XZ entry and flashtool then gets stuck. Just shows the screen where it says you to connect in fastboot.
I even tried to create cwm flashable zip to get around using the flashtool...but this didnt work out..
Has anyone any idea what I could have done wrong?
Click to expand...
Click to collapse
Why are you trying to flash Flash official Sony's 4.2.2 10.3.1.A.2.74 or 10.3.1.A.2.67 with flashtool? If you are rooted and unlocked bootloader, you must have a custom recovery installed? I'm pretty sure that installing of an older official Sony firmware is mentioned at the installing instructions only to be able to root the XZ.
Try this:
1) Backup
2) Reboot to recovery
3) Wipe Data, Cache and Dalvik Cache
4) Flash the rom (existenz-ultimate)
Kariharri said:
Why are you trying to flash Flash official Sony's 4.2.2 10.3.1.A.2.74 or 10.3.1.A.2.67 with flashtool? If you are rooted and unlocked bootloader, you must have a custom recovery installed? I'm pretty sure that installing of an older official Sony firmware is mentioned at the installing instructions only to be able to root the XZ.
Try this:
1) Backup
2) Reboot to recovery
3) Wipe Data, Cache and Dalvik Cache
4) Flash the rom (existenz-ultimate)
Click to expand...
Click to collapse
Hi,
thank you for your reply.
Your version gets me stuck in a bootloop (cm logo).
I didn't need to install an older firmware, I was just using the Auto root files from doomlord “Z_DooMLoRD_CF-Auto-Root-ported_FW-350.img” & “Z_DooMLoRD_insecure_FW-350.img)
Did you wipe cache after flashing cm?
Thank you for your help.
I finally figured out what I did wrong.
I booted my phone in fastboot mode not flashmode (as it clearly stated by the flashtool ^^)
I guess I shouldn't have followed the guides so blindly.
Sorry for the double post, but I cant post in the existenz thread (not allowed to).
Is it possible to install a different theme for this rom (like this one: https://play.google.com/store/apps/...DIxMiwiY29tLm1hYy50aGVtZS5TaW1wbGV4LmJsdWUiXQ.. )
Didn't find an option in this rom
no as that's a cm11 theme and you are now on a stock based rom, have a look in the thread for themes, that's if anyone has made them
First of all I just bought Global Moto G 2014 (XT1063) from US Amazon and that was KXH21.85-23 (not updatable to Lollipop via shared OTA.)
So I did manage to unlocked the bootloader and flashed KXH21.85-17 and tried to flash the "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US" which supposed to flash the Lollipop.
Unfortunately at first it failed to update me because "Printspooler.apk" mismatch the hash check. After attempt to flash (yes, I ignore the abort message and redo the process, It passed.... I don't know why) and stuck at some "xxx.apk" mismatch the hash again. After redo the process and bypass (for unknown reason that redo bypass the mismatch) I stuck at "velvet.apk" mismatch and this time It won't let me bypass and keep going on update to lollipop.
In my theory, Is it possible that I flash KXH21.85-17 from other country? Yes, any XT1063 (latin american, whereever on earth) supposed to flashable, but maybe the different country has slightly different apk. So that's why I failed the hash check.
Can anyone give me a URL or mirror to USA XT1063 for KXH21.85-17 that confirmed updatable to Lollipop? Since SBF-Dev and MotoFirmware is now down I couldn't find any.
I know what I'm saying is sound ridiculous, but I have no other theory that support my conspiracy anymore.
Hi @bankkung, I was facing similar problems. First you'd want to get back to stock kitkat which is up-gradable to Lollipop, so I would suggest downloading this file, http://180upload.com/bzl3ah1wov5g, which is 21.85-17, you can flash this file with fastboot by following this guide http://forum.xda-developers.com/moto-g-2014/general/index-guide-update-to-lollipop-android-t2941340. Next you'd want to download both Lollipop files, the first and second one. (The second one is the newest update that fixes memory management). First file: https://mega.co.nz/#!UoQ02KLQ!22OUNBctGLoAUOMd_frTRT9jgbB3tRPUa4pPqfesGho.. Second file: https://mega.co.nz/#!s8ZSVJDA!SqUWPZODvM4-GYuXo6MC2JWTmpE9_jdyqlH-ycWi78I. Download both of those files and put them somewhere accessible (like your SD card) so you can flash these in stock recovery, so after you downgrade to kitkat you can flash the first one, then boot up and then go back into stock recovery and flash the second file. I'd recommend factory resetting your phone after this to smoothen everything out.
If all else fails you can flash TWRP recovery using this guide http://forum.xda-developers.com/moto-g-2014/development/recovery-twrp-2-8-0-1-moto-g-2014-t2896165, and then download this TWRP backup of the latest Lollipop, and place it in /data/media/0/TWRP/backups/(your device name here). All of that can be done right in TWRP recovery using the file manager (no need to root your phone). https://mega.co.nz/#!59AAiQaR!cPUsNpI5j-ZaIMX10uiS93EJqpLxua-iwKHj30InX1U
I would really recommend the first option tho, just in case any other updates come you can easily upgrade your phone.
Hope I helped!
Lamech242 said:
Hi @bankkungFirst you'd want to get back to stock kitkat which is up-gradable to Lollipop, so I would suggest downloading this file, http://180upload.com/bzl3ah1wov5g, which is 21.85-17, you can flash this file with fastboot by following this guide http://forum.xda-developers.com/moto-g-2014/general/index-guide-update-to-lollipop-android-t2941340. Next you'd want to download both Lollipop files, the first and second one. (The second one is the newest update that fixes memory management). First file: https://mega.co.nz/#!UoQ02KLQ!22OUNBctGLoAUOMd_frTRT9jgbB3tRPUa4pPqfesGho.. Second file: https://mega.co.nz/#!s8ZSVJDA!SqUWPZODvM4-GYuXo6MC2JWTmpE9_jdyqlH-ycWi78I. Download both of those files and put them somewhere accessible (like your SD card) so you can flash these in stock recovery, so after you downgrade to kitkat you can flash the first one, then boot up and then go back into stock recovery and flash the second file. I'd recommend factory resetting your phone after this to smoothen everything out.
Click to expand...
Click to collapse
Hi Thanks for your help
I've done that several time and still having the same problem (yes, mine is unlocked bootloader and flashed-reflashed that 21.85-17 over twenty time right now)
Lamech242 said:
If all else fails you can flash TWRP recovery using this guide http://forum.xda-developers.com/moto-g-2014/development/recovery-twrp-2-8-0-1-moto-g-2014-t2896165, and then download this TWRP backup of the latest Lollipop, and place it in /data/media/0/TWRP/backups/(your device name here). All of that can be done right in TWRP recovery using the file manager (no need to root your phone). https://mega.co.nz/#!59AAiQaR!cPUsNpI5j-ZaIMX10uiS93EJqpLxua-iwKHj30InX1U
I would really recommend the first option tho, just in case any other updates come you can easily upgrade your phone.
Hope I helped!
Click to expand...
Click to collapse
I'm thinking about getting some Nandroid backup (never used TWRP before but I think this methond you gave is the same thing as I think) to get straight from Custom Recovery to Lollipop.
So what I need to do in the 2nd method is
a
flash TWRP
Place TWRP Backup of XT1063 Lollipop
restore
reflash Stock Recovery + Locked recovery
Is this sound corrected?
bankkung said:
Hi Thanks for your help
I've done that several time and still having the same problem (yes, mine is unlocked bootloader and flashed-reflashed that 21.85-17 over twenty time right now)
I'm thinking about getting some Nandroid backup (never used TWRP before but I think this methond you gave is the same thing as I think) to get straight from Custom Recovery to Lollipop.
So what I need to do in the 2nd method is
a
flash TWRP
Place TWRP Backup of XT1063 Lollipop
restore
reflash Stock Recovery + Locked recovery
Is this sound corrected?
Click to expand...
Click to collapse
Yes once you place the backup on your SD card, flash TWRP, reboot into recovery and go to advanced then go to file manager, then finish following the instructions above. Once you place it in the right place then you restore it. As of the stock recovery issue, it wouldn't make much sense to do that unless you followed the first option, where the stock recovery would actually be needed. But if you find a recovery image then yeah. If you do the second method you won't be able to receive updates nor update it manually unless doing the first method.. But the TWRP backup is the latest lollipop so enjoy!
If you still need help you can just flash TWRP recovery, and download this and flash it. http://forum.xda-developers.com/mot...-stock-rom-t2970427/post57438355#post57438355
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Try re download the zip (or try an other rom)maybe you just got an false download. i also had some trouble with my m7 back in the day.
But in your case now you are stuck with no os or bootloop, i give you as advice to follow an soft unbrick method it worked for me, or if you have an usb otg cable and usb or and usb otg thumbstick, put the rom on that usb and connect it to your phone and then try to flash it (if your using twrp you have an option to choose from wich storage you want to use)
Also a piece of advice, when flashing roms, kernels etc please have your phone charged above 50% (just in case).
Sent from my HUAWEI P7-L10 using XDA Free mobile app
---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------
its the peanut said:
Try re download the zip (or try an other rom)maybe you just got an false download. i also had some trouble with my m7 back in the day.
But in your case now you are stuck with no os or bootloop, i give you as advice to follow an soft unbrick method it worked for me, or if you have an usb otg cable and usb or and usb otg thumbstick, put the rom on that usb and connect it to your phone and then try to flash it (if your using twrp you have an option to choose from wich storage you want to use)
Also a piece of advice, when flashing roms, kernels etc please have your phone charged above 50% (just in case).
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Click to expand...
Click to collapse
Also make sure you downloaded the rom made for your phone model!
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Can you please post the output of
Code:
fastboot getvar all
please remove your imei and serial number.
Depending on which variant of the M7 you have you probably just need a different version of recovery to install a CM rom. I think they prefer TWRP 2.7.x.x. Post the getvar and we can see what you have. then I can give you a better informed instruction. :good:
P.s also check the md5 of the rom zip you downloaded. Use this tool www.winmd5.com the correct md5 should be listed with the link you downloaded the rom from
failed to mount /dev/block/blah blah blah = needs "block:by-name" support which twrp 2.6.3.3 doesn't have
everything explained here
So update your recovery
and do what danny said above so he can confirm you have the right rom/recovery for your device.
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Your getvar looks fine this rom should work fine with your device. Download this version of TWRP https://www.androidfilehost.com/?fid=23501681358561860 (2.7.1.2). dropthe file in your fastboot folder and flash it with fastboot.
Code:
fastboot flash recovery "name-of-recovery".img
fastboot erase cache
fastboot reboot-bootloader
Once thats done reflash the rom with the new version of TWRP. It should flash just fine :good:
iv managed to flash cm12.1 now, thanks guys, is there anyway i could get the HTC software back on.
Burky1996 said:
iv managed to flash cm12.1 now, thanks guys, is there anyway i could get the HTC software back on.
Click to expand...
Click to collapse
There are a number of ways to return to stock software. You can simply flash a stock rom through twrp or use a stock nandroid. look for rom that match your version main. 7.19.401.22
I think there is even an lollipop 7.19.401.22 RUU for your device but I'm not sure if it will work with s-on though because it's a zip but it certainly wouldnt hurt to try it though. You will need to relock your bootloader and flash it with fastboot.
I'll edit this post with links when I find them unless some one beats me to it
Hey Dan do you think we could skype and you could talk me through it, it would be much easier?
Burky1996 said:
Hey Dan do you think we could skype and you could talk me through it, it would be much easier?
Click to expand...
Click to collapse
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Danny201281 said:
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Click to expand...
Click to collapse
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
Burky1996 said:
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
Click to expand...
Click to collapse
Okay try this. Download the OTA but select the option "Install Later" connect your m7 to your pc and browse your storage. In the download folder on your phone you should find the OTA in zip format. Copy it to your pc.
Now open the OTA zip on your pc. Inside you'll find another zip called "firmware.zip" extract it then open it. Inside you'll find a recovery.img. extract the recovery file and flash it with fastboot. Now reboot to android and continue to install the OTA. :fingers-crossed:
Sent from my SM-T230 using Tapatalk
im going to have to unlock the boot loader again and then do it
Burky1996 said:
im going to have to unlock the boot loader again and then do it
Click to expand...
Click to collapse
Yes you will need to unlock the bootloader to flash the recovery, Dont forget to fastboot erase cache after flashing the recovery that is cruicial. You don't need to be relocked to install the OTA though.
When you select install now, the device should reboot to the Stock Recovery. At first the screen will just be black for a short while. Then you'll see an image of a phone with a Green ring and download arrow. If you hold Volume up and press the power button you will see the Stock Recovery and its progress in installing the OTA.
I'm not sure why your device was hanging on boot after installing the OTA. Maybe a bad recovery.img. that's why I say to get the recovery from the OTA file.
its still not working so i mite just install twrp and restore to cm12.1
Burky1996 said:
im going to have to unlock the boot loader again and then do it
Click to expand...
Click to collapse
Yes you will need to unlock the bootloader to flash the recovery, Dont forget to fastboot erase cache after flashing the recovery that is cruicial. You don't need to be relocked to install the OTA though.
When you select install now, the device should reboot to the Stock Recovery. At first the screen will just be black for a short while. Then you'll see an image of a phone with a Green ring and download arrow. If you hold Volume up and press the power button you will see the Stock Recovery and its progress in installing the OTA.
I'm not sure why your device was hanging on boot after installing the OTA. Maybe a bad recovery.img. that's why I say to get the recovery from the OTA file.
Danny201281 said:
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Click to expand...
Click to collapse
could it be not working coz my hboot has changed to 1.51.
Burky1996 said:
could it be not working coz my hboot has changed to 1.51.
Click to expand...
Click to collapse
Your still stuck with this? Try starting the process over, but do not relock your bootloader at any point.
Wipe system data and cache partitions with TWRP Advanced wipe
Flash the Rom with twrp as a clean install.
Reboot and download the OTA. Choose install later, then copy the OTA to your pc. Extract the Stock Recovery and flash it with fastboot. Reboot and install the OTA.
But do not relock your boot loader. Because when you unlock the bootloader, it wipes the device including the data/preload folder. If the preload folder is not intact the OTA will fail
Sent from my M7 Running ARHD 92.x
Hey guys
So I just bought a new Z3C and I'm planning on rooting it and installing CM12.1 on it. But before that I wanna make sure I perfectly understood the entire process. So if anyone could help by answering/confirming some of the things below, I would really appreciate that.
First, Sony devices don't come with a default recovery? Did I get that part right? That's why I need to flash a custom one, right? I suppose this is also the reason why I need a custom recovery in order to flash CM12.1 on my phone. Since I don't know if CM can run without one.
Second of all, kingroot. Ok, so this is an app for PC or phone that will root your phone in one click. Still without needing to unlock the bootloader (thus compromising that TA partition), right? It's in Chinese but I guess I don't need to know Chinese to click the only button on the screen. ) So that won't be a problem.
Third, I need root access for the backup part, right? So after running kingroot, I need to make a backup of my DRM stuff, right? It won't be of any use in CM, I suppose. So I just keep it somewhere safe.
Another thing, since I don't already have a custom recovery, I need the "installer" version of that xzdrecovery recovery, right? Cause there is also a flashable zip version of it, and I was wondering how the hell do I install that with no default recovery.
Can CM12 run on a locked bootloader? Probably stupid question. But this forum seems to pack some really interesting tricks I never thought were possible. So...I'm asking.
One thing I didn't quite understand: why do I need to flash part of CM12.1 to have a working recovery? Is the recovery not usable after installing it? Does it need a "simulated" ROM in order to be accessible/visible? I mean, on my SGS4, I just had to have a custom recovery (in my case it was CWM, but I'm not sure there is such a thing for the Z3C) and then just boot into it and flash CyanogenMod ROM or any other custom ROM for that matter. I didn't have to "split" the installation. First the boot.img, and then the rest (which will basically rewrite the boot.img anyway). So this part is still a bit confusing to me. Can anyone explain?
Thank you very much.
arsradu said:
First, Sony devices don't come with a default recovery? Did I get that part right? That's why I need to flash a custom one, right? I suppose this is also the reason why I need a custom recovery in order to flash CM12.1 on my phone. Since I don't know if CM can run without one.
Click to expand...
Click to collapse
As far as I know there really isn't a default recovery for Sony devices so to install CM you will need a recovery.
arsradu said:
Second of all, kingroot. Ok, so this is an app for PC or phone that will root your phone in one click. Still without needing to unlock the bootloader (thus compromising that TA partition), right? It's in Chinese but I guess I don't need to know Chinese to click the only button on the screen. ) So that won't be a problem.
Click to expand...
Click to collapse
I do not recommend kingroot but you can try it if you trust it. I used the xda guide on doing it and it worked fine for me: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343 (takes some time but its worth it if you ever want to go back to factory). As long as the bootloader stays locked the TA partition wont be touched thats right but once you unlock it you will lose all DRM keys and they wont restore if you flash a factory frimware again.
arsradu said:
Third, I need root access for the backup part, right? So after running kingroot, I need to make a backup of my DRM stuff, right? It won't be of any use in CM, I suppose. So I just keep it somewhere safe.
Click to expand...
Click to collapse
Yes you need root to backup the TA parition and yes only Sony roms use the DRM keys, CM doesn't touch them.
arsradu said:
Another thing, since I don't already have a custom recovery, I need the "installer" version of that xzdrecovery recovery, right? Cause there is also a flashable zip version of it, and I was wondering how the hell do I install that with no default recovery.
Click to expand...
Click to collapse
You install it over fastboot pretty much or with locked bootloader you use the Sony flash tool. More here: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Also keep in mind that custom Kernels like "M5 Kernel" come with a pre-installed recovery.
arsradu said:
Can CM12 run on a locked bootloader? Probably stupid question. But this forum seems to pack some really interesting tricks I never thought were possible. So...I'm asking.
Click to expand...
Click to collapse
Im pretty sure its not possible. For not sony kernels you need a unlocked bootloader, otherwise it wont even boot up.
arsradu said:
One thing I didn't quite understand: why do I need to flash part of CM12.1 to have a working recovery? Is the recovery not usable after installing it? Does it need a "simulated" ROM in order to be accessible/visible? I mean, on my SGS4, I just had to have a custom recovery (in my case it was CWM, but I'm not sure there is such a thing for the Z3C) and then just boot into it and flash CyanogenMod ROM or any other custom ROM for that matter. I didn't have to "split" the installation. First the boot.img, and then the rest (which will basically rewrite the boot.img anyway). So this part is still a bit confusing to me. Can anyone explain?
Click to expand...
Click to collapse
Unlike Samsung... Sony devices have no recovery (maybe at a later time?) so you cant just replace the stock recovery with a custom one. You have to take out boot.img because fastboot cant flash entire zips like a recovery, so you flash the boot.img over fastboot which installs the recovery for you.
After that you execute "fastboot reboot" and spam your volume up key till you enter the recovery and from there you can install cyanogenmod and other.
MyPictures said:
As far as I know there really isn't a default recovery for Sony devices so to install CM you will need a recovery.
I do not recommend kingroot but you can try it if you trust it. I used the xda guide on doing it and it worked fine for me: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343 (takes some time but its worth it if you ever want to go back to factory). As long as the bootloader stays locked the TA partition wont be touched thats right but once you unlock it you will lose all DRM keys and they wont restore if you flash a factory frimware again.
Yes you need root to backup the TA parition and yes only Sony roms use the DRM keys, CM doesn't touch them.
You install it over fastboot pretty much or with locked bootloader you use the Sony flash tool. More here: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Also keep in mind that custom Kernels like "M5 Kernel" come with a pre-installed recovery.
Im pretty sure its not possible. For not sony kernels you need a unlocked bootloader, otherwise it wont even boot up.
Unlike Samsung... Sony devices have no recovery (maybe at a later time?) so you cant just replace the stock recovery with a custom one. You have to take out boot.img because fastboot cant flash entire zips like a recovery, so you flash the boot.img over fastboot which installs the recovery for you.
After that you execute "fastboot reboot" and spam your volume up key till you enter the recovery and from there you can install cyanogenmod and other.
Click to expand...
Click to collapse
Alright. Thank you a lot for your answers.
So, to sum up:
First, I need to root my device. You said you would not recommend Kingroot. Ok. But I'm on stock Lollipop right now. And for as far as I understood, in order to get root on it without using Kingroot method, I need to downgrade to KitKat using FlashTool. Did I get it right?
Second, I need to backup my TA partition stuff.
Third, I need to flash the boot.img from CM12.1 flashable zip and then the recovery (flashable zip version of it, right?). In this order. Am I right?
And for the recovery part, I think I'm gonna go with that FlashTool (since I already got it for downgrading to KitKat) or via fastboot (command line), for which I need the Android SDK installed, I suppose?
Forth, unlock the bootloader. I guess I'm gonna have to Google that part. I saw some videos explaining how to do that, so I guess I'm gonna be ok.
Fifth, boot into recovery and flash CM12.1 (finally).
Please, let me know if I got the flow right or if you would make any suggestions/adjustments/corrections to it.
Also, one other thing, I heard people not being able to flash back stock and booting with it, after having a custom ROM installed, even after re-adding the content of the TA partition back and re-locking the bootloader. Any idea how to get this right from the first time, in case I need to revert to stock?
Again, big thank you for your help.
arsradu said:
Alright. Thank you a lot for your answers.
So, to sum up:
First, I need to root my device. You said you would not recommend Kingroot. Ok. But I'm on stock Lollipop right now. And for as far as I understood, in order to get root on it without using Kingroot method, I need to downgrade to KitKat using FlashTool. Did I get it right?
Second, I need to backup my TA partition stuff.
Third, I need to flash the boot.img from CM12.1 flashable zip and then the recovery (flashable zip version of it, right?). In this order. Am I right?
And for the recovery part, I think I'm gonna go with that FlashTool (since I already got it for downgrading to KitKat) or via fastboot (command line), for which I need the Android SDK installed, I suppose?
Forth, unlock the bootloader. I guess I'm gonna have to Google that part. I saw some videos explaining how to do that, so I guess I'm gonna be ok.
Fifth, boot into recovery and flash CM12.1 (finally).
Please, let me know if I got the flow right or if you would make any suggestions/adjustments/corrections to it.
Also, one other thing, I heard people not being able to flash back stock and booting with it, after having a custom ROM installed, even after re-adding the content of the TA partition back and re-locking the bootloader. Any idea how to get this right from the first time, in case I need to revert to stock?
Again, big thank you for your help.
Click to expand...
Click to collapse
- Yes you need to downgrade to a version where that root exploit isn't patched and root that way
- Yea then when you got root and all, you use that tool to backup your TA partition
- Yea after that you unlock your bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ and then you flash boot.img from CM (or a custom Kernel that implements a recovery). After flashing the boot.img you reboot into your recovery and flash the whole Cyanogenmod.zip there (Apply update). I just installed my recovery over fastboot, never actually tried the FashTool way. fastboot.exe is in the Android SDK yeah but you can also just get the small ADB installer which has it too: http://forum.xda-developers.com/showthread.php?t=2588979 (For Linux you need to install it over your package manager I think).
- No. You need to unlock the bootloader before, otherwhise it wont allow you to flash a custom boot.img
Not sure about the restoring process, I kinda don't think that I will move back from CM anyways.
However if I would go back then I would try this:
- Relock bootloader
- Factory reset
- Flash back old sony rom with root exploit over flashtool
- Gain root over that exploit and use the TA Backup tool to restore TA partition
- Install latest Sony ROM and that should work? (Not sure)
Can you post one of those theards where they get issues with restoring? How do they do it?
MyPictures said:
- Yes you need to downgrade to a version where that root exploit isn't patched and root that way
- Yea then when you got root and all, you use that tool to backup your TA partition
- Yea after that you unlock your bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ and then you flash boot.img from CM (or a custom Kernel that implements a recovery). After flashing the boot.img you reboot into your recovery and flash the whole Cyanogenmod.zip there (Apply update). I just installed my recovery over fastboot, never actually tried the FashTool way. fastboot.exe is in the Android SDK yeah but you can also just get the small ADB installer which has it too: http://forum.xda-developers.com/showthread.php?t=2588979 (For Linux you need to install it over your package manager I think).
- No. You need to unlock the bootloader before, otherwhise it wont allow you to flash a custom boot.img
Not sure about the restoring process, I kinda don't think that I will move back from CM anyways.
However if I would go back then I would try this:
- Relock bootloader
- Factory reset
- Flash back old sony rom with root exploit over flashtool
- Gain root over that exploit and use the TA Backup tool to restore TA partition
- Install latest Sony ROM and that should work? (Not sure)
Can you post one of those theards where they get issues with restoring? How do they do it?
Click to expand...
Click to collapse
It was a post in a long thread. I'm not sure I can find it right now.
Anyway, I got stuck at flashing back KitKat. FlashTool says "waiting for flashmode", whike asking me to disconnect my phone, press the back button (I got it that this is for older phones that do have a physical button), and plugging back. Which I did. The result being a very nice animation for charging. The USB debugging is ON. What am I missing here?
Sent from my D5803 using Tapatalk
arsradu said:
It was a post in a long thread. I'm not sure I can find it right now.
Anyway, I got stuck at flashing back KitKat. FlashTool says "waiting for flashmode", whike asking me to disconnect my phone, press the back button (I got it that this is for older phones that do have a physical button), and plugging back. Which I did. The result being a very nice animation for charging. The USB debugging is ON. What am I missing here?
Sent from my D5803 using Tapatalk
Click to expand...
Click to collapse
Did you install the drivers properly and on which Operating system are you flashing it?
MyPictures said:
Did you install the drivers properly and on which Operating system are you flashing it?
Click to expand...
Click to collapse
I would say yes. I mean...after googling a bit, I saw that I actually don't need to just "ignore" that message asking to press the Back button, but to actually press Volume Down instead. Which I did. And I was able to go into Flash Mode. (Flash Tool says "device connected in Flash Mode"). The device was properly recognized in MTP mode. Still, I had to manually install the Flash-tool drivers to get it recognized in flash mode, as well. Not sure why...
I mean, if the phone was properly recognized without manually installing anything (Windows downloaded and installed its own drivers), why the hell do I need to install custom drivers to get it recognized in flash mode? By the way, this "flash mode" is similar to Samsung's "Download Mode", for as far as I could see. And, just like on Samsung's devices, the access is made by pressing the Volume Down upon booting up.
Anyway, even though the device is now recognized in flash mode, I still get an error trying to flash stock 4.4.4.
I get this:
Code:
14/014/2015 21:14:34 - INFO - Please connect your device into flashmode.
14/016/2015 21:16:28 - INFO - Device disconnected
14/017/2015 21:17:03 - INFO - Device connected in flash mode
14/017/2015 21:17:03 - INFO - Opening device for R/W
14/017/2015 21:17:03 - INFO - Reading device information
14/017/2015 21:17:03 - INFO - Unable to read from phone after having opened it.
14/017/2015 21:17:03 - INFO - trying to continue anyway
14/017/2015 21:17:03 - INFO - Start Flashing
14/017/2015 21:17:03 - INFO - Processing loader.sin
14/017/2015 21:17:03 - INFO - Checking header
14/017/2015 21:17:03 - ERROR - Processing of loader.sin finished with errors.
14/017/2015 21:17:03 - INFO - Ending flash session
14/017/2015 21:17:03 - ERROR - Error in processHeader : 1 : Incorrect function.
14/017/2015 21:17:03 - ERROR - Error flashing. Aborted
14/017/2015 21:17:03 - INFO - Device connected in flash mode
And after a while, it automatically reboots in normal mode.
Windows version is Windows 10. But I'm not sure that's the problem here since, as I said, the device does get recognized both in MTP and flash modes. Also, for as far as I could see, other people are having the same issues on other versions of Windows.
Hmm not exactly sure but for Windows 8 and 8.1 (also Vista 64 bit and 7 64 Bit) You sometimes need to disable enforced driver signature.
Are you running the correct executable for your OS?:
FlashTool64.exe for 64 Bit OS and
FlashTool.exe for 32 Bit OS.
Is the device properly recognized in your device manager. Maybe re-downloading the frimware might help.
MyPictures said:
Hmm not exactly sure but for Windows 8 and 8.1 (also Vista 64 bit and 7 64 Bit) You sometimes need to disable enforced driver signature.
Are you running the correct executable for your OS?:
FlashTool64.exe for 64 Bit OS and
FlashTool.exe for 32 Bit OS.
Is the device properly recognized in your device manager. Maybe re-downloading the frimware might help.
Click to expand...
Click to collapse
Yes, I'm running FlashTool64.exe since I'm running a 64-bit version of Windows.
The device is correctly recognized in flash mode (after manually selecting the driver installed with flash-tool). See the attached image for more info.
But indeed maybe I got the wrong firmware. Problem is that I'm not really sure which one should I choose.
I got one called D5803_23.0.1.A.5.77_Customized_FR.ftf. I don't mind it that it's in French. All of them have English anyway.
Also, I saw one for UK here called D5803_23.0.A.2.105_UK.ftf. Seems to be different.... I will try with that as well.
Update: same error with that UK firmware, as well.
Update2: Well I'm half way there. Got 4.4.4 installed and got it rooted. YAY. Still trying to figure out why adb is not correctly running when trying to backup TA.
Update3: ok, backup done too!
Update4: the boot.img that comes with CM12.1 doesn't seem to have a recovery.... Or if it does, I couldn't boot in it so I can flash CM12.1.
I tried the one from Doomlord (Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img) and that seems to be based on CWM v6.0.4.7.
Problem with that is that, even though I can boot into recovery, I can't flash CM12.1. It says error status 7. Any idea why or how to fix this?
I belive error 7 indicates a outdated recovery (CM 12.1 needs a up to date one).
MyPictures said:
I belive error 7 indicates a outdated recovery (CM 12.1 needs a up to date one).
Click to expand...
Click to collapse
Might be. The problem is the device is not correctly recognized upon flashing (it says the device is "Aries" but the ROM is for D5803, D5833, z3c LOL), due to the check made within the updater-script (first line). For as far as I could see, this is a known issue... Not sure why it hasn't been fixed by now.
Anyway, removing that line will get the ROM installed successfully (at least with THAT recovery).
So I'm on CM12.1 , been for a few days now (thank you for your help), and I was wondering if there are any "permanent" recoveries (compatible with CM12.1, of course) that I can flash, something that can give me the ability to boot into recovery (and not Cyanogen Recovery, since that one sucks) and do things like nandroid backup (I know TWRP and CWM can do that, but I couldn't find any permanent version of those (or maybe I just didn't dig deep enough), and I'm not sure they are compatible with CM12.1) and formatting /system. The last one is really important for a clean installation of the ROM, especially since it doesn't look like it's done by the ROM itself.
So I was an idiot, I've resigned myself to this fact because I've clearly done something wrong.
TWRP installed, rooted and booted.
Then I tried to flash a new ROM from here using TWRP and well... that's where things went tits up. Something in TWRP said in red about not being able to mount something. The loading screen was stuck and then it just bootlooped over and over again. I downloaded a stock ROM, wiped system and tried to flash but now it's stuck on the "your device is shifty" screen and I'm totally out of ideas...
Please refrain from pointing out what a moron I've been.
Thanks in advance to anyone who can save this wretched soul.
do you have access to bootloader with fastboot?
seeing a lot of threads like this around here. Don't want to offend you or anybody else but just that someone has said it: First thing you do after flashing TWRP is a backup :angel:
hope you get your things sorted though. Can your please provide a more detailed list of things you did? How did you try to flash the stock rom you downloaded? dload forced update? flashed in twrp? etc.
lomunet said:
do you have access to bootloader with fastboot?
Click to expand...
Click to collapse
I can still get in to bootloader and fastboot mode no problem.
seeing a lot of threads like this around here. Don't want to offend you or anybody else but just that someone has said it: First thing you do after flashing TWRP is a backup
hope you get your things sorted though. Can your please provide a more detailed list of things you did? How did you try to flash the stock rom you downloaded? dload forced update? flashed in twrp? etc.
Click to expand...
Click to collapse
Yeah I realised I should have done that the second things started going wrong, I got cocky. And I tried to flash the stock with TWRP; downloaded it to my laptop, put it on the SD card and then in to the phone. Every process that the installation or wipe or any of the other actions performed by TWRP is followed by a line saying "Failed to mount '/ data' (Invalid argument)". I tried to follow the forced update of the stock but I couldn't seem to get that to work either ( this method stechguide.com/marshmallow-stock-rom-for-huawei-p9 ). After all that I can't think if there's anything else.
zandercook1 said:
I can still get in to bootloader and fastboot mode no problem.
Yeah I realised I should have done that the second things started going wrong, I got cocky. And I tried to flash the stock with TWRP; downloaded it to my laptop, put it on the SD card and then in to the phone. Every process that the installation or wipe or any of the other actions performed by TWRP is followed by a line saying "Failed to mount '/ data' (Invalid argument)". I tried to follow the forced update of the stock but I couldn't seem to get that to work either ( this method stechguide.com/marshmallow-stock-rom-for-huawei-p9 ). After all that I can't think if there's anything else.
Click to expand...
Click to collapse
Ok, so a few things:
-The failed to mount /data message probably means that you have an old version of TWRP, check the thread again and make sure you use at least RC3 (newest one afaik).
-Original stock Huawei roms are not suitable for TWRP, to flash a stock rom you need a stock recovery which you can flash back the same way you flashed twrp (using fastboot, or SRK tools). Once you have stock recovery, you can force the update by putting the update file in a folder on your sdcard (internal or external) called "dload". Then you turn off the phone and start it by holding volume up, volume down and power.
-Alternatively you could use a custom rom, which you can find in the dev thread. Custom roms can and should be flashed in TWRP.
Try relocking botloader and installing stock rom with this tool
http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
clouds5 said:
Ok, so a few things:
-The failed to mount /data message probably means that you have an old version of TWRP, check the thread again and make sure you use at least RC3 (newest one afaik).
-Original stock Huawei roms are not suitable for TWRP, to flash a stock rom you need a stock recovery which you can flash back the same way you flashed twrp (using fastboot, or SRK tools). Once you have stock recovery, you can force the update by putting the update file in a folder on your sdcard (internal or external) called "dload". Then you turn off the phone and start it by holding volume up, volume down and power.
-Alternatively you could use a custom rom, which you can find in the dev thread. Custom roms can and should be flashed in TWRP.
Click to expand...
Click to collapse
I keep pressing the up/down + power buttons but it keeps going to TWRP, as for the out of date version I have 3.0.0-0 but as lomunet suggested I'm downloading the srk tool. That's what I originally used to install TWRP in the first place. For the stock ROM to boot do I need to do anything to the file when it's downloaded (ie zipped or unzipped)? Nosing around a few other threads I noticed they mention something about making a file in the root of the file, and I hope you'll pardon my ignorance, but I have no idea how to do that. As for the custom ROM, I'll try that again when srk tools has finished downloading and I've reinstalled TWRP.
lomunet said:
Try relocking botloader and installing stock rom with this tool
http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
Click to expand...
Click to collapse
And I'd just like to thank you two for your patience!
Edit:
Ok so, I installed the latest TWRP (3.0.2-eva-modaco-rc3) and that went off without a hitch. Using the SRK tools that lomunet suggested I tried to sideload the stock ROM but the error message of " cannot read 'sideload\ROM.zip' " keeps popping up. I'm downloading a custom ROM (forum.xda-developers.com/p9/development/rom-huawei-p9-fromfuture-newworld-t3390820) as I type to see if that works flashing it through TWRP.
zandercook1 said:
I keep pressing the up/down + power buttons but it keeps going to TWRP, as for the out of date version I have 3.0.0-0 but as lomunet suggested I'm downloading the srk tool. That's what I originally used to install TWRP in the first place. For the stock ROM to boot do I need to do anything to the file when it's downloaded (ie zipped or unzipped)? Nosing around a few other threads I noticed they mention something about making a file in the root of the file, and I hope you'll pardon my ignorance, but I have no idea how to do that. As for the custom ROM, I'll try that again when srk tools has finished downloading and I've reinstalled TWRP.
And I'd just like to thank you two for your patience!
Edit:
Ok so, I installed the latest TWRP (3.0.2-eva-modaco-rc3) and that went off without a hitch. Using the SRK tools that lomunet suggested I tried to sideload the stock ROM but the error message of " cannot read 'sideload\ROM.zip' " keeps popping up. I'm downloading a custom ROM (forum.xda-developers.com/p9/development/rom-huawei-p9-fromfuture-newworld-t3390820) as I type to see if that works flashing it through TWRP.
Click to expand...
Click to collapse
if twrp works the rom must be work without problems...
zandercook1 said:
I keep pressing the up/down + power buttons but it keeps going to TWRP
Click to expand...
Click to collapse
clouds5 said:
Original stock Huawei roms are not suitable for TWRP, to flash a stock rom you need a stock recovery
Click to expand...
Click to collapse
you really need to flash stock recovery first to flash stock firmware. It won't work as long as you have TWRP installed you can use SRK tools to flash stock recovery.
If you are always stuck, jus download "DC Phoenix"(i don't know if i'm authorized to post the name ?), it's a paid app but it's worked for me. Just boot to fastboot mode, and flash your firmware with the app
clouds5 said:
you really need to flash stock recovery first to flash stock firmware. It won't work as long as you have TWRP installed you can use SRK tools to flash stock recovery.
Click to expand...
Click to collapse
Ahhhh right right right. So I need to remove TWRP first, then use SRK tools to flash the stock recovery?
... so, how do I remove TWRP?
zandercook1 said:
Ahhhh right right right. So I need to remove TWRP first, then use SRK tools to flash the stock recovery?
... so, how do I remove TWRP?
Click to expand...
Click to collapse
Installing stock recovery will remove TWRP.
You're all heroes.
zandercook1 said:
You're all heroes.
Click to expand...
Click to collapse
You are a batman yourself.