Now what is this install.sh you're talking about? I've never heard of that or had to deal with that when flashing a recovery before (at least not that I remember)??
I haven't tried CWM on my N10 yet, but at least that's what was required for CWM to stick on the Nexus S (and also A510):
Am I right in thinking...
cd to the adb tools folder where the sdk is saved.
I need to unlock the boot loader via fastboot oem.
Then copy your file to the same directory on my Mac
Then type in the command line you suggested with the correct filename?
After that I will be rooted
Swype'd at pace from my Galaxy S2
I took the stock recovery.img from https://developers.google.com/androi...mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 188.8.131.52 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/show....php?t=1538053 )
|Thread Tools||Search this Thread|