[/INDENT]Yesterday I rooted my Verizon Galaxy Note III using the Towelroot method and everything was working. I installed SuperSU and all of the other works. Little did I know I went and installed CWM and soft bricked my device. I was able to follow steps given to me in a previous thread but the download links for the OTA 4.4.2 update were taking way too long. So I went and downloaded the 4.4.3 links and they downloaded in a fraction of the time. So I continued following the steps that were given except the file I downloaded is an .MD5 file and not a .PIT . So I guess this is two questions in one. 1. Is it ok for me to move up a version? 2. How do I use the MD5 in ODIN. If someone can give me a few pointers that would be great. Thanks so much. :cyclops:
TheCottonKid said:
[/INDENT]Yesterday I rooted my Verizon Galaxy Note III using the Towelroot method and everything was working. I installed SuperSU and all of the other works. Little did I know I went and installed CWM and soft bricked my device. I was able to follow steps given to me in a previous thread but the download links for the OTA 4.4.2 update were taking way too long. So I went and downloaded the 4.4.3 links and they downloaded in a fraction of the time. So I continued following the steps that were given except the file I downloaded is an .MD5 file and not a .PIT . So I guess this is two questions in one. 1. Is it ok for me to move up a version? 2. How do I use the MD5 in ODIN. If someone can give me a few pointers that would be great. Thanks so much. :cyclops:
Click to expand...
Click to collapse
4.4.3 is not available for the Note 3 and it will not work. Once you're on the OTA version of 4.4.2 you can not downgrade since you're on the NC4 bootloader. You'll have to enter download mode and flash the stock NC4 Tar file that you can find HERE. You have to put the .md5 file in the AP slot. Patience Grasshopper...
TheCottonKid said:
[/INDENT]Yesterday I rooted my Verizon Galaxy Note III using the Towelroot method and everything was working. I installed SuperSU and all of the other works. Little did I know I went and installed CWM and soft bricked my device. I was able to follow steps given to me in a previous thread but the download links for the OTA 4.4.2 update were taking way too long. So I went and downloaded the 4.4.3 links and they downloaded in a fraction of the time. So I continued following the steps that were given except the file I downloaded is an .MD5 file and not a .PIT . So I guess this is two questions in one. 1. Is it ok for me to move up a version? 2. How do I use the MD5 in ODIN. If someone can give me a few pointers that would be great. Thanks so much. :cyclops:
Click to expand...
Click to collapse
Buddy we cant install Custom Recovery like CWM or TWRP in our devices because out Bootloaders are locked, so never try it again...
The solution is to install the latest Safestrap v3.72 for Kitkat currently which is safe...
4.4.3 is still under testing for Note 3 and will be launched in future...currently the latest version for our device is 4.4.2,so no matter what dont try to install newer version which are not yet launched for Verizon Note 3...
Please follow this thread to flash in ODIN if you have bricked your device...http://forum.xda-developers.com/showthread.php?t=2610757
Make sure you download the NC4 Stock ROM only...
Thanks!!!
moin786 said:
Buddy we cant install Custom Recovery like CWM or TWRP in our devices because out Bootloaders are locked, so never try it again...
The solution is to install the latest Safestrap v3.72 for Kitkat currently which is safe...
4.4.3 is still under testing for Note 3 and will be launched in future...currently the latest version for our device is 4.4.2,so no matter what dont try to install newer version which are not yet launched for Verizon Note 3...
Please follow this thread to flash in ODIN if you have bricked your device...http://forum.xda-developers.com/showthread.php?t=2610757
Make sure you download the NC4 Stock ROM only...
Thanks!!!
Click to expand...
Click to collapse
Thanks so much! Do you mind taking a look at my "I think I broke my phone thread?"
Related
I have read the faq's and stickys and im running in circles.. I had Odin'd to 4.4.2 just fine, but want to go back to 4.3 to root and debloat...
So i successfully am back to 4.3 now running on MJE.. I have read about Klingo working/not working.. I went into the FAQ's and downloaded what i thought or is a rooted flashable 4.3 MJE build, but when i look at the file its a totally uncompressed unflashable file?? Where is the md5?? Am i looking in the wrong place?
I downloaded the Universal-RDLV file too, dont know what to do with it, the video i watched the guy selected a file in ODIN that i dont have or cant find?
Sorry for the desperation everyone, i appreciate the proper direction.
Thanks so much!
Hang on, i think i was using incorrect newer Kingo.. 1.1.6 seems to be doing something now.
Had to run it 2x, but Root Succedded.. Guess now i can reflash kitkat or is it a requirement that i install safestrap?
Well... I see the instructions for the 4.4.2 Rooted require safestrap.. and i just flashed the 4.4.2 i had sooooo.. I probably goofed and have to re-do it all over again.. Grrrrrrr...
Okay so I've searched the forums and haven't found the answer to what I'm looking for quite yet. I'm not new to rooting, but new to the Galaxy Note 3. I just recently started getting prompted for the update to KK4.4.2 (I have the Verizon model and we all know how long they take to push out updates.) So I decided to flash the leaked de-oxed NC2 rom and after follow the instructions from here. I reboot and get stuck at a black screen. It boots no further and I have to pull the battery to get back to recovery.
Am I missing something, another step maybe? Is this an old process?
Any help would be appreciated. Thanks
Did you also flash the firmware package in odin?
<Note3>
LeftyGR said:
Did you also flash the firmware package in odin?
<Note3>
Click to expand...
Click to collapse
Yes I also flashed the firmware through Odin. Does it matter which version of Odin I used?
Odin doesn't matter.
Root 4.3
Install safe strap.
Now you can update to the rooted 4.4 through odin.
barrackOBAMA said:
Odin doesn't matter.
Root 4.3
Install safe strap.
Now you can update to the rooted 4.4 through odin.
Click to expand...
Click to collapse
Actually it looks as if this was caused by Odin 3.09. It doesn't seem to like the bootloader file for NC2 and for some reason doesn't load the entire boot portion of the file. Flashed with Odin 3.07 and booted no problem. Thanks for the input though.
Please follow all the steps or you'll have bricked device
Step 1 :
This is the easiest way to enable USB debugging.
Dial *#0808#
Select last option, DM+Modem+ADB
YOUR PHONE MUST ASK FOR USB DEBUGGING AUTHORIZATION ! YOU MUST CHECK ALWAYS ALLOW FROM THIS COMPUTER AND THEN PRESS OK. IF YOU DO NOT GET THIS DO NOT PROCEED
Step 2:
Reboot phone into download mode
Select PDA slot in odin
And flash the tar file root kernel (you'll need to extract contents of rar file and rename file to boot.tar)
Your device will not have display but it will still be working, run saferoot.
Step 3:
Use saferoot thanks to k1mu, Surge1223, download is at the end of the post linked below
http://forum.xda-developers.com/showpost.php?p=48392009&postcount=1
After phone reboots for first time remove USB and enter download mode.
Step 4:
Select PDA slot in odin
And flash the tar file restore display kernel (you'll need to extract contents of rar file and rename file to boot.tar)
Step 5:
Install Supersu from market and open it. Continue with saferoot, that is waiting for the phone.
When flashing the root_boot.tar.md5 i get an error.
<OSM> MD5 hash value is invalid
<OSM> root_boot.tar.md5 is invalid.
---------- Post added at 03:24 PM ---------- Previous post was at 03:12 PM ----------
nvm, I fixed it by removing the .md5 extension.
You're awesome! Thanks!
Nice work.
Looks like we're flashing 4.2.2's kernel, rooting, then flashing 4.4.2's kernel again.
I guess this also means there is the potential to downgrade back to 4.2.2 completely with mobile odin now...
Did you guys have any trouble getting SuperSU to update the su binary?
SU works, just prompts me to update the binary and fails.
az4x4runner said:
Nice work.
Looks like we're flashing 4.2.2's kernel, rooting, then flashing 4.4.2's kernel again.
I guess this also means there is the potential to downgrade back to 4.2.2 completely with mobile odin now...
Click to expand...
Click to collapse
You can downgrade to 4.2.2, just flash the stock bootloader first, then it will let you flash the ROM. I had to do it because I bricked at the 4.4.2 upgrade.
Trying this root now!
djdevin said:
You can downgrade to 4.2.2, just flash the stock bootloader first, then it will let you flash the ROM. I had to do it because I bricked at the 4.4.2 upgrade.
Trying this root now!
Click to expand...
Click to collapse
I have not been able to find the JB bootloader. It's out there? The ROMs on Sammobile don't include it... I had previously bricked trying to downgrade due to the locked KK bootloader.
az4x4runner said:
I have not been able to find the JB bootloader. It's out there? The ROMs on Sammobile don't include it... I had previously bricked trying to downgrade due to the locked KK bootloader.
Click to expand...
Click to collapse
Sorry, I misspoke. I don't know if it was the bootloader or something else. Check this out: http://forum.xda-developers.com/showpost.php?p=55251936&postcount=18
Also, root works!
Someone want to explain how those two files could be flashed via ODIN?
djdevin said:
Sorry, I misspoke. I don't know if it was the bootloader or something else. Check this out: http://forum.xda-developers.com/showpost.php?p=55251936&postcount=18
Also, root works!
Someone want to explain how those two files could be flashed via ODIN?
Click to expand...
Click to collapse
They are stock kernel images. I've never had issues flashing stock kernels or recoveries with Odin.
az4x4runner said:
They are stock kernel images. I've never had issues flashing stock kernels or recoveries with Odin.
Click to expand...
Click to collapse
stock images from the sm-g730a? or another device?
djdevin said:
stock images from the sm-g730a? or another device?
Click to expand...
Click to collapse
From the SM-G730A.
"Root kernel" is simply the 4.2.2 stock kernel, which worked with Saferoot previously, and still does.
"Restore display kernel" is the stock 4.4.2 kernel you started with, you're just reflashing it after rooting.
I extracted boot.img from each ROM (4.2.2 and 4.4.2), created my own tar.md5 files and was able to root successfully also. I'm not sure why the ones in this post don't work with the md5 extension. It's a great idea.
az4x4runner said:
From the SM-G730A.
"Root kernel" is simply the 4.2.2 stock kernel, which worked with Saferoot previously, and still does.
"Restore display kernel" is the stock 4.4.2 kernel you started with, you're just reflashing it after rooting.
I extracted boot.img from each ROM (4.2.2 and 4.4.2), created my own tar.md5 files and was able to root successfully also. I'm not sure why the ones in this post don't work with the md5 extension. It's a great idea.
Click to expand...
Click to collapse
ah I see. that makes sense
az4x4runner said:
Did you guys have any trouble getting SuperSU to update the su binary?
SU works, just prompts me to update the binary and fails.
Click to expand...
Click to collapse
i have the same trouble
I just finished step 4 and how it keeps restarting and vibrating.
FIX for "Installation Failed when Updating Binary on SuperSU"
bam056 said:
i have the same trouble
Click to expand...
Click to collapse
az4x4runner said:
Did you guys have any trouble getting SuperSU to update the su binary?
SU works, just prompts me to update the binary and fails.
Click to expand...
Click to collapse
It seems that the SuperSU version (2.01) that is currently (13/10/2014) on the Play Store is outdated. You need to do the following:
1) Download v 2.13 of Chainfire's SuperSU from his Google+ page (I cannot post the link here as I am a new user)
2) Extract the .zip file and find 'Superuser.apk'
3) Transfer 'Superuser.apk' to SD card of your phone
4) Open 'Superuser.apk' from your phone and install/update
5) After the installation/update is complete, open SuperSU and update binary (normal method)
Good luck. I just used this thread to root my Samsung SIII Mini (SM-G730A) from Fido. Working great so far. Thanks atinder! :good:
Great post
It's a great post, I would like thank az4x4runner and wisdom and all of you guys, if you do it step by step is a 123 solve for the ATT S3 Mini SM-G730A 4.4.2 Root :good::good::victory::victory:
I can confirm that I've rooted my G730A using the steps given and with the SuperSU apk provided. The first thing I did was bypass Kitkat's SD card limitations -- everything is now exactly the way I want it. Thank you all!
I need help. I tired to root my g730a and I followed all the steps and now my phone has a blank screen with the blue light on. How can I fix this? thanks!
-----------------------------------
nvm, I got it to work.
Recovery
Which recovery works for 4.4.2?
Will this work on Verizon SIII mini running 4.4.2? I successfully rooted my Galaxy Tab with Odin and it was easy as pie. This looks a lot more complicated and I have already tried TowelRoot, Saferoot, etc with no success.
atinder said:
Please follow all the steps or you'll have bricked device
Step 1 :
This is the easiest way to enable USB debugging.
Dial *#0808#
Select last option, DM+Modem+ADB
YOUR PHONE MUST ASK FOR USB DEBUGGING AUTHORIZATION ! YOU MUST CHECK ALWAYS ALLOW FROM THIS COMPUTER AND THEN PRESS OK. IF YOU DO NOT GET THIS DO NOT PROCEED
Step 2:
Reboot phone into download mode
Select PDA slot in odin
And flash the tar file root kernel (you'll need to extract contents of rar file and rename file to boot.tar)
Your device will not have display but it will still be working, run saferoot.
Step 3:
Use saferoot thanks to k1mu, Surge1223, download is at the end of the post linked below
http://forum.xda-developers.com/showpost.php?p=48392009&postcount=1
After phone reboots for first time remove USB and enter download mode.
Step 4:
Select PDA slot in odin
And flash the tar file restore display kernel (you'll need to extract contents of rar file and rename file to boot.tar)
Step 5:
Install Supersu from market and open it. Continue with saferoot, that is waiting for the phone.
Click to expand...
Click to collapse
After flashing 1st boot.tar you say screen goes blank then run saferoot. After saferoot reboot will you have screen display again?
I updated my galaxy s4 i9500 to 5.0.1 using odin. My phone was working well when I saw that i am having no more root access So i rooted my device. But rooting on 5.0.1 was no use. Most of the application's were not compatible with 5.0.1. So i flashed xposed framework and was dumb enough to read the full instructions. After flashing my phone was soft brick. So i went to the forum again and saw the instructions that thr version is not for Touchwiz. So i glashed cm11 and it worked my phone was working again but i noticed that it's been a while and my network signals are not appearing. I thought that the zip file would be corrupted so i flashed ozcan rom. But no success. Then i opened my settings and saw that imei was "Null/Null". And lastly /device/data folder is empty. Would be great if anyone will help.
1. Flash again the lollipop version.
2. Then root it using cf root.
3. Problem solved
ps maybe you should also do a factory reset, but backup first.
Lennyz1988 said:
1. Flash again the lollipop version.
2. Then root it using cf root.
3. Problem solved
ps maybe you should also do a factory reset, but backup first.
Click to expand...
Click to collapse
Thank you sir for your reply but i have factory reset my device more then 7 times. And can yoyou please give me the link for Lollipop frimware becuase the link through i download was of mega.co but now it's not working and sammobile is also having lollipop firmware but there download speed is very poor. So any other link would be appreciated. Thank you.
Ive been going so crazy trying for about 15 hours total now trying to root and get a custom recovery on my phone, for some reason, nothing will work. I do have alot of experience with rooting and ive done just about everything, attempting to get this phone to flash a custom recovery.
ATT SGH i337
4.4.4
KTU84P.I337UCUFNJ4
I am currently rooted, but i cannot get a custom recovery. I have just tried this method,
http://forum.xda-developers.com/showthread.php?t=2297033
with that tool, however after running it, it successfully flashes the recovery, then boots me into the Odin Mode Download screen with the picture of an android. Same thing with trying any other method of flashing a recovery. Can someone please tell me how to get past this, im so exhausted trying to fix this. I tried factory reseting my phone from the phones settings and even that brought me back to the download screen with a picture of an android. I cant get into any recovery at all! Stock or custom it sends me back to that screen.
How can i flash a custom recovery and get this working? Thank you guys in advance
You're on nj4. Safestrap is the only recovery you're going to be able to use. Read the stickies in the general forum
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You're on nj4. Safestrap is the only recovery you're going to be able to use. Read the stickies in the general forum
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
i installed the proper NJ4 safestrap apk and pressed install recovery, however it still says it is not installed "reboot to recovery" is greyed out. Upon booting into recovery, i am still stuck in Odin mode. Anyway for me to stop odin mode from continuing to come up instead of recovery?.
I would guess the system is looking for stock recovery, and it isn't there any more due to your flashing the CWM OUDHS recovery and/or TWRP. You probably need to put the stock recovery back.
I know and I've been trying to find out a way to do that. Could you help me if that's what I need to do? Once I reinstall stock recovery will safestrap work?
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
I would suggest that you flash nb1 then nb4, root and install safestrap. At this point, a clean install is your best bet. Refer to this thread in the general forum.
U can get stock recovery back by either flashing the whole stock firmware via odin or extracting the recovery image from the firmware and flashing it by its self via odin I don't know anything about safestrap as I'm on Canadian version some one else can hopfully help u out with tht
I read what you posted and I don't entirely understand. Could you point to me to a download a maybe dumb it down a bit?
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
How would I do that..
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
xstokerx said:
U can get stock recovery back by either flashing the whole stock firmware via odin or extracting the recovery image from the firmware and flashing it by its self via odin I don't know anything about safestrap as I'm on Canadian version some one else can hopfully help u out with tht
Click to expand...
Click to collapse
Exxoriscism said:
I read what you posted and I don't entirely understand. Could you point to me to a download a maybe dumb it down a bit?
Click to expand...
Click to collapse
Exxoriscism said:
How would I do that..
Click to expand...
Click to collapse
You are on NJ4 (I337UCUFNJ4). There is no flashable "whole stock firmware" for that version. There is a flashable whole stock firmware for the NJ1 version (I337UCUFNB1). Also, there is no easy way to "extract the recovery image out of the firmware and flash it by its self via odin." The reason for this is that you need a .tar archive to flash in odin, so if you extract just the recovery, you then need a Linux box, or a Linux virtual machine running on your windows pc to make the tar file from it.
This is why I suggested that you flash the NB1 full stock firmware, and then flash the upgrade to NJ4 from stock recovery, as outlined in the guide I linked.
As you asked for a little more detailed help, I'll try to walk you through following the Odin to Stock, Updating, Rooting, and Safestrap Guide.
First, read through post #1 and the FAQ in post #3. Next, you need to decide what version you want to end up with. Let's assume that you want to end with NJ4 -- KitKat 4.4.4. (If you want to end with OC3 -- Lollipop 5.0.1, then the instructions are a little different.)
In post #2, under the section titled NJ4 -- KitKat 4.4.4 expand Step 1 - Odin to stock. The files you need to download are at the top of this section. Follow the steps; they are pretty self explanatory. Part 1 installs full stock NB1, and Part 2 installs the upgrade to NJ4.
You are now on fully stock NJ4. If you want to root and install Safestrap, expand Step 2 -- Root and Install Safestrap. The files you need to download are at the top of this section. Again, the steps are pretty self explanatory.
That's it. If you want to now install custom firmware, you are ready, or you can just stay on stock if you prefer.
creepyncrawly said:
You are on NJ4 (I337UCUFNJ4). There is no flashable "whole stock firmware" for that version. There is a flashable whole stock firmware for the NJ1 version (I337UCUFNB1). Also, there is no easy way to "extract the recovery image out of the firmware and flash it by its self via odin." The reason for this is that you need a .tar archive to flash in odin, so if you extract just the recovery, you then need a Linux box, or a Linux virtual machine running on your windows pc to make the tar file from it.
This is why I suggested that you flash the NB1 full stock firmware, and then flash the upgrade to NJ4 from stock recovery, as outlined in the guide I linked.
As you asked for a little more detailed help, I'll try to walk you through following the Odin to Stock, Updating, Rooting, and Safestrap Guide.
First, read through post #1 and the FAQ in post #3. Next, you need to decide what version you want to end up with. Let's assume that you want to end with NJ4 -- KitKat 4.4.4. (If you want to end with OC3 -- Lollipop 5.0.1, then the instructions are a little different.)
In post #2, under the section titled NJ4 -- KitKat 4.4.4 expand Step 1 - Odin to stock. The files you need to download are at the top of this section. Follow the steps; they are pretty self explanatory. Part 1 installs full stock NB1, and Part 2 installs the upgrade to NJ4.
You are now on fully stock NJ4. If you want to root and install Safestrap, expand Step 2 -- Root and Install Safestrap. The files you need to download are at the top of this section. Again, the steps are pretty self explanatory.
That's it. If you want to now install custom firmware, you are ready, or you can just stay on stock if you prefer.
Click to expand...
Click to collapse
Yes and i did everything under the NJ4 Kitkat 4.4.4 section. I am rooted and everything worked except for safestrap. I open it and press install recovery and everytime it finishes it says "state:Not Installed". And reboot to recovery is greyed out. Upon manually rebooting into recovery mode, i am in normal stock recovery.
I cant use the selinux mode changer it says. To root i didnt use towelroot because installing the NC1 kernel disables my wifi connection, and since the phone has no service, i had to use KingO Root. I have confirmed root access using root checker. But Safestrap wont work.
What do i do? Is safestrap not working because i didnt root with towelroot? I assumed it didnt quite matter how i rooted. If it is because of towelroot, then how do i get towel root to work while on the NC1 kernel with no wifi and no cell service?
Update: I found a selinux Mode changer apk on xda and installed it. I tried it and safestrap still would not work and said "not installed". I also reflashed the NC1 Kernel and the same thing happened. I booted into recovery for confirmation.
I guess its maybe because i didnt root with towelroot? But it is impossible without phone service because flashing NC1 disables the wifi. Please reply as soon as you can
I can't help with your current issue with safestrap because I don't own this phone. I have worked on my son's S4, and a couple of others that have come through my hands. I have performed the exact process you just used with no issues.
I would suggest you post your issues in the guide thread where someone who has more experience with safestrap can help.
creepyncrawly said:
I can't help with your current issue with safestrap because I don't own this phone. I have worked on my son's S4, and a couple of others that have come through my hands. I have performed the exact process you just used with no issues.
I would suggest you post your issues in the guide thread where someone who has more experience with safestrap can help.
Click to expand...
Click to collapse
Can i move this thread?
Exxoriscism said:
Can i move this thread?
Click to expand...
Click to collapse
You can't move this thread into that one. But you can state your issue in that thread and then provide a link to this one for more info.
Sent from my Nexus 9 using XDA Free mobile app