Hi, is it possible to flash a new firmware of this device while the samsung account still present on the device?
Can anyone tell me what would happen if i would simply flash a new firmware and root it without logging out the samsung account beforehand?
sarf2k4 said:
Hi, is it possible to flash a new firmware of this device while the samsung account still present on the device?
Can anyone tell me what would happen if i would simply flash a new firmware and root it without logging out the samsung account beforehand?
Click to expand...
Click to collapse
I'm not sure exactly what you're asking. If you dirty flash firmware (no data wipe) and root it, then you'd be updated with root and still have all your credentials on the device.
V0latyle said:
I'm not sure exactly what you're asking. If you dirty flash firmware (no data wipe) and root it, then you'd be updated with root and still have all your credentials on the device.
Click to expand...
Click to collapse
Sorry for not clarifying. What I meant is to simply flash a new firmware with odin while the samsung account still in the phone, as in, if we want to do a factory data reset from the settings interface, we have to key in the password or unbind the device from the account
sarf2k4 said:
Sorry for not clarifying. What I meant is to simply flash a new firmware with odin while the samsung account still in the phone, as in, if we want to do a factory data reset from the settings interface, we have to key in the password or unbind the device from the account
Click to expand...
Click to collapse
Are you asking whether flashing factory firmware will get rid of FRP?
I typically use Odin to flash firmware, and there's two ways to do it. In the firmware package, you have the BL, AP, CP, CSC, and HOME_CSC files. If you want to dirty flash without wiping user data (including a Samsung account), use the HOME_CSC file in the CSC slot. If however you want to force a data wipe, use the CSC file.
V0latyle said:
Are you asking whether flashing factory firmware will get rid of FRP?
I typically use Odin to flash firmware, and there's two ways to do it. In the firmware package, you have the BL, AP, CP, CSC, and HOME_CSC files. If you want to dirty flash without wiping user data (including a Samsung account), use the HOME_CSC file in the CSC slot. If however you want to force a data wipe, use the CSC file.
Click to expand...
Click to collapse
Erm... I don't know what an FRP really is, it has been a while since I last do phone rooting and flashing
I am asking because I saw a warning of odin v3.14.4 with the following message
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sarf2k4 said:
Erm... I don't know what an FRP really is, it has been a while since I last do phone rooting and flashing
I am asking because I saw a warning of odin v3.14.4 with the following message
View attachment 5812713
Click to expand...
Click to collapse
Did you have a Samsung account on the device already?
FRP = Factory Reset Protection. Requires the Google account login information that was previously on the device before factory reset in order to continue setup; this is an anti-theft measure.
Your bootloader has to be unlocked to use Odin.
V0latyle said:
Did you have a Samsung account on the device already?
FRP = Factory Reset Protection. Requires the Google account login information that was previously on the device before factory reset in order to continue setup; this is an anti-theft measure.
Your bootloader has to be unlocked to use Odin.
Click to expand...
Click to collapse
Yeah, you could say get rid of FRP
It has the account of the previous owner (it was given out). The previous owner kept telling me to bring it to a samsung center to reformat/factory reset it because the previous owner forgot his password
By unlocked, did you mean from the developer menu?
sarf2k4 said:
Yeah, you could say get rid of FRP
It has the account of the previous owner (it was given out). The previous owner kept telling me to bring it to a samsung center to reformat/factory reset it because the previous owner forgot his password
By unlocked, did you mean from the developer menu?
Click to expand...
Click to collapse
That's where you start - you enable OEM Unlocking in Developer Options, then you reboot to download mode and unlock the bootloader.
A clear indication of whether the bootloader is unlocked is the "OEM LOCK" line in download mode; if the bootloader is locked it'll say ON, if unlocked it'll say OFF
Are you able to get into the device at all? Is it locked by a password or pattern? If I were you I'd try to get the previous owner to unlock it; it's their responsibility to remove FRP before they sell the device.
V0latyle said:
That's where you start - you enable OEM Unlocking in Developer Options, then you reboot to download mode and unlock the bootloader.
A clear indication of whether the bootloader is unlocked is the "OEM LOCK" line in download mode; if the bootloader is locked it'll say ON, if unlocked it'll say OFF
Are you able to get into the device at all? Is it locked by a password or pattern? If I were you I'd try to get the previous owner to unlock it; it's their responsibility to remove FRP before they sell the device.
Click to expand...
Click to collapse
I don't know how to get into download mode and unlock the bootloader. From what I've read, I need to turn off the phone, press power/bixby? + volup then plug usb? This is the actual part that I somewhat confused because I already have the required file in order to root, twrp, and ketan's rom. Just the instruction wasn't very clear on what exactly what I must do, more below
Yes I'm able to get into the device, it is just that I can't get rid of the samsung account of the previous owner that enforces the FRP from the settings page because the device asks for the password of the previous owner's account in order to remove it
The flashing/rooting instruction were from http://www.mediafire.com/folder/d4ugie4yadxu6/N975F which is:
Section 2
Instructions for users who are on Stock Q/R/S Non rooted/Other ROMS or running trouble like boootloop
- First install stock latest stock S (A12) firmware (recommended same base if available, base info can be found in changelog post on XDA)
- Download ROM N975F_N976B_DrKetanROM_S*.zip and copy to SD card/USB & Check MD5
- Download & Extract N97*_TWRP_*_tar.md5 + Booloader and Modem according your device variant.
- Flash TWRP file with AP tab of Odin
- Again Reboot to Download mode
- Flash Bootloader and Modem
- Reboot to TWRP(DON't REBOOT TO SYSTEM) - Wipe - Format DATA (Full wipe) This will erase all data from your device
- Reboot TWRP - Flash N975F_N976B_DrKetanROM_S*.zip
- Reboot to System
Read Instrcutiona at end "After rebooting to System"
Click to expand...
Click to collapse
The part where I don't get is, "again reboot to download mode" and "reboot to twrp". I read on other thread, I have to untick "auto-reboot" option in odin?
sarf2k4 said:
I don't know how to get into download mode and unlock the bootloader. From what I've read, I need to turn off the phone, press power/bixby? + volup then plug usb?
Click to expand...
Click to collapse
No, don't press power. Just turn phone off, don't connect USB yet, and hold both Volume buttons while plugging in USB cable. It should start with a prompt for download mode, device unlocking, or cancel. Select device unlocking.
sarf2k4 said:
This is the actual part that I somewhat confused because I already have the required file in order to root, twrp, and ketan's rom.
Click to expand...
Click to collapse
What file? What exactly is your end goal here?
sarf2k4 said:
Just the instruction wasn't very clear on what exactly what I must do, more below
Yes I'm able to get into the device, it is just that I can't get rid of the samsung account of the previous owner that enforces the FRP from the settings page because the device asks for the password of the previous owner's account in order to remove it
Click to expand...
Click to collapse
Hmm. Hopefully a clean flash in Odin will do the trick.
sarf2k4 said:
The flashing/rooting instruction were from http://www.mediafire.com/folder/d4ugie4yadxu6/N975F which is:
The part where I don't get is, "again reboot to download mode" and "reboot to twrp". I read on other thread, I have to untick "auto-reboot" option in odin?
Click to expand...
Click to collapse
Yes. The idea here is that after you flash TWRP, you can't let the device boot into system, because if it does, it'll overwrite TWRP with the stock recovery.
But let's just focus on one step at a time; you first need to unlock the bootloader. Use the key combo I described above, and select whatever option mentions device unlocking. Should be a blue warning screen asking if you want to unlock the bootloader (may have an option for Device Unlock mode). Follow the prompt to unlock the bootloader. Once done report back here and we'll go to the next step.
V0latyle said:
No, don't press power. Just turn phone off, don't connect USB yet, and hold both Volume buttons while plugging in USB cable. It should start with a prompt for download mode, device unlocking, or cancel. Select device unlocking.
What file? What exactly is your end goal here?
Hmm. Hopefully a clean flash in Odin will do the trick.
Yes. The idea here is that after you flash TWRP, you can't let the device boot into system, because if it does, it'll overwrite TWRP with the stock recovery.
But let's just focus on one step at a time; you first need to unlock the bootloader. Use the key combo I described above, and select whatever option mentions device unlocking. Should be a blue warning screen asking if you want to unlock the bootloader (may have an option for Device Unlock mode). Follow the prompt to unlock the bootloader. Once done report back here and we'll go to the next step.
Click to expand...
Click to collapse
I followed your instruction, I wasn't sure connect to which, a charger outlet or pc/laptop. I decided to connect to a laptop anyway while holding both volume buttons. As you described, a cyan warning screen appeared, I proceeded by holding volup and another volup again to proceed with unlocking bootloader. It states that the phone will be wiped during the process.
The phone rebooted twice, first one says there's a yellow triangle that the bootloader has been unlocked, it shows the android with "preparing" message. It then rebooted once again and I pressed the power button to proceed when there yellow triangle appeared on this second boot up.
The phone stuck at SAMSUNG text for like about 5 minutes? I thought it got bricked or something so I detached the usb. After a while the phone booted up like a new phone with the first time setup wizard. I skipped everything.
Going into settings, the account of the previous owner is not there anymore, checking software information shows the latest build of N975FXXS8HVJ1, oneui 4.1, android 12
sarf2k4 said:
I followed your instruction, I wasn't sure connect to which, a charger outlet or pc/laptop. I decided to connect to a laptop anyway while holding both volume buttons. As you described, a cyan warning screen appeared, I proceeded by holding volup and another volup again to proceed with unlocking bootloader. It states that the phone will be wiped during the process.
Click to expand...
Click to collapse
Sorry, I should have been more specific.
sarf2k4 said:
The phone rebooted twice, first one says there's a yellow triangle that the bootloader has been unlocked, it shows the android with "preparing" message. It then rebooted once again and I pressed the power button to proceed when there yellow triangle appeared on this second boot up.
The phone stuck at SAMSUNG text for like about 5 minutes? I thought it got bricked or something so I detached the usb. After a while the phone booted up like a new phone with the first time setup wizard. I skipped everything.
Going into settings, the account of the previous owner is not there anymore, checking software information shows the latest build of N975FXXS8HVJ1, oneui 4.1, android 12
Click to expand...
Click to collapse
Alright, success. So what is your end goal here? Are you trying to install a custom ROM? Let me know what you're ultimately trying to accomplish so I can help you with the next steps.
V0latyle said:
Sorry, I should have been more specific.
Alright, success. So what is your end goal here? Are you trying to install a custom ROM? Let me know what you're ultimately trying to accomplish so I can help you with the next steps.
Click to expand...
Click to collapse
Thank you for the help.
I actually came from samsung galaxy note 1, gt-n7000, hard bricked accidentally 2 years ago because of the brickbug present if I'm not careful, but it got me. So I am using a vivo phone for almost a year, for which I can't even flash any firmware let alone running adb commands to grant permission on the phone. It is running android one and it has full locked down in my opinion.
I actually missed the viper4android that I tweaked on my note 1 for a very good sound quality I achieved back then although viper4android wasn't the only reason I wanted to root it. I would like to have adaway at least as well. Perhaps some other 'extra' features that stock can't offer.
I'm not sure how do I put it during the use of this device while still in the previous owner's account is that, when I launched netflix or youtube (respecting the privacy of course), the phone screen became brighter than I would like. Even if it is slightly dimmed, launching one of these app would make it brighter, then go back down to previous brightness when exiting them.
There's already a screen burn-in from excessive youtubing from the previous owner and I can see why, 3 years later this phone has burn-in already because of the app's behavior of 'boosting' the brightness. Not sure if some of the rooted modules 'can' prevent these brightness adjustments by the app or not.
I also never used any banking/financial app on any of my mobile devices
edit:
I often go for stock rom most of the time.
Coming from note 1 that has the potential brick bug during that era especially exynos variants, this note 10+ don't have any potential brick bug do they?
I also tried to restart the phone, I still get that yellow triangle warning saying bootloader has been unlocked and can't be verified, would like to get rid of that as well. Furthermore, I checked the developer menu, "oem unlocking" is now missing
You didn't answer my question, bud. What are you trying to do? What is your goal? For example, are you trying to get a custom ROM installed? Or were you just trying to get the Samsung account removed?
V0latyle said:
You didn't answer my question, bud. What are you trying to do? What is your goal? For example, are you trying to get a custom ROM installed? Or were you just trying to get the Samsung account removed?
Click to expand...
Click to collapse
Sorry if I veered off, yes I would like to have custom rom installed which is to have root in mind. I'm eyeing for drketan's mostly stock rom
Related
Hi guys, I have had my Galaxy note 2 I317 for only 7 weeks now with the 4.3 update. A couple days after I had it, I rooted the phone. However, 2 weeks ago, the sim card reader stopped working. I contacted samsung since I was still under warranty and they told me to send the phone so they can fix now. Now while trying to unroot it, I flashed it using the wrong stock firmware. I used 4.1 instead of 4.3 firmware. Now the phone is stuck to the Samsung logo and I am so depressed. I need help finding the 4.3 stock firmware and telling me exactly what to do in order to unroot the phone, reset the binary count to zero, so that i can be able to send the phone to Samsung to be fixed.
Thanks in advance for your help.
Kobeamox
Were you on 4.3 when you rooted the phone? If so did you trip Knox? You may not be able to get a warranty repair if you did.
However you may not need one. Have you tried just getting a new SIM card from your carrier? It might just be a bad SIM.
How did you come to the conclusion that the reader was broken?
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
If your stuck in Samsung logo try flashing 4.3param.tz using Odin.
And most likely you tripped knox.
So you lost warranty.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Thanks for your quick reply. I was indeed on 4.3 when I rooted the phone. ABout knox, I may have done it without knowing. how was I supposed to trip knox? I hope I did not. Regarding the sim card, the phone definitely has a problem: we have tested several sim cards from different companies in it, but it does not work. before that, I even went to my company, changed my sim card. That new one worked in my friends phone but wouldnt work in mine. the first day it had just a bit of signal then 2 days later, no signals at all. Please let me know about how I was supposed to trip knox, so that I see if I did it or not
Thanks
ShrekOpher said:
Were you on 4.3 when you rooted the phone? If so did you trip Knox? You may not be able to get a warranty repair if you did.
However you may not need one. Have you tried just getting a new SIM card from your carrier? It might just be a bad SIM.
How did you come to the conclusion that the reader was broken?
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Ye
Thanks for your quick reply. But when will I find the 4.3 param.tz? I dont have it. Can u help me locate it?
ilaf0106 said:
If your stuck in Samsung logo try flashing 4.3param.tz using Odin.
And most likely you tripped knox.
So you lost warranty.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
kobeamox said:
Thanks for your quick reply. I was indeed on 4.3 when I rooted the phone. ABout knox, I may have done it without knowing. how was I supposed to trip knox? I hope I did not. Regarding the sim card, the phone definitely has a problem: we have tested several sim cards from different companies in it, but it does not work. before that, I even went to my company, changed my sim card. That new one worked in my friends phone but wouldnt work in mine. the first day it had just a bit of signal then 2 days later, no signals at all. Please let me know about how I was supposed to trip knox, so that I see if I did it or not
Thanks
Ye
Click to expand...
Click to collapse
Check to see if you have a baseband or IMEI in your about phone status under your phone settings. Se screen shots for location.
If these are still full and not listed as unknown then it might be That you need to set your SE Linux to permissive.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
ShrekOpher said:
Check to see if you have a baseband or IMEI in your about phone status under your phone settings. Se screen shots for location.
If these are still full and not listed as unknown then it might be That you need to set your SE Linux to permissive.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
fyi .. prolly not a good idea to show your imei...some will use that number to fraudulently sell imei bad phone using your number for reference
The issue is that I am stuck on the samsung logo so cant acceed my IMEI
ShrekOpher said:
Check to see if you have a baseband or IMEI in your about phone status under your phone settings. Se screen shots for location.
If these are still full and not listed as unknown then it might be That you need to set your SE Linux to permissive.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
kobeamox said:
The issue is that I am stuck on the samsung logo so cant acceed my IMEI
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2618447
Info in here may help you.
Thanks a lot for letting me know!!!
qkster said:
fyi .. prolly not a good idea to show your imei...some will use that number to fraudulently sell imei bad phone using your number for reference
Click to expand...
Click to collapse
kobeamox said:
The issue is that I am stuck on the samsung logo so cant acceed my IMEI
Click to expand...
Click to collapse
Have you tried to Odin back to a stock 4.3 ROM.
You might want to try the one click.
Think I have it somewhere let me check.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
---------- Post added at 05:37 AM ---------- Previous post was at 05:34 AM ----------
This method worked for me.
One click Odin AT&T 4.3 update Note2 -> http://forum.xda-developers.com/showthread.php?t=2496292
Direct download link from above --> http://forum.xda-developers.com/showthread.php?t=2496292&page=23
Youtube video with instructions -->https://www.youtube.com/watch?v=zwUdd_SkzSQ
CF Auto Root -> http://forum.xda-developers.com/showthread.php?t=1980644
****Also you probably don't have a sim card read problem it was probably just the SE Linux settings that were making it seem like you could read the sim card. ****
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Thank you for your help. I just did it steps by steps, but it did not work for me at all. Any other suggestions/
ShrekOpher said:
Have you tried to Odin back to a stock 4.3 ROM.
You might want to try the one click.
Think I have it somewhere let me check.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
---------- Post added at 05:37 AM ---------- Previous post was at 05:34 AM ----------
This method worked for me.
One click Odin AT&T 4.3 update Note2 -> http://forum.xda-developers.com/showthread.php?t=2496292
Direct download link from above --> http://forum.xda-developers.com/showthread.php?t=2496292&page=23
Youtube video with instructions -->https://www.youtube.com/watch?v=zwUdd_SkzSQ
CF Auto Root -> http://forum.xda-developers.com/showthread.php?t=1980644
****Also you probably don't have a sim card read problem it was probably just the SE Linux settings that were making it seem like you could read the sim card. ****
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
kobeamox said:
Thank you for your help. I just did it steps by steps, but it did not work for me at all. Any other suggestions/
Click to expand...
Click to collapse
Everything you need to do is here.
http://forum.xda-developers.com/showthread.php?t=2618447
Next time, all you had to do was open SuperSU app and do a Full unroot from there, and run triangle away to reset counters.
Here's the instructions on Page 2 on the Dev thread.
http://forum.xda-developers.com/showthread.php?t=1992303
If you do this http://forum.xda-developers.com/showthread.php?t=2618447, all you have to do is the Triangle Away to get counters reset.
Since you have rooted, and IF you were on the FULL Stock MK6 ATT ROM, you have tripped Knox. You will see that when you run Triangle Away or if you go into Download Mode.
Entering download mode is very simple. First you will need to turn off your device. Once it’s off, you need to press this button combination: volume down, power button and home button. Keep them pressed until the download mode shows up. Once you’re there, you will be required to press volume up to enter the download mode or volume down to cancel and reboot the device.
Triangle Away will not reset Knox Warranty Void counter.
Pre-triangle Away
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cleared
I am trying to do it exactly what u said bymaking sure that everythg is checked and done right, but in step one , when i flash it, instead of saying reset, it takes a while and says: FAil, even though I did everythg right!
Help please!
dicksteele said:
http://forum.xda-developers.com/showthread.php?t=2618447
Info in here may help you.
Click to expand...
Click to collapse
kobeamox said:
I am trying to do it exactly what u said bymaking sure that everythg is checked and done right, but in step one , when i flash it, instead of saying reset, it takes a while and says: FAil, even though I did everythg right!
Help please!
Click to expand...
Click to collapse
What are you trying to flash ?? I317UCALJ2_I317ATTALJ2_ATT.zip
When it fails, what does it say it's failing on ?
The first step finally worked, you're the best, thank you. I am about to start the next step, but since I have to reset the binary count to 0 using Triangle away, at what specific step should I install Triangle away? and how should it happen? I dont think it is precised in the next 2 steps. Thank you and I will be online waiting for your answer in order to get that done tonight.
dicksteele said:
What are you trying to flash ?? I317UCALJ2_I317ATTALJ2_ATT.zip
When it fails, what does it say it's failing on ?
Click to expand...
Click to collapse
kobeamox said:
The first step finally worked, you're the best, thank you. I am about to start the next step, but since I have to reset the binary count to 0 using Triangle away, at what specific step should I install Triangle away? and how should it happen? I dont think it is precised in the next 2 steps. Thank you and I will be online waiting for your answer in order to get that done tonight.
Click to expand...
Click to collapse
You do not need Triangle Away to complete any of the other steps. The upgrade to i317UCAMH3 does not do any checks.
You should be booted into the stock ROM 4.1.1.
These are your next steps
SECTION 2: OTA to MH3
You are now booted into the original stock 4.1.1 Note II ROM, i317UCALJ2.
You do not need to set anything up except your wireless connection to download the 302 MB OTA update. Cancel all setups and make a Wifi Connection. (connect to a wireless connection to not use Phone Data)
After you have made a Wifi connection:
Go to Settings> About Device> Software Update
If you have setup account info for anything that's fine.... Continue on.
It should come up and tell you an update is available.
[If it says update not available, go to Settings Date/Time and take auto sync off. Advance the date one day and try again]
Complete the steps in the Update Windows (Simply by clicking NEXT or CONTINUE)
* You have flashed using ODIN to the original stock 4.1.1 Note II ROM, i317UCALJ2.
* You have now OTA’d to i317UCAMH3, which is the required baseline to OTA to 4.3.
After the reboot of the 302 MB OTA install, your phone will hang on the Samsung GALAXY Note II screen.
There are some unique steps that need to be done to get the install to complete successfully for the i317UCAMH3 OTA.
-First step is:
- Download 4.3param_tz.zip from http://d-h.st/OYC
- Extract the .zip file to get to 4.3param_tz.tar.
- Put your Note 2 in Download Mode.
Entering download mode is very simple. First you will need to turn off your device. Once it’s off, you need to press this button combination: volume down, power button and home button. Keep them pressed until the download mode shows up. Once you’re there, you will be required to press volume up to enter the download mode or volume down to cancel and reboot the device.
Open ODIN and place the 4.3param_tz.tar file in PDA and flash.
This .tar DOES NOT contain ANY 4.3 bootloader. If you flash a .tar file that has a sboot.bin in it. It will fail. That is because the current OTA 4.3 bootloader is write protected, as of 1/19/2014 (when I wrote this)
Your phone will reboot and it will redo the OTA install and update again. Not the download portion, but the after download and reboot portion. Let it finish it 100 %.
- Pull phone’s battery and go into Download mode once again.
- Second step is:
You will need to download TWRP 2.6.3.1 and flash it in ODIN.
http://goo.im/devs/OpenRecovery/t0lt...lteatt.img.tar
This is necessary for an openrecovery script to run that is stored in the /cache directory from the update.
- Put your Note 2 in Download Mode.
- Open ODIN, put openrecovery-twrp-2.6.3.1-t0lteatt.img.tar in PDA slot. Click Start and let the phone reset.
- Your phone will reboot in TWRP. If not, pull battery and enter recovery mode boot into TWRP recovery (HOLD VOL UP+HOME+POWER). The script will run by itself.
Thank you. I tried so many times but there is no update available. what can i do? I try so bad by turning the auto synch off and going one day up, but there is no update still. I even try 2 or 3 days up, still no update. Same thg even happens when i turn the dates backward. Help please genius.
dicksteele said:
You do not need Triangle Away to complete any of the other steps. The upgrade to i317UCAMH3 does not do any checks.
You should be booted into the stock ROM 4.1.1.
These are your next steps
SECTION 2: OTA to MH3
You are now booted into the original stock 4.1.1 Note II ROM, i317UCALJ2.
You do not need to set anything up except your wireless connection to download the 302 MB OTA update. Cancel all setups and make a Wifi Connection. (connect to a wireless connection to not use Phone Data)
After you have made a Wifi connection:
Go to Settings> About Device> Software Update
If you have setup account info for anything that's fine.... Continue on.
It should come up and tell you an update is available.
[If it says update not available, go to Settings Date/Time and take auto sync off. Advance the date one day and try again]
Complete the steps in the Update Windows (Simply by clicking NEXT or CONTINUE)
* You have flashed using ODIN to the original stock 4.1.1 Note II ROM, i317UCALJ2.
* You have now OTA’d to i317UCAMH3, which is the required baseline to OTA to 4.3.
After the reboot of the 302 MB OTA install, your phone will hang on the Samsung GALAXY Note II screen.
There are some unique steps that need to be done to get the install to complete successfully for the i317UCAMH3 OTA.
-First step is:
- Download 4.3param_tz.zip from http://d-h.st/OYC
- Extract the .zip file to get to 4.3param_tz.tar.
- Put your Note 2 in Download Mode.
Entering download mode is very simple. First you will need to turn off your device. Once it’s off, you need to press this button combination: volume down, power button and home button. Keep them pressed until the download mode shows up. Once you’re there, you will be required to press volume up to enter the download mode or volume down to cancel and reboot the device.
Open ODIN and place the 4.3param_tz.tar file in PDA and flash.
This .tar DOES NOT contain ANY 4.3 bootloader. If you flash a .tar file that has a sboot.bin in it. It will fail. That is because the current OTA 4.3 bootloader is write protected, as of 1/19/2014 (when I wrote this)
Your phone will reboot and it will redo the OTA install and update again. Not the download portion, but the after download and reboot portion. Let it finish it 100 %.
- Pull phone’s battery and go into Download mode once again.
- Second step is:
You will need to download TWRP 2.6.3.1 and flash it in ODIN.
http://goo.im/devs/OpenRecovery/t0lt...lteatt.img.tar
This is necessary for an openrecovery script to run that is stored in the /cache directory from the update.
- Put your Note 2 in Download Mode.
- Open ODIN, put openrecovery-twrp-2.6.3.1-t0lteatt.img.tar in PDA slot. Click Start and let the phone reset.
- Your phone will reboot in TWRP. If not, pull battery and enter recovery mode boot into TWRP recovery (HOLD VOL UP+HOME+POWER). The script will run by itself.
Click to expand...
Click to collapse
Also, remember that I have to send my phone back to samsung to fix the simcard reader which does not rread my sim card, thats wwhy I absolutely need to reset my binary count to 0, so that they think that nothing was done on the phone. Also, please give me your paypal Account. You are being so helpful
kobeamox said:
Thank you. I tried so many times but there is no update available. what can i do? I try so bad by turning the auto synch off and going one day up, but there is no update still. I even try 2 or 3 days up, still no update. Same thg even happens when i turn the dates backward. Help please genius.
Click to expand...
Click to collapse
kobeamox said:
Also, remember that I have to send my phone back to samsung to fix the simcard reader which does not rread my sim card, thats wwhy I absolutely need to reset my binary count to 0, so that they think that nothing was done on the phone. Also, please give me your paypal Account. You are being so helpful
Click to expand...
Click to collapse
Ahhh gotcha, I forgot.
You can run the triangle away after everything is back up and running.
No need for paypal for me. Just pick your favorite charity and donate.
It's 9:40 PM in California. I'll still checking in.
Hi
"Can't find valid operating system. The device will not start."
Then shows the visit g.co/ABH link.
I am not even able to boot into recovery. When selecting recovery from fastboot mode it just goes right to the same "Can't find valid operating system..." screen.
Device State: Locked
Developer Mode : Not Enabled and not possible to do now
PLease help me. As i am from Nepal , there is nothing i can't claim for warranty.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
senbros said:
Hi
"Can't find valid operating system. The device will not start."
Then shows the visit g.co/ABH link.
I am not even able to boot into recovery. When selecting recovery from fastboot mode it just goes right to the same "Can't find valid operating system..." screen.
Device State: Locked
Click to expand...
Click to collapse
Sorry, but with no working recovery and a locked bootloader you are dead in the water. There is nothing that can be done.
Are you able to unlock your bootloader? Might be able to download the factory image do it that way. Fastboot flashing unlock it something. Then run the flash all.bat from the factory image once you download it and unzipped it.
mammothjojo88 said:
Are you able to unlock your bootloader? Might be able to download the factory image do it that way. Fastboot flashing unlock it something. Then run the flash all.bat from the factory image once you download it and unzipped it.
Click to expand...
Click to collapse
I tried nothing works to unlock bootloader.. Still looking for solution..
Thank you for your time
Can't find valid operating system
senbros said:
Hi
"Can't find valid operating system. The device will not start."
Then shows the visit g.co/ABH link.
I am not even able to boot into recovery. When selecting recovery from fastboot mode it just goes right to the same "Can't find valid operating system..." screen.
Device State: Locked
Developer Mode : Not Enabled and not possible to do now
PLease help me. As i am from Nepal , there is nothing i can't claim for warranty.
Click to expand...
Click to collapse
Hi Mate,
I had the same thing happen Last Friday morning. I was just applying an OTA update, then when phone rebooted I got the same message on my Pixel 3 ( 2 weeks old ). I spent many hours over the weekend trying to figure out how to get a factory image on it. However without unlocking the bootloader ( which is not possible ), also having the recovery also corrupted, there is nothing we can do, except send it to a friend or someone we know and trust to get the phone repaired or if its under warranty still, possibly replaced by google. Sorry to be the giver of bad news. These are now expensive paper weights. It seems it becoming more common.
This is happening for more pixels. Google is must fix it remotely or pixel 4 might fail on landing.
issue resolved by google support
Hi,
i am having same issue with my pixel 3 last week, so i called Indian google service center ( 1800-419-0655 ) they pick up my phone from my place and resolve the issue.
so i will suggest you to visit/call google support team so they will resolve you issue.
---------- Post added at 06:03 AM ---------- Previous post was at 05:59 AM ----------
slysurfer said:
Hi Mate,
I had the same thing happen Last Friday morning. I was just applying an OTA update, then when phone rebooted I got the same message on my Pixel 3 ( 2 weeks old ). I spent many hours over the weekend trying to figure out how to get a factory image on it. However without unlocking the bootloader ( which is not possible ), also having the recovery also corrupted, there is nothing we can do, except send it to a friend or someone we know and trust to get the phone repaired or if its under warranty still, possibly replaced by google. Sorry to be the giver of bad news. These are now expensive paper weights. It seems it becoming more common.
Click to expand...
Click to collapse
hi there,
i had same issue last week, so i called google support. they pick up my pixel from my place and resolve the issue.
so please do the same contact google support. they will help you.
Problem in Pixel 3
They gave you a replacement or repaired the original device?? And how many days B2X took from pickup to delivering it back??
tailorhardik94 said:
Hi,
i am having same issue with my pixel 3 last week, so i called Indian google service center ( 1800-419-0655 ) they pick up my phone from my place and resolve the issue.
so i will suggest you to visit/call google support team so they will resolve you issue.
---------- Post added at 06:03 AM ---------- Previous post was at 05:59 AM ----------
hi there,
i had same issue last week, so i called google support. they pick up my pixel from my place and resolve the issue.
so please do the same contact google support. they will help you.
Click to expand...
Click to collapse
Not sure if anyone still needs help with this, but I just ran into this issue on my Pixel 4 XL and I held down the volume down button and power button to reboot into fastboot. From there you can connect to a PC and flash images or unlock/lock bootloader, etc.
From there I was able to use the flash.android.com site and flash the latest OTA to my phone and now I'm back up and running.
Hope this helps someone down the road.
bradwatson said:
Not sure if anyone still needs help with this, but I just ran into this issue on my Pixel 4 XL and I held down the volume down button and power button to reboot into fastboot. From there you can connect to a PC and flash images or unlock/lock bootloader, etc.
From there I was able to use the flash.android.com site and flash the latest OTA to my phone and now I'm back up and running.
Hope this helps someone down the road.
Click to expand...
Click to collapse
You can't do anything if you come across this problem whilst your bootloader is locked. I had a Pixel 3, applied ota via recovery and I got that error message. Couldn't do anything, flash factory image etc due to locked bootloader and recovery being corrupted.
Quite simply if it's under warranty, contact google.
kartikb said:
You can't do anything if you come across this problem whilst your bootloader is locked. I had a Pixel 3, applied ota via recovery and I got that error message. Couldn't do anything, flash factory image etc due to locked bootloader and recovery being corrupted.
Quite simply if it's under warranty, contact google.
Click to expand...
Click to collapse
Not entirely true. If OEM unlocking was previously enabled, then despite your phone being locked, it will still accept the unlocking command. Just happened to me. I am trading in my phone. I uninstalled Magisk, booted to bootloader, locked the bootloader and got the dreaded "Can't find valid operating system" alert. I thought it was toast since no response to adb at that point. The screen looked like the bootloader screen but with less text. Finally used vol down/pwr to get to bootloader, re-unlocked and re-flashed the OS. Back in business, at least getting my full trade-in price!
flash.android.com really helped, thank you!
device locked (locking the device is what caused this for me) and windows saying it doesnt recognize the device when I plugged it in while in the bootloader. For some reason flash.android.com recognized the device, not sure why
same thing happened with right now
i was trying to lock bootloader on custom rom (nonsense,i know)
so,phone wasnt being recognized by pc,and somehow android flash tool recognized and i clicked flashing and it needed bootloader to be unlocked so it did,and phone booted back on custom rom.
nice
yearn2burn said:
Not entirely true. If OEM unlocking was previously enabled, then despite your phone being locked, it will still accept the unlocking command. Just happened to me. I am trading in my phone. I uninstalled Magisk, booted to bootloader, locked the bootloader and got the dreaded "Can't find valid operating system" alert. I thought it was toast since no response to adb at that point. The screen looked like the bootloader screen but with less text. Finally used vol down/pwr to get to bootloader, re-unlocked and re-flashed the OS. Back in business, at least getting my full trade-in price!
Click to expand...
Click to collapse
Just happened to my Pixel 4a5G trade-in for Pixel 7. Completely uninstalled magisk and then tried to re-lock the bootloader. Bootloader locked and got the no operating system error. Called google and they said send it in as and I will get full amount. The dude did not sound very reassuring. I luckyly stumbled on this thread. tried to unlock the bootloader but it failed. I reset my computer and tried it again and it worked. Phone booted up. I took and OTA and tried to re-lock the bootloader and SUCCESS. This phone never had an OTA so I believe the one slot was empty, maybe that is why this happened. Moral to the story, make sure both slots has an OS on them.
Thanks
BB
bradwatson said:
Not sure if anyone still needs help with this, but I just ran into this issue on my Pixel 4 XL and I held down the volume down button and power button to reboot into fastboot. From there you can connect to a PC and flash images or unlock/lock bootloader, etc.
From there I was able to use the flash.android.com site and flash the latest OTA to my phone and now I'm back up and running.
Hope this helps someone down the road.
Click to expand...
Click to collapse
Thanks! This was exactly what I needed. I didn't realize you could get into fastboot with hardware controls and I was trying through adb
I'm an idiot and did this same thing.
bradwatson said:
Not sure if anyone still needs help with this, but I just ran into this issue on my Pixel 4 XL and I held down the volume down button and power button to reboot into fastboot. From there you can connect to a PC and flash images or unlock/lock bootloader, etc.
From there I was able to use the flash.android.com site and flash the latest OTA to my phone and now I'm back up and running.
Hope this helps someone down the road.
Click to expand...
Click to collapse
Just wanted to say thanks - had a panic moment until I read this and realized I could do that. Pixel 4 wiped and ready to go back. Thanks again, years later.
Good morning,
I'm writing this post 'cause I'd like to know if it's a possibility to "unlock", if I can say this, my phone. My company installs on my phone VMware Hub and the Debug USB is locked because I cannot unlock the related menu. I've tried to format the phone from original recovery by wiping data and nothing changed. So, I've run my phone into bootloader in order to overwrite the original firmware with a new original one. The process is ok but when I restart my phone, VMware is installed and configured.
Now, a question, is it possible to remove it withouth root or debug USB? I'm so annoyed because it is possible to check everything I do in my phone
Did someone answer you? I have the same problem.
Thanks.
Hello, sorry for such late reply been way for too long, the answer is simple, go to developer options, select the oem unlock option reboot the phone to download or recovery i don't remember, a message will come before that will alow you to unlock bootloader, precede to unlock, i can't recall if the phoene will reset but i assume so, when it comes back it will no longer be tied to your employer, it will be an A50 like any other bougt on the store, keep in mind that from then foword you will get a message saying that bootloader is unlocked at phone power on, that's it
I recently got a used Samsung Galaxy S9 (G960F/DS) with a broken screen (shattered glass and a black spot on the LCD). I was preparing to replace its screen, however, I'm currently not getting the device to boot.
When connected to power, the phone turns on automatically and ends up stuck on the "Samsung Galaxy S9 Secured by Knox Powered by android" screen. When disconnecting power, it turns off after 1-2 seconds.
By pressing power + bixby + volume down, the device enters download mode. When trying to flash stock firmware (BL + AP + CP + CSC) downloaded through Frija (SM-G960F_2_20211021052205_oql3mv17br_fac) the process fails and the phone shows "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". However, I was able to flash the four parts separately by rebooting in between.
This doesn't change anything about the booting problem though. Holding power + bixby + volume up doesn't boot recovery either.
I'd be happy to hear any suggestions. If any more information is required, I'm happy to send you everything I know.
Jogius said:
I recently got a used Samsung Galaxy S9 (G960F/DS) with a broken screen (shattered glass and a black spot on the LCD). I was preparing to replace its screen, however, I'm currently not getting the device to boot.
When connected to power, the phone turns on automatically and ends up stuck on the "Samsung Galaxy S9 Secured by Knox Powered by android" screen. When disconnecting power, it turns off after 1-2 seconds.
By pressing power + bixby + volume down, the device enters download mode. When trying to flash stock firmware (BL + AP + CP + CSC) downloaded through Frija (SM-G960F_2_20211021052205_oql3mv17br_fac) the process fails and the phone shows "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". However, I was able to flash the four parts separately by rebooting in between.
This doesn't change anything about the booting problem though. Holding power + bixby + volume up doesn't boot recovery either.
I'd be happy to hear any suggestions. If any more information is required, I'm happy to send you everything I know.
Click to expand...
Click to collapse
May I'm wrong, but the first impression seems that not only the screen is defective, keep in mind that a device with that broken screen had to receive a severe shock (or various of them), to this can happen, in the incident -of course- other hardware could be damaged.
But taking apart the hardware thing, did you try to format data through stock recovery? Or could you see in the recovery screen (if something is visible) the current build number, so you can flash the right firmware instead of a lower version or the first you found out there?
SubwayChamp said:
May I'm wrong, but the first impression seems that not only the screen is defective, keep in mind that a device with that broken screen had to receive a severe shock (or various of them), to this can happen, in the incident -of course- other hardware could be damaged.
But taking apart the hardware thing, did you try to format data through stock recovery? Or could you see in the recovery screen (if something is visible) the current build number, so you can flash the right firmware instead of a lower version or the first you found out there?
Click to expand...
Click to collapse
I feel like the phone might have another hardware defect, but I'd still like to try my best to fix it.
Unfortunately, the previous owner already tinkered with the device aswell, when I received it, it was not booting stock recovery. However, I only tried flashing the newest update of the firmware - was that the wrong approach? How (and where) can I find a lower version without knowing the exact version details?
Thank you for the input!
Jogius said:
I feel like the phone might have another hardware defect, but I'd still like to try my best to fix it.
Unfortunately, the previous owner already tinkered with the device aswell, when I received it, it was not booting stock recovery. However, I only tried flashing the newest update of the firmware - was that the wrong approach? How (and where) can I find a lower version without knowing the exact version details?
Thank you for the input!
Click to expand...
Click to collapse
Not sure if as the screen is broken you can see something through it, in the recovery screen you'll find the build number version for your device.
Flashing the latest update is always the best bet to not fail. Flashing lower version is not a good idea. You also have to check what is the input in the download screen, if something like KG prenormal warning is there, then you can't flash something in this state.
Also, as the previous owner seems to be not so careful with this device, it is probable that the latest Google account is still there that will trigger the FRP protection.
SubwayChamp said:
Not sure if as the screen is broken you can see something through it, in the recovery screen you'll find the build number version for your device.
Flashing the latest update is always the best bet to not fail. Flashing lower version is not a good idea. You also have to check what is the input in the download screen, if something like KG prenormal warning is there, then you can't flash something in this state.
Also, as the previous owner seems to be not so careful with this device, it is probable that the latest Google account is still there that will trigger the FRP protection.
Click to expand...
Click to collapse
I attached an image of what information download mode has. The second image shows what happens when I try to boot recovery (or anything except download mode for that matter).
You are right that the FRP ist still turned on. Does that mean there is no way to go around this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Jogius said:
I attached an image of what information download mode has. The second image shows what happens when I try to boot recovery (or anything except download mode for that matter).
You are right that the FRP ist still turned on. Does that mean there is no way to go around this?
View attachment 5478243View attachment 5478245
Click to expand...
Click to collapse
Yes, I suspected that, FRP is active, try to find the guy that sold to you this device, and ask him to log out from his Google account. Also the FRP trigger can be a false positive in the instance that you can enable OEM unlock toggle (what it is not actually enabled), and if Odin allow you to flash something on it and from there you could set it up your device normally.
SubwayChamp said:
Yes, I suspected that, FRP is active, try to find the guy that sold to you this device, and ask him to log out from his Google account. Also the FRP trigger can be a false positive in the instance that you can enable OEM unlock toggle (what it is not actually enabled), and if Odin allow you to flash something on it and from there you could set it up your device normally.
Click to expand...
Click to collapse
I'll try to get in touch with the seller, thank you! However, does FRP change anything about the device not being able to boot at all? Do you have any tips for me how to troubleshoot the fact that not even recovery mode is working?
Jogius said:
I'll try to get in touch with the seller, thank you! However, does FRP change anything about the device not being able to boot at all? Do you have any tips for me how to troubleshoot the fact that not even recovery mode is working?
Click to expand...
Click to collapse
frp still allows you to boot, it just will ask for your google account when setting the phone up
Jogius said:
I'll try to get in touch with the seller, thank you! However, does FRP change anything about the device not being able to boot at all? Do you have any tips for me how to troubleshoot the fact that not even recovery mode is working?
Click to expand...
Click to collapse
FRP works mainly in two ways, when you didn't enable OEM unlock and of course USB debugging then FRP detects an unofficial attempt to inject some custom binary rejecting to boot to system, (What would be the purpose of FRP if you could flash a custom binary, rooting it and then pulling all the data you want?) sometimes this is bypassed by formatting data either booting to recovery (that you say you can't do at this time) or flashing the CSC different from the CSC_HOME, this will wipe/format all your data. And the second instance where FRP can be trigger is when the device was black listed (plus the Samsung account if the last owner didn't log out). The first thing you have to do when buying a Samsung device is logging into the two accounts, then formatting data, and from there you can do what you want.
Hey guys I have finally admitted defeat, Im not really sure what else to do at this point, as I have tried a lot;
- Flashed the base android pie (12.0) OS
- Hard reset
- Changed Date and Time back 7 days to prevent jail
- Disabled automatic system updates
- Disabled things such as updates, timezone change, etc.
Enable Developer options: and OEM doesn't appear at all, simply doesnt exist, not even grayed out or anything
The only thing I could find online explaining this issue is that the reason this happens is because my device is SIM-locked. Which it isn't. It's fully unlocked (XAG/XAG/XAA)
Model: SM-N975U1 Region: XAA
Any help would be great thanks
and yes it is connected to the wifi, and tried updating also (im on the latest), still nothing has changed
jacobjake7 said:
Hey guys I have finally admitted defeat, Im not really sure what else to do at this point, as I have tried a lot;
- Flashed the base android pie (12.0) OS
- Hard reset
- Changed Date and Time back 7 days to prevent jail
- Disabled automatic system updates
- Disabled things such as updates, timezone change, etc.
Enable Developer options: and OEM doesn't appear at all, simply doesnt exist, not even grayed out or anything
The only thing I could find online explaining this issue is that the reason this happens is because my device is SIM-locked. Which it isn't. It's fully unlocked (XAG/XAG/XAA)
Model: SM-N975U1 Region: XAA
Any help would be great thanks
Click to expand...
Click to collapse
Your device is probably RMM locked. Please take a look at this thread.
nxmryada said:
Your device is probably RMM locked. Please take a look at this thread.
Click to expand...
Click to collapse
Thanks,
I don't quite understand this part;
"
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Power" + "Vol. Down" + "Vol. Up" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Vol. Up" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
***Don't boot into rom because it will lock your device again!!!!
Once the custom recovery booted, swipe to "Allow modification" and flash RMM-State_Bypass.zip as normal zip"
I flashed then did as it said but it just sends back to the original recovery screen
jacobjake7 said:
Thanks,
I don't quite understand this part;
"
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Power" + "Vol. Down" + "Vol. Up" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Vol. Up" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
***Don't boot into rom because it will lock your device again!!!!
Once the custom recovery booted, swipe to "Allow modification" and flash RMM-State_Bypass.zip as normal zip"
I flashed then did as it said but it just sends back to the original recovery screen
Click to expand...
Click to collapse
RMM locking prevents flashing AFAIK. Please check for "RMM state" in download mode, if it's "Prenormal" then you're locked out.
nxmryada said:
RMM locking prevents flashing AFAIK. Please check for "RMM state" in download mode, if it's "Prenormal" then you're locked out.
Click to expand...
Click to collapse
I am unable to find any display info on this device, like such as in downloader. Where can I find my RMM state?
nxmryada said:
RMM locking prevents flashing AFAIK. Please check for "RMM state" in download mode, if it's "Prenormal" then you're locked out.
Click to expand...
Click to collapse
Wait isn't RMM state just that 7 day jailing? I tried doing this before I flashed/hard reset my phone was on months before I reset it and was still unable to get that OEM option
nxmryada said:
RMM locking prevents flashing AFAIK. Please check for "RMM state" in download mode, if it's "Prenormal" then you're locked out.
Click to expand...
Click to collapse
I understand the lingo a bit more now after reading up, but that article is a flat circle. It wants me to Install twrp to flash a RMM bypass zip (which you need to disable bootloader to even do in the first place), and you need root access to use twrp.
Yet the information provided below of how to root tells me I need to install twrp and boot into it's recovery, but you need to be root to do that?!?
Make it make sense!
Probably by flashing a combination without etoken or something of that sort?
Locked bootloader prevents booting unsigned boot stages.
What about disable Knox through ADB with the SamFwTool ?
I think you may need to remove google account and screenlocks first, not sure.
Network_Pro said:
Probably by flashing a combination without etoken or something of that sort?
Locked bootloader prevents booting unsigned boot stages.
What about disable Knox through ADB with the SamFwTool ?
I think you may need to remove google account and screenlocks first, not sure.
Click to expand...
Click to collapse
Disabling Knox within SamFw works, however I am still KG/RMM locked
Hit a brick road here not really sure where else to go...
I have a Galaxy Note 10+ (SM-N975U1 XAG) that is RMM locked an unable to get the OEM option in dev settings,
Since Knox is one responsible for the valutmanager line that releases the RMM check, I tried disabling Knox completely through SamFW tool, disabling works, however I am still locked.
Any help would be apricated...
jacobjake7 said:
Hit a brick road here not really sure where else to go...
I have a Galaxy Note 10+ (SM-N975U1 XAG) that is RMM locked an unable to get the OEM option in dev settings,
Since Knox is one responsible for the valutmanager line that releases the RMM check, I tried disabling Knox completely through SamFW tool, disabling works, however I am still locked.
Any help would be apricated...
Click to expand...
Click to collapse
This video may help...
youtu.be/6RTbx2jTkpQ
as the person said only Exynos versions can be unlocked and not Snapdragon ones.
and also this video below shows how to unhide the hidden oem unlock button
youtu.be/mF2Nxck4FtM
aiSanaul said:
This video may help...
youtu.be/6RTbx2jTkpQ
as the person said only Exynos versions can be unlocked and not Snapdragon ones.
and also this video below shows how to unhide the hidden oem unlock button
youtu.be/mF2Nxck4FtM
Click to expand...
Click to collapse
I have a Exynos, OEM doesn't exist in Dev options, since im RMM locked....
jacobjake7 said:
I have a Exynos, OEM doesn't exist in Dev options, since im RMM locked....
Click to expand...
Click to collapse
check out methods here
www (dot) 99mediasector.com/how-to-disable-rmm-state-lock-in-samsung-galaxy-devices/
aiSanaul said:
check out methods here
www (dot) 99mediasector.com/how-to-disable-rmm-state-lock-in-samsung-galaxy-devices/
Click to expand...
Click to collapse
Thanks,
First option I can't do TWRP since I need root and unlocked bootloader, so next step;
Miracle Box Thunder ive been messing around with before, is interesting, can only get it to work for the first half second it connects to my phone and then the stop button grays out :/
Though I got it do to this for the "Reset Reactivation/EE Locks":
Start Detect device.
Device detected OK.
Downloading..
Get phone data..
Reactivation Lock Reset Launched...
Searching For Reactivation Data 1...
Loading Data Please wait..
Rc Block Update ok...
Processing Data...
Done..
EE Lock Reset Launched...
Searching For EE Data 1...
Loading Data Please wait..
Error Data Not Found...
>>All Done..
I am unable to view my download mode info in the top left. Would you know how to "enable" it or how I can go about viewing it another way?
aiSanaul said:
check out methods here
www (dot) 99mediasector.com/how-to-disable-rmm-state-lock-in-samsung-galaxy-devices/
Click to expand...
Click to collapse
Actually while doing the "Reset Reactivation/EE Locks" it gave me a text top left of the download mode, saying "ODIN: TOKEN Size is too large [-13]"
Update...I was able to bypass the RMM/KG lock by first doing a fresh install;
skip through all intro and setup (or just FRP skip)
DONT SET A SCREEN LOCK, must be unlocked or swipe otherwise you will be softbricked in a infinite "starting device..."
next you use Minimal ADB and Fastboot terminal and type "adb shell pm disable-user --user 0 com.android.systemui"
your phone is gonna freak out now dont worry about it and open up FRP Samsung by NKTEAM and click "Kill update" (this is important)
then after kill update is complete you can run "Disabled KG Locked MTK ADB" which will lock your phone saying you uninstalled a samsung service etc....just reboot your device and your good!
Though, I don't understand how to unlock OEM still? I still don't have the option?
Should I flash oreo or something? Though flashing causes it all to relock again
Not to give up and never admit defeat, here is what I would do since I am not sure what that RMM is, I am not actively reversing this technology just collecting information from the web.
I would ask the tools creators through their support chats if they can extend the tools to deal with the faulting security mechanisms. At the same time I will check where is a cheap replacement board, just in case help it brick itself (yes the security mechanism design is self-destructing, I do not admit I break it it breaks itself).
I will flash with Odin with pit file with format to try to truly revert to factory. If I am not happy with the result I start becoming creative with the tools at hand LOL:
Then I will start flashing Bin-compatible official files with patched Odin, until the device resets itself to factory at least two times. The idea being due to crypto differences in the versions, the entire partitions gets rewritten during flashing. I would try this by removing all locks and protections (accounts), resetting to defaults, and flashing the first and the last bin-compatible firmware from samfw site.
Someone mentioned they achieved not-keeping previous things by mixing their firmware files AP BL CSC etc this is something I would try to try and get the device to confuse the crypto and overwrite things.
The idea is that the second stage bootloader BL will always be able to get you to download mode to flash with Odin so messing and even triggering with the later boot and protection stages should not erase the XBL. If it does then I will need the emergency_download_debug whatever package for the Bin version.
What Bin version is the device anyway ?
SM-N975U1 is Snapdragon. Why did you think it was Exynos?
Ask @afaneh92 he is unlocking specific versions of bootloaders for US/Canada devices since the SamPWN team are missing from the forums. https://forum.xda-developers.com/t/...unlock-for-samsung-us-canada-devices.4215101/