I've been reading through other threads here on XDA about a common boot loop issue that N900T users are experiencing, but nowhere was it mentioned that the Canadian variant users had a similar problem, but I do.
I was wondering if there were any other SM-N90028 users out there that were stuck in a boot loop?
Here is my situation:
I have a Canadian SM-N900W8 (it is, also a Qualcomm LTE version) and I'm in a boot loop... it all started when I tried to restore a Stock-Rooted Rom with TWRP.
I can't, however get it out, and I've tried all of the versions of TWRP, I've also used odin like 30 times... nothing.
I successfully restored a Rooted stock ROM through TWRP, but it wasn't until I re-installed a factory un-rooted one that things got ugly..
So I was thinking about this and perhaps the cause of this is KNOX... since the first thing I did when I rooted my phone initially was uninstall KNOX and all of its files. I know these didn't carry over when I did a TWRP backup, which is perhaps why my restore of that backup worked the first time. The second time, I just went and downloaded everything stock and used Odin, and that's when the bootloop occurred.
if anyone knows of a way to solve this, I'd be forever grateful!
I really hope I will be able to fix this...
Not to sound.to xdaish...but dude seriously this topic.is all.over the n3 forums. Have a.look and you will find tons of info.
Also...good idea to.read prior to flashing..if you had you would have know not to restore with twrp since it causes bootloops.
Just trying to you some friendly advice.
Sent from my SM-N900W8 using xda premium
force70 said:
Not to sound.to xdaish...but dude seriously this topic.is all.over the n3 forums. Have a.look and you will find tons of info.
Also...good idea to.read prior to flashing..if you had you would have know not to restore with twrp since it causes bootloops.
Just trying to you some friendly advice.
Sent from my SM-N900W8 using xda premium
Click to expand...
Click to collapse
Thank you, but I've read them all and most are regarding the n900t, I felt it appropriate to ask about the n900w8 variant.
Also, I know that would have been better, but it's too late for that now. I just thought I'd share my experiences here with this issue so that others will know better.
So I tried a different stock ROM, and with the latest version of Odin, but it still is in a boot loop.
However there is one difference; this time it will boot past the Samsung logo and into android, but then a window will pop up saying "Process system isn't responding" and ask me to wait for it to respond or close it. Regardless of what I select, it will end up rebooting seconds later.
In the very short time that everything stays booted for, I can access the two pull-down menus from the top, but selecting anything will yield me no results.
Perhaps this can tell us more about this issue?
Did you have a read.through this....a few.guys have revived their n900w8s here
http://forum.xda-developers.com/showthread.php?p=46450690
Sent from my SM-N900W8 using xda premium
force70 said:
Did you have a read.through this....a few.guys have revived their n900w8s here
http://forum.xda-developers.com/showthread.php?p=46450690
Sent from my SM-N900W8 using xda premium
Click to expand...
Click to collapse
Thanks! I checked it out and my phone is already set to those settings, so it didn't work, but I'm still trying!
c_est_la_vie said:
Thanks! I checked it out and my phone is already set to those settings, so it didn't work, but I'm still trying!
Click to expand...
Click to collapse
Check post #350 in this thread and read forward. http://forum.xda-developers.com/showthread.php?t=2467001&page=46
this worked!
Hey guys, I'm not sure if anyone's checked this out yet, but I managed to get myself out of the boot loop!
here is the solution:
http://forum.xda-developers.com/showthread.php?t=2471421
Glad your back up and running!
Sent from my SM-N900W8 using xda premium
Thanks!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Related
I replaced my 16 with 32gb model rooted the phone and I just realized the custom warning on boot is not showing....
Why is that?
lowspeed said:
I replaced my 16 with 32gb model rooted the phone and I just realized the custom warning on boot is not showing....
Why is that?
Click to expand...
Click to collapse
Means you rooted properly? Whenever I have to reroot, as long as I follow the steps provided I don't even get the custom screen, and this is on my 16Gb.
Use root checker to verify root though.
Thermalwolf said:
Means you rooted properly? Whenever I have to reroot, as long as I follow the steps provided I don't even get the custom screen, and this is on my 16Gb.
Use root checker to verify root though.
Click to expand...
Click to collapse
Oh yeah definitely rooted
I rooted an follow the instructions to avoid the custom unlock Icon. No problem it did not show. Then three days later when I started the phone in the morning it showed. I tried unrooting (then no Icon) and rerooting but nothing seems to work, still have the Icon. I used both method the original and the revised to reroot.
Yes. Has nothing to do with rooting 'correctly'. It will reappear eventually. Always does.
Sent from my Galaxy S4 using Tapatalk
Baldilocks said:
Yes. Has nothing to do with rooting 'correctly'. It will reappear eventually. Always does.
Sent from my Galaxy S4 using Tapatalk
Click to expand...
Click to collapse
NEVER reappeared for me I'm still extremely confused about the phone just randomly choosing to do this..
Thermalwolf said:
NEVER reappeared for me I'm still extremely confused about the phone just randomly choosing to do this..
Click to expand...
Click to collapse
No biggie really. Especially since we have the stock firmware and ODIN in case we need to restore it to factory.
Sent from my Galaxy S4 using Tapatalk
Baldilocks said:
No biggie really. Especially since we have the stock firmware and ODIN in case we need to restore it to factory.
Sent from my Galaxy S4 using Tapatalk
Click to expand...
Click to collapse
I guess, it just makes me wonder though, what's going on in the background of the phone that sets it back into custom mode. You're right though, it's not really a big deal since we can ODIN back
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Mine has always been there too but I don't care that much. I also debloated it so I suspect that's why mine is "custom".
Sent from my SAMSUNG-SGH-I337 using xda premium
Hello guys my nexus 7 recently went into a bootloop almost exactly similar to the once described in this thread. http://forum.xda-developers.com/showthread.php?t=2468392
This started when I reinstalled KaosDroid v.7.0.0 after I realised that I'd forgotten to flash Google apps. Now when I switch on my nexus all I can see is a bootloop between the Google screen and the CWM initial screen. There is a video in the other thread about what I'm talking about. Now,I have a couple of questions....
Please do refer to the other thread to satisfy any questions you might have and.if not, I'll answer your questions.
1. Is it possible by any means to recover my nexus or at least, break out of the bootloop?
2. If the answer to the above is no, then I'd there any point trying to claim the warranty?
Thanks on advance for trying to help me.
Sent from my GT-S5570 using xda app-developers app
Try stock factory image, it'll reinstall stock recovery, bootloader, system.
I got into bootloops after I tried updating to 4.4 (from 4.3 stock) and I just installed stock factory image and everything works as a charm.
Hmmm. Thank you for your reply.It seems you didn't read the other thread. The problem odds that the fastboot mode it's completely inaccessible. All I want you too answer honestly I'd the second question
Sent from my GT-S5570 using xda app-developers app
So I was trying to help a friend flash stock using Odin because his phone app was being a piece of crap, he was on a CM 11 nightly and, well, long story short I almost bricked his phone not knowing there is a limit on how many times you can flash a Samsung device using Odin because of the yellow triangle. I can't use triangle away because it's the CM ROM on a CM kernel, I was able to get rid of the softbrick by using a older CM ROM on his SD card, this wouldn't be a problem if his phone app was still working, his WiFi was working and if his sound was working, but it's not. So to recap and for the question, Samsung is stupid, and can anyone help?
Thanks in advanced
Sent from my awesome LG-E980
lonlyhornet said:
So I was trying to help a friend flash stock using Odin because his phone app was being a piece of crap, he was on a CM 11 nightly and, well, long story short I almost bricked his phone not knowing there is a limit on how many times you can flash a Samsung device using Odin because of the yellow triangle. I can't use triangle away because it's the CM ROM on a CM kernel, I was able to get rid of the softbrick by using a older CM ROM on his SD card, this wouldn't be a problem if his phone app was still working, his WiFi was working and if his sound was working, but it's not. So to recap and for the question, Samsung is stupid, and can anyone help?
Thanks in advanced
Sent from my awesome LG-E980
Click to expand...
Click to collapse
First thing you have to do for anyone to help you is,provide which build you were on and which stock rom you were trying to flash. There are tons of people here with great knowledge if you can be real specific.
Sent from my Nexus 5 using Tapatalk
So you wanna go to complete stock on a sprint s4?
Sent from my SPH-L720 using XDA Premium 4 mobile app
Fairly sure there is no limit to the amount of times you can flash using Odin. There is a counter but no limit
Sent from my SPH-L720 using xda app-developers app
Sorry, Samsung isn't stupid or they wouldn't just magically be a $250+billion dollar company that has been around for 76 years.
Because you jumped in and were unsuccessful with what you were doing doesn't constitute failure on their part.
How about taking that phone - S4 back to bone stock. ALL the answers on how to do that are here. In fact in the last couple days I've personally given instructions on how to do that for a number of people here in the help section. Do some searching and reading and you'll find your answers.
It always helps to come to a manufacture's section and say how sh**y they are. Makes those of us who choose to use and support them feel ever so helpful.
Ok sorry should've been more specific, I'm not new to these forums I was just in a hurry, also seriously guys I'm just frustrated I know Samsung is not stupid you don't have to post their history, they're awesome it's just dumb that they have a limit, and yes if you install the latest stock Sprint update (the one I did before I rooted and rom'd his phone) there wouldn't be a thing such as triangle away. Anyway on Odin it says it passed when flashing stock (the firmware that comes with the phone) but it does it in 4 seconds, and when his phone boots up and it just restores CM, so far everything we've tried either softbricks it or restores CM. Is there anything that completely and I mean completely restores this phone
Sent from my awesome LG-E980
lonlyhornet said:
Ok sorry should've been more specific, I'm not new to these forums I was just in a hurry, also seriously guys I'm just frustrated I know Samsung is not stupid you don't have to post their history, they're awesome it's just dumb that they have a limit, and yes if you install the latest stock Sprint update (the one I did before I rooted and rom'd his phone) there wouldn't be a thing such as triangle away. Anyway on Odin it says it passed when flashing stock (the firmware that comes with the phone) but it does it in 4 seconds, and when his phone boots up and it just restores CM, so far everything we've tried either softbricks it or restores CM. Is there anything that completely and I mean completely restores this phone
Sent from my awesome LG-E980
Click to expand...
Click to collapse
Where are you getting this idea there is a limit on Odin flashes?
Sent from my SPH-L720 using xda app-developers app
There is no limit, as mentioned already, with Odin.
I've used it probably a hundred times since I got my S4. I know others have used it more.
Take some time, look through the Q&A/help forum and you'll see some posts I've helped others with, in the last 24hours alone, on how to get back to stock.
Edit:
Okay read this post. It'll get you to stock. Just read the instuctions on how to do it.
Ok I'll try it thanks for tolerating me I can be hard to understand when panicking
Sent from my awsome LG-E980
leaderbuilder said:
There is no limit, as mentioned already, with Odin.
I've used it probably a hundred times since I got my S4. I know others have used it more.
Take some time, look through the Q&A/help forum and you'll see some posts I've helped others with, in the last 24hours alone, on how to get back to stock.
Edit:
Okay read this post. It'll get you to stock. Just read the instuctions on how to do it.
Click to expand...
Click to collapse
Did it and it worked thanks man! sorry for being rude I was just worried that I may have ruined my friends phone.
lonlyhornet said:
Did it and it worked thanks man! sorry for being rude I was just worried that I may have ruined my friends phone.
Click to expand...
Click to collapse
Glad you got it working and THANK YOU for posting back - that is what helps the community.
I understand the panic too. Especially when things are f'd up.
But if there is one valuable lesson I've learned in my half century of life; if you can just pause, relax and step back, many problems are easily resolved. And better yet more avoided by haste.
Good luck with the new phone setup.
OK one more quick thing, we flashed it successfully but now it won't boot its been over an hour after we flashed and its stuck on the Sprint logo
lonlyhornet said:
OK one more quick thing, we flashed it successfully but now it won't boot its been over an hour after we flashed and its stuck on the Sprint logo
Click to expand...
Click to collapse
You can first boot to stock recovery (power on + volume up) and choose a 'factory reset'. That often clears stuff up pretty well
Or
Try and PC Oding a stock MK2 kernel. Then battery pull and restart after. Saw this on a few phones
I'll have to search to find it but it's here somewhere.
leaderbuilder said:
You can first boot to stock recovery (power on + volume up) and choose a 'factory reset'. That often clears stuff up pretty well
Or
Try and PC Oding a stock MK2 kernel. Then battery pull and restart after. Saw this on a few phones
I'll have to search to find it but it's here somewhere.
Click to expand...
Click to collapse
Thanks! Factory resetting worked his phone is back on stock and ready for 4.4.2 thanks for the help LeaderBuilder!
lonlyhornet said:
Thanks! Factory resetting worked his phone is back on stock and ready for 4.4.2 thanks for the help LeaderBuilder!
Click to expand...
Click to collapse
Great!
Sent from my SPH-L720 using XDA Premium 4 mobile app
Hey guys, I don't post here often, but I'm not new to this. It was through this forum that I first started rooting with mfy s3.
I just got a note 3 through Sprint. I've gotten used to getting off the grid, so I immediately jumped to root it. I decided on Jellybomb after reading some reviews. Then I downloaded everything necessary to make the jump: Odin, 1.85 and 3.09, jellybomb, cwm 6.0, twrp 7, auto-root, and the original roms in case I had to hop back.
First I went with Chainfires auto-root. I didn't seem to have any problem flashing that. The problem came with flashing twrp and the new rom. I can't remember which one was giving me trouble (I've been fighting it almost a week now). Somehow some way the phone has been stuck in an autoboot that says "seandroid not enforcing" and either "warranty bit: recovery" or "warranty bit: kernel". I tried new kernels. I tried things in different order. I can get into recovery but only after going immediately after autoroot. Even there you have a broken android.
Please help. I've been without a phone for a week.
KoolCharisma said:
Hey guys, I don't post here often, but I'm not new to this. It was through this forum that I first started rooting with mfy s3.
I just got a note 3 through Sprint. I've gotten used to getting off the grid, so I immediately jumped to root it. I decided on Jellybomb after reading some reviews. Then I downloaded everything necessary to make the jump: Odin, 1.85 and 3.09, jellybomb, cwm 6.0, twrp 7, auto-root, and the original roms in case I had to hop back.
First I went with Chainfires auto-root. I didn't seem to have any problem flashing that. The problem came with flashing twrp and the new rom. I can't remember which one was giving me trouble (I've been fighting it almost a week now). Somehow some way the phone has been stuck in an autoboot that says "seandroid not enforcing" and either "warranty bit: recovery" or "warranty bit: kernel". I tried new kernels. I tried things in different order. I can get into recovery but only after going immediately after autoroot. Even there you have a broken android.
Please help. I've been without a phone for a week.
Click to expand...
Click to collapse
This one is the International Note 3 forum.
You should ask for actual details in the specific Sprint Note 3 forum:
http://forum.xda-developers.com/note-3-sprint
You should also pay more attention to the fact that the questions should be posted in the Q&A subforum.
Thanks
xclub_101 said:
This one is the International Note 3 forum.
You should ask for actual details in the specific Sprint Note 3 forum:
http://forum.xda-developers.com/note-3-sprint
You should also pay more attention to the fact that the questions should be posted in the Q&A subforum.
Click to expand...
Click to collapse
Cheers! It looks from your sig though that you have found a work around on your international version. Are they really that different, that need entirely separate instructions. Obviously I downloaded all of the suggested software for Sprint and followed Sprint suggested, but I'm frustrated because I simply don't understand how I could do something the same way everyone else did and yet have it fail on me like this.
I am having the exact same problem...at first i was able to flash 'openrecovery-twrp-2.6.3.0-hltetmo.img.tar and it would boot my phone back to normal. I have now run into this problem again and my first original fix isn't working anymore. If I can figure out a way I will definitely let you know!
Getting Answers
Anonymous777 said:
I am having the exact same problem...at first i was able to flash 'openrecovery-twrp-2.6.3.0-hltetmo.img.tar and it would boot my phone back to normal. I have now run into this problem again and my first original fix isn't working anymore. If I can figure out a way I will definitely let you know!
Click to expand...
Click to collapse
Hey man, thanks for reaching out. I realized I should probably have been in the Sprint form so I created a new thread there and I've been getting some help!
If you want: shoot over there and see if the tips can help you: http://forum.xda-developers.com/showthread.php?p=51096673
Anonymous777 said:
I am having the exact same problem...at first i was able to flash 'openrecovery-twrp-2.6.3.0-hltetmo.img.tar and it would boot my phone back to normal. I have now run into this problem again and my first original fix isn't working anymore. If I can figure out a way I will definitely let you know!
Click to expand...
Click to collapse
Hey man we've made a lot of headway at the above thread Thanks to Macmars. You should check it out and see if we can help each other.
Sent from my SM-N900P using xda app-developers app
KoolCharisma said:
Hey man we've made a lot of headway at the above thread Thanks to Macmars. You should check it out and see if we can help each other.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
I figured out what to do, use odin 3.9 and flash this, it took about 15 minutes to go through the whole process. Once my phone boot up it froze at the T-Moble logo or whatever, so I waited like 20 minutes and then powered it off, went into recovery and did a factory reset which then solved all my problems. I lost root, but no big deal to me. Better than buying a new phone!!! Btw the only place I could find this file is off sammobile.com. You have to sign up for a free membership thing but at least they give you the stock firmware.
TMB-N900TUVUCNB4-20140305155920/N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5
KoolCharisma said:
Hey man we've made a lot of headway at the above thread Thanks to Macmars. You should check it out and see if we can help each other.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Right on man!
Sent from my SM-N900P using xda app-developers app
I hate to do this but I'm in a rush here don't shoot me...
I am having a hell of a time trying to get TWRP recovery installed.. I have a AT&T SGH-I337 4.4.2 stock rom (rooted).
Tried every way thru TWRP manager no dice...
What is the trick????
Ok EDIT:
Found out i can't use TWRP on NC1 will look into safestrap. mod you can close this thread or delete.
Thanks
Dude, in the future don't post the same problem in so many place. Oeut makes it very difficult to know if you still have a problem and help you. Just saying
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Dude, in the future don't post the same problem in so many place. Oeut makes it very difficult to know if you still have a problem and help you. Just saying
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm with ya 100% I was just in a huge rush I needed to get this phone fixed fast and get it back to my sister and brother in law. I would have never done it otherwise.
I tried to update all the posts accordingly, I will make sure they are showing that I have solved the issue.
Thanks,