..the vbmeta.img and boot_a from the unlocked variant? I tried flashing TWRP kind of half cocked, and yea... Anyhow, if someone has either\or or both of these files, hook a brother up!
Disregard. I was able to unbrick with the dre8t_10_O.05_210713.ops firmware floating around. It wouldnt let me flash via MSMDownloadTool, however I was able to decrypt/extract the ops file with the oppo_decrypt python script, then reflash the vbmeta and vbmeta_system partitions plus boot_a and userdata with the extracted files.
PHEW had me scared for a minute
the.real.p3y0t3 said:
..the vbmeta.img and boot_a from the unlocked variant? I tried flashing TWRP kind of half cocked, and yea... Anyhow, if someone has either\or or both of these files, hook a brother up!
Click to expand...
Click to collapse
For future reference:
For unlocked variant:
Download the latest OTA update from the OnePlus website and you can use any assortment of payload dumpers to obtain all of the raw image files.
My payload dumper of preference is Fastboot Enhanced/Payload Dumper. It can even install the full OTA via fastboot/fastbootd
For T-Mobile and Metro variants I would recommend the T-Mobile MSM tool and update from there.
The download link to "Incremental OTAs" can be scraped from the system logcat at time of download.
I haven't looked much into incremental OTA and how it is setup yet.
Thanks for the heads up. I actually already had the above mentioned OPS file when I bricked my device, I just hadn't been able to extract, then decrypt it. Had to download a obscure bzip2 binary for windows to extract the tar, etc etc.
A seller from ebay sent a t-mobile (2118) that was carrier unlocked, wasn't able to unlock the bootloader. Is there anything I can do?
Related
Hi everyone,
I have an 10.8 inch wifi only tablet imported from China, non-pro, model CMR-W09C00 which was running firmware B123.
I was playing around trying to convert it to a global firmware and tried to flash it with the same firmware 123 but for CMR-W09C432 using Huawei Firmware Finder.
Turns out this was a pretty bad idea
Now the tablet is not booting and I can't figure out how to recover. Here's what I tried:
1. eRecovery is not working, it downloads the firmware completely and tries to install but fails. It did work fully once before I tried to flash the wrong firmware.
2. Wiping cache and data partition does nothing
3. I have access to fastboot and can unlock/lock the bootloader at will.
4. I have the full-OTA zip file for the original firmware CMR-W09C00B123 and have extracted all the img files contained in update.app
5. I'm trying / hoping to flash images to recover (with bootloader unlocked) but I'm a bit confused at this step.
All the instructions I found in my research mention mostly flashing just boot.img, system.img and recovery.img but I'm missing some of those files from the update.app or I guess they could be named differently. I don't have a boot.img, just a fastboot.img which I'm sure is not the same. I also don't have a recovery.img, just recovery_ramdis, recovery_vbmeta, recovery_vendor, erecovery_ramdis, erecovery_vendo, erecovery_vbmet and erecovery_kerne.
I was able to flash system.img successfully but that didn't help.
Also tried to use the unbrick feature from Huawei Multi-Tool but here again I seem to be missing image files. Multi-Tool says it needs system.img, ramdisk.img, cust.img, ramdisk_recovery.img and userdata.img.
Of those, I think I'm missing cust.img for sure, ramdisk_recovery I might have but it's named differently (recovery_ramdis) and userdata.img I don't think I really need.
I'm attaching a txt file with a list of all the img files I do have in case it can be useful or rings a bell for someone.
Oh yeah, I also tried flashboot update update.zip but it's only giving me this warning:
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
So...does anyone have any advice or suggestions? Is there a better method to recover that I missed?
Any help is appreciated!
Flash the ramdisk.img to ramdisk and report back please. I have an M3 that is in the same condition as yours, but I am on an extended deployment and won't be able to test this for at least another month :/
fargonaz said:
Flash the ramdisk.img to ramdisk and report back please. I have an M3 that is in the same condition as yours, but I am on an extended deployment and won't be able to test this for at least another month :/
Click to expand...
Click to collapse
Thanks for taking the time to the reply mate, sorry to hear about your M3.
I tried fastboot flash ramdisk ramdisk.img and it said flashed successfully but the device is still not booting. Nothing else seems to have changed either.
Let me know if I misunderstood what you wanted to try or if you have any other ideas.
Cheers
etheberge said:
Hi everyone,
I have an 10.8 inch wifi only tablet imported from China, non-pro, model CMR-W09C00 which was running firmware B123.
I was playing around trying to convert it to a global firmware and tried to flash it with the same firmware 123 but for CMR-W09C432 using Huawei Firmware Finder.
Turns out this was a pretty bad idea
Now the tablet is not booting and I can't figure out how to recover. Here's what I tried:
1. eRecovery is not working, it downloads the firmware completely and tries to install but fails. It did work fully once before I tried to flash the wrong firmware.
2. Wiping cache and data partition does nothing
3. I have access to fastboot and can unlock/lock the bootloader at will.
4. I have the full-OTA zip file for the original firmware CMR-W09C00B123 and have extracted all the img files contained in update.app
5. I'm trying / hoping to flash images to recover (with bootloader unlocked) but I'm a bit confused at this step.
All the instructions I found in my research mention mostly flashing just boot.img, system.img and recovery.img but I'm missing some of those files from the update.app or I guess they could be named differently. I don't have a boot.img, just a fastboot.img which I'm sure is not the same. I also don't have a recovery.img, just recovery_ramdis, recovery_vbmeta, recovery_vendor, erecovery_ramdis, erecovery_vendo, erecovery_vbmet and erecovery_kerne.
I was able to flash system.img successfully but that didn't help.
Also tried to use the unbrick feature from Huawei Multi-Tool but here again I seem to be missing image files. Multi-Tool says it needs system.img, ramdisk.img, cust.img, ramdisk_recovery.img and userdata.img.
Of those, I think I'm missing cust.img for sure, ramdisk_recovery I might have but it's named differently (recovery_ramdis) and userdata.img I don't think I really need.
I'm attaching a txt file with a list of all the img files I do have in case it can be useful or rings a bell for someone.
Oh yeah, I also tried flashboot update update.zip but it's only giving me this warning:
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
So...does anyone have any advice or suggestions? Is there a better method to recover that I missed?
Any help is appreciated!
Click to expand...
Click to collapse
I think I am in a similar spot. I went from a custom ROM back to stock, but now all attempts at installing full OTAs fail. Did you ever figure this out how to fix it?
Thanks
Before rooting, you'll need an unlocked bootloader. Check my previous guide here: https://forum.xda-developers.com/x3...ck-bootloader-realme-x3-t4136325/post83109505.
After unlocking, we can get started with rooting.
First, you'll want to install Magisk Manager. You can find the latest APK here: https://github.com/topjohnwu/magisk/releases.
Next, you'll need to download the latest OTA OZIP. There's a link at the end of the post for this.
While that's downloading, you'll also need to grab a copy of an OZIP extractor. Follow the link below, download the repository as a ZIP, and unzip it.
For this program to work, you'll need Python 3 installed. On Linux systems, it should already be installed. On Windows 10, you can install Python from the Store.
Open a terminal or CMD window and cd to where you extracted the OZIP extractor files.
Use pip to install the docopt module: "pip3 install docopt".
Once the OZIP has finished downloading, move it to the same folder as the extractor program.
Run the following command: "python3 ozipdecrypt.py NAME_OF_OZIP_FILE". This will take a while!
Once it's done extracting, there will be a ZIP file with the same name as the OZIP. We only need two files from here: boot.img and vbmeta.img.
Extract those two files to the same folder as the extractor program.
Copy the boot.img file to your device.
Open Magisk Manager and choose the "INSTALL" option next to the Magisk status. Tap "INSTALL" in the dialog that appears and then choose "Select and Patch a File."
Browse to where you copied your boot.img to and select it. Magisk will now patch it and create a file named magisk_patched.img in your Download folder. Copy magisk_patched.img back to your computer.
Reboot your phone into fastboot: "adb reboot bootloader". If you don't have ADB or fastboot installed (which you should, since you needed them for the previous guide), you can find the link in the bootloader unlocking guide.
Before you flash the patched boot image, you need to disable image verification, which is where the vbmeta.img comes in.
Run "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" (remember, you'll probably need to unplug and replug the device after hitting Enter). This will disable boot verification and allow the patched image to actually work.
Finally, run "fastboot flash boot magisk_patched.img". This will flash the rooted boot image to your device.
Run "fastboot reboot" and let the phone boot back into the system. Check Magisk Manager and you should now be rooted!
Troubleshooting:
If you get an error that the boot image was "destroyed," don't worry. You'll just need to flash the stock boot.img and try again. Unplug your phone from your computer and wait for it to turn off. Once the screen is black, hold down VOL-DWN and PWR to enter fastboot mode. You can then run "fastboot flash boot boot.img" (where boot.img is the stock image) to restore. Reboot, then try the vbmeta and patched image flashing again.
You can get the OTA OZIPs from Realme EU's site: https://www.realme.com/eu/support/software-update.
You can get an OZIP extractor from here: https://github.com/bkerler/oppo_ozip_decrypt. (NOTE: you'll need to install the "docopt" Python module.)
OZIPs contain a boot.img, which you can extract and patch with Magisk for root. If someone else has an idea for patching Magisk into the boot.img, this is where to start.
Here's my patched boot.img for A.32. I don't recommend using this on other versions: https://www.androidfilehost.com/?w=files&flid=315334
Could you share your patched boot.img for the latest OS version? And could you check if the aux magisk module from X2 pro works to activate all aux cameras in Gcam? Thanks
Patched boot image
Thanks Zacharee1....Could someone upload the patched boot image for the latest one? Also do we have a generic version of twrp that can be installed on x3 ?? If yes, then we could try installing havoc gsi...
I've added a link to a patched A.32 boot.img.
also needed pip install pycryptodome win10
Zacharee1 said:
I've added a link to a patched A.32 boot.img.
Click to expand...
Click to collapse
Thanks a ton Zacharee!!
But it seems like I have A.33 version (https://www.realme.com/in/support/software-update)
I wish we had a video guide or something. Does anyone have a patched A.33 boot.img?
cheth20 said:
Thanks a ton Zacharee!!
But it seems like I have A.33 version (https://www.realme.com/in/support/software-update)
I wish we had a video guide or something. Does anyone have a patched A.33 boot.img?
Click to expand...
Click to collapse
It's pretty simple to patch it yourself. Download the OZIP, use the Python tool to unencrypt it, take the boot.img file out of the created ZIP, copy it to your device, and then patch with with Magisk Manager.
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Firmware for RMX2085
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
sukhad86 said:
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Click to expand...
Click to collapse
cheth20 said:
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
Click to expand...
Click to collapse
The firmware is the same for them all.
Great thread @Zacharee1. I have been waiting for this!
I have one question - is it mandatory to download the OTA package and do the patching? Is it because of the absence of recovery software like TWRP yet, for the X3 Super Zoom?
phonedroid said:
Great thread @Zacharee1. I have been waiting for this!
I have one question - is it mandatory to download the OTA package and do the patching? Is it because of the absence of recovery software like TWRP yet, for the X3 Super Zoom?
Click to expand...
Click to collapse
Yes, and that's why. It might be possible to pull the boot image directly from your device, but I'm not sure.
Can someone tell me if I can use realme 6 pro vbmeta.img?
realme x3 super zoom twrp recovery bro give me
Hi Sukhad,
I updated the system to the latest OTA (39), but I do not have the latest magisk patched file. Could you kindly help me with latest version patched boot for x3 superzoom?
sukhad86 said:
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Click to expand...
Click to collapse
Thanks Zacharee1!
Finally did it (15/20 year old windows machines... Win7 was dificult and finally use a win8). Worth big as root gives me a new smartphone
Had all sorts of problems (installing python... But once installed was pretty quick) mainly adb conneting...
Anyway I will share vbmeta.img attached for a38 rom.
Also link to boot img, again a38.
For A38 rom
http://www.mediafire.com/file/i9jvl1al95k40vv/magisk_patched_a38.img/file
bro please could u tell me.. help
cheth20 said:
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
Click to expand...
Click to collapse
bro please could u tell me.. after unlocking the bootloader of realme X3 superzoom , does it breaks the fingerprint sensor?
ota update after root
Someone have experiencing ota update failed on rooted device with this procedure? I m on RMX2081EU_11.A.40 but ota update to RMX2081EU_11.A.42 fails. how to update now?
Good afternoon. I want to get a root for my X3 super zoom, but I literally do not understand all the manipulations so that your description is attached with an image (screenshots). I think it will be useful for everyone who can't.
Anyone have working patched boot.img for a46?? I'm trying and always boot destroyed. Magisk 21.4
It's really weird on official en site there is a42 soft from September but on pl site there is a46 from December.
All fix avilable (no network solved)
Watch it carefully do it step by step as showen in my video you will never brick if you follow my video
All required files are in the video description
This guide Tested on the firmware (20e ,20c,20d) (if you didn't see your firmware don't worry leave a command , I will help you ! )
How to check the frimware:
* Go to Settings - >System -> About phone -> sofware version ( eg: V20e-IND-XX so use 20e rootboot file)
All required files are in the video description
watch it in 720p only 40 mb
subscribe for more lg g8x content !!!
If any issue let me know i will help you with that
I've rooted with Magisk and root seems to be working. I then restored the abl_a back to abl_a and abl_b partition. Now I keep getting system UI crashes and the phone app freezes when I try to make a call.
cyr4n0 said:
I've rooted with Magisk and root seems to be working. I then restored the abl_a back to abl_a and abl_b partition. Now I keep getting system UI crashes and the phone app freezes when I try to make a call.
Click to expand...
Click to collapse
looks like your device is not a 20e firmware (audio not work,cant make a call ,ui crash) i will help you to root just share the boot_a img (stock)
[email protected] said:
looks like your device is not a 20e firmware (audio not work,cant make a call ,ui crash) i will help you to root just share the boot_a img (stock)
Click to expand...
Click to collapse
Hello,
I have the exact same issues. Didn't notice the Indian variant on Magisk in the Root guide, and ended up with an unusable phone.
You say boot_a image stock, do you mean from before the whole process? I unfortunately didn't back up this particular partition..
Boot.zip contains the boot.img file pulled from the kdz of the US G850 20b.I don't know if this is useful, but I got it...
ReadData_.ufs_Lun4_...... is the boot_a file pulled from my phone after I turned it into a buggy mess I also don't know if this helps, but I do need help getting my phone working again if you'd be so kind. This is NOT the boot_b flashed as boot_a like mentioned in the video.
rainbowtuba said:
Hello,
I have the exact same issues. Didn't notice the Indian variant on Magisk in the Root guide, and ended up with an unusable phone.
You say boot_a image stock, do you mean from before the whole process? I unfortunately didn't back up this particular partition..
Boot.zip contains the boot.img file pulled from the kdz of the US G850 20b.I don't know if this is useful, but I got it...
ReadData_.ufs_Lun4_...... is the boot_a file pulled from my phone after I turned it into a buggy mess I also don't know if this helps, but I do need help getting my phone working again if you'd be so kind. This is NOT the boot_b flashed as boot_a like mentioned in the video.
Click to expand...
Click to collapse
The one you provided was not help ,Give me the stock boot_a img (download the whole kdz and extract the boot_a.img)
rainbowtuba said:
Hello,
I have the exact same issues. Didn't notice the Indian variant on Magisk in the Root guide, and ended up with an unusable phone.
You say boot_a image stock, do you mean from before the whole process? I unfortunately didn't back up this particular partition..
Boot.zip contains the boot.img file pulled from the kdz of the US G850 20b.I don't know if this is useful, but I got it...
ReadData_.ufs_Lun4_...... is the boot_a file pulled from my phone after I turned it into a buggy mess I also don't know if this helps, but I do need help getting my phone working again if you'd be so kind. This is NOT the boot_b flashed as boot_a like mentioned in the video.
Click to expand...
Click to collapse
Or you can flash the kdz back (make sure you are using the correct KDz
How do I flash the KDZ? I have tried pushing it with LGUP but it hasn't been successful.
Also, I've extracted the kdz with LG Firmware Extract but I'm not seeing a boot_a.img. The closest thing I see is boot.img_257490
I think I'm stuck now. I tried to use LGUP but now I can't even boot into anything but fastboot. Now it fails the security check and goes into fastboot. Unlocking the bootloader doesn;t work now and it's stuck on locked...
BTW, I renamed the boot.img_257490 and tried to flash it via fastboot but the error was "sending boot_a - too large" so I think this IS the boot_a. Not that it may matter for me at this point lol
rainbowtuba said:
How do I flash the KDZ? I have tried pushing it with LGUP but it hasn't been successful.
Also, I've extracted the kdz with LG Firmware Extract but I'm not seeing a boot_a.img. The closest thing I see is boot.img_257490
I think I'm stuck now. I tried to use LGUP but now I can't even boot into anything but fastboot. Now it fails the security check and goes into fastboot. Unlocking the bootloader doesn;t work now and it's stuck on locked...
BTW, I renamed the boot.img_257490 and tried to flash it via fastboot but the error was "sending boot_a - too large" so I think this IS the boot_a. Not that it may matter for me at this point lol
Click to expand...
Click to collapse
wait ill share you my lg up and kdz extractor.
and are you sure you downloaded the correct one?
[email protected] said:
wait ill share you my lg up and kdz extractor.
and are you sure you downloaded the correct one?
Click to expand...
Click to collapse
Now that I'm trying it again, it's failing to pull it. The DZ seems to pull from the KDZ, but anything from the DZ fails with an incorrect header check error. It's a blank file. I'm sure you noticed that before I did.
rainbowtuba said:
Now that I'm trying it again, it's failing to pull it. The DZ seems to pull from the KDZ, but anything from the DZ fails with an incorrect header check error. It's a blank file. I'm sure you noticed that before I did.
Click to expand...
Click to collapse
KDZ Extractor LG
Download the Zip : http://www.mediafire.com/file/0a6iikrao70ma5s/KDZTools_20200305.7z/file Extract the file zip Copy the Downloaded KDZ into the KDZ Extractor folder Open "OneKeyExtraction.bat" It will Start to extract the file for you The...
forum.xda-developers.com
use this
[email protected] said:
KDZ Extractor LG
Download the Zip : http://www.mediafire.com/file/0a6iikrao70ma5s/KDZTools_20200305.7z/file Extract the file zip Copy the Downloaded KDZ into the KDZ Extractor folder Open "OneKeyExtraction.bat" It will Start to extract the file for you The...
forum.xda-developers.com
use this
Click to expand...
Click to collapse
Thank you, here is the boot_a.img
EDIT: I have potentially good news! I was completely stuck in a boot loop, but using the files from the KDZ (modem_a, modem_b, boot_a,boot_b, abl_a, and abl_b) and pushed them each with fastboot. The device restarted (with sound!) and it is resetting to stock now. We'll see what happens!
rainbowtuba said:
Thank you, here is the boot_a.img
Click to expand...
Click to collapse
How to restore download mode ?
can we root on 20f?
What about 20b
I own a LG G8x Sprint fw model with SW version g850um20f build qkq1.200216.002 with April Security patch. I unlocked the bootloader with this method after I sim unlocked it today. Interestingly I have now a T-mobile splash screen perhaps because I tested the sim unlock with my t-mobile sim? Either way it provisioned all the T-mobile operator software so it got rid of all the Sprint garbage and loaded volte wifi calling etc...I have yet to test all the features but it did it all for me after the factory reset happens when the boot loader unlocks. I did not load the original abl_a abl_b backup files back to the device. Was the patched abl file a US model dump?
Me gustaría saber si la versión 20j de sprint también se puede rootear
Anyone successful unlock the 20b (G8X Us variant)? Having a hard time finding any info on unlocking this version.
20b
Adminislayer said:
Anyone successful unlock the 20b (G8X Us variant)? Having a hard time finding any info on unlocking this version.
Click to expand...
Click to collapse
I did 20j sprint yesterday.
The hardest part was to get into EDL.
Where are you stuck?
BTW, does anyone have the twrp bin for these phones? I can't find a working link. I just want to boot into twrp temporary to do a system image.
Does anyone know where to get the stock boot.img? I have artic & travis' custom kernel flashed and, long story short, I need to flash back to stock for now. I have a MetroPCS model btw.
use payload dumper and extract boot.img from latest firmware downloaded from oneplus website
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
Ytube21 said:
use payload dumper and extract boot.img from latest firmware downloaded from oneplus website
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
Click to expand...
Click to collapse
That's OEM and will prevent me from updating OTA
You can factory reset and then use the GSI method to get a copy of stock boot.img, I don't know if anyone has done this before for MetroPCS
I have most of the previous Tmobile boot.img available at this archive, I don't know if it works for MetroPCS: https://androidfilehost.com/?w=files&flid=329532
T-Mobile and MetroPCS are using a unified image and will customize for the proper providers tools and boot logo based in sim inserted during initial setup.
The boot.img is the same for both.
Hi everyone, I prefer remain with the Chinese rom for a while but I'd like to root my moto x40 with magisk.
I've tried but after flashing the patched boot.img the phone boot normally. the firmware has vbmeta so I followed the procedure suggested by the guide in this situations.
the weird thing is the patched root remain exactly with the same original dimensions.
I think this is an a type partition firmware due to boot.img presence but there is also a file called vendor_boot.img. according with this article seems an a/b type.
Vendor Boot Partitions | Android Open Source Project
source.android.com
I attach a screen of the firmware content, the log of patched boot file and the adb process.
Please, can anyone explain me how can I root successfully? thanks
Did you unlock the bootloader? Once done you need to flash a patched init_boot.img instead of boot.img through fastboot.
This guide should be useful (it's for the Pixel 7s, but should work with this phone, and of course use the init_boot.img from the original ROM file for your phone)
Hope that helps
hi, thank you for the answer.
yes the bootloader was unlocked.
This rom is the same as my phone's. I had take by lolinet.
unfortunately magisk is unable to patch vendor_boot , I'm trying to attach it.
Is Someone able to patch?
vendor_boot.img
Shared with Dropbox
www.dropbox.com
This is my vendor-boot
Do you lose VPN access after bootloader unlocked?
No, I didn't lose
mikaelcbr2 said:
hi, thank you for the answer.
yes the bootloader was unlocked.
This rom is the same as my phone's. I had take by lolinet.
unfortunately magisk is unable to patch vendor_boot , I'm trying to attach it.
Is Someone able to patch?
Click to expand...
Click to collapse
You need to patch init_boot.img using Magisk, and flash both init_boot_a and init_boot_b with the patched file through fastboot
sooyong94 said:
You need to patch init_boot.img using Magisk, and flash both init_boot_a and init_boot_b with the patched file through fastboot
Click to expand...
Click to collapse
Yes I followed the guide, thanks