From stock 2.0.1 >to> Sholes.info ROM..STEP BY STEP..NO ADB involved. NOOB CHALLENGE!

[Drrhoid]

Great guide, appreciate all the work you put into it.

[silenceforus]

Question: I did this to my gfs phone and she prefers the 2.0.1 multimedia dock rather than the new one. How do I get the old dock back up?

[Topsy]

Question: I did this to my gfs phone and she prefers the 2.0.1 multimedia dock rather than the new one. How do I get the old dock back up?

I believe you're looking for the Deskclock.apk from the original version. Be honest I don't even remember what it looked like, but someone should have it.

[cplus]

@silenceforus - boot into sprecovery and do steps 31-55 again. at step 55, make all of your selections being sure this time to uncheck '2.1 desk clock'. Then complete 56-58. It might seem redundant but that's how I'd do it. Nice work doing it all on your DROID btw!

[silenceforus]

Hey I did this an it didn't install the older clock and multimedia dock. Ill need someone to email me the older apks @ silence.v3@gmail.com

Thanks!

@silenceforus - boot into sprecovery and do steps 31-55 again. at step 55, make all of your selections being sure this time to uncheck '2.1 desk clock'. Then complete 56-58. It might seem redundant but that's how I'd do it. Nice work doing it all on your DROID btw!

[bL33d]

Thanks followed works great other keyboard lag??

[daddycat31]

So I got the 1.0.1 installed just fine but when I tried to install the 1.1 nothing happened... I moved the 1.0.1 ROM into a different folder so it's not in the SDcard root and I dropped the new 1.1 rom file in the root directory. I can go to install from SD card and find it there but when I click install it runs through the backup process and everything but at the end it just says "done" and nothing. It doesn't ask me if I want to wipe or keep my data. It doesn't ask me what applications I want to include (the list with the x's). I'm pretty sure I'm still running 1.0.1 because the manual brightness still does not work. I'm a totally newbee but that's the point of this thread "Noob Challenge", right? So any help would be amazing. THanks!

Same thing is happening to me when I tried to install it. Anyone have any ideas or know what the problem is??

Ok Oliver84...I downloaded Shole 1.1 rom at http://www.sholes.info/ and everything worked like a charm (I was trying to do 1.0 before)...

[Invader DJ]

Thanks so much for this great guide, I doubt I could have done this without it.

My set up process went fairly smoothly, I had a problem first with the recovery 0.99 download, the link was dead, and right clicking and selecting Save Link As made the image file, but it wasn't the real image. I found the correct version by going into the actual Sholes topic, there was a link there.

I also blanked out and skipped like half of the steps, but that was just me being stupid. I was able to easily go back and reenter everything.

My phone was also acting weird until I wiped /data and basically set it up as a new phone. My touch screen was really messed up and constantly shook and wouldn't register my finger. After that though, everything worked great. I haven't had a chance to do any in depth testing (I work a boring night shift so will get plenty of chances to test it out tonight) but so far everything works well. Speed wise, it seems maybe slightly faster, but about the same. Love the multi touch browser, it is really the thing that makes the custom ROM worthwhile.

This seems pretty idiot proof, people just have to make sure to carefully follow the directions. I copied the actual code into Notepad on my PC, just to make sure I was right on all the spacing and things like that.

[barcodelinux]

19. Type 'mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system'. (Again.)

This step is not needed because step 15, the /system partition is already mounted as rw. To confirm, just AFTER step 18 and BEFORE step 19, type:

mount

You will see that the /system partition is mounted as read/write. As proof, the user can not "dd, "chmod", or "sync" the /system partition if the partition is mounted as read-only. Although repeating step 15 at step 19 does no harm, it is redundant and potentially dangerous.

As long as the user types in the command correctly, there would be no issue. However, if the user mistypes the command, the user could end up with the /system partition mounted incorrectly and this could lead to a whole set of new problems. I believe that it is best to remove all chances of failure.

[cplus]

@barcodelinux - Step 19 has been officially omitted to reduce redundancy in the process.