Database Develop

[HOW TO] [ROOT] [S-OFF] Change boot logo (skateboards, not boot animation)

DISCLAIMER:
1) You are doing this at your own risk.
2) Educate yourself first and try this ONLY if you feel comfortable with modifying with your phone.
3) If you break your phone it is not my fault nor is it my responsibility to fix your phone.
Things could go wrong but they shouldn't if you follow the directions and have some general knowledge of Android.
##############################
Go from this:-------------------------------------------------To This:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
----------
##############################
Things needed:
ADB/Fastboot knowledge - HERE and HERE
RGB565Converter v0.3c - Thanks to DeToX-cz!
UPDATE: You must have the engineering bootloader flashed for access to splash1. Follow the steps here to flash the S=OFF bootloader. -Thanks to jcase
Instructions:
Find an or create an image (.png, .bmp, .jpg, or .gif -- 320x480 is preferrable)
Open RGB565 Converter
Ensure that "To RGB565 (binary)" tab is selected
Click "Open Image", select your image
Click "Convert to RGB565" (RGB565 Converter will make your image 320x480 if it is not already)
CLOSE RGB565 CONVERTER
Reboot phone into Fastboot using this command: adb reboot bootloader
OR Button combo: SEND/CALL + END/POWER
Flash image using this command: fastboot flash splash1 <your_image_name>.rgb565
Reboot phone using this command: fastboot reboot
OR fastboot oem powerdown if not then remove your battery
View the results of your hard work.
Enjoy!

As of right now there is no way to read the splash1 partition to back it up short of some kind of kernel mod to partition splash1 from NAND as a new MTD. At least that's how I understand it, please correct me if I'm wrong.
You must flash the S-OFF BOOTLOADER for this to work.
You can use the RGB565Converter tool to flash your image successfully without needing to type commands.
Below is another method used to keep your phone from rebooting unexpectedly during the process:
joshw0000 said:
I tried using the "Flash Splash1" button that someone had posted earlier and I almost **** myself. I think my phone tried to load the file I originally used to root it. I was getting really nervous so I pulled the battery and, to my relief, it powered on and it booted normally. I'm sure that method works but I'm scared of it now.
I tried the original instructions and it rebooted my phone before I was ready so I did this in the command prompt (this was mentioned on the first page of posts):
cd C:\android-sdk-windows\tools
adb shell
su
reboot bootloader
fastboot flash splash1 <copy and paste file name here>
fastboot reboot
Of course this will only work if you've downloaded the program, converted your picture and placed it in the tools directory of SDK.
Worked great for me. I couldn't be happier!
Click to expand...
Click to collapse

didnt seem to work for me, but im not rooted, ill try this with my brothers rooted phone in a bit and repioret back

Wow that worked great! Thanks

Reboot phone into Fastboot (Power down, hold Send press and hold Power)
Click to expand...
Click to collapse
How do you get into fastboot? I held the trackball down and power. Is that what you meant by hold "send press" and also does the image need to be on the root of the sdcard(Im guessing so...)?

ch4sethe5un said:
How do you get into fastboot? I held the trackball down and power. Is that what you meant by hold "send press" and also does the image need to be on the root of the sdcard(Im guessing so...)?
Click to expand...
Click to collapse
no, Hold Call button and end button to get into fastboot
and this is ONLY FOR ROOTED PHONES
thanks

thanks i will try it out. Im using ivan's 0.7

Ok so i figured out i needed to be in "fastboot usb" mode, but i searched and found that i had to type this command into the CommandPrompt
Code:
adb shell
su
reboot bootloader
then type in the command that was mentioned before, but make sure that the image is in the \tools dir in your android sdk install.

ch4sethe5un said:
Ok so i figured out i needed to be in "fastboot usb" mode, but i searched and found that i had to type this command into the CommandPrompt
Code:
adb shell
su
reboot bootloader
then type in the command that was mentioned before, but make sure that the image is in the \tools dir in your android sdk install.
Click to expand...
Click to collapse
^^^ This worked...But i have question after this how do you reboot?
I just did a battery pull But I'm sure there must be a command to reboot anyone know what it is?
and I used this Picture of an android with the letters ERIS in the center is anyone else want that instead of the droid one or something.

there should be an option to go to HBOOT menu and then into recovery and reboot from there.
I used this one:

Great tutorial. Thanks!
Here's mine if someone likes it they are free to use it.

+1 rep (if only we could do that). I was looking for something like this. Thanks!

t2noob said:
^^^ This worked...But i have question after this how do you reboot?
I just did a battery pull But I'm sure there must be a command to reboot anyone know what it is?
and I used this Picture of an android with the letters ERIS in the center is anyone else want that instead of the droid one or something.
Click to expand...
Click to collapse
I did a battery pull myself too lazy to go into recovery from hboot. My phone did not explode after doing a battery pull so it "should" be safe however do so with caution.

moved thread by request of OP.
Best regards,
Flar

Ive learned that battery pull is the easyiest way,

As a fan of FFXIII, I could not pass up the opportunity to do this.
[Taking Requests also ]

Maybe we should come up with a thread so people can post all boot images and animations in one place, no?
Just remember to convert it like mentioned in the first post
Here is one(as a fan =] ):

Was just thinking about changing and found this. Thanks.

Awesome!!!
Thanks for the tutorial.

Worked great!

Recovery Gone No ADB Please Help

I tried to flash the new recovery image for Amon- Ra and I have now lost my recovery image. I did see the thread giving instructions on possible fixes and it seemed to work for some, but I am having no luck, because I dont have access to install adb at my location.
On to my problem I am now not able to update any of my apps, and I was not able to un-root to start over. I have tried many different times through the console (terminal emulator) to reflash the proper image, but I have had no luck. So now i feel i screwed myself, because I was not able to get firerats script to work. Can anyone help me with this.
I have a Mytouch 3g I have stock radio and spl 8g cls 6 sd running superbad 1.3

crxforya said:
I tried to flash the new recovery image for Amon- Ra and I have now lost my recovery image. I did see the thread giving instructions on possible fixes and it seemed to work for some, but I am having no luck, because I dont have access to install adb at my location.
On to my problem I am now not able to update any of my apps, and I was not able to un-root to start over. I have tried many different times through the console (terminal emulator) to reflash the proper image, but I have had no luck. So now i feel i screwed myself, because I was not able to get firerats script to work. Can anyone help me with this.
I have a Mytouch 3g I have stock radio and spl 8g cls 6 sd running superbad 1.3
Click to expand...
Click to collapse
Sounds like you need to flash a good hardSPL in terminal and then with fastboot-usb, flash recovery.

Hard SPL
Do you know where I can find a good one. And doesnt it require me to have a working recovery in-order to flash the spl???
thanks for your response.

crxforya said:
Do you know where I can find a good one. And doesnt it require me to have a working recovery in-order to flash the spl???
thanks for your response.
Click to expand...
Click to collapse
Anything that can be flashed in recovery/console/terminal can be flashed (more safely, according to lbcoder, ezterry, etc) in fastboot-usb. So you want to use the .img file out of this zip and flash it in fastboot to the hboot partition. This spl is a recoded sapphire 2005 hboot, made to look like 2004 -- for DVT board 32As, but less risk of crossing wires with radio, AFAIK. The second one is just a straight-up 2009, which is pretty current. I assume you have a Sapphire MT3G, not a Magic MT3G (Fender/v1.2) because I wouldn't count on these files working for you. If you happen to have DangerSPL installed (although that's not necessary with MT3G) check the rooting/SPL instructions on that forum to make sure these files are right. Good luck!
NOTE: Here's a good Wiki on SAFELY flashing hboot/radio/recovery images that I found in Firerat's sig. As someone who has bricked a G1 by willy-nilly flashing, I implore you to have a look-see:
http://wiki.xda-developers.com/index.php?pagename=HTC_Dream_Bootloader

rynosaur said:
Anything that can be flashed in recovery/console/terminal can be flashed (more safely, according to lbcoder, ezterry, etc) in fastboot-usb. So you want to use the .img file out of this zip and flash it in fastboot to the hboot partition. This spl is a recoded sapphire 2005 hboot, made to look like 2004 -- for DVT board 32As, but less risk of crossing wires with radio, AFAIK. The second one is just a straight-up 2009, which is pretty current. I assume you have a Sapphire MT3G, not a Magic MT3G (Fender/v1.2) because I wouldn't count on these files working for you. If you happen to have DangerSPL installed (although that's not necessary with MT3G) check the rooting/SPL instructions on that forum to make sure these files are right. Good luck!
Click to expand...
Click to collapse
BUT, no adb , so chances are no fastboot..........
OP needs to get over the adb issue

Firerat said:
BUT, no adb , so chances are no fastboot..........
OP needs to get over the adb issue
Click to expand...
Click to collapse
Hmmm, I remember that way back in the day, JF included native ADB access in first custom RC30 Roms and then he packaged it into his custom recovery, but I don't know if losing a recovery image means losing ADB access and therefore fastboot access whatsoever?

Ill have to check
I have used adb before but Im not at my personal computer so I am not able to utilize the adb shell, and the computer that I am using, I do not have access to install. Is there another option that does not require adb, or is there a reason that I cant flash a sappimg file unroot, and start over???

crxforya said:
I have used adb before but Im not at my personal computer so I am not able to utilize the adb shell, and the computer that I am using, I do not have access to install. Is there another option that does not require adb, or is there a reason that I cant flash a sappimg file unroot, and start over???
Click to expand...
Click to collapse
No problem at all doing that, nbh overwrites radio, hboot, recovery. Just make sure you have the rooting files stored locally, i.e. custom rom, custom recovery, custom/hard/eng SPL, new radio, recovery test keys, etc.

crxforya said:
because I dont have access to install adb at my location.
Click to expand...
Click to collapse
rynosaur said:
Hmmm, I remember that way back in the day, JF included native ADB access in first custom RC30 Roms and then he packaged it into his custom recovery, but I don't know if losing a recovery image means losing ADB access and therefore fastboot access whatsoever?
Click to expand...
Click to collapse
did you read the post?
no adb = no fastboot
@crxforya'
your best bet is
Code:
su
ash
flash_image recovery /sdcard/recovery.img
if it fails, scroll up with track ball, and hit enter again, repeat until it works

crxforya said:
I tried to flash the new recovery image for Amon- Ra and I have now lost my recovery image. I did see the thread giving instructions on possible fixes and it seemed to work for some, but I am having no luck, because I dont have access to install adb at my location.
On to my problem I am now not able to update any of my apps, and I was not able to un-root to start over. I have tried many different times through the console (terminal emulator) to reflash the proper image, but I have had no luck. So now i feel i screwed myself, because I was not able to get firerats script to work. Can anyone help me with this.
I have a Mytouch 3g I have stock radio and spl 8g cls 6 sd running superbad 1.3
Click to expand...
Click to collapse
read this it might help it did for me when i try 2 use ROM MANAGER APP n i lost my recovery-->>> http://forum.cyanogenmod.com/index....toasted-not-bricked-phone-thread/page__st__40

No luck
Thanks for your help Firerat, It seems that everytime I hit enter to flash recovery it just gives me another command line. Ive done it about 30 times and doesnt appear that its gonna take. Do you know what I would need to do to unroot, and start over. I looked at the Unlockr website and the process with the NBH file looks like it works until i reboot and it is still 2.1. Any help there I really appreciate it.

ur recovery is corrupted try this
To boot into fastboot you need to hold back and power.
Then plug the original usb cable into your pc then into phone. your phone should say FASTBOOT USB
If not you will have to use USB deview (a few posts above). Then using it unistall anything that says Android or HTC or ADB or Fastboot... You get the idea.
Then unplug and replug the usb cable to your pc.
Windows should say that there is an unrecognised item or something, go into device manager and there should be one with an "!" mark, or a wizard to install the drivers appears.
When it asks you where to find drivers, click the option that says select where the drivers are (advanced), or something. Then point it to the folder were the USB drivers are and let it do its work.
After its finished start cmd and use the command "cd" to go to the tools folder where your sdk is extracted if it was at "C:\android-sdk-windows\tools" you would type in cmd "cd C:\android-sdk-windows\tools"
Then put in "fastboot devices" and it should give you your phones serial number, as long as the drivers work and you are in fastboot (phone should say FASTBOOT USB)
If that works we are back on track
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok now download the latest Amon_Ra recovery XDA link
Now check the md5 using this tiny standalone app Download.cnet.com link this is self explanatory, as the md5 sum is on the XDA link.
Ok, so now you have checked that its not corrupted, move the .img file to the tools folder. For me it would be "C:\android-sdk-windows\tools" . (The .img file needs to be where the fastboot.exe is, so it finds it.)
Now this is where you get the stuff you type in to cmd.
Fastboot devices
Fastboot erase recovery
Fastboot flash recovery recovery-RA-dream-v1.7.0.img
Click to expand...
Click to collapse

same problem
i have the same problem except i have danger spl, i noobed it up and tried to flash recovery with cm 5.0.7...
i tried to flash the recovery a bunch of times, and i treid to get into fastboot, but idk where the drivers are, and idk how to find them.
help plz

crxforya said:
Thanks for your help Firerat, It seems that everytime I hit enter to flash recovery it just gives me another command line. Ive done it about 30 times and doesnt appear that its gonna take. Do you know what I would need to do to unroot, and start over. I looked at the Unlockr website and the process with the NBH file looks like it works until i reboot and it is still 2.1. Any help there I really appreciate it.
Click to expand...
Click to collapse
ok, thats interesting
straight after you do that
logcat
<track ball> then c
( or in terminal preferences, change the control key )
I'm guessing you see
I/flash_image( 2410): header is the same, not flashing recovery
so, try flashing a different version ( 1.6.2 ) , then 1.7.0
edit: or
Code:
erase_image recovery
flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img

I need to start over
What does changing the control key do??? I know Im a noob!! Sorry and thanks for your help

Same problem here, on mt3g with latest super bad. I no longer have recovery and cant seem to flash one. And the latest amon-ra says not to flash from terminal if using latest cyanogenmod, yet my computer doesn't recognize my device, so I cant use adb.
-------------------------------------
Sent via the XDA Tapatalk App

Well im back at the out of memory messg
well after erasing recovery and trying to reflash on the 3rd time it gave me the out of memory error again. Now that script you made Fire do i just
su
sh firstboot.txt and your script will work???

crxforya said:
well after erasing recovery and trying to reflash on the 3rd time it gave me the out of memory error again. Now that script you made Fire do i just
su
sh firstboot.txt and your script will work???
Click to expand...
Click to collapse
well, I have a spaming script here
http://forum.cyanogenmod.com/index.php?/topic/3867-broke-recovery/page__view__findpost__p__39273
spamming the flash in CM5 seems to be working for most
Code:
#!/system/bin/sh
test=1
while [ "$test" = "1" ];do
flash_image recovery /sdcard/recovery.img
test=`echo $?`
done
echo "we got there in the end....."
[attachment=1106:spamflash.txt]
get that onto your sdcard
rename the recovery image to recovery.img and put on the sdcard
then
Code:
su
sh /sdcard/spamflash.txt
that will keep trying to flash until it works
another way is to flash before android starts ( plenty of free memory available )
this is a firstboot.sh script
Code:
flash_image recovery /data/recovery.img
if [ "$?" = "0" ];
then
rm /data/recovery.img
echo "recovery flashed"
else
echo "recovery flash failed..."
fi
[attachment=1107:firstboot.txt]
get that onto your sdcard
then
Code:
su
cp /sdcard/firstboot.txt /data/firstboot.sh
again rename the recovery image to recovery.img, but for this method you need to put it on /data/
It will 'self clean', i.e. if it works it will delete the recovery image, and the bit which runs the firstboot.sh deletes that ( but it will delete that regardless of it working or not )
Click to expand...
Click to collapse

deltawye said:
Same problem here, on mt3g with latest super bad. I no longer have recovery and cant seem to flash one. And the latest amon-ra says not to flash from terminal if using latest cyanogenmod, yet my computer doesn't recognize my device, so I cant use adb.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
When my phone does not recognize the USB connection I simply reboot my G1 while the USB is is still connected and that seems work for some odd reason.

I had the same problem. All I did was install rom manager, flash the rom manager recovery nothing. From there flash RA- recovery nothing and then did that back and fourth until it worked I also tried flashing it with one click root hope all help. Also tried the terminal. Hope you fine a way. Good luck!!!!!!!
-------------------------------------
Sent via the XDA Tapatalk App

help installing cm - too many different guides, any verified?

hi there,
so i am slightly new at this and have searched for hours and hours trying to find a consistent formula for rooting and installing my g1 to cyanogen mod 4.2 (or latest stable one, thus not cm 5). I seriously stayed up until 1am last night and now i am at work (started at 8) still searching.. I have used google, youtube, and several other cm sites. Basically the problem is there is not one guide and I am not sure if because I followed the CM wiki guide if i can switch because I am having problems with that one. So one question: does anyone know which is the latest and verifiably the best CM 4.latest guide to installing?
I am pretty sure i have rooted the phone because I successfully downgraded to RC29, the old school android OS. However when I try completing this guide: [cant put a URL in but the webpage title is: "G1 CM4.2 installation" and I already completed this wikiguide title: "Full Update Guide - G1/Dream Firmware to CyanogenMod" but it continues into the next page to install cm)
I get freaking stuck. I put all three files on my SD and when I try to push "Alt-A" there is not an option there for it, its not an option on my recovery mode menu. I tried putting the files back there after reformatting several times but still no 'alt-a' so I am stuck on step 5 because there is no option for step 5 on my recovery mode on the above web guide..
Does this mean I did not install something? should I try and install the ota radio, cm update, drc83 zip files separately (like load one on the sd card and install it, then reformat the sd card and then repeat with the other two files?) ? If so what order should I do that in??
Sorry I suck and have not been able to find these answers, there are just a plethora of guides and I am not confident in my modding to start deviating away from the wiki guide in case I brick my beautiful g1..
thanks so much, this has been a huge headache for me.. i literally spent 4 hours yesterday trying to get to this step.. aww...

At Step 5 select "apply any zip from sd" in Recovery.
Select "DRC83_base_defanged.zip" on your SD.
Press Home to confirm flashing.
Then select "update-cm-4.2.x-signed.zip" on your SD to flash CyanogenMod.
After everything is completed reboot your Phone normally.
Edit:
Here is the Link to the Tutorial.

zerocoolriddler said:
At Step 5 select "apply any zip from sd" in Recovery.
.
Click to expand...
Click to collapse
Yup you hit the nail on the head. Sorry I must not have been too clear on what was I was saying earlier. That is exactly the problem, you see I would select that in recovery mode, But "apply any zip from SD" is not there! Did I load some file wrong??
It only gives me:
Android system recovery utility
E: Can't open /cache/recovery/command
Home+Back - reboot system now
ALt+L - toggle log text display
Alt+S - apply sd:update.zip
Alt+W - wipe data/factory reset
could it be this: "E: Can't open /cache/recovery/command" that is the problem? I only found one reference to this message during my internet searches and the guy said it always says that..

So you have CM-Recovery?
Flash Amon_RA`s Recovery, it´s more comfortable to me. I´m using 1.6.2.
For G1: http://forum.xda-developers.com/showthread.php?t=566669
For MT3G(Magic 32b): http://forum.xda-developers.com/showpost.php?p=4029315&postcount=1

Nope. I am also using Flash Amon_RA's recovery.. (v1.6.2)
I loaded it up on the flash drive and also used telnet app to flash it in (wrong terminology? I typed it in the telnet box and hit return and it gave me the # # which I read means I did it right)

Try flashing again using fastboot.
Following Points should be listed:
1. Reboot system now
2. Go to console
3. USB-MS Toggle
4. Backup/Restore
5. Flash zip from sdcard
6. Wipe
7. Partition sdcard
8. Other
9. Power off
Install via Fastboot:
Copy recovery-RA-dream-v1.6.2.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.6.2.img

maybe i get something wrong
but did you boot into the recovery menu already? (press home and power when you turn the phone on)
from there you can choose your task with the trackball nice and easy...
(you r from vienna?)

zerocoolriddler said:
Try flashing again using fastboot.
Following Points should be listed:
1. Reboot system now
2. Go to console
3. USB-MS Toggle
4. Backup/Restore
5. Flash zip from sdcard
6. Wipe
7. Partition sdcard
8. Other
9. Power off
Install via Fastboot:
Copy recovery-RA-dream-v1.6.2.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.6.2.img
Click to expand...
Click to collapse
those points are not listed!
I did not try flashing via fastboot before but rather via terminal app.. Do I need some special software for fastbooting? Amon_RA's post says i need "Requires engineerings SPL!" which I do not have ..
and I now I loaded it via fastboot and I cant get out of it! how do I reboot out of fastboot? Because I can do not know how to "fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.6.2.img" .. can you explain that in more detail?
skarboy- no i am not from vienna but the USA. and yea I tried to boot from the recovery menu but when i am there it does not show the option of flashing zip from sd (see above)

You did not succesfully apply the recovery image then. Find amon_ra 1.6.2, rename it to recovery.img (make sure that you don't accidentally name it to recovery.img.img because of windows explorer on your computer). Put it on the root of your sdcard. From there, open the telnet app and type "su", then type "flash_image recovery /sdcard/recovery.img" power back on to recovery (home+power), and apply DRC83, CM4.2.15.1, and radio 2.22.23.02.

mejorguille said:
You did not succesfully apply the recovery image then. Find amon_ra 1.6.2, rename it to recovery.img (make sure that you don't accidentally name it to recovery.img.img because of windows explorer on your computer). Put it on the root of your sdcard. From there, open the telnet app and type "su", then type "flash_image recovery /sdcard/recovery.img" power back on to recovery (home+power), and apply DRC83, CM4.2.15.1, and radio 2.22.23.02.
Click to expand...
Click to collapse
oh okay. shoot.. I followed your instructions. do I hit return after typing 'su' in telnet? I did and then typed in the flash image stuff and hit return again. it gave me '##'
i am not rebooting in recovery.. hopefully it will work .
can i have all 4 files on the SD card at the same time? or should i erase it then load the DRC83, CM4.2.15.1, and radio 2.22.23.02 files??
also if i dont get the alt+a option should i just keep trying ??
EDIT: NOPE IT did not work, maybe I should just rename the file recovery, i looked under file properties last time but it didnt say it was hiding the file extension.. I am not quite sure what I am doing wrong.. if someone could show lead me through each individual step by step that would be swell.. of post a video (not outdated).
awwwwwww this is soo painful

austriker27 said:
oh okay. shoot.. I followed your instructions. do I hit return after typing 'su' in telnet? I did and then typed in the flash image stuff and hit return again. it gave me '##'
i am not rebooting in recovery.. hopefully it will work .
can i have all 4 files on the SD card at the same time? or should i erase it then load the DRC83, CM4.2.15.1, and radio 2.22.23.02 files??
also if i dont get the alt+a option should i just keep trying ??
EDIT: NOPE IT did not work, maybe I should just rename the file recovery, i looked under file properties last time but it didnt say it was hiding the file extension.. I am not quite sure what I am doing wrong.. if someone could show lead me through each individual step by step that would be swell.. of post a video (not outdated).
awwwwwww this is soo painful
Click to expand...
Click to collapse
First make sure you have all the files needed (recovery.img, DRC83_base_defrangled, CM4.2.15.1, and radio 2.22.23.02). Tell me if you are missing anything. Load them all up on your sdcard. Make sure that none of the files are in any folders. Next you are going to want to download the "terminal emulator" app from the market (by ZTA). Once downloaded, open the app and type "su" (enter). After that, type "flash_image recovery /sdcard/recovery.zip"(enter). Type "reboot recovery" (enter). If you do not see this image below, then something went wrong.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(note, that image shows 1.7 but you are going to want to install 1.6.2. v1.7 is for CM5-based roms)

okay, so after a much needed break of watching the US draw with England (world cup!!) i am back..
yes I have all of those files but my radio file is different (older?).. It is "ota-radio-2_22_19_26I".. should I have the radio file you mentioned? can you link it to me?
EDIT: Okay I found that file that you referenced and downloaded it. I will throw it in my sd card instead of the 26I because it sounds like it is a better radio flash..
also the 'radio', update cm, and DRC83 files are really zipped folders (.zip) that I have not extracted. Do I need to extract the contents into a folder and put the files from these extracted folders on the SD card root (so that there are ZERO folders on the sd? (no one mentioned this)
and so I use terminal emulator as opposed to telnet?? I was using telnet before because the CM wikiguide says so..

You don't need to unzip. They're zipped to flash via Recovery.
Flash the Recovery via Fastboot.
PS: It's called Terminal, not Telnet. ;-)

mejorguille said:
First make sure you have all the files needed (recovery.img, DRC83_base_defrangled, CM4.2.15.1, and radio 2.22.23.02). Tell me if you are missing anything. Load them all up on your sdcard. Make sure that none of the files are in any folders. Next you are going to want to download the "terminal emulator" app from the market (by ZTA). Once downloaded, open the app and type "su" (enter). After that, type "flash_image recovery /sdcard/recovery.zip"(enter). Type "reboot recovery" (enter). If you do not see this image below, then something went wrong.
(note, that image shows 1.7 but you are going to want to install 1.6.2. v1.7 is for CM5-based roms)
Click to expand...
Click to collapse
okay so I tried all that.. and freaking a! awwwwww no success it just gave me the old screen like before
when I typed in "su" it said permission denied so I think I have to go back and do something that I missed. I cant keep track of how many times I have done everything, then erased then tried again.. I wish someone would be specific and just walk me through this without skipping a single detail..

zerocoolriddler said:
You don't need to unzip. They're zipped to flash via Recovery.
Flash the Recovery via Fastboot.
PS: It's called Terminal, not Telnet. ;-)
Click to expand...
Click to collapse
this is exactly what i am talking about everyone is saying something different:
here is the CM site telling me to use telnet:
Open Android Telnet Client and type (include all spaces)
flash_image recovery /sdcard/recovery.img [enter]
If completed correctly you will simply see # # appear on your screen beneath the line you've just typed. If you get the "permission denied" message, type "su" (without quotes), press enter and repeat the previous step. If you get a file not found message, you may need to remount your sd card or make sure you typed the file name correctly.
Press Home key and proceed to next step

austriker27 said:
okay, so after a much needed break of watching the US draw with England (world cup!!) i am back..
yes I have all of those files but my radio file is different (older?).. It is "ota-radio-2_22_19_26I".. should I have the radio file you mentioned? can you link it to me?
EDIT: Okay I found that file that you referenced and downloaded it. I will throw it in my sd card instead of the 26I because it sounds like it is a better radio flash..
also the 'radio', update cm, and DRC83 files are really zipped folders (.zip) that I have not extracted. Do I need to extract the contents into a folder and put the files from these extracted folders on the SD card root (so that there are ZERO folders on the sd? (no one mentioned this)
and so I use terminal emulator as opposed to telnet?? I was using telnet before because the CM wikiguide says so..
Click to expand...
Click to collapse
the 2.22.23.02 radio is newer and its supposed to have better reception and less battery usage as compared to the .26I radio but the difference should be minimal. Everything is supposed to be in a zipped folder exept for the recovery image. Terminal is similar to telnet in that you can put in commands but it works a little different. It is what I usually use to flash recovery's, etc, so since telnet was not working for you I though terminal might make a difference.
Again, open terminal and type:
Code:
su(enter)
flash_image recovery /sdcard/recovery.img(enter)
reboot recovery(enter)
Tell me if this works.
Edit:look at my next post

austriker27 said:
this is exactly what i am talking about everyone is saying something different:
here is the CM site telling me to use telnet:
Open Android Telnet Client and type (include all spaces)
flash_image recovery /sdcard/recovery.img [enter]
If completed correctly you will simply see # # appear on your screen beneath the line you've just typed. If you get the "permission denied" message, type "su" (without quotes), press enter and repeat the previous step. If you get a file not found message, you may need to remount your sd card or make sure you typed the file name correctly.
Press Home key and proceed to next step
Click to expand...
Click to collapse
The "su" command signifies root access. If it says permission denied, then that means that you are not rooted or you skipped a step.
CYANOGEN WIKI said:
Rooting the phone
You need to have root (or 'admin') access to the phone so that you can install whatever software you want and not just what your provider gives you. This is not the same as unlocking your phone.
Finish booting up your phone, and sign-in to your Google account.
If you don't have access to a 3G network, then follow the G1 logon to google via wifi guide to sign-in via wifi. The original guide to do this is out of date.
You could try and add your networks provider's APN. To do this press Menu key -> APN Settings, press Menu again -> Add APN and enter 4 things: Name, MCC (Mobile Country Code), MNC Mobile Network Code and APN - all this info should be available here: http://en.wikipedia.org/wiki/Mobile_network_code and on your network provider's site. The image you booted with might also have the extensive APN list. If so, and you can't get a data connection, then you might try the wifi guide.
Once you're at the Home screen, open the keyboard, and press the Enter (Return) button twice.
Type
telnetd [enter]
Typing will bring up the Contacts screen, but you can just ignore that.
There will be no indication to let you know you did it right. Just continue on to the next step.
If you get an error when trying to connect (step 5), try pressing Enter twice and type "telnetd" and press Enter again
Open the Android Market, and install "Telnet" by ClockworkMod (Formerly by Koushik Dutta)
Open Android Telnet Client, enter "localhost" in the large text box and press connect. (You may have to enter "23" in the smaller text box on the right)
Click to expand...
Click to collapse
Do those steps again.

okay so I am in the telnet client and have entered localhost and 23 and hit return. so now i am in a black screen. i typed in what cm wikiguide told me and it gave me :
## (good sign!)
now do I turn off the phone and go into recovery mode or this where I am missing a step??
Sorry I am so ornery (wow and i can spell) there are just a number of things frustrating me.. besides me knowing this should only take like 2 hours at the most and knowing I keep messing up some mundane detail or something.. Also I am doing it in windows on my macbook and the wireless keeps disconnecting. Also I would take photos of the screens to show you but I do not have any photo software on the windows partition of my laptop (i mostly use mac os x) so I cannot... and i am very tired from working 6 days a week (and only getting 6 hours of sleep last night due to this issue) and frustrated from this whole fiasco.. And I have a headache.. yup call me a whiner if ya want but i am just trying to explain why i am kinda mad...

HALELUJAH! it worked and the android system recovery looks like your image mejor!!!!!!!! hopefully this works, i will let you know.. thanks soo much! i have no idea what i did differently

YESSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
wow so that wasnt a giant headache, although now i pretty have the process memorized and have learned tons in the process. I think I may have the longest time to root a g1 record so far of any human haha... Lets see I worked on it yesterday from 8pm-1am while kind of watching world cup. This morning for about 2 hours from 9-1130 at my job. And this afternoon for about 2 hours..So like 9 hours give or take an hour of two.. NEW RECORD!! haha
THANKS SO MUCH for you help guys I love you. Especially mejor because he/she lead me down the finishing stretch... Now to install apps2sd (after my class 6 card comes) and take a nap

[Q] Phone stuck on a loop

My phone is stuck on a loop after I tried fixing it. I tried installing Viper 6.2 on my m7 and it didn't work with an error of 7 or something and since I was coming from a different Rom I chose to wipe the data and start over. So now I have no Rom on my phone, no problem. I rebooted and tried to get into recovery again but then something weird happened where it would show the CW recovery logo and than skip to the Google logo like it was trying to boot up (no letters at top of screen). I tried installing a different recovery image but same thing it would show Teamwin logo and than cycle to the Google logo without letters at the top like it was trying to boot up and will go in a loop until I turn it off or go into the white bootloader menu. Also tried a factory reset from the white menu which did nothing. Please Help!

aznspdrmn said:
My phone is stuck on a loop after I tried fixing it. I tried installing Viper 6.2 on my m7 and it didn't work with an error of 7 or something and since I was coming from a different Rom I chose to wipe the data and start over. So now I have no Rom on my phone, no problem. I rebooted and tried to get into recovery again but then something weird happened where it would show the CW recovery logo and than skip to the Google logo like it was trying to boot up (no letters at top of screen). I tried installing a different recovery image but same thing it would show Teamwin logo and than cycle to the Google logo without letters at the top like it was trying to boot up and will go in a loop until I turn it off or go into the white bootloader menu. Also tried a factory reset from the white menu which did nothing. Please Help!
Click to expand...
Click to collapse
Try this procedure from alray:
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse

majmoz said:
Try this procedure from alray:
​
Click to expand...
Click to collapse
Yeah but the problem is I can't get to the recovery image anymore. the command says device not found and when trying to get to the recovery image it doesn't work.

aznspdrmn said:
Yeah but the problem is I can't get to the recovery image anymore. the command says device not found and when trying to get to the recovery image it doesn't work.
Click to expand...
Click to collapse
After you re-install the adb & fastboot disconnect your phone from the computer. Then reboot the computer and open the command window. Type: adb kill-server then when it is finished type: adb start-server. Now connect your phone to the PC. Type: adb devices

majmoz said:
After you re-install the adb & fastboot disconnect your phone from the computer. Then reboot the computer and open the command window. Type: adb kill-server then when it is finished type: adb start-server. Now connect your phone to the PC. Type: adb devices
Click to expand...
Click to collapse
ok when I do that it does nothing. The only menu I can get to on my phone is the bootloader one. If I choose recovery it'll get stuck in a loop and if I choose factory reset from the bootloader menu it'll get stuck in a loop. I think I need a way to factory reset the phone to any rom to get out of the loop. Right now I think the phone has a full recovery image on it but not a rom and that is somehow messing it up?

aznspdrmn said:
ok when I do that it does nothing. The only menu I can get to on my phone is the bootloader one. If I choose recovery it'll get stuck in a loop and if I choose factory reset from the bootloader menu it'll get stuck in a loop. I think I need a way to factory reset the phone to any rom to get out of the loop. Right now I think the phone has a full recovery image on it but not a rom and that is somehow messing it up?
Click to expand...
Click to collapse
If in setting USB Debugging is not enabled and there is an OS ADB will not work. It will work in Recovery.
If you have the stock firmware, you could flash it (if you are s-on, then you will need to relock your bootloader)
Then you would need to unlock your bootloader and flash a new recovery
ADB Push or sideload you rom while in recovery
Or
Flash a new recovery
ADB push or sideload your rom while in recovery

majmoz said:
If in setting USB Debugging is not enabled and there is an OS ADB will not work. It will work in Recovery.
If you have the stock firmware, you could flash it (if you are s-on, then you will need to relock your bootloader)
Then you would need to unlock your bootloader and flash a new recovery
ADB Push or sideload you rom while in recovery
Or
Flash a new recovery
ADB push or sideload your rom while in recovery
Click to expand...
Click to collapse
I've tried flashing a new recovery even changing the versions and types of recovery images. It still loops
Link to video of loop https://www.youtube.com/watch?v=efoXC-w45TA&list=UUXhWO2R4Ll4NrhM7M91T2sw
Fixed the issue by installing a RUU zip and then installing a custom rom.

aznspdrmn said:
I've tried flashing a new recovery even changing the versions and types of recovery images. It still loops
Link to video of loop https://www.youtube.com/watch?v=efoXC-w45TA&list=UUXhWO2R4Ll4NrhM7M91T2sw
Click to expand...
Click to collapse
It looks like your have an OS 3.09.401.1. I found a stock, non-rooted odex version.zip. This may wipe all of your personal data off of the phone. If fastboot is working, you should be able to flash it in FASTBOOT USB.
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_rom.zip
fastboot flash zip name_of_rom.zip
fastboot reboot
You have to run the flash command twice, the first time prepares the firmware/rom to accept the changes.

[Q&A] [PORT] Ubuntu Touch for LG L90 Dual

Q&A for [PORT] Ubuntu Touch for LG L90 Dual
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [PORT] Ubuntu Touch for LG L90 Dual. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Lg l90 405n
Hi, thank's for your efforts making Ubuntu touch working on our devices. Just tried to install your port to LG L90 405n (single card) and it perfectly works. Installation went smooth, no three restarts, no troubles at all, only it took some time to install rom, but again, installation did all itself, i had not to do anything.
After 10 minutes testing only one thing that distracts me - not working hardware keys.

keturidu said:
Hi, thank's for your efforts making Ubuntu touch working on our devices. Just tried to install your port to LG L90 405n (single card) and it perfectly works. Installation went smooth, no three restarts, no troubles at all, only it took some time to install rom, but again, installation did all itself, i had not to do anything.
After 10 minutes testing only one thing that distracts me - not working hardware keys.
Click to expand...
Click to collapse
Thank you for reporting - I've updated the thread! For 3 restarts, I don't understand why you don't experience it. It first need to restart to Ubuntu's recovery to push files, then restart again to install files, and finally into Ubuntu Touch. For hardware buttons, I think you don't need that. I remembered that Ubuntu Touch isn't designed for using with buttons.
Anyway, hope you enjoy new OS on your phone!

peat_psuwit said:
Thank you for reporting - I've updated the thread! For 3 restarts, I don't understand why you don't experience it. It first need to restart to Ubuntu's recovery to push files, then restart again to install files, and finally into Ubuntu Touch. For hardware buttons, I think you don't need that. I remembered that Ubuntu Touch isn't designed for using with buttons.
Anyway, hope you enjoy new OS on your phone!
Click to expand...
Click to collapse
Well, i really do!
After first reboot to fastboot and doing install magic itself, it boots to a responding recovery window (meanwhile in terminal install magic continues, so i just did nothing and it worked ), after that it boots to Ubuntu Touch. Guess, you're right and i just didn't notice 3 restarts.
Buttons are functional (maybe because i came from android and used to use it) - why to scroll to the top of window to go back, when you could just push "back" button?for me it's obligatory when browsing. so, if there is possibility to add "back" button functionality, it would be really nice. of course, i'm not pushing anything, i even don't know if it's possible.
After using for all day i have some reports (actually it's more "what to expect" for other users of Ubuntu Touch):
- 2 times in ~6 hours i lost mobile internet. i don't know what happened, only could guess, that it may be connected to changes between 2G and 3G. reboot cures a problem.
- changing wallpaper first time hanged up system (when trying to choose gallery). after reboot it let me choose a picture from gallery, but then again, choosing picture won't change anything.
- when i came back home, telephone won't connect to WiFi, i had to reboot then it connected automaticaly.
- battery works as expected and i didn't notice changes from cyanogenmod. maybe ubuntu is little more energy drainer. after 5 hours of using (all the time Wifi or 3G on, some surfing, some games playing, most of the time 100% brightness) drained about 35% of battery. I guess, it would be similar on cyanogenmod.
- i tested some camera stuff, but for now i really don't get the magic, how to use it. after clicking something, closing and opening app, i got working both cameras, but as i said, i'll need to test it more, because for now i couldn't tell, how to make use of both (front and rear) cameras.
- sd card works just fine.
some of things i missed in Ubuntu Touch (not related to this port for L90):
- no lithuanian keyboard layout
- no screenshot or screencasting app
- no call recording app
- no skype app
thanks again, peat_psuwit, for your great work!

How to install Ubuntu Touch after geting CWM
Sir i installed
adb
fastboot
ubuntu-device-flash
And phablet-tools
Without any problem.
After these commands I got CWM with ubuntu logo.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
adb shell su -c 'dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/boot bs=16 count=1'
adb reboot
sudo ubuntu-device-flash touch --channel ubuntu-touch/vivid-proposed --device generic --device-tarball device-w7.tar.xz --bootstrap --wipe
but after sometimes i got an error "Failed to enter Recovery".
What can i do?? Please replay any suggestions.
---------- Post added at 12:57 PM ---------- Previous post was at 12:17 PM ----------
After installing ubuntu Touch i Struck in fastboot.
I got Ubuntu Touch (CWM based) Recovery v6.0.4.6 After that i got an error Called
"failed to enter Reboot"
What can i do after that ???

Unknown Flag..
Nevermind, ran the apt get again with -f and its running fine.

latest update - no Ubuntu one login
I have tried again Ubuntu touch on L90 device. Same terrible battery drain (i know it's Ubuntu OS problem), 12 hours - >50 battery percent with practically no using, just enabled wifi.
Also, on previous release i had not problems with updating, now i could not update OS - "network error - please retry" while loging in to Ubuntu One.

Error while installing Ubuntu Touch on LG L90
I installed all the required files for flashing ubuntu touch on LG L90. I connected my mobile and Run these three commands:
1 : adb shell su -c 'dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/boot bs=16 count=1'
2 : adb reboot
3 : sudo ubuntu-device-flash touch --channel ubuntu-touch/devel-proposed/ubuntu --device generic --device-tarball device-w7.tar.xz --bootstrap --wipe
After the #rd command my phone show the cwm and rebooted automatically. Then the terminal said
Failed to enter Recovery
After that i got many partition of my mobile is mounted on my PC.
Then my mobile show the pink screen.
Is there any sollution for that???

kmvignesh said:
After that i got many partition of my mobile is mounted on my PC.
Then my mobile show the pink screen.
Click to expand...
Click to collapse
Let's first solve unbootable issue. Either your phone's critical partitions seems to be broken, or you forgot to flash unlocked bootloader. To fix this:
First get bootstack files from http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632. Choose boot stack for Kitkat. Make sure you choose correct file for your device or you may brick the device again. Extract the files.
Then, use instruction from http://forum.xda-developers.com/showthread.php?t=2582142. Just make sure you don't download any files from that topic. Instead, use files from extracted bootstack. Also, replace reference to openrecovery file to TWRP file.
When you reboot to recovery, copy compressed bootstack to device, and then use TWRP to flash that. This is optional, but I recommend this because I'm not sure if all the partitions are in good state.
Then, within TWRP, use first install instruction again.
kmvignesh said:
After the #rd command my phone show the cwm and rebooted automatically. Then the terminal said
Failed to enter Recovery
Click to expand...
Click to collapse
If you didn't forget to unlock bootloader, then I would need your full output from the Terminal to debug further.

So I was able to get it to boot on my d415 the way the instructions said I had it booted one way and wanted to test to see if the original issue was what I thought so I sent my device back to stock then rerooted et.(I found a work around to flash it a different way that worked and everything worked when I did it that way I had no issues other then front camera). when I finally flashed it using the instructions nothing worked that required my sim, sms failed, it wouldn't call etc. So i pressed restart and now my device is stuck on fastboot, I've tried reflashing it now I'm getting unable to flash errors again, I tried booting to recovery to try and restore android and use my work around but it just locks up and does nothing. any help would be greatly appreciated. any fastboot commands or anything.
one good thing did come out of this though I found an flashing error that comes from using twrp. I've read people having the unable to flash recovery error and the fix is as simple as booting into recovery(because the flash didn't work twrp should still be your recovery) install a rom boot into android and download flashify(for root users) then plug you device into your computer as MTP. unpack the tarball file and go to the partitions folder and copy recovery.img to your sdcard. Then flash it using flashify and reboot to recovery then just use "sudo ubuntu-device-flash touch --channel ubuntu-touch/devel-proposed/ubuntu --device generic --device-tarball device-w7.tar.xz --wipe" while your phones in the ubuntu recovery.

Hi! I can't seem to get past the recovery flash stage of the installation. I have tried disconnecting the usb and retrying many times. The last message my phone displays is flash:recovery
My LG L90 is the D405 version.

Antza2 said:
The last message my phone displays is flash:recovery
Click to expand...
Click to collapse
Only last message from the phone isn't enough. Could you please give me whole message from both phone screen and computer screen?

peat_psuwit said:
Only last message from the phone isn't enough. Could you please give me whole message from both phone screen and computer screen?
Click to expand...
Click to collapse
My computer:
2015/10/31 18:46:17 Device is |generic|
2015/10/31 18:46:19 Flashing version 338 from ubuntu-touch/devel-proposed/ubuntu channel and server (https): // system-image.ubuntu. com to device generic
can't flash recovery image
(i had to break the url link because of forum restrictions)
My phone:
[750] fastboot_init()
[850] USB init ept @ 0xfff9000
[870] udc_start()
[4990] -- reset --
[4990] -- portchange --
[5110] -- reset --
[5110] -- portchange --
[5290] fastboot: processing comands
[24440] fastboot: getvarartition-type:recovery
[24440] fastboot: getvar:max-download-size
[24470] fastboot: download:00c03800
[24860] fastboot flash:recovery

Antza2 said:
My phone:
[750] fastboot_init()
[850] USB init ept @ 0xfff9000
[870] udc_start()
[4990] -- reset --
[4990] -- portchange --
[5110] -- reset --
[5110] -- portchange --
[5290] fastboot: processing comands
[24440] fastboot: getvarartition-type:recovery
[24440] fastboot: getvar:max-download-size
[24470] fastboot: download:00c03800
[24860] fastboot flash:recovery
Click to expand...
Click to collapse
Well, if that's all message, then I don't know what happens. I recommend you to try re-plugging the USB chord and re-run the command again.

peat_psuwit said:
Well, if that's all message, then I don't know what happens. I recommend you to try re-plugging the USB chord and re-run the command again.
Click to expand...
Click to collapse
I did this about 20 times. Always the same result.

Would it be possible to create an update.zip on the SD card and flash the recovery by using the fastboot update command?
Edit: I tried flashing TWRP on my phone and i get this:
sudo fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (13644 KB)...
OKAY [ 0.439s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.441s
So apparently i can't flash any type of recovery image now. :/
I assume this is caused by the same problem that is preventing ubuntu from being flashed.
Edit2: It turns out no matter what fastboot command i use, the result is always: FAILED (remote: unknown command)
I can't even access the OEM device info.
Edit3: It seems that my bootloader wasn't unlocked after all. I think the download for D405 in the discussion op is not the correct aboot.bin, since the file in the zip is actually called abootb.bin.
Is there a way to insert the correct aboot.bin while in fastboot? i can't boot back to normal android.

thank you
Thanks a lot for your port. Installation went fairly easily for me. everything seems to be working for me so far.
again thanks.