samsung i747 help - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

samsung i747 help - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

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

Related

new rom , how to root for galaxy tab 3 t210R

Hi guys
Today i buy a galaxy tab 3 sm-T210R
1 - how to root it?
2 - the stock firmware is 4.1.2 , what is the latest stock firmware for it?pls give me a link.
3 - does this device support simcard?
4 - one of my friend told me that it is locked.what that it means?how to know that it is lock or unlock?how to unlock it?
Thanks

muiacir said:
Hi guys
Today i buy a galaxy tab 3 sm-T210R
1 - how to root it?
2 - the stock firmware is 4.1.2 , what is the latest stock firmware for it?pls give me a link.
3 - does this device support simcard?
4 - one of my friend told me that it is locked.what that it means?how to know that it is lock or unlock?how to unlock it?
Thanks
Click to expand...
Click to collapse
1. http://forum.xda-developers.com/showthread.php?t=2437219
2. You have the latest firmware - http://www.samsungis.com/Firmwares/SM-T210R.html.
3. No, the device does not support a simcard.
4. The device is WiFi only and is not locked. Phones in the US are locked to specific carriers. To unlock the phone means to allow the phone to work on any carrier.

Brian D said:
1. http://forum.xda-developers.com/showthread.php?t=2437219
2. You have the latest firmware - http://www.samsungis.com/Firmwares/SM-T210R.html.
3. No, the device does not support a simcard.
4. The device is WiFi only and is not locked. Phones in the US are locked to specific carriers. To unlock the phone means to allow the phone to work on any carrier.
Click to expand...
Click to collapse
The topic for tw recovery and another topic for cwm recovery did not work and i still have the stock recovery.
Is there another way to root the device with no installung the pre-rooted firmware? I want the stock firmware

muiacir said:
The topic for tw recovery and another topic for cwm recovery did not work and i still have the stock recovery.
Is there another way to root the device with no installung the pre-rooted firmware? I want the stock firmware
Click to expand...
Click to collapse
The recovery and root works, you must unchecked the auto reboot by odin, after flashing boot manuly with the 3 combo keys into the revovery andflash the xxxroot.zip.

muiacir said:
The topic for tw recovery and another topic for cwm recovery did not work and i still have the stock recovery.
Is there another way to root the device with no installung the pre-rooted firmware? I want the stock firmware
Click to expand...
Click to collapse
All of my posted recoveries work fine. You didn't follow the directions close enough. Make sure you flash the universal root.zip once you get the recovery working. If not, it will re-install the stock recovery automatically.

Please explain how you are trying to add TWRP or CWM to your device. Do not leave out any details. This what we can see if you are missing a step. It should be a very simple process if the steps are followed correctly (as mentioned above). So please explain how you are doing it and what tools you are using.
Thanks

Brian D said:
1. http://forum.xda-developers.com/showthread.php?t=2437219
2. You have the latest firmware - http://www.samsungis.com/Firmwares/SM-T210R.html.
3. No, the device does not support a simcard.
4. The device is WiFi only and is not locked. Phones in the US are locked to specific carriers. To unlock the phone means to allow the phone to work on any carrier.
Click to expand...
Click to collapse
gr8nole said:
All of my posted recoveries work fine. You didn't follow the directions close enough. Make sure you flash the universal root.zip once you get the recovery working. If not, it will re-install the stock recovery automatically.
Click to expand...
Click to collapse
Brian D said:
Please explain how you are trying to add TWRP or CWM to your device. Do not leave out any details. This what we can see if you are missing a step. It should be a very simple process if the steps are followed correctly (as mentioned above). So please explain how you are doing it and what tools you are using.
Thanks
Click to expand...
Click to collapse
Thanks guys
1 - i go into download mode
2 - i open the odin v3.07(in win 8 that all the usb drivers were installed)
3 - then i connect the device to the computer via cable
4 - in the odin , the device added succesfully.
5 - i add the .tar file into pda and then uncheck the auto-reboot and f-partition
6 - i press start and it succesfully insralled(the odein said res ok and a green color upright said pass)
7 - i fo not go to the os , i directlly pres home and lower volme and power and directlly go to the recovery but still the recovery is stock recovery

muiacir said:
Thanks guys
1 - i go into download mode
2 - i open the odin v3.07(in win 8 that all the usb drivers were installed)
3 - then i connect the device to the computer via cable
4 - in the odin , the device added succesfully.
5 - i add the .tar file into pda and then uncheck the auto-reboot and f-partition
6 - i press start and it succesfully insralled(the odein said res ok and a green color upright said pass)
7 - i fo not go to the os , i directlly pres home and lower volme and power and directlly go to the recovery but still the recovery is stock recovery
Click to expand...
Click to collapse
I think step 7 is where you might be going wrong. Again, I THINK, I could be mistaken. But I would say start the tablet in normal mode before attempting to go into recovery. After the tablet starts, go ahead and shut it down. Then try and go into recovery mode.
Also, did you start Odin as an administrator? It sounds like you are OK in that regard as you got it going and loading. But if you are still having problems then try executing Odin as administrator.
Which .tar file are you loading? Is it one of the recovery files such as TWRP or CWM?
The only other thing might be the version of recovery you are trying to load. Make sure it works with your tab and firmware. I am sure you have already checked that, but just in case you forgot.

Brian D said:
I think step 7 is where you might be going wrong. Again, I THINK, I could be mistaken. But I would say start the tablet in normal mode before attempting to go into recovery. After the tablet starts, go ahead and shut it down. Then try and go into recovery mode.
Also, did you start Odin as an administrator? It sounds like you are OK in that regard as you got it going and loading. But if you are still having problems then try executing Odin as administrator.
Which .tar file are you loading? Is it one of the recovery files such as TWRP or CWM?
The only other thing might be the version of recovery you are trying to load. Make sure it works with your tab and firmware. I am sure you have already checked that, but just in case you forgot.
Click to expand...
Click to collapse
Ok i will test that(going to recovery after going to os)
What version should i use? I tested both of the tw and cwm

muiacir said:
Ok i will test that(going to recovery after going to os)
What version should i use? I tested both of the tw and cwm
Click to expand...
Click to collapse
In your number 7, you should be holding volume up to get into recovery. When you see the Tab 3 logo, release the power button but continue holding home and volume up until you get into recovery.
Sent from my SCH-I605

gr8nole said:
In your number 7, you should be holding volume up to get into recovery. When you see the Tab 3 logo, release the power button but continue holding home and volume up until you get into recovery.
Sent from my SCH-I605
Click to expand...
Click to collapse
My fault ..... i mean volume up but still stock recovery

muiacir said:
My fault ..... i mean volume up but still stock recovery
Click to expand...
Click to collapse
I'm not sure wath you are doing wrong.
Here are a link to a vid from Tomsgt , " How to install TWRP and root", when you are following the step you can root you Tab.
http://m.youtube.com/watch?feature=youtu.be&v=BDShwBHRjUE

[Q] odin on and off

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.

[Q] bricked -i747.

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.

[Q] N7100 Help Service State: Out Of Service. And More.

Dear all,
Well I dont know where to start. But here is what happened with my N7100 Note 2.
I was on the latest 4.4.2, the phone restarted suddenly one day and it just dont boot stuck at samsung logo,
flashed the 4.4.2 stock from sammobile. and it worked fine everything was perfect for a week, till it happened again
flashed the same rom. and here is where the trouble begins.
The IMEI changed to generic 00499XXX.., Serial No: 000000
i managed to downgrade to 4.1.2 with mobile odin, flashed a lot of stocks and customs as well. And after a very hard work for a week i manage to get back my IMEI and serial number back, now I backed up my EFS learned my lesson
Now i flashed the stock rom 4.1.1, phone is unlocked. cant make calls, or sms or data internet.
Now I have service: out of service, Bluetooth address: unavailable (while its in the efs folder the mac is in the file), Device status modified, And when I connect it to USB it wont recognize the phone until I have to dial *#7284# and change USB from modem to PDA, then save and reset. (EVERYTIME) I need a permanent fix as well for that.
Please I need help with those as i cant make my phone work.
Thanks and regards,
Mohamed Selim.

First and most important:
If you ever were on stock 4.4.x you can't downgrade to 4.1.x because of knoxed bootloader.
What you did with mobile odin was no real downgrade cause your bootloader wasn't touched.
Don't try to flash firmware beyond your current bootloader version.
Install Samsung Phone Info app from play store and look for actual bootloader version.

Androidwizzard said:
First and most important:
If you ever were on stock 4.4.x you can't downgrade to 4.1.x because of knoxed bootloader.
What you did with mobile odin was no real downgrade cause your bootloader wasn't touched.
Don't try to flash firmware beyond your current bootloader version.
Install Samsung Phone Info app from play store and look for actual bootloader version.
Click to expand...
Click to collapse
Well It actually did downgrade to 4.1.2 with Mobile odin and I checked the version and Baseband and everything it was the 4.1.2
Now I am on 4.1.1 stock. rooted and trying to figure out what to do now

onix17_5 said:
Well It actually did downgrade to 4.1.2 with Mobile odin and I checked the version and Baseband and everything it was the 4.1.2
Now I am on 4.1.1 stock. rooted and trying to figure out what to do now
Click to expand...
Click to collapse
As I said before: YOU DID NOT DOWNGRADE firmware to 4.1.2 with Mobile Odin, check with Info app from Samsung:
You will find bootloader between *ND3 and *NI1 and all are 4.4.2 KitKat
So, whatever firmware you try to flash under 4.4.2 is supposed to fail.

Androidwizzard said:
As I said before: YOU DID NOT DOWNGRADE firmware to 4.1.2 with Mobile Odin, check with Info app from Samsung:
You will find bootloader between *ND3 and *NI1 and all are 4.4.2 KitKat
So, whatever firmware you try to flash under 4.4.2 is supposed to fail.
Click to expand...
Click to collapse
I am not trying to argue here, And yes I do agree with you, it failed with i tried to downgrade with windows odin all the time, but acutally never failed with mobile-odin pro latest version. you dont have to believe me, I wont lie to you. I just need a solution for the problem im having now.
Thanks.

onix17_5 said:
I am not trying to argue here, And yes I do agree with you, it failed with i tried to downgrade with windows odin all the time, but acutally never failed with mobile-odin pro latest version. you dont have to believe me, I wont lie to you. I just need a solution for the problem im having now.
Thanks.
Click to expand...
Click to collapse
Mobile Odin does everything but doesn't flash bootloader so it is like flashing a custom rom which also doesn't contain bootloader.
PC Odin flashes complete firmware, so this is the only way to really up- or downgrade. Hope you understand the difference.
The only solution I see for you is to concentrate on 4.4.2 equal or up your actual bootloader version.

Androidwizzard said:
Mobile Odin does everything but doesn't flash bootloader so it is like flashing a custom rom which also doesn't contain bootloader.
PC Odin flashes complete firmware, so this is the only way to really up- or downgrade. Hope you understand the difference.
The only solution I see for you is to concentrate on 4.4.2 equal or up your actual bootloader version.
Click to expand...
Click to collapse
I do Understand the difference, and thanks for explaining more.
But I attached About my device
But any way beside all this points, I need to fix all the problems I am having either im on 4.1.1 or 4.4.2
Thanks.

onix17_5 said:
I do Understand the difference, and thanks for explaining more.
But I attached About my device
But any way beside all this points, I need to fix all the problems I am having either im on 4.1.1 or 4.4.2
Thanks.
Click to expand...
Click to collapse
I really want to help you out and I assure you that I know what I am talking about (take a look into my signature with stock roms and bootloaders).
There is indeed no solution on 4.1.1 and the screenshot doesn't show bootloader version. To believe what I say try to find out what BL version you are on. If it shows XXUFND3 up to XXUFNI1 you have the proof.

Androidwizzard said:
I really want to help you out and I assure you that I know what I am talking about (take a look into my signature with stock roms and bootloaders).
There is indeed no solution on 4.1.1 and the screenshot doesn't show bootloader version. To believe what I say try to find out what BL version you are on. If it shows XXUFND3 up to XXUFNI1 you have the proof.
Click to expand...
Click to collapse
kay my Bootloader is: N7100XXUFND4. Android Version: 4.1.1, you are right, I kinda understand what you were talking about now.
So now im all ears, Please help me solve my problems.

onix17_5 said:
Okay my Bootloader is: N7100XXUFND4. Android Version: 4.1.1
Well now how can I solve my problems, All ears
Click to expand...
Click to collapse
XXUFND3 was the first KitKat firmware for N7100 and yours was the second.
Three options:
1) Flash firmware using PC Odin at least ND4, maybe better NE1 or up
2) Flash through recovery any stock KitKat custom rom provided by wesamothman, cosmyndemeter or me
3) Flash through recovery any KitKat custom rom you like from development section here
4.3 custom roms may work also, but not 100% sure.
Beyond 4.3 I wouldn't recommend.

Androidwizzard said:
XXUFND3 was the first KitKat firmware for N7100 and yours was the second.
Three options:
1) Flash firmware using PC Odin at least ND4, maybe better NE1 or up
2) Flash through recovery any stock KitKat custom rom provided by wesamothman, cosmyndemeter or me
3) Flash through recovery any KitKat custom rom you like from development section here
4.3 custom roms may work also, but not 100% sure.
Beyond 4.3 I wouldn't recommend.
Click to expand...
Click to collapse
Okay, I will flash a stock Kitkat custom rom provided by you, Can you please require one for me. And I will flash it through recovery now.

onix17_5 said:
Okay, I will flash a stock Kitkat custom rom provided by you, Can you please require one for me. And I will flash it through recovery now.
Click to expand...
Click to collapse
Best and fastest one is XXUFNI1, NH2 and NG3 aren't bad either.
Do a clean installation (factory reset) and after setup device go back into recovery to flash SuperSu.zip.:highfive:

Androidwizzard said:
Best and fastest one is XXUFNI1, NH2 and NG3 aren't bad either.
Do a clean installation (factory reset) and after setup device go back into recovery to flash SuperSu.zip.:highfive:
Click to expand...
Click to collapse
Okay I staterd the download for XDA_XXUFNI1.zip and the BL NH2.
I think I got it, no BL just the XDA_XXUFNI1.zip and clean install it
Okay will be back when im done

onix17_5 said:
Okay I staterd the download for XDA_XXUFNI1.zip and the BL NH2.
should I flash the NH2 with odin after the rom? , or just the Rom without the NH2?
Click to expand...
Click to collapse
No need to flash BL cause you already have KitKat BL

Androidwizzard said:
XXUFND3 was the first KitKat firmware for N7100 and yours was the second.
Three options:
1) Flash firmware using PC Odin at least ND4, maybe better NE1 or up
2) Flash through recovery any stock KitKat custom rom provided by wesamothman, cosmyndemeter or me
3) Flash through recovery any KitKat custom rom you like from development section here
4.3 custom roms may work also, but not 100% sure.
Beyond 4.3 I wouldn't recommend.
Click to expand...
Click to collapse
Okay im done with this part flashed and step up, and installed superU.
So what next

onix17_5 said:
Okay im done with this part flashed and step up, and installed superU.
So what next
Click to expand...
Click to collapse
After reboot everything should be fine: Stable, rooted, fast, right?

Androidwizzard said:
After reboot everything should be fine: Stable, rooted, fast, right?
Click to expand...
Click to collapse
Yes rooted fast everything is stable, but all the problems I said in the first post still there

onix17_5 said:
Yes rooted fast everything is stable, but all the problems I said in the first post still there
Click to expand...
Click to collapse
You mean really everything
out of service,
Bluetooth address: unavailable
Device status modified -> that's ok
USB doesn't recognize the phone

Androidwizzard said:
You mean really everything
out of service,
Bluetooth address: unavailable
Device status modified -> that's ok
USB doesn't recognize the phone
Click to expand...
Click to collapse
Yes still out of service
Bluetooth address: unavaliable
USB doesnt recognize the phone until i have to do *#7284# and change USB to PDA, this its okay but once i restarted the phone I have to do it again save and reset.

onix17_5 said:
Yes still out of service
Bluetooth address: unavaliable
USB doesnt recognize the phone until i have to do *#7284# and change USB to PDA, this its okay but once i restarted the phone I have to do it again save and reset.
Click to expand...
Click to collapse
Ok, last one is driver related to your PC (Mac or Windows?), are you running Kies?
For BT I found this APP
For the first issue I think about IMEI lost, pls check

N7100 stuck in boot

Hi,
I am new to the custom ROM scene, and am learning by flashing lineageOS on my old note 2. I followed the lineageOS instructions found here, with opengapps, and it got stuck on the boot screen for hours. I wiped and tried without gapps, and it still got stuck. This is where i noticed on the lineageOS device page it said this was for the n7105, while I have the N7100.
I tried flashing a rom for the N7100 (first this then this) but both times it failed, with the error message that I am trying to flash a rom for the N7100, but that the device is t0lte.
Did I cause this, or is my device indeed t0lte? how can I fix this?
edit: logcat doesn't work while booting
edit 2: the exact error message is: 'E3004: This package is for device: t0rg,n7100,GT-N7100; this device is t0lte.'
edit 3: It seems the 'default.prop' file also specifies this is an N7105 phone.

Boot the phone into download mode to confirm the model number.

audit13 said:
Boot the phone into download mode to confirm the model number.
Click to expand...
Click to collapse
The model in download mode is indeed N7100. Do you have any idea how I can fix this?

The model # is GT-N7100?
Was the phone running the latest stock ROM before flashing TWRP?
Tried flashing TWRP with Odin? Tried different versions of TWRP?

audit13 said:
The model # is GT-N7100?
Was the phone running the latest stock ROM before flashing TWRP?
Tried flashing TWRP with Odin? Tried different versions of TWRP?
Click to expand...
Click to collapse
Yes! I realised the lineageOS guide linked to a t0lte version of TWRP. a quick reinstall and everything is working as intended now thanks!

ThaChillera said:
Yes! I realised the lineageOS guide linked to a t0lte version of TWRP. a quick reinstall and everything is working as intended now thanks!
Click to expand...
Click to collapse
Good to hear. Have fun with your "new" phone

Develop Bugs

welcome