Database Info

[WARNING] Do not partition SD card using ClockworkMod | FIXED in 3.0.2.6

As the title says, do not partition SD card using ClockworkMod or ROM Manager.​
There has been multiple bricked devices already, all after partitioning SD in CWM. The device suddenly turns off while the partitioning is in progress, and never turns on again. We do not know what causes this issue yet, but I am sure that ClockworkMod team will look into it.
Update:
Koush said:
Looking into this. I don't have a DHD but I have an idea why this is happening.
Click to expand...
Click to collapse
Update 2:
Koush said:
I have a fix ready now. I will need to release a new recovery and new ROM Manager to address this.
Click to expand...
Click to collapse
Update 3:
New ClockworkMod 3.0.2.6 and ROM Manager 4.1.0.0 are out! There has been multiple confirmations of the problem being fixed, but also ONE brick. So take the fix with a grain of salt.

Wow... Never used partitions on SDcard , but thanks for the warning.
I'm curious how the device bricked while partitioning SDCARD, though, as I don't see the connection!

have another brick here from the same reason, be aware.

MafiotuL said:
Wow... Never used partitions on SDcard , but thanks for the warning.
I'm curious how the device bricked while partitioning SDCARD, though, as I don't see the connection!
Click to expand...
Click to collapse
Easy, partition the wrong partition, iow the NAND/eMMC.

does anybody know if it affects other devices also?

MafiotuL said:
Wow... Never used partitions on SDcard , but thanks for the warning.
I'm curious how the device bricked while partitioning SDCARD, though, as I don't see the connection!
Click to expand...
Click to collapse
HOLY SHT!!!!!!!
I partitioned my sdcard thru Clockword recovery 3 months ago back then with 2.5.0.7 htc desire
it hung for 1 hour so i pulled the battery but it was paritioned rite phewwwwww..
Cant imagine if i had a bricked phone now,would prolly pee on my pants....

Darn it. I was thinking about partitioning my SDCard today but postponed it. Thanks for the information.
Are there any other known issues that the CWM might cause to the device? Last year, when I had HTC Dream, I remember reading in forums at Cyanogen that some people didn't recommend using ROM Manager. I don't know what issues it used to cause because I used Amon_Ra back then.
Anyways, thanks for the information. I won't partition the SDCard using CWM.

Ok............
This thread has been stickied by me in order to inform everybody about this situation.
Do report if you have gone through this problem only...no more thanks or OT chatter, please.
I'm in contact with the Mod team to investigate even further if this does affect any other devices as well.
Please be patient and do not pollute this thread
Cheers,
M_T_M
@jkoljo...thanks for your help on this very important matter.

Got another one here: http://www.android-hilfe.de/root-ha...t-nicht-mehr-nach-partitionierung-der-sd.html [German], thank goodness it wasn't mine

Bricked DHD
Hi There,
Had this a few days ago.
the device is indeed completely bricked, no matter what you do.
Luckily for me my HTC DHD was only 10 days old, so i went to the store and after inspection theyt gave me a new one. I must be very lucky i guess.
Thanks for the warning nevertheless.

hello. I have the same problem. it goes in the black this afternoon before I have read the forum. Is there any thing i can do to get the phone alive again. : ((

All versions of CWM ? Or is it specific to a version ?
All the best,
Sharro

We do not exactly know at this point. At least 3.0.2.5 has the problem.
There is nothing you can do to fix a brick. That is why it is called a brick.

kilavuz said:
hello. I have the same problem. it goes in the black this afternoon before I have read the forum. Is there any thing i can do to get the phone alive again. : ((
Click to expand...
Click to collapse
I believe you can still return it for manufacturer warranty. HTC phones has at least one year manufacturer. Just say to them you turn on your phone and it couldn't turn on....simplesssss

it is only 2 weeks old. : ((

Other solution
Hi guys,
I've also read somewhere, last november I think, that partitioning could be problematic. So I looked up on the internet and can recommand you what I use to partition my SDHC cards: Paragon partition manager 11 free , I used it on Win XP 32 bits without any problem with my 16gb and with my 3 other 8gb SDHC.
link: here
f.
M_T_M said:
This thread has been stickied by me in order to inform everybody about this situation.
Do report if you have gone through this problem only...no more thanks or OT chatter, please.
I'm in contact with the Mod team to investigate even further if this does affect any other devices as well.
Please be patient and do not pollute this thread
Cheers,
M_T_M
@jkoljo...thanks for your help on this very important matter.
Click to expand...
Click to collapse

Thanks
Thanks for the warning, yesterday I had considered to partition my SD ..

best would be to partition SD's via PC and to disable the partitioningfunction for the next update. I'd be bad if someone uses it again.

2-die-4 said:
best would be to partition SD's via PC and to disable the partitioningfunction for the next update. I'd be bad if someone uses it again.
Click to expand...
Click to collapse
Yep. I contacted Koush about this issue, so hopefully we get a fix (someone dare to try..? ) or it gets disabled.

I heard this from a customer so take this with a grain of salt but he told me he was an Android Developer and had heard of an interesting "trick" concerning all HTC Android phones.
These phones apparently have a SECONDARY bootloader that is completely hidden and disabled by default and that all those phones are HARDCODED to immediately enter into it the moment they get connected to a specific USB cable.
The guy was looking for the cheapest possible, well, item really, to buy and then proceed to cannibalize as a test to its' validity (he bought an old Motorola handsfree) so it seems he wasn't sure of it either.
Apparently what needs to be done is that the PLUG needs to be completely stripped and either two resistors or two capacitors (I forget which) of specific values need to be soldered to two specific lungs of the plug.
I am sorry I am being this vague but that was all the information I got from him in the matter of the couple of minutes it took him to buy the handsfree.
Perhaps there's sth to be looked into by some people better equipped than I?
EDIT: On second thought, it makes more sense if what he said was to solder A resistor/capacitor to TWO specific lugs of the plug, perhaps?
I kinda remember him saying that the plug itself doesn't even really need to lead to anywhere but it's more like the means to connecting the resistor/capacitor to those two lugs...
He also said that that's how HTC themselves un-brick bricked phones. He didn't appear to be talking just for Dev phones either.
I am sorry I really do not know any details.

How to deodex the Infuse?

Is there anyway to deodex the Infuse yet?

probably the same as a galaxy s. gtg465x posted one but we are haveing trouble getting a successful odin package to fix the phone when things go wrong so people were not willing to try it.

Thank you for the fast respond, are we gonna lose the phone if something goes wrong. or if something goes wrong is there a way to fix it.

sinan2010 said:
Thank you for the fast respond, are we gonna lose the phone if something goes wrong. or if something goes wrong is there a way to fix it.
Click to expand...
Click to collapse
well with samsung we are lucky enough to have odin which is a factory flash tool. unfortunately it is not working on the infuse 100%, there may be a new build of it just for the infuse but it hasnt been leaked yet as far as we know. there is also an opensource application called heimdall that works in place of odin. there has been some success with heimdall but the one user that restored with it is having random vibrate issues.
there are still things to figure out, but there is no reason you cant flash with cwm, there are just no proven roms or reliable methods to restore if it goes wrong.

Thanks again. I'll just wait since I'm not good in doing these kind of things.

Just to chime in, you can definitely softbrick the phone if you try to deodex the rom and something goes wrong. I know from experience (happened to me yesterday ) As far as I know, I'm the only one who has successfully flashed back to stock using h8rift's original test tar but now there's confusion about whether it's reliable or not due to other testers' experiences. We're gonna get there just hang tight.

beatblaster said:
Just to chime in, you can definitely softbrick the phone if you try to deodex the rom and something goes wrong. I know from experience (happened to me yesterday ) As far as I know, I'm the only one who has successfully flashed back to stock using h8rift's original test tar but now there's confusion about whether it's reliable or not due to other testers' experiences. We're gonna get there just hang tight.
Click to expand...
Click to collapse
So there are already some people brick their devices and good to know that you have successfully flashed it back.
I just have no idea how to do these kind of things this is my first Android device. I had HD2 and was so easy to do anything. I'm just afraid to brick my infuse, so I'll just wait
I just need to deodex it so I can be able to read and write in Arabic.
Thanks

Note radio messed up phone HELP!!

So earlier today i Dl'ed the new radio and its been down here from there.
I was able to get to odin before and i installed
http://forum.xda-developers.com/showthread.php?t=1601483
And i now cant use odin. I found from this thread what to do if i could get into odin (also cant get cwm)
http://forum.xda-developers.com/showthread.php?t=1611796
What should i do?

Does your phone work at all? It sounds like you might have bricked it using ODIN incorrectly. Did you leave "repartition" checked? If so, you shouldn't have.
Can you get into download mode at all? Does your PC recognize your phone? If you don't know what I'm talking about, you need to go to the "DEV" section and read all of the sticky threads, which you hopefully already did before you tried to do anything with your phone. Asking a bunch of questions about things you haven't taken the time to read about isn't going to help you at all.
Have you tried the "Odin Oneclick" leak"s" that have been released? They include ODIN in the install package.
You claim the Note radio flash derped your phone? It has been known to mess with phones but I haven't known of it bricking any phones. If so, have you tried to flash a different radio? You need to provide as much info as you can about what you did and read all of the threads that pertain to what it is you think you wanted to do. If you provide more acurate info, maybe someone can help (if you didn't brick your phone with ODIN). Good luck.

actually my phones all fixed now i did alot of research and fixed it
Thanks anyways
Correction im trying to get the lock screen/ power off menu solution thats all i need atm

Dwolf16 said:
actually my phones all fixed now i did alot of research and fixed it
Thanks anyways
Correction im trying to get the lock screen/ power off menu solution thats all i need atm
Click to expand...
Click to collapse
I'm happy to hear you are back up and running. I think the best thing to do is just stay away from the "Note" radio...its just not worth the risk.

scott14719 said:
I'm happy to hear you are back up and running. I think the best thing to do is just stay away from the "Note" radio...its just not worth the risk.
Click to expand...
Click to collapse
Are you sure you didn't mean to say "it's just note worth the risk. " XDDDDDDD
~PsyCl0ne
Sent from my SAMSUNG-SGH-I727 using XDA

its really not...im still trying to fix my homescreen and shutdown

I'm learning a hard lesson about the Note radio, too.

i just need to find some one with a full efs folder so i cant replace mine and ill be fine

I've updated my method, try again. If ur having write issues with efs, no guarantee that simply dropping it I'm with fix it. I think this new method will allow it to stick

Rom Question.

Okay,
I'm hoping that I'm posting this in the right place, since I'm new here, but here it goes.
I was wondering how to tell if I am able to use a rom. I know the obvious that it has to be for my phone, but what other important things (such as firmware) should I look at to make sure a rom is right for my phone. If there's a thread on this already, or if this is the wrong section please just point me in the right direction.

If the ROM is made for your phone, then it will work completely. If it was made for a phone in the same family of devices as yours, it may work fully or partially. For example, I have the LG P505. I can use any ROM made for the P505. I can use any ROM made for the P500 (which opens the doors to dozens of choices, from only a handful), but the screen driver is wrong, so the colors are messed up, and once the screen goes black, it doesn't come back (lol). To solve it, I have to flash a kernel made specifically for my phone (P505) after flashing the ROM.
If you have a flashable kernel .zip for your phone, you can use any ROM made for the whole family of devices of which your phone is a part.

Vinny Bacon said:
Okay,
I'm hoping that I'm posting this in the right place, since I'm new here, but here it goes.
I was wondering how to tell if I am able to use a rom. I know the obvious that it has to be for my phone, but what other important things (such as firmware) should I look at to make sure a rom is right for my phone. If there's a thread on this already, or if this is the wrong section please just point me in the right direction.
Click to expand...
Click to collapse
Just read the OP of the ROM thread (all of it; more than once). That's where you should find information on compatibility. If its in your device's section, its quite likely it will be compatible. But, you still need to read in case it requires a specific recovery, etc. to be flashed and work correctly.

Thanks for the replies! I've been having problems with boot loops and I was wondering if it was a compatibility issue. where would I get my hands on my phones kernel? I have an HTC sensation currently running sence-o-manic btw

Theonew said:
Just read the OP of the ROM thread (all of it; more than once). That's where you should find information on compatibility. If its in your device's section, its quite likely it will be compatible. But, you still need to read in case it requires a specific recovery, etc. to be flashed and work correctly.
Click to expand...
Click to collapse
I'm having trouble flashing ViperS. the op doesn't specify any procedures, but I get caught in a boot loop after going through the setup. not sure if I'm missing something or if i may have neglected to run a process that the op is assuming Ive completed. Needless to say, I'm completely lost lol.

Vinny Bacon said:
Thanks for the replies! I've been having problems with boot loops and I was wondering if it was a compatibility issue. where would I get my hands on my phones kernel? I have an HTC sensation currently running sence-o-manic btw
Click to expand...
Click to collapse
Vinny Bacon said:
I'm having trouble flashing ViperS. the op doesn't specify any procedures, but I get caught in a boot loop after going through the setup. not sure if I'm missing something or if i may have neglected to run a process that the op is assuming Ive completed. Needless to say, I'm completely lost lol.
Click to expand...
Click to collapse
Thanks for the replies! I've been having problems with boot loops and I was wondering if it was a compatibility issue. where would I get my hands on my phones kernel? I have an HTC sensation currently running sence-o-manic btw. I'm having trouble flashing ViperS. the op doesn't specify any procedures, but I get caught in a boot loop after going through the setup. not sure if I'm missing something or if i may have neglected to run a process that the op is assuming Ive completed. Needless to say, I'm completely lost lol.

Vinny Bacon said:
Thanks for the replies! I've been having problems with boot loops and I was wondering if it was a compatibility issue. where would I get my hands on my phones kernel? I have an HTC sensation currently running sence-o-manic btw. I'm having trouble flashing ViperS. the op doesn't specify any procedures, but I get caught in a boot loop after going through the setup. not sure if I'm missing something or if i may have neglected to run a process that the op is assuming Ive completed. Needless to say, I'm completely lost lol.
Click to expand...
Click to collapse
If you go to sensation forum instead of posting in general there will be A LOT more people there to help you.
Once you get there, read stickied thread by malybru called something like "great starting point for new sensation users" in Sensation general, and if you still have questions after that, go to Sensation Q&A , find another stickied thread called "Help Thread" and ask there.

Touchscreen not working after root, but S-Pen works fine

I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
Thanks,
Reffu

Hi,
same issue here. Today the touchscreen stopped working suddenly after i flashed the Android Revolution HD 5.0 Rom yesterday. However, the S-Pen is still working fine. Installing other ROMs and the Stock ROM via Odin did not help. Issue allso appears in Touch-enabled-Recovery.
I see no reason, why this should be a hardware issue, although my N8000 came back from service a few days ago, where they also replaced the screen and digitizer.
Had anyone this issue before and was abled to resolve it?
Greets

I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2

to read this as a Note 10.1 newbie is not very encouraging. are there any similar facts between all of you like
which Note model do you have
how did you jaibreak (which method)
which rom did you have before
which rom do you have now
how did you flash a new rom
...
is there a way to find out whether the touchscreen is really "dead for touch"?

This is a bit scary - my Note 10.1 is arriving today, and I plan to root it at a minimum. I actually don't mind Touchwiz all that much on my Note 2 (which is running CleanROM ACE), so I think I might just root the 10.1 for now.
So restoring completely back to stock (via Odin) doesn't fix it? That is really odd that ROM-ing this thing might cause a hardware failure...

jiggyman said:
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?

kkretch said:
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
Click to expand...
Click to collapse
Did anyone solve this, I'm having the same problem.

I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.

reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
Just curious - did you just root, or did you root and install a ROM?
I am only rooted so far - haven't felt the need to ROM yet - partially due to worries about this happening. I bought a refurb from Best Buy and only get 90 days of warranty.

reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
If they say you got a new one, you got one. They'll tell you otherwise if there's an issue over the phone.
But I wouldn't be afraid of ROMs, but to be more diligent and wise when it comes to choosing them. It's like choosing a poisonous mushroom versus an edible one to make stroganoff or stir fry. If you know what to avoid for the next time and follow the correct process to doing the root and flashing, there will not be an issues.
This is from someone who has soft-bricked my first tablet and learned how to unbrick my SIM-less Captivate and Note 10.1. It's how you apply the method and how much attention you practice not getting stuck into these situations is what matters. Especially since I bricked my tablet via experimentation and un-bricked it on the same day with ease.
It's not some big complex deal of rocket science or something only the mere geniuses can do, its how you perceive yourself and how you act. If you believe that you will suck and brick it to kingdom come , it will happen intentionally or subconsciously.
In this case, it was a freak accident where the file/s accessed and deleted the wrong files which allowed for capacitive touchscreen use, and it should be reported to x developers if you have not done so already.
I have rooted and used the Revolution HD rom, the Rom where you customize the colors of the bar/other things, and on the Captivate, the AOKP Collective. I further customized the latter with the Xperia launcher as it zips.

Did anyone find a repair for this besides replacement? My Note 2 is doing the same thing now.

Has anyone found a fix for the touch screen not working yet??
Anyone have any ideas?

Technicians input for touch problem
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain that follows the instructions on the mod sites exactly as shown step by step will never have a problem, all those that do end up with paper weights or bricks didn't follow the instructions in numerical order.
Believe it or not even if after you have modded a rom and brought it back to standard they know it has been modded as they have a list of problems associated with repairs after roms have been modded so you are only fooling yourself they don't.
Same as the smoker that tells his Dr he has given up even though all the symptoms prove he really didn't.
So in my expert opinion if you play with modding and stuff it up why should you be eligible for a warranty claim ? The manufacturer has sold you or supplied a working item that you decided to f_ck around with and because of your stupidity expect some one else to pay for it.
I am not saying don't mod your phone with all the great roms out there but please to save yourself a lot of pain and cost some poor smuck trying to run a business in these economic times a lot of out of pocket from sending items back for replacement or warranty plus the time it takes to do all the paperwork and such, please please please read the instructions 300% or triple check you are doing everything exactly as the instructions say and you will be enjoying all the new benefits of that customised rom and laughing at all the noobs stuffing up their brand new device from not doing so.
I know this won't fix your problem but reread that last bit it was your problem as you are to clever to follow some one else's instructions

anyone have solution regarding this issue, mine have issue also, can anyone spare how to fix it without changing hardware?
---------- Post added at 06:47 AM ---------- Previous post was at 06:28 AM ----------
i hope anyone can solve my issue with touch not responding

WOW.. on TOPIC Flashing .pit might help ???
Gardum said:
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain
Click to expand...
Click to collapse
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck

erica_renee said:
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
Click to expand...
Click to collapse
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir

popohunters said:
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
Click to expand...
Click to collapse
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .

erica_renee said:
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
Click to expand...
Click to collapse
thanks sir, im done the flashing with pit files+ official firmware but touch screen is still missing, is there a modem file for touch screen maybe i missed it while its in downloading process before i brick the touch screen

any hope out there?????
confused and need help
i have a n8000 , base band version N8000XXCLL1, my touch screen stoped responding while playing a game , only Spen works , tried resetting , but no help, I'm a no-voice when it comes to programing and need a step by step guide >>>> many thanks in advance for all your help

reffu said:
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
I got the same problem after rooting my phone.... I used the following method and got ride of that Problem. ..
type this star code in in it Phone dialler *#2663#
Now you should see "TSP"
<update>
TAP on TSP ......it will take 5 seconds only....
......
NOW ENJOY ☺☺
Click to expand...
Click to collapse