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

Root My first "brick", and I have the wrong laptop.

AshG

Member
Aug 10, 2010
82
24
This is turning into one of those days.

I decided it would be a nice idea to update to the .595 leak. I was toying around with LibertyGB 0.5 last night so I Bootstrap SBFed myself back to 2.3.340 and went from there. I was rolling and patting myself on the back for getting this process down and really commanding my phone. Then, my office phone rang. I made a mental note of where I was in the process and picked up where I left off (or so I thought). Phone boots to the white Moto logo (White? Uhoh.) for about 2 seconds then shuts off.

Long story short, I've missed a step somewhere and now I get to do an old fashioned hard-connection SBF. So I reach into my bag and grab my USB cable. Check. Reach into my bag and grab my Macbook. Check. Wait, Macbook? I grabbed the wrong laptop on the way out of the house. Gulp. Now instead of having a freshly SBFed and updated phone for the trip home, I have a paperweight to shore my coffee cup in place. :D

Moral of the story: Don't take phone calls while playing around in Recovery, even if you've done this 1000 times.

Moral of the story 2: Make sure you have an SBF-able laptop or desktop with you before starting potentially brick-making processes.
 
I got it working, then found a new wrinkle and got it working too.

Here's the process that I used to get from where I was to where I am now.

1. SBF to 340
2. Run Z4, install D2 Bootstrap, reboot.
3. Wipe Data three times, Cache three times.

Here's where it went wrong. I tried to install 595 straight up. I couldn't find anything that said you couldn't, so... I guess I was wrong.

4. Install the 588 Triple Zip, reboot
5. Install D2 Bootstrap, reboot.
6. Triple wipe both partitions (again, for good measure)
7. Install 595, reboot.

I ended up running into yet another hurdle - the "prerooted" 595 wasn't completely rooted, and Gingerbreak wasn't fixing it (i.e. SU was installed and logging permissions, notifications were popping up, but programs requiring root gave No Root warnings). That left me without TiBU to get things put back in place. On a hunch, I downloaded Busybox Installer. When I ran it, it said there was no Busybox installed. Shouldn't GingerBreak have installed that? I ran the program and installed the latest version and one reboot later TiBU worked like a charm. Everything is back in place and running as smooth as silk.

This should hold me for a week until its time to maderstcok back for the OTA. ;)
 
Upvote 0
your first mistake was using bootstrap to "SBF" you can't go to Gingerbread that way...you have to do a "full" SBF....

Not according to the TBH App. :) Their SBF-as-zip works quite well. Only had to do it the hard way because I made other mistakes.

Aggie, I didn't know TiBU had that functionality. Thanks for the heads up. I'm still learning the ropes with this OS.
 
Upvote 0
Not according to the TBH App. :) Their SBF-as-zip works quite well. Only had to do it the hard way because I made other mistakes.

No, actually it does not...their .zip functions exactly like maderstcok.zip does...and while both serve the same purpose as an actual SBF, for whatever reason those that attempted to update to the GB leaks after using such .zip files all had problems...

if you notice in the instructions for the Gingerbread leaks as posted by P3Droid himself they include SBFing by using RSD Lite not flashing the .zip files
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones