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
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.
SGH-I747 (non rooted)
4.4.2 KitKat OTA
I have read a ton of the (un-brick) post on the forums, but they are all rooted phones, and the problem is usually because people tried to install the wrong ROM, but this phone is not rooted.
After OTA update, the phone was fine for a while (wife's). Then is started to reboot randomly. Did factory reset, and still had the same problem.
So I picked up an S5 for my wife and put her S3 in a box. Yesterday i tried to fix the S3 with Kies, tried firmware recovery, failed (Firmware upgrade encountered an issue).
Can get to download mode but that is it. Tried Odin, back to stock file (fail auth), so im guessing because i was trying to flash older ROM, looked for new (KK) ROMs but they are not Odin friendly, then read something about bootloader and 4.4.2 will not work, so i gave up after that.
Kies, emergency recovery will not work, fails every time, so what are my options?
thanks in advance.
Semper-Fidelis
I suggest you flash the latest version of Philz Touch for the d2lte in Odin from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Copy a the latest cm10.2 ROM to your sd card.
Boot into recovery and flash CM10.2. Install the Samsung Phone Info App from the Play Store and confirm the installed bootloader and modem.
Alternatively, you could flash TWRP as your recovery, boot into TWRP, open a terminal windows, and type getprop ro.bootloader to get the bootloader version.
audit13 said:
I suggest you flash the latest version of Philz Touch for the d2lte in Odin from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Copy a the latest cm10.2 ROM to your sd card.
Boot into recovery and flash CM10.2. Install the Samsung Phone Info App from the Play Store and confirm the installed bootloader and modem.
Alternatively, you could flash TWRP as your recovery, boot into TWRP, open a terminal windows, and type getprop ro.bootloader to get the bootloader version.
Click to expand...
Click to collapse
Thanks! will try that tonight.
Really appreciate your response!
Semper Fidelis
Any luck?
audit13 said:
Any luck?
Click to expand...
Click to collapse
Sorry, wife had other plans. Will give a try tonight and i will post back.
thanks again.
audit13 said:
Any luck?
Click to expand...
Click to collapse
Success!
Thanks a lot. Had to use a different phone to load rom onto SD card, usb device would not recognize. no big deal. everything else went without issue. Thanks again!
Semper Fidelis
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
Hello guys!
I have a problem with my wife's Note II (should be 7100).
Starting from a stock 4.4.2 I tried installing MIUI 8 through PhilzTouch. Everything went fine, I also installed Open Gapps but I had lost the IMEI. The phone didn't recognize the sim at all (INSERT SIM).
So I tried to restore the working EFS partition (of the 4.4.2) but still the IMEI was corrupted.
I had to restore the whole ROM backup to get the phone working again.
Then i tried with RR 7.1 but I had the same problem.
Basically it seems that everything i flash make me lose the IMEI :|
Any suggestions? Thanks!
The phone was running the latest bootloader and modem before flashing a custom ROM? I also recommend using TWRP to flash, not CWM or Philz.
audit13 said:
The phone was running the latest bootloader and modem before flashing a custom ROM? I also recommend using TWRP to flash, not CWM or Philz.
Click to expand...
Click to collapse
Thanks for the reply!
I'm not sure that the Samsung firmware the phone was running was the latest. Didn't think it could make any difference :/
Can you pinpoint me to the correct files?
Oh and will try with TWRP as you told
The latest n7100 firmware is here: https://www.sammobile.com/firmwares/database/GT-N7100/
To find out about the phone's bootloader and modem, you can install the Samsung Phone Info app from the Play Store.
audit13 said:
The latest n7100 firmware is here: https://www.sammobile.com/firmwares/database/GT-N7100/
To find out about the phone's bootloader and modem, you can install the Samsung Phone Info app from the Play Store.
Click to expand...
Click to collapse
Thanks, downloading now.
It's terribly slow, is there any other mirror?
Try this: http://samsung-updates.com/
audit13 said:
Try this: http://samsung-updates.com/
Click to expand...
Click to collapse
Even worse
Update:
Installed the latest n7100 firmware then flashed MIUI 8 through TWRP... Still unknown baseband and no IMEI
Tried to restore EFS and MODEM but no luck.
Same for RR 7.1.1
I'm trying Eclipse now sigh
UPDATE 2:
Eclipse working good at least!
Maybe it's just a bug in MIUI? I'm not sure as I don't have a note 2 to test.
audit13 said:
Maybe it's just a bug in MIUI? I'm not sure as I don't have a note 2 to test.
Click to expand...
Click to collapse
I don't think so, cause I'm having the same problem on RR 7.1 :/
Maybe you need to flash a different kernel? Anyone else in the RR thread mention this issue?
I have spent the past 2 days trying to get a new cfw installed on my phone that didnt have many bugs. I settled with the cyanogenmod13 and read that it was good for a daily driver. At first i installed the wrong gapps and would make the keyboard crash, but now that i figured that out i need help with getting the rom to recognize the sim card. I tryed reflashing with twrp 2.8.6.0 because i read that it would flash the modem correctly, but still no luck. i'm fairly new to flashing and have only done it 3 times in the past. So now i made an account here to ask for help.
Thanks in advance to all the help i get here.
Is the phone running the latest bootloader and modem? You can compare the versions in the phone to sammobile.com.
audit13 said:
Is the phone running the latest bootloader and modem? You can compare the versions in the phone to sammobile.com.
Click to expand...
Click to collapse
Thanks for your rely, Im not 100% sure what you mean by modem as im fairly new to this whole business. I will go to the website to see what i can find. Where can i see that information about the modem i am currently running?
I recommend matching the bootloader and modem version to each other.
You can download the Samsung Phone Info app from the Play Store to learn about the phone.
audit13 said:
I recommend matching the bootloader and modem version to each other.
You can download the Samsung Phone Info app from the Play Store to learn about the phone.
Click to expand...
Click to collapse
Ok I did some research and learned that the modem is the baseband number that shows in the about phone section. This is currently unknown or my guess non existant and that is why the phone says that the sim card is not inserted.
I also learned that i can use ODIN to flash the modem/baseband directly without the need to reflash the whole rom.
I dont know where to find the file online for the modem that matches the rom. I have spent a while looking around and have seen older posts of people saying that they have experienced the same issues after flashing cm13 on n9005 Note 3.
Here is what i am running on my phone:
- Cyanogenmod Version: 13-20151031-UNOFFICIAL-hlte (maybe there is a newer version to this somewhere that has this issue fixed)
- Baseband: Unknown
- Kernal Version: [email protected] #5
- Build Number: 1
-hlte-userdebug 6.0 MRA58K 2127f69904 test-keys
What do you think? And thanks for you help so far. :good:
The simplesting may be this: update TWRP to the latest version. You can flash the img file from TWRP.
Once TWRP has been updated, create a nandroid backup of the existing ROM.
Download the latest ROM from sammobile.com and flash the whole ROM. This is the simplest and safest option IMHO.
After flashing the stock ROM and making sure the sim is recognized and IMEI is correct, use Odin to flash the latest tar version of TWRP , boot into TWRP, restore backup, test your sim.
audit13 said:
The simplesting may be this: update TWRP to the latest version. You can flash the img file from TWRP.
Once TWRP has been updated, create a nandroid backup of the existing ROM.
Download the latest ROM from sammobile.com and flash the whole ROM. This is the simplest and safest option IMHO.
After flashing the stock ROM and making sure the sim is recognized and IMEI is correct, use Odin to flash the latest tar version of TWRP , boot into TWRP, restore backup, test your sim.
Click to expand...
Click to collapse
Ok I will give it a go and let you know what Happens, it will take a while because Here in Ecuador i Have very slow internet. I have to leave the files downloading over night.
Thanks for you help
Wouldnt I be able to flash the modem with odin as long as it matches the phone model? or will that cause problems?
Good luck. I hope it works for your phone.
audit13 said:
The simplesting may be this: update TWRP to the latest version. You can flash the img file from TWRP.
Once TWRP has been updated, create a nandroid backup of the existing ROM.
Download the latest ROM from sammobile.com and flash the whole ROM. This is the simplest and safest option IMHO.
After flashing the stock ROM and making sure the sim is recognized and IMEI is correct, use Odin to flash the latest tar version of TWRP , boot into TWRP, restore backup, test your sim.
Click to expand...
Click to collapse
Tempestelf2 said:
Ok I will give it a go and let you know what Happens, it will take a while because Here in Ecuador i Have very slow internet. I have to leave the files downloading over night.
Thanks for you help
Click to expand...
Click to collapse
Updating to the latest version of TWRP is a bad idea. If you update to version 3.0+ you can't install ROM's that use the AROMA installer. The newer versions of TWRP do not support it. The best version I've found is 2.7.8.0 to be able to handle any flashing.
The biggest problem is the sim card in my opinion.
audit13 said:
The biggest problem is the sim card in my opinion.
Click to expand...
Click to collapse
The sim card works fine in Ecuador, I have used it before flashing to cm13. I found the website of the ones who made the build and noticed that the version that I have downloaded is 1.33 from Oct 31, 2015 and that their latest updates on the channel log is version 12. I will download and flash latest build and she if the issue is fixed.
I was referring to the card bot being recognized in CM, not on a stock ROM. Thanks.