Attempting to downgrade my N910P due to recent update issues. I have an OF5 rom for the device that I'd like to load but ODIN is complaining about not wanting to back track/ Software Revision error. Is the solution here simple to flash the bootloader and modem for OF5? As I understand it, I have to tar up the .mbn files to assemble the 'bootloader tar' for odin, and have to tar up the modem.bin and NON-HLOS.bin for my 3g and LTE baseband flash, essentially loading both through Odin, flashing, then using Odin afterwards to flash the OF5 ROM (or can all 3 be done together?). Some basic questions: is this likely to trip my knox warranty flag/counter? Is there another way I should be seeking to downgrade my operating system on this phone? Is this even possible?
In terms of technical abilities I'm relatively new to this realm but I have flashed alternative bootloaders/roms onto devices before (thinking back to my HTC Incredible OG) and I'm a software engineer by day so I do have *some* understanding of what's going on here behind the scenes.
Any help would be greatly appreciated. Thank you for your time folks.
Related
Hello everybody im in a little bit of a crisis.
I tried to update my modem to MK2 and I used odin to do so. It turns out that it failed for some reason.
After that whenever I boot my phone it gives me a black screen and says Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again.
After that I followed this youtube video right here: https://www.youtube.com/watch?v=G1jyZ5QafAQ and downloaded this file to go back to stock: http://downloadandroidfiles.org/download-l720vpuamdc_l720sptamdc_spr-zip/
But yet it still gave me a Fail in odin. Any help would be appreciated as I am Freaking out right now
Here is the message log directly from odin when it starts
Firmware update starts
aboot.mbn
NAND write start
Complete(Write) Operation Failed
I switched USB ports now Odin is saying there is no PIT partition
88exp88 said:
Hello everybody im in a little bit of a crisis.
I tried to update my modem to MK2 and I used odin to do so. It turns out that it failed for some reason.
After that whenever I boot my phone it gives me a black screen and says Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again.
After that I followed this youtube video right here: https://www.youtube.com/watch?v=G1jyZ5QafAQ and downloaded this file to go back to stock: http://downloadandroidfiles.org/download-l720vpuamdc_l720sptamdc_spr-zip/
But yet it still gave me a Fail in odin. Any help would be appreciated as I am Freaking out right now
Click to expand...
Click to collapse
If your on MJA/MK2 firmware (bootloader) you cannot go back to MDC (the file you showed).
Also did you run PC Odin 'As Administrator'?
You can find the link to the MK2 here.
leaderbuilder said:
If your on MJA/MK2 firmware (bootloader) you cannot go back to MDC (the file you showed).
Also did you run PC Odin 'As Administrator'?
You can find the link to the MK2 here.
Click to expand...
Click to collapse
I am on MDC bootloader. What I did was download the tar file from stockroms.net for MDC. And I ran the 3.07 odin as adimistrator and it worked. Thank you cause I think that it was me not clicking run as administrator. Another question: Is it worth upgrading to MK2 if I wanna root again or should I just keep MK2. I have the geeksquad warrenty from bestbuy so it shouldn't matter if it trips the knox flag because I give them rooted phones all the time.
88exp88 said:
I am on MDC bootloader. What I did was download the tar file from stockroms.net for MDC. And I ran the 3.07 odin as adimistrator and it worked. Thank you cause I think that it was me not clicking run as administrator. Another question: Is it worth upgrading to MK2 if I wanna root again or should I just keep MK2. I have the geeksquad warrenty from bestbuy so it shouldn't matter if it trips the knox flag because I give them rooted phones all the time.
Click to expand...
Click to collapse
I wouldn't update to the knox bootloader (take the OTA or flash the full .tar) but that's me, for now.
Since you're on the earlier bootloader you can still update to any number of ROMs that have the knox bootloader removed.
Also I would definitely update the modem firmware - Unknownforce has a thread for that here.
Spend some time and read and you'll find loads of stuff you can do.
Good luck.
leaderbuilder said:
I wouldn't update to the knox bootloader (take the OTA or flash the full .tar) but that's me, for now.
Since you're on the earlier bootloader you can still update to any number of ROMs that have the knox bootloader removed.
Also I would definitely update the modem firmware - Unknownforce has a thread for that here.
Spend some time and read and you'll find loads of stuff you can do.
Good luck.
Click to expand...
Click to collapse
So I can use the files http://forum.xda-developers.com/showthread.php?t=2338919 in odin to update. Also since I am on mdc could I just use the latest in odin or do I have to go incrementaly.
Sent from my SPH-L720 using xda app-developers app
If you truly are on MDC and did not trip the knox bootloader you can Odin back to stock MDC. That will wipe the phone completely, giving you an all MDC phone - bootloader, recovery (stock), kernel, modem and ROM.
But I would just jump to MF9. It was the last official without the Knox bootloader. You can grab that here.
This is the FULL system tar. All stock, kernel, recovery, ROM Modem.
Extract the .tar.md5 and place that in the PDA slot and that's it. Make sure you don't check 'repartition'!.
Then use CF-Autoroot to root and again be careful NOT to check anything like repartition etc.
Once rooted you can then open up supersu, update the binaries. Go to playstore and download GooManager. User that to install custom recovery and then you can flash away.
I do suggest you spend some time here reading a whole bunch. You'll learn a lot about these methods and how and what you can do.
Good luck.
leaderbuilder said:
If you truly are on MDC and did not trip the knox bootloader you can Odin back to stock MDC. That will wipe the phone completely, giving you an all MDC phone - bootloader, recovery (stock), kernel, modem and ROM.
But I would just jump to MF9. It was the last official without the Knox bootloader. You can grab that here.
This is the FULL system tar. All stock, kernel, recovery, ROM Modem.
Extract the .tar.md5 and place that in the PDA slot and that's it. Make sure you don't check 'repartition'!.
Then use CF-Autoroot to root and again be careful NOT to check anything like repartition etc.
Once rooted you can then open up supersu, update the binaries. Go to playstore and download GooManager. User that to install custom recovery and then you can flash away.
I do suggest you spend some time here reading a whole bunch. You'll learn a lot about these methods and how and what you can do.
Good luck.
Click to expand...
Click to collapse
Hey man, just wanted to say thanks for continuing your tradition of quality posting. It is responses like this that made the E4GT forums such a great place to be.
leaderbuilder said:
If you truly are on MDC and did not trip the knox bootloader you can Odin back to stock MDC. That will wipe the phone completely, giving you an all MDC phone - bootloader, recovery (stock), kernel, modem and ROM.
But I would just jump to MF9. It was the last official without the Knox bootloader. You can grab that here.
This is the FULL system tar. All stock, kernel, recovery, ROM Modem.
Extract the .tar.md5 and place that in the PDA slot and that's it. Make sure you don't check 'repartition'!.
Then use CF-Autoroot to root and again be careful NOT to check anything like repartition etc.
Once rooted you can then open up supersu, update the binaries. Go to playstore and download GooManager. User that to install custom recovery and then you can flash away.
I do suggest you spend some time here reading a whole bunch. You'll learn a lot about these methods and how and what you can do.
Good luck.
Click to expand...
Click to collapse
Ok I have upgraded to MF9 now should I use Unkown Forces links: http://forum.xda-developers.com/showthread.php?t=2338919 to upgrade the firmware and modem?
And when I try to root with CF auto root on MF9 it fails on complete write operation failed.
Strike that its all good
If you're on MF9 full rooted you can update your firmware/modem following Unknownforce's instructions.
HOWEVER PLEASE take heed about the MJA(MK2 too) Notes: ...
some people report better success with turning Auto Reboot and F. Reset Time unchecked. Do the same flash, but when you see PASS on Odin, unplug the phone and Hold the Power key for 10 seconds to reboot.
Click to expand...
Click to collapse
And read through the whole post not just the OP. Some people had to flash it a few times to get it to show up (in system info) properly - mainly because they didn't follow directions precisely and skipped the note part on MJA/MK2.
Since you're now on MF9 fully rooted (stock) you can install yourself a custom recovery (Philz or TWRP - the latest Philz;philz_touch_6.08.9-jfltespr, seems to be the most reliable for now) and flash some ROMs. Virtually all of the 4.3/4.4 ROMs require the MK2 modem so know that too.
One thing I would highly recommend is to spend some time reading through the sections to get a clearer understanding of how this device behaves vs others (HTC, Moto etc.). Every device has it's peculiarities and caveats and not paying attention to them could ruin you day.
i have a different problem. i think my sprint sph-l720 bricked because my screen is stuck on kernel is not seandroid enforcing and it also says set warrant bit: kernel. need help as soon as possible
Tonymontana2421 said:
i have a different problem. i think my sprint sph-l720 bricked because my screen is stuck on kernel is not seandroid enforcing and it also says set warrant bit: kernel. need help as soon as possible
Click to expand...
Click to collapse
People need to know the difference between soft bricked and hard bricked. Most say bricked and they mean soft. Hard is nearly impossible to get the phone back up and running. I have that same problem when I try to install a kernel. You need to reflash a ROM.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
People need to know the difference between soft bricked and hard bricked. Most say bricked and they mean soft. Hard is nearly impossible to get the phone back up and running. I have that same problem when I try to install a kernel. You need to reflash a ROM.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
can you tell me which rom i need to flash because i cant figure out what rom i need to use in odin
Just rooted my Note 3 (MJE) and flashed CWM via Rom Manager and tried to boot into the recovery and get this message "System software not authorized by verizon has been found on your phone, please turn off your phone and go to the nearest store." Now the phone won't boot at all. Anyone know how to fix this without having to use Odin?
Slimfast35 said:
Just rooted my Note 3 (MJE) and flashed CWM via Rom Manager and tried to boot into the recovery and get this message "System software not authorized by verizon has been found on your phone, please turn off your phone and go to the nearest store." Now the phone won't boot at all. Anyone know how to fix this without having to use Odin?
Click to expand...
Click to collapse
The Verizon Note 3 uses secure (signed) blob verification at each step in it's boot sequence including boot images (normal OS kernel or recovery); if you attempt to flash anything which is not signed by Samsung, it results in exactly what you are experiencing. For now - no custom recoveries nor custom boot partitions.
If the phablet won't boot into *anything*, how exactly would you flash anything except by using Odin?
Disclaimer: I've never flashed used Odin. If the question you are asking is "can I put only the recovery back using Odin to avoid a full wipe?" then I suspect the answer is "possibly yes" - if you provide an Odin .tar file containing only the stuff you want to flash (e.g. the recovery image).
I note that the folks with developer versions of the VSGN3 use Odin files that do not include "aboot.mbn". That sort of suggests that Odin only wipes partitions that are slated to be flashed, not all of them. Were that not the case, you would have to always use a PIT file and always provide an image for every partition.
OTOH, Odin is a rather opaque tool, so you can't preclude it from having unexpected behaviors. Given that your device is brand-new, it would be a bummer to hard-brick it, so it might be better for you to just take your lumps and reflash the entire MJE Odin release ROM.
I *think* that folks here have said that attempting to roll back to prior full (factory) releases with Odin will result in a hard-brick. (Well, at least flashing down-rev low-level boot gearing such as aboot.mbn, sbl1.mbn, dbi, tz, etc). So if you flash anything, use MJE components (for now).
good luck. Please report your experiences, good or bad.
.
bftb0 said:
The Verizon Note 3 uses secure (signed) blob verification at each step in it's boot sequence including boot images (normal OS kernel or recovery); if you attempt to flash anything which is not signed by Samsung, it results in exactly what you are experiencing. For now - no custom recoveries nor custom boot partitions.
If the phablet won't boot into *anything*, how exactly would you flash anything except by using Odin?
Disclaimer: I've never flashed used Odin. If the question you are asking is "can I put only the recovery back using Odin to avoid a full wipe?" then I suspect the answer is "possibly yes" - if you provide an Odin .tar file containing only the stuff you want to flash (e.g. the recovery image).
I note that the folks with developer versions of the VSGN3 use Odin files that do not include "aboot.mbn". That sort of suggests that Odin only wipes partitions that are slated to be flashed, not all of them. Were that not the case, you would have to always use a PIT file and always provide an image for every partition.
OTOH, Odin is a rather opaque tool, so you can't preclude it from having unexpected behaviors. Given that your device is brand-new, it would be a bummer to hard-brick it, so it might be better for you to just take your lumps and reflash the entire MJE Odin release ROM.
I *think* that folks here have said that attempting to roll back to prior full (factory) releases with Odin will result in a hard-brick. (Well, at least flashing down-rev low-level boot gearing such as aboot.mbn, sbl1.mbn, dbi, tz, etc). So if you flash anything, use MJE components (for now).
good luck. Please report your experiences, good or bad.
.
Click to expand...
Click to collapse
I just flashed back to stock via odin. Worked fine.
Slimfast35 said:
I just flashed back to stock via odin. Worked fine.
Click to expand...
Click to collapse
Full MJE over the top of soft-bricked MJE?
bftb0 said:
Full MJE over the top of soft-bricked MJE?
Click to expand...
Click to collapse
Yeah.
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.
Hey there, I'm an idiot... I tripped KNOX and now phone is stuck on Tmobile boot screen. With so many different ways to do things and so many variants of this frickin phone and Android it seems the rules are every changing.
So my questions:
1.) How can I get this thing back to working? Can I flash a factory image with ODIN? If so which factory image do I use and what version of ODIN and what boxes need to be ticked in ODIN?
2.) Will #1 reset KNOX? Can KNOX be reset?
3.) Whats the best method to get the thing rooted so I can put a ROM on it. I hate TouchWiz. I tried using this method but it landed me here... http://www.androidrootz.com/2014/04/how-to-root-galaxy-s5-recovery-root.html
Thanks in advance....
Can I just flash the corresponding firmware with ODIN? Is it that simple? Does the firmware version displayed in factory recovery always correspond to the firmware to flash with ODIN? Any insights would help!!!! Thanks for your time!
sammobile dot com, grab a stock ROM for your model S5 (G900T), flash with ODIN
KNOX is permanently tripped now, no way to reset
your knox is permanently tripped, so might as well do what you want with the phone.
if you can get into download mode, you should be able to flash a recovery through ODIN, and then flash the rom of your choice. if that doesn't work, follow Detection's post above and flash a factory Tmobile rom through ODIN and start again.
That's all great thanks all, but does the firmware have to match the version that corresponds to the recovery that is currently on it? For instance, if I flashed 5.1.1 me thinks I wouldn't be able to root it or downgrade it thereafter, correct?
[bor]Its the loosey goosey instructions for multiple methods of doing the same thing for various android versions that make this sketchy. I found it easier to flash my HTC magic with jesus freak and a gold card than it is to flash this thing...or maybe my brain is decaying. Anyway, not what I expected for a common android phone. [/eor]
Hello all!
I've had a family member brick their Verizon S5 because they thought they were being smart and now I've been given the task of fixing it. The S5 was on the stock PF4 build previously (no root and no unlocked bootloader) and then had the stock OC4 tar from SamMobile flashed onto it via Odin which obviously bricked it. Furthermore they flashed the PD1 stock tar on top of that thinking that being on the same Android version would fix the problem so right now I have a phone with PD1 firmware but a PF4 bootloader. The phone currently will boot to the setup menu but has a continuous stream of error messages that makes the phone unusable (if I were able to get it into MTP transfer mode I could potentially have Kies 3 fix this).
Unfortunately, SamMobile doesn't have the PF4 tar file online yet and I don't have a spare Verizon S5 to exploit Kies with to get the tar file (I was able to get an encrypted version of the PF4 build using Kies 3's feature that pre-downloads the most recent firmware automatically but it lacks any file extensions and I've no clue how to make it usable).
I know that people have access to the stock components of PF4 like flashable tars for the modem and bootloader and even a flashable zip for custom recoveries of the entire stock PF4 build so I was wondering if anyone could help me out with getting a stock PF4 tar file (if not I will just have to wait till SamMobile puts up the file).
Any help would be greatly appreciated!
Edit: Found the firmware via Samsung-Updates and fixed the phone so help no longer needed
Closed at OP's request.