Database Develop

Android 4.4 KitKat installation failed on nexus 7 (2012)

Hello,
I had a problem with my nexus 7 today, hope someone will help me.
Today i got a notification that says, new android system has been downloaded.. touch to install..
So i tapped the notification, and if anyone who has nexus 7 and got an updated before.. he will know exactly mo problem.
So i clicked the button "reboot and install".. my device has been rebooted .. and there was that screen like cmd in Windows.. i remember some messages from it "MD5 not found" then the the deviced booted and didn't get Android kitkat update.
Information about my nexus 7 device:
1) It's rooted.
2) I've Android 4.3.
My Questions are:
1) How can i get that notification another time to try install it again?
2) When i go to Recovery.. Install.. I see the ZIP file for Android 4.4, it's name was "kataski" i think, my question if i flashed that ZIP file.. means i've installed kitkat manually, then i'll lose my auto updates?
Waiting for the reply.
Thanks

Mob_Dev said:
Hello,
I had a problem with my nexus 7 today, hope someone will help me.
Today i got a notification that says, new android system has been downloaded.. touch to install..
So i tapped the notification, and if anyone who has nexus 7 and got an updated before.. he will know exactly mo problem.
So i clicked the button "reboot and install".. my device has been rebooted .. and there was that screen like cmd in Windows.. i remember some messages from it "MD5 not found" then the the deviced booted and didn't get Android kitkat update.
Information about my nexus 7 device:
1) It's rooted.
2) I've Android 4.3.
My Questions are:
1) How can i get that notification another time to try install it again?
2) When i go to Recovery.. Install.. I see the ZIP file for Android 4.4, it's name was "kataski" i think, my question if i flashed that ZIP file.. means i've installed kitkat manually, then i'll lose my auto updates?
Waiting for the reply.
Thanks
Click to expand...
Click to collapse
Hi,
As per: http://forum.xda-developers.com/showpost.php?p=47648484&postcount=2342
OTAs will never work on a system which is modified in some way, because they contain only bytes which were changed between two Android versions. If files on the device are changed (custom ROM, different kernel, MultiROM-injected init, sometimes even root), OTA simply can't be applied. Everyone who roots his device should be aware of that.
Wait for the flashable ZIPs,
Click to expand...
Click to collapse
So, instead of OTA (over-the-air), you can simply download the image files directly from Google Android's site: https://developers.google.com/android/nexus/images#nakasi

topet2k12001 said:
Hi,
As per: http://forum.xda-developers.com/showpost.php?p=47648484&postcount=2342
So, instead of OTA (over-the-air), you can simply download the image files directly from Google Android's site: https://developers.google.com/android/nexus/images#nakasi
Click to expand...
Click to collapse
Aha, i see. So maybe because i've rooted my nexus 7, and i've also got a different kernel for MultiRom( I've installed ubunto touch on my device). ... Those the reasons that leads the installation to be failed?
Anyway, my system auto downloaded the update, it name was "nakasi".
I tried to go to Recover mode, and tried to flash the nakasi ZIP file and flash it,,, but the operation was failed!
What should i do?
How i get auto update installation for kitkat on my nexus 7?
Another question, if i downloaded the Factory image from the link you gave me: https://developers.google.com/android/nexus/images#nakasi and flash it in Recovery Mode... Let say it will success? then i''ll lose auto system update on my nexus in future - because it will be installed manually.
=========
Please Copy the questions in your reply, and post the reply below each one.
Thanks

You modified your rom, therefore, you cannot ota. Use the full images or restore the rom to normal (kernel and whatever else you did).

topet2k12001 said:
Hi,
As per: http://forum.xda-developers.com/showpost.php?p=47648484&postcount=2342
So, instead of OTA (over-the-air), you can simply download the image files directly from Google Android's site: https://developers.google.com/android/nexus/images#nakasi
Click to expand...
Click to collapse
That quote isn't exactly correct. My N7 (tilapia) is rooted, unlocked & twrp recovery. The OTA worked fine. I had to reroot (which us normal), but its clear evidence that's contrary to "OTA's will never work on a system that has been modified in some way". In fact, wug's toolkit thread has multiple comments where people go it the OTA after rooting, unlocking & installing a different recovery. That said, mods MAY result in OTA's failing.
Sent from my Nexus 7 using XDA Premium 4 mobile app

khaytsus said:
You modified your rom, therefore, you cannot ota. Use the full images or restore the rom to normal (kernel and whatever else you did).
Click to expand...
Click to collapse
Can you guide me how to install kitkat on my nexus 2012 - rooted and modified ROM.
What do I need?

Another 4.4 Upgrade failure
I am having problems with the OTA upgrade too. However I am running a unmodified/rooted version of 4.3. I have also tried sideloading the factory zip and doing OTA and sideload from a factory reset.
I get the dead android and red triangle error and if I go to the restore menu then this is the error report I get each time
{
"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"
}
/system/apps/hangouts.apk produces some type of verfication error.
I can then reboot and I am back to 4.3
Any thoughts on solutions are gratefully recieved

Mob_Dev said:
Can you guide me how to install kitkat on my nexus 2012 - rooted and modified ROM.
What do I need?
Click to expand...
Click to collapse
You can use this ZIP( http://forum.xda-developers.com/showthread.php?t=2528090) file flash using recovery. You can use cyanogenmod window installer to give nexus new life and then revert to kitkat. Using that zip. This zip can update via ota. Just help
Sent from my Nexus 7 using XDA Premium 4 mobile app
PS: cyanogenmod window installer auto root your rom

dbgeek said:
That quote isn't exactly correct. My N7 (tilapia) is rooted, unlocked & twrp recovery. The OTA worked fine. I had to reroot (which us normal), but its clear evidence that's contrary to "OTA's will never work on a system that has been modified in some way". In fact, wug's toolkit thread has multiple comments where people go it the OTA after rooting, unlocking & installing a different recovery. That said, mods MAY result in OTA's failing.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
We are probably agreeing to refer to the same thing; maybe it was just a little miscommunication.
If we take only the first sentence of the quoted post "as-is", then it may contextually be construed as an over-generalization (to which, I agree that it is not exactly correct). However if we read the entirety of the quoted post, it was explained further that if a user has a "different kernel and multiROM-injected init), then OTA cannot be applied.
...to which, this thread's OP eventually mentioned that he has "a different kernel for MultiROM" installed.
But as far as being able to receive the OTA, yes I did receive it (rooted and running MultiROM); I just couldn't apply the OTA update. To solve, I performaed a "fresh install", i.e. download and install factory image method.

yusopa said:
You can use this ZIP( http://forum.xda-developers.com/showthread.php?t=2528090) file flash using recovery. You can use cyanogenmod window installer to give nexus new life and then revert to kitkat. Using that zip. This zip can update via ota. Just help
Sent from my Nexus 7 using XDA Premium 4 mobile app
PS: cyanogenmod window installer auto root your rom
Click to expand...
Click to collapse
I am following this guide to install Android kitkat on my nexus 2012 (Wifi only): http://www.droidviews.com/install-kitkat-factory-image-on-nexus/
But if you can see the last step satisfy that i need to flash the 4.4 Factory Image, type, using the following command:
fastboot -w update image-nakasi-krt16s.zip
Click to expand...
Click to collapse
The problem is that, the nakasi file i downloaded from here: https://developers.google.com/android/nexus/images
is not a ZIP file!. It's (.tar) file. And i can't process that command!!
Let me know what is the problem.
Thanks in advance

topet2k12001 said:
We are probably agreeing to refer to the same thing; maybe it was just a little miscommunication.
If we take only the first sentence of the quoted post "as-is", then it may contextually be construed as an over-generalization (to which, I agree that it is not exactly correct). However if we read the entirety of the quoted post, it was explained further that if a user has a "different kernel and multiROM-injected init), then OTA cannot be applied.
...to which, this thread's OP eventually mentioned that he has "a different kernel for MultiROM" installed.
But as far as being able to receive the OTA, yes I did receive it (rooted and running MultiROM); I just couldn't apply the OTA update. To solve, I performaed a "fresh install", i.e. download and install factory image method.
Click to expand...
Click to collapse
My bad. I read the "different kernel..." as an example of mods that might be made, that could cause failure, not a specific listing of mods that would cause a failure (implying that if the mod's not on the list then it wouldn't be a problem).

So i have the same problem, but aditionally my Windows 8 is unable to recognize my Nexus 7 while in recovery mode and i can't mount the sdcard to install a new rom. Only recognizes it as "grouper". Any advice?

I think Wug Fresh for nexus toolkit can help you guy to bring back your nexus to life. I use from the start.
Sent from my Nexus 7 using XDA Premium 4 mobile app

CM Recovery for Nexus Player (fugu)

This is the CM-12.1 recovery for fugu.
Use the bottom button to navigate. One push to scroll down and long press to select. I've tested both adb side load and install from internal storage. This recovery also supports adb backup, but I haven't tested it yet.
I hope you enjoy not having to fastboot everything.
Download: fugu_cm_recovery-20150418.img
To install just boot bootloader and
Code:
fastboot flash recovery fugu_cm_recovery.img

Dude, quit being so amazing. It's getting ridiculous.

Excellent! This is the first custom recovery available for this device, correct? I suppose this would open the door to something like the Xposed Framework being installed on the Nexus Player but since my device is running on Android 5.1, I'll probably wait until rovo89 officially adds support for the latest version of Android first.

Yes!!! Glad to see you!

@WugFresh

@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Dear Developers,
It has come to our attention that due to excessive ads that simulate download buttons, fly-by malware APK attacks from Mobogenie, and reused (and potentially dangerous) reused short URLs, Dev-Host no longer meets our minimum acceptable requirements as a hosting affiliate. As such, we are ending our affiliation with this provider. We urge you to find a safer download host for your development projects such as our other affiliates: Goo.im and AndroidFileHost.
Click to expand...
Click to collapse
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]

GabbyWC said:
Excellent! This is the first custom recovery available for this device, correct? I suppose this would open the door to something like the Xposed Framework being installed on the Nexus Player but since my device is running on Android 5.1, I'll probably wait until rovo89 officially adds support for the latest version of Android first.
Click to expand...
Click to collapse
Yes this is the first recovery for the device but last I checked Xsposed had nothing to do with recovery. This will allow for custom firmware like cm-12.1 to be flashed to the device without having to use fastboot.
---------- Post added at 03:27 AM ---------- Previous post was at 03:17 AM ----------
WugFresh said:
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
Click to expand...
Click to collapse
I have to agree with Wugfresh on this bro AndroidFileHost is great. All you need to do is @ the guy on Twitter and he'll hook you up with a developer account complete with ftp access.
Wugfresh the issue with a revision on this is it's cm's android bootable recovery so technically anytime a commit is made to that repo it would be a revision change.

I'll host the updated image somewhere else tonight and I will be adding the date to the end of the image so you can tell if it is updated.

bkjolly said:
Yes this is the first recovery for the device but last I checked Xsposed had nothing to do with recovery. This will allow for custom firmware like cm-12.1 to be flashed to the device without having to use fastboot.
Click to expand...
Click to collapse
The Q&A for Xposed on Android 5.0 at http://www.xda-developers.com/xposed-framework-for-android-lollipop-is-here/ contains this quote:
I want to install it. Now! What do I have to do?
Make sure that you’ve read my words above and you’re familiar with your phone’s internals. Obviously, you need to be on a Lollipop ROM and have a good backup of your data. For now, I will only publish the ARMv7 version. 64-bit is more complex, so let’s try the “easy” variant first.
For now, the installation has to be performed manually in a custom recovery. Flashing the zip file will install:
* app_process32_xposed and some symlinks
* libexposed_art.so
* libart.so and some related binaries + libraries (based on 5.0.2, enhanced with support for hooking etc.)
* XposedBridge.jar (now stored in /system/framework)
Backups of existing files will be created automatically and could be restored later.

Can confirm a working flash. Everything looks great! Thanks for all the hard work

no option to make a recovery image...whats the point of this then?
I tried to wipe my cache to free some space and it sent my nexus player into a bootloop...whats going on with this?

How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!

Edit

Noob
I'm a bit of a noob - I have managed to ADB a new boot and system image to my nexus player - it's now running lollipop1.6. What does this recovery mean and how is it different than loading a boot and system image? Thanks - Does this require ClockworkMod?
dhacker29 said:
I just got my Nexus Player last night and made a working version of CM recovery for it. Use the bottom button to navigate. One push to scroll down and long press to select. I've tested both adb side load and install from internal storage. This recovery also supports adb backup, but I haven't tested it yet.
I hope you enjoy not having to fastboot everything.
Download: fugu_cm_recovery.img - 8.41 MB
To install just boot bootloader and
Code:
fastboot flash recovery fugu_cm_recovery.img
Click to expand...
Click to collapse

OathYvne said:
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Click to expand...
Click to collapse
if you restored your backup you would be downgrading it from the update you just took. you dont need a custom recovery to back up apps and their data, there are apps for that. a custom recovery makes it so its easier to flash new/custom roms(os), make backups of the current rom(os) so if anything goes wrong you can restore it, flash zips like the supersu zip or xposed framework. if you try take an ota with a custom recovery the ota will fail to install as its looking for the stock recovery(may be diff on a nexus device but its always been like that on the devices i have owned)

OathYvne said:
How exactly does this work? If my device is rooted on 5.1.0 and I flash this custom recovery. Can I make a backup of everything on the device? Then when google goes to update the android version, can I update it, then restore my backup of everything and not lose root? I'm sorry i'm new to custom recovery and not quite sure how they work. Thank you for your help!
Click to expand...
Click to collapse
This recovery does not provide a "nandroid" type backup where all of your info is zipped up and stored on the devices internal storage, where any application can get access to it, but rather supports adb backup. which backs up your information to a file on your computer. See http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351 for more information on usage.

WugFresh said:
@dhacker29 Sweet! Thank you! May I suggest you don't use dev host to host this file . They use to be good a while back, but now often employ sketchy MITM type "download manager" scams, and other bad practices. From the original dev thread http://forum.xda-developers.com/showthread.php?p=54363645 -
Just a heads up. I had a bad experience with them before I saw that post.
Also, it would be awesome if you had a naming convention with version number for all future releases (assuming you plan on updating it); like "cm_recovery_fugu_1.0.0.img" or something.
Thanks again! I know lots of people have been patiently waiting and hoping for a fugu recovery. [emoji106] [emoji106] [emoji106]
Click to expand...
Click to collapse
I swtiched to andriodfilehost and uploaded the latest version.

dhacker29 said:
I swtiched to andriodfilehost and uploaded the latest version.
Click to expand...
Click to collapse
Thanks for an update. I tried to full backup by following commands.
adb backup -apk -shared -all -f C:\backup20151904.ab
But getting this "Now unlock your device and confirm the backup operation" lines and asking for unlock your deivice to confirm. Any sugestion to pass this. Thanks

Yes it seems Google decided to remove the backup confirmation dialog from TcSettings

So it means adb backup of a full ROM is not possible? Going to try your rom later.
Sent from my Nexus 6 using Tapatalk 2

S7 EDGE [7.0] UNLOCKED (G935UOYM4BQD2) +OTA UPDATES(BQH3) [File: 1.85 GB] 4.11.17

NO AT&T BLOATWARE, ALL STOCK & UNLOCKED, FAST DOWNLOAD, QUICK AP LOAD + OTA UPDATES!
{
"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"
}
WARNING: BEFORE EVER FLASHING A NEW FIRMWARE TO YOUR DEVICE, YOU MUST REMEMBER - Flashing this firmware will erase the entire Internal Storage of your device... not just your app data, but also your private photos, music, text messages, call log and everything else that hasn't been synced or backed up will be completely erased when the drive for your device is entirely formatted when flashing your new firmware. KEEP READING TO LEARN HOW TO SYNC YOUR DEVICE, BACK UP YOUR DATA AND SAVE YOUR SANITY.
This is the unlocked version specified for AT&T S7 Edge models
But will work on the compatible S7 devices listed below.
:::This firmware will work for G935U, G935T, G935A, G935AZ, G935P, G935V, G935R4 Models ONLY:::
Filesize is only 1.85GB! Fast AP Load, Fast Flash, Snappy Rom, Can Remove/Uninstall Most Leftover Bloatware. OTA updates is confirmed to be working! I am now running G935UUEU4BQH3-NRD90M.G935UUEU4BQH3 because of the OTA update, and can now install S8 APKS like the latest version of TouchWiz, Gallery, MyFiles and more!
BACKUP YOUR DEVICE
○Sync App Data
Helium
○Download Win version
Smart Switch for Windows
(New Windows installations need this file installed on your PC if SmartSwitch gives a "Side by Side" installation error: 64 bit machines need both x86 and x64 files to install, x86 machines only need the x86 file to install Samsung SmartSwitch)
vcredist_x86.exe
vcredist_x64.exe
○Download Mac version
Smart Switch for MAC
○Download Mobile App(Needed For PC/MAC Backups)
Smart Switch Mobile
○Backup Your Phone using Desktop Computer
SyncMe
¡BE SURE YOU'VE BACKED UP YOUR ENTIRE PHONE BEFORE PROCEEDING TO FLASH THIS FIRMWARE!
DOWNLOAD FIRMWARE
DOWNLOAD G935UOYM4BQD2
HOW TO INSTALL
○Download Odin PC and v3.12.7(Just in case)
ODIN PC DOWNLOAD
ODIN DOWNLOAD
○Extract Odin ZIP file.
○Right click Odin and click Run as Administrator.
○Power Off phone and boot into Download Mode (Hold Home + Power + Volume Down)
○Select Continue on the warning screen.
○Connect phone and wait until you get a blue sign in Odin that says Connected
○Unzip and add files to BL, AP, CP, CSC
OPTIONS
○Make sure Re-Partition is NOT selected
○Fully Unroot: Select Phone Bootloader Update (Removes EngBoot Changes)
○Click Start
HOW TO OTA UPDATE
○Click Settings
○Click System Update
○Click Update Manually
○Click Confirm Update
INSTALL S8 APKS
○Download APK FILE
DOWNLOAD S8 APKS
○Click Install
○Click Unknown Sources
○Install APK
○Click Done
S8 APK INFO: You do not need Device Manager.
Alternate TouchWiz APK provided in case one doesn't work.
INSTALL PIXEL OREO LAUNCHER APK
○Download APK FILE
DOWNLOAD OREO LAUNCHER
○Click Install
○Click Unknown Sources
○Install APK
○Click Done
INFO
Reasons to install: Can receive OTA firmware updates, Unlocked for all carriers, doesn't have that branded bloat feel, RUNS SMOOTH after caching, can uninstall and disable most leftover stock Samsung apps (Bloatware). Cannot delete Facebook, etc, but you can still disable the app.
OP INFO UPDATE: CAN NOW INSTALL S8 APKS AFTER UPDATING FIRMWARE OTA TO VERSION G935UUEU4BQE2
HELP SECTION
Are you trying to flash this rom but you are stuck?
Here are the answers that most ask for in order to flash a ROM.
ODIN FAILED TO WRITE ERROR
Did you get this Failed To Write Message in Odin?
----------------------------
Odin Error Message:
<ID:0/003> FAIL! Model dismatch fail
<OSM> All threads completed. (succeed 0 / failed 1)
---See-Figure-Below---
SOLUTIONS
Did you:
○ Open Odin as Administrator?
○ Try the Prince Comsy version?
○ Enable Developer Settings?
-Open Settings > About Phone > Tap Build Number 7 Times
○ Enable OEM Unlock?
-Go Back to Settings > Tap Developer Options > Tap OEM Unlock
○ Enable USB Debugging?
-Tap Developer Options > Tap USB Debugging
NOTHING WORKS
Did you try every single thing but nothing works?
Well, did you right click "Odin" each time you go to open it and then click "open as administrator"?
Sometimes you have to try several different versions of Odin.
But I have found that Odin3 v3.12.7 was the one that would work when the others had not.
I always would forget to also open Odin as Administrator.
It's a pain in the neck to have to remember to open as admin every time.
But you usually have to do it.
Did you check that ADB had started? Maybe that might be the reason it won't work?
But I doubt it! But you just never know and I am just trying to help you get it flashed.
It's a very quick flash and you can see that the PDA load was very quick as well.
But as far as the errors, you just have to keep trying...
Which I mean, you sometimes have to open, close, reopen Odin when it doesn't work.
Sometimes that helps, sometimes it doesn't.
It's all about the right Odin version at the time
making sure the cord is good
Opening Odin as Admin
And keep trying again after restarting your phone by holding the download mode button sequence again.
Sometimes a fresh start will work, sometimes a restart of the PC will help
Basically, you just have to keep trying. I am on G935A too. I had the same issues, but I never gave up!
Keep trying, you'll get it!
Thanks for trying the rom guys! You are all awesome and helping me make the initial OP better with every question you ask, so thanks!
SCREENSHOTS
Several apps you see in these screenshots are not installed with this ROM
I am Just showing that Carrier Bloatware is minimal
I TAKE NO CREDIT FOR THIS BUILD, I ONLY FOUND THE FILES, EDITED INSTALLATION INSTRUCTIONS FOR THE LATEST UNLOCKED VERSION WITH THE SMALLEST FILESIZE, THEN SHARED AND DOCUMENTED IT HERE IN THE S7 FORUMS AFTER TESTING ROM.
A THANKS IS APPRECIATED.
PS, USING THIS FIRMWARE WILL NOT MAGICALLY "UNLOCK YOUR PHONE" YOUR PHONE WILL STILL STAY LOCKED TO YOUR PHONE'S CARRIER AFTER FLASHING THIS FIRMWARE. THIS IS ONLY THE FACTORY UNLOCKED VERSION OF THIS ROM.

This i can aplly with the 7.0 version of s7 edge att? build february 2k17? this can receive OTA update?

alexraptor4 said:
This i can aplly with the 7.0 version of s7 edge att? build february 2k17? this can receive OTA update?
Click to expand...
Click to collapse
Yes you can and it's reported that you can receive OTA with this firmware.

Overall, the only root method is still the engboot method?
I'm running tmo firmware on mine, but have been toying with the idea of flashing U.

t12icky0 said:
There is no specific at&t unlocked version. Plus there is already 2 threads with this same info on it so why make another?
Click to expand...
Click to collapse
Is this any different than the other threads?

t12icky0 said:
There is no specific at&t unlocked version. Plus there is already 2 threads with this same info on it so why make another?
Click to expand...
Click to collapse
Hey, post a link showing this same build on the S7 Edge forums instead of making wild claims without showing proof? You could have sent me a private message by the way, you don't have to start drama. Just saying.

dfdub said:
Is this any different than the other threads?
Click to expand...
Click to collapse
Yes, this is a different build.

Status update!
If you see another thread with this rom within this section of the forum, please show me. LOL. I wouldn't post without doing my homework, I didn't find this rom anywhere on XDA before posting. I'm doing you guys a favor and I don't have to do this, either appreciate it and try the ROM or move onto a different forum for a ROM you actually want to use. I like this rom, did hours of research finding it, and put it on my phone. I didn't have to share it guys, I chose to. As I mentioned before, a thanks is appreciated. I appreciate users concern over people double posting threads to take credit yadda yadda yadda, and the thrill of being a forum nazi, but please respect the thread owner, especially if you like people sharing rare ROMs here that they found.
Thanks for participating in the thread, and thanks for trying the rom, even though it doesn't bother me if you use it or not, I'm only sharing it and answering questions for those who actually WANT to try new roms to find the one they like. Thanks again for participating and trying the ROM, I like it, it has its perks and whatnot, and it's also not perfect, but it works. Hope you like using it, I do! #NoDrama :highfive:

t12icky0 said:
This is the same exact Rom on every thread. This is proof enough. It's the same everything from a different thread in this section. So please tell me how this is different? They pic I posted is from the nougat unlocked Rom. Look familiar??
Click to expand...
Click to collapse
It is not the same everything, you should take some time doing thorough research before bashing someone for something you think is a fraud. Thanks.

t12icky0 said:
Just because you post a title doesn't make it true.
Click to expand...
Click to collapse
HAHA, alright bro, one second... I'm about to solve this once and for all.

t12icky0 said:
Plus look at the upload date...You apparently didn't do your homework like you said. Just face it that this Rom you call the s7 edge+ is the same as every other Rom.
Click to expand...
Click to collapse
This download is 1.85 GB and others are 2.10 GB. Sorry, I had to do your homework for you since you didn't want to on your own. Now can we stop trolling the forum thread creator? Thanks!

MafiaIlluminati said:
You see that part in this title where it says S7 Edge +?
Click to expand...
Click to collapse
could you educate me on the +(plus) ?

dfdub said:
could you educate me on the +(plus) ?
Click to expand...
Click to collapse
WYM? I do not own one. Maybe I read the download wrong, because I know remembered there was an Edge + line? But either way the filesize is different so this is definitely a different build, maybe due to less bloatware, maybe different lines of coding, but it's smaller in size, which is why I wanted it when I found it, because I couldn't find this same exact file anywhere else and I wanted less preinstalled on my phone.

t12icky0 said:
Also just some more proof. The same Rom. This is from bytes thread and it was way before you because I was the one who uploaded the files for him.
Click to expand...
Click to collapse
Ok people lets stop acting like children and move on. Use the rom or dont use it. Enough with the bickering. Who gives a crap as to who posted what we are here to help each other.
---------- Post added at 02:37 PM ---------- Previous post was at 02:26 PM ----------
dfdub said:
could you educate me on the +(plus) ?
Click to expand...
Click to collapse
There is no+ with the s7. It is eaither an S7 or S7 edge. The plus came about when it was the S6 and S6+ which is basically S6 edge.

I'd appreciate it if you removed your posts now.

You have nothing to prove... Checksum all you want. The total zip filesize for each file you're obsessing over is different. No matter what you say, no matter how many ways you try to prove it, this is a different build. You cannot have two of the exact same builds and them both come out different filesizes, compression or not, you're not about to compress a file that much. Are you really going to keep being this silly and posting ridiculous harassing posts? Dude, this is why you have been added to the ignore list hours and hours ago. :good:

Ok, if it wasn't for your post I would have never seen the files for the ATT Version of the S7 Edge (G935A). I know it is usable on all the different versions, but I hardly ever check other forums.
That being said, has anyone used the ENG.IMG version of rooting this ROM? I am on the Rooted G935A and am wanting to use these files to update my phone and then root this version. Has anyone done it? I know how to root with the ENG.IMG but I just want to make sure I can do it with this one and to make sure there aren't any problems.
Thanks in advance.

From the Moderator
The next trolling post in this thread will be met with an infraction and possible Ban from XDA
If anyone has an issue report it Let the Mods manage issues or conflicts do not try to do that yourself.
CLEAR ENOUGH ???
~~~Oka1

freeop said:
Ok, if it wasn't for your post I would have never seen the files for the ATT Version of the S7 Edge (G935A). I know it is usable on all the different versions, but I hardly ever check other forums.
That being said, has anyone used the ENG.IMG version of rooting this ROM? I am on the Rooted G935A and am wanting to use these files to update my phone and then root this version. Has anyone done it? I know how to root with the ENG.IMG but I just want to make sure I can do it with this one and to make sure there aren't any problems.
Thanks in advance.
Click to expand...
Click to collapse
I got stuck in a bootloop trying to root yesterday, let me finish testing and I'll update the OP when I figure out how to do it without tripping the system up. Thanks!

I had to use PrinceComsy's Odin to flash this version. Any other version of Odin failed.

Alternate TWRP v3.1.1.0 and Root for Albus/Moto Z2 Play US Retail

What this thread is for:
Booting into TWRP Recovery for the Moto Z2 Play Retus Variant
Rooting the Z2 Play Retus Variant with Magisk
Things you will need:
IMPORTANT: You WILL need a USB C OTG cable and USB Thumbdrive (or a USB C Thumbdrive)
Magisk Zip 13.3 Mod uploaded by Junior Passos: https://www.androidfilehost.com/?fid=889764386195922735
Magisk Manager v5.1.1 apk: https://github.com/topjohnwu/MagiskManager/releases/download/v5.1.1/MagiskManager-v5.1.1.apk
DM Verity and Forced Encryption Disabler v5.1: https://androidfilebox.com/miscellaneous/dm-verity-and-forced-encryption-disabler/
My modified TWRP: https://www.androidfilehost.com/?fid=673368273298983327 md5: ebcecfaf2e00725561555dd398f883dc
Magisk ZIP and DM Verity ZIP must be put on a thumbdrive. Installing from (external) SD Card will not work with this version of TWRP.
Things you will need to keep in mind:
Make sure you fully update your device before unlocking and rooting as it likely will break OTAs. You'll likely have to rely on stock images posted by users to this forum from now on.
In order to be able to do what you need to do in TWRP, you will need to format data due to forced encryption. You won't be able to root and boot your device otherwise.
My version of TWRP is a hacky build. It works, but one feature in particular does not work: External SD card mounting. Until an updated build is made to fix this issue (of which I will require the assistance of people MUCH better at this than I am), you will need to use a USB C OTG cable and a thumbdrive to be able to back up your device and to flash ZIPs.
Try booting (not flashing) the TWRP build here first: https://forum.xda-developers.com/z2-play/development/twrp-3-1-1-0-moto-g5-plus-albus-t3622593 - If it doesn't work (hangs on logo), then try mine.
DO NOT install SuperSU from within TWRP.
These instructions assume you know how to use ADB and Fastboot Android tools. If you need the utilities, you can download the Windows versions from here: https://forum.xda-developers.com/showthread.php?t=2317790
How to boot into TWRP, make backups and root your device:
0) Your device must already be bootloader unlocked.
0a) DO NOT install SuperSU from within TWRP!!
1) Boot into Fastboot (powered off, hold down Power and Vol Down)
2) Plug your USB C cable into your computer and phone, make sure you have the Android tools installed.
3) Use fastboot command to boot into TWRP (NOT flash): fastboot boot albus_twrp.img
3a) I do not recommend flashing this version of recovery to the device because, as I said before, it's a hacky build. I don't want people to rely on it as their permanent recovery in case issues are found and fixed later.
4) Swipe to allow modification, click Cancel when it asks for passphrase to read encrypted partition.
5) Press Wipe on main screen, slide to wipe. This will wipe Data, Cache and Dalvik partitions. You will need to do this because the partitions will have to remain unencrypted after you flash DMVerity and Encryption Disabler.
5a) Yes, you have to wipe. DM Verity and forced encryption will cause your device to fail to boot if you don't disable them.
6) Back up your device. Attempting to back up System Image may fail because the partition is over 4GB and nearly every thumbdrive will be formatted in Fat32. Back up System, Boot and Recovery.
7) Install DM-Verity ZIP.
8) Install Magisk ZIP linked in this thread.
9) Reboot into system. Anticipate a longer first boot.
10) Sideload Magisk Manager.
Magisk running on Z2 Play:
{
"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"
}
What I did:
Extracted kernel, img_info and dt.img from the retus albus system image and dumped it into a harpia twrp build. I suspect the other version of TWRP was built against a different AOSP version, triggering a SELinux boot block. In my version of TWRP, fstab paths are correct but for some reason MicroSD won't mount. I'll leave that to the professionals. Everything else that I did (as described above) worked and was my exact method for doing so.
Finally:
Special thanks to Dees_Troy for TWRP. Without you, devices would suck.
Here's the Moto Z2 Play Albus boot.img for anyone who wants to take on the task of doing an official TWRP build for the device. https://www.androidfilehost.com/?fid=889764386195927416

You're the man. I'll give this a shot today and report back.

Great tutorial! One question: Does your device pass the "SafetyNet check"?

romhippo.com said:
Great tutorial! One question: Does your device pass the "SafetyNet check"?
Click to expand...
Click to collapse
In my case... it does not fully pass. Passes Safetynet Request and Response Signature... but fails on the Basic Integrity and CTS Profile Match tests. I also did modify /system (ad away, removed bootanimation.zip, moved Magisk apk and Substratum apk into /system) so that could be why.
https://i.imgur.com/u9OVkUq.png

Followed the directions to the letter and everything is working for me. Thanks a lot, twelfth!

Twelfth, sorry for going offtopic a bit, but was anyone successfully able to install a Substratum theme on the device? I'm running into issues when attempting to theme Android System / System UI. Everything else seems to work flawlessly.

Just a heads up guys. Flashed Magisk 14.0. Passed safetynet. Can't download/install modules though, gives Parse Error or something. Haven't tried installing modules through TWRP to see if it works.

atheart said:
Can't download/install modules though, gives Parse Error or something.
Click to expand...
Click to collapse
I have had the same issue with Magisk 13.3 ...

This may sound like a bad question but I know that VZW has a locked bootloader is there and successful chance that this will work on the VZW variant?
Please try not to flame me for this....

cantsingh said:
Twelfth, sorry for going offtopic a bit, but was anyone successfully able to install a Substratum theme on the device? I'm running into issues when attempting to theme Android System / System UI. Everything else seems to work flawlessly.
Click to expand...
Click to collapse
Substratum is strange. I've had issues getting white text on dark backgrounds to work until I just re-applied specific elements like Android System after I applied System UI and rebooted. Sometimes I couldn't even get notifications to look normal until I applied elements from a second theme (Swift Dark > Reboot > Default Dark > Reboot, it works)... just gotta keep fussing with it until it sticks.
cmjester6421 said:
This may sound like a bad question but I know that VZW has a locked bootloader is there and successful chance that this will work on the VZW variant?
Please try not to flame me for this....
Click to expand...
Click to collapse
Nope. Locked bootloader means locked bootloader. You must be unlocked first before you can flash or boot unsigned/unofficial images.
That said, if you ordered the Z2 Play Unlocked from Motorola, chances are you'd be able to use it on Verizon by swapping out the sim card since the unlocked Z2 Play is compatible with all carriers. This means swapping out an already activated sim card yourself, NOT activating the device on Verizon.

twelfth said:
Substratum is strange. I've had issues getting white text on dark backgrounds to work until I just re-applied specific elements like Android System after I applied System UI and rebooted. Sometimes I couldn't even get notifications to look normal until I applied elements from a second theme (Swift Dark > Reboot > Default Dark > Reboot, it works)... just gotta keep fussing with it until it sticks.
Nope. Locked bootloader means locked bootloader. You must be unlocked first before you can flash or boot unsigned/unofficial images.
That said, if you ordered the Z2 Play Unlocked from Motorola, chances are you'd be able to use it on Verizon by swapping out the sim card since the unlocked Z2 Play is compatible with all carriers. This means swapping out an already activated sim card yourself, NOT activating the device on Verizon.
Click to expand...
Click to collapse
Thanks for the response! Yeah, I encountered the same behavior. Seems like I almost got a working combination using just Swift Black, but random UI elements would be black on black rendering them unreadable. No worries, a small price to pay!
As for your second point - I can confirm that the US Unlocked Z2 does work on Verizon with an unlocked bootloader. :good:

Cameras not working post root
So I basically did the same thing but didn't use this site. Unlocked bootloader, flashed TWRP via adb and fastboot, flashed magisk. I'm rooted and have the XT1710-01 rooted on stock firmware. I did only what I said I did, nothing like sideload and putting anything on or flashing any other zips, only magisk. I need a camera fix ASAP and I can't find one.

Can you make this alittle more simple like in steps, I recently got this phone and I want to root it

cantsingh said:
Thanks for the response! Yeah, I encountered the same behavior. Seems like I almost got a working combination using just Swift Black, but random UI elements would be black on black rendering them unreadable. No worries, a small price to pay!
As for your second point - I can confirm that the US Unlocked Z2 does work on Verizon with an unlocked bootloader. :good:
Click to expand...
Click to collapse
How did you verify this? I recently bought the US Retail (non verizon) version and it isn't letting me unlock the bootloader. So what phone did you buy then that allowed you to unlock the bootloader?
Nevermind I'm an idiot. I forgot to check the button in the developers option to "unlock oem bootloader"
Forgive me all!

ihatevz said:
How did you verify this? I recently bought the US Retail (non verizon) version and it isn't letting me unlock the bootloader. So what phone did you buy then that allowed you to unlock the bootloader?
Nevermind I'm an idiot. I forgot to check the button in the developers option to "unlock oem bootloader"
Forgive me all!
Click to expand...
Click to collapse
Haha, we've all been there! :good:

Alabamajackhammer said:
So I basically did the same thing but didn't use this site. Unlocked bootloader, flashed TWRP via adb and fastboot, flashed magisk. I'm rooted and have the XT1710-01 rooted on stock firmware. I did only what I said I did, nothing like sideload and putting anything on or flashing any other zips, only magisk. I need a camera fix ASAP and I can't find one.
Click to expand...
Click to collapse
What's wrong with the camera, after root?

Are there no images to restore out yet?

Wait so if we have a phone that came from verizon we can't root it because of the locked bootloader right?

Pooper22 said:
Wait so if we have a phone that came from verizon we can't root it because of the locked bootloader right?
Click to expand...
Click to collapse
Yes. I'm surprised that this surprises you.

Is there a specific reason why op says not to flash SuperSU? Will it not work or damage something?

Question Vivo X Fold: OEM unlock seems to be there, root anyone?

I don't have the Vivo X Fold — am interested in getting it.
From what I've been reading there seems to be OEM unlock present in the settings…
Anyone rooted somehow? I haven't used a Vivo device yet — just Samsung, so with the restrictive Chinese approach assume there'd be no full firmware downloads, whereby Magisk patching tse boot would be easy. Or am I wrong?

I unlocked bootloader and rooted, I usee DSU Loader and dd command to extract boot.img from the device. (search it)
Note that the device must be before 2022-04-30 compile time to unlock bootloader, latest firmware blocks unlocking.

AndroPlus said:
I unlocked bootloader and rooted, I usee DSU Loader and dd command to extract boot.img from the device. (search it)
Note that the device must be before 2022-04-30 compile time to unlock bootloader, latest firmware blocks unlocking.
Click to expand...
Click to collapse
Many thanks! :0)
Is there a way to buy such a device online? Do you know any seller who will check and guarantee this?

白い熊 said:
Many thanks! :0)
Is there a way to buy such a device online? Do you know any seller who will check and guarantee this?
Click to expand...
Click to collapse
I don't know, you should ask seller to see if they can do it...

AndroPlus said:
I unlocked bootloader and rooted, I usee DSU Loader and dd command to extract boot.img from the device. (search it)
Click to expand...
Click to collapse
I'm searching fro DSU loader info — never used it before — and reading up on it. Thanks for the pointer.
Just for more details if I may:
— dd boot partition — understood; Looking now for how to via DSU loader.
— Then you patch via Magisk Manager I assume, right?
— How do you then flash back to phone? DSU loader again? Or is that where it's “magic ” comes in, it creates a virtual partitIon somewhere, placed modified boot there and you boot off of it?
— If the above is the case, do you boot modified via some boot combo?
— If it isn't the case, could you briefly describe?
Many thanks. :O)

> Note that the device must be before 2022-04-30 compile time to unlock bootloader, latest firmware blocks unlocking.
Does that mean after you unlock, you won't be able to install any Android updates or security patches (and remain unlocked)?

robsmith11 said:
> Note that the device must be before 2022-04-30 compile time to unlock bootloader, latest firmware blocks unlocking.
Does that mean after you unlock, you won't be able to install any Android updates or security patches (and remain unlocked)?
Click to expand...
Click to collapse
That's usually the case…

白い熊 said:
That's usually the case…
Click to expand...
Click to collapse
Even on phones that can be officially unlocked like Google Pixels?
That sucks. I only have experience using root with 3rd party roms, so didn't realize that.

白い熊 said:
I'm searching fro DSU loader info — never used it before — and reading up on it. Thanks for the pointer.
Just for more details if I may:
— dd boot partition — understood; Looking now for how to via DSU loader.
— Then you patch via Magisk Manager I assume, right?
— How do you then flash back to phone? DSU loader again? Or is that where it's “magic ” comes in, it creates a virtual partitIon somewhere, placed modified boot there and you boot off of it?
— If the above is the case, do you boot modified via some boot combo?
— If it isn't the case, could you briefly describe?
Many thanks. :O)
Click to expand...
Click to collapse
Maybe it's easier to use DSU Sideloader app.
GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feature.
A simple app made to help users easily install GSIs via DSU's Android feature. - GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feat...
github.com
The step to root is:
1. Download AOSP GSI (system-squeak-arm64-ab-vanilla.img.xz) from Phhusson
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
2. Once you prepared DSU, reboot from notification to boot into DSU's image
3. Connect USB cable
4. Run these commands in command prompt or powershell:
adb shell
su
dd if=/dev/block/by-name/boot of=/data/local/tmp/boot.img
chown shell.shell /data/local/tmp/boot.img
5. Exit adb shell and run this command to pull boot.img:
adb pull /data/local/tmp/boot.img
6. Patch boot.img with Magisk app
Installation
The Magic Mask for Android
topjohnwu.github.io
7. Reboot into bootloader and run:
fastboot flash boot magisk_patched_[random].img
robsmith11 said:
> Note that the device must be before 2022-04-30 compile time to unlock bootloader, latest firmware blocks unlocking.
Does that mean after you unlock, you won't be able to install any Android updates or security patches (and remain unlocked)?
Click to expand...
Click to collapse
No, you can get OTA update even after unlocking and remain unlocked.
First attempt will fail but then updater app downloads full zip automatically.

AndroPlus said:
Maybe it's easier to use DSU Sideloader app.
GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feature.
A simple app made to help users easily install GSIs via DSU's Android feature. - GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feat...
github.com
The step to root is:
Click to expand...
Click to collapse
Many thanks for the details.
I'm trying to find a pre-end-of-April device seller online now… :O)
BTW — is there a clean reflash or something option to rescue Vivo devices — if you brick it after root? Just factory reset from Recovery would do I guess.
Reason being — sometimes you're too eager to do somethIng and end up in a bootloop — happens to me from time to time - and I guess here the risk would be significant having to freeze all the China bloatware…
I would think there is Recovvery reset — but best to ask, I've never seen a Vivo device…

白い熊 said:
Many thanks for the details.
I'm trying to find a pre-end-of-April device seller online now… :O)
BTW — is there a clean reflash or something option to rescue Vivo devices — if you brick it after root? Just factory reset from Recovery would do I guess.
Reason being — sometimes you're too eager to do somethIng and end up in a bootloop — happens to me from time to time - and I guess here the risk would be significant having to freeze all the China bloatware…
I would think there is Recovvery reset — but best to ask, I've never seen a Vivo device…
Click to expand...
Click to collapse
Yes, factory reset from recovery or flash correct partition from fastboot (in case you flashed wrong/corrupted image).
There's EDL mode too, but I don't know if it can be used.
PD2145F_EX_A_3.11.8_vivo_qcom_LA.UM.9.14.r1-12600-LAHAINA-sm7325-sm8350_split_GsmMafia.Com.rar
drive.google.com

AndroPlus said:
Yes, factory reset from recovery or flash correct partition from fastboot (in case you flashed wrong/corrupted image).
There's EDL mode too, but I don't know if it can be used.
PD2145F_EX_A_3.11.8_vivo_qcom_LA.UM.9.14.r1-12600-LAHAINA-sm7325-sm8350_split_GsmMafia.Com.rar
drive.google.com
Click to expand...
Click to collapse
edl can't be used, needs authorization from vivo

AndroPlus said:
Note that the device must be before 2022-04-30 compile time to unlock bootloader, latest firmware blocks unlocking.
Click to expand...
Click to collapse
I'm communicating with some Chinese sellers on ebay - it's all shady in a regular way :O) - is the compile time printed somewhere on tthe box outside?
Or is there manufacture time there? And go by that? Could you tell me exactly where on the box - or, if possible, share a pic?
They're all saying - we can't break the seal and check, since then it's a used phone - logical. But also: don't worry it'll be OK - which usually means it won't… :O)

白い熊 said:
I'm communicating with some Chinese sellers on ebay - it's all shady in a regular way :O) - is the compile time printed somewhere on tthe box outside?
Or is there manufacture time there? And go by that? Could you tell me exactly where on the box - or, if possible, share a pic?
They're all saying - we can't break the seal and check, since then it's a used phone - logical. But also: don't worry it'll be OK - which usually means it won't… :O)
Click to expand...
Click to collapse
There's "生产日期" (Manufactured date) on the back of the box, and if it's 2022-04 it should have firmware with compile time before 2022-04-30.

白い熊 said:
Or is there manufacture time there? And go by that? Could you tell me exactly where on the box - or, if possible, share a pic?
Click to expand...
Click to collapse
My phone's manufactured date is 2022-06-27, and compile time is 2022-04-21.
I didn't install any updates yet.
{
"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"
}

KestL said:
My phone's manufactured date is 2022-06-27, and compile time is 2022-04-21.
I didn't install any updates yet.
View attachment 5676893 View attachment 5676895
Click to expand...
Click to collapse
Yeah - the problem is, there's no way to check compile time unless you go into Settings and for this you have to unseal the box — so they don't want to do this with an unused phone…

Hi guys, i read all you wrote and Im very interested in unlocking Vivo X note, but i have updated it (a few days ago), one thing i dont understand is what would possibly happen if i unllock the bootloader. Im very interested in doing it to flash any gsi and at least get wearOs working. Sorry, i know its not the phone, but i dont know where to ask

The X Note and the X Fold share the same underlying Origina OS Ocean operating system. Each has slightly different versions of the firmware, with the latter being 'tweaked' for use with the tablet style screen. With both phones the exploit that existed that allowed unlocking of the bootloader was patched by June's security update. If you have updated your X Note recently then you can't unlock your bootloader. There are currently no "downgrade" firmware packages available via the Vivo downgrade application. If Vivo makes these available then you could downgrade to May's firmware and use the exploit described in the X70 Pro forum to unlock and then you could flash with Magisk and do whatever you need to do. You can't at present.

frcraig said:
The X Note and the X Fold share the same underlying Origina OS Ocean operating system. Each has slightly different versions of the firmware, with the latter being 'tweaked' for use with the tablet style screen. With both phones the exploit that existed that allowed unlocking of the bootloader was patched by June's security update. If you have updated your X Note recently then you can't unlock your bootloader. There are currently no "downgrade" firmware packages available via the Vivo downgrade application. If Vivo makes these available then you could downgrade to May's firmware and use the exploit described in the X70 Pro forum to unlock and then you could flash with Magisk and do whatever you need to do. You can't at present.
Click to expand...
Click to collapse
Thanks man a lot.
So the only thing i can do is wait.

AndroPlus said:
Maybe it's easier to use DSU Sideloader app.
GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feature.
A simple app made to help users easily install GSIs via DSU's Android feature. - GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feat...
github.com
The step to root is:
1. Download AOSP GSI (system-squeak-arm64-ab-vanilla.img.xz) from Phhusson
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
2. Once you prepared DSU, reboot from notification to boot into DSU's image
3. Connect USB cable
4. Run these commands in command prompt or powershell:
adb shell
su
dd if=/dev/block/by-name/boot of=/data/local/tmp/boot.img
chown shell.shell /data/local/tmp/boot.img
5. Exit adb shell and run this command to pull boot.img:
adb pull /data/local/tmp/boot.img
6. Patch boot.img with Magisk app
Installation
The Magic Mask for Android
topjohnwu.github.io
7. Reboot into bootloader and run:
fastboot flash boot magisk_patched_[random].img
No, you can get OTA update even after unlocking and remain unlocked.
First attempt will fail but then updater app downloads full zip automatically.
Click to expand...
Click to collapse
Do you need unlock bootloader at first?