got everything else to work are on 6.0 but no modem.bin file that works
anybody out here that can help me..
Old thread, but I'm running into a closely related problem: the latest two firmware zips I've downloaded for this device do not contain a modem.bin binary. How can I flash the modem, then?
Someone out there?
Related
Hi,
I have a 16GB N8010 wifi-only note 10.1 which is superb.
Mostly I've flashed a few N8010 firmwares via odin, but a couple of times I've tried N8000 firmware and gone back again -- the only issue really being the "no signal" icon on the system tray. I've done this when the 8000 firmware has been substantially newer.
A couple of months ago I had the N8010 german CMD2 firmware installed, but then upgraded to the N8000 CMF1 firmware -- this was working great too
However I was unable to install either the N8010 CMH2 or CMG1 firmwares -- in both cases the odin flash aborted before completion. I tried both 3.04 and 3.07 on 2 different PCs
I was able though to happily reflash CMF1 without any problem which again is working fine.
Are there any gotchas with this switching? Anyone encountered a similar problem? Any tips to resolve? Or am I stuck now?
I can still use my device fine so it's not a huge issue, more annoying than anything else!
I tried the following firmware
KIES_HOME_N8010XXUCMH2_N8010OXACMH2_805288_REV00_user_low_ship.tar
- seemed to write cache.img, hidden.img, param.bin,recovery.img, sboot.bin - and at this point said FAIL !
N8010XXUCMG1_N8010OXXCMG1_HOME.tar
- seemed to fail immediately on tz.img
N8010XXBLK9_N8010OXXBLL1_HOME.tar
- system.img, boot.img, recovery.img, cache.img, hidden.img, -> completed just fine
At this point the tablet was running some elderly BTU firmware for the N8010 which was indeed how it shipped
Looks like it might be sboot.bin in that latest firmware that was causing an issue with odin. I no longer use mobile odin as I'm waiting for the skygo app (which won't work rooted)
In the end I tried the H2 firmware again, but repacked the tar file without param.bin, tz.img and sboot.bin - it flashed fine and the tablet is now back 8010 style and updated
No idea what this means in terms of how "complete" the update is, I believe those files relate to the bootloader & pit definitions which are unlikely to cause any real issues in not having been applied (I hope) . Not sure what tz.img is (timezone definitions?) so again I expect it will be fine
The device status does show as "custom" though. but that could be the flash counter.
planetf1 said:
I tried the following firmware
KIES_HOME_N8010XXUCMH2_N8010OXACMH2_805288_REV00_user_low_ship.tar
- seemed to write cache.img, hidden.img, param.bin,recovery.img, sboot.bin - and at this point said FAIL !
N8010XXUCMG1_N8010OXXCMG1_HOME.tar
- seemed to fail immediately on tz.img
N8010XXBLK9_N8010OXXBLL1_HOME.tar
- system.img, boot.img, recovery.img, cache.img, hidden.img, -> completed just fine
At this point the tablet was running some elderly BTU firmware for the N8010 which was indeed how it shipped
Looks like it might be sboot.bin in that latest firmware that was causing an issue with odin. I no longer use mobile odin as I'm waiting for the skygo app (which won't work rooted)
In the end I tried the H2 firmware again, but repacked the tar file without param.bin, tz.img and sboot.bin - it flashed fine and the tablet is now back 8010 style and updated
No idea what this means in terms of how "complete" the update is, I believe those files relate to the bootloader & pit definitions which are unlikely to cause any real issues in not having been applied (I hope) . Not sure what tz.img is (timezone definitions?) so again I expect it will be fine
The device status does show as "custom" though. but that could be the flash counter.
Click to expand...
Click to collapse
Hi, I have exactly the same issue. Where I can get the "N8010XXBLK9_N8010OXXBLL1_HOME.tar"?
THX
planetf1 said:
I tried the following firmware
KIES_HOME_N8010XXUCMH2_N8010OXACMH2_805288_REV00_user_low_ship.tar
- seemed to write cache.img, hidden.img, param.bin,recovery.img, sboot.bin - and at this point said FAIL !
N8010XXUCMG1_N8010OXXCMG1_HOME.tar
- seemed to fail immediately on tz.img
N8010XXBLK9_N8010OXXBLL1_HOME.tar
- system.img, boot.img, recovery.img, cache.img, hidden.img, -> completed just fine
At this point the tablet was running some elderly BTU firmware for the N8010 which was indeed how it shipped
Looks like it might be sboot.bin in that latest firmware that was causing an issue with odin. I no longer use mobile odin as I'm waiting for the skygo app (which won't work rooted)
In the end I tried the H2 firmware again, but repacked the tar file without param.bin, tz.img and sboot.bin - it flashed fine and the tablet is now back 8010 style and updated
No idea what this means in terms of how "complete" the update is, I believe those files relate to the bootloader & pit definitions which are unlikely to cause any real issues in not having been applied (I hope) . Not sure what tz.img is (timezone definitions?) so again I expect it will be fine
The device status does show as "custom" though. but that could be the flash counter.
Click to expand...
Click to collapse
Do you mind sharig the tar file you repacked with me? I am trying to revert to a true N8010 status re: bootloader or device id as it is now N8000.
Thanks.
planetf1 said:
I tried the following firmware
KIES_HOME_N8010XXUCMH2_N8010OXACMH2_805288_REV00_user_low_ship.tar
- seemed to write cache.img, hidden.img, param.bin,recovery.img, sboot.bin - and at this point said FAIL !
N8010XXUCMG1_N8010OXXCMG1_HOME.tar
- seemed to fail immediately on tz.img
N8010XXBLK9_N8010OXXBLL1_HOME.tar
- system.img, boot.img, recovery.img, cache.img, hidden.img, -> completed just fine
At this point the tablet was running some elderly BTU firmware for the N8010 which was indeed how it shipped
Looks like it might be sboot.bin in that latest firmware that was causing an issue with odin. I no longer use mobile odin as I'm waiting for the skygo app (which won't work rooted)
In the end I tried the H2 firmware again, but repacked the tar file without param.bin, tz.img and sboot.bin - it flashed fine and the tablet is now back 8010 style and updated
No idea what this means in terms of how "complete" the update is, I believe those files relate to the bootloader & pit definitions which are unlikely to cause any real issues in not having been applied (I hope) . Not sure what tz.img is (timezone definitions?) so again I expect it will be fine
The device status does show as "custom" though. but that could be the flash counter.
Click to expand...
Click to collapse
can you share with me too?
Hey guys.
I've seen some threads from people that had almost the same problem as me with the camera failing.
The thing is I'm completely stock on NE1, and the fix I saw was flashing a pit file and stock tar, but I'm not sure that's compatible with my Kitkat version.
Don't want to brick my device.
I odin flashed the stock NE1 tar, I already had that version, so I was bootloader locked from the beginning, and it didn't fix my camera.
I didn't see a PIT file here. http://forum.xda-developers.com/showthread.php?t=2791801
Please recommend what to do to fix the camera.
Thanks.
Hi i wanted to flash a custom marshmallow rom i was rooted and custom rom already but when i flashed the rom it didnt opened so i tried to flash a stock rom GR from sammyfirmware but it dosnt pass it fail in the start i read somewhere about a fix with the sammy roms that dont pass that you must rename the hidden.img to hidden.img.tar does anyone can help me or has anyone rom with seperate files of csc , modem and etc ...
manouvras said:
Hi i wanted to flash a custom marshmallow rom i was rooted and custom rom already but when i flashed the rom it didnt opened so i tried to flash a stock rom GR from sammyfirmware but it dosnt pass it fail in the start i read somewhere about a fix with the sammy roms that dont pass that you must rename the hidden.img to hidden.img.tar does anyone can help me or has anyone rom with seperate files of csc , modem and etc ...
Click to expand...
Click to collapse
Hi,
What is the exact error you get? Which firmware version you tried from sammobile?
manouvras said:
Hi i wanted to flash a custom marshmallow rom i was rooted and custom rom already but when i flashed the rom it didnt opened so i tried to flash a stock rom GR from sammyfirmware but it dosnt pass it fail in the start i read somewhere about a fix with the sammy roms that dont pass that you must rename the hidden.img to hidden.img.tar does anyone can help me or has anyone rom with seperate files of csc , modem and etc ...
Click to expand...
Click to collapse
ROM didn't opened because it might have got corrupted while downloading try redownloading it, By the way ROM isn't opened its flashed by any custom recovery.......
In case of stock ROM did you tried Odin and flashed the full zip (tar) file ?
Hi all,
I mistakenly put the wrong modem on my phone (Galaxy S5 SM-G900T). I was trying to do a USB-based sim unlock, after installing a new logic board, which had Android 5.0 installed. I had previously done the same steps on my old (broken) logic board, but at the time, that had Android 6.0 installed. The steps included updating the modem file on the phone using Odin, so that it could talk to the SIM-unlocking sofware. (The custom modem came packaged in a TAR file).
So now my Android 5.0 phone has a modem that was presumably for Android 6.0. It doesn't reliably connect to my computer using USB when not in download mode. I can put it into download mode, but I'm trying to figure out how to re-install the original stock Android 5.0 modem.
Here's what I've tried:
Downloaded a new stock Android 5.0 ROM for my phone. I searched SamMobile for my model number (SM-G900T). I got it from sammobile. Forums won't allow me to post the URL, but the full filename was G900TUVU1DOB1_G900TTMB1DOB1_G900TUVU1DOB1_HOME.tar.md5.
Extracted the rom on my computer using tar.
Found the modem.bin file that was extracted.
Used tar to wrap modem.bin in a new file called G900T50Original.tar
Used Odin to put the G900T50Original.tar onto my phone (by selecting it in the CP section).
I tried these steps, but it just timed-out, and I had to unplug and restart my phone.
Did I miss a step here? Is there a specific way that the TAR has to be packaged for it to work?
Thanks in advance,
Antun
karlovac said:
Hi all,
I mistakenly put the wrong modem on my phone (Galaxy S5 SM-G900T). I was trying to do a USB-based sim unlock, after installing a new logic board, which had Android 5.0 installed. I had previously done the same steps on my old (broken) logic board, but at the time, that had Android 6.0 installed. The steps included updating the modem file on the phone using Odin, so that it could talk to the SIM-unlocking sofware. (The custom modem came packaged in a TAR file).
So now my Android 5.0 phone has a modem that was presumably for Android 6.0. It doesn't reliably connect to my computer using USB when not in download mode. I can put it into download mode, but I'm trying to figure out how to re-install the original stock Android 5.0 modem.
Here's what I've tried:
Downloaded a new stock Android 5.0 ROM for my phone. I searched SamMobile for my model number (SM-G900T). I got it from sammobile. Forums won't allow me to post the URL, but the full filename was G900TUVU1DOB1_G900TTMB1DOB1_G900TUVU1DOB1_HOME.tar.md5.
Extracted the rom on my computer using tar.
Found the modem.bin file that was extracted.
Used tar to wrap modem.bin in a new file called G900T50Original.tar
Used Odin to put the G900T50Original.tar onto my phone (by selecting it in the CP section).
I tried these steps, but it just timed-out, and I had to unplug and restart my phone.
Did I miss a step here? Is there a specific way that the TAR has to be packaged for it to work?
Thanks in advance,
Antun
Click to expand...
Click to collapse
This should help you figure it out.
http://www.rwilco12.com/forum/showthread.php?tid=92
Thanks. Actually, after writing my post, I decided to try uploading just the raw modem.bin file via Odin, and it worked. (i.e. without tarballing it up). My baseband now shows the stock Android 5.0 one (
I'm not sure what I was doing differently than the instructions you posted. I didn't specify the ustar format, so maybe that was it. (I just did tar -cvf modem.bin > myfile.tar).
Droidriven said:
This should help you figure it out.
Click to expand...
Click to collapse
Before I get to my question, a quick background, which might help with explaining my question. So recently I switched to another cellular carrier on my unlocked S6 Edge (G925F) and now I would like to flash the baseband from the firmware corresponding to my new carrier in order to get better/proper connectivity. I downloaded and flashed the new carrier's firmware .tar.md5 using Odin, however, in the process of flashing, Odin threw a FAIL message when flashing the hidden.img file. So I had to manually extract and flash that file again, and it worked.
Anyway, it seems like, because of the aforementioned Odin FAIL message, the flashing process did not include the new modem.img file. So now I would like to manually flash that in order to get better service on my new carrier. So how do I do that? I tried flashing just the modem.img file with Odin by selecting it in the "CP" field, however, the flashing process gets stuck on "File analysis..." and nothing gets flashed. Am I doing something wrong? Can I flash that baseband some other way?
UPDATE, SOLVED:
I figured out the solution. I had to manually create a new .tar archive (with 7zip) containing just the modem.bin file. When I tried to flash that with Odin (by adding it under the "CP" field), it successfully went through.
tahaa7 said:
Before I get to my question, a quick background, which might help with explaining my question. So recently I switched to another cellular carrier on my unlocked S6 Edge (G925F) and now I would like to flash the baseband from the firmware corresponding to my new carrier in order to get better/proper connectivity. I downloaded and flashed the new carrier's firmware .tar.md5 using Odin, however, in the process of flashing, Odin threw a FAIL message when flashing the hidden.img file. So I had to manually extract and flash that file again, and it worked.
Anyway, it seems like, because of the aforementioned Odin FAIL message, the flashing process did not include the new modem.img file. So now I would like to manually flash that in order to get better service on my new carrier. So how do I do that? I tried flashing just the modem.img file with Odin by selecting it in the "CP" field, however, the flashing process gets stuck on "File analysis..." and nothing gets flashed. Am I doing something wrong? Can I flash that baseband some other way?
UPDATE, SOLVED:
I figured out the solution. I had to manually create a new .tar archive (with 7zip) containing just the modem.bin file. When I tried to flash that with Odin (by adding it under the "CP" field), it successfully went through.
Click to expand...
Click to collapse
May I please ask you, how did you get a firmware with a modem binary inside it? So far I've downloaded two different firmwares for this device, latest baseband versions, and none of them ships a modem.bin or anything similar. I'm totally puzzled.
zogoibi said:
May I please ask you, how did you get a firmware with a modem binary inside it? So far I've downloaded two different firmwares for this device, latest baseband versions, and none of them ships a modem.bin or anything similar. I'm totally puzzled.
Click to expand...
Click to collapse
So were you able to get the latest baseband /modem?? And how??