Related
Hi guys!
I hope that I chose the right forum to ask my question: I installed this rom onto my Note 2 LTE N7105, but now I don't have wifi (as the text in the rom description says). Before I flashed the rom, I had installed Devils Rom (deodexed and deknoxed 4.3 stock) with the devils kernel (based on MK5). I thought that the bootloader will be kept, because I already installed a wifi hotfix for that bootloader.
Now I have the new 4.4 rom installed, it works fine - except for wifi. If I got this right (if not, correct me) - flashing the MJ5 bootloader will solve the problem and I won't have KNOX triggered (now I have a "MA5" bootloader). So I tried to flash the MJ5 bootloader with ODIN 3.09 but it keeps failing. The drivers are installed, I can access the download menu. My pc recognizes the phone as COM5, but when I load the bootloader and click on flash, almost instantly a red FAIL appears in the first block. The output says "writing NAND..." and then "FAILED".
Now I am a bit confused - does the MJ5 bootloader work with the Note 2 LTE or only the non- LTE version? Are there any other ways to get wifi to work? If there's now way around, I am willing to trigger my knox.
Thanks in advance, I hope you can help a very confused user
Im having the same problems. odin is giving no love on updating the bootloader
Kenny_ken said:
Hi guys!
I hope that I chose the right forum to ask my question: I installed this rom onto my Note 2 LTE N7105, but now I don't have wifi (as the text in the rom description says). Before I flashed the rom, I had installed Devils Rom (deodexed and deknoxed 4.3 stock) with the devils kernel (based on MK5). I thought that the bootloader will be kept, because I already installed a wifi hotfix for that bootloader.
Now I have the new 4.4 rom installed, it works fine - except for wifi. If I got this right (if not, correct me) - flashing the MJ5 bootloader will solve the problem and I won't have KNOX triggered (now I have a "MA5" bootloader). So I tried to flash the MJ5 bootloader with ODIN 3.09 but it keeps failing. The drivers are installed, I can access the download menu. My pc recognizes the phone as COM5, but when I load the bootloader and click on flash, almost instantly a red FAIL appears in the first block. The output says "writing NAND..." and then "FAILED".
Now I am a bit confused - does the MJ5 bootloader work with the Note 2 LTE or only the non- LTE version? Are there any other ways to get wifi to work? If there's now way around, I am willing to trigger my knox.
Thanks in advance, I hope you can help a very confused user
Click to expand...
Click to collapse
Did you try to flash the kernel as stated in the installation instructions of the rom that your trying to install?
I have the agni kernel as it is the only way to get the wifi to work without the bootloader, which im trying to get too. For the life of me i cannot figure out why odin doesnt want to flash the bootloader. mj5 or nd3 makes no difference. according to info app my boot loader version is N7105ZHALJ4. Do I need to step up 'slower'?
I want to go to any of those recent bootloaders so wifi will work normally. It seems slow on the agni kernel but at least it works.
TeamFox said:
I have the agni kernel as it is the only way to get the wifi to work without the bootloader, which im trying to get too. For the life of me i cannot figure out why odin doesnt want to flash the bootloader. mj5 or nd3 makes no difference. according to info app my boot loader version is N7105ZHALJ4. Do I need to step up 'slower'?
I want to go to any of those recent bootloaders so wifi will work normally. It seems slow on the agni kernel but at least it works.
Click to expand...
Click to collapse
AFAIK you can't install Agni Kernel using Odin. Instead use your Custom Recovery to install that kernel, under "Install Zip from Storage" option of your custom recovery. HTH.
asin_punk said:
AFAIK you can't install Agni Kernel using Odin. Instead use your Custom Recovery to install that kernel, under "Install Zip from Storage" option of your custom recovery. HTH.
Click to expand...
Click to collapse
To clear things up i have already got agni kernel installed via recovery. I just cant update my bootloader via odin.
problem flashing mj5 bootloader and agni kernel too
i am on phoenix rom v18.8
cannot figure out if i am on mj5 bootloader
how to check my bootloader version?
secondly, i m trying to flash mj5 via odin but it says FAILED
Trying to flash agni kernel via odin and mobile odin,, it says success but when i check in my phone, nothing is done...
where am i going wrong?
pls help
anandsaurabh said:
i am on phoenix rom v18.8
cannot figure out if i am on mj5 bootloader
how to check my bootloader version?
secondly, i m trying to flash mj5 via odin but it says FAILED
Trying to flash agni kernel via odin and mobile odin,, it says success but when i check in my phone, nothing is done...
where am i going wrong?
pls help
Click to expand...
Click to collapse
Agni kernel is only flashable via recovery not with odin.. Its a zip file.. U can flash it using CWM or Philz Or twrp recoveries
Sent from my GT-N7100 using XDA Premium 4 mobile app
U r right hazin ... That file can be flashed only via recovery... But I m not able to flash it.. It goes into aroma installer, does its work and says done but does not show on settings... I e saved log file too of that process...
So no answer on this question yet?? I'm also trying to flash the MJ5 bootloader using Odin, no luck though.
Can anyone explain why it keeps failing?
did you fix the problem ?
apuntigam said:
So no answer on this question yet?? I'm also trying to flash the MJ5 bootloader using Odin, no luck though.
Can anyone explain why it keeps failing?
Click to expand...
Click to collapse
having the same thing now...
Davids said:
having the same thing now...
Click to expand...
Click to collapse
No, I never managed to fix it. I think I found out in the end that there never was an MJ5 bootloader for the GT-N7105 (the international LTE version). There was only an MJ5 bootloader for the non-LTE version, the GT-N7100. And of course, that phone's bootloader will never work on the N7105.
So we're out of luck it appears
so the phone is dead ?
apuntigam said:
No, I never managed to fix it. I think I found out in the end that there never was an MJ5 bootloader for the GT-N7105 (the international LTE version). There was only an MJ5 bootloader for the non-LTE version, the GT-N7100. And of course, that phone's bootloader will never work on the N7105.
So we're out of luck it appears
Click to expand...
Click to collapse
noting to do to bring back wifi&BT ?
Davids said:
noting to do to bring back wifi&BT ?
Click to expand...
Click to collapse
All of the new KitKat ROMs have fixes built in for that. Some of the Lollipop ROMs also fix this, so you don't really need that bootloader.
apuntigam said:
All of the new KitKat ROMs have fixes built in for that. Some of the Lollipop ROMs also fix this, so you don't really need that bootloader.
Click to expand...
Click to collapse
can you give me a link pls for somthing that works ?
i am Desperate a week with no wifi BT
THX
Davids said:
can you give me a link pls for somthing that works ?
i am Desperate a week with no wifi BT
THX
Click to expand...
Click to collapse
I'm on NamelessROM 5.0.2 at the moment, works fine for me. I'd probably recommend that one, battery life is also great. It's in the N7105 development forum. :good:
I was also on CM11 official, worked like a charm. There are a number of 4.4.4 ROMs in the N7105 development forum that were quite mature and worked well.
apuntigam said:
I'm on NamelessROM 5.0.2 at the moment, works fine for me. I'd probably recommend that one, battery life is also great. It's in the N7105 development forum. :good:
I was also on CM11 official, worked like a charm. There are a number of 4.4.4 ROMs in the N7105 development forum that were quite mature and worked well.
Click to expand...
Click to collapse
i have the 7100..
somthing for that device..
Davids said:
i have the 7100..
somthing for that device..
Click to expand...
Click to collapse
Ok, then it's a completely different discussion... not sure why the bootloader would be failing in that case, since it was built for that device. You could try a different Odin? (Assuming of course that your are NOT trying to DOWNGRADE the bootloader... it's well known that you can't downgrade the bootloarder to MJ5 from something more recent).
Otherwise, I'm sure there are equally useful ROMs for the N7100 in the Note 2 Original Development forum.
But, since your device is probably pretty old and almost certainly out of warranty by now, I would seriously consider flashing the latest official Samsung ROM to get the latest bootloader and then flash whatever you want on top of that. Voiding the warranty is irrelevant if you're already out of warranty. But, I have heard that even with the latest bootloader some people still have trouble with wifi and BT. In that case all I can suggest is playing around with different ROMs until you find something that works for you. As I'm not a N7100 user I can't really offer more advice than that, sorry man.
Guys where I can find a REAL WORKING link to download mj5 or higher bootloader??
I tried a lot & most of them are obselete
Maybe downnload the latest stock ROM from sammobile.com and extract the bootloader?
https://www.sammobile.com/firmwares/database/GT-N7105/
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
Hello, I used to be rooted with custom ROMs ect but went back to stock I317ATTALJ2 so I can give the phone to my daughter. Well everything went smooth until an update from AT&T came through and she ran it when the battery was at 21% but I'm not sure it that matter but didn't help in matters... Anyhow it ran the upgrade and on reboot it stayed on the Galaxy Note II screen and wont do anything but sit there. I let it sit for a long time before pulling the battery and booting but it goes to same screen and same thing. I can not get into recovery (Volume Up, Home, Pwr) but I can go into download mode. With the battery being so low I read that it charges while in download mode so for the remainder of the day I put the phone in download mode and plugged into charger.
Suggestions?
After you get it charged up some and you're in download mode. Just Odin back to stock Att firmware should fix the problem hopefully...
You can find the stock firmware here>> http://bit.ly/1HNVFVJ
Guess the phone didn't like that update ?.
Bajanman said:
After you get it charged up some and you're in download mode. Just Odin back to stock Att firmware should fix the problem hopefully...
You can find the stock firmware here>> http://bit.ly/1HNVFVJ
Guess the phone didn't like that update .
Click to expand...
Click to collapse
Ok, Ill give the stock firmware (At&t Firmware I317UCALJ2 Uploaded By-Bajanman) that Bajanman supplys ill let you guys know in an hour or two its downloading now. I did try re installing the stock firmware I had that worked the first time and it was from SamMobile and it too sent me to the Galaxy Note II screen and froze so its not looking good.....
Thanks!
Oxicottin said:
Ok, Ill give the stock firmware (At&t Firmware I317UCALJ2 Uploaded By-Bajanman) that Bajanman supplys ill let you guys know in an hour or two its downloading now. I did try re installing the stock firmware I had that worked the first time and it was from SamMobile and it too sent me to the Galaxy Note II screen and froze so its not looking good.....
Thanks!
Click to expand...
Click to collapse
Ok.
Hopefully everything works out next time around.
Another thing you could try is flashing which ever recovery you previously had installed. Last time I was having issues with something similar, after re flashing my recovery everything started working again. Just just a thought that might work.
I'm monitoring this thread too see what happens ok.
Bajanman said:
Ok.
Hopefully everything works out next time around.
Another thing you could try is flashing which ever recovery you previously had installed. Last time I was having issues with something similar, after re flashing my recovery everything started working again. Just just a thought that might work.
I'm monitoring this thread too see what happens ok.
Click to expand...
Click to collapse
Recovery? can I flash the stock recovery using ODIN? If so where do I get it.... I always have used TWRP I wanted to use custom ROMs never really experimented with anything else.
Oxicottin said:
Recovery? can I flash the stock recovery using ODIN? If so where do I get it.... I always have used TWRP I wanted to use custom ROMs never really experimented with anything else.
Click to expand...
Click to collapse
Yes you can flash a custom recovery from Odin. You just have to use the (Twrp) tar file found here>>>
http://bit.ly/1y0Tyg7
Find your device model and download the tar. And make sure you're downloading the correct file for your device ok!
I to use Twrp and luv it.?
OK, well its not looking good....
1) Flashed the stock firmware suggested...... Still get same results!
2) Flashed TWRP through ODIN and it made it to the same screen and froze. Did a battery pull and button combo and it wont go into recovery.
Is there a application that will force your phone into recovery and download modes? I remember back when I messed with the captivate there was a application someone built that did such a thing.
Any suggestions?
Oxicottin said:
OK, well its not looking good....
1) Flashed the stock firmware suggested...... Still get same results!
2) Flashed TWRP through ODIN and it made it to the same screen and froze. Did a battery pull and button combo and it wont go into recovery.
Is there a application that will force your phone into recovery and download modes? I remember back when I messed with the captivate there was a application someone built that did such a thing.
Any suggestions?
Click to expand...
Click to collapse
Not sure you were on the newer 4.4.2 bootloader or not. If it was on a newer bootloader then you won't be able to downgrade.. This might help you get the phone working again since you just flashed the original firmware.
Go to this thread here>>http://forum.xda-developers.com/showthread.php?t=2502464.
Download
4.3 Param.bin and Tz.img
http://d-h.st/OYC
Step 2 (no bootloader in here)
flash this to bring wifi back
but keep your knox free 4.1.2 bootloader.
Allowing you to freely flash between 4.1.2 roms and the latest 4.3 leak
Without having to one click,Keeping Wifi Throughout and removing Knox
Click to expand...
Click to collapse
Unzip, Boot into Download mode, Open ODIN, put tar file in PDS slot, click Start.
Then you can go here for the latest stock Att firmware. If the above steps don't help you, then you could try flashing one one the rooted stock packages from this thread.
Bajanman said:
Not sure you were on the newer 4.4.2 bootloader or not. If it was on a newer bootloader then you won't be able to downgrade.. This might help you get the phone working again since you just flashed the original firmware.
Go to this thread here>>http://forum.xda-developers.com/showthread.php?t=2502464.
Download
4.3 Param.bin and Tz.img
http://d-h.st/OYC
Unzip, Boot into Download mode, Open ODIN, put tar file in PDS slot, click Start.
Then you can go here for the latest stock Att firmware. If the above steps don't help you, then you could try flashing one one the rooted stock packages from this thread.
Click to expand...
Click to collapse
Ok that worked and it booted!!!! Now im on 4.1.1 with TWRP
Not really sure what I just did? Did I downgrade my bootloader? Also, now how do I get it to the most up to date version without this again?
I downloaded an app and it says im on.....
Bootloader Version: 1317UCUBMK6
Thanks!
Oxicottin said:
Ok that worked and it booted!!!! Now im on 4.1.1 with TWRP
Not really sure what I just did? Did I downgrade my bootloader? Also, now how do I get it to the most up to date version without this again?
Thanks!
Click to expand...
Click to collapse
Ok not is back working again, which is great news ?. Go to the link I posted for the stock firmware, and use the rooted one.
But first make a backup of your working system first ok.
Bajanman said:
Ok not is back working again, which is great news . Go to the link I posted for the stock firmware, and use the rooted one.
But first make a backup of your working system first ok.
Click to expand...
Click to collapse
Ok, Im On 4.3 now and its working great.... Thank You!
Oxicottin said:
Ok, Im On 4.3 now and its working great.... Thank You!
Click to expand...
Click to collapse
You're very welcome glad I could help fix it.
Have a good day...
Ok problem solved so unsubscribing from this thread. If you run into any other problems you can always hit me up thru pm ?.
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
After updating my bootloader to NE2 using odin, by phone just keeps and booting up to the Samsung Galaxy logo and restarting. The logo appears for a second or so before restarting. I can access download mode, but receive the following:
ODIN MODE
PRODUCT NAME: GT-N7100
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
AP SWREV: A2
RPMB: INVALID RPMB DATA
( the last three lines have appeared, and were not there previously before updating the bootloader). The phone was working fine with stock 4.4.2, before installing the bootloader. I cannot access recovery mode, and have flashed TWRP with odin (reported success in odin), but cannot access the TWRP recovery menu on my phone. I have tried to flash stock 4.4.2 again with odin, I do not receive any errors and receive a success 1 in odin where a blue bar is visible (when flashing) on the screen of my phone. But after the phone restarts, i experience the same bootloop problem. Help would be greatly appreciated.
Open Odin, uncheck everything, flash latest stock ROM from sammobile (https://www.sammobile.com/firmwares/database/GT-N7100/), you'll see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery using volume up+power+home, factory wipe, reboot.
audit13 said:
Open Odin, uncheck everything, flash latest stock ROM from sammobile, you'll see the word "reset" in the status window, remove USB cable from the phone, remove battery, replace battery, boot into recovery using volume up+power+home, factory wipe, reboot.
Click to expand...
Click to collapse
Before proceeding, I'd like to ask:
1 - I have a motherboard that I've obtained from China. Would it be ok for me to flash as you've recommended with this motherboard, taking into account the "RPMB: INVALID RPMB DATA" message that appears in download mode ?
2 - Can I install any of the latest firmwares available on sammobile for my galaxy note 2 ?
3 - Would I be able to install TWRP and custom roms after ?
Thanks
1) The important thing is to match the model # to the firmware. If you try to flash firmware from sammobile and it is not the correct firmware, Odin will stop the flash process. As of right now, this seems to be the safest method to get the phone working.
2) See my response to question 1.
3) Yes, you can install TWRP and custom ROMs either before or after flashing a stock ROM. I recommend getting the phone to work with a stcok ROM before trying custom ROMs.
audit13 said:
1) The important thing is to match the model # to the firmware. If you try to flash firmware from sammobile and it is not the correct firmware, Odin will stop the flash process. As of right now, this seems to be the safest method to get the phone working.
2) See my response to question 1.
3) Yes, you can install TWRP and custom ROMs either before or after flashing a stock ROM. I recommend getting the phone to work with a stcok ROM before trying custom ROMs.
Click to expand...
Click to collapse
After flashing the N7100XXUFOC2 firmware with all boxes unchecked in odin, i still receive a bootloop, and the phone is not entering recovery :-/. The messages that appear in download mode have remained unchanged.
It's flashing properly with no error? When you try to enter recovery, what shows on screen? Did you try any other firmware? I see there is PE2 firmware too.
audit13 said:
It's flashing properly with no error? When you try to enter recovery, what shows on screen? Did you try any other firmware? I see there is PE2 firmware too.
Click to expand...
Click to collapse
Yes it flashes with no errors. When turning the phone on, the samsung galaxy note 2 logo appears for just under a second, and the phone restarts and repeats until i remove the battery. Nothing happens when I try to enter the recovery menu, the same behaviour is observed (phone restarting constantly after showing SGnote2 logo). I have been reading around, and i suspect (just a guess, not sure) that the "RPMB: INVALID RPMB DATA" message that I observe in download mode may have something to do with this.
You may have to have it fixed at a cell repair shop. They may be able to fix it via jtag cable or maybe with an Octopus box.
audit13 said:
You may have to have it fixed at a cell repair shop. They may be able to fix it via jtag cable or maybe with an Octopus box.
Click to expand...
Click to collapse
Is there anything else that i could try ? I used an app to check the bootloader version when it was working on stock 4.4.2, and it stated that it was at LJ7. After updating the bootloader to NE1, I've experienced this problem. Would it be possible to revert back to the previous bootloader ( and would this help ?). I've flashed custom roms with no problems, beforehand using TWRP.
How did you update the bootloader? Did you update the bootlaoder without updating anything else?
audit13 said:
How did you update the bootloader?
Click to expand...
Click to collapse
I downloaded the NE1 bootloader from a user here who has a list of bootloaders on his profile (user: Androidwizzard), and flashed it using Odin v3.09 with the default boxes checked. I did not update anything else ( just clicked the "BL" field and selected the bootloader, then flashed).
Are you sure the bootloader was for your phone? I know that updating the bootloader without updating anything else on the Samsung s3 can cause the phone to hard or soft brick.
audit13 said:
Are you sure the bootloader was for your phone? I know that updating the bootloader without updating anything else on the Samsung s3 can cause the phone to hard or soft brick.
Click to expand...
Click to collapse
Yeah. Would it be possible to revert the bootloader back to what it was previously ? Also, is there anything else that you may suggest that i could do ? I'm still not sure what is causing this issue exactly. It seems strange that I can flash all files with no errors using Odin. By flashing a later firmware, is the bootloader automatically updated ? ( if yes, then I'm not sure why the app stated that my bootloader version was at LJ7, given that I've flashed stock 4.4.2 with odin beforehand.)
Do you have a link for the bootloader?
Did the phone work properly before flashing the new NE1 bootloader?
Did you try flashing the latest ROM, regardless of the country from sammobile? Something newer than ne1?
audit13 said:
Do you have a link for the bootloader?
Did you try flashing the latest ROM, regardless of the country from sammobile? Something newer than ne1?
Click to expand...
Click to collapse
I have not tried flashing the latest rom ( I could try, if that may help). I can not provide the direct link to the bootloader, since i will have to produce 10 posts ( new user here lol ). You can find the bootloader by searching google: [bootloader/modem/rom][tw kitkat][4.4.2][pf1 + pc1 + oe1 + od4 + nl1 +], then going to Androidwizzard second post.
The phone was working great before flashing the NE1 bootloader. As mentioned previously, I've flashed the N7100XXUFOC2 firmware resulting in no change.
Try flashing the latest ROM PF1 ROM as that may help.
I think updating the bootloader without updating other parts of the ROM may have caused the problem but I don't know for sure.
If flashing the latest ROM does not work, try flashing the latest ROM with a pit file. If that still doesn't work, you may have to have it force flashed at a cell shop.
audit13 said:
Try flashing the latest ROM PF1 ROM as that may help.
I think updating the bootloader without updating other parts of the ROM may have caused the problem but I don't know for sure.
If flashing the latest ROM does not work, try flashing the latest ROM with a pit file. If that still doesn't work, you may have to have it force flashed at a cell shop.
Click to expand...
Click to collapse
I will give it a go right now. Would you be able to guide me to where I could obtain the appropriate pit file for the phone ? The firmwares with PF1 have (orange) carrier. Would this affect things ?
Is your phone a 16 GB or 32 GB model?
It should not matter at this point because you want to get the phone booted. Once booted, you should be able to change the carrier later.
audit13 said:
Is your phone a 16 GB or 32 GB model?
It should not matter at this point because you want to get the phone booted. Once booted, you should be able to change the carrier later.
Click to expand...
Click to collapse
16 GB model. Alright, I'll try to flash the latest rom.