im sorry if this question is in the wrong location!! move it if it is!
right, so basically i got a new note 4 on contract around 2 weeks ago now, android 4.4.4, model sm-n910f and one of the first things i tried doing was rooting as ive already rooted my s4, but after odin finished, my phone would only say something about seandroid not enforcing, ive since managed to get samsung to replace my phone as its under 28 days from when i took my contract out, and i keep getting the urge to try and root again.
the first time i tried, im 99% sure i followed chainfires instructions, and it didnt work, but that could well be me doing something wrong!! can anyone help me??
just read that im not allowed to post here! sorry!!
snazeh said:
im sorry if this question is in the wrong location!! move it if it is!
right, so basically i got a new note 4 on contract around 2 weeks ago now, android 4.4.4, model sm-n910f and one of the first things i tried doing was rooting as ive already rooted my s4, but after odin finished, my phone would only say something about seandroid not enforcing, ive since managed to get samsung to replace my phone as its under 28 days from when i took my contract out, and i keep getting the urge to try and root again.
the first time i tried, im 99% sure i followed chainfires instructions, and it didnt work, but that could well be me doing something wrong!! can anyone help me??
just read that im not allowed to post here! sorry!!
Click to expand...
Click to collapse
Did you download the exact files for your N910x Model? did u installed Samsung drivers? did you unzip the file correctly? also did you read Odin instructions?
Yeah well I thought I did but I guess not! I unzipped with winrar, put my phone in download mode with usb debugging enabled, and pressed start, but then odin was saying failed and I was getting 'seandroid is not enforcing' and them phone turns of and 2 seconds later turns itself back on and keeps doing that!
snazeh said:
im sorry if this question is in the wrong location!! move it if it is!
right, so basically i got a new note 4 on contract around 2 weeks ago now, android 4.4.4, model sm-n910f and one of the first things i tried doing was rooting as ive already rooted my s4, but after odin finished, my phone would only say something about seandroid not enforcing, ive since managed to get samsung to replace my phone as its under 28 days from when i took my contract out, and i keep getting the urge to try and root again.
the first time i tried, im 99% sure i followed chainfires instructions, and it didnt work, but that could well be me doing something wrong!! can anyone help me??
just read that im not allowed to post here! sorry!!
Click to expand...
Click to collapse
http://galaxynote4root.com/galaxy-note-4-root/how-to-root-galaxy-note-4-using-cwmtwrp-method/ROOT
Good luck! And...use search on the forum for your qualcomm device or ask your best friend google
Sent from my SM-N910C using XDA Free mobile app
Thanks for the link, but will this work for build number ktu84p.n910fxxu1ank4? 90% of the tutorial for rooting the sm-n910f are for another build number?
Related
so heres the story... this is my first post on the site. although i have been using the site for awhile. i guess i just never had any info to offer, but now i ask for some help from you guys. i have a captivate (hence me posting here) and have put in a couple of new roms before (some being harder than others to do) and luckily from other posts i have been able to do it by myself. wow getting long. but anyways i was redoing my phone the other day and it just went downhill fast. but now im in froyo 2.2 and cannot root or anything. im getting "signature verification failed" or something along those lines and cant seem to do anything. i have flashed using every flash kit available and nothing seems to work. im not sure if im missing something or not. So i guess my question here is for a link or some step by step directions. i dont have tons of time to work on it because im in the military and work like 12 - 14 hour days.... now that thats over. sorry for the long post. oh and the 3 button trick doesnt work for me so i bought a jig for download mode. but no worries there. anywho. thanks in advance.
It sounds like you're running into the 3e recovery fix bug. There's a sticky in the Development section that mentions a fix for that.
The other option is to flash to Gingerbread via Heimdall/Odin, which would take care of that problem.
Those would be my first two suggestions for your situation.
cal5202 said:
so heres the story... this is my first post on the site. although i have been using the site for awhile. i guess i just never had any info to offer, but now i ask for some help from you guys. i have a captivate (hence me posting here) and have put in a couple of new roms before (some being harder than others to do) and luckily from other posts i have been able to do it by myself. wow getting long. but anyways i was redoing my phone the other day and it just went downhill fast. but now im in froyo 2.2 and cannot root or anything. im getting "signature verification failed" or something along those lines and cant seem to do anything. i have flashed using every flash kit available and nothing seems to work. im not sure if im missing something or not. So i guess my question here is for a link or some step by step directions. i dont have tons of time to work on it because im in the military and work like 12 - 14 hour days.... now that thats over. sorry for the long post. oh and the 3 button trick doesnt work for me so i bought a jig for download mode. but no worries there. anywho. thanks in advance.
Click to expand...
Click to collapse
So like the guy said above there is a fix for the error it sounds like you are having. But it is terribly annoying to see this thread pop up what seems like every day. There is a thread at the top of this forum. It is called The Captivate Directory |Guides|ROMs|Themes|Etc.| READ BEFORE POSTING(Updated 9/7/11)
And in that thread is this thread [RECOVERY] 3e Recovery Modded w/ No Verification. As well as this thread: How to Flash a ROM
Here is the link, and for the future: READ BEFORE POSTING
http://forum.xda-developers.com/showthread.php?t=887525
the one i saw in development page required you to be rooted. or at least i think. i dont know of a way to change the /system/bin/recovery file... and flashed to gingerbread a couple of times. still no go
cal5202 said:
so heres the story... this is my first post on the site. although i have been using the site for awhile. i guess i just never had any info to offer, but now i ask for some help from you guys. i have a captivate (hence me posting here) and have put in a couple of new roms before (some being harder than others to do) and luckily from other posts i have been able to do it by myself. wow getting long. but anyways i was redoing my phone the other day and it just went downhill fast. but now im in froyo 2.2 and cannot root or anything. im getting "signature verification failed" or something along those lines and cant seem to do anything. i have flashed using every flash kit available and nothing seems to work. im not sure if im missing something or not. So i guess my question here is for a link or some step by step directions. i dont have tons of time to work on it because im in the military and work like 12 - 14 hour days.... now that thats over. sorry for the long post. oh and the 3 button trick doesnt work for me so i bought a jig for download mode. but no worries there. anywho. thanks in advance.
Click to expand...
Click to collapse
Here is a detailed signature verification discussion http://forum.xda-developers.com/showthread.php?t=1052991
---------- Post added at 04:12 AM ---------- Previous post was at 04:09 AM ----------
capocaccia said:
So like the guy said above there is a fix for the error it sounds like you are having. But it is terribly annoying to see this thread pop up what seems like every day. There is a thread at the top of this forum. It is called The Captivate Directory |Guides|ROMs|Themes|Etc.| READ BEFORE POSTING(Updated 9/7/11)
And in that thread is this thread [RECOVERY] 3e Recovery Modded w/ No Verification. As well as this thread: How to Flash a ROM
Here is the link, and for the future: READ BEFORE POSTING
http://forum.xda-developers.com/showthread.php?t=887525
Click to expand...
Click to collapse
C'mon.........go easy. Dont bold at people who admit they are clueless. Sometimes searching to find the exact answer, when your dear little phone is not working right can be a real stressful thing. Especially, if he does not even understand the problem.
As stated above, this seems to be the 3e recovery bug. As for a solution, if your trying to root and flash things, instead of using the fix, I would just flash a GB rom. The only risk with this option is flashing GB boot loaders, but it's hard to make a mistake if you've done a little research
My wife has a Droid 3. She's had it for a year and just recently had some problems. Long story short, we ended up getting a warranty like new replacement phone. I need to put the old phone back to stock. I'm not too familiar with Motorola phones (I mainly own and work with Samsung Androids). I've been looking through threads but am having a tough time making heads or tails of how to put this thing back to stock. Some of the threads I've found are a little older with outdated links. Can someone please point me in the right direction here with some good directions? Thanks much!
SOTK said:
My wife has a Droid 3. She's had it for a year and just recently had some problems. Long story short, we ended up getting a warranty like new replacement phone. I need to put the old phone back to stock. I'm not too familiar with Motorola phones (I mainly own and work with Samsung Androids). I've been looking through threads but am having a tough time making heads or tails of how to put this thing back to stock. Some of the threads I've found are a little older with outdated links. Can someone please point me in the right direction here with some good directions? Thanks much!
Click to expand...
Click to collapse
quickest and easyest is to sbf..
first go to settings/about phone and see what the system version is... .890 or .906
the clcick the link in my sig..
if your on. 890 download the. zip at the top of the thread and install that using rsdlite
if your on. 906 download the 1click .exe file and follow the directions..
ovelayer said:
quickest and easyest is to sbf..
first go to settings/about phone and see what the system version is... .890 or .906
the clcick the link in my sig..
if your on. 890 download the. zip at the top of the thread and install that using rsdlite
if your on. 906 download the 1click .exe file and follow the directions..
Click to expand...
Click to collapse
Thanks, much! That worked like a champ and was exactly what I was looking for!
I may have spoke too soon; it just stays at the Motorola Dual Core boot image. Maybe I am not waiting long enough? I waited for like 9 minutes and no booting. I used the one click after checking the version. In the script, I got "okays" for everything. The phone rebooted. Everything seemed to go fine. So, not sure what's up. As I said, maybe I didn't give it enough time?
Sent from my Galaxy Nexus using Tapatalk 2
SOTK said:
I may have spoke too soon; it just stays at the Motorola Dual Core boot image. Maybe I am not waiting long enough? I waited for like 9 minutes and no booting. I used the one click after checking the version. In the script, I got "okays" for everything. The phone rebooted. Everything seemed to go fine. So, not sure what's up. As I said, maybe I didn't give it enough time?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Seems like it soft bricked ( which is fixable ).
Im just a lurker so im not sure how to fix lol
post your first terrifying experience( which you thought your phone is dead) with installing a costume ROM or rooting
I decided to follow advice on a blog about changing the text file build.prop to have longer battery life and faster internet, etc.
Well that sent my phone into infinite boot loop.
I had to download the stock rom from the internet and relash.
Whatever, lesson learned, don't mess with build.prop
All my pics and videos are on sd card so I didn't lose anything (app data is in the cloud)
Installing Android on my old HD2. It was a branded device so there was no updated radio available after the first factory release. As such, bricked it.
Freaked me right out, couldn't sleep for a week. To this day I still don't know how I managed to bring it back to life. It may have involved a few very creative solutions, and in the end it was a toss-up between seeing if there was a Wiccan spell for it, or taking a hammer to the bloody thing.
Needless to say, neither worked. I don't know what worked (And at this point I'm not sure I want to know) but something did. Alas, it's still stuck on wm6.5.
And don't ask me how it survived the hammer.
My first terrifying experience?
Well then.
I was goofing around with my phone, and then I decided to upgrade to Lollipop. Obviously, I wanted it rooted. So, I went to have a look at some root solutions. Then, I dun goofd because I was a dum dum back then (I know I know) and I bricked my baby.
I went catatonic and I was about to jump out of the window (no, I wasn't, overexaggerating there) and I thought to myself - can I revert to stock? So I started scouring the forums for some solutions, and I found one. (flashing a TOT or KDZ, don't remember which one.) so 30 minutes later, I followed the instructions successfully, but - (surprise surprise,) I dun goofd again.
I yanked out the USB too soon, but...
IT WORKED AND I HAVE MY PHONE BACK
Now I'm not afraid of bricking ?
Sent from my D855 running CloudyG3 2.3 with Gabriel5 kernel.
Don't forget to smash that thanks button if I, or someone else helps you, guys!
got stuck at 98% while flashing MIUI 6. lol.
for a while, i was shocked.
Well.
Mt first terrifying experience was with my galaxy pocket:i soft-bricked it with a ROM,only download mode was working,so ODIN helped me
The most terrifying with my G3:i made a battery pack and tried to connect it to my G3. It was not working so i swapped the connections(+ with - and so on). Most stupid thing i've ever done. Almost broke my OTG module
First terrifying moment is when my razr brick coz try to apply lollipop cm 12. Failure because wrong twrp...
Need 3 months to revive with factory cable from china.
1 week from that, my razr was broken... Because dropped from my pocket when i ride a motorcycle....
That's so bad......
Sent from my HTC DNA using XDA Premium mobile app
flash- said:
post your first terrifying experience( which you thought your phone is dead) with installing a costume ROM or rooting
Click to expand...
Click to collapse
***ignore***
Sorry posted something off topic!
Sent from my SM-G900F using XDA Free mobile app
i decided to update zenfone 2.But my zenfone was from CN and i didn't know that.Installing ww otas failed everytime.Then i decided to wipe cache in stock recovery.after 5 mins it didn't finished so i decided to shutted down.after this phone entered only in fastboot.but my pc didnt recognize phone in fastboot.did a driver mess and then it worked.i converted phone from cn to ww
I have a terrifying experience while using my phone. I though it has gone for forever. But when took my phone for servicing it looks okey. No problem at all their.
Opening this thread bricks my phone. :/
JetSoJet said:
Transfer iPhone 5 data to iPhone 6.... worst ever
Click to expand...
Click to collapse
Why are you even posting about this here. iPhones have no place here ??
Sent from my D855 running CloudyG3 2.3 with Gabriel5 kernel.
Don't forget to smash that thanks button if I, or someone else helps you, guys!
Mevolent said:
Why are you even posting about this here. iPhones have no place here ??
Sent from my D855 running CloudyG3 2.3 with Gabriel5 kernel.
Don't forget to smash that thanks button if I, or someone else helps you, guys!
Click to expand...
Click to collapse
They have place in the bin or on the shelf™
Inviato dal mio LG-D855 utilizzando Tapatalk
AT&T released 5.1.1 a couple of weeks ago, and I still haven't gotten a notification on my phone that the OTA update is ready to be installed. I check manually every day, too, but every time it says that the "update was interrupted" and I have to wait 24 hours. Is that because the server is busy and I'll just have to wait patiently as the update is being rolled out to AT&T phones over the air? (Yes, I know I can simply move the date forward one day and try again manually, but I don't want to inadvertently mess up the automatic OTA checks.)
I would really like to install 5.1.1 on my S6. Is there a way to speed things up? Is there an official AT&T image I can install through Kies or some other way?
Thanks!
--Ron
Make sure you have at least 4GB of storage free when you try the update. I have heard of this sort of thing happening if you don't have enough free space.
I had read that, too, but I have a 64 GB S6, with some 30 GB free, so that's not an issue.
Same here
i'm not sure why i'm not getting the update...i have an unlocked galaxy S6 at&t version.
i'm living outside the US so i'm using another sim card. Is that the problem?
I also have an unlocked AT&T S6, but I live in the U.S., so that shouldn't be an issue either.
--Ron
I know the feeling. I have been checking daily too and finally got it late last night.
Does root effect updating from SmartSwitch?
Still nothing (10/13). Is anyone else seeing the same thing? Should it really take weeks and weeks before we get this update after it's been officially released?
--Ron
Dude just flash the damn thing using odin and be at peace
How?
timde9 said:
Dude just flash the damn thing using odin and be at peace
Click to expand...
Click to collapse
how I do? I download the correct file, I followed all the steps and do not work for me. I get FAIL in Odin. If someone could help me, please
Is there an *official*, AT&T-sanctioned image that I can use? Will this trip Knox?
--Ron
Is it the one in this thread: http://forum.xda-developers.com/att-galaxy-s6/general/stock-odin-tar-files-g920aucu3boi2-t3213306
--Ron
Don't know what to tell you other than the basics.. The correct file is available in the android developnent portion of this forum.. Download make sure you put all four files in proper slots in odin and hit start.. Should wipe everything and complete unless you using the wrong model of s6 or the wrong files in the slots.. Honestly nothing is worth losing root though in my opinion.. I only want 5.1.1 so I can use. Xposed but without the ability to root the update is meaningless to me and really more of a regression to me.. But no it won't trip knox
timde9 said:
Don't know what to tell you other than the basics.. The correct file is available in the android developnent portion of this forum.. Download make sure you put all four files in proper slots in odin and hit start.. Should wipe everything and complete unless you using the wrong model of s6 or the wrong files in the slots.. Honestly nothing is worth losing root though in my opinion.. I only want 5.1.1 so I can use. Xposed but without the ability to root the update is meaningless to me and really more of a regression to me.. But no it won't trip knox
Click to expand...
Click to collapse
I downloaded the correct file, unzipped and I did these 4 files, which put in its proper place and time to flash the firmware gives me error.
I'm in the OF4 version and have not received the update by air today. I restored the phone several times to see if I update and nothing appears. I searched around in various forums and can not find the solution
I bought the galaxy used and I'm not sure if the USB cable is original. Anyway, I've tried other cables and various USB ports. The last thing I did was to restore the PC and start from scratch ... it still did not work for me
I am very good at following tutorials. I have not damaged a phone or electronic equipment and has not gone bad in the process, I always get everything right, but it is the first time you see me in this situation where I can not find the solution
I think it's the cable. Anyway, where I live not sell the USB cable separately. Buy by amazon and I'm waiting for it to arrive, but if not the USB cable and anyone knows anything please help me
Make sure you. Put phone in download mode. I overlooked that when I was a noob
Finally bit the bullet and just flashed the 5.1.1 update using Odin. Very smooth process. My phone is running 5.1.1 now. And with Google automatic backup, it didn't even take that long to set up my phone again.
--Ron
Before coming across the link in this forum here at http://forum.xda-developers.com/not...y-steps-n910t3-dofc-dog1-how-to-root-t3177225 ...
I thought I could shortcut all the work by going to the auto root chainfire site to download the actual CF Auto Root File for model sm-n910t3. I successfully flashed that file using odin. It went into a bootloop and then I freaked out.
The error messages when I turn on the phone first show
"kernal is not seandroid enforcing" in red, and
"Set Warranty Bit: kernal" in yellow writing.
After being in this bootloop i went to the link posted above and followed each step by step. My phone is successfully rooted now and I can log in to my phone fine. However, there are two problems. First, those error messages are still there. How do I get rid of that? I tried a factory reset on my phone and it wont do it.
Will get to that after. Second, when I go into twrp by hitting volume up+home+power, once im in there it wont allow me to backup my current rom. It says an error message about E:/ data mount or something like that. And also while in twrp it won't let me factory reset my phone. So the recovery program is pretty useless to me. I don't know why it doesn't work properly.
Where do I go from here? Can someone help me out in fixing this error message and getting a recovery program to work? I'm just wondering why the twrp that I flashed while following that root guide above does not work. Has anyone ever encountered those two error messages while turning on their phone? Thanks.
The error messages are normal after rooting.
Sent from my SM-N920T using Tapatalk
mrfordwrench said:
The error messages are normal after rooting.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
So other people have those messages on the top of their phone after rooting this device? Im guessing we just ignore that message then? I thought it was there because I flashed the wrong kernal before doing it the right way and following the forum...
What if I flashed the original firmware for this note 4 phone that I have a copy of, then root the phone going through that tutorial step by step? Wouldn't that get rid of the error messages? And my twrp would work then?
Im not able to make a backup of my current rom. And Im not even able to factory reset this phone. This is a problem for me since I want to put marshmallow on here soon. When I do I get an error message. Part of my second question is wondering why twrp isn't working correctly?
please help
i took my battery out to charge it and put a new one in. now it wont even boot up. it turns on and says
"custom binary blocked by FRP"
"secure fail: kernal"
for those of you who followed my other post i rooted my phone and tripped knox. phone was giving a message but would still turn on. where do i go from here? i have everything backed up and can start fresh. please provide step by step instructions on how i can fix this phone. thank you so much in advance and god bless.
I went to samsung and downloaded the firmware for this device and then flashed it. Now it's back to normal so you can disregard my post. Thanks guys.
scary
areininger30 said:
I went to samsung and downloaded the firmware for this device and then flashed it. Now it's back to normal so you can disregard my post. Thanks guys.
Click to expand...
Click to collapse
#UberNoob Drink your ovaltine. You should probably get an iPhone.
Everything worked as expected you are just so inexperienced you just gave us a play by play of your ignorance and then went running scared from the fear of 2x hello worlds and the unknown right back to momma Samsung. Good post
V3racious said:
#UberNoob Drink your ovaltine. You should probably get an iPhone.
Everything worked as expected you are just so inexperienced you just gave us a play by play of your ignorance and then went running scared from the fear of 2x hello worlds and the unknown right back to momma Samsung. Good post
Click to expand...
Click to collapse
Easy dude, that's not how things are done around here.
Ubernoob?
Drink my ovaltine? Hash tag for uber noob? Didn't your parents raise you to not say something if you have nothing nice to say at all? Apparently not so who's really the ignorant. Ask yourself that question. Ignorance is bliss. That's a good hashtag huh.
And the bottom line is that we were all beginners at one point right? So cut me some slack im learning. It will take me time to get to where you guys are at. Yes I am brand new to this stuff and no I don't like the iphones. Androids are more user friendly. I like Samsung phones and want to learn more about them.
Its people like you that keep us beginners from wanting to come back to this website, when guys say blatantly rude comments. It shouldn't be a bashing forum. Let's all chill and get along.
areininger30 said:
Drink my ovaltine? Hash tag for uber noob? Didn't your parents raise you to not say something if you have nothing nice to say at all? Apparently not so who's really the ignorant. Ask yourself that question. Ignorance is bliss. That's a good hashtag huh.
And the bottom line is that we were all beginners at one point right? So cut me some slack im learning. It will take me time to get to where you guys are at. Yes I am brand new to this stuff and no I don't like the iphones. Androids are more user friendly. I like Samsung phones and want to learn more about them.
Its people like you that keep us beginners from wanting to come back to this website, when guys say blatantly rude comments. It shouldn't be a bashing forum. Let's all chill and get along.
Click to expand...
Click to collapse
Good for you. If you need anything further, please don't hesitate to ask. There are a lot of great, talented and humble people on here, who would be glad to help.