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
Related
Hey guys, I think i may have bricked my SGN.
I rooted via adb and then flashed the abyss kernel followed by stunner ics rom. But when i restarted through CWM the phone never restarted and now it won't even turn on. No download mode either and i've tried every possible trick including the wall outlet.
Phone won't turn on at all. Is this considered hard bricked and has anyone found a solution to this. Will a USB jig work on this.
Also, the stunner ics 4.5 beta showed successfull at CWM so i'm not sure what happened. Battery was fully charged too.
Try taking out the battery for a few minutes, put it back again and try entering download mode again.
What's sky ics rom?
Sent from my GT-N7000 using Tapatalk
hey thanks for the reply, i've tried that already as well. no download mode working here.
itsjiffybruh said:
Hey guys, I think i may have bricked my SGN.
I rooted via adb and then flashed the abyss kernel followed by stunner ics rom. But when i restarted through CWM the phone never restarted and now it won't even turn on. No download mode either and i've tried every possible trick including the wall outlet.
Phone won't turn on at all. Is this considered hard bricked and has anyone found a solution to this. Will a USB jig work on this.
Also, the sky ics showed successfull at CWM so i'm not sure what happened. Battery was fully charged too.
Click to expand...
Click to collapse
hmmm try to pull down battery, put it back again, try to turn on download mode, do this several times if it wont help, try to charge phone and do same. goodluck
sorry, i meant stunner ics. got confused with sky ics cuz i just put that into my friends skyrocket.
You didnt follow the instructions ti install the rom so you now have a brick
Try pluggingn it top the pc , if you hear some noises on the pc then your noté is alive
Sent from my GT-N7000 using xda premium
Well, did you try a USB-jig to force your Note into Download-Mode?
Than you should be able to flash a stock and start over again.
Did you let your Note do the first startup at his own, I've read that the first start may took a bit longer and shouldn't be interrupted?
Regards
thor2001 said:
Well, did you try a USB-jig to force your Note into Download-Mode?
Than you should be able to flash a stock and start over again.
Did you let your Note do the first startup at his own, I've read that the first start may took a bit longer and shouldn't be interrupted?
Regards
Click to expand...
Click to collapse
Well, i was in CWM and then installed the rom then pressed restart phone on CWM menu. Went downstairs and when I came back it didn't turn on.
if it doesn't turn on at all is it a hard brick?
I ordered a usb jig from amazon for $7.00 and it will arrive tomorrow, I heard the usb jig only works on soft bricked phones though and since mines won't even turn on will there be any chance at all of it working?
Hey guys I just realized what went wrong. I download the N7000 Galaxy note roms and kernels instead of the i717 (ATT) versions. Stupid me!
Has anyone ever had success getting a fix on this? If not would I be able to go to an AT&T store and just get a new one? What should I tell them. Please help
itsjiffybruh said:
Hey guys I just realized what went wrong. I download the N7000 Galaxy note roms and kernels instead of the i717 (ATT) versions. Stupid me!
Has anyone ever had success getting a fix on this? If not would I be able to go to an AT&T store and just get a new one? What should I tell them. Please help
Click to expand...
Click to collapse
Your phone may has yellow triangle and flash counters now. So you would not be able to get a new one or order them fixing it for you.
Sent from my GT-N7000 using xda premium
Wow that really sucks . I wish you could fix it soon and please keep us updated with how you fixed if so .
Sent From My Samsung Galaxy Note N7000 Using XDA Premium
.Hell. said:
Wow that really sucks . I wish you could fix it soon and please keep us updated with how you fixed if so .
Sent From My Samsung Galaxy Note N7000 Using XDA Premium
Click to expand...
Click to collapse
Ill definitely keep you guys updated. My usb jig isn't scheduled to arrive until monday so i might just try to go to the att store today and try to get a replacement.
siuming720 said:
Your phone may has yellow triangle and flash counters now. So you would not be able to get a new one or order them fixing it for you.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
how would they be able to test it if it doesn't even turn on?
hi try this not my work dont now if it works
Default Bricked Galaxy Note N7000 or Incorrect ROM Flash Easy Fix
Ok simple you won't see nothing on the screen because the bootloader is wrong.....
Just put the battery in then do following.
1. hold vol down+home+power for 15 seconds...
2. release then press volume up...
Note: Don't worry about seeing anything on the screen or any keys light
it will be blank this is because bootloader is incorrect
3. open odin you should see comxx in listed flash the original bootloader back
into phone this will/should resume visual display.
I have attached necessary files to resume
Load File in PDA NOT BOOTLOODER
4. Wait 10 seconds.. Remove Battery Then Boot Back into Bootloader following steps 1&2
5. finally flash Stock Rom to resume the whole phone to original state.
Hope That Helps......see hear for post http://forum.xda-developers.com/showthread.php?p=23052721#post23052721
Sent from my GT-N7000 using Tapatalk
thanks for the help. i read that on another post and already tried it. unfortunately its a no go.
Just came back from att center and they said that they couldn't replace it for me on the spot because they don't have the phone in stock since its a newer phone. I gotta call the number they gave me now.
Sorry you've run into such a serious issue, but in a few way it's probably quite a good thing it's a hard brick.... It's likely you would have had a raised flash counter and the fact they can't power it on there and then is a bit of a God sent.
Hope you get a replacement soon mate :thumbup:
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Sorry you've run into such a serious issue, but in a few way it's probably quite a good thing it's a hard brick.... It's likely you would have had a raised flash counter and the fact they can't power it on there and then is a bit of a God sent.
Hope you get a replacement soon mate :thumbup:
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
hey, im supposed to send my phone in to them and so your saying that when i send it in they won't be able to find out that i flashed a custom rom and kernel on it?
and im not sure if its such a good thing because if it was at least soft bricked i wouldve been able to fix it most likely. thanks for your help
itsjiffybruh said:
hey, im supposed to send my phone in to them and so your saying that when i send it in they won't be able to find out that i flashed a custom rom and kernel on it?
and im not sure if its such a good thing because if it was at least soft bricked i wouldve been able to fix it most likely. thanks for your help
Click to expand...
Click to collapse
First of all I think It wouldnt have raised the binary counter and give triangle because you didnt use Odin to flash (Am I right?).
Second thing Thought it had given you a triangle since your phone is dead.
So they cant find that you flashed a custom kernel or the binary.
itsjiffybruh said:
how would they be able to test it if it doesn't even turn on?
Click to expand...
Click to collapse
Oh.. I didn't see you can't enter to cwm
Sent from my GT-N7000 using xda premium
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
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,
I've hard bricked this thing once trying to flash a rom once. Tried to gain custom recovery via AUTOREC. Should be called Autowreck.
Sometimes it is best just to ask to be pointed in the right direction.
I just learned about LOKI and SAFESTRAP. BUT are these just for TW based ROMS? I want a CM based ROM. PACROM, specifically. I see others with this AT&T phone running it.
Will someone please help a noob with a tutorial or advice and stop me from running in circles? W/ rooted 4.4.2, NC1 build.
Start with reading well the SafeStrap thread by Hashcode in Q&A
and the All Thinks ATT, MK2 in General
You can only use SafeStrap and can not flash non TW roms or custom recoveries/kernels, so CM AOSP etc
Sorry
rugmankc said:
Start with reading well the SafeStrap thread by Hashcode in Q&A
and the All Thinks ATT, MK2 in General
You can only use SafeStrap and can not flash non TW roms or custom recoveries/kernels, so CM AOSP etc
Sorry
Click to expand...
Click to collapse
Been reading the safe strap thread. 89 pages! Stumped on the first one. ENCRYPTED? Not sure. How do I tell? Nb1, Mk2, Mf3 software? No idea. Did not see it in settings> about device. How do I tell is the next step I guess.
On to check the All Thinks Mk2 thread. Sorry for my noobness.
New Song said:
Been reading the safe strap thread. 89 pages! Stumped on the first one. ENCRYPTED? Not sure. How do I tell? Nb1, Mk2, Mf3 software? No idea. Did not see it in settings> about device. How do I tell is the next step I guess.
On to check the All Thinks Mk2 thread. Sorry for my noobness.
Click to expand...
Click to collapse
Get a terminal emulator on your phone. In it type:
su
getprop ro.bootloader
What does it say? Look at the last three characters
Edit, in about devices what is your baseband, last three characters?
Sent from my Nexus 5 using XDA Free mobile app
Sorry, I thought you NC1 now?
jd will get you sorted, he is more hands on with safestrap than i am
but, the gist of it is going to All Thinks ATT, MK2 and to post 5
but read all you can in both threads--:good:
Nc1. So this is the SafeStrap file: JFLTE-3.72-kk-B01.apk. How a bow the encryption determination? Sound like a bootloader if it is encrypted.
New Song said:
Nc1. So this is the SafeStrap file: JFLTE-3.72-kk-B01.apk. How a bow the encryption determination? Sound like a bootloader if it is encrypted.
Click to expand...
Click to collapse
Did you get nb1 from your baseband? Is your device encrypted? That's different than than the bootloader. Your bootloader is definitely locked. But you can root by updating to nc1 and using towelroot and then safestrap.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Did you get nb1 from your baseband? Is your device encrypted? That's different than than the bootloader. Your bootloader is definitely locked. But you can root by updating to nc1 and using towelroot and then safestrap.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
NC 1
I am rooted. SS installed. ROM DL'ed ready to go. Creating ROM slot. Or trying t seems stuck. I know it takes about 5 minutes. But it's been about 15-20
sorry for the pic quality. No zoom on this tab 4. It's next.
New Song said:
NC 1
I am rooted. SS installed. ROM DL'ed ready to go. Creating ROM slot. Or trying t seems stuck. I know it takes about 5 minutes. But it's been about 15-20
sorry for the pic quality. No zoom on this tab 4. It's next.
Click to expand...
Click to collapse
You have to use the stock slot, not a secondary slot
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You have to use the stock slot, not a secondary slot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Aaaaand. S'S stopped working. Uninstalled, reinstalled and the same. Technology fails me.
New Song said:
Aaaaand. S'S stopped working. Uninstalled, reinstalled and the same. Technology fails me.
Click to expand...
Click to collapse
What are you trying to flash? PAC isn't going to work, it's cm based. You can only flash touch wiz based roms
Sent from my Nexus 5 using XDA Free mobile app
Anything else. I have Gravitron zip ready to go. But I cannot even get S'S to open now. "SafeStrap has stopped working". Even after attempted reinstalls. If there was someone here local I could just delegate this to, I would.
New Song said:
Anything else. I have Gravitron zip ready to go. But I cannot even get S'S to open now. "SafeStrap has stopped working". Even after attempted reinstalls. If there was someone here local I could just delegate this to, I would.
Click to expand...
Click to collapse
You probably have to use Odin to re-flash nb1 and start over
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You probably have to use Odin to re-flash nb1 and start over
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That may be. Got safestrap to start working by using se linu mode changer. Still stuck at updating partition details. Gonna start a thread on that I think. Maybe one on the search functions too.
New Song said:
That may be. Got safestrap to start working by using se linu mode changer. Still stuck at updating partition details. Gonna start a thread on that I think. Maybe one on the search functions too.
Click to expand...
Click to collapse
Just as an FYI, I've had very good results with Golden Eye installed via SafeStrap. No problems with it, whatsoever, in my experience. That being said, I'm tired of being restricted to touchwiz ROMs so I've bought a T-Mobile S4 (unlocked SIM/Bootloader) and will be selling my ATT one soon.
Marc
Frankenscript said:
Just as an FYI, I've had very good results with Golden Eye installed via SafeStrap. No problems with it, whatsoever, in my experience. That being said, I'm tired of being restricted to touchwiz ROMs so I've bought a T-Mobile S4 (unlocked SIM/Bootloader) and will be selling my ATT one soon.
Marc
Click to expand...
Click to collapse
Starting to feel the same way. Flashing this sgh-i337 is turning out to be quite an infuriating ordeal. So much conflicting info. Allllll these ROMs available for S4, it seems. But they don't work because this version isn't compatible. And the Tw ones I've tried ALL DAY are not working either. Granted, I was not using SS correctly initially, but now that they are successfully loading in the stock slot are not working. Graviton never boots, stays on the ouroboros snake screen. Imperium has no data or wifi etc (i9505 rom? I tried it as it said it was verified working 9th i337. Nope. Figured it was a problem when it said i9505 on my model). Goldeneye, actually can connect, wifi etc. But when I change settings in Wanam, it does not take them (after reboot). Had all the other connectivity issues until I flashed a patch. Also, I was pretty happy to see than I could activate hotspot. But my device was nowhere to be found by other devices. Modules, kernals, patches, oh my... out of all the tutorials for S4's on the wide wide world of internets, nothing seems to fly. This must be the red headed bastard child of Android.
I know it is all user error, but can nothing be simple?
Just want a simple rom and hotspot. That looks awesome. Hrm.
About to try this GE download. GE-XXUGNG4-37.zip. I tried the later NG-8-38 version last time. And yes, I did the ST update at&t module update previously.
Great googley moogley! I think he's finally got it, folks! Ooooh. Niiice. So smooth. Roomy!
This hacking biz ain't for the faint of heart. Thanks guys!!! MUCH APPRECIAT3D! :good:
Paraphrasing, I think, Tom Hanks
"It's suppose to hard, the hard is what makes it great. If it wasn't hard, everyone would do it."
:good:
rugmankc said:
Paraphrasing, I think, Tom Hanks
"It's suppose to hard, the hard is what makes it great. If it wasn't hard, everyone would do it."
:good:
Click to expand...
Click to collapse
Avoid the clap.... Jimmy Dugan.
Hey that's good advice kid....