Note 4 N910P rooted- crash followed by phone being stuck on logo - Sprint Galaxy Note 4 Q&A, Help & Troubleshooting

So i got my note 4 sprint variant a few weeks ago. Rooted it using CF auto root, installed twrp 3.1.0 and installed cm13 on it. It ran fine for a few days then out of nowhere it would shut off and when i tried rebooting it, it would get stuck on logo screen, the blue led would just stay on and then nothing. I thought it maybe the rom so i tried a deoxed rom and the same thing happened. 3 more roms later i kept getting the random crash and then not being able to go past the boot screen.
I don't have xposed installed, or magisk. Just plain root. i am forced to make daily backups using twrp just in case my phone blacks out again. Has this problem happened to any of you guys before? Is there a fix or do i have to break the receipt out?

Personally, I've read about issues on CM and lack of SPen features on CM so I didn't try CM.
But when I ran CM on another Samsung S model phone, I did run CM but always wiped internal memory when switching because app data isn't compatible between the two OS platforms.
Did you wipe internal memory? Have you tried modified stock ROMs? UN7 with modset is a well featured ROM based on Note7. And stable too. Currently using Beastmode kernel but there's a kernel being developed for it.
Sent from my SM-N920P using Tapatalk

mrblack92 said:
So i got my note 4 sprint variant a few weeks ago. Rooted it using CF auto root, installed twrp 3.1.0 and installed cm13 on it. It ran fine for a few days then out of nowhere it would shut off and when i tried rebooting it, it would get stuck on logo screen, the blue led would just stay on and then nothing. I thought it maybe the rom so i tried a deoxed rom and the same thing happened. 3 more roms later i kept getting the random crash and then not being able to go past the boot screen.
I don't have xposed installed, or magisk. Just plain root. i am forced to make daily backups using twrp just in case my phone blacks out again. Has this problem happened to any of you guys before? Is there a fix or do i have to break the receipt out?
Click to expand...
Click to collapse
Try Lineage 14.
https://forum.xda-developers.com/showthread.php?p=70508450
Sent from my trltespr using XDA-Developers Legacy app

samep said:
Personally, I've read about issues on CM and lack of SPen features on CM so I didn't try CM.
But when I ran CM on another Samsung S model phone, I did run CM but always wiped internal memory when switching because app data isn't compatible between the two OS platforms.
Did you wipe internal memory? Have you tried modified stock ROMs? UN7 with modset is a well featured ROM based on Note7. And stable too. Currently using Beastmode kernel but there's a kernel being developed for it.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thanks I will give it a try when i get the chance this weekend. It's so strange out of all the devices i've rooted this is the only one to give me this crazyness. Yes always wipe internal, system, cache, and dalvik cache.

Even on stock it gave me the random crash and no boot past the samsung logo. I think it's safe to say that this thing is ****ed lol

mrblack92 said:
Even on stock it gave me the random crash and no boot past the samsung logo. I think it's safe to say that this thing is ****ed lol
Click to expand...
Click to collapse
Though not normal, these non boots on Samsung logo should be corrected by wiping dalvik-cache or factory reset. If not, something may be wrong.
That said, the initial boot after flash to optimize applications can easily take more than 12 minutes. Much longer if many apps are to be optimized. Shorter if factory reset is applied (less user apps to optimize but still has some optimization to do).
Are you familiar with reactivation lock or eMMC failure? When you flash stock tar in Odin, check your phone's display and Odin log for errors. A failed boot may boot to download mode and indicate an eMMC error.
Outside of those issues, I'd say wipe everything but ext sdcard, pull the battery, wait at least 30 seconds while discharging the power circuit with power button press and hold (not too firmly). Reinstall battery and boot directly to download mode and flash the stock tar in Odin using Odin defaults. Let it auto reboot. Note any failures.
Alternately, you can remove the ext sdcard or delete the Android folder on it. A functional phone should boot rather quickly with the wipes and no errors; shouldn't stay at the Samsung logo very long but still needs to initialize and find network and start the auto start apps. But prior to initial boot, you should also see it make a brief stop in stock recovery to initialize csc before booting system.
Sent from my SM-N920P using Tapatalk

samep said:
Though not normal, these non boots on Samsung logo should be corrected by wiping dalvik-cache or factory reset. If not, something may be wrong.
That said, the initial boot after flash to optimize applications can easily take more than 12 minutes. Much longer if many apps are to be optimized. Shorter if factory reset is applied (less user apps to optimize but still has some optimization to do).
Are you familiar with reactivation lock or eMMC failure? When you flash stock tar in Odin, check your phone's display and Odin log for errors. A failed boot may boot to download mode and indicate an eMMC error.
Outside of those issues, I'd say wipe everything but ext sdcard, pull the battery, wait at least 30 seconds while discharging the power circuit with power button press and hold (not too firmly). Reinstall battery and boot directly to download mode and flash the stock tar in Odin using Odin defaults. Let it auto reboot. Note any failures.
Alternately, you can remove the ext sdcard or delete the Android folder on it. A functional phone should boot rather quickly with the wipes and no errors; shouldn't stay at the Samsung logo very long but still needs to initialize and find network and start the auto start apps. But prior to initial boot, you should also see it make a brief stop in stock recovery to initialize csc before booting system.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I recieved no errors on my phone screen during the flash. It always passed right through, although one time it did fail due to a faulty usb cable. Other than that once incident I've had no issues with flashing tars through odin. Thanks for your help! really appreciate. I will give the the battery discharge a shot when i get the chance.

Related

[Q] Phone went from Soft bricked to FULLY bricked, What are my options?

Hi, first let me give you the background of my phone.
I bought it off eBay used and it came in an almost perfect condition, preinstalled with Gingerbread 2.3.6. The only problems known with the phone is that it won't get recognized by Samsung Kies, but it does by my PC. Onto the problem...
My friend introduced me to the Cyanogen Mod 9, telling me it could increase battery life, performance, etc. I was interested and wanted to install this mod. I first rooted my phone with a Zip off a tutorial and that worked flawlessly and I had Super User. I then installed Rom Manager and proceeded to installing the mod. He gave me two zips to put into my SD card to install for the Cmod and Google Play. Long story short, after wiping cache, data user, and every other wipe before installing these two zips, I was stuck in a boot loop with the Samsung Logo and Cyanogen Mod 9 Animation. I didn't think much of it and turned off my phone for the night, leaving it for the morning.
This morning, I tried going to Download Mode and flashing a stock os with Odin3 and it went from boot loop to soft bricked. It gave me a message to connect the phone to Samsung Kies in order for it to before restored, but the problem is that the phone isn't recognized by the program. I tried .tar files and it led to nothing on Odin3 because it wouldn't get past "Get Pit for Mapping...". I tried numerous times and on one occasion, I accidentally had Re-Partition ticked but the flash didn't go through so I unplugged my device. After that, the phone turned off and no response after that.
It won't turn on, no device recognized through USB or Odin3. I tried the wall charger to see if it was the battery's fault but it led to nothing. What are my options in reviving my Samsung Galaxy S2 ?
Yikes. Sounds hard bricked. I think your only option is to pay to get try a jtag recovery. Search the board on that.
Sorry man.
Sent from my SGH-T989 using xda app-developers app
I agree. Not a lot of options especially since warranty will be difficult without proof of purchase.
For future reference (for you and anyone else in this situation) the boot loop you experienced is due to cwm v5.0.2.7 not wiping caches correctly. After flashing an ics rom, if you are running this recovery, you have to flash the darkside cache wipe to get the rom to boot.
yoft1 said:
I agree. Not a lot of options especially since warranty will be difficult without proof of purchase.
For future reference (for you and anyone else in this situation) the boot loop you experienced is due to cwm v5.0.2.7 not wiping caches correctly. After flashing an ics rom, if you are running this recovery, you have to flash the darkside cache wipe to get the rom to boot.
Click to expand...
Click to collapse
Thanks for the replies! I was wondering how reputable is MobileTechVideos on doing JTAG repairs on bricked phones. Also, do you have a tutorial on how I can try to install Cyanogen Mod 9 again with the Dark Side cache wipe so i wont get the same problem again? Thank you.

[Q] Stuck in boot loop, trying to return to stock, I think I need to use PIT file

Hi all. I'm in a real pickle here and hoping someone can tell me how to get out of this mess. It's a bit of a long story, but I'll summarise as best I can.
I've had my Galaxy Note 2 LTE (N7105) for a year and I rooted it pretty much the day after I got it. I'm not new to rooting at all (fourth Android device since 2010, all rooted), but I still feel like a noob at times. Over this 2014 Easter period I had time off so I decided to change ROMs.
I was previously using CM 11, which I had been using pretty much since I rooted. And I had updated CM at least once a month, sometimes more frequently. So I was looking for some new ROMs, downloaded about 5 and tried them out. The last two I tried was OmniROM (a 4.4.2 ROM) and CM 11 Remix (also a 4.4.2 ROM). I was using TWRP 2.7.0.2 to do the wipes, caches, flashes, etc. I had no issues flashing OmniROM, but when I flashed CM 11 Remix, I couldn't get in the first time. I was stuck in a boot loop. I pulled the battery, got back into recovery and tried flashing again. Still boot looping. I think the mistake I made was a Data Format. Either way, I finally got CM 11 Remix to load by first wiping, flashing the ROM, GApps, a sensor fix, a camera fix, Devil Kernel and then Super SU. However once in the ROM I was getting constant Google Play Store / Services FCs. Oh, and yes, I went through the typical brand new Android setups, entering my Google account and so on... I found that if I cleared data / caches on both Google Play Store app and Google Play Services app, it gave me temporary joy but as soon as I tried to download any app in Google Play I'd get the FC. Also, my signal was totally gone. I tried flashing back to OmniROM as it was my last known good and working ROM, but now that was boot looping. I even tried some of the other ROMs from that bunch I had, including AOKP. All would boot loop.
So after much trying different GApp packages, I decided to best thing to do would be restore it to stock, root again, then go for the custom ROM (hopefully CM 11 Remix) from a nice clean slate. So I did this. I downloaded the Android 4.3 stock ROM from SamMobile here. Installed Odin 3.07, then loaded it up and flashed the stock ROM. All seemed to go great, but when the ROM was done and phone rebooted, I get stuck in another boot loop! This time at the white "Samsung" logo with the glowing blue edges. Not the model number screen. Also my LED light is on blue, if that means anything.
So I found this thread (post at top of page) which suggests I need to flash the PIT file during the stock ROM installation with Odin. So I found the PIT file here, and I'm ready to flash this along with the stock ROM... HOWEVER, I read something somewhere (can't find it now) that implied if I'm on Android 4.3, flashing a PIT is a bad move. Can anyone comment on that? I guessing since the stock ROM is 4.3, I'm technically on 4.3 (even though I can't get into it).
Or if anything else I'm doing immediately stands out as a seriously stupid move, please let me know. I've been without normal use of my phone for a couple days now and ironically I'm at the point where I'm considering going without a phone for the rest of my life... LOL! AS IF I COULD!
Anyways, any help will be much appreciated!
EDIT: I just realised I should have posted in Troubleshooting, not General Questions... If mods want to move this, please do.
i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.
edan1979 said:
i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.
Click to expand...
Click to collapse
I don't have any working ROM. All I have now is a boot loop.
invertedskull said:
I don't have any working ROM. All I have now is a boot loop.
Click to expand...
Click to collapse
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.
Banutu said:
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.
Click to expand...
Click to collapse
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?
invertedskull said:
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?
Click to expand...
Click to collapse
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.
Banutu said:
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.
Click to expand...
Click to collapse
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!
invertedskull said:
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!
Click to expand...
Click to collapse
I'm glad to hear that man, peace ^^
Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!
invertedskull said:
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!
Click to expand...
Click to collapse
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S
Banutu said:
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S
Click to expand...
Click to collapse
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.
invertedskull said:
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.
Click to expand...
Click to collapse
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk
Banutu said:
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk
Click to expand...
Click to collapse
Hmmm, I haven't seen that one... Feel free to PM me a link.
Help Me!
Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
If you have access to anything, and don't get JUST the boot loop, then you DO NOT have the same case I was in. You are probably able to recover from this. Try posting on the Tf Forums. The guys over there are "specialists" in Asus Tf tablets, and as you'll see on this thread (http://www.transformerforums.com/fo...-boot-loop-after-doing-routine-cm-update.html), they gave me a lot of help. Not that I was able to recover, but they were awesome dudes.
mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
mroldman281, You didn't post again, so I don't know, If You found solution, but since I had same simptoms, and after four days of reinstalling different stock roms, wiping and even messing with PIT via Odin etc..I can say, that in my case the reason for boot loop was faulty battery. The phone worked when it was plugged in and restarted soon after i unplugged USB cable, and just lopped afterwards. Replacement battery put everything back in order. And I am one happy Camper!
Hope this info helps someone else with boot loop problem
same problem stuck in bootloop
hey guys i have the same problem bootloop all the time i tryied stock firmware but nothing happend avec i rooted my note 2 and intalled a costom recovery and a many roms but stuck in bootloop i didn't chage baterry , by the way i wiped cache and reset factory and clear dalvick cache but the same always bootloop
what u suggest i do
ps : i can acces to bootloader or download mode it charge normally
woow get back my note 2 lte alone
hey guys i get back my note 2 i don't know how but it was a succes :victory:
first : i tried so many afficial firmware 4.4.2 and costom roms but didn't change the problem of bootloop
then i remembred what version i was in it was 4.1.1 so i download it from sammobiles thenks to them flash it and boooom the note 2 lte start like a charm
i want to thanks everyone for their help even if they didn't help directly but this past 3 days i read almost all the threads about note 2
well i thinks one of the selutions here is to revert back the the original stock firmware like i did so maybe will fix the bootloop

[Q] Can't boot into recovery or OS

First of all, thank you very much for taking a look at this.
This message has been deleted 4 times by the text editor. Hopefully this one will sound a bit more polished as a result. Over the past few days I have been slowly installing cyanogenmod 12 to my Note 4. I have been dealing with issues installing it from the get-go, and quickly became familiar with restoring the stock ROM with Odin as a result. This latest time it seems did not go as swimmingly as they were before. The last time I tried flashing it back to the stock OS with Odin, it wouldn't boot into android afterwords. It now flashes the boot screen, doesn't even show the sprint bootstamp, shuts down, and restarts again. My multiple days of google-fu has failed me and I believe you guys are my only hope.
Did you try flashing stock ROM through Odin mod
leader601 said:
This latest time it seems did not go as swimmingly as they were before.
Click to expand...
Click to collapse
Sorry, I should've been more clear here. The last time I tried flashing it back to the stock OS with Odin, it wouldn't boot into android afterwords.
[Solved]
For the next person who makes this mistake, remove the battery for 30 seconds.
It seems I was too occupied with the more complex solutions to notice the simple one in front of my eyes.
Can you get to recovery and factory reset?
Tried without sdcard?
Odin TWRP recovery and wipe everything, power down and then Odin stock tar?
Not necessarily all the above at same time but in progressive manner getting more aggressive each attempt.
While in CM12, was there anything you might have flashed that started some problems prompting a return to stock? Xposed framework? Restore a nandroid?

[Q] Loads of Problems (rooted, unrooted, firemwares, flash, stuck on logo screen)

I'm having one hell of a time with this tablet. This is pushing a month and I'm still not satisfied with my tablet.
Tonight I finally tracked down what I had hoped was a stock firmware for my tablet. Halfway through the download it timed out and when I went to download it again, the same thing happened.
So I tried to take my tablet that isn't "properly rooted" anymore and use Odin 9, instead of Odin 10, and place kitkat on my device rather than be stuck with Lollipop 5.0.2. All of this because The Sims Freeplay app isn't working and I can't find another soul on the face of the earth who can give me an answer to why this is happening.
Now I'm stuck on the samsung logo. I managed to get it back in download mode and that's where I flashed Lollipop 5.0.2 through Odin 10. I figured that would solve my problem. It didn't, but at least I got TWRP back on my device.
I never recovered anything that came with my tablet. I did not think I'd ever go back to unroot nor did I know how to back it up in the first place. So there's nothing in my recovery I can boot from. So what I did was I came back here and I downloaded the recovery for TWRP. I flashed it from my SD card, it told me it was successful... now what? I've rebooted and my device still loads to the samsung logo...and just stays there. The little confetti animation happens behind the logo, but that's it. It doesn't turn off. It doesn't reset itself.
CAN SOMEONE PLEASE TELL ME WHAT I'M DOING WRONG?!
I've already voided the warranty on this device and I regret almost daily that I decided to root in the first place. I say this only because I think rooted devices are top-notch, but I haven't been having very much luck with them. It took me a week to root. When I finally rooted then my favorite app game stopped working. Then I figured I could flash the stock firmware easily (but it seems like every place I go to find kitkat or even stock lollipop I can't find or I do, but files are corrupt or sites are full of ads).
I can't use my device at all now except click around in TWRP which isn't doing me any good.
I just want my tablet back. I spent 500 dollars on this thing and I haven't had time to even enjoy it. It's only two months old.
Please. Again. Someone HELP me. I want to figure this out and I don't want to accept that I bricked my device because I've watched plenty of videos on youtube and people are stuck with a phone that's resetting and all they do is fix it right there in front of my eyes.
Why can't I fix this? What is it that I'm not doing properly?
geekery15 said:
I'm having one hell of a time with this tablet. This is pushing a month and I'm still not satisfied with my tablet.
Tonight I finally tracked down what I had hoped was a stock firmware for my tablet. Halfway through the download it timed out and when I went to download it again, the same thing happened.
So I tried to take my tablet that isn't "properly rooted" anymore and use Odin 9, instead of Odin 10, and place kitkat on my device rather than be stuck with Lollipop 5.0.2. All of this because The Sims Freeplay app isn't working and I can't find another soul on the face of the earth who can give me an answer to why this is happening.
Now I'm stuck on the samsung logo. I managed to get it back in download mode and that's where I flashed Lollipop 5.0.2 through Odin 10. I figured that would solve my problem. It didn't, but at least I got TWRP back on my device.
I never recovered anything that came with my tablet. I did not think I'd ever go back to unroot nor did I know how to back it up in the first place. So there's nothing in my recovery I can boot from. So what I did was I came back here and I downloaded the recovery for TWRP. I flashed it from my SD card, it told me it was successful... now what? I've rebooted and my device still loads to the samsung logo...and just stays there. The little confetti animation happens behind the logo, but that's it. It doesn't turn off. It doesn't reset itself.
CAN SOMEONE PLEASE TELL ME WHAT I'M DOING WRONG?!
I've already voided the warranty on this device and I regret almost daily that I decided to root in the first place. I say this only because I think rooted devices are top-notch, but I haven't been having very much luck with them. It took me a week to root. When I finally rooted then my favorite app game stopped working. Then I figured I could flash the stock firmware easily (but it seems like every place I go to find kitkat or even stock lollipop I can't find or I do, but files are corrupt or sites are full of ads).
I can't use my device at all now except click around in TWRP which isn't doing me any good.
I just want my tablet back. I spent 500 dollars on this thing and I haven't had time to even enjoy it. It's only two months old.
Please. Again. Someone HELP me. I want to figure this out and I don't want to accept that I bricked my device because I've watched plenty of videos on youtube and people are stuck with a phone that's resetting and all they do is fix it right there in front of my eyes.
Why can't I fix this? What is it that I'm not doing properly?
Click to expand...
Click to collapse
I just skimmed through all this reading, so I may have missed a few things. The thing I didn't see if factory resetting. You need to factory reset in twrp. Just go to wipe and factory reset. Now reboot and wait at least 20 minutes as it does take quite a while to boot.
If doesnt do, transfer a custom stock based ROM for your device (any KK ROM should do) to your SD card. Factory reset in twrp and flash ROM. Now reboot and wait.
Typically, flashing with Odin takes 20 minutes to boot up for the first time. Just be sure you factory reset.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
I just skimmed through all this reading, so I may have missed a few things. The thing I didn't see if factory resetting. You need to factory reset in twrp. Just go to wipe and factory reset. Now reboot and wait at least 20 minutes as it does take quite a while to boot.
If doesnt do, transfer a custom stock based ROM for your device (any KK ROM should do) to your SD card. Factory reset in twrp and flash ROM. Now reboot and wait.
Typically, flashing with Odin takes 20 minutes to boot up for the first time. Just be sure you factory reset.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Ok. I just factory resetted. Then I went to reboot and clicked "system". Now it restarted and brought me back to the same samsung logo... do I wait 20 minutes on that screen?
geekery15 said:
Ok. I just factory resetted. Then I went to reboot and clicked "system". Now it restarted and brought me back to the same samsung logo... do I wait 20 minutes on that screen?
Click to expand...
Click to collapse
Yep.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
Yep.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
By any chance does it take longer than 20 minutes?
It's been 28 minutes and I'm still on the Samsung logo.
geekery15 said:
By any chance does it take longer than 20 minutes?
It's been 28 minutes and I'm still on the Samsung logo.
Click to expand...
Click to collapse
Sometimes. Try and wait 10 more minutes.
If it doesn't boot, I think you may have to flash a custom stock based ROM and flash it from your SD card in twrp.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
Sometimes. Try and wait 10 more minutes.
If it doesn't boot, I think you may have to flash a custom stock based ROM and flash it from your SD card in twrp.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Custom Stock Based Rom? Does that mean I'll push myself further away from a stock firmware? Also... where do I find one and are there instructions for it? I thought roms were firmwares up until like 4 hours ago and I've been reading of roots for a little over a month now.
I see you've got the same tablet. By any chance are you running 5.0.2 lollipop and do you happen to know having a rooted device is the reason why The Sims Freeplay won't get past it's splash screen or if it's the app itself and it's newest update that made it wiggy?
I'll flash whatever at this point, but my main reasons for continuing to mess with my tablet was because of not being able to play the sims on there. Every other game I play works.
geekery15 said:
Custom Stock Based Rom? Does that mean I'll push myself further away from a stock firmware? Also... where do I find one and are there instructions for it? I thought roms were firmwares up until like 4 hours ago and I've been reading of roots for a little over a month now.
I see you've got the same tablet. By any chance are you running 5.0.2 lollipop and do you happen to know having a rooted device is the reason why The Sims Freeplay won't get past it's splash screen or if it's the app itself and it's newest update that made it wiggy?
I'll flash whatever at this point, but my main reasons for continuing to mess with my tablet was because of not being able to play the sims on there. Every other game I play works.
Click to expand...
Click to collapse
The only thing I can suggest is download this to your SD card and flash it in twrp. http://forum.xda-developers.com/showthread.php?p=56345482
The Sims may not work because its uncomptiple with lollipop.
Simply, hit wipe in twrp, hit advanced wipe, and tick system, dalivk and cache. Then go back and install the Cm11 zip and reboot. Hopefully it gets you booting
Sent from my SM-T800 using Tapatalk
I'd actually flash this as its more like stock just debloated.
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
You need to wipe system, dalvik, cache and data then Install via twrp.
Wait at least 10 to 15 mins after install for initial boot up.
For future reference whenever you go back to kitkat from lollipop you need to wipe the data and cache partition first.
By the way some apps and games do not work on rooted devices for security reasons.
DUHAsianSKILLZ said:
Yep.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
DUHAsianSKILLZ said:
Sometimes. Try and wait 10 more minutes.
If it doesn't boot, I think you may have to flash a custom stock based ROM and flash it from your SD card in twrp.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
ashyx said:
I'd actually flash this as its more like stock just debloated.
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
You need to wipe system, dalvik, cache and data then Install via twrp.
Wait at least 10 to 15 mins after install for initial boot up.
For future reference whenever you go back to kitkat from lollipop you need to wipe the data and cache partition first.
By the way some apps and games do not work on rooted devices for security reasons.
Click to expand...
Click to collapse
I understand that. That is why I clicked unroot in supersu and tried the game app, but it still wouldn't work. On my galaxy note 3 I run 5.0 lollipop and my game works fine. My phone isn't rooted and I never decided to root it and then unroot it.
Is an app smart enough to know when a device has been rooted and if are those that hack their actual game on rooted devices uses cloak or xposed or both to by pass their root?
I rather be unrooted for the sake of the game, but how does one find the stock firmware? Or is it not possible at this point?
Sorry for any confusion.
ashyx said:
I'd actually flash this as its more like stock just debloated.
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
You need to wipe system, dalvik, cache and data then Install via twrp.
Wait at least 10 to 15 mins after install for initial boot up.
For future reference whenever you go back to kitkat from lollipop you need to wipe the data and cache partition first.
By the way some apps and games do not work on rooted devices for security reasons.
Click to expand...
Click to collapse
Okay. I installed or flashed ironrom to my tablet from twrp. i followed the directions it told me and I decided to pick the regular rom above the custom one that was close to stock. Then it told me that it was going to reboot; which it did. When it came back it got stuck on the same samsung loading screen so I powered it off, went back into TWRP (because powering off now isn't possible, more like restart) and I went to "Reboot " and then I clicked "power off".
I guess I'll be waiting for 10 to 15 minutes.
I Pray I did this correctly.
geekery15 said:
Okay. I installed or flashed ironrom to my tablet from twrp. i followed the directions it told me and I decided to pick the regular rom above the custom one that was close to stock. Then it told me that it was going to reboot; which it did. When it came back it got stuck on the same samsung loading screen so I powered it off, went back into TWRP (because powering off now isn't possible, more like restart) and I went to "Reboot " and then I clicked "power off".
I guess I'll be waiting for 10 to 15 minutes.
I Pray I did this correctly.
Click to expand...
Click to collapse
Thanks for all the help! I'm finally back to where I want to be and the ss freeplay seems to be working. I can't thank you both enough.
geekery15 said:
Thanks for all the help! I'm finally back to where I want to be and the ss freeplay seems to be working. I can't thank you both enough.
Click to expand...
Click to collapse
Why did you reboot back into twrp? You should have just let it do its thing after it rebooted.
So for any others that may happen upon this thread.
What was your solution?
ashyx said:
Why did you reboot back into twrp? You should have just let it do its thing after it rebooted.
So for any others that may happen upon this thread.
What was your solution?
Click to expand...
Click to collapse
I did because I thought it had to be shut down before I powered it on and waited. I realized afterwards that you probably meant to just let it sit for 10 to 15 minutes.
Are you asking me my solution or other peoples solution?
geekery15 said:
Are you asking me my solution or other peoples solution?
Click to expand...
Click to collapse
Your solution.
cant reboot after failed encryption
I was trying to encrypt my galaxy tab s, which is rooted and has lollipop 5.0. Afrer reading encryption failed. I tried to reboot in recovery via twrp. My device doesn't reboot, it just acts like its going thru the motions. Only to return to twrp recovery menu. How do I reboot the system clearing the failed encryptions. I am a noob and any suggestions would be much appreciated.
You will have to go into recovery and wipe the data and cache partition then reboot.
It may take a while to boot up after that.
Well I thought my solution was using IronRom... but i'm not too sure now.
I just got back from work and I went to turn on my tablet and it took me to the same loading screen and then after about 5 minutes it tells me that the system can't respond. It asks me to click "ok" or "wait" ... clicking either just turns my tablet off.
Now the screen has dimmed. It's turning on when it wants and sometimes it'll show me the time in the upper right hand corner, but it won't let me do anything because it's a black screen.
What does all of this mean?
I just noticed if I click the "power button" it just flashes my tablet desktop then goes back to black, but it shows me the battery percentage and the time in the upper right hand corner...
smt 800 stuck in logo
SAMSUNG GALAXY TAB S 10.5 WIFI WHAT IT CAN AND CANT DO
i HAD ROOTED AND INSTALLED LOLLIPOP 5.0 WITH SUPER SU AND TWRP RECOVERY.
I THEN TRIED TO ENCRYPT WHICH FAILED.
MY DEVICE SAID TO REBOOT SYSTEM AND THEN TRY TO ENCRYPT AGAIN. AFTER REBOOTING, MY DEVICE IS STUCK WITH (logo screen)THE SAMSUNG TAB S NAME AT THE TOP OF THE SCREEN AND ANDROID ON THE BOTTOM. I then rerooted with cf auto root thru odin. Odin and my tablet went thru the motions. When everything was complete and device should have initialize, but didn't. This part of the process didn't happen.
I am able to go into DOWNLOAD MODE and can get to manual mode, but I seem to have lost recovery. Here is the info.
android system recovery <3e>
kot49h_t800xxu1af8..
the binary reads: samsung official
system status: custom
Do you have any suggestions.

Stuck in Boot loop after weeks of normal usage

Hi.
I have a problem with my D855. My phone is rooted and runs the fulmics ROM. Everything was working fine, , on Fulmics 5.3, except than one day, I was using my phone normally and then it crashed. I saw the phone rebooting, but for some reason it got stuck. The phone tried to boot unsuccessfully until the "firmware update" went through, after what it reboots again (unsuccessfully) and so on.
At that time, I was able to access twrp, do some backup, and flash properly with a downgraded version of fulmics (from 5.3 to 4.1).
It was able to boot again and use my phone like before. Yet, after one month of usage, the same problem happened on version 4.1. The phone crashed and now cannot boot.
Any idea of where it is coming from? Should I go back to stock? Should I contact customer service?
What did you do before the phone crashes ?
I think you probably should flash the stock ROM and wait for an other crash... or not.
Jb-kun said:
What did you do before the phone crashes ?
I think you probably should flash the stock ROM and wait for an other crash... or not.
Click to expand...
Click to collapse
I haven't done anything special. I think that the first time I was playing on candy crush. The second time I was just looking at pictures in my gallery.
I was using the ROM without any tweaks or extra modules such as Xposed. Just regular use.
Update on my situation: I switched back to stock ROM and it seems to work OK for now (it has been 4 days). So I will wait and see if new problems happen. By the way, it was extremely difficult for me to get back to Stock directly from fulmics ROM. I tried several methods that I have found on xda based on LGUP or LG Flash tool without success. For some reason I was not able to connect the phone to my PC in download mode.
The only way that I found was to use a nandroid backup that I did just after rooting the phone and that was based on stock ROM.
shewshain said:
I haven't done anything special. I think that the first time I was playing on candy crush. The second time I was just looking at pictures in my gallery.
I was using the ROM without any tweaks or extra modules such as Xposed. Just regular use.
Update on my situation: I switched back to stock ROM and it seems to work OK for now (it has been 4 days). So I will wait and see if new problems happen. By the way, it was extremely difficult for me to get back to Stock directly from fulmics ROM. I tried several methods that I have found on xda based on LGUP or LG Flash tool without success. For some reason I was not able to connect the phone to my PC in download mode.
The only way that I found was to use a nandroid backup that I did just after rooting the phone and that was based on stock ROM.
Click to expand...
Click to collapse
You can also use the Stock rom flashable from twrp. So you can wipe the system partition and get a "better situation" than a nandroid backup that should be with an old version.
Or use this that has also root and other improvements.
shewshain said:
Hi.
I have a problem with my D855. My phone is rooted and runs the fulmics ROM. Everything was working fine, , on Fulmics 5.3, except than one day, I was using my phone normally and then it crashed. I saw the phone rebooting, but for some reason it got stuck. The phone tried to boot unsuccessfully until the "firmware update" went through, after what it reboots again (unsuccessfully) and so on.
At that time, I was able to access twrp, do some backup, and flash properly with a downgraded version of fulmics (from 5.3 to 4.1).
It was able to boot again and use my phone like before. Yet, after one month of usage, the same problem happened on version 4.1. The phone crashed and now cannot boot.
Any idea of where it is coming from? Should I go back to stock? Should I contact customer service?
Click to expand...
Click to collapse
Same problem here. Normal usage suddenly started to reboot and now it's stuck in boot loop
Coming from Fulmics too - stopped working one fine day.
Now, continues to boot-loop at the initial LG screen. Trying to get into the recovery shows me the the 'Factory Reset' screen, but beyond that leads to boot-loops again. Even the Download mode loops!
I'm at my wits end without a solution in sight.
Blysterk said:
You can also use the Stock rom flashable from twrp. So you can wipe the system partition and get a "better situation" than a nandroid backup that should be with an old version.
Or use this that has also root and other improvements.
Click to expand...
Click to collapse
Thank you for this advice. I was able to update my stock ROM after the Nandroid backup through LGUP, but your method would have been faster.
But anyway, I am waiting to see if I am stuck with bootloops again, using non-root stock version, so I can send it to customer service if this happen again.
AhmadAlmousa said:
Same problem here. Normal usage suddenly started to reboot and now it's stuck in boot loop
Click to expand...
Click to collapse
abourdeau said:
I have the exact same problem, I even bought a second battery with no success.
Click to expand...
Click to collapse
Are you using Fulmics ROM as well? Can you have access to TWRP? I was able to connect to a PC in the recovery mode and to transfer files before flashing, in case you need some basic backup...
prakhargr8 said:
Coming from Fulmics too - stopped working one fine day.
Now, continues to boot-loop at the initial LG screen. Trying to get into the recovery shows me the the 'Factory Reset' screen, but beyond that leads to boot-loops again. Even the Download mode loops!
I'm at my wits end without a solution in sight.
Click to expand...
Click to collapse
Silly question, but are you sure that you selected "Yes" when the screen asks you about factory reset? you have to press "volume down" and the "power button", since the default answer is no.
shewshain said:
Silly question, but are you sure that you selected "Yes" when the screen asks you about factory reset? you have to press "volume down" and the "power button", since the default answer is no.
Click to expand...
Click to collapse
Yes, of course I was able to access TWRP successfully earlier.
Curiously enough, the phone boot-loops in regular startup, Download mode and trying to get to recovery. However, it doesn't restart itself and fall into a loop, while on the Factory Reset menu. Am I correct in assuming that the battery could not be the root cause of the overall problem? Because if it was, it would likely loop even on this Factory Reset menu as well as far as I understand.
Unfortunately, the phone restarts as soon as it lands in the Download mode so I cannot even restore to stock.
EDIT: Okay, weirdly enough it just booted and reached the homescreen before restarting again. What I did was let it charge to a 100% and tried booting while plugged in. Could it be the battery after all? Though this exact set of steps hasn't been helpful before.

Categories

Resources