Thread from Chainfire for Galaxy Tab:
http://forum.xda-developers.com/showthread.php?t=888071
Just to be sure, we should check all new inofficial Firmwares from Samsung before posting it here to avoid problems. Maybe they'll do the same for SGS.
Thanks for the info mate! I'll be sure to spread this around but may I ask how do we make sure a ROM includes these new "checksum" bootloaders ?
Extract and look for "boot.bin" or "sbl.bin".
If these files are included, delete them before flashing. ;-)
codeworkx said:
Extract and look for "boot.bin" or "sbl.bin".
If these files are included, delete them before flashing. ;-)
Click to expand...
Click to collapse
Okay thanks again. This should be STICKIED!
I think almosr every new has them, i'm sure that XXJPY also has them too, but since my PC isn't near I can't say for sure. If it has I th en it isn't problem since have reveryed few timrs on older fitmeare without any problem.
00.ante said:
I think almosr every new has them, i'm sure that XXJPY also has them too, but since my PC isn't near I can't say for sure. If it has I th en it isn't problem since have reveryed few timrs on older fitmeare without any problem.
Click to expand...
Click to collapse
jpu only got it, has a low level package
00.ante said:
I think almosr every new has them, i'm sure that XXJPY also has them too, but since my PC isn't near I can't say for sure. If it has I th en it isn't problem since have reveryed few timrs on older fitmeare without any problem.
Click to expand...
Click to collapse
No XXJPY dont have it... I updated the bootloader and switch between roms like allways..
I would also advise not to use KIES anymore..
JPY has no boot.bin and sbl.bin
Time to wait a little more before flashing a future ROM via Kies Hack now and / or switch to a "Odin-only" with middle package ROM method.
Thanks for the Warning !
The latest bootloaders from Samsung are those in the JPU release and are 110% SAFE to be flashed.
We are using them to fix the 3-button combo issue.
After that, be sure NOT to update the bootloaders anymore
RazvanG
thanks for the heads-up codeworkx !
@mods:
*sticky please*
So to sum it up, there is currently no firmware package which includes a checksum check, right? JPU has boot.bin and Sbl.bin but the zImage is only 4.6 MB, so I assume it doesn't suffer from this issue.
Just have to be more careful while flashing any FUTURE firmwares, right?
Yes, these troubles can occur in a future firmware..
Thanks, codeworkx. Just in case, I do have the dxjp1 bootloaders too, if anyone is interested, I can upload those.
Sent from my GT-I9000 using XDA App
push
sticky plx
yeah, thanks for bringing it up. And a sticky would be nice too =)
On a side note, there is no stopping Samsung from implementing the checksum via official Kies update... I'll think twice before using the Kies patcher from now onwards.
Sent from my GT-I9000 using XDA App
Has anyone looked at il2 firmware for the I 9000m. People are reporting that once that flash this firmware flashing anything else will not boot, but they can flash back to il2 fine. Sounds like the first occurance of a locked bootloader on a galaxy s to me?
Sent from my GT-I9000 using Tapatalk
couldnt you reflash the boot/spl using the 3-button combo fix for any firmware version through odin if it ever gets updated.
a program with root can do a check if your boot/spl ever does change after a firmware flash. if it does just adb download, odin and flash the combo fix and you are in the clear to muck around with kernels/roms.
edit: my bad a new firmware will most likely have 3e recovery and no easy root without a kernel flash. can you do a dd dump without root using adb? if you can manually dd dump the boot and spl using adb and hash check with a save that will be able to tell if your boot/spl has been changed.
Hi all
The I9000XWJM5 firmware is known to include the boot.bin and Sbl.bin which erase the 3BR fix.
Could it be usefull in this case ?
Related
http://hotfile.com/dl/104757943/6d6d23b/I9000_XEN_I9000XWJS5.rar.html
SamFirmware : I9000XWJS5 FULL
3 files , flash with 803 pit
http://www.multiupload.com/6JX2LEUCTY / Pit FIle
arch pass : samfirmware.com
some guy below said there is risk so pleas noob pleas stay away from this rom it can kill your phone
Another new firmware!
I have a flashed JPY (Odin) firmware. Can I just flash this new firmware or do I have to flash back or anything...sorry I'm new to this.
Sent from my GT-I9000 using XDA App
same topic like here!
I don't think that it's good to provide this firmware, this firmware does include a boot.bin and an Sbl.bin, if by any chance a user flashes the firmware and Odin hangs during flashing these files then the mobile phone is totally unusable(brick).
We all have seen this firmware since the morning and non have posted it because of what I mentioned above.
I can confirm that the boot.bin and Sbl.bin in this firmware do not disable download mode, but still, if anything goes wrong as bad USB connection or bad drivers then the phone is dead.
[Ramad] said:
I don't think that it's good to provide this firmware, this firmware does include a boot.bin and an Sbl.bin, if by any chance a user flashes the firmware and Odin hangs during flashing these files then the mobile phone is totally unusable(brick).
We all have seen this firmware since the morning and non have posted it because of what I mentioned above.
I can confirm that the boot.bin and Sbl.bin in this firmware do not disable download mode, but still, if anything goes wrong as bad USB connection or bad drivers then the phone is dead.
Click to expand...
Click to collapse
+1 on this. I already posted the same warning on BogdanSNB's thread about this ROM. I think it would be of great benefit to the XDA community if people who start threads about new Samfirmware ROMs did some basic investigation before posting and posted some useful technical specs along with appropriate warnings about the possible dangers of flashing the ROM in question before encouraging others to flash / kill their phones. Helping people to make informed decisions about upgrades should be a priority, not an after thought.! (I'll get off my soap box and put on my fire proof suit now...)
802.pit? Never knew such existed, anyone know how it differs from 512/803 (ie data larger, system smaller)?
Sent from my GT-I9000 using XDA App
Mothatt said:
802.pit? Never knew such existed, anyone know how it differs from 512/803 (ie data larger, system smaller)?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
i have the same question..
ermy sti said:
i have the same question..
Click to expand...
Click to collapse
Must of been a typo, I just checked samfirmware and it says 803
Mothatt said:
Must of been a typo, I just checked samfirmware and it says 803
Click to expand...
Click to collapse
yes but my question is: what is the difference between the pit's? (in this case 803 vs 512)
TNX
ermy sti said:
yes but my question is: what is the difference between the pit's? (in this case 803 vs 512)
TNX
Click to expand...
Click to collapse
Information in the pit files are used by Odin for configuring partition sizes on the internal disks in Samsung Android phones. Different ROMs need different partition sizes depending on the amount of data needing to be written to each partition. Some XDA members tried looking into how pit files work a while ago but AFAIK weren't able to find out much because the Odin code is closed source so they couldnt work out what Odin does with regards to repartitioning (anyone got an update on this??). I've found that you can often flash ROMs that Samfirmware say should be 803 pit on a 512 pit phone with no problem. I'm running JS5 on my phone, having come from JS3 and JS2 but my last repartition was with the 512 .pit file when I flashed JPU.
I've searched but can't find an UVUAMDL baseband file to flash anywhere, any idea why that is ?
I'm on rooted UVUAMDL stock rom but still on UVUAMDB baseband and I've been losing network connection 3 times today in areas where my gf's S4 on stock UVUAMDL has been rock solid, so I think having the modem mismatch the rom is probably the issue...
Sent from my SGH-M919 using Tapatalk 2
Another thread actually has info that this is an issue with the phone. I'm sorry, but I'm unable to locate the thread again.
I dont think its a issue....been flashable modems on every galaxy phone including both international s4 so irs just a matter of someone who knowshow to make it
Can someone with the know how make one?....thanks in advance
+1 for UVUAMDL baseband for some reason my device is still on UVUAMDB after updating
lazaro17 said:
+1 for UVUAMDL baseband for some reason my device is still on UVUAMDB after updating
Click to expand...
Click to collapse
I'm using the Wicked v2 ROM that is using MDB as the baseband and the only network issue I'm having is connecting to the LTE network. Phone connection is fine, 4G connection works great, but whenever I'm in an area that has the new T-mobile LTE network, my phone loses its data connection unless I force it to use the 4G connection.
I had same exact problem. I Odin'd the MDL tar which put me at MDL baseband and that fixed my problem. http://forum.xda-developers.com/showthread.php?t=2258628
weez101 said:
I had same exact problem. I Odin'd the MDL tar which put me at MDL baseband and that fixed my problem. http://forum.xda-developers.com/showthread.php?t=2258628
Click to expand...
Click to collapse
tried this twice. didnt work, yesterday and today
Deleted.
weez101 said:
I had same exact problem. I Odin'd the MDL tar which put me at MDL baseband and that fixed my problem. http://forum.xda-developers.com/showthread.php?t=2258628
Click to expand...
Click to collapse
Also tried this last night with no success. Still on older baseband. I believe its what breaks my WiFi. The only temporary solution I've found is to flash a custom kernel I found here. Its fixed my WiFi issues but I'd eventually would like to have my baseband upgraded too.
http://forum.xda-developers.com/showthread.php?p=41240723
lazaro17 said:
Also tried this last night with no success. Still on older baseband. I believe its what breaks my WiFi. The only temporary solution I've found is to flash a custom kernel I found here. Its fixed my WiFi issues but I'd eventually would like to have my baseband upgraded too.
http://forum.xda-developers.com/showthread.php?p=41240723
Click to expand...
Click to collapse
Yeah, same. Did not update baseband and I'm having some weird signal issues so hopefully someone figures out how to do this
here guys, try this and let me know if it works please. thanks!
MDL Modem for Odin
mrvirginia said:
here guys, try this and let me know if it works please. thanks!
MDL Modem for Odin
Click to expand...
Click to collapse
Updated baseband for me. Thank you! I was already on Matt's Kernel sobmy WiFi was already working. I would think this would fix any WiFi issues if i go back to stock.
Sent from my SGH-M919 using Tapatalk 2
lazaro17 said:
Updated baseband for me. Thank you! I was already on Matt's Kernel sobmy WiFi was already working. I would think this would fix any WiFi issues if i go back to stock.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
sweet :highfive:
mrvirginia said:
sweet :highfive:
Click to expand...
Click to collapse
You should make a flashable zip
xXchrizhurtyXx said:
You should make a flashable zip
Click to expand...
Click to collapse
i'll try to tmw. this is just what i had on hand and already uploaded
we now have a modem thread
http://forum.xda-developers.com/showthread.php?t=2282342
Wow, that was crazy. I tried heimdall flashing the modem at first and nothing. So I made one of my flashable update .zips I had made for T999 and still nothing!
Then I found this thread and tried something crazy:
(1) Download mode + heimdall flash of a few files w/o reboot, then hard reboot back to Download Mode
(2) heimdall flash of same files w/o reboot (it should error)), then hard reboot back to Download Mode
(3) heimdall print-pit (forces it to reboot cleanly)
I did this with all the firmware files including the bootloader but it was scary. I tried to do all the other firmware files at once and it wrote all but aboot.mbn and failed to write that one out. It was worrying since I the other bootloader files had succeeded and I was worrying I could possibly brick it. I repeated the above steps for aboot.mbn and got it to update as well. It seems the above steps can't be used for all the firmware files at once, but at least a few of them. It seems heimdall can get into a bad state with communicating with the device if too many flashes are pushed at once.
This was with a clean git checkout of heimdall from its github repo the other night. Unfortunately heimdall seems to have a bunch of bugs lately. 1.4rc1 (shipped with Debian and other distros) is broken for the S3. --no-reboot option suppresses reboot on S3 and S4 but further commands are not accepted, requiring manual hard reboot. Earlier versions don't work at all.
It worked out for me in the end but gosh I don't know how I'd modify the script to work short of someone having some sort of way of overriding the write protection. I tried dd manually in recovery and in CM and nothing... Seems like some sort of NAND write protection is going on. If I dd a modem to mmcblk0p1 and read it back, the content doesn't change
Maybe we need something like wpthis.ko from HTC Vision days ...
Anyway I got my wife's phone on UVUAMDL w/o Odin but boy it wasn't pretty. I made an updater script but it doesn't actually work do to the above reasons.
Anyone know what's up with the crazy write protection on the mmcblk0 partitions? It seems nothing ever gets written to mmcblk0p1 for example if I try to write NON-HLOS.bin out to it.
Major props for the modem-only Odin package for the S4, but unfortunately not all of us here have/want to use Windows, so I'd like to figure out a flashable update.zip solution to simplify this like I've done on the T999 S3.
Unfortunately my script was a no-op and only doing a bunch of crazy stuff through heimdall and hard rebooting the device several times over was the only way for me to achieve a full MDL firmware upgrade for S4 that included NON-HLOS.bin and modem.bin (the two modem firmwares on S4), rpm.mbn (Resource and Power Management), sbl{2,3}.mbn and aboot.mbn (MDL bootloader), and tz.mbn (MDL Trust Zone)
I noticed Download Mode had "Write Protect: On" -- I don't remember if my S3 says this or not.
Is anyone working on a way to get around this? Maybe the hack can be integrated into an update.zip script that updates the firmware. MDB radio / firmware seemed really bad on the S4. It would sometimes have trouble making 911 calls (!!!) and was overall really lame with power usage and data. I'm still playing with MDL to see how much improvement there is, but seems like a nice win.
mrvirginia said:
here guys, try this and let me know if it works please. thanks!
MDL Modem for Odin
Click to expand...
Click to collapse
I flashed this & has the wifi working but my 4g lte doesn't come up at all.
Sent from my SGH-M919 using xda premium
sdizzy101 said:
I flashed this & has the wifi working but my 4g lte doesn't come up at all.
Click to expand...
Click to collapse
Does your area have LTE? I don't seem to get LTE in San Jose, California or at least where I live there. I haven't tried it at the office in San Francisco yet.
To start off my name's Gerry.
I have an sgh-t999v from videotron in Montreal. I would like to root my phone and just want to make sure I'm downloading the right file.
http://forum.xda-developers.com/showthread.php?t=1771687
I'm running completely stock 4.1.1 at the moment. Do I have to use the version 4.1.1 or can I use the 4.1.2 for videotron ?
I follow the directions from the same page right?
I ask because I've already tried doing this with instructions from here and it ended disastrously .
http://galaxys3root.com/galaxy-s3-root/how-to-root-t-mobile-galaxy-s3-sgh-t999/
Phone crashed twice then could not get out of download mode.
I ended up finding a stock rom from sprint that I flashed with ODIN.
My counter is now at 9 I believe. I just want to make sure this will work because I don't want to have to go through the bs all over again.
Any insight as to how to make it even easier than it already looks would be greatly appreciated thanks.
4.1.1 or 4.1.2, either is fine. download the root66 file for your phone.
Extract the root66 tar file from the .7z file you downloaded.
Put phone into download mode [ with phone off, hold vol. down + home + power ], connect to computer and open Odin.
once in odin click the PDA field and select the root66 tar you downloaded.
Leave Auto Reboot and F. Reset Time checked.
click start and
when done let phone reboot.
If you have issues flashing with Odin please ensure you are using the microusb cable that came with the phone, users have had issues using other cables.
you can stop here if you just want root.
If you want to flash custom ROMs, download ROM manager from play store to flash the clockworkmods recovery.
Sent from my SAMSUNG-SGH-T999 using xda app-developers app
ayeitschris said:
4.1.1 or 4.1.2, either is fine. download the root66 file for your phone.
Extract the root66 tar file from the .7z file you downloaded.
Put phone into download mode [ with phone off, hold vol. down + home + power ], connect to computer and open Odin.
once in odin click the PDA field and select the root66 tar you downloaded.
Leave Auto Reboot and F. Reset Time checked.
click start and
when done let phone reboot.
If you have issues flashing with Odin please ensure you are using the microusb cable that came with the phone, users have had issues using other cables.
you can stop here if you just want root.
If you want to flash custom ROMs, download ROM manager from play store to flash the clockworkmods recovery.
Sent from my SAMSUNG-SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
When I click on the links to download it doesn't let me.
Brings me here
{"INFO":"failed posted hashcheck","SOLUTION":"please make sure you have javascript enabled for androidfilehost.com. Hit the back button, enable javascript and try again please. we promise we are probably not doing anything nefarious. maybe. no promises though."}
Try using a different browser, like chrome or firefox (if you are not already using one of them) It seems your current browser settings are not properly set. So downloading a different browser could just save you some time and allow you to enjoy the almighty rootness of your S3!!
ayeitschris said:
If you want to flash custom ROMs, download ROM manager from play store to flash the clockworkmods recovery.
Click to expand...
Click to collapse
For the T999V and T999L, its best to not use Rom Manager or Goo Manager. There are a number of flashables that will only flash if you are using the d2tmo (T999) recovery. Using one of those apps will install d2can or d2ltetmo.
Easiest way is to download either TWRP or CWM (both are good, its up to you which) and flash in Odin right after you flash root66.
You'll want to download one with the .tar.md5 extension. Flash in Odin the exact same way you flash the firmware.
You don't have to do this, but its better for broader compatibility.
Sent from my SGH-T999 using xda premium
Thanks a lot!!!!
I used the CWM method and all is good
As for roms.I have just downloaded WICKED and am in the middle of flashing it . Anything I need to look out for ? Any roms you would suggest ?
MtlGalaxy said:
Thanks a lot!!!!
I used the CWM method and all is good
As for roms.I have just downloaded WICKED and am in the middle of flashing it . Anything I need to look out for ? Any roms you would suggest ?
Click to expand...
Click to collapse
nice. one tip, never ever flash roms for the international galaxy s3 (i9300).
wicked is a pretty good rom, was using it before i moved onto 4.2.2 aosp
ayeitschris said:
nice. one tip, never ever flash roms for the international galaxy s3 (i9300).
wicked is a pretty good rom, was using it before i moved onto 4.2.2 aosp
Click to expand...
Click to collapse
I flashed WICKED but no luck . The camera wouldn't work and couldn't connect to the network either maybe I'm doing something wrong . The phone is rooted but I've flashed 2 Rom now and no luck . Does anyone have a link for Rom that are just for the T999v model? Maybe I'm not looking in the right place.
If you flashed your stock kernel the camera wouldve probably worked. If you can't find one, ill make a zip for you a little later. Its usually tge kernel on stuff like that.
An no there are zero roms built only for the T999V. Everyone else has been doing fine with what's available.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
If you flashed your stock kernel the camera wouldve probably worked. If you can't find one, ill make a zip for you a little later. Its usually tge kernel on stuff like that.
An no there are zero roms built only for the T999V. Everyone else has been doing fine with what's available.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Is there a rom that you would work on my phone that you could recommend then
please. it is greatly appreciated.
Just look at the ones that seem to get the most discussion. As far as I was aware, wicked worked fine for just about everyone, so I'd say just try another with similar features you want. If it doesn't work maybe another T999V user can give you a clue as to what you might be missing, if anything. I haven't tried most of them so I'm going by what I hear others say. There are several very good ones to choose from. I'd just start trying them each for a few days to see if any work well for you.
Sent from my SGH-T999 using xda premium
MtlGalaxy said:
I flashed WICKED but no luck . The camera wouldn't work and couldn't connect to the network either maybe I'm doing something wrong . The phone is rooted but I've flashed 2 Rom now and no luck . Does anyone have a link for Rom that are just for the T999v model? Maybe I'm not looking in the right place.
Click to expand...
Click to collapse
When I flashed a rom different from the stock rom I also had issues with the camera.
Option 1:
- You can try dialing *#34971539# (don't forget the * in front) and then selecting your Phone/CAM FW Ver Check
- Once you do that, a little box on the bottom will tell you your Rear Camera Firmware. You have to make sure that they match. If not, you can install the proper firmware (look around on the forums, I know its there)
- Extract the file to the root of your storage and then after that dial *#34971539# and select the second option. This should write the firmware onto your phone
- Exit out and then redial *#34971539# again and select the Phone/CAM FM Ver Check and see if the firmware are both matching. If they are, reboot the phone and it should work again
Option 2:
- If you are running a different rom and stock kernel, the camera may not work so you should probably flash the ktoonsez kernel (http://forum.xda-developers.com/showthread.php?t=1871946) I ran into this problem and after installing this kernel and changing my firmware my camera worked again
I hoped that help you out
dannytron said:
When I flashed a rom different from the stock rom I also had issues with the camera.
Option 1:
- You can try dialing *#34971539# (don't forget the * in front) and then selecting your Phone/CAM FW Ver Check
- Once you do that, a little box on the bottom will tell you your Rear Camera Firmware. You have to make sure that they match. If not, you can install the proper firmware (look around on the forums, I know its there)
- Extract the file to the root of your storage and then after that dial *#34971539# and select the second option. This should write the firmware onto your phone
- Exit out and then redial *#34971539# again and select the Phone/CAM FM Ver Check and see if the firmware are both matching. If they are, reboot the phone and it should work again
Click to expand...
Click to collapse
Sorry, but Ive got to correct a couple of things here. This hasn't worked since at least a couple of updates ago. The firmware write option is locked. Also, you said to extract the file? Do you mean the option to perform the fw dump? This doesn't create a file you can see, use or flash that I've ever found. Not sure what you mean by this. Sorry it just doesn't make sense.
This is the correct way, if it were working.
Chose Cam to Phone FW Ver Check, if the camera firmware is older than the Phone firmware, then you would choose Phone to Cam FW Write. Thats it.
The dump, I believe basically created a fw img dump on one of the underlying partitions. No one ever reported finding it.
Anyway, I believe it was when we updated to LJA that we lost the ability to update the camera firmware. Also, the camera FW is not the device firmware, just so you know.
If you know something different I'm glad to hear it, I'm just not sure what you are trying to tell people to do...
Sent from my SGH-T999 using xda premium
I flashed Dandroid this morning and am loving it so far.
Completely trouble free. The only thing I ask is how do I keep all my apps that i've bought ? Or do I just have to keep downloading them from playstore ?
With me not reading about Samsung latest OTA locked bootloader , I rooted my phone, installed TWRP and updated SU, them I am stuck at a soft brick at the download mod, I have tried every possible way with ODIN to no luck, I always kept booting to the damn download mod, then accidentally I was able to flash this pit file to bypass the stuck download mod and was able to boot normally
All you need is ODIN and the attached pit file,
1. Download attached file and unzip it
2. Run ODIN
3. Click on pit
4. Loacate the unziped SGS-I337_16GB.pit file and load it
5. Click start, phone will reboot when when compelete
6. Done
Thought to share my findings
Good Luck Don't forget to Hit the Thanks Button
This is interesting. Is the PIT file you linked a "signed" PIT file?
The reason I am asking is because the PIT file listed in this thread...
http://forum.xda-developers.com/showthread.php?t=2323019&highlight=pit
...appears to not be signed and I think people had trouble flashing it through ODIN because it was not signed.
The size of the PIT file in the thread I linked and the PIT file in your post is different so it definitely appears to be a different PIT file.
Where did you get the PIT file from in your post? Was it pulled from a device running MF3 firmware?
Also, people should be aware both PIT files are for 16GB phones. It says so in the file name, but it's worth an extra mention just the same.
Thank, and it will be interesting to find out more information about this.
wait so, this will just fix the fact u tried to flash the recovery on mf3.. u weren't able to downgrade to amdl were u ?
scott14719 said:
This is interesting. Is the PIT file you linked a "signed" PIT file?
The reason I am asking is because the PIT file listed in this thread...
http://forum.xda-developers.com/showthread.php?t=2323019&highlight=pit
...appears to not be signed and I think people had trouble flashing it through ODIN because it was not signed.
The size of the PIT file in the thread I linked and the PIT file in your post is different so it definitely appears to be a different PIT file.
Where did you get the PIT file from in your post? Was it pulled from a device running MF3 firmware?
Also, people should be aware both PIT files are for 16GB phones. It says so in the file name, but it's worth an extra mention just the same.
Thank, and it will be interesting to find out more information about this.
Click to expand...
Click to collapse
The pit is indeed signed, and it should work for both 16GB and 32GB according to the original information
Yes It is the same file
Sent from my GT-N7105 using xda app-developers app
iB4STiD said:
wait so, this will just fix the fact u tried to flash the recovery on mf3.. u weren't able to downgrade to amdl were u ?
Click to expand...
Click to collapse
I didn't try, but I don't see why not, dude, this could be a work around
Thanks
Sent from my GT-N7105 using xda app-developers app
nkhater said:
The pit is indeed signed, and it should work for both 16GB and 32GB according to the original information
Yes It is the same file
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Can you tell me where the original information came from (a link)?
scott14719 said:
Can you tell me where the original information came from (a link)?
Click to expand...
Click to collapse
Prob his phone...they are simple to pull from your phone, at least with heimdall. Ive been able to pull my pit with heimdall and use it in odin successfully
His is the exact same size of the pit I pulled from my device which confirms my theory on obtaining it
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
mg2195 said:
Prob his phone...they are simple to pull from your phone, at least with heimdall. Ive been able to pull my pit with heimdall and use it in odin successfully
His is the exact same size of the pit I pulled from my device which confirms my theory on obtaining it
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
The reason i am asking is because I think people have tried to use the PIT file (the one I linked above) with ODIN, and although ODIN reported it as successfully flashing, it actually did not flash. Of course, the PIT file I linked above couldn't have been from MF3 (it wasn't released at the time of that post), but I was wondering if it was a signing issue with the PIT file that kept it from actually flashing, and if not, what would be the difference between the PIT file posted by the OP and the PIT file that is in the thread I linked (other than being pulled from different firmwares)?
It is my understanding (I might be wrong here), that flashing a PIT file via ODIN to a phone would erase all partition information including ROM, KERNEL, and boot partitions. Without this information (in this case a MF3 TAR file) being flashed through ODIN directly after a successful PIT file flash, how could the phone successfully boot back up into MF3? And we all know an ODIN flashable MF3 TAR does not yet exist.
scott14719 said:
The reason i am asking is because I think people have tried to use the PIT file (the one I linked above) with ODIN, and although ODIN reported it as successfully flashing, it actually did not flash. Of course, the PIT file I linked above couldn't have been from MF3 (it wasn't released at the time of that post), but I was wondering if it was a signing issue with the PIT file that kept it from actually flashing, and if not, what would be the difference between the PIT file posted by the OP and the PIT file that is in the thread I linked (other than being pulled from different firmwares)?
Click to expand...
Click to collapse
You know...im not sure. I mean...even with new firmwares shouldnt it be the same? Unless they changed the partitions around in mf3...than again...the one I pulled from my phone was from mdl and mine is the same exact size as his...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
mg2195 said:
You know...im not sure. I mean...even with new firmwares shouldnt it be the same? Unless they changed the partitions around in mf3...than again...the one I pulled from my phone was from mdl and mine is the same exact size as his...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
I added some Ninja edit info to my last post...
nkhater said:
I didn't try, but I don't see why not, dude, this could be a work around
Thanks
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
i say fire up odin and try to downgrade to amdl :good:
iB4STiD said:
i say fire up odin and try to downgrade to amdl :good:
Click to expand...
Click to collapse
As much as I would like to see it work, I don't think it would be a good idea.
A. If the OP was on MF3, how did he even attempt to install TWRP as was stated?
B. (I mentioned this in one of my lasts posts in this thread) If the PIT fil actually has flashed successfully, how would any information (other than partition information) remain on his phone? Wouldn't the PIT file wipe it completely...requiring the OP to immediately flash a firmware TAR file...which does not exist yet for MF3?
Something either is very right with this (a breakthrough) or is very wrong with this.
scott14719 said:
As much as I would like to see it work, I don't think it would be a good idea.
A. If the OP was on MF3, how did he even attempt to install TWRP as was stated?
B. (I mentioned this in one of my lasts posts in this thread) If the PIT fil actually has flashed successfully, how would any information (other than partition information) remain on his phone? Wouldn't the PIT file wipe it completely...requiring the OP to immediately flash a firmware TAR file...which does not exist yet for MF3?
Something either is very right with this (a breakthrough) or is very wrong with this.
Click to expand...
Click to collapse
see, im hoping very right.. I would love to see people get around the sammy bs.. so im trying to be positive (for once) Im confused how this would work myself.. but hey stranger things have happened.. :good:
iB4STiD said:
see, im hoping very right.. I would love to see people get around the sammy bs.. so im trying to be positive (for once) Im confused how this would work myself.. but hey stranger things have happened.. :good:
Click to expand...
Click to collapse
I am theorizing (just a theory) that the PIT file actually did not flash through ODIN. It reported as flashing correctly (successful), but as others have experienced, it was a false positive and didn't really flash. I am guessing the OP's phone started to work because of the method ODIN used to reboot the phone somehow bypassed the bootloop caused by trying to put TWRP onto MF3. I have seen a couple of recent posts where people were able to boot their phones by somehow getting into recovery and canceling a certain operation out ( I'm not sure which), causing the phone (that was in a previous bootloop) to start booting correctly.
I hope it is a break through as well, but I am leaning towards my explanation (or one close to it) as the reason for the OP's success.
scott14719 said:
I am theorizing (just a theory) that the PIT file actually did not flash through ODIN. It reported as flashing correctly (successful), but as others have experienced, it was a false positive and didn't really flash. I am guessing the OP's phone started to work because of the method ODIN used to reboot the phone somehow bypassed the bootloop caused by trying to put TWRP onto MF3. I have seen a couple of recent posts where people were able to boot their phones by somehow getting into recovery and canceling a certain operation out ( I'm not sure which), causing the phone (that was in a previous bootloop) to start booting correctly.
I hope it is a break through as well, but I am leaning towards my explanation (or one close to it) as the reason for the OP's success.
Click to expand...
Click to collapse
ya, wiping cache in stock recovery, will kick the phone out of bootloop
iB4STiD said:
ya, wiping cache in stock recovery, will kick the phone out of bootloop
Click to expand...
Click to collapse
And here is another example of someone getting out of a bootloop through Download (ODIN) mode:
http://forum.xda-developers.com/showpost.php?p=44433724&postcount=11
Possibly, Odin triggered a similar reaction.
Actually, the original thread i pulled that post out of sounds very similar to what happened to the OP in this post.
Take a look at the OP of this post to see what I mean:
http://forum.xda-developers.com/showthread.php?t=2398336
So, I think my theory is correct. The PIT file never actually flashed, it was the interaction between ODIN and D/L mode that overcame the bootloop.
But hey, feel free to keep messing around with the PIT file because you never know...
I wonder where op went...
Sent from my SGH-I337 using xda premium
orlandoxpolice said:
I wonder where op went...
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
OP was sleeping and just woke up will reply shortly
Sent from my GT-N7105 using xda app-developers app
scott14719 said:
It is my understanding (I might be wrong here), that flashing a PIT file via ODIN to a phone would erase all partition information including ROM, KERNEL, and boot partitions. Without this information (in this case a MF3 TAR file) being flashed through ODIN directly after a successful PIT file flash, how could the phone successfully boot back up into MF3? And we all know an ODIN flashable MF3 TAR does not yet exist.
Click to expand...
Click to collapse
Sorry if this off topic but what's stopping someone from wiping the bootloader partition and flashing the MDL firmware?
I'm not sure if this would be done via a PIT file, ADB script or some other method but in general isn't this the path of last resistance for achieving root/bootloader access?
scott14719 said:
Can you tell me where the original information came from (a link)?
Click to expand...
Click to collapse
Here is the link
http://forum.xda-developers.com/showthread.php?t=2323019&highlight=pit
hello every one
as the subject says if you soft brick your phone for whatso ever reason( and you are facing Firmware Upgrade encountered an issue on display when turning on,
then this solution might be very helpful for you
i was on 4.3 with MJ5 boot loader, made the mistake didnt checked the phone info and tried to downgraded the firmware caused my phone soft bricked
the worst thing i realized i didnt made any backup( even the EFS back up was lost)
in short the story is..
i asked couple of people for advise,
i tried following to bring my phone back
* Samsung Kies( recovery Modes by entering Device Serial Numbers and Model Name) Result: Failed, this device cant be upgraded/restored due to custom firmware
* Odin: 3.09 + stock firm ware ( 4.3 from O2uk and then 4.3 3 Uk) Result: failed, error message, missing PIT File
* Tried to find PIT File online but there are few places you can get stock 4.3 Firmware Extracted PIT File to flash) tried here http://forum.xda-developers.com/show....php?t=1927983, result failed
* then tried different firmwares ( European, French 4.3, UK 4.1 with and Without PIT file ( http://www.sammobile.com/firmwares/) but failed again, the ODIN 3.09 was not helping out here
I was about to give up here but then steff advise me to try and flash rescue firm ware from http://forum.xda-developers.com/showpost.php?p=32273406 link but only 2nd firm ware ( not the 1st or 3rd, ) for some reason the 4.1 rescue firmware link is down,( download from here : https://www.dropbox.com/s/qs9wigflyrwp8ip/N7100XXDLL7_N7100OXADLL4_N7100XXDLK7_FACTORY_XEF.rar)
Android - 4.1.2
PDA - N7100XXDLL7
CSC - MULTI XEF_N7100OXADLL4
RADIO - N7100XXDLK7
DOWNLOAD_N7100XXDLL7_FACTORY (2012-28-12)(
and steff helped me out with his drop box to upload the rescue firm ware ( https://www.dropbox.com/s/gfdh3mgbv34c3ti/N7100XXDLL7_N7100OXADLL4_N7100XXDLK7_FACTORY_XEF.rar )
any way by extracing the rescue firmware 4.1, and doing PIT file flash with Odin 3.09 didnt worked either, so as per advise i changed the Odin 3.09 to 3.07( download from ( Odin 3.07 - XDA-Developers)
i was successfuly able to flash PIT ( done this number of times , at first flashed rescue firmware with PIT File, failed half way cause the PIT was flashed but firmware couldnt went through, then flashed rescue firmware 4.1 alone
stopped half way, again started in download mode and flashed it went through and finally phone booted up)
* NOw the IMEI was gone, tried to enter phone engineering screen to update the IMEI from GPR Service Menu but failed
* i flashed MJ5 boot loader to see if it works fine failed again.
* Finally i was told to flash Stock 4.4 KK which will remove all bugs from the phone and hope fully the phone will boot with correct imei
downloaded 4.4 from this link ( https://mega.co.nz/#!2QRmCbyb!YkWs927BfvYxqL-vJiQHXkshqG3UtqHm4XIDbgLsEK0) fast download, and flashed successfully , which bring my note back to life
everything works fine
* I tried to flash 4.4.2 direct to see if it works( both with Odin 3.09 and 3.07 before flashing rescue firm ware but this didnt work either
* IMportant Points:
Avoid flashing any rom/kernal unless you are sure what you are doing
* always keep a nand back up prior to any flashing
* always read good enough before you flash
* and even if you read enough and something went wrong, use your phone for parts and pay for the charity at the end
i hope this is simple guide for you to sort your bricked phone from the error'' firmware upgrade encountered an issue please connect with kies''
special thanks to smeet.somaiya , singhpratik87 , , Logel, nitol, and Specially to steff195 for providing all links up and running
this will save time and money to those who are out of warranty
thanks
@tnt4ever awesome guide dude
Sent from my GT-N7100 using Tapatalk
singhpratik87 said:
@tnt4ever awesome guide dude
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Hi @tnt4ever Please help me, I softkitted my n7100, and by reading you guide I need factory firmwire, but the download link is not working, could you please share it???
Let me check
Sent from my GT-N7100 using XDA Premium 4 mobile app
Hello
Have you tried loading 4.4 with odin
What is the issue with the phone...?
Sent from my GT-N7100 using XDA Premium 4 mobile app
carlinleos said:
Hi @tnt4ever Please help me, I softkitted my n7100, and by reading you guide I need factory firmwire, but the download link is not working, could you please share it???
Click to expand...
Click to collapse
I have requested steff to upload the rescue firmware Dropbox link just wait for that
If u can find that somewhere else u can try in the mean while give it a Google search
Sent from my GT-N7100 using XDA Premium 4 mobile app
http://www.4shared-china.com/zip/OSOApuGm/N7100XXDLJ2_OXA_FACTORY.html
Sent from my GT-N7100 using Tapatalk
carlinleos said:
Hi @tnt4ever Please help me, I softkitted my n7100, and by reading you guide I need factory firmwire, but the download link is not working, could you please share it???
Click to expand...
Click to collapse
Hello
I hope u can fix your issue with below link provided by Ibrahim
Keep updated
Sent from my GT-N7100 using XDA Premium 4 mobile app
WoW! guys you rock!!! i was able to fix the issue!!! thanks and best regards
---------- Post added at 03:16 AM ---------- Previous post was at 03:13 AM ----------
tnt4ever said:
Hello
Have you tried loading 4.4 with odin
What is the issue with the phone...?
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thatd what I did, I downloaded, a stock 4.4 And flashed it using Odin, let me tell you I was scared!
@tnt4ever I always have problem flashing any firmware, official or custom, either the imei goes corrupt or phone goes in emergency calls only. Can I flash this firmware to get out of the situation and get OTA update for 4.1.2, 4.3 or 4.4.2.
Thanks.
Sent from my GT-N7100 using Tapatalk
thankyou for your share.this method is really good
ibraahim said:
@tnt4ever I always have problem flashing any firmware, official or custom, either the imei goes corrupt or phone goes in emergency calls only. Can I flash this firmware to get out of the situation and get OTA update for 4.1.2, 4.3 or 4.4.2.
Thanks.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Ibrahim this can be a corrupt partiton
I have explained everything in details I tried
I am not a developer but I have experienced almost every possible way out to flash my phone and it worked as well
What is the actual story of your phone, can you please explain in detail what happened before you may start any solution
If possible details
Regards
Sent from my GT-N7100 using XDA Premium 4 mobile app
carlinleos said:
WoW! guys you rock!!! i was able to fix the issue!!! thanks and best regards
---------- Post added at 03:16 AM ---------- Previous post was at 03:13 AM ----------
Thats what I did, I downloaded, a stock 4.4 And flashed it using Odin, let me tell you I was scared!
Click to expand...
Click to collapse
Happy to see you are back on life with your note 2
Sent from my GT-N7100 using XDA Premium 4 mobile app
@tnt4ever my problem is this...
Guys I have been experimenting with a lots of custom roms, but flashing them only results in emergency calls only. My imei remains intact but mobile network does not work.
I have tried flashing Wanamlite v3.9, Phoenix 13, Omega 17-18, tried changing modems, ariza patch, restoring efs via terminal emulator and note 2 tool kit.
Right now I am on XXDLL7 and DDDMG1 (patched using Zuluman's modem patcher and it worked!!!)
I have successfully flashed 4.4.2 dn3 v5 with patched kernel, but due to some reasons I prefer 4.1.2, and would like to use any of the four aforementioned custom roms.
Please help. Thanks.
Sent from my GT-N7100 using Tapatalk
Hey guys, sorry for the delay...
Dunno if the link provided by ibraahim is efficient for anyone having a problem, if it does, it's fine by me, but when I had troubles months ago (because I ticked "Nand Erase All" option in Odin, thus corrupting my bootloader and messing up my phone) I tried all the solutions from this link and, as tnt4ever well remembered to specify in OP, only the 2nd firmware from that link worked. That file was the only one to contain all three required files to re-write the bootloader and related stuff (param.img, tz.img, sboot.bin), along with the .pit file, for re-partition. Ibraahim's file is the one from the 3rd file from that link, so I remember it didn't contain all those files. But, I repeat, according to your phone's problem, that firmware could be just fine to fix your problem. For me, it didn't.
So, as OP stated, the links are not available anymore, but I have the file on my pc and uploaded (again) to my Dropbox, if anyone needs it. The problem is that Dropbox doesn't allow excessive file download and thus the file may become unavilable for download (as it did before). So, the one(s) who get to grab the file, is more than welcome to mirror it.
N7100XXDLL7_N7100OXADLL4_N7100XXDLK7_FACTORY_XEF.rar
Btw, tnt4ever: didn't you already have this file, since you downloaded and tried it, so you could upload it somewhere?
steff195 said:
Hey guys, sorry for the delay...
Dunno if the link provided by ibraahim is efficient for anyone having a problem, if it does, it's fine by me, but when I had troubles months ago (because I ticked "Nand Erase All" option in Odin, thus corrupting my bootloader and messing up my phone) I tried all the solutions from this link and, as tnt4ever well remembered to specify in OP, only the 2nd firmware from that link worked. That file was the only one to contain all three required files to re-write the bootloader and related stuff (param.img, tz.img, sboot.bin), along with the .pit file, for re-partition. Ibraahim's file is the one from the 3rd file from that link, so I remember it didn't contain all those files. But, I repeat, according to your phone's problem, that firmware could be just fine to fix your problem. For me, it didn't.
So, as OP stated, the links are not available anymore, but I have the file on my pc and uploaded (again) to my Dropbox, if anyone needs it. The problem is that Dropbox doesn't allow excessive file download and thus the file may become unavilable for download (as it did before). So, the one(s) who get to grab the file, is more than welcome to mirror it.
N7100XXDLL7_N7100OXADLL4_N7100XXDLK7_FACTORY_XEF.rar
Btw, tnt4ever: didn't you already have this file, since you downloaded and tried it, so you could upload it somewhere?
Click to expand...
Click to collapse
Hello steff
Thanks for your detailed reply
As I said I am travelling at the moment
I do have the file saved in my pic you provided and I didn't get time to upload it
Any way I will do this in the first instance this week as I have to travel for work during the week and long week caused a lot of work delays
Thanks for the help but if you can advise where I can mirror it easily would be nice.
Sent from my GT-N7100 using XDA Premium 4 mobile app
steff195 said:
Hey guys, sorry for the delay...
Dunno if the link provided by ibraahim is efficient for anyone having a problem, if it does, it's fine by me, but when I had troubles months ago (because I ticked "Nand Erase All" option in Odin, thus corrupting my bootloader and messing up my phone) I tried all the solutions from this link and, as tnt4ever well remembered to specify in OP, only the 2nd firmware from that link worked. That file was the only one to contain all three required files to re-write the bootloader and related stuff (param.img, tz.img, sboot.bin), along with the .pit file, for re-partition. Ibraahim's file is the one from the 3rd file from that link, so I remember it didn't contain all those files. But, I repeat, according to your phone's problem, that firmware could be just fine to fix your problem. For me, it didn't.
So, as OP stated, the links are not available anymore, but I have the file on my pc and uploaded (again) to my Dropbox, if anyone needs it. The problem is that Dropbox doesn't allow excessive file download and thus the file may become unavilable for download (as it did before). So, the one(s) who get to grab the file, is more than welcome to mirror it.
N7100XXDLL7_N7100OXADLL4_N7100XXDLK7_FACTORY_XEF.rar
Btw, tnt4ever: didn't you already have this file, since you downloaded and tried it, so you could upload it somewhere?
Click to expand...
Click to collapse
Hello
Is your issue sorted now with the link provided by steff..?
ibraahim said:
@tnt4ever my problem is this...
Guys I have been experimenting with a lots of custom roms, but flashing them only results in emergency calls only. My imei remains intact but mobile network does not work.
I have tried flashing Wanamlite v3.9, Phoenix 13, Omega 17-18, tried changing modems, ariza patch, restoring efs via terminal emulator and note 2 tool kit.
Right now I am on XXDLL7 and DDDMG1 (patched using Zuluman's modem patcher and it worked!!!)
I have successfully flashed 4.4.2 dn3 v5 with patched kernel, but due to some reasons I prefer 4.1.2, and would like to use any of the four aforementioned custom roms.
Please help. Thanks.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Sent from my GT-N7100 using XDA Premium 4 mobile app
Hello Every one
link to my drop box in case required
https://www.dropbox.com/s/qs9wigflyrwp8ip/N7100XXDLL7_N7100OXADLL4_N7100XXDLK7_FACTORY_XEF.rar
@tnt4ever, I flashed the above ROM but I still have problem with imei.... it becomes 0049×××. What do you suggest now.
Actually I don't want to flash any 4.3 or above Rom. I do get everything working on 4.3 and above with patched kernel and modem. But I need to get 4.1.2 working without tripping imei or getting emergency calls only.
Can you please find a 4.1.1 rom for me. Please.
Sent from my GT-N7100 using Tapatalk
8
ibraahim said:
@tnt4ever, I flashed the above ROM but I still have problem with imei.... it becomes 0049×××. What do you suggest now.
Actually I don't want to flash any 4.3 or above Rom. I do get everything working on 4.3 and above with patched kernel and modem. But I need to get 4.1.2 working without tripping imei or getting emergency calls only.
Can you please find a 4.1.1 rom for me. Please.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
hello Ibrahim
i find it really funny but to be very honest once you flash stock 4.4.2( download and flash with doing 3.07) then your imei issue will be sorted
i used stock 4.4 for few days then i rooted the phone and went back on latest dn3 v5+ rom
anyway once you got your working phone then you can Do whatever you want ( rooting flashing any rom you wish)
Sent from my GT-N7100 using XDA Premium 4 mobile app