[Q] Confused about TWRP/ROM's - T-Mobile Samsung Galaxy S6

Ok, this is my first Samsung phone (used mainly LG/HTC phones) I can root and I've gotten TWRP installed but every time I try and install a ROM it will get to the Samsung screen and the Tmo jingle will ring and go into a boot loop. I installed the 5.1 update not knowing that it would be this difficult to flash a darn ROM onto this phone. Once it boot loops I Odin the 5.1 firmware back onto the phone and restart the process. I just need a little help on what ROMS can be installed and a step by
step process on what to/what not to do.
Thanks

Related

Repeating Bootscreen ... need help!

Ok so i rooted my moto droid i just got in and installed ROM Manager. I Dl'ed the newest stable version of the cyanogenmod rom and choose to make a backup and install the new rom. the backup failed and moved on by itself to installing the ROM. after it was done and rebooted the boot logos have just been repeating themselves over and over. It has the "droid" logo that turns into the red eye. Can anyone please help me. I just want a "working" custom moto droid. Thanks
Can you boot into recovery (hold x while you power on)?
I had the same issue and could not get into recovery. I removed the battery from my Droid to turn it off, connected my Droid to my computer, started RSD Lite and re-flashed SP Recovery. I was then able to boot into recovery and reinstall my previous ROM (which you can do if you have a valid backup). That got be back to normal save reinstalling apps.
Some time ago, when I did my first flash process on android I fell on that very problem, and I could fix that flashing again, BUT I think that is very important to do a factory reset before that, so, yes, go to your Open Recovery and clean first your phone, then flash it again and I hope you are done.. good luck

Help! Captivate Boot Loop

All,
I had rooted a Captivate recently for a friend and installed CM7. After about a week, my friend decided to go back to stock. Prior to rooting, I made a backup of his stock rom just in case. I then showed him how to restore via Clockwork if need be. Tonight he came in to work and wanted to restore to stock, now he is stuck with a boot-looping Captivate. Now the phone sits at the AT&T World Phone splash screen. I've tried and tried all night to get the phone in DL mode so that I can use the One-Click ODIN restore but to no avail. I can't seem to get the phone in DL mode no matter what I try. Whenever I attempt, the phone simply reboots to the AT&T splash. Please assist if available.
P.S. When I plug the phone into any USB I get a circle (reminiscent of the Android loading spinner) in the center of the screen.
Assistance is greatly appreciated.
Thanks.
- E.
thats not how clockwork backups work...those are to restore your set up to the way you had it once you flash the rom it was backed up from thats why hes looping. you would odin back to stock THEN restore and it would be like he never flashed anything at all.
build/buy a jig that'll for sure get you int download mode.
Loop
I'm getting that same loop screen. What I did was use odin to restore my captivate back to factory because the 2.2 update wouldn't allow me superuser permission. After it was back to factory I rooted with super one click. It was successful but when i went to reboot the att world screen looped.
Help please
superoneclick works fine on 2.2.........you had no reason to go back to 2.1

[Q] Help! Stuck in Boot Loop

Hey,
I need some help. I got an I9000M the other day and have been doing a lot of reading towards rooting and eventually SIM-unlocking the phone.
Currently, with the chainfire root method by installing that kernel through Odin i expected that I would have had a rooted phone.
However, the flashing process was completed successfully and after it was finished, I was supposed to let my phone reboot but its stuck at the black and white galaxy s screen.
What happened?
Perhaps I installed the wrong kernel?...anyways I have no clue. Please help so I can proceed towards my goal.
*Also if I just flash an original firmware will it start me back at where I was from the beginning? That way I can figure out which CF I should have used...
Just pull the battery, 3 button into download mode (Vol Down+Home+Power) and ODIN flash to stock.
Do a little reading and make sure you have the right version.
BUT BEFORE YOU DO ANY OF THAT, pull the battery and see if it starts up. My phone always gets stuck on home screen after an Odin flash and have to battery pull to get it to load.
alright thanks, i flashed to stock and now i am going to try and figure out exactly which CF will work.

Tried to flash and upgrade a 4.4.2 AT&T SM-G900A using Odin - won't boot now

Hi everyone,
I've had numerous problems with OTA updates with my AT&T SM-G900A since I got it. I'm not in the US anymore and my phone was unlocked, so I thought "hey, how hard could it be" and tried to flash it.
I used the following binaries that were posted here a couple of days ago: http://forum.xda-developers.com/att-galaxy-s5/general/g900aucs4cpa2-odin-files-em-hot-t3372388
I ran them through Odin3 3.09, and got a PASS - but the phone is stuck at the boot logo screen ("Samsung Galaxy S5 Powered by Android" screen).
Download mode still works, but normal booting, recovery booting and safe mode do not.
Any suggestions on what I could do?
EDIT: I used the stock image located here: http://forum.xda-developers.com/showthread.php?t=2714455 to reflash it using Odin again. It seems to have worked, though all sorts of apps were crashing. I've just done a factory reset and am in the process of restoring it, but it seems promising for now. Never trying to update AT&T crap again.
Hey man, are you still having troubles? I just rooted my Sm-G900A, and then decided to use Odin to flash it with the 5.1.1 files. So this is what happened to me:
1: Flashed AP with the 5.1.1 file, passed but stuck at the Samsung Logo- Powered by Android.
2: rebooted into download mode and flashed "BL" or Bootloader with the 5.1.1 file and I got passed that screen. Now I'm waiting for it to optimize my apps.
My guess is after we flash the AP file we then have to flash the bootloader as well. So if you haven't tried that I'd suggest it to see what happens.

Bricked A715F, Can't boot even after clean stock rom flash

my phone suddenly started this problem with the mic and was frozen too
last week my phone was out of battery but when i charged it up and wanted to boot it, it went on bootloop (couldn't access recovery either)
So i kinda wanted to install TWRP (which I did) and tried a new custom rom.
but now even after a clean stock rom flash using Odin, phone wont boot at all. its stuck on samsung logo to Galaxy A71 logo back and forth. any solutions? please.
Thank you
If flashing full stock isn't working, then it could be a dead motherboard

Categories

Resources