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

Root is anyone trying a work around for the bootloader

post what you need me to do and i'll test

Edit: you MUST have .Net framework 4 installed on your computer

http://forum.xda-developers.com/showthread.php?t=1512203
Follow the instructions from this thread above, BUT make sure you use the CWM image shabby made for THIS phone. Also, you do not need UDK nor the recovery from that phone.

Where it says this:

1. Run KDZ Updater from UPK with Windows Enabler on.
Select your KDZ file
.

Just replace that with following my unbrick guide, but stop at step 14.


Then follow the directions from the xda thread.

In step 8 from the xda thread, make sure you copy the address correctly!!! If you don't then you WILL be hard bricked.

Because of the differences between the Optimus Black and the LG Motion, I really do think mrpnut should try this since he has an extra phone...
 
http://forum.xda-developers.com/showthread.php?t=1512203
Follow the instructions from this thread above, BUT make sure you use the CWM image shabby made for THIS phone. Also, you do not need UDK nor the recovery from that phone.

Where it says this:

1. Run KDZ Updater from UPK with Windows Enabler on.
Select your KDZ file
.

Just replace that with following my unbrick guide, but stop at step 14.


Then follow the directions from the xda thread.

In step 8 from the xda thread, make sure you copy the address correctly!!! If you don't then you WILL be hard bricked.

Because of the differences between the Optimus Black and the LG Motion, I really do think mrpnut should try this since he has an extra phone...

Just read that thread. I'm with Ya I think someone with a test phone should try this first. It sure does look good on paper!:D
 
what are the chances of this working do you think?

There are 5 things that could happen:

1) You do everything successfully and it boots correctly and CWM actually works (I feel like this would be a miracle...)

2) You don't copy and paste the number correctly causing a perma-brick (hard-brick)

3) You do everything correctly and it boots correctly, but trying to load recovery gets you fastboot (that wouldn't be bad at all)

4) You do everything correctly, bootloader finds the replaced recovery right away and gives you a soft-brick.

5) You do everything correctly and it perma-bricks. (I wouldn't know if this was a problem with Shabby's recovery or if it would always perma-brick.)
 
There are 5 things that could happen:

1) You do everything successfully and it boots correctly and CWM actually works (I feel like this would be a miracle...)

2) You don't copy and paste the number correctly causing a perma-brick (hard-brick)

3) You do everything correctly and it boots correctly, but trying to load recovery gets you fastboot (that wouldn't be bad at all)

4) You do everything correctly, bootloader finds the replaced recovery right away and gives you a soft-brick.

5) You do everything correctly and it perma-bricks. (I wouldn't know if this was a problem with Shabby's recovery or if it would always perma-brick.)

I'll go with number 4
Or 2 is quite possible
 
There are 5 things that could happen:

1) You do everything successfully and it boots correctly and CWM actually works (I feel like this would be a miracle...)

2) You don't copy and paste the number correctly causing a perma-brick (hard-brick)

3) You do everything correctly and it boots correctly, but trying to load recovery gets you fastboot (that wouldn't be bad at all)

4) You do everything correctly, bootloader finds the replaced recovery right away and gives you a soft-brick.

5) You do everything correctly and it perma-bricks. (I wouldn't know if this was a problem with Shabby's recovery or if it would always perma-brick.)

fingers crossed. 1 or 3 daddy needs a new cwm
 
Back
Top Bottom