Related
Well, I started out with CM7 RC4, and everything was dandy.
But then I decided to try out Virtuous. I did a Titanium Backup, then did a nandroid backup and wiped through ROM Manager. Virtuous was horribly laggy, however, so I decided to switch back to CM.
Upon restoring my nandroid, my G2 froze at the 'data' section, and I was forced to pull the battery. After reboot, it couldn't get past the white HTC screen. When I booted back into CWM, I immediately got the following:
"ClockworkMod Recovery v3.0.0.5
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log"
It reloads those errors every time I go back to the main menu of CWM, as well.
Every ROM I try and flash still gets stuck at the splash screen.
I've wiped everything there is to wipe, and any time I try and restore any of my nandroids, I get:
"Erasing boot before restore...
Error while erasing boot image!"
I've been looking for a solution for the past 4 hours and I can't seem to fix it. I don't even know what ROM is actually loaded on my phone.
Please, if anyone can help, it would be greatly appreciated! I just want to be able to actually use my phone.
pokemontrainer4life said:
Well, I started out with CM7 RC4, and everything was dandy.
But then I decided to try out Virtuous. I did a Titanium Backup, then did a nandroid backup and wiped through ROM Manager. Virtuous was horribly laggy, however, so I decided to switch back to CM.
Upon restoring my nandroid, my G2 froze at the 'data' section, and I was forced to pull the battery. After reboot, it couldn't get past the white HTC screen. When I booted back into CWM, I immediately got the following:
"ClockworkMod Recovery v3.0.0.5
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log"
It reloads those errors every time I go back to the main menu of CWM, as well.
Every ROM I try and flash still gets stuck at the splash screen.
I've wiped everything there is to wipe, and any time I try and restore any of my nandroids, I get:
"Erasing boot before restore...
Error while erasing boot image!"
I've been looking for a solution for the past 4 hours and I can't seem to fix it. I don't even know what ROM is actually loaded on my phone.
Please, if anyone can help, it would be greatly appreciated! I just want to be able to actually use my phone.
Click to expand...
Click to collapse
From the looks of it. It seems that you messed up your recovery , all you have to do is go back into fastboot and then reflash/reinstall the recovery.img and everything should be working fine afterwards
derykisonder said:
From the looks of it. It seems that you messed up your recovery , all you have to do is go back into fastboot and then reflash/reinstall the recovery.img and everything should be working fine afterwards
Click to expand...
Click to collapse
I've read a few places that you need the engineering hboot. Is that true?
And how can I tell if I have it already?
Well it appears I don't have the engineering hboot. When I flashed the recovery via fastboot it came back saying "FAILED (remote: not allowed)".
Is there a way I can install the hboot without using Terminal on the phone?
Wow same for my i dont have Eng hboot i thought i put it in my phone but somehow its gone know D: looking for solution :/
OK, I had this same problem and was able to fix it. I d on't know how many of you this will help but here is what I did. I was able to boot into CWM and choose advanced restore where I manually restored the system and data files. I then reboot my device and I was able to get it to fully boot. So far I have seen no real issues with the phone and it's better than a brick; it will at least get you running again so you can try something different if need be.
pokemontrainer4life said:
Well it appears I don't have the engineering hboot. When I flashed the recovery via fastboot it came back saying "FAILED (remote: not allowed)".
Is there a way I can install the hboot without using Terminal on the phone?
Click to expand...
Click to collapse
Ever heard of adb?
Sent from my T-Mobile G2 using XDA Premium App
flash & restore
I had a workaroudn for something similar - basically phone wouldnt boot past splash screen after losing power. I was able to make a CWM backup, and the only way i could find to get all my things back was to do a fresh os flash and work with some nandroid abckup files to try to extract the data out manually - there is one called Nandroid Manager, but it ahsnt always worked for me, but a great concept. worth a try, if not there appears to be other products on the market now which may help
I would love your guy's opinions on this issue. I was planning to do a fresh install of Cyanogenmod due to wifi issues when I ran into some trouble. I just updated my Clockworkmod recovery from 3.0.0.8 to 5.0.2.0 this morning, and it has been bringing up errors along the lines of:
Code:
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/log
E: Error in /cache/recovery/log
(Read-only file system)
I read up on these errors, and it seems that attempting to flash ROMs and whatnot with these errors often lead to bricked devices. So far, my device still works fine (minus the WiFi, obviously), and I've successfully flashed the recovery several times, performed a nandroid backup, and reflashed my kernel without error, as far as I can tell. However, given the nature of these errors, I am much too nervous to try reflashing Cyanogenmod. So far I have attempted downgrading CWM, checking my emmc and checked the cache partition for the files CWM supposedly can't open. last_log is present, but log is not. From the results of the emmc test, I think it's working fine, but I'd like you guys to verify that for me. Below is about as detailed a log as I can give of what has happened today. Any assistance in fixing this problem and making sure it is safe to reflash Cyanogenmod would be extermely appereciated.
Phone Info
HTC Droid Incredible (ADR6300)
Cyanogenmod 7.1.0 RC1
Android 2.3.4
Clockworkmod Recovery 3.0.0.8
Incredikernel 2.6.38.8 (8/15/11)
HBOOT 0.92.0000
Radio 2.15.00.07.28
S-OFF
Code:
Events leading up to this:
Flashed CWM 5.0.2.0 through ROM Manager-flash failed
Rebooted into recovery-still running 3.0.0.8
Rebooted phone
Tried again through ROM Manager with "erase recovery" option checked
Rebooted into recovery-still running 3.0.0.8
Rebooted phone
Flashed CWM 5.0.2.0 through Terminal Emulator
Rebooted into recovery-flash was successful
Rebooted phone
Discovered WiFi error issue
Rebooted into CWM 5.0.2.0
Performed a nandroid backup, which appeared to be successful
Errors appeared at some point, can't remember when.
"E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_log"
Rebooted phone
Rebooted into CWM 5.0.2.0
Wiped Dalvik cache and reflashed incredikernel, thinking it would fix the WiFi issue
Flash seemed successful, same errors popped up again, can't remember exactly when
Rebooted phone
Researched errors, came to notice that navigating menus and backing out now caused:
"E: Error in /cache/recovery/log
(Read-only file system)
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_log"
Further navigation would always produce:
"E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_log"
Code:
Steps taken to fix the problem (so far)
Tried flashing CWM 3.0.0.8 through ROM Mangager
Rebooted into recovery-still running 5.0.2.0
Tried flashing CWM 3.0.0.8 through adb
Rebooted into recovery-flash was successful
Errors still persisted
Found a thread suggesting the problem may be with a faulty emmc
Ran "cat /proc/kmsg | grep mmc0" through adb to test the emmc
Results of test
Checked to see if log and last_log files exist
Found last_log, not log
Images of the problem
Results of the emmc test
Errors in CWM 5.0.2.0
Errors in CWM 3.0.0.8
last_log is present in /cache/recovery
Have you wiped the cache partition from recovery and then flash cwm recovery from hboot as a PB31IMG.zip?
How exactly do I go about doing that? I know how to wipe the cache, but do I just rename the CWM zip to PB31IMG.zip and flash it?
Rixanu said:
How exactly do I go about doing that? I know how to wipe the cache, but do I just rename the CWM zip to PB31IMG.zip and flash it?
Click to expand...
Click to collapse
Um not sure what file you have but here is one for you http://dinc.does-it.net/PB31IMG.zip, just place it on the root of your sdcard and boot into hboot. It will find the file after a couple secs and prompt to press vol up to install. This is version 5.0.1.0
Also you may want to run fix permisions from the advanced menu in recovery.
You are quite the lifesaver, it worked like a charm! One more question, though. I would like to upgrade CWM to 5.0.2.0 if possible. Would it be safe to flash it through terminal emulator/adb, or should I just update through hboot from now on? Thanks so much for your help!
Rixanu said:
You are quite the lifesaver, it worked like a charm! One more question, though. I would like to upgrade CWM to 5.0.2.0 if possible. Would it be safe to flash it through terminal emulator/adb, or should I just update through hboot from now on? Thanks so much for your help!
Click to expand...
Click to collapse
No problem. Hboot is the best way to do it. I dont have a 5.0.2.0 file at the moment but if you need one i can get it for you.
Edit: you could also update it thru rom manager and if for some reason it messes something up just flash the one from earlier post again.
That's alright, I found one a few minutes ago, just in case. This also seems to have fixed my wifi issue, so this is about the best case scenario I can picture. Thanks again!
Your welcome.
I guess all is not as it seems. The problem in CWM started popping up again just a few minutes ago. On top of that, when I rebooted, I got caught in a bootloop. I managed to boot up fine after a battery pull, but this is really starting to scare me. Does anyone have any advice?
PS. I'm posting here because I feel this doesn't need a whole new topic. If that would be better, just let me know.
Rixanu said:
I guess all is not as it seems. The problem in CWM started popping up again just a few minutes ago. On top of that, when I rebooted, I got caught in a bootloop. I managed to boot up fine after a battery pull, but this is really starting to scare me. Does anyone have any advice?
PS. I'm posting here because I feel this doesn't need a whole new topic. If that would be better, just let me know.
Click to expand...
Click to collapse
I would revert back to CWM 3.0.0.8 thru rom manager for awile and see if the problem still persists. However once you do make sure to make a new nandroid as i dont believe cwm 5 backups are compatible with version 3.
Rom manager didn't work (again), so I flashed through hboot and it worked fine. Errors are gone, and no more bootloops since last night. I'm gonna wipe and reflash Cyanogen later today because my wifi is all buggy again and I feel as if a clean install may hopefully kill any latent symptoms. Feel free to let me know it that's a bad idea, haha. Thanks again.
Hello all.
I have tried to get my phone up and running for the 3 past days now.
I have been googling and trying everything to get it to work.
I am getting AN errors like this one: cant access to system/csc/TEN/system ´.
everytime I try to install official thrue Odin 4.42 using this firmware: S5660XXKTU_S5660XXKTA_S5660TENKT2
Then it boots and goes into revovery
I managed to get enhanced236 working. But then there was a problem with TWLauncher.
I did a factory resett in the phone and then it all got Fu"#% up. Now I cant even wipe data from CWM, nor original recovery
FCC ID:A3LGTS5660
SSN: -S5660GSMH
Hoping someone can help me out.
I am getting this error when trying to install official firmware:
--Appling Muti-CSC --
Cant access to ´/system/csc/TEN/system´.
I cant wipe data, It will freeze or just reboot into recovery again.
____________________
If I root and install CWM (signed_cwm-5.0.2.7-flashablezip-ext4only.zip)
I get these errors:
E: cant mount /cache/recovery/command
E: cant mount /cache/recovery/log
E: cant open /cache/recovery/log
E: cant mount /cache/recovery/last_log
E: cant open /cache/recovery/last_log
Then if I wipe cache theese errors disapears.
But no I cant wipe data(factory reset)
It freezes or reboots.
If I try to install enhanched or another firm it will stopp when wiping data.
If I choose not to format it freezes wfen skipping format and wipe.
Please help...
GizmoPower said:
I am getting this error when trying to install official firmware:
--Appling Muti-CSC --
Cant access to ´/system/csc/TEN/system´.
I cant wipe data, It will freeze or just reboot into recovery again.
____________________
If I root and install CWM (signed_cwm-5.0.2.7-flashablezip-ext4only.zip)
I get these errors:
E: cant mount /cache/recovery/command
E: cant mount /cache/recovery/log
E: cant open /cache/recovery/log
E: cant mount /cache/recovery/last_log
E: cant open /cache/recovery/last_log
Then if I wipe cache theese errors disapears.
But no I cant wipe data(factory reset)
It freezes or reboots.
If I try to install enhanched or another firm it will stopp when wiping data.
If I choose not to format it freezes wfen skipping format and wipe.
Please help...
Click to expand...
Click to collapse
signed_cwm-5.0.2.7-flashablezip-ext4only.zip
wrong recovery!
Stock is not ext4!
use other recovery and errors should be gone
And download cwmext4+rfs
Sent from my GT-S5660 using xda app-developers app
I´ve tried everything..
I dont get what I am doing wrong.
I just tried another recovery ( signed_cwm-5.0.2.7-flashablezip-ext4+rfs )
Flashed stock rom ( S5660XXKTU_S5660XXKTA_S5660TENKT2_HOME.tar) with Odin 4.4.2
Same errors:
Cant access to /system/csc/TEN/system
Can someone please explain in detail how I can get it working.
Dont mind falshing a nonstock rom.
Thanx
GizmoPower said:
I´ve tried everything..
I dont get what I am doing wrong.
I just tried another recovery ( signed_cwm-5.0.2.7-flashablezip-ext4+rfs )
Flashed stock rom ( S5660XXKTU_S5660XXKTA_S5660TENKT2_HOME.tar) with Odin 4.4.2
Same errors:
Cant access to /system/csc/TEN/system
Can someone please explain in detail how I can get it working.
Dont mind falshing a nonstock rom.
Thanx
Click to expand...
Click to collapse
Here's a thread with a lot of info about flashing, including a step by step guide.
X-zone said:
Here's a thread with a lot of info about flashing, including a step by step guide.
Click to expand...
Click to collapse
Thanks but..
I think you forgot the link
GizmoPower said:
Thanks but..
I think you forgot the link
Click to expand...
Click to collapse
Woops! Here it is! http://forum.xda-developers.com/showthread.php?t=2394513
Sent from my GT-S5660 using xda app-developers app
I loaded CWM v5.0.2.6 then wiped cached and dalvik cache then did a master reset. After rebooted, goes into bootloop with the tmobile s2 logo, progress bar goes all the way to the right then reboots, sometimes to the middle,sticks, then reboots and repeats. I then updated the CWM to v6.0.4.3 this morning, updated fine but told me my phone was not rooted. When I try to wipe cache, it hangs on the formatting cache (don't know if this latest CWM is compatible with the t-989?) If I try to do a reset, the recovery hangs. I have had this S2 since the S2's first came out with Tmobile.
I want to install a fast kicka** rom. Well, as fast as an S2 is concerned. Just need help. Trying to learn the OS also, but for now just want to get this running. Thanks.
1.Phone is not rooted, (correction, I just ran a rooted program while in recovery and it passed,so maybe it is) I thought is was but CWM recovery said it wasn't
2. Boot loops while loading with Tmobile S2 logo displayed
3. Loaded CWM rocovery v5.0.2.6 When a master reset/wipe was performed with this version, it completed but still boot looped
4. Loaded CWM recovery v6.0.4.3 When trying to do a master reset/wipe cache, hangs and freezes. Will complete a Dalvik wipe though.
5. This 989 has been unlocked also from Tmobile
Mike
I put Carbon ROM on my phone last night, well, I tried. I put the file on an SD card, installed the card and powered up into CWM. Performed the install, everything went well as far as the output from the install went but now, as expected, do not have the T-Mobile S2 boot screen with progress bar, just a blank screen after I reboot, get the samsung logo, then it looks like something tries to start in the middle of the screen then freezes.
I can go back into CWM no problem, perform a backup, reinstall Carbon ROM, everything in CWM works, runs fine EXCEPT when reading erasing or wiping the CACHE.
And I always get the:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I have a feeling it is something with a corrupted file in the cache; wonder how I came to that deduction?
I will keep posting till this is resolved, am scouring the internet for solutions and answers to screen printouts while going through the steps
to resolve this.
5egeek said:
I put Carbon ROM on my phone last night, well, I tried. I put the file on an SD card, installed the card and powered up into CWM. Performed the install, everything went well as far as the output from the install went but now, as expected, do not have the T-Mobile S2 boot screen with progress bar, just a blank screen after I reboot, get the samsung logo, then it looks like something tries to start in the middle of the screen then freezes.
I can go back into CWM no problem, perform a backup, reinstall Carbon ROM, everything in CWM works, runs fine EXCEPT when reading erasing or wiping the CACHE.
And I always get the:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I have a feeling it is something with a corrupted file in the cache; wonder how I came to that deduction?
I will keep posting till this is resolved, am scouring the internet for solutions and answers to screen printouts while going through the steps
to resolve this.
Click to expand...
Click to collapse
FIXED FIXED FIXED!!!!!!!!!!!!!!!!!!
Am going through the Carbon ROM setup now. Will post more later today. Have to go to work in a bit.
Mike
Hi,
I installed clockworkmod recovery 6.0.5.1 via Odin, rooted my Samsung Galaxy s4 Mini and installed cyanogenmod 11 (from this thread http://forum.xda-developers.com/showthread.php?t=2558685). Everything went fine, but when I enabled wifi connection my device freezed and when I removed the battery it wouldn't power on again: the display didn't light up and it wouldn't even vibrate.
After a full night charge, the device turned on again, but it is stuck on the black screen with the white Samsung logo and a yellow writing saying "Set Warranty Bit: kernel".
I tried flashing the stock rom but it didn't work (https://samsung-firmware.org/download/Galaxy-S4-Mini-LTE/62n1/ITV/I9195XXUCOG1/I9195ITVCOG1/). I then tried installing another cyanogenmod, but the result didn't change, so I flashed different recoveries through Odin, but I can't get them work: I am stuck with the cwm 6.0.5.1 and can't change nor the recovery, nor the ROM.
In the download mode I can see "write protection: enable" on the top of the screen and if I enter in the cwm recovery I get on the bottom:
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
Do you have any ideas on how could I get it to work?
Thank you.
you can asscess recovery? :/
InFam0us-1985 said:
you can asscess recovery? :/
Click to expand...
Click to collapse
Yes I can, but the problem is that when I try to flash a ROM to boot android the recovery says that the installation is complete, but when I reboot nothing changed. Is there an effective way to replace this recovery and install a ROM? Thank you for your time.
Well nooby stuff - did you Clear dalvik cache and cache partition? and do the system and data wipe before flashing the rom?