It is works similar to one click but you need a PC android sdk installed then you just double click on superboot windows oh and you Need to be in fastboot a cmd window will pop up and when your phone reboots you will be rooted.is that a simple method like 1 click or is it a more standard somewhat technical way?
Has anyone seen anything official from Google? Or is no news good news?
Sent from my Nexus One using XDA App
Is it safe to say that rooting is the only way to get rid of 33?
Chances are you wont, there's been a lot of leaked ROMs in the past and only a couple of them ever were released (AT&T and Voda build).
So it's safe to say that this update is authentic?
Sent from my Nexus One using XDA App
If it weren't authentic, it would not load successfully via the PASSIMG.ZIP method on a locked bootloader. Only signed ROMs can be applied that way.
But that's not to say this update is bug-free. If you're unrooted on FRF91 and your bootloader isn't unlocked, I would highly recommend this upgrade path instead:
1-Click Root -> ROM Manager -> flash ClockworkMod recovery -> full nandroid backup -> apply Paul's repacked version as an update.zip.
This will allow you a simple roll-back pathway (i.e. boot into custom recovery and restore the backup). If you upgrade via the PASSIMG method, then according to reports on this thread you lose all possible return pathways short of unlocking the bootloader.
cmstlist;8094893...I would highly recommend.. apply Paul's repacked version as an update.zip..[/QUOTE said:I recommend you also consider Geo's FRG33 version too. Being using it, SetCpu, plus WildMonks kernel for great results
http://xdaforums.com/showthread.php?t=714184
If it weren't authentic, it would not load successfully via the PASSIMG.ZIP method on a locked bootloader. Only signed ROMs can be applied that way.
But that's not to say this update is bug-free. If you're unrooted on FRF91 and your bootloader isn't unlocked, I would highly recommend this upgrade path instead:
1-Click Root -> ROM Manager -> flash ClockworkMod recovery -> full nandroid backup -> apply Paul's repacked version as an update.zip.
This will allow you a simple roll-back pathway (i.e. boot into custom recovery and restore the backup). If you upgrade via the PASSIMG method, then according to reports on this thread you lose all possible return pathways short of unlocking the bootloader.
This problem is compounded because afaik very few people flashed it and are now stuck with it and want to stay locked, like me. Since there isn't a lot of focus on it I'm not holding out too much hope for a fix. Stupid question - So the build.prop can't be modified and repackaged as a flashable zip in order to give us stock suckers access to our protected apps? Just curious