Well , first of all this problem started when i was trying to update the table with kies and it got stuck in 66% for hours ,so i decided to boot the tablet and try again but the problem didnt dissapear. After many tries now the kies wont recognize the tablet , it just shows a box saying the device is not answering blah blah reboot , i do it but still it wont recognize it. so i wonder what should i do , i tried installing the pda by odin but it gets stuck too in system =/ and after a while it says that it failed
That should be a lesson for everyone to NEVER use Kies.
And posting that "the device is not answering blah blah" will never get you help. If you want to have your problem solved, post detailed information with what exact steps you performed and what exact errors you get. Take a screenshot, etc. Do your best to help us help you.
You probably boot loop'ed your device, go in CWM mode and do a complete wipe for starters... it will mostly do nothing but worth a try. Then, flash your tablet with a stock vanilla 3.1 ROM which will not allow you anymore to upgrade to TouchWiz unless you use a custom ROM like Starburst or Task560. Personally, I believe that TouchWiz is a pile of garbage... but that is my humble opinion.
well somehow i managed to get it done with odin3 but as fas as i see it looks like with an europe software , cuz when i try to update or logg with my samsung acc and i have to choose a country theres no US lol
Btw what ROM would you suggest and why
Thanks for answering anyways
This problem probably has shown up a lot and usually I would take my time to look around before asking but I'm feeling lazy so here goes:
I recently put in a new-ish ROM (it's am US stock type ROM that I found on here) and all works well except for one thing - the CWM refuses to load. At first I was getting the dead android with the red triangle sticking out and so I decided to use ROM Manager to flash CWM again. Might have been a bad move since I'm still fairly noob-ish but anyhow it didn't work. Now whenever I try to go in it just freezes. If I try manually it shows the RCK box, android box, etc and just stays there. When I try to do it through ROM Manager it stays at the first ASUS logo. Can someone refer me to a guide I could follow or even give me a solution to fix this? I will be very grateful. Thank you in advance.
I recently bought an S4 on eBay, and the phone activated and is working perfectly fine minus one thing: it won't update. The update downloads and starts to install, but about ten seconds into the install the "falling Android" logo appears, indicating that something went wrong. Upon reboot it tells me the software update was unsuccessful.
I don't know if the phone is currently or was previously rooted. Could this have something to do with the failed update? If so, how would I go about getting the phone back to stock? I have previous experience with rooting Android devices, but never anything in the Galaxy family. Also, because this is my girlfriend's phone, it doesn't need to be rooted, only upgraded.
If it has nothing to do with it being rooted, what's the problem here, and how do I fix it?
Sportsmaniac13 said:
I recently bought an S4 on eBay, and the phone activated and is working perfectly fine minus one thing: it won't update. The update downloads and starts to install, but about ten seconds into the install the "falling Android" logo appears, indicating that something went wrong. Upon reboot it tells me the software update was unsuccessful.
I don't know if the phone is currently or was previously rooted. Could this have something to do with the failed update? If so, how would I go about getting the phone back to stock? I have previous experience with rooting Android devices, but never anything in the Galaxy family. Also, because this is my girlfriend's phone, it doesn't need to be rooted, only upgraded.
If it has nothing to do with it being rooted, what's the problem here, and how do I fix it?
Click to expand...
Click to collapse
If you know how to get into download mode, get there and tell me what it says in the upper right hand corner.
If it's been rooted and has a high flash count it might prevent the upgrade.
If there is a custom recovery installed it would prevent it as well. You can check on that by turning the phone off then holding power and volume up until it says REBOOTING RECOVERY in blue letters at the top. Once it boots into recovery see if it's the stock recovery or a custom one.
Skipjacks said:
If you know how to get into download mode, get there and tell me what it says in the upper right hand corner.
If it's been rooted and has a high flash count it might prevent the upgrade.
If there is a custom recovery installed it would prevent it as well. You can check on that by turning the phone off then holding power and volume up until it says REBOOTING RECOVERY in blue letters at the top. Once it boots into recovery see if it's the stock recovery or a custom one.
Click to expand...
Click to collapse
I'm not quite certain what you're referring to when you say "download mode". Do you mean just starting the download of the update?
As for the recovery, it looks stock to me. It's titled "Android system recovery <3e>".
Sportsmaniac13 said:
I'm not quite certain what you're referring to when you say "download mode". Do you mean just starting the download of the update?
As for the recovery, it looks stock to me. It's titled "Android system recovery <3e>".
Click to expand...
Click to collapse
Power off again, hold power and volume DOWN this time until it says ENTERING DOWNLOAD (or something like that).
In the upper left corner there will be a bunch of tiny writing.
Skipjacks said:
Power off again, hold power and volume DOWN this time until it says ENTERING DOWNLOAD (or something like that).
In the upper left corner there will be a bunch of tiny writing.
Click to expand...
Click to collapse
Okay, after doing that the top-left says this:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
Also, I just emailed the guy I bought the phone from, and he informed that that it was indeed rooted, but he flashed it back to stock before selling the phone. He suggested to wipe the cache, but after trying that in recovery the error logo came up again.
Sportsmaniac13 said:
Okay, after doing that the top-left says this:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enable
Also, I just emailed the guy I bought the phone from, and he informed that that it was indeed rooted, but he flashed it back to stock before selling the phone. He suggested to wipe the cache, but after trying that in recovery the error logo came up again.
Click to expand...
Click to collapse
You have the Verizon version of the S4. This is a forum for the international version.
Version may have tweaked the software update to require you to do something else. I think you are best off asking this question in the Verizon S4 forum.
It's not that I don't want to help you, but without knowledge of what Verizon might have done I'm just shooting in the dark. The users on the Verizon forum might have an immediate answer for you as this might be a common problem with a simple fix for all I know.
Here's the link...
http://forum.xda-developers.com/galaxy-s4-verizon/help
Skipjacks said:
You have the Verizon version of the S4. This is a forum for the international version.
Version may have tweaked the software update to require you to do something else. I think you are best off asking this question in the Verizon S4 forum.
It's not that I don't want to help you, but without knowledge of what Verizon might have done I'm just shooting in the dark. The users on the Verizon forum might have an immediate answer for you as this might be a common problem with a simple fix for all I know.
Here's the link...
http://forum.xda-developers.com/galaxy-s4-verizon/help
Click to expand...
Click to collapse
Okay. Thanks for the help anyways, I appreciate it.
Sportsmaniac13 said:
Okay. Thanks for the help anyways, I appreciate it.
Click to expand...
Click to collapse
OK, you've been moved to the Verizon forum.
The OTA failing quickly as you describe usually means that one of the files that the OTA is trying to update has been modified.
What you should do is figure out what build your phone is running (Settings, More, About phone, then look at "Build number").
That will tell you what you need to flash to restore the phone to stock, hopefully with a no-wipe image.
Thanks for all your help guys. I finally solved the issue, so I figured I'd post how I did it in case anyone else runs into something similar.
I actually updated the phone through Verizon Software Upgrade Assistant. I'm assuming that through doing this I flashed the phone back to stock. Once this was over, the phone notified me of another update, and this time everything went smoothly. The phone is now completely stock and completely up-to-date.
So if anyone has a similar problem, give Verizon Software Upgrade Assistant a shot.
Hello! I have tried to get help from here before but then i did not have much info about the programs i used for my phone.
Anyways, I have a LG Optumis 3D (P929). I rooted it as told, Got myself a rom ( i useClockworkmod recovery v6.0.1.9).
Restarted into recovery mod and i did wipe out data/factory resetfollowed by Cache...
Installed this famous-for-not-working-file "XBSA404.ZIP". Not only me who's getting "Installation aborted" whitout any details why.
I have also tried out "ISC 30a" wich is supposed to be the stock rom. This one works to install but nothing happends.
It says it is mounting but as the XBSA404.ZIP once it comes to install it just jumps to complete?
It seems but i dont know if iits supposed to do that? It takes around 2minutes for this to happend..
Since i tried to install a newer version of android into my phone, everything is stuck at the startup logo. "Bricked" i think is the word.
Im new within this but i try to learn. Now i just want it to start and what ever i must do to get it to work again i am happy for any help with it.
I have looked for downloads with any working ROM and on this site all the links seems not to work.
I have done this tutorial via xda forum a several times without any good resaults.
Also.. once i try to start up in recoverymod the phone jumps into my logo and freezes. I press vol- home and power, releasing once the logo appears. Dont know if its me or if its the phone thats not working. No dmg to it what so ever but i have to repeat this a several times before it comes into recovery mod.
Please help!
Did you backed up your phone's ROM?
else, I think you have to find someone that have the same phone as you are and back its ROM then use that back up ROM to your own phone
*fellow people out there correct me if i am wrong, thanks"
Hello
Just received OTA update to MARSHMALLOW. After downloading I did run the install. Various steps run OK including the 156 ( or more) application optimization. New restart up to the lock screen, but then immediate reboot.
Now the phones is stocked in this bootloop.
By pressing volume down and power together I was able to access Fastboot. I tried to enter Recovery mode but I got the Android with "no command" message.
How to proceed to recover my phone?
Thanks
That is Recovery.. that is what it looks like.
The fact you did not know that yet know how to get into Recovery tells me one thing.
You most likely have already used custom stuff on the phone such as TWRP, Root etc.
Then you installed an OTA for Marshmallow which has a new level of security.
I would have started by providing details on what model of phone you have and
what OS you were running before hand and what version of it and if you were rooted or had TWRP installed etc.
Saying.. "i clicks on teh Marshmallows Installs an it's no works"
Is not going give people here much to go on to TRY and help you.
And did you search this forum help section ?
Because the same questions get asked non stop.
So much that most people don't reply to them anymore..
Each guy that has a problem creates his own new topic
so he can have repeated for him the same thing the last 100 guys were told.
Hello
My model is SM4163AD1E1
The phone has never been rooted.
It was running only official ROM received by OTA from manufacturer.
I try to remember which version it was running before ? Probably 5.1
I tried to search on the forum, but I didn't found anything related to the brand new update to 6.0 leading to bootloop !