Flashed Miui rom, now black screen - Xperia Z Q&A, Help & Troubleshooting

Hi guys! Followed the simple guide of flashing a miui rom>
Install:
-1. Put MI-ustone-UIVxx.zip on Internal or External Storage
-2. Goto Recovery and Install MI-ustone-UIxx.zip
-3. Reboot to Recovery
-4. Goto Wipe Menu->Advanced Wipe and Check everything except USB OTG and SD (or what you want;- )
-5. Install again MI-ustone-UIxx.zip
-6. Wipe Cache/Dalvik after successfully install
-7. Reboot & Enjoy!
(Give it time to boot !)
I have rooted phone, places zip on internal. Installed the bootmanager that you install with a .apk file...XZ recovery? In that app I chose boot into recovery and worked. I then Installed zip file. Wiped some stuff and then wiped cache&dalvik. I went back to menu and tried to install zip again but did nothing. I then pressed BOOT and BOOT TO RECOVERY. After this I am experiencing black screen and bootloop. I press volume- volume+ and power etc but just get vibration on phone and nothing else.
What to do now?
Update: Trying to flash recovery with fastboot but getting error:
FAILED remote: command not allowed
Update: Downloaded stock 244 rom and flashed it and now phone is back to normal but no root So what was wrong?

Related

[Q] Clean fresh Install OS - Required

Hi..
I was trying to upgrade my samsung galaxy s plus (GT-19001) device to Android 4.0.4.
i just installed CWM-based recovery v5.5.0.4 on my device by rebooting and selecting (install zip from sd card).
------using mentioned combination of keys -------
Then i placed the files in my phone's internal SD Card.
files are mentioned below:
1-> cm-9-20121011-ivendor-ariesve-rc5.zip
2-> gapps-ics-20120429-signed.zip
3-> recovery-clockwork-6.0.1.2-ariesve.zip
then install 1 by choosing from internal SD card and then 2nd file.
my device prompted completion success messages but it took very short time.
----------------------------------------------------------------------------------------------------------------------
now what happened after doing this. my device is displaying same booting screen of CWM-based recovery v5.5.0.4 on each re-boot.
i treid many times by unplug the battrey but unfortunately unsuccessfull.
After that i did Wipe data/factory reset and wipe cache partition.
----------------------------------------------------------------------------------------------------------------------
I tried it through window's based utility Odin v4.43 but it could detect my device usb driver even after success of USB driver installation.
it didn't display Added in message box.
now what should i do ?
i already installed samsung Kies but still undetected.
I tried some old version of Odin 3v1.8 , it detected the port and displayed Added but failed to write ROM on my device.
-----------------------------------------------------------------------------------------------------------------------
My desktop machine's OS : windows 8 64 bit enterprise edition.
----------------------------------------------------------------------------------------------------------------------------------------------------------
I am unable to install new ofor revert back my OS because when i Hold Vol Down + Home + Power, This is not putting me in Download Mode instead Ramdump Mode.
I need your guidence to resolve the issue. Thanks in advance.
Please ask for further details if required.
I'm not sure I got exactly what you did.
1) You installed CWM recovery.
2) You rebooted into recovery.
3) You installed the CM ROM zip.
4) You installed the GApps zip.
5) You rebooted.
Am I right ? And now you only get access to the recovery ?
If you're coming from a GingerBread ROM, this is normal. Simply, re-install the ROM again (and the GApps obviously). If it doesn't work, tell us.
support required
Einril said:
I'm not sure I got exactly what you did.
1) You installed CWM recovery.
2) You rebooted into recovery.
3) You installed the CM ROM zip.
4) You installed the GApps zip.
5) You rebooted.
Am I right ? And now you only get access to the recovery ?
If you're coming from a GingerBread ROM, this is normal. Simply, re-install the ROM again (and the GApps obviously). If it doesn't work, tell us.
Click to expand...
Click to collapse
Hi Einril.
I try to summarize in some chunks for better understanding.
=======================================================================================
Hi.
I just started with CWM-based recovery v5.5.0.4 and placed all above mentioned files/packages into the device internal SD card.
That's what i did :
1). Entered into the recovery mode menu by holding down Volume Up + Power and installed CWM-based recovery v5.5.0.4 zip from the selection of Internal SD Card .
2). After reboot, i came up again in Recovery mode using CWM-based recovery v5.5.0.4 application.
3). Now installed cm-9-20121011-ivendor-ariesve-rc5.zip by the navigation of "Install zip from SD".
It took hardly 4 to 5 seconds and displayed a message that it completes . no flash screen or anything came up and reboot.
4). After that installed gapps-ics-20120429-signed.zip by the navigation of "Install zip from SD".
It displayed same complete message but within 5 to 8 seconds i think.
5). I Wipe data/cache/Dalvik cache after above step and then again repeat the process.
After that i did Wipe data/factory reset and wipe cache partition.
Now when i try to start my device then each time it comes into the CWM-based recovery v5.5.0.4' s recovery mode.
Ask further please if anything is unclear, i have tried too many things with it but yet not soft bricked.
I am able to switch into Download mode.
Did you try to re-install the ROM from the recovery ? (flash cm-9-20121011-ivendor-ariesve-rc5.zip again)
new post
Einril said:
Did you try to re-install the ROM from the recovery ? (flash cm-9-20121011-ivendor-ariesve-rc5.zip again)
Click to expand...
Click to collapse
Hi Erinil,
I think i installed but not sure.
Could you elaborate the re-install ROM steps ?
I tried but same recovery display of CWM-based recovery v5.5.0.4, comes again and stay on recovery mode screen.
How my OS will be started?
It might be possible , i am doing something wrong.
Could you enlist the steps?
Ok.
1) Boot into recovery.
2) Wipe data/Factory reset.
3) Wipe cache.
4) Go to Advanced, then wipe Dalvik cache.
5) Go back, go to Mount & Storage, then Format System.
6) Go back, go to Install zip from SD Card => Choose zip from SD Card => cm-9-20121011-ivendor-ariesve-rc5.zip.
7) Do the same thing for the gapps zip.
8) Wipe data/Factory reset again (just to be sure).
9) Reboot.
This, I think, is the cleanest install you can do. Tell me the result.
Einril said:
Ok.
1) Boot into recovery.
2) Wipe data/Factory reset.
3) Wipe cache.
4) Go to Advanced, then wipe Dalvik cache.
5) Go back, go to Mount & Storage, then Format System.
6) Go back, go to Install zip from SD Card => Choose zip from SD Card => cm-9-20121011-ivendor-ariesve-rc5.zip.
7) Do the same thing for the gapps zip.
8) Wipe data/Factory reset again (just to be sure).
9) Reboot.
This, I think, is the cleanest install you can do. Tell me the result.
Click to expand...
Click to collapse
Einril I tried it same as you explained in steps.
It didn't worked nor display any error during this process.
I think my problem is that. when i start my device it automatically entered into the recovery mode of CWM-based recovery v5.5.0.4..
whether i hold Vol+ and Powerbutton or not, it entered into the recovery mode each reboot.
It might be possible that OS has been installed sucessfull but how the OS will be started now?
Hum, that's strange. You say you can access to Download Mode ? Are you able to flash back the Samsung stock ROM ?
Hi Einril,
What does that mean? Means that Reverting to Gingerbread through Desktop Window OS?
I am unable to revert from my One Laptop (i7 3610 & WIndow 8 - 64 bit) but i am able to revert from my OLD laptop (OS is : window 7 32 bit)
Ok, I heard that some people are having issues with USB drivers on Windows 8. But if you can restore Gingerbread with your old computer, this is great.
Can you try to re-install a stock gingerbread firmware, with re-partition enabled, and then to try again the procedure I gave you ? This way, we are sure that your previous attempts have no effects on the result.
Einril, I have installed stock gingerbread firmware on my device and it is working now.
now guide please how to re-partition? Do you mean using CWM recovery ?
Could you simply enlist the thing which i will have to do now on fresh gingerbread OS?
I 'll tell you today night because right now i am not at home.
Well, if your gingerbread frmware is working, you don't need to repartition.
Now, simply re-install ClockworkMod Recovery, and re-do the whole installation process I gave you. By the way, you said you installed ClockworkMod recovery by flashing a zip in recovery. Isn't it supposed to be a .tar.md5 to flash via Odin ?
Yes i installed ClockworkMode Recovery from recovery mode.
I haven't tried with .tar.md5 using Odin4.43.
I 'll try with both throught Clockworkmode and Odin.
In fact i have tried many time 2-3 months ago too through TeamWin Recovery . problem was same.
It didn't start my OS instead displaying its recovery screen and operations.
i tried but all in vain.
Couldn;t be successful.
it just start from CWM recovery mode and so. not switching into the other mode.

[Q] Clear Install Android 4.0.4

Hi..
I want to clean install Android 4.0.4 OS on my Samsung galaxy s plus (GT-19001) device.
Clean install means that i 'll have to install OS from scratch. Does i need Micro USb Jig for this purpose?
I have below files.
1-> cm-9-20121011-ivendor-ariesve-rc5.zip
2-> gapps-ics-20120429-signed.zip
3-> recovery-clockwork-6.0.1.2-ariesve.zip
4> CWM-based recovery v5.5.0.4
Guide me in simple steps , i tried many times to install ICS (Android 4.0.4) but unfortunately unsuccessfull each time.
Why it didn't work for me?
I have tried in many ways. Thanks in advancee
Hey,
Could you tell me what was unsuccessful about the install? Did it stop installing, did it bootloop, so on so forth?
But this is how I flashed CM9 onto my I9000, and I know that the I9001 is very similar so...
1.) You've got CWM, sweet. Boot into recovery. Make a bckup of your data through the option provided.
2.) Wipe data/cache/Dalvik cache. The first two are pretty simple to do, the last one is under "Advanced" settings.
3.) Now that you've got that, select "Install zip from SD". Navigate to where your CM9 file is. Select and confirm. Wait for it to flash in...
4.) At this point you might get a recovery bootloop. Don't panic here- just take out the battery, reinsert. Reboot into recovery. You should see that your recovery has been updated.
5.) Reselect the rom from the "Install zip from SD" option. This time it should start flashing in. Wait for it to finish, then it should reboot normally. Be patient as it boots up for the first time.
6.) Once you've done so, reboot into recovery again but this time select the gapps zip.
Unless the I9001 is different in a major way in terms of installing, that should work. I'm not quite sure...
Hope I helped
Sent from my GT-I9000
support required
Soryuu said:
Hey,
Could you tell me what was unsuccessful about the install? Did it stop installing, did it bootloop, so on so forth?
But this is how I flashed CM9 onto my I9000, and I know that the I9001 is very similar so...
1.) You've got CWM, sweet. Boot into recovery. Make a bckup of your data through the option provided.
2.) Wipe data/cache/Dalvik cache. The first two are pretty simple to do, the last one is under "Advanced" settings.
3.) Now that you've got that, select "Install zip from SD". Navigate to where your CM9 file is. Select and confirm. Wait for it to flash in...
4.) At this point you might get a recovery bootloop. Don't panic here- just take out the battery, reinsert. Reboot into recovery. You should see that your recovery has been updated.
5.) Reselect the rom from the "Install zip from SD" option. This time it should start flashing in. Wait for it to finish, then it should reboot normally. Be patient as it boots up for the first time.
6.) Once you've done so, reboot into recovery again but this time select the gapps zip.
Unless the I9001 is different in a major way in terms of installing, that should work. I'm not quite sure...
Hope I helped
Sent from my GT-I9000
Click to expand...
Click to collapse
Hi.
I just started with CWM-based recovery v5.5.0.4 and placed all above mentioned files/packages into the device internal SD card.
That's what i did :
1). Entered into the recovery mode menu by holding down Volume Up + Power and installed CWM-based recovery v5.5.0.4 zip from the selection of Internal SD Card .
2). After reboot, i came up again in Recovery mode using CWM-based recovery v5.5.0.4 application.
3). Now installed cm-9-20121011-ivendor-ariesve-rc5.zip by the navigation of "Install zip from SD".
It took hardly 4 to 5 seconds and displayed a message that it completes . no flash screen or anything came up and reboot.
4). After that installed gapps-ics-20120429-signed.zip by the navigation of "Install zip from SD".
It displayed same complete message but within 5 to 8 seconds i think.
5). I Wipe data/cache/Dalvik cache after above step and then again repeat the process.
After that i did Wipe data/factory reset and wipe cache partition.
Now when i try to start my device then each time it comes into the CWM-based recovery v5.5.0.4' s recovery mode.
Ask please i have tried too many things with it but yet not soft bricked.
I am able to switch into Download mode.
Soryuu said:
Hey,
Could you tell me what was unsuccessful about the install? Did it stop installing, did it bootloop, so on so forth?
But this is how I flashed CM9 onto my I9000, and I know that the I9001 is very similar so...
1.) You've got CWM, sweet. Boot into recovery. Make a bckup of your data through the option provided.
2.) Wipe data/cache/Dalvik cache. The first two are pretty simple to do, the last one is under "Advanced" settings.
3.) Now that you've got that, select "Install zip from SD". Navigate to where your CM9 file is. Select and confirm. Wait for it to flash in...
4.) At this point you might get a recovery bootloop. Don't panic here- just take out the battery, reinsert. Reboot into recovery. You should see that your recovery has been updated.
5.) Reselect the rom from the "Install zip from SD" option. This time it should start flashing in. Wait for it to finish, then it should reboot normally. Be patient as it boots up for the first time.
6.) Once you've done so, reboot into recovery again but this time select the gapps zip.
Unless the I9001 is different in a major way in terms of installing, that should work. I'm not quite sure...
Hope I helped
Sent from my GT-I9000
Click to expand...
Click to collapse
Perfectly simple guide! Thanks.:good:
The only thing I want to ask - what is the backup you have mentioned in point 1)? Is it back up of your personal data, or is it back up of your current ROM?
Hey man, glad I made it simple
Yeah, its a backup of your whole rom I believe- system apps, system files, all your downloaded apps all your data, so on so forth.
Helps you get back to what you were running before in case something goes wrong during installation.
Sent from my GT-I9000
---------- Post added at 02:29 PM ---------- Previous post was at 02:15 PM ----------
empnetsol said:
Hi.
I just started with CWM-based recovery v5.5.0.4 and placed all above mentioned files/packages into the device internal SD card.
That's what i did :
1). Entered into the recovery mode menu by holding down Volume Up + Power and installed CWM-based recovery v5.5.0.4 zip from the selection of Internal SD Card .
2). After reboot, i came up again in Recovery mode using CWM-based recovery v5.5.0.4 application.
3). Now installed cm-9-20121011-ivendor-ariesve-rc5.zip by the navigation of "Install zip from SD".
It took hardly 4 to 5 seconds and displayed a message that it completes . no flash screen or anything came up and reboot.
4). After that installed gapps-ics-20120429-signed.zip by the navigation of "Install zip from SD".
It displayed same complete message but within 5 to 8 seconds i think.
5). I Wipe data/cache/Dalvik cache after above step and then again repeat the process.
After that i did Wipe data/factory reset and wipe cache partition.
Now when i try to start my device then each time it comes into the CWM-based recovery v5.5.0.4' s recovery mode.
Ask please i have tried too many things with it but yet not soft bricked.
I am able to switch into Download mode.
Click to expand...
Click to collapse
Hmmm... Okay, I see...
What recovery did you start with before flashing CWM 5.5.0.4? Because I think what happens is that in whatever recovery you start with, you start by flashing in the CM9 file directly, instead of flashing a different CWM version in first.
So a good place to start would be back at 2.3.6 (don't know the firmware for the I9001). That can be done through download mode and Odin (If you need help with that feel free to ask). Then root again, get recovery back.
Flashing in the CM9 file the first time actually doesn't take long- maybe 5-10 seconds as you said, before bootlooping. What that bootloop does is it actually sets up a newer recovery, so that you can properly flash CM9 in.
Once you flash in the CM9 file the first time, try flash it in a second time. If it takes 4-5 seconds again then you have a problem, otherwise it should take a little bit for the file to install.
It will reboot; like I said in my little guide, just turn off, reboot into recovery and flash in Gapps, then let it boot.
Also, I don't think you need to wipe everything after the CM9 zip finishes. I didn't need to, and it worked fine...
Again, hope I helped
Sent from my GT-I9000
hi .
i am trying to give answer in point:
What recovery did you start with before flashing CWM 5.5.0.4?
-> yes i t was exactly CWM 5.5.0.4.
Because I think what happens is that in whatever recovery you start with, you start by flashing in the CM9 file directly, instead of flashing a different CWM version in first.
-> Could you elaborate the above sentence please? As long as i understood I initially installed CWM recovery through recovery mode by holding +Vol + Power+ Home.
So a good place to start would be back at 2.3.6 (don't know the firmware for the I9001). That can be done through download mode and Odin (If you need help with that feel free to ask). Then root again, get recovery back.
-> Yes i have been reverted through Odin Stock Gingerbread. How to root again? Could you please enlist in points?
Flashing in the CM9 file the first time actually doesn't take long- maybe 5-10 seconds as you said, before bootlooping. What that bootloop does is it actually sets up a newer recovery, so that you can properly flash CM9 in.
-> I don't think it's a bootlooping situation. When i start my device , It dispays CWM recovery screen each time even after the sucessull completion of CM9 and gapps,
Once you flash in the CM9 file the first time, try flash it in a second time. If it takes 4-5 seconds again then you have a problem, otherwise it should take a little bit for the file to install.
It will reboot; like I said in my little guide, just turn off, reboot into recovery and flash in Gapps, then let it boot.
-> I tried it many time right now and 2-3 months ago too but it took almost 20 - 30 seconds in first attempt.
Also, I don't think you need to wipe everything after the CM9 zip finishes. I didn't need to, and it worked fine...
-> I tried through Wipe and with it but could start my OS. Instead it display everytime a CWM screen.
=================================================================================================
In last , i did below steps :
1) Boot into recovery.
2) Wipe data/Factory reset.
3) Wipe cache.
4) Go to Advanced, then wipe Dalvik cache.
5) Go back, go to Mount & Storage, then Format System.
6) Go back, go to Install zip from SD Card => Choose zip from SD Card => cm-9-20121011-ivendor-ariesve-rc5.zip.
7) Do the same thing for the gapps zip.
8) Wipe data/Factory reset again (just to be sure).
9) Reboot.
Go into the cm10 thread by ivendor in developement section and in the middle of the 1st post is a download link for cwm 6.0.1.9. Flash it in recovery and reboot. The Problem should be gone.
Had the same issue.
Hope i helped
Hi Markey.
Do you mean that I 'll have to get CM10 and CWM 6.0.1.9 and then installed with same approach as i aforesaid?
Elaborate please if i misunderstood. Thanks
empnetsol said:
Hi Markey.
Do you mean that I 'll have to get CM10 and CWM 6.0.1.9 and then installed with same approach as i aforesaid?
Elaborate please if i misunderstood. Thanks
Click to expand...
Click to collapse
No i meant that you can install everything like in your guide and after that you install the cwm 6.0.1.9 and reboot, then you should be in recovery and then you have to reboot your phone and it should start normally
This solved it for me
Hope i helped
That's what I understood now:
0.5) Entered into the recovery mode menu by holding down Volume Up + Power and installed CWM-based recovery v5.5.0.4 zip from the selection of Internal SD Card .
1) Boot into CWM-based recovery v5.5.0.4 Recovery mode.
2) Wipe data/Factory reset.
3) Wipe cache.
4) Go to Advanced, then wipe Dalvik cache.
5) Go back, go to Mount & Storage, then Format System.
6) Go back, go to Install zip from SD Card => Choose zip from SD Card => cm-9-20121011-ivendor-ariesve-rc5.zip.
7) Do the same thing for the gapps zip.
8) Wipe data/Factory reset again (just to be sure).
9) Reboot
10) Then install the cwm 6.0.1.9 and reboot.
It could be solution, i will try and 'll tell at today night (after 6 hours).
It should be the right way but you can skip step 5 and 9
Hope i helped
empnetsol said:
That's what I understood now:
0.5) Entered into the recovery mode menu by holding down Volume Up + Power and installed CWM-based recovery v5.5.0.4 zip from the selection of Internal SD Card .
1) Boot into CWM-based recovery v5.5.0.4 Recovery mode.
2) Wipe data/Factory reset.
3) Wipe cache.
4) Go to Advanced, then wipe Dalvik cache.
5) Go back, go to Mount & Storage, then Format System.
6) Go back, go to Install zip from SD Card => Choose zip from SD Card => cm-9-20121011-ivendor-ariesve-rc5.zip.
7) Do the same thing for the gapps zip.
8) Wipe data/Factory reset again (just to be sure).
9) Reboot
10) Then install the cwm 6.0.1.9 and reboot.
It could be solution, i will try and 'll tell at today night (after 6 hours).
Click to expand...
Click to collapse
It should be the right way but you can skip step 5 and 9
Hope i helped
Dear Markey,
Whyn't should i start from cwm 6.0.1.9 rather than CWM-based recovery v5.5.0.4 .
Should i require to check from it or not? cwm 6.0.1.9 support cm-9-20121011-ivendor-ariesve-rc5.zip ?
empnetsol said:
Dear Markey,
Whyn't should i start from cwm 6.0.1.9 rather than CWM-based recovery v5.5.0.4 .
Should i require to check from it or not? cwm 6.0.1.9 support cm-9-20121011-ivendor-ariesve-rc5.zip ?
Click to expand...
Click to collapse
I don't know if cwm 6.0.1.9 supports cm9 but it should.
You could try it out and tell me back
when i go in advance and select wipe dalvik cache option.
it display an error:
E:unknown volume for path [/sd-ext]
Dalvik Cache wiped.
After completion of each step, i tried again but still not start OS.
empnetsol said:
when i go in advance and select wipe dalvik cache option.
it display an error:
E:unknown volume for path [/sd-ext]
Dalvik Cache wiped.
After completion of each step, i tried again but still not start OS.
Click to expand...
Click to collapse
Got the same error, i think its normal
Ok, then flash this file: http://forum.xda-developers.com/attachment.php?attachmentid=861538&d=1326841043 in recovery, reboot and tell me back if it works
Or you could try this way if the other isn't working: http://forum.xda-developers.com/attachment.php?attachmentid=928219&d=1330695090 its the stock recovery, flash it in recovery and reboot and tell me back. I think you should first try stock recovery and then the other file. Sry for the wrong order
Hope it will work again
hi markey.
how to flash these files? i didn't understand the flashing word.
Got an error from mentioned recoveries.
Installing update...
E:Error in /tmp/sideload/package.zip
(Status 2)
Installation aborted.
empnetsol said:
hi markey.
how to flash these files? i didn't understand the flashing word.
Click to expand...
Click to collapse
empnetsol said:
Got an error from mentioned recoveries.
Installing update...
E:Error in /tmp/sideload/package.zip
(Status 2)
Installation aborted.
Click to expand...
Click to collapse
I mean that you have to install them via recovery with install update from sd card or with install zip from sd card -> its called flashing
And i meant that you have to install the first file first and reboot and if its not working when you reboot then install the stock recovery and then the problem should be solved. But then you have to flash the cwm recovery everytime you want to flash something like a new kernel or a custom rom
Hope i could help
Markey,
I did the same as you are saying and got the above error on each file.
Could you explain the below linw please ?
But then you have to flash the cwm recovery everytime you want to flash something like a new kernel or a custom rom
What i 'll have to do now?
empnetsol said:
Markey,
I did the same as you are saying and got the above error on each file.
Could you explain the below linw please ?
But then you have to flash the cwm recovery everytime you want to flash something like a new kernel or a custom rom
What i 'll have to do now?
Click to expand...
Click to collapse
Which recovery do you use?
Cwm or stock recovery?
If you use stock then you have to reboot without installing one of the files and the problem should be solved
I meant that if you want to install another kernel or custom Rom you have to install the cwm recovery because its better then stock and after installation of the Rom or kernel you have to reinstall the stock recovery
If you don't understand i'll write you a guide for what you have to do

Unable to select cm zip file in recovery menu

Hi
I followed this link wiki.cyanogenmod.org/w/Install_CM_for_huashan and I wanted to install CM 13 to my C5303.
I downloaded cm-13.0-20160814-NIGHTLY-huashan.zip unpacked boot.img and flashed.
Then I made factory reset and tries to select zip file from sd card but when I select Apply update>choose from sdcard1 then it brings me back to main menu.
Adb sideload returns "no devices error".
What I can do?
I made full factory reset and wipe cache partition so now I cannot start my phone.
Ok. I successfully installed 12.1, but what with this 13.0?
I resolved issue using twrp, but... cwm recovery 13.0 still not working.

Can't get out of Fastboot.

"Cyanogendmod.Org / Install CM for z3c / Unlock Your Xperia Z3 Compact" <--- That's the URL somehow.
Followed this instruction. Got myself the 12.1 .zip and .img.
I get error installaing the .zip and the .img isn't even an option:
The old rom is infinitly loading in that blue/purple wave line.
I then turn the phone off by holding down the power button until the phone restarts.
My history:
>Pressing up and down on the button rockers.
>Cyanogen Recovery starts.
>I choose "Wipe data/factory reset".
>I choose "Apply update".
(Apply from ADB doesn't work as it seems as ADB has no access for USB debugging. That's why install it from an external SD)
>Install "cm-12.1-20160918-NIGHTLY-z3c.zip" or its copy that I named "update.zip".
Error message:
[CAN'T POST PICTURE BECAUSE XDA HAS VERY FUNNY MEME RULES XDDD]
Private message maybe...? Can I send you guys URL pics via PM?
How can I get out of this loop?
If you want to go back to stock, use flashtool and flash whatever version you want (FTF method), I had an issue with flashing CM too, it said this is for aries but this device is z3c etc. Is this your problem?
marshalpear said:
If you want to go back to stock, use flashtool and flash whatever version you want (FTF method), I had an issue with flashing CM too, it said this is for aries but this device is z3c etc. Is this your problem?
Click to expand...
Click to collapse
I definitly want CyanogenMod 12.1 on my Z3C. Is it still possible?
I hope you can decypher the URL h t t p : / / t i n y u r l . c o m / j 6 4 u 8 u a
Few things you can do:
1- Download the ROM again, might be corrupted download.
2- Flash Lollipop FTF(not necessary), Flash TWRP recovery, boot into recovery, (If it asks, swipe to allow modifications to system), wipe everything (system,cache,dalvik,data), flash the ROM through TWRP recovery.
3- If it gives the error that I talked about in my first message, let me know.
marshalpear said:
Few things you can do:
1- Download the ROM again, might be corrupted download.
2- Flash Lollipop FTF(not necessary), Flash TWRP recovery, boot into recovery, (If it asks, swipe to allow modifications to system), wipe everything (system,cache,dalvik,data), flash the ROM through TWRP recovery.
3- If it gives the error that I talked about in my first message, let me know.
Click to expand...
Click to collapse
I tried #1 but I'm already stuck with the "SONY XPERIA" blackscreen at the very beginning when booting the smartphone. I suppose it's because of the failed installation and the not choosing of "Wipe clean/factory reset".
I hope that still doesn't count as bricking. I let the accumulator run dry and reload the battery and try to get into the Cyanogenmod Recovery again. Right now nothing is possible. =/
I hope that doesn't count as bricking. If so: These special OTG USB thingies fix a lot I heard, should I get myself one?
SYLVER SECOND said:
I tried #1 but I'm already stuck with the "SONY XPERIA" blackscreen at the very beginning when booting the smartphone. I suppose it's because of the failed installation and the not choosing of "Wipe clean/factory reset".
I hope that still doesn't count as bricking. I let the accumulator run dry and reload the battery and try to get into the Cyanogenmod Recovery again. Right now nothing is possible. =/
I hope that doesn't count as bricking. If so: These special OTG USB thingies fix a lot I heard, should I get myself one?
Click to expand...
Click to collapse
If you are on CM recovery, then there is the problem. AFAIK you can't flash anything through that, so you have to push TWRP on your device using fastboot and then flash AOSP/CM rom you want.
SYLVER SECOND said:
I tried #1 but I'm already stuck with the "SONY XPERIA" blackscreen at the very beginning when booting the smartphone. I suppose it's because of the failed installation and the not choosing of "Wipe clean/factory reset".
I hope that still doesn't count as bricking. I let the accumulator run dry and reload the battery and try to get into the Cyanogenmod Recovery again. Right now nothing is possible. =/
I hope that doesn't count as bricking. If so: These special OTG USB thingies fix a lot I heard, should I get myself one?
Click to expand...
Click to collapse
That's called a soft-brick. You should install the ADB drivers for your phone on your PC and then download TWRP for your phone (.img file) and rename the TWRP you downloaded to recovery.img .
You should put the recovery.img into the folder where your ADB drivers are installed, then Shift + RClick on that folder then select Open Command Window Here. Connect your phone in fastboot mode to your PC (Keep Vol. Up button then plug in your device). Type the following commands:
fastboot flash boot recovery.img
fastboot reboot
If you've done it all correctly, your phone should boot into TWRP recovery. From there you should go to wipe-advanced wipe and wipe your Cache,Dalvik Cache, System, Boot. DO NOT REBOOT NOW. You should go back to main menu and choose install, then choose the ROM you want to install. It should flash it if you don't have a corrupted file. After flashing, you can safely reboot your phone, don't forget to flash GApps if you want Google features on your Cyanogen, hope I helped!
More info about my error:
h t t p : / / t i n y u r l . c o m / z b e v y u 2
Each version of step #3 doesn't work. Still trying to figure out how to get TWRP...
marshalpear said:
That's called a soft-brick. You should install the ADB drivers for your phone on your PC and then download TWRP for your phone (.img file) and rename the TWRP you downloaded to recovery.img .
You should put the recovery.img into the folder where your ADB drivers are installed, then Shift + RClick on that folder then select Open Command Window Here. Connect your phone in fastboot mode to your PC (Keep Vol. Up button then plug in your device). Type the following commands:
fastboot flash boot recovery.img
fastboot reboot
If you've done it all correctly, your phone should boot into TWRP recovery. From there you should go to wipe-advanced wipe and wipe your Cache,Dalvik Cache, System, Boot. DO NOT REBOOT NOW. You should go back to main menu and choose install, then choose the ROM you want to install. It should flash it if you don't have a corrupted file. After flashing, you can safely reboot your phone, don't forget to flash GApps if you want Google features on your Cyanogen, hope I helped!
Click to expand...
Click to collapse
K, 90% of this works. I got the TWRP "app" and I cleaned the cache and all that, but I had to reboot. You see:
To transfer new media I need to remove my external SD from the z3c to my old LG. The LG is connected with my PC and is therefore a kind of card-reader. I tried 2 different nightly thingies.
I still get extraction errors, see:
h t t p : / / t i n y u r l . c o m / h j j d 4 o b
I downloaded 2 different nightlies 6 times already. I dunno. Somethings off here.
Also: For what is the recovery.img? Should I install it afterwards?
I have to restart the phone in order to replug the SD card and get recognigzed by the TWRP.
I did everything from this:
http://forum.xda-developers.com/showthread.php?t=2522762
Because of Error 7.
Now I get Error 6.....
SYLVER SECOND said:
K, 90% of this works. I got the TWRP "app" and I cleaned the cache and all that, but I had to reboot. You see:
To transfer new media I need to remove my external SD from the z3c to my old LG. The LG is connected with my PC and is therefore a kind of card-reader. I tried 2 different nightly thingies.
I still get extraction errors, see:
h t t p : / / t i n y u r l . c o m / h j j d 4 o b
I downloaded 2 different nightlies 6 times already. I dunno. Somethings off here.
Also: For what is the recovery.img? Should I install it afterwards?
I have to restart the phone in order to replug the SD card and get recognigzed by the TWRP.
I did everything from this:
http://forum.xda-developers.com/showthread.php?t=2522762
Because of Error 7.
Now I get Error 6.....
Click to expand...
Click to collapse
OK, your problem is that you messed up your system, so wiping it is not gonna solve this issue. You need to download a stock firmware file (an FTF file) and flash it through Flashtool, because your device name seems to be "." which is why you were getting "error 7". As for the recovery.img, you will use it to flash TWRP recovery on your phone. TWRP app doesn't work correctly if you don't flash it to your recovery partition so do as follows:
1- Download Flashtool, install the drivers of your device for Flashtool (you can search it on xda forums), download an FTF file, any of them should do, but as you will install CM 12.1, I recommend a Lollipop FTF.
2- Flash the firmware through Flashtool. This will turn your phone into a stock one. Unlock your bootloader if you haven't already, which I believe you have.
3- Flash the TWRP recovery through fastboot (follow my earlier instructions)
4- After you open TWRP recovery do the wipes, note that you can still connect your phone to your computer for file transfers in TWRP Recovery.
5- Install the CM zip file through recovery
IF YOU GET ERROR 7 SAYING :this package is for device: D5803, D5833, z3c; this device is aries.
7- Open the CM 12.1 zip file on your computer and proceed to META-INF/com/google/android directory.
8- In that folder you should see "updater-script", extract it to somewhere and open it with Notepad.
9- Once you open it press Ctrl + H to change some of the lines.
10- Write "D5833" without the quotation marks in the first space and write "aries" without the quotation marks into the second space and click replace all.
(This will change all "D5833" to "aries" in the file therefore making it usable for your device) Save the file and put it into the directory of where you found it, replace it with the original.
11- Now put the edited .zip file into your phone storage, and flash it through recovery. It should work. :good:
marshalpear said:
3- Flash the TWRP recovery through fastboot (follow my earlier instructions)
Click to expand...
Click to collapse
I think he shouldn't flash TWRP on boot partition, as you wrote. That might cause further issues. I am flashing my recovery through fastboot without problems using next command:
fastboot flash recovery recovery.img
Cirra92 said:
I think he shouldn't flash TWRP on boot partition, as you wrote. That might cause further issues. I am flashing my recovery through fastboot without problems using next command:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
It won't matter. Because when he flashes the CM, it'll flash the CM Recovery along with it.
marshalpear said:
It won't matter. Because when he flashes the CM, it'll flash the CM Recovery along with it.
Click to expand...
Click to collapse
Yea I know, but before that, he needs to have a working TWRP on right partition to be able to even flash any rom.
Cirra92 said:
Yea I know, but before that, he needs to have a working TWRP on right partition to be able to even flash any rom.
Click to expand...
Click to collapse
That's why I wrote those steps for him/her to follow. If you flash TWRP to boot partition, when you boot the phone, it will go straight into TWRP. If you flash it to recovery partition, you'll have to boot it manually.
marshalpear said:
That's why I wrote those steps for him/her to follow. If you flash TWRP to boot partition, when you boot the phone, it will go straight into TWRP. If you flash it to recovery partition, you'll have to boot it manually.
Click to expand...
Click to collapse
Logical step, didn't think about it that way, I assumed OP knew how to enter recovery
"1- Download Flashtool, install the drivers of your device for Flashtool (you can search it on xda forums), download an FTF file, any of them should do, but as you will install CM 12.1, I recommend a Lollipop FTF.
2- Flash the firmware through Flashtool. This will turn your phone into a stock one. Unlock your bootloader if you haven't already, which I believe you have.
3- Flash the TWRP recovery through fastboot (follow my earlier instructions)
4- After you open TWRP recovery do the wipes, note that you can still connect your phone to your computer for file transfers in TWRP Recovery.
5- Install the CM zip file through recovery
IF YOU GET ERROR 7 SAYING :this package is for device: D5803, D5833, z3c; this device is aries.
7- Open the CM 12.1 zip file on your computer and proceed to META-INF/com/google/android directory.
8- In that folder you should see "updater-script", extract it to somewhere and open it with Notepad.
9- Once you open it press Ctrl + H to change some of the lines.
10- Write "D5833" without the quotation marks in the first space and write "aries" without the quotation marks into the second space and click replace all.
(This will change all "D5833" to "aries" in the file therefore making it usable for your device) Save the file and put it into the directory of where you found it, replace it with the original.
11- Now put the edited .zip file into your phone storage, and flash it through recovery. It should work."
K, so I guess I'm finished with #1 and #2. Sorry, had a ****-ton of chores to do. Before I progress, I wanted to send you guys
this pic:
https://img3.picload.org/image/rdricord/unbenannt.png
Is the root access necessary, or can I progress?
That's the sites I've used, if anybody wonders why something is the way it is right now:
http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
http://forum.xda-developers.com/showpost.php?p=66275965&postcount=2029
http://forum.xda-developers.com/showpost.php?p=60001557&postcount=829
Von "Sony Mobile Flasher by Androxyde":
"23/023/2016 22:23:52 - INFO - Root access denied
23/024/2016 22:24:07 - ERROR - Illegal key size or default parameters
23/024/2016 22:24:12 - ERROR - Illegal key size or default parameters
23/024/2016 22:24:13 - WARN - Please check your Phone and 'ALLOW' Superuseraccess!
23/024/2016 22:24:14 - INFO - Root access denied"
FlashTool says the firmware has been flashed so I don't understand what are you trying to do after that? After flashing the FTF file you should flash TWRP through "FASTBOOT". Then follow the instructions.
K, did everything you said. Read everything five-times. Replaced "D5833" to "aries" and all that stuff. Still getting ERROR 7.
The phone is still in TWRP Recovery from FASTBOOT / BOOTLOAD because I "constantly" charge it to stay in recovery. If I had found this Mount option earlier... kinda feel stupid for that. So I still get ERROR 7. I copied the modified .zip to internal storage and SD card to see if I get the same error twice. And yeah.
Exact error message in red letters:
"Updater process ended with ERROR: 7
Error installing zip file ' /external-sd/cm-12.1-20160918-NIGHTLY-z3c.zip'
Updating partition details...
... done"
So I forethought and cleaned the cache and need somewhat new instructions.
Also:
I suppose with "Advanced Wipe" and your instructions you meant this points, right?:
http://tinyurl.com/jc5rv3a
SYLVER SECOND said:
K, did everything you said. Read everything five-times. Replaced "D5833" to "aries" and all that stuff. Still getting ERROR 7.
The phone is still in TWRP Recovery from FASTBOOT / BOOTLOAD because I "constantly" charge it to stay in recovery. If I had found this Mount option earlier... kinda feel stupid for that. So I still get ERROR 7. I copied the modified .zip to internal storage and SD card to see if I get the same error twice. And yeah.
Exact error message in red letters:
"Updater process ended with ERROR: 7
Error installing zip file ' /external-sd/cm-12.1-20160918-NIGHTLY-z3c.zip'
Updating partition details...
... done"
So I forethought and cleaned the cache and need somewhat new instructions.
Also:
I suppose with "Advanced Wipe" and your instructions you meant this points, right?:
http://tinyurl.com/jc5rv3a
Click to expand...
Click to collapse
OK, so try flashing TWRP to recovery partition to get you out of TWRP after you boot by writing these commands in the ADB:,
fastboot flash recovery recovery.img
fastboot reboot recovery
This will flash the TWRP to recovery partition and will boot you into TWRP. As you do this you won't have a go at the recovery again but for this time. You can reach the TWRP by pressing the Vol. Down button when the phone vibrates at the boot. Also if you want to force shutdown your phone you can use Vol. Up + Power Button combination for a few secs.
marshalpear said:
OK, so try flashing TWRP to recovery partition to get you out of TWRP after you boot by writing these commands in the ADB:,
fastboot flash recovery recovery.img
fastboot reboot recovery
This will flash the TWRP to recovery partition and will boot you into TWRP. As you do this you won't have a go at the recovery again but for this time. You can reach the TWRP by pressing the Vol. Down button when the phone vibrates at the boot. Also if you want to force shutdown your phone you can use Vol. Up + Power Button combination for a few secs.
Click to expand...
Click to collapse
K, cool feature. Got it all set up now, but back to the main subject:
Is it even possible to install CyanogenMod 12.1 on Sony Z3C?

[Solved] Error while flashing Katkiss from CWM v6.0.5.0

Dear friends I need help!
I've tried to flash my tablet but I've got an error message while flashing Katkiss 6.0
What I did:
downloaded Rom.(md5sum is OK)
my bootloader is ww_epad-11.4.1.17-20140711
recovery CWM v6.0.5.0
previous rom zoombi pop
/format data
wipe data factory reset
install zip from sd card. (from internal storage or micro sd card)
And I have got the following error (in attachement)
Please help, my tablet boot only recovery now.
Thanks in advance for the help
trying to boot in fastboot mode when children let me try that...
Edit: fastboot ok.
I placed the the files
KatKiss-6.0_TF701T_033.zip
open_gapps-arm-6.0-pico-20170120.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
In
C:\Program Files (x86)\Minimal ADB and Fastboot
ok I don't know how to proceed now.
Seems I cannot change the recovery from CMW to TWRP,
My bootloader is 11.4.1.17 and the tutorial to install TWRP says in capital red:
MUST BE ON A BOOTLOADER 11.4.1.27, 11.4.1.29 or 11.4.1.30
So how can I do?
I there a way to upgrade the bootloader to be able to install TWRP?
Or should I Flash the custom rom from fastboot?
My TF701 in not booting anymore.... only bootloader and recovery CMW
the positive thing is :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
15C3E10090400000011FA8580 fastboot
Please help
I have been able to flash CROMI X (unfortunately with strong battery drain) so CMW is able to flash but for some reasons not Katkiss 6.0.
I have been told that my problem is not ROM related... So it is recovery related?
What is the better option to get katkiss on my tablet? Flash the recovery to get TWRP even if my bootloader is 11.4.1.17 and the tutorial to install TWRP says in capital red:
MUST BE ON A BOOTLOADER 11.4.1.27, 11.4.1.29 or 11.4.1.30????
There is a technical reason about this warning?
Edit: I found this on an old post:
You can try this:
Download the stock recovery from here: http://droidbasement.com/db-blog/?p=3210
Copy the image to your fastboot folder.
Download the Asus firmware, unzip the file once and copy it to your internal SD.
Boot tablet into fastboot
Issue this command
Code:
fastboot boot recovery.img
Note: Do not flash the recovery, just boot it.
It should recognize the firmware file on your tablet and flash it.
Click to expand...
Click to collapse
Would this method work to get the latest stock rom from Asus?
Got your PM and will try to find some time at work today. Hang in there and don't do anything to make it worse
Ok, work was crazy busy so it took a bit longer.
If you flash a recovery that is incompatible with the bootloader nothing happens. Until you use the recovery... That could permanently brick the tablet. So heed the warnings, they are there for a reason.
Ok, let's try to get you on the latest bootloader. It's no suprise at all that nothing boots if you try to flash a Android 6 rom on an Android 4 bootloader....
Download either WW or US package from here: https://forum.xda-developers.com/showpost.php?p=61045480&postcount=2
That zip contains the latest bootloader and a compatible TWRP recovery. Flash the zip in your current recovery just like any rom, then reboot.
When you flash a bootloader or recovery you actually write those files to the staging partition. On the next boot the bootloader will unpack it and write everything to it's proper place.
So it's essential that you flash, then reboot. Does not matter that the boot does not go anywhere. The first part, flashing the contents of /staging to it's partition(s), will happen anyway.
You should see a brief blue bar filling up when that happens. It does not take long.
Boot back into fastboot and check your bootloader version.
Enter recovery through RCK and that should be TWRP now.
Then format /data. Do not wipe it, format it. Do not interrupt it. Wait for it to finish even if it takes an hour (a full battery is a must before you start this). The format command is under the Wipe menu.
Unfortunately the formatting in this kanged TWRP is pretty buggy, but I still like it better than CWM.... If you get lots of error messages after the format (cannot mount this, cannot mount that) go into Wipe > Advanced > select Data > Change or repair file system > Change file system > choose ext3 and execute
Note: The button you have to swipe is pretty "sticky". Swipe it slowly and fully
Reboot to recovery
Go back into Wipe > Advanced etc and change the file system back to ext4
Reboot to recovery
Now everything should be ok, try to mount/unmount data.
Finally you are ready to flash Katkiss
If the bootloader flash does not work, we can try to flash Asus firmware in fastboot, but try the above first.
berndblb said:
Ok, work was crazy busy so it took a bit longer.
If you flash a recovery that is incompatible with the bootloader nothing happens. Until you use the recovery... That could permanently brick the tablet. So heed the warnings, they are there for a reason.
Ok, let's try to get you on the latest bootloader. It's no suprise at all that nothing boots if you try to flash a Android 6 rom on an Android 4 bootloader....
Download either WW or US package from here: https://forum.xda-developers.com/showpost.php?p=61045480&postcount=2
That zip contains the latest bootloader and a compatible TWRP recovery. Flash the zip in your current recovery just like any rom, then reboot.
When you flash a bootloader or recovery you actually write those files to the staging partition. On the next boot the bootloader will unpack it and write everything to it's proper place.
So it's essential that you flash, then reboot. Does not matter that the boot does not go anywhere. The first part, flashing the contents of /staging to it's partition(s), will happen anyway.
You should see a brief blue bar filling up when that happens. It does not take long.
Boot back into fastboot and check your bootloader version.
Enter recovery through RCK and that should be TWRP now.
Then format /data. Do not wipe it, format it. Do not interrupt it. Wait for it to finish even if it takes an hour (a full battery is a must before you start this). The format command is under the Wipe menu.
Unfortunately the formatting in this kanged TWRP is pretty buggy, but I still like it better than CWM.... If you get lots of error messages after the format (cannot mount this, cannot mount that) go into Wipe > Advanced > select Data > Change or repair file system > Change file system > choose ext3 and execute
Note: The button you have to swipe is pretty "sticky". Swipe it slowly and fully
Reboot to recovery
Go back into Wipe > Advanced etc and change the file system back to ext4
Reboot to recovery
Now everything should be ok, try to mount/unmount data.
Finally you are ready to flash Katkiss
If the bootloader flash does not work, we can try to flash Asus firmware in fastboot, but try the above first.
Click to expand...
Click to collapse
Thanks a lot to take time to help me.
Will try that tonight and I'll let you know the result.
Thanks a lot!
It was just like you said.
I had to format to ext3 and ext4 because I had errors.
Battery seems to be very good. Just the screen display is very white, needs color saturation and contrast I guess...
Thanks again you save my tablet.
Now that's what I like to read! :cyclops:

Categories

Resources