[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 30/08/14 19:04, Migel Wimtore wrote: > And by the way, I always wipe cache and Dalvik after I update > cyanogenmod. It may even be necessary. > AND I use the "wipe to install new ROM", or some such named option, in > Phillz, before installing a new ROM. Awesome, loads more good advice from someone who has actually done this, several times by the sound of it. Just so you know, this is a standard Google Nexus 10 which is manufactured by Samsung, and is most definitely a tablet rather than a phone (although from the flashing standpoint, I don't imagine it makes any difference: it's just an Android device). Only took me a few moments to get back into recovery mode (using recovery-clockwork-6.0.4.7-manta.img, which is touch enabled like Phillz so nice and easy to use) and re-flash with cm-10.2.1-manta.zip which is the latest stable version from a couple of months back. To my surprise/annoyance, it has made absolutely zero difference and I'm still looking at a suspiciously identical cyanogenmod loading screen. I would have thought that the stable build particularly would have booted no problem, so I'm suspecting operator error. Your advice about forcibly wiping caches is jumping out at me, so this time I'll try Pillz and then the same stable image. I'm going to be really cross after all this if I end up getting a no-go on cyanogenmod, and have to reluctantly fall back to a stock google crapified version... This is actually more tricky than jailbreaking IOS devices, to my surprise. Thanks again, Cheers -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq