I recently updated my Rooted GS4 to 4.3
I started by downloading the sofftware then when i went to install it, it brought me to Clockwork recovery saying that what i was trying to install was unknown or something but i knew it was the firmware so i accepted it. It all went through installing and was booting up but stayed at the Yellow Sprint screen. for a long time
I read multiple forums looking for what to do, i reset it first by taking out the battery(over 5 times), then i tried it without the sim or sd in. Nothing. I tried wiping the data and cache from CWR still yellow screen. i am about to try restoring it to the stock rom (currently downloading it) but before i wanted to come here for help on how to do it or anything else i can possibily do.
Please help. :crying:
Related
Today i woke up to the new Update for the vibrant. So of course i tried to update it. My phone is rooted if that makes a difference running everything else stock though. I did the one click root or whatever it was. Well i clicked update and sat my phone down as i got ready. Come back its at the boot screen where it says Vibrant and Samsung in white. I figured it was just loading the new files and just taking a little long. Well by the time i got to school it was still like that so i removed the battery so it would not overheat. Replaced the battery booted up and stalled on boot screen again. This time it made the opening music but never transitioned screens. So i took battery out replaced it and went into clockwork and did a nandroid. Reset it same thing happened. Tried that with three of my backups of previous dates. all failed. so i decided to wipe all data of the phone or factory reset. still stuck at boot screen.
If anyone can help me it would be much appreciated. if you need any other information just let me know.
same thing here. i've done all those steps. when i get home, im going to try and update the JI6 update through ODIN. i'll let you know what happens.
Common problem, easy solution..
http://forum.xda-developers.com/showthread.php?t=803492
I think I may have completely bricked my phone as it gets to the "Samsung Galaxy S3" screen and restarts itself. The kicker here is that it will not boot into recovery mode and upon trying it simply shows the "booting into recovery" in the top left and then goes black and resets again.
A bit of backstory:
Following instructions from here (Update Verizon Galaxy S3 I535 with CM10.2 Android 4.3 JB Custom ROM), I attempted to do exactly what was described in that article and everything was running smoothly until the "Warning, content not authorized by verizon has been installed etc" screen came up, which was weird because I had in fact unlocked my bootloader a while back but for whatever reason it seemed to have been knocked out. After going through multiple guides I tried another factory reset with cache / dalvik clear and attempted to install an unlocked bootloader and figured as long as I could get it started it would be a win in the moment, sadly, none of the methods I had found worked and resorted to a guide that directed me to the factory kernel / rom for my phone (SCH - 1535), which I then tried to install using Odin.
After that I figured it had fixed itself as it booted past the "unauthorized content" screen but now simply does what I stated above. Any help is appreciated.
@JDiTo
Here take some time to read this thread. it is most likely your problem has been solve already but as i've said head over this thread and find out.
http://forum.xda-developers.com/showthread.php?t=2344125
Sorry comment was ment for a diff tab
JDiTo said:
I think I may have completely bricked my phone as it gets to the "Samsung Galaxy S3" screen and restarts itself. The kicker here is that it will not boot into recovery mode and upon trying it simply shows the "booting into recovery" in the top left and then goes black and resets again.
A bit of backstory:
Following instructions from here (Update Verizon Galaxy S3 I535 with CM10.2 Android 4.3 JB Custom ROM), I attempted to do exactly what was described in that article and everything was running smoothly until the "Warning, content not authorized by verizon has been installed etc" screen came up, which was weird because I had in fact unlocked my bootloader a while back but for whatever reason it seemed to have been knocked out. After going through multiple guides I tried another factory reset with cache / dalvik clear and attempted to install an unlocked bootloader and figured as long as I could get it started it would be a win in the moment, sadly, none of the methods I had found worked and resorted to a guide that directed me to the factory kernel / rom for my phone (SCH - 1535), which I then tried to install using Odin.
After that I figured it had fixed itself as it booted past the "unauthorized content" screen but now simply does what I stated above. Any help is appreciated.
Click to expand...
Click to collapse
If you really have an i9300 and you've flashed something for an i535 then yes, you've probably bricked it. Try a full stock rom flash via odin, otherwise a repair centre.
If you actually have an i535 then you've posted in the wrong forum, this is only for i9300 -the international model.
Hi all,
I've managed to royally mess up my Galaxy S2, and I could really do with a bit of help! It was running a rooted stock rom.
The problem started when I attempted to install the Orange Signal Booster using instructions from this thread. I think the killer was replacing default.prop in system.
At this point the phone would crash a couple of seconds after the unlock screen appeared. I could get as far as dragging down and clicking settings before the entire thing hangs. I got similar results in safe mode. I also tried wiping cache etc in CWM but to no avail. I'm backed up, so I tried a factory reset, but I'm having a similar issue. The language selection screen appears, I press start and the phone freezes again.
I'd really appreciate some help!
BTW, my phone's USB port doesn't work so I'm looking for a solution that can be done within recovery. This is a separate issue and I believe it is unrelated as I have managed fine for over a year.
With a dead usb port you're pretty much screwed. The best and fail proof solution is to reflash stock rom using odin because it will wipe and reflash all partitions that were used before.
Hi,
I have one hard bricked Galaxy Note Pro 12.1 2014 Version tablet I bricked while loading custom ROM. I mistakenly popped out the external sd card that the rom was installing from. I was having some trouble with battery issues and was thinking a fresh install of the custom rom would fix it.
When the external card popped out while the rom was loading from the screen said it failed. On reboot the screen goes thru Galaxy logo then goes black. I tried installing recovery images and whatnot thru odin. Some would pass some would fail. And on reboot it just goes thru logo then goes black. I could see its on but nothing else. It does accept a charge though.
Its probably completely broken and at a complete loss but I thought maybe there was some chance. I think it might be possible to repartition or something to that affect but thought I'd see what is possible.
FYI: Not under warranty. Knox is tripped. I am willing to provide a $50 reward to whomever can walk me thru a possible fix. Yeah I know, if you help and it works again I could just say it still doesn't work but all I can offer is my word that you will be rewarded if it gets fixed.
Thank you for any positive feedback.
Tom
Solved
Kies was able to fix this problem. I tried odin a recovery tar , everything numerous times, even kies several times, nothing would do it. Also tried odin a stock rom and that helped a tiny bit. After installing stock rom several times (at first it didnt want to and would fail) it finally did go thru on like the 3rd try installed and passed. But then it would only go to samsung logo and lock up. This morning it tried kies again and miraculously it didnt lock up like it did before and install all the way thru. On reboot it went past logo and turned on completely as new. Moral of the story, have faith and dont give up. I almost trashed this thing and was ready to press the buy it now button for a new one but I decided to insanely try again as if some miracle might happen. And sure as sh#t a miracle happened.
Ok, first up I know there are many posts out there about this issue because I've looked at most of them and tried them so please bear with me.
I have a Samsung Galaxy GT-N8010, about 4 years old. I have never rooted or done anything to the firmware in all that time except OTA updates & the occasional factory reset to clean things up.
Couple of months ago it was on, i had been using it and put it down and when i came back it was on the Samsung logo screen and has been ever since.
Since i could get into the download page even though it was already bricked I figured i'd try rooting to see if i could fix the problem. Now possibly i should have attempted to get into recovery mode first but I attempted to install CWM (as per posts here). It appeared to install fine. But no recovery partition, screen blinks and goes back to the logo.
I've tried flashing stock firmware, TWRP, CWM - all 'appear' to install successfully according to ODIN, but nothing changes, still stuck on the logo screen.
So does this sound like a hardware issue or am i missing something? The Tab A 10.1 with s-pen looks great, would be a perfect replacement, but is not available in NL
Thanks guys (& gals)
Darren