View Single Post
Old March 20th, 2010, 09:54 PM   #449 (permalink)
UBRocked
Rock--> YOU <--Hard place
 
UBRocked's Avatar
 
Join Date: Jan 2010
Location: Ohio
Posts: 3,982
 
Device(s): See my signature...this section isn't big enough anymore!
Thanks: 1,729
Thanked 1,521 Times in 810 Posts
ubrocked@gmail.com
Default

Quote:
Originally Posted by DroidSuks View Post
Thank god he didn't just release 505... they had some major issues with the first test run... would have created a panic with 80% of the people installing it. The been fixed for the most part. Quote below of description from a poster over at Cyan.

"Based on what happened last night, that would be a bad policy. It was a nightmare scenario where Rom manager was okay, but the update hosed recovery. If you wiped data when you installed the rom, but didn't get the Google apps installed before rebooting, you couldn't get into recovery and couldn't re-download RM. Would have been impossible for Koush to help people out of. I got lucky because I didn't wipe. Others got lucky because they installed both pkgs simultaneously. Since we were all communicating we could help each other through. If anyone had done it on their own, unless they got lucky, they'd have been hosed and needlessly afraid they'd bricked. Limited testing in a group environment is a good thing."


Hopefully everyone sticking with SPR gets the same update.zip love for 5.0.5 as was given with 5.4.2 / 3 .....
I for one used this as a learning experience...I'm should start a new thread on the subject so the "DroidMod" rooters who start flashing other roms without thinking or knowing the first thing about what they are doing will take second look at "okay, so what am I actually doing here?"...but I doubt I will...don't think it will do much good. I'll just get "you think your better than us" kinds of comments...like always when touching on that subject.

I got a copy of the test release on this (from secondary source that had informed me about the issues). Knowing what what was going to happen, I wanted to make sure I could fix it and learn what I needed to know. I haven't had to use adb to push a recovery image in a few months now... People would have been screwed if they didn't understand more than how do download a file and apply it as a update.zip in recovery. Really, really screwed! It took me about 30-45 minutes to fix the problems the ROM caused...AND I KNEW WHAT WAS GOING TO HAPPEN! The problems left you with no recovery (can't press 'x' while turning power on...nothing), no market (can't download a new ROM Manager), there was no file manager built into the system so you couldn't navigate to your SD card...what a nightmare to someone without a little knowledge about ADB (or maybe ADB never even being set up on their cpu).

But all the discussions I've had about ACTUALLY LEARNING about what your doing when you root...go over really badly!

Thankfully, Koush was wise enough to have a limited test release...The testers (most of them very knowledgeable) would have had problems...they wouldn't have been prepared for it...they would have been okay...but my guess is that it would have taken over a good part of their Saturday!
__________________
Myself: Galaxy Nexus, Droid 4, Transformer, Logitech Revue, Sony Blu-ray Player with Google TV
Wife and Kids: iPhone4, Apple iPad, Galaxy Player 4.0, B&N NookColor
Retired: Thunderbolt, Droid Pro, Fascinate, 2 Motorola Droids (the OG), Galaxy Tab (7" WiFi), Archos 70
UBRocked is offline  
Reply With Quote