[Q] recovery mode problems with cache - G1 Q&A, Help & Troubleshooting

whenever i go into recovery mode i get an error on the bottom of the screem
BUILD : RA-dream-v1.7.0
E:Error in CACHE:recovery/log
(No Space left on device)
i cant nand backup or anything

rickyiswhite said:
whenever i go into recovery mode i get an error on the bottom of the screem
BUILD : RA-dream-v1.7.0
E:Error in CACHE:recovery/log
(No Space left on device)
i cant nand backup or anything
Click to expand...
Click to collapse
There are two possibilities:
1) The log is occupiing really the whole space on cache. In that case try to remove the log file from cache directory
2) Did you mess up with custom partion tables? To me this happened some time ago when I forgot to flash fr_boot_xxx.zip onto a boot.img while having installed custom partitions. In that case you have to clean everything. Eventually you need also to flash recovery again. If you have a recent backup, you can try to do a
fastboot erase system -w
then boot into recovery and see, if everything works for you again. If not you need to flash a new recovery:
fastboot flash recovery recovery.img
After that everything should work again, i.e. you can install your backup or you can install a new ROM.

AndDiSa said:
There are two possibilities:
1) The log is occupiing really the whole space on cache. In that case try to remove the log file from cache directory
2) Did you mess up with custom partion tables? To me this happened some time ago when I forgot to flash fr_boot_xxx.zip onto a boot.img while having installed custom partitions. In that case you have to clean everything. Eventually you need also to flash recovery again. If you have a recent backup, you can try to do a
fastboot erase system -w
then boot into recovery and see, if everything works for you again. If not you need to flash a new recovery:
fastboot flash recovery recovery.img
After that everything should work again, i.e. you can install your backup or you can install a new ROM.
Click to expand...
Click to collapse
hmm ok ill try that... thanks... and sometimes it says cant open cache or something

Related

RECOVERY - postrecoveryboot.sh - ERROR: 2

Google has no answer for me.
Every time I enter into the recovery and push the message button I get this ERROR: 2.
Everything works fine, its latest TWRP 3.0.2.
Could you tell me something about this error message 2?
What is 'postrecoveryboot.sh'?
How can I get this red message off / without error?
thanx in advance
How do I edit my boot script?
MichaBit said:
Google has no answer for me.
Every time I enter into the recovery and push the message button I get this ERROR: 2.
Everything works fine, its latest TWRP 3.0.2.
Could you tell me something about this error message 2?
What is 'postrecoveryboot.sh'?
How can I get this red message off / without error?
thanx in advance
Click to expand...
Click to collapse
Hi,
I have the same problem. Also on TWRP 3.0.2. and everything seems to work.
Can't find anything about this 'postrecoveryboot.sh' Error 2.
Did you find a solution in the meantime?
Thanks for any help in advance.
Arninho said:
Did you find a solution in the meantime?
Click to expand...
Click to collapse
No, unfortunately not.
If XDA has no solution, who else?
I have the same problem, this is inside the file
Code:
#!/sbin/sh
# Include device-specific vars
source /sbin/bootrec-device
# Turn the LED off
echo 0 > ${BOOTREC_LED_RED}
echo 0 > ${BOOTREC_LED_GREEN}
echo 0 > ${BOOTREC_LED_BLUE}
that error is because this file bootrec-device located at sbin folder always missing when reboot system or recovery
I have try many way
-flash stock rom with flashtool
-flash rom via recovery
-wipe via adb and fastboot
-chmod this file bootrec-device to read only
-remove this file postrecoveryboot.sh just come back after reboot recovery
all that way doesn't work
my Xperia unable to boot right know :crying:
maybe i'll try search what's file that create this??? postrecoveryboot.sh
where's boot script locate???
any help would be apreciated
InAMovies said:
my Xperia unable to boot right know :crying:
Click to expand...
Click to collapse
Thanks for that much information. :good:
A possible 'emergency solution' so that your device reboots again could be attached link.
What really surprised me, no one else has this ERROR: 2, and if not, why not?
http://www.flashtool.net/index.php
You can fix this 'postrecoveryboot.sh' Error 2 with a lower version twrp
I use twrp 2.8.7 which has been uploaded by someone from here androidfilehost.com/?fid=24052804347811669
flash with "fastboot flash boot boot.img" only if you UB, on LB try downgrade your twrp version
and then via file manager, just chmod the file bootrec-device located at sbin folder with read only access
my phone can only be booted only with rom existenz, and it was frequently rebooted and my battery status is unclear, sometimes 65% during the initial boot, and then only a 5% reboot afterwards
I have flash using flashtool with many based rom from 10.5.1.A, 10.6.1.A, 10.7.1.A latest, but it still does not make my phone work just to show sony screen flickered and died with the indicator is still red
all the problems occurred after I had this problem 'postrecoveryboot.sh' Error 2
I still do not know how to turn off the script, when I delete the file after reboot definitely go back there
hoping my phone can be normal again sometime
InAMovies said:
I still do not know how to turn off the script, when I delete the file after reboot definitely go back there
Click to expand...
Click to collapse
Could the cause for the error be a kind of provider branding?
So deeper implemented than the usual firmware.
My device was delivered via German Telekom.
[B]Solution![/B]
After installing Multirom v33 the error message is gone!
Dont ask why, both recoverys, the new one into the FOTA partition from attached link und the older, normal one 3.0.2.0 are error-free! :good:
https://forum.xda-developers.com/xperia-z/orig-development/mod-multirom-v33x-xperia-z-t3432385
I have installed the Modified recovery FOTA, before this error happen all working fine any custom rom working
but after this error, i can boot into recovery and install rom then reboot got bootloop, charger just show blip screen logo
just wanna try your idea with the Multirom v33 non modified
MichaBit said:
Google has no answer for me.
Every time I enter into the recovery and push the message button I get this ERROR: 2.
Everything works fine, its latest TWRP 3.0.2.
Could you tell me something about this error message 2?
What is 'postrecoveryboot.sh'?
How can I get this red message off / without error?
thanx in advance
Click to expand...
Click to collapse
Can You be so Kind to tell me how to flash in the correct way the latest version of TWRP with no error? Thank You very much!!
Ricky_Karmator said:
Can You be so Kind to tell me how to flash in the correct way the latest version of TWRP with no error? Thank You very much!!
Click to expand...
Click to collapse
Download latest recovery 'twrp-3.0.2-0-yuga.img' from link 1.
Put it to your Phone, turn of, push volume + and insert USB-cable for flashmode.
Blue LED-light appears.
Type -fastboot flash boot boot.img
-fastboot reboot
in ADB-connection CMD on your PC --> thats all.
Optional you can use the Tool in link 2.
*Flashing recovery successfully*
https://dl.twrp.me/yuga/
https://twrp.me/app/
MichaBit said:
Download latest recovery 'twrp-3.0.2-0-yuga.img' from link 1.
Put it to your Phone, turn of, push volume + and insert USB-cable for flashmode.
Blue LED-light appears.
Type -fastboot flash boot boot.img
-fastboot reboot
in ADB-connection CMD on your PC --> thats all.
Optional you can use the Tool in link 2.
*Flashing recovery successfully*
https://dl.twrp.me/yuga/
https://twrp.me/app/
Click to expand...
Click to collapse
I wa sure to copy the .img file in "platform-tools" folder in my PC and with cmd type "-fastboot flash boot boot.img" and not to have the file inside the internal memory of my Xperia Z. Obviously i think to rename "Twrp-3.0.blablabla" into boot.img
Ricky_Karmator said:
I wa sure to copy the .img file in "platform-tools" folder in my PC and with cmd type "-fastboot flash boot boot.img" and not to have the file inside the internal memory of my Xperia Z. Obviously i think to rename "Twrp-3.0.blablabla" into boot.img
Click to expand...
Click to collapse
Yes, very correct, copy and rename the file into 'boot.img' to your ADB-folder and flash it. :angel:
Finally with some free time i unlocked and flash the latest TWRP on my old Xperia Z. And yes i've got the same error "ERROR: 2". But everything works from backup to restore and flash Custom ROM. So i think we can nevermind about that
I have the same.
Sometimes my phone randomly reboot, and seems to be some app cause this reboots.
It was happend more and more often. And suddenly couple days ago my phone start to bootloop (just endlesly booting at xperia logo).
I have F5121 stock 8.0 Oreo and done all like in this manual https://forum.xda-developers.com/t/...els-latest-34-4-a-2-118-25-sept-2018.3594502/
So I was have rooted kenrnel twrp 3.2.3.0+DRM-Fix +magisk +FCS_1.3 +debloat script.
Almost 2 years of no problems and this surprise.
When I load to twrp and press menu button i see this:
Updating partition details...
...done
Unable to mount storage
So I was trying do backup of all partitions and after that I go in in wipe menu => advanced wipe => checkbox cache partition => fix patition
than I try to fix all patitions - it doesn't help.
So I do this:
wipe menu => advanced wipe => checkbox data partition => change to exFAT filesystem then => change back to EXT4 filesystem and restore data from backup. And do system/data partitions
and try to restore my backup - and it don't work.
EVEN my older backups don't works - I always become bootloop on xperia logo.
When I download twrp backup to PC and unpack cache.ext4.win\recovery I see file with name last_log.
Thats how last strings of file last_log look like:
~
ro.bootimage.build.date.utc=1533015130
ro.bootimage.build.fingerprint=Sony/omni_suzu/suzu:8.1.0/OPM4.171019.021.R1/4:eng/test-keys
ro.bootloader=s1
ro.debuggable=1
ro.property_service.version=2
init.svc.adbd=running
init.svc.ueventd=running
init.svc.recovery=running
init.svc.ldconfigtxt=stopped
init.svc.set_permissive=stopped
twrp.crash_counter=0
keyguard.no_require_sim=true
tombstoned.max_tombstone_count=50
Running boot script...
I:/sbin/postrecoveryboot.sh process ended with RC=0
Done.
I would like to hear some ideas why that may happen (Unable to mount storage). Coz i lost part of my data and don't wanna have the same experience again and again in future.

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:

Can't boot into system only twrp

So i was trying to install Liquid Remix rom on my op3t i wiped everything as the manual and have flashed opengapps magisk and the rom but when rebooted into the rom it asked me for my pin ive entered my pin but it said ur pin is correct but ur data has been corrupt u have to factory reset and automatically boots into twrp and when i try to boot into the system the process over and over again and i factory reset it nothing again says data is corrupt and ive flashed my recovery and try to boot into system nothing boots into fastboot iveand being a dummy i am i delted the system everything heard that u can fix it with adb sideloader but my question is can i flash a custom rom notthe stock rom please help me
Try to format data instead of wiping, either do it within TWRP (Wipe > Format Data > type "yes") or fastboot:
Code:
fastboot format userdata
Please note that all data is going to be lost, in case you didn't make a backup yet (if it's even possible to do it, since it says that data is corrupted).
przemcio510 said:
Try to format data instead of wiping, either do it within TWRP (Wipe > Format Data > type "yes") or fastboot:
Code:
fastboot format userdata
Please note that all data is going to be lost, in case you didn't make a backup yet (if it's even possible to do it, since it says that data is corrupted).
Click to expand...
Click to collapse
i already did that on accidentand deleted everything even the backups
Something similar happen to me. I was in twrp and was performing a full wipe(not factory reset), I installed RR, kernel, and then when I was installing gapps, the phone rebooted, and when I tried anything, it said e: legacy property not found( or something similar) and would not boot to system, would not flash anything, wouldn't boot to bootloader, but I was able to transfer files and use adb so I plugged into the computer and used adb reboot fastboot and booted to bootlaoder, now everything works
tergeltengo said:
i already did that on accidentand deleted everything even the backups
Click to expand...
Click to collapse
Backups are supposed to be stored outside the device you make a backup of, keep that in mind for future
Immortalis said:
Try to format data instead of wiping, either do it within TWRP (Wipe > Format Data > type "yes") or fastboot:
Code:
fastboot format userdata
Please note that all data is going to be lost, in case you didn't make a backup yet (if it's even possible to do it, since it says that data is corrupted).
Click to expand...
Click to collapse
Thank You, saved my phone.

help pls rog phone 2 soft bricked

Getting Failed to clear BCB message: failed to open /dev/block/boot/device/by-name/misc: No such file or directory after phone crash​
cant solve this please help
tried edl recovery flashed well but didnt solve problem
i have unlocked the bootloader and flashed many raw firmware didnt solved problem
flashed twrp sucessfully but cant mount storage intenal storage 0mb and cant swipe anything
get this message everytime in recovery
Getting Failed to clear BCB message: failed to open /dev/block/boot/device/by-name/misc: No such file or directory after phone crash​
please help
I have no idea it helps, I had my phone crash on me and me trying my old-and-tried flashing etc. I did not have such BCB message, but it sounds like there is an issue with the partitions or partitioning.
There are nice YouTube videos at least that show how to flash the stock ROM (not giving link here for advertising etc).
it boils down to (FIRST get your data off the phone as you are going to lose this)
- TWRP being bootable
- in TWRP: factory reset, wipe data
- flash stock ROM twice: to partition A and after reboot to TWRP, to partition B. I do not know why this needs to be done, love to learn it by myself.
- flash without wiping a custom recovery if wanted.
- restore your data

Categories

Resources