• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root How to go from first leak to second without sbf?

Status
Not open for further replies.
Vmanisme

Vmanisme

Android Enthusiast
Title pretty much describes it, i get the basic idea of how to do it but double checking wont hurt =)
 
you need to be on .340 froyo to install any of the GB releases. However if you do a backup of your current GB you can SBF to .340 then install the newest leak, after the first reboot reboot to CWR and do an advanced restore of data only from your GB backup. I have SBfing down to a science these days. It only takes about 10 minutes to sbf.
 
assuming you have a good nandroid of the stock Froyo, use CWR or Bootstrapper to go back to Froyo, then go to GB per instructions
 
quickaudi said:
assuming you have a good nandroid of the stock Froyo, use CWR or Bootstrapper to go back to Froyo, then go to GB per instructions
Click to expand...

from what i understand if he is on the first GB leak, you have to SBF back to Froyo...using a backup won't work...
 
There is no way to get to the new GB without going back to FroYo via SBF.

The hundred people who have tried to do it and posted here saying, "I'm bricked because I tried using maderstock, how do I fix it?" or "I'm bootlooping because I restored an old nandroid, how do I fix it?" or "I tried installing the GB leak over the old GB and now I'm bricked, what do I do?" will attest to this fact.

In order to get to the new Gingerbread, you must go back to FroYo via SBF. Period. There's a reason those were the instructions, and it ain't because TBH likes making things difficult. If there were an easy way to upgrade without SBF, those instructions would have been posted.
 
Is it at all possible for someone to put together a youtube video on how to go from rooted GB to the .588 new rooted deodoxed GB? Id greatly appreciate that.
 
OP simply put as you've seen is.

It is not possible to go from the first leak to the second without SBF'ing. so there is your answer.

i recommend a Mod close this thread now.
 
MiamiFin33 said:
Why would the thread need to be closed? Its now a resource for someone with the same question in the future.
Click to expand...



as in closed for additional comments. Not closed as in deleted. The op's question was answered. Its a cut and dry issue that was answered. No reason to risk people putting bad information in and possibly confusing people.
 
While the issue may currently be cut and dry, there could always be new developments/future information/questions.
 
Status
Not open for further replies.
Back
Top Bottom