Good afternoon
I would like a help with my A30 A305GT it is in infinite loop after a reset when passing the rom through the odin it passes normally and at the end it restarts as if it were going to turn on when entering the part of the installation of the updates it presents an error and soon after going to the screen to erase it is about 5 seconds and restart and does not leave the screen anymore with the samsung logo i am without another cell phone to put some more print when my wife arrives or provide i don't know what else to do i already installed three rons with different binaries and the current rom is the latest binary rom 4 I apologize if the post is in the wrong place and it has been a long time since I entered the forum
thanks in advance
Related
My i9000 gets stuck at the GalaxyS boot logo every time I try to start it.
First it shows the Samsung boot logo, then the logo of my provider (Drei) and then it gets stuck at the S logo. After some time the screen goes off but the phone stays on (the buttons light up when I touch the phone).
I read about others having the same issue but I can't even go into recovery or download mode.I tried several three button combinations but every single one gets to the same result-> the samsung logo shows over and over.
Maybe you know how to fix it?
Thank you.
P.S.: I'm sorry for my bad english.
First you'll need to state what you did to cause that to happen?
nwsk said:
First you'll need to state what you did to cause that to happen?
Click to expand...
Click to collapse
A longer time ago I rooted it and applied the One Click Lag Fix.
Everything worked fine.
But today I installed SGS-Tools from the market, installed the hacked camera and suddenly there was no camera installed at all.
I downloaded a Galaxy S camera apk and tried to install it but it couldn't install it.
Then I installed busybox and wanted to restart the phone but it won't start again.
Hi all,
I use CM12 from MacLaw in combination with TWRP 2.8.1.0 recovery for about 3 weeks now.
Yesterday the phone didn't respond properly, was very very slow and I basically couldn't use the phone. It felt like the CPU was at 100% all the time, so unlocking the phone, calling and so was nearly impossible. A reboot (battery removal) didn't solve it, also the pin code for the sim card came after a few minutes while usually this will come right after starting.
So eventually I did a factory reset from the menu as I did on other occasions just to get rid of this kind of problems.
Well, right after the Samsung s3 mini logo I get the TWRP logo and it will be stuck in there, I see it blinking every few seconds and that's it. When I connect the phone to USB I hear it connecting-disconnecting every few seconds (bing-bong, bong-bing sound).
After a while I flashed TWRP using Odin again, this didn't give any problem but it will still hang in this TWRP loop.
I found some references to this problem but no real solutions. Someone suggested to use ADB but I don't know how to do that, nor could I find a suitable guide on this.
Can anyone help me? Or is it bricked somehow?? I suspect not, download mode is still working.
Thanks for any help!
I feel the need to make this post as I have yet to find anyone else with the exact same issue as me, however here is the details:
I am running a Samsung Galaxy Note 8 SM-N950U from AT&T
Rooted with SamFAIL one month ago without any issues.
Context:
Yesterday when I turned on my phone for no obvious reason it just got stuck into a boot loop (the one where it stays on the Samsung logo forever. Did the obvious steps with no effect.
Afterwards, I tried to follow the SamFAIL root guide from the start to end just to see if it would fix it (I was desperate). Everything went fine, however, when it booted up and whenever it does boot up it starts black then it flashes the recovery mode screen for half a second (I'd post an image, but I am not allowed to, just search up, "recovery mode note 8" and look at the images with the blue background and android mascot), displays some white text on the black screen for perhaps a second, goes black and repeats this. I am able to enter download mode and upload mode, but whenever I try booting into the actual phone this happens.
Strange problem huh? Any hope for me, or do I have a brick now? It's been looping this process for the past 20 minutes now. For now, my plan is to try flashing the stock firmware with Odin. (My internet is slow so it will likely take all day for that file to download.
flash csc in odin. your cache got corrupted
me2151 said:
flash csc in odin. your cache got corrupted
Click to expand...
Click to collapse
Thank you for the response, any suggestion as to where I can get the latest csc for my model?
https://www.androidfilehost.com/?fid=962021903579483124
Okay, that fixed that issue, however now my phone is doing the same thing again but getting stuck on the flashing Samsung logo screen. What now?
EDIT: NEVERMIND, EVERYTHING WORKS NOW. Thank you so much <3
Hi, I am running a Samsung Galaxy Note 8 SM-N950U from Verizon and im currently styck in a boot loop as well. I can still enter download mode and stuff so im trying to flash back to stock firmware to see if thatll help at all. Can someone please help me find the right file to do so, as i dont wanna cause any further issues here lol.
go sammobile / updato - Search there
It has the whole repository of FW for devices
Good afternoon folks, I'm having a very big problem. Yesterday I was using my phone listening to music, I then received a text message in a group text. I went to pull down the notification center but my touch screen wasn't responding. I thought it was a one off but tried to open my phone and nothing was responding to my touch. I then did a reset (vol dnw+power) which restarted the phone but still the touch screen was unresponsive. Reset phone again now here I am in the infinite boot loop. It starts to galaxy note 8 screen and stays for about 30 sec then goes to recovery mode but will lock up and restart this process over again. I've tried to manually boot into recovery mode but it doesn't work. I'm able to boot to download mode where I've tried flashing with stock firmware but after flashing is restart back to the boot loop. Note 8 hasn't been flashed with anything custom before so this thing is a big mystery for me. Any help would be greatful. Thanks in advance
jaydeeem07 said:
Good afternoon folks, I'm having a very big problem. Yesterday I was using my phone listening to music, I then received a text message in a group text. I went to pull down the notification center but my touch screen wasn't responding. I thought it was a one off but tried to open my phone and nothing was responding to my touch. I then did a reset (vol dnw+power) which restarted the phone but still the touch screen was unresponsive. Reset phone again now here I am in the infinite boot loop. It starts to galaxy note 8 screen and stays for about 30 sec then goes to recovery mode but will lock up and restart this process over again. I've tried to manually boot into recovery mode but it doesn't work. I'm able to boot to download mode where I've tried flashing with stock firmware but after flashing is restart back to the boot loop. Note 8 hasn't been flashed with anything custom before so this thing is a big mystery for me. Any help would be greatful. Thanks in advance
Click to expand...
Click to collapse
Make sure you flash the correct firmware for your model. What is SM-950u1 anyway?? You should also use the latest Odin 3.13.1 or higher. Odin lower than that is giving problems with Oreo firmware. Good luck. LJ
Leejay1953 said:
Make sure you flash the correct firmware for your model. What is SM-950u1 anyway?? You should also use the latest Odin 3.13.1 or higher. Odin lower than that is giving problems with Oreo firmware. Good luck. LJ
Click to expand...
Click to collapse
Thanks for your input, sm-n950u1 is the model number according to sam mobile site for the firmware. But found out that phone was still under manu. warranty after registering it on samsungs website. So i shipped it off yesterday so they can get to the bottom of it
Hey, sorry to bother everyone with another bootloop thread by I just can't for the life of me work out if I'm doing something wrong, or my device is more of a dud than usual.
So got the phone yesterday, did some ota updates ended up in a bootloop.
Now at this point my bootloader wasn't unlockable as I hadn't enabled it in developer settings.
By some miracle it managed to boot itself back into the OS after an hour of fiddling and i decided to enable the option in developer settings.
Now I've unlocked the boot loader and got all the flashing related fastboot commands working i've
Flashed a stock image using the miflash tool, seems to succeed but then on reb but once it's done i'm still in a boot loop!
I've been able to boot into twrp a few times (though most of the time I can't and am still in a bootloop)
Tried flashing a custom rom, but I always seem to be in a boot loop after attempting that.
Throughout the last few hours i've also managed to hit the os a couple of times but it seems very easy to accidently put it back in a bootloop.
If anyone has advice of something to try, that would be great.
(was trying stock image version 10.0.9.0, going to try and go back to stock Oreo)
Smtih said:
Hey, sorry to bother everyone with another bootloop thread by I just can't for the life of me work out if I'm doing something wrong, or my device is more of a dud than usual.
So got the phone yesterday, did some ota updates ended up in a bootloop.
Now at this point my bootloader wasn't unlockable as I hadn't enabled it in developer settings.
By some miracle it managed to boot itself back into the OS after an hour of fiddling and i decided to enable the option in developer settings.
Now I've unlocked the boot loader and flashed a stock image using the miflash tool which all seems to go swimmingly, but once it's done i'm still in a boot loop!
Throughout the last few hours i've managed to get into the os a couple of times.
I've been able to boot into twrp a few times (though most of the time I can't)
Tried flashing a custom rom, but I always seem to be in a boot loop after attempting that.
Sometimes it goes to a failed to boot screen, while other times it seems to loop endlessly.
If anyone has advice of something to try, that would be great.
(was trying image version 10.0.9.0, going to try and go back to stock Oreo)
Click to expand...
Click to collapse
Try some custom kernel, or patched boot img
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
NotOverHere said:
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
Click to expand...
Click to collapse
Yeah, A2 have A/B partition and if update is faulty and the phone ends in bootloop, after a few failed boots, it will boot from other partition.
NotOverHere said:
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
Click to expand...
Click to collapse
I think something along these lines is how i managed to get into the phone the first time and enable oem unlocking.
After a lot of playing around I was able to get the phone to boot by flashing the latest Oreo image (9.6.16)
After that tried going to a pie image again from fast-boot image (10.0.8) and once again ended up in a boot loop.
Lastly I flashed a fast-boot image of the latest ota (10.0.10) and managed to boot in.
So phone is at least all working now. Thanks for everyones help. Just hope the next ota doesn't bootloop the phone again.
@NotOverHere: When the phone finally does boot up, do you find it's stable and reboots are fine after that?
Smtih said:
I think something along these lines is how i managed to get into the phone the first time and enable oem unlocking.
After a lot of playing around I was able to get the phone to boot by flashing the latest Oreo image (9.6.16)
After that tried going to a pie image again from fast-boot image (10.0.8) and once again ended up in a boot loop.
Lastly I flashed a fast-boot image of the latest ota (10.0.10) and managed to boot in.
So phone is at least all working now. Thanks for everyones help. Just hope the next ota doesn't bootloop the phone again.
@NotOverHere: When the phone finally does boot up, do you find it's stable and reboots are fine after that?
Click to expand...
Click to collapse
Plss post the link of 10.0.10