Hi buddys... i have a issue, a really big issue
I have a moto g8+, and I was want to update them to android 11, and a see a tutorial on youtube but my bad was no see about the tutorial was only for moto g8
After make the update with the wrong rom, the phone still working but without IMEI, the wifi and bluethooth is still work.
When I tried to flash the device with the correct ROM, i got a error like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Checking the device, on setting>about phone> android version, the phone shows that had android 10 but the Rom that i used was this:
(the latest version on the official page to moto g8, not g8+):
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
I already tried use smart assist, the official software from motorola, to restore the device, but the same problem, the flash failed when the program try to flash the bootloader flash.
Seeing the files from the smart assist a found the correct rom, thats was i use to tried flash again but return the preflash failed.
Comparing both roms i noticed that the first one is REV retail and the second one (the correct) is DOHA retail.
It's supposed to be that my phone is DOHA because the model is XT 2019-2 (and i am from mexico, also the smart assist download the doha version).
When i use the comand to get info across the adb platform, its show me the next info:
The bootloader was change by the wrong file.
I guess that the error from the preflash failed bootloader is because the adb platform cant flash a bootloader with a lower version, remember about the wrong flash was with a android 11 version .
At the same time i tried to change the rom to a custome rom but the device have lock the oem options, i have the code provided by the motorola official page to unlock the bootloader, but i cant unlock them.
The device have deactivate the option to allow the oem unlock
Browsing on other posts, i found some options to fix them, the first one was wait 7 days to the phone activate the option by himself, did not work.
The second one was change the device to guest account and after return to the owner account, also did not work.
After that i thought... wait, the android system is like a mini linux, i supuse can use the adb shell to force the activation of the oem option to install a custome rom.
Searching across the web, i found some information about that. using the next command a tried allow the oem unlock, but the same story, they did not work:
service oem_lock 1 s16 1
This one in particular i thought it would work, but no, the same story, did not work.
Bue the Shell return me a message (i dont have a this moment the shell) like this:
cant allow the oem unlock, contacto to your carrier to unlock.
something curious is when i flash the wrong rom, only the first and second file was flash correctly, the other command display an error:
Only the red text work, the other some did not.
Also when i tried to flash the correct rom, it's the other way around, only the command to flash the bootloader fail.
But here i got a new 'error command', anti roll back.
I knew the bootloader is from android 11, then, when try to flash the bootloader to android 10 display that error, at the same time i knew i need the bootloader unlock to make a downgrade... but i cant unlock them
when i make this in particular, the device turn on in a bootloop, and I need flash the wrong rom to the device turn on "normally" without IMEI
I guess I've spent all my resources to fix them.
i need the device, already now i cant buy a new phone.
Someone can help me?... Pleaseeeeee
And sorry for my bad english, I know my spelling is horrible, I'm just learning.
I hope you can understand me
Also im sorry if the post is in the incorrect place, i tried to post them on the section that i supuse is the correct place
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since it has no thread decided to make a thread for the Vitria since this little thing has potential.
Specs
4 Inch LCD
Quallcomm MSM8930 1200mhz CPU
Rear 5Mp/Front 1.3Mp Cameras
1750mah Battery
1GB Ram
Android 4.1.1
Performance:
Stock
-Quadrant:4,400
-Antutu:11500
Stock Debloated
-Quadrant: 4,950
-Antutu: 13,500
Overclock Kernel(1.7Ghz)
-Quadrant: 6,570
-Antutu: 18,200
Rooting
The Vitria can be Rooted 4 ways
Kingo Root (works with B137 update)
Cydia Impactor(works with B137 update)
FarmaRoot (not recommend but works)
SuperSU CWM Installed(Requires bootloader unlock and CWM)
ENABLE USB DEBUGGING AFTER ROOTING/KEEP IT ENABLED, IF YOU BRICK THIS CAN SAVE YOU FROM HAVING TO COMPLETELY WIPE
Roms(no CWM Needed)
I have uploaded the stock rom from huawei here, its especially useful if you brick and don't have cwm installed.
http://d-h.st/49v
-How to install stock rom(If bricked or otherwise)(Will wipe all data)
- --Copy dload folder to the root of a micro-sd card
- --hold vol up+vol down+power to enter recovery(force mode) and wait for it to finish
--- will reboot when done if not pull battery
--- wipe data as above.
Backed up files
Stock Recovery
http://d-h.st/wB2
Stock Boot.img
http://d-h.st/9QR
-How to restore boot and recovery with adb(can't use fastboot if bootloader locked)
--use dd command in adb
(WARNING)Brick Land
Bootloader Unlock
The bootloader unlock code should be obtained by emailing huawei, try following this layout
URGENT Bootloader Unlock Vitria <-- SUBJECT
- IMEI =
- Serial Number =
- Device =
Be sure to keep it as simple and discrete as possible
Clockworkmod/TWRP
I have built CWM and TWRP for it already, you can find them here.
http://forum.xda-developers.com/showthread.php?p=47234338#post47234338
http://forum.xda-developers.com/and...vitriay301-t2809324/post53999091#post53999091
-How to Install
--flash in fastboot only, not adb(requires bootloader unlocked)
---fastboot flash recovery recovery.img
Roms(CWM needed)
Rooted Deodexed, Zipaligned + Init.d Stock Rom(B132)
http://d-h.st/bkq
-How to install
--Install in CWM
]What to do if you have bricked
YOU NEED ACCESS TO THE STOCK RECOVERY TO RESTORE(If you have CWM or TWRP installed you should know what to do).
If you never updated flash the stock rom with the install method above
http://d-h.st/49v
If you updated use this hacked one instead to downgrade to B132 completely(then simply do the ota update again)
http://d-h.st/6SO
If you screwed the stock recovery and your bootloader is locked but its still accessible via pow + vol down, try to get the bootloader unlock code and reflash the stock recovery once unlocked then reinstall the stock rom
If successful your device should be restored back to out of the box factory state.
Kernel source
http://consumer.huawei.com/en/support/downloads/detail/index.htm?id=17935
hope this thread helps
Excellent
Super!!! Finding things for this cellphone is not easy, This is the most complete thread I have found for this cell phone, Thanks
Don't you know if there is any custom rom for this cellphone?
bootloader unlock tool
Ok.. so I got this device super cheap to jump on the unlimited lte for $50 deal metropcs had going. Tried downloading the chinese tool you had listed above, but its chalked full of malware unfortunately. Any other unlock options other than emailing huawei directly [[email protected]] and requesting [which I read on a like thread at android forums]? Did that a week ago with no response. I'm a bit worried this device is not supported anymore because of its age. Could be. Any input/suggestions you might have though are appreciated.
Regards,
Rob
insink71 said:
Ok.. so I got this device super cheap to jump on the unlimited lte for $50 deal metropcs had going. Tried downloading the chinese tool you had listed above, but its chalked full of malware unfortunately. Any other unlock options other than emailing huawei directly [[email protected]] and requesting [which I read on a like thread at android forums]? Did that a week ago with no response. I'm a bit worried this device is not supported anymore because of its age. Could be. Any input/suggestions you might have though are appreciated.
Regards,
Rob
Click to expand...
Click to collapse
devhost kinda sucks now(stopped using them but the old links are still up) and its hard to download from them because of fake link(with adware) next to a real one, anyway the monkeytool was blocked buy huawei over and over until the maker of the software gave up and stopped releasing new versions for it a good while back so I'm gonna remove it.
for unlocking the bootloader I would try to send another email and put URGENT on it, that sped it up for me(on my first vitria) used the tool for another one.
there might be other methods to get the code like the script hack here http://forum.xda-developers.com/and...tory-image-t3008551/post59408408#post59408408 , I tried it but couldn't get it to work though.
personally I don't really use my vitria anymore though but hopefully someone else with chime in and post another method.
I probably clicked the wrong d/l link... over a week w/ no reply from Huawei.. perhaps you could relink the monkey tool & I'll try to be smarter
Called Huawei today 888-5HUAWEI and they gave me same instructions. I then told them it had been over a week with no response; to which, they said if the phone is no longer supported, there will be no response. A nice lil reply of this device is no longer supported would have solved this riddle for me a week ago. But apparently, this method no longer works for this device [emailing official support]; so, I'm gonna have to try some alternative method(s).
Update
I tried to update but I keep getting install abort check software version and I never seen a file Ending in msp.7z is that the right ending
you have to extract that file 7z is a 7zip archive.
Hello all,
My goal is to image my phone with TWRP(which I have used when I had a rooted EVO2,) I am not after root. My goal is to test different NON-ROOT backup programs and restore if something is missing. So I have to ask the experts here, I see NO official TWRP rom for sm-g930t, whats the deal?
Here is what I find at TWRP website for Samsung Galaxy S7 (Exynos) (herolte)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
imgur.com/ABMYYc9
The alternative is the Chinese variant. Also why does it say herolte in the first place? This is not to be confused with the hero phone?
This concerns me as I find guides to install TWRP for the sm-g930t from places like androidinfotech.com/2017/03/root-samsung-galaxy-s7-t-mobile-sm-g930t-nougat.html and Youtube.com using ENG-Root-USA.zip as the TWRP rom.
Thanks in advance for any help,
XDAGuy
G930T is Snapdragon SoC which has a locked bootloader, you aren't getting TWRP onto it, it's not possible.
herolte is the codename for the Exynos SoC S7's, which is the SoC you need for TWRP.
Beanvee7 said:
G930T is Snapdragon SoC which has a locked bootloader, you aren't getting TWRP onto it, it's not possible.
herolte is the codename for the Exynos SoC S7's, which is the SoC you need for TWRP.
Click to expand...
Click to collapse
Thanks @Beanvee7. So am I able to image my emmc partitions with adb for my cloning purposes atleast? Can they ever be returned? And finally you are saying if I have G930T, I cannot install TWRP on it period (even with Odin)---then what are some tutorials and success for... trololol? And is this lock thx to T-Mobile?
Thanks,
XDAGuy
emmc partitions I believe fall under boot partitions, which are locked by the bootloader.
Yes I am saying the G930T cannot install TWRP on it period even with Odin.
Odin can only flash what the device permits, and a locked device won't permit boot modifications.
If you can find me a tutorial where they successfully flashed TWRP onto a G930T I'd like to see it.
The lock applies to all USA models, it's not specifically T-Mobile. It was likely AT&T and/or Verizon that forced the requirement onto Samsung.
Smaller carriers would be prevented from allowing an unlock method, because it could then be used on AT&T and Verizon models since they have the same SoC.
Beanvee7 said:
emmc partitions I believe fall under boot partitions, which are locked by the bootloader.
If you can find me a tutorial where they successfully flashed TWRP onto a G930T I'd like to see it.
Click to expand...
Click to collapse
I linked one in the first thread(without the protocol +www for anyones imagination,) they limit new posters on links. I also found one on you tube with people saying in comments worked on G930T, however cant find it since I cant search comments and its annoying.
androidinfotech.com/2017/03/root-samsung-galaxy-s7-t-mobile-sm-g930t-nougat.html
or
fastunlocker.in/root-samsung-s7-sm-g930t.html
Finally, whats this @ 1:49 youtube.com/watch?v=3yJY9RSpV0c, for custom OS? Cant change boot but can OS?
Those guides are both nonsense tbh, first one is full of errors without any photo or video, second one under the TWRP says 'we can't provide the files, find them yourself', so where's TWRP?
The video they show is also for a different model.
As for your youtube video, that's just standard recovery and download mode. All Samsung phones display the same warning, even models that can't actually flash custom firmware.
TWRP looks like this
Standard recovery looks like this
After some more digging, there is this:
https://forum.xda-developers.com/tmobile-galaxy-s7/development
https://forum.xda-developers.com/verizon-galaxy-s7/development
You still don't get full custom ROM's, but you can run some modded zips.
Beanvee7 said:
After some more digging, there is this:
https://forum.xda-developers.com/tmobile-galaxy-s7/development
https://forum.xda-developers.com/verizon-galaxy-s7/development
You still don't get full custom ROM's, but you can run some modded zips.
Click to expand...
Click to collapse
You da man, very much appreciated for your time. I checked out the piece by Kevin, looks like he spent alot of time on it. Thanks for helping, but again, I was just looking to get TWRP installed so I could image my phone and test non-root backup solutions. I do not want ROOT atm. From what I am gathering I cannot change the boot parition to put TWRP, correct? And via ADB I cannot image my phone? And if I could image my phone, I couldnt restore the images to my phone, correct?
Thanks again,
XDAGuy357
So what do you folks think of the new Lenovo Smart Tab P10? I just ordered one because my LG G Pad 8.3 v500 is very long in the tooth and I finally just got tired of waiting for a good spec tablet with plenty of storage and memory to show up. It only has a midrange Snapdragon 450, but the storage a memory make up for that.
https://www.lenovo.com/us/en/smart-tab/
I was looking for a owners manual to read and found this. Looks like replacing the battery in the future won't be too bad. I'll cross my fingers and hope that the bootloader is unlockable.
https://download.lenovo.com/consumer/mobiles_pub/tab_p10_hmm_en_201812.pdf
https://fccid.io/O57TBX705F/User-Manual/User-Manual-R1-pdf-4117204.pdf
Open Source Code
TB-X705F (Wi-Fi)
https://support.lenovo.com/us/en/downloads/DS506312
TB-X705L (LTE)
https://support.lenovo.com/us/en/downloads/DS506313
Stock Roms
TB-X705F (Wi-Fi)
Lenovo TB-X705F_USER_S000017_20180831_Q00020_ROW Factory ROM [androidhost.ru].zip
TB-X705L (LTE)
Lenovo TB-X705L_USER_S000023_20180921_Q00020_ROW Factory ROM [androidhost.ru].zip
I received my Lenovo Smart Tab P10 (TB-X705F) a few weeks ago. It's a nice tablet with good features. The only thing I'm struggling with is unlocking the bootloader. The developer options have the "Allow OEM unlocking" setting and I've enabled it, but no unlock commands are recognized when in fastboot mode. The error is "FAILED (Unknown command)". I've tried "fastboot oem unlock", "fastboot oem unlock-go", "fastboot flashing unlock" etc.
I hope Amazon didn't force Lenovo to lock down the bootloader because it has Alexa poopoo installed. I figure there will be a Chinese exploit for this and the LTE version eventually.
I couldn't stand Alexa and disabled it. I'm looking forward to TWRP so I can make a backup, root and install Adaway.
Same here....
Hey guys, I got the same issue, all unlock commands are unknown. Has anybody got a fix yet?
I had no problem with the bootloader, Tb-x704v. Install most recent https://devsjournal.com/download-minimal-adb-fastboot-tool.html it solved some of my issues.
I bought one a few weeks ago... No dock though. Seems ok, their os is pretty slim though, can't wait for some development.
it is project treble supported but still no lineage 16.1 (pie)? for lenovo tab P10 TB-X705L
Hi, you should be able to unlock bootloader with this command:
fastboot oem enable-unlock-once
TWRP
I installed the TWRP Builder app, but it couldn't extract the recovery image and build.prop file because I don't have root. Do you think that a TWRP recovery can be made from the older firmware in my first post? It has a recovery.img file, but couldn't find a build.prop file.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How do we get this device in to it's only device thread? When you search for it through "my device" in the xda app it doesn't come back with a correct result. Maybe it will also get more community development by doing that.
Any hope lineage 16.1 for lenovo tab P10
Hello all,
Any developments on this device. What are the chances of getting rid of the echo features and make it a Google assistant instead?
Can anybody share the alexa show mode apk? I'm downloading the firmware but it is taking ages
Any one been able to install the Google Now Launcher in this tablet? The Play Store message says that it's incompatible with this tablet.
Thanks for any assistance!
Did anybody try to unlock the bootloader in Linux?
I successfully rooted Z3 Play in Linux while it didn't work in Windows
Can anybody find full ROM in lollinet (where I can find Moto/Lenovo ROM)?
I've tried installing the stock images that are posted and keep getting a signature error using the recovery. I noticed that the image doesn't have a system.img but rather system_1.img-system_32.img. Is there a way to package the system files to install the new system? Having an issue with the OTA and it keeps wanting to install the PRN rather than the ROW image. Any thoughts?
Anyone successfully root this as of yet? Not seeing any TWRP for it or an approach.
I today received an update to Android 9 on my tablet. Was kind of surprised. Anyone else can confirm?
Update contains new "Le Tab UI".
so there is no way to root this tablet?
gforums said:
I today received an update to Android 9 on my tablet. Was kind of surprised. Anyone else can confirm?
Update contains new "Le Tab UI".
Click to expand...
Click to collapse
Confirmed. I'm at Android 9 after an OTA update.
Chaser
---------- Post added at 08:27 PM ---------- Previous post was at 07:58 PM ----------
ZHIONZY said:
so there is no way to root this tablet?
Click to expand...
Click to collapse
My tablet is rooted. I found a root solution a little while back, but I haven't posted it yet because it's not very user-friendly. Basically it requires that you do a fresh install of Oreo and it gets bricked on an OTA update. If you're interested in getting it rooted like that then send me a private message. If there's enough interest I'll create a root thread. I consider myself quite capable with Android but not a full expert. I'm really hurting without custom recovery and without a fastboot OEM unlock that works longer than once. That temporary unlock command successfully allows me to swap out the bootloader image but upon reboot it doesn't like the new image as it asks for a password that must be part of the bootloader security because it won't accept any passwords that I have set. Perhaps with a root thread we could all contribute to getting this working. I have two of P10s now so I'm able to test on my spare, but I don't have unlimited time to devote to this.
I know that a lot of people would be excited to get root on this device. I assure you sure you that it is possible. However, I don't want to start a thread with a solution that will force people to do a fresh install of Oreo and possibly lose data. And of course there's the problem with the OTA update which will brick the device. Of course everyone understands that they modify their device at their own risk, but I consider my root solution still a bit dirty and I was hoping at least to get it to accept OTA updates before I wrote up a root guide. I really think that if we could get a permanent bootloader unlock instead of a temporary unlock that we could get past this problem. And if somebody is out there that could make a TWRP image for this device, I think we would be golden as we could do a standard magisk root install via custom recovery.
Chaser
i have a moto g pure from xfinity mobile i found a stock zip file using the lenovo rsa i then copied the boot image then ran it through the magisk app i then fast boot it and this is the error i get i did oem unlock in settings and also fastboot oem unlock it sends to phone then starts to write and this is the error can someone smarter please help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
moderater sorry im new please foward to appropiate forum thank you
My guess is you've a driver problem.
Use the driver offered here:
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
motorola-global-portal.custhelp.com
jwoegerbauer said:
My guess is you've a driver problem.
Use the driver offered here:
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
motorola-global-portal.custhelp.com
Click to expand...
Click to collapse
not a driver problem its a failed verification on the stock patched.img through magisk diferent verifiction key for the two images
OK
So did you ever get it figured out? I have the moto g pure as well. I have it bootloader unlocked but have been unable to find a boot.img to try to use Magisk on. The stock file I tried to get from the Motorola tool keeps giving me an error saying the file failed to decompress....
Agent_Orange1488 said:
So did you ever get it figured out? I have the moto g pure as well. I have it bootloader unlocked but have been unable to find a boot.img to try to use Magisk on. The stock file I tried to get from the Motorola tool keeps giving me an error saying the file failed to decompress....
Click to expand...
Click to collapse
No I never did how did you get your bootloader unlocked?
Agent_Orange1488 said:
So did you ever get it figured out? I have the moto g pure as well. I have it bootloader unlocked but have been unable to find a boot.img to try to use Magisk on. The stock file I tried to get from the Motorola tool keeps giving me an error saying the file failed to decompress....
Click to expand...
Click to collapse
Newportswag74 said:
No I never did how did you get your bootloader unlocked?
Click to expand...
Click to collapse
There is your boot img
Newportswag74 said:
There is your boot img
Click to expand...
Click to collapse
Thanks a ton!!! Bootloader unlock was simple for me (T-Mobile). https://androidbiits.com/unlock-bootloader-motorola-moto-g-pure-xt2163-4-easily/
The guide at this link worked perfectly for me!! I will let you know how Magisk root goes
Agent_Orange1488 said:
Thanks a ton!!! Bootloader unlock was simple for me (T-Mobile). https://androidbiits.com/unlock-bootloader-motorola-moto-g-pure-xt2163-4-easily/
The guide at this link worked perfectly for me!! I will let you know how Magisk root goes
Click to expand...
Click to collapse
Really when I tried that at the Lenovo website it said my pure wasn't eligible
did patching that boot work?
i managed to patch the latest firmware with march security update, and root the stock rom, now i need to mess with gsis
I got an s10e from an ebay refurbisher but couldn't get OEM unlock to show up no matter how many times I did all the steps (connect wifi > change date > disable auto updates in dev options > tap download updates etc). At some point, I happened upon a tutorial that showed how to unlock the bootloader with computer usb + volume down + bixby on boot. To my surprise, it only gave me the option for *locking* the bootloader.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The OEM unlock option still doesnt even show up in the options however, not even grayed out. I do wonder if the refurbisher flashed their own vanilla rom onto this since it says the binary is custom . I imagine this is probably good to go?
I then tried to flash both stock firmware and that same firmware flashed with magisk with no success. I want to install /e/ android onto this, which like a lot of other rom installation guides, explictly says that I should update to latest firmware. In this case, the latest android 11 firmware available, or else downgrading from stock 12 to /e/ 11 could cause problems (according to the /e/ instructions).
Odin just didnt work. I tried multiple usb ports, multiple firmwares, multiple cables, multiple versions of Odin. The only consistent behavior is that trying to flash using odin freezes on startup, with a red error text showing up on the download screen. Using home CSC makes a SECURE CHECK FAIL : (BOOTLOADER) error show up, using factory wipe CSC makes a SECURE CHECK FAIL : (PIT) error show up. Some articles say to try using the pit option, but the odin warning of DO NOT USE THIS TAB has me apprehensive. This is as far as I've gotten.
So the problem turned out to be that I was sold the wrong product. Not cool refurbisher, not cool, maybe not even legal. Anyways, as you can tell in the download mode, this is not the SM-G970F that I was sold, its a SM-G970N. Still runs an exynos chip, but it's a korean model. Not certain how the refurbisher got the phone to show up as a F skew without the "THIS ISNT OFFICIAL SAMSUNG FIRMWARE" warning and all that.
Flashing firmware specificaly for the N skew worked just fine. I flashed the latest verison of android 11 KTN firmware for the phone and it worked, just needed a factory reset from recovery after I flashed the firmware. After I did so, the OEM unlock option showed up in developer options, already greyed out and turned on.
I next decided to try flashing /e/ android using the build madefor the F skew, and it worked without any fuss! I am now happily running a custom firmware like I planned to do when I bought this. I may get a weird boot screen in korean, but that's the least of my concerns.