Related
Ok, here's a thread where those who are having difficulty upgrading to Mango should post so as to stay clear from the other "I have Mango" thread.
The format should be
Carrier
Phone Model
Updating from NODO/7004/7008
Force update(disconnect trick) or Official Zune notice?
Error Code
Problem Description: Eg, Phone hangs for 30 minutes at booting screen.
Ok, so my phone is now dead. I don't know what to do..
Carrier O2 UK
Phone Model HTC HD7
Updating from nodo to mango
Problem Description: I didn't get an error code. It froze on the update at step 8 or 9 (restarting the phone) and now will not boot. It vibrates 7 times and stays on the HTC logo screen.
Please help me
It was updating for over 3 hours.
---------- Post added at 12:30 AM ---------- Previous post was at 12:00 AM ----------
Please someone help me?
Carrier: Rogers (Canada)
Phone Model: Samsung Focus
Updating from 7390 (I guess, the one after NODO)
Error Code : none, stuck at step 8 "Restarting your phone"
Problem Description: Phone is frozen at the Samsung logo and nothing happens from there (been there for about 30 mins).
Mango update is quite meh for me here -_-
Carrier ORANGE CARAIBES
Phone Model HTC HD7
Updating from NODO TO MANGO
Error Code
Problem Description: Can't boot anymore. I don't even can turn on the phone :/ My first problem on windows phone!
Chasseur d'étoiles said:
Carrier: Rogers (Canada)
Phone Model: Samsung Focus
Updating from 7390 (I guess, the one after NODO)
Error Code : none, stuck at step 8 "Restarting your phone"
Problem Description: Phone is frozen at the Samsung logo and nothing happens from there (been there for about 30 mins).
Mango update is quite meh for me here -_-
Click to expand...
Click to collapse
just wanted to remind everybody that those of use who went from NoDo to RTM had varied times for the updates, some people reported more than an hour at the boot logo until it continued. After two hours I'd say something is wrong.
A hard reset might bring it to back (loosing all info of course). That in fact worked for me in the first update state going from NoDo to 7661 beta. I thought I bricked my phone, but it came back after a cold boot/hard reset.
derausgewanderte said:
just wanted to remind everybody that those of use who went from NoDo to RTM had varied times for the updates, some people reported more than an hour at the boot logo until it continued. After two hours I'd say something is wrong.
A hard reset might bring it to back (loosing all info of course). That in fact worked for me in the first update state going from NoDo to 7661 beta. I thought I bricked my phone, but it came back after a cold boot/hard reset.
Click to expand...
Click to collapse
My phone was updating for collectively updating for three hours. At least two of those it was stuck on the boot screen. I've tried resetting it (holding both volume keys when turning it on) and nothing works. Microsoft's support page said to disconnect if it freezes..
mdjmurray said:
My phone was updating for collectively updating for three hours. At least two of those it was stuck on the boot screen. I've tried resetting it (holding both volume keys when turning it on) and nothing works. Microsoft's support page said to disconnect if it freezes..
Click to expand...
Click to collapse
a hard reset on mine worked by pushing down power button, camera button and both vol plus and minus at the same time while the phone booted. I unplugged the battery, plugged it back in and then get the timing right to push the buttons down. Good luck.
Dead HTC Surround..
In the same boat as others. Phone stuck between steps 8 & 9, no phone won't turn on at all. Hard reset won't work. Acts like the battery is completely dead and USB port doesn't work. No lights, no beeps.. dead. Ugh.
Never installed any hacks, ROMs etc. I was 100% normal updates. Very frustrating...
This was actually my third attempt to install the updates. Previous times it had froze I was able to do a hard reset and restore the backup.
Anyone have suggestions? I've pulled the battery and it hasn't made any difference.
bbrian said:
In the same boat as others. Phone stuck between steps 8 & 9, no phone won't turn on at all.
Click to expand...
Click to collapse
This happened to my Omnia 7 while doing the final restart. It got stuck on the 'Samsung Omnia 7' logo for about 15 minutes. I just hit the home button and it finished booting.....problem solved.
Ok. Did you guys forced the update or waited for the official notification?
i got a message on my cell about it so i upgraded i i got a sdamsun focus v1.4
Carrier: AT&T
Phone Model: Samsung Focus
Updating from NODO
Force update(disconnect trick)
Error Code C1010009
Problem Description: It got through the friends and family update, then when it tries to update to Mango I get error C1010009 each time. I've tried this on multiple PCs with the same exact outcome. I went through the suggested MS troubleshooting steps and tried the Fix It thing to no avail, Fix It says nothing is wrong. Any suggestions?
VoodooKing said:
Ok, here's a thread where those who are having difficulty upgrading to Mango should post so as to stay clear from the other "I have Mango" thread.
The format should be
Carrier
Phone Model
Updating from NODO/7004/7008
Force update(disconnect trick) or Official Zune notice?
Error Code
Problem Description: Eg, Phone hangs for 30 minutes at booting screen.
Click to expand...
Click to collapse
tamcdonald said:
Carrier: AT&T
Phone Model: Samsung Focus
Updating from NODO
Force update(disconnect trick)
Error Code C1010009
Problem Description: It got through the friends and family update, then when it tries to update to Mango I get error C1010009 each time. I've tried this on multiple PCs with the same exact outcome. I went through the suggested MS troubleshooting steps and tried the Fix It thing to no avail, Fix It says nothing is wrong. Any suggestions?
Click to expand...
Click to collapse
Ok you may want to try to wait for the official notice to pop up. There is a reason why but I used to get that error when I changed my carrier code. A while back there was a Samsung firmware update being pushed down to some carriers that my carrier hadn't released yet. So I changed my carrier code to force the update. The update downloaded but did not manage to install and giving me that error code. I reverted to my original carrier code and a week later, My phone notified me of the same update and successfully installed it.
I believe that nobody is meant to do the disconnect trick and its best to just wait for the official update notice.
It almost seems like some kind of driver issue. After Zune updated it detected a new device and Windows said it installed it ok, the phone works fine in every other way as far as syncing with Zune etc. Device manager says the device is working properly, but when specifically trying to transfer the Mango update it refuses. Weird.
Edit: I fixed it. After reading your post about carrier codes, I starting poking around and rebranded my phone to ATT-US. After that Mango installed no problem.
VoodooKing said:
Ok you may want to try to wait for the official notice to pop up. There is a reason why but I used to get that error when I changed my carrier code. A while back there was a Samsung firmware update being pushed down to some carriers that my carrier hadn't released yet. So I changed my carrier code to force the update. The update downloaded but did not manage to install and giving me that error code. I reverted to my original carrier code and a week later, My phone notified me of the same update and successfully it.
I believe that nobody is meant to do the disconnect trick and just wait for the official update notice.
Click to expand...
Click to collapse
tamcdonald said:
It almost seems like some kind of driver issue. After Zune updated it detected a new device and Windows said it installed it ok, the phone works fine in every other way as far as syncing with Zune etc. Device manager says the device is working properly, but when specifically trying to transfer the Mango update it refuses. Weird.
Edit: I fixed it. After reading your post about carrier codes, I starting poking around and rebranded my phone to ATT-US. After that Mango installed no problem.
Click to expand...
Click to collapse
That's good to know. Now we know one of the causes for the error message. Mine is unbranded 000-88.
bricked focus
Carrier AT&T
Phone:: Samsung Focus v1.3
Updating from 7390
Force Update Disconnecting trick
Error cod:e none froze during step 8 or 9 phone restart phase of 7392 update
Problem: My phone will not move past the AT&T orange world phone screen. I have hard reset the phone numerous times both without SD card and with. Have followed all the steps to what i have seen posted do far. Not really sure what to do now. I have entered it into the download mode twice the first time for over 30 minutes the second time around 20 or so. What would be next step if there is one?
Hi i have i an unuseal problem my phone is htc 7 mozart and in about it says hardware revision NA radio hardware version 0.0.0.0 and when i boot to bootloader mode in the red colour it says something like chinese.Now i am in mango.Why it says that???
{sorry for my english i am from greece}
depdereck said:
Carrier AT&T
Phone:: Samsung Focus v1.3
Updating from 7390
Force Update Disconnecting trick
Error cod:e none froze during step 8 or 9 phone restart phase of 7392 update
Problem: My phone will not move past the AT&T orange world phone screen. I have hard reset the phone numerous times both without SD card and with. Have followed all the steps to what i have seen posted do far. Not really sure what to do now. I have entered it into the download mode twice the first time for over 30 minutes the second time around 20 or so. What would be next step if there is one?
Click to expand...
Click to collapse
How long did it get stuck at the operator screen? I have seen reports of 15mins before the phone boots again.
aggelosss5 said:
Hi i have i an unuseal problem my phone is htc 7 mozart and in about it says hardware revision NA radio hardware version 0.0.0.0 and when i boot to bootloader mode in the red colour it says something like chinese.Now i am in mango.Why it says that???
{sorry for my english i am from greece}
Click to expand...
Click to collapse
Is your phone still working after the update? What are the version numbers? You can check in Settings > About
VoodooKing said:
How long did it get stuck at the operator screen? I have seen reports of 15mins before the phone boots again.
Click to expand...
Click to collapse
It gets stuck there for a long time longest i let it sit there before trying another reset was about 45 minutes or so. I got Zune to recognize my phone and start a restore but it stopped again at the phone restart and sat there for about 30 minutes. I had to exit out to leave work and head home. I also tried to recover the phone with the Windows Phone Support Tool but that timed out at the restart as well and gave me an error code of 800004005.
My G4 gives me warning about unlock attempts remaining when using a pattern or knock code (See attached image).
However, it doesn't say that it's going to wipe my device.... so I'm not sure what it's going to do if all the attempts are used. I don't want some idiot to pick up my phone and be able to wipe the device just by messing around with the unlock screen.
Can anyone confirm what happens when all the unlock attempts are used?
Is there any way to disable the unlock attempts limit `feature`?
sevin7 said:
My G4 gives me warning about unlock attempts remaining when using a pattern or knock code (See attached image).
However, it doesn't say that it's going to wipe my device.... so I'm not sure what it's going to do if all the attempts are used. I don't want some idiot to pick up my phone and be able to wipe the device just by messing around with the unlock screen.
Can anyone confirm what happens when all the unlock attempts are used?
Is there any way to disable the unlock attempts limit `feature`?
Click to expand...
Click to collapse
Why on Earth would you think it wipes the device? It, like most any other phone, has a longer wait period to unlock the device if you incorrectly enter codes in.
Dennisg34 said:
Why on Earth would you think it wipes the device? It, like most any other phone, has a longer wait period to unlock the device if you incorrectly enter codes in.
Click to expand...
Click to collapse
On page 41 of the Verizon LG G4 Manual it states:
After 5 unsuccessful attempts to unlock your phone, you're prompted to enter a text phrase to confirm that you're trying to unlock your phone.
You have 10 opportunities to enter your unlock sequence. After 10 unsuccessful attempts, your phone will automatically perform a factory data reset and all of your
personal files will be erased. You will be warned after the 9th unsuccessful attempt.
If you've set a Knock Code, after 6 unsuccessful attempts, you're prompted to enter your Backup PIN to unlock your phone.
woozzy101 said:
On page 41 of the Verizon LG G4 Manual it states:
After 5 unsuccessful attempts to unlock your phone, you're prompted to enter a text phrase to confirm that you're trying to unlock your phone.
You have 10 opportunities to enter your unlock sequence. After 10 unsuccessful attempts, your phone will automatically perform a factory data reset and all of your
personal files will be erased. You will be warned after the 9th unsuccessful attempt.
If you've set a Knock Code, after 6 unsuccessful attempts, you're prompted to enter your Backup PIN to unlock your phone.
Click to expand...
Click to collapse
That has a lawsuit waiting to happen. Thanks Verizon... (or LG, if this is a phone design rather than carrier)
Dennisg34 said:
That has a lawsuit waiting to happen. Thanks Verizon... (or LG, if this is a phone design rather than carrier)
Click to expand...
Click to collapse
My Mom's Galaxy S5 for Verizon wipes the phone after 10 unlock attempts by default but has an option to turn it off (she discovered this the hard way when she wiped her phone because she couldn't remember her pattern).
Also, I know that the HTC One M8 does this.
Thankyou woozzy101 for finding that information, its very helpful. Now I just need to find a way to disable this idiotic 'feature'.
I just tested using an invalid Knock Code 5x times to make it use the backup pin... However when entering the backup pin it doesn't tell me that there are 'x attempts remaining' , but I only attempted to enter my backup pin once (and did it correctly) as I'm afraid of wiping my device by testing entering invalid backup pins. Is anyone brave/crazy enough to test what happens if you use all of your invalid knock code attempts then enter the backup pin incorrectly multiple times? I want to know if this will result in wiping the device... if it doesn't then I'll be using this unlock method instead of the pattern.
Also, does anyone know if this 'feature' is something that is part of Android, or a custom addition by LG or Verizon?
Dennisg34 said:
That has a lawsuit waiting to happen. Thanks Verizon... (or LG, if this is a phone design rather than carrier)
Click to expand...
Click to collapse
I downloaded the G4 manual from Verizon to familiarize myself with the phone before I got it. When I read about the factory reset I was like, ruh-roh, that is an accident waiting to happen. Way too easy to wipe someones phone messing around with it. Or if you have kids and your kid gets it and plays around with it....
I keep re-reading the Manual and the factory reset falls under "Changing Your Screen Lock". It might only do factory reset if you already have the phone unlocked and in the settings to remove the lock screen? Best Buy wont deliver my phone till June 5th (this Friday) so i cant really test it
On my EU origin H815 at the 10th attempt for a pin it simply tells me to wait 30 seconds just like it did at 5 attempts. At 15 attempts you get this;
http://imgur.com/WUdkXxz
After the 20th you get this;
http://imgur.com/UKAntAP
rahlquist said:
On my EU origin H815 at the 10th attempt for a pin it simply tells me to wait 30 seconds just like it did at 5 attempts. At 15 attempts you get this;
http://imgur.com/WUdkXxz
After the 20th you get this;
http://imgur.com/UKAntAP
Click to expand...
Click to collapse
So it looks like a Verizon thing. Go figure, they're always trying to f*** with you
I have a G960F/DS, I tried to root after the 7 days waiting so when I had the option I enabled OEM unlock, BUT it asked me to do a factory reset so I did, but I didn't know that I should have to enter download mode before rebooting, so now I have OEM lock and FRP on OFF, but I've got the RMM state again in prenormal. I waited again 7 more days but the OEM unlock option is not showing again, what should I do? Wait more time? Do another factory reset? Install again the stock rom?
That's weird. Maybe re-flash stock firmware, wait 7 days. When enabling OEM unlock and it requests to factory reset, once it reboots go straight into download mode and flash TWRP. From there in my experience OEM unlock will always then be there, even when I did re-flash stock ROM at a later date.
InteliDroid said:
That's weird. Maybe re-flash stock firmware, wait 7 days. When enabling OEM unlock and it requests to factory reset, once it reboots go straight into download mode and flash TWRP. From there in my experience OEM unlock will always then be there, even when I did re-flash stock ROM at a later date.
Click to expand...
Click to collapse
Should I flash CSC or HOME CSC?
Legasx said:
I have a G960F/DS, I tried to root after the 7 days waiting so when I had the option I enabled OEM unlock, BUT it asked me to do a factory reset so I did, but I didn't know that I should have to enter download mode before rebooting, so now I have OEM lock and FRP on OFF, but I've got the RMM state again in prenormal. I waited again 7 more days but the OEM unlock option is not showing again, what should I do? Wait more time? Do another factory reset? Install again the stock rom?
Click to expand...
Click to collapse
When you first had the OEM unlock, did you ODIN install TWRP and then flash the NoVerify file immediately after doing the Factory reset. I waited the 7 days, did the above and OEM unlock always shows up now in developer options even after trying other ROMs and just going back to stock rooted setup.
Docmjldds said:
When you first had the OEM unlock, did you ODIN install TWRP and then flash the NoVerify file immediately after doing the Factory reset. I waited the 7 days, did the above and OEM unlock always shows up now in developer options even after trying other ROMs and just going back to stock rooted setup.
Click to expand...
Click to collapse
I know that I should have installed twrp and the fix before rebooting, now I have unlocked bootloader but RMM state is prenormal again.
Legasx said:
Should I flash CSC or HOME CSC?
Click to expand...
Click to collapse
Any ideas?
I'm pretty sure everything I just read there was wrong... W. R. O. N. G.
Firstly.. If you're unlucky enough to have a phone that's going to have the RMM state.. It's a 2 week wait MINIMUM.
When you first get the phone, select the OEM unlock and be prepared for it to reset the phone and reboot... This is NOT OPTIONAL... And at this point if you see the RMM state as PRENORMAL you can forget about flashing twrp or anything else for at least another 7 days.
Anybody that tells you that you should have flashed twrp before you restarted the phone doesn't know what they are talking about.. When you press that OEM unlock button for the first time.. That bloody phone WILL REBOOT, It WILL RESET... There is no way to get to ODIN MODE and even if there was, the RMM state is triggered straight away if you have one of those phone.
I have an S9 that had no RMM state period.. I was able to to flash twrp straight away.
I also have an S9+ where the RMM state was triggered the moment you accept the phones request to restart after selecting the OEM unlock.
Secondly, after you've selected OEM unlock and the phone has reset and restarted, I'd suggest leaving it on for 7 days... Some people say it doesn't matter if you turn it off, but to be safe.. Just wack it on the charger and leave it.
Once the 7 days is up, the OEM option will reappear... Ignore it.
Boot the phone into ODIN MODE and see if the RMM STATE has vanished.
Understand... It's a 14 day wait... Not a 7 day wait.
Wait 7 days from purchase for oem option.
Unlock oem.. Reboot/reset phone.
Wait 7 more days for oem option to reappear.. Ignore it and boot into Odin mode.
Flash TWRP... For the love of God turn off the Auto restart in Odin.
Prepractice the art of restarting the phone into TWRP manually.. If you miss your window of opportunity and it restarts into android one of two things will happen.
Best case scenario.. You have to reflash TWRP.
Worst case scenario.. The RMM state comes back for another 7 days.
To get out of download mode
Hold volume down and power for 7 seconds.
The moment you feel the phone vibrate (a fraction of a second before the Samsung logo appears) boot into TWRP by
Quickly releasing all the buttons then very quickly press the power, up volume and bixby... And you need to do it BEFORE the screen initialises.. If you see the Samsung logo and you haven't got those buttons down.. You've missed it.
Make sure you have all your files ready to go... With this phone being so *****y I had all my files on both the sd card and a usb with OTG.
RMM STATE BYPASS
N96X ROOT FOR OEM ISSUES.
MAGISK (I'm using the Lineage AOSP 16.4 version, it works on Samsung touchwiz)
A selection of firmwares
Flashable modems.
With this phone you have to be prepared.
batfink1 said:
I'm pretty sure everything I just read there was wrong... W. R. O. N. G.
Firstly.. If you're unlucky enough to have a phone that's going to have the RMM state.. It's a 2 week wait MINIMUM.
When you first get the phone, select the OEM unlock and be prepared for it to reset the phone and reboot... This is NOT OPTIONAL... And at this point if you see the RMM state as PRENORMAL you can forget about flashing twrp or anything else for at least another 7 days.
Anybody that tells you that you should have flashed twrp before you restarted the phone doesn't know what they are talking about.. When you press that OEM unlock button for the first time.. That bloody phone WILL REBOOT, It WILL RESET... There is no way to get to ODIN MODE and even if there was, the RMM state is triggered straight away if you have one of those phone.
I have an S9 that had no RMM state period.. I was able to to flash twrp straight away.
I also have an S9+ where the RMM state was triggered the moment you accept the phones request to restart after selecting the OEM unlock.
Secondly, after you've selected OEM unlock and the phone has reset and restarted, I'd suggest leaving it on for 7 days... Some people say it doesn't matter if you turn it off, but to be safe.. Just wack it on the charger and leave it.
Once the 7 days is up, the OEM option will reappear... Ignore it.
Boot the phone into ODIN MODE and see if the RMM STATE has vanished.
Understand... It's a 14 day wait... Not a 7 day wait.
Wait 7 days from purchase for oem option.
Unlock oem.. Reboot/reset phone.
Wait 7 more days for oem option to reappear.. Ignore it and boot into Odin mode.
Flash TWRP... For the love of God turn off the Auto restart in Odin.
Prepractice the art of restarting the phone into TWRP manually.. If you miss your window of opportunity and it restarts into android one of two things will happen.
Best case scenario.. You have to reflash TWRP.
Worst case scenario.. The RMM state comes back for another 7 days.
To get out of download mode
Hold volume down and power for 7 seconds.
The moment you feel the phone vibrate (a fraction of a second before the Samsung logo appears) boot into TWRP by
Quickly releasing all the buttons then very quickly press the power, up volume and bixby... And you need to do it BEFORE the screen initialises.. If you see the Samsung logo and you haven't got those buttons down.. You've missed it.
Make sure you have all your files ready to go... With this phone being so *****y I had all my files on both the sd card and a usb with OTG.
RMM STATE BYPASS
N96X ROOT FOR OEM ISSUES.
MAGISK (I'm using the Lineage AOSP 16.4 version, it works on Samsung touchwiz)
A selection of firmwares
Flashable modems.
With this phone you have to be prepared.
Click to expand...
Click to collapse
I have done that, activated oem unlock, it asked to do a factory reset so I did, got rmm state prenormal again, then waited 7 days again but still no oem unlock switch for the second time, now I've tried the method that involves changing date and checking for new updates without results, now yesterday I've re installed firmware, bl, modem and CSC, factory new, and still no oem switch, still prenormal
Ok, I went through the same thing determined to find a way around the 14 day wait period... That included downloading 9 different Samsung firmwares from Sammobile all different versions from different counties.. It didn't work, and each time I installed a new firmware it reset the 7 day RMM state counter... I lost 3 days trying that on the S9+.
After the first OEM unlock /reboot /reset did you just leave it on, not touch it except to check the uptime in the settings... I know other people said you can turn it off, but I've been through this on an S8+ and s9+ and it definitely worked better just leaving it on and making sure it got charged occasionally.
I can tell you now, installing that new firmware just reset the RMM state back to 7 days.
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
I mean some people cant wait and reboot into ODIN mode to check before the time is up... Did you wait the full 168 hours.
batfink1 said:
Ok, I went through the same thing determined to find a way around the 14 day wait period... That included downloading 9 different Samsung firmwares from Sammobile all different versions from different counties.. It didn't work, and each time I installed a new firmware it reset the 7 day RMM state counter... I lost 3 days trying that on the S9+.
After the first OEM unlock /reboot /reset did you just leave it on, not touch it except to check the uptime in the settings... I know other people said you can turn it off, but I've been through this on an S8+ and s9+ and it definitely worked better just leaving it on and making sure it got charged occasionally.
I can tell you now, installing that new firmware just reset the RMM state back to 7 days.
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
I mean some people cant wait and reboot into ODIN mode to check before the time is up... Did you wait the full 168 hours.
Click to expand...
Click to collapse
The first time, before ticking oem unlock switch, I even turned it off some times and checked download mode to see rmm state, even after that I got the oem unlock switch after 7 days, then I switched it and now I got oem unlocked but rmm state prenormal again, but I have waited 7 days again with no results, yesterday I reinstalled firmware, CSC and everything, guess I need to wait 7 more days without turning it off.
Could it be that I bought my phone from ebay and my service provider and CSC are AFG (Afganistan)? But my phone is unlocked, I use it in Mexico
Legasx said:
The first time, before ticking oem unlock switch, I even turned it off some times and checked download mode to see rmm state, even after that I got the oem unlock switch after 7 days, then I switched it and now I got oem unlocked but rmm state prenormal again, but I have waited 7 days again with no results, yesterday I reinstalled firmware, CSC and everything, guess I need to wait 7 more days without turning it off.
Could it be that I bought my phone from ebay and my service provider and CSC are AFG (Afganistan)? But my phone is unlocked, I use it in Mexico
Click to expand...
Click to collapse
My phone is SAME as yours except I use Tmobile in US. My phone is an S9. Unlocked from a third party Net I purchased from as new and it has the same AFG CSC. I waited exactly 7 days. But installed TRWP immediately by holding Pwr Vol dwn and Bixby from the Format data answer yes etc after seeing the OEM unlock after that 7 days. This was my experience all I can say.
Docmjldds said:
My phone is SAME as yours except I use Tmobile in US. My phone is an S9. Unlocked from a third party Net I purchased from as new and it has the same AFG CSC. I waited exactly 7 days. But installed TRWP immediately by holding Pwr Vol dwn and Bixby from the Format data answer yes etc after seeing the OEM unlock after that 7 days. This was my experience all I can say.
Click to expand...
Click to collapse
So did you not format the data and just reboot into the bootloader after clicking OEM unlock?
jal3223 said:
So did you not format the data and just reboot into the bootloader after clicking OEM unlock?
Click to expand...
Click to collapse
When you toggle OEM unlock it will ask to reboot. At that point power down the phone, DO NOT REBOOT IT. Then hold volume down, bixby and power to get into the bootloader. Once there, you will see your RMM state is NORMAL. Now confirm by pressing volume up or whatever it was and you will be able to flash TWRP with ODIN.
This is where it gets tricky. Once the flash is complete the phone will reboot. You will need to hold volume up, bixby, and power for about 5 seconds to boot directly into TWRP. Once there you will need to wipe, then reboot recovery and flash no-verity, then reboot and flash RMM fix.
If you don't follow above, and the phone reboots you are screwed into waiting another 7 days if your lucky, otherwise you will need to flash stock firmware again and the whole process starts over.
shiftr182 said:
When you toggle OEM unlock it will ask to reboot. At that point power down the phone, DO NOT REBOOT IT. Then hold volume down, bixby and power to get into the bootloader. Once there, you will see your RMM state is NORMAL. Now confirm by pressing volume up or whatever it was and you will be able to flash TWRP with ODIN.
This is where it gets tricky. Once the flash is complete the phone will reboot. You will need to hold volume up, bixby, and power for about 5 seconds to boot directly into TWRP. Once there you will need to wipe, then reboot recovery and flash no-verity, then reboot and flash RMM fix.
If you don't follow above, and the phone reboots you are screwed into waiting another 7 days if your lucky, otherwise you will need to flash stock firmware again and the whole process starts over.
Click to expand...
Click to collapse
This has got to be the most concise write up of the situation. Thank you for clearing it up!
I've been RMM Prenormal with OEM unlocked for about 10 days now; no new firmware or wipes or anything, just waiting it out. I have no idea when it will be back to Normal; should I wipe it to reset the counter to wait the 7 full days anew, or should I just continue to wait, checking the recovery every day until it is Normal?
There is only one thing I can say... THANKS a lot, Samsung... This was my last SAMSUNG phone !
batfink1 said:
I'm pretty sure everything I just read there was wrong... W. R. O. N. G.
Firstly.. If you're unlucky enough to have a phone that's going to have the RMM state.. It's a 2 week wait MINIMUM.
When you first get the phone, select the OEM unlock and be prepared for it to reset the phone and reboot... This is NOT OPTIONAL... And at this point if you see the RMM state as PRENORMAL you can forget about flashing twrp or anything else for at least another 7 days.
Anybody that tells you that you should have flashed twrp before you restarted the phone doesn't know what they are talking about.. When you press that OEM unlock button for the first time.. That bloody phone WILL REBOOT, It WILL RESET... There is no way to get to ODIN MODE and even if there was, the RMM state is triggered straight away if you have one of those phone.
I have an S9 that had no RMM state period.. I was able to to flash twrp straight away.
I also have an S9+ where the RMM state was triggered the moment you accept the phones request to restart after selecting the OEM unlock.
Secondly, after you've selected OEM unlock and the phone has reset and restarted, I'd suggest leaving it on for 7 days... Some people say it doesn't matter if you turn it off, but to be safe.. Just wack it on the charger and leave it.
Once the 7 days is up, the OEM option will reappear... Ignore it.
Boot the phone into ODIN MODE and see if the RMM STATE has vanished.
Understand... It's a 14 day wait... Not a 7 day wait.
Wait 7 days from purchase for oem option.
Unlock oem.. Reboot/reset phone.
Wait 7 more days for oem option to reappear.. Ignore it and boot into Odin mode.
Flash TWRP... For the love of God turn off the Auto restart in Odin.
Prepractice the art of restarting the phone into TWRP manually.. If you miss your window of opportunity and it restarts into android one of two things will happen.
Best case scenario.. You have to reflash TWRP.
Worst case scenario.. The RMM state comes back for another 7 days.
To get out of download mode
Hold volume down and power for 7 seconds.
The moment you feel the phone vibrate (a fraction of a second before the Samsung logo appears) boot into TWRP by
Quickly releasing all the buttons then very quickly press the power, up volume and bixby... And you need to do it BEFORE the screen initialises.. If you see the Samsung logo and you haven't got those buttons down.. You've missed it.
Make sure you have all your files ready to go... With this phone being so *****y I had all my files on both the sd card and a usb with OTG.
RMM STATE BYPASS
N96X ROOT FOR OEM ISSUES.
MAGISK (I'm using the Lineage AOSP 16.4 version, it works on Samsung touchwiz)
A selection of firmwares
Flashable modems.
With this phone you have to be prepared.
Click to expand...
Click to collapse
I face the same problem. 7 days are not sufficient on my phone. Have been waiting 169 hors and do NOT see the OEM unlock at all. So will have to wait 7 more days... I doubt it will then appear
Then I have to reboot to odin-mode, see the RMM state and reboot and wait againe 7 (or maybe 14 ??) days ???
GREAT feature from Samsung...
If it is not possible to root the phone, I will sell it and never again buy anything from Samsung..
after the 7 days or 168 hrs, just reboot and check again on dev settings. That worked for me.
Two oposing instructions
1st.
shiftr182 said:
When you toggle OEM unlock it will ask to reboot. At that point power down the phone, DO NOT REBOOT IT.
Click to expand...
Click to collapse
2nd.
batfink1 said:
select the OEM unlock and be prepared for it to reset the phone and reboot... This is NOT OPTIONAL.
Click to expand...
Click to collapse
Could somebody clarify?
Sure, I'll clarify in about 1 week when my Note 9 512 gig phone arrives.
I'll try his way first, however what I stated about being ready is vitally important.
Make sure you have everything you need on an SDCARD AND on a USB stick if you have an OTG adapter.
You can't put any of it internally on the phone because to remove the encryption you need to wipe the internal storage completely.
So make sure you have
no-verity-opt-encrypt-6.0-star.zip
RMM STATE BYPASS
A selection of custom firmwares.. Alexandr's excellent devbased roms have RMM STATE BYPASS built in, they also have Xposed built in by renaming the rom slightly such as N960Fxxx_DevBase_v6.x_xposed.zip
Will install Xposed framework.
Renaming the rom as N960Fxxx_DevBase_v6.x_noroot.zip
Will install the rom without root or Magisk being installed.
I use his rom on both an S9 and an S9+ and they work perfectly.
So read and read and read, and when you've collected everything you need on two different media.... READ SOME MORE.
I'll update this thread when I try out shiftr182 method.
Most importantly, before you do anything.. Practice booting into recovery and Odin mode till you get it down pat.. You really only get one go at it.
Now mind you, I'm really cavalier, I'm a computer technician and I can't sit around wringing my hands together worrying about what's going to happen or I'll never get anything done, so to do this you do your homework, lots of homework and then you take your balls in your hand and do it and accept that if it all goes arse up... Well you tried.
It's actually pretty hard to totally brick these phones.. It just means more waiting, more reading and more asking questions.
I hope this has not only qualmed (not the urban dictionary meaning) your fears but also put the fear of God in you.
DO YOUR RESEARCH :angel:
I have requested the unlock via the miunlocker and got the 360 hours wait message.
Does the phone automatically unlock after this time frame? do I get a notification?
Do I have to run the unlocker again after 360 hours?
does the phoen have to remain on for 360 hours or could I switch it off for 2 weeks?
most importantly - can I remove the simcard from the phone and use in another phone whilst waiting?
As I need a phone for work, with my work emails and apps, so instead of reinstalling on a miui rom, and then wiping and reinstalling again I can simply use my old phone
t3rm3y said:
I have requested the unlock via the miunlocker and got the 360 hours wait message.
Does the phone automatically unlock after this time frame? do I get a notification?
Do I have to run the unlocker again after 360 hours?
does the phoen have to remain on for 360 hours or could I switch it off for 2 weeks?
most importantly - can I remove the simcard from the phone and use in another phone whilst waiting?
As I need a phone for work, with my work emails and apps, so instead of reinstalling on a miui rom, and then wiping and reinstalling again I can simply use my old phone
Click to expand...
Click to collapse
You need to connect to the computer and use the unlock program to unlock it.
It does not have to remain on for the unlock wait period. Does not need a sim installed either.
goofball2k said:
You need to connect to the computer and use the unlock program to unlock it.
It does not have to remain on for the unlock wait period. Does not need a sim installed either.
Click to expand...
Click to collapse
Thanks. So after 15 days I connect it back up and run the unlock again?
I just don't want to wait that long and donut wrong and get the same message...
t3rm3y said:
Thanks. So after 15 days I connect it back up and run the unlock again?
I just don't want to wait that long and donut wrong and get the same message...
Click to expand...
Click to collapse
yes, you can connect up and run the unlocking tool after your timer is up.
Hi, I'm new to XDA. I am trying to get a rooted device so I can play around with it and do cool things. After trying 4 different phones and weeks of nonstop research and attempts, I decided to an Amazon Fire 8 Plus (10th Generation). I know how to unlock bootloader using windows 10 and android sdk. The one problem is that I can't enable OEM unlocking. When I tried fastboot flashing unlock anyway, my tablet got stuck in fastboot mode. Basically, what happens is, I turn it on, nothing suspicious there, but after I confirm it when I get the warning message, it INSTANTLY turns back off. Tinkering around with date and time, software updates, rebooting, and toggle developer options did nothing. I even went as far as disabling the lock screen so it doesn't make me enter my pin when I try to turn it on - still nothing! I am very desperate and tired of all this rooting, it would be nice to get some help!
Also, I think I can use this video
to root if I figure out to get to that temp directory command thing the guy entered. I use windows ten, but can't find how to get to that place.
An answer to either question would be much appreciated, thanks!
Zeek347 said:
Hi, I'm new to XDA. I am trying to get a rooted device so I can play around with it and do cool things. After trying 4 different phones and weeks of nonstop research and attempts, I decided to an Amazon Fire 8 Plus (10th Generation). I know how to unlock bootloader using windows 10 and android sdk. The one problem is that I can't enable OEM unlocking. When I tried fastboot flashing unlock anyway, my tablet got stuck in fastboot mode. Basically, what happens is, I turn it on, nothing suspicious there, but after I confirm it when I get the warning message, it INSTANTLY turns back off. Tinkering around with date and time, software updates, rebooting, and toggle developer options did nothing. I even went as far as disabling the lock screen so it doesn't make me enter my pin when I try to turn it on - still nothing! I am very desperate and tired of all this rooting, it would be nice to get some help!
Also, I think I can use this video
to root if I figure out to get to that temp directory command thing the guy entered. I use windows ten, but can't find how to get to that place.
An answer to either question would be much appreciated, thanks!
Click to expand...
Click to collapse
You will find more accurate information about it in the specific device's forum https://forum.xda-developers.com/c/amazon-fire-hd-8-and-hd-10.4709/ I guess you choose the more problematic OEM to start tinkering with, Amazon is not such good for rooting and modding.