Samsung Galaxy S Blaze problem: it gets to the Samsung Galaxy screen and the blue line runs across and that's it, nothing further. I can get it into recovery mode, when I do I have five options, only one of which even seems to have a remote chance of working, which is this:
2. apply update from external storage,
I have tried to do several times with this: /update.zip
every time, however, i get this message: finding update package.. opening update package..verifying update package...E:signature verification failed.
Nothing else I do makes any difference at all, just keeps running into the logo screen and hanging.
I hope someone has an idea of how to work around this?
Thanks,
uesay
Related
Last Saturday, I awoke to the OTA Jellybean upgrade on my tab. For some reason it totally screwed up my tab, so I figured best thing to do was remove it and start over. I have tried everything., It is now rooted, but no matter what OS I try to install, it never gets past the "ASUS " splash screen. Though I do notice I get a small blink of "Signature Mismatch" in red letters for about 2 seconds before I get to that part. I have tried many packages from here and ASUS's site to install an OS. I ma too new to the android world to get any further, so I need help!
Thanks in advance!!
I've managed to get myself so confused and flustered I don't even know where to go at this point.
A couple months ago I got tired of waiting for Samsung to send out the 4.1.2 Android update so I grabbed the Odin version and updated it myself.
I like it well enough but I want to try putting CyanogenMod 10.1 on my P6210. I tried everything last night and it's turned into a long chain of things that won't work.
The bottom line seems to be that I can't change the recovery mode - I've tried installing goo.im; no joy. I have tried several versions of CWM - no luck. Every time I get the "signature verification" error if I try from stock Android Recovery; if I try from Odin I just get a big "FAIL" message; I've tried with Heimdall and I just get partition errors.
I've reached a point where I don't know what to do - I'd really like to strip it down to basics but I've definitely reached a point where I'm over my head.
Any help would be hugely appreciated...
I have a Samsung Galaxy S GT-i9000. I've tried to upgrade it to ICS but when I rooted my phone showed that E:\ can't mount "\SD card" or something like this. then I tried to re root my phone but in the middle of the process odin stoped responding and closed suddenly. from that time the "download mood" is not coming. so that I'm stuck with the black screen of death. I've tried a lot of method to get the "download mood" but none of them worked. I've also made up a USB jig so that I can force the Download mood but it didn't worked either. now what should I do right now.
My Karbonn Sparkle V appears to have bricked itself, I don't know why, I don't know how to fix it, and I don't have the money or time to replace it. I turned it off when I was going to a job interview, prior to which it was working fine. Afterwards I tried to turn it back on, and for the last 12 hours I've been fighting to get it working again with no success.
I can get into recovery mode, but nothing more. If allowed to try a normal boot, then it will either stay on the "Karbonn Smart" logo screen forever and ever amen, or it will APPEAR to boot, but once it reaches the lock screen it dies on its arse. The best-case is that the lock screen will stay up for about 3 seconds, then the screen will go black for another 3 seconds, and then we go back to the lock screen and the process repeats. OR, the lock screen comes up, 3 seconds, and then we go back to the bouncing dots loading screen forever and ever amen.
I tried a hard wipe from recovery mode - it's made absolutely no difference.
This is a stock phone which has only ever received the OTA updates; I've never rooted it, I don't have a custom recovery installed, and I've never used ADB before today.
I've downloaded a number of "stock ROMs" for this phone, but none of them actually work for me; it doesn't seem to matter whether I try to install them through Recovery mode\Apply update from ADB, or put them on the SD card and try "Apply update from SD card". For most of them, I get the error "failed to verify whole-file signature" and it won't install; I tried to install the stock file from https://forum.xda-developers.com/crossdevice-dev/android-one-general/ota-links-t3287707 but that doesn't get me much further; The error becomes
"Package expects build thumbprint of 6.0.1/MMB290/2459718:user/release-keys or 6.0.1/MMB29K/2419427:user/release-keys; the device has 6.0.1/MOB31E/3142026:user/release-keys"
Click to expand...
Click to collapse
I have pretty much no idea what I'm doing here; Please help.
Hello all!
This morning my wife tried to turn on her phone (Stock GS7 Edge on Tmobile) after charging overnight- It kept cycling the Galaxy S7 Edge screen. It would then show the Samsung shutdown screen, and then re-load the Galaxy S7 Edge starting screen. It did this probably 10 times or before I went to boot into recovery mode. However, when I tried this it showed the "Recovery Mode..." screen, but then immediately went to the blue "Installing system update" screen. It says here for a second then goes back to the black "Recovery booting...". It does this back and forth at least 5 times, and then if I plug it into something eventually it changes from the system update screen to a blue screen that says "No Command".
Now, if I let it sit on this screen for a minute or so it will actually boot to Recovery mode successfully. I wiped the cache but that did nothing. I checked the logs and nothing immediately weird jumped out at me but I am not 100% sure what I would be looking for as I don't know what caused this issue. The only messages I see worth noting/present some kind of error are:
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata_path: ANDROID_DATA not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
And: error: open_script: could not open /res/recovery.customize.do No Such File or Directory
[failed start]
sales_code=[TMB]
Carrier ID=[EMPTY]
Don't Delete lib .so files
Not sure if these are normal or helpful to anyone reading. I have not yet tried anything with Odin or recovering the stock ROM or factory resetting. I was hoping there was some way to get this thing back on without losing the data but I think we are past that point. However, if anyone has anything I can try before factory resetting that may fix this it would be greatly appreciated!!!
Well. After trying repeatedly it finally decided to break out of the loop and boot normally. Totally bizarre....but I am backing up everything while I still can!
Krieger0311 said:
Well. After trying repeatedly it finally decided to break out of the loop and boot normally. Totally bizarre....but I am backing up everything while I still can!
Click to expand...
Click to collapse
what exactly did you do to "try repeatedly"??
I am stuck in a recovery loop and nothing is working.