I know the hardware shutdown, keep press the shut off button, then select the option to shutdown, and once it's done keep press the shut off button until the Apple is shown showing the restart. After some problem with last synchronization I attempted an hardware shutdown, but it never end, still have the the busy cycling cursor, yep still now. I tried attempt again the hardware shutdown but this has no effect. I suppose I could wait the battery is off but could get in end an dead ipad if that sort of bad event wasn't anticipated in ios design. I wonder if there is no other wait to stop this shutdown loop to see if the start loop could work.
Ha well ok I found on the net the way to really force shutdown in case the standard hardware shutdown doesn't work, keep press shut button and home middle button during about 10 seconds. Now let see if that dam ipad is starting now... EDIT: Ok it started now let see if a synchronize work. EDIT: Arg I have a real problem at last phase of synchronization, phase 6, there's a message about synchronizing photo and after a message the synchronization got a problem. That is smelling a lot linked to a previous anomaly I got when updating some application, and got iPad drive full over its expected capacity, looks like if I met an ugly ios bug.
Mmm I'm afraid now to attempt a restore with those synchronizations that didn't work. I finally succeed make my synchronization work by disabling photo synchronizing and after delete some pointless photo on the ipad and enabled again photo synchronization and it finally worked. I hope it is solved now and think there was something bad with photo I suppose that now that everything seems back to normal I should ensure a synchronization (that includes a backup) and then do a full restore from this last backup. This could reset some bad stuff that are possibly still resilient on my iPad. Well keep my fingers crossed but I'll wait the end of the WE to attempt it, I have some very important things to do this WE with my ipad like... playing some games. EDIT: And for the ios bug, I mentioned it because let an application update overload the drive over its capacity seems quite like an os bugs because its api managed by the os at the end.
