Edit #2
Ok so I downloaded stock firmware from sammobile...and that corrected my problem. So I started fresh, by first installing Philz touch cwm...which seems to work fine and I could still at that point boot up normally.
However, upon attempting to flash a couple of different custom Roms(Deleterious and RocketTab), I am left with the same issue ("Since then, when I reboot, it shows the samsung logo, then goes black. Sometimes if I hit the power button, suddenly the screen appears. Sometimes it doesn't.").
Am I missing something? I'm only trying roms that are specifically for the sm-t210r....I've tried using three different recoveries...and I've been flashing roms...tons...since my original galaxy s phone. Simple stuff. So what the heck is going on?
I want a custom rom...lol...grrr Do these roms just not have bootscreens and I'm just being paranoid?
-----------------------------------
Ok so I just got my tablet and started searching for root methods..
I may have gotten a little ahead of myself, and using odin, I used this method:
http://forum.xda-developers.com/showthread.php?t=2391367
Since then, when I reboot, it shows the samsung logo, then goes black. Sometimes if I hit the power button, suddenly the screen appears. Sometimes it doesn't.
I've tried a few different custom roms, using Philz cwm, and even tried using odin to flash a stock rom I found online(in an attempt to see if using odin would help.)
Same issue.
If it goes into the OS, it seems to run fine...but then more often than not when I reboot again the samsung logo appears, then black. Never to return.
I know it's not bricked but I don't know what else to try. Any suggestions would be great.
Im on sm-t210r..
EDIT:
Think this will work?
http://forum.xda-developers.com/showthread.php?t=1840030
If so, how to I find the bootchain files for the sm-t210r? Or maybe the PIT? (from the second post...sounds more like my problem..)
Nevermind...apparently it was a kernel issue..
Sent from my SM-T210 using XDA Premium 4 mobile app
Related
I was flashing the newest cm10 as I do every few days. I flash that, then inverted apps, then kernel, then reboot and never had a problem. Now I am getting a blank screen after the "Samsung Galaxy SIII" splash with the button back-lights lit. Nothing else happens, no response. Never had an issue, but now I am worried. Any help here?
EDIT: I tried booting into recovery a few times with no success. Just tried it again and held all 3 buttons past the recovery flash on the top of the screen. Booted into that and re-flashed the update by itself. Phone just booted back up. Not sure what happened, but all is well in my s3 land again.
Usually not a good idea to flash a ROM and kernel at the same time. I know you said that that's the way you've been doing it buuuut....what happened to your phone is the symptom of your phone trying to match up a ROM and separate kernel at the same time, it got confused while booting lol. Best practice it ROM, gapps, reboot system let phone fully boot, reboot recovery and install kernel. Its an extra step but usually avoids what happened to you.
If your using ktoonsez kernel he has a special build for the latest nightly for people with the same problem as yours, it's not in the op, start from the end of the thread and work backwards.
Sent from my SGH-I747 using Tapatalk 2
I have tried to install [ROM][N7105] AOKP JB 4.2.1 [PUB] [FeB - 5] & the Nightly's on my 7105. It soft bricks every time. It tries to reboot after installing the roms and then flickers twice or so and goes black and has no more activity till I take the battery out and put it back. I have to install the stock rom through Odin to get it going again. I always do a factory reset & wipe cache before I install. What might I do to run custom roms? Thanks in advance for any help.
Hi. I have the same problem on my N7100. I could not install any custom rom. Tried CM 10.1 + gapps ( full wipe and cache wipe before install ) after install and reboot system screen flicks 2 times and goes black without any response. Must return to stock via Odin . Tried several times... result is the same. Before Note 2 used S3 and never had such problems with installing CM10.1. Hope someone will help.
Sent from my GT-N7100 using xda premium
I used my Note i717 and installed rom's on it all the issues as long as I didn't flash the wrong ones.
Any help?
Sent from my GT-N7100 using xda premium
I reckon these phones must be too new for us to get help.
My N2 screen flickers as well, just pressed the sleep button after awhile, and unlock it as usual via home screen.
Hope it works for you too
Your screen flickers after you install custom rom?
Almost every ROM I flash I have issues around booting. Some boot up how they should, but MOST don't...
I flash the rom and then I boot. The Samsung Note 2 screen shows but then flashes all crazy and stuff a couple times and then goes blank. I just wait a while and after a minute or so I start pressing the power button, and the screen will come up as it should on the lock screen or if its a brand new rom it will be at the set up screen.
What helps me to know when it has finished booting, is to connect the phone via USB to my Macbook, and when it is booted the mac will ask me to allow it access to the phone.
Just don't worry too much about it, coz it is ok and will work. Another way to see if it is finished booting is to wave your finger over the menu and back button, and it will light up when the phone has booted; you just have to keep trying to wake up the phone with button presses, but don't go crazy and keep pressing and/or holding buttons
Is there any custom ROM's for the Hong Kong version of the 7105 that I can try since the others won't boot?
I've got a Galaxy Tab P5210 that's stuck in a constant boot loop. I flashed it with the correct stock firmware from SamMobile using Odin, but it fails to boot properly. It automatically boots to the stock recovery screen, but the problem is it will instantly reboot as soon as it reaches this screen. I see the dead android with the red triangle and exclamation point for just a second, and it instantly reboots. Is that normal? I don't think that's normal. From what I've been reading, this screen is supposed to stay there until you push the volume keys to bring up a menu, but it reboots so fast that I don't have a chance to even push anything.
I've tried flashing it with other recovery images. I tried using CWM, and it almost worked. With that, as soon as the tablet booted, I'd see the CWM splash screen, and it would instantly reboot. Similarly to how it's booting now but with stock recovery.
I'd like to point out that I've never messed with anything like this before. I work in a computer/small electronic repair shop and a customer brought it to me. She ended up getting into stock recovery and a friend of hers did some serious damage in there which prevented it from booting properly. Normally we don't mess with things like this but, with it being how it was, I figured there was no way I could make it even worse than it already is by working on it. I thought if I flashed the original stock firmware back to it, it would fix it, but that looks like a no-go since it's still booting the same way it was when she first brought it to me.
Is this thing completely broken or is there still hope for it?
No - it should be recoverable. However - any data will most likely be lost.
When you flash with Odin, make sure only F. Reset Time is checked. Use Odin 3.07. Make sure again that firmware is correct before you flash. After it flashes, power off and then on again
Latest KK firmware for the US version of the 5210 is P5210UEU0CNK1_P5210XAR0CNK1_HOME.TAR
Good luck. If you're trying to root, then there are threads in the 10.1 Dev section that should help
M,
this firmware was always my goto for device recovery/restoration https://www.androidfilehost.com/?fid=23060877490005046
posted by user chpettit , flash with odin 3.07
m
OKAstro said:
No - it should be recoverable. However - any data will most likely be lost.
When you flash with Odin, make sure only F. Reset Time is checked. Use Odin 3.07. Make sure again that firmware is correct before you flash. After it flashes, power off and then on again
Latest KK firmware for the US version of the 5210 is P5210UEU0CNK1_P5210XAR0CNK1_HOME.TAR
Good luck. If you're trying to root, then there are threads in the 10.1 Dev section that should help
Click to expand...
Click to collapse
Not interested in rooting, just wanna get the stock firmware back on. Maintaining data isn't a necessity, the customer just wants it back in working order. I tried using that firmware, but I had Auto-Reboot checked.
EDIT
Yeah, it's still doing the same thing. When I first boot it up post-firmware flash I see an Android with a loading bar underneath it, and then it reboots. When it boots again, I see the same Android and then it suddenly changes to the dead one with the red triangle. Maybe I'm just doing something wrong here with the button presses following the flash?
EDIT2
It looks to me like the stock recovery image is just broken, since the tablet just automatically reboots the instant it attempts to load it up. Flashing a new firmware replaces that though, so I don't know how or why it would even be corrupted. Odin reports no errors, so I don't know what's going on. And every guide I'm reading with fixing bootloops all say "go into stock recovery and clear the cache", but I can't even boot into stock recovery. It's like it's not even there. And I know it's not a power button issue causing it to shut down, I can power the device off fully with it, and it will stay off until I press it again. I'm banging my head against the desk here.
What if you flashed a TWRP recovery in Odin. Then if that's successful, boot into recovery and wipe/format everything except ext SD, Then try the ODIN flash again with filr your stock tar
I'm having the same problem and that didn't work for me. It shows the twrp splash screen and reboots. I'm looking for the .pit file it has to be the recovery partition right?
Sent from my LG-D851 using Tapatalk
Tried everything I could find, so decided it was finally time to come here. I was happily running CM11 for more than a year and saw that CM12 was available. Used the CM app on my phone, did the whole Windows part, the update started, then failed. Now my phones boots and gets to the first screen after, and for hours the arrow spins round and round.
Tried Vol+/Home and Power, the screen flashes something real quick and it reboots. When I try the same with Vol-, I get a screen that says it's downloading, but nothing ever happens. I'd be happy getting the stock Samsung ATT ROM, CM11, anything so the phone would work. I even tried seeing if I cold flash various other ROMS with Odin to no avail. Must have brain damage (exhaustion) because Odin isn't seeing the file it wants in any of the ROMs I've downloaded.
Thanks in advance.
Before flashing anything else, flash back to cm11 and confirm the bootloader currently installed on the phone.
NoteII Randomly stuck in a bootloop with no access to recovery
I looked for two days around the web for fixes to this, tried flashing everything from roms (if i understand it correctly it's like a phone OS), through custom recoveries (the things that show up after the up/home/power button combo) and even a kernel. I know that I honestly shouldn't have done that without the full knowledge of what I did, but at 3AM I didn't think much. I think i even tried using PIT, but it got stuck and didn't go through.
Okay, specifics:
One day I pick up my phone and notice the big white letters - " (...) note II" etc, standard bootloop. Kinda surprising since I didn't do anything to the phone, but It had some problems before like deleting like 4-5 apps randomly once, or an icon or two disappearing. I tried the obvious method of recovery mode and clearing caches and such, but it didn't work:
after the button combination it briefly showed the "teamwin" blue logo of my recovery i used to have for like 2 years, and then it goes black, and the white letters show up again. Only the download mode shows up. Odin detects the phone and when i flashed a stock rom and some recoveries on it, odin said they "passed", but no change ensued, the recovery still showed teamwin's, even after flashing clockwork recovery, or whatever it's called. I basically accomplished nothing, and I need to know what to do specifically to fix the phone, without bricking it even more. can you guys point me in the right direction, or maybe try to diagnose the problem? Thanks.
-no recovery
-recovery flashing doesn't change anything
-download mode works, odin detects the phone
I've got the impression that you're trying to make two steps in one. I suggest to flash firmware through Odin, reboot, setup and then make wipes and factory reset in stock recovery. Then flash the custom recovery through Odin and all should be fine again.
Reminder: Don't flash firmware beneath your current bootloader version.