Related
I think my CM7 installation is f up. It did not install, and I can't go back to my phone! Its stuck on Google logo with an unlock key down below. I can get in clockworkmod recovery though. Any help?
Did u try to install it from the recovery menu that should work
Sent from my PC36100 using XDA Premium App
smoothfreeze said:
I think my CM7 installation is f up. It did not install, and I can't go back to my phone! Its stuck on Google logo with an unlock key down below. I can get in clockworkmod recovery though. Any help?
Click to expand...
Click to collapse
go into recovery, wipe data/factory reset, flash cm7, flash gapps(google apps add on), reboot. if that still leads you to the same place, then redownload the rom, put it on your sd card, and try again.
simms22 said:
go into recovery, wipe data/factory reset, flash cm7, flash gapps(google apps add on), reboot. if that still leads you to the same place, then redownload the rom, put it on your sd card, and try again.
Click to expand...
Click to collapse
and wipe dalvik (in advanced).
Wait, I'm at recovery mode now. A whole bunch of lines appeared at the bottom of the screen.
E:Can't mount /cache/recovery/last_log
E:Can't find /cache/recovery/last_log
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
smoothfreeze said:
Wait, I'm at recovery mode now. A whole bunch of lines appeared at the bottom of the screen.
E:Can't mount /cache/recovery/last_log
E:Can't find /cache/recovery/last_log
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
Click to expand...
Click to collapse
You get this error because you are using i9023 version of Nexus S and you installed the stock version of Clockworkmod Recovery
You should install the Clockworkmod Custom Recovery from the Development Forums for the i9023.
I have some weird stuff going on and I was wondering if maybe someone could tell me what it means. My phone is running fine, in fact better than ever. But when I reboot into recovery mode, and before I apply update.zip and I am in stock recovery (blue), I get the follow message below all of the recovery options (error message is in red):
E: Can't mount /dev/block/st111
(Invalid Argument)
E Can't mount /dev/block/mmcblk0p1
(Invalid Argument)
# MANUAL MODE #
E: Can't mount /dev/block/st111
(Invalid Argument)
E: Can't mount /dev/block/st111
(Invalid Argument)
Then, when I do a backup through CWM, everything goes through fine and then I get this message:
Back complete!
E: Can't open /cache/recovery/log
E: Can't open CACHE:recovery/log
When I go into CWM recovery, I do see a backup labeled with the correct date and everything, so I guess it is backing up correctly? Not quite sure what to make of it.
Ignore it.
Sent from my SCH-I500 using XDA App
JayRHamlin said:
I have some weird stuff going on and I was wondering if maybe someone could tell me what it means. My phone is running fine, in fact better than ever. But when I reboot into recovery mode, and before I apply update.zip and I am in stock recovery (blue), I get the follow message below all of the recovery options (error message is in red):
E: Can't mount /dev/block/st111
(Invalid Argument)
E Can't mount /dev/block/mmcblk0p1
(Invalid Argument)
# MANUAL MODE #
E: Can't mount /dev/block/st111
(Invalid Argument)
E: Can't mount /dev/block/st111
(Invalid Argument)
Then, when I do a backup through CWM, everything goes through fine and then I get this message:
Back complete!
E: Can't open /cache/recovery/log
E: Can't open CACHE:recovery/log
When I go into CWM recovery, I do see a backup labeled with the correct date and everything, so I guess it is backing up correctly? Not quite sure what to make of it.
Click to expand...
Click to collapse
I've had this happen and it happens when you have lagfix enabled and try to revert/odin back to a stock kernel (non voodoo) you'll need to follow the manual disabling procedure (of lagfix) by injecting an empty file named "disable lagfix" into the clockwork folder on your SD card then reboot. After that you should be clear to do a clean flash to get everything working properly. If you tried restoring right now it would probably give you an MD5 mismatch, and trying to flash from recovery would probably give you dev/block errors and it would cancel installation until you get your file system back in order.
bdemartino said:
I've had this happen and it happens when you have lagfix enabled and try to revert/odin back to a stock kernel (non voodoo) you'll need to follow the manual disabling procedure (of lagfix) by injecting an empty file named "disable lagfix" into the clockwork folder on your SD card then reboot. After that you should be clear to do a clean flash to get everything working properly. If you tried restoring right now it would probably give you an MD5 mismatch, and trying to flash from recovery would probably give you dev/block errors and it would cancel installation until you get your file system back in order.
Click to expand...
Click to collapse
OK that makes sense. I was flashing all over the place trying to fix that radio issue. Although I liked Add's answer better. Much more convenient
Sent from my SCH-I500 using XDA App
JayRHamlin said:
OK that makes sense. I was flashing all over the place trying to fix that radio issue. Although I liked Add's answer better. Much more convenient
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Lol yea, I tried that too when I buggered mine up, but since I couldn't flash anything in recovery I decided to find out how to fix it
Hi there,
I used Cyanogenmod 1.1 beta for a while and while I was pretty happy about it, it did have some issues i wasn't very fond of. So I decided to to perform a nandroid restore of my stock rom and succeeded. My stock rom kept crashing when trying to use internet (synchronising, browsing etc). While messing a little with the settings (like no account syncing etc) my phone crashed and it went into an infinite bootloop. I went into recovery, did the neccesary wipes and performed a nandroid recovery to my Cyanogenmod again. It errored while doing so (can't remember exactly what the line was, but was something like unable to format...something).
Now when I boot into recovery it displays the following information:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Any idea's? I know there is a lot to find about this on the internet and this forum but they're all guides from other devices and don't know if it would be wise to follow them
Help would be appreciated!
Clockworkmod v4.0.1.4
Eisken said:
Hi there,
I used Cyanogenmod 1.1 beta for a while and while I was pretty happy about it, it did have some issues i wasn't very fond of. So I decided to to perform a nandroid restore of my stock rom and succeeded. My stock rom kept crashing when trying to use internet (synchronising, browsing etc). While messing a little with the settings (like no account syncing etc) my phone crashed and it went into an infinite bootloop. I went into recovery, did the neccesary wipes and performed a nandroid recovery to my Cyanogenmod again. It errored while doing so (can't remember exactly what the line was, but was something like unable to format...something).
Now when I boot into recovery it displays the following information:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Any idea's? I know there is a lot to find about this on the internet and this forum but they're all guides from other devices and don't know if it would be wise to follow them
Help would be appreciated!
Clockworkmod v4.0.1.4
Click to expand...
Click to collapse
What happens when you attempt to enter RECOVERY and format CACHE?
Did you at any point in this boot loop process pull the battery?
ben_pyett said:
What happens when you attempt to enter RECOVERY and format CACHE?
Did you at any point in this boot loop process pull the battery?
Click to expand...
Click to collapse
When doing cache wipe:
Formatting /cache...
Cache wipe complete.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I did not pull the battery out except for the infinite bootloop I mentioned earlier.
Eisken said:
When doing cache wipe:
Formatting /cache...
Cache wipe complete.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I did not pull the battery out except for the infinite bootloop I mentioned earlier.
Click to expand...
Click to collapse
Sorry, I'm afraid that I must be the bearer of bad news ....I believe that by pulling out the battery you have ruined the eMMC chip in the device, this appears to be a flaw or defect with a selection of recent HTC devices.
I believe that the only thing you can do is to return the device for warranty or to attempt to get the chip replaced.
Here are a selection of similar threads, within this forum which also cover this problem and I believe that you should be able to find others......
http://forum.xda-developers.com/showthread.php?t=1165304
http://forum.xda-developers.com/showthread.php?t=1150917
http://forum.xda-developers.com/showthread.php?t=1226849
Thanks for your reply!
Too bad there is nothing to do about it. I'll just send it in for repair then.
having the same problem.. so should i try to wipe the cache and see what happens?
I fixed that by going into recovery and wiping the cache. It still says that it is unable to mount but re-flashing the ROM fixed all that.
I've tried that quite a few times, but it always failed to flash the rom. Did you get errors when flashing the rom?
What errors do you get when you're installing the ROM?
If you are still able to go into recovery then....
Do you have EXT4 recovery installed?
If not 1) Download this FILE which is EXT4 recovery 2) then copy it onto your SD card 3) enter recovery and flash the EXT4 ZIP file 4) Reboot Recovery
Then look at what format the existing CACHE partition is in?
OK i seem to be the next one with this Problem.
But for now it isn't a real problem, the following happended:
Used Hydrogen for some weeks, but wanted to try the new Virtuous Unity. So i did a backup of my apps with titanium, booted into recovery, flashed the Virtuous Rom, Install was complete and after that it says the known E: cant't mount ... and so on.
After that i pressed restart now in ext4 recovery and the Rom booted as it should. I restored my apps, everything is ok. But now i'm a little scared what will happen next
So is this the normal "way" it goes, or did i just have luck? I'm thinking about going back to s-on and stock, if this is possible.
Btw i didn't pull out the battery ever, cause i knew this could brick my ds, and i never had a bootloop or something like that.
Hope someone can give me some tips.
Cheers
EbiEre said:
OK i seem to be the next one with this Problem.
But for now it isn't a real problem, the following happended:
Used Hydrogen for some weeks, but wanted to try the new Virtuous Unity. So i did a backup of my apps with titanium, booted into recovery, flashed the Virtuous Rom, Install was complete and after that it says the known E: cant't mount ... and so on.
After that i pressed restart now in ext4 recovery and the Rom booted as it should. I restored my apps, everything is ok. But now i'm a little scared what will happen next
So is this the normal "way" it goes, or did i just have luck? I'm thinking about going back to s-on and stock, if this is possible.
Btw i didn't pull out the battery ever, cause i knew this could brick my ds, and i never had a bootloop or something like that.
Hope someone can give me some tips.
Cheers
Click to expand...
Click to collapse
The good news here is that you recovered from this problem and also that you didn't pull battery, so we can rule that out as being the cause in your case.
Between the Installation/flashing of the second ROM did you perform the necessary WIPES?
You may well have done, but, just in case, I'd always recommend that you take a full Nandroid backup of an existing system ROM before moving and flashing another (just to have a fall back position in case)?
@ EbiEre
I got scared after reading those lines too. Nothing to worry about. Just keep flashing roms as usual . Just a cache error. If you didnt pull out the battery, and if the rom booted, then everything is ok.
Yeah but I'm scared because I think it could brick "really".
I don't think it is sure that it only happen if i pull out the battery isn't it?
For now I'm back at the stock tom, it's OK but to be honest I love to root my phone and flash rims, and so maybe I will root again
Thx for your answers
EbiEre said:
Yeah but I'm scared because I think it could brick "really".
I don't think it is sure that it only happen if i pull out the battery isn't it?
For now I'm back at the stock tom, it's OK but to be honest I love to root my phone and flash rims, and so maybe I will root again
Thx for your answers
Click to expand...
Click to collapse
Can only echo the comments of @.sh4d0w.
We all take a minor risk of bricking our devices with the majority of commands and flashes that we do.....but we still do them because that's half the fun...
Did you ever examine the format types ie EXT3/EXT4 of each partition using the EXT4 recovery?
Hey all:
While I consider myself quite technologically inclined, it appears that what I think and what reality is are quite different things. Thus, I look for advice from this wonderfully adept community (I've surfed around quite a bit, but I've never had to ask anything).
Here are my phone's specs:
Model: i9020A
Carrier: Koodo
The short story:
because, currently, there's only ICS for the GSM version of the phone, I thought I'd try flashing the GSM version of ICS onto my phone, then load the radio settings for my phone type so that it would work. It didn't. I was able to load ICS, and it worked great; the radio settings for the i9020A, however, didn't load up. As a result, I tried to reload the stock 2.3.6 onto the phone, and I seemed to have failed miserably.
I'm now at the following point:
Normal boot: only loads to the Google screen (with the padlock)
Fastboot Mode: here's the information.
Product Name - HERRING
HW Version - REV 16
Bootloader Version: I9020XXKL1
Baseband Version: I9020XXKI1
Carrier Info: ATT
Serial Number: 3935CEB394BE00EC
Lock State: Unlocked
When I select "Recovery," it briefly goes to the Google screen (with the unlocked padlock at the bottom), then loads into ClockworkMod Recovery v3.0.0.0
Here are the below options:
- reboot system now
- apply update from sdcard
- wipe data/factory reset
- wipe cache partition
- install zip from sd card
- backup and restore
- mounts and storage
- advanced
- GO BACK
Below these options is the following information:
ClockworkMod Recovery v3.0.0.0
E: Can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/command
E: Can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't find misc
E: failed to find "cache" partition to mount at "/cache"
Essentially, what I am asking is if there is anyway to load the original 2.3.6 for the i9020A on here. If I'm able, then I'll patiently wait for the ICS OTA.
Any help that anyone can provide would be immensely appreciated. If there's any other information I can provide, such as pictures, I'd be more than happy to provide that.
Thanks so much.
rcm8 said:
Hey all:
While I consider myself quite technologically inclined, it appears that what I think and what reality is are quite different things. Thus, I look for advice from this wonderfully adept community (I've surfed around quite a bit, but I've never had to ask anything).
Here are my phone's specs:
Model: i9020A
Carrier: Koodo
The short story:
because, currently, there's only ICS for the GSM version of the phone, I thought I'd try flashing the GSM version of ICS onto my phone, then load the radio settings for my phone type so that it would work. It didn't. I was able to load ICS, and it worked great; the radio settings for the i9020A, however, didn't load up. As a result, I tried to reload the stock 2.3.6 onto the phone, and I seemed to have failed miserably.
I'm now at the following point:
Normal boot: only loads to the Google screen (with the padlock)
Fastboot Mode: here's the information.
Product Name - HERRING
HW Version - REV 16
Bootloader Version: I9020XXKL1
Baseband Version: I9020XXKI1
Carrier Info: ATT
Serial Number: 3935CEB394BE00EC
Lock State: Unlocked
When I select "Recovery," it briefly goes to the Google screen (with the unlocked padlock at the bottom), then loads into ClockworkMod Recovery v3.0.0.0
Here are the below options:
- reboot system now
- apply update from sdcard
- wipe data/factory reset
- wipe cache partition
- install zip from sd card
- backup and restore
- mounts and storage
- advanced
- GO BACK
Below these options is the following information:
ClockworkMod Recovery v3.0.0.0
E: Can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/command
E: Can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't find misc
E: failed to find "cache" partition to mount at "/cache"
Essentially, what I am asking is if there is anyway to load the original 2.3.6 for the i9020A on here. If I'm able, then I'll patiently wait for the ICS OTA.
Any help that anyone can provide would be immensely appreciated. Thank you all kindly in advance.
Click to expand...
Click to collapse
Do you have a backup that you can restore? If not, grab the 2.3.6 update from here http://forum.xda-developers.com/showthread.php?t=1063664 and try a flesh install.
You should also flash a new radio, I didn't have any luck with the KI1 radio on my i9020a.
Not saying this will help at all but have you tried the latest version of clockwork mod your version seems to be very old. Try this one and see if it helps Clockwork 5.0.2.3
Thanks a ton for this. I'm a bit of a noob with this, so any other information, i.e., how to flash it properly, would be super helpful.
Again, thanks a bunch for the reply!
rcm8 said:
Thanks a ton for this. I'm a bit of a noob with this, so any other information, i.e., how to flash it properly, would be super helpful.
Again, thanks a bunch for the reply!
Click to expand...
Click to collapse
Download this LINK put it on your internal sd card boot up into recovery then do a full wipe in clockwork mod and flash the ROM it contains recovery, radio and bootloader. So you will be back to stock and can follow one of the guides on here to get back onto which every rom you choose.
Will do.
Thanks again!
FeaRThiS said:
Download this LINK put it on your internal sd card boot up into recovery then do a full wipe in clockwork mod and flash the ROM it contains recovery, radio and bootloader. So you will be back to stock and can follow one of the guides on here to get back onto which every rom you choose.
Click to expand...
Click to collapse
Okay, so I've downloaded the file, then put it onto the sd card.
I then boot into Fastboot Mode, then go to Recovery. I do the following here:
- wipe data/factory reset, then "Yes - delete all user data". It says the following:
-- Wiping data. . .
Formatting /data. . .
Formatting /cache. . .
E: format_volume: no MTD partition "cache"
Formatting /sd-ext. . .
Formatting /sdcard/.android_secure. . .
Data wipe complete.
E: failed to find "cache" partition mount at "/cache"
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
I then went into "advance" and "Wipe Dalvik Cache" (which works)
I also did "wipe cache partition," and it says the following:
-- Wiping cache
Formatting /cache
E: format_volume: no MTD partition "cache"
Cache wipe complete.
E: failed to find "cache" partition mount at "/cache"
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
I then went to "install zip from sd card," then "choose zip from sd card," then chose the file that you LINKED to (0b9c8148de0d.signed-sojua-ota-189904.0b9c814)
It says:
-- installing <the above file name>
E: can't find misc
Finding update package
Opening update package
Installing update. . .
then there's a bar, which never fills; it then goes to the following text:
assert failed: write_raw_image ("/tmp/boot.img","boot")
E: Error in /sdcard/<the file name from above>
(Status 7)
Installation aborted.
I'm pretty stuck. Anything else you might have would be fantastic!
Thanks again.
tehgeekguy said:
Do you have a backup that you can restore? If not, grab the 2.3.6 update from here http://forum.xda-developers.com/showthread.php?t=1063664 and try a flesh install.
You should also flash a new radio, I didn't have any luck with the KI1 radio on my i9020a.
Click to expand...
Click to collapse
Yeah, I tried flashing the original 2.3.6 from that page, but there's no luck . . . :S
Thanks for the reply, though! Do you recommend anything else?
rcm8 said:
Yeah, I tried flashing the original 2.3.6 from that page, but there's no luck . . . :S
Thanks for the reply, though! Do you recommend anything else?
Click to expand...
Click to collapse
What do you mean "no luck"? What error did you get? Did you get the right version?
If you're on a i9020A you should be using this one - http://goo.gl/nN0Zp (Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.)
rcm8 said:
Okay, so I've downloaded the file, then put it onto the sd card.
I then boot into Fastboot Mode, then go to Recovery. I do the following here:
- wipe data/factory reset, then "Yes - delete all user data". It says the following:
-- Wiping data. . .
Formatting /data. . .
Formatting /cache. . .
E: format_volume: no MTD partition "cache"
Formatting /sd-ext. . .
Formatting /sdcard/.android_secure. . .
Data wipe complete.
E: failed to find "cache" partition mount at "/cache"
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
I then went into "advance" and "Wipe Dalvik Cache" (which works)
I also did "wipe cache partition," and it says the following:
-- Wiping cache
Formatting /cache
E: format_volume: no MTD partition "cache"
Cache wipe complete.
E: failed to find "cache" partition mount at "/cache"
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
I then went to "install zip from sd card," then "choose zip from sd card," then chose the file that you LINKED to (0b9c8148de0d.signed-sojua-ota-189904.0b9c814)
It says:
-- installing <the above file name>
E: can't find misc
Finding update package
Opening update package
Installing update. . .
then there's a bar, which never fills; it then goes to the following text:
assert failed: write_raw_image ("/tmp/boot.img","boot")
E: Error in /sdcard/<the file name from above>
(Status 7)
Installation aborted.
I'm pretty stuck. Anything else you might have would be fantastic!
Thanks again.
Click to expand...
Click to collapse
Could be wrong but that looks like your partition tables got messed up at some point.
EDIT you could also try looking on here might be helpful LINK
EDIT X2 Other people have screwed up their partition tables and have fixed it using this guide LINK
tehgeekguy is right, if your model number is I9020A then it should work using the rom he linked, did you install Clockwork 5.0.2.3 before trying to install the stock 2.3.6 rom, if not then please try.
Yeah, that's the one I tried, but I received the same error message as before:
-- installing <the above file name>
E: can't find misc
Finding update package
Opening update package
Installing update. . .
then there's a bar, which never fills; it then goes to the following text:
assert failed: write_raw_image ("/tmp/boot.img","boot")
E: Error in /sdcard/<the file name from above>
(Status 7)
Installation aborted.
I'm going to try it one more time to see if I can't get it working. I have a feeling my partitions may have been messed up . . .
Thanks for the reply.
d.chatten said:
tehgeekguy is right, if your model number is I9020A then it should work using the rom he linked, did you install Clockwork 5.0.2.3 before trying to install the stock 2.3.6 rom, if not then please try.
Click to expand...
Click to collapse
Yeah, I'll be sure to try this right away.
Thanks a ton.
FeaRThiS said:
Could be wrong but that looks like your partition tables got messed up at some point.
EDIT you could also try looking on here might be helpful LINK
EDIT X2 Other people have screwed up their partition tables and have fixed it using this guide LINK
Click to expand...
Click to collapse
I'll definitely take a look at this. Thank a bunch!
The partitions is probably right, have you tried with the stock recovery instead of clockwork, worth a try.
d.chatten said:
tehgeekguy is right, if your model number is I9020A then it should work using the rom he linked, did you install Clockwork 5.0.2.3 before trying to install the stock 2.3.6 rom, if not then please try.
Click to expand...
Click to collapse
So, I went to the page and downloaded the following file:
"Option for no confirmation at all. Just flash in recovery.
signed-noconfirm.zip"
I put this onto the sd card, then attempted to install. This is what I received:
"-- Installing: /sdcard/signed-noconfirm.zip
E: Can't find misc
Finding update package . . .
Opening update package . . .
Installing update . . .
Installing .no_confirm
use at your own risk!!
reboot recovery and enjoy!
Install from sdcard complete"
Thus, it seemed to work pretty well. I thus rebooted recovery, but ClockworkMod is still showing that it's version V3.0.0.0.
Should I be flashing one of the other options on that page? If so, which one? And would you, by chance, have a detailed explanation as to how to go about doing that?
Thanks so much. I'm starting to feel like I won't be getting anywhere . . . . The responses have been awesome, though, everyone. I really appreciate it.
You have been trying to install a switch to turn off confirmations, to get Clockwork 5.0.2.3 installed you will need to use the same method as when you installed Clockwork 3.0.0.0 but use this image > 5023-cyan.img.
d.chatten said:
You have been trying to install a switch to turn off confirmations, to get Clockwork 5.0.2.3 installed you will need to use the same method as when you installed Clockwork 3.0.0.0 but use this image > 5023-cyan.img.
Click to expand...
Click to collapse
Makes a lot of sense. I'll try that.
Thanks.
d.chatten said:
You have been trying to install a switch to turn off confirmations, to get Clockwork 5.0.2.3 installed you will need to use the same method as when you installed Clockwork 3.0.0.0 but use this image > 5023-cyan.img.
Click to expand...
Click to collapse
Okay, so I flashed Clockwork 5.0.2.3, then I flashed the correct i9020A package. It worked beautifully.
Thanks a ton, everyone, for all your help. This is great!
Clad it worked for you.
Alright guys, I've got a question. I have my brothers nexus s that has had CM9 A11 on it and we decided to move to the latest CM9. Long story short, I am no longer able to boot the phone up, but can only access CWM Recovery and Bootloader/Fastboot mode. Trying to boot results in a bootloop. I need help getting this thing back to stock however I can. I've tried to flash recovery.img via fastboot but cannot get my computer to recognize the phone in order to do what I need. He would like his phone back ASAP and I hate to tell him its bricked for a few days. Thanks!
Download full OTA ROM from the link in my signature. Boot into CWM, mount USB storage, and transfer the file to SD card. Flash it. Done.
Just make sure you download the correct ROM for your phone model.
Sent from my Nexus S using xda premium
Video on that page will show you how to install drivers on a windows-based machine to recognise the phone for fastboot, and provide files to do so.
Also, can't you go into CWM --> mounts and storage --> mount usb storage (while plugged into the computer) then copy over any files you need, then flash through recovery.
I forgot to mention that I am getting this when trying to format cache:
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/command
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/latest_log
E:Can't open /cache/recovery/latest_log
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
I tried to install the OTA update like you said but got the following:
assert failed: write_raw_image("/tmp/boot.img".
"boot")
E:Error in /sdcard/(OTA file name here)
(status 7)
Installation aborted.
Maybe the internal SD card is bad? Any thoughts?
When you get the drivers installed, download the latest 5.0.2.0 CWM from here.
Alright, so I got fastboot to recognize the phone, but am having another problem. It gave me an error when I gave the command to flash the new CWM. I tried to install pdanet for the drivers, and the phone says at the bottom "FASTBOOT STATUS - FAILInvalid Command". I really think something has been corrupted, any ideas on how to fix it/restore it? Thanks for all the help guys.
Fastboot status is not a command.
Fastboot devices is the command you use to test if it sees the device . The serial number will show.
uh oh sounds like someone flashed brickROM V1
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.