Related
How might one apply the DJ05 update without using Odin v3?
Clearly the ROM and Kernel can be updated through CWM, but all searchable info seems to indicate that the modem file can only be altered via Odin on M$ Windoze. What is the methodology behind applying this kind of change using only tools available on a Linux platform?
Can I just overwrite a file on the Fascinate via adb?
cheers
I have only ever heard of modem.bin being flashed via Odin. I could be wrong, but I think it occupies its own partition, hence the need to actually flash rather than copy an individual file.
You can use redbend_ua to flash without Odin, but I recall (perhaps incorrectly) reading in IRC that redbend doesn't work for modem flashes in practice, at least not yet.
Hopefully someone can give more authoritative info, but I think you are stuck with Odin for good reasons. Just be nice to one of your friends with a PC. Don't have any? Shame! Windows users need love too ya know.
Swyped w/ XDA App. When in doubt, mumble.
Google search keyword: heimdall
Sent from my SCH-I500 using XDA App
Heimdall:
http://forum.xda-developers.com/showthread.php?t=755265
Awesome. That's a good question, why don't we just speak in terms of Heimdall in general... and use that instead? Strangely more soothing to say anyway, like "goos fraba"
You might find post 3 here useful as well.
That thread Soba49 posted is about 60 pages now, but reading through it all will give you a lot of good info on how it works. About page 56 or 57, you will see some specific questions I posed regarding flashing DJ05 modem.bin onto the Fascinate. It's almost too simple to use, so best to understand it as this is also the tool that will be saving your arse if you 'almost' brick your phone.
Heimdall actually emulates Odin in some areas & Kies in others and aims to eventually do more than either of those tools, w/o all the buggy Samsung coding. I believe the modem.bin is flashed using Kies methodology, FWIW.
So, I've been searching all over this forum and through the 60 pages of the Heimdall thread, but can't find an answer to this simple question - how do I just flash DJ05 onto my fascinate from OSX 10.6? When I try to connect in download mode and turn on Heimdall frontend, I just get "no compatible device connected" Do I need to flash bootloaders too or some other complicated stuff? Or am I just missing something easy?
SupraLance - What happened when you commanded: "heimdall flash --verbose --modem modem.bin"?
That command flashed the new modem for me. I am running DJ05 now and my phone has never been violated by a Windows device, lol.
I just re-read a bit of that thread regarding OSX, and it seems that Samsung released these phones with a crappy secondary boot loader. It will communicate with Linux and Windows, but not OSX. The only way around this is to flash a fixed boot loader through Linux or Windows, then you can use OSX from there out. Big problem is the only fixed boot loader verified to work with Heimdall & OSX is for the International Galaxy S. You need one specific for the Fascinate.
So this leaves American OSX users hoping that Samsung fixed this in the 2.2 Froyo code they have released. Heimdall & Odin cannot be made to work on OSX without it and boot loaders are not something you want to experiment with. Messing with the boot loader = quickest way to truly brick your phone.
If I was at your computer trying to do this, I would set up a dual-boot on your Mac with Ubuntu (completely free and similar to OSX interface) and do it through Ubuntu.
Heimdall Success!
fragmented post
Code
fragmented post
Notes on Code.
fragmented post
Next step.
fragmented post
fragmented post
Heimdall Success!
Installed Heimdall 1.1.0 for Debian.
http://www.glassechidna.com.au/products/heimdall/
Flashed modem using:
Code:
heimdall flash --verbose --modem modem.bin
Making sure that SF is in DL mode and the current directory contains "modem.bin" file.
Then flash ROM (and Kernel) via CWM.
Additional possibly helpful info here:
http://mobiletech.knguyentu.com/2010/12/fascinate-rom-dj05-and-beyond-all-you.html
Cheers
So I began playing around with "rooting," my Vibrant. I'm a computer engineer, but relatively new to the whole "smart phone," thing. Loaded a few different ROMs, played around a bit. No problem. At some point tonight, I tried to load a new ROM, and after clockworkmod, the vibrant screen took FOREVER. That's about the time my cats went crazy. Long story short, I dropped the phone. Cover popped off, battery fell out.
Now, the phone is sitting at the Vibrant screen for hours, will not boot into recovery mode, and if I plug it in, it just shows a gray battery.
I've tried the 3-button recovery mode over and over, with no success. Nothing at all. I CAN get to "download," mode, where I get the droid icon, and it says "Downloading...Do not turn off Target!!!" That said, I have no idea what, if anything, I can do from this screen. I have no idea what to do, but I know I can't afford another 500.00 phone. Please help!!
--SFGAirborne
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
Sent from my Vibrant running Bionix-v 1.2.1 in GingerRED
Probably you will need a couple of things in your tool kit.
You will need Odin 1.3 or higher
Pit file (there are 512 and 831) Guessing you will need the 512pit
Original JFD stock file 2.1
Eugenes froyo that does not brick
Remove the sim and the sd card, remove the battery have Odin up on the computer> then hold down the 3 buttons and plug in the phone to the usb connected to computer. If this works and Odin sees the phone (does not matter if it says com5 or 6 etc.) then you can go from there, If not then you will need a jig, people here sell them, i saw connextion2005 sells them but there are others (like 8bucks) or you could make it is 301k resistors tied to one 2 pins of the usb (do a search if you are interested).
Then the sequence for the fix is to flash the Froyo first that does not brick (do not check repartition) once it begins to reboot pull the battery out (does not need to reboot) then flash the JFD on top and this time check the repartition
Let this finish reboot> then use super one click root or other of your choice. Then download CWM and Titanium backup...... flash your new rom and you are back in business.
Hope that helps
Thanks a ton! Open-source research indicates Odin is a proprietary tool used by Samsung techs, correct? I'm not at home right now, so I can't do anything with it, but I will download and run when I get home. Does it have to be run from Windows? I'm a Linux user. If necessary, I can build a VM, but if Odin will work easily in Wine, that's better for me.
Again, thanks for the help!
Odin is your one way stop to guarantee that your phone will always work, unless it's hardware issues.
I have used Odin to go back to stock so many times to clear data, to reflash ROMs or to recovery from splash screen loops or soft bricks. Always works like a charm.
You should check out CyanogenMod forums under Galaxy S and there is a step by step guide how to do it. That's what I use. Works always!
Sent from my SGH-T959 using XDA App
sfgairborne said:
Thanks a ton! Open-source research indicates Odin is a proprietary tool used by Samsung techs, correct? I'm not at home right now, so I can't do anything with it, but I will download and run when I get home. Does it have to be run from Windows? I'm a Linux user. If necessary, I can build a VM, but if Odin will work easily in Wine, that's better for me.
Again, thanks for the help!
Click to expand...
Click to collapse
I have a friend running fedora and odin works fine for him, if you have problems with Odin there is another application out there called heimdall, you will have to excuse me as i have no experience with it, but have heard that it plays well with linux and unix systems when odin doesnt.
sfgairborne said:
Thanks a ton! Open-source research indicates Odin is a proprietary tool used by Samsung techs, correct? I'm not at home right now, so I can't do anything with it, but I will download and run when I get home. Does it have to be run from Windows? I'm a Linux user. If necessary, I can build a VM, but if Odin will work easily in Wine, that's better for me.
Again, thanks for the help!
Click to expand...
Click to collapse
Try Heimdall: Here is a post I did last week:
http://forum.xda-developers.com/showthread.php?t=944598
maybe you will get better results with this, there also is a linux version as well
The Bible is also a good reference:
http://forum.xda-developers.com/showthread.php?t=771111
Restoring via ODIN, as we speak. No idea how long it'll take, but I'll let you know the outcome. Again, thanks a ton!
And, I've definitely learned my lesson. Being a "computer guru," does not necessarily translate to being a "technology guru." I should probably RTFM before playing with things I don't know next time. If I can ever off you all any network security advice/assistance, please feel free to ask.
You all rock! Fully restored, back up and running!!
I bricked a brand new verizon galaxy tab! It isn't even mine. it's my brothers and he's going to be pissed if i can't fix it
here is what i did:
i rooted it using z4root from this post: http://forum.xda-developers.com/showthread.php?t=833953
no problems.
then i downloaded sgs kernel flasher from the market and flashed this file http://gunsforgeeks.com/Tab/kernel/KhasMek.Voodoo.plus.CDMA.Tab.v4.OC.zImage
which i got from this post: http://forum.xda-developers.com/showthread.php?t=941781
it auto re-booted when done and is now stuck on samsung logo forever! **** me! i can't reboot into recovery, but i can reboot into download mode.
only problem is i have an old mac ibook running osx 10.4 which is too old for hemidall and too mac for odin. for christs sake i can't even get bootcamp or parallels to work on that old of a mac so i can run windows and thus odin.
what can i do? i'd really like to fix this without having to ask my brother to use his newer mac that should let me run hemidall, cause if i bricked his tab he ain't gonna want me touching his computer.
any suggestions? pleeeeeeease
Get rid of your ****ty mac and get a windows based PC/laptop instead obviously, then flash using odin etc.
Also use the search function, there is an endless amount of topics on this exact issue so no need to create a new one just because you are scared your bro is gunna kick your arse.
Oh btw, your device isnt "bricked", I wish people would not use that term so loosely.
You're gonna have to beg, borrow, buy, or otherwise get yourself a machine that'll run Heimdall... don't think there's any other way around it...
Once you do that, do this: http://forum.xda-developers.com/showthread.php?t=967175
crisis averted
sorry ya'll. you'll have to excuse a noob. crisis has been averted. i borrowed a windows laptop and successfully restored to stock via hemidall. guess i have more reading to do before i attempt to flash a rom on this thing again. didn't think i was such a noob as i've never had such problems flashing all kinds of roms on my vibrant. different devices. chalk it up to a learning experience.
tkirkable said:
sorry ya'll. you'll have to excuse a noob. crisis has been averted. i borrowed a windows laptop and successfully restored to stock via hemidall. guess i have more reading to do before i attempt to flash a rom on this thing again. didn't think i was such a noob as i've never had such problems flashing all kinds of roms on my vibrant. different devices. chalk it up to a learning experience.
Click to expand...
Click to collapse
Good to hear you solved the problem. Just out of curiosity what happened when you tried to run Heimdall on your mac? Theoretically the universal binaries I redistribute should run on 10.4+ with any processors architecture supported by OS X (i.e. x86, AMD64 and PPC).
Heimdall requires osx 10.5?
Apparently. That's what it says when i try to open the .pkg file. it says this package type requires osx 10.5 I can run it in windows 7 though. I had to three times yesterday cause i kept soft bricking my device if that's the right way to put it. read read read. i must be missing something. I had clockworkmod recovery and ext. 4 for a second but then froze on the samsung logo at reboot again. had to heimdall my way back and lost it all. back to the drawing board
okay well i rooted my phone a while ago with motochopper and yesterday i tried to download the cyanogenmod from the rom manager and it downloaded but once it rebooted it wen into a boot loop of the cyanogenmod logo so i tried to to restore from the factory clockworkmod backup and it wont restore back. im on a mac so what can i do i got the phone back to the original samsung software but its now stuck on the ATT logo. also it will load all the way up to a new setup but then the setting stop working and i cant go any further. can anyone lead me in the right direction
In the future, don't use rom manager for anything other than getting a custom recovery on your phone. I've seen more people cause problems on their phone using it. Search for heimdal. It is similar to odin for putting stock recoveries on your phone using a Mac. I've never used it so can't be of much additional help.
i tried using hemdall to put a stock tar file on the phone and it still wont restore. its stuck on the custom driver and i dint know what to do
jb0322 said:
i tried using hemdall to put a stock tar file on the phone and it still wont restore. its stuck on the custom driver and i dint know what to do
Click to expand...
Click to collapse
Ate you sure the rom you got from rom manager was for your specific device?
i mean it was the latest CM 10.2 idk if that had anyting to do with it
jb0322 said:
i mean it was the latest CM 10.2 idk if that had anyting to do with it
Click to expand...
Click to collapse
The thing I don't like about rom manager is it's too easy to grab a Rom that is not for your phone. I'm guessing that's what you did and you've messed up the partitions on it. I hate to say it, but I think jtag is your option at this point. Look up mobiltechvideos.com.
There are also some pit files floating around here, but they scare me and can do more harm than good.
Hi! jb0322
I use a Mac (a couple of them, actually) and found that heimdal can be made to work, but it just is not as user friendly as Odin. (Btw, you should not need a custom driver to use Heimdal -its a mac and should see your phone w/o driver issues!)
Maybe it's just my experience, but sometimes when you have everything set up correctly, Heimdal still seems to choke, or just not complete the task (or see the tar file that you want to use!). The newer versions seem better, but I have not found it particularly easy to use. [Also, are you using a current version of Heimdal? Heimdal front end package? Here is a Heimdal link in case you want to check: http://www.glassechidna.com.au/products/heimdall/ . Please check your file -the stock image or rom image that you want to load and make sure it's the right one and also that its in a form Heimdal can use. . .
Conversely, Odin seems to work great -especially (or even) the older versions. This is why I think you could save yourself tons of time and open your options up significantly if you can either: (1) use bootcamp and boot into a windows OS, or (2) use Parallels/VM Ware Fusion and use windows in a virtual window.
Bootcamp is 100% windows running on your mac and is rock-solid, while the VM machine approach also is mature and pretty good, if occasionally temperamental...:good:
If you can do this, then you can use Odin and work to restore you phone with all the tools that most folks here have and use to good effect.
Agree with the advice on being real careful on using Rom Manager, it works, but also seems to have a knack for surprising you with a bad outcome when least expected.
Good Luck!
---------- Post added at 09:45 AM ---------- Previous post was at 09:27 AM ----------
Here is another very good, informative thread right here on this forum sharing someone's experience restoring his i337 using Heimdal!
it might be helpful (and it is just a few posts down from yours
http://forum.xda-developers.com/showthread.php?t=2374441
jd1639 said:
In the future, don't use rom manager for anything other than getting a custom recovery on your phone. I've seen more people cause problems on their phone using it. Search for heimdal. It is similar to odin for putting stock recoveries on your phone using a Mac. I've never used it so can't be of much additional help.
Click to expand...
Click to collapse
I have read so many posts of people using Rom Manager/Goo Manager and soft bricking their devices with it by just trying to install custom recoveries...I wouldn't touch either.
There are tools available to automatically install custom recoveries...seems much more stable and safe, especially for rookies.
This one is my favorite - lets you pick OUDHS auto-loki CWM or TWRP:
http://forum.xda-developers.com/showthread.php?t=2297033&highlight=oudhs
I started this thread: (https://forum.xda-developers.com/axon-7/help/help-loss-root-twrp-t3781054)
a while back and ended up never solving my issue, eventually giving up and living with an unrooted phone.
Anyhow I've been trying again to get to the bottom of the issue and after another day of fruitless research here I am hoping to bring it back to your attention.
Does anyone around here regularly use a mac to perform adb commands? I'd love to get some help trying to get fastboot working again.
Should I just give up and find a Windows computer to do this?
Thanks for reading
alajoy said:
I started this thread: (https://forum.xda-developers.com/axon-7/help/help-loss-root-twrp-t3781054)
a while back and ended up never solving my issue, eventually giving up and living with an unrooted phone.
Anyhow I've been trying again to get to the bottom of the issue and after another day of fruitless research here I am hoping to bring it back to your attention.
Does anyone around here regularly use a mac to perform adb commands? I'd love to get some help trying to get fastboot working again.
Should I just give up and find a Windows computer to do this?
Thanks for reading
Click to expand...
Click to collapse
That guy was horribly wrong and sorry you had to live with an unrooted phone for so long. But in newer versions of Nougat (i think B32 or B35) they removed fastboot and you could not boot into it. I have a way of being able to install TWRP here without fastboot (assuming you're on an Oreo bootstack, otherwise you can do almost everything in that thread except use a TWRP for Nougat instead). I haven't tried this, but if you have stock recovery, try downgrading to Nougat B19 by using an official SD card update and using apply update from SD card in stock recovery. Haven't found an official SD card update for you but I've only done a little bit of searching.
edit: ive only found B19 Nougat full image , but here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ!tNsQhD5Y
download A2017U-7.1.1-B19-Full-326200B1901A2017UV1.1.0B19.zip and extract it and put update.zip in your sd card. boot into stock recovery and use apply update from sd card and select it. hopefully it works and it will downgrade
Teet1 said:
That guy was horribly wrong and sorry you had to live with an unrooted phone for so long. But in newer versions of Nougat (i think B32 or B35) they removed fastboot and you could not boot into it. I have a way of being able to install TWRP here without fastboot (assuming you're on an Oreo bootstack, otherwise you can do almost everything in that thread except use a TWRP for Nougat instead). I haven't tried this, but if you have stock recovery, try downgrading to Nougat B19 by using an official SD card update and using apply update from SD card in stock recovery. Haven't found an official SD card update for you but I've only done a little bit of searching.
edit: ive only found B19 Nougat full image , but here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ!tNsQhD5Y
download A2017U-7.1.1-B19-Full-326200B1901A2017UV1.1.0B19.zip and extract it and put update.zip in your sd card. boot into stock recovery and use apply update from sd card and select it. hopefully it works and it will downgrade
Click to expand...
Click to collapse
Thank you so much for responding.
So I finally went out and bought an sd card yesterday to try this and I am having no luck.
I tried unzipping the file, but it just creates a duplicate zip file so I simply tried installing the whole package.
Wether I try and install via sd card or via sideload/adb I get the same "installation aborted" message.
This is so frustrating. All I want is to root again! I'm trying to get this phone to last me as long as I can before replacing it.
Doing this all on a Mac, fyi. Not sure if that changes things. Since we're not using EDL or Axon7toolkit I assumed it doesn't matter, but there is a lot that I don't know.
Thanks for any help that you're able to provide!
alajoy said:
Thank you so much for responding.
So I finally went out and bought an sd card yesterday to try this and I am having no luck.
I tried unzipping the file, but it just creates a duplicate zip file so I simply tried installing the whole package.
Wether I try and install via sd card or via sideload/adb I get the same "installation aborted" message.
This is so frustrating. All I want is to root again! I'm trying to get this phone to last me as long as I can before replacing it.
Doing this all on a Mac, fyi. Not sure if that changes things. Since we're not using EDL or Axon7toolkit I assumed it doesn't matter, but there is a lot that I don't know.
Thanks for any help that you're able to provide!
Click to expand...
Click to collapse
If it's saying that error then it's probably not letting you downgrade.
Also this might be slightly more difficult since you're in a Mac. Can you get access to a windows machine at all? This is why I hate macs
Teet1 said:
If it's saying that error then it's probably not letting you downgrade.
Also this might be slightly more difficult since you're in a Mac. Can you get access to a windows machine at all? This is why I hate macs
Click to expand...
Click to collapse
So what would be the reason that it wouldn't let me downgrade?
I've always used a mac and always managed to find an answer. Sure, toolkits don't work, but using fastboot and adb and doing it that way always has. Now suddenly no fastboot and I'm screwed... I don't really have access to a windows pc.
I just find it hard to believe that it's simply not possible on a mac.
alajoy said:
So what would be the reason that it wouldn't let me downgrade?
I've always used a mac and always managed to find an answer. Sure, toolkits don't work, but using fastboot and adb and doing it that way always has. Now suddenly no fastboot and I'm screwed... I don't really have access to a windows pc.
I just find it hard to believe that it's simply not possible on a mac.
Click to expand...
Click to collapse
Yeah fastboot screen was removed in newer versions. But that's at a software level of the phone. On your computer, the adb and fastboot commands are universal. It's usable on Mac, Linux and windows. The tools used for the phone like miflash or axon7tool are made for windows though and you kinda need those to fix bricked phones. There's a way to force push the twrp image into the recovery partition via adb but I don't know what the name of the recovery partition is
@alajoy: You can give yourself access to a fake Windows on your Mac. It's called a virtual machine. VirtualBox is one free software that can do this. Pretty easy to use, you install a virtualized Windows that you can boot into. Then you can run all Windows-based tools out there. It's also easy to share a USB port with the VM. Then flashing tools can access it. I run Linux as my main OS on a Sager gaming laptop, this is how I flash my A7 and Samsung phones. It just works, and reliably. I do also have a real Windows 10 installed on a partition on the same PC, but that is only for gaming and I never, ever allow it to connect to the Internet.
@Teet1: The literal name of the recovery partition is exactly that, recovery. And that is what most Android devices call it, regardless of manufacturer. It doesn't matter whether it is TWRP or ZTE stock recovery, the name is the same. It can be accessed via the paths:
/dev/block/platform/soc/624000.ufshc/by-name/recovery
/dev/block/bootdevice/by-name/recovery
/dev/block/sde14
On other devices the path may be different (but the 2nd example above will work for most), but the name is usually the same.
AnonVendetta said:
@alajoy: You can give yourself access to a fake Windows on your Mac. It's called a virtual machine. VirtualBox is one free software that can do this. Pretty easy to use, you install a virtualized Windows that you can boot into. Then you can run all Windows-based tools out there. It's also easy to share a USB port with the VM. Then flashing tools can access it. I run Linux as my main OS on a Sager gaming laptop, this is how I flash my A7 and Samsung phones. It just works, and reliably. I do also have a real Windows 10 installed on a partition on the same PC, but that is only for gaming and I never, ever allow it to connect to the Internet.
@Teet1: The literal name of the recovery partition is exactly that, recovery. And that is what most Android devices call it, regardless of manufacturer. It doesn't matter whether it is TWRP or ZTE stock recovery, the name is the same. It can be accessed via the paths:
/dev/block/platform/soc/624000.ufshc/by-name/recovery
/dev/block/bootdevice/by-name/recovery
/dev/block/sde14
On other devices the path may be different (but the 2nd example above will work for most), but the name is usually the same.
Click to expand...
Click to collapse
By name i meant the path, are you sure that's the path for our device? I tried that once and it was not that. Either way he is able to do it
@Teet1: Yeah, I'm sure, but not on all 3 paths. /dev/sde14 may be correct or not, depending on firmware/boot stack that is installed (or the presence of a vendor partition, which might change the paths). But the other 2 should be as I listed.
Just open a root file manager and see for yourself. I use Total Commander, which also shows symbolic links (the one with "bootdevice" in the path is really just a symlink to 624000.ufshc). Getting the recovery path from the example with "bootdevice" in the name should also work on almost any device running Android, and will generally point to the recovery partition. You can see the paths in TWRP too, but TWRP doesn't show symlink (but you should be able to see them if you use the right commands in any terminal, like TWRP's terminal).