I have no doubt that this has been asked and answered, but I'm having a hard time finding it... hoping for a definitive answer!
I understand the process for getting to LibertyGB .05 from the Donate Toolbox.
My question is this:
I am currently on Froyo .340, Liberty 2.0.1. So would the very first step for me would be to get the leaked GB .588 installed and build from there using the Liberty v.04 file? Or do I need to get the Liberty v.01 file FIRST (through the toolbox, I'm assuming?) Or should I have the latest GB leak to start with (.595 or .596...?) Or none of the above? Also, once I get the leaked GB to start (if needed), do I then need to root my phone again before beginning the Liberty GB install?
And thanks Team liberty for all that you do!
I had this exact same setup. This is what you need to do. I got the instructions from another post, credit goes to mcp770 over on the thread
http://www.droidforums.net/forum/liberty-rom-dx/145785-how-do-i-go-2-01-lgb-0-5-a.html. I used this method and have had zero issues with LGB v0.5.
I would highly recommend to buy the donate toolbox with the rom manager. If you do that than you can update very easily.
My upgrade path: (have droid2bootstrap .apk on your sd)
1. Donated for the toolbox and downloaded Libery GB v.1 FULL via rom manager to my sd. Also downloaded GB v.5 (the one WITH the kernel update included) to sd.
2. Rebooted into clockwork and wiped data/cache/dalvik cache twice each
3. Chose install zip from SD and navigated to the Liberty download folder and ran the GB v.1 Zip
4. Let phone boot. First boot on GB takes a while and appears to bootloop. GIVE IT TIME.
5. I skipped login and went to files and installed the d2 bootstrapper and then booted into clockwork right away. ( saves time having to login and re-download toolbox right now)
6. Wipe data/cache/dalvik cache again
7. Install from sd and choose the liberty gb v.5 update.
Another long reboot and you are set...login and enjoy.
Hope this helps, I know it helped me.
Looking forward to the official LGB release, or a v0.6. So far I am not having any issues with v0.5.