Related
Hi,
Have a Note II as an alternative phone. Apparently, the phone worked correctly until last month. It started to reboot, not too much, but it happened. Well, I tried to give a solution changing the ROM (when it started with the problem I was in 4.4.2 OmniROM). My first try was with Omega ROM, cause it was my first custom ROM when I bought the phone with 4.1.2 in, but the problem persist (maybe increment the number of reboots-freezes/day) so I changed it again to Android Revolution HD, but it only increment the reboots/freezes.
It seems that it's not a ROM installation problem or something like that, maybe it's a hardware problem, but I would like to hear your opinions about it.
Now the phone have:
TWRP recovery
Rooted
Android Revolution HD
I am thinking on put the stock ROM and bootloader with Odin. What do you think?
Thanks!
Could you enter recovery, format /system /data /cache and flash clean Omni > reboot >reboot to recovery >flash Gapps> reboot and observe without installing any apps. Until it freezes or reboots anyway.
My dad also has note 2,he had the same problem on many different roms.
He had to give it back to repair. They've replaced power button and something else, after that the phone seems normal.
Sent from galaxy n7105
mat9v said:
Could you enter recovery, format /system /data /cache and flash clean Omni > reboot >reboot to recovery >flash Gapps> reboot and observe without installing any apps. Until it freezes or reboots anyway.
Click to expand...
Click to collapse
Hi mat9v,
Thanks for your reply. I am in the office now, but I will try it as soon as I can. I thought on your suggestion too, so I will give a chance .
In case of it does not working, if I restore to stock ROM, will it restore the bootloader and recovery automatically too?
My actual bootloader if I am not wrong, is MJ5 bootloader (to fix the WiFi problems with custom ROMs in 4.3).
Thanks!
Edit:
jakuburban said:
My dad also has note 2,he had the same problem on many different roms.
He had to give it back to repair. They've replaced power button and something else, after that the phone seems normal.
Sent from galaxy n7105
Click to expand...
Click to collapse
Did you repair it even with custom ROM? Samsung does not accept it, right? Anyway, my phone is not in guarantee time.
Thanks!
Nah, of course I restored it to official 4.1.2 so everything was like new.
If You don't have guarantee, not good
Sent from galaxy n7105
pep0te said:
Hi mat9v,
Thanks for your reply. I am in the office now, but I will try it as soon as I can. I thought on your suggestion too, so I will give a chance .
In case of it does not working, if I restore to stock ROM, will it restore the bootloader and recovery automatically too?
My actual bootloader if I am not wrong, is MJ5 bootloader (to fix the WiFi problems with custom ROMs in 4.3).
Thanks!
Click to expand...
Click to collapse
Yes, it will overwrite both bootloader and recovery, unroot and so on. Be careful with KNOX and look for TriangleAway to reset flash status to factory.
jakuburban said:
Nah, of course I restored it to official 4.1.2 so everything was like new.
If You don't have guarantee, not good
Sent from galaxy n7105
Click to expand...
Click to collapse
Hope I can fix it by other way then . Thanks!
mat9v said:
Yes, it will overwrite both bootloader and recovery, unroot and so on. Be careful with KNOX and look for TriangleAway to reset flash status to factory.
Click to expand...
Click to collapse
Hm, could you explain me a bit? Sorry if my question is stupid.
Thanks a lot.
pep0te said:
Hope I can fix it by other way then . Thanks!
Hm, could you explain me a bit? Sorry if my question is stupid.
Thanks a lot.
Click to expand...
Click to collapse
If you want to return the phone to service center you mast be careful to maintain KNOX status 0 and Software status: Factory or they may refuse to fix the phone (warranty void by messing with software) - it's not such a big deal here in Europe but in US there are some stupid rules like that. So long as you remain on MJ5 bootloader you should have no problem with KNOX when you flash Samsung firmware but Firmware status: Modified vs Factory require using TriangleAway program to reset specific counters. Find it on Playstore and follow the link there to explanation on how to proceed.
mat9v said:
If you want to return the phone to service center you mast be careful to maintain KNOX status 0 and Software status: Factory or they may refuse to fix the phone (warranty void by messing with software) - it's not such a big deal here in Europe but in US there are some stupid rules like that. So long as you remain on MJ5 bootloader you should have no problem with KNOX when you flash Samsung firmware but Firmware status: Modified vs Factory require using TriangleAway program to reset specific counters. Find it on Playstore and follow the link there to explanation on how to proceed.
Click to expand...
Click to collapse
Hi mat9v,
Just fyi, I am from Europe . So this mean that I should check if Firmware status is "Modified" or "Factory" and KNOX = 0. In case of it is "Modified" (most probably right?) or KNOX = 1 or more, I must use TriangleAway to reset the counters.
That's okay, thank you all for your help . I will try and give my feedback asap!
pep0te said:
Hi mat9v,
Just fyi, I am from Europe . So this mean that I should check if Firmware status is "Modified" or "Factory" and KNOX = 0. In case of it is "Modified" (most probably right?) or KNOX = 1 or more, I must use TriangleAway to reset the counters.
That's okay, thank you all for your help . I will try and give my feedback asap!
Click to expand...
Click to collapse
You can't reset KNOX counter if you are on a bootloader newer than MJ5 (it's been tested that on MJ5 you can deal with it by flashing earlier firmware along with older bootloader). More info HERE
mat9v said:
You can't reset KNOX counter if you are on a bootloader newer than MJ5 (it's been tested that on MJ5 you can deal with it by flashing earlier firmware along with older bootloader). More info HERE
Click to expand...
Click to collapse
How can I check my bootloader? I am almost sure that is MJ5 but... better to check.
Thanks!
Edit:
The stock ROM I should install is the 4.3 I choose in sammobile, right? Spain country in my case.
http://www.sammobile.com/firmwares/3/?download=23362
Thank you.
pep0te said:
How can I check my bootloader? I am almost sure that is MJ5 but... better to check.
Thanks!
Edit:
The stock ROM I should install is the 4.3 I choose in sammobile, right? Spain country in my case.
http://www.sammobile.com/firmwares/3/?download=23362
Thank you.
Click to expand...
Click to collapse
To check bootloader install "Info" by Nag from Playstore and look in OS category.
Yes, but it will flash bootloader newer than MJ5 I think (MJ9 if my memory serves me right) and you may not be able to set KNOX to 0. Also you must play with TriangleAway before flashing stock 4.3 because it does not work on stock (root required).
Since you are in Europe, it should not matter too much (according to European law) so if someone makes any heat just say that it a law
mat9v said:
To check bootloader install "Info" by Nag from Playstore and look in OS category.
Yes, but it will flash bootloader newer than MJ5 I think (MJ9 if my memory serves me right) and you may not be able to set KNOX to 0. Also you must play with TriangleAway before flashing stock 4.3 because it does not work on stock (root required).
Since you are in Europe, it should not matter too much (according to European law) so if someone makes any heat just say that it a law
Click to expand...
Click to collapse
Amazing, alright now. Hope I can fix this usual problem...
Thanks for your complete and helpful answers!
mat9v said:
To check bootloader install "Info" by Nag from Playstore and look in OS category.
Yes, but it will flash bootloader newer than MJ5 I think (MJ9 if my memory serves me right) and you may not be able to set KNOX to 0. Also you must play with TriangleAway before flashing stock 4.3 because it does not work on stock (root required).
Since you are in Europe, it should not matter too much (according to European law) so if someone makes any heat just say that it a law
Click to expand...
Click to collapse
Hi again,
My bootloader (Info app) is:
Bootloader: N7100XXDLL7
I think this is the old (4.1.2) right?
Sent from my Nexus 5 using xda app-developers app
pep0te said:
Hi again,
My bootloader (Info app) is:
Bootloader: N7100XXDLL7
I think this is the old (4.1.2) right?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Yes, and it is probably the reason for Android Revolution problems. If I remember correctly it is a 4.3 rom and they have compatibility problems with older bootloaders - the results are random reboots and freezes (there is a lot about it in Phoenix rom thread). To comfortably use TW 4.3 rom it's best to update bootloader to MJ5. AOSP roms should not be affected though so I suppose that there was some other cause for this. You can flash 4.1.2 on this bootloader without issue, be mindful to safeguard data from your internal sdcard as you may loose them all.
I would advise testing standard 4.1.2 version and if everything works fine, flashing something new (with MJ5 bootloader for compatibility sake).
mat9v said:
Yes, and it is probably the reason for Android Revolution problems. If I remember correctly it is a 4.3 rom and they have compatibility problems with older bootloaders - the results are random reboots and freezes (there is a lot about it in Phoenix rom thread). To comfortably use TW 4.3 rom it's best to update bootloader to MJ5. AOSP roms should not be affected though so I suppose that there was some other cause for this. You can flash 4.1.2 on this bootloader without issue, be mindful to safeguard data from your internal sdcard as you may loose them all.
I would advise testing standard 4.1.2 version and if everything works fine, flashing something new (with MJ5 bootloader for compatibility sake).
Click to expand...
Click to collapse
Thanks. You suggest to flash 4.1.2 stock from sammobile right? I mean, it should install the same bootloader that I have now.
Thanks again!
Sent from my Nexus 5 using xda app-developers app
pep0te said:
Thanks. You suggest to flash 4.1.2 stock from sammobile right? I mean, it should install the same bootloader that I have now.
Thanks again!
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Yes, exactly.
mat9v said:
Yes, exactly.
Click to expand...
Click to collapse
Okay, I will do it then. Thanks a lot! :fingers-crossed:
mat9v said:
Yes, exactly.
Click to expand...
Click to collapse
Hey mat9v,
I am trying to reset the counter but it still shows "1" (before this, it showed "7"). Do you know why can't get to fully reset it?
Thanks!
pep0te said:
Hey mat9v,
I am trying to reset the counter but it still shows "1" (before this, it showed "7"). Do you know why can't get to fully reset it?
Thanks!
Click to expand...
Click to collapse
To fully reset the counter it has to be done in certain order. I do not remember exactly in which order the sequence of events should proceed but it went something like this:
- run triangle away
- reboot
- enter download mode (odin version)
- flash stock rom
If you reboot even once to custom rom (this I'm certain) or even custom recovery (I think) the triangle away effect will be gone and the count returns to 1 because it detects custom rom/kernel.
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/
I updated my phone to kitkat using the OTA update while rooted, which was definitely a stupid thing to do, but now my phone seems to be stuck on the ATT splash screen after booting. It's been this way for 15+ minutes. Any way to reset it/unbrick it?
I am able to get into recovery mode and download mode.
Try a factory reset in recovery?
pre4speed said:
Try a factory reset in recovery?
Click to expand...
Click to collapse
I tried this and nothing changed. Would a flash back to 4.3 stock fix the problem?
cfsharp said:
I tried this and nothing changed. Would a flash back to 4.3 stock fix the problem?
Click to expand...
Click to collapse
I would read about doing that before doing so. From what I've been reading if you're on a certain bootloader, you can't go backwards. I'm by no means an expert, so just read a lot so you're comfortable with doing that. Good luck .
Dont flash old firmware, but older roms are ok to try. I'd start by trying to flash enewmans stock kk rom.
I managed to get the phone back to 4.3 Stock however now I don't have mobile data. I'm thinking this is a modem issue? Anyone have a fix?
I believe dochliday77 has a post somewhere with the kk modem ripped from the rom
crazymonkey05 said:
I believe dochliday77 has a post somewhere with the kk modem ripped from the rom
Click to expand...
Click to collapse
I installed a 4.3 modem and it did not fix the issue. In phone status IMEI is Unknown.
You need to install the 4.4 modem on a 4.3 rom
crazymonkey05 said:
You need to install the 4.4 modem on a 4.3 rom
Click to expand...
Click to collapse
Thanks! I coincidentally figured this out right before checking this post. For anyone having the same issue, check this thread here. It seemed to fix my issues with mobile data, wifi, and pretty much everything else.
cfsharp said:
Thanks! I coincidentally figured this out right before checking this post. For anyone having the same issue, check this thread here. It seemed to fix my issues with mobile data, wifi, and pretty much everything else.
Click to expand...
Click to collapse
Did you get your imei back?
crazymonkey05 said:
Did you get your imei back?
Click to expand...
Click to collapse
Yes, I did.
That's good to hear
Help please
What did yu do to get it past the AT&T logo? I am also stuck there
cfsharp said:
Yes, I did.
Click to expand...
Click to collapse
Hey im also stuck on the at&t logo. I was rooted but used triangle away to remove the counter and unrooted via super su/user <--- I don't really know the name of it. So i did the ota update and the phone restarted, it installed the update and restarted again and now will not get passed the att logo, even let it stay on over night. How did you get back to 4.3?? I'm a serious n00b so I need detailed instructions, anyone please?!?
ajcrunk said:
Hey im also stuck on the at&t logo. I was rooted but used triangle away to remove the counter and unrooted via super su/user <--- I don't really know the name of it. So i did the ota update and the phone restarted, it installed the update and restarted again and now will not get passed the att logo, even let it stay on over night. How did you get back to 4.3?? I'm a serious n00b so I need detailed instructions, anyone please?!?
Click to expand...
Click to collapse
Everything in download mode needs to say "official" in order to get the OTA. See if this helps:
http://forum.xda-developers.com/galaxy-s3-att/general/how-to-restore-device-status-to-t2832880
If the ota appeared to flash, and its hanging during boot, factory reset should solve it.
Be aware that doing so with stock recovery installed will wipe the internal sd card.
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
I guess this question had posted.. But I search still not answer.
SPH-M919 stock firmware OK3, Never root. The problem I can't hear caller, neither caller can't hear me on Regular call or WiFi Call with Sim Card. (T-mobile Sim card).
Using Google voice with Hangout work fine. I Also tried Viber, or Tango work fine. Mic work on Google voice search. I guess something have do with Modem file or should odin back stock to find out??
Remember, OK3 firmware, never root or flash before. Restock with Odin can trip the Knox??
Link to Stock Sph-M919 firmware to restock please you see link. Thanks alot
Tekone said:
I guess this question had posted.. But I search still not answer.
SPH-M919 stock firmware OK3, Never root. The problem I can't hear caller, neither caller can't hear me on Regular call or WiFi Call with Sim Card. (T-mobile Sim card).
Using Google voice with Hangout work fine. I Also tried Viber, or Tango work fine. Mic work on Google voice search. I guess something have do with Modem file or should odin back stock to find out??
Remember, OK3 firmware, never root or flash before. Restock with Odin can trip the Knox??
Link to Stock Sph-M919 firmware to restock please you see link. Thanks alot
Click to expand...
Click to collapse
You can flash stock. As long as its the same or later. Shouldnt effect knox.
lordodin912 said:
You can flash stock. As long as its the same or later. Shouldnt effect knox.
Click to expand...
Click to collapse
Thanks.. is Samsung website has stock rom on this Sph-m919 model? Please link if you see one. thanks
Tekone said:
Thanks.. is Samsung website has stock rom on this Sph-m919 model? Please link if you see one. thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3276231
lordodin912 said:
http://forum.xda-developers.com/showthread.php?t=3276231
Click to expand...
Click to collapse
Thanks again.. I downloaded and flashed. It doesn't work. flashed entire taz, what you think i could try? Google voice with hangout work fine. Viber work fine.. Not in regular phone call "weire"
Anyone can suggest will be listen..
I thinking to odin flash any tar below OK3 to see any problem. This is obviously a software problem. Odin flash below OK3 Will it trigger the Knox?
Tekone said:
I thinking to odin flash any tar below OK3 to see any problem. This is obviously a software problem. Odin flash below OK3 Will it trigger the Knox?
Click to expand...
Click to collapse
Try reflashing with odin, then boot into recovery and do a factory reset before the 1st boot. You cant downgrade, could try a different rom/kernel mabey.
lordodin912 said:
Try reflashing with odin, then boot into recovery and do a factory reset before the 1st boot. You cant downgrade, could try a different rom/kernel mabey.
Click to expand...
Click to collapse
I did that again and try to reset all user data... By trying different rom or kernel. I need to be rooted right with custom recovery right? Or it can be flash on odin for different kernel??
Tekone said:
I did that again and try to reset all user data... By trying different rom or kernel. I need to be rooted right with custom recovery right? Or it can be flash on odin for different kernel??
Click to expand...
Click to collapse
Flashing a recovery or kernel will trip knox....havent tried this because i dont have all that knox jazz, heres a guide to flash roms without tripping knox: http://forum.xda-developers.com/showthread.php?t=2852310