Ok I have been at this for a few hours. I have upgraded the original Samsung Infuse 4G HD's firmware to gingerbread version something or other but it is a leaked release. Sooo now I'd like to root the phone and put a ROM on it. I downloaded everything I believe I need. (Again I have been at this for awhile) I have SOC and KiesMini as well as full Kies. I have downloaded Titanium Backup, ROM manager, and Superuser to the phone. I went to do a root on SOC and it will get to step 6 and freeze. I've read a few things and gathered that I need to download the drivers for the phone again and restart root process. Well it's been and hour and a half and I can find the damn drivers anywhere on the web. I have repeatedly unplugged and replugged the phone to the computer and let it download the drivers. Kies and KiesMini both are unable to connect to the phone. Scratch that Mini connects but doesn't recognize the device, my guess is that it does not have the original firmware on it, then again I don't see how this would stop the program from recognizing the phone itself seeing as though this was just a firmware update. I'm semi new to this so I wouldn't be surprised if I was wrong.
Please if you have a full guide or step by step instructions or just know where the hell to get the drivers online I'd be very appreciative.
Also if this is the wrong thread section, let me know I'll be happy to move it. I believe I am in the right place though.
Thank you,
If I understand correctly, you already rooted your phone once. Then flashed one of the gingerbread leaks and lost root?
I don't think any of the normal root methods will work. I believe you need to flash a certain kernel to get root back.
Or just use GTGs method to get back to stock. Then normal root methods will work.
if all else fails try superoneclick. thats what i used. and once you get it rooted again flash the MIUI mod to your phone. its a great ROM, i highky recommend it. anyways i agree with the guy above. you may need to find a way to flash a different kernal. let us know how it goes.
Imo, i would flash back to stock with with GTG's unbrick... Either flash community kernel to get red CWM or do SOC to get root, download CWM Rom Manager from market and flash CWM Recovery thru there, make sure to choose "Galaxy s i9000" and NOT the MTD. Do it twice just in case or thrice for sure. You should be able flash any ROM through there or reboot to recovery. This has worked for me multiple times. Good luck.
Here is a link from @misterjunky in the wiki thread for the usb drivers:
http://forum.xda-developers.com/showthread.php?p=18138847
Sent from my SGH-I997 using xda premium
I would suggest using GTG's back to stock package, then re-root, flash the leak (if you still want it), and flash Entropy's DD for root, then flash back to the stock kernel.
Reply if you need any help with this, I'll try to reply during school, if I don't, someone else will, or I will after school.
If you need root with gb I assume you flashed a stock kernel. The board elders have stated you can't root gb through superoneclick. That hack was patched. You need to flash a rooted kernel and then flash back to stock if you want stock or just leave it with custom kernel. Read through the uckj2 (I think) thread in development. Linuxbozo gave perfect instructions.
Sent from my SAMSUNG-SGH-I997 using XDA App
It's good that the information is finally getting passed around. Sorry but root it's now done from the kernel end. It's the last backdoor in but Samsung makes it easy on the user end, only problem now is ya gotta wait for developers to compile kernels with initramfs mods.
what you need is.
1. Drivers, Samsung.com infuse product support section. No need for kies.
2. A kernel that roots, entropy has a good one with wifi and sd compatibility.
3. A flash tool such as Odin or heimdall and dependencies. (visual c++ redistributable package from Microsoft download center for heimdall)
4. (optional) a stock uckj2/4/ kernel if you want hdmi to work.
If you use Odin, the custom kernel that will root you needs to be in a ".tar" archive. You put it in the pda slot. After first boot you will have root and have the option to flash back to a kernel with hdmi. once rooted this can be done with sgs kernel flasher if you can't find the .tar version of the stock kernel, you can extract the zimage from the original Odin package and zip it or .rar it and put it on the sd card to be flashed in kernel flasher.
If you use heimdall (my personal preference) you will extract the zimage out of what ever archive it is in. it may be .zip .tar .rar it can even be cwm flashable. You open the tab labeled "flash" load the infuse.pit that gtg made (found with the unbrick package) then click the "add" button select "kernel" for the partition and then browse for the zimage for the root kernel.
Same process to go back to the hdmi kernel for heimdall. Or you can use kernel flasher like I explained above.
No need to go back to stock or wipe data for kernel flashing. That's just overkill and a waist of time.
Dani897 said:
It's good that the information is finally getting passed around. Sorry but root it's now done from the kernel end. It's the last backdoor in but Samsung makes it easy on the user end, only problem now is ya gotta wait for developers to compile kernels with initramfs mods.
what you need is.
1. Drivers, Samsung.com infuse product support section. No need for kies.
2. A kernel that roots, entropy has a good one with wifi and sd compatibility.
3. A flash tool such as Odin or heimdall and dependencies. (visual c++ redistributable package from Microsoft download center for heimdall)
4. (optional) a stock uckj2/4/ kernel if you want hdmi to work.
If you use Odin, the custom kernel that will root you needs to be in a ".tar" archive. You put it in the pda slot. After first boot you will have root and have the option to flash back to a kernel with hdmi. once rooted this can be done with sgs kernel flasher if you can't find the .tar version of the stock kernel, you can extract the zimage from the original Odin package and zip it or .rar it and put it on the sd card to be flashed in kernel flasher.
If you use heimdall (my personal preference) you will extract the zimage out of what ever archive it is in. it may be .zip .tar .rar it can even be cwm flashable. You open the tab labeled "flash" load the infuse.pit that gtg made (found with the unbrick package) then click the "add" button select "kernel" for the partition and then browse for the zimage for the root kernel.
Same process to go back to the hdmi kernel for heimdall. Or you can use kernel flasher like I explained above.
No need to go back to stock or wipe data for kernel flashing. That's just overkill and a waist of time.
Click to expand...
Click to collapse
Awesome instructions but I think it's worth mentioning (and maybe that's why you DIDN'T mention it actually) that you need a pit to flash anything in the front end but unless you WANT to repartition, you should make sure that check box is UNCHECKED after you select the pit.
jvanlew said:
Awesome instructions but I think it's worth mentioning (and maybe that's why you DIDN'T mention it actually) that you need a pit to flash anything in the front end but unless you WANT to repartition, you should make sure that check box is UNCHECKED after you select the pit.
Click to expand...
Click to collapse
Yeah don't repartition!. It's potential for disaster, better left for situations whet you have all the partitions to flash and the phone won't boot after trying without repartition. The pit is just for partition mapping in the new front end. I guess it's designed to work with devices that may have different partitioning as well
jvanlew said:
.... that you need a pit to flash anything in the front end....
Click to expand...
Click to collapse
Talking about heimdall? I think you can use an older version like 1.1 to get around this?
Sent from my SAMSUNG-SGH-I997 using XDA App
rxnelson said:
Talking about heimdall? I think you can use an older version like 1.1 to get around this?
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
This is true. 1.1 works great and doesn't need a pit file. It is also easier if you never used it before. It kinda explains itself.
Dani897 said:
It's good that the information is finally getting passed around. Sorry but root it's now done from the kernel end. It's the last backdoor in but Samsung makes it easy on the user end, only problem now is ya gotta wait for developers to compile kernels with initramfs mods.
what you need is.
1. Drivers, Samsung.com infuse product support section. No need for kies.
2. A kernel that roots, entropy has a good one with wifi and sd compatibility.
3. A flash tool such as Odin or heimdall and dependencies. (visual c++ redistributable package from Microsoft download center for heimdall)
4. (optional) a stock uckj2/4/ kernel if you want hdmi to work.
If you use Odin, the custom kernel that will root you needs to be in a ".tar" archive. You put it in the pda slot. After first boot you will have root and have the option to flash back to a kernel with hdmi. once rooted this can be done with sgs kernel flasher if you can't find the .tar version of the stock kernel, you can extract the zimage from the original Odin package and zip it or .rar it and put it on the sd card to be flashed in kernel flasher.
If you use heimdall (my personal preference) you will extract the zimage out of what ever archive it is in. it may be .zip .tar .rar it can even be cwm flashable. You open the tab labeled "flash" load the infuse.pit that gtg made (found with the unbrick package) then click the "add" button select "kernel" for the partition and then browse for the zimage for the root kernel.
Same process to go back to the hdmi kernel for heimdall. Or you can use kernel flasher like I explained above.
No need to go back to stock or wipe data for kernel flashing. That's just overkill and a waist of time.
Click to expand...
Click to collapse
Sorry I haven't responded until now, I've been incredibly busy. Anywho, so I went ahead and flashed back to stock. So now it is exactly how it should be when I bought it. I run SOC and it gets to running pneuter and stops. I've waited an hour on it and it won't continue. Any suggestions?
Hi
I am using unrooted Infuse phone. Recently i have updated it to official gingerbread UCKL2 through samsung Kies mini.
I want to try ZEUS ROM on samsung infuse. Please let me know how to start in detail as I am new on Linux.
Thanks
Nits
ndhanta said:
Hi
I am using unrooted Infuse phone. Recently i have updated it to official gingerbread UCKL2 through samsung Kies mini.
I want to try ZEUS ROM on samsung infuse. Please let me know how to start in detail as I am new on Linux.
Thanks
Nits
Click to expand...
Click to collapse
That's the ROM i'm trying to get on mine as well, I just cant get the damn phone to root.
I posted a reply in the other thread
My phone is soft bricked and I have to flash a tar file via Odin to fix it there is a stock gingerbread one and an ics one can I use both? Because I want to use the latest one and save the time of updating
Thunder guy said:
My phone is soft bricked and I have to flash a tar file via Odin to fix it there is a stock gingerbread one and an ics one can I use both? Because I want to use the latest one and save the time of updating
Click to expand...
Click to collapse
It should unbrick depending on what you are flashing. For eg: If you have stock ROM in .tar file you are safe to flash it via Odin following the instructions.
Not sure which your phone is, but if you have GB or ICS stock ROM images, then I guess you can flash any one of them depending upon your choice.
it depends
sankapax said:
it depends
Click to expand...
Click to collapse
I am using a galaxy note i717 and I flashed a rom for the galaxy note 2..... Ya I know there's ics stock tar gb stock tar and a jelly bean one
I have extracted the .zip from the newest AT&T RUU. I was hoping someone could make a TWRP flashable ZIP out of these. some people would like to run the stock rom and be on the latest available.
I have looked and i dont know where to look to find info on how to do the work. so I was hoping someone would be able to stepup and help out.
here is the extracted rom.zip from the RUU. There is 2 so i grabbed them both. the smaller one seems to have only the HBoot.img but feel free to look as well.
http://www.androidfilehost.com/?fid=23501681358541398ROM.zip 780.1mb
http://www.androidfilehost.com/?fid=23501681358541397Rom2.zip 1.MB
I want to flash .zip Rom with odin v3.07
I've downloaded nolekat rom for my samsung tab 3 neo I was just trying to root it from odin and somehow it stuck at boot logo now. So I have downloaded rom and it is in .zip extension can I change it's name to .tar or .tar.md5
or is my thinking is wrong?
You have to download firmware, you can't flash custom roms with odin only stick firmware, try Sammobile
Sent from my SM-G386T1 using Tapatalk
You use a custom recovery such as twrp or CWM to flash roms. I suggest doing some reading of the How to's and tutorial threads in your device section to learn more.....before you accidentally destroy your device. Odin is for official firmware, as said above. Be very careful with what you flash and how, or your device can become a paperweight quickly.
Read up first, then do. :good:
close thread
Thanks for replying to my post I fixed problem and requesting to close this thread. Thanks
Hi Guys,
Does anyone know where I can find/ download the stock w8 flashable modem?
I'm using RENOVATE 1.0 ROM and it's very nice... just my cell signal is poor compared to stock.
Thanks for your time!
http://samsung-updates.com/device/?id=SM-G935W8
Thanks for a point in the right direction
I'm assuming once I open the .zip it will have the individual modem file to flash via Odin?
No you will have the whole rom you'll have to flash, honestly i dont believe that rom flashed a new modem, they really shouldn't.
peachpuff said:
No you will have the whole rom you'll have to flash, honestly i dont believe that rom flashed a new modem, they really shouldn't.
Click to expand...
Click to collapse
that's too bad- I already have my stock file backed up with twrp... no need to reflash whole firmware.
I thought the recovery used to back up modem file as well? or am I mistaken?
It's been so long since I've played with this type of thing...
I think you have to specify to backup the modem.
Keep this updated if you do get a hold of a flashable modem. I'm in the spot and would like to reflash the stock modem.