I bought my phone in the US, and unlocked it before coming to Europe.
I was able to root my phone and now I'm running Resurrection Remix (6.0.1) on it with almost no problems.
I'm trying to find out if my bootloader is locked since I would like to do some other things as well (the partition structure is terrible and I would like to change it, and also I would like to install jfltexx modem and bootloader).
I've tried to flash using ODIN but it fails, and Heimdall won't recognize the device (even after driver installation).
If the bootloader isn't locked can I simply dd files to mmcblk0p6 from adb or terminal emulator?
Thx in advance.
djuka007 said:
I bought my phone in the US, and unlocked it before coming to Europe.
I was able to root my phone and now I'm running Resurrection Remix (6.0.1) on it with almost no problems.
I'm trying to find out if my bootloader is locked since I would like to do some other things as well (the partition structure is terrible and I would like to change it, and also I would like to install jfltexx modem and bootloader).
I've tried to flash using ODIN but it fails, and Heimdall won't recognize the device (even after driver installation).
If the bootloader isn't locked can I simply dd files to mmcblk0p6 from adb or terminal emulator?
Thx in advance.
Click to expand...
Click to collapse
Bootloader is not locked, none of the Sprint firmware for this device contain a locked bootloader. Tried to flash what using Odin?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bilgerryan said:
Bootloader is not locked, none of the Sprint firmware for this device contain a locked bootloader. Tried to flash what using Odin?
Click to expand...
Click to collapse
Tried to flash both modem and bootloader for fltexx and failed both times. Reason - secure check fail: mdm and secure check fail: aboot. Write protecton enabled is shown in Download mode, maybe that has something to do with it?
djuka007 said:
Tried to flash both modem and bootloader for fltexx and failed both times. Reason - secure check fail: mdm and secure check fail: aboot. Write protecton enabled is shown in Download mode, maybe that has something to do with it?
Click to expand...
Click to collapse
You sure you don't have the L720T? It has a Write Protection setting in Settings/Security on the stock ROM that needs to be disabled before using Odin. Also if you flash another modem you will lose your carrier unlock.
bilgerryan said:
You sure you don't have the L720T? It has a Write Protection setting in Settings/Security on the stock ROM that needs to be disabled before using Odin.
Click to expand...
Click to collapse
Quite sure (you can also see by firmware version).
bilgerryan said:
Also if you flash another modem you will lose your carrier unlock.
Click to expand...
Click to collapse
Shouldn't the international modems be unlocked by default?
djuka007 said:
Quite sure (you can also see by firmware version).
Shouldn't the international modems be unlocked by default?
Click to expand...
Click to collapse
The international modems aren't for this device, hence your problem. Odin does a device check before flashing anything.
bilgerryan said:
The international modems aren't for this device, hence your problem. Odin does a device check before flashing anything.
Click to expand...
Click to collapse
OK, but does Odin do something special except copying the files? Popular recoveries that we use are cool but you can also do everything manually if you know a bit of Linux over ADB.
Is it the same here?
djuka007 said:
OK, but does Odin do something special except copying the files? Popular recoveries that we use are cool but you can also do everything manually if you know a bit of Linux over ADB.
Is it the same here?
Click to expand...
Click to collapse
It copies tar files. Such as modems, boot, and recovery. It's not like recovery such as TWRP.
bilgerryan said:
It copies tar files. Such as modems, boot, and recovery. It's not like recovery such as TWRP.
Click to expand...
Click to collapse
Right, but .tar are just archives and then you unpack it and copy the files to the right place. For example aboot.mbn to mmcblk0p6 (and other files accordingly as well)
Related
No WIFI turn on after flashing a rom?
That's because Sammy locked flashing radio+modem on our phones.
But there is where android command line comes in handy...
Put the two files from any downloaded stock rom you are currently running on your SDCARD:
NON-HLOS.bin
modem.bin
and execute the following in adb or in the emulator:
Code:
su
cd mnt/sdcard/
dd if=/dev/block/mmcblk0p1 of=backup-NON-HLOS.bin
dd if=/dev/block/mmcblk0p2 of=backup-modem.bin
Now, when the backup is done - just in case, let's flash:
Code:
dd if=NON-HLOS.bin of=/dev/block/mmcblk0p1
dd if=modem.bin of=/dev/block/mmcblk0p2
reboot
Done, your WIFI is restored!
__________________________
Original credits: http://www.alliance-rom.com
Hi,
I'm sorry but how can this issue happen ?
Flashing with ODIN ?
And, if it happen, where can I find
NON-HLOS.bin
modem.bin
files ?
I had this problem today but when I flashed faux kernel the problem was gone
sebarkh said:
Put the two files from the original rom on your SDCARD:
NON-HLOS.bin
modem.bin
and execute the following in adb or in the emulator:
Click to expand...
Click to collapse
Am I supposed to grab the files from the ROM that was on the device before the flash or the files from the ROM I just flashed? If I need to use the files from the old ROM then how can I ever upgrade the modem?
Thanks
ewok666 said:
Am I supposed to grab the files from the ROM that was on the device before the flash or the files from the ROM I just flashed?
Thanks
Click to expand...
Click to collapse
No, from the rom you are flashing, any stock Rom.
On your device you have mismatched files. That's the reason you have no WiFi.
sebarkh said:
No, from the rom you are flashing, any stock Rom.
On your device you have mismatched files. That's the reason you have no WiFi.
Click to expand...
Click to collapse
Thanks but it did not work for me using either the MEA or the ME2 files (my old version). It took a bit of effort but the dd commands completed. What did work in the end is flashing with Odin 3.07 (after two atempts with 3.04)....whatever that means.
ewok666 said:
Thanks but it did not work for me using either the MEA or the ME2 files (my old version). It took a bit of effort but the dd commands completed. What did work in the end is flashing with Odin 3.07 (after two atempts with 3.04)....whatever that means.
Click to expand...
Click to collapse
dd'ing shouldn't be a problem. it takes a few seconds.
this is the output:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You have to flash the same mdem and radio from a firmware you are running. Works perfect. If any assistance needed contact me via pm
uae_1990 said:
I had this problem today but when I flashed faux kernel the problem was gone
Click to expand...
Click to collapse
Thanks, this deffinetly fixed my problem. I would never belive there was a such easy solution. But you my dear friend, just made my day 15% better.
Is their any way i can apply the modem.bin and NON-HLOS.bin via updater script? so far I haven't been successful. S3 allows you to update firmware via flashable zip but it seems samsung blocks s4 from flashing NON-HLOS.bin and modem.bin.
asapmoola310 said:
Is their any way i can apply the modem.bin and NON-HLOS.bin via updater script? so far I haven't been successful. S3 allows you to update firmware via flashable zip but it seems samsung blocks s4 from flashing NON-HLOS.bin and modem.bin.
Click to expand...
Click to collapse
No, that's not possible anymore. You can only use Odin/Heimdall.
Why?
Lennyz1988 said:
No, that's not possible anymore. You can only use Odin/Heimdall.
Click to expand...
Click to collapse
@Lennyz1988 do you know why that is? Would Mobile ODIN work?
I got a used LG G2 in a box.
It was running Aeon AllianceRom v3. The keyboard went missing. It was impossible to use the rom because I couldn't type anything or even install another keyboard. So I flashed Aeon AllianceRom v3 over top again from TWRP in an to attempt to get a keyboard.
No dice. I did a factory reset that got me caught in a boot loop where TWRP was inaccessible.
I couldn't turn the phone off or take out the battery so I thought that it would be a good plan to flash a stock rom with FlashTool. Since I saw that the phone was a d800 when I was using Aeon AlllianceRom I assumed that it was an American Ebay special phone, common in Canada, and proceeded to flash the stock AT&T d800 rom. I did this from LGFlashTool. The rom barely runs. I checked the IMEI and model number on the box and this is for sure a d803. Yet LGFlashTool thinks otherwise.
With the d800 rom I can't enable USB debugging to re-root the phone because it is greyed out in settings. The phone reboots every minute or so and is unusable.
Firmware download mode says that I am rooted, and it is loaded with a stock Att d800 rom. Anyone know how I could go about flashing a plain rogers d803 rom onto it so that I can get the phone back in working order?
Thanks in advance.
Here are all the stock roms for the LG G2
http://storagecow.eu/index.php?dir=Xda/LG+G2/Stock/
here are some instructions if needed
http://forum.xda-developers.com/showthread.php?t=2432476
alex xander said:
Here are all the stock roms for the LG G2
http://storagecow.eu/index.php?dir=Xda/LG+G2/Stock/
here are some instructions if needed
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
This doesn't help. I following this guide only allows me to install the unusable d800 firmware on my d803.
I run into this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bad decisions all the way.
I would trust trust what the hw says not what a box says.
Anyway. Flash what you can to get twrp back. Then you can flash what you want.
Sent from my LG-D802 using Tapatalk
darkobas said:
Bad decisions all the way.
I would trust trust what the hw says not what a box says.
Anyway. Flash what you can to get twrp back. Then you can flash what you want.
Click to expand...
Click to collapse
Thanks, It is definitely a d803. The box, previous owner, and IMEI all say it is. What the hardware is saying is definitely wrong and the d800 firmware doesn't work.
Is there some way to change the device identified in a kdz file? Is there multi-model kdz files or a way to build them? Because currently i only can flash the AT&T stock kdz which is completely useless. Flashing something broken over something broken seems pointless.
Problem: At&t d800 rom installed on a Rogers d803.
There has been a long tedious process that has come from this. I'll let you know the basics of how I got back to a working system. Figuring out how to do it is up to you because I didn't keep a full list of everything I did. So this is a loose guide. (Thanks to autoprime for helping me out so much.)
The problem: lgflashtool can't help you because it has a crc check which stops you from flashing the correct kdz file. How you fix this is to use the moments that the device is turning on and off to enable USB debugging.
Manually root the LG G2; a .bat or .sh file won't work. You will need adb and fastboot which are available in most rooting bundles.
After the device is rooted, you will need to install the TWRP on it using adb.
Push the ROM for the correct model (d803) on the phone using ADB, and install it from TWRP.
The phone will only boot into fastboot after that. You will need to flash d803 images of aboot, boot, dbi, laf, modem, recovery (TWRP), rpm, sbl1 and tz onto their respective partitions.
Go into twrp and install a good ROM for your model.
Use LGFlashTool to install the correct kdz on the device.
Request for the D803R10c Rogers stock rom.
I have gotten my phone into a stable state but I am using the Bell stock ROM and need the rogers one in order to do a full kdz flash from LGFlashTool
If you have access to a copy of the rom I would be very grateful. :good:
**You can Odin back to NC2 at anytime after taking the NL1 update.**
1. Extract the N900A_NL1_Stock_Rooted_Backup folder from the .rar and place that folder into your Safestrap backups folder, i.e: ext-sdcard/TWRP/BACKUPS/xxxxxx (the name of your backups folder may vary. If a backups folder does not already exist you must first create a backup using Safestrap's "Backup" function before proceeding).
2. Use Safestrap's Backup Function to back-up User Data.
3. Perform an "Advanced Wipe" and wipe everything but your ext-sdcard.
4. From the main menu press "Restore" and restore the N900A_NL1_Stock_Rooted_Backup.
5. Once complete press the back button twice to access your backups again and restore User Data.
6. Last, from the main menu press "Reboot," reboot into "Download" mode and flash the N900A_NL1_Stock_Partitions using Odin's PDA slot(AP in Odin v3.09+).
Changelog: http://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB423151#fbid=2oEtZq05ft1
Notes:
1. The above process will not affect your User Data or Knox Warranty Flag.
2. This Restore process will update your Modem, Non-hlos, System, Kernel, Stock Recovery, and Bootloader to NL1.
3. Safestrap will not function after updating to NL1 4.4.4. See workaround here: http://forum.xda-developers.com/showthread.php?p=57141494
4. If you do not already have root access you must first flash back to factory stock NC2 using the N900AUCUCNC2_Full_Odin_Tar (flash in Odin's PDA slot(AP in Odin v3.09+)), root with Towelroot, install Safestrap, then proceed with the above process.
EXTRAS
N900A_NL1_Stock_Modem.tar.md5
N900A_NL1_Stock_Recovery.tar.md5
Would it be possible to install this update over NJ5 without having to downgrade to NC2? Because I'd hate to have to set up my phone AGAIN!
timark251 said:
Would it be possible to install this update over NJ5 without having to downgrade to NC2? Because I'd hate to have to set up my phone AGAIN!
Click to expand...
Click to collapse
It should be possible. You should be able to get to the safestrap recovery splash screen by flashing the NC2 kernel. See the safestrap workaround thread linked to in the OP.
Can confirm that it does work, successfully updated to NL1 while retaining root and my data.
@muniz_ri do you know what binary count on aboot is?
Walter.White said:
@muniz_ri do you know what binary count on aboot is?
Click to expand...
Click to collapse
3, same as NC2.
muniz_ri said:
3, same as NC2.
Click to expand...
Click to collapse
Perfect. Not sure why ATT isn't screwing with us but I'll take it.
Walter.White said:
@muniz_ri do you know what binary count on aboot is?
Click to expand...
Click to collapse
I see no change
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there a difference between NJ5 and NL1? Also, will this trip Knox counter?
Thanks in advance
coollkidd said:
Is there a difference between NJ5 and NL1? Also, will this trip Knox counter?
Thanks in advance
Click to expand...
Click to collapse
NL1 is a very minor update to resolve an issue caused by AT&T's bloatware. I don't remember the specifics but you can check AT&T's website for the changelog. And no, the warranty flag will not be affected.
Walter.White said:
Perfect. Not sure why ATT isn't screwing with us but I'll take it.
Click to expand...
Click to collapse
they added this to feature.xml
<CscFeature_Message_LinkDAUSA2>true</CscFeature_Message_LinkDAUSA2>
beyond compare is pdf
carl1961 said:
they added this to feature.xml
<CscFeature_Message_LinkDAUSA2>true</CscFeature_Message_LinkDAUSA2>
beyond compare is pdf
Click to expand...
Click to collapse
Do you have the adb sideload zip file for the baseband NL1 4.4.4, I'm still on the NJ5. I can't receive any updates via OTA because it always says, Software Update Interrupted
mozart1791able said:
Do you have the adb sideload zip file for the baseband NL1 4.4.4, I'm still on the NJ5. I can't receive any updates via OTA because it always says, Software Update Interrupted
Click to expand...
Click to collapse
@timark251 uploaded it here
http://forum.xda-developers.com/note-3-att/general/update-t2947366/page19
unzip and rename 2400258.cfg to update.zip
carl1961 said:
@timark251 uploaded it here
http://forum.xda-developers.com/note-3-att/general/update-t2947366/page19
unzip and rename 2400258.cfg to update.zip
Click to expand...
Click to collapse
Thanks, but I'm just wondering why my build number is different? My build number right now was KTU84P.N900AUCUDNL1
http://www.att.com/esupport/article...pObpQ-g7rVGcDvsbegWQ2c2zA2Bg#fbid=1gjGyucKyuU
mozart1791able said:
Thanks, but I'm just wondering why my build number is different? My build number right now was KTU84P.N900AUCUDNL1
http://www.att.com/esupport/article...pObpQ-g7rVGcDvsbegWQ2c2zA2Bg#fbid=1gjGyucKyuU
Click to expand...
Click to collapse
that is correct, this is update for NL1
New Software Specifications
Android version: 4.4.4
Baseband version: N900AUCUDNL1
Kernel version: 3.4.0-3032228
After flashing this rom
I keep get a message saying that Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes
What should I do?
I flashed kernel too
songssam said:
I keep get a message saying that Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes
What should I do?
I flashed kernel too
Click to expand...
Click to collapse
that is Knox security
do you have safe strap installed
run this in recovery to remove Knox related files
carl1961 said:
that is correct, this is update for NL1
New Software Specifications
Android version: 4.4.4
Baseband version: N900AUCUDNL1
Kernel version: 3.4.0-3032228
Click to expand...
Click to collapse
My build number is different from the original one? How is this possible? The original one is JSS15J.N900AUCUDNL1, I need your help here
mozart1791able said:
My build number is different from the original one? How is this possible? The original one is JSS15J.N900AUCUDNL1, I need your help here
Click to expand...
Click to collapse
so what is it now? I'm not clear at what you did.
Hi folks,
I am trying to flash this firmware onto my s6 edge+
G928FXXS5CRH1_G928FDBT4CRF1_DBT (newest samsung official binary)
but Odin will FAIL right after modem.bin (see screenshot)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know why this happens Please help to find out.
Before I tried to flash the firmware mentioned above, another samsung official was installed:
G928FXXU4CRF4_G928FOXA4CRE1_BTU
Now any attempt to flash former binary will also fail (because older bootloader??)
I'm stuck here Please help!
m0tt3 said:
Hi folks,
I am trying to flash this firmware onto my s6 edge+
G928FXXS5CRH1_G928FDBT4CRF1_DBT (newest samsung official binary)
but Odin will FAIL right after modem.bin (see screenshot)
I don't know why this happens Please help to find out.
Before I tried to flash the firmware mentioned above, another samsung official was installed:
G928FXXU4CRF4_G928FOXA4CRE1_BTU
Now any attempt to flash former binary will also fail (because older bootloader??)
I'm stuck here Please help!
Click to expand...
Click to collapse
I have the same problem with that file : THL-G928CXXS4CRF5-20180705114510.zip it worked before, but not anymore, my device is softbricked.
chongtak said:
I have the same problem with that file : THL-G928CXXS4CRF5-20180705114510.zip it worked before, but not anymore, my device is softbricked.
Click to expand...
Click to collapse
Which version is currently installed? (you can check it in recovery mode)
Most likely you are not able to install former version because it has an older bootloader.
In my case "S5" ist installed, so I am not able to downgrade to "U4", which was installed before
m0tt3 said:
Hi folks,
I am trying to flash this firmware onto my s6 edge+
G928FXXS5CRH1_G928FDBT4CRF1_DBT (newest samsung official binary)
but Odin will FAIL right after modem.bin (see screenshot)
I don't know why this happens Please help to find out.
Before I tried to flash the firmware mentioned above, another samsung official was installed:
G928FXXU4CRF4_G928FOXA4CRE1_BTU
Now any attempt to flash former binary will also fail (because older bootloader??)
I'm stuck here Please help!
Click to expand...
Click to collapse
Use samfirm for your newest firmware and use the region option for your current region. (it should work properly) if you get hidden.img failure, remove from package and repack .tar
Use updato.com to download latest firmware with full speed download.
I'm having the same issue. I wiped everything with TWRP and was going to reinstall the OS, but I'm getting the same fail as you do. I'm trying to flash the same version as I did before wiping everything.
Any ideas?
WVWVWVW said:
I'm having the same issue. I wiped everything with TWRP and was going to reinstall the OS, but I'm getting the same fail as you do. I'm trying to flash the same version as I did before wiping everything.
Any ideas?
Click to expand...
Click to collapse
Got this fixed by removing hidden.img from the file I was flashing
WVWVWVW said:
Got this fixed by removing hidden.img from the file I was flashing
Click to expand...
Click to collapse
You just saved me! Thanks a lot! I thought I was stuck on CM 14.1. Just removing hidden.img fixed my flashing issues.
same here always stuck or error on modem.img so after unclick hidden.img use z3x it worked mine is G928GUBS5CRH1
Or you can try with this. Fix the phone is bricked, black screen and more by flash a new ROM for Samsung Galaxy phone. Maybe not the newest firmware, but works perfectly.
https://www.youtube.com/watch?v=zXSHe3oorIM
I have better solution download this stock rom this is the latest and its binary 5 the latest one
Stock Rom:*SM-G928F_G928FXXU5CRI1_G928FDDX4CRF1_4Files_7.0.rar
Size: 2.0 GB
Security Patch Level: U5
Android:*7.0 Nougat
Model: SM-G928F
Model Name: Samsung Galaxy S6 EDGE+
Download this rom from site FirmwareX.net
Try will work for u
Purpp said:
Use samfirm for your newest firmware and use the region option for your current region. (it should work properly) if you get hidden.img failure, remove from package and repack .tar
Click to expand...
Click to collapse
hii i got same problem how to remove and repack wicht too did you used
Have an old SM -G935V that I'm trying to use on ting mobile. Can anyone recommend a Rom that will work? VZW says device is unlocked but still has VZW app on it saying "sim card is not Verizon." Any help is greatly appreciated!
kckish said:
Have an old SM -G935V that I'm trying to use on ting mobile. Can anyone recommend a Rom that will work? VZW says device is unlocked but still has VZW app on it saying "sim card is not Verizon." Any help is greatly appreciated!
Click to expand...
Click to collapse
download the U firmware or Tmobile firmware for it
Thanks @jrkruse I downloaded and read through your EASY_ROOT_ROM post. Would following your EASY_ROOT_ROM steps be better or does that include more steps than I really need?
For the U or T-mobile firmware download, do you recommend a link? I found one on updato... takes forever for the free version. Thank You!
kckish said:
Thanks @jrkruse I downloaded and read through your EASY_ROOT_ROM post. Would following your EASY_ROOT_ROM steps be better or does that include more steps than I really need?
For the U or T-mobile firmware download, do you recommend a link? I found one on updato... takes forever for the free version. Thank You!
Click to expand...
Click to collapse
what version firmware are you on the bootloader version
I'm sorry. Don't follow. Are you asking for the versions on the U firmware I'm trying to download? Or what is currently on the phone?
Downloaded version:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kckish said:
I'm sorry. Don't follow. Are you asking for the versions on the U firmware I'm trying to download? Or what is currently on the phone?
Downloaded version:
View attachment 5605133
Click to expand...
Click to collapse
thats what you need but you may have to extract the pit file located in the CSC_OYM_**** file and load it in the pit tab in odin and flash it with the above firmware
I asked what version you were on because if your on B/11 bootloader you cant use anything in my EASY_ROOT_ROM post
jrkruse said:
thats what you need but you may have to extract the pit file located in the CSC_OYM_**** file and load it in the pit tab in odin and flash it with the above firmware
I asked what version you were on because if your on B/11 bootloader you cant use anything in my EASY_ROOT_ROM post
Click to expand...
Click to collapse
Thanks for your help on this. Yes, the phone is currently on the B/11 bootloader.
I selected the appropriate BL, AP, CP, CSC (tried both HOME and not). Tried extracting the PIT file out and loading it separately like you suggested. Using PrinceCosmy ODIN v3.12. I only selected auto-reboot and F. Reset Time. Still fails. Should I try selecting any other on the ODIN options tab like BL update or Nand Erase All?
I tried an earlier G935U ROM w/out breaking out the PIT file and it failed too.
kckish said:
Thanks for your help on this. Yes, the phone is currently on the B/11 bootloader.
I selected the appropriate BL, AP, CP, CSC (tried both HOME and not). Tried extracting the PIT file out and loading it separately like you suggested. Using PrinceCosmy ODIN v3.12. I only selected auto-reboot and F. Reset Time. Still fails. Should I try selecting any other on the ODIN options tab like BL update or Nand Erase All?
View attachment 5605813
I tried an earlier G935U ROM w/out breaking out the PIT file and it failed too.
Click to expand...
Click to collapse
your not showing the flash error from odin so I really dont know
jrkruse said:
your not showing the flash error from odin so I really dont know
Click to expand...
Click to collapse
try using regular odin
Split out PIT from CSC which checks ‘re-partition’ option, loading BL, AP, CP, CSC:
Auto-reboot, F Reset Time and Phone bootloader update is also checked.
This is with regular odin. Not much on the error though.
At one point, I got an error on writing emmc_appsboot.mbn.lz4 from the BL. 'Write failed' was the error. Now the phone is stuck in a boot loop, unless in download mode.
kckish said:
Split out PIT from CSC which checks ‘re-partition’ option, loading BL, AP, CP, CSC:
Auto-reboot, F Reset Time and Phone bootloader update is also checked.
This is with regular odin. Not much on the error though.
View attachment 5606045
At one point, I got an error on writing emmc_appsboot.mbn.lz4 from the BL. 'Write failed' was the error. Now the phone is stuck in a boot loop, unless in download mode.
Click to expand...
Click to collapse
Use this odin and maybe try a different cable also make sure the files are on your computer and not a storage device
Thank you! Switching the cable worked! I got so far down the rabbit hole, I forgot to check something like that.