Hi I am wondering how do I root sgh-i337 with 5.0.1 it is already updated from Att all I can find is threads that have keep root, any help on this would be great and yes I know this voids warranty I don't care if it does just saying before people start posting saying different thing like that all I want to do is root my phone thanks for any help
killernos said:
Hi I am wondering how do I root sgh-i337 with 5.0.1 it is already updated from Att all I can find is threads that have keep root, any help on this would be great and yes I know this voids warranty I don't care if it does just saying before people start posting saying different thing like that all I want to do is root my phone thanks for any help
Click to expand...
Click to collapse
Flash NB1 and do the keeproot method, otherwise there's no other way.
how do i flash nb1 fron 5.0.1? by odin like any other samsung??
Enviado desde mi SAMSUNG-SGH-I337 mediante Tapatalk
DeadlySin9 said:
Flash NB1 and do the keeproot method, otherwise there's no other way.
Click to expand...
Click to collapse
Will flashing nb1 not downgrade the bootloader?
Root SGH-I337 running Lollipop 5.0.1
Hi All, I'm new here and also a noob. Can I continue this thread or do I need to start a new one? Just like OP, I want to root my AT&T S4, and eventually install custom ROM's. I've tried everything I can find with no success. King Root, KingoRoot, CASUAL, Super Root, OneClick root, Root Genius... I just want my phone my way. Can anyone help with tutorials and such? Thanks in advance
Cliffhanger68 said:
Hi All, I'm new here and also a noob. Can I continue this thread or do I need to start a new one? Just like OP, I want to root my AT&T S4, and eventually install custom ROM's. I've tried everything I can find with no success. King Root, KingoRoot, CASUAL, Super Root, OneClick root, Root Genius... I just want my phone my way. Can anyone help with tutorials and such? Thanks in advance
Click to expand...
Click to collapse
Its impossible (momentarily) to direct root 5.0.1
Only method is downgrading to NB1 - rooting with towelroot - then doing a keeproot update to 5.0.1
Downgrade to NB1 and root using this post HERE (Second post - second part under HOW TO GET TO ANY KITKAT 4.4.2)
To update to 5.0.1 and keep root follow this post HERE.
TheJuli said:
Its impossible (momentarily) to direct root 5.0.1
Only method is downgrading to NB1 - rooting with towelroot - then doing a keeproot update to 5.0.1
Downgrade to NB1 and root using this post HERE (Second post - second part under HOW TO GET TO ANY KITKAT 4.4.2)
To update to 5.0.1 and keep root follow this post HERE.
Click to expand...
Click to collapse
I tried to downgrade to NB1 before using the same guide and file in the link, got several errors, I don't remember what they were. When I rebooted I was still in OC4. I will try again in the next couple of days (Wife's birthday tomorrow) when I have the extra time. I will update post when I find out something. Thanks for the response and the interest in helping!
---------- Post added at 04:42 AM ---------- Previous post was at 03:59 AM ----------
Cliffhanger68 said:
I tried to downgrade to NB1 before using the same guide and file in the link, got several errors, I don't remember what they were. When I rebooted I was still in OC4. I will try again in the next couple of days (Wife's birthday tomorrow) when I have the extra time. I will update post when I find out something. Thanks for the response and the interest in helping!
Click to expand...
Click to collapse
Just tried to Odin v3.09 to NB1... FAIL! Here is the log from Odin. Don't know if you can tell anything from it or not, besides that it failed.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUFNB1_TWRootable_Full_Odin.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
Cliffhanger68 said:
I tried to downgrade to NB1 before using the same guide and file in the link, got several errors, I don't remember what they were. When I rebooted I was still in OC4. I will try again in the next couple of days (Wife's birthday tomorrow) when I have the extra time. I will update post when I find out something. Thanks for the response and the interest in helping!
---------- Post added at 04:42 AM ---------- Previous post was at 03:59 AM ----------
Just tried to Odin v3.09 to NB1... FAIL! Here is the log from Odin. Don't know if you can tell anything from it or not, besides that it failed.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUFNB1_TWRootable_Full_Odin.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
Click to expand...
Click to collapse
Tried it again, it got a few more steps in then failed, then again a few steps more. Then it hung... uh oh! softbricked. None of the "fixes" work. Any more ideas? HELP!!!
---------- Post added at 08:40 AM ---------- Previous post was at 08:34 AM ----------
Cliffhanger68 said:
I tried to downgrade to NB1 before using the same guide and file in the link, got several errors, I don't remember what they were. When I rebooted I was still in OC4. I will try again in the next couple of days (Wife's birthday tomorrow) when I have the extra time. I will update post when I find out something. Thanks for the response and the interest in helping!
---------- Post added at 04:42 AM ---------- Previous post was at 03:59 AM ----------
Just tried to Odin v3.09 to NB1... FAIL! Here is the log from Odin. Don't know if you can tell anything from it or not, besides that it failed.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUFNB1_TWRootable_Full_Odin.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
Click to expand...
Click to collapse
Tried it again, it got a few more steps in then it failed, then again a few steps more, failed. Then it hung... uh oh! softbricked. "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again". None of the "fixes" that I have tried work. Any more ideas? HELP!!!
Cliffhanger68 said:
Tried it again, it got a few more steps in then failed, then again a few steps more. Then it hung... uh oh! softbricked. None of the "fixes" work. Any more ideas? HELP!!!
---------- Post added at 08:40 AM ---------- Previous post was at 08:34 AM ----------
Tried it again, it got a few more steps in then it failed, then again a few steps more, failed. Then it hung... uh oh! softbricked. "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again". None of the "fixes" that I have tried work. Any more ideas? HELP!!!
Click to expand...
Click to collapse
FINALLY!!! got it back up. Running 4.4.2, NB1, rooted.
Cliffhanger68 said:
FINALLY!!! got it back up. Running 4.4.2, NB1, rooted.
Click to expand...
Click to collapse
Im pretty sure the cable you are using is faulty OR the port in which you have connected it is faulty. In this case faulty, does not mean totally broken. Something like kinda loose, not in a particularly good shape. Try using a different port in the PC or a different micro USB cable. Everything you did was fine and how it should have been done. Hardware problem.
TheJuli said:
Im pretty sure the cable you are using is faulty OR the port in which you have connected it is faulty. In this case faulty, does not mean totally broken. Something like kinda loose, not in a particularly good shape. Try using a different port in the PC or a different micro USB cable. Everything you did was fine and how it should have been done. Hardware problem.
Click to expand...
Click to collapse
I think there may be a little truth to that, I used my son's PC (newer hardware) and it got further but still failed several times. I moved it back to mine and used a MoBo USB port and it seemed to do better. I installed the PIT file and finally got it to work after probably 15 to 20 times. Now, I can Odin with no problem, but only the NB1 that is on it now. I tried to update to OC4 and it stuck at the Samsung logo. I re-Odin'd the NB1 which went in with no problem. Now, I'm setting it up, I'm gonna rock 4.4.2 for a while, got scared! . Been going thru Titanium backup and getting it cleaned up a bit. Thanks for all the assistance.
Cliffhanger68 said:
I think there may be a little truth to that, I used my son's PC (newer hardware) and it got further but still failed several times. I moved it back to mine and used a MoBo USB port and it seemed to do better. I installed the PIT file and finally got it to work after probably 15 to 20 times. Now, I can Odin with no problem, but only the NB1 that is on it now. I tried to update to OC4 and it stuck at the Samsung logo. I re-Odin'd the NB1 which went in with no problem. Now, I'm setting it up, I'm gonna rock 4.4.2 for a while, got scared! . Been going thru Titanium backup and getting it cleaned up a bit. Thanks for all the assistance.
Click to expand...
Click to collapse
Glad you got it all sorted out.
There is nothing to be afraid of imo - with these updates files and files, its impossible to hard brick. You simply just hate it when it soft bricks because you have to re do it all again.
BTW - Did you odin the new bootlader after flashing the oc4 update with flashfire? That could be the problem of why it gets stuck to the smasung logo.
TheJuli said:
Im pretty sure the cable you are using is faulty OR the port in which you have connected it is faulty. In this case faulty, does not mean totally broken. Something like kinda loose, not in a particularly good shape. Try using a different port in the PC or a different micro USB cable. Everything you did was fine and how it should have been done. Hardware problem.
Click to expand...
Click to collapse
Just in case anyone is still following this, I ended up going back to stock, letting it update OTA back to Lollipop. Then this week I decided to try again and I was able to direct root my I337, on 5.0.1. OC4, using Kingroot. Then I used w0lfdroid's method to replace Kinguser with Supersu. Worked like a charm. Still rooted after multiple reboots. Then I installed Titanium Backup and took out some of the BS apps and I like my phone a lot better now. Hmmm, what's next? :victory:
Hmmm, maybe I'll try to install a custom recovery... any suggestions on a ROM? Got a lot of reading to do.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Rooted Galaxy S4 SGH-I337 on 5.0.1 Lollipop.
Cliffhanger68 said:
Hmmm, maybe I'll try to install a custom recovery... any suggestions on a ROM? Got a lot of reading to do.
Sent from my Rooted Galaxy S4 SGH-I337 on 5.0.1 Lollipop.
Click to expand...
Click to collapse
Dropped it week before last. Broke the lcd. Ordered a new one, now back up and running!
Related
I had a problem with my phone I couldn't go into CWM and I din't have superSU privileges anymore. So I tried doing a reset and it didn't boot up only to custom OS install screen and I tried using odin to install S4 stock I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 and i get FAIL. can someone please help me with this.. I am also going to try another computer.
Also, redownload the tar file. It could be a bad download.
jd1639 said:
Also, redownload the tar file. It could be a bad download.
Click to expand...
Click to collapse
ok will try that.
here are the messages that I am getting
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
2nd message
ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
what firmware were you running when the issue began? MDL, MF3? sounds like maybe you took the update?
xBeerdroiDx said:
what firmware were you running when the issue began? MDL, MF3? sounds like maybe you took the update?
Click to expand...
Click to collapse
I think that is where the problem started. I tried 2 computers and the same problem. I am redownloading the stock firmware again.
jimsond said:
I think that is where the problem started. I tried 2 computers and the same problem. I am redownloading the stock firmware again.
Click to expand...
Click to collapse
If you had mf3 on, no amount of odin is going to help.
jimsond said:
I think that is where the problem started. I tried 2 computers and the same problem. I am redownloading the stock firmware again.
Click to expand...
Click to collapse
You must have taken the update to MF3. Essentially, you will not be allowed to downgrade firmware back to older versions. The way Samsung is writing the bootloader is there a monotonic counter only going in one direction, up. So if the bootloader has been updated to the latest version by an OTA, you can't revert it back. Currently I believe there is no workaround, but we have some awesome devs on this site so keep your fingers crossed.
jimsond said:
I had a problem with my phone I couldn't go into CWM and I din't have superSU privileges anymore. So I tried doing a reset and it didn't boot up only to custom OS install screen and I tried using odin to install S4 stock I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 and i get FAIL. can someone please help me with this.. I am also going to try another computer.
Click to expand...
Click to collapse
What exactly did you do that caused the problem?
What exactly is the state of your phone now? Can you boot up or not? Please be clear.
jeffreii said:
What exactly did you do that caused the problem?
What exactly is the state of your phone now? Can you boot up or not? Please be clear.
Click to expand...
Click to collapse
I tried the update but it didn't finish. The phone was working but I couldn't go into cwm recovery. I also tried to use TWRP to go into recovery could that be the problem? would this work http://forum.xda-developers.com/showthread.php?t=2360859
jimsond said:
I tried the update but it didn't finish. The phone was working but I couldn't go into cwm recovery. I also tried to use TWRP to go into recovery could that be the problem? would this work http://forum.xda-developers.com/showthread.php?t=2360859
Click to expand...
Click to collapse
You tried what update? What do you mean it didn't work? What do you mean you tried to go into both recoveries? You can only have one on your phone at any given time. Tell me exactly what you did. DETAILS.
Also, again, exactly what is the state of your phone right now? What does it do when you turn it on and what exactly is the problem.
Please try to be clear.
jeffreii said:
You tried what update? What do you mean it didn't work? What do you mean you tried to go into both recoveries? You can only have one on your phone at any given time. Tell me exactly what you did. DETAILS.
Also, again, exactly what is the state of your phone right now? What does it do when you turn it on and what exactly is the problem.
Please try to be clear.
Click to expand...
Click to collapse
HI I just tried this http://forum.xda-developers.com/showthread.php?t=2360859 and how I am able to boot into my phone. How can I tell you if the update over the air did anything? I know there was a problem with the update over the air. The last thing I did was a factory data reset and format SD card. So now I can use the phone and if I try to go into CWM turning of the phone and holding power, up volume and home and it doesn't go in cwm just go to downloading screen. I take out the battery and power up and it works. I think the phone now is not rooted. So should I try to root or try to use odin and install Stock Firmwares..
P.S in kies the current firmware version PDA:MF3 / PHONE:MF3 / CSC:MF3 (ATT)
jimsond said:
HI I just tried this http://forum.xda-developers.com/showthread.php?t=2360859 and how I am able to boot into my phone. How can I tell you if the update over the air did anything? I know there was a problem with the update over the air. The last thing I did was a factory data reset and format SD card. So now I can use the phone and if I try to go into CWM turning of the phone and holding power, up volume and home and it doesn't go in cwm just go to downloading screen. I take out the battery and power up and it works. I think the phone now is not rooted. So should I try to root or try to use odin and install Stock Firmwares..
Click to expand...
Click to collapse
Go into settings, about device, and see what your build number is. If it ends in mf3 you have the update. If it ends in mdl or mdb then you don't and you can still use Odin. If it's mf3 Odin is not going to work.
jimsond said:
HI I just tried this http://forum.xda-developers.com/showthread.php?t=2360859 and how I am able to boot into my phone. How can I tell you if the update over the air did anything? I know there was a problem with the update over the air. The last thing I did was a factory data reset and format SD card. So now I can use the phone and if I try to go into CWM turning of the phone and holding power, up volume and home and it doesn't go in cwm just go to downloading screen. I take out the battery and power up and it works. I think the phone now is not rooted. So should I try to root or try to use odin and install Stock Firmwares..
Click to expand...
Click to collapse
Please don't take offense to this, but you need to hear it:
You have a serious problem - and it's not your phone - it's you. You clearly are not well-versed on what you are doing to your phone. You seem to be just trying things to see if they'll work and a common result is a bricked and unrecoverable phone. Just take a look at the Q & A forums and see how many threads there are about people who didn't read, research, and understand before attempting something...and now they are desperate for help. Your thread is one of those.
You have not yet given a clear indication of what you did to cause your problem in the first place, nor have you explained clearly what your problem was and the current state of your phone. You then asked "should I try this?" and before anyone told you whether or not it was a good idea, you tried it anyways.
You need to step away from your phone and take some time to read, research, and understand what's going on. You don't even know how to tell if your phone is rooted. It seems like you've completely lost your recovery mode, and now you want to try more stuff. You will be lucky if you don't ruin your phone if you keep it up.
You need to read all of this and understand it before you continue:
http://forum.xda-developers.com/showthread.php?t=2301762
http://forum.xda-developers.com/showthread.php?t=2314494
http://forum.xda-developers.com/showthread.php?t=2387577
Once you finish reading that, you'll understand how dangerous your current situation is. Phones on MF3 firmware have no way to recover to stock and, quite often, if you brick your phone there is currently no way to fix it...so you'll have a $650 paperweight.
jd1639 said:
Go into settings, about device, and see what your build number is. If it ends in mf3 you have the update. If it ends in mdl or mdb then you don't and you can still use Odin. If it's mf3 Odin is not going to work.
Click to expand...
Click to collapse
It look like I have mf3 So I f__k up. The phone is working
jimsond said:
It look like I have mf3 So I f__k up. The phone is working
Click to expand...
Click to collapse
Good to hear the phone is working. I wouldn't mess with it any more.
jeffreii said:
Please don't take offense to this, but you need to hear it:
You have a serious problem - and it's not your phone - it's you. You clearly are not well-versed on what you are doing to your phone. You seem to be just trying things to see if they'll work and a common result is a bricked and unrecoverable phone. Just take a look at the Q & A forums and see how many threads there are about people who didn't read, research, and understand before attempting something...and now they are desperate for help. Your thread is one of those.
You have not yet given a clear indication of what you did to cause your problem in the first place, nor have you explained clearly what your problem was and the current state of your phone. You then asked "should I try this?" and before anyone told you whether or not it was a good idea, you tried it anyways.
You need to step away from your phone and take some time to read, research, and understand what's going on. You don't even know how to tell if your phone is rooted. It seems like you've completely lost your recovery mode, and now you want to try more stuff. You will be lucky if you don't ruin your phone if you keep it up.
You need to read all of this and understand it before you continue:
http://forum.xda-developers.com/showthread.php?t=2301762
http://forum.xda-developers.com/showthread.php?t=2314494
http://forum.xda-developers.com/showthread.php?t=2387577
Once you finish reading that, you'll understand how dangerous your current situation is. Phones on MF3 firmware have no way to recover to stock and, quite often, if you brick your phone there is currently no way to fix it...so you'll have a $650 paperweight.
Click to expand...
Click to collapse
Thanks for your input I have a hard time saying on paper what was my problem. I like to talk things out and I use the link that you posted and I have root now..
For two days i have been struggling to root my new Orange Romania N9005.
First of all I downloaded CF Auto Root and Odin 3.09. Followed the steps exactly (i'm not new to rooting) ,Uninstalled Kies and downloaded the latest drivers only, and every single time I try to root it Odin gives the following error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the screen of the note 3 the following error in red : SECURE CHECK FAIL : recovery
I have since tried every single version of ODIN , tried flashing pre-rooted roms only to get my device soft bricked(Fails right at the very end, and then I restored via kies )
,I have tried to change usb ports to no avail, even tried to root it on 4 different laptops.Tried with different cables, with usb debugging on and off, NOTHING WORKS!!!
Please help me I am thinking of setting it on fire!!!
Try install Kies and try again...
/CK
tried with old kies and kies 3 as well.Also tried older drivers.
Do i have a locked BootLoader?This shouldnt be the case as it is an n9005.
Any way to check if bootloader is locked and if so any way to unlock it for the international version?
Thanks!
No one?
Doesn't any one know how to help?Don't know where else to ask.
NavDragan said:
Doesn't any one know how to help?Don't know where else to ask.
Click to expand...
Click to collapse
On the settings page under security..make sure you have reactivation lock uncheck...
Than try again..that's usually the problem
Sent from [email protected] Ass Note III SM-N9005
NavDragan said:
For two days i have been struggling to root my new Orange Romania N9005.
First of all I downloaded CF Auto Root and Odin 3.09. Followed the steps exactly (i'm not new to rooting) ,Uninstalled Kies and downloaded the latest drivers only, and every single time I try to root it Odin gives the following error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the screen of the note 3 the following error in red : SECURE CHECK FAIL : recovery
I have since tried every single version of ODIN , tried flashing pre-rooted roms only to get my device soft bricked(Fails right at the very end, and then I restored via kies )
,I have tried to change usb ports to no avail, even tried to root it on 4 different laptops.Tried with different cables, with usb debugging on and off, NOTHING WORKS!!!
Please help me I am thinking of setting it on fire!!!
Click to expand...
Click to collapse
I had the same issue while rooting my Galaxy S4,tried on every other laptop,different ports,cables and more but then I realized I was using the wrong file.
Yes,the international version comes with Bootloader unlocked so your bootloader is fine.Are you able to boot your phone into Download mode?I am sure u cant boot into Recovery mode,can you?
First go back and check your phone's model no and use the proper file and try again!I will help you,dont worry!
I deactivated the reactivation lock but still the same problem.I have Downloaded the CF-Auto-Root-hlte-hltexx-smn9005.tar file several times same thing every time.My last chance is doing a full wipe of the system and then trying again.I hope orange Romania CSC does't have some sort of security block.
Frustrating thing is the phone is fully functional so i cannot ask for a replacement.And even after the dozens of failed flash attempts it still reads 0x0.
YES!!!Finally.A full wipe did it.!Thank you for your interest in helping me.
iznee said:
On the settings page under security..make sure you have reactivation lock uncheck...
Than try again..that's usually the problem
Sent from [email protected] Ass Note III SM-N9005
Click to expand...
Click to collapse
Thanks that helped! Unlike the OP didnt have to wipe phone.
Thank youu
nsnarayan10 said:
I had the same issue while rooting my Galaxy S4,tried on every other laptop,different ports,cables and more but then I realized I was using the wrong file.
Yes,the international version comes with Bootloader unlocked so your bootloader is fine.Are you able to boot your phone into Download mode?I am sure u cant boot into Recovery mode,can you?
First go back and check your phone's model no and use the proper file and try again!I will help you,dont worry!
Click to expand...
Click to collapse
THank you soo much after following exact instruction that you gave i finally got it rooted!! Thank you!!
nsnarayan10 said:
I had the same issue while rooting my Galaxy S4,tried on every other laptop,different ports,cables and more but then I realized I was using the wrong file.
Yes,the international version comes with Bootloader unlocked so your bootloader is fine.Are you able to boot your phone into Download mode?I am sure u cant boot into Recovery mode,can you?
First go back and check your phone's model no and use the proper file and try again!I will help you,dont worry!
Click to expand...
Click to collapse
thanks for bringing this up.
so where do you get the proper file?
i have the same problem, and a full wi[e has not helped here..
kindly give the correct link.
thanks once again
Before you wanna flash. Don't forget to uncheck reactivation lock, put off your external sd card. And look carefully for your modem and radio. Don't switch with the another kernel before official launch comes.
Sent from my CruelB Note 3 SM-N9005 Snapdragon 800 using Tapatalk
Cruel B said:
Before you wanna flash. Don't forget to uncheck reactivation lock, put off your external sd card. And look carefully for your modem and radio. Don't switch with the another kernel before official launch comes.
Sent from my CruelB Note 3 SM-N9005 Snapdragon 800 using Tapatalk
Click to expand...
Click to collapse
h guys!
i asked for 'the propper files' link?...
my phone now entres boot-loop when i restart it. any help?
...after several loops, it finally completes start up. by now i'd have left it alone for about 15 mins!
tanks, in advance..
---------- Post added at 03:22 PM ---------- Previous post was at 02:51 PM ----------
aidelnma said:
THank you soo much after following exact instruction that you gave i finally got it rooted!! Thank you!!
Click to expand...
Click to collapse
h guys!
i asked for 'the propper files' link?...
my phone now entres boot-loop when i restart it. any help?
...after several loops, it finally completes start up. by now i'd have left it alone for about 15 mins!
tanks, in advance..
THANK YOU!
Yes, the reactivation lock did it for me too. I was stuck at exactly the same point and couldn't think of why, and this didn't even come to mind. In fact, I forgot that I even did that, but it worked. !!!
nsnarayan10 said:
I will help you,dont worry!
Click to expand...
Click to collapse
Help please, I have a (Note 3) SM-N900V on JSS15J.N900VVRUBMJE.
I bought it on Jan 12th ish, and took the firmware update as soon as I saw it because of some reading I had done.... shouldn't have done that I guess.
I am still totally unable to root this thing, Kingo, Odin v3.0.9. I am willing to do w/e (go back to older firmware even if possible)
I know there are no guarantees in this attempt, and would not hold you to anything, I have rooted every other android I have had and am very familiar with the process, any help you can offer would be greatly appreciated
https://plus.google.com/u/0/+JoelJrMcCracken/
This has helped. Thanks a lot.
iznee said:
On the settings page under security..make sure you have reactivation lock uncheck...
Than try again..that's usually the problem
Sent from [email protected] Ass Note III SM-N9005
Click to expand...
Click to collapse
This helped a lot. Problem fixed.
regards
iznee said:
On the settings page under security..make sure you have reactivation lock uncheck...
Than try again..that's usually the problem
Sent from [email protected] Ass Note III SM-N9005
Click to expand...
Click to collapse
Thanks. 1.5 years later and this helped me too!
iznee said:
On the settings page under security..make sure you have reactivation lock uncheck...
Than try again..that's usually the problem
Sent from [email protected] Ass Note III SM-N9005
Click to expand...
Click to collapse
U sir are a life saver!
Thanks!
iznee said:
On the settings page under security..make sure you have reactivation lock uncheck...
Than try again..that's usually the problem
Sent from [email protected] Ass Note III SM-N9005
Click to expand...
Click to collapse
Thank you, you saved me from pulling my hair out :highfive:
Hello to all.
I have a Tab 3 (that was given to me)on Software version T217SVPUBOH1
Hardware Version T217S.04
Model Number SM-TS17S
Android Ver: 4.4.2
Baseband T217SVPUBOH1
I guess Stock Kernel 3.4.0-1715729
Build Number KOT49H.T217SVOUBOH1
Could Someone direct me to the PROPER CF Auto Root and Odin? I am not planning on changing the ROM, I just want to Add Viper to increase the Audio Volume and maybe some other root controls.
Any and All Help Is Appreciated
Thank you in Advance
Blessings
Thank a lott!!!already rooted!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just wanted to let you guys know how to unroot the AT&T Galaxy Note 3 especially since it looks like you have to do some digging to find the correct files for the SM-N900A Galaxy Note 3.
I have created a step by step guide: Here
All credits go to designgears' thread!
techfanatic9 said:
Just wanted to let you guys know how to unroot the AT&T Galaxy Note 3 especially since it looks like you have to do some digging to find the correct files for the SM-N900A Galaxy Note 3.
I have created a step by step guide: Here
All credits go to designgears' thread!
Click to expand...
Click to collapse
Thanks a lot sir!!
Thank you
Lose regional lock?
supers2k said:
Thank you
Click to expand...
Click to collapse
If you unroot Lose the regional unlock????
can you at least put a warning up, if you are on MJ5 and you try this method you will brick your device?
Thanks.
What if you are on MI1, can you still do the MJ9 one click and upgrade to MJ9 unrooted?
dead link
I have been looking for a way to unroot my n900a and everywhere i have gone the files needed leave me at a dead link...can anyone help with this a mirror or am I missing something here?
If you rooted with Kingo, just unroot using the unroot commend in SU. After a couple of restarts everything will be back to normal. This also works on MJ5..
Sorry, but this doesn't work.
I keep getting a "FAILED" message.
If you are on mj5 and you flash it using Odin with the mj5 stock ROM will the Knox counter trigger?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Kitkat 4.4 Leak
Could you use this to return a Note 3 to stock that was running the leaked build of kitkat?
Failed
I'm getting a failed message as well. Seems like the OP isn't responding to anyone who was unsuccessful returning back to stock.
Also get the failed message.
many more people are getting it on his website with zero response.
songokussm said:
Also get the failed message.
many more people are getting it on his website with zero response.
Click to expand...
Click to collapse
Yeah. With all the ads on OPs website, OP is just probably here to make some extra revenue from the ads.
i have a friend who works for Samsung mobile and she tried putting on kitkat from her work laptop. The firmware she has comes directly from Samsung but it wouldn't let her because it kept reading that my phone had been rooted. i had used this app ginger unroot to supposedly remove my root but it apparently didn't work. I would like to know if i use this method will that by pass the message?
You won't get anywhere with this method. Read our replies.
Odin Fails
Hi I have my AT&T Note 3 currently rooted but want to put it back to normal. I never changed the ROM and Knox hasn't been tripped. But what I did was uninstall certain apps that were preloaded with out backing them up first. Also my wifi decided to not work anymore and I cant do any updates. So I decided I wanted to reinstall stock firmware. I downloaded the firmware from SamMobile and used Odin 3.09 like it was recommended. But every time I try Odin Fails. I also tried this method as well and Odin fails. I tried mulitple cords, usb ports, and different computers. Here is what the Odin log says
<ID:0/019> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900AUCUBMI9_N900AATTBMI9_N900AUCUBMI9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/019> Odin v.3 engine (ID:19)..
<ID:0/019> File analysis..
<ID:0/019> SetupConnection..
<ID:0/019> Initialzation..
<ID:0/019> Get PIT for mapping..
<ID:0/019> Firmware update start..
<ID:0/019> SingleDownload.
<ID:0/019> sbl1.mbn
<ID:0/019> NAND Write Start!!
<ID:0/019> FAIL! (Auth)
<ID:0/019>
<ID:0/019> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
StormChaser83 said:
Sorry, but this doesn't work.
I keep getting a "FAILED" message.
Click to expand...
Click to collapse
Did you figure out why it was failing and if there is any fix for it?
Unfortunately, I will have to unroot my phone.... work requires me to encrypt my device... which apparently won't encrypt with root. Is this a pretty safe method to unroot?
I apologize if my situation is here somewhere. I have read through so many forums and can't find what I need, plus I am sort of new at this. So here goes.
I rooted my Samsung I337 about 8 months ago for the first time. I can't remember exactly how, but I followed a thread here to do it. It worked perfectly! I then flashed the Golden Eye rom to it through TWRP. I have loved it since then. I did a back up of my original rom on my phone from the start. Well, I decided yesterday to unroot it. I followed the directions from a thread here and it seems to have worked except that when I turn it on, the custom screen is first. However, I have no supersu and when I try to get rooting apps it tells me I need to root my phone. So I assume it worked.
Well, I have used it for a day and now remember why I rooted it in the first place. I want to put it back but can't seem to do that. I downloaded Odin, connected my phone, and when I try and download the file to it, it fails. This is what I get.
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
The only thing I can see is that I am told the COM port should be yellow and mine is blue. Does that make a difference? What could the issue be? Any help would be awesome!
Ok, I figured it out. I went about it a different way. Odin wasn't working for me so I went the route of Motochopper and it worked perfectly.
Now, my question is, before I rooted again I wanted to upgrade from 4.2.2 to 4.3. However, every time it tried, it failed. Each time it would download the update it would reboot to TWRP and then I would get the "something interrupted the download" so it wouldn't finish. How would I get around that? How do I get the update?
traderkat64 said:
Ok, I figured it out. I went about it a different way. Odin wasn't working for me so I went the route of Motochopper and it worked perfectly.
Now, my question is, before I rooted again I wanted to upgrade from 4.2.2 to 4.3. However, every time it tried, it failed. Each time it would download the update it would reboot to TWRP and then I would get the "something interrupted the download" so it wouldn't finish. How would I get around that? How do I get the update?
Click to expand...
Click to collapse
Don't. Getting the update will lock your bootloader and you won't get TWRP and any ROM freedom anymore. If you want 4.3, use the StockUp ROM or something. Then you can still switch to something like Google Edition 4.4.2 or any other ROM if you ever want to.
DeadlySin9 said:
Don't. Getting the update will lock your bootloader and you won't get TWRP and any ROM freedom anymore. If you want 4.3, use the StockUp ROM or something. Then you can still switch to something like Google Edition 4.4.2 or any other ROM if you ever want to.
Click to expand...
Click to collapse
Ok, I won't update!! Thanks!!!!
Here is the the stock T-Mobile newest firmware that was just pushed to everyone's phone that was not rooted.. >>> N930TUVU2API4
FYI::: Do not install this on your phone if you want to keep root<<<< YOU HAVE BEEN WARNED!!!!!
Otherwise Odin this if you want to be on the latest firmware..
Download Zip File -- use your favorite zip program to unpack it, and have fun..
galaxyuser88 said:
Here is the the stock T-Mobile newest firmware that was just pushed to everyone's phone that was not rooted.. >>> N930TUVU2API4
FYI::: Do not install this on your phone if you want to keep root<<<< YOU HAVE BEEN WARNED!!!!!
Otherwise Odin this if you want to be on the latest firmware..
Download Zip File -- use your favorite zip program to unpack it, and have fun..
Click to expand...
Click to collapse
Good one bud.... I can't get it last night but I'm glad u did[emoji106]
TwisT3DroiD_N920T
Threads of this nature do not belong in the development section. Please read the sticky titled "Rules for Posting in Development" before posting in there again.
THREAD MOVED
galaxyuser88 said:
Here is the the stock T-Mobile newest firmware that was just pushed to everyone's phone that was not rooted.. >>> N930TUVU2API4
FYI::: Do not install this on your phone if you want to keep root<<<< YOU HAVE BEEN WARNED!!!!!
Otherwise Odin this if you want to be on the latest firmware..
Download Zip File -- use your favorite zip program to unpack it, and have fun..
Click to expand...
Click to collapse
Can this be odined over the rooted ROM, to return to stock... Before returning to store
Sent from my SM-N930T using XDA-Developers mobile app
PhilPan said:
Can this be odined over the rooted ROM, to return to stock... Before returning to store
Sent from my SM-N930T using XDA-Developers mobile app
Click to expand...
Click to collapse
yes, as odin wipes your internal card and firmware..
PhilPan said:
Can this be odined over the rooted ROM, to return to stock... Before returning to store
Sent from my SM-N930T using XDA-Developers mobile app
Click to expand...
Click to collapse
just factory reset.....poof root gone!
galaxyuser88 said:
Here is the the stock T-Mobile newest firmware that was just pushed to everyone's phone that was not rooted.. >>> N930TUVU2API4
FYI::: Do not install this on your phone if you want to keep root<<<< YOU HAVE BEEN WARNED!!!!!
Otherwise Odin this if you want to be on the latest firmware..
Download Zip File -- use your favorite zip program to unpack it, and have fun..
Click to expand...
Click to collapse
Tried flashing another stock ROM trying to get back to stock from root. That didn't work. Then I flashed this and am able to boot. But my mobile data icon is just 4G instead of being 4G LTE (or LTE), and I'm missing the WiFi calling button as well.
So, I probably need to flash the radios and everything with this. So, do I flash the AP first from the ZIP, then everything else after, or can I flash them all at once? Not an experienced ODIN user. Only used it a handful of times.
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
ted77usa said:
Good one bud.... I can't get it last night but I'm glad u did[emoji106]
TwisT3DroiD_N920T
Click to expand...
Click to collapse
Throwing you in the mix as well. Please see my post above.
-BoneZ- said:
Tried flashing another stock ROM trying to get back to stock from root. That didn't work. Then I flashed this and am able to boot. But my mobile data icon is just 4G instead of being 4G LTE (or LTE), and I'm missing the WiFi calling button as well.
So, I probably need to flash the radios and everything with this. So, do I flash the AP first from the ZIP, then everything else after, or can I flash them all at once? Not an experienced ODIN user. Only used it a handful of times.
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
Throwing you in the mix as well. Please see my post above.
Click to expand...
Click to collapse
@-BoneZ-
U said that u tried to go back to stock from root? Meaning u have pgc firmware and u CAN'T use this PI4 firmware to go back to stock..... when u do that u stuck with newer Bootloader and u not able to root again.... if u need to go back then flash PGC original firmware.
EDIT:
If u already on PI4 then flash all at once.... BL AP CP CSC....
TwisT3DroiD_N920T
-BoneZ- said:
Tried flashing another stock ROM trying to get back to stock from root. That didn't work. Then I flashed this and am able to boot. But my mobile data icon is just 4G instead of being 4G LTE (or LTE), and I'm missing the WiFi calling button as well.
So, I probably need to flash the radios and everything with this. So, do I flash the AP first from the ZIP, then everything else after, or can I flash them all at once? Not an experienced ODIN user. Only used it a handful of times.
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
Throwing you in the mix as well. Please see my post above.
Click to expand...
Click to collapse
Yes you must flash all parts of this to be on stock PI4 ROM. But remember that you will lose root and not get it back.
You sir are a life saver thank you so much i was stupid didnt read thru forums and tried to root on the latest update...this flashed via odin brought my phone back to life
ted77usa said:
@-BoneZ-
U said that u tried to go back to stock from root? Meaning u have pgc firmware and u CAN'T use this PI4 firmware to go back to stock..... when u do that u stuck with newer Bootloader and u not able to root again.... if u need to go back then flash PGC original firmware.
EDIT:
If u already on PI4 then flash all at once.... BL AP CP CSC....
TwisT3DroiD_N920T
Click to expand...
Click to collapse
galaxyuser88 said:
Yes you must flash all parts of this to be on stock PI4 ROM. But remember that you will lose root and not get it back.
Click to expand...
Click to collapse
Thanks, guys. Those were the answers I was looking for.
Hello I want to say thank you for providing the T-Mobile Firmware Package for restoring the Note 7 to its original state after a Rooting atampt botched up. I also had this problem but now restored the phone with the supplied firmware. Thank you.
I do have one problem though. The firmware supplied has the first update with the annoying Safety Recall statement in that hugh box while plug is inserted, pulled out and turned on. I like to know if you can supply the original firmware that the phone came boxed with or if you have some kind of way of getting rid of that stupid annoying big box message that pops up all the time.
And again thank you so much.
Ok I feel like a dumb ass,
This has to be the most complicated root, update I have ever seen. I accidently hit update earlier today which reduced my battery life to 60% I tried living with it today and it was driving me absolutely nuts I thought about taking the phone in and getting a damn iphone just because I'm tired of messing around with this phone..... I tried to root using post one however it keeps failing, I tried rooting using post 2 that also failed. I tried going back one firmware version that also didn't work, I tried doing the samsung smart switch recovery it asks for a code I tried the serial of the phone and model number that also didn't work. Can someone please explain either how to get root from the newest firmware or to revert back to a older firmware that dosen't have this stupid battery restriction. The information of my phone is below .
I'm tired of the battery restriction and tired of hitting okay I know my phone will blow up....
Samsung Note 7 Tmobile
SM-N930T
6.0.1
Build Number
MMB29M.N930TUVU2APK1
any help is appreciated as I am pulling out my hair...
mikesx4911 said:
Ok I feel like a dumb ass,
This has to be the most complicated root, update I have ever seen. I accidently hit update earlier today which reduced my battery life to 60% I tried living with it today and it was driving me absolutely nuts I thought about taking the phone in and getting a damn iphone just because I'm tired of messing around with this phone..... I tried to root using post one however it keeps failing, I tried rooting using post 2 that also failed. I tried going back one firmware version that also didn't work, I tried doing the samsung smart switch recovery it asks for a code I tried the serial of the phone and model number that also didn't work. Can someone please explain either how to get root from the newest firmware or to revert back to a older firmware that dosen't have this stupid battery restriction. The information of my phone is below .
I'm tired of the battery restriction and tired of hitting okay I know my phone will blow up....
Samsung Note 7 Tmobile
SM-N930T
6.0.1
Build Number
MMB29M.N930TUVU2APK1
any help is appreciated as I am pulling out my hair...
Click to expand...
Click to collapse
Have you tried this yet?
★[ROM] [STOCK] N930TUVU1APGC | 6.0.1 |… | T-Mobile Samsung Galaxy Note 7
http://forum.xda-developers.com/tmo...om-n930tuvu1apgc-6-0-1-deodexed-knox-t3461513
---------- Post added at 08:04 AM ---------- Previous post was at 07:56 AM ----------
mikesx4911 said:
Ok I feel like a dumb ass,
This has to be the most complicated root, update I have ever seen. I accidently hit update earlier today which reduced my battery life to 60% I tried living with it today and it was driving me absolutely nuts I thought about taking the phone in and getting a damn iphone just because I'm tired of messing around with this phone..... I tried to root using post one however it keeps failing, I tried rooting using post 2 that also failed. I tried going back one firmware version that also didn't work, I tried doing the samsung smart switch recovery it asks for a code I tried the serial of the phone and model number that also didn't work. Can someone please explain either how to get root from the newest firmware or to revert back to a older firmware that dosen't have this stupid battery restriction. The information of my phone is below .
I'm tired of the battery restriction and tired of hitting okay I know my phone will blow up....
Samsung Note 7 Tmobile
SM-N930T
6.0.1
Build Number
MMB29M.N930TUVU2APK1
any help is appreciated as I am pulling out my hair...
Click to expand...
Click to collapse
If you can restore it back to stock. This thread may help. It's helping me.
Need help with Package Disabler 6.3 | Samsung Galaxy Note 7
http://forum.xda-developers.com/note-7/help/help-package-disabler-6-3-t3494052
So I just tried to do the instructions from the ROM STOCK below however I get stuck on step 5 when I try to flash the "MODIFIED_TMO_SPR_N930PVPU1APH3_REV00_ENGBOOT_FIRM WARE.tar.md5" it FAILS at
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> adspso.bin
<ID:0/003> apdp.mbn
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Auth) <------------------------
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I than did a quick search had someone suggest checking "re-partition" that also failed with the same error. After rebooting the phone it wouldn't boot anymore and was stuck at "an error has occured while updating the device software. Use the emergency recovery function in the smart switch pc software"
So I gave that a go and it tells me that the device is not supported after doing the model and serial number lol.
ConcernedCustomer said:
Have you tried this yet?
★[ROM] [STOCK] N930TUVU1APGC | 6.0.1 |… | T-Mobile Samsung Galaxy Note 7
http://forum.xda-developers.com/tmo...om-n930tuvu1apgc-6-0-1-deodexed-knox-t3461513
---------- Post added at 08:04 AM ---------- Previous post was at 07:56 AM ----------
If you can restore it back to stock. This thread may help. It's helping me.
Need help with Package Disabler 6.3 | Samsung Galaxy Note 7
http://forum.xda-developers.com/note-7/help/help-package-disabler-6-3-t3494052
Click to expand...
Click to collapse
mikesx4911 said:
So I just tried to do the instructions from the ROM STOCK below however I get stuck on step 5 when I try to flash the "MODIFIED_TMO_SPR_N930PVPU1APH3_REV00_ENGBOOT_FIRM WARE.tar.md5" it FAILS at
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> adspso.bin
<ID:0/003> apdp.mbn
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Auth) <------------------------
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I than did a quick search had someone suggest checking "re-partition" that also failed with the same error. After rebooting the phone it wouldn't boot anymore and was stuck at "an error has occured while updating the device software. Use the emergency recovery function in the smart switch pc software"
So I gave that a go and it tells me that the device is not supported after doing the model and serial number lol.
Click to expand...
Click to collapse
I was able to stop the 60% update with package disabler, but was also trying to go back to pgc update...getting the same fails as you. 3 Button into recovery and wipe everything then reboot. Should start you fresh to use the phone
Sent from my SM-G935T using XDA-Developers mobile app
ArmyofTracy said:
I was able to stop the 60% update with package disabler, but was also trying to go back to pgc update...getting the same fails as you. 3 Button into recovery and wipe everything then reboot. Should start you fresh to use the phone
Sent from my SM-G935T using XDA-Developers mobile app
Click to expand...
Click to collapse
If only it was that easy. As of now I can't even get into android it fails to boot. I cleared cache and factory reset and still won't boot. I'm sure I will have to flash now for sure from recovery or download mode. I think Samsung is ****n with us somehow to not let us flash.
mikesx4911 said:
If only it was that easy. As of now I can't even get into android it fails to boot. I cleared cache and factory reset and still won't boot. I'm sure I will have to flash now for sure from recovery or download mode. I think Samsung is ****n with us somehow to not let us flash.
Click to expand...
Click to collapse
The same thing happened to me. I re-flashed to the recent firmware I had installed originally (the one with the big ugly safety recall message from September). I flashed everything at once BL, AP, CP and CSC(I used the HOME_CSC_*.tar.md5 named file because I was returning to stock)
This site appears to be an archive for all Android devices. You can find the firmware of your phone using the model going back to launch date.
Download Firmware – Samsung Update
http://updato.com/firmware-archive-select-model
I think you will find this thread useful as well. It contains definitions and explanations on flashing and working with Odin. I just wish there was more information.
Good luck
Galaxy Note 7 All-In-One Information & A… | Samsung Galaxy Note 7
http://forum.xda-developers.com/note-7/help/galaxy-note-7-one-information-answers-t3448689
Is there a way too get back to PGC? That was the one before the recall? I've tried flashing it and it fails
Sent from my SM-G935T using XDA-Developers mobile app
ConcernedCustomer said:
The same thing happened to me. I re-flashed to the recent firmware I had installed originally (the one with the big ugly safety recall message from September). I flashed everything at once BL, AP, CP and CSC(I used the HOME_CSC_*.tar.md5 named file because I was returning to stock)
This site appears to be an archive for all Android devices. You can find the firmware of your phone using the model going back to launch date.
Download Firmware – Samsung Update
http://updato.com/firmware-archive-select-model
I think you will find this thread useful as well. It contains definitions and explanations on flashing and working with Odin. I just wish there was more information.
Good luck
Galaxy Note 7 All-In-One Information & A… | Samsung Galaxy Note 7
http://forum.xda-developers.com/note-7/help/galaxy-note-7-one-information-answers-t3448689
Click to expand...
Click to collapse
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Failed again... Tried both CSC files