I've really done it this time!
I was playing around installing a few different ROMs on my Nexus S (i9020a) when I noticed that I lost OTA data connection. Okay, maybe I screwed something up in the ROM. I booted into CWM and wiped data/factory reset, wiped cache partition, wiped Dalvik cache. Then formatted /system /cache /data /boot.
Then I installed a different ROM and the phone booted up fine, but still no data connection. At this point, I noticed when I turned on the wifi and connected to an access point, the signal power bars would turn blue (what I expect when I get a data connection). So I turned off wifi and the blue bars went away. All I had was grey bars and I could send and receive calls only.
I repeated the process to install yet another ROM, but this time noticed the radio wasn't on at all. No phone, no data.
Then I wiped the entire phone clean and copied a stock ROM to the phone. When i tried to install I got the dreaded "Installing update...
script aborted: assert failed...yada yada... E:Error in /sdcard/i9020a-stock.zip (Status 7) Installation aborted."
Now if I try to install any ROM, that's all I get. I've been reading, but nothing really explains my situation. I know I'm not bricked because I do get stuff on screen.
I know I'm I'm a knob for doing this, but can anyone shine a light on this for me?
try updating to latest cwm recovery
nexus s http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-crespo.img
fastboot flash recovery image
[Q] Not able to install ANY ROMs - SOLVED
Thank you so much sean for pointing out my massive brain fart. Worked like a charm.
I should have tried that hours ago!
You da man!!
helgansven said:
Thank you so much sean for pointing out my massive brain fart. Worked like a charm.
I should have tried that hours ago!
You da man!!
Click to expand...
Click to collapse
no problem glad I could help
Earlier tonight I was on Valhalla Final Lightning Zapped. After using titanium backup to integrate some system app updates to rom and adjusting my SD Read Ahead to 4096 I then restarted my phone just to see if any system changed needed to take place because of a needed reboot. But once I rebooted everything kept on crashing and I was instantly bogged with app FC and something about Android Log provider crashed please retry again. Every time I tried to restart the log provider it kept on crashing preventing me from doing anything. So I said let me go back to my lock screen and long press power button to reboot into recovery using advance power menu. So my phone then rebooted into recovery so I tried formatting data, cache and dalvik and reflash my back up of Valhalla Final but when I went to do so I kept on receiving a error saying fail to unmount system partition. So I went to advance settings in recover and clicked on show log then after looking at the log it said system read only so I said dammit man .-. Since the partition was no read only I couldn't flash any rooms at all. Even if I did it would just restore the boot image and restart Valhalla final which kept on crashing because of the stupid android log provider. At the time I was away from my computer so I just decided to try flashing a ics. Risky but bleh at this point my options are slim, I flashed cm9 but phone restarted and showed Android logo with some crazy crash image. So I said to myself I wonder if I could access CM9 Recovery. So I took of my battery cover and pull the battery out and reinsert it. 3 button combo my way into cm9 recovery and install a fresh copy of cm9. I figured though the system partition was read only and at the time a BML state if I try to convert it to MTD it should everything should go back to normal. So on I had went with proceeding to flash cm9. Phone booted perfectly luckily I had a nand backup of cm9 before I had downgraded back to GB. I then went back to recovery to wipe everything and restore from backup phone is run completely back to normal now. Does anyone have any insight on this strange fiasco?
Sent from my SGH-T959V using Tapatalk 2
VillaCastana321 said:
Earlier tonight I was on Valhalla Final Lightning Zapped. After using titanium backup to integrate some system app updates to rom and adjusting my SD Read Ahead to 4096 I then restarted my phone just to see if any system changed needed to take place because of a needed reboot. But once I rebooted everything kept on crashing and I was instantly bogged with app FC and something about Android Log provider crashed please retry again. Every time I tried to restart the log provider it kept on crashing preventing me from doing anything. So I said let me go back to my lock screen and long press power button to reboot into recovery using advance power menu. So my phone then rebooted into recovery so I tried formatting data, cache and dalvik and reflash my back up of Valhalla Final but when I went to do so I kept on receiving a error saying fail to unmount system partition. So I went to advance settings in recover and clicked on show log then after looking at the log it said system read only so I said dammit man .-. Since the partition was no read only I couldn't flash any rooms at all. Even if I did it would just restore the boot image and restart Valhalla final which kept on crashing because of the stupid android log provider. At the time I was away from my computer so I just decided to try flashing a ics. Risky but bleh at this point my options are slim, I flashed cm9 but phone restarted and showed Android logo with some crazy crash image. So I said to myself I wonder if I could access CM9 Recovery. So I took of my battery cover and pull the battery out and reinsert it. 3 button combo my way into cm9 recovery and install a fresh copy of cm9. I figured though the system partition was read only and at the time a BML state if I try to convert it to MTD it should everything should go back to normal. So on I had went with proceeding to flash cm9. Phone booted perfectly luckily I had a nand backup of cm9 before I had downgraded back to GB. I then went back to recovery to wipe everything and restore from backup phone is run completely back to normal now. Does anyone have any insight on this strange fiasco?
Sent from my SGH-T959V using Tapatalk 2
Click to expand...
Click to collapse
Maybe it all started w/ a bad Valhalla Final or Lightning Zap download, check the md5, also if u r trying to flash ics I would recommend using a one-click first (It just seems like it always works better for me when I do that)... and I assume u know about the kernel version b4 flashing ics, right?
Yeah. Seems like I do have to do a one click. Everytime I go to make a call on pics it just ring once and then automatically hangs up
Sent from my SGH-T959V using xda premium
ya I would try that 1st
(Just wrote a detailed post and when I went to post, it said I wasn't logged in and erased it...will give a quick run down and can supply more detail where needed as I work through fixing my phone)
Stuck on the white htc splash screen is my most recent problem. Sometimes it gets by that but then boots into recovery. I think bananagranola has the solution in their sig to flash a boot.img. and think I'm comfortable with how to do that, just need to find that file (in the ROM zip?)
What led up to this.
Successfully unlocked and flashed to CM7 back in late Jan/early Feb.
Started experiencing random freezing about two weeks ago.
A week later (last weekend) flashed Jellybean (R10). Worked great for a couple hours then started having the same random freezes.
If things froze I'd have to remove the battery and reboot. After a day or two of this though it'd get to the point that even that would leave me on a frozen jellybean boot animation. So I'd go and factory/data reset in CWM Recovery, wipe cache, wipe Dalvik then reflash the ROM. and I'd be good for a little while more.
Tried flashing back to CM7 but Recovery didn't like the file (it has a good MD5 when checked) Had tried my restore point from early Feb before to no avail, so decided this morning to try other restore points from the last few weeks, right before and after switching to JellyBean. They got further, the first step is something with boot then something with system. It failed on the system part. OK...so I wiped and reflashed jellybean again, and now I am to my splash screen freezes.
I should have asked for help much earlier (lesson learned!) but here I am asking now...what's the first step.
Do I test out and see if I hang on the splash screen again. I haven't turned the phone on in about an hour. Worried of screwing it up more.
Thanks all.
TL;DR Believe I'm stuck on splash screen and know solution to that. Have had phone flashed with new ROM with no prob for months, recently freezing, regardless of ROM. Hoping for advice on getting things working again, starting with whether fixing the splash screen thing first is where to start
splash screen issue seems fixed
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
irishpanther said:
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
Click to expand...
Click to collapse
That doesn't sound like an sdcard problem. Are you full wiping?
bananagranola said:
That doesn't sound like an sdcard problem. Are you full wiping?
Click to expand...
Click to collapse
I'm wiping data/factory reset and cache as well as the dalvik cache.
The steps to flashing a ROM by sashank at link mention to format /boot and /system. I didn't specifically do those...but don't see the option for /boot in any menus I've checked.
A week or so ago I was beginning to suspect there was an issue with the memory but I never found the right search terms to find out how to do a memtest if that's what would have found any problems. Yesterday I did come across some discussion of a corrupt partition/bad chips in some HTC devices. I followed the directions there and through adb ran dmesg | grep mmc0 and the output was similar to the 'normal' one given and showed none of the messages they claimed to indicate a bad chip.
I'm not too concerned with any data from the phone...I backed all that up long ago and the rest restores from my google account. So if I getting things running would normally raise concerns of lost data, that's not an issue for me.
Thanks for taking the time to read. I try to be brief...but don't want to leave anything out.
Wanted to update here before trying to start a new thread and clogging up the board. The title of this thread is not up to date though.
I can hboot just fine and boot into recovery just fine. My phone is unlocked and rooted, ENG S-OFF from when I used AAHK quite a while ago.
When trying to navigate from menu to menu in Recovery I will get the following error messages (best I remember from last time I was in there, I've let the phone be for the last 2-3 days now)
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
This doesn't show up at first though, only after I do a Wipe Data/Factory Reset. And if I understand correctly, that wipes /cache so maybe that's causing these errors?
Anyway, after wiping the dalvik cache I can flash a ROM, I've been using Jellytime, I haven't been able to rollback to CM7, not sure why not.
Jellytime will run though...at first! the first couple of boots I can get in and get through registering my google account and have it begin restoring apps if i make that selection. The time I have to work on the phone before it freezes gets shorter and shorter though. I have to remove the battery to get it to reboot. Eventually I am left with the phone hung during the boot animation. I've left it for over an hour before...it's definitely hung there.
So my reading leads me to believe corrupt partitions. I'm not finding a lot on what I should do to reformat and maybe repartition or whatever I may need to do to recover a functioning phone. I don't care about any data on the phone. I just want to get things working again. I ended up getting a new SD card during all this that arrived earlier. If I can get my phone working, I'd prefer to use that from here on out too. I can use the adb in recovery mode just fine if that's necessary to rejigger things to work.
Can anyone help reset my partitions, if that's what this issue seems to be? If not...any ideas?
Thanks.
Recovery and version?
bananagranola said:
Recovery and version?
Click to expand...
Click to collapse
ClockworkMod Recovery v5.0.2.0
Full wipe?
bananagranola said:
Full wipe?
Click to expand...
Click to collapse
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
irishpanther said:
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
Click to expand...
Click to collapse
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
OK, I'll give this a try. The issue with the freezing is why I moved from CM7 though (which had been stable for four months) so it's reproduced itself in different ROMS. I'll post back once I give this a try. Thanks.
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
I gave Android Revolution a shot. During the flash it gave a message which might also be why I wasn't able to flash back to CM7. The MD5 did verify.
Code:
assert failed:write_raw_image("/tmp/boot.img","boot")
When I went to reboot, I ended up in Jellytime. Of course I had to sign back in to google apps and those things were reset from the dalvik wipe. Shortly there after the phone froze.
On reboot I tried a logcat. Didn't get it right from the start (you can send the command during the boot animation if I read correctly) but captured the failure of things. It's back around the 09:02 portion of the log. To my eyes it looks similar to others I've collected. Especially the message
Code:
Fatal signal 7 (SIGBUS)
though I haven't been able to figure out much about that, or identify what it is before that that could give another clue as to what is screwy since that's maybe (Probably?) related to the flashing issues.
Hey, I need some help.
CyanogenMod doesn't mount my sdcard anymore. I mean its mounted but cannot be used (sdcard is in /data/media/0 are the files but there's no /storage/emulated/0). My Recovery is also showing after every operation that its unable to mount 'persistent'. And then my sim is not working and the camera force-closes.
That all started by me dropping my phone - Crack in the glass. So I saw some tutorials on how to switch the screen. Shouldnt be really difficult and just to try I opened the back of the n5 and closed it with not even really touching any of the hardware I closed it. Then I tried to boot from my CyanogenMod so I got my bootanimation and then a **** ton of pop ups telling that probably everything is crashing. Pressed ok, ok, ok and it showed the boot animation again. Same again and again. It didn't even asked to decrypt the phone >.<
So I turned it off and started the recovery (TWRP), which was showing E: Unable to mount 'persistent'. Had no idea what to do and why soooo
- Factory Reset - flashed another version of cm back on
Same ****
- Complete wipe (Backuped my files) - flashed
I got to the GUI but no sdcard mounted
- Tried to flash Stock ROM from Google - Bootloop and of course no recovery
- Another Factory Reset plus cm flash
Same as after the wipe
- Tried another version of TWRP
Same
So what should I do? Did I broke my phone by opening the back?
I hope not so it would be awesome if you could help a kinda noob like me
Hi all, new here. I would appreciate any responses/ideas.
I have an Samsung Galaxy Rush. Here's what happened:
After playing Netflix for a while the sdcard would get full, so I would go into root and delete the cache(as instructed by someone else). One night I fell asleep, woke up the next morning, and decided to just wipe the entire sdcard. Booting into recovery I did just that. Plugged to compuer, ran Odin, pushed the stock tar.. all went well, but then the phone would not boot up. It will only go into recovery.
So I tried this again, except I wiped everything. Cache, dalvik cache, everything(i'm noob, pls don't hate ). Same result.
I should mention that in recovery, I can mount cache, mount this, mount that, but mounting the sdcard won't happen. It just blinks the screen.
I'm thinking either the sdcard is fried. Or it's one of these things I'm not familiar with (boot loop? soft brick?)
Thanks for taking the time to read.