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 all,
I tried to flash CM 11 nightly version on my Galaxy Note 2 but is unable to do so.
When I try to flash, I get an error message that "This package is for device: t03g, n7100, GT-N7100; this device is t03gub"
I am sure that I have downloaded the correct version but from the above message it seems that I am trying to flash different version.
Please help!!! As I have cleared all the cache and memory, I even cannot boot into system. Cleared all the data for flashing the new CM11 but as I cannot flash now, I am stuck with a dead phone which I cannot use.
Please Help!!!!!!!
Flash Stock
Kindly go to www.sammobile.com and download the correct stock firmware for your phone.
Follow the instructions over there on how to flash. Or Google how to flash with Odin.
Once you get your phone live with stock OS you can go for Custom Rom.
As per my opinion DN4 by Electron Team is the best custom ROM.
Thanks for the help...... I did figure it out.... I had the flashed the wrong TWRP file initially and now rectified it.
Was able to install the CM on my phone.
Have a another problem though..... Phone network is not recognized. I mean by default, the mobile network is turned off and when I turn it on manually, it turns off the mobile network automatically.
Not sure how to rectify it..... everything else seem to be working fine.
Please help!!!
Anyone Help please....
The EFS partition is the culprit. I do not get ant IMEI no. on the phone.
Worst part is that I dont have the back-up too....
Any way by which I can bring back the phone to life?
Please help!!!!
Shankar9822 said:
Anyone Help please....
The EFS partition is the culprit. I do not get ant IMEI no. on the phone.
Worst part is that I dont have the back-up too....
Any way by which I can bring back the phone to life?
Please help!!!!
Click to expand...
Click to collapse
Do as @vipsy6 suggested and hope that the efs gets fixed.
erljayp said:
Do as @vipsy6 suggested and hope that the efs gets fixed.
Click to expand...
Click to collapse
Yep... did that and the phone is working fine now...
Thanks for the help.
Shankar9822 said:
Yep... did that and the phone is working fine now...
Thanks for the help.
Click to expand...
Click to collapse
Good to hear.
Just don't forget to do a backup. ^^
erljayp said:
Good to hear.
Just don't forget to do a backup. ^^
Click to expand...
Click to collapse
Sure sir... did it immly...
Shankar9822 said:
Yep... did that and the phone is working fine now...
Thanks for the help.
Click to expand...
Click to collapse
Hi,
did you manage to install the custom ROM or went back to stock only. I faced the same issue and followed this post and installed stock rom from from www.sammobile.com and the phone was up again. I tried to install the custom ROM again but getting the same error. Below i have given the steps i followed. Please help if i am missing something. Please do mention the exact version of twrp recvovery that you used. Giving the link would he helpful.
steps that i followed.
1)installed custom ROM from www.sammobile.com using Odin. Phone was up again.
2)installed twrp-2.8.6.0-t03gub https://dl.twrp.me/t03g/twrp-2.8.6.0-t03gub.img.tar.html using Odin
3)booted into recovery.
4)tried to install the ROM zip from post CyanogenModX [5.1.1_r2] http://forum.xda-developers.com/showthread.php?t=2758963
5)but got the same error.
i have note 2 gt-n7100 t03gub. please help me.
regards
Varun
&kuttan said:
Hi,
did you manage to install the custom ROM or went back to stock only. I faced the same issue and followed this post and installed stock rom from from www.sammobile.com and the phone was up again. I tried to install the custom ROM again but getting the same error. Below i have given the steps i followed. Please help if i am missing something. Please do mention the exact version of twrp recvovery that you used. Giving the link would he helpful.
steps that i followed.
1)installed custom ROM from www.sammobile.com using Odin. Phone was up again.
2)installed twrp-2.8.6.0-t03gub https://dl.twrp.me/t03g/twrp-2.8.6.0-t03gub.img.tar.html using Odin
3)booted into recovery.
4)tried to install the ROM zip from post CyanogenModX [5.1.1_r2] http://forum.xda-developers.com/showthread.php?t=2758963
5)but got the same error.
i have note 2 gt-n7100 t03gub. please help me.
regards
Varun
Click to expand...
Click to collapse
Varun Did you ensure your phone is still rooted ?
Since you Install a stock rom form sams I assue its not Rooted or deodexed coz its stock rom ofcource..
Unless u are rooted you cannot install a good custom rom
Do a CF auto rooting using Odin
Reflash TWRP
Then Enjoy a new Custom rom
Go for DN 4 2.1 with mod v11 :good::good:
I loaded CM-13.0 nightly and have Been updating as the updates come but when I go to make a call it takes forever to go through and start ringing and sometimes it r just hangs up. The data keeps going from LTE to nothing and no SIM . I can't get mms either. Can someone tell me what to do.thanks.
Sent from my SGH-T999 using Tapatalk
HUCCG said:
I loaded CM-13.0 nightly and have Been updating as the updates come but when I go to make a call it takes forever to go through and start ringing and sometimes it r just hangs up. The data keeps going from LTE to nothing and no SIM . I can't get mms either. Can someone tell me what to do.thanks.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Same thing is happening to me. I've tried using OctOs M and now I am on PacRom 6.0.1 and I am having the same "No sim card" error. I can text and call, but no Data whatsoever.
Have you tried changing your APN settings for your network on your phone?
wmzed said:
Same thing is happening to me. I've tried using OctOs M and now I am on PacRom 6.0.1 and I am having the same "No sim card" error. I can text and call, but no Data whatsoever.
Have you tried changing your APN settings for your network on your phone?
Click to expand...
Click to collapse
are you on the latest baseband for your phone?
ratchetrizzo said:
are you on the latest baseband for your phone?
Click to expand...
Click to collapse
My stock OS Is 4.1.2 and is running Baseband UVAMB7. Do I need to go for the higher updates for the LTE to work?
wmzed said:
My stock OS Is 4.1.2 and is running Baseband UVAMB7. Do I need to go for the higher updates for the LTE to work?
Click to expand...
Click to collapse
I think you need to be on UVUBOH1.
https://forum.xda-developers.com/showthread.php?t=1949687 has the list of FW and it looks like you are using a super super old baseband.
ratchetrizzo said:
I think you need to be on UVUBOH1.
https://forum.xda-developers.com/showthread.php?t=1949687 has the list of FW and it looks like you are using a super super old baseband.
Click to expand...
Click to collapse
Do I need to use ODIN for this? I tried installing UVUBOH1 with TWRP, but I get an error when I installing it:
"could not find 'META-INF/com/google/android/update-binary' in the zip file"
wmzed said:
Do I need to use ODIN for this? I tried installing UVUBOH1 with TWRP, but I get an error when I installing it:
"could not find 'META-INF/com/google/android/update-binary' in the zip file"
Click to expand...
Click to collapse
Yes, download https://www.androidfilehost.com/?fid=24052804347821137
NOTE, if you click on "UVUBOH1" and not the androidfilehost link in the FW thread, it links you to the wrong FW and you'll flash UVUBNC1! Make sure you click the androidfilehost link underneath UVUB0H1.
Then flash it with odin.
Afterwards let it reboot and upgrade, then odin TWRP back and either restore a nandroid or flash the rom of your choosing
Oh also, if you're still on 4.1 and on a touchwiz rom, you may want to factory unlock it before you upgrade.. Just because you can. Follow the unlock thread on here
ratchetrizzo said:
Yes, download https://www.androidfilehost.com/?fid=24052804347821137
NOTE, if you click on "UVUBOH1" and not the androidfilehost link in the FW thread, it links you to the wrong FW and you'll flash UVUBNC1! Make sure you click the androidfilehost link underneath UVUB0H1.
Then flash it with odin.
Afterwards let it reboot and upgrade, then odin TWRP back and either restore a nandroid or flash the rom of your choosing
Oh also, if you're still on 4.1 and on a touchwiz rom, you may want to factory unlock it before you upgrade.. Just because you can. Follow the unlock thread on here
Click to expand...
Click to collapse
Thank you so much! I will try this out soon and respond with the results! And I had already unlocked my device :. I had to root and use the RegionLock app to unlock it, as the *#197328640# menu option did not work for me.
wmzed said:
Thank you so much! I will try this out soon and respond with the results! And I had already unlocked my device :. I had to root and use the RegionLock app to unlock it, as the *#197328640# menu option did not work for me.
Click to expand...
Click to collapse
how did you make out?
ratchetrizzo said:
how did you make out?
Click to expand...
Click to collapse
Was quite a bit of trouble at first . I managed to download and flash the software. flashed TWRP via odin.
Then through TWRP, I rooted by using the Knox remover zip (as i was on official 4.3, my service signal did shoot up to normal again!). Installed SuperSU.
Now when I try to flash any ROM via TWRP it gives errors such as "Status 7", or error reading MD5 when I try to backup software.
wmzed said:
Was quite a bit of trouble at first . I managed to download and flash the software. flashed TWRP via odin.
Then through TWRP, I rooted by using the Knox remover zip (as i was on official 4.3, my service signal did shoot up to normal again!). Installed SuperSU.
Now when I try to flash any ROM via TWRP it gives errors such as "Status 7", or error reading MD5 when I try to backup software.
Click to expand...
Click to collapse
Make sure twrp is up to date for d2tmo, and make sure the rom you are flashing is 4.3 or later. I'm pretty sure that once you're on the latest 4.3 rom you can't flash anything lower
ratchetrizzo said:
Make sure twrp is up to date for d2tmo, and make sure the rom you are flashing is 4.3 or later. I'm pretty sure that once you're on the latest 4.3 rom you can't flash anything lower
Click to expand...
Click to collapse
Got the latest TWRP running, but still the same issue trying to flash OctOS M, PACROM 5.0.1, etc.
wmzed said:
Got the latest TWRP running, but still the same issue trying to flash OctOS M, PACROM 5.0.1, etc.
Click to expand...
Click to collapse
That's strange, I'm using 3.0.2.0 and the latest 999L baseband and I haven't had any issues with flashing.
I'm Using the MM pac rom but I've tried CM14.1 nightly builds with no problem
ratchetrizzo said:
That's strange, I'm using 3.0.2.0 and the latest 999L baseband and I haven't had any issues with flashing.
I'm Using the MM pac rom but I've tried CM14.1 nightly builds with no problem
Click to expand...
Click to collapse
I have finally managed to figure it out. You need to completely format the entire ROM currently installed from your phone. Once that is done, you can add any ROM to install properly. I'm running well on OctOS-N 3/17/2017 build.
Thanks all for your help.
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.