I can't install ROMs for Espressowifi (p31xx, p51xx), but I can install ROM for p5110 - Galaxy Tab 2 Q&A, Help & Troubleshooting

For example, I can't install this ROM. https://androidfilehost.com/?fid=529141701856461698
When I install this ROM, the system doesn't boot
But I can install this ROM. https://androidfilehost.com/?fid=95916177934523996
So what's the problem?

dogukans3131 said:
For example, I can't install this ROM. https://androidfilehost.com/?fid=529141701856461698
When I install this ROM, the system doesn't boot
But I can install this ROM. https://androidfilehost.com/?fid=95916177934523996
So what's the problem?
Click to expand...
Click to collapse
which version of twrp are you running?

smart-t78 said:
which version of twrp are you running?
Click to expand...
Click to collapse
I don't use twrp.I'm using PhilZ Touch Recovery 6.59.2

dogukans3131 said:
I don't use twrp.I'm using PhilZ Touch Recovery 6.59.2
Click to expand...
Click to collapse
and thats the cause of your problem. philz touch recovery is out of date and cant handle unified espressowifi builds. if you want to use the latest roms, update to the latest common twrp by android-andi

smart-t78 said:
and thats the cause of your problem. philz touch recovery is out of date and cant handle unified espressowifi builds. if you want to use the latest roms, update to the latest common twrp by android-andi
Click to expand...
Click to collapse
the same problem was repeated for recovery.When I flash this recovery,it doesn't boot https://androidfilehost.com/?fid=673368273298980762
( I flash it using TWRP 3.0.0-0)
But when ı flash TWRP 3.0.0-0 for P5110( https://androidfilehost.com/?fid=24407100847293583 )It works perfectly

dogukans3131 said:
the same problem was repeated for recovery.When I flash this recovery,it doesn't boot https://androidfilehost.com/?fid=673368273298980762
( I flash it using TWRP 3.0.0-0)
But when ı flash TWRP 3.0.0-0 for P5110( https://androidfilehost.com/?fid=24407100847293583 )It works perfectly
Click to expand...
Click to collapse
which rom do you want to install?
when you run a unified common twrp, you cant install older device specific roms. if you run an older device specific twrp, you cant install newer unified roms.

smart-t78 said:
which rom do you want to install?
when you run a unified common twrp, you cant install older device specific roms. if you run an older device specific twrp, you cant install newer unified roms.
Click to expand...
Click to collapse
I want to install newer unified ROMs, but I can't install anything for Unified , I can only install device specific ROM and TWRP
If I install anything for "Unified espresso" (ROM, TWRP, Kernel etc.), the system will not boot, but if I install anything for device specific, the system will boot successfully

dogukans3131 said:
I want to install newer unified ROMs, but I can't install anything for Unified , I can only install device specific ROM and TWRP
If I install anything for "Unified espresso" (ROM, TWRP, Kernel etc.), the system will not boot, but if I install anything for device specific, the system will boot successfully
Click to expand...
Click to collapse
so what was the last installed samsung stock rom? 4.2.2 or 4.0.4?

smart-t78 said:
so what was the last installed samsung stock rom? 4.2.2 or 4.0.4?
Click to expand...
Click to collapse
4.2.2

dogukans3131 said:
4.2.2
Click to expand...
Click to collapse
ok.
next case is there replaced hardware in your tab (e.g mainboard, display)? you need a special kernel then. look here https://forum.xda-developers.com/ga...nified/kernel-anykernel-t3484739/post74352635

smart-t78 said:
ok.
next case is there replaced hardware in your tab (e.g mainboard, display)? you need a special kernel then. look here https://forum.xda-developers.com/ga...nified/kernel-anykernel-t3484739/post74352635
Click to expand...
Click to collapse
No

dogukans3131 said:
No
Click to expand...
Click to collapse
are you sure. maybe its a refurbished tab. try it out. install common twrp + unified rom + special kernel for your device

smart-t78 said:
are you sure. maybe its a refurbished tab. try it out. install common twrp + rom + special kernel for your device
Click to expand...
Click to collapse
Is this the kernel I need to install?
anykernel-2017-11-04-17-13-p5110-only.zip
And is this kernel compatible with Kitkat?(I'm using cm11)

dogukans3131 said:
Is this the kernel I need to install?
anykernel-2017-11-04-17-13-p5110-only.zip
And is this kernel compatible with Kitkat?(I'm using cm11)
Click to expand...
Click to collapse
backup your current system. after that try a marshmallow rom (e.g lineage 13). only to be sure

dogukans3131 said:
Is this the kernel I need to install?
anykernel-2017-11-04-17-13-p5110-only.zip
And is this kernel compatible with Kitkat?(I'm using cm11)
Click to expand...
Click to collapse
no, this kernel isnt compatible with kitkat.

smart-t78 said:
no, this kernel isnt compatible with kitkat.
Click to expand...
Click to collapse
I just downloaded Cyanogenmod 13 (device specific). Does this kernel work with device-specific ROMs? If it works, I'll try to flash the latest Unified TWRP first. If it works, I'll install the Unified ROMs.
The second question is, can I install cm 13 without factory reset(on CM 11)

dogukans3131 said:
I just downloaded Cyanogenmod 13 (device specific). Does this kernel work with device-specific ROMs? If it works, I'll try to flash the latest Unified TWRP first. If it works, I'll install the Unified ROMs.
The second question is, can I install cm 13 without factory reset(on CM 11)
Click to expand...
Click to collapse
1. i think there is no need for the special kernel on device specific roms. keep in mind that device specific builds wont be supported and wont get updates amymore.
2. no, you cant upgrade from cm11 to cm13 without factory reset. clean install is needed

smart-t78 said:
1. i think there is no need for the special kernel on device specific roms. keep in mind that device specific builds wont be supported and wont get updates amymore.
2. no, you cant upgrade from cm11 to cm13 without factory reset. clean install is needed
Click to expand...
Click to collapse
No, I want to install this kernel because I want to install Unified TWRP. If it works, then install Unified ROM

dogukans3131 said:
No, I want to install this kernel because I want to install Unified TWRP. If it works, then install Unified ROM
Click to expand...
Click to collapse
You can install unified twrp (or any other version of twrp) without installing the kernel. The rom and the kernel you have installed are completely independent of the twrp recovery. If you want to install a unified rom with a custom kernel you must first install unified twrp, then clean flash the rom and after that flash the kernel.

john99ap said:
You can install unified twrp (or any other version of twrp) without installing the kernel. The rom and the kernel you have installed are completely independent of the twrp recovery. If you want to install a unified rom with a custom kernel you must first install unified twrp, then clean flash the rom and after that flash the kernel.
Click to expand...
Click to collapse
Unfortunately, I can't enter the recovery mode when I flash Unified TWRP (after the Samsung Galaxy Tab 2 logo, the screen goes black and remains until I restart the system). I can only enter the recovery mode when I flash device specific TWRP

Related

TWRP - Update AOSP meaning

Hi all,
I know that AOSP is Android Open Source Project.
So, when TWRP says that version 2.8.6.1 includes a "Update AOSP base to 5.1", what does it exactly mean?
Does it mean that the device OS will be upgraed to Android 5.1 ?
BTW, I ask it here just because I have N5...
Thank you
dushkin said:
Hi all,
I know that AOSP is Android Open Source Project.
So, when TWRP says that version 2.8.6.1 includes a "Update AOSP base to 5.1", what does it exactly mean?
Does it mean that the device OS will be upgraed to Android 5.1 ?
BTW, I ask it here just because I have N5...
Thank you
Click to expand...
Click to collapse
No, it doesn't mean that.
So,
1. Can you explain to me please what does it mean exactly?
2. TWRP does not let me install the OTA upgrade to 5.1. how can I overcome that?
Thank you!!
dushkin said:
So,
1. Can you explain to me please what does it mean exactly?
2. TWRP does not let me install the OTA upgrade to 5.1. how can I overcome that?
Thank you!!
Click to expand...
Click to collapse
It means that TWRP base has been updated to Android 5.1. TWRP is based on the open source Android recovery, with each release of Android (4.4, 5.0, 5.1 etc) Google update everything to the new base. So currently everything in Googles repo is a 5.1 base. TWRP updates itself to the latest android recvoery base which is 5.1. It allows for the flashing of latest ROMs, bug fixes and any new features (although in Google stock recovery, new features are very rare)
To update to 5.1 you will need to flash an unoffcial stock version in the development secion or you can grab the OTA zip and 'adb sideload' it.
Thank you Matt
1. Can you just point me to the place where I can select the files to flash?
2. Which one would you recomment me to use?
3. Can I flash them with TWRP?
Many thanks!
dushkin said:
So,
2. TWRP does not let me install the OTA upgrade to 5.1. how can I overcome that?
Thank you!!
Click to expand...
Click to collapse
What's the exact error when installing OTA on TWRP, please.
dushkin said:
Thank you Matt
1. Can you just point me to the place where I can select the files to flash?
2. Which one would you recomment me to use?
3. Can I flash them with TWRP?
Many thanks!
Click to expand...
Click to collapse
You cant apply ota updates above 5.x.x with twrp. Use stock recovery instead.
It is not an error. Aftert the upgrade is downloaded it reboots into the TWRP screen and there I do not know what to do.
So, I simply choose to reboot into system from there, and thus, there is no upgrade.
dushkin said:
It is not an error. Aftert the upgrade is downloaded it reboots into the TWRP screen and there I do not know what to do.
So, I simply choose to reboot into system from there, and thus, there is no upgrade.
Click to expand...
Click to collapse
Oh, so it's exactly like @bitdomo said, and I quote, "You cant apply ota updates above 5.x.x with twrp. Use stock recovery instead."

xposed on stock cm13?

Can we install xposed on the stock rooted cm13 nightly on this phone? Or do we have to install another ROM? This phone confuses me how its already rooted but there are still guides on how to root it.... and yes I have twrp.
yes you can use xposed on official cm13.. but be aware of the modules.. some are still not compatible with 6.0 and result in a bootloop
Which version is the proper one to install for this phone
NexusS4gFreak said:
Which version is the proper one to install for this phone
Click to expand...
Click to collapse
Two steps
Download and install this file as an apk
http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
Download and flash this file from your custom recovery like TWRP
http://forum.xda-developers.com/attachment.php?attachmentid=3543418&d=1447616689
Now, you can install the supported list of xposed modules

What did TWRP do to my tablet?

I installed TWRP. It was supposed to be TWRP 2.8.6.0, but it is 2.8.5.0. Today, I just backed up my tablet with it. After using TWRP, my tablet boots up 6 times faster and the UI functions twice as fast as it did before. Overall, my tablet got better after running TWRP. So, what did it do? Also, I want to flash Lollipop. Can I do that with this version?
I don't know what twrp did to your tablet. If you want to flash a lollipop or a marshmallow rom however you should use this version of twrp : http://forum.xda-developers.com/gal...overy-team-win-recovery-project-twrp-t3464050
And use one of theses rom :
lollipop : http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-cyanogenmod-12-cm12-t2997934
Marshmallow (recommended) : http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
Ka-B00M said:
I installed TWRP. It was supposed to be TWRP 2.8.6.0, but it is 2.8.5.0. Today, I just backed up my tablet with it. After using TWRP, my tablet boots up 6 times faster and the UI functions twice as fast as it did before. Overall, my tablet got better after running TWRP. So, what did it do? Also, I want to flash Lollipop. Can I do that with this version?
Click to expand...
Click to collapse
twrp manage all general functions before the android system completely started. you can compare twrp with the bios system on your pc.
if you want install the latest roms, you should upgrade your twrp to the latest unofficial common version (3.0.2-6). you can find it here: http://andi34.github.io/recoveries_tab2.html
smart-t78 said:
twrp manage all general functions before the android system completely started. you can compare twrp with the bios system on your pc.
if you want install the latest roms, you should upgrade your twrp to the latest unofficial common version (3.0.2-6). you can find it here: http://andi34.github.io/recoveries_tab2.html
Click to expand...
Click to collapse
Can I flash the linked recovery using the recovery I already have? If not, how can i do it? I do not have a PC, BTW.
Ka-B00M said:
Can I flash the linked recovery using the recovery I already have? If not, how can i do it? I do not have a PC, BTW.
Click to expand...
Click to collapse
yes, you can install the new version with your current twrp.
smart-t78 said:
yes, you can install the new version with your current twrp.
Click to expand...
Click to collapse
Awesome.
It's official, my device will be upgraded. May the force be with us all!

Trouble updating mi-globe rom

Hello! I have been using mi-globe & previous smiui for quite some time and never had an issue with dirty flashes. Now, I try to install 6.12.22 over the 6.11.24 version and I always get an "Updater gave an Error 7" and the update fails. I want to flash 6.12.22 to prepare myself for android 7 update. I have also tried to flash 6.12.15 version and also fails. I have tried with TWRP version 2.8.7.3 and later with version 3 which also fails. What can I do ?
Weired...
Are you sure you took the right one? DL again via a computer?
Your nov. build should have the last TWRP version. Did you tried to update it via fastboot?
Kéno40 said:
Weired...
Are you sure you took the right one? DL again via a computer?
Your nov. build should have the last TWRP version. Did you tried to update it via fastboot?
Click to expand...
Click to collapse
yes of course i tested all that... i've tried multiple times
alexvv said:
yes of course i tested all that... i've tried multiple times
Click to expand...
Click to collapse
You have this TWRP :
https://www.androidfilehost.com/?fid=529152257862699043
Or team's superluminal one? (this one I think.. https://www.androidfilehost.com/?fid=24421527759888487)
Did you try to install the same version on Xiaomi.eu before, and just flash over the Mi-globe twice?
Kéno40 said:
You have this TWRP :
https://www.androidfilehost.com/?fid=529152257862699043
Or team's superluminal one? (this one I think.. https://www.androidfilehost.com/?fid=24421527759888487)
Did you try to install the same version on Xiaomi.eu before, and just flash over the Mi-globe twice?
Click to expand...
Click to collapse
thanks for the help but i succeeded by dirty flashing xiaomi.eu 6.12.22 over mi-globe 6.11.24, for some reason it worked. I don't know which one recovery I have, i flashed the 3.0 version using the TWRP app from tha playstore, I don't know which of the two is this ( I think the file I flashed was around 45mb so it's probably the first...).
UPDATE: I have the 3.0.2 TWRP version. Is it compatible with nougat ??
I'm not sure it's about the number only. On the mi-globe topic, it's explained. Flash nougat. Then unlockdevice, then flash twrp compatible

How to install TWRP on Xperia L running unlocked bootloader, rooted stock ROM?

I have rooted my Xperia L stock ROM 15.3.A.1.17 and unlocked the bootloader. Now I wish to install TWRP recovery on a separate partition. As indicated on official TWRP page on Xperia L,
The Xperia devices have a recovery-in-boot arrangement. This means that the recovery is booted using the regular kernel / boot image in the device. Team Win has worked with the FreeXperia device maintainers to come up with a way to extract the ramdisk from the FOTAKernel partition and use the ramdisk from that partition instead of the recovery that is included in the boot image of your device. This means that if you install current CM nightlies and flash TWRP to the FOTAKernel partition, you will be able to use TWRP instead of the CWM or CM recovery that normally comes in a CM boot image. Other boot images including stock kernels can be repacked to include this extraction utility to allow you to use TWRP from the FOTAKernel partition. This setup allows you to choose what recovery you want to have installed and allows you to update your recovery more easily. Unfortunately this setup requires that the boot image that you have installed include the ramdisk extraction utility. The source for this utility is here.
This setup means that you must have a kernel or boot image installed that will use the FOTAKernel method. This utility is designed to work in conjunction with the current methods that most AOSP ROMs, like OmniROM or CyanogenMod, will support. Some rare stock kernels may also support the FOTAKernel method.
What does all this mean? It means that TWRP may not work on your device unless you install other custom software as well. Check with your ROM developer to see what they support.
Click to expand...
Click to collapse
However, the stock kernel does not support FOTAkernel method a.ka. extract_elf_ramdisk feature. The webpage does not address the issue of running TWRP on stock kernel. It's like a chicken and egg problem. To have TWRP running, one needs a custom kernel. To flash a custom ROM, one needs TWRP (or other custom recovery).
I can think of two possible ways of breaking this deadlock.
Possible method #1:
Flash TWRP using Recovery Installer Toolkit for Xperia L
Flash a custom ROM (zip) from this recovery
Flash TWRP to FOTAkernel using official TWRP app or dd-ing a TWRP raw image on FOTAkernel partition or using Recoveries and Recovery Installer for Taoshan
Possible method #2:
Use a stock ROM image with TWRP integrated:
Code:
adb flash boot boot_twrp2.img
Flash a custom ROM (zip) from this recovery
Flash TWRP to FOTAkernel using official TWRP app or dd-ing a TWRP raw image on FOTAkernel partition or using Recoveries and Recovery Installer for Taoshan
Possible method #3:
Boot into fastboot mode
Flash the TWRP image directly onto the boot partition
Code:
fastboot flash boot twrp.img
Reboot the phone which now should boot directly to TWRP recovery
The screen flickers when you are in recovery menu. However, flashing a custom ROM will fix the problem
Flash a custom ROM (zip) from this recovery
Flash TWRP to FOTAkernel using official TWRP app or dd-ing a TWRP raw image on FOTAkernel partition or using Recoveries and Recovery Installer for Taoshan
As of now, I installed TWRP on FOTAkernel partition using official TWRP app. As expected, when I issue,
Code:
adb reboot recovery[/CODEL] the phone boots to stock recovery instead of TWRP. This behavior is expected as stock kernel knows nothing about TWRP being located on FOTAkernel.
I don't even know if any of the proposed methods work. However, before embarking down any one of those routes, I want to ask the community if I am overlooking any straightforward, less cumbersome alternative(s).
[B]Credits:[/B]
[LIST]
[*] Dees_Troy
[*] Kungfu73
[/LIST]
Holmes.Sherlock said:
I have rooted my Xperia L stock ROM 15.3.A.1.17 and unlocked the bootloader. Now I wish to install TWRP recovery on a separate partition. As indicated on official TWRP page on Xperia L,
However, the stock kernel does not support FOTAkernel method a.ka. extract_elf_ramdisk feature. The webpage does not address the issue of running TWRP on stock kernel. It's like a chicken and egg problem. To have TWRP running, one needs a custom kernel. To flash a custom ROM, one needs TWRP (or other custom recovery).
I can think of two possible ways of breaking this deadlock.
Possible method #1:
Flash TWRP using Recovery Installer Toolkit for Xperia L
Flash a custom ROM (zip) from this recovery
Flash TWRP to FOTAkernel using official TWRP app or dd-ing a TWRP raw image on FOTAkernel partition or using Recoveries and Recovery Installer for Taoshan
Possible method #2:
Use a stock ROM image with TWRP integrated:
Code:
adb flash boot boot_twrp2.img
Flash a custom ROM (zip) from this recovery
Flash TWRP to FOTAkernel using official TWRP app or dd-ing a TWRP raw image on FOTAkernel partition or using Recoveries and Recovery Installer for Taoshan
As of now, I installed TWRP on FOTAkernel partition using official TWRP app. As expected, when I issue,
Code:
adb reboot recovery[/CODEL] the phone boots to stock recovery instead of TWRP. This behavior is expected as stock kernel knows nothing about TWRP being located on FOTAkernel.
I don't even know if any of the proposed methods work. However, before embarking down any one of those routes, I want to ask the community if I am overlooking any straightforward, less cumbersome alternative(s).[/QUOTE]
Well, I think installing latest TWRP directly from stock XL ROM for first time is hard for everyone :D
I myself exactly used first method and worked fine. Also please note that in step 2 of method 1, you should install some Lollipop or KitKat versions of custom ROM (because current recovery is old)
I've not tested 2nd method, but it should work too.
I think these methods are the most simple ones if you want to jump from stock to latest TWRP ;)[COLOR="Silver"]
[SIZE=1]---------- Post added at 12:06 PM ---------- Previous post was at 11:53 AM ----------[/SIZE]
[/COLOR]Oh I forgot to mention that there is another (a little risky) way to use latest TWRP.
Using adb&fastboot run this command:
[B]fastboot flash boot twrp.img[/B]
[I](twrp.img is your recovery image name)[/I]
This command flashes recovery image directly to boot partition and because of that, when you power on the phone, you jump directly to TWRP recovery!
[B] Please note that in this method, the screen flickers when you are in recovery menu, but it's normal and gets fixed by flashing custom ROM
Note 2: immediately after booting to recovery, flash your custom ROM to avoid any problems![/B]
If there were any problems, simply flash stock ROM to get back to normal state.
Click to expand...
Click to collapse
Kungfu73 said:
Also please note that in step 2 of method 1, you should install some Lollipop or KitKat versions of custom ROM (because current recovery is old)
Click to expand...
Click to collapse
I don't get the point why I need a KitKat/Lollipop based custom ROM. What do you mean by current recovery being old?
Oh I forgot to mention that there is another (a little risky) way to use latest TWRP.
Using adb&fastboot run this command:
fastboot flash boot twrp.img
(twrp.img is your recovery image name)
This command flashes recovery image directly to boot partition and because of that, when you power on the phone, you jump directly to TWRP recovery!
.
Click to expand...
Click to collapse
I talked to @Dees_Troy on IRC about the issue and he suggested the same to me.
.
Please note that in this method, the screen flickers when you are in recovery menu, but it's normal and gets fixed by flashing custom ROM
Note 2: immediately after booting to recovery, flash your custom ROM to avoid any problems!
If there were any problems, simply flash stock ROM to get back to normal state.
Click to expand...
Click to collapse
I am also experiencing flickering. It's surprising to hear that the problem is supposed to go away with custom ROM. Do you have any idea how does having a custom ROM make any difference at all?
Holmes.Sherlock said:
I don't get the point why I need a KitKat/Lollipop based custom ROM. What do you mean by current recovery being old?
Click to expand...
Click to collapse
Well, the version of twrp that recovery installer app flashes, is 2.7 or something like that (not 3.0.2) and it may fail to flash MM or N ROMs (it's mentioned in some official custom ROMs download page to use latest TWRP)
Holmes.Sherlock said:
I am also experiencing flickering. It's surprising to hear that the problem is supposed to go away with custom ROM. Do you have any idea how does having a custom ROM make any difference at all?
Click to expand...
Click to collapse
If you mean by difference, fixing the flickering, well it wipes boot partition while flashing ROM, and (some of ROMs) flash latest TWRP to fota agian, and it fixes that
But if you mean difference between stock and custom ROM, well... it depends on your using. The most obvious ones are the improved security and more space for apps and tons of customizable and useful features, etc.
(And also sorry if I had mistakes in English!)
Kungfu73 said:
Well, the version of twrp that recovery installer app flashes, is 2.7 or something like that (not 3.0.2) and it may fail to flash MM or N ROMs (it's mentioned in some official custom ROMs download page to use latest TWRP).
Click to expand...
Click to collapse
The installer app lets you choose the version to flash. You can very well flash any version (of twrp.img) downloaded on your phone.
Holmes.Sherlock said:
The installer app lets you choose the version to flash. You can very well flash any version (of twrp.img) downloaded on your phone.
Click to expand...
Click to collapse
Oh this is what that makes difference!
On stock ROM, you can only use old TWRP's that are compatible with stock ROMs that don't support fota !
And also you should use the recovery that the app gives to you
Kungfu73 said:
On stock ROM, you can only use old TWRP's that are compatible with stock ROMs that don't support fota !
And also you should use the recovery that the app gives to you
Click to expand...
Click to collapse
The app gives a list of all recovery versions available on the official website for category `taoshan`. Are you sure that there is some TWRP version that does not support FOTA and works with stock ROM?
Holmes.Sherlock said:
The app gives a list of all recovery versions available on the official website for category `taoshan`. Are you sure that there is some TWRP version that does not support FOTA and works with stock ROM?
Click to expand...
Click to collapse
Well, if you check the official twrp website, there is no version before 2.8 for XL , and lol those removed ones are compatible!
Kungfu73 said:
Well, if you check the official twrp website, there is no version before 2.8 for XL , and lol those removed ones are compatible!
Click to expand...
Click to collapse
I am curious to know how come any TWRP version be compatible with stock ROM unless the recovery ramdisk is integrated with the boot image than being written onto FOTAkernel.
Holmes.Sherlock said:
I am curious to know how come any TWRP version be compatible with stock ROM unless the recovery ramdisk is integrated with the boot image than being written onto FOTAkernel.
Click to expand...
Click to collapse
I don't have much detailed information about that.
You can get help from experts
And could you finally flash and boot any version of twrp using that 3 methods?
Kungfu73 said:
And could you finally flash and boot any version of twrp using that 3 methods?
Click to expand...
Click to collapse
I tried method #2 and #3. Both works

Categories

Resources