3711 replies to this topic

[ICS_THX_2_HOB]

That is a AP fast boot repair. This is in a boot loop.

My Bad!! Sorry about that.

[SamuriHL]

Ok I need to know what to do. Before HOB I would have just fire rsd lite up and reflash but I dont want to perma brick my phone. I used Titanium backup to move my user apps to sd card... went to fire up my mobile hotspot and would not turn on.... so I rebooted the phone. Now I am stuck with the boot loader.... phone will not start. Do I just plug back into AP mode and reinstall .247?

Factory reset.

Sent from my Xoom using Tapatalk 2

[KenDroid]

I'm not in the habit of looking in my spambox for verification emails, not sure why this one ended up in there, so I've been unable to post til now.

I tried many times to get a Blur.232 up and running but it kept failing for one reason or another. I live on the road and recently found HoB and my .232 came from elsewhere. -not surprising, it didn't work.

I finally read this entire post, and WOW is there a lot going on and a lot to look forward to.

By the time I got to yesterdays' posts, I concluded that I should just bite the bullet and go all the way, after all, my rooted .905 sucked and was almost unusable some days with all the data drops, GPS signal drops etc... and how is it that a phone works better as a game than it does as a damn phone? GOOD RIDDANCE .905! I'm pleased to say that .247 went flawlessly and faster than I expected.

Since I'm at home, I won't be using the phone as much and the real test starts when I jump in that 18 wheeler and hit the road, that's when I need and expect my phone to really work, I rely on it for everything!

Thank you very much Samurai and everyone else for putting this all together.

I fully endorse a short fuse concerning those that can't read (or refuse to) and follow instructions. You're actually nicer than I'd be.... colorful words abound!

[skass]

I tried the update today and it appears to work and then stop as follows:

"Found update: Blur_Version.5.9.905.XT875.Verizon.en.us"

"Looking for your phone... if this hangs, its not finding your phone

* daemon not running. starting it now *

* Daemon started successfully *

AFter this only have blinking cursor

[skass]

Also, I am now on 232 and USB is set to MTP and USB Debugging

[SamuriHL]

If only it told you what the problem was.....

[altspeed]

Just wanted to say i've never rooted a phone or done anything outside of accepting official updates prior to using HoB.

After reading the instructions and FAQ twice over I went through the process being careful to follow directions exactly and after 30 minutes am now enjoying ICS and root for the first time with absolutely no issues!

Thank you very much for providing such an easy to use tool.

Noob follows directions. Has successful experience. Film at 11:00.

[skass]

What is the problem?

[SamuriHL]

I tried the update today and it appears to work and then stop as follows:

"Found update: Blur_Version.5.9.905.XT875.Verizon.en.us"

"Looking for your phone... if this hangs, its not finding your phone

* daemon not running. starting it now *

* Daemon started successfully *

AFter this only have blinking cursor

What is the problem?

I'm guessing the fact that you don't want to read.

Q: Why doesn't ADB like my phone? (Daemon started, doing nothing else, "Looking for your phone...if this hangs, it's not finding your phone")
A: Check the following...ESPECIALLY after you just installed an update as things CAN get reset:

-Are you on USB 3.0?
-Do you have the latest Moto driver installed?
-Did you boot into AP Fastboot and allow Windows to install the ADB driver?
-Is the phone set to charge only or MTP mode?
-Is USB Debugging enabled?
-With the phone plugged in, try unchecking USB Debugging mode, wait a few seconds, then re-enable USB Debugging
-Are you using the original cable that came with your phone?
-Have you rebooted your phone and/or PC lately?
-Try unplugging the phone from USB for a few seconds and plugging it back in
-Try a different USB port

If none of that fixes it, chances are it's time to do a factory reset which will in fact erase the contents of your phone and reset you to a factory state. I like answering questions with more questions.

[Hikenit]

I'm guessing the fact that you don't want to read.

[/font][/color]

Ah man, I was just about to reply to his last post. I'm too slow.

[Killians]

skass, I had the same issue. I tried all those steps and it still didn't work for me. I select the CPU option and when it returned my CPU information, I figured it was at least finding my phone. I manually copied the file to my SD-EXT card, answered no to the copy prompt and everything went as expected from that point forward. I'm quite certain that it was operator error!

[King Howie]

I'm not in the habit of looking in my spambox for verification emails, not sure why this one ended up in there, so I've been unable to post til now.

Doh! Turns out mine has been in my spam box for a few days lol

[Dr4g0nf1y]

I just wanted to post a final Thank you to SamuriHL. I was able to get my phone moved to .247 with the manual method you posted way back. I had a medical issue and was unable to log back in until now to tell you that it worked and all was well. Thanks!!!

[SamuriHL]

I just wanted to post a final Thank you to SamuriHL. I was able to get my phone moved to .247 with the manual method you posted way back. I had a medical issue and was unable to log back in until now to tell you that it worked and all was well. Thanks!!!

Excellent. Just so you know that manual method is built into the latest House of Bionic. When you see me tell people to add a NORSD file to their House of Bionic directory, it's turning off RSD mode and switching to moto-fastboot which is what i had you do. Very glad it worked for you.

[SamuriHL]

skass, I had the same issue. I tried all those steps and it still didn't work for me. I select the CPU option and when it returned my CPU information, I figured it was at least finding my phone. I manually copied the file to my SD-EXT card, answered no to the copy prompt and everything went as expected from that point forward. I'm quite certain that it was operator error!

I would caution on the manually copying thing. It's fine. However, you may still want to verify the MD5 hash just to make sure that it was copied correctly.

[Killians]

Yes, absolutely yes on the MD5 check. Next step if I recall correctly after the transfer prompt. In no way would I have proceeded if that step failed.

[KenDroid]

I started FoxFi and got a popup that asked if I wanted wifi to automatically turn on and I selected NO. FoxFi failed to start wifi tether and I cannot for the life of me find where to reset that feature. I've gone through all wifi settings to no avail, uninstalled and reinstalled FoxFi and it still won't create a hotspot. Am I looking at a factory reset to get this thing working again or is there another way to fix this?

[SamuriHL]

No idea. You might want to post that in a more appropriate thread.

[KenDroid]

ok, I figured it had something to do with .247 since I've never seen that popup before (.902 and .905)

[csantarcangelo]

I started FoxFi and got a popup that asked if I wanted wifi to automatically turn on and I selected NO. FoxFi failed to start wifi tether and I cannot for the life of me find where to reset that feature. I've gone through all wifi settings to no avail, uninstalled and reinstalled FoxFi and it still won't create a hotspot. Am I looking at a factory reset to get this thing working again or is there another way to fix this?

No idea. You might want to post that in a more appropriate thread.

You don't need an app:

Please Login or Register to see this Hidden Content

This method has worked for me on .902, .905, and the .232, .244, and .247 ICS leaks. You basically need to turn off the provisioning verification and use the native settings to create a hotspot. Thanks to HoB not wiping your data, you don't lose the setting when you update to a newer version of ICS.

Or you could use Google and find this out for yourself next time. Not flaming, just sayin'.