Cant obtain root for MJE - Verizon Galaxy Note 3 Q&A, Help & Troubleshooting

Hey everyone. Hoping someone can help. I asked questions in the URDLV thread but got my hand slapped because that thread isn't in the official Verizon forums.
No idea what Im doing wrong. Here are the details.. I got my CSC. I downloaded N900VVRUBMJE_N900VVZWMJE.
I have cygwin installed. I have Universal-RDLV_v05 on my desktop. I open cygwin and cd to that folder. I then run ./URDLV.sh full (Path To My MJE tar.md5) inside of cygwin.
When I do this it extracts the firmware, says its hooking system image, verifies system hook, finds system hook and then creates an odin flash able tar. The creation pieces takes about 15 seconds and a new tar is in my output folder. I then put the phone into download mode and use odin to AP that tar.md5 file. Odin gets all the way to the end and then it fails. If I reboot the phone its corrupt and I have to odin the regular MJE to get back up and running.
What am I doing wrong? I don't get any errors that indicate that Im having issues when it is creating the tar. And the regular tar I have before going through this mess is fine as I can Odin it ok before running the script. Verizon Note 3.
I want to add that I have followed the steps in post 1127 of that thread exactly, using the firmware for my phone, and it still failed at the end.
http://forum.xda-developers.com/show...postcount=1127
Not sure where I am going wrong on this.

To expand on my last post - I decided to redownload the tar file from sammobile and start the whole process over again. I still get the fail when pushing the created tar file in Odin so I started following GalaxHE's post again.
This time I get all the way to this part:
ComputerName /cygdrive/c/temp/MK2_stock
$ tar -H ustar -c boot.img modem.bin rpm.mbn system.img.ext4 cache.img.ext4 NON-HLOS.bin sbl1.mbn tz.mbn hidden.img.ext4 recovery.img sdi.mbn > MK2VEGA.tar
In my case, I named the files MJE_stock. I run the above script in cygwin and get this error:
/cygdrive/c/temp/MJE_stock
$ tar -H ustar -c boot.img modem.bin rpm.mbn system.img.ext4 cache.img.ext4 NON-HLOS.bin sbl1.mbn tz.mbn hidden.img.ext4 recovery.img sdi.mbn > MJEVEGA.tar
tar: hidden.img.ext4: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
This file does NOT exist on my MJE_stock folder. I never touched it in any way. I just went back to the original MJE file I downloaded from sammobile, extracted it down again, and there is no hidden.img.ext4 file anywhere to be seen.
What is this file and how important is it? the MJE from sammobile restores my phone fine, even though that file isnt in it.
I packaged the file by taking the piece regarding that hidden file out. Worse case I figured I repackage and start from there. Went through the remaining steps and pushed the file with Odin and once again it fails. Same place each time.
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Someone, PLEASE HELP.

Hello sir,
First step. Relax. I'll take care of ya. '/cygdrive/c/temp/MK2_stock' it looks like you might have downloaded the wrong package.
Here is stock MJE
Download that. Next, you'll want to get Kingo root here
Ignore all the hubub about it, it's fine. Go ahead and get that.
System.img is giving a fail auth error either because it's for the S4, or it's because the file is not 'signed' meaning it's not authorized by Verizon/Samsung, since it's not official, or it wasn't made for your specific model. PM me if you need any further assistance.
For further reference, you can find all VZW firmware and modems in this thread here

ryanbg said:
Hello sir,
First step. Relax. I'll take care of ya. '/cygdrive/c/temp/MK2_stock' it looks like you might have downloaded the wrong package.
Here is stock MJE
Download that. Next, you'll want to get Kingo root here
Ignore all the hubub about it, it's fine. Go ahead and get that.
System.img is giving a fail auth error either because it's for the S4, or it's because the file is not 'signed' meaning it's not authorized by Verizon/Samsung, since it's not official, or it wasn't made for your specific model. PM me if you need any further assistance.
For further reference, you can find all VZW firmware and modems in this thread here
Click to expand...
Click to collapse
Hello. Thanks for the reply.
Despite mentioning MK2, I did use MJE. As I mentioned, I can flash the MJE file before modifying it with URDLV fine. I obtained my CSC and used that to determine that MJE was the right file for me.
Based on the name of the file you linked me to, thats the same file I used. Its like somehow when using URDLV the system.img is becoming corrupted.
I wouldn't think Verizon would use the same MJE file for the S4 as it does for the note? Wouldn't it be completely different?
I was really trying to avoid using Kingo since it seems like no one knows exactly what all its doing yet.

GaresTaylan said:
Hello. Thanks for the reply.
Despite mentioning MK2, I did use MJE. As I mentioned, I can flash the MJE file before modifying it with URDLV fine. I obtained my CSC and used that to determine that MJE was the right file for me.
Based on the name of the file you linked me to, thats the same file I used. Its like somehow when using URDLV the system.img is becoming corrupted.
I wouldn't think Verizon would use the same MJE file for the S4 as it does for the note? Wouldn't it be completely different?
I was really trying to avoid using Kingo since it seems like no one knows exactly what all its doing yet.
Click to expand...
Click to collapse
The URDLV program you are running modifies MJE. You are correct. The problem is that when you modify that file, you break the digital signature on that file, meaning it is no longer the original file and is not authorized to be flashed. It appears that program is for people without signature verification enabled aka 'unlocked bootloader' if you will. The Verizon Note 3 does not have such luxury. I wouldn't worry about Kingo. It's a closed source exploit because they don't want it patched, which might make some people uncomfortable, and rightfully so, but I've yet to see any implications from it and I've used it multiple times on multiple devices. Vroot was the sketchy one sending IMEIs to China.

Related

Using Odin to reflash 4.3 baseband on I337m

Been using 4.3 on my telus I337M for over a month now. Everything has worked perfectly except for MMS. My apn settings are fine, i've flashed three different roms over the last month and a half. No call or data drops have been noticed.
My best guess is that the baseband didn't properly flash (although my phone does say MK6). I used this thread to do so
http://forum.xda-developers.com/showpost.php?p=47819176&postcount=9322
when using MobileOdin, my android was green, I held the power key for 10 secs and it rebooted my phone. It said MK6, so I assumed it succeeded, except for mms.
I can't reuse MobileOdin, since I'm warned that its not available for 4.3 yet.
My question is, how can I use Odin to reflash my baseband? I'm an Odin novice. Unless someone might have another idea as to why my mms is no longer working after the update.
Go to sammobile.com and download the mk6 firmware. Use that in Odin
jd1639 said:
Go to sammobile.com and download the mk6 firmware. Use that in Odin
Click to expand...
Click to collapse
Two questions... won't I lose root when flashing the firmware from sammobile? Also, won't that install Knox and cause a bunch of problems? I have the baseband itself, I just don't know how to install it through Odin.
GuySmiles said:
Two questions... won't I lose root when flashing the firmware from sammobile? Also, won't that install Knox and cause a bunch of problems? I have the baseband itself, I just don't know how to install it through Odin.
Click to expand...
Click to collapse
You will definitely lose root and you'll have to re-root. Knox will also be part of mk6. What do you mean you have the baseband? But you don't know how to install it with Odin. What file format its it in?
jd1639 said:
You will definitely lose root and you'll have to re-root. Knox will also be part of mk6. What do you mean you have the baseband? But you don't know how to install it with Odin. What file format its it in?
Click to expand...
Click to collapse
It's a modem.bin file, which I heard can be flashed through Odin. I originally flashed it through mobile odin, but the mobie version doesn't as of yet work with 4.3
I have Odin 3.09, I just don't know where to load it within Odin, or what spots to tick or untick within Odin. Its a confusing program for me. I don't want to wipe my phone (although i'll backup just in case), but just want to re-flash the baseband through the modem.bin file (MK6) I got from the link in the 1st post. I just need the steps in order to do that.
GuySmiles said:
It's a modem.bin file, which I heard can be flashed through Odin. I originally flashed it through mobile odin, but the mobie version doesn't as of yet work with 4.3
I have Odin 3.09, I just don't know where to load it within Odin, or what spots to tick or untick within Odin. Its a confusing program for me. I don't want to wipe my phone (although i'll backup just in case), but just want to re-flash the baseband through the modem.bin file (MK6) I got from the link in the 1st post. I just need the steps in order to do that.
Click to expand...
Click to collapse
Ok, you'll want to load it in the phone slot in Odin, browse to it. Just have auto-reboot and f.reset checked. Don't check anything else, this should be the default settings.
GuySmiles said:
It's a modem.bin file, which I heard can be flashed through Odin. I originally flashed it through mobile odin, but the mobie version doesn't as of yet work with 4.3
I have Odin 3.09, I just don't know where to load it within Odin, or what spots to tick or untick within Odin. Its a confusing program for me. I don't want to wipe my phone (although i'll backup just in case), but just want to re-flash the baseband through the modem.bin file (MK6) I got from the link in the 1st post. I just need the steps in order to do that.
Click to expand...
Click to collapse
You can only flash .tar file formats using Odin(desktop), a .bin file will not work.
How to use Odin
jd1639 said:
Ok, you'll want to load it in the phone slot in Odin, browse to it. Just have auto-reboot and f.reset checked. Don't check anything else, this should be the default settings.
Click to expand...
Click to collapse
Difference of opinion here. DO NOT Check auto-reboot. Odin and the mobile.bin have to cook for about 2 min 15 sec or the change won't happen. When you get a green pass on Odin and the bar on the face of your phone is finished, then you can unplug it and manually reboot the phone. The modem.bin file will work, I've done it several times now.
GuySmiles said:
It's a modem.bin file, which I heard can be flashed through Odin. I originally flashed it through mobile odin, but the mobie version doesn't as of yet work with 4.3
I have Odin 3.09, I just don't know where to load it within Odin, or what spots to tick or untick within Odin. Its a confusing program for me. I don't want to wipe my phone (although i'll backup just in case), but just want to re-flash the baseband through the modem.bin file (MK6) I got from the link in the 1st post. I just need the steps in order to do that.
Click to expand...
Click to collapse
rfrenz said:
Difference of opinion here. DO NOT Check auto-reboot. Odin and the mobile.bin have to cook for about 2 min 15 sec or the change won't happen. When you get a green pass on Odin and the bar on the face of your phone is finished, then you can unplug it and manually reboot the phone. The modem.bin file will work, I've done it several times now.
Click to expand...
Click to collapse
I stand corrected. Thanks
Not a Problem
muniz_ri said:
I stand corrected. Thanks
Click to expand...
Click to collapse
No problem, I just wish that Mobile Odin would get itself updated.
rfrenz said:
Difference of opinion here. DO NOT Check auto-reboot. Odin and the mobile.bin have to cook for about 2 min 15 sec or the change won't happen. When you get a green pass on Odin and the bar on the face of your phone is finished, then you can unplug it and manually reboot the phone. The modem.bin file will work, I've done it several times now.
Click to expand...
Click to collapse
Thanks for the tips.
I was hoping that the modem.bin file would work, it loads in Odin but fails once it tries to flash onto my phone. I've tried all the basics (reinstall usb drivers, different versions of Odin etc.) to get it to flash but am currently stuck. There's something i'm missing. Any ideas as to what that can be?
Modem & Odin
GuySmiles said:
Thanks for the tips.
I was hoping that the modem.bin file would work, it loads in Odin but fails once it tries to flash onto my phone. I've tried all the basics (reinstall usb drivers, different versions of Odin etc.) to get it to flash but am currently stuck. There's something i'm missing. Any ideas as to what that can be?
Click to expand...
Click to collapse
Have you done as I suggested and unchecked the auto-boot box and allowed things to cook for a full 2-1/2 minutes? That was the key for me. If you check the auto-boot box it will never install. This is a step by step guide:
-start Odin.
-Select "phone" and fetch the modem.bin file.
-Only thing checked should be "F. Reset Time"
-Put phone in download mode
-Plug in USB
-hit Start
Let it reboot and thou shalt have signal (this is where you wait the 2-1/2 minutes)
rfrenz said:
Have you done as I suggested and unchecked the auto-boot box and allowed things to cook for a full 2-1/2 minutes? That was the key for me. If you check the auto-boot box it will never install. This is a step by step guide:
-start Odin.
-Select "phone" and fetch the modem.bin file.
-Only thing checked should be "F. Reset Time"
-Put phone in download mode
-Plug in USB
-hit Start
Let it reboot and thou shalt have signal (this is where you wait the 2-1/2 minutes)
Click to expand...
Click to collapse
I have done all that. Especially unchecking the auto-boot box and leaving f.reset time checked and unchecked.
In the top left box, it loads modem.bin and a green bar slides across. Then that top left box goes red and says FAIL!
This is what is written
<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> modem.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005>
<ID:0/005> Receive Response from boot-loader
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
It seems that when it writes to the phone it gets stuck somehow. I'm not sure why. My only guess at this point is that because my cat ate my original cable, it could be the issue. I tried using an HTC one cable, a nexus 7 2013 cable, and an "official" samsung cable I bought off amazon, all without success.
I also tried installing samsung USB drivers which also doesn't seem to have worked. Some others have had the same problem on xda, sadly no solution.
Try using Odin 3.09?
GuySmiles said:
I have done all that. Especially unchecking the auto-boot box and leaving f.reset time checked and unchecked.
In the top left box, it loads modem.bin and a green bar slides across. Then that top left box goes red and says FAIL!
This is what is written
<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> modem.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005>
<ID:0/005> Receive Response from boot-loader
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
It seems that when it writes to the phone it gets stuck somehow. I'm not sure why. My only guess at this point is that because my cat ate my original cable, it could be the issue. I tried using an HTC one cable, a nexus 7 2013 cable, and an "official" samsung cable I bought off amazon, all without success.
I also tried installing samsung USB drivers which also doesn't seem to have worked. Some others have had the same problem on xda, sadly no solution.
Click to expand...
Click to collapse
See if Odin 3.09 will do the trick for you. You can get it here along with other good info - http://forum.xda-developers.com/showthread.php?t=2189539 and here are instruction with a picture with download info. Make sure the mobile.bin file is in the CP (Phone) flashing area. Did you let it sit and cook for the full two minutes? If Odin recognizes the phone your drivers are probably ok.
This is the place that I got my info when I flashed mine. http://forum.xda-developers.com/showthread.php?t=2324667
rfrenz said:
See if Odin 3.09 will do the trick for you. You can get it here along with other good info - http://forum.xda-developers.com/showthread.php?t=2189539 and here are instruction with a picture with download info. Make sure the mobile.bin file is in the CP (Phone) flashing area. Did you let it sit and cook for the full two minutes? If Odin recognizes the phone your drivers are probably ok.
This is the place that I got my info when I flashed mine. http://forum.xda-developers.com/showthread.php?t=2324667
Click to expand...
Click to collapse
I tried 3.09 earlier and it didn't work for me. But this time I downloaded the modem from the site you passed along and it worked perfectly.
Finally, odin worked and the file flashed. Thanks a lot for sticking around for the long haul and helping me fix this. I really appreciate it.
You're welcome
GuySmiles said:
I tried 3.09 earlier and it didn't work for me. But this time I downloaded the modem from the site you passed along and it worked perfectly.
Finally, odin worked and the file flashed. Thanks a lot for sticking around for the long haul and helping me fix this. I really appreciate it.
Click to expand...
Click to collapse
Glad I could help. I went through the same series of frustrations. There is enough info on this site to solve most any problem.
Got a i337m (Rogers), flashed this twice via ODIN but baseband version still stick with I337MVLUAMG1. Any clue?

please help before I brick it

good evening
I am in a bit of tight spot
and before a srew it up (more) I wonder if you could help
I have a SM-G900V which is rooted and I had TWRP working just fine
I tried to flash a rom (project infinity) with aroma which freezed on installing aroma
the developer replied to me that the problem was from TWRP which had a bus and that I should instal CWP
I tried to install CWP on top of TWRP through ODIN and got a failure message
as of now I have neither TWRP or CWP or any rom flashed in mydevice
once I go into recovery mode and try to flash the previous rom that I had through the sdcard it says "footer is wrong signature fail" an reboots and gets stuck with no rom
just tried to reinstall TWRP through ODIN and got the failure message again
with the folowing message:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth) <OSM> All threads completed. (succeed 0 / failed 1)
please help
Hey man,
Sounds like you're in a bit of a pickle. Not sure if this would be a bit extreme, but I'd download the stock firmware and flash it through Odin. After that, reflash recovery and retry your rom.
I kind of see flashing back to stock a 'fail safe' in most cases, so it's always handy to have the stock firmware stored somewhere anyway. ?
Sent from my SM-G900I
..
fffft said:
Don't flash anything until someone discerns what went wrong..
being impatient at this point will put you at high risk of bricking or worse.
The phone boots normally up until the footer error?
What is the exact error message that you see?
What version of TWRP did you have?
Any backups? If so, do they include your baseband, EFS & PIT?
16 GB ROM?
Did you have a Verizon ROM when this happened?
Rooted?
.
Click to expand...
Click to collapse
let me start by thank you for your time!
I am a bit new to all this, I have flashed some roms in the past so I am also familiar with some stuff...
The phone doesn't boot it gets stuck like the attached picture, the OS doesn't start.
I don't see any message as it is stuck like I mentioned before, I just saw a message of "FAIL!" in Odin when I tried to install CWM on top of TWRP
my version of TWRP was 2.7.1.0
I had a backup on TWRP but as I dont see TWRP working anymore I dont know if its still available
my phone is 16GB
my SM-G900V is rooted and at the moment I had working perfectly SpeedROM v1 Rev2
if you would like to contact me through chat let me know, and again thank you very much!!
Try this
..
fffft said:
Okay, on the positive side there isn't anything to suggest that your bootloader is corrupt which would make this a lot harder. Probably the failed aroma install just messed your kernel up. But I don't want to recommend messing around with shortcut solutions e.g. just flashing the kernel that may or may not work, but would put you at unnecessary further risk.
The earlier suggestion to flash a full stock image is generally sound advice, but it does not apply to all situations. My questions were basically aimed at getting a sense of whether you have corrupted the bootloader or partitioning which has a bearing on how to best recover your phone.
First, I am assuming that you do not have the Dev (unlocked bootloader) version S5. If you have the Dev edition with the unlocked bootloader, do not proceed with the rest of this post until we discuss that.
On the assumption that you have a regular 16 GB Verizon SM-G900V S5, then I would like to see you Odin flash a full stock S5 Verizon image that has been rooted. Unfortunately I couldn't find anyone who has made and posted a stock rooted Verizon S5 image like that. I don't mean a stock rooted (custom) ROM.. I mean the full stock firmware image, including the bootloader, but rooted.
That's fine. The rooted part would just be a little extra insurance put against theoretical possible snags i.e. Knox issues. So I will suggest that you use Odin to flash a full stock Verizon S5 image, with an explicit partition table. Normally we don't touch the partition information (PIT) in Odin, but in your case we need to.
Download the files below from this thread
Unless you already have the file on your PC
Verizon S5 Retail Tar 4.4.2 NCG baseband and Mar 31 kernel
MD5: 699a949b57c771b00db9f3ed675c7a5e
NCG Pit
MD5: 3dd82f91a02c82e60e0a1f9964fdb5c0
Odin 3.09
MD5: 810ad286967d0a33881fd8181d35959f
You should thank the OP in that thread for collating the files that you need in one place.
Particularly that all important PIT file.
Start Odin and check these three boxes only: Auto reboot, Re-Partition, F. Reset Time
Choose the PIT file in the PIT window. Note that the PIT file needs to be extracted. Do not leave it zipped.
Choose the stock firmware tar.md5 file in the PDA window. The tar.md5 file needs to remain tarred i.e. tar.md5 or .tar
Put your phone into download mode. Ensure that your phone is off, remove the battery for a few seconds if necessary, then press volume down + home + power until you see the android robot screen come up. If it doesn't go into download mode, repeat these steps. And in the very unlikely event that you can't get into the download mode at all, stop and post that information
Connect your phone to your PC, Odin should say that it has detected your phone
Press start and let Odin flash your phone
Basically we are replacing all of the system files and assuring that your partitioning has not been corrupted
When Odin finishes with a success message your phone should be back to normal. Do a normal reboot to confirm
If you did not backup your phone, your user files in the /data partition might still be accessible
Decide if you wish to back them up or not. Do so if you need them. Then do a factory reset from the Settings menu
You will need to re-root and reinstall your apps, etc
If you run into any difficulties:
If the Odin write fails, note the error message and double check that your Odin settings were correct
Do not close Odin. Pull the battery from your phone for ten seconds.
Then replace the battery and go into download mode again (vol down + home + power)
Note whether Odin detects the phone
Then try flashing with Odin again. Note that you are not closing the Odin program if the first flash attempt fails
Odin can be a bit picky and it is not unheard of to have to reset the phone like this and run the session a second time
Odin is also picky about USB cables. If you still continued trouble, try a different USB cable and USB port
Don't despair if anything goes astray. There is almost always an alternate way to go about something.
Let us know your results so that we can (hopefully) celebrate. Or at least regroup.
.
Click to expand...
Click to collapse
you senior member??? pppffffffff
you should OWN this forum!!! thanx a lot for your extended time in this explanation mate, I will proceed and let you know
Agreed. I use a Dell and sometimes I have problems with odin using the front usb. I have to use the read usb and then no problems.
Hi Guys!!
I am back, back with my phone completely restored
A special THANX to fffff for your help!!
..

Need Bootloader package for G900FDXUANG1

I have a Singapore variant of the 900F, which has the latest firmware package of G900FDXUANG1 (but modem is still XXUANE2). I'm hoping to use the mobile odin/everoot method of rooting this phone, but I realize that this will require separate modem and bootloader files, in addition to the actual firmware file.
Does anyone have the bootloader package for DXU1ANG1? Or can anyone help me with extracting it from the stock firmware file?
Thanks!
You didn't explain or elaborate about the method that you referred to.. so it isn't clear what you are trying to do.
Normally, a bootloader is only updated if it is part of a full firmware image. We don't often see separate bootloader files. If you really need that, you can try doing a comprehensive search. But more than likely you'd need to format the bootloader files yourself.
From memory, extract the following files from the full firmware image, then package them together in a .tar.md5 volume. These are the files that constitute the bootloader. You should do a forum search to confirm the file names since I am writing them out from memory.
aboot.mbn
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
You'd then flash the .tar.md5 with Odin, specifying the .tar.md5 file name on the BL Odin line. Realize that flashing the bootloader is hazardous and should anything go wrong, you will have a bricked device that won't be easy to recover.
.
fffft said:
You didn't explain or elaborate about the method that you referred to.. so it isn't clear what you are trying to do.
Normally, a bootloader is only updated if it is part of a full firmware image. We don't often see separate bootloader files. If you really need that, you can try doing a comprehensive search. But more than likely you'd need to format the bootloader files yourself.
From memory, extract the following files from the full firmware image, then package them together in a .tar.md5 volume. These are the files that constitute the bootloader. You should do a forum search to confirm the file names since I am writing them out from memory.
aboot.mbn
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
You'd then flash the .tar.md5 with Odin, specifying the .tar.md5 file name on the BL Odin line. Realize that flashing the bootloader is hazardous and should anything go wrong, you will have a bricked device that won't be easy to recover.
.
Click to expand...
Click to collapse
Hey, thanks for that. The 'method' I'm hoping to use is detailed in the thread here. It basically involves downgrading to a firmware that's rootable by towelroot, then upgrading using Mobile Odin and everoot. The bootloader files and modem files need to be flashed separately via Odin PC using this method, as the mobile version doesn't seem to do it. I have the modem file for my phone, but not the bootloader. Have dug through the forums, but have unfortunately not found anyone who's posted the bootloader for the DXU1ANG1 firmware yet.
If a pre June 3rd version of the full firmware is available for your phone.. and it most likely is.. then you should be able to revert by using the full firmware image. And thereafter should be amenable to the Towel root exploit.
Then if you still wish to upgrade to ANG1, use Mobile Odin Pro to do so.. and you should retain root.
The above seems a lot easier and more to the point, less risky than the approach that you seeking to do. But it's your phone.. so whichever you prefer.
.
fffft said:
If a pre June 3rd version of the full firmware is available for your phone.. and it most likely is.. then you should be able to revert by using the full firmware image. And thereafter should be amenable to the Towel root exploit.
Then if you still wish to upgrade to ANG1, use Mobile Odin Pro to do so.. and you should retain root.
The above seems a lot easier and more to the point, less risky than the approach that you seeking to do. But it's your phone.. so whichever you prefer.
.
Click to expand...
Click to collapse
Yup, that was my plan. however in the thread i mentioned, the OP who's actually tried it mentions that he needed to flash the bootloader and modem separately via pc.odin, as the mobile odin pro did not flash the bootloader or modem for.some reason. hence why i'm trying to get my hands on the bootloader for ANG1.

Help with Rooting Galaxy S4

Hello, everyone. I'm new to this site, and have come here because I've gotten a bit desperate. I have been trying to root my AT&T Galaxy S4 (Model number: Samsung-SGH-I337, Android version 4.4.4) for a long time and have been unable to. I have tried multiple programs, such as Kingo Root, Root Genius, and towelroot. Nothing worked until someone I know told me to go to TomsGuide (a website; I tried to post the link, but was unable to) and follow the steps. It seemed to work at first, because I now have SuperSu and Superuser in my apps.
However, when I open the Superuser app, a message pops up: "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices." There are two options: Cancel and Recovery Install. Nothing happens when I click Cancel; when I click Recovery Install, I receive this message: "There was an error installing Superuser. Please send a log of the error to the developer."
I have also gone into My Files on my phone and found the apk files (there was one on my SD card and one in the phone's memory). I installed both, but when I opened it, I either received the same message as above or this one "There is no SU binary installed and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device."
I am not sure what to do now and have been unable to find the answer to this problem yet. Any help would be appreciated. I am also new to this kind of stuff, so detailed explanations would be nice. Thank you in advance.
Kingroot DESKTOP will root a S4. Look for my post on the subject.
Unfortunately I haven't figured out how to include links in my posts from Tapatalk. Maybe someday.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
This thread should help you out: http://forum.xda-developers.com/gal...to-root-i337ucufnj4-4-4-4-11-13-2014-t2939553
Kingroot seems kind of shady; I don't want to use it. I'd prefer to fix the problem I'm having, not try another one-click solution that won't work.
I've also already tried towelroot. It didn't work. Thanks for trying to help, though.
phoenix_fire said:
Kingroot seems kind of shady; I don't want to use it. I'd prefer to fix the problem I'm having, not try another one-click solution that won't work.
Click to expand...
Click to collapse
Agreed.
I've also already tried towelroot. It didn't work. Thanks for trying to help, though.
Click to expand...
Click to collapse
Towelroot works only with the NC1 kernel. You must flash the nc1 kernel, root with towelroot, and flash back the kernel for your system, presumably NJ4 or NJ5. If you didn't do this, then of course towelroot will not work. And it probably depends on which version of towelroot you use as well. The link above provided by @merlise will give you the download link for the correct version of towelroot, and will work if you follow it.
creepyncrawly said:
Towelroot works only with the NC1 kernel. You must flash the nc1 kernel, root with towelroot, and flash back the kernel for your system, presumably NJ4 or NJ5. If you didn't do this, then of course towelroot will not work. And it probably depends on which version of towelroot you use as well. The link above provided by @merlise will give you the download link for the correct version of towelroot, and will work if you follow it.
Click to expand...
Click to collapse
You are correct; I believe I have the NJ5 kernel (found it under Baseband Version; is that right?). Can you walk me through how to flash the nc1 kernel? And then how to flash back the kernel for my system? I have no idea how to do that.
phoenix_fire said:
You are correct; I believe I have the NJ5 kernel (found it under Baseband Version; is that right?). Can you walk me through how to flash the nc1 kernel? And then how to flash back the kernel for my system? I have no idea how to do that.
Click to expand...
Click to collapse
Baseband is the modem. Usually when stock firmware is installed, kernel, system and baseband will all be the same, although the modem can be installed individually, but you would probably know about it since you would have had to do it yourself. So let's assume that you are on NJ5 system. When you look in about device, "Build Number" should tell you which system and kernel is installed.
Here is the link for the walk-through you need. (It's the same thread that was linked above by @merlise.
Skip step 1, of course since you are already on NJ5. After that, follow the steps in order, 2 through 6. The download links for everything you need are in-line with the relevant steps.
If you've never flashed firmware using Odin, it's not difficult. I can post a tutorial for using Odin if you need it, or you can find similar on the forum.
Edit: Since you are on NJ5 and not NJ4, go here to download the NJ5 stock kernel.
creepyncrawly said:
If you've never flashed firmware using Odin, it's not difficult. I can post a tutorial for using Odin if you need it, or you can find similar on the forum.
Click to expand...
Click to collapse
Wow! Thanks; I'll give this a shot. I'll look for a tutorial for using Odin, but I'd appreciate if you could post one for me as well.
creepyncrawly said:
Here is the link for the walk-through you need. (It's the same thread that was linked above by @merlise.
Skip step 1, of course since you are already on NJ5. After that, follow the steps in order, 2 through 6. The download links for everything you need are in-line with the relevant steps.
If you've never flashed firmware using Odin, it's not difficult. I can post a tutorial for using Odin if you need it, or you can find similar on the forum.
Edit: Since you are on NJ5 and not NJ4, go here to download the NJ5 stock kernel.
Click to expand...
Click to collapse
Okay, so I just tried to follow the instructions from the link that merlise had posted. I skipped step 1, did step 2, and ran into trouble on step 3. Both the nc1 Kernel and Odin downloaded to my computer just fine, but flashing it to my phone failed. It said there was no pit partrition. So I Googled that, found the pit partition for my phone, and tried to flash that. This is what Odin said:
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<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> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
So I am completely clueless what to do next. Can you help?
phoenix_fire said:
Okay, so I just tried to follow the instructions from the link that merlise had posted. I skipped step 1, did step 2, and ran into trouble on step 3. Both the nc1 Kernel and Odin downloaded to my computer just fine, but flashing it to my phone failed. It said there was no pit partrition. So I Googled that, found the pit partition for my phone, and tried to flash that. This is what Odin said:
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<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> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
So I am completely clueless what to do next. Can you help?
Click to expand...
Click to collapse
From what you say above, you tried to flash the pit file alone, without a firmware. From what I understand, it is usually flashed in conjunction with a full firmware. It may not work when flashed by itself.
I wish you had posted the results of your first attempt to flash the NC1 kernel. I would be very surprised if you actually have a problem with the partitioning of your memory. It is almost never required to flash a pit file. There is usually some other cause for issues.
When Odin flash fails, it is very often a problem with the connection between the computer and the phone, so it is always a good idea to make some changes and try flashing again. Use another cable, use another port on the computer, especially one that is connected directly to the motherboard on a desktop pc, or even use another computer. Also, you might try a different version of Odin. If you are using v3.09 or similar, you might try v1.85 which you can download from my Download Repository (see link in my signature.)
Try again to flash the NC1 kernel, as in step 3 of the guide.
How to use stand-alone Odin3 to flash firmware:
Follow and recheck each of the following steps. Do them in order listed, as some steps are dependent on previous steps. Instructions are for Odin3 v1.85. It should work with any version of Odin, but some details, like color of items, may be different. In Odin 3.09, the PDA slot is named AP.
1.) Open Odin on the Windows Desktop.
2.) Have the USB cable plugged into USB port on the computer and into the phone.
3.) Shut the phone off.
4.) Put the phone into download mode.
5.) In Odin, you should get the yellow box under where it says ID:COM with the text 0:[COMx], and in the Message area, <ID:0/00x> Added!! where x is some number, usually 1-8.
6.) In Odin, make sure Auto Reboot and F. Reset Time are checked and all other items are not checked.
7.) Click on the PDA button. Browse to the tar file you want to install and select it so its path appears in the text edit box next to the button.
8.) Make sure the check box next to the PDA button is checked.
9.) Click the Start button.
10.) You should see the green progress bar advancing.
11.) When complete, you will get a PASS (or FAIL if unsuccessful).
Let me know if it flashes successfully. Regardless if it works or not, before you close Odin, copy out the information in the Messages section and post it back here.
creepyncrawly said:
I wish you had posted the results of your first attempt to flash the NC1 kernel. I would be very surprised if you actually have a problem with the partitioning of your memory. It is almost never required to flash a pit file. There is usually some other cause for issues.
Click to expand...
Click to collapse
I wish I had thought of that, too.
creepyncrawly said:
Let me know if it flashes successfully. Regardless if it works or not, before you close Odin, copy out the information in the Messages section and post it back here.
Click to expand...
Click to collapse
I was just about to attempt flashing again, but now my computer is not recognizing my phone at all: "The last USB device you connected malfunctioned and Windows does not recognize it." I tried a few different cables and two different ports. I believe it's a driver error. Also, I noticed that I've lost the ability to connect to wifi.
phoenix_fire said:
I wish I had thought of that, too.
I was just about to attempt flashing again, but now my computer is not recognizing my phone at all: "The last USB device you connected malfunctioned and Windows does not recognize it." I tried a few different cables and two different ports. I believe it's a driver error. Also, I noticed that I've lost the ability to connect to wifi.
Click to expand...
Click to collapse
If the problem is in the phone, then I don't know the remedy. If you can boot into recovery, you might try performing a wipe data/factory reset.
You might try uninstalling and reinstalling the USB driver. See this thread for download. Or you might try a different PC.
creepyncrawly said:
If the problem is in the phone, then I don't know the remedy. If you can boot into recovery, you might try performing a wipe data/factory reset.
You might try uninstalling and reinstalling the USB driver. See this thread for download. Or you might try a different PC.
Click to expand...
Click to collapse
Hi. Sorry about the late response; I've put trying to root my phone on the back burner for now, since I am really busy at the moment and things aren't going to slow down for a while. I'm going to attempt to figure it once more around Christmas time, so you'll hear from me again around then! Also, I just wanted to thank you for your help thus far; I appreciate it!

[RECOVERY][STOCK S8+] G955USQS2BQL1 - Galaxy S8+ SM-G955U SPR Spint

In the S8 firmware Samsung are now providing 5 files.
Here is how to install an S8 firmware
Phone preparation:
1. Download and install Odin on your PC
2. Download firmware below
3. Download and unzip your firmware (do not use WinRAR as it can give errors)
4. From your download put these files into Odin:
BL
AP
CP
CSC (not HOME_CSC)
5. Now look at the Odin Settings (for this select Options)
F.reset time
Auto reboot
6. Installing another country CSC or a network CSC will need the system partition size changing.
For this select Options and add this setting
Re-partition
7 Put phone into Download Mode and connect to PC .
When the Odin ID:COM box changes color press START
Download link: https://drive.google.com/open?id=1-I2ZyNfyN4JCdcRO_ugkrxJ_sh-088z8
I download the official firmware from Samsung directly using this software (samfirm _v0.3.6) and use the most recent ODIN-v3.13.1, newest firmware for my Sprint S8 is G950USQS2BQL1 from January which my phone updated to G950USQS2BRB1 which must not be in a full firmware yet, just an OTA update it seems.
I got 6 files in this downloaded file(SM-G950U_1_20171206185327_w3c9ywqj6i_fac.zip.enc4) which are:
AP_G950USQS2BQL1
BL_G950USQS2BQL1
CP_G950USQS2BQL1
CSC_OYN_G950UOYN2BQL1
HOME_CSC_OYN_G950UOYN2BQL1
USERDATA_SPR_G950USQS2BQL1
What I learned is (HOME_CSC) does not wipe your data, but the (CSC) will just like a factory reset, so with this in mind
If your just upgrading your stock firmware and want to keep your Data,
then just flash these 4 files....
BL (bootloader)
AP (System)
CP (Radio)
HOME_CSC (Region)
To Wipe your phone and bring it back to Stock like brand new out of the box first time powering it up.
Flash all the above but replace (HomeCSC) with (CSC) and add in the (USERDATA_SPR) file too..
ALWAYS ALWAYS ALWAYS backup your stuff first.. I use Smart Switch to backup all my Samsung devices.
Does it lock my phone to sprint
MindTrix said:
I download the official firmware from Samsung directly using this software (samfirm _v0.3.6) and use the most recent ODIN-v3.13.1, newest firmware for my Sprint S8 is G950USQS2BQL1 from January which my phone updated to G950USQS2BRB1 which must not be in a full firmware yet, just an OTA update it seems.
I got 6 files in this downloaded file(SM-G950U_1_20171206185327_w3c9ywqj6i_fac.zip.enc4) which are:
AP_G950USQS2BQL1
BL_G950USQS2BQL1
CP_G950USQS2BQL1
CSC_OYN_G950UOYN2BQL1
HOME_CSC_OYN_G950UOYN2BQL1
USERDATA_SPR_G950USQS2BQL1
What I learned is (HOME_CSC) does not wipe your data, but the (CSC) will just like a factory reset, so with this in mind
If your just upgrading your stock firmware and want to keep your Data,
then just flash these 4 files....
BL (bootloader)
AP (System)
CP (Radio)
HOME_CSC (Region)
To Wipe your phone and bring it back to Stock like brand new out of the box first time powering it up.
Flash all the above but replace (HomeCSC) with (CSC) and add in the (USERDATA_SPR) file too..
ALWAYS ALWAYS ALWAYS backup your stuff first.. I use Smart Switch to backup all my Samsung devices.
Click to expand...
Click to collapse
If I FLASH with CSC USERDATA_SPR does it mean my phone will be locked to the sprint network? because it currently works with all networks. I'm just not clear
hello Guys, i got a G955U that camed with the firmware G955USQS3CRE2 from sprint, I flashed a Combination file (build number G955USQU4CRE1) via ODIN, phone boots well, no problem at this point, but when I try to return to Stock I place the original firmware (build Number G955USQS3CRE2) and all the files correspondig to its slot at ODIN, when I start te flashing proces I get normal message of intilializing, after a few secconds the program says Failed.
Ive tryed diferent firmwares but they dont work, phone remains with the Combination Firmware. Im stuck at combination Firmware.
Im using Odin3_v3.13.1 version. Here is teh Log
HTML:
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1301)..
<ID:0/008> File analysis..
<ID:0/008> skip file list for home binary
<ID:0/008> apdp.mbn
<ID:0/008> msadp.mbn
<ID:0/008> persist.img.ext4
<ID:0/008> userdata.img.ext4
<ID:0/008> Home Binary Download
<ID:0/008> Total Binary size: 4744 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> abl.elf
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any suggestion?
A will atatch a image of what is displaying the devices after it fails.
bullracing said:
hello Guys, i got a G955U that camed with the firmware G955USQS3CRE2 from sprint, I flashed a Combination file (build number G955USQU4CRE1) via ODIN, phone boots well, no problem at this point, but when I try to return to Stock I place the original firmware (build Number G955USQS3CRE2) and all the files correspondig to its slot at ODIN, when I start te flashing proces I get normal message of intilializing, after a few secconds the program freezes and the progress bar never camed up.
Ive tryed diferent firmwares but they dont work, Im stuck at combination Firmware.
Im using Odin3_v3.13.1 version. Here is teh Log
HTML:
Added!! Odin engine v(ID:3.1301).. File analysis.. skip file list for home binary apdp.mbn msadp.mbn persist.img.ext4 userdata.img.ext4 Home Binary Download Total Binary size: 4744 M SetupConnection.. Initialzation.. Get PIT for mapping.. Firmware update start.. NAND Write Start!! SingleDownload. abl.elf FAIL! (Auth) Complete(Write) operation failed. All threads completed. (succeed 0 / failed 1)
Any suggestion?
Click to expand...
Click to collapse
The 5th number from the end in firmware/combination files is the bootloader version aka BL, they must be equivalent and or higher than your current bootloader. So you cannot flash BL 3 firmware are you flashed BL4 combination file, you must resource BL4 firmware or above to and you will be good to go.
Sent from my SM-G955U using XDA-Developers Legacy app
Quickvic30 said:
5the number from the end is the bootloader version aka BL, they must be equivalent and or higher than your current bootloader. So you cannot flash BL 3 firmware are you flashed BL4 combination file, you must resource BL4 firmware or above to and you will be good to go.
Sent from my SM-G955U using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for your reply.
Sorry I dont get it at all, Im trying to understand. Let me see. The combination file I installed its BL4, so the stock firmware must be BL4 or above to allow the Firmware to be flashed on the device?
How can I know the BL#number# of the firmware?
---------- Post added at 10:14 PM ---------- Previous post was at 10:08 PM ----------
Quickvic30 said:
The 5th number from the end in firmware/combination files is the bootloader version aka BL, they must be equivalent and or higher than your current bootloader. So you cannot flash BL 3 firmware are you flashed BL4 combination file, you must resource BL4 firmware or above to and you will be good to go.
Sent from my SM-G955U using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ohh I got it "The 5th number from the end in firmware/combination files"
Thanks! So I will get the right firmware. :highfive:
Ive just downloaded the G955USQU4CRE9 firmware, I deploy it on ODIN to my device, but im getting the same error. I see that this firmwares that have de BLL4 are not from Sprint, there is a alternative to dowgrade my device BLL#number# to go back to Stock Sprint? like install from TWRP the firmware, that will be secure?
bullracing said:
Ive just downloaded the G955USQU4CRE9 firmware, I deploy it on ODIN to my device, but im getting the same error. I see that this firmwares that have de BLL4 are not from Sprint, there is a alternative to dowgrade my device BLL#number# to go back to Stock Sprint? like install from TWRP the firmware, that will be secure?
Click to expand...
Click to collapse
Sounds like the partitions are different with the file you flashed and the stock sprint firmware. I sometimes tell Odin to re-partition to get back to stock along with the nand erase option checked as well. Just a thought... its how I get a screwed up flash back to stock, but you need a stock sprint firmware not a combo file. if you have twrp then your not stock at all and flashing a stock firmware will replace it back to original.
MindTrix said:
Sounds like the partitions are different with the file you flashed and the stock sprint firmware. I sometimes tell Odin to re-partition to get back to stock along with the nand erase option checked as well. Just a thought... its how I get a screwed up flash back to stock, but you need a stock sprint firmware not a combo file. if you have twrp then your not stock at all and flashing a stock firmware will replace it back to original.
Click to expand...
Click to collapse
Thanks for the Reply.
I sove it with the G955USQS5CRF5 file from Verizon, seems that it its compatible with the Spint firmware. I flashed with Odin, and make a FactoryReset at Recovery menu. That fixed it!
Good evening,
None of this worked. I followed the steps to a T. Put all files in and received this error? What am I doing wrong? I tried rooting my Sprint G955U and that failed. Didn't trip knox, which says 0x0 currently, but disabled fingerprint id, face recognition, samsung pay - says device has been rooted. In about section, specifies "official". Also, a new update just came out a few days ago in August, 2018. I tried to update and that failed as well. I put all these files in odin and it failed pretty quickly. Please help me restore my phone. Please see attached photos. Currently, running Android Oreo.
Serious help!
Alright so bare with me guys I’ve been an android user for a very long time (don’t kill me) but i recently moved to iOS yes I know ? lol point is I bought my girl a s8+ (well she did with my money lol) and of course being a female she got played and bought a locked device meaning frp and since I haven’t been in the Android scene in a Lil I did some diggin but came up with nothing really the phone is on G955USQS5CRF5 but I can’t find a combination for it so is she/we screwed?
kiddPREMIERE said:
Alright so bare with me guys I’ve been an android user for a very long time (don’t kill me) but i recently moved to iOS yes I know ? lol point is I bought my girl a s8+ (well she did with my money lol) and of course being a female she got played and bought a locked device meaning frp and since I haven’t been in the Android scene in a Lil I did some diggin but came up with nothing really the phone is on G955USQS5CRF5 but I can’t find a combination for it so is she/we screwed?
Click to expand...
Click to collapse
You're gonna wanna check out jrkruses thread which as an frp remove flashable zip through safe strap
https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206
bullracing said:
Thanks for the Reply.
I sove it with the G955USQS5CRF5 file from Verizon, seems that it its compatible with the Spint firmware. I flashed with Odin, and make a FactoryReset at Recovery menu. That fixed it!
Click to expand...
Click to collapse
Do you have the Combination file for G955USQS5CRF5? Can you provide a link to it?
CLKeenan said:
Do you have the Combination file for G955USQS5CRF5? Can you provide a link to it?
Click to expand...
Click to collapse
Sorry I didnt saw your reply, do you still Need it? I erased it from my computer but I can get it for you if you need it
i have just installed rooted frimwire in my galaxy s8 plus g955u and trying to get back in fectory frimwire i have searched on google but nothing found but today i have seen this post for get back in recovery am downloding file thank you so much for the post have a nice day :laugh:
---------- Post added at 12:19 PM ---------- Previous post was at 12:14 PM ----------
Dear ' sir i have s8plus sm-g55u snapdragon with locked bootloader and i have installed a rooted frimwire in my phone pda is also G955USQS2BQL1 is that possible to use this file is done to get back in stock frimwire ?

Categories

Resources