Greetings, fellow Mega-Maniacs!
I am currently working with dev Geohot to get us root access for the SGH-I527 with Baseband Version I527UCUBNE7. All known root methods have been tested and proven to not work with this version of android with this baseband, due to the extremely locked down nature of Samsung Knox on this device.
I, personally, have been throwing every exploit I can think of at this device, to no avail. As of the time and date of this post, we have a donor ready to help the cause (Special thanks to caguas56). That is why I'm proposing a bounty on root access for this phone (SGH-I527 AT&T US version only, although there is a high possibility that it'll work on the Sprint,T-Mo and VZW variant).
The first developer who can successfully get ROOT on KitKat with baseband I527UCUBNE7 and demonstrate this with a successful public test will be awarded the bounty. The bounty will be split equally between devs and donors willing to team up.
I'm in for $10 at the moment, and I'll piss away more if needed down the line.
Who else is in? LETS GET THIS DONE, PEEPS!
Please, only posts regarding root access on this thread. For firmware rollbacks to 4.2.2, see azpatterson3's thread located HERE
kmt5150 said:
Greetings, fellow Mega-Maniacs!
I am currently working with dev Geohot to get us root access for the SGH-I527 with Baseband Version I527UCUBNE7. All known root methods have been tested and proven to not work with this version of android with this baseband, due to the extremely locked down nature of Samsung Knox on this device.
I, personally, have been throwing every exploit I can think of at this device, to no avail. As of the time and date of this post, we have a donor ready to help the cause (Special thanks to caguas56). That is why I'm proposing a bounty on root access for this phone (SGH-I527 AT&T US version only, although there is a high possibility that it'll work on the Sprint,T-Mo and VZW variant).
The first developer who can successfully get ROOT on KitKat with baseband I527UCUBNE7 and demonstrate this with a successful public test will be awarded the bounty. The bounty will be split equally between devs and donors willing to team up.
I'm in for $10 at the moment, and I'll piss away more if needed down the line.
Who else is in? LETS GET THIS DONE, PEEPS!
Please, only posts regarding root access on this thread. For firmware rollbacks to 4.2.2, see azpatterson3's thread located HERE
Click to expand...
Click to collapse
In for at least $20.
Put me down for 2 bucks.
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
DarkAngel said:
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
Click to expand...
Click to collapse
Bootloader is locked
So no recovery flashing
Sent from my GT-I9205 using XDA Free mobile app
Grarak said:
Bootloader is locked
So no recovery flashing
Sent from my GT-I9205 using XDA Free mobile app
Click to expand...
Click to collapse
Well technically all bootloaders are locked (except for the few that aren't) but I take it AT&T is wanting/trying to join the band wagon with Verizon and locking the bootloaders indefinitely by encrypting them on all the devices they can now.
Sorry then, my method will not work straight forward. Good luck. :good:
DarkAngel said:
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
Click to expand...
Click to collapse
Believe me, we have tried it all. I have tried a process similar to this and when the phone got done with all the flashing and went to boot up, I got a prompt that said 'We have detected software not approved for use by AT&T. Please take your phone to an AT&T store for assistance.' It also says Secure Check Failed: Kernel. I had to send my phone to sammy to get it fixed since I tripped a few flags. Should be back by Friday the 10th.
Possible to use this method with 4.4 kernel from mega?
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
jstinger9489 said:
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
Click to expand...
Click to collapse
Will definitely try this again when my phone gets here tomorrow and post updates...
jstinger9489 said:
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
Click to expand...
Click to collapse
Tried and my device still won't act right, can only get into download mode. recovery is gone and when i attempt to power on, I get a msg about Secure fail: Kernel and then a yellow triangle with a ! says 'System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nesrest AT&T store for help."
UPDATE: A buddy of mine has a JTAG service and I'm going to send it to him for repair. UGH! I'm selling this sonofabitch. I should NOT have to go thru this much bull**** just do modify something I paid 500 bucks for without a contract.
kmt5150 said:
Tried and my device still won't act right, can only get into download mode. recovery is gone and when i attempt to power on, I get a msg about Secure fail: Kernel and then a yellow triangle with a ! says 'System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nesrest AT&T store for help."
UPDATE: A buddy of mine has a JTAG service and I'm going to send it to him for repair. UGH! I'm selling this sonofabitch. I should NOT have to go thru this much bull**** just do modify something I paid 500 bucks for without a contract.
Click to expand...
Click to collapse
Have you tried towel root
http://towelroot.com/
BarakOsama said:
Have you tried towel root
http://towelroot.com/
Click to expand...
Click to collapse
Have YOU tried towelroot?
Or have you not read any of the many theads on the subject?
Sorry, not trying to be rude, the same thing has been said so many times
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Can anyone send me boot.img of ATT KK rom?
captemo said:
Have YOU tried towelroot?
Or have you not read any of the many theads on the subject?
Sorry, not trying to be rude, the same thing has been said so many times
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
My bad..
Alright.
To summarize for people who haven't paid attention. Phone was bricked in a last ditch effort to flash back to 4.3 because the 4.4 update made my phone run like s#it. I also have an S4 Active and the service sucks harder than it already did. The 4.4 update makes the S4 drop out constantly and the battery life blows. Samsung told me to run kies in download mode to get it back to 4.3 I did and BOOM, now phone is fu©k!ng bricked and they won't fix it, claiming it's 'rooted' because the kernel says it's version 3 when it's supposed to be at 4 for kitkat. Fu©k!ng duh, you jerks made me flash it back. I am personally never buying another samsung product again because their customer service was horsesh!t. I happen to have a sammy tv, blu ray, home theater and 2 of their former 'top end' phones, but now I'm ditching them. They can lick my scrotum for all I care anymore.
end rant, back to music.
SCH-R960
I have the US Cellular Galaxy Mega SCH-R960 also updated to 4.4.2 out of the box. I am in for some bucks if you can apply this to my version also the baseband number is R960TYUBNF1, I will send you whatever info you need from the phone. Lets get this done! Thank you!
MeatHammer311 said:
I have the US Cellular Galaxy Mega SCH-R960 also updated to 4.4.2 out of the box. I am in for some bucks if you can apply this to my version also the baseband number is R960TYUBNF1, I will send you whatever info you need from the phone. Lets get this done! Thank you!
Click to expand...
Click to collapse
Can you make a complete firmware dump and compile a .PIT file?
No root.
I do not have root so I can not do those things. If there is a way without root please point me in that direction. Thanks
MeatHammer311 said:
I do not have root so I can not do those things. If there is a way without root please point me in that direction. Thanks
Click to expand...
Click to collapse
sure you can
use heimdall
and can anyone send me the boot.img now?
I don't even think you guys want root if you're not even trying to help
Grarak said:
sure you can
use heimdall
and can anyone send me the boot.img now?
I don't even think you guys want root if you're not even trying to help
Click to expand...
Click to collapse
tell me how to get it any you will have it 1 before 5pm today est.
also here is the pit file you asked for. I used it to unbvrick my phone a few times with odin.
ita for the at&t version
Related
This guide will enable you to easily root your phone in 6 steps. I've taken out the mystery and complications.
1) Go to HTC Dev site and manually unlock your bootloader. Select "register" and create your account.
1a) After you are registered select "all other supported models" in the pull down box
1b) Click "begin unlock bootloader". it will ask "are you sure" yes of course you are. acknowledge legal terms. then continue.
1c) Ignore the battery pull instructions as we can't pull the battery. hold down the power key and the volume down key until the bottom buttons stop flashing and your phone shuts off (don't worry if you take a screenshot. It happens all the time). then release ONLY THE POWER BUTTON. Keep holding the volume down key until the bootloader screen shows up.
1d) Follow "step 3" and the rest of the instructions as listed on the HTC site to unlock your bootloader manually.
2) Install android ADB/SDK on your pc. This video shows how to do it nicely:
2a) ****NEW UPDATED 03/05/13*** Alternatively if you DON'T want to install ADB/SDK you can just download the NON-FLASHABLE platform-tools.zip file located in my dropbox folder here.
Just extract this folder to your desktop using WINZIP or whatever archive tool you use and proceed to step 3.
3) Open a command line in your "platform-tools" folder by holding shift+right click anywhere within the folder and selecting the menu option "open a command window here". Then click here to install TWRP using fastboot. Follow the "Download - Fastboot Method:" instructions.
3a) If your phone isn't detected by windows please install the proper USB drivers for your operating system. Go here for 32bit. Go here for 64 bit.
4) Flash SuperSu and Busybox on your device:
4a) Click here and download the latest version of SuperSu. save it to your sdcard.
4b) Go to my dropbox and download Busybox 1.20.2 and save it to your sdcard.
5) Reboot into recovery (via the bootloader selection)
6) Flash the SuperSu zip and the Busybox zip listed in 4a and 4b
That's it!
"So now what?" you may be asking.
You are now free to flash ROMs that support s-on.
Two are my favorites are
(1) Stock with Goodies. (my personal favorite and the one I use today). This is a great ROM for beginners and people who prefer a slimmed down ROM (minus the bloat) and lots of free memory!
(2) Viper4G. This is a ROM for more experienced users and offers TONS of customization.
You can also run apps from Google play that required ROOT access!
If you're feeling slightly adventurous you can flash a custom kernel (which will allow you to overclock your phone). Two of the kernels I use are:
(1) ElementalX by flar2. Click here to take a trip over there. This one is especially important to flash as it seems HTC was up to shenanigans with the latest HBoot (2.09).
If you're unlucky enough to have HBoot 2.09 they have RESTRICTED access to your /system partition. What does this mean to you? It means that if any app writes to your /system partition (ROOTED or not) the phone will "panic" and reboot. Shady behavior if you ask me. The solution? Flash this kernel! it will give you write access so that everything works properly.
(2) The Arc-Reactor kernel! This one is for people that are s-off (see below for an explanation of s-off) only! It's the kernel I currently use and is the fastest kernel out there! Highly recommended if you decide to go s-off!!!
If and when you're feeling more adventurous you can go "s-off" (security off) which removes any security limitations of your phone. It makes flashing ROMs and updating firmware a lot easier. You can find out about s-off by taking a trip over to the DirtyRacun thread here. I will NOT walk you through this process. They will totally help you on their IRC channel. Just read post # 1 in that thread.
There's also a new method of s-off which literally takes 2 minutes. It's called facepalm and is located here But is NOT for the feint of heart, bad typers, nor people that cannot follow instructions! Why? One typo here and your phone is a brick. A paperweight. Useless. Well...you can recover...but that's not the purpose of this thread. If you DO brick your phone PM me. I'll help you out.
I take NO credit for any of this. It's all out there to learn I just put it all together. In one spot. Any questions feel free to PM me.
If I helped you out hit the THANKS button...or buy me a beer! Either way lol!
Tested and works with 3.16.651.3 (even if you took the OTA and have hboot 2.09 and are s-on)
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
lancemoreland said:
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
Click to expand...
Click to collapse
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
rawintellect said:
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
Click to expand...
Click to collapse
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
lancemoreland said:
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
Click to expand...
Click to collapse
Indeed this is a well documented problem but really not what this thread is about. Perhaps you can check out THIS thread where they are discussing this issue at length and hopefully they will come up with a solution for it?
http://forum.xda-developers.com/showthread.php?t=1538053
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
rawintellect said:
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
Click to expand...
Click to collapse
Yes I am participating in that thread. Chainfire is looking for a work around for his specific app, other apps that write to the system partition will no longer work. The point is that with Hboot 2.09 there are limitations and we will not enjoy full root as we have before when we were s-on.
Updated with an alternative superuser program.
SuperSU would ask to update binary and then just reboot. This fixed my problem for being able to access/deny and turn off messages. However it did not uninstall superSU will this cause a conflict having them both?
Edit: Okay I am dumb, I had to uninstall superSU first. Then I reflashed superuser to be able to have root privileges for my apps. When I just reflashed superuser hoping it would get ride of and superuser and keep root it did not.
Thanks it worked!
Help with rooting please.
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
MrSteez said:
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
Click to expand...
Click to collapse
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Updated thread with instructions on manually uninstalling supersu first before installing superuser 3.2
Thank you very much!
rawintellect said:
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Click to expand...
Click to collapse
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
MrSteez said:
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
Click to expand...
Click to collapse
yes. going back to stock is as simple as this:
(1) Boot your phone into the bootloader. make sure fastboot is selected. if you have the drivers installed correctly your phone will read "fastboot usb"
(2) if you followed my instructions on rooting you have ADB/SDK installed. so issue the command to relock your phone. type: fastboot oem lock
(3) run the RUU for 3.15.651.16. Done. Your bootloader will say *relocked* but it will be 100% stock.
Uh oh
I think i messed up. I did not see busy box installed and SuperSU is not updating.
The file listed in step 6 contains busybox. It also contains supersu. You want to flash the superuser file after flashing the file in step 6. It will overlay supersu with superuser 3.2. There is no need to update superuser 3.2 once you flashed it. It is the latest release.
Sent from my EVO using xda app-developers app
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
mobilecj said:
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
Click to expand...
Click to collapse
I replied to your email. But check my first post on the subject of superuser and how to uninstall supersu. if you need to that is. I tested this myself and it did uninstall supersu for me by just flashing superuser 3.2. Some people have reported this doesn't work for them.
okay sorry just got both i am going to try it now.. Its all knew to me it seemed like the information was explaining a dual process and i only had acquired one problem.. will post back in a few!
JUST THOUGHT I WOULD TOSS THIS UP IF ANYONE NEEDS IT, THERE IS A COPY IN BLOATWARE LISTS !!!
First what version of KIKAT are you on ? If you are on 4.4.4 NH7 or NK4 the latest upgrade then you can root with Chainfires CF-autoroot or his SuperSu v 1.94, v2.02 or 2.40 this will trip KNOX warranty. Towel Root will not work yet for NH7 or NK4. If you are still on 4.4.2 NC5 then you can use Towel Root to root your device, this will NOT trip KNOX warranty. If you root with Chainfires CF-autoroot or his SuperSu v 1.94 or v2.40 this will trip KNOX warranty on NC5. If you want odin flash a fresh copy of 4.3 NAB, 4.4.2 NC5, or 4.4.4 NH7 here is micmars link http://forum.xda-developers.com/showthread.php?t=2712205 or rpenrod23 [ odin ] (mirrors )http://forum.xda-developers.com/showthread.php?t=2522638 for NK4 and OC5 you will need to go here http://www.sammobile.com/firmwares/ . Make sure you have USB drivers installed on your PC here is the link http://www.mediafire.com/download/ti6xeoh2lx79zis/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
How to flash a fresh copy of a stock OS
1. download the version of KitKat you want to the desktop of your PC.
2. extract zip file to the desktop of your PC it will turn it into a .tar file
3. you need to install Samsung drivers on your PC you can get them from here http://www.mediafire.com/download/ti6xeoh2lx79zis/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
4. download odin to your desktop here is the link ( version 1.85 ) https://mega.co.nz/#!oA5xzTAL!LXoVWBVDWN_7SULGPIv6nWx1gCI3ZZlOMSWdRGVX6Uo ( version 3.07 ) http://www.mediafire.com/download/2uxt5u83qxhz6xr/Odin_v307.zip
5. completely power down device, reboot into download mode (hold power button, home button, and volume down button at the same time, then push the volume up button)
6. open odin on desktop, connect device to PC via USB cable COM: will light up in upper left corner of odin doesn't matter what color it is just shows a connection.
7. click the PDA button a box will open click on desktop then on KitKat file to open
8. now don't touch anything else and click start
9. it will take several minutes, then say pass, and automatically reboot device with new OS/ROM ( this will take 3 to 4 min. after you see Samsung logo )
10. Important !!! If the device was rooted or you are trying to downgrade from NH7 or NK4 back to NC5 the device may bootloop on the startup. ( you will know this when the Samsung logo is still on the screen after 6 to 7 min. )
11. to fix bootloop pull battery then reinstall, boot into download mode and use odin to flash the OS/ROM again it will take the second time and boot up.
Let's root the phone, there is a couple of ways. First if you are running NC5 4.4.2 you can download Towel Root directly to the device here is the link http://towelroot.org/ The second way if you are running any version of KitKKat is to use odin to flash the cf-autoroot .tar, just download cf-autoroot here is the link http://autoroot.chainfire.eu/ to your PC desktop and follow the same instructions listed above just use the root file in place of the rom .tar file. Remember to choose the right root file for the version of KitKat you running so you don't trip KNOX !!!
Recoveries, the two popular ones are TWRP and Philz CWM. INSTALLING A RECOVERY WILL TRIP KNOX WARRANTY!!! You need a recovery to flash roms so you need to make choice at this point ? Here is the link to Philz CWM latest version 6.48.4.tar http://forum.xda-developers.com/showthread.php?t=2201860 and TWRP here http://teamw.in/project/twrp2/201 download to desktop or downloads.
I run a stock rooted 4.4.2 NC5 with Philz custom recovery version 6.12.9 hltespr https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltespr/ . The device was rooted and warranty tripped the second day I owned it. I was in a Sprint corporate Store a couple of wks ago. Showed the tech my rooted note 3. He said I can't touch that, I said what if I unrooted the phone. He said no problem, now I can warranty the phone. He didn't care that the KNOX flag was tripped at all 0x1. Just can't be rooted when you bring it in for service. Sprint doesn't care about KNOX only Samsung cares about KNOX. What is KNOX, KNOX is a program that creates secure encrypted containerization of DATA so it can be sent to another location. So, when Samsung paid millions to the NSA to design the KNOX security containerization system, which apparently they won't warranty will work after the device is rooted, than maybe they care. Can you say track and spy on me !!!
Ok lets install a recovery !!!
1. you need Odin on the desktop of your PC here is the link ( version 1.85 ) https://mega.co.nz/#!oA5xzTAL!LXoVWBVDWN_7SULGPIv6nWx1gCI3ZZlOMSWdRGVX6Uo ( version 3.07 ) http://www.mediafire.com/download/2uxt5u83qxhz6xr/Odin_v307.zip
2. you need to install Samsung drivers on your PC you can get them from here http://www.mediafire.com/download/ti6xeoh2lx79zis/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
3. completely power down your device, and boot into download mode (press and hold the power button, volume down button, and the home button at the same time) a new screen will popup then push the volume up button to get into download mode.
4. click on the Odin zip file and extract to desktop, right click and run as administrator
5. with your device in download mode connect it to your pc via usb cable, COM: will light up in the upper left hand corner of Odin doesn't matter what color or number just shows a connection has been made.
6. click PDA box in odin, a box will popup click where ever you have recovery file downloaded, once open it will show up in box next to PDA
7. click start wait till you see pass and success , then your custom recovery is installed.
After the recovery is installed, download a copy of SuperSu to your desktop here is the link http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip to version v2.40 and for SuperSU 2.46 go here http://forum.xda-developers.com/showthread.php?t=1538053 . Then copy and paste to sd card via USB cable. Now the next thing you are going to do is completely power down the device and boot into recovery. (press and hold the power button, volume up button, and home button at he same time) a menu will come up, click on Install Zip, then sd card to install zip and root device. Boot device and verify it is rooted, then power down, and boot into recovery. Click on backup, MAKE A BACKUP OF YOUR ROOTED ROM !!! Then make a backup of EFS file by its self it will show up in your backup file on the sd card or ext sd card depending on where you choose to put it. Copy and paste the efs file someplace safe.
With the Google Play Store download some type of root file manager like ES File Manager or Root Explorer (what I use). Then you can remove/freeze/delete some of the bloatware on your stock rooted rom. Check out this thread on Bloatware removal http://forum.xda-developers.com/showthread.php?t=2770729
OK lets flash a rom !!!
First, you CANNOT flash a rom that is based on an older version of rom you are currently running. EX: If you are on KK 4.4.2 NC5 you can flash a rom based on NAB or NC5 but you CANNOT use a rom based on mj4 or older read the OP thread carefully . You can run AOSP roms as long as they are based on 4.4+. If you are running a KK 4.4.4 based rom, you will need to odin flash a stock lollipop 5.1.1 OS. Then root the lollipop 5.1.1 OS, install a lollipop compatible recovery. Now you can flash a lollipop based rom.
1. install the new rom zip you want to flash on your sd card via usb cable from PC or download directly to device
2. power down phone completely and boot into recovery
3. from the menu find and wipe cache, delvik cache, and wipe system to install new rom, NOT FACTORY RESET !!!
4. go back to menu and click on install zip then click on where you have the zip ( i.e. sd card ) and install this will take a minute or two
5. back to main menu and reboot device this will take several minutes on the first boot of a new rom
6. enjoy your new rom !!!
Lets do a restore from a backup recovery file !!!
1. completely power down device and boot into recovery
2. go to main menu and click on wipe system to install new rom ( no need to mess with the caches on a restore )
3. back to the menu click on back up and restore, then click on the backup file location ( i.e. sd card )
4. now click on restore
5. when its completed reboot device this will install your original rooted stock rom you made a backup for
Eventually you will figure out that you can make several backups and they have really weird numbered time stamps to identify them.
If my instructions are hard to follow you can find root and recovery installation videos here http://galaxynote3root.com/ or http://qbking77.com/ both are excellent sites !!!
Malware in linked odin site
That odin site is complete malware. Its not where you should get odin.
juts said:
That odin site is complete malware. Its not where you should get odin.
Click to expand...
Click to collapse
Thanks, that just happened. Looks like the site has been hacked !!!
jimzweb1 said:
Thanks, that just happened. Looks like the site has been hacked !!!
Click to expand...
Click to collapse
I have a Note 3 locked to Sprint which announce "Invalid SIM card" everytime I get the sim in and of course it doesn't have network. So I have a question 4u that after flashing this ROM am I possible to use the SIM (I'm from VN) ?
3597dxta said:
I have a Note 3 locked to Sprint which announce "Invalid SIM card" everytime I get the sim in and of course it doesn't have network. So I have a question 4u that after flashing this ROM am I possible to use the SIM (I'm from VN) ?
Click to expand...
Click to collapse
No, it's my understanding the device has to be unlocked by sprint. There is an access code to do that, I have seen it just can't remember where. I will do a little searching.
Should make a noob tutorial since people are still confused.
asim.sidz said:
Should make a noob tutorial since people are still confused.
Click to expand...
Click to collapse
I guess if people are still confused, there are a lot of youtube videos that have walk-throughs as to how to root, install recovery, and flash a ROM. Maybe some people might be visual learners?
asim.sidz said:
Should make a noob tutorial since people are still confused.
Click to expand...
Click to collapse
If my instructions are hard to follow you can watch these videos http://galaxynote3root.com/ or http://qbking77.com/ both are excellent sites !!!
Great work Jimmy
Pretty lucid , these tutorials are
great stuff !!!
Cool!
jimzweb1 said:
If my instructions are hard to follow you can watch these videos http://galaxynote3root.com/ or http://qbking77.com/ both are excellent sites !!!
Click to expand...
Click to collapse
Thank you very much! I cannot imagine the process to get any easier than the way demonstrated in the ways that you directed me. Really appreciate it! Thanks again! Keep up the good work and support! :highfive:
I am on 4.4.4 NH7, how can i downgrade to 4.4.2 NC5?
i am facing gps fix issues...so wanted to give it a try. any ideas?
swapyworld said:
I am on 4.4.4 NH7, how can i downgrade to 4.4.2 NC5?
i am facing gps fix issues...so wanted to give it a try. any ideas?
Click to expand...
Click to collapse
You can't and you shouldn't . Flashing nc5 might brick your phone that's why we all believe one should always wait for a few weeks before jumping on a new ota as downgrade is not possible
Sent from my NOTE 3 .. size does matter .......
lord dredd said:
You can't and you shouldn't . Flashing nc5 might brick your phone that's why we all believe one should always wait for a few weeks before jumping on a new ota as downgrade is not possible
Sent from my NOTE 3 .. size does matter .......
Click to expand...
Click to collapse
My phone came with 4.4.4, that's the problem.. I was told it is possible by odin one click method by r wilco?
Sent from my SM-N900P using Tapatalk
swapyworld said:
My phone came with 4.4.4, that's the problem.. I was told it is possible by odin one click method by r wilco?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
First, if your device came with 4.4.4 NH7 it should be possible to down grade to 4.4.2 NC5. However, is the phone new and under warranty ? If so odin flashing back to NC5 won't trip the knox e-fuse, that happens when you install a custom recovery. Here we go, first BACK UP ALL YOUR DATA TO AN EXT SD CARD OR PC !!! ( i.e. pics, music, videos etc.) From my post here is the link for odin https://mega.co.nz/#!oA5xzTAL!LXoVWBVDWN_7SULGPIv6nWx1gCI3ZZlOMSWdRGVX6Uo download to PC desktop. Then go to micmars and download a copy of NC5 here is the link http://forum.xda-developers.com/showthread.php?t=2712205. It is a zip file so just right click and extract it to your desktop, that will change to a .tar file in a folder. Next extract the odin zip to your PC desktop, and open the odin file as administrator. Now connect your device to your PC via a USB cable. A box will light up in the upper left hand corner COM: doesn't matter what color it is just shows a connection. Now click on the PDA box a new window will open up click on desktop then click on the NC5.tar file to open. Then the file show up next to the PDA box don't touch anything else just click start. Sit back go get a coffee it is going to take few minutes.
Now here is the fun part, if your phone boots up GREAT !!! If it doesn't, and bootloops no problem this common when going back to NC5 it happened to me. Just pull the battery, then reinsert battery, and boot into your stock recovery ( hold the power button, volume up button, and menu button at he same time) once there navigate to factory reset with the volume button and click on factory reset with power button. Finally the phone should boot into NC5, now go to settings/general/about phone and see what version you have.
If you are still on NH7 no problem, it didn't stick go through the process again. Others have had the same thing happen to them, and it took the second time, in the end it's worth it.
I had all kinds of problems on NH7 and so have many others, I went back to NC5 and have had no problems, I'm going to stay here and wait till android 5.0 (lollipop) comes out. Enjoy !!!
Jimzweb1
You sent me here for the thread "How to root Galaxy Note 3".
Thing is, I know how to use CF Auto Root, but I'm pretty green even at that. Maybe a total of 10 phones for my family.
I took root off a Note 3 (sm-n900p) by upgrading to the new firmware (NK4). It was having issues and he wanted to go back to a stock. Now he needs root again and chainfire doesn't list a file for the NK4.
Chainfire says he needs a image file from the update to add to his list, but I do not have it. He also states that in most cases, root will work on the new firmware. But if does not, that's where things go black, what to expect and how to recover?
And from what I read, I can't go back to an early firmware?
Your help would be greatly appreciated, thanks.
btb601 said:
Jimzweb1
You sent me here for the thread "How to root Galaxy Note 3".
Thing is, I know how to use CF Auto Root, but I'm pretty green even at that. Maybe a total of 10 phones for my family.
I took root off a Note 3 (sm-n900p) by upgrading to the new firmware (NK4). It was having issues and he wanted to go back to a stock. Now he needs root again and chainfire doesn't list a file for the NK4.
Chainfire says he needs a image file from the update to add to his list, but I do not have it. He also states that in most cases, root will work on the new firmware. But if does not, that's where things go black, what to expect and how to recover?
And from what I read, I can't go back to an early firmware?
Your help would be greatly appreciated, thanks.
Click to expand...
Click to collapse
First you have a S5 not a note 3 but other than size they are basically the same. Read the post above yours, the same thing will probably happen to you don't panic !!! I have to go to work will be back tonite if you want to wait so I can help as you do it or you can try it yourself even you loop it (like what happened to me and most people ) don't panic just follow the instructions in post # 14. You need a clean copy of NE5 go here enter SM-G900P in search on right, you will have to register but its free , I don't see a XDA site for stock NE5 so here is the link http://www.sammobile.com/firmwares/ enjoy !!!
jimzweb1 said:
First you have a S5 not a note 3 but other than size they are basically the same. Read the post above yours, the same thing will probably happen to you don't panic !!! I have to go to work will be back tonite if you want to wait so I can help as you do it or you can try it yourself even you loop it (like what happened to me and most people ) don't panic just follow the instructions in post # 14. You need a clean copy of NE5 go here enter SM-G900P in search on right, you will have to register but its free , I don't see a XDA site for stock NE5 so here is the link http://www.sammobile.com/firmwares/ enjoy !!!
Click to expand...
Click to collapse
LOL, I know I'm getting old and senile. Been called all kind of mean names and all, but I do believe I know what phone I'm working on. And thanks for the help, maybe a rain check for now. It's not my phone and he's not here.
Have a happy new year, as for me, I'm old and tired and going to bed.
btb601 said:
LOL, I know I'm getting old and senile. Been called all kind of mean names and all, but I do believe I know what phone I'm working on. And thanks for the help, maybe a rain check for now. It's not my phone and he's not here.
Have a happy new year, as for me, I'm old and tired and going to bed.
Click to expand...
Click to collapse
Sorry about that, I'm no spring chicken either. I'm sure you know what phone you have, I only based my statement on the firmware name (NK4). If you want try in the future I would glad to try and help !!! You will find as I have that here on XDA there is always someone to lend a hand !!!
jimzweb1 said:
Sorry about that, I'm no spring chicken either. I'm sure you know what phone you have, I only based my statement on the firmware name (NK4). If you want try in the future I would glad to try and help !!! You will find as I have that here on XDA there is always someone to lend a hand !!!
Click to expand...
Click to collapse
Yeah, I kind of figured that, plus the the model number is one letter different too. I would only try it if you are sure I won't lock up his phone using CF Auto root. I've been at this since the 27th, even throw money at chainfire, although I doubted that would do anything. I needed to donate anyway to show some support for his work.
My other question, can I put it back to the firmware he was on? It's was 4.4.4 (NH7). Then I could root his phone if I can't do it as you said in post #14.
btb601 said:
Yeah, I kind of figured that, plus the the model number is one letter different too. I would only try it if you are sure I won't lock up his phone using CF Auto root. I've been at this since the 27th, even throw money at chainfire, although I doubted that would do anything. I needed to donate anyway to show some support for his work.
My other question, can I put it back to the firmware he was on? It's was 4.4.4 (NH7). Then I could root his phone if I can't do it as you said in post #14.
Click to expand...
Click to collapse
No guarantee it won't bootloop !!! I did on my note 3, you just have to take a step back and keep going. Let me give you an overview, but then you need to follow the individual steps in my first post for each part you need to do.
Ok, the first thing you are going to do is BACK UP ALL THE DATA ON THE DEVICE !!! I.E. music, pics, and videos. These are found on the internal sd card copy and paste them on the desktop of your PC.
Now download Odin to your desktop and extract it. (get the link in 1st post) Download a fresh copy of NH7 4.4.4 to your desktop (get the link in 1st post) and extract it. Now follow the instructions in the first post to flash a stock rom. Let it boot up, if it bootloops take off the back and pull the battery. Let it sit for two minutes, replace the battery and hold the power button, volume up button, and the menu button at the same time. It should boot into a stock recovery, if it DOES use the volume button to navigate to factory reset and push the power button. Let device reboot this will take a couple of minutes. Now go to settings/general/about device and see what version of KK you are running.
If it DOES NOT boot into a stock recovery, and goes back to your custom recovery or bootloops. No problem, pull the battery let it set for a couple of minutes reinstall battery then hold the power button, volume down button, and menu button at the same time and boot into download mode. Go to the first post and flash the rom again it will stick the second time.
Once you are back to bone stock 4.4.4 NH7 just follow the first post for rooting and recoveries. I know this is your friend's device and you don't want to mess it up. So before you try anything check here http://autoroot.chainfire.eu/ go to SM-G900P NK4 and try the CF-auto root for the s5. The s5 and note 3 are pretty much the same. You can try to flash the root through odin the worst that can happen is it will fail and not install. Then you are back to try and going back to 4.4.4 NH7.
This is for both US Cellular Samsung S6 and S6 Edge variant. Thanks also goes to @g.lewarne for his work on Unikernel as a couple of their ramdisk/kernel commits were needed to get this going. Also, thanks to @datajosh for this template And @bpdev for testing the 925R4 version...
This will trip KNOX. It will. Trip. KNOX. IF YOU HAVE NOT TRIPPED KNOX YET - THIS WILL TRIP IT. ALSO - you CANNOT downgrade after you take the OTA so be sure you want it.
I hope that's clear enough?
Instructions:
After you've booted into OF7, go to Settings > About device and tap Build number 7 times to enable Developer Mode.
Go back and select Developer options and turn on OEM unlocking
Reboot in to download mode (Power + Home + Volume Down)
Use ODIN to flash 925R4root.tar or 920R4root.tar (depending on your device)
After your phone boots you will now have root!
If you notice constant messages about security issues because of KNOX and the kernel being permissive. To get rid of these, open Titanium Backup (or your personal favorite app freezing app) and freeze SecurityLogAgent.
Downloads
925R4 - http://1drv.ms/1HeDWXO
925R4 Source
920R4 - http://1drv.ms/1NUVJ8B This is untested...I did not have a tester for this version....
920R4 Source
The 925R4 version may or may not work with the Sprint 925P variant...no working data confirmed!
ENJOY!
Man I wish we could just find a damn exploit already lol gone this long without tripping Knox. And with the fact that I've received the "Fingerprint scanner has encountered an error, use your backup password." error 4-5x already I'm worried about tripping Knox, although you'd think they'd still fix that considering just rooting shouldn't break the scanner lol.
So this requires me to stay on that kernel huh? I couldn't go back to stock kernel huh?
cpfeifer said:
Man I wish we could just find a damn exploit already lol gone this long without tripping Knox. And with the fact that I've received the "Fingerprint scanner has encountered an error, use your backup password." error 4-5x already I'm worried about tripping Knox, although you'd think they'd still fix that considering just rooting shouldn't break the scanner lol.
So this requires me to stay on that kernel huh? I couldn't go back to stock kernel huh?
Click to expand...
Click to collapse
You could go back to the stock kernel, but you would loose root. Also as stated above you would trip knox.
someone on a sprint s5 edge said the only thing they noticed didnt work was data..just posting for them since they under 10 post..so thats awesome! if we could get data goin..we can have root!!
---------- Post added at 03:29 PM ---------- Previous post was at 03:17 PM ----------
this kernel has working data on the edge...if you could port the data stuff in yours it should be fine http://forum.xda-developers.com/spr...t/5-1-1-stock-of7-kernel-root-7-4-15-t3150350
Does this method then require flashing a custom recovery then SuperSU.zip (or CF Auto Root)? Just curious because all that's in the .rar is a boot.img and some are having issues with following the method and not having root immediately.
borxnx said:
Does this method then require flashing a custom recovery then SuperSU.zip (or CF Auto Root)? Just curious because all that's in the .rar is a boot.img and some are having issues with following the method and not having root immediately.
Click to expand...
Click to collapse
It should be flashed using ODIN...I believe I updated the link in the OP to fix that issue since I derp'd...
Sent from my SM-G920P using Tapatalk
Flashed on a 920r4, but it is not rooted.
Funny enough, I get knox warnings about threats and stuff. But when I check with root checker, I don't have root.
sintro said:
Flashed on a 920r4, but it is not rooted.
Funny enough, I get knox warnings about threats and stuff. But when I check with root checker, I don't have root.
Click to expand...
Click to collapse
Perhaps you still have to install SuperSU or another super user app.
Sent from my SM-G925R4 using Tapatalk
cpfeifer said:
Perhaps you still have to install SuperSU or another super user app.
Sent from my SM-G925R4 using Tapatalk
Click to expand...
Click to collapse
I reflashed back to stock, then installed supersu. Then opened it up, obviously it said "supersu binary not installed". Next, I flashed this kernel and once booted up supersu still repeats the previous message. In addition, root checker shows that phone is not rooted.
The only thing in the .tar file, for 920r4 at least because that's all I downloaded, is a modified kernel. Nothing about SuperSU or its binaries. This method alone does not root. This merely installs a modified SELinux permissive stock kernel. More steps are necessary to obtain root. You must flash either CF Auto Root or a custom kernel + SuperSU.zip.
Bump? Nobody? OP, amirite? Because the method you describe, and thank you so much for the SELinux permissive kernel, does not complete all of the steps between stock and fully rooted.
borxnx said:
Bump? Nobody? OP, amirite? Because the method you describe, and thank you so much for the SELinux permissive kernel, does not complete all of the steps between stock and fully rooted.
Click to expand...
Click to collapse
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
djvoleur said:
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
Click to expand...
Click to collapse
Thank you for redoing the ramdisk.
Will try out and let you know.
Anyone experiencing issues with 925r4? I have service but see no signal bars no matter where I go.
https://youtu.be/y7EpSirtf_E
djvoleur said:
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
Click to expand...
Click to collapse
This does indeed work. Thank you so much!
Edit...Added instructions I used to complete the root process.
First of all, I wanted to thank the OP of this thread for posting this guide and getting me headed in the right direction.
Credit to @djvoleur
I just wanted to share the method I used to root my USC Galaxy S6 with the Android 5.1.1 update. You will notice that the instructions are similar in the beginning. I added the extra steps that I used to complete the root process. I do not know if this method works for the Edge version.
As the OP states: This will trip knox. Personally, it doesn’t matter to me. I am too impatient and too much of a flash-a-holic to wait for a method that doesn’t trip knox.
Also, I am not a dev and I am unable to answer any questions other than how I obtained root. I am not responsible for any damage that might happen to your phone. Follow this procedure at your own risk.
Having stated these disclaimers, it really isn’t very difficult to implement. I’ve done it twice and both times worked perfectly.
Files you will need for flashing in Odin:
Odin 3.10.7 found here: http://tinyurl.com/puyq4v9
Rooted kernel 920R4root.tar found in the OP.
TWRP 2.7.8.0 (Sprint version, but I can confirm it worked for me. YMMV.) Here: http://tinyurl.com/phvrkaf
Files for flashing in TWRP:
Updated V-Kernel 920R4-071615.zip found here: http://tinyurl.com/o2h8rv4
Super SU v2.49 (beta) found here: http://tinyurl.com/or6mmqr
Now, PLEASE read these instructions before starting so that you will have a good understanding of what to do. After reading, you may begin.
Don’t forget to put the files for flashing in TWRP on your SD card (phone) before beginning this process.
After you've booted into OF7, go to Settings > About device and tap Build number 7 times to enable Developer Mode.
Go back and select Developer options and turn on OEM unlocking
Boot into download mode (Power + Home + Volume Down)
Use ODIN to flash 920R4root.tar
Use ODIN to flash TWRP and make sure that reboot is NOT checked in options.
Unplug the phone and hold the Power + Volume Down key to reboot. When the screen goes blank, quickly hold the Power + Home + Volume Up key to boot into TWRP. If it doesn’t boot to TWRP, you may have to start over.
In TWRP flash the updated V-Kernel file first, then the Super SU file, and then reboot.
After your phone boots you will now have root!
If you notice constant messages about security issues because of KNOX and the kernel being permissive. To get rid of these, open Titanium Backup (or your personal favorite app freezing app) and freeze SecurityLogAgent. (Worked for me.)
You now should be able to install Chainfire's Super SU app from the Play Store, and you can also use Root Checker to confirm you are rooted.
Good Luck!
Would this work on G920R7... J4 (rather than OF7) 5.1.1? That's what I have.
I see there is a PC1 update available also for my G920R7 which is 6.0 marshmallow.
Hard to believe I've had this device for a year with no root... Anyone can help me get this rooted? Thanks!
so after installing the intial kernel that did not work I scrolled through and saw the updated version...you should probably update the link for the untested r4 to the working version later posted...
my problem is that Im unable to load in anything but download mode due to kernel not seandroid enforcing basically not enabling me to load into recovery mode so I need the zipped version of the kernel to install via odin in download mode if possible otherwise im waiting on a 2 hour download of the stock kernal to install
i just picked up a us cellular note 5 (SM-N920R4 on OJ5)
its trying to download and update to a new firmware so i turned off wifi and that appears to stop it but i cant do any of the gazillion updates from play store like we normally do after you receive a new phone or do a factory data reset.
please advise what i need to do since im already on OJ5 and can not connect to wifi as it will auto install whatever update its trying to download.
thanks again
en11gma said:
i just picked up a us cellular note 5 (SM-N920R4 on OJ5)
its trying to download and update to a new firmware so i turned off wifi and that appears to stop it but i cant do any of the gazillion updates from play store like we normally do after you receive a new phone or do a factory data reset.
please advise what i need to do since im already on OJ5 and can not connect to wifi as it will auto install whatever update its trying to download.
thanks again
Click to expand...
Click to collapse
Use TB to remove the update apps - green phone icons in TB. That's how it always gets stopped on any samsung.
Have a Verizon SCH-I535 running android 4.4.2 I have been trying in vain for two days now to root this phone and replace the stock recovery. I'm aiming for running clockworkmod recovery and cyanogenmod. I've followed their instructions using terminal and heimdall which DOES WORK and communicate with device.
Problem is EVERY TIME I boot to recovery and try to run anything...a stock zip to downgrade it says "failed to verify whole-file signature" and "signature verification failed."
The only thing I can do is run towelroot.apk, install superSU.apk, and use the stock ROM. Using ODIN is a waste of time and fails every file every time. At this point I'm honestly kinda amazed I don't have a brick I've done so many transfers! I also always wipe data/cache before I install zips off SDcard.
I'm out of answers. Oh! At one point my counter was too high and it was also saying, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. " I downloaded TriangleAway and it reset the counter back to zero and the error went away, but there for a while I couldn't even get to recovery (take battery out and cancel out of download mode FYI to boot back into device).
Samsung Kies is the closest glimmer of hope I've gotten. Twice now it has returned my phone back to stock; so I don't think its a hardware issue ie. bad ram or ROM memory...
I've rooted a couple older Galaxy S3's running 4.3 with no issue. It's been a couple years but that was a simple ODIN flash and I kept standard ROM/recovery as I was flashing carriers and didn't want to risk breaking anything.
I'd like to think I'm not an idiot, but what the hell am I missing. I've watched dozens of youtube videos and read hundreds of guides that all seem to work. It's something with this phone and kies or some type of heightened security...
Thanks in advance! You can also email me at [email protected]
Anyone? Even a, "Yeah, that's weird man! Sounds like you did everything right!" Would make me feel better...
Yes I've tried it and it worked make sure u have the unofficial safestrap the one for your phone and do the busy box and terminal emulator thing and it works if you try to install safestrap without the other things you will brick I did it twice but it very easy to unbrick so download busybox terminal emulator and the correct safestrap for you device and also I'm on 4.4.2 also and there is only one rom i have found that works and its called superliter there ya go hope I help would provide download links but I'm not home
Also I forgot to mention your bootloader won't be unlocked it'll be bypassed and you will have a custom recovery
androidforums.com/threads/verizon-verizon-bootloader-unlock.856221/page-2[/url]
forum.xda-developers.com/showthread.php?t=2605648
device specific safestrap recovery and image
4.4.2 has a 'locked bootloader' courtesy of Verizon! This is what has been giving me fits... Going to try to go back to totally stock 4.4.2 (right not my bootloader is the international version and locked out), then towelroot to root, then install root explorer/supersu, then I'll try safestrap and hopefully its the miracle cure!
schmitey said:
Have a Verizon SCH-I535 running android 4.4.2 I have been trying in vain for two days now to root this phone and replace the stock recovery. I'm aiming for running clockworkmod recovery and cyanogenmod. I've followed their instructions using terminal and heimdall which DOES WORK and communicate with device.
Problem is EVERY TIME I boot to recovery and try to run anything...a stock zip to downgrade it says "failed to verify whole-file signature" and "signature verification failed."
The only thing I can do is run towelroot.apk, install superSU.apk, and use the stock ROM. Using ODIN is a waste of time and fails every file every time. At this point I'm honestly kinda amazed I don't have a brick I've done so many transfers! I also always wipe data/cache before I install zips off SDcard.
I'm out of answers. Oh! At one point my counter was too high and it was also saying, "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help. " I downloaded TriangleAway and it reset the counter back to zero and the error went away, but there for a while I couldn't even get to recovery (take battery out and cancel out of download mode FYI to boot back into device).
Samsung Kies is the closest glimmer of hope I've gotten. Twice now it has returned my phone back to stock; so I don't think its a hardware issue ie. bad ram or ROM memory...
I've rooted a couple older Galaxy S3's running 4.3 with no issue. It's been a couple years but that was a simple ODIN flash and I kept standard ROM/recovery as I was flashing carriers and didn't want to risk breaking anything.
I'd like to think I'm not an idiot, but what the hell am I missing. I've watched dozens of youtube videos and read hundreds of guides that all seem to work. It's something with this phone and kies or some type of heightened security...
Thanks in advance! You can also email me at [email protected]
Click to expand...
Click to collapse
Verizon spends a pretty penny when it comes to making sure their devices................. stay theirs i guess you can say when it comes to the boot-loader! To my knowledge their isn't a way of getting around that with a permanent recovery flash that completely replaces Verizon's stock recovery. I can almost guaranteeing you that your problem is Verizon locked boot loader. Stock recoveries are solely only their for their technicians, so unless someone somehow has leaked a program that they use to get around that stuff without screwing it up, we the general public will never be able to flash anything permanent with any phones stock recovery unless we have their "secret" software! Every once in a while you do find a leaked one. I got lucky and found one for the T-mobile galaxy S6 Edge. As far as Odin I've noticed that the new versions seem to be very particular. Meaning if a dot or a space is misplaced anywhere in the zip or what not it will always fail. With my t-mobile S6 I spent two days figuring out I had to take a letter out of the name of the file i was trying to Odin. One letter that was it and once I did that it went flawlessly. Otherwise man i really don't know what to tell you, seems like ya followed the lines as described. Just remember its a Samsung Galaxy in my opinion Galaxies are unbrickable. Ive even pulled the cord in the middle of a Odin flash to see if i could brick it for good and was still able to go right into download mode and flash stock back onto it and everything working. So don't be afraid of bricking it. It will be way easier (sorry to say) for you to re-flash stock right now! Good luck bro wish you the best!
---------- Post added at 08:25 PM ---------- Previous post was at 08:18 PM ----------
schmitey said:
4.4.2 has a 'locked bootloader' courtesy of Verizon! This is what has been giving me fits... Going to try to go back to totally stock 4.4.2 (right not my bootloader is the international version and locked out), then towelroot to root, then install root explorer/supersu, then I'll try safestrap and hopefully its the miracle cure!
Click to expand...
Click to collapse
Are you able to disable Signature verification in the recovery?
Are you able to disable Signature verification in the recovery?
You can once I flash to say clockworkmod recovery. Stock I don't know of a way to...hence the Catch 22 there's no going forward and no going back...you're stuck with stock ROM/recovery but at least its rooted.
Well ****. Take my word for it you CAN brick a galaxy s3.
I used KIES to restore back to factory stock recovery etc etc.
I then used towelroot to root phone and install supersu. I then installed safestrap which totally worked! I was able to bypass the stock recovery and everything was running smoothly...I got overzealous and tried to install the cyanogenmod vrale6 bootloader zip through safestrap. I currently have a brick. It won't boot, no led's, no screen, no vibrate. I have another galaxy s3 charging batteries and swapped it out...removed sim and micro sd. I should have just installed the cyanogenmod app and done it that way...
So close and now I bricked it...
OK got my brick back by writing image to microSD card...pretty happy about that little trick. And that's utter nonsense about needing the same size card as your internal memory! I used a 32gig card on a 16gig phone...
Still trying but this locked 4.4.2 bootloader is BULL****. Going to try to downgrade but I'm not sure I'm going to end up with anything but a rooted stock rom...
So does anyone know of a way to downgrade or change recovery on Verizon 4.4.2?
I have s3 Verizon I-535 & clockworkmod recovery is not gonna work cuz of the locked bootloader, I used safestrap that's the only recovery for 4.4.2
slimcyril said:
I have s3 Verizon I-535 & clockworkmod recovery is not gonna work cuz of the locked bootloader, I used safestrap that's the only recovery for 4.4.2
Click to expand...
Click to collapse
Thanks for the reply. But with safestrap its a step in the right direction but every zip fails...so I don't see what it really does for us. Don't see myself ever running cyanogenmod at this rate unless you know something I don't...
schmitey said:
Thanks for the reply. But with safestrap its a step in the right direction but every zip fails...so I don't see what it really does for us. Don't see myself ever running cyanogenmod at this rate unless you know something I don't...
Click to expand...
Click to collapse
Well no zip has ever failed on my end using safestrap, does your device have init.d support?
No point me to it! I'm basically stock rom running safestrap atm. If you can walk me through this I'd be grateful.. Just remember I'm locked Verizon bootloader...
And may I say I finally got the I535 switched to selectel (was on a flashed sprint L710) and holy cow 4G LTE is fast...faster than my home internet!
schmitey said:
No point me to it! I'm basically stock rom running safestrap atm. If you can walk me through this I'd be grateful.. Just remember I'm locked Verizon bootloader...
And may I say I finally got the I535 switched to selectel (was on a flashed sprint L710) and holy cow 4G LTE is fast...faster than my home internet!
Click to expand...
Click to collapse
Go to mount on safestrap & see if your system partition is checked(mounted) e.t.c & go to playstore install universal init.d app
Note; uncheck verify signature checks if you're trying flash anything via recovery or else it will definitely fail
slimcyril said:
Go to mount on safestrap & see if your system partition is checked(mounted) e.t.c & go to playstore install universal init.d app
Note; uncheck verify signature checks if you're trying flash anything via recovery or else it will definitely fail
Click to expand...
Click to collapse
system partition is NOT checked within safestrap. Installed universal init.d but I'm out of my league on it... Init.d says stock kernel does not have support...
Disclaimer:
I am not responsible for anything that happens to your device after following this guide. Also, I'm not entirely sure if this works 100% for OF1, although I can guarantee that this guide works for OB6 because I just successfully rooted, unlocked the bootloader, and flashed a custom recovery onto my Galaxy Note 3 running the OB6 update.
This guide was compiled for the sole purpose of convenience for other users here on XDA Forums. My reason for making this guide was to make it as easy as possible for Verizon Galaxy Note 3 owners to root, unlock the bootloader, and flash a custom recovery without jumping from thread to thread, searching for answers.
ONLY FOLLOW THIS GUIDE IF YOU KNOW WHAT IT MEANS TO BE ROOTED, HAVE AN UNLOCKED BOOTLOADER, AND WHAT A CUSTOM RECOVERY IS USED FOR
If you are the proud owner of a Verizon Galaxy Note 3 (SM-N900V) and would like to root, unlock the bootloader, and/or flash a custom recovery onto it, you've come to the right place. Included in this guide are methods of doing these exact things, which also happen to be generally easy to perform.
Before you begin, you'll need a few things:
a Verizon Galaxy Note 3 (running OB6 or OF1, obviously)
a computer of some sort (running Windows)
a micro SD card (make sure there isn't anything on it, because it WILL be erased)
Odin 3.09 *
TWRP 3.02-1 *
ArabicTool *
eMMC Brick Bug Checker app
unlock_n3 (for unlocking the bootloader, attached) *
* place these files in a location that you know the path of. e.x. C:\ or C:\Users\...\Desktop
Once you are 100% sure that you have all of these things, continue to the rest of the guide.
Root
Open ArabicTool
Make sure your phone is connected to your computer
In ArabicTool, click on the "Version" field and select your firmware version (OB6/OF1)
Click on "Read phone info" and wait for the information above to show your phone's status
Check the logs on the bottom right to make sure that everything is correct, then click on "Root" below the "Phone info" box (if there is an error about not being on 5.0, close the app, set the compatibility mode to W7, and run as admin)
Once your phone restarts, continue to the next part of the guide
Unlocking the Bootloader
Just follow this tutorial. The consequences of messing this part up can lead to bricking your phone, although the process itself is fairly simple. Just remember that you need to unzip samsung_unlock_n3.zip and rename the file in there to unlock_n3. Follow the instructions from there.
Flashing TWRP
Honestly, this part was the easiest for me.
Unzip and open Odin 3.09
Reboot your phone into download mode (with it plugged into the computer, obviously)
In Odin, click "AP" and find the flashable TWRP tar that you downloaded earlier
Start the flashing process by clicking "Start" in the bottom right hand corner
If, after this process, your phone reboots and shows an error about the recovery partition in the top left hand corner (in blue), then goes into a bootloop:
Download the stock recovery.tar from the attached files at the bottom of this post
Open Odin again
Click "AP", find the file you just downloaded, and start the flashing again
Follow the instructions to unlock your bootloader again, but only do the second set of code. The first set is irrelevant to us at this point.
Flash TWRP onto your phone again. This time, it should work if it didn't already.
To make sure, boot your phone into recovery mode. If TWRP boots up, success (obviously )!
If you have any issues whatsoever that I haven't covered in this guide, please either PM me or reply to this thread. Also, if I have made any mistakes in outlining the instructions in this guide, do the same.
Credit to:
@androidyemen and others for finding the root method,
@ryanbg for finding the bootloader unlock method,
@beaups for finding the eMMC backdoor,
and Team Win for creating TWRP
Source posts:
[Official] Note 3 Verizon Bootloader Unlock by ryanbg
OB6 & OF1 N900V Note 3 Verizon Oneclick SuperSU Rooted Successfully
If in any case you would like to donate to me for this post (which in no way am I asking you to), here is my PayPal email:
[email protected]
Any thoughts on if this will work on OF1 partial firmwares such as the one included for jasminerom 6.1 retail edition?
Since I'm rooted already, I would be picking up from after the rooting steps.
Also, can you provide the steps for bootloader unlock. The link provides is coming up as invalid link in xda mobile app.
Sent from my SM-N900V using XDA-Developers mobile app
i420bdawg1 said:
Any thoughts on if this will work on OF1 partial firmwares such as the one included for jasminerom 6.1 retail edition?
Since I'm rooted already, I would be picking up from after the rooting steps.
Also, can you provide the steps for bootloader unlock. The link provides is coming up as invalid link in xda mobile app.
Click to expand...
Click to collapse
I'm not entirely sure if it will work on JasmineROM 6.1 specifically, but it won't hurt your device to try. Unless your CID doesn't start with 15 for some reason. If it does, the worst that can happen is the unlock file won't work.
I'll have to edit that part when I get home. I'm only going to be gone for about 20 minutes or so.
Sent from my LG-H634 using XDA Labs
i420bdawg1 said:
Any thoughts on if this will work on OF1 partial firmwares such as the one included for jasminerom 6.1 retail edition?
Since I'm rooted already, I would be picking up from after the rooting steps.
Click to expand...
Click to collapse
It really only needs root, although the spot it looks for the eMMC CID value changed from kernel release to kernel release, so there were some minor release dependencies.
[Edit 8/25/2016] Based on feedback from member shallmann, it appears that specific binary versions released within the Unlock Thread should be used depending on the firmware revision of your phone. See this post in that thread.
The version which seems to be most compatible with M*, N*, and O* kernels is the build posted (along with source code) in post #218 of the bootloader unlock thread.
( The newly-rebuilt version in the OP of that thread is still incompatible with 4.3 and 4.4 (M*, N*) releases. )
Man up and use your browser if the XDA app is broken.
.
i420bdawg1 said:
Any thoughts on if this will work on OF1 partial firmwares such as the one included for jasminerom 6.1 retail edition?
Since I'm rooted already, I would be picking up from after the rooting steps.
Also, can you provide the steps for bootloader unlock. The link provides is coming up as invalid link in xda mobile app.
Sent from my SM-N900V using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes it will, I did it already months ago when all this first came out.
Sent from my SM-N900V using Tapatalk
@jamesalynch
I know you are trying to help and everything, but you've kind of screwed the pooch in a couple of different ways. First, the binary that you attached doesn't work on any 4.3.x (M*) or 4.4.x (N*) series ROMs, and I'm not sure it ever worked even on OB1 and OF1.
Second, you should not be re-attaching files that are available in other people's posts. Just provide a link to the original post; if there is an ambiguity as to what download is desired, then describe it in your post.
Third, you should not be taking other people's downloads, unpacking them, and then renaming the included files to match filenames used elsewhere - that is only going to increase people's confusion.
Fourth, in that OP (@ryanbg 's post) he mentions re-building the code and NOT USING the version that you provided as an attachment. Unfortunately, he was in a hurry when he rebuilt the code, and even the new version he built still does not work on 4.3.x and 4.4.x ROMs.
[Edit 8/25/2016] Based on feedback from member shallmann, it appears that specific binary versions released within the Unlock Thread should be used depending on the firmware revision of your phone. See this post in that thread.
The version that will work for everyone is in @donc113's post #218 in that thread.
Code:
$ find . -type f \( \! -name '*.zip' -a \! -name '*.c' \) -exec md5sum {} \;
[b][color=green]ea856efcb7de0ca8ff428522dbdc0267 ./donc113-post218/unlock[/color][/b] [b]<<<==== Use this for NK1 and prior.[/b]
0bcb409af65e311ce4b67faf7ed3f0af ./ryanbg0804/unlock_n3 [b]<<<==== Use this for OB6 and OF1.[/b]
cba959357ed1d0207dbde56bb6b6a1b7 ./ryanbgORIG/samsung_unlock_n3
cba959357ed1d0207dbde56bb6b6a1b7 ./JAL/unlock_n3 [b]<<<==== Your version with name change from 'samsung_unlock_n3'.[/b]
Thanks to everyone who posted. I will be going back to the post mentioned in the comments.
Sent from my SM-N900V using XDA-Developers mobile app
This is kinda confusing, to be honest.
Once bootloader is unlocked you could just download FlashFire and download and flash TWRP from there rather than using Odin.
The root tool you linked didn't work for me, even on Windows 7, granted others said it worked for them. If they are on Windows 10, there is a different tool to use.
stock recovery?
I need the stock recovery file, that you said would be attached. My phone is not booting with the Recovery warning..
Tremo419 said:
I need the stock recovery file, that you said would be attached. My phone is not booting with the Recovery warning..
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/download/45906/N900VVRUEOB6_N900VVZWEOB6_VZW/
Open that file and extract the recovery image. Compress it in a TAR. Flash.
Sent from my LG-H634 using XDA Labs
I have the sm-900v on 5.0 and I rooted and unlocked bootloader and twrp and flash a rom but didn't go through so I Odin stock rom back to begin fresh and now it won't root...as soon as I do the root process and it restarts my phone into stock recovery...so I clean cache and reboot and goes right back to stock recovery...can anyone help
Sent from my SM-N900V using XDA-Developers mobile app
ozz200127 said:
I have the sm-900v on 5.0 and I rooted and unlocked bootloader and twrp and flash a rom but didn't go through so I Odin stock rom back to begin fresh and now it won't root...as soon as I do the root process and it restarts my phone into stock recovery...so I clean cache and reboot and goes right back to stock recovery...can anyone help
Sent from my SM-N900V using XDA-Developers mobile app
Click to expand...
Click to collapse
Firstly, if you have an unlocked bootloader, you never have to flash STOCK again.
So - after you have gotten this problem fixed - learn how to avoid using Odin with STOCK firmware bundles.
Odin can flash a custom recovery when the bootloader is unlocked. That will save you trouble in the future. You need to learn how to build Odin ".tar.md5" files. In a nutshell, for doing what I just mentioned, you take a TWRP .img file, rename it to "recovery.img", put it in a "ustar" format tar file, and then compute the md5 signature of that and append it to the end of the file. Search for "Odin md5 ustar" in these forums.
For your current problem, I can't tell exactly what you are saying. If you are saying "I am stuck in a vicious cycle of nothing but recovery reboots (the stock recovery)", then
- pull the battery and wait ten seconds
- put the battery back in
- start in download mode with Vol_Down+Home+Power. When you get the pop-up screen, select cancel.
- if it still boots into the stock recovery, the do a full wipe (yes the whole phone, data+cache) and try booting. If the same trouble persists, go back and do the Odin STOCK flash again. (You can't flash a custom recovery with a locked bootloader).
If it still doesn't work, make sure your next problem report includes far more details than the one above, for instance:
- what version of firmware was on your phone before this mess started
- what version of firmware you were trying to flash with Odin
- what version of Odin you were using
- the name of the Odin file and it's MD5 signature.
that's a start.
VZW Note 3+Root+Jasmine Rom+Partial Firmware
CID starts with 15 (verified with EMMC)
Android Ver: 5.0
N900VVRUEOF1
Ive ran the unlock countless times I gets nothing no unlock of the bootloader at all
Omegastorm said:
VZW Note 3+Root+Jasmine Rom+Partial Firmware
CID starts with 15 (verified with EMMC)
Android Ver: 5.0
N900VVRUEOF1
Ive ran the unlock countless times I gets nothing no unlock of the bootloader at all
Click to expand...
Click to collapse
It produces error messages when it encounters a problem and exits without completing it's job.
Is there some reason why you believe we should be able to intuit what those countless error messages were? (It would be simpler if you just cut-n-paste that output into your post.)
You might also want to state which version of the tool you used - there are at least 3 in the original thread.
im thinking about getting a verizon note 3.. does this work for all variants to get root, twrp and custom roms?
thanks
Jaws4God said:
im thinking about getting a verizon note 3.. does this work for all variants to get root, twrp and custom roms?
thanks
Click to expand...
Click to collapse
No
You can root all variants but can not unlock all variants, thus can't use TWRP or use custom ROMS or kernel.
Must be model SM-N900V, must have a specific Samsung eMMC (cid must start with 15) and the external SD card slot must work along with the USB port.
Sent from my SM-N900V using Tapatalk
bftb0 said:
It produces error messages when it encounters a problem and exits without completing it's job.
Is there some reason why you believe we should be able to intuit what those countless error messages were? (It would be simpler if you just cut-n-paste that output into your post.)
You might also want to state which version of the tool you used - there are at least 3 in the original thread.
Click to expand...
Click to collapse
Oh wow didn't know there was three I'm gonna go back and check that out again thanks
This is awesome man, great thanks to you. I'm new on n3 verizon, i like unleashing the power of my phone, =D
THANK YOU!
Nice post! I hadn't looked at XDA/ note 3 development in awhile. Awesome to see an exploit found! BAM!
Has anyone made a STOCK deodex/? CM is cool, but I like the S-pen. I have the n900V.
Thanks again
1Xfan said:
Nice post! I hadn't looked at XDA/ note 3 development in awhile. Awesome to see an exploit found! BAM!
Has anyone made a STOCK deodex/? CM is cool, but I like the S-pen. I have the n900V.
Thanks again
Click to expand...
Click to collapse
There are some Stock out there:
[LP] [5.0] [RE/DE] [Xposed] [MultiSystem] JasmineROM v6.1
mostly stock N900VVRUEOF1[debloated/deodexed/wifi fixed]