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
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.
so everything was working fine, I had strarburst rom and then try to load zedomax kernal via recovery, so I got to recovery and did a format/system then wipe cache etc.. and then I press power by accident then everything just got screw up, so now I can still get to recovery but I get a lot of errors see below, so anything that I do I get the following ..so I try to load a stock rom/kernal via odin( everything seams smooth because it loads it up,) but phone never reboots i get stock at boot screen.. any suggestions..
CWM-based Recovery v5.0.2.3
E: fail to open/etc/recovery.fstab (no such file or directory)
E: unknown volume for patch cache/recovery/log
E: Can't mount/cache/recovery/command
E: Can't open cach/recovery/log
got it fix, figure it out after 1 hour of hard searching for info etc..
Hey how's it going? I'm stuck in the boot loader. I had CM7 installed before and it got stuck in a loop. So, tried wiping cache/data and dalvik. Dalvik couldn't be wiped. Tried installing another rom and that didn't work at all. I'm able to get into recovery mode without a problem, but now I'm getting stuck on the HTC screen.
Error wise, I'm getting the following:
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
I've looked around for some help and couldn't find much help, but it was a recovery issue/ Don't have a backup or anything, and don't mind wiping everything and starting from scratch anyways.
I'm on a mac as of now but can grab a windows computer if needed. Any ideas?
Well, last resort should be to flash the ruu file that will get you back to stock. Honestly, this sounds like a hardware failure though. Try going to recovery, fixing permissions, then go to mounts and storage in recovery and manually mount those things and see what, if any errors you get.
Sent from my Incredible 2 using xda premium
Not a hardware failure at all. You just need to reflash your recovery Just follow the Guide #6 in my guides directory, just the part about reflashing the recovery.
Thanks for the replies and glad to hear it isn't a hardware failure. So as I said I'm on my mac and the phone doesn't come up under devices at all. Do I need the drivers still on the mac?
I was able to load the sd card onto my computer and throw the cam file in the root of the card. Is there a way to flash memory from that through clockwork or does it have to be through command prompt?
I had paranoid android installed on my phone running 4.1.2 and it kept crashing sometimes so I decided to go back to cm-10 which i used before but didn't prefer it. I did the exact same things I did last time but this time my phone would just stay at the cm-10 logo and never turn on. I had backup for paranoid android created before i flashed the cm-10 and so I tried restoring but it wouldn't work it my phone would turn off in middle of the restore. I tried that a few times and I just tried to retore the ORIGINAL 4.0 before i rooted my phone and it stopped in middle for that too and my phone just turned off. Idk what to do can anyone PLEASE HELP?? :crying:
I tried factory reset & clear data partition open it would also freeze in middle and turn off.
Also it says this at the bottom when i go to CWM recovery
E:can't open /cache/recovery/log
E:can't open /cache/recovery/log
E:can't open /cache/recovery/log/last_log
E:can't open /cache/recovery/log/last_log
PLEASE HELP ME CAN'T DO ANYTHING WITH THIS PHONE RIGHT NOW :crying:
You should try and redownload the ROM and place it at the root of your sdcard
I normally do...
Wipe Data/Factory reset
Wipe cache partition
install zip from sdcard
go to Advanced
Wipe dalvik cache
Wipe battery status
Fix permissions (just incase)
Reboot Device
wait about usually 3-8 minutes depends on the ROM. if it's longer then that then your stuck in a boot loop
this is all on done on CWMR v6.0.1.5
aplastar said:
You should try and redownload the ROM and place it at the root of your sdcard
I normally do...
Wipe Data/Factory reset
Wipe cache partition
install zip from sdcard
go to Advanced
Wipe dalvik cache
Wipe battery status
Fix permissions (just incase)
Reboot Device
wait about usually 3-8 minutes depends on the ROM. if it's longer then that then your stuck in a boot loop
this is all on done on CWMR v6.0.1.5
Click to expand...
Click to collapse
It wouldn't let me. That's the problem, anything I tried to do in recovery mode it would freeze and then turn off. And now it doesn't even go to recovery mode anymore! It just stays black the whole time. any help?
Last time I had this problem, I had to revert to stock using Odin and download mode.. works great now. It's a big hassle, but it is good to do a full reset every now and then. Then again, had so many problems with cwm that now I'm a twrp only man. That might help too.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app