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.
Related
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.
[ Read the How To at the second post ]
Heya guys,
I just got yesterday my new Galaxy S5. I'm actually someone who is switching from the iPhone world to Galaxy.
I had a Note 2 in the past for some time and I'm sys admin so I'm a bit familiar with flashing and technical stuff.
Phone Information:
Model: SM-G900FD (or SM-G900MD?) (DuoS)
Country of Origin: United Arab Emirates
The phone came with stock rom 4.4.2. On the About Phone screen it shown SM-G900FD as model, directly from unboxing.
But when entering the Odin Mode it shows as product name SM-G900MD (which would fit the origin of course).
The first I did was downloading G900FDXXU1BNL9 (Android 5.0 SER (Russia)) and flash it with Odin. It works like a charm.
Then I tried dozen of different rooting methods, and failed every time, I spent I believe 10 hours on it already and flashed the phone about 30 times.
When flashing the stock rom, either the new G900FDXXU1BNL9 (5.0) or old G900FDXXU1ANF6 (4.4.2) it works like a charm.
The phone comes to life, Android is working fine.
As soon as I try to flash *any* other image, CWM, CF-Auto-Root or anything, it starts with "NAND Write Start!" and then in some seconds stops with "Complete(Write) operation failed." and the system ends up in a soft brick (Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.). I tried from every piece of software I could find many different versions. Different Odin versions. I tried Heimdall (Mac) and fastboot (Windows & Mac) without success. These two don't work at all with the phone. Heimdall can't correctly connect to the phone and download the PIT, I was reading its a bug with the newest bootloader of Samsung. And fastboot/adb can't see the phone, at all. While heimdall or odin can see the phone, so its not a driver issue that the OS can't recognize the phone.
I tried also different versions of CWM, CF-Auto-Root, either for SM-G900FD or SM-G900MD. No luck.
What I tried then was using towelroot, but it doesn't work with the newest Android. So I found a thread that stated to flash a old Kernel, which will give errors during booting but you can then root the phone with towelroot, and then flash the newest kernel back to the phone. I tried that, taking out the boot.img files from old and new firmware out and use a script to package them into .tar.md5 files and try to flash them with Odin. Even there, Odin reports FAIL! With the boot.img files from the stock images, which work fine flashing if I flash the entire stock image.
I tried also installing a old stock rom and try rooting it there with CWM/CF-Auto-Root. Same stuff, FAIL! flashing.
I'm a bit out of ideas right now. Does anyone ever encountered this? Or does have a hint on what could cause this problems?
Some threads I was reading (its a way more, but the list would be too long, I just add the most recent ones) and following:
[How to] Root for 4.4.2 and Flash rooted Stock Android 5.0 with KNOX 0x0?
http://forum.xda-developers.com/showpost.php?p=54745709&postcount=13
Galaxy S5 G900FD
http://forum.xda-developers.com/showpost.php?p=55994495&postcount=102
[Script][Tool] how to create a tar.md5 file from img For Odin
http://forum.xda-developers.com/showthread.php?t=2446269
Click to expand...
Click to collapse
Thank you very much for any assistance. I hope there is a possibility to root this phone
Cheers,
Sven
PS: My KNOX Warranty Void is already increased, so the warranty is killed already.
[HowTo]
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
$ COPYFILE_DISABLE=1 gtar -H ustar -c NON-HLOS.bin aboot.mbn boot.img cache.img.ext4 hidden.img.ext4 modem.bin recovery.img rpm.mbn sbl1.mbn sdi.mbn system.img.ext4 tz.mbn > image.tar
$ gmd5sum -t image.tar >> image.tar
$ mv image.tar image.tar.md5
Click to expand...
Click to collapse
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven
Well done!!
af2k said:
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven
Click to expand...
Click to collapse
Well done !!
i was looking for this root for my phone M-G900FD
until i read your thread ,so please upload the ready made file to root my phone as i am not experienced in this matter
waiting for your feed back
thanks
I had the same problem. I couldn't flash any other image whatever I did. And what I did was disabling reactivation lock within the settings. Worked since then.
free007 said:
please upload the ready made file
Click to expand...
Click to collapse
I will look into this tomorrow and provide a ready image for this.
AlwaysAndroid said:
what I did was disabling reactivation lock within the settings. Worked since then.
Click to expand...
Click to collapse
It didn't work out of the box at me. I checked right now within the settings and the reactivation lock is disabled already.
So we seem to face different problems. I still don't understand why flashing anything but an entire firmware is failing.
Well done indeed, would love to get my hands on your modded ROM, as in Dubai with new Duos just purchased today.
Any problems with Wifi passwords not being stored on re-boot?
af2k said:
Heya everyone again,
I just wanted to say that the last hope I had to try did work finally.
As every flashing of single partitions (eg. recovery.img, cache.img.ext4 or boot.img) failed, I did the following:
1. Take the image you want to have, in my case it is Android 5.0 SER (G900FDXXU1BNL9) stock image, and unpack it
2. Take the CWM, I used philz_touch_6.26.2-klte.tar.md5, and unpack it
3. Move the recovery.img file from the CWM to the image you want to flash and replace the original recovery.img
4. Package all together into one image.tar.md5 file, in my case it would be the stock image with the replaced CWM recovery.img
5. Flash it with Odin, it worked at me!
6. Proceed with the default rooting procedure of CWM (copy SuperSU, boot recovery, install ZIP)
You are done!
Steps to package the image.tar.md5 file (I used Mac OS X Yosmite):
The OS X tools (tar and md5) are NOT suitable! You should use brew install coreutils and use the gnu tar and md5sum commands. The OS X tar will produce a unusable tar file and Odin will crash, the OS X md5 produces a different output than md5sum (even when using md5 -r) and the verification will fail. When using Linux/Windows tar/md5sum tools all should be fine. If odin crashes when trying to flash it doesn't like how tar packaged up your file. Try a different tar version (better: operating different system).
I hope this helps people that encountered the same issue as me and they can now enjoy Android 5.0 with root on their SM-G900FD.
Cheers,
Sven
Click to expand...
Click to collapse
Looks like gtar needs to be installed separately.
$ brew install gnu-tar
This is what I was looking for...
I am not on OSX. Is there a possibility to get access to the modified image?
Hello,
I am on Cyanogenmod 13. and I have outdated Modem and Bootloader. which effect my network signal
I have downloaded the latest stock firmware which is for my specific device .
from reading all over XDA this is what i understand is the procedure:
1. getting the right stock rom <- done
2. extracting the required files <- my main question
3. create 2 tar packages for Modem and for Bootloader
4. creating MD5 checksum of both file.
5. flashing using ODIN while placing modem file to CR slot and Bootloader to BL slot. (flashing it twice before boot as it might be reset)
now i know how to do all this steps but my problem is to understand which files are required to Modem tar and Bootloader tar.
the available flash-able files made by the community are not consistent. for example some of the modem tar file people made contain modem.bin and NON-HLOS.bin while others only modem.bin.
this are the files in the original stock rom:
aboot.mbn
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
NON-HLOS.bin
boot.img
recovery.img
system.img.ext4
modem.bin
cache.img.ext4
hidden.img.ext4
which of them i need to place in the Bootloader tar (BL) and which in the Modem tar (CP)?
I've also searched around hoping to find answer to this question. I've also compared a lot of bootloader & modem tarballs and each was different. If you found a solution please post it here. Otherwise the safest way is to flash stock firmware and then reflash it with desired custom one ...
allidea said:
I've also searched around hoping to find answer to this question
Click to expand...
Click to collapse
Which one? About Odin's slot? Use AP slot for everything.
bbsc said:
Which one? About Odin's slot? Use AP slot for everything.
Click to expand...
Click to collapse
I'd like to know which files to extract from stock FW. I don't want to end up in boot loop or something worse.
From what I've seen my stock ROM has following files as shown on 1st attachment and most custom modem + bootloader tarballs have files (below files are from PhoeniX ROM v13.6) as shown on 2nd attachment.
There is one particular file named sdi.mbn which can be found in custom modem+bootloader tarballs and which is not present in stock rom.
Ok, I don't know if it's correct or no, but I used for bootloader/modem/kernel update on SM-G900V such a file as shown on the picture.
The original (HOME) .tar.md5 was renamed to .tar.
The next files from it were deleted:
- cache.img.ext4;
- system.img.ext4.
Pit-file was added.
The resulting file was flashed via Odin's AP slot.
Result:
- bootloader, recovery, kernel and modem updated;
- Binary: Official; System: Official;
- all data on /data remain untouched.
allidea said:
I've also searched around hoping to find answer to this question. I've also compared a lot of bootloader & modem tarballs and each was different. If you found a solution please post it here. Otherwise the safest way is to flash stock firmware and then reflash it with desired custom one ...
Click to expand...
Click to collapse
All described here: https://jdrch.wordpress.com/2017/01...ions-without-breaking-custom-rom-or-recovery/
Thanks to both of you. @Hawaiihemd - As I already mentioned I am bothered by mysterious file named sdi.mbn which is not present in stock ROM (also mentioned by others who asked around about it too) but everyone mentioned it should be there ... funny ...
allidea said:
Thanks to both of you. @Hawaiihemd - As I already mentioned I am bothered by mysterious file named sdi.mbn which is not present in stock ROM (also mentioned by others who asked around about it too) but everyone mentioned it should be there ... funny ...
Click to expand...
Click to collapse
Are you still trying to figure this out??
bobbylo said:
Are you still trying to figure this out??
Click to expand...
Click to collapse
Nope. I don't know if I figured it out, but I've extracted all files from stock ROM as shown on second attachment in Post #4 above except sdi.mbn, created a .tar and flashed via ODIN ... Everything is working fine and new modem is displayed in device info.
allidea said:
Nope. I don't know if I figured it out, but I've extracted all files from stock ROM as shown on second attachment in Post #4 above except sdi.mbn, created a .tar and flashed via ODIN ... Everything is working fine and new modem is displayed in device info.
Click to expand...
Click to collapse
ok,so you created a .tar?Not a .tar.md5? why did'nt you need the sdi.mbn?
bobbylo said:
ok,so you created a .tar?Not a .tar.md5?
Click to expand...
Click to collapse
No just .tar as ODIN will accept it as well. I'm no expert but my guess .md5 is just a hash to verify .tar.
I used a tool named Odin Tar Converter v1.0 I think I found it on xda somewhere, but you can use any compression tool which is able to make .tar archives ie. 7-Zip.
Afterwards I just followed instructions for flashing bootloader and modem from PhoenixROM so I added .tar archive I've created to AP (newer ODIN) / PDA (older ODIN) and flashed it.
I've came across following instructions:
For the bootloader select BL and browse to your bootloader file.
For the modem select CP and browse to your modem file.
Click to expand...
Click to collapse
But since I created .tar regarding PhoenixROM bootloader and modem .tar structure it made more sense to follow PhoenixROM instructions.
why did'nt you need the sdi.mbn?
Click to expand...
Click to collapse
Maybe I needed it, but no matter how many stock ROMs I got my hands on none of them had this file. According to this article it seems sdi.mbn contains contains transmission band info although I don't think author himself was clear what it actually is used for. Anyway I decided to try and flash modem without it.
allidea said:
No just .tar as ODIN will accept it as well. I'm no expert but my guess .md5 is just a hash to verify .tar.
I used a tool named Odin Tar Converter v1.0 I think I found it on xda somewhere, but you can use any compression tool which is able to make .tar archives ie. 7-Zip.
Afterwards I just followed instructions for flashing bootloader and modem from PhoenixROM so I added .tar archive I've created to AP (newer ODIN) / PDA (older ODIN) and flashed it.
I've came across following instructions:
But since I created .tar regarding PhoenixROM bootloader and modem .tar structure it made more sense to follow PhoenixROM instructions.
Maybe I needed it, but no matter how many stock ROMs I got my hands on none of them had this file. According to this article it seems sdi.mbn contains contains transmission band info although I don't think author himself was clear what it actually is used for. Anyway I decided to try and flash modem without it.
Click to expand...
Click to collapse
Ok,was just wondering...I have an xda page where i created bootloaders and modems for the S5 G900T t-mobile.I use a program called cygwin64 to create the .tar.md5 files.It involves some command line input..Maybe yours is easier....Anyway,don't think i'll need to make any more,as i think there done with updates for the G900T,and maybe all the S5's
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.
Hello everyone I'm having a problem, I'm trying to put the stock firmware back on my Samsung but Odin keeps failing.
Saying '' Complete write failure'' What do I need to ?
Thanks for the help everyone!
I have the same problem. I've downloaded and tried many firmware, i even tried to use Heimdall to flash firmware, but aboot.mbn fails to flash. Please help what to do...
john.reyes.jmr said:
I have the same problem. I've downloaded and tried many firmware, i even tried to use Heimdall to flash firmware, but aboot.mbn fails to flash. Please help what to do...
Click to expand...
Click to collapse
extract the tar package and make another tar package with only system, boot and recovery related content from that original tar . It worked for me. I too was failing on aboot.mbn .IT will most likely work unless you are trying to upgrade/downgrade your phone. Downgrading is not going to work for sure. About upgrading I am not sure.
adarshadhungel1 said:
extract the tar package and make another tar package with only system, boot and recovery related content from that original tar . It worked for me. I too was failing on aboot.mbn .IT will most likely work unless you are trying to upgrade/downgrade your phone. Downgrading is not going to work for sure. About upgrading I am not sure.
Click to expand...
Click to collapse
Same problem occurs the system fails to download
don't know if you have already fixed the device or not but maybe flashing 4 files firmware can help you. I was able to flash all without any problem.
use samfirm with "binary nature" enabled.
adarshadhungel1 said:
don't know if you have already fixed the device or not but maybe flashing 4 files firmware can help you. I was able to flash all without any problem.
use samfirm with "binary nature" enabled.
Click to expand...
Click to collapse
I just tried this but still failed in aboot.mbn
john.reyes.jmr said:
I just tried this but still failed in aboot.mbn
Click to expand...
Click to collapse
Aboot.mbn is the bootloader. If Odin fails when flashing this file, you need to try a different USB cable, different USB port, the boot loader is not made for your phone, or you are trying to flash an older bootloader over a newer bootloader.