The change date hack to unlock OEM isnt working help me
Wait
*Detection* said:
Wait
Click to expand...
Click to collapse
;(
Lol, I succeeded by setting date to past 1 month, upgrading to pie then setting it back to jan after update
amakuramio said:
Lol, I succeeded by setting date to past 1 month, upgrading to pie then setting it back to jan after update
Click to expand...
Click to collapse
You don't need OEM unlock to update to Pie if it's stock with ODIN
only official released binaries ... nonsense again. I want to flash oreo with root etc.
amakuramio said:
only official released binaries ... nonsense again. I want to flash oreo with root etc.
Click to expand...
Click to collapse
Yea you have to wait 7 days, there is more than just the OEM unlock that needs to time-out, RMM state pre-normal too
Last I heard there was no bypass other than waiting 7 days
*Detection* said:
Yea you have to wait 7 days, there is more than just the OEM unlock that needs to time-out, RMM state pre-normal too
Last I heard there was no bypass other than waiting 7 days
Click to expand...
Click to collapse
downgrading to aug update then trying date hack also impossible?
amakuramio said:
Lol, I succeeded by setting date to past 1 month, upgrading to pie then setting it back to jan after update
Click to expand...
Click to collapse
How what the phone condition before you did the upgrade? you were using it normally, with google, samsung account logged, you had Dev option enabled when OEM appeared? I really need a guide to make this appear for the first time.
scroll-lock said:
How what the phone condition before you did the upgrade? you were using it normally, with google, samsung account logged, you had Dev option enabled when OEM appeared? I really need a guide to make this appear for the first time.
Click to expand...
Click to collapse
I bought it from a second hand shop and tried many times to get oem unlock, from my teenager years I always used xposed so a phone without that is useless. I tried the classical time trick but it didn't work, so in the normal recovery I did factory reset, then didn't login, remove sim, set date one month behind, turn off auto update and time and then connected internet to update, it failed. Then I set date to today and started update it to pie. While it was downloading I put it one month behind, after install I had oem unlock. Before the reboot from oreo it wasn't there in the development options. RMM prenormal prevented me from installing twrp im going to bring this phone back get s8 plus and downgrade to nougat. One week is too long
Related
I just got another monthly update for my AT&T Note 5 labeled N920AUCS4CPL1 with the December 1, 2016 security patch included. I can't find anything else on this update but again, it looks like another security update - - NOT Android 7.0+
@mattern1974, did you take a screenshot or something? What does the about device screen say?
itskapil said:
@mattern1974, did you take a screenshot or something? What does the about device screen say?
Click to expand...
Click to collapse
Here you go!
Second screen shot
mattern1974 said:
Second screen shot
Click to expand...
Click to collapse
mattern1974 said:
Here you go!
Click to expand...
Click to collapse
Thanks man!
mattern1974 said:
Here you go!
Click to expand...
Click to collapse
How did you change your background
MusicHelps said:
How did you change your background
Click to expand...
Click to collapse
Themes in the settings.
Edit: I also use Nova Launcher since I like the speed and customization over the stock Touchjizz.
Can someone please post a link for adb push or odin files, so we can update our n920a as we are not in USA?
Thx.
Wow---this update is KILLING my battery. Google play services is running in the background like crazy. I've lost 10% in 2 HRS with little use where as before the update I would have lost 10% by 2 PM---UGH! Anyone else having this problem?
I updated to PK1 the day I got my phone (last week Monday).
The battery life for me has been superb (since I flashed through ODIN and started setting it up from scratch).
I want to get PL1 (for peace of mind), but I don't have an AT&T SIM card, so I'm waiting for a complete file that I can flash through ODIN.
I don't want anymore updates because I'm almost out of equipment contract now and I want to hack my Note 5. I wasn't aggressive about this until recently but somehow I had auto update on. So my phone started the download but I rebooted it and stuck it in the microwave.. (panic style) Then I tried to downgrade to 5.11 using the PH4 and the PH2 firmwares in succession but PH4 soft bricked me. Then I tried flashing N920AUCS4CPK1. and I got success. Wiped it all back to November 2016 security patch. (I dunno if this works after it installs, I have a sinking feeling it will not work.. There is no firmware available with Dec 2016 security patch that I'm aware so no way to recover if I'm correct in assuming the bootloader is blocking me from downgrades)
Edit: I want stress that fact that my phone never said Dec 2016 security patch, during all this it was still Nov 2016 patch
droidvoider said:
if I'm correct in assuming the bootloader is blocking me from downgrades)
Click to expand...
Click to collapse
With AT&T bootloaders, I thought that was always the case.
You WILL take the update when Nougat arrives. I'm eager to know when that will be. I have no intention of rooting my device to trip Knox.
batuhur said:
Can someone please post a link for adb push or odin files, so we can update our n920a as we are not in USA?
Thx.
Click to expand...
Click to collapse
Here S4CPK1 - to- S4CPL1 -
norbarb said:
Here S4CPK1 - to- S4CPL1 -
Click to expand...
Click to collapse
Thank you very much
Updating now
I find another update from S4CPL1 to S4CQA1 I think this is January security update but AT&T did not released yet. If someone whan to try it is ADB sideload or from sd-card. Remember if you go for it will erase your data. So backup your phone first.
norbarb said:
I find another update from S4CPL1 to S4CQA1 I think this is January security update but AT&T did not released yet. If someone whan to try it is ADB sideload or from sd-card. Remember if you go for it will erase your data. So backup your phone first.
Click to expand...
Click to collapse
Why don't you try it and let us know?
mattern1974 said:
Why don't you try it and let us know?
Click to expand...
Click to collapse
I don't have Note 5
It seems I'll have to wait unit the next big update is released. I have the N920A, but AT&T is not my carrier so I can't get that OTA. I'm currently on PK1. My device is stock and unrooted since I have no intention of tripping knox at the moment.
Anonymously_Unknown said:
My device is stock and unrooted since I have no intention of tripping knox at the moment.
Click to expand...
Click to collapse
With a locked bootloader, it will probably stay unrooted. I don't know of a root for it, would be nice if there was one. I think 5.01 bootlaoder got unlocked... But I keep looking...
Anonymously_Unknown said:
It seems I'll have to wait unit the next big update is released. I have the N920A, but AT&T is not my carrier so I can't get that OTA. I'm currently on PK1. My device is stock and unrooted since I have no intention of tripping knox at the moment.
Click to expand...
Click to collapse
Check the file to norbarb post, and send to your phone via ADB, you can search in google how can you send ota by adb, its easy. Send OTA via adb donesnt affect knox, its install manually OTA.
Many users reported TWO different variants of the April Security Update. One which is labeled April 1st and another April 5th. I am confused by this as well, I want to get all the hotfixes but my build does not match Google's OTA page.
I'm using a Pixel XL 2 and I have April 1st version on TELUS network. I got it yesterday night, the download was 46.6 MB My build number is OPM4.171019.015.A1 BUT per Google official OTA website it says I should have 8.1.0 (OPM2.171019.029, Apr 2018)
Can anyone shed some light on these TWO variants? Many Rogers users got April 1st but a few got April 5th. Bell seems to be all on April 5th. Telus/Koodo seems to be a mixed bag also.
The one you're referring to on the Factory Images page is the stock release for non-carrier Pixel 2s.
Sometimes carrier branded releases come out the same time, but usually they're released after. Carrier branded releases will have different version numbers, as you can see in the previous release history.
ilal2ielli said:
The one you're referring to on the Factory Images page is the stock release for non-carrier Pixel 2s.
Sometimes carrier branded releases come out the same time, but usually they're released after. Carrier branded releases will have different version numbers, as you can see in the previous release history.
Click to expand...
Click to collapse
That still doesn't explain why I got April 1st variant. I don't even know if I got the new hotfixes.
Even Google were surprised to hear that. They told me that eventually. The update is pushed through anyways from Google channels. They escalated the issue.
But first time I see two variants
Waibashi said:
That still doesn't explain why I got April 1st variant. I don't even know if I got the new hotfixes.
Even Google were surprised to hear that. They told me that eventually. The update is pushed through anyways from Google channels. They escalated the issue.
But first time I see two variants
Click to expand...
Click to collapse
Then I direct you here:
http://reddit.com/r/GooglePixel/comments/8abtyt/april_update/dwxnpu5
Two versions a couple of days apart of actually pretty common.
ilal2ielli said:
Then I direct you here:
http://reddit.com/r/GooglePixel/comments/8abtyt/april_update/dwxnpu5
Click to expand...
Click to collapse
That's explained a lot, thanks!
BUT for the Pixel security update. That means im missing on all the bugfixes if I understood correctly... It says here that all the hotfixes are included in. The 2018-04-05 version.
https://source.android.com/security/bulletin/pixel/2018-04-01
The April 5 release contains all of the security patches and bug fixes plus the current updates for Pixel 2, Pixel, Nexus 6P, Nexus 5X and Pixel C. The April 1 release allows OEMs to apply specific patches to correct problems found with AOSP. This has always been the case and I can remember only one time I only had the 1st patch to apply to my Nexus.
stevemw said:
The April 5 release contains all of the security patches and bug fixes plus the current updates for Pixel 2, Pixel, Nexus 6P, Nexus 5X and Pixel C. The April 1 release allows OEMs to apply specific patches to correct problems found with AOSP. This has always been the case and I can remember only one time I only had the 1st patch to apply to my Nexus.
Click to expand...
Click to collapse
So what would explain I have only received the April 1st update ? Is it possible to have two updates in one month? I never noticed that.
This is the first time I get the 1st patch too. I'm not the only one
I was able to update to the 4/5 patch at 8PM, 4/4. I'm on the Pixel 2 XL. Which model do you have? Have you done anything to the stock software?
Pixel 2 XL 64GB Stock OS.
I used the Beta Enrollment in the past, but this is a fresh phone from RMA.
Unable to update Latest Pack
i have already unlocked bootloader, rooted with magisk.
now for latest update, i have uninstalled magisk, trying to flash factory image in fastboot mode. but unable to do so.
Please let me know how to do ?
Max memory error is coming . i have read to update factory image need to critical unlock bootloader.
please suggest ?
Device : Pixel 2 XL
navi_j said:
i have already unlocked bootloader, rooted with magisk.
now for latest update, i have uninstalled magisk, trying to flash factory image in fastboot mode. but unable to do so.
Please let me know how to do ?
Max memory error is coming . i have read to update factory image need to critical unlock bootloader.
please suggest ?
Device : Pixel 2 XL
Click to expand...
Click to collapse
You don't have to uninstall magisk to update your factory image. Have you also unlocked the _critical partition with "fastboot flashing unlock_critical"?? This WILL wipe your phone if you haven't!!
What type of pc are you using?? Laptops have been know to have difficulties with this due to improper USB cables. The pic is the procedure I use each mont to update the stock OS without wiping data :good:
Badger50 said:
You don't have to uninstall magisk to update your factory image. Have you also unlocked the _critical partition with "fastboot flashing unlock_critical"?? This WILL wipe your phone if you haven't!!
What type of pc are you using?? Laptops have been know to have difficulties with this due to improper USB cables. The pic is the procedure I use each mont to update the stock OS without wiping data :good:
Click to expand...
Click to collapse
i have seen screenshot and did the same process but failed in cmd.
i havent unlocked the critical partition . is it required to flash factory image ?
i am using windows 10 Dell Inspiron 13 7000 series.
thanks
navi_j said:
i have seen screenshot and did the same process but failed in cmd.
i havent unlocked the critical partition . is it required to flash factory image ?
i am using windows 10 Dell Inspiron 13 7000 series.
thanks
Click to expand...
Click to collapse
Yes. You have to unlock_critical to fastboot factory images to allow the bootloader to update ?
Badger50 said:
Yes. You have to unlock_critical to fastboot factory images to allow the bootloader to update
Click to expand...
Click to collapse
OMG
can i use directly this command now or i have to use some process to do ?
thank you sir, you saved my time , i have wasted almost 3 hours trying different methods but failed everytime.
navi_j said:
OMG
can i use directly this command now or i have to use some process to do ?
thank you sir, you saved my time , i have wasted almost 3 hours trying different methods but failed everytime.
Click to expand...
Click to collapse
Just put your phone in bootloader mode, connect to pc, open up your command prompt, and run the command...fastboot flashing unlock_critical....
Again, this Will completely wipe your phone! ?
Has GPS lock issue been fixed?
Seems my thread got hijacked
I am using a Verizon pixel 2 xl. Decided to get in to the beta program. Too many of the apps I use on a daily basis crash .After 2 hours I unenrolled on the beta program website. Still have not got the un update yet. Can flash the factory image from https://developers.google.com/android/images or should I just wait longer?
ckilps said:
I am using a Verizon pixel 2 xl. Decided to get in to the beta program. Too many of the apps I use on a daily basis crash .After 2 hours I unenrolled on the beta program website. Still have not got the un update yet. Can flash the factory image from https://developers.google.com/android/images or should I just wait longer?
Click to expand...
Click to collapse
Did you try and check for update? I was enrolled for a few hours and it didn't update until I checked
I am already on P. I want to go back to oreo
ckilps said:
I am already on P. I want to go back to oreo
Click to expand...
Click to collapse
If stock, bootloader locked, unenroll from the beta, you'll get an OTA to downgrade you.
If rooted, then just clean fastboot the latest factory image.
Ok thanks I wait until I get the downgrade then
ckilps said:
Ok thanks I wait until I get the downgrade then
Click to expand...
Click to collapse
I don't think you will get an update back to 8.1 until nexts months security patch.
ckilps said:
I am using a Verizon pixel 2 xl. Decided to get in to the beta program. Too many of the apps I use on a daily basis crash .After 2 hours I unenrolled on the beta program website. Still have not got the un update yet. Can flash the factory image from https://developers.google.com/android/images or should I just wait longer?
Click to expand...
Click to collapse
According to the FAQ it can take up to 24 hours to either get the beta ota or the opt out ota that wipes your phone
Yes, finally got the downgrade at 9 o'clock last night. Was up all night setting it back up. Sorry, I will be waiting until P is offical. Do not run on your main device.
ckilps said:
Yes, finally got the downgrade at 9 o'clock last night. Was up all night setting it back up. Sorry, I will be waiting until P is offical. Do not run on your main device.
Click to expand...
Click to collapse
Most Apps seem to work, some need to be reinstalled to fix the crashing, haven't had any other problems other than my fingerprint sensor, but I'll get that fixed as well.
ckilps said:
Yes, finally got the downgrade at 9 o'clock last night. Was up all night setting it back up. Sorry, I will be waiting until P is offical. Do not run on your main device.
Click to expand...
Click to collapse
They must have fixed the lag of the downgrade, i opted out, checked for an update immediately and the downgrade ota downloaded instantly.
It doesn't appear that even if your in the beta program that you can unlock the boot loader on a Verizon Pixel 2 xl, is that the case for everyone else? I still have the OEM Unlocking toggle grayed out even though I've to P installed via the OTA
thetriplejranch said:
It doesn't appear that even if your in the beta program that you can unlock the boot loader on a Verizon Pixel 2 xl, is that the case for everyone else? I still have the OEM Unlocking toggle grayed out even though I've to P installed via the OTA
Click to expand...
Click to collapse
Why would it change? It isn't a firmware based lock. If you were locked before, you'd be locked on p as well, just like I am on my Verizon pixel 2 xl
SM-G960F/DS
RMM State: Prenormal
OEM LOCK: OFF
FRP LOCK: OFF
KNOX tripped: 1
Current binary: Custom
I just flashed TWRP, Magisk, no-verity, and the samsung root preventer disabler following the guide here. I used Magisk 16.6 (supposedly S9 is officially supported now, but it's still in beta).
Everything was going fine, then after an hour or two it froze on the lock screen, and would NOT come out of it. After a couple minutes, I held volume down and power to reboot, and it went into a soft brick.
I can't flash via download mode as it gives the error "Only official released binaries are allowed to be flashed". It gives that error when I try to start the phone or boot into TWRP as well.
So what are my options to fix this, and is it possible to prevent this in the future?
you must flash the latest firmware, yesterday I happened the same.
angel8502 said:
you must flash the latest firmware, yesterday I happened the same.
Click to expand...
Click to collapse
Man, I was hopeful ng that wasn't the case. I've already started downloading from sammobile.
So what are you going to do from here? Try rooting again? Is there a more up-to-date RMM disabler?
Any one else have any ideas about why this happens ? I just flashed EdyoBlue ROM after being on Soldier ROM --- all was uneventful
Upon first reboot I came to the screen about Custom Binaries --- seemed to have lost TWRP etc.
Only way out was to flash stock, lose root and I assume WAIT ANOTHER 7 DAYS !!!
Any other ideas ? Or ideas on how to prevent in the future?
jcrompton said:
Any one else have any ideas about why this happens ? I just flashed EdyoBlue ROM after being on Soldier ROM --- all was uneventful
Upon first reboot I came to the screen about Custom Binaries --- seemed to have lost TWRP etc.
Only way out was to flash stock, lose root and I assume WAIT ANOTHER 7 DAYS !!!
Any other ideas ? Or ideas on how to prevent in the future?
Click to expand...
Click to collapse
Did you also flash the rmm state bypass? I did, and I'm going to try again with v2.
LysolPionex said:
Did you also flash the rmm state bypass? I did, and I'm going to try again with v2.
Click to expand...
Click to collapse
Well I didn't flash anything prior to EdYoBlue ROM -- I had been running Soldier ROM for a while and it was my understanding that the RMM bypass was included in those custom ROMs and or kernels
Obviously I did something wrong
jcrompton said:
Well I didn't flash anything prior to EdYoBlue ROM -- I had been running Soldier ROM for a while and it was my understanding that the RMM bypass was included in those custom ROMs and or kernels
Obviously I did something wrong
Click to expand...
Click to collapse
Oh... Yeah I don't know about that.
Same problem. Samsung Galaxy S9+ (SM-G965F)
I rooted my Samsung Galaxy S9+ (SM-G965) yesterday with
Odin, Magisk (modified version as official verson doesn't work apparently) and TWRP.
Took about 10 minutes to do all up, and root was successful!!! 20 minutes later it turned itself off!! No matter what i did or tried.....I couldn't turn it back on nor get into recovery (TWRP). All while it was constantly flashing........ (ONLY OFFICIAL RELEASE BINARIES TO BE FLASHED)
Figured it was somehow a soft brick. So i flashed original firmware back onto phone with Odin and all was well. ILL BE TRYING A NEW WAY AND WILL POST RESULTS.
1AussieTradie said:
I rooted my Samsung Galaxy S9+ (SM-G965) yesterday with
Odin, Magisk (modified version as official verson doesn't work apparently) and TWRP.
Took about 10 minutes to do all up, and root was successful!!! 20 minutes later it turned itself off!! No matter what i did or tried.....I couldn't turn it back on nor get into recovery (TWRP). All while it was constantly flashing........ (ONLY OFFICIAL RELEASE BINARIES TO BE FLASHED)
Figured it was somehow a soft brick. So i flashed original firmware back onto phone with Odin and all was well. ILL BE TRYING A NEW WAY AND WILL POST RESULTS.
Click to expand...
Click to collapse
What's the new way? Are you able to flash again already, or do you have to wait 7 days again?
same issue i had to re flash the stock OS & wait for 7 days for OEM unlock now i have that option but i am not sure which method should i use.
RMM STATE PRENORMAL is also what blocks custom binaries from being flashed
Check the TWRP guide on how to deal with that too
LysolPionex said:
What's the new way? Are you able to flash again already, or do you have to wait 7 days again?
Click to expand...
Click to collapse
Unfortunately no success. Have to wait the 7 days . Currently trying to find a work around. Will keep informed.
Any news I got my OEM unlock back any way to root the phone and get a custom firmware to work
rockykv2 said:
Any news I got my OEM unlock back any way to root the phone and get a custom firmware to work
Click to expand...
Click to collapse
Once my RMM status is normal, I'm going to try Soldier's Rom. I've heard good things about it.
You'll need to follow the official TWRP guide first. Both in this S9 forum.
I already tested that It gets stuck on welcome screen it will not go forward
rockykv2 said:
I already tested that It gets stuck on welcome screen it will not go forward
Click to expand...
Click to collapse
I'd ask about that in the soldier Rom thread; sounds like it might be a wipe issue (really not sure), but a ton of people love the Rom, so it's probably something random on your end.
I'd stick with a stock-based rom, as they're usually more stable.
That Max Lee tutorial about s9+ root is outdated. He is a ****ing bull****. He did not even cared to update his post that magisk root method always freeze. And also his rmm unlock fix is not updated too. Did you guys have the august 1 security update? I guess that was the cause of this "Only official binaries allowed" after rebooting. Here's hoping somebody here got an answer for that RMM.
jonathan_moreno91 said:
That Max Lee tutorial about s9+ root is outdated. He is a ****ing bull****. He did not even cared to update his post that magisk root method always freeze. And also his rmm unlock fix is not updated too. Did you guys have the august 1 security update? I guess that was the cause of this "Only official binaries allowed" after rebooting. Here's hoping somebody here got an answer for that RMM.
Click to expand...
Click to collapse
That's kinda the general consensus I've gotten about that tutorial.
I was using the August 1 security update, but I was using v1 of Mesa's RMM bypass. I downloaded v2, and downgraded my Rom to like April or March or something and will try it again, once the prenormal clears.
RMM v2 is here:
https://forum.xda-developers.com/sa...nuary-security-patch-sm-t3739225/post75360965
LysolPionex said:
That's kinda the general consensus I've gotten about that tutorial.
I was using the August 1 security update, but I was using v1 of Mesa's RMM bypass. I downloaded v2, and downgraded my Rom to like April or March or something and will try it again, once the prenormal clears.
RMM v2 is here:
https://forum.xda-developers.com/sa...nuary-security-patch-sm-t3739225/post75360965
Click to expand...
Click to collapse
Bro if you are on august 1 security update too then you are in xu2 bootloader... you cannot downgrade to xu1 bootloader which was before august..
jonathan_moreno91 said:
Bro if you are on august 1 security update too then you are in xu2 bootloader... you cannot downgrade to xu1 bootloader which was before august..
Click to expand...
Click to collapse
Really?! This is literally the first I've heard of this. Do you know if there's a thread discussing this?
Hello, I have been trying to install TWRP on my S9 with snapdragon processor. I'm running pie with november security patch, I enabled OEM on dev settings and followed this guide (https://forum.xda-developers.com/ga...development/twrp-3-2-1-0-sm-g9600-s9-t3803297) but I can't make it pass. I saw some other guides that skip CROM Services (anyway I can't run it as it closes right after I open it). In download mode I got KG Status Checking and OEM Lock : Off but Odin can't flash the twrp I'm using latest version and tried on 2 different PC's even tried the patched version of Odin (runned both as admin) but nothing happens just fails and keep failing. Tried different ways like 15h in the past 3 days but I can't finally make it
Hey Alessandro,
I was just wondering if you were able to overcome from this.
I am having the same issue.
Thanks
stormkingpin said:
Hey Alessandro,
I was just wondering if you were able to overcome from this.
I am having the same issue.
Thanks
Click to expand...
Click to collapse
What seems to be the issue
TheMadScientist said:
What seems to be the issue
Click to expand...
Click to collapse
I have been trying to install TWRP on my SM-9650 (Brazil). I'm running the latest A10 stock rom. I enabled OEM on dev settings and followed this guide (https://forum.xda-developers.com/ga...er-development/g9650zhu6dta7-android-t4051751) but I can't make it pass. CROM app wont work. Though in Dev Options it says my Bootloader is already unlocked. In download mode I get the "only official released binaries are allowed to be flashed" in Odin while trying to flash the twrp.
stormkingpin said:
I have been trying to install TWRP on my SM-9650 (Brazil). I'm running the latest A10 stock rom. I enabled OEM on dev settings and followed this guide (https://forum.xda-developers.com/ga...er-development/g9650zhu6dta7-android-t4051751) but I can't make it pass. CROM app wont work. Though in Dev Options it says my Bootloader is already unlocked. In download mode I get the "only official released binaries are allowed to be flashed" in Odin while trying to flash the twrp.
Click to expand...
Click to collapse
What about in download mode your rmm state or kg status
TheMadScientist said:
What about in download mode your rmm state or kg status
Click to expand...
Click to collapse
OEM LOCK: OFF
RMM STATUS : Prenormal
KG STATUS : Checking
stormkingpin said:
OEM LOCK: OFF
RMM STATUS : Prenormal
KG STATUS : Checking
Click to expand...
Click to collapse
Rmm is why
It's that 168 hour crap. Look up how to bypass rmm status prenormal. It's a security feature.
TheMadScientist said:
Rmm is why
It's that 168 hour crap. Look up how to bypass rmm status prenormal. It's a security feature.
Click to expand...
Click to collapse
Will do. I was reading about that issue.
Tried all the non-paid options and none seems to work.
I'll wait for the 168 hour window then.
Thanks again!
stormkingpin said:
Will do. I was reading about that issue.
Tried all the non-paid options and none seems to work.
I'll wait for the 168 hour window then.
Thanks again!
Click to expand...
Click to collapse
Supposedly if you flash the combo file. Then disconnect all radios. Roll back the clock, turn off auto time update flash firmware. No sim, setup. Then connect to internet and let auto time update it will bypass. Not 100% sure
TheMadScientist said:
Supposedly if you flash the combo file. Then disconnect all radios. Roll back the clock, turn off auto time update flash firmware. No sim, setup. Then connect to internet and let auto time update it will bypass. Not 100% sure
Click to expand...
Click to collapse
That is what I tried, even after flashing Stock Pie
It wont clear RMM State from prenormal. Apparently it works for some people.
I am fairly familiar with this custom ROM thing, but apparently no donut for me this time.
No worries, having to be patience is by no means a struggle for me.
Just bought this device. Will play around with the Q Stock ROM until RMM is normal.
Nonetheless, very nice of you to reply.
You sir have a good soul.
stormkingpin said:
That is what I tried, even after flashing Stock Pie
It wont clear RMM State from prenormal. Apparently it works for some people.
I am fairly familiar with this custom ROM thing, but apparently no donut for me this time.
No worries, having to be patience is by no means a struggle for me.
Just bought this device. Will play around with the Q Stock ROM until RMM is normal.
Nonetheless, very nice of you to reply.
You sir have a good soul.
Click to expand...
Click to collapse
Well you landed with a great set of devs. We got stock q rooted. Where all modding on. Plus los 17.1 was just released in beta. So it's a great time to read up on it all. There is also a Qualcomm telgram support group for help on some of the stuff. You can find that I think in the twrp and los threads