Gaming Console with Lollipop? Ouya Gets an Android TV Port

Android is a very flexible platform, and it can be used on a large variety of … more

Android App Review: Manage Your Connections Automagically – XDA TV

Material Design is all the buzz in the Android world right now. … more

Official TWRP Recovery Lands on Micromax Canvas Magnus

With the recent release of Android One, Micromax and MediaTek released fully buildable … more

Update Overload: SuperSU Heavily Updated

There are apps and apps out there. Very few can reach the level of popularity required to stay at … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

tale of a rooting gone terribly wrong

OP omnius1

19th April 2012, 03:31 AM   |  #1  
OP Senior Member
Thanks Meter: 157
 
385 posts
Join Date:Joined: Mar 2011
I can laugh about it now, but...

First let me say that I am new to rooting, but not to toys Here's my train wreck comedy of errors, maybe someone can tell me how all of this was even possible?

I started by rooting using Doomlord's rooting script. That went super-easy. Then I decided I wanted to do a nand backup, so following the instructions here I went and installed ROM manager and used it to flash Clockwork Recovery Mod. CWR wouldn't load when I tried to get to recovery mode to do my backup so I asked around and I discovered that my Atrix was not unlocked. It all goes downhill from there.

Following all the unlocking instructions in the Pudding sticky, I used RSDLite, and the IHOP sbf (since I'm on Bell Canada). Well that looked like it was working, but when RSD showed me at 100% reboot after it was all done, the program stopped showing any further status to say it was complete. I've seen this happen a lot before doing other smartphone activities, and I knew it wasn't going to proceed further. So after giving it another 10 minutes just in case, I unplugged from my PC. And yes, of course, now RSD protests that it wasn't done. Typical. I shut down my phone and rebooted. Time for the Fastboot stage.

(at this point I want to point out that BriefMobile's guide is wrong. you do NOT skip to instruction #13 if you are on gingerbread because that does not work. I ran into a couple of other people who reported the same problem with his guide)

(also at this point, I want to clarify that all my USB drivers needed for this to work were installed, and many of the links provided by Pudding sticky are out of date and don't work. or both so I had to get software from other sources and cross my fingers)

So, now onto the fast boot. But wait! Briefmobile guide (linked as the guide to use in Pudding sticky) never informed me I need to put my sim card back in now. or not. I decided since NO instruction is being given either way, I left it out. Fastboot works fine until I enter the "fastboot oem unlock ###" part. Then the cmd window showed zero progress. Once again I wait 20 minutes this time. Nothing. Finally I sigh "here we go again" and unplug, knowing I am now going to be soft bricked, and I was right. I am now showing "unlocked" at bootup, but I am also now stuck in the logo boot-loop. Tried to reflash, that didn't work. Tried to fastboot boot again, that didn't work.

Finally I caved in and did a factory reset/wipe. My phone is now restored to 2.3.6 but I am now also rooted and unlocked like I wanted to be when I started all of this.

The problem is that none of this went anything nearly as smooth as others claimed it would be. Every step of the way caused errors. RSD didnt work properly in the end, and neither did the fastboot. The instructions for Bell Atrix 2.3.6 are all extremely outdated and/or irrelevant in some cases. Before all this happened I was considering flashing custom ROMS. Now I am absolutely terrified to do so, and would rather just use TiBU to freeze some bloatware and leave it at that. How did this all go so terribly wrong? Are days like this normal in the custom ROM scene?
Last edited by omnius1; 19th April 2012 at 03:35 AM.
24th April 2012, 04:00 PM   |  #2  
OP Senior Member
Thanks Meter: 157
 
385 posts
Join Date:Joined: Mar 2011
no ideas anyone? I'm still baffled how my phone went through the train wreck that happened in the above post but still manages to be unlocked and rooted after the factory reset and 2.3.6 re-installed OTA. I still have root, and the phone is still unlocked.
25th April 2012, 05:04 AM   |  #3  
sheeparecurious's Avatar
Member
Thanks Meter: 17
 
76 posts
Join Date:Joined: Feb 2012
Quote:
Originally Posted by omnius1

Fastboot works fine until I enter the "fastboot oem unlock ###" part. Then the cmd window showed zero progress. Once again I wait 20 minutes this time. Nothing. Finally I sigh "here we go again" and unplug, knowing I am now going to be soft bricked, and I was right. I am now showing "unlocked" at bootup, but I am also now stuck in the logo boot-loop. Tried to reflash, that didn't work. Tried to fastboot boot again, that didn't work.

Finally I caved in and did a factory reset/wipe. My phone is now restored to 2.3.6 but I am now also rooted and unlocked like I wanted to be when I started all of this.

The problem is that none of this went anything nearly as smooth as others claimed it would be. Every step of the way caused errors. RSD didnt work properly in the end, and neither did the fastboot.


Yep, sounds a little like the night I had when I unlocked the bootloader. If it helps, I've done a little bit of rom flashing since and have had exactly zero problems there. (I'm not a new-rom-every-week kind of gal, just wanted something more functional than stock.)

So that SBF was known to cause a soft-brick; RSD Lite would predictably choke on itself and your phone would display "failed to boot" with a bunch of options. You enter the fastboot oem unlock command and keep going. My fastboot procedure went as advertised, but upon reboot it did stick for ~15 minutes on the startup screen and I had to do a battery pull. After that, up it came and everything was peachy.

Did you pull the battery and attempt another reboot before doing the factory reset? Just curious.
25th April 2012, 08:18 AM   |  #4  
OP Senior Member
Thanks Meter: 157
 
385 posts
Join Date:Joined: Mar 2011
Yeah, second battery pull was because both the phone and the PC cmd window became non responsive after I executed the final stage of the OEM unlock procedure.

The phone went into bootloop. Wouldn't reboot. Had to hard factory reset with the 3 finger salute
25th April 2012, 08:55 PM   |  #5  
sheeparecurious's Avatar
Member
Thanks Meter: 17
 
76 posts
Join Date:Joined: Feb 2012
Huh. Well, unlocking the bootloader also causes a factory reset, so in this case your end outcome was the same. Sorry it was such a pain in the meantime.

Seriously, though, that's the hardest part. Installing CWM recovery and other roms is a piece of cake, just do plenty of reading before changing anything.
26th April 2012, 09:07 AM   |  #6  
OP Senior Member
Thanks Meter: 157
 
385 posts
Join Date:Joined: Mar 2011
well looks like I got all the final kinks worked out. I froze all of my bloatware with TiBU including Motoblur Launcher and I'm now running my phone using Launcher 7. Everything's pretty zippy now and I think I may have just extended my phone as a keeper for the rest of this year
Last edited by omnius1; 26th April 2012 at 09:53 AM.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes