[Q] CWM Troubles (E: Can't open /cache/recovery etc. etc.) - Droid Incredible Q&A, Help & Troubleshooting

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.

Related

[Q] Please help! Nandroid restore froze, can't get past splash screen

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

[Q] Phone Stuck on HTC screen

I was running CM7 nightly 38 and everything was fine until my gps was not working so i tried to reboot it got stuck on the boot screen so then i tried to do a restore to an earlier nightly and now i get stuck on the HTC screen i can still get into the CW recovery but i dont know what to do help please
Edit : i dont know if this will help but i also get the error when i restore
E:Can't mount /cache/recovery/command
E:Can't Open /cache/recovery/log
E:Can't mount /cache/recovery/log
E:Can't Open /cache/recovery/last_log
E:Can't mount /cache/recovery/last_log w
And when i try to wipe Dalvik cache it also says unknown volume for path [/sd-ext]
It appears this is happening quite a bit lately. I too am plagued with this issue.
No help well can anyone answer this is it possible to unroot s-off the phone through clockworkrecovery mod so i can return for warrenty
Edit : Wondering what would happen if i did reset to factory in hboot would that make things even worse? i dont want to do it unless i get some information
hey man
don't worry so much your phone seems to be fine
just go and reflash your rom or flash a fresh rom
for example, go dl the stable version of CM and flash that instead~
hope this works
and btw when you flash a new rom, you want to wipe everything meaning wipe to factory settings
i have tried flashing a new rom to no avail it get stuck on htc boot screen i keep getting the cant mount cache error when doing things i think it might be the problem but thanks for the response
i was trying this method http://forum.cyanogenmod.com/topic/15623-how-to-fix-a-semi-bricked-g2/#entry175839
But im stuck on one part
~ # dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
dd: writing '/dev/block/mmcblk0p17': I/O error
1+0 records in
0+0 records out
0 bytes (0B) copied, 2.056183 seconds, 0B/s
if anyone knows i appreciate
Did you use Rage/gfree to root your phone? Then you should be able to flash PC10IMG.zip again. goodluck
i used Rage for the perm root im pretty sure. But how will i flash this PC10IMG.zip?
put it in my zip file then restart phone? I think ive read not to do this as it will certainly Brick you phone
Originally Posted by YuBlue View Post
well I got Desire Z so I'm not sure if it helps the G2 also but this is what I've done. First I downloaded the stock firmware here http://wiki.cyanogenmod.com/index.ph...ads#HTC_Vision and flashed it through fastboot. When it rebooted I could go use my phone again. Then I flashed CWM again and installed a engineering hboot. That's really what I did, when I flashed the orignial firmware I didn't lose my S-OFF for some reason. Maybe I'm lucky today
With flashing I meant renaming it to PC10IMG and reboot in bootloader
Click to expand...
Click to collapse
Not sure if it always works like this...
source: http://forum.xda-developers.com/showthread.php?t=949733&page=3
well PC10IMG.zip wont update it says failed
I have the same problem. Getting the same errors. wont let me flash new rom.
dragokld said:
well PC10IMG.zip wont update it says failed
Click to expand...
Click to collapse
You have to hex edit... because the PC10IMG.zip is older and you would need a newer version. I used unforgivens way of s-off and I would always have to hex edit, so my phone won't be semi-brick when I flash the orginal PC10IMG. Anyways am to to sure how to use ADB...
Sent from my HTC Desire Z using XDA Premium App
i read something about hex editing what do i hex edit i read it somewhere i cant find it now

[Q] (Q) Issues with flashing etc on Desire

Well, I have rooted my phone with unrevoked it installed the recovery mod 2.5.0.7 and I'm a bout to flash my phone. Thing is though I've been here for a while.
The story goes like this.. Relatively chronological..
I download HBOOT drivers install them on my Windows 7 64bit. I then download and run unrEVOked3, hook up my phone and choose charge only. unrevoked3 does it's thing and everything seems fine. I partition the SDcard with 6,5gb fat32 and 1gb ext4. Then i go into recovery i then go to wipe data/factory reset and chose it. Then i cant find dalvik data at first but i later find it, so i wipe that. Then I chose to install zip from sdcard which earlier moved. The InsertCoin A2SD+ 1.0.9 mod.
It starts up finds the file and starts flashing or so it seems.
It stops, and I cant remember the error message. So, I go searching cant really find anything except the fact that I should have wiped cache partitions also.. So I go back do a full wipe again and run it.
Then I get this error message: ( i tried again with a Cyanogen mod, and i got assert_failed write_raw_image...)
- assert failed: Package_extract_file("boot.img","/tmp/boot.img")
E: Error in /sdcard/InsertCoin_GB_Sense2.1_A2SD+_1.0.9.zip
(status 7)
Installation aborted..
I then find the baadnwz irc and ask for help there.. repartition my sdcard with gparted, and run through it all again...
Same error..
I then notice that CWMR is saying:
E: Cant fint MISC:
E: Cant mount Cache:recovery/command
E:Cant find misc:
E:Cant mount cache:recovery/log
E: cant fin misc:
I ask if this is normal, NO, is the clear answer i get.. so i test different things, new repartition correct sized and everything..
Still same..
Then I go and download the Froyo RUU and install it reset everything (of course i forgot to sync my contacts..) and i do everything from the top root, cwrm and try flashing but the same errors are still there..
So i then create this thread hoping that this error already isnt here after search.. And hoping someone can help me..?
I'm running the HTC Desire on HBOOT 0.93.0001, radio 5.11.05.27.
Worst thing is no matter how many times i wiped the different things no changes were made on the phone, when i rebooted i still got up my original bckgrnd image and everything...
So, what is going on?
It might be worth watching a few vids and reading a few guides. Here's a start http://forum.xda-developers.com/showthread.php?t=1016084. Also, don't worry. I messed up too when I first started to root and flash.
I can't remember what the status 7 error is and how to fix it. Think it's just to re-download the rom and try again.
If you have PVT4 device, you need to use AmonRA recovery.
I guess you're S-ON? If S-OFF try recovery from my sig.
Ironically I have used the tutorial in the development forum.. Used all the videos i could find, except s-off cause i was told i didnt have to do that when i was just flashing a new ROM..
How do i know if i have a pvt4 device?
edit: i found out.. im a pvt4 device..
Then root again, download recovery from my sig unpack .img and choose "custom recovery" in unrevoked and select it.
You can also use AmonRA recovery.
Or if you don't want to root again, S-OFF and flash new recovery in fastboot.
I don't really understand why they made CWM default recovery in unrevoked, people have so many issues with it. :-(
Sent from my HTC Desire using XDA App
spike0209 said:
Well, I have rooted my phone with unrevoked it installed the recovery mod 2.5.0.7 and I'm a bout to flash my phone. Thing is though I've been here for a while.
The story goes like this.. Relatively chronological..
I download HBOOT drivers install them on my Windows 7 64bit. I then download and run unrEVOked3, hook up my phone and choose charge only. unrevoked3 does it's thing and everything seems fine. I partition the SDcard with 6,5gb fat32 and 1gb ext4. Then i go into recovery i then go to wipe data/factory reset and chose it. Then i cant find dalvik data at first but i later find it, so i wipe that. Then I chose to install zip from sdcard which earlier moved. The InsertCoin A2SD+ 1.0.9 mod.
It starts up finds the file and starts flashing or so it seems.
It stops, and I cant remember the error message. So, I go searching cant really find anything except the fact that I should have wiped cache partitions also.. So I go back do a full wipe again and run it.
Then I get this error message: ( i tried again with a Cyanogen mod, and i got assert_failed write_raw_image...)
- assert failed: Package_extract_file("boot.img","/tmp/boot.img")
E: Error in /sdcard/InsertCoin_GB_Sense2.1_A2SD+_1.0.9.zip
(status 7)
Installation aborted..
I then find the baadnwz irc and ask for help there.. repartition my sdcard with gparted, and run through it all again...
Same error..
I then notice that CWMR is saying:
E: Cant fint MISC:
E: Cant mount Cache:recovery/command
E:Cant find misc:
E:Cant mount cache:recovery/log
E: cant fin misc:
I ask if this is normal, NO, is the clear answer i get.. so i test different things, new repartition correct sized and everything..
Still same..
Then I go and download the Froyo RUU and install it reset everything (of course i forgot to sync my contacts..) and i do everything from the top root, cwrm and try flashing but the same errors are still there..
So i then create this thread hoping that this error already isnt here after search.. And hoping someone can help me..?
I'm running the HTC Desire on HBOOT 0.93.0001, radio 5.11.05.27.
Worst thing is no matter how many times i wiped the different things no changes were made on the phone, when i rebooted i still got up my original bckgrnd image and everything...
So, what is going on?
Click to expand...
Click to collapse
try this, we have same problem... http://forum.xda-developers.com/showthread.php?p=16320099#post16320099
Somehow, installing alpharev and s-offing the phone, and then installing a new recovery helped me. Im now running cyanogen 7 om my phone

DInc Gingerbread Upgrade problem and Froyo CWM Errors - Can't Mount SDcard and Cache

This is a follow-up to my "Problem Installing Gingerbread; currently have Froyo 2.2 s-off" post.Thought I'd repost with an updated title that better reflects progress made so far in restoring my DInc.
Background:
- DInc purchased new; rooted; s-off; Incredikernal; Convert2Ext4_no_data_limit_normal_dalvik mod; CM7.2 (was on Tiny's CM10.1)
- Phone died while listening to music (plugged in to 5volt 2amp Nexus7 charger); would not boot beyond white HTC Incredible screen.
- Tried to restore nandroid backup.
- Upon booting to recovery received numerous “can’t mount” errors in ClockworkMod (CWM).
- Could not access zip from sdcard "E:Can't mount /sdcard/". (Note: also can't mount /emmc/)
- Tried loading image from nandroid backup via HBOOT, with no success
Progress:
- Flashed stock Froyo 2.2 via HBOOT successfully. DInc is working!
- Regained root via unrevoked3 successfully
- Flashed CWM 5.0.2.0 via HBOOT successfully
Issues:
1. Still can’t access sdcard
a. Confirmed card is formatted FAT32
b. SDCard seems OK – flashing image via HBOOT works and sdcard can be read from Froyo
c. Tried "fastboot oem enableqxdm 0" followed by “fastboot reboot” commands. Programs ran but still no access.
d. Tried to re-format a different sdcard in Froyo, card got corrupted!
- Formatted FAT32 on PC, inserted in phone
- “Unmount SDcard” and "Format SDcard" in Froyo, could not “Mount sdcard” in Froyo.
- PC says that SDcard needs to be formatted
e. Help please!
2. CWM mount errors:
a. ClockworkMod Recovery v2.5.1.2
E:Can't mount /dev/block/mmcblk0p2 (File exists)
E:Can't mount /cache:recovery/command
E:Can't mount /dev/block/mmcblk0p2 (File exists)
E:Can't mount /cache:recovery/log
E:Can't mount /dev/block/mmcblk0p2 (File exists)
b. ClockworkMod Recovery v5.0.2.0
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
c. Are these errors possibly related to bad partitions: Should I try Parted per topic 6433 at cyanogenmod forum (sorry, can’t post links)?
d. Are these errors possibly caused by the Convert2Ext4 mod, and should I try to run that again if/when I get my sdcard mounted?
e. Are these errors probably hardware related, and I stop looking for a software fix?
3. Gingerbread
a. I tried to load Gingerbread images (from pvillecomp, and also a version from cmlusco) via HBOOT; but no luck (boot loop).
b. I tried to load the Gingerbread RUU (from pvillecomp), but no luck. Perhaps a HTC Sync issue, but have not yet reloaded HTC Sync.
c. If I can't overcome mounting problems, I would at least like to be running Gingerbread vs Froyo (hence title of original thread).
d. Help please!
Thanks all,
Al
Please don't double post or post a new thread just to edit the title. You can edit your own OP to reflect progress made, (and edit the Title of the OP above the Message/Body portion in the Advanced edit screen).
Have you tried the latest TWRP? I see you have tried the latest CWM.
PonsAsinorem,
Sorry for double-posting, and thanks for taking the time to describe how I should go about changing the title going forward.
Thanks also for the suggestion to try TWRP instead of CWM. Unfortunately I couldn't get TWRP to load.
I downloaded the latest version for the DInc from the TWRP site (openrecovery-twrp-2.6.3.0-inc.img) and tried to load via fastboot - got the error message "FAILED: Remote not allowed".
I then tried to flash via HBOOT (I zipped the twrp image, naming the file PB31IMG.zip). It got to the "Parsing PB31IMG" stage, but I never received the option to Install Yes/No.
Any suggestions on what I am doing wrong?
Thanks again,
Al
BelmontAl said:
I then tried to flash via HBOOT (I zipped the twrp image, naming the file PB31IMG.zip). It got to the "Parsing PB31IMG" stage, but I never received the option to Install Yes/No.
Click to expand...
Click to collapse
Not quite as simple as just zipping. Here, load this one through HBOOT:
PB31IMG.zip - 4.04 MB
PonsAsinorem said:
Not quite as simple as just zipping. Here, load this one through HBOOT:
PB31IMG.zip - 4.04 MB
Click to expand...
Click to collapse
Thanks! That file loaded and I have TWRP running. I then tried to Mount the sdcard. The line item "highlights", but the checkbox doesn't check (The only items that "check" are System and Data).
Should I try "Factory Reset" as my next step?
Thanks again,
Al
Thanks PonsAsinorem for closing the other thread. My apologies again for the double post - I realize now how such a practice causes avoidable confusion.
Trozzul, thanks for your input on the other thread "yeah i saw that too i think it only works with AOSP, i think the problem might be your recovery, i saw that you used two different versions, 5.0.x.x and 2.5.x.x, have you tried the latest, 6.0.X.X? not sure if our ol dinc is update able to 6.0.x.x, i would try another custom recovery too, i know my inc has some flashing issues on CWM"
Per the ClockworkMod website, the latest CWM Recovery for the DInc is 5.0.2.0, so I think 6.0.X.X is not an option. Also, as mentioned above, PonsAsinorem has helped me get TWRP loaded. Am awaiting suggestions for next steps.
Thanks again,
Al
Well I'm just going to watch and see for right now, I'm not sure what's wrong with your twrp, maybe pons will know
Trozzul said:
Well I'm just going to watch and see for right now, I'm not sure what's wrong with your twrp, maybe pons will know
Click to expand...
Click to collapse
OK. Thanks Trozzul.

Can boot only into CWM on Tmobile SGH T-989

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

Categories

Resources