It seems that when I connect my phone to odin a com port opens. When I put my phone into recovery mode the com port does not open so odin does not see my phone. Yes I do have the phone in debug mode. Samsung drivers are in.
BigNoobee said:
It seems that when I connect my phone to odin a com port opens. When I put my phone into recovery mode the com port does not open so odin does not see my phone. Yes I do have the phone in debug mode. Samsung drivers are in.
Click to expand...
Click to collapse
Odin is used in download mode. Are you trying to use it in recovery mode?
Larry2999 said:
Odin is used in download mode. Are you trying to use it in recovery mode?
Click to expand...
Click to collapse
Trying to root the phone. Doesn't the phone need to be in recovery mode to root it?
BigNoobee said:
Trying to root the phone. Doesn't the phone need to be in recovery mode to root it?
Click to expand...
Click to collapse
Depending on your phone model and what method you are trying to use to root, you may need to flash SuperSU via recovery. This process does not, however, start in recovery. It starts with flashing custom recovery via Odin and then manually booting to recovery to flash the SuperSU zip. To flash a custom recovery via Odin, you would need to boot into download mode. There are other methods, of course, to root that do not require either download or recovery modes. What's the model of your phone and what firmware version are you on?
Have you tried flashing a pre-rooted ROM? You have an i747 or i747m?
Larry2999 said:
Depending on your phone model and what method you are trying to use to root, you may need to flash SuperSU via recovery. This process does not, however, start in recovery. It starts with flashing custom recovery via Odin and then manually booting to recovery to flash the SuperSU zip. To flash a custom recovery via Odin, you would need to boot into download mode. There are other methods, of course, to root that do not require either download or recovery modes. What's the model of your phone and what firmware version are you on?
Click to expand...
Click to collapse
The phone is a SGH-I747M ver. 4.3
I tried rooting based on a number of videos as to easily follow the process.
audit13 said:
Have you tried flashing a pre-rooted ROM? You have an i747 or i747m?
Click to expand...
Click to collapse
I have a i747m, The situation is that odin only opens the com port when the phone is in operating mode.
BigNoobee said:
It seems that when I connect my phone to odin a com port opens. When I put my phone into recovery mode the com port does not open so odin does not see my phone. Yes I do have the phone in debug mode. Samsung drivers are in.
Click to expand...
Click to collapse
I should have stated my goal. My goal is to put kitkat on my phone. After talking to my provider (petro mobility) on the Rogers network no upgrades are going to be provided and at the very least I need an s4 or better s5 to run kitkat. Also this information I was given is NOT official but only the opinion of an employee"s personal opinion, having worked for the company for some time. The phone is not supported in any way by petro mobility but is only running on the Rogers network. If any upgrades are made it will be by Rogers. Rogers will not say anything because I am not a Rogers customer.
To flash a Kit Kat ROM, you need to have a custom recovery installed on your phone.
You can load Philz Touch via Odin.You can flash the latest tar Philz d2lte from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Boot into download mode, put the Philz tar file in the PDA section of Odin, check nothing except auto reboot and F.Reset Time.
Boot into recovery mode and you will see that Phil has replaced the stock recovery.
You can copy a custom rom to your external micro SD card and flash it.
If you just want a rooted stock ROM, look here: http://forum.xda-developers.com/sho...tmctr=(not provided)&__utmv=-&__utmk=34317218
Warning: doing all of these things can soft or hard brick your phone. Make sure you read and understand everything before proceeding. The method I described worked my i747m with 4.1.2 and another i747m with 4.3. I cannot guarantee it will work for you.
audit13 said:
To flash a Kit Kat ROM, you need to have a custom recovery installed on your phone.
You can load Philz Touch via Odin.You can flash the latest tar Philz d2lte from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Boot into download mode, put the Philz tar file in the PDA section of Odin, check nothing except auto reboot and F.Reset Time.
Boot into recovery mode and you will see that Phil has replaced the stock recovery.
You can copy a custom rom to your external micro SD card and flash it.
If you just want a rooted stock ROM, look here: http://forum.xda-developers.com/sho...tmctr=(not provided)&__utmv=-&__utmk=34317218
Warning: doing all of these things can soft or hard brick your phone. Make sure you read and understand everything before proceeding. The method I described worked my i747m with 4.1.2 and another i747m with 4.3. I cannot guarantee it will work for you.
Click to expand...
Click to collapse
GREAT !!!! GREAT !!!:laugh: Sorry for Yelling It worked for me ThanX
My next step is to go get Rom Manager from the app store...watching their video now on Rom Manager.. Very high learning curve for me- hope I don't brick the phone ....
BigNoobee said:
GREAT !!!! GREAT !!!:laugh: Sorry for Yelling It worked for me ThanX
My next step is to go get Rom Manager from the app store...watching their video now on Rom Manager.. Very high learning curve for me- hope I don't brick the phone ....
Click to expand...
Click to collapse
Now you have custom recovery, you can flash a Kit-Kat based custom ROM. There is, of course, a difference between a Kit-Kat based custom ROM and official Kit-Kat 4.4. We have information and I'm sure they are reliable enough, that Kit-Kat 4.4 will be rolled out for Samsung GS III and all its variants including the i747U/M. The expectation has, however, been on for some time and no one really knows when and if. If you are using a custom ROM, you will not be able to get OTA updates for official firmware if the official version is rolled out but manual updates will still be possible, thanks to the development community.
BigNoobee said:
GREAT !!!! GREAT !!!:laugh: Sorry for Yelling It worked for me ThanX
My next step is to go get Rom Manager from the app store...watching their video now on Rom Manager.. Very high learning curve for me- hope I don't brick the phone ....
Click to expand...
Click to collapse
I don't personally use ROM Manager as I find it redundant. Now that you have Philz which can flash pretty much any KK ROM, you can just stick with using Philz to flash.
I like the Validus ROM on the i747m. I find it works well and has great battery life and performance.
BTW, you do not need to root in order to flash a custom ROM.
Related
i tried to upgrade my s3 i accidentally falshed with correpted file('i renamed the file .mb5 to .tar) it stuck and showing that needed to connect kies
.. and kies not detecting my device and it wont boot into recovery mode but after search i rooted again through cf auto root and then it can enter into recovery mode is it bricked/not what happend to my device currently it can enter into both recovery &download mode ......
pls help me with this
ghjsdf9 said:
i tried to upgrade my s3 i accidentally falshed with correpted file('i renamed the file .mb5 to .tar) it stuck and showing that needed to connect kies
.. and kies not detecting my device and it wont boot into recovery mode but after search i rooted again through cf auto root and then it can enter into recovery mode is it bricked/not what happend to my device currently it can enter into both recovery &download mode ......
pls help me with this
Click to expand...
Click to collapse
Welcome to the forum! Your phone's hardly bricked if you can get to download and recovery modes. Flashing the correct (stock) firmware should get you back to working conditions. What Android version were you on prior to it being stuck and what were you trying to upgrade to?
Larry2999 said:
Welcome to the forum! Your phone's hardly bricked if you can get to download and recovery modes. Flashing the correct (stock) firmware should get you back to working conditions. What Android version were you on prior to it being stuck and what were you trying to upgrade to?
Click to expand...
Click to collapse
THANKS FOR WELCOME PARTY:
and for the rly tooo.
i can get into both download mode as well as recovery mode ..... i'm not clear with my phones model-in odin mode it showing "PRODUCT NAME:-SGH-I747M" on starting it is running 4.1.2 (zsemc1) version i am not clear with baseband etc.
and i'm not clear with supported varient versions when i flashed with different version in odin mode it showing differnt causes for different version
ex: "unsupported dev type","secure check fail sb12",securechech fail aboot" for three different versions
ghjsdf9 said:
THANKS FOR WELCOME PARTY:
and for the rly tooo.
i can get into both download mode as well as recovery mode ..... i'm not clear with my phones model-in odin mode it showing "PRODUCT NAME:-SGH-I747M" on starting it is running 4.1.2 (zsemc1) version i am not clear with baseband etc.
and i'm not clear with supported varient versions when i flashed with different version in odin mode it showing differnt causes for different version
ex: "unsupported dev type","secure check fail sb12",securechech fail aboot" for three different versions
Click to expand...
Click to collapse
i747M is for the Canadian and Mexican variants. If you were on stock 4.1.2, you should be able to Odin back to stock 4.1.1 or upgrade to 4.3 via custom recovery. You can go to the thread below to check the correct stock image for your phone based on carrier. Make sure you use the correct image as flashing the wrong version could hard brick your phone. Download to your PC and then flash. If you select the 4.3 version, you would need to flash custom recovery to your phone via Odin, save the file to a (micro) SD card and then flash via custom recovery.
http://forum.xda-developers.com/showthread.php?t=1739426
Let me know if this works for you.
Larry2999 said:
i747M is for the Canadian and Mexican variants. If you were on stock 4.1.2, you should be able to Odin back to stock 4.1.1 or upgrade to 4.3 via custom recovery. You can go to the thread below to check the correct stock image for your phone based on carrier. Make sure you use the correct image as flashing the wrong version could hard brick your phone. Download to your PC and then flash. If you select the 4.3 version, you would need to flash custom recovery to your phone via Odin, save the file to a (micro) SD card and then flash via custom recovery.
http://forum.xda-developers.com/showthread.php?t=1739426
Let me know if this works for you.
Click to expand...
Click to collapse
i'm Asian it worked for local networks before bricked so i'm not clear with choosing in versions... ["help me with it"]
ghjsdf9 said:
i'm Asian it worked for local networks before bricked so i'm not clear with choosing in versions... ["help me with it"]
Click to expand...
Click to collapse
If we are going to flash a stock ROM, we would need to flash the correct version as there is risk of a worse brick if we flash the wrong one. When the phone was working normally, the old network would probably be showing during booting. If you got it from abroad, please check if you can get the information from the previous owner. If there is no way of telling the correct firmware, then you can flash custom recovery to the phone and try flashing a custom ROM via recovery. It's always tidier flashing a custom ROM to a device functioning normally but, unless we can be sure of the correct stock firmware to flash, your options may be limited.
Larry2999 said:
If we are going to flash a stock ROM, we would need to flash the correct version as there is risk of a worse brick if we flash the wrong one. When the phone was working normally, the old network would probably be showing during booting. If you got it from abroad, please check if you can get the information from the previous owner. If there is no way of telling the correct firmware, then you can flash custom recovery to the phone and try flashing a custom ROM via recovery. It's always tidier flashing a custom ROM to a device functioning normally but, unless we can be sure of the correct stock firmware to flash, your options may be limited.
Click to expand...
Click to collapse
and finally i found the correct version and when tried to flash through odin i came across this problem
it stuck at "initialization..." [more than hour..] help pls......
ghjsdf9 said:
and finally i found the correct version and when tried to flash through odin i came across this problem
it stuck at "initialization..." [more than hour..] help pls......
Click to expand...
Click to collapse
Sounds like a partition problem. Please let me know the firmware version you are trying to flash.
Larry2999 said:
Sounds like a partition problem. Please let me know the firmware version you are trying to flash.
Click to expand...
Click to collapse
it's version 4.3(I747MVLUEND2_I747MOYBEND2_SPC) at sammobiles.com............
and once "i tried with pit file by marking re partition" will this effect ??????????????
ghjsdf9 said:
it's version 4.3(I747MVLUEND2_I747MOYBEND2_SPC) at sammobiles.com............
and once "i tried with pit file by marking re partition" will this effect ??????????????
Click to expand...
Click to collapse
I've seen this particular problem reported several times and it's always been a problem with the pit file. Flashing a complete stock system should fix all partition problems though. If the stock file you are using is an Odin flashable file, you may try using Odin 3.09. Otherwise, I'd suggest you find a recovery flashable image and flash via (custom) recovery.
It's been a long bloody time since I fiddled around with stuff on this phone. So I'm still on a rooted 4.1.2.
My questions are is it worth the upgrade to KitKat? And if so, what's the easiest way for me to do so? Hopefully retaining root, but not too necessary.
Help would be appreciated. For dummies.
Hey there.
I've gone through the process myself recently. Here is what you should do :
1. Download a custom rom from the Android Development forum. For example I downloaded the DN3 v5.2, but whatever catches your eye is fine.
2. Just follow the instructions the rom' s topic states.
3. If you have trouble getting to the recovery mode, you should flash with Odin some custom recovery. I like the cwm recovery.
4. Most guides provide info how to root your phone but if not then there is a topic in the Android Development forum about it.
I suggest backing up everything you can before- copy the phone contents to your pc, run the efs professional program to backup your efs.
Cheers
Rizaria said:
It's been a long bloody time since I fiddled around with stuff on this phone. So I'm still on a rooted 4.1.2.
My questions are is it worth the upgrade to KitKat? And if so, what's the easiest way for me to do so? Hopefully retaining root, but not too necessary.
Help would be appreciated. For dummies.
Click to expand...
Click to collapse
Hi there. I'm using n7100. N7105 is not far different to n7100. I've recently upgraded my phone from 4.3 to 4.4. I can't see a big difference from the 2 version except 4.4 consumes more battery than 4.3. I think you should consider 4.3 first before going straight to 4.4.
Just to inform you. What I know is...4.3 and 4.4 Official Rom already have Knox. So maybe you should read about them first. And Flashing Custom Recovery like PhilzTouchRecovery may trigger your Knox and increase your Binary Counter. And you may loose your warranty.
Flashing and rooting stock ROM is easy. But you have to do it right. What I did:
1. Download Odin
2. Download Samsung USB Drivers
3 Download 4.4 Firmware for my phone at sammobile.com
4. Install Samsung USB Driver
5. Run Odin
6. Put phone in Download Mode. Check if Odin successfully detected my phone
7. Once success, load the firmware to PDA Tab/Button. Don't touch anything
8. Press start. Wait till done. Wait till your phone reboot on it's own.
9. Once rebooted, check "About Device".
10. Done!
11. Download PhilzTouchRecovery 6.26
12. Put device into Download Mode again.
13. Run Odin again
14. Connect device again
15. Load PhilzTouchRecovery.tar.md5 to PDA Tab/Button
16. Uncheck Auto Reboot from Odin
17. Click start. Once Pass! Disconnect device.
18. Hold Power Button, DON'T RELEASE till you boot into your new recovery.
19. Once booted to PhilzRecovery, select reboot system now, but make sure not to overwrite with stock recovery or else you're PhilzRecovery will be reverted back to your stock recovery and you have to flash again your PhilzRecovery.
20. Once successfully flashed PhilzRecovery. Make all necessary backups (Full backup) you can't make EFS/MODEM backup yet because your not yet Rooted. You just installed Custom Recovery.
21. Once fully backed up. Copy backup files to your PC.
22. If you want to root again. Use CF-ROOT on 4.4.2 or use Dr.Ketan's Multi-Tool-Advance-V6 in 4.3. And follow their instructions.
Good Luck. HTH.
PoOoZaQ said:
Hey there.
I've gone through the process myself recently. Here is what you should do :
1. Download a custom rom from the Android Development forum. For example I downloaded the DN3 v5.2, but whatever catches your eye is fine.
2. Just follow the instructions the rom' s topic states.
3. If you have trouble getting to the recovery mode, you should flash with Odin some custom recovery. I like the cwm recovery.
4. Most guides provide info how to root your phone but if not then there is a topic in the Android Development forum about it.
I suggest backing up everything you can before- copy the phone contents to your pc, run the efs professional program to backup your efs.
Cheers
Click to expand...
Click to collapse
Thanks for that. Still wondering which one I should try all this Knox stuff is puzzling. Seems a lot of things have happened since I last had a fiddle.
asin_punk said:
Hi there. I'm using n7100. N7105 is not far different to n7100. I've recently upgraded my phone from 4.3 to 4.4. I can't see a big difference from the 2 version except 4.4 consumes more battery than 4.3. I think you should consider 4.3 first before going straight to 4.4.
Just to inform you. What I know is...4.3 and 4.4 Official Rom already have Knox. So maybe you should read about them first. And Flashing Custom Recovery like PhilzTouchRecovery may trigger your Knox and increase your Binary Counter. And you may loose your warranty.
Flashing and rooting stock ROM is easy. But you have to do it right. What I did:
1. Download Odin
2. Download Samsung USB Drivers
3 Download 4.4 Firmware for my phone at sammobile.com
4. Install Samsung USB Driver
5. Run Odin
6. Put phone in Download Mode. Check if Odin successfully detected my phone
7. Once success, load the firmware to PDA Tab/Button. Don't touch anything
8. Press start. Wait till done. Wait till your phone reboot on it's own.
9. Once rebooted, check "About Device".
10. Done!
11. Download PhilzTouchRecovery 6.26
12. Put device into Download Mode again.
13. Run Odin again
14. Connect device again
15. Load PhilzTouchRecovery.tar.md5 to PDA Tab/Button
16. Uncheck Auto Reboot from Odin
17. Click start. Once Pass! Disconnect device.
18. Hold Power Button, DON'T RELEASE till you boot into your new recovery.
19. Once booted to PhilzRecovery, select reboot system now, but make sure not to overwrite with stock recovery or else you're PhilzRecovery will be reverted back to your stock recovery and you have to flash again your PhilzRecovery.
20. Once successfully flashed PhilzRecovery. Make all necessary backups (Full backup) you can't make EFS/MODEM backup yet because your not yet Rooted. You just installed Custom Recovery.
21. Once fully backed up. Copy backup files to your PC.
22. If you want to root again. Use CF-ROOT on 4.4.2 or use Dr.Ketan's Multi-Tool-Advance-V6 in 4.3. And follow their instructions.
Good Luck. HTH.
Click to expand...
Click to collapse
Very concise steps, cheers for that. Might give all that a try. Just need a safe rom. Not sure what. Is there anything else that needs flashing, like modem files or anything?
Thanks for both your comments.
Only the rom is necessary. Shouldn't flash modem and kernel etc unless something doesn't work.
All the roms published in xda are fine and safe. I just went for the topic with the most views.
If you want you can also download stock 4.3 from www.sammobile.com
Just choose your device and you get a file flashable with odin. About 1.9 giga download.
Rizaria said:
Thanks for that. Still wondering which one I should try all this Knox stuff is puzzling. Seems a lot of things have happened since I last had a fiddle.
Very concise steps, cheers for that. Might give all that a try. Just need a safe rom. Not sure what. Is there anything else that needs flashing, like modem files or anything?
Thanks for both your comments.
Click to expand...
Click to collapse
Your current Bootloader doesn't have Knox. So you better search for a 4.3 or 4.4 rom that doesn't flash new bootloader. I think i saw it somewhere in the development.If I were not mistaken, it should be flashed thru custom recovery. Coz it's a zip file.
All I know is all rom files from sammobile.com includes new kernel, bootloader and modem. So if you flash this roms from sammobile, you will have a new kernel, bootloader and modem. It's all up to you. If I were you, I'll stay away from Knox. So find a rom that supports your current bootloader. Maybe a custom one.
Maybe this will help...
http://forum.xda-developers.com/showthread.php?t=2747963
asin_punk said:
Your current Bootloader doesn't have Knox. So you better search for a 4.3 or 4.4 rom that doesn't flash new bootloader. I think i saw it somewhere in the development.If I were not mistaken, it should be flashed thru custom recovery. Coz it's a zip file.
All I know is all rom files from sammobile.com includes new kernel, bootloader and modem. So if you flash this roms from sammobile, you will have a new kernel, bootloader and modem. It's all up to you. If I were you, I'll stay away from Knox. So find a rom that supports your current bootloader. Maybe a custom one.
Maybe this will help...
http://forum.xda-developers.com/showthread.php?t=2747963
Click to expand...
Click to collapse
Fair enough, thanks.
If I try the one below, think that'd work out alright? And which to use, deoxed or not?
http://forum.xda-developers.com/showthread.php?t=2588787
Sent from my GT-N7105 using XDA Free mobile app
Rizaria said:
Fair enough, thanks.
If I try the one below, think that'd work out alright? And which to use, deoxed or not?
http://forum.xda-developers.com/showthread.php?t=2588787
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah nice find... It should work fine... you're on the 3rd status "For those are on the 4.1.2 bootloader the rom could work normally with AGNi Kernel include in rom". I think you should go for DEODEXED for more customization and etc. Read here: http://codeversed.com/deodexed-vs-odexed-rom/.
Make sure to follow instruction precisely and strictly. And make sure to copy your Backup to your PC right after you created it. Coz if you do a Full Wipe, Reset and Clean Install, it will also delete the backup that you made. Read the instructions multiple times carefully to avoid mislead. Once you done it successfully, you will be on Custom Rom and Custom Kernel. Sounds very techie. Hahaha. Good Luck!
asin_punk said:
Yeah nice find... It should work fine... you're on the 3rd status "For those are on the 4.1.2 bootloader the rom could work normally with AGNi Kernel include in rom". I think you should go for DEODEXED for more customization and etc. Read here: http://codeversed.com/deodexed-vs-odexed-rom/.
Make sure to follow instruction precisely and strictly. And make sure to copy your Backup to your PC right after you created it. Coz if you do a Full Wipe, Reset and Clean Install, it will also delete the backup that you made. Read the instructions multiple times carefully to avoid mislead. Once you done it successfully, you will be on Custom Rom and Custom Kernel. Sounds very techie. Hahaha. Good Luck!
Click to expand...
Click to collapse
Thanks for the advice.
Really, I wanted to upgrade to Android L but then I saw it wasn't out yet so I was like...huh, KitKat time?
I'm not even sure if it'll be any better than what I have! Mostly just want something with better battery life. Even though I just bought a new battery that lets me use my phone for 3 days and a half hour. I have noticed that Screen/Android seem to be bleeding power a lot more these days, so figured it might be worth a wipe and an upgrade.
In any case, whenever I do, I have some handy guides now. Cheers~
Hello Everyone!
I'm stuck!!! If anyone can help, it is so appreciated!
I attempted to root my subject named device using ODIN following these directions:
http://forum.xda-developers.com/galaxy-note-10-2014/development/root-cf-auto-root-t2905495
Everything seems to go as planned until restart.. the tablet continuously reboots, over and over, but fails to load.
I have no clue what to do from here, so this is my only option... ask those who have much more knowledge than me!
Thanks in advance. I really appreciate your assistance.
That's called a bootloop. Something went wrong with flashing. What is a subject named device? That autoroot method only works for smp600 that is already running stock 5.1 or 4.4.2 . Boot into downloadmode using the appropriate buttons, then Download stock firmarwe from sammobile.Com and flash via Odin to get back a working device.
Which build are you on? If it is 5.1.1, that method will result in a bootloop if you try to root.
Use this instead
http://forum.xda-developers.com/showthread.php?p=63637426
Sent from my SM-N915G using Tapatalk
diabl0w said:
That's called a bootloop. Something went wrong with flashing. What is a subject named device? That autoroot method only works for smp600 that is already running stock 5.1 or 4.4.2 . Boot into downloadmode using the appropriate buttons, then Download stock firmarwe from sammobile.Com and flash via Odin to get back a working device.
Click to expand...
Click to collapse
The tablet is a Samsung Galaxy Note 10.1 (2014 Edition) Model SM-P600.
Not sure about the build.... but I will most definitely checkout the link you provided - thanks!
Question, can I flash a different rom rather than stock?
Also, I was just able to flash TWRP via ODIN and was able to get TWRP to load on the device. I'm hoping to flash a custom rom from the external SD via TWRP. I don't care which one at this point.. just need to get the tablet functional again and get a backup saved lol.
smoothbeaver said:
Not sure about the build.... but I will most definitely checkout the link you provided - thanks!
Question, can I flash a different rom rather than stock?
Also, I was just able to flash TWRP via ODIN and was able to get TWRP to load on the device. I'm hoping to flash a custom rom from the external SD via TWRP. I don't care which one at this point.. just need to get the tablet functional again and get a backup saved lol.
Click to expand...
Click to collapse
Here is "how to" instruction by me - post #225 for upgrade to the latest 5.1.1 and root your device. Once done and you want custom rom, just boot into twrp and flash any custom rom that you like. Let me know if you have issue.
http://forum.xda-developers.com/gal...lollipop-5-1-1-galaxy-note-10-t3239971/page23
So I have a Galaxy S4 from T-Mobile and want to use CM or any other bloatware free ROM, I have some experience flashing ROMS and Kernels but with Xperia's not Sam devices.
Now just watched some videos and tutorials to follow, but all of them start using Odin or in some cases Heimdall (CM Wiki), but is there where should I start or need to ROOT or Unlock the Bootloader
After TWRP Im fine, Thanks in advance, already google it but my english isnt good enough, if you can list me the steps, without description, just the step it would be GREAT!
Do not use any bootloader unlocking apps on your phone as I don't believe the T-mobile s4 has a locked bootloader. If the bootloader is not locked and you use bootloader unlocking apps or procedures, you could hard-brick the phone.
If the bootloader is unlocked, here's how to flash TWRP:
Download the latest tar version of TWRP for the s4 Tmobile from here: https://dl.twrp.me/jfltetmo/
Download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=...5QWImOPDJboTA_V3D5S9eA&bvm=bv.112454388,d.amc
Open Odin, uncheck everything except r.reset time. Click on PDA and select the twrp tar file you downloaded. Connect phone to the computer in download mode. Click on start to flash TWRP. When you see the word "reset" in the status window, remove USB cable from the phone, remove battery, wait about 3 seconds, replace battery, use button combination to boot into recovery.
If the bootloader is locked, do not use Odin to flash TWRP.
Thanks man nad in your opinion what is the most stable ROM AOSP based
Not sure about the most stable ROM as I am using stock at the moment as I was having signal problems and I need to determine if the signal problem are due to software or hardware..
Did you get TWRP installed?
Yes its installed now, one more question in order to do a backup only for stock galaxy rom should I unmark data from TWRP backup settings? Or its easy to install the galaxy stock rom and should skip the backup
Good afternoon . sorry for my english writing an interpreter because of Belarus.
The problem, in my i747 screen does not respond to touch, after the installation cm13, all done correctly and according to the instructions, and after flashing when the phone beeps, the same does not go in recovery in odin mode. And now I do not know him Thu wasps do.
Flash the stock rom using Odin. You have i747 or i747m? You can confirm the model in Odin mode.
Re: Help
Tegra56 said:
Good afternoon . sorry for my english writing an interpreter because of Belarus.
The problem, in my i747 screen does not respond to touch, after the installation cm13, all done correctly and according to the instructions, and after flashing when the phone beeps, the same does not go in recovery in odin mode. And now I do not know him Thu wasps do.
Click to expand...
Click to collapse
@Tegra56
You may have to provide some more information about your device before we can start to identify the problem:
1. Have you checked the md5sum on the ROM you are using? (To make sure you did not get a bad download)
2. Is you device rooted?
3. What is your Bootloader/Modem Version #? [Settings-About Phone-Baseband Version: ( I747UCUFNJ2- this is the latest)]
4. Have you installed a custom recovery?(TWRP; CWM; Phil's Touch)
If you can provide this information I will try to assist with the problem.
edit: If you can't get into your settings follow @audit13 instructions in Post#2 and we will proceed from there.
audit13 said:
Flash the stock rom using Odin. You have i747 or i747m? You can confirm the model in Odin mode.
Click to expand...
Click to collapse
he does not go in odin mod
CoperaN said:
@Tegra56
You may have to provide some more information about your device before we can start to identify the problem:
1. Have you checked the md5sum on the ROM you are using? (To make sure you did not get a bad download)
2. Is you device rooted?
3. What is your Bootloader/Modem Version #? [Settings-About Phone-Baseband Version: ( I747UCUFNJ2- this is the latest)]
4. Have you installed a custom recovery?(TWRP; CWM; Phil's Touch)
If you can provide this information I will try to assist with the problem.
edit: If you can't get into your settings follow @audit13 instructions in Post#2 and we will proceed from there.
Click to expand...
Click to collapse
1 Firmware has been checked md5
2 firmware has rights root
3 This I can not say. as the phone will not turn on, it was i747
4 Was installed TWRP
Did you install cm13 for the d2att? Sounds like the incorrect ROM may have been flashed to the phone.
Re: Help
Tegra56 said:
1 Firmware has been checked md5
2 firmware has rights root
3 This I can not say. as the phone will not turn on, it was i747
4 Was installed TWRP
Click to expand...
Click to collapse
Ok @Tegra56
I noticed in your reply to @audit13 that you cannot get into Odin. But does the phone get into stock recovery mode?
Did you make a backup (with TWRP) of the ROM you used before flashing cm13 ? fingers-crossed
If you did, try restoring this backup first.
audit13 said:
Did you install cm13 for the d2att? Sounds like the incorrect ROM may have been flashed to the phone.
Click to expand...
Click to collapse
Yes, I downloaded it for cm13 for the d2att
CoperaN said:
Ok @Tegra56
I noticed in your reply to @audit13 that you cannot get into Odin. But does the phone get into stock recovery mode?
Did you make a backup (with TWRP) of the ROM you used before flashing cm13 ? fingers-crossed
If you did, try restoring this backup first.
Click to expand...
Click to collapse
unfortunately I did not make a copy
It may not help but have you tried using a USB jig to force the phone into download mode?
http://www.xda-developers.com/need-a-samsung-usb-jig-build-your-own/
Tegra56 said:
unfortunately I did not make a copy
Click to expand...
Click to collapse
Ok, Here is where the fun begins!!... First we must know what your bootloader/modem # is right now. This is very Important.
Based on the information you have provided thus far, it seems to me that your firmware was out of date when you flashed the custom ROM. My suggestion to you, would be to do a clean install (Wipe) of this ROM: http://d-h.st/sV2 You can Read More about it here: http://forum.xda-developers.com/showthread.php?t=2390147 It's a Custom KitKat ROM, just so you can boot into something, the recommended gapps for this ROM have been discontinued, but you can try "Open Gapps" Choose the 4.4 -Nano Package: http://opengapps.org/
If you were running KitKat 4.4.2 chances are, you might be updated to at least I747UCUEMJB in which case they are 3 incremental firmware updates left for your device. However updating firmware should only be done using Odin so we must try the above alternative first and then work on getting Odin to work with your device. Good Luck.
edit: I just noticed you said the phone won't turn on!!....
If you have TWRP installed then you will have to hold down the "Volume up" , "Power" and "Home" buttons, release the power button(Keep holding the other two) once you feel the device vibrate, when you see the android logo you may release the other two, TWRP recovery should boot.
audit13 said:
It may not help but have you tried using a USB jig to force the phone into download mode?
http://www.xda-developers.com/need-a-samsung-usb-jig-build-your-own/
Click to expand...
Click to collapse
No, I do not even know if such a method, after the holidays try