I've tried it with Odin3 V1.82 / V1.83
CWM Recovery 4.0.0.8 would not flash. I tried using another CWM that I found , but I can't boot into CWM.
Before flashing CWM with ODIN am I supposed to load a rooted kernel to take the place of something like an adb root?
I'm a bit lost on how to go about. My goal was to just flash a gummy rom.
heynicebits said:
I've tried it with Odin3 V1.82 / V1.83
CWM Recovery 4.0.0.8 would not flash. I tried using another CWM that I found , but I can't boot into CWM.
Before flashing CWM with ODIN am I supposed to load a rooted kernel to take the place of something like an adb root?
I'm a bit lost on how to go about. My goal was to just flash a gummy rom.
Click to expand...
Click to collapse
I'm not understanding how you "got lost" on how to go about it. Also, your issues are very vague. Instead of saying "I can't flash CWR," you should say, "Having trouble flashing CWR, here's the error I get." I'm not trying to be mean here but you have to give people something to work with in order to get help. Just saying you can't flash something doesn't give anyone any insight on how to fix the issue because we don't know what the issue is.
This post here: http://forum.xda-developers.com/showthread.php?t=1160580
This post explains everything you need to know, and it is pretty detailed on what you need and how exactly you need to do it. If you still have any issues, or if this is the method you were using to begin with, then post back here and tell me what your exact issue is (ie: COM port changes when trying to flash, process is stuck at "waiting for device....") and I will try to help you to the best of my abilities.
I think I figured out what I did wrong. I was able to flash my wife's fascinate fine, but not everything was the exact same for the charge.
For some reason Odin 1.82 worked and 1.83 did not
CWR Mod for ALL file worked with Odin, but I was unable to access it. The link in previous post did Flash and worked great.
Thanks for helping out a newbie.
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
After a failed ROM flash, I am now unable to flash any ROM onto my Galaxy s 4G except for PDA_UXKG3_rooted_no_bootloaders_v2.tar.md5. However, this ROM won't do since I have no service when I turn on my phone. I assume this ROM is for another carrier or a different type of Galaxy.
I can get into download mode and recovery mode.
I have tried many different ROMS (rooted and stocked, got them from http://forum.xda-developers.com/wik..._Rooted.2C_Deodexed.2C_Busyboxed_ROM_packages) for my phone and none of them will finish the flash process, Odin3 always fails at modem.bin. I have tried numerous times to reset to factory defaults from the Recovery Mode but the phone says it can't access some ATT folder.
I am using Odin3 1.85 and have a Samsung Galaxy s 4g sgh-i997.
Anyone have any ideas on how to get my phone working again? At this point I just want any ROM that gives me service to work on there. I
Thanks.
slipnslider said:
After a failed ROM flash, I am now unable to flash any ROM onto my Galaxy s 4G except for PDA_UXKG3_rooted_no_bootloaders_v2.tar.md5. However, this ROM won't do since I have no service when I turn on my phone. I assume this ROM is for another carrier or a different type of Galaxy.
I can get into download mode and recovery mode.
I have tried many different ROMS (rooted and stocked, got them from http://forum.xda-developers.com/wik..._Rooted.2C_Deodexed.2C_Busyboxed_ROM_packages) for my phone and none of them will finish the flash process, Odin3 always fails at modem.bin. I have tried numerous times to reset to factory defaults from the Recovery Mode but the phone says it can't access some ATT folder.
I am using Odin3 1.85 and have a Samsung Galaxy s 4g sgh-i997.
Anyone have any ideas on how to get my phone working again? At this point I just want any ROM that gives me service to work on there. I
Thanks.
Click to expand...
Click to collapse
that would be the rom for a rogers infuse 4g galaxy s i997r
if you have an att infuse 4g i997 it will work with bugs (incompatible bootloaders cause rainbow garbage on boot and in camera and video previews) both phones use identical frequencies and work on each others carriers if the apn settings are correct. the problem is that it is failing at the modem.bin flash
check the baseband version in about phone. if it says baseband unknown this shows that the modem.bin is broken!
it is possible that there is a bad block or something on that partition or that the file is corrupt or that it is just the simple fact that odin and windows are both complete garbage, and the samsung drivers are even worse.
what i would do is install a rooting kernel with cwm (entropy daily driver or hellraiser are good but i dont know if they are in .tar format) and install a new modem from the modems thread through cwm (any should work but uxkg3 is the proper one). if you are avoiding rooting then try extracting the modem.bin from a cwm package and use heimdall to flash it, if you know how to make a .tar then you can use odin to flash only the modem.bin.
if you still get a baseband unknown error then odin flashing with the pit file and repartition selected "may" help but it will wipe your data and also risks bricking.
Thanks. I followed this tutorial droidangel.blogspot.com/2011/07/guide-how-to-unbrick-and-fix-your.html to a T and it worked. I guessed I need the PIT, PHONE (modem) and PDA files. I was only using the PDA file before.
Sorry the link is messed up, I'm new and can't post links yet. Just add www before droidangel and it will work.
Hey everyone, so I have from what I researched here is a "soft" bricked phone as my recovery mode (TWRP) and download mode works fine but no boot.
First let me say this is the Canadian version of the Note 5 SM-N920W8. I posted here because there is no forum for that version everything seems to be the same and posted under 920T version.
HISTORY OF THE PHONE:
It was a while ago that I rooted but let me describe to the best of my memory how my note 5 ended up in the state that it is in. So stock was lollipop 5.1.1. I flashed the skyhigh kernel which gave root access but had random reeboot issues which led me to flashing TWRP recovery so I could flash boot.img as an image file which did take away the random reeboot problem and removed that red error on startup "kernel is not SEANDROID enforcing". Life was good at this point! Everything worked great woth no issues. I greenified everything and underclocked the cpu with system tuner and used system app removed to manually all the bloatware as I didnt want to start using custom roms I stuck with the stock firmware. Part of the reason that I didnt want to use custom roms is because I started reading up on xposed framework, so I decided to flash it and give it a try. I read the xposed framework thread followed the download link to my version downloaded it and flashed with TWRP. Immediately after this was a bootloop.
TROUBLESHOOTING:
Unfortunately I had no backup in TWRP.. In a panic before researching I started flashing other kernels like arters kernel and I think space x whcih can be used on some note 5s.. which brought back that SEANDROID error message in the bootloop. I flashed the skyhigh kernel but flashing the boot.img didn't get rid of that error message again.
A friend of mine at work recommended that I just wipe everything and flash the stock firmware from sammobile.com with odin since I still have recovery mode then just re root. So I went into TWRP and wiped EVERYTHING. I think there was 4 or 5 boxes in twrp data wipe but I selected all the boxes. Now the phone doesn't even get the Samsung logo on boot or anything but download mode works so I flashed twrp again which loads up. I downloaded my version of the Samsung firmware which was about 1.6gb from sammobile.com. I open odin load the file that I extracted. A tar.md5 file which took longer than normal to load into the AP but I didn't change any settings or anything. Should I have? Because after I hit start it failed. I retried at least 3 times. Does this firmware contain all the AP CP and all the other boxes or do I need to find those separately? Should I just try a custom rom?
Im not sure what to do here I have a completely blank phone but twrp and download mode works so it recoverable right?
I read up on adb sideloader but didn't get too far.. is that worth trying for recovery in this case?
I also read a few threads on here for other samsung versions where they say to flash a PIT file with odin but they all say that it only works specifically for that phone and I couldn't find one for this version of the note 5.
I know the #1 rule here is to research before posting and Ive really made my best attempt to research on here and Google over the last few days but I really need my phone back. Any help is greatly appreciated.
re: phone won't boot
bloewen4 said:
Hey everyone, so I have from what I researched here is a "soft" bricked phone as my recovery mode (TWRP) and download mode works fine but no boot.
First let me say this is the Canadian version of the Note 5 SM-N920W8. I posted here because there is no forum for that version everything seems to be the same and posted under 920T version.
HISTORY OF THE PHONE:
It was a while ago that I rooted but let me describe to the best of my memory how my note 5 ended up in the state that it is in. So stock was lollipop 5.1.1. I flashed the skyhigh kernel which gave root access but had random reeboot issues which led me to flashing TWRP recovery so I could flash boot.img as an image file which did take away the random reeboot problem and removed that red error on startup "kernel is not SEANDROID enforcing". Life was good at this point! Everything worked great woth no issues. I greenified everything and underclocked the cpu with system tuner and used system app removed to manually all the bloatware as I didnt want to start using custom roms I stuck with the stock firmware. Part of the reason that I didnt want to use custom roms is because I started reading up on xposed framework, so I decided to flash it and give it a try. I read the xposed framework thread followed the download link to my version downloaded it and flashed with TWRP. Immediately after this was a bootloop.
TROUBLESHOOTING:
Unfortunately I had no backup in TWRP.. In a panic before researching I started flashing other kernels like arters kernel and I think space x whcih can be used on some note 5s.. which brought back that SEANDROID error message in the bootloop. I flashed the skyhigh kernel but flashing the boot.img didn't get rid of that error message again.
A friend of mine at work recommended that I just wipe everything and flash the stock firmware from sammobile.com with odin since I still have recovery mode then just re root. So I went into TWRP and wiped EVERYTHING. I think there was 4 or 5 boxes in twrp data wipe but I selected all the boxes. Now the phone doesn't even get the Samsung logo on boot or anything but download mode works so I flashed twrp again which loads up. I downloaded my version of the Samsung firmware which was about 1.6gb from sammobile.com. I open odin load the file that I extracted. A tar.md5 file which took longer than normal to load into the AP but I didn't change any settings or anything. Should I have? Because after I hit start it failed. I retried at least 3 times. Does this firmware contain all the AP CP and all the other boxes or do I need to find those separately? Should I just try a custom rom?
Im not sure what to do here I have a completely blank phone but twrp and download mode works so it recoverable right?
I read up on adb sideloader but didn't get too far.. is that worth trying for recovery in this case?
I also read a few threads on here for other samsung versions where they say to flash a PIT file with odin but they all say that it only works specifically for that phone and I couldn't find one for this version of the note 5.
I know the #1 rule here is to research before posting and Ive really made my best attempt to research on here and Google over the last few days but I really need my phone back. Any help is greatly appreciated.
Click to expand...
Click to collapse
If you have either a custom or stock rom installed or the official Samsung firmware installed
then it should be an easy fix, you must have flashed a incompatible kernel or perhaps you
deleted the kerned. (the phone will not boot without a kernel)
You need to find a compatible kernel and flash it using twrp recovery.
Here is a link you may want to try, it's for kernels for the Note 5 only:
http://forum.xda-developers.com/tmobile-galaxy-note5/orig-development
It might even be better if you were to Odin flash a fresh copy of your Note 5 specific
firmware using download mode, that's the surest way to get your phone working again.
Give it a try...
Good luck,
Have a great day!
Good luck!
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
A friend of mine at work recommended that I just wipe everything and flash the stock firmware from sammobile.com with odin since I still have recovery mode then just re root. So I went into TWRP and wiped EVERYTHING. I think there was 4 or 5 boxes in twrp data wipe but I selected all the boxes. Now the phone doesn't even get the Samsung logo on boot or anything but download mode works so I flashed twrp again which loads up. I downloaded my version of the Samsung firmware which was about 1.6gb from sammobile.com. I open odin load the file that I extracted. A tar.md5 file which took longer than normal to load into the AP but I didn't change any settings or anything. Should I have? Because after I hit start it failed. I retried at least 3 times. Does this firmware contain all the AP CP and all the other boxes or do I need to find those separately? Should I just try a custom rom?
Click to expand...
Click to collapse
Unfortunately I had no backup in TWRP.. In a panic before researching I started flashing other kernels like arters kernel and I think space x whcih can be used on some note 5s.. which brought back that SEANDROID error message in the bootloop. I flashed the skyhigh kernel but flashing the boot.img didn't get rid of that error message again
Click to expand...
Click to collapse
re: not sure what you mean
bloewen4 said:
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
Click to expand...
Click to collapse
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
or flashing firmware is the same process in odin. Use the AP slot.
And now I know what messed up your phone... it was as I posted before either
flashing the wrong kernel or the kernel got deleted who knows how.
That's all I can tell you except if you want the link to the official Samsung
N920T firmware here it is:
http://forum.xda-developers.com/tmo...t/rom-android-6-0-marshmallow-note-5-t3250812
The link also guides you thru the odin flashing process and other important things.
Good luck!
re: not sure what you mean
Quote:
Originally Posted by bloewen4
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
Click to expand...
Click to collapse
I was researching some methods of flashing firmware to a completely wiped phone and read somewhere that there is a method to download all the files individually and put them into all the other sections in odin but I guess these tar.md5 files are a package of everything and one file is enough for a completely wiped phone? If all I need to k ow is to download that firmware unzip and flash in AP then awesome So longlong as they both have the same effect.
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
Click to expand...
Click to collapse
Just to clarify the order of this; first download that firmware via that link. 2nd wipe everything in twrp except for recovery so I can go back into twrp and factory reset in twrp? This alone will boot my phone before flashing the firmware? Or do I need to factory reset in twrp then flash that firmware in odin to get a boot? And is this custom firmware do I need to root again after I get boot?
Thanks for the link to that firmware going to be trying this right after work
bloewen4 said:
re: not sure what you mean
Quote:
Originally Posted by bloewen4
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
I was researching some methods of flashing firmware to a completely wiped phone and read somewhere that there is a method to download all the files individually and put them into all the other sections in odin but I guess these tar.md5 files are a package of everything and one file is enough for a completely wiped phone? If all I need to k ow is to download that firmware unzip and flash in AP then awesome So longlong as they both have the same effect.
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
Just to clarify the order of this; first download that firmware via that link. 2nd wipe everything in twrp except for recovery so I can go back into twrp and factory reset in twrp? This alone will boot my phone before flashing the firmware? Or do I need to factory reset in twrp then flash that firmware in odin to get a boot? And is this custom firmware do I need to root again after I get boot?
Thanks for the link to that firmware going to be trying this right after work
Click to expand...
Click to collapse
Wait. You have a W8 variant. Odin won't flash a T variant on your W8 device, I don't believe. You need to download your carrier specific, hopefully 6.0.1 version, of the firmware for your specific carrier version, and flash that in the latest 3.10.7 version of odin.
---------- Post added at 09:21 PM ---------- Previous post was at 09:08 PM ----------
bloewen4 said:
re: not sure what you mean
Quote:
Originally Posted by bloewen4
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
I was researching some methods of flashing firmware to a completely wiped phone and read somewhere that there is a method to download all the files individually and put them into all the other sections in odin but I guess these tar.md5 files are a package of everything and one file is enough for a completely wiped phone? If all I need to k ow is to download that firmware unzip and flash in AP then awesome So longlong as they both have the same effect.
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
Just to clarify the order of this; first download that firmware via that link. 2nd wipe everything in twrp except for recovery so I can go back into twrp and factory reset in twrp? This alone will boot my phone before flashing the firmware? Or do I need to factory reset in twrp then flash that firmware in odin to get a boot? And is this custom firmware do I need to root again after I get boot?
Thanks for the link to that firmware going to be trying this right after work
Click to expand...
Click to collapse
What carrier are you on? Go to sammobile and find out exactly what firmware is the latest for your variant on your carrier, for us T variants it's dpd1, but yours will be different, and sammobile is slow so if you can find a mirror somewhere for the stock firmware do that, download it...should be a tar.md5....if you get an error loading it you can often remove the .md5 from the extension...now first reboot recovery and you only need to wipe art/dalvik cache, system, data, cache, and if you want to internal storage but I normally don't...if you wipe efs and everything else you'll be sorry because only thing that will restore it is a full factory odin firmware flash...which is exactly what we're doing...so wipe those partitions then reboot download mode....launch odin and load your downloaded image into the AP slot. Make sure it's at least 3.10.7 version of Odin...when you connect the usb after rebooting to download mode you should see a green/blue box with COM:x (where x is a com port number on your pc) and it should say added...now flash it and wait until it finishes, it'll reboot maybe even a couple times, but it'll eventually make it to the setup screen- from here you can continue stock or flash twrp in odin then recovery flash a rooted kernel for stock rooted or continue with a custom rom, there's a fix in the note 5 gen section for making t/w8 devices work with call audio on intl roms and there's some stock Deodexed stuff at this point and certainly tekhd's mm rom...so from there the choices are yours...but your device is fine you just NEED to flash the correct stock firmware for your variant and use the latest version of odin with a factory usb cable and latest usb drivers from Samsung on your pc when you do it...you'll find links to all this stuff in most of the guides that are abundantly available...
Wait. You have a W8 variant. Odin won't flash a T variant on your W8 device, I don't believe. You need to download your carrier specific, hopefully 6.0.1 version, of the firmware for your specific carrier version, and flash that in the latest 3.10.7 version of odin.
Click to expand...
Click to collapse
I realize I have a W8 and hes providing the firmware for a T. I rooted with a kernel that was for a T version and everything worked fine. I researched rooting note 5 SM-N920W8 and they said do everything the same for the T version because theyre basically identical and isnt much info on the w8 version. So far Ive had no issues flashing everything designed for the T version on my W8. Actually Ive only tried flashing stock w8 firmware from.sammobile.com and got a fail in odin so now Ill try the version MisterJunkie provided me with for the T version unless considering all this you think I should still try a different firmware all together for the W8?
Misterjunky said:
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
or flashing firmware is the same process in odin. Use the AP slot.
And now I know what messed up your phone... it was as I posted before either
flashing the wrong kernel or the kernel got deleted who knows how.
That's all I can tell you except if you want the link to the official Samsung
N920T firmware here it is:
http://forum.xda-developers.com/tmo...t/rom-android-6-0-marshmallow-note-5-t3250812
The link also guides you thru the odin flashing process and other important things.
Good luck!
Click to expand...
Click to collapse
Bud, that's not the official tmo pd1 firmware, and I'm not sure if the leaked (alright it would likely run) would be the best here...plus he scares me when he says he cleared EVERYTHING cuz I'm thinking back to exactly how much twrp will wipe, but it's a lot so I fear he's going to need some partitions restored that are only going to come from a full pit file mapping...I don't believe official pd1 would flash in odin, nor would I recommend doing so- I would locate the most recently official firmware to ensure all partitions are restored, then if he doesn't have official mm support he can look into the leak, but if he had official for his variant and carrier that's his best bet to ensure 100% fix and give him a solid foundation to start from if he wants to root, rom, mod, etc
Not to discount your advice, I'd just hate to see him in a worse place than he is...which he's not even bricked YET...but he's starts screwing with wiping efs or messaging with csc stuff from different variants and he could back himself into a corner...
What carrier are you on? Go to sammobile and find out exactly what firmware is the latest for your variant on your carrier, for us T variants it's dpd1, but yours will be different, and sammobile is slow so if you can find a mirror somewhere for the stock firmware do that, download it...should be a tar.md5....if you get an error loading it you can often remove the .md5 from the extension...now first reboot recovery and you only need to wipe art/dalvik cache, system, data, cache, and if you want to internal storage but I normally don't...if you wipe efs and everything else you'll be sorry because only thing that will restore it is a full factory odin firmware flash...which is exactly what we're doing...so wipe those partitions then reboot download mode....launch odin and load your downloaded image into the AP slot. Make sure it's at least 3.10.7 version of Odin...when you connect the usb after rebooting to download mode you should see a green/blue box with COM:x (where x is a com port number on your pc) and it should say added...now flash it and wait until it finishes, it'll reboot maybe even a couple times, but it'll eventually make it to the setup screen- from here you can continue stock or flash twrp in odin then recovery flash a rooted kernel for stock rooted or continue with a custom rom, there's a fix in the note 5 gen section for making t/w8 devices work with call audio on intl roms and there's some stock Deodexed stuff at this point and certainly tekhd's mm rom...so from there the choices are yours...but your device is fine you just NEED to flash the correct stock firmware for your variant and use the latest version of odin with a factory usb cable and latest usb drivers from Samsung on your pc when you do it...you'll find links to all this stuff in most of the guides that are abundantly available...
Click to expand...
Click to collapse
My carrier is Rogers. I did goto sammobile.com already and downloaded and flashed what I thought was the current stock firmware for my 920w8, but I flashed without wiping all data as previously stated. Maybe doing this will allow my firmware to flash? Will try when Im home from work. Will also post the link from sammobile.com for the exact firmware I download just to verify ots the right one.
Yeah I literally wiped everything I checked all the boxes and I remember having to manually type y e s to proceed so yeah pretty serious wipe lol.
I have the latest version of odin 3.10.7 and tried installing drivers on my pc said theyre already installed.
When I connect my phone to usb in download mode it says com:4
I thought also that just flashing the stock firmware would be the solution since I get download mode and twrp I just have a blank phone but as I said I did get the stock firmware from sammobile.com and try but it failed. Maybe I grabbed the wrong one but it looked pretty straightforward. Maybe with MM coming out Wednesday for rogers note 5 Im downloading the wrong version.
Im worried like you wrote earlier that I deleted too much with twrp if I needing mapping partitions and PIT files I will need some serious help that stuff is beyond me.
Go to sammobile and find out exactly what firmware is the latest for your variant on your carrier, for us T variants it's dpd1, but yours will be different, and sammobile is slow so if you can find a mirror somewhere for the stock firmware do that, download it...should be a tar.md5....if you get an error loading it you can often remove the .md5 from the extension...now first reboot recovery and you only need to wipe art/dalvik cache, system, data, cache, and if you want to internal storage but I normally don't...if you wipe efs and everything else you'll be sorry because only thing that will restore it is a full factory odin firmware flash...which is exactly what we're doing...so wipe those partitions then reboot download mode....launch odin and load your downloaded image into the AP slot. Make sure it's at least 3.10.7 version of Odin...when you connect the usb after rebooting to download mode you should see a green/blue box with COM:x (where x is a com port number on your pc) and it should say added...now flash it and wait until it finishes, it'll reboot maybe even a couple times, but it'll eventually make it to the setup screen- from here you can continue stock or flash twrp in odin then recovery flash a rooted kernel for stock rooted or continue with a custom rom
Click to expand...
Click to collapse
Goodmorning, as I mentioned I would try this right after work. Heres what I did.. I verified that I had the 3.10.7 version of odin which I do, checked drivers on pc which I have. I re downloaded the firmware from here http://www.sammobile.com/firmwares/database/SM-N920W8/ Its was the Canadian Rogers version 5.1.1 near the bottom as mm isnt out for rogers yet.. Oh and I checked my cable ot connected another device to my PC.. so after all this I went into twrp wiped everything you mentioned. After that I was looking for the factory reset option in twrp but couldn't find anywhere only restore which I have no rom backups made. Do I need this step?
Went into download mode pressed vol up.. opened odin 3.10.7. I did notice a change after wiping. Its now says com:6 instead of com:4 if that means anything.. I loaded the firmware into AP it took a while to load but it did without errors. Flashed and failed If you need I can copy the error message from odin in here tonight.
Do you think I need to remap partitions as you said earlier? Getting PIT files? Im lost here... appreciate any help
Still with a blank phone, any ideas?
Or if anyone could direct me to another thread that might be useful for re mapping partitions?
Have you tried flashing twrp again in Odin?
I hit too many buttons before when wiping. It even erased my recovery.
Once I had recovery again I could Odin flash the official firmware.
Could try Philz recovery as well.
Sent from my SM-N920T using XDA-Developers mobile app
Yeah I did try that heres the link where I got the firmware and yeah twrp is on there.
Goodmorning, as I mentioned I would try this right after work. Heres what I did.. I verified that I had the 3.10.7 version of odin which I do, checked drivers on pc which I have. I re downloaded the firmware from here http://www.sammobile.com/firmwares/database/SM-N920W8/ Its was the Canadian Rogers version 5.1.1 near the bottom as mm isnt out for rogers yet.. Oh and I checked my cable ot connected another device to my PC.. so after all this I went into twrp wiped everything you mentioned. After that I was looking for the factory reset option in twrp but couldn't find anywhere only restore which I have no rom backups made. Do I need this step?
Went into download mode pressed vol up.. opened odin 3.10.7. I did notice a change after wiping. Its now says com:6 instead of com:4 if that means anything.. I loaded the firmware into AP it took a while to load but it did without errors. Flashed and failed If you need I can copy the error message from odin in here tonight.
Click to expand...
Click to collapse
bloewen4 said:
Yeah I did try that heres the link where I got the firmware and yeah twrp is on there.
Click to expand...
Click to collapse
Since you have twrp on the phone.. Tap to create a backup even if there's no system on it so that you can at least make it create the folder.. Try using adb to push a ROM and kernel to the phone so you can use twrp to flash it. If you can get into the phones storage using Windows then just drop a ROM and kernel for your device in the folder and then use twrp to flash.
By the way.. Use the SkyHigh kernel.
Follow the directions to a T!!
http://forum.xda-developers.com/note5/orig-development/kernel-skyhigh-tw-6-0-1-kernel-t3321646
If you can get into the phones storage using Windows then just drop a ROM and kernel for your device in the folder and then use twrp to flash.
Click to expand...
Click to collapse
I did try immediately to connect with Windows to my phone so I could try flashing stock firmware with twrp but its currently not allowing me access to view storage on Windows though it does connect with odin saying com:6.
Since you have twrp on the phone.. Tap to create a backup even if there's no system on it so that you can at least make it create the folder..
Click to expand...
Click to collapse
I will do this as soon as I am home from work. Will this perhaps allow access with Windows and/or adb sideloader?
Try using adb to push a ROM and kernel to the phone so you can use twrp to flash it.
Click to expand...
Click to collapse
I will be researching how to do this. Have you any threads to learn adb? So basically this will allow me to put ROMS or other files into the internal memory?
By the way.. Use the SkyHigh kernel.
Follow the directions to a T!!
http://forum.xda-developers.com/note...ernel-t3321646
Click to expand...
Click to collapse
Is this the right kernel for SM-N920W8?
* SAME kernel for ALL supported variant !!
** If other party cannot hear voice when on speaker phone ** Then read Post #636
SM-N920 C / CD / G / i [ v3.2 ]
SM-N9200_HK [ v3.2 ]
Click to expand...
Click to collapse
Also Marshmellow isnt out officially for SM-N920W8 so Ill need a kernel for lollipop 5.1.1 unless you suggest to wait for marshmellow then try a mm kernel?
Thanks for helping!
How about this adb sideloader does anyone think that will work to load the firmware? If so any good threads to guode me?
What did you end up doing? I have a similar problem except no recovery mode, just download mode for Odin.
bloewen4 said:
Goodmorning, as I mentioned I would try this right after work. Heres what I did.. I verified that I had the 3.10.7 version of odin which I do, checked drivers on pc which I have. I re downloaded the firmware from here http://www.sammobile.com/firmwares/database/SM-N920W8/ Its was the Canadian Rogers version 5.1.1 near the bottom as mm isnt out for rogers yet.. Oh and I checked my cable ot connected another device to my PC.. so after all this I went into twrp wiped everything you mentioned. After that I was looking for the factory reset option in twrp but couldn't find anywhere only restore which I have no rom backups made. Do I need this step?
Went into download mode pressed vol up.. opened odin 3.10.7. I did notice a change after wiping. Its now says com:6 instead of com:4 if that means anything.. I loaded the firmware into AP it took a while to load but it did without errors. Flashed and failed If you need I can copy the error message from odin in here tonight.
Do you think I need to remap partitions as you said earlier? Getting PIT files? Im lost here... appreciate any help
Click to expand...
Click to collapse
Where did you get your firmware from?
Why oh why did I bother reading through this entire thread, with intentions to help OP. Lol I didnt realize the date till the last post.