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!!
Related
[Q] Installed OTA 4.4 Update on my Rooted HTC One and now it's stuck on "No Command"
Hey All,
I tried searching for a solution to my problem and I couldn't find it. I am hoping you can help me.
I have a T-Mobile HTC one that I rooted and put the Stock Google Edition on back in August of this year. It's worked beautifully. Two nights ago, I received a 4.4 OTA update and I went to install it right away. Sometime during or after installation, the screen went black and was showing the Android guy with his chest open and a ! inside a red rectangle. It said "Error" then "No Command". I rebooted the phone a few times and when nothing changed, I ended up (in a moment of frustration and panic) wiping the cache and the partition and doing a factory reset. Now, I'm still in the same place as when I initially saw the "No Command" screen except 4.4 isn't on my phone anymore due to all the wiping and resets. The computer (mac) won't recognize the phone connection when I connect it to USB.
Is there anything I can do? I don't think T-Mobile would be much of help since I rooted the device.
Thanks in advance for your help.
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
somesortofthing said:
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
Click to expand...
Click to collapse
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
ShapesBlue said:
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
Well, can I somehow get my phone into working order? Because it's as good as bricked right now.
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
Hey, so I just bought a S6 to use Samsung Pay.
Received it today, fist thing I had to do was update it from 5.0.2. So I used the OTA update from t-mobile option (as it offered it as soon as I turned the phone on and connected to Wifi).
I click the "Restart and apply update" when it had finished downloading, set the phone down, browse the internet for a little and notice it was hanging on the Samsung logo.
I try to turn it off and on, nothing works. I try entering recovery mode, won't let me.
So I then download and try manually flashing 5.1.1 through ODIN.
Everything says "PASS" in ODIN, it reboots and gets to the Samsung logo, shows the android robot, says "installing updates" but when the bar reaches about 45% it switches to "erasing" then goes back to getting stuck on the Samsung Logo.
What can I do ? I really don't want to trip knox as Pay is the sole reason I bought this stupid phone, all other Stock ROMS now fail odin and G920TUVU3DOI1_G920TTMB3DOI1_G920TUVU3DOI1_HOME.tar is just doing the Install then erase thing.
ANY AND ALL SUGGESTIONS WELCOME !
You could try this
http://forum.xda-developers.com/showpost.php?p=63289213&postcount=42
Appreciate the link, tried again and again, but still, every time: the phone reboots, then starts with the "installing updates", it blocks at 33% and just switches to saying "erasing" and the progress bar empties ... until it reboots and hangs at the logo.
I'll try and get a video of it, it that helps at all.
alexnader said:
I'll try and get a video of it, it that helps at all.
Click to expand...
Click to collapse
If with smartswitch won't succeed don t even try anything else send back to Samsung they will repair or give you another one because if you modify the Knox the guarantee is avoid they really strict they don't even touch the phone to try to repair
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.