Database Develop

[Q] recovery mode problems with cache

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

kernel flashing sequence..

Does it matter if i flashed kernel, wipe, install rom? Thats how i been doing..
Just curious cuz i seen it saying u need to wipe, flash kernel, than immediately rom.
But once i flash kernel phone reboots which means i have to force close/take out battery so the phone wont try to boot to os.

greypimps said:
Does it matter if i flashed kernel, wipe, install rom? Thats how i been doing..
Just curious cuz i seen it saying u need to wipe, flash kernel, than immediately rom.
But once i flash kernel phone reboots which means i have to force close/take out battery so the phone wont try to boot to os.
Click to expand...
Click to collapse
in fastboot, the phone will not reboot until you tell it to
Code:
fastboot flash boot boot.img
thats it, if you do a fastboot reboot command after, thats why you are getting a reboot.
after flashing the kernel, just hit 'bootloader' then 'recovery' and it will boot straight into recovery

What about when you flash a kernel that has other files with it? Example below:
bcm4330.ko
From the .bat file that came with it, it copies it over to the system modules directory. I mean I guess if you mount the /system directory in CWM then you could flash via adb. The file up above being named bcm4330 makes me think it is some kind of network driver.

unc-newbie said:
What about when you flash a kernel that has other files with it? Example below:
bcm4330.ko
From the .bat file that came with it, it copies it over to the system modules directory. I mean I guess if you mount the /system directory in CWM then you could flash via adb. The file up above being named bcm4330 makes me think it is some kind of network driver.
Click to expand...
Click to collapse
If its copying over a .ko file, you better already have a rom installed since ko files go in /system/lib/modules. If you copy that file over and then install the rom it was all for nil.
Sent from my GT-I9100

[Q] [CWM Manager][Help needed][Flash Stock firmware option]

CWM Manager has the ability to flash firmware parts either from separate files (zImage, factoryfs.img, etc) or from .tar / .tar.md5 files that they usually come packaged in.
- Download the firmware you want to flash
- If you have a ZIP or RAR file, extract it until you have seperate files, or .tar / .tar.md5 files
- Create a folder named 'firmware' on your external SD card
- Copy the files you want to flash to this folder ( /sdcard/external_sd/firmware ). factoryfs ("system") is mandatory part at the moment.
- TIP: If you are flashing a new firmware that already has a CF-Root kernel available, put it in the 'firmware' folder as well in zImage or .tar form (NOT .zip). Select it when asked which kernel to use, then use the "Flash normally" option later on.
- Open the CWM Manager app
- Select "Flash stock firmware"
Click to expand...
Click to collapse
Is what im following. I have the RocketRom files extracted into the internal SD card /external_sd/firmware folder and one on the external SD card with the folder firmware. The rocketRom zip had META-INF - system - modem.bin - zImage. But when i click on Flash stock firmware it says it cant find anything. Did i do something wrong? Or actually im not sure what im doing wrong.
Thanks for any help!

Renren1403 said:
Is what im following. I have the RocketRom files extracted into the internal SD card /external_sd/firmware folder and one on the external SD card with the folder firmware. The rocketRom zip had META-INF - system - modem.bin - zImage. But when i click on Flash stock firmware it says it cant find anything. Did i do something wrong? Or actually im not sure what im doing wrong.
Thanks for any help!
Click to expand...
Click to collapse
Stock firmware is always .tar files, Rocket ROM is .zip file..
Put the whole Rocket ROM .zip folder in your sd card (do not unzip it), open Mobile Odin and choose flash update zip and then choose RocketRom.zip
EDIT: or you can just put the zip in your sd card, reboot into recovery, choose install zip from sd card and then reboot system

Thanks i tried that. But when it rebooted everything looked the same. Is that what the rocketrom looks like?

matius44 said:
Stock firmware is always .tar files, Rocket ROM is .zip file..
Put the whole Rocket ROM .zip folder in your sd card (do not unzip it), open Mobile Odin and choose flash update zip and then choose RocketRom.zip
EDIT: or you can just put the zip in your sd card, reboot into recovery, choose install zip from sd card and then reboot system
Click to expand...
Click to collapse
but if i use recovery wont it increase my counter?

Renren1403 said:
but if i use recovery wont it increase my counter?
Click to expand...
Click to collapse
No, recovery and mobile odin will not increase your flash counter
Flash counter will increase only if you flash custom firmware using PC Odin

Renren1403 said:
Thanks i tried that. But when it rebooted everything looked the same. Is that what the rocketrom looks like?
Click to expand...
Click to collapse
Rocket ROM is stock-like custom ROM so yes it will look the same
Go to Settings > about phone and check

Thank you so much for your help.. The official CF posts for flashing ROMs are so confusing and such. Thanks for clearing it out for me +1

matius44 said:
Rocket ROM is stock-like custom ROM so yes it will look the same
Go to Settings > about phone and check
Click to expand...
Click to collapse
I just did it via recovery mode, the animation starts then goes to a black screen. Is it rebuilding its cache?

Renren1403 said:
I just did it via recovery mode, the animation starts then goes to a black screen. Is it rebuilding its cache?
Click to expand...
Click to collapse
Did the flash went successfully?
Try to reboot couple of times, that might help..
If not, reboot to recovery, do cache and dalvik wipe..
If not, try to reboot into recovery and do factory reset/data wipe/cache/dalvik wipe and reboot..you will lose your data this way

matius44 said:
Did the flash went successfully?
Try to reboot couple of times, that might help..
If not, reboot to recovery, do cache and dalvik wipe..
If not, try to reboot into recovery and do factory reset/data wipe/cache/dalvik wipe and reboot..you will lose your data this way
Click to expand...
Click to collapse
It didnt say any errors when installing so it shouldve of went fine.
Im doing a cache wipe. and it just went to a black screen after "calling all speed demons"
Ill doo a factory wipe then and get back to you. Thanks for your help so far!

I re did the whole process this time. And it still goes black after "calling all speed demons". Should i wait during this time? In the s2 forums i read about it going like this because it is building cache or something along those lines.
I judt reread the whole RM thread. I didnt read the "flash 22 first" bit. Ill do that and hope it works that time ><!

Can't mount /data and /system

I've tried TWRP and Philz CWM and I've tried flashing a number of roms. But it gives me an error that /data and /system can not be mounted.
I really need help with this. I have tried deleting and formatting everything which is available in the recoveries I've tried and it gives the same error if I try to format them (in the recovery menu).
I'd love to get any help ty

I really need help with this.. I can give 1 dollar paypal to a person who fixes this for me...

jeyko said:
I've tried TWRP and Philz CWM and I've tried flashing a number of roms. But it gives me an error that /data and /system can not be mounted.
I really need help with this. I have tried deleting and formatting everything which is available in the recoveries I've tried and it gives the same error if I try to format them (in the recovery menu).
I'd love to get any help ty
Click to expand...
Click to collapse
What't the exact message you see?

kalpetros said:
What't the exact message you see?
Click to expand...
Click to collapse
I don't have the device infront of me but I am 99% sure it was
"Can't mount /system
Can't mount /data"
For the record I can flash a STOCK rom with Odin. I don't think there is a way to flash any other roms by usb neither with heimdall nor odin.
Attempting to format data and system just outputs the same error.
I've been used to playing around with HTCs. Is there a way to for me to format data and system via the Android Console or adb?
I also tried fully formatting sdcard0(internal sdcard) and sdcard1(external sdcard) and flashing stock from Odin and then a recovery (I understand recovery =kernel on samsung?) with heimdall.
Can I try flashing via built-in recovery with update.zip or something like aroma installer just won't work?

jeyko said:
I don't have the device infront of me but I am 99% sure it was
"Can't mount /system
Can't mount /data"
For the record I can flash a STOCK rom with Odin. I don't think there is a way to flash any other roms by usb neither with heimdall nor odin.
Attempting to format data and system just outputs the same error.
I've been used to playing around with HTCs. Is there a way to for me to format data and system via the Android Console or adb?
I also tried fully formatting sdcard0(internal sdcard) and sdcard1(external sdcard) and flashing stock from Odin and then a recovery (I understand recovery =kernel on samsung?) with heimdall.
Can I try flashing via built-in recovery with update.zip or something like aroma installer just won't work?
Click to expand...
Click to collapse
Which stock firmware are you using? Try to flash XXJVU with Odin. Also use a 512 pit and check re-partition.

Yes, recovery is built in the kernel. It can't be flashed separately.

kalpetros said:
Which stock firmware are you using? Try to flash XXJVU with Odin. Also use a 512 pit and check re-partition.
Click to expand...
Click to collapse
Last time I attempted to install XXJVU it bootlooped. I will attempt what you suggested this evening. I have the correct pit files.
The stock firmware which worked:
XWJVW/XXJVT/OXXJV9/Sbl (MultiCSC): Download (143 MB) (Build date: Fri Oct 28 19:40:18 KST 2011)
(MultiCSC: AUT, BSE, CNX, COA, COS, CPW, CRO, CYO, CYV, EUR, IRD, KOR, MET, MOZ, MSR, MTL, O2C, ONE, ORO, ORS, SEB, SIM, SMO, SUN, TMZ, TOP, TPH, TRA, TRG, TSR, TWO, VDH, VDI, VIM, VIP, VVT, XEH, XEO, XEZ, XFA, XFC, XFE, XFM)
Stock Kernel: Download
Click to expand...
Click to collapse

kalpetros said:
Which stock firmware are you using? Try to flash XXJVU with Odin. Also use a 512 pit and check re-partition.
Click to expand...
Click to collapse
Not fixed. Seems to show like they can mount on Semaphore kernel but trying to flash any rom results in a bootloop. Flashing ANOTHER kernel results in... Unable to mount /system & /data
EDIT: fixed. ur a god. give me ur paypal on PM

jeyko said:
Not fixed. Seems to show like they can mount on Semaphore kernel but trying to flash any rom results in a bootloop. Flashing ANOTHER kernel results in... Unable to mount /system & /data
EDIT: fixed. ur a god. give me ur paypal on PM
Click to expand...
Click to collapse
Glad it worked. There is no need to pay me my friend. Just hit the thanks button.

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.