Phone: SM-N900T
Baseband: NB4
Build: OB6
Symptoms: Lagging/freezing video playback on certain videos. Video camera will freeze then force reboot in native apps and accessed from other apps when recording (IE Skype video message, or taking video with camera app), however Skype streaming works.
Research: Teh internets claimed that a mismatched build/baseband could cause funky issues.
Attempted remedies: Changed ROMs and had same problem. Then tried to upgrade baseband (both modem and non-hlos) via Odin, but no matter what file I download, how I rename it, what I extract it with, or which version of Odin I used...Odin will NOT see the files neither as .tar, .tar.md5, or even extracted out to the .bin.
Computer: Alienware 13 x64 W8.1 (yes I've rebooted it several times)
Odin's used: 3.7, 3.9, 3.12.3 (always ran as administrator)
Help? I've also tried downloading the files several times, and from different sources...clicking any of the buttons in Odin (in any version), with the files either located in a folder or on my desktop, Odin will NOT see .tar, .tar.md5, or .bin.
Update: It turns out that somehow, the file explorer in Odin is stuck in some view of the past...It contains a folder, that still shows up even when I've deleted it. It's like Odin is stuck in the past and doesn't see any new changes when accessing the file explorer to get its files. I can also add a new folder to a directory in Odin's file selection GUI that will only show up in Odin's file explorer, yet it won't show up in Windows file explorer. Thoughts?
Flash the latest stock rom from sammobile.com in Odin. This way, the phone will definitely have a matched bootloader and modem.
Related
I captured the following four tar.md5 archives downloaded by kies, during a recent restoral.
PHP:
T989UVKL1_ABOOT_SGH-T989user_CL799405_REV00.tar.md5
T989UVKL1_phone_secure_D_PROJECT_TMOBILE_REV_04_CL744338.tar.md5
T989UVKL1_PLATFORM_KERNEL_AMSS_SGH-T989user_CL799405_REV00.tar.md5
T989UVKL1_SGH-T989-CSC-TMBT989UVKL1_CL799405.tar.md5
Just thought I'd get this out there, as you probably won't find a cleaner base to build from. I've used 7zip to compress, and split an archive, to make it available via MediaFire. But the md5 archives within, are completely untouched. Have Fun.... =)
TMBT989UVKL1.7z.001 http://www.mediafire.com/?lrvxzmquubyfour
TMBT989UVKL1.7z.002 http://www.mediafire.com/?bt28h7b25c4pnwt
In my attempt to play around with the new JSS15J.I317UCUBMJ4 leak to get Wifi working on the I317M, I dont know which part corrupted my PIT so now I cannot access my internal media. I'm not sure if it is the bootloader, PIT or combination of the files I was using but I need a full I317M firmware to unbrick the device (preferably 4.1.2 / RWC).
This was my first time using Heimdall and despite reading through the ReadMe a few times, there were countless problems along the way including driver issues and file formats.
I hope to get a full firmware for the I317M as all the ones on Sammobile do not contain param, sboot, tz, and pit. The most important file for me at the moment is the pit file as I think that would restore access to the internal media, which would make flashing other things much easier for me. I havent tried sideload in TWRP yet but I doubt any solutions to my immediate problem could be solved in recovery.
Anyone who has a I317M, please download a copy of your pit file with the instructions as provided by Zen Arcade below:
Zen Arcade said:
1 - Install the USB drivers for the i317m (from samsung web site)
2 - Download the latest Heimdall package from here - http://www.glassechidna.com.au/products/heimdall/
3 - Extract Heimdall to a folder on your PC and open a command window there
4 - Connect the phone in download mode to your PC. From windows go to the drivers folder and run zadig. Consult the readme or search XDA on instructions on how to configure the heimdall driver. The device you are looking for might be shown as "Gadget Serial" for the i317.
5 - Now go back the the command window you opened and enter the following commands:
5a - heimdall detect [this will tell you whether the interface is working]
5b - heimdall download-pit --output i317m.pit --no-reboot
6 - check your heimdall folder, you should have a file called i317m.pit if everything worked
7 - If this allows you to successfully repartition your phone, upload the resulting pit here for others to use
Click to expand...
Click to collapse
hellocng said:
In my attempt to play around with the new JSS15J.I317UCUBMJ4 leak to get Wifi working on the I317M, I dont know which part corrupted my PIT so now I cannot access my internal media. I'm not sure if it is the bootloader, PIT or combination of the files I was using but I need a full I317M firmware to unbrick the device (preferably 4.1.2 / RWC).
This was my first time using Heimdall and despite reading through the ReadMe a few times, there were countless problems along the way including driver issues and file formats.
I hope to get a full firmware for the I317M as all the ones on Sammobile do not contain param, sboot, tz, and pit. The most important file for me at the moment is the pit file as I think that would restore access to the internal media, which would make flashing other things much easier for me. I havent tried sideload in TWRP yet but I doubt any solutions to my immediate problem could be solved in recovery.
Anyone who has a I317M, please download a copy of your pit file with the instructions as provided by Zen Arcade below:
Click to expand...
Click to collapse
Did you ever find a good download? I am trying to pull a pit file from a newly upgraded i317m Stock 4.3 but it is failing during the pit download... I have another i317m that is in the same boat as yours so any help/info you have would be helpful
Cheers
full flash?
Any progress in acquiring a full flash for this phone?
hellocng said:
In my attempt to play around with the new JSS15J.I317UCUBMJ4 leak to get Wifi working on the I317M, I dont know which part corrupted my PIT so now I cannot access my internal media. I'm not sure if it is the bootloader, PIT or combination of the files I was using but I need a full I317M firmware to unbrick the device (preferably 4.1.2 / RWC).
This was my first time using Heimdall and despite reading through the ReadMe a few times, there were countless problems along the way including driver issues and file formats.
I hope to get a full firmware for the I317M as all the ones on Sammobile do not contain param, sboot, tz, and pit. The most important file for me at the moment is the pit file as I think that would restore access to the internal media, which would make flashing other things much easier for me. I havent tried sideload in TWRP yet but I doubt any solutions to my immediate problem could be solved in recovery.
Anyone who has a I317M, please download a copy of your pit file with the instructions as provided by Zen Arcade below:
Click to expand...
Click to collapse
emutter said:
Any progress in acquiring a full flash for this phone?
Click to expand...
Click to collapse
The pit file is here - http://forum.xda-developers.com/showthread.php?t=2609871
The 4.1.2 and 4.3 stock firmwares are available from sammobile.com and do contain bootloader and tz (and most everything else except param and tombstones).
I've not seen a param file for the i317m... if someone wants to extract them from stock rooted 4.1.2 and 4.3 and share them I will resize and post them.
To do so run these commands from terminal emulator on phone:
Code:
su
dd if=/dev/block/mmcblk0p7 of=/sdcard/param.bin
PM me and let me know what firmware you were running and what specific phone - i.e. i317-rogers or bell or ...
Hello Community,
I tried to install custom recovery using this manual "wiki.cyanogenmod.org/w/Install_CM_for_serranoltexx" (<- cannot use the link function, because it's my first post). I followed every step. At point 9 I have to make commands using the cmd. Unfortunately the result is an Error:
Failed to access device. libusb error: -12
I had two insecurities while following the manual:
At point 4 I had to rename the recovery image but I'm not sure what the recovery image is. What I downloaded was a .tar.md5 file within a .zip. Do I have to rename the .zip or the .tar.md5? The renaming causes a change of the file type and I cannot really understand, why they didn't put the right file in that .zip at the beginnig...this step is a bit confusing
To point 5: I deinstalled Kies and the device driver in the Windows operating system. Since I've done this, there are appearing two devices in the zadig.exe when I connect my S4. I installed the zadig driver for both of them.
Im using Windows 7 x64
I hope someone can help me, for this moment I don't know what to do further...
greets
Dr. Bob! said:
At point 4 I had to rename the recovery image but I'm not sure what the recovery image is. What I downloaded was a .tar.md5 file within a .zip. Do I have to rename the .zip or the .tar.md5? The renaming causes a change of the file type and I cannot really understand, why they didn't put the right file in that .zip at the beginnig...this step is a bit confusing
Click to expand...
Click to collapse
I don't know about the libUSB error, and I haven't modded a Galaxy S4 mini, but I have installed CM on Galaxy Player. The tar.md5 has to be extracted from the zip; it is in fact a tar.gz file (tar archive compressed with gzip), but you don't have to rename it.
I flashed the Galaxy Player with Odin 3 v. 3.04, after having installed Kies to have the drivers installed. The Player showed in Odin with something like "ID:0 COM"; I then clicked on the "PDA" button, then pointed to the tar.md5, and clicked flashed, and it worked.
Here are my 2 cents :^)
Is your phone rooted? If rooted already it easy! For the most noob method, install ROM Manager from https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager and ROM manager will install the CWM for you. From there, its pretty simple.
If it not rooted, that the first thing you'll have to do.
fdelente said:
[...] The tar.md5 has to be extracted from the zip; it is in fact a tar.gz file (tar archive compressed with gzip), but you don't have to rename it.
Click to expand...
Click to collapse
I found out, the .tar.md5 is also a compressed file. If I extract it, I get a file called "recovery.img". At this point it's not very clear what to do. Because there is nothing to rename. And even if you are right, the tutorial would be also wrong.
TNCS said:
If it not rooted, that the first thing you'll have to do.
Click to expand...
Click to collapse
This is for installing the custom recovery, that's is the root, isn't it? I had the problem that Heimdall doesn't gets access to the device (lubusb error: -12). It's probably a driver problem.
However, I solved the problem by doing another method using odin. The root was succesfull. Afterwards I will flash the custom rom.
Dr. Bob! said:
I found out, the .tar.md5 is also a compressed file. If I extract it, I get a file called "recovery.img". At this point it's not very clear what to do. Because there is nothing to rename. And even if you are right, the tutorial would be also wrong.
This is for installing the custom recovery, that's is the root, isn't it? I had the problem that Heimdall doesn't gets access to the device (lubusb error: -12). It's probably a driver problem.
However, I solved the problem by doing another method using odin. The root was succesfull. Afterwards I will flash the custom rom.
Click to expand...
Click to collapse
No, custom recovery is not rooting. Not my favourite method but it easy enough, try this: http://www.kingoapp.com/
It a universal root for JB and it will prompt you to install CWM afterwards.
After installing the CWM I rooted the device. I succesfully installed Canogenmod 10.2.1. The Tutorial says explicit, that it only helps for 10.2.x but I want to install the Nightly version which is running at CM version 11. If I could, I would ask this questions in the threat but I'm not allowed yet to post in the developers section. "forum.xda-developers.com/showthread.php?t=2474054"
Can I use this tutorial for flashing CM version 11?
Hi all,
just having some problems flashing my tab 10.1 3 p5220.
Kies is refusing to do it as I suspect it is because the rom in it is
currently a german one.
Now, how do I intercept the rom file after kies has downloaded it but
before it attempts to install it and fails?
I seem to remember being able to do this on the htc and assume
we can do the same with the samsung. This way I hope I can I
reflash it via odin.
Many thanks in advance,
Andrew
Just download a firmware from sammobile and flash through odin
BennyCat said:
Now, how do I intercept the rom file after kies has downloaded it but
before it attempts to install it and fails?
Click to expand...
Click to collapse
Not sure if you've managed it now?
Anyway here is how you do it, also may be useful for others too, I've done this in the past, although I was doing an emergency recovery instead of an upgrade, this works either way.
I take absolutely no credit for this:
Here is a guide to save the firmware during your kies update,so u can save that firmware for future use .i just copy paste this from some where else
1. On your pc, windows explorer, check the option "Show hidden files, folders, and drivers".
2. Now connect your phone to pc via kies to begin the firmware upgrade.
3. Kies will begin to download the firmware files...
a. The files will be saved under a tmp file called "tmp****.tmp"
(NB: **** can be any letters or numbers, e.g. In my two times of upgrade via kies,
first timethe tmp files was "tmpA4CE.tmp", and on the second it was "tmpD900.tmp"
b. In Windows 7, this tmp file is located at, C:\Users\*\AppData\Local\Temp
(NB: * is the pc user session name, e.g. C:\Users\Spacks\AppData\Local\Temp)
4. When download is complete, kies decompresses this tmp file into a folder called
"tmp****.tmp.zipfolder" and begins the firmware upgrading process.
a. The folder has same name as the tmp file but now with an extention of .zipfolder.
(So scroll through the folders in the same directory to locate it).
b. When kies begins the upgrade process starting from 1% until it reaches 100%,
quickly copy the "tmp****.tmp.zipfolder" to your desktop.
You have about 2 to 3 minutes to do this. Kies will delete the folder once upgrade is 100% (completed).
5. The "tmp****.tmp.zipfolder" contains all the firmware files kies has used to upgrade your phone.
Now you have a backup of official firmware from kies. This is also useful in case kies fails to complete the upgrade process.
Click to expand...
Click to collapse
:good: Credit to & quoted guide by blackperl @ androidforums.com :good:
after rooting my samsung galaxy s 6 SM-G920P it does not recognize my 32 gigs internal memory and Google Play keeps shutting down what do I need to do to fix these problems?
First let me ask how you rooted your phone? I ask because I am pretty sure that I can show you a method that doesn't break anything.
While you are answering that, here is how to restore:
Download the latest version of Odin from here: http://www.samsungodindownload.com/ Extract that to your desktop.
Download this file to your computer: https://www.androidfilehost.com/?fid=24343351889231947 (It is the latest stock file zipped up for the 920P. If you have a different phone, don't use this.)
Extract the .md5 inside. Only the .md5, leave the stuff inside as it is.
Follow this video and you should be back to stock: https://www.youtube.com/watch?v=tv0BnfpNxEs