Related
Good day!
I'm on Win 7 64 bit and did all the procedures here, ran zadig, etc., before I went to download mode and ran Heimdall....
However, after I ran Heimdall and chosen the files the "Start" button on Heimdall is still grayed out so I cannot start the flashing process...
Any help will be highly appreciated.
***Added: have reseached and was even able to flash using odin on my TAB... I need to bring back my TAB to its original DXKM3 firmware and do not have the firmware to use for odin, that's why I'm trying to use heimdall...
***Also tried it on my laptop with the same results...
Lhon0901 said:
Good day!
I'm on Win 7 64 bit and did all the procedures here, ran zadig, etc., before I went to download mode and ran Heimdall....
However, after I ran Heimdall and chosen the files the "Start" button on Heimdall is still grayed out so I cannot start the flashing process...
Any help will be highly appreciated.
***Added: have reseached and was even able to flash using odin on my TAB... I need to bring back my TAB to its original DXKM3 firmware and do not have the firmware to use for odin, that's why I'm trying to use heimdall...
***Also tried it on my laptop with the same results...
Click to expand...
Click to collapse
Uncheck the partition box. Whenever it's grayed out, it means that for one of your options you haven't met the pre-reqs. For example partition requires a PBL, SBL and a recovery file I believe. Error -12 after clicking start refers to a driver issue.
Lets see if I can explain this how I think you're stating it....
Odin and Heimdall are flashing programs. They're only purpose is to write data to your phone.
Unlike, say, the HD2, which has cLK and Magldr for bootloaders and requires the ROM to be written for that bootloader, there are not separate versions for Odin and Heimdall.
It's only a matter of knowing what files need to go where and in which program.
Odin and Heimdall do the exact same thing, only Odin was a leaked software and Heimdall was written specifically for Galaxy S devices.
Hope this helps
btyork said:
Lets see if I can explain this how I think you're stating it....
Odin and Heimdall are flashing programs. They're only purpose is to write data to your phone.
Unlike, say, the HD2, which has cLK and Magldr for bootloaders and requires the ROM to be written for that bootloader, there are not separate versions for Odin and Heimdall.
It's only a matter of knowing what files need to go where and in which program.
Odin and Heimdall do the exact same thing, only Odin was a leaked software and Heimdall was written specifically for Galaxy S devices.
Hope this helps
Click to expand...
Click to collapse
Okay, I'll try the partition part and see if it works, but I beleive it's not checked as I put no file in it... As for the second post, yes, I have found the firmware I need but it's extracted and not in tar form... That's why I need heimdall...
Maybe if somebody can point me on how to compile it to TAR again I'll just use odin...
***Added: I got my hands on a DXKM3 firmware that came with my phone here. Now if someone can help me put those files again in the TAR format I would be very glad... Getting heimdall to work would, too...
Thanks for the replies!!!
You're right!!! I failed to notice that factory.rfs is not yet extracted, and "Start" magically became selectable!!!
I feel kinda stupid... T_T
Was able to flash now... Thanks for the help guys!!!
Hello everybody,
I've been following some posts around the forum for some time now.
So I decided to flash my Samsung Galaxy S + with the newest stock firmware.
I first tried Odin, but that was no succes because VirtualBox couldn't handle it and just crashed when it started to upload the roms into my phone.
So it was bricked first, but got it back up and running.
I'm using linux as my OS, so of course I found Heimdall.
This seemed a nice tool, but I found out that the package format needs to be else then how the stock roms are delivered.
At last I tried to flas using the dd method.
I did the command dd if=...img of=dev/block/mmcblk0p.. bs=4096 for all partition images.
I managed to start the flashed roms. Only I found out that after installing some apps and after a few reboots the system starts to get faulty.
All of a sudden Play Store doesn't install apps anymore "Package Invalid" error, and for some reason also after each reboot more apps start to dissappear (get replaced by sd-card icon but unable to open or reïnstall).
Also I did a factory reset after dd'd the images into my phone, cause that's what everybody recommends.
The roms I've tried so far were XXKQB and XXKP1, both with the same issues.
The original firmware which came with my phone is: XXKPG.
Hopefully somebody can point me in the right direction in getting a newer rom onto my pda.
Greetings PsychoGame
I suggest you use a PC, im sure you will find one somewhere, friend/neighbour/relative. Then use Odin to flash.
Odin firmwares
Sammobile.com You should find I9001 firmware here
http://forum.xda-developers.com/showthread.php?t=1102881 Not sure if compatible with I9001
Or if your persistent have you tried here. **Check if compatible** If its an older firmware, connect to Kies and it should update to the latest.
JUST NOTICED THE I9001 CHECK THAT THE FIRMWARE IS COMPATIBLE
I agree with Talon, use ODIN on a windows-based machine... In any case you can always install windows on a different partition, but it's not worth it. For me the whole flashing process only lasted for 4 minutes, so just grab a PC somewhere and install it...
I also recommend KQE insted of KQB as the wifi is fixed
Hi all!
So I felt over this easy root guide, but the article didn't say anything about the correct version and so on. I managed to root the phone but got the loop reboot. after that i tried with some kind of pit file. After some research i figuired out that I had done all wrong. After that i manged to install WCM but thats not what i really need now!
My problem now is that i cant enter my phone at all. I have tried to use heimdall, but I can't install the driver that needs to be used for my device. I can still enter the download mode, but I cant find all the files to unbrick it?
So far as i remember, the latest firmware and version of the phone was 2.3.6 and XWJW8.(Thats weird because im from Denmark, and XWJW8 is for Australia?)
I was hoping that someone could help me find all the files: pit file, PDA, Phone and CSC because everytime i find some stock files, its only the PDA file? or Am I wrong?
I use Odin 1.85 and I just want my phone to work again, so I can root it!
I hope there is a friendly soul out there who can help me Its my first time Im trying to trying all this stuff with a android phone.
Thanks in advance!
Edit:
I have just tried to download this: I9000XWJWB_I9000NEEJW2_NEE.zip and tried to install it, but my phone reboots everytime. Can it has something to be that I have tried to use a PIT file before i found this stock? I can turn it on now and it loads with the S logo, but it just restarts after it has loaded
You need JVU it has the boot loaders you need. Use PIT 512. Use Odin with it.
JVU: http://www.google.com/m?hl=en-GB&source=android-browser-type&q=I9000XXJVU_I9000OXAJVU_OXA.zip
and after here is kernel with root and cwm. Out into PDA on Odin no repartition: http://download.chainfire.eu/132/CF-Root/SGS/
Sent from my GT-I9000 using Xparent Skyblue Tapatalk 2
Thanks man!
But i have a new problem. The phone can't enter the internet. I can only connect via Wifi I wanted to root because I wanted to use my 3G network abd
Nevermind! Got it working! I added a APN from my carriers homepage, with setup and help!
Hi everyone,
So I have a I9305, the factory ROM is not booting, but I do have the Samsung flashtool working, and I also have TWRP installed.
I am trying to flash the factory ROM back to the phone before I install Lineage OS.
I have tried using Odin3 to flash this, but it keep asking for the pit file, when I allow Odin to find the pit file, it then reboots the phone, after this Odin no longer sees the phone until I restart the app, thus loosing the pit file. :-S (I am running this on Linux)
So my question is, how can I flash the factory ROM back to the phone?
Any help appreciated
I managed to find a pit file online, but still cant get Jodin to flash the ROM. What is the best way to flash this factory ROM, can it even be done?
If it cant, then what can I do to get this phone up and running again.
I have read through many articles online stating how this should be done for this phone, but the methods do not work.
Hi, I need some help flashing my device. Somehow, my device got stuck in a boot loop last night, and I've been having trouble getting it to work again. I think my phone may have reset during an update while in my pocket as I was laying down on the couch last night.
I found my device firmware on sammobile according to the specs listed below. I've downloaded Odin 3.14.4 and have flashed my phone successfully 3 or 4 times at this point, but when it restarts post-flash, it keeps booting into download mode. I can't seem to get it to boot into recovery mode or just turn it off at all anymore. No matter what, it boots straight into download mode.
Does anyone know of a way that I can force it into recovery mode so that I can try restarting it normally? This is my first time flashing a phone, so I have little experience here though I am competent with technology and willing to try further tricks to get it working.
I'm just looking for recommendations and hoping that my phone isn't bricked. I've only owned it for 3 months at this point, so I'm very disappointed.
Thanks in advance for the help, and I'm happy to provide any more information if it helps you come up with any potential solutions.
Specs
Phone: Samsung 21 Ultra
Model: SM-G998U1
PDA: G998U1UES5CVCB
Carrier: XAA
Text on download mode screen:
<!>
partition recovery
Reason avb.slot_verify.c:276: ERROR: recovery: Hash of data does not match digest in descriptor. [2nd]
Calculated Hash of (recovery) : 9C3B9F195F, (VEMETA) : 1C38BF9F7A
Samsung recovery, G998U1UES5CVCB, 50338466R
VBMETA G998U1UES5CVCB, 50341365R
Do you have TWRP installed? Try flushing it. You can also follow Dr. Ketan ROM installation guide, it's very straightforward.
shaharofir said:
Do you have TWRP installed? Try flushing it. You can also follow Dr. Ketan ROM installation guide, it's very straightforward.
Click to expand...
Click to collapse
I don't. I was looking at that post earlier and noticed that it mentioned the G998B/N model. Mine is the G998U1, so I was worried that it wouldn't work or cause more problems. I couldn't find any versions of TWRP that matched my specific model.
your bootloader version is above v1. cannot be unlocked. you need to flash a samsung rom. try redownloading it if you can't boot. and twrp probably won't work either.
you're saying that if you hold the vol up key and power button when the device is off that it won't reboot into recovery at all?
ffuser1 said:
your bootloader version is above v1. cannot be unlocked. you need to flash a samsung rom. try redownloading it if you can't boot. and twrp probably won't work either.
you're saying that if you hold the vol up key and power button when the device is off that it won't reboot into recovery at all?
Click to expand...
Click to collapse
I was actually able to get it to boot into recovery mode this morning. The download mode timed out and the phone shut off which allowed me to finally get into it. I tried redownloading the same rom I got from sammbolie again a few mins ago but still no luck.
Try another firmware with the same BL revision, CVC9 for example
dipotis said:
Hi, I need some help flashing my device. Somehow, my device got stuck in a boot loop last night, and I've been having trouble getting it to work again. I think my phone may have reset during an update while in my pocket as I was laying down on the couch last night.
I found my device firmware on sammobile according to the specs listed below. I've downloaded Odin 3.14.4 and have flashed my phone successfully 3 or 4 times at this point, but when it restarts post-flash, it keeps booting into download mode. I can't seem to get it to boot into recovery mode or just turn it off at all anymore. No matter what, it boots straight into download mode.
Does anyone know of a way that I can force it into recovery mode so that I can try restarting it normally? This is my first time flashing a phone, so I have little experience here though I am competent with technology and willing to try further tricks to get it working.
I'm just looking for recommendations and hoping that my phone isn't bricked. I've only owned it for 3 months at this point, so I'm very disappointed.
Thanks in advance for the help, and I'm happy to provide any more information if it helps you come up with any potential solutions.
Specs
Phone: Samsung 21 Ultra
Model: SM-G998U1
PDA: G998U1UES5CVCB
Carrier: XAA
Text on download mode screen:
<!>
partition recovery
Reason avb.slot_verify.c:276: ERROR: recovery: Hash of data does not match digest in descriptor. [2nd]
Calculated Hash of (recovery) : 9C3B9F195F, (VEMETA) : 1C38BF9F7A
Samsung recovery, G998U1UES5CVCB, 50338466R
VBMETA G998U1UES5CVCB, 50341365R
Click to expand...
Click to collapse
Was your phone carrier branded originally? And you're flashing the u1 firmware so you won't have bloat? Or is it originally an unlocked model? I ask because if it was originally carrier branded and you used the Odin version from the SamMobile site then that may be the reason. U need to use the modded version of Odin that's floating around somewhere. If you need it I can upload it to my drive and let you download that version. I literally just flashed VCB last night and everything worked just fine.
JG96EVO said:
Was your phone carrier branded originally? And you're flashing the u1 firmware so you won't have bloat? Or is it originally an unlocked model? I ask because if it was originally carrier branded and you used the Odin version from the SamMobile site then that may be the reason. U need to use the modded version of Odin that's floating around somewhere. If you need it I can upload it to my drive and let you download that version. I literally just flashed VCB last night and everything worked just fine.
Click to expand...
Click to collapse
No, I bought my phone directly from Samsung, and I bought the unlocked model. I chose the rom from sammobile that looked to be exactly what my phone originally had on it based on the model and PDA/carrier info I found when looking through the recovery logs on the phone when the issue first occurred, before flashing anything onto it. If you think the modded Odin might work, I'd be willing to give it a shot.
I can't tell you the exact differences, but I would flash with the patched odin. it's on xda if you search for it.
No luck so far. I've downloaded the patched Odin software and have tried flashing my device numerous times with the same result. I also tried tried flashing firmware that I found on Frija instead of the firmware I originall downloaded from sammobile to see if anything would be different, and that didn't seem to make a difference.
My best guess (could be wrong) is that it doesn't like the bootloader tied to the firmware I've tried to flash onto the device. I've spent a good while searching firmware that uses the version of the bootloader it wants, but I can't find it anywhere. At this point, I'm all out of ideas, but I appreciate everyone's responses and advice.
So this is what you are saying: You're using patched odin (https://forum.xda-developers.com/attachments/odin3-v3-14-1_3b_patched-zip.5158507/) to flash an official U1 Samsung rom (https://samfw.com/firmware/SM-G998U1/XAA/G998U1UES5CVCB for example) in the AP slot, all other slots are empty, without any odin errors during flash, and are then unable to boot, with partition errors seen in download mode? This is very unusual... flashing in download mode overwrites partitions, including recovery. I would assume if there are no odin errors, then the rom file is not corrupt and the sd card is not damaged. I don't know much about flashing through odin with a locked bootloader, maybe unpatched odin with the above instructions is worth a shot. I'm out of ideas aside from the sd card being damaged or trying unpatched odin if the above instructions with patched odin are resulting in recovery partition errors. I don't think you can access adb in download mode either.
You can extract the CSC file using 7zip. In there you will find the PIT file and you can try flashing it with repartition selected and inserting the PIT file in developers section of Odin.
ffuser1 said:
So this is what you are saying: You're using patched odin (https://forum.xda-developers.com/attachments/odin3-v3-14-1_3b_patched-zip.5158507/) to flash an official U1 Samsung rom (https://samfw.com/firmware/SM-G998U1/XAA/G998U1UES5CVCB for example) in the AP slot, all other slots are empty, without any odin errors during flash, and are then unable to boot, with partition errors seen in download mode? This is very unusual... flashing in download mode overwrites partitions, including recovery. I would assume if there are no odin errors, then the rom file is not corrupt and the sd card is not damaged. I don't know much about flashing through odin with a locked bootloader, maybe unpatched odin with the above instructions is worth a shot. I'm out of ideas aside from the sd card being damaged or trying unpatched odin if the above instructions with patched odin are resulting in recovery partition errors. I don't think you can access adb in download mode either.
Click to expand...
Click to collapse
Interesting. I did not try it with only the AP slot populated. I thought you needed to always flash with the BL, AP, CP, and CSC.
wait, i messed up. if it has all of those files, flash them. my bad. i was thinking about custom roms - sorry about that.
Hey everyone, just wanted to make a final update.
I ended up bringing my phone into ubreakifix after trying just about everything I could, and they were not able to fix it either. They suggested that it might be a hardware issue and recommended sending it to Samsung for repair. I then sent it over to Samsung, and they confirmed that it was an issue with my motherboard. Samsung replaced my motherboard, and the phone is back in action. Since I only had my phone for about 6 months, it was still under warranty.
I appreciate everyone who took their time to provide me with advice. I hope that this post may help someone experiencing a similar issue to mine in the future.