background info: I installed the froyo that was leaked a few months ago. it wasnt stable so I went back to JH6. The problems started when i tried to update OTA to JH7.
Issue: so i've tried this many times. first, i go to settings, software update, then i select "check for update". it goes through the communication process then i downloaded some file. then the phone tells me it needs to be rebooted, so i let it reboot. as it reboots a white screen pops out and a status bar that reads "installing" reaches 50% then it says that the installation failed. the phone reboots and when the phone gets to the home screen a message comes on that says the "update was not applied".
could anyone help me with this? it happens everytime. ive master cleared, flashed over and over with odin. it doesnt work. plus my gps and google nav doesnt work. it continuously reads "searching gps". please help. thanks.
Use search, look for Kies Mini.
Sent from my Craptivate with the leaky rom
ive tried that too. when i plug in my phone Kies force closes on my computer...i followed every step on the website suggested by the att folks and still didnt work.
There is a stock jh7 zip you can apply in recovery in development forum.
newter55 said:
There is a stock jh7 zip you can apply in recovery in development forum.
Click to expand...
Click to collapse
+1. Flash the stock JH7 Design Gears posted and flash it with clockwork mod.
Related
To start, I was using I9000XXJP2 firmware on an unlocked samsung I9000 from Bell. I installed a lagfix a few days ago and everything was working fine. The phone was really slow and freezing a lot today so I decided to restart. Ever since then, the phone is stuck on the Samsung S screen (not the one with the triangle). I can get into download mode just fine and i tried reflashing XXJP2 using odin back onto the phone. Odin does everything fine up until i see a blue 'reset' on odin and the phone is in recover mode with the options asking for me to restart the system etc. I restored to factory settings from there and even cleared the cache and restarted but it is still stuck on that "S" screen at startup. Odin only says "pass" once the phone is disconnected. So as of yet I haven't been able to flash a working ROM back on the phone. If you have any ideas as to which ROM i should try, if you could place a link with that, I would be very grateful.
I've had this problem myself a couple of times (just happened today in fact).
Boot into recovery mode (vol-up, home & power). Do you see any error messages in yellow under the menu?
I was unsuccessful at reflashing any of the Froyo firmwares so I reverted back to the last official 2.1 firmware from Bell JH2. Since I was coming from a 512 pit firmware, I didn't repartition or specify a pit file. This ended up working for me. I've since flashed to JK3 and am about to go back to JPU.
Reply:
I actually do see an error message E:can't mount /dev/block/mmcblk0p1, Can't mount SD card.
I should mention that Im using the unlocked bell phone on fido. Will i lose the unlock if i downgrade? Also, if you could point me to the site where i can download bell firmware, that would be awesome. I went to samfirmware.com and they dont have canadian versions there.
Unless one of the pros comes by and says otherwise, I understand that's the error indicating internal sdcard issues.
However... if the thing is dead, you can't hurt it more by trying some fixes
You can get the official and unofficial Bell firmwares from samfirmware.com, you just have to look in the US section. You want the firmwares starting with "i9000UG". Here's direct download links for you:
JH2 (official 2.1)
http://www.multiupload.com/ZNBT2RY5Y0
JK3 (unofficial 2.2)
http://www.multiupload.com/WTZGSKJGPF
JK4 (official 2.2)
I've heard people flashing this via CWM but I haven't see the files.
Also, I've seen references to people saying their phones begin working again after this error msg after they've left the battery hour for hours.
Let us know how things go.
Reply:
No go. When i flash to 2.1, it just shows the "S" screen and turns off. When i flash to 2.2, does the same thing as my first post. I still can get to the download screen through all of this so I hope its not messed up too bad.
I tried several times this afternoon before it worked including clearing data/cache.
Although, I had a different error message so you might be SOL in the end.
called samsung
So I called samsung this morning and they basically said they won't repair it because Bell handles repairs. Since I dont have a bell account, I can't get it repaired. I keep reading on forums that if you can get into the download mode, if you see the battery icon when you plug the phone in, its not totally bricked so i still have hope yet everything I've tried doesn't work. I tried to adb into the phone in recovery mode and it detects it but says I dont have permissions to push files onto the phone. If anyone can tell me what possibly went wrong and if it is fixable, how, that'd be awesome because right now this is a very expensive paperweight.
mkay o i'm kind of new to android and tonight i wet my pants cause i thoughy i bricked the optimus. I wanted to install CM7 but something went horribly wrong.
After I rooted and installed ROM manager I copied CM7 to my SD and installed. After it was done the CM7 boot screen kept looping. No way the phone was doing anything more than that.
The only other thing it would do was to sho a 'waiting for update' screen. After a lot of searching I mangaged to get stock ROM back by using smartflash, praise be...
Now that I know I can rescue the phone I'd like to know what whent wrong..any clues? Did I use the wrong build of CM7? I just used the latest of the 4th of july.
I want to try again but maybe some insight would be helpful, thanks...
Did you remember to tick the wipe data box in ROM Manager?
Well it would not install from rom
Manager (installation canceled by itself and ennded up with fresh install of LG rom...) so after that i did it from recovery. cant remember if i got the option to wjpe in there...
So when i installed from ROM manager i did xheck the wipe boxes. Then started installing from SD. The installation stopped, i have seen some sort of warning exclamation but i could not read what was wrong the message disappeared too fast. I think the 'wipe' was sucssesful though because all my apps and settings for stock LG firmaware were back to factory.
Ah ha.
ROM Manager and the stock ROM don't get on too well. Boot to recovery, wipe and install from there.
Assume you are using CWM recovery? It has the option to wipe on there if you look carefully so you can wipe it manually before flashing.
I tried again and it seems GB is now running cause I can see the battery icon on a different angle but it keeps givin me LG installation error messages after boot which i may ' forrxe close' but basicly nothing happens. Did i forget to wipe somerhing or forget to do smth else?
What recovery are you using? If it's 4.0.0.5, you might want to update to the newest 4.0.0.5, as the original one I built had some problems formatting.
The error messagel all seem to refer to LG apps or services. Device wont go beyond these messages.
I know, if it's what I'm thinking, they will have been left behind during the CM install, which shouldn't happen.
Ok so what do you think i should do? thanks for the snappy replies rusty.
Fyi, behind the error messages i can see a black background. The top bar with battery indicator is present, it charging. Signal indicator is there but has no signal.
Change recovery and flash again, either to 3.2.0.0 or the newest 4.0.0.5
this is what it looks like now. When i switch off and do volume down+ power its says waiting for S/W upgrade.
First i need to re-install syock again i guess? Wont do much else..
If you're getting software upgrade, you're letting go of power to early, keep em both held.
Edit: Or use 'adb reboot recovery'
hmkay im in recovery now thanks for that. It says 3.0.2.8
Signarure check enabled
Signature check disabled
Script asserts eneabled
Im not quite sure what you want me to do now. Thanks for your patience
Oh, 3.0.2.8 shouldn't have had any problems then, annoying.
Still, pik the wipe data/cache option, then install CM7
Im there thanks so much Rusty.
So, I was running CM7 no problems. Then one day the ax just fell. I tried re-flashing the ROM and it hangs on the boot animation...so, I removed CWM, made a bootable CWM SD and flashed a few different "return to Stock.zips." One finally worked, but when I connect to Wifi, it says it can't connect and shows that my device doesn't have a serial number or a model number, so I can't get beyond that screen, and it is on version 1.0.1. So I tried using the CWM SD again to update the Firmware. When I did that as soon as I turned on the device, it locked up on a screen that says, "Install Failed, please power Off and the Back on again." So I tried completely wiping and re-installing CM7 to eMMc, and now, again it just hangs on the boot screen.
Oh, and 8 boot interruptions doesn't work for me and when I try holding the power +N keys I go directly into the "Install failed please press off and power back on to try again," screen.
My head is going to explode. Please help. I think my next attempt is going to be trying to flash an alternate kernel.
Use this .zip to get full stock 1.3: http://dl.dropbox.com/u/30572895/Nook_Color/update-nc-stock-1.3.zip
patruns said:
Use this .zip to get full stock 1.3: http://dl.dropbox.com/u/30572895/Nook_Color/update-nc-stock-1.3.zip
Click to expand...
Click to collapse
Hey I tried this, and when I flash the .zip, as soon as the device powers on it goes straight into the "install failed please turn off device and the turn back on to try again," dialog. On this screen it is black with a white stenciling of the NC. I have grown to despise this screen.
Also, anytime I have tried to factory reset, it goes directly into the install failed screen.
I have managed to get into the stock 1.0.1 homescreen by bypassing the Out of Box Experience, and even when I try to Erase/Deregister there, it stops and says device not registered, and therefore it cannot wipe. Also, when I check device info, every single one has red 000000000.
I suppose that since I'm at least to the homescreens I could try ADB, because it wasn't working either the last two nights.
Also is there anything in the LOST.DIR that could help? What the hell is a LOST.DIR?
So, another interesting thing here...whenever I go to install ADB the softkeys show up in the status bar, like its already rooted and running the stock 1.0.1 launcher bar, as soon as I unplug the USB, they disappear, so I can't even enable debugging.
Also, the NC isn't showing up on the ADB device list.
I was already running 4.1.2 on my German GT-N7000 (installed also from an OTA update). All my previous software updates went
fairly eventless and ok.
So a few days ago, my phone prompted me for another software update. I let it download the update, and
when that was done it said 'stability updates'.
When I applied the update, the phone of course rebooted, and then the familiar green andoid mascot
started showing, with the turning code in its belly. I span for a few seconds, and
then it started doing that over and over, the screen goes blank, the androidn mascot reappears, the
cor spins for about a second with the progress bar filling up in the same tine, and then the screen blanks again, and
the same this shows again. This has now been going on for nearly half an hour, with no change.
I have made a quick video of the screen
https://dl.dropboxusercontent.com/u/39837205/androidOTAupdate/Resources/androidOTAupdate - Wi-Fi.m4v
There is no indication what it is in fact doing (whether it is updateing different files etc, or whether it always fails
on the same one and is stuck).
I see no way out of this.
What can I do?
I have a MAc only, no PC and have never used KIES or such..
HELP
Kies also does not detect this phone in this state now. horrors.
sejtam said:
Kies also does not detect this phone in this state now. horrors.
Click to expand...
Click to collapse
seems like it has failed. Try to see if you can get into download mode and if yes then open PC odin and see if it detects the phone. If it does not then try to uninstall kies and install latest samsung drivers or kies again and flash JB for your country again.
Edit: before you enter download mode, try to see if you can get into recovery mode and if you are on stock recovery flash philz kernel and do the wipes before you flash JB
Running a Captivate that I rooted and upgraded to 2.3 over a year ago. All was working well. This week it began freezing after it fully loaded after a reboot or power-on. It will go through the ATT, the Corn logo, and the S animation. It will scan the USB storage devides (internal and external) and then quietly freeze. It will sit there with the wallpaper moving around, but the first key stroke done after all has been loaded up will cause everything to freeze.
While it is starting up, I can enter my passcode, use all of the menu buttons and get to applications or settings. However, once the scanning is done, wherever I am will freeze. I can get all the way through the perform a factory reset procedure before the scanning is done, but it I will run out of time before the phone can start the reset.
Seems like something in 2.3 got corrupted and I need to reload the software without going through the boot-up (I went through Kies, but once the phone booted up, it disappeared from Kies and it told me the phone was disconnected).
Any step by step to either repair 2.3 or to install another droid system prior to the phone booting up? I'd appreciate the help.
ktvanhorne said:
Running a Captivate that I rooted and upgraded to 2.3 over a year ago. All was working well. This week it began freezing after it fully loaded after a reboot or power-on. It will go through the ATT, the Corn logo, and the S animation. It will scan the USB storage devides (internal and external) and then quietly freeze. It will sit there with the wallpaper moving around, but the first key stroke done after all has been loaded up will cause everything to freeze.
While it is starting up, I can enter my passcode, use all of the menu buttons and get to applications or settings. However, once the scanning is done, wherever I am will freeze. I can get all the way through the perform a factory reset procedure before the scanning is done, but it I will run out of time before the phone can start the reset.
Seems like something in 2.3 got corrupted and I need to reload the software without going through the boot-up (I went through Kies, but once the phone booted up, it disappeared from Kies and it told me the phone was disconnected).
Any step by step to either repair 2.3 or to install another droid system prior to the phone booting up? I'd appreciate the help.
Click to expand...
Click to collapse
You could grab Odin KK4 without bootloaders and flash it in download mode.
From there, use Odin 1.87 to flash Corn kernel if you wanna be rooted and have a custom recovery again.
Then it's your choice whether you wanna stay on 2.3 or look into 4.2 ROMs.
BWolf56 said:
You could grab Odin KK4 without bootloaders and flash it in download mode.
From there, use Odin 1.87 to flash Corn kernel if you wanna be rooted and have a custom recovery again.
Then it's your choice whether you wanna stay on 2.3 or look into 4.2 ROMs.
Click to expand...
Click to collapse
So, do you agree with me that it seems to be a software issue? Or is this something to try and see if all goes well with the new install? I have no problem if this is something to try since nothing else is working, but I am just curious if my diagnosis is correct.
Thanks for the quick respond.
KT
ktvanhorne said:
So, do you agree with me that it seems to be a software issue? Or is this something to try and see if all goes well with the new install? I have no problem if this is something to try since nothing else is working, but I am just curious if my diagnosis is correct.
Thanks for the quick respond.
KT
Click to expand...
Click to collapse
My guess is that something got corrupted, so yes, software issue. Find the required Odin and 2.3 kernel for the I9000 and flash them in download mode. It should run fine after that.
Got things resolved
Thanks for the help. I tried to follow your steps, but I could never get the phone connected to the PC. It would charge, but not connect to let Odin in. (It will connect to another PC without issues. I uninstalled and reinstalled the drivers, but no dice). However, in the process of putting the phone into download mode and rebooting it back somehow got me into the recovery screen. I did a factory reset through there and it worked.
Thanks for the help of all the contributers to the site.
K