just wanted to share my experience in downgrading my G4's software version and want to let everyone know it's possible.
using the guide by @tabp0le here: https://forum.xda-developers.com/sp...-mellowmallow-debloated-60fps-camera-t3358340
Depending on which current version you are on you will need the official TOT to get the process going. Once you pull your cable use the MellowMallow .img (ZVB) provided by tabp0le in his original guide and his diag commands.
I have successfully downgraded two ls991's to ZVB using this method. I do not know if this will work on other variations on the phone. THE KEY POINT IS THAT I AM VERY SURE THAT WHILE ON ZVI MY ARB WAS ON ARB 4 AND I WAS ABLE TO SUCCESSFULLY DOWNGRADE TO A LOWER software. Here's the thing, my ARB STAYED THE SAME so while ZVB is techincally ARB 2 my ARB stayed at 4.
with this in mind, you should, be able to downgrade to ZVA. I have not tested going from ZVI to ZVA so anyone willing to you will be trying the downgrade at your OWN RISK! I cannot assist you if you brick your phone but at this point I don't think too many people are worried about bricking the phone especially how cheap you can pick one up. the problem remains that you will still be on a higher ARB and the existing root methods were all done on a ARB <=2 .
quick guide (using tabp0le's original instructions):
0. if you haven't yet, read tabp0le's post, download all the files including LGUP and the official TOT for whatever version you are on (if you are on ZVI then download the ZVI.tot)
1. place the ZVB .img custom rom on tabp0le's post in your internal storage default folder. I will say the MellowMallow rom he provided is a a little buggy but the trade-off to be back pre security patch for 6.0 and unlocked sim card was worth it. make sure you use the right rom for your phone. If you have a global phone use the global rom/img. I haven't tested it yet but once you are back on ZVB you should be able to flash the official ZVB TOT so you can have a completely stock LG G4 with ZVB.
2. Place phone in diag mode by dialing ##DIAG# on dialer.
3. hook your phone into pc and change your usb mode to "charge only"
4. open up LGUP, if you have all your drivers installed from tabp0le's post then you should see your phone/version pop up.
5. select the TOT for your installed version on your phone, for me it was ZVI. hit start.
6. THIS IS WHERE YOU NEED ABSOLUTE ATTENTION TO DETAIL. Your phone will reboot. Keep an eye on the completion percent. 9% is the magic number. I would recommend watching your phone though. As soon as it says "COM XX" in green YOU PULL THE USB PLUG. if done right when it pops up, you would have pulled it right at 9%. if you are late, you risk bricking your device. However I will say that I did pull it at 11% before and all I did was replug the USB and allow the software version to update/reboot my phone. everything was fine and I attempted the whole process again successfully. if you just zone out and miss the sweet spot no worries, just allow the software to update and attempt the whole process again, DO NOT TRY TO STOP THE SOFTWARE UPDATE ONCE IT'S PAST 9%.
7. did you nail it at 9%? GREAT! continue on.
8. close down LGUP and open up a command prompt and navigate to the folder with "ports.bat" from tabp0le's post. run ports.bat. the instructions are word for word from tabp0le's post so I will just quote them.
* Now check which COM# for LGDIAG port
* Send_Command.exe \\.\COMxx
* Command to flash is listed next to the download near the end of this post.
* After you issue the command with Send_Command.exe, it should pause for about 2 minutes then go back to #.
* Type LEAVE then pull battery when complete.
Click to expand...
Click to collapse
here are the commands to flash based on version:
US ROM:
dd if=/data/media/0/MellowMallow_LS991ZVB_v1.04.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
Click to expand...
Click to collapse
GLOBAL ROM:
dd if=/data/media/0/MellowMallow_LS991ZVB_v1.04_Global.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
Click to expand...
Click to collapse
if done correctly the command will "process" for a minute, it will look like nothing is happening, but that's a good thing! wait for the # to re-appear after about 3 to 6 minutes. once it does type "LEAVE", unplug your phone and reboot.
VIOLA! you should be on ZVB! hope this helps give this underrated phone some new life for those out there who gave up on it.
to check your version, download Hidden Menu APK
open it up after install and select:
* SVC Menu --> Version Info
https://androidfilehost.com/?fid=745425885120746375
update next post below
follow up post:
Okay! good news. I went ahead and tested flashing another (custom) rom image using above method and everything went fine! I know there aren't a lot of G4 users out there left but hey, it's something..
*WARNING* Again, this is a highly untested process, your risk for brick is very high. Know that before you proceed *WARNING*
just download whatever rom you want and place it in your root internal storage folder.
when you get to
dd if=/data/media/0/"rom_name".img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
Click to expand...
Click to collapse
you will, instead, replace "rom_name" with the name of the (custom) rom you are trying to install. so, for instance, your rom name is "ZVAUltra" you will use:
dd if=/data/media/0/ZVAUltra.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
Click to expand...
Click to collapse
for simplicity sake you can just rename the rom before you put it on your sd card to crom.img or something.
Right now, my LS991 is running UltraPOP AOSP created by @Agimax, his thread:
https://forum.xda-developers.com/sprint-g4/development/rom-mm-ultrapop-aospish-v1-0-t3351164
Bugs:
depending on the rom, you may have some buggy responses. I now have a constant "sd card is corrupt error" so your mileage will vary with this method. working on fixing this. I have NOT tested changing android versions ( android 6.0 to 5.0, etc...) so you will be DOING SO AT YOUR OWN RISK.
edit: more bugs. Once your apps start to update, dialer codes won't work properly (can't put phone in DIAG mode), bluetooth no longer works and you'll have some issues with SD showing up as corrupt. still researching. I might attempt a downgrade to ZV6 stock rom and root (I can dream, can't I?)to see how it goes. updates to come!
the only fix for the dialer code and the other issues is to format your phone either from "backup and reset" option in settings or through recovery mode. don't let your phone update! Put it in airplane mode or take out your SIM card. if you want to return to ZVI follow the steps outlined above with LGUP except this time just allow the update to finish and your phone will be on the latest software version.
I really surprised to see almost no response for this thread. The information provided here is awesome.
ardian1899 said:
I really surprised to see almost no response for this thread. The information provided here is awesome.
Click to expand...
Click to collapse
hahah, thanks! I really didn't expect to get too much response here. Most people only care if I was claiming to have achieved root, which I haven't. I did manage to downgrade to ZV6, which is the "rootable" rom but the few attempts I made at rooting caused a soft-brick and I had to restore a TOT to remove the soft-brick.
A lot of this info here was done by piecing together info others provided on this site so I was passing it along in the hopes this info could help another take another step forward.
From all my messing with this method it is fairly safe, worst I've gotten on two LS991 is a soft-brick, which was easily fixed by using LGUP and a proper TOT with a factory reset. I was originally worried about testing my theory because most claimed the method of getting phone into diag mode and doing something wrong would hard-brick but I've had no such (bad) luck.
lokichaos said:
hahah, thanks! I really didn't expect to get too much response here. Most people only care if I was claiming to have achieved root, which I haven't. I did manage to downgrade to ZV6, which is the "rootable" rom but the few attempts I made at rooting caused a soft-brick and I had to restore a TOT to remove the soft-brick.
A lot of this info here was done by piecing together info others provided on this site so I was passing it along in the hopes this info could help another take another step forward.
From all my messing with this method it is fairly safe, worst I've gotten on two LS991 is a soft-brick, which was easily fixed by using LGUP and a proper TOT with a factory reset. I was originally worried about testing my theory because most claimed the method of getting phone into diag mode and doing something wrong would hard-brick but I've had no such (bad) luck.
Click to expand...
Click to collapse
Yeah.. root must be awesome, but anybody who use LS991 shouldn't ask much, haha.
So you can go down as far as ZV6? that's impressive. Is it using the similar method?
ardian1899 said:
Yeah.. root must be awesome, but anybody who use LS991 shouldn't ask much, haha.
So you can go down as far as ZV6? that's impressive. Is it using the similar method?
Click to expand...
Click to collapse
I spoke too soon on ZV6, it will install and boot to LG logo where it will load in an infinite loop. I tried doing a factory wipe from recovery but that didn't help and I had to restore a custom ZVA rom to get back to functioning. In the ZV6 root thread they mention a infinite boot logo is normal and they did a couple things to fix it but I had no luck. I'm guessing that although the rom works the anti-rollback remains at ARB 4 and is blocking certain functions.
I'm not a dev so this is all trial and error for me. custom roms based on ZVA do work, AFAIK. If someone needed to downgrade to a rom with unlocked sim then this method is perfect, for example.
lokichaos said:
I spoke too soon on ZV6, it will install and boot to LG logo where it will load in an infinite loop. I tried doing a factory wipe from recovery but that didn't help and I had to restore a custom ZVA rom to get back to functioning. In the ZV6 root thread they mention a infinite boot logo is normal and they did a couple things to fix it but I had no luck. I'm guessing that although the rom works the anti-rollback remains at ARB 4 and is blocking certain functions.
I'm not a dev so this is all trial and error for me. custom roms based on ZVA do work, AFAIK. If someone needed to downgrade to a rom with unlocked sim then this method is perfect, for example.
Click to expand...
Click to collapse
I see that.
Very nice, thanks
I used to find a method to make gsm work in a ZVI version and about to give up. Your post is really so helpful. (It's really unexpected that there still have active threads about that old model)
Are the files still available?
Hey @lokichaos I recently picked up a Sprint G4 LS991 with DVI and all I'm hoping to do is unlock it for use on Verizon. Your guide sounds like exactly what I'm trying to accomplish but all of the links on the linked guide by @tabp0le are now broken (maybe I should ask them?). Do you happen to have a copy of the various needed files? I'm fairly happy with my G2 (lol) but the G4 seems like a solid improvement.
lokichaos said:
just wanted to share my experience in downgrading my G4's software version and want to let everyone know it's possible.
using the guide by @tabp0le here: https://forum.xda-developers.com/sp...-mellowmallow-debloated-60fps-camera-t3358340
Depending on which current version you are on you will need the official TOT to get the process going. Once you pull your cable use the MellowMallow .img (ZVB) provided by tabp0le in his original guide and his diag commands.
I have successfully downgraded two ls991's to ZVB using this method. I do not know if this will work on other variations on the phone. THE KEY POINT IS THAT I AM VERY SURE THAT WHILE ON ZVI MY ARB WAS ON ARB 4 AND I WAS ABLE TO SUCCESSFULLY DOWNGRADE TO A LOWER software. Here's the thing, my ARB STAYED THE SAME so while ZVB is techincally ARB 2 my ARB stayed at 4.
with this in mind, you should, be able to downgrade to ZVA. I have not tested going from ZVI to ZVA so anyone willing to you will be trying the downgrade at your OWN RISK! I cannot assist you if you brick your phone but at this point I don't think too many people are worried about bricking the phone especially how cheap you can pick one up. the problem remains that you will still be on a higher ARB and the existing root methods were all done on a ARB <=2 .
quick guide (using tabp0le's original instructions):
0. if you haven't yet, read tabp0le's post, download all the files including LGUP and the official TOT for whatever version you are on (if you are on ZVI then download the ZVI.tot)
1. place the ZVB .img custom rom on tabp0le's post in your internal storage default folder. I will say the MellowMallow rom he provided is a a little buggy but the trade-off to be back pre security patch for 6.0 and unlocked sim card was worth it. make sure you use the right rom for your phone. If you have a global phone use the global rom/img. I haven't tested it yet but once you are back on ZVB you should be able to flash the official ZVB TOT so you can have a completely stock LG G4 with ZVB.
2. Place phone in diag mode by dialing ##DIAG# on dialer.
3. hook your phone into pc and change your usb mode to "charge only"
4. open up LGUP, if you have all your drivers installed from tabp0le's post then you should see your phone/version pop up.
5. select the TOT for your installed version on your phone, for me it was ZVI. hit start.
6. THIS IS WHERE YOU NEED ABSOLUTE ATTENTION TO DETAIL. Your phone will reboot. Keep an eye on the completion percent. 9% is the magic number. I would recommend watching your phone though. As soon as it says "COM XX" in green YOU PULL THE USB PLUG. if done right when it pops up, you would have pulled it right at 9%. if you are late, you risk bricking your device. However I will say that I did pull it at 11% before and all I did was replug the USB and allow the software version to update/reboot my phone. everything was fine and I attempted the whole process again successfully. if you just zone out and miss the sweet spot no worries, just allow the software to update and attempt the whole process again, DO NOT TRY TO STOP THE SOFTWARE UPDATE ONCE IT'S PAST 9%.
7. did you nail it at 9%? GREAT! continue on.
8. close down LGUP and open up a command prompt and navigate to the folder with "ports.bat" from tabp0le's post. run ports.bat. the instructions are word for word from tabp0le's post so I will just quote them.
here are the commands to flash based on version:
US ROM:
GLOBAL ROM:
if done correctly the command will "process" for a minute, it will look like nothing is happening, but that's a good thing! wait for the # to re-appear after about 3 to 6 minutes. once it does type "LEAVE", unplug your phone and reboot.
VIOLA! you should be on ZVB! hope this helps give this underrated phone some new life for those out there who gave up on it.
to check your version, download Hidden Menu APK
open it up after install and select:
* SVC Menu --> Version Info
https://androidfilehost.com/?fid=745425885120746375
update next post below
Click to expand...
Click to collapse
Great post, but the problem I think now seems to be the files are not available for download now on tadpole's mellow mallow thread for ZVB
lokichaos said:
follow up post:
(custom) rom image using above method and everything went fine! I know there aren't a lot of G4 users out there left but hey, it's something..
*WARNING* Again, this is a highly untested process, your risk for brick is very high. Know that before you proceed *WARNING*
just download whatever rom you want and place it in your root internal storage folder.
when you get to
you will, instead, replace "rom_name" with the name of the (custom) rom you are trying to install. so, for instance, your rom name is "ZVAUltra" you will use:
for simplicity sake you can just rename the rom before you put it on your sd card to crom.img or something.
Right now, my LS991 is running UltraPOP AOSP created by @Agimax, his thread:
https://forum.xda-developers.com/sprint-g4/development/rom-mm-ultrapop-aospish-v1-0-t3351164
Bugs:
depending on the rom, you may have some buggy responses. I now have a constant "sd card is corrupt error" so your mileage will vary with this method. working on fixing this. I have NOT tested changing android versions ( android 6.0 to 5.0, etc...) so you will be DOING SO AT YOUR OWN RISK.
edit: more bugs. Once your apps start to update, dialer codes won't work properly (can't put phone in DIAG mode), bluetooth no longer works and you'll have some issues with SD showing up as corrupt. still researching. I might attempt a downgrade to ZV6 stock rom and root (I can dream, can't I?)to see how it goes. updates to come!
the only fix for the dialer code and the other issues is to format your phone either from "backup and reset" option in settings or through recovery mode. don't let your phone update! Put it in airplane mode or take out your SIM card. if you want to return to ZVI follow the steps outlined above with LGUP except this time just allow the update to finish and your phone will be on the latest software version.
Click to expand...
Click to collapse
hey I am recent LG G4 (ls991ZVI) acquiree I tried to download the linksfrom the other guys post, but they were all expired. Can you or anyone help me get this phone rooted I need a starting point.
Related
I tried to unlock my bootloader, following various guides, and kept getting stuck on the "Download Mode !!!" part. I just want to install the latest stable version of Cyanogenmod on my phone since the stock ROM is being a real pain for me (very slow and unresponsive).
I have:
Android 4.1.2
Build Number: JZ054K
Software Version: AME-XXX
I read online that you need the Euro firmware to unlock the bootloader, can I flash the euro firmware and will it mess with my service? I'm confused as to how the firmware affects things since I've read conflicting information. I didn't flash my firmware a few hours before trying to unlock, so maybe that's the problem?
Seriously?
There aren't enough threads and guides for you to read already? Everything you need is already out there on this forum so why start another thread just because you are too lazy to search and read for yourself?
I have read around and have tried a number of guides a number of times. They haven't worked for me and I'm just wondering what i'm doing wrong. Even though all the information is out there, I don't have the experience to understand it apparently. I've spent hours trying to figure things out but i keep reading conflicting info and half-explained steps and now I'm just confused and would like a clear point in the right direction.
So, do i need to reflash the latest firmware, wait a few hours, then try again on a full charge? Or do i need a euro firmware? Which guide should i follow?
I've downloaded a few applications and driver packages and whatnot but if those could possibly conflict with each other and cause problems i could work with a fresh OS. I'm running OS X but i have linux VMs and friends with clean windows installs (mine is all sorts of messed up)
eatfoodnow said:
I tried to unlock my bootloader, following various guides, and kept getting stuck on the "Download Mode !!!" part. I just want to install the latest stable version of Cyanogenmod on my phone since the stock ROM is being a real pain for me (very slow and unresponsive).
I have:
Android 4.1.2
Build Number: JZ054K
Software Version: AME-XXX
I read online that you need the Euro firmware to unlock the bootloader, can I flash the euro firmware and will it mess with my service? I'm confused as to how the firmware affects things since I've read conflicting information. I didn't flash my firmware a few hours before trying to unlock, so maybe that's the problem?
Click to expand...
Click to collapse
It isn't a question of firmware, the phone needs to have an unlockable bootloader to be able to be, well, unlocked. Here is a list http://forum.xda-developers.com/showthread.php?t=2181581 of P880 bootloader versions. Follow the guide to check which BL your phone has.
Thats obsolete, all versions can be unlocked afaik, either with official method or by fuse editing. No need to keep sim card in,you just need proper drivers
Oh, OK, I didn't know that. But, even better, OP should not have any trouble, provided he follows the BL unlock guide here http://forum.xda-developers.com/showthread.php?t=2224020
Maybe his BL is already unlocked OR is relocked (meaning can't be unlocked anymore).
Its more likely that his drivers are messed up imo.
The fuse editing method should work for everyone, i recommend you give it a try
So the fuse method would be the "BL-unlock.bat" method on that bootloader unlock forum post? I've tried it before, but I'll try it again. The directions only say to run it, is there anything else I need? Now, since it's a .bat file I absolutely have to run it on Windows, right? Because if so I'll use a friend's computer instead of my windows installation.
What are the necessary installations before I run the file? How should I configure settings on my phone? (like what type of usb connection should it be)
There are a lot of things that people expect readers to know but I'm really not very knowledgeable about standard practices for phone stuff so I really need every step. Thanks for helping!
Since its.bat file, you can open it in text editor to see which commands it executes. I'd still recommend to do it on windows machine, other OSs may work but aren't tested.
You need abd & fastboot drivers, plus drivers for our device. It's been a while since I've done it, but afaik you can get proper device drivers via lg support tool.
Flying_Bear said:
Since its.bat file, you can open it in text editor to see which commands it executes. I'd still recommend to do it on windows machine, other OSs may work but aren't tested.
You need abd & fastboot drivers, plus drivers for our device. It's been a while since I've done it, but afaik you can get proper device drivers via lg support tool.
Click to expand...
Click to collapse
Also, correct me if i'm wrong I only had stock for 2hours, but also stock needs usb debugging to be enabled or adb won't work?
Yep, afaik usb debugging needs to be enabled
When you are fast enough, it is possible in charging mode wihle the carger animation is shown. But you have install adb driver very fast...
So I'm pretty sure I got the bootloader unlocked, I ran the .bat file and it went through everything until the part where it checks to see if my bootloader is unlocked, it just froze forever, so I closed it.
How should I go about checking?
Also, what would be my next step now for installing CM10.1.3? I tried to follow the guide on the cyanogenmod wiki (install_CM_for_p880) (I can't post links yet)
...but ran into problems with pushing it into root with adb. It said I didn't have permissions, so I googled some stuff, but just got myself confused.
Thanks for all the help btw!
eatfoodnow said:
So I'm pretty sure I got the bootloader unlocked, I ran the .bat file and it went through everything until the part where it checks to see if my bootloader is unlocked, it just froze forever, so I closed it.
How should I go about checking?
Also, what would be my next step now for installing CM10.1.3? I tried to follow the guide on the cyanogenmod wiki (install_CM_for_p880) (I can't post links yet)
...but ran into problems with pushing it into root with adb. It said I didn't have permissions, so I googled some stuff, but just got myself confused.
Thanks for all the help btw!
Click to expand...
Click to collapse
you can check your bl status by entering sw mode (phone off, hold vol+ and insert charger) or reeboting into bl (adb reboot oem-unlock)
to install cm steps are:
-install recovery (you can choose either cwm or twrp, it's more about looks than functions)
-download rom zip onto sd card
-install said zip from said recovery, there's no adb involved
Now my personal opinion, I really don't see the point in flashing 10.1, i would go staright for cm11 if i were you
Ok well I think I got things together more or less, eventually I tried to install CM10.1 with the ROM manager app. I forgot to select the options to wipe my data partitions and now I'm stuck in an endless boot loop every time I turn the phone on. I tried to boot from my backup using CWM which I made with the app prior to trying to install, and it gave me an error about an MD5 checksum failing, no matter what I tried. Should I do the factory reset/wipe option with CWM now? What's my best option.
Also why would you recommend CM11 over CM10.1? I don't want to have to deal with a nightly, all this phone stuff is a supreme headache to me.
eatfoodnow said:
Ok well I think I got things together more or less, eventually I tried to install CM10.1 with the ROM manager app. I forgot to select the options to wipe my data partitions and now I'm stuck in an endless boot loop every time I turn the phone on. I tried to boot from my backup using CWM which I made with the app prior to trying to install, and it gave me an error about an MD5 checksum failing, no matter what I tried. Should I do the factory reset/wipe option with CWM now? What's my best option.
Also why would you recommend CM11 over CM10.1? I don't want to have to deal with a nightly, all this phone stuff is a supreme headache to me.
Click to expand...
Click to collapse
Factory reset then get nandroid manager app and see if you can restore your stuff with that
CM11 is bugless atm and performance (imo) is way superior
So after a factory reset/data wipe, my phone just booted into CM10.1 and now that's working. And it looks like all of my stuff on the phone is still there (though of course apps aren't installed and whatnot, that wouldn't make sense). Thanks for all the help!
I tried to find a feature list or something to see what exactly is better about CM11, and found out that "stable" doesn't exactly mean stable for CM, and that it looks like a good idea to update, so I think I will try to update to that. Do you know anywhere that has an actual feature list to show me what CM11 does that CM10.1 doesn't?
I have a (previously) rooted D950, and I can't get the OTA At&t update to install. I've completely removed root, and double checked through root checker that it's gone, and the update errors out every time with a message about having been rooted.
I read another thread where some people report being able to retain root after receiving the update THEN downgrading and rooting 4.2.2., then installing the OTA again, but it seems that I jumped the gun and rooted first, which is now causing the install to error out.
Has anyone else experienced this? Found a workaround? Ideas? Totally frustrating.
Sent from my LG-D950 using xda premium
Here is the link to a detailed guide . Dev hyelton's page includes links to AT&T ROMs.
If you need help with LG Flash Tool:
- Connect your phone with usb to laptop/computer and open device manager
- seek for Ports: COM & LPT, right click onto Android LTE usb port connection, click "properties", click "Advanced", then change port number to number 41, click "OK"
- DOWNLOAD LG Flash Tool and install .exe
- DOWNLOAD MegaLock.zip (3kb), unzipped (7kb)
- Exchange MegaLock.dll in your system folder "LG" with the unzipped MegaLock.dll file that you have downloaded
- Open LG Flash Tool, input .dll file of downloaded stock rom.zip folder and input .tot file of this folder
- Click onto USB instead of LAN, then click "OK"
- Left arrow at the window top should be enlightened now
- Click onto this arrow
- Wait for all popup windows telling milky way download and connections to fail
- Wait then for the check of CRC and .dll files
- One or all ports should be opened, "READY" enlightened
- Disconnect your phone from computer
- Connect again and watch the immediate start of the flashing process
- After completion you must install most of the app updates, update your LG and/or AT&T profile before installing kitkat update.zip
If you'll stick in updating stock rom to kitkat, watch my video on YouTube (it's about LS995 Sprint, but AT&T LG Flex will proof the same installation process):
Visit my blog at http://www.myreviewsofreviews.for the detailed description how to avoid bootloop during the installation of LG Kitkat update.zip via ADB sideload
Thanks, but this is not a fix. Unfortunately, that guide is of no use since his links are still down. Further, I was hoping for feedback from others who have experienced this issue, and found a resolution. I have read that this is also happening on devices that have not been rooted.
I am not looking to flash a rom through FlashTool. I'm looking to fix the OTA error. All I want to do is install the OTA update.
lorawithano said:
Thanks, but this is not a fix. Unfortunately, that guide is of no use since his links are still down. Further, I was hoping for feedback from others who have experienced this issue, and found a resolution. I have read that this is also happening on devices that have not been rooted.
I am not looking to flash a rom through FlashTool. I'm looking to fix the OTA error. All I want to do is install the OTA update.
Click to expand...
Click to collapse
Not sure what you were hoping for but the guide is correct process for your problem. You need to flash back to 4.2, don't touch anything in the way of modifying system files or deleting bloatware, sign into your main Google account, update all your apps...then root the phone and when it reboots look for the ota. I would give it a couple min to setup after flashing back to 4.2 so that it successfully finds the update rather than telling you you're on the most current software. I had your exact problem too, I was one of the first AT&T users on here to take the update I tried everything to
A: retain root with supersu features and some root cloaker programs etcetera
B: factory reset, call AT&T, to get them to push the update again because I just could not get it to successfully flash without detecting suspicion of root.
Flashing back to 4.2 to retain root worked for me over 4 times now on 3 different flex phones (I had some hardware and then software issues on my replacement model)
Sent from my LG-D950 using XDA Premium 4 mobile app
brittoking said:
Not sure what you were hoping for but the guide is correct process for your problem. You need to flash back to 4.2, don't touch anything in the way of modifying system files or deleting bloatware, sign into your main Google account, update all your apps...then root the phone and when it reboots look for the ota. I would give it a couple min to setup after flashing back to 4.2 so that it successfully finds the update rather than telling you you're on the most current software. I had your exact problem too, I was one of the first AT&T users on here to take the update I tried everything to
A: retain root with supersu features and some root cloaker programs etcetera
B: factory reset, call AT&T, to get them to push the update again because I just could not get it to successfully flash without detecting suspicion of root.
Flashing back to 4.2 to retain root worked for me over 4 times now on 3 different flex phones (I had some hardware and then software issues on my replacement model)
Sent from my LG-D950 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You say flash back to 4.2, but I am already on 4.2. Never left 4.2. That's the issue. The device is defective. They're sending me a new one.
lorawithano said:
You say flash back to 4.2, but I am already on 4.2. Never left 4.2. That's the issue. The device is defective. They're sending me a new one.
Click to expand...
Click to collapse
You didn't understand my post at all it seems, I gave you the instructions to flash back to STOCK which would have fixed your problem. I did accidentally word my post incorrectly saying "flash BACK to 4.2" obviously I knew you were on 4.2, so clearly I meant use the aforementioned guide to flash back to stock then take the update. Looks like you went another route, congrats
Sent from my LG-D950 using XDA Premium 4 mobile app
Huh? Wut
Not sure where things went wrong here.....
Me thinks some thread cleaning is in order...
Stand-by....
Cleaning finished.
Come on folks, let's relax and take a breath. Sometimes things just don't work and there's little to be done about it. If common known procedures don't work, then hopefully something else will, and just move along to something else.
Or in this case, the device is being returned which of course solves all.
No need for anybody to get all bent out of shape, what started out as being helpful, just took a bad turn somewhere for unknown reasons.
Relax, be cool....
MD
KitKat update on ATT G FLEX running on Tmobile.
This might be a stupid question . I have my ATT G FLEX D950 running on Tmobile. It is on Jellybean . I am unable to pull the Kitkat update and it says "Phone is not registered on network". I am assuming I need to get my phone on ATT network to pull the update. Am I right? is there any other way out ?
santy83 said:
This might be a stupid question . I have my ATT G FLEX D950 running on Tmobile. It is on Jellybean . I am unable to pull the Kitkat update and it says "Phone is not registered on network". I am assuming I need to get my phone on ATT network to pull the update. Am I right? is there any other way out ?
Click to expand...
Click to collapse
Kinda, yes.
I had the same problem. My phone was never activated on the ATT network so it would not recognize it. You have 2 options:
Get a prepaid sim from ATT, use it once and than put your Tmobile sim back in there or ask a friend that has ATT to use the sim for a few minutes. A text or a phone call is all you need.
Worked great for me.
(Note: I didn't make any of this software. I just found it all and brought it together. I apologize for not being able to add direct links to each post I got this all from, I didn't record the sites I got them from.)
This is for the people who were unlucky enough to own a VS980 LG G2, rather than the other models which are loved by developers, a phone that is incredibly finicky and niche...
I honestly wish somebody made a guide like this for us VS980 users (a phone which most ROMs don't work on, has a locked bootloader, etc...) before I had to experience this pain.
(Okay, rant over.)
However, I have done it anyway and installed 7.1.1 Nougat on the VS980
(If you don't know the pain I'm talking about, consider yourself lucky...)
I've also gathered all the necessary files to one place so you won't have to hunt like I did. Following this guide to a T should result in a "effortless" to a "dang, I had to do something" modding experience
"Basic" Steps:
Install ALL tools Necessary (Drivers, Programs, Etc...)
Downgrade to Kitkat
Root
Install TWRP and Kernel
Erase Phone
Install Bootstack
Install ROM (CM14.1)
Install Gapps
Reboot and Enjoy (Might take a while first boot.)
Additional Notes (So you guys don't do what I do)
The files are all downloadable here:
Mega: https://mega.nz/folder/nOQiSZhA#geOCtLtVnEqVABogOXhmvA
(The files are 3.3GB so it will take a while.)
Use MegaDownloader to bypass Mega's download restrictions:
https://megadownloader.en.softonic.com/
The folders are marked accordingly to the "Basic" steps listed above.
Follow each of them in order and Open the "READ ME" text file in each for instructions.
Good luck!
(Sorry for the Bland-looking Post and Files, I don't really have a knack for making colorful Guides.)
EXTRA:
If you'd like to try getting 8.1, Here's a link to a ROM (I tested) that works:
https://forum.xda-developers.com/lg-g2/development/rom-aospextended-rom-v5-6-t3802329
Just make sure you flash the bootstack. Files are found in Folder: "9.Things to Try"
Basically follow the same steps (Downgrading, TWRP, etc...)
-Use Magisk to Root (Better than Super SU because, installed properly, it will hide your root so you don't
have to use Root Cloak.) <=(Pokémon GO)
NOTICE: WHEN REBOOTING AFTER FLASHING, DO NOT PRESS INSTALL SUPER SU
Just press do not install. You can root later....
[ Installing Super SU can possibly brick your phone and you'll have to start over ]
(It's just that every time I press that button, it never works... but I'm not sure )
If you brick your phone (Black screen of death), you can use a USB jig to get it to download mode and use the .kdz flasher (Lg Flash Tool) to restart from the beginning with the stock software.
USB jigs are really cheap (like <2$. I just made one myself ) and are incredibly useful to get out of tight situations. If you plan on modding a lot in the future, you should consider getting one.
(If you don't know what I am talking about, try to keep it that way.)
ADDITIONAL RESOURCES:
I thought I should add this (You're welcome BTW)
Bootstacks:
https://forum.xda-developers.com/ve...resources-bootstacks-unofficial-t3050777/amp/
Stock Kdz and Tot Files:
https://lg-kdz-firmware.com/lg-g2-firmware/36.html
(If any download links don't work, I can update them)
Dude, you are the boss.. Been doing this forever, and it is always appreciated when I find someone who puts it all in one place.. MANY MANY thanks to you for putting all this in one place.. Also thanks to the coders who made it possible..
angael said:
Dude, you are the boss.. Been doing this forever, and it is always appreciated when I find someone who puts it all in one place.. MANY MANY thanks to you for putting all this in one place.. Also thanks to the coders who made it possible..
Click to expand...
Click to collapse
Glad I helped
Is anyone still out there?
All of the Mega linked folders are empty, am I doing something wrong?
As a side note, my objective is to upgrade the ROM to at least Marshmallow so I can install Android Auto and Screen2 Auto. There is one app I want to use but it isn't allowed by Android Auto. I'm then hoping to make the phone a dedicated Android Auto "server" and leave it connected to my car's USB port. Any guidance on the best way to do this would be appreciated.
My VS980 is currently on the stock Android 5.0.2 ROM.
Update: I managed to get CM14.1 installed following the "Basic" steps. It took some trial and error but I got there.
If anyone finds this thread and knows of a better ROM for my use I'd be interested in hearing about it.
RKCRLR said:
Is anyone still out there?
All of the Mega linked folders are empty, am I doing something wrong?
As a side note, my objective is to upgrade the ROM to at least Marshmallow so I can install Android Auto and Screen2 Auto. There is one app I want to use but it isn't allowed by Android Auto. I'm then hoping to make the phone a dedicated Android Auto "server" and leave it connected to my car's USB port. Any guidance on the best way to do this would be appreciated.
My VS980 is currently on the stock Android 5.0.2 ROM.
Update: I managed to get CM14.1 installed following the "Basic" steps. It took some trial and error but I got there.
If anyone finds this thread and knows of a better ROM for my use I'd be interested in hearing about it.
Click to expand...
Click to collapse
What happened? I do have LG G2 VS980 and works fine to me. I'm actually in Android 11 now. Links are down? How come?
Absolute Territory said:
What happened? I do have LG G2 VS980 and works fine to me. I'm actually in Android 11 now. Links are down? How come?
Click to expand...
Click to collapse
I think the files expired in Mega (or I'm doing something wrong to access them).
My phone seems to be working OK but I don't use it for making phone calls.
My main problem now is I can't figure out how to access fastboot. I get a "waiting for any device" response when I issue any fastboot command. I can get to the download screen where it is waiting for a firmware update but I can't get past that.
Re uploaded the MEGA link. Don't know why there weren't any files there anymore. It is probably because I didn't check it for a while.
Root instructions on the RP2 forum seem to assume a level of familiarity with rooting, and general instructions on the web seem to want to cover every possible device which means they cover every means of rooting options and device types and Android versions, and it isn't clear reading those where to start with the RP2.
I've found people on XDA tend to be pretty welcoming to dumber questions, so here's my dumb question.
If I have an "unlocked" (non-AT&T) device running 9 Pie, can someone translate this post:
https://forum.xda-developers.com/razer-phone-2/development/root-pie-update-unlocked-devices-t3905454
Into usable instructions for those of us new to rooting? I have a Windows computer, a USB-A to USB-C cable (since the C-to-C cable that comes with the phone isn't suitable?), and an unrooted Razer Phone 2 on Pie.
I enable developer options in my phone's settings by tapping the version 7 times. I got that part.
Now, what do I download to my device? A boot image and magisk (?)? The boot image from the thread above, right? How do I ensure what I download to my phone goes to my phone and not the SD card? Is that a dumb question? Do I just remove the SD card before downloading anything?
Then what do I download to my computer? The Android SDK, or some smaller thing? Fastboot something something? ADB something something?
Then I plug my phone in to the computer, enable OEM unlocking in Dev settings on my phone, anything else while I'm in there? USB debugging?
Then I open CMD on the computer? Or some program?
Then I have to check slots, or something? Boot_a vs boot_b?
Then I give what instructions in the command line? What does each one do? I'm coming from a web Dev background where commit comments and //comments or <!--comments--> explain anything new or unexpected or whatever. Similar explantions for each instruction would be ideal. What does each one do?
Any common problems and common fixes, or explanations behind any Razer Phone 2-specific quirks to the process we should be aware of?
Help with any or all of these would be appreciated.
Thank you.
AbsoluteContingency said:
Root instructions on the RP2 forum seem to assume a level of familiarity with rooting, and general instructions on the web seem to want to cover every possible device which means they cover every means of rooting options and device types and Android versions, and it isn't clear reading those where to start with the RP2.
I've found people on XDA tend to be pretty welcoming to dumber questions, so here's my dumb question.
If I have an "unlocked" (non-AT&T) device running 9 Pie, can someone translate this post:
https://forum.xda-developers.com/razer-phone-2/development/root-pie-update-unlocked-devices-t3905454
Into usable instructions for those of us new to rooting? I have a Windows computer, a USB-A to USB-C cable (since the C-to-C cable that comes with the phone isn't suitable?), and an unrooted Razer Phone 2 on Pie.
I enable developer options in my phone's settings by tapping the version 7 times. I got that part.
Now, what do I download to my device? A boot image and magisk (?)? The boot image from the thread above, right? How do I ensure what I download to my phone goes to my phone and not the SD card? Is that a dumb question? Do I just remove the SD card before downloading anything?
Then what do I download to my computer? The Android SDK, or some smaller thing? Fastboot something something? ADB something something?
Then I plug my phone in to the computer, enable OEM unlocking in Dev settings on my phone, anything else while I'm in there? USB debugging?
Then I open CMD on the computer? Or some program?
Then I have to check slots, or something? Boot_a vs boot_b?
Then I give what instructions in the command line? What does each one do? I'm coming from a web Dev background where commit comments and //comments or <!--comments--> explain anything new or unexpected or whatever. Similar explantions for each instruction would be ideal. What does each one do?
Any common problems and common fixes, or explanations behind any Razer Phone 2-specific quirks to the process we should be aware of?
Help with any or all of these would be appreciated.
Thank you.
Click to expand...
Click to collapse
Hi I create a post that might help you, check it out. https://forum.xda-developers.com/razer-phone-2/how-to/root-pie-guide-t3910407
BTW the moderator will likely move this to the questions area.
AT&T Version ?
New to the RP2 community..
Thinking of getting the AT&T RP2 and wanted to find out/confirm if the AT&T version can be OEM UNLOCKED so you can unlock the bootloader.
Thanks in advance,
RJR
AbsoluteContingency said:
Root instructions on the RP2 forum seem to assume a level of familiarity with rooting, and general instructions on the web seem to want to cover every possible device which means they cover every means of rooting options and device types and Android versions, and it isn't clear reading those where to start with the RP2.
I've found people on XDA tend to be pretty welcoming to dumber questions, so here's my dumb question.
If I have an "unlocked" (non-AT&T) device running 9 Pie, can someone translate this post:
https://forum.xda-developers.com/razer-phone-2/development/root-pie-update-unlocked-devices-t3905454
Into usable instructions for those of us new to rooting? I have a Windows computer, a USB-A to USB-C cable (since the C-to-C cable that comes with the phone isn't suitable?), and an unrooted Razer Phone 2 on Pie.
I enable developer options in my phone's settings by tapping the version 7 times. I got that part.
Now, what do I download to my device? A boot image and magisk (?)? The boot image from the thread above, right? How do I ensure what I download to my phone goes to my phone and not the SD card? Is that a dumb question? Do I just remove the SD card before downloading anything?
Then what do I download to my computer? The Android SDK, or some smaller thing? Fastboot something something? ADB something something?
Then I plug my phone in to the computer, enable OEM unlocking in Dev settings on my phone, anything else while I'm in there? USB debugging?
Then I open CMD on the computer? Or some program?
Then I have to check slots, or something? Boot_a vs boot_b?
Then I give what instructions in the command line? What does each one do? I'm coming from a web Dev background where commit comments and //comments or <!--comments--> explain anything new or unexpected or whatever. Similar explantions for each instruction would be ideal. What does each one do?
Any common problems and common fixes, or explanations behind any Razer Phone 2-specific quirks to the process we should be aware of?
Help with any or all of these would be appreciated.
Thank you.
Click to expand...
Click to collapse
rrusek said:
New to the RP2 community..
Thinking of getting the AT&T RP2 and wanted to find out/confirm if the AT&T version can be OEM UNLOCKED so you can unlock the bootloader.
Thanks in advance,
RJR
Click to expand...
Click to collapse
I have a rp2, att, bootloader unlocked, rooted, on global pie firmware. Not Sim unlocked, but don't care to move carriers.
jonchance_84 said:
I have a rp2, att, bootloader unlocked, rooted, on global pie firmware. Not Sim unlocked, but don't care to move carriers.
Click to expand...
Click to collapse
Same phone/firmware but I cannot get it rooted. It boot loops or gets stuck at Powered by Android logo with fast boot so at least I can re flash the stock global firmware and boot that. Seems no rooted boot loader works nicely for me. If you have any advice I would appreciate it.
i did fastboot boot_a nd boot_b with reboot but now im stuck on razer loading screen. does this mean im stuck in a bootloop?
It did turn out pretty easy.
I wiped all data, flashed the global MR1 image, booted system and took OTA update to MR2, rebooted to bootloader and flashed Arter 12 kernel, rebooted to Arter TWRP recovery, wiped Dalvik, flashed Magisk 20.1, wiped Dalvik, rebooted system >>> Profit!
Got Edxposed, Gravitybox and Greenify running and all banking apps load perfectly. It's just like the old days of modding, LOL!
Wifi is noticeably improved compared to my previous experience with the phone as well.
Total noob question
gboybama said:
took OTA update to MR2
Click to expand...
Click to collapse
What do you mean? You rooted, then upgraded "normally" to MR2? (I had to look up what OTA is, and it's "over the air"? As in a "normal" upgrade for people who let all their things just update as they please?) I ask because I thought once you rooted, normal updates weren't available?
All the tutorials I find are to upgrade to the MR1 boot.img (which my phone will boot with), then upgrade to the arter97 .img which leaves my phone in an endless booting state. (This is the exact step-by-step I followed: https://forum.xda-developers.com/ra...er-phone-2-t3914996/post79489415#post79489415 -- should be post #94: Castanoff 8th May 2019, 11:07 PM). I started out at MR2, I guess from when I updated the phone to a September update before attempting root. (Its original date was January 2019.)
I'm confused at the whole Magisk thing, as I was assuming that's after the arter update?
Tincan17 said:
What do you mean? You rooted, then upgraded "normally" to MR2? (I had to look up what OTA is, and it's "over the air"? As in a "normal" upgrade for people who let all their things just update as they please?) I ask because I thought once you rooted, normal updates weren't available?
All the tutorials I find are to upgrade to the MR1 boot.img (which my phone will boot with), then upgrade to the arter97 .img which leaves my phone in an endless booting state. (This is the exact step-by-step I followed: https://forum.xda-developers.com/ra...er-phone-2-t3914996/post79489415#post79489415 -- should be post #94: Castanoff 8th May 2019, 11:07 PM). I started out at MR2, I guess from when I updated the phone to a September update before attempting root. (Its original date was January 2019.)
I'm confused at the whole Magisk thing, as I was assuming that's after the arter update?
Click to expand...
Click to collapse
Not at all. I totally factory reset my phone and wiped everything. Flashed the latest stock factory image from Razer that I could find at the time (March 2019?). That put me on the older stock ROM, non-rooted. From there, I just booted into the system and kicked off the (as you put it) "normal" check for updates in the system options. That got me to the September version. Next, I flashed Arter's root and custom recovery kernel IMG file with the bootloader and installed the Magisk zip from TWRP recovery.
Update: Actually, it looks like the build number I'm currently running is now available on the Razer site, so flashing back to an earlier version and taking the OTA update is no longer required. You could just flash their latest system image, which they're putting out there as December 2019. (has the same exact build number as my September build) Then the Arter boot.img and a compatible Magisk zip will complete the root.
Just remember that flashing a full Razer system image in this way will erase your internal (non-SD card) storage. I lost some photos doing this.
Is there any way someone can or has a video on ho wto do this. Or maybe a similar phone thats the same.. But i can just use the specific files for my phone instead... This compared to regualr jailbreaking is like reading chinese. I switched from apple to androd rp2 and i love android way better. But these act more computer based. As far as files and stuff like that
I've been beating my head against the wall here. I've tried both MR0 and MR1. When I type in the fastboot command, all I get is < waiting for any device > My phone is in fastboot mode. I have the right drivers installed. I can see my phone using the adb devices command, so WTF?
scottysize said:
I've been beating my head against the wall here. I've tried both MR0 and MR1. When I type in the fastboot command, all I get is < waiting for any device > My phone is in fastboot mode. I have the right drivers installed. I can see my phone using the adb devices command, so WTF?
Click to expand...
Click to collapse
Try running this tool and see if it helps with fastboot. Let it run it'll boot your phone into the bootloader automatically and install all drivers.
https://forum.xda-developers.com/an...astboot-installer-tool-windows-t3999445/page1
When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting. I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging.
jwils1236 said:
When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting and wouldn't have bought it if I would have known (or at least not updated to Pie). I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging/impossible. Any help would be appreciated and if a solution is brought to light, I am gladly offering $. This could easily be considered a device with best hardware and when rooted, access to best software -- I didn't see significant enough improvements in Note 9 and figured by now the support from XDA community would be abundant for the exynos processor. Turning out ridiculous waste of money if I can't root it (already purchased silver carbon fiber skin, 256 GB Samsung Evo Select SD card, attachable portable wireless charging pack, etc.). Please help!
Click to expand...
Click to collapse
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.
Its just easy step
Things u needed before proceed
* SD card
*Magisk latest version
*Odin
* Twrp zip file
1. Reflash ur device with proper firmware
2. After done go download mode and flash Twrp zip on odin. After done reboot ur device to Twrp again
3. After boot up to Twrp go to Wipe and do a factory restore . After this done u must install Magisk or u will get official binary only after reboot to system
4. After all the step are followed u are good to go. Cheers
stonedpsycho said:
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.
Click to expand...
Click to collapse
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
Also, for anyone reading this with the same issue, extracting the boot image from stock firmware (can be done through command prompt/terminal dump or by extracting from stock firmware -- AP Odin file) and patching with Magisk will not flash or work/give root access either unless this device is fully unlocked -- OEM unlock doesn't matter, if RMM still says "Prenormal" in download mode.
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I am quite sure it is still rootable on bootloader 6, so updating would be fine.
The trick to get the OEM toggle is a bit hit and miss, the guide below is the method that has had a higher success rate for me, if followed exacty as written.
https://www.google.com/amp/s/www.xd...-samsung-galaxy-s8-samsung-galaxy-note-8/amp/
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I ended up using Chimera Tool to bypass RMM state. Worked instantly. This seems to be a common issue for many Samsung devices, at least on Pie. Not sure there is an alternative solution, currently. Only one I could find for my device.