Database Develop

[Q] JB Rom on Galxy i9003 stuck at Boot animation screen

Hi all,
I updated the firmware on my Galaxy S advance i9003 from a 2.3.4 GB version to a customized JB mod using the tutorial at
//androidadvices.com/update-galaxy-sl-i9003-jellybean-411-codename-350-firmware/ . After a reboot yesterday, the android keyboard app stopped working and hence, i followed some steps online to enter the recovery mode and wipe cache and data.
Ever since then, the phone fails to proceed past the Droid X animation screen and is stuck at the same. Tried leaving at this state overnight as wel but it didnt help. The OS just wont complete loading.
Whats worse is that I'm unable to enter the recovery mode too by pressing the Vol up+ down buttons and the power button. Every time i do that the screen is blank and when i release the power button it boots into the Droid X animation thingy.
Any suggestions to recover my phone or is it bricked completely?

No ur phone is not bricked.
If u would brick your device. then
It wouldn't boot up. Nothing would happen if you when u press the power key.
The phone would be compeletly dead..
.
Try to install the official firmware via Odin.
I think you know how to do that.
That might restore your phone
Sent from my GT-S6802 using xda app-developers app

Note 5 Hang.. After Restart - Won't Boot

So this weird thing happened to my 1 month old Galaxy Note 5 with no root or any software modifications to it.
I was using it to send a text message yesterday and all of a sudden the phone hanged, did not restart by itself, the screen and the buttons were not responsive. I was able to restart the phone but it will not go beyond the Galaxy Note 5, powered by Android screen. I can restart the phone with Volume Down + Power but it will not go beyond that point. Holding the power button will not turn it off, so all I can do is restart the phone as well as enter download mode. I cannot enter recovery mode as I cannot switch off the phone. Tried to wait until the battery drained but once plugged in, the screen will automatically go to the Galaxy Note 5 Screen. Also tried pushing the Volume Up, Home and Power buttons before plugging the device in but still will not enter recovery mode.
When I got home, I tried using Smart Switch Initialization to re-flash firmware. Still the same problem.
Tried flashing with Odin 3.10.7 using latest firmware from my region. Firmware flash PASS but the problem is still the same: Cannot go beyond Galaxy Note 5 Screen, Cannot access Recovery Mode
Are there any other solutions that I can employ without tripping off Knox?
Thanks guys!

Did you find a way to fix this

Try wiping Cache in recovery.
If that doesn't work then a factory reset?
It will wipe everything on your device.

This is exactly the same scenario I am facing right now... exactly...

Need some pro help || Not my phone || Full Details

Hi guys and girls, i came here looking for some help.
What has happened?
My friend tried to root his samsung galaxy note 5
By the look of things it hasnt gone to well.
So im sat here trying to resolve the issue
What i think the issue is!
I think he has soft bricked the phone because when i turn it on its just boot logo looping.
Now when i try and do a recovery / download mode i think its a full brick reason being i cannot put it in to recovery or download mode.
What have i done?
Ive tried to put it in recovery mode
Ive tried to turn the phone on
What was my results?
Turning the phone on i got boot logo loop.
Ive held power, volume and home button all together.
Now there is 3 options i have got
[Recovery]
[FastBoot]
[Normal]
When i try to select one of these using the volume button it doesnt work, how ever the phone says {Volume_Up to select. volume_Down is ok.}
Now this is the reson i think it is fully bricked is due to the fact i cannot boot it in any of those options and it wont even run in download mode.
So what kind of information have you guys got for me on how i can fix this issue?
He tried to root the phone yes but he previously rooted plenty of phone, so what can i do and how can i do it?
I hope there is enought information here for you guys but if not ask away

When you try to boot the phone pressing power, volume down and the home button, does it not go into download mode?
Sent from my iPhone using Tapatalk

Mine did the same after gettimg the no signal issue and then i flashed a rom hoping itd fix it but it still got the 30 second or so reboot, never getting out of the initial boot phase and appearing to boot loop at the splash screen. Its hard to get into a download or recovery mode ar that point since its already trying to do so much and times limited by the time it received a recovery mode request it was rebooting. The fix for that issue is letting it bootloop to fully dying, some say without sim card in and in download mode if possible, i think just letting it die will do trick and u can then see if you got the no signal issue if it boots correctly after charging a little

apd said:
When you try to boot the phone pressing power, volume down and the home button, does it not go into download mode?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
No, it doesnt even get to there, last night after 3 hours of playing around with it i managed to get it to a android logo saying no command then 10 mins later i managed to get a list up and then clicked something and it would let me go back so we had to wait for the phone to die and now it wont load back up to where we had it

xZerTza said:
No, it doesnt even get to there, last night after 3 hours of playing around with it i managed to get it to a android logo saying no command then 10 mins later i managed to get a list up and then clicked something and it would let me go back so we had to wait for the phone to die and now it wont load back up to where we had it
Click to expand...
Click to collapse
You finally managed to get the device into factory recovery....you're not bricked it's just frustrating and timing is important...do this...hold vol down+home+pwr for up to 2 mins and see if you don't come to a screen saying press vol up to continue or vol down to cancel, choose to continue and you'll be in download mode, use odin and flash factory firmware
Sent from my SM-N920T using Tapatalk

Samsung Tab S2 BootLoop + FRP Locked

Hello, I am currently in a big problem right now,
My tablet, a Galaxy Tab S2 SM-T719Y is stuck inside a boot loop - the Samsung tab s2 logo appears, but it does not reach the Samsung logo.
I tried to go to recovery mode, but to no avail. So I booted the tab into download mode and tried to install TWRP into it but due to FRP lock, the device did not allow me to download it.
Trying to fix it for school, tried a few FRP unlocking tools, but does not work.
It'd be great if anyone can help me, thanks
This is the Tab S2 8.0", 32GB.

Hi , since no one else helped. Try again download mode. .
If it won't stop looping try vol down+pwr to turn it off
then vol up+home+pwr to turn device on, release buttons when screen turns on, wait after 10 secs recovery will start.
Then you can factory-reset, this will wipe all your stuff too, but hopefully fix it!

bricked?

I was trying to go back to stock after having Lineage installed but it crapped out during the install. The tablet is now stuck on the SAMSUNG logo screen and it seems impossible to do anything to get around it. The only button combo options that work are power+vol down which reboots and power+vol down +home which puts it into download mode. I've tried reloading the stock firmware and twrp using Odin but it always results in the same, the tablet reboots then goes to the standard android update screen, says it's doing an update and then reboots and it's back to the SAMSUNG screen. Nothing I do gets me into recovery and while Odin connects I can't get ADB etc to.
Any suggestions other than throw it in a drawer and forget about it?
TIA

Ok I got further. I left the tablet for the battery to die, then fully charged it, plugged into the PC and then started with the recovery key combo and bingo got the No Command screen then the standard recovery options. Deleted the cache and did a factory delete/reset and it's alive again.