Root [FAQ-GUIDE] ClockWorkMod Optimus Elite

[mysticalnyte]

In step 5 are you naming the file properly and do have the path correct?

If the path is not /sdcard (where your file is stored, then you need to change it) move the file out of any sub folders and to the root of the SD card

ie: NOT IN /sdcard/External_SD

dd if=/"path of file"/"name_of_file.bin" of=/dev/block/mmcblk0p14

Got it to work!

 

[DsyMnapTic]

Good, I'm glad it worked for you!

 

[Artine]

It works on the Sprint version. I know, because it's on my son's phone.

That's a second confirmation - thank you; updated the FAQ accordingly.

 

[Artine]

Significantly altered Prerequisite 11.

 

[ktb83]

Artine,

You can remove this:
(Guide note: You will get a low/empty/no space left on device warning. This is to be expected, continue onto step 6.)

That was related to a different command. I removed the step (zeroing out the recovery partition) which results in that output as it wasn't necessary being that the CWM BIN file is the exact same size as the partition.

 

[Artine]

Artine,

You can remove this:
(Guide note: You will get a low/empty/no space left on device warning. This is to be expected, continue onto step 6.)

That was related to a different command. I removed the step (zeroing out the recovery partition) which results in that output as it wasn't necessary being that the CWM BIN file is the exact same size as the partition.

Thanks for letting me know, FAQ updated accordingly!

 

[giantpune]

For 3.0.5, how to navigate, you can also use the 4 capacitative buttony things on the front of the phone. Home = up, menu = down, back = back.

 

[Artine]

For 3.0.5, how to navigate, you can also use the 4 capacitative buttony things on the front of the phone. Home = up, menu = down, back = back.

Thank you for applying functionality to them! FAQ updated.

 

[blizard]

I fallowed step by step and now i get
fastboot mode started :0 usb init ept @ 0x82000 fastboot_init() udc_start() anyone know how to fix this?

 

[LacWare]

Your going to have to access the phone with QPST and reboot it. Look at the guide to retrieve your MSL Code with QPST and it will set up the drivers and everything for you (I don't think you need to worry about all the permissions as your not going to be doing anything too crazy) once you get to the Memory Debug App section make sure it finds your phone and hit the "Reset Phone" button. If you need more clarification let me know that was just a simple run through.

What happened was the recovery either didn't flash or was corrupt. I'm not 100% sure but I'm pretty sure when I did it I typed the recovery file name wrong and didn't pay attention to the output therefor I (we?) ended up with an empty recovery partition.

 

[LacWare]

I rewrote the guide excluding anything you don't really need to worry, this should get anyone who runs into that issue back to there rom

Edit: Rewrote as a two part prerequisite and post error guide

Setting your phone in diag mode incase of disaster:

Start your phone normally and enable development under the applications menu
(Settings -> Applications -> Development -> Check all on page

Dial ##DATA# and click on Data Profile then edit.

That's all for the prerequisite



Rebooting to rom when stuck in fastboot:

Connecting to your android

Download: LGVM696.zip

Download the above archive and extract it to an easily accessible folder
Open all three included files, this will install the drivers required for windows to see your phone

Hold then entire Volume Up/Down rocker and plug in the USB cable. It should restart in "Download Mode"

Install QPST

Download: http://conflipper.com/Software/QPST_2.7_366.rar

Configuring QPST

From the start menu QPST- -> "QPST Configuration"
Remove any exsisting ports and click "Add new Port"
You should see a "COM # USB/QC Diagnostic" Select that and your phone should appear under "Active Phone"

Resetting your phone

Exit the Configuration and run QPST -> "Memory Debug App"
Hit the "Reset Phone" button and your phone should reboot normally


Be sure to flash a recovery on to it to avoid having to do this for every reboot

All credit goes to WhisperPntr, I just shortened the guide to be more specific to this situation

 

[LacWare]

I just realized unless you have already put your phone in diag mode this guide is irreverent if your stuck in fast boot then you can't access the rom to do that. Sorry little too much drinking last night didn't connect the right dots when I wrote that. If your phone is in diag mode already your good if not, it's beyond me.

Artine you may want to put something up warning people about this. If they set their phone in diag mode ahead of time then my guide will work (from the QPST program and on) so it's a good idea to turn that feature on and leave it on.

 

[Artine]

I just realized unless you have already put your phone in diag mode this guide is irreverent if your stuck in fast boot then you can't access the rom to do that. Sorry little too much drinking last night didn't connect the right dots when I wrote that. If your phone is in diag mode already your good if not, it's beyond me.

Artine you may want to put something up warning people about this. If they set their phone in diag mode ahead of time then my guide will work (from the QPST program and on) so it's a good idea to turn that feature on and leave it on.

Duly noted, adding shortly.

 

[DsyMnapTic]

About the Quickboot (reboot)....there's an option in titanium backup to reboot into recovery, can't we just use that?

 

[Artine]

About the Quickboot (reboot)....there's an option in titanium backup to reboot into recovery, can't we just use that?

I'm also aware that ROM ToolBox does the same thing. I'll be incorporating the previous update by LacWare as well as two more methods (respectfully Titantium Backup and ROM ToolBox being able to boot into recovery) before the next hour hits. Have to take care of a couple personal things quick though.

 

[DsyMnapTic]

I know this could potentially be a pain in the ass, but is there anyway we could include a change log with updated versions, so that we know exactly what has been improved?

 

[HackADevice]

Wait I already have cwm on the phone but what is the reason for these updated steps 3-5

 

[DsyMnapTic]

Wait I already have cwm on the phone but what is the reason for these updated steps 3-5

The new steps are for the updated versions of cwm

 

[DsyMnapTic]

I know this could potentially be a pain in the ass, but is there anyway we could include a change log with updated versions, so that we know exactly what has been improved?

Point made

Wait I already have cwm on the phone but what is the reason for these updated steps 3-5

 

[Artine]

There will be a changelog in place in the near future. As it stands now, I've edited this well over a hundred times (a LOT of formatting changes because I have an artist's mind and if something's slightly off in what I'm looking for in the format it bothers me ) already, so once the edits start winding down in frequency, I'll call it version 1.0 then and proceed to add a changelog.

In the mean time, I'll post what I've updated in the pages that follow - like these:

I've done a few background changes (as usual),
added in three more prerequisites,
updated the CWM procedures,
incorporated LacWare's guide for those who are stuck in fastboot (it is located under section 2.0, subsection b),
and added both Titanium Backup and ROM ToolBox to Method 1 under section 2.0, subsection a, as well as placing them in what is now prerequisite 11.

Soon I'll call it version 1.0 and start a changelog - probably even by the end of today, as I've got the guide/FAQ mostly to where I'd like it to be in terms of readability and formatting, although it is always open to suggestion!

 

[DsyMnapTic]

and thankyou so much for all this greatly helpfull info Artine , didn't mean to throw more on your plate than you could eat at the moment.....lol, my bad, just throwing the suggestion out there

Though I didn't leave out that fact that it might be a PITA

 

[Artine]

and thankyou so much for all this greatly helpfull info Artine , didn't mean to throw more on your plate than you could eat at the moment.....lol, my bad, just throwing the suggestion out there

Though I didn't leave out that fact that it might be a PITA

It would have been a PITA if I had started doing a changelog yesterday or when I started this FAQ, but fortunately that's no longer really the case. I have a pretty good idea as to how I want to add that in - including adding in the old CWM builds and their release dates so that people can check which version they have.

Also, I'm just glad to be doing this for everyone - it needed to be done We have a general thread, and an FAQ which compiles everything neatly (hopefully) in one post - being constantly updated as more information is available. Speaking of which, the x's next to section 3.2 and beyond (including sub-entries) are unanswered/unknown at the moment in case that was a little cryptic.

Also, the first part of Prerequisite 14 has been updated.

 

[giantpune]

Why is the msl is the list of prerequisites?

 

[ktb83]

I fallowed step by step and now i get
fastboot mode started :0 usb init ept @ 0x82000 fastboot_init() udc_start() anyone know how to fix this?

You could also probably just use fastboot.exe to flash CWM to the /recovery (mmcblk0p14) partition (with your phone connected to a PC). Unless you mistakenly wiped out your /boot (mmcblk0p9) partition. In that case you could use fastboot.exe to flash the boot.img back to the /boot partition.

You would need to have the Android SDK installed. fastboot.exe is in the same directory as adb.exe (platform-tools).

Does it go to Fastboot mode when you try to boot the phone normally or when you try to boot recovery or both?

Being stuck in Fastboot isn't the worst thing in the world.

 

[HackADevice]

where is the updated version and do i really need DIAG and msl or can i do it like the CWM before??