I wanted to clean flash a new CM10.2 nightly so I made a nandroid in TWRP 2.6.0.0 and then wiped data, system, and caches. But when I went to select the new nightly, ALL of my data was gone, including internal storage /sdcard. I have everything backed up to the cloud, no biggie. I adb push the newest nightly, gapps, and m_plus kernel to /sdcard and flash. It seems to work fine, go through setup wizard, then I reboot my phone again and now it's stuck at the google logo. I hold the power button, hard reboot again and again, but it's just stuck. So I go back into TWRP and try to reflash the ROM, but then it gives this error message:
E:error opening '/data/data/com.google.android.setupwizard'
E:error I/O error
I tried to adb push an older nightly to /sdcard in recovery, then I get this message:
failed to copy 'cm-10.2-20130914-NIGHTLY-mako.zip' to '/sdcard//cm-10.2-20130914-NIGHTLY-mako.zip': Read-only file system
What?! I tried fixing permissions, but it gave the same I/O error as above. I tried formatting internal storage and it gave me this error:
E:Unable to chmod '/data/data/com.android.phasebeam/.'
I am out of ideas and I did not see anyone with this issue after a quick search. What do I need to do to fix this?
Just clean out everything, reinstall it all
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
Now boot to recovery and sideload ROM of choice
Might be overkill, but will only take a couple minuets and you'll be so fresh and so clean
Sent from my Nexus 4 using Tapatalk 2
Have you tried to restore the factory image via fastboot?
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 4 using Tapatalk 4
You have to mount /data as read write. Do
adb shell
busybox mount -o remount,rw /data
If that doesnt work, try
mount -o remount,rw /data
demkantor said:
Just clean out everything, reinstall it all
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
Now boot to recovery and sideload ROM of choice
Might be overkill, but will only take a couple minuets and you'll be so fresh and so clean
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
This worked! Turns out that the Format Data option in TWRP (requires you to type 'yes') erases your whole device instead of the /data partition. oops! I'm not sure why this option borked the permissions for /sdcard or the other errors, but fastboot erase seems to have fixed it. Thanks demkantor!
ChemBot said:
This worked! Turns out that the Format Data option in TWRP (requires you to type 'yes') erases your whole device instead of the /data partition. oops! I'm not sure why this option borked the permissions for /sdcard or the other errors, but fastboot erase seems to have fixed it. Thanks demkantor!
Click to expand...
Click to collapse
HELP! that just happened to me, everything seems to be okay, mi device installs the ROM but never starts the phone
I've been reading the recovery and appears that, E: error: data....
How U did the "fastboot"??
Thank you
demkantor said:
Just clean out everything, reinstall it all
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
Now boot to recovery and sideload ROM of choice
Might be overkill, but will only take a couple minuets and you'll be so fresh and so clean
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Thank you so much bro....
demkantor said:
Just clean out everything, reinstall it all
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
Now boot to recovery and sideload ROM of choice
Might be overkill, but will only take a couple minuets and you'll be so fresh and so clean
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
this worked for me too, but 10 seconds into twrp froze ant booted.
My phone has been stck in a bootloop, doesnt pass google screen. OEM unlocked, rooted, PURENEXUS ROM, out of the blue phone booted and has been that way since. I cant side load on ADB because ADB does not reconize device but Fastboot does. I tried eveything i posssibly could in fastboot to get this working and nothing is working.
Other forums state this as a bug from google and not fixable, could also be a hardware issue, so porobably considering getting a new phone
Mefer said:
this worked for me too, but 10 seconds into twrp froze ant booted.
My phone has been stck in a bootloop, doesnt pass google screen. OEM unlocked, rooted, PURENEXUS ROM, out of the blue phone booted and has been that way since. I cant side load on ADB because ADB does not reconize device but Fastboot does. I tried eveything i posssibly could in fastboot to get this working and nothing is working.
Other forums state this as a bug from google and not fixable, could also be a hardware issue, so porobably considering getting a new phone
Click to expand...
Click to collapse
Use nexus root toolkit google it install on a PC and it will fix your phone maybe depending on the cause of the issue worth a try
I'll give it a try, Def will keep you posted
Thanks man
lopezk38 said:
You have to mount /data as read write. Do
adb shell
busybox mount -o remount,rw /data
If that doesnt work, try
mount -o remount,rw /data
Click to expand...
Click to collapse
can you pls tell the commands
Vijayyaru said:
can you pls tell the commands
Click to expand...
Click to collapse
Those are the commands:
Code:
busybox mount -o remount,rw /data
If that doesnt work, try
Code:
mount -o remount,rw /data
Nitin
Related
I tried encrypting my phone today while on CM10.1 and it rebooted and hung on the google screen for a few minutes so I held the power button and it rebooted and went back into CM10.1 except it said, encryption was unsuccessful and i needed to do a factory reset. So I let it reset, but it kept sending me to that page. So i booted into recovery tried to manually wipe it and it said /sdcard could not be mounted. I am currently using a linux toolkit and trying to push the google sock image, so far it has pushed the bootloader, boot, and recovery. I am sitting at system and thinking my phone is borked.
Someone else mentioned that they can't mount /sdcard .... are you actually trying to mount it?
Are you using fastboot to flash the appropriate stock files?
From bootloader: fastboot flash boot boot.img
fastboot flash system system.img etc... ?
Or running the flashall.sh script in the stock downloaded files?
>I have a Nexus 7
>Rooted, with CWM recovery
>Paranoid Andoid installed, works fine
>Decide to try alternative Rom's
>Download and install CM
>Bootloops
>Flash to stock and unroot using Nexus Root Toolkit
>Root again, install TeamWin recovery
>Try and flash CM again
>Bootloops
>Flash to stock again, install TeamWin recovery
>Try Smooth Rom
>Starts fine
>Reboot
>Bootloops
>Flash to stock again, install CWM recovery
>Decide to flash Paranoid Android as I wish I hadn't changed anything
>Flash PA
>Bootloops
>Flash to stock again, install CWM recovery
>Flash PA
>Boots fine, all going well
>Reboot
>Bootloops
So basically, that is the situation, and I can't figure out why it is happening. I have flashed Rom's before with no problem, but ever since I tried CM, it's all funked up, so yeah, any help at all would be greatly appreciated
The one thing I don't see in your set of trials is whether or not the complete stock ROM (whether rooted or not) bootloops on it's 2nd boot the way all the other combinations seem to.
Did you do that, or did you presume that we would also presume that Stock always boots in your experiments (at least twice!)?
BTW, you don't need to follow then entire Stock installation script if your tablet bootloader (& radio in the tilapia case) are up to date. That will save you extra steps and the need to re-flash the recovery image afterwards. All that should be needed are:
Code:
fastboot erase system
fastboot format system
fastboot flash system system.img
[b][color=red]fastboot format userdata[/color][/b] *
* obviously this nukes EVERYTHING in userdata, so a complete backup of anything you want saved from /sdcard is needed beforehand. You could replace this step with just a "factory reset" procedure in the custom recovery if you want to avoid the hassle and are convinced that the userdata partition is not causing problems (it's filesystem looks healthy & is appropriately-sized for the variant of the device you have).
Note that this proposal assumes that "flash userdata userdata.img" from the factory install instructions is superfluous. (Unless perhaps there is some sort of "oneshot" logic in there that alters /system on the first boot but not thereafter) - otherwise, how could you erase all of /data and get a "factory reset" some time later? But I think the filesystem sent by this command actually has no files in it, so... same conclusion... superfluous).
bftb0 said:
The one thing I don't see in your set of trials is whether or not the complete stock ROM (whether rooted or not) bootloops on it's 2nd boot the way all the other combinations seem to.
Did you do that, or did you presume that we would also presume that Stock always boots in your experiments (at least twice!)?
BTW, you don't need to follow then entire Stock installation script if your tablet bootloader (& radio in the tilapia case) are up to date. That will save you extra steps and the need to re-flash the recovery image afterwards. All that should be needed are:
Code:
fastboot erase system
fastboot format system
fastboot flash system system.img
[b][color=red]fastboot format userdata[/color][/b] *
* obviously this nukes EVERYTHING in userdata, so a complete backup of anything you want saved from /sdcard is needed beforehand. You could replace this step with just a "factory reset" procedure in the custom recovery if you want to avoid the hassle and are convinced that the userdata partition is not causing problems (it's filesystem looks healthy & is appropriately-sized for the variant of the device you have).
Note that this proposal assumes that "flash userdata userdata.img" from the factory install instructions is superfluous. (Unless perhaps there is some sort of "oneshot" logic in there that alters /system on the first boot but not thereafter) - otherwise, how could you erase all of /data and get a "factory reset" some time later? But I think the filesystem sent by this command actually has no files in it, so... same conclusion... superfluous).
Click to expand...
Click to collapse
I kept flashing to stock so I know where I'm at each time, I'm pretty knew to all this so I don't want to confuse myself.
I'm just about to flash stock and see if that bootloops now.
I don't understand how any files could remain on there after a factory reset though, thats why can't grasp why it's bootlooping every time
okay, so I have flashed stock, and it DOES NOT bootloop
miketino said:
I don't understand how any files could remain on there after a factory reset though, thats why can't grasp why it's bootlooping every time
Click to expand...
Click to collapse
It does seem unusual. OTOH, a "factory reset" in the custom recovery never re-builds the /data ext4 filesystem - so I suppose if the filesystem itself was bolluxed up, that would persist across a (custom recovery) "factory reset".
The thing is, the sequence you describe involves re-doing things with the factory install, and either
Code:
fastboot erase userdata
fastboot format userdata
fastboot flash userdata userdata.img
or
Code:
fastboot format userdata
fastboot flash userdata userdata.img
seems like they certainly should be rebuilding the ext4 filesystem in the userdata (/data) partition.
I mentioned something like this in a couple other posts, but I have experienced odd troubles with the /system partition where I could occasionally create an empty (and new) filesystem using the "Wipe system" option in TWRP, and immediately after that, if I manually checked it's status using (TWRP's) "e2fsck" program, it would report massive problems
Code:
adb shell e2fsck -f -n /dev/block/mmcblk0p<PARTNUM>
which doesn't make any sense at all - a brand-new & empty filesystem should be perfectly clean!
Anyway, something you might want to try is to run the above e2fsck program as a sanity check just after you flash a ROM and just before you are getting ready to reboot into the normal OS. The "-n" option to "e2fsck" prevents it from altering anything, so this is a nondestructive (no touch/read only) test. (I've never tried to actually use e2fsck for a repair - I just start over either with fastboot or the recovery filesystem formatting).
Note that "e2fsck" needs the partitions to be unmounted, so e.g. in TWRP you would:
Code:
adb shell umount /system
adb shell e2fsck -f -n /dev/block/mmcblk0?? (grouper system = p3)
adb shell umount /sdcard
adb shell umount /data
adb shell e2fsck -f -n /dev/block/mmcblk0?? (grouper data = p9)
If they don't come up clean, obviously you need to do something. Because "mount /sdcard" seems to fail when performed manually in TWRP, I just re-boot the recovery from within TWRP to do other tasks, should that be necessary.
Hope this helps.
miketino said:
okay, so I have flashed stock, and it DOES NOT bootloop
Click to expand...
Click to collapse
I wonder if this means something screwy is being caused by the ROM flashing in the recovery. Maybe try the above suggestions just as a sanity check?
BTW, what recovery and version are you using?
Its Clockwork Mod Recovery, version 6.0.2.3
miketino said:
Its Clockwork Mod Recovery, version 6.0.2.3
Click to expand...
Click to collapse
fwiw, I just booted the touch version of CWM 6.0.2.3
Code:
fastboot boot recovery-clockwork-touch-6.0.2.3-grouper.img
to make sure that it had e2fsck present in it's /sbin. It does.
e.g. my (32 GB grouper) device:
Code:
# e2fsck -f -n /dev/block/platform/sdhci-tegra.3/by-name/UDA
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/sdhci-tegra.3/by-name/UDA: 24564/1875968 files (0.4% non-contiguous), 2641387/7503608 blocks
# e2fsck -f -n /dev/block/platform/sdhci-tegra.3/by-name/APP
e2fsck -f -n /dev/block/platform/sdhci-tegra.3/by-name/APP
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/sdhci-tegra.3/by-name/APP: 1100/41664 files (1.0% non-contig
uous), 121097/166400 blocks
also, "tune2fs" seems to be present too. You can get a listing of the filesystem creation options using the -l option, as in
Code:
tune2fs -l /dev/block/platform/sdhci-tegra.3/by-name/APP
although I will say I've compared this output before, searching for difference(s) between the way that fastboot formats things and the custom recovery does things and didn't see anything compelling.
[ TWRP might be different than CWM though - it has a utility called "make_ext4fs", whereas I think CWM uses "mke2fs" for fs creation. ]
HTH
Hello everybody!
Last week installing cyainfire my device felt in bootloop..
I tryed all the ways possible but i' m sure someone of you will be better
I have destroyed everything on the nexus, also the recovery.. The only one working is the bootloader (obviously unlocked)
What i can do at this moment is: flashing a custom recovery TWRP on the device by toolkit and from there activating the ADB sideload. Trought cmd the working and useful commands are:
Code:
adb push rom.zip
adb sideload rom.zip
From the recovery i wasn' t able to flash the pushed zip...
I tryed several times with the sideload but the nexus was telling me that it couldn' t mount /system and /cache... So, it wasn' t working..
But finally i tryed wiping everything whit the commands:
Code:
fastboot erase system
fastboot erase cache
fastboot erase userdata
And formatting data by the TWRP..
(It is still saying me it cannot mount the /cache)
The ADB sideload of the device was working but anyway it fails flashing the sent zip..
What could be the problem? I have no more ideas...
Thanks a lot
p.s. english is not my first language
P.S.2: Solved on my own.. this time the sideload command worked.. sometimes i thing the linux kernel has its owns intelligence..
So to start I'm not new to this, I've been flashing roms for a couple years now except right now I've gotten myself in a sticky situation.
Heres what I did, now I'm stuck and I'm not sure if my linux build is messing it up.
Linux ADB drivers previously installed
First downloaded TWRP 2.6.0.0
Then I got SuperSU
I followed all the steps here http://schier.co/post/how-to-root-nexus-7-(2013)-in-linux
Everything went smooth until step 5 the reboot, then it just got stuck. So I powered off and booted back in to recovery to make sure I still had TWRP, I did. So I decided to try and reboot to the bootloader, works fine getting there.
Heres where I'm stuck
1. TWRP shows internal memory 0MB and unable to factory reset etc.
2. Booted in fastboot and tried to just install the stock images from google located here JSS15Q However terminal stays stuck at <waiting for device>
adb kill-server followed by adv devices shows nothing (again in bootloader/fastboot)
Sooo I'm stuck guys :/
I can't adb anything and my TWRP says can't mount E:/ 0MB internal memory.
How do i fix this
kylecore said:
So to start I'm not new to this, I've been flashing roms for a couple years now except right now I've gotten myself in a sticky situation.
Heres what I did, now I'm stuck and I'm not sure if my linux build is messing it up.
Linux ADB drivers previously installed
First downloaded TWRP 2.6.0.0
Then I got SuperSU
I followed all the steps here http://schier.co/post/how-to-root-nexus-7-(2013)-in-linux
Everything went smooth until step 5 the reboot, then it just got stuck. So I powered off and booted back in to recovery to make sure I still had TWRP, I did. So I decided to try and reboot to the bootloader, works fine getting there.
Heres where I'm stuck
1. TWRP shows internal memory 0MB and unable to factory reset etc.
2. Booted in fastboot and tried to just install the stock images from google located here JSS15Q However terminal stays stuck at <waiting for device>
adb kill-server followed by adv devices shows nothing (again in bootloader/fastboot)
Sooo I'm stuck guys :/
I can't adb anything and my TWRP says can't mount E:/ 0MB internal memory.
How do i fix this
Click to expand...
Click to collapse
For the internal memory showing 0MB, just format data from your recovery. I had that issue and once I formatted data from recovery, was able to do everything else I needed.
kylecore said:
So to start I'm not new to this, I've been flashing roms for a couple years now except right now I've gotten myself in a sticky situation.
Heres what I did, now I'm stuck and I'm not sure if my linux build is messing it up.
Linux ADB drivers previously installed
First downloaded TWRP 2.6.0.0
Then I got SuperSU
I followed all the steps here http://schier.co/post/how-to-root-nexus-7-(2013)-in-linux
Everything went smooth until step 5 the reboot, then it just got stuck. So I powered off and booted back in to recovery to make sure I still had TWRP, I did. So I decided to try and reboot to the bootloader, works fine getting there.
Heres where I'm stuck
1. TWRP shows internal memory 0MB and unable to factory reset etc.
2. Booted in fastboot and tried to just install the stock images from google located here JSS15Q However terminal stays stuck at <waiting for device>
adb kill-server followed by adv devices shows nothing (again in bootloader/fastboot)
Sooo I'm stuck guys :/
I can't adb anything and my TWRP says can't mount E:/ 0MB internal memory.
How do i fix this
Click to expand...
Click to collapse
In my experience fastboot needs to be run as root for it to pick up the device (this may be distro-dependent to some degree).
cowabunga said:
For the internal memory showing 0MB, just format data from your recovery. I had that issue and once I formatted data from recovery, was able to do everything else I needed.
Click to expand...
Click to collapse
What he said.
Sent from my Nexus 7 using Tapatalk 4
swagstr said:
What he said.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Agreed. Had the same problem last night, manually formatted system, data and cache, and it worked. If you just try 'factory wipe', it seems to only try and delete, not format, so it fails until you force a format. The guide I was following wasn't quite right, but I figured it out.
I'm also running the Linux method, and tried using the same instructions that you did. I also ran into trouble at the same spot, and my tablet wouldn't reboot successfully after that. I was also able to rescue my tablet by clearing the cache, etc. Since this whole experience was so scary as a new tablet owner, I decided to stop the rooting experiment at that point. I had also tried the one-click rooting app on Windows to fix the problem and then later to re-root, but I had no success with that technique on either.
Now with my tablet full of apps, I am again tempted to retry the rooting process. However, I have no confidence in any technique, either on Linux or windows. I have no idea why the original Linux technique didn't work. If I did retry, I would have to put my full confidence in the backups that I tried to run.
P.S. I used the tapatalk app and voice to create this message, which is sort of neat!
Sent from my Nexus 7 using Tapatalk 4
Linux worked fine for me.
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
adb reboot bootloader
fastboot oem unlock
fastboot reboot-bootloader
cd Downloads
fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
adb push update-supersu-v1.51.zip /sdcard/Downloads
Username invalid said:
Linux worked fine for me.
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
adb reboot bootloader
fastboot oem unlock
fastboot reboot-bootloader
cd Downloads
fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
adb push update-supersu-v1.51.zip /sdcard/Downloads
Click to expand...
Click to collapse
Thanks for the guy who posted terminal commands! +1
Sent from my Nexus 4 using Tapatalk 4
I had a lot of issues trying to successfully flash TWRP and achieve root, so I just resorted to CW recovery and ran into no problems. Kind of sucks, though, I prefer TWRP.
For some reason ADB didn't work well for me, so I stuck with fastboot and downloaded the su package after unlocking. Had it rooted in two minutes.
Sent from my Nexus 7 using XDA Premium HD app
smelenchuk said:
In my experience fastboot needs to be run as root for it to pick up the device (this may be distro-dependent to some degree).
Click to expand...
Click to collapse
Yes, this is a common trouble point. Try running the adb server as root, and then all the subsequent commands as root as well.
Sent from my Nexus 7 using xda app-developers app
smelenchuk said:
In my experience fastboot needs to be run as root for it to pick up the device (this may be distro-dependent to some degree).
Click to expand...
Click to collapse
You can fix this by using a udev rule to assign your user as owner of the usb device
$ cat /etc/udev/rules.d/11-android.rules
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", MODE="0640", OWNER="casey"
Where 18d1 is the beginning of the device id, which you can get from lsusb
$ lsusb -v | grep Nexus
Bus 002 Device 043: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)
(yes, that is actually a Nexus7 2013, but it doesn't matter)
and the OWNER="user" is your username.
After setting up that rule, restart udev and plug your device in and now you can run fastboot as your user.
I hv rooted nexus 7 with f2fs file system i accidently flashed m kernel 5.1 on f2fs incompatible freakslim lp 5.0.2(i didnt knew v need f2fs modified rom also) after i did that rom got stucked on bootanimation,and also i wasnt able to boot twrp also(it showed twrp logo and directly booted into rom) so i tried flashing twrp again but still no luck then i flashed cwm and it boot but doesnt mount /data and /data/media i think its corrupted any way i could repair it without wiping my internal sd card data there are important files in it?when i see log of cwm it shows like this
When try to mount data it shows
Mount: mounting/dev/block/platform/sdhci-tegra.3/by-name/UDA on /data failed : invalid arguement
W: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/UDA (file exits) error mounting data
And for sdcard it shows
I:using/data/media for /sdcard
Mount: mounting/dev/block/platform/sdhci-tegra.3/by-name/UDA on /data failed : invalid arguement
W: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/UDA (file exits) cant mount /sdcard
Plz tell if it is corrupted or not and if yes then how to repair it and also i want to recover all my sdcard data
u can't recover ur data if partition got corrupted
u can still revive ur tab if u are on twrp
just re format partition to f2fs or ext4 then flash ROMs according to partition system
Sent from my Nexus 7 using Tapatalk 2
adeelraj said:
u can't recover ur data if partition got corrupted
u can still revive ur tab if u are on twrp
just re format partition to f2fs or ext4 then flash ROMs according to partition system
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I cant flash twrp i tried flashing it but it doesn't boot jus shows logo n tries to boot rom
ANESH said:
I cant flash twrp i tried flashing it but it doesn't boot jus shows logo n tries to boot rom
Click to expand...
Click to collapse
It happened to me after f2fs crippled the partitions.
Boot into fastboot mode (hold volume buttons till you get the device info and options to boot etc)
Type fastboot /erase userdata
fastboot /erase cache
fastboot /erase system
Then, boot into TWRP again (will work now)
Format the paritions to ext4 (stay safe :3)
Install CM13 and follow its tips to make ext4 better! (Other ROMs will work just fine)
Good luck and stay away from f2fs! Don't attempt data recovery since it's probably crippled. If you wanna try, just copy them from TWRP via USB
Good luck!
KawaiiAurora said:
It happened to me after f2fs crippled the partitions.
Boot into fastboot mode (hold volume buttons till you get the device info and options to boot etc)
Type fastboot /erase userdata
fastboot /erase cache
fastboot /erase system
Then, boot into TWRP again (will work now)
Format the paritions to ext4 (stay safe :3)
Install CM13 and follow its tips to make ext4 better! (Other ROMs will work just fine)
Good luck and stay away from f2fs! Don't attempt data recovery since it's probably crippled. If you wanna try, just copy them from TWRP via USB
Good luck!
Click to expand...
Click to collapse
Will try this and get back to tell if it worked or not thnks
ANESH said:
Will try this and get back to tell if it worked or not thnks
Click to expand...
Click to collapse
Okay! Good luck