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

4.2.2 is here for boost k2_cl

Ya I used lower case. Should I just unplug? I am afraid the bootloader may be jacked. But it never went passed ... On the cmd prompt.

To be safe, assuming it's still trying to process on the cmd window, I would wait at least 30 minutes and if nothing happens, pull the plug.
 
However, if the screen is blank after entering the command then that would just simply imply that your computer doesn't recognize your device. Which would mean it is safe to unplug it now.

Whenever I use adb or fastboot I always do adb devices and/or fastboot devices to insure there is a connection before running any other commands.
 
Before I get out of boot loader should I try to do anything? Ex: try to reinstall boot loader or something.

Yes I checked adb and fastboot with devices command. I got to think that I may not have stock recovery installed at thus point. Hopefully it never started doing anything. The ... With the blinking cursor has me worried though.
 
Yes I checked adb and fastboot with devices command. I got to think that I may not have stock recovery installed at thus point. Hopefully it never started doing anything. The ... With the blinking cursor has me worried though.

Always have your stock recovery before relocking the bootloader lol. Otherwise, you may get a watermark on your bootloader saying, security warning. You won't be screwed if that is the case as you aren't the first to do it lol, but it's not fun dealing with it.
 
Alright so fastboot boot recovery.IMG says booting but the phone never actually boots the recovery. Odgeek was having the same problem. Any ideas?

I never was able to "fastboot boot" TWRP. I finally gave up and did "fastboot flash recovery " Then it would boot from bootloader just fine.

However, I also discovered something odd...If you leave TWRP flashed to recovery, and you power off the handset, then plug it into the charger...It the phone would power itself on and boot to TWRP, only the touch screen would not respond...have to pull battery & unplug to reset...

Reflashed the recovery.img from the firmware.zip that is inside the 4.2.2 OTA update file, and now there is an on-screen battery meter that works when the handset is charging when powered off.

So, only way I could get TWRP to boot was to flash it to recovery.
 
I never was able to "fastboot boot" TWRP. I finally gave up and did "fastboot flash recovery <TWRP.img>" Then it would boot from bootloader just fine.

However, I also discovered something odd...If you leave TWRP flashed to recovery, and you power off the handset, then plug it into the charger...It the phone would power itself on and boot to TWRP, only the touch screen would not respond...have to pull battery & unplug to reset...

Reflashed the recovery from the firmware.zip that is inside the 4.2.2 OTA update file, and now there is an on-screen battery meter that works when the handset is charging when powered off.

So, only way I could get TWRP to boot was to flash it to recovery.

I noticed the TWRP booting automatically when the phone is off and plugged in thing myself. Quite annoying
 
Gonna have to check it out myself. I havent experienced it yet, but will see if I can duplicate the problem.
 
l
Gonna have to check it out myself. I havent experienced it yet, but will see if I can duplicate the problem.

Have you run the RUU on your handset? I did on mine, and I'm wondering if that is the difference on why mine doesn't "fastboot boot" an image anymore?

Also, what hboot version do you have? Could a different version of that explain this?
 
The bootloader is upgraded from 2.0 to 2.21. That is why the TWRP is having an issue. I'm gonna have to rebuild it from source with everything updated. Just that I am not currently by my computer right now.
 
If you are S-Off you can downgrade your bootloader and use the official TWRP just fine though.
 
Back
Top Bottom