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/
Gentlemen, I introduce myself, my name is John and I come from HTC Mania, I speak Spanish and I hope excuse my grammatical errors.
I hope you can help me is small big problem that I have with my Galaxy note II. First I must confess that until yesterday had one with version 4.1.2, 5.15 and acces Philpz Custom Root.
* I was anxious to install a Custom ROM on my phone, because I must confess bringing something boring, and they recommended asking the Phantom ROM. http://forum.xda-developers.com/showthread.php?t=2737570 and i chose the latest version.
I made a backup of my files, unfortunately Synchronize my messages, whatsapp among others for not having lost all conversations and let the 3 files in SD Storage. I also made a backup of an EFS file?, Nose if it really is well done, but I have a file on my PC Image EFS weighing about 20 megabytes.
Well, the thing esque watching the video of the Phantom ROM installation, the comments left that could be installed by Philpz but assure me that it was the latest version, then downloaded the 6.48.4 and un updating. These were my steps:
1 - I downloaded the three files such as video and got into SD Storage.
2 - I turned off the computer, I got into recovery mode and did the following Wipes: Wipe Data / Factory reset - Wipe cache partition - Format system - format data - Format preload (the latter not remember doing it)
3 - I installed and followed the same steps as the video in the aroma, but I did not reboot before install SuperSU, ie, installed Part 1, Part 2, Super SU and then Reboot.
4 - I rebooted the phone and the process was over.
Al and peel off the Samsung logo, and start the setup, the team was stuck like 3 times, having to restart the phone. His signal was turned mobile network but I do not plan, I could call, but the Wi-fi could not ignite at any time. This will not start., Therefore I have no way to install Whatsapp and other applications, gmail etc. and taking into account the time that the phone stay stuck flashing process could be wrong and could have other mistakes I know.
Asking elsewhere with few answers, and also reading the same thread Phantom ROM, few mentioned some "MD5 chek?" (I did not understand how it was done), and I had not installed Bootloader MJ5, by the fact that gone from 4.1.2 to 4.3 +.
I do not know what to do right now, I could help? What should I do, should I download, what to do first and last, I have to download the video tutorial TWRP? what version is it?, did Wipe any other, can please guide me step by step from the point at which I am. something like "Download these files first sluts, put on sd and install this, and this one, flash it by Odin, and then makes these wipes ROM upgrade." Now I guess I must have several things that can be bad.
I hope not to bother, thank you very much for your attention and patience.
I reiterate my apologies for my language, but I'm using google translator.
I don't know if i have installed an bootloader.
Download device info app n then check ur bootloader
If its below mj5 u need to flash mj5 for having wifi
Sent from my GT-N7100 using Tapatalk
karan2012 said:
Download device info app n then check ur bootloader
If its below mj5 u need to flash mj5 for having wifi
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Thanks a lot, if I wanted to make sure my ROM did not have any problem with the installation, you may re-install it again? That is, now I install the Bootloader MJ5, and then do the same steps of the video? Or have any other way to do ... or is it better to do nothing and just install the mj5?
deathjuano said:
Thanks a lot, if I wanted to make sure my ROM did not have any problem with the installation, you may re-install it again? That is, now I install the Bootloader MJ5, and then do the same steps of the video? Or have any other way to do ... or is it better to do nothing and just install the mj5?
Click to expand...
Click to collapse
First flash mj5 bootloader from dr.ketan's thread via odin n then see if u have got ur wifi back or not
Sent from my GT-N7100 using Tapatalk
karan2012 said:
Download device info app n then check ur bootloader
If its below mj5 u need to flash mj5 for having wifi
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
karan2012 said:
First flash mj5 bootloader from dr.ketan's thread via odin n then see if u have got ur wifi back or not
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
I've installed bootlader an yeeeeeeeeeeeeeeees, it's works now , thanks a lot for the suport , if i someday i want to change this ROM, its necesary do the same, or the bootloader will be saved?
deathjuano said:
I've installed bootlader an yeeeeeeeeeeeeeeees, it's works now , thanks a lot for the suport , if i someday i want to change this ROM, its necesary do the same, or the bootloader will be saved?
Click to expand...
Click to collapse
Bootloader will always remain same n if warranty is not a big deal for u or your warranty period is over u cn upgrade modem to nd3 or ne2
These are kitkat knoxed bootloader n fixes the issue of charging phone while its off (a problem in mj5)
U can find these bootloaders in the faqs of jellykat by singhpratik87
Sent from my GT-N7100 using Tapatalk
sawayai n2
karan2012 said:
Bootloader will always remain same n if warranty is not a big deal for u or your warranty period is over u cn upgrade modem to nd3 or ne2
These are kitkat knoxed bootloader n fixes the issue of charging phone while its off (a problem in mj5)
U can find these bootloaders in the faqs of jellykat by singhpratik87
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Thanks for the support, but i have another question.
My phone sometimes stay freezed and i must reboot it, and i think it is a problem, or when i want to choose a wallpaper it says " Config. has stopped ", Play music has stopped, and Super SU when i open it says, " Binaris of supersu are not installed, and supersu can't be installed, this is a problem! " .... and with it i think that the process of installation no was god and many other problems will attack. What you recomend to do ?, Flash again ? what wipes y must do, TWRP must be installed and the version of pihlpz that i have doesn't work well? Thanks. ( And if i must flash again.... with the bootloader installed, my wi-fi will work ? )
Well I would suggest a clean flash with all necesary wipes
Sent from my GT-N7100 using Tapatalk
karan2012 said:
Well I would suggest a clean flash with all necesary wipes
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
It means, that i have to do all the steps again, but when the aroma makes me chose things to put in phone like, gmail, drop, starting logo samsung s5, etc i don't choose nothing ?
deathjuano said:
It means, that i have to do all the steps again, but when the aroma makes me chose things to put in phone like, gmail, drop, starting logo samsung s5, etc i don't choose nothing ?
Click to expand...
Click to collapse
U can choose anything n flash the rom
Sent from my GT-N7100 using Tapatalk
deathjuano said:
....and Super SU when i open it says, " Binaris of supersu are not installed, and supersu can't be installed, this is a problem! " ....
Click to expand...
Click to collapse
You should just flash in your custom recovery latest UPDATE-SuperSU.zip (v.2.xx) from Chainfire's thread or website.
tetakpatalked from Nexus 7 flo
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
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.