Database Develop

flash_image: not found

I can't find the flash_image command in my android (i have just installed the lastest HTC_ADP_1.6_DRC83_rooted_base) so i cant install cyanogen 1.4 ... please any workaround or help will be very appreciated
Thanks in advanced
chineseman

You are going to be directed to ask this in the Q&A section.

chineseman said:
I can't find the flash_image command in my android (i have just installed the lastest HTC_ADP_1.6_DRC83_rooted_base) so i cant install cyanogen 1.4 ... please any workaround or help will be very appreciated
Thanks in advanced
chineseman
Click to expand...
Click to collapse
You just type it in terminal.

chineseman said:
I can't find the flash_image command in my android (i have just installed the lastest HTC_ADP_1.6_DRC83_rooted_base) so i cant install cyanogen 1.4 ... please any workaround or help will be very appreciated
Thanks in advanced
chineseman
Click to expand...
Click to collapse
Take it from someone who just spent last evening re-rooting their phone, reinstalling apps etc...I would get familiar with ADB. And fast:
http://forum.xda-developers.com/showthread.php?t=502010
From there, you can pretty much do whatever you need to the phone, and it's a LOT less hassle.

I've got the same problem,
I can't flash via adb shell, because flash_image is not found
using fastboot , i flash recovery img file, which doesn't give me errors
but I still don't get cm's recovery.
I'm stuck at the stock HTC ADP1.6 rom

sleepy_sanchez said:
I've got the same problem,
I can't flash via adb shell, because flash_image is not found
using fastboot , i flash recovery img file, which doesn't give me errors
but I still don't get cm's recovery.
I'm stuck at the stock HTC ADP1.6 rom
Click to expand...
Click to collapse
Did you read this thread?
http://forum.xda-developers.com/showthread.php?t=567943

can't get into recovery mode
B-man007 said:
Did you read this thread?
http://forum.xda-developers.com/showthread.php?t=567943
Click to expand...
Click to collapse
I just did. The problem was solved via fastboot, which I've tried. Itdoesn't give me errors and says writing 'recovery'.... OKAY, but I still don't get cm's recovery mode.

sleepy_sanchez said:
I just did. The problem was solved via fastboot, which I've tried. Itdoesn't give me errors and says writing 'recovery'.... OKAY, but I still don't get cm's recovery mode.
Click to expand...
Click to collapse
does your phone show up when you type
Code:
fastboot devices
?
EDIT: Also, try updating to cyan's latest build from the stock recovery
Alt-L
Alt-W
Alt-S
Make sure you rename cyans update to update.zip
then try updating the recovery from there
if that doesnt work, try
Code:
fastboot erase recovery
and then reflash the recovery

yes, I'm able to see the device in fastboot.
I am able to erase and flash the recovery and get no error, but I can't login to the cm's recovery. Actually for some reason, the first time I try to go to recovery, the phone ignores me and boots directly to android.
. I did try to update from stock recovery, however I get installation aborted error during the update
It turns out flash_image isn't available in htc's stock rom, so I copied it to /system/bin . What happens when I try to flash the recovery img the first time is like this: I get
mtd: erase failure at 0x002e0000 (I/O error)
mtd: erase failure at 0x002e0000 (I/O error)
mtd: skipping write block at 0x002e0000
the second time i get no messages.
if I try flash_image erase recovery, it says
can't find erase partition

Ok, found my answer after googling with some people who had similar problem in an unrelated forum
ah ... i think the problem is that the recovery is replaced with each reboot.
first do:
adb root
adb remount
adb shell
cat /system/etc/install-recovery.sh > /system/etc/install-recovery.sh.disabled
rm /system/etc/install-recovery.sh
cat /system/recovery-from-boot.p > /system/recovery-from-boot.p.disabled
rm /system/recovery-from-boot.p
Flash a recovery-image like before ... I would recommend this one (from cyanogen) - the one I'm using: http://n0rp.chemlab.org/android/cm-recovery-1.4.img
Click to expand...
Click to collapse
after this I was able flash and login to cm's recovery

sleepy_sanchez said:
Ok, found my answer after googling with some people who had similar problem in an unrelated forum
after this I was able flash and login to cm's recovery
Click to expand...
Click to collapse
Thanks for posting that. So the reason the stock recovery was flashed is because you booted on the 1.6 recovery instead of flashing cm right after, correct?

B-man007 said:
Did you read this thread?
http://forum.xda-developers.com/showthread.php?t=567943
Click to expand...
Click to collapse
Yes it did works!! my SPL was very outdated... then after update my SPL i could use fastboot!

@sleepy_sanchez you're my hero tried the whole day to get the cm recovery on my stock ADP1.6... thanks nandroid is back as well as my backup from 4.9.1.1

@ B-man007 yes after I flashed stock adp image, I couldn't flash cm's image immediately(since I had to rename htc's adp1.6 image to sth else and the cm's image to update.zip). my CM 1.2 recovery was overwritten somehow, or disappeared during the many times I tried to get my G1 working(wiping reinstalling htc's image) . and I couldn't flash CM 1.4 recovery neither using fastboot nor adb.

sleepy_sanchez said:
@ B-man007 yes after I flashed stock adp image, I couldn't flash cm's image immediately(since I had to rename htc's adp1.6 image to sth else and the cm's image to update.zip). my CM 1.2 recovery was overwritten somehow, or disappeared during the many times I tried to get my G1 working(wiping reinstalling htc's image) . and I couldn't flash CM 1.4 recovery neither using fastboot nor adb.
Click to expand...
Click to collapse
ahh ic. judging from the instructions you posted, it looks like the HTC recovery image has a script to replace the stock recovery upon each boot

I can't install recovery via fastboot, cos after ENTER this command:
fastboot flash recovery recovery.img my PC freezes.
So I wanted flash it via terminal, take a look at my log:
{
"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"
}
File is placed directly in /sdcard

ZduneX25 said:
I can't install recovery via fastboot, cos after ENTER this command:
fastboot flash recovery recovery.img my PC freezes.
So I wanted flash it via terminal, take a look at my log:
File is placed directly in /sdcard
Click to expand...
Click to collapse
Sorry for bump. I have the exact same problem as you. Anyone know the soloution?
Thanks

Do you have flash_image installed? Is flash_image executable? Is flash_image in your path?
Btw.: This is a G1 thread, not a Desire thread.

from those who display flash_image: not found
this works for me:
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
flash_image recovery /sdcard/nombre del recovery.img
(for me: recovery-RA-sapphire-v1.7.0G.img)
reboot recovery
and its done!

[Solved/Workaround] Boot with no boot screen. (console)

Is there a way to view the raw boot process in text mode instead of the boot animation?
Hoping there is a setting in a config file somewhere....
Edit: ([Solved/Workaround])
One easy solution is to install the paid app mentioned here. It shows you the logcat log as your phone boots.
A free kernel mod to accomplish this is still elusive.

For linux/grub this is accomplished by removing the 'quiet' and 'splash' options in /boot/grub/menu.lst
Also found a possible setting in /init.rc
export ANDROID_BOOTLOGO 1
Click to expand...
Click to collapse
However I cannot chmod this file to edit it even as root. / is mounted read-only
su
chmod u+w init.rc
chmod: init.rc: Read-only file system
Click to expand...
Click to collapse
Do I need to unpack + edit the file + repack boot.img and then flash(boot) it to achieve this?

britoso said:
For linux/grub this is accomplished by removing the 'quiet' and 'splash' options in /boot/grub/menu.lst
Also found a possible setting in /init.rc
However I cannot chmod this file to edit it even as root. / is mounted read-only
Do I need to unpack + edit the file + repack boot.img and then flash(boot) it to achieve this?
Click to expand...
Click to collapse
you need to mount /system as rw before you can chmod anything. SU file manager works well for this, and you can do it all on the phone, even the edits. Just don't forget to make a nandroid before you do any tweaks.
I know there is a way to disable the boot animation in the boot.img-kernel, i've seen it done before.

So you want a verbose boot mode?

uansari1 said:
So you want a verbose boot mode?
Click to expand...
Click to collapse
Yes.
SU file manager is not free.

followinginsanity said:
you need to mount /system as rw before you can chmod anything. SU file manager works well for this, and you can do it all on the phone, even the edits.
Click to expand...
Click to collapse
SU file manager can only mount /data and /system as RW, afaik / is a ramdisk image that is only modifiable if the change is made in a boot.img and flashed.

heh Just depends on where you need to make the changes Its what I used to do the build.prop mods to get navi working on the G1 back before they did the official update. Either way I do hope we can figure out how to disable the boot animation. Like I said I know its been done, and where the guy said he did the mod to do it. But thats only a start. Also I know the emulator has a command so that you can boot it without the animation but thats the emu, not the actual device.

Heres where I am now:
The first X comes from initlogo.rle in the root directory of the bootimage.
The next image is the boot logo. This is a set of two images in framework-res.apk/assets/images.
{
"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"
}
If a bootanimation.zip is found in /data/local or system/media, it is shown next. This is the nexus boot animation.
I tried renaming bootanimation.zip...the boot logo images were shown instead.
I removed the boot logo images from framework-res.apk...got a blank black screen until the lock screen appeared.
Also tried editing pushing a modified init.rc with these commands, didnt help the original init.rc was restored on reboot.
Code:
adb shell mount -o remount,rw rootfs /
adb pull init.rc .
#edit the file.
adb push init.rc /
adb shell sync
adb reboot
Found some instructions on how to edit the boot image:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Thinking of setting up ubuntu in a virtualbox to try this. (Goal is to turn set ANDROID_BOOTLOGO 0 in init.rc). Dont know if this will let us see the verbose boot log or not...
Update:
Tried this. the 2.5MB boot.img splits up into two pieces (ramdisk and kernel), totaling 2MB (?), flashing an updated 2MB boot.img gets the phone stuck on the initial x. ... Something is missing.

heh this is what I want (not the phone)
http://www.youtube.com/watch?v=5yO2KQHkt4A#t=1m44s

Re: Boot with no boot screen? (console)
I noticed there is a /system/bin/bootanimation. I ran it from terminal and the animation played. I couldn't exit it and had to take the battery out to reboot. It took over my screen and disabled all the buttons.
If you removed the images and still had a black screen, I wonder if this program was running but was black because the images were gone. Maybe renaming it would keep it from running and do what you want?
I tried to "cat" it but it's a binary. There was some garbled text toward the end which said "boot animation disabled" and gave some file locations etc. May be some clues there.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

fubaya said:
I noticed there is a /system/bin/bootanimation. Maybe renaming it would keep it from running and do what you want?
Click to expand...
Click to collapse
Tried this.
adb -d shell mv /system/bin/bootanimation /system/bin/bootanimation1
It booted ok and I got a black screen in place of the boot animation, went straight to the lock screen.
Didnt get the console text though

sorry, cant contribute. but id love to have this as well.

Well where are all the Kernel hackers when you need em
Told by someone pretty intelligent that the Kernel will basically need to be compiled to enable the console framebuffer option and maybe remove references to the boot animations etc. I'd love something like this though, wish I knew more about implementing it.

I can contribute a little bit.
Go over to the Dev section, see the "update.zip creation" thread. There are instructions for creating a boot image:
http://forum.xda-developers.com/showthread.php?t=667923
In these instructions, you'll notice an interesting switch for kernel to execute with:
--cmdline 'no_console_suspend=1 console=null'
I believe that might lead you to where you're trying to get

Jack_R1 said:
I can contribute a little bit.
Go over to the Dev section, see the "update.zip creation" thread. There are instructions for creating a boot image:
http://forum.xda-developers.com/showthread.php?t=667923
In these instructions, you'll notice an interesting switch for kernel to execute with:
--cmdline 'no_console_suspend=1 console=null'
I believe that might lead you to where you're trying to get
Click to expand...
Click to collapse
I tried that, the new boot.img I create does not work, see post #8

what did you define as console?

Jack_R1 said:
what did you define as console?
Click to expand...
Click to collapse
What you posted, and also tried the command that was in my boot.img (cyanogenmod)

Re: Boot with no boot screen? (console)
i would love this!
unfortunately i did the same things eg move bootanimation.zip bootanimation script etc.
only got a black screen.
we could build a bootanimation.zip with text images... lol
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

leonnib4 said:
we could build a bootanimation.zip with text images... lol
Click to expand...
Click to collapse
There is one out there, but I prefer the real thing.
We need help from one of the kernel masters!

britoso said:
What you posted, and also tried the command that was in my boot.img (cyanogenmod)
Click to expand...
Click to collapse
But I posted the default command, and marked it in red to say - if you're making a boot image with default command line, you're actually redirecting the console to null, so what do you expect to see?!
First, try eliminating redirection, the default might work. Remove the "console=null" from the line and rebuild the boot image.
In case it still won't work - try to change it to "console=tty", "console=ttyS0" or something like that.

[Obsolete] [ROM] Stock 3.2.78 firmware rooted on squashfs/ext4 for SDE enabled Gen9

Hi All,
Here is rooted 3.2.78 firmware for SDE enabled devices.
I did two versions:
- squashfs (like my previous build), in this one, system is read-only, you can't add/remove stock apps and edit system files. Files are compressed so it takes less storage space than ext4, it should be also slower than ext4.
- ext4, system is read/write and should be quicker. Be careful if you modify system files though.
Both have kernel/modules from 3.2.78.
To install it:
0) You must have SDE installed. If you didn't do it already, check there instructions on how to do it.
1) Extract zip file content
2) Copy android_3.2.78.squashfs (or android_3.2.78.ext4) to internal storage root. You can do it the usual way or with adb with this:
Code:
adb push android_3.2.78.squashfs /data/media
or
Code:
adb push android_3.2.78.ext4 /data/media
3) Reboot
4) On boot menu, select "Recovery system"
{
"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"
}
5) Select "developer edition menu"
6) Select "flash kernel and initramfs"
6) A drive should appear on your PC, copy zImage and initramfs.cpio.gz to it.
7) Select OK, the kernel should flash.
8) Select OK to reboot and maintain vol+ pressed. Boot menu should appear after reboot.
9) Select SDE in boot menu, you should be rooted and SuperUser functional.
The only change from stock: I enabled vibrator control panel option, it has been reported to work on some, it doesn't on mine.
I checked 3.2.78 stock firmware, it has an updated bootloader, it may be worth flashing stock firmware too to have everything synched.
Download rooted 3.2.78 on squashfs here.
Download rooted 3.2.78 on ext4 here.
Cheers,
LeTama

great thank you
gonna flash it as soon as its downloaded
btw do i have to do any special things to flash the ext4 ?

Ok...good job....!!!
I understand now why I did not have options rw in root-explorer....because I managed the Rom with squashfs and not with ext4.....
Now everything is ok....thanks again @letama...

No, nothing special for ext4, same thing as squashfs...

letama said:
No, nothing special for ext4, same thing as squashfs...
Click to expand...
Click to collapse
Are you saying that installing with ext4 partition I'll can't be mount RW in root_explorer ?
-because with squashfs I can't ....

surdu_petru said:
Are you saying that installing with ext4 partition I'll can't be mount RW in root_explorer ?
-because with squashfs I can't ....
Click to expand...
Click to collapse
no i think he answered my question from above

surdu_petru said:
Are you saying that installing with ext4 partition I'll can't be mount RW in root_explorer ?
-because with squashfs I can't ....
Click to expand...
Click to collapse
No, sorry, our posts crossed, I was effectively replying to djnilse. I'm trying to refrain my "quote mania", it was not a good idea this time
Ext4 is R/W, and permanently, no need to remount it in root explorer.
I would have preferred ext4 mounted first as r/o and allow the option to remount as r/w when needed, but this is not possible with the way Archos designed their rootfs.

Hi Letama,
Thanks for your build but I cant use your kernel with 3.2.78 kernel modules and when I extract kernel from 3.2.78, init kernel does not boot :/.
Thanks in advance
Thaolia

ok i flashed it everything worked fine
i have now a dualboot recovery menu with Android(non-root) and developer(root)
on developer the root is ok, also the system is r/w
thx letama for the rooted newest update

As a question to get out of the way early in the thread, I'm on your earlier rooted one, do I need to wipe?
Sent from my HTC Desire HD using xda premium

Tha0lia said:
Hi Letama,
Thanks for your build but I cant use your kernel with 3.2.78 kernel modules and when I extract kernel from 3.2.78, init kernel does not boot :/.
Thanks in advance
Thaolia
Click to expand...
Click to collapse
Archos kernel is using a new compression scheme for initrd, check my howto, the "find . | cpio ..." command. You need to rebuild your initrd.

Quinny899 said:
As a question to get out of the way early in the thread, I'm on your earlier rooted one, do I need to wipe?
Click to expand...
Click to collapse
I don't think so, Archos firmware update doesn't, so it shouldn't be necessary.
I had to wipe mine for another reason so I can't be sure though.

letama said:
Archos kernel is using a new compression scheme for initrd, check my howto, the "find . | cpio ..." command. You need to rebuild your initrd.
Click to expand...
Click to collapse
My extract kernel is of 5Mb (I use your howto for extract the 3.2.78 kernel). Init and recovery extract kernel doesn't boot with a lzop initramfs.cpio. Wheras with your kernel and modules, all works fine.
Sry but I certainly forget somethings.
Thanks in advance
Thaolia

Tha0lia,
5 MB is wrong:
- aos-unpack gives you 9_MMCF (5145304)
- dd strips header and gives you init_kernel which contains zImage+initrd (5145040)
- aos-kernel-unpack of init_kernel gives you kernel and initrd separated (unpacked-kernel, unpacked-cpio.gz), that I renamed to init-zImage afterwards.
This is the one you want, size should be 3993572.
Cheers,
LeTama

Noticed an issue in the first post:
adb cp should read
adb push
Sent from my ARCHOS 80G9 using xda premium

Quinny899 said:
Noticed an issue in the first post:
adb cp should read
adb push
Click to expand...
Click to collapse
Thanks! I shouldn't post when I'm in a hurry . First post fixed.

letama said:
Tha0lia,
5 MB is wrong:
- aos-unpack gives you 9_MMCF (5145304)
- dd strips header and gives you init_kernel which contains zImage+initrd (5145040)
- aos-kernel-unpack of init_kernel gives you kernel and initrd separated (unpacked-kernel, unpacked-cpio.gz), that I renamed to init-zImage afterwards.
This is the one you want, size should be 3993572.
Cheers,
LeTama
Click to expand...
Click to collapse
Sorry, your kernel and my extract kernel have same md5sum.
It's my fault but thanks for your help.
Have a nice day !
Thaolia

For the Buzz in FRANCE
http://www.jbmm.fr/?p=25015
(ps : je recherche des rédacteurs "techniques" pour jbmm - envoyez un MP)

Is it possible to get swap working in the build modifications?
When I use swapper for root from the market, reboot and type free, I get this:
It shows it as empty and unused. Any idea why? There's a swapfile on /sdcard, in fat, which is being activated by the app on boot. Could this be fixed? I'm using the latest rooted ext4 version btw
Sent from my ARCHOS 80G9 using xda premium

I got swap working!
You use swapper 2 and direct it to /mnt/sdcard, and rather than /sdcard. Turns out internal is ext and it needs fat
Sent from my ARCHOS 80G9 using xda premium

SOLVED [Q] Serious Bootloop issue using cwm

Hello everyone,
I recently rooted my phone ( http://theunlockr.com/2013/03/16/how-to-root-the-motorola-razr-i/ ) and everything was ok. But while setting up a new ROM, my system got stuck in a bootloop.
I can't figure out what is wrong, and no matter what rom i install, the device manages to boot up, but then crashes when loading GUIs and third party apps.
What i have tried so far:
wipe everything there is to wipe using CWM and formating folders also using cwm
press factory settings on fastboot
using bp tools on fastboot (though i don't know what it is used for) it managed to boot up the phone ONCE but with no wi fi nor mac adress available (the rom i used http://www.argendroid.com/topic-ROM...u-Control-Smart-Battery-21-08-2013-ArgenDroid )
mess up with different roms, all of them crashed at the same point
The Roms i tried:
Pillama 1.6 http://www.argendroid.com/topic-ROM...u-Control-Smart-Battery-21-08-2013-ArgenDroid
Atom CFW http://www.argendroid.com/topic-ROM-Atom-CFW-CustomFirmWare-Final
The tutorial's rom mentioned before which worked well
Progress and hints
at first i would just wipe data/factory , cache partition and dalvik, and the booting could not go further than displaying the unlock warning
{
"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"
}
once i formated /system, /cache, /data, /pds, /sdcard(which is actually the phone internal storage, there is another folder named /external-sd)
only then the boot process would go further and display the nice loading animations, but still crashing in the end before i could do anything.
Aditionally i can't manage to use ADB because somehow, my Barcode managed to dissapear. ADB won't recognize my device.. i'll try to find a ROM with usb debugging enabled by default but who knows...
So please help, what can i do?
I think there is something inside the internal storage that is not quite erased and is jamming when installing other roms. It is still pretty bizarre, and my phone is no more than a month old so...
Thanks beforehand.

How you installed CWM? Was using this? Which CWM version are you using? Tried to flash to stock?

well, you need to find pi-llama 1.4
download it, enter fastboot and flash the system.ext4 image. type
fastboot flash system (name of the file)
then look forward the omar-avelar kernel img and type
fastboot flash boot (name of the kernel img)

SOLVED
sky0165 said:
well, you need to find pi-llama 1.4
download it, enter fastboot and flash the system.ext4 image. type
fastboot flash system (name of the file)
then look forward the omar-avelar kernel img and type
fastboot flash boot (name of the kernel img)
Click to expand...
Click to collapse
Surprisingly enough, pi-llama 1.4 solved it.
https://mega.co.nz/#!wFpjhLrA!ODHD6DKRN-DFTGUhNPTTgzrzcIE_aG2lgWDp4gBgXHY
i just had to modify the .bat file so it wouldn't search for fix.zip in the phone memory.
It succesfully flashed system.img, boot and cwm 6.0.9 (not sure didn't check)
then i wiped data on phone, and installed fix.zip flash with cwm
once i got to restart it, i got it on fastboot mode and used bp tools and.... IT BOOTED UP!!
i think the boot included is omar's already, because wlan issues were solved (device has got a MAC adress)
thank you so much!
i won't turn off my phone again just to be sure
thiagomtl said:
How you installed CWM? Was using this? Which CWM version are you using? Tried to flash to stock?
Click to expand...
Click to collapse
Hi, it got solved thanks to @sky0165 advice,
i just used fastboot recovery <cwm image>
<cwm image> being the file downloaded from this thread
http://forum.xda-developers.com/showthread.php?t=1974097
6.+ version i didn't check
i tried to flash to stock yes but since adb didn't work it was kind of pointless i think.. it just didn't work
Thanks for your concern

I should mention that my PC is not able to recognize the usb storage.
I don't mind since Airdroid exists, but it's still kind of a bummer.
ADB recognizes it, though it displays Medfield<hex number>

ymer92 said:
Surprisingly enough, pi-llama 1.4 solved it.
https://mega.co.nz/#!wFpjhLrA!ODHD6DKRN-DFTGUhNPTTgzrzcIE_aG2lgWDp4gBgXHY
i just had to modify the .bat file so it wouldn't search for fix.zip in the phone memory.
It succesfully flashed system.img, boot and cwm 6.0.9 (not sure didn't check)
then i wiped data on phone, and installed fix.zip flash with cwm
once i got to restart it, i got it on fastboot mode and used bp tools and.... IT BOOTED UP!!
i think the boot included is omar's already, because wlan issues were solved (device has got a MAC adress)
thank you so much!
i won't turn off my phone again just to be sure
Hi, it got solved thanks to @sky0165 advice,
i just used fastboot recovery <cwm image>
<cwm image> being the file downloaded from this thread
http://forum.xda-developers.com/showthread.php?t=1974097
6.+ version i didn't check
i tried to flash to stock yes but since adb didn't work it was kind of pointless i think.. it just didn't work
Thanks for your concern
Click to expand...
Click to collapse
It's nice to hear that. You can flash other roms(Omar for example) in case you got bootloops with clean installs. You just need to do the pi-llama method (flash the system.img & kernel) and then install the rom you want on top of the pi-llama 1.4

Lended Phone to Friend; He Decided to "Encrypt his phone for "Google for Work"".

Lended Phone to Friend; He Decided to "Encrypt his phone for "Google for Work"".
He Decided he wanted to encrypt the phone so he could use Google for work.
Huge Mistake letting him do that, he ended up bricking the thing and now I've got a major issue.
I Cant write, mount, or read the /system Partition in TWRP no matter WHAT I do.
Anyone have any suggestions?
I Can get onto the system where it says "Enter your pattern to decrypt" He puts the correct one in and then it tells him "Decrypt unsuccessful"
When I try to wipe /system in wipe mode, it says Error: Cannot mount /system repeatedly.
Please put your input on the matter Thanks
(I still have 1 L90 that works, but both have Download mode wiped because I accidentally deleted it while unlocking boot loader to discover its already unlocked.
(Will post pictures later)

Bro, go to recovery, plug your device on USB, then from win open adb and type separate one by one in command prompt:
adb shell
recovery –wipe_data –set_filesystem_encryption=off

Nada
{
"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"
}
Also, Recovery Wont load anymore and now is "Blinking" Teamwin over and over. GG

And your system won't boot up? Nonsense, you did not wipe recovery with this command to make clear.

Vule991 said:
And your system won't boot up? Nonsense, you did not wipe recovery with this command to make clear.
Click to expand...
Click to collapse
Just to be clear, I'm was on Cyandogen Mod and he decided to Encrypt and I cant get past there.
And Recovery cant mount /system.

When you prompted to enter pasword to decrypt you enter: default_password?

Now, I cant mount /data

Jacobwitt said:
Now, I cant mount /data
Click to expand...
Click to collapse
Lets Recap, I ran your command and Now I can mount /system Great!
but Now I cant mount /data.
What would I do to fix that?
Also, How do you update TWRP from Recovery? (I'm an idiot lol)

Jacobwitt said:
Lets Recap, I ran your command and Now I can mount /system Great!
but Now I cant mount /data.
What would I do to fix that?
Also, How do you update TWRP from Recovery? (I'm an idiot lol)
Click to expand...
Click to collapse
If you can go into recovery, simple factory reset, your data must be wiped and clean install ROM, gapps, etc...
Have option to flash ZIP or IMAGE from recovery, select flash image, then flash TWRP.
You turn off encryption with my command: recovery –wipe_data –set_filesystem_encryption=off?
Tell other user for that, this will be useful.
Regards

Vule991 said:
If you can go into recovery, simple factory reset, your data must be wiped and clean install ROM, gapps, etc...
Have option to flash ZIP or IMAGE from recovery, select flash image, then flash TWRP.
You turn off encryption with my command: recovery –wipe_data –set_filesystem_encryption=off?
Tell other user for that, this will be useful.
Regards
Click to expand...
Click to collapse
Yes, I Issued your command and Now I cannot mount /data in TWRP and therefore cannot wipe it.
I will attempt to update TWRP, but as I said, without /data access I cannot do anything on any rom I install.

You do not mount data to flash, please unmount all partition, then wipe system, data, dalvik ART, cache and optionally internal card.

Ok This is going to be a mouthful, but this is how i fixed it.
I Tried many methods, but the one that worked was this:
So, You know how the D415's boot loader is unlocked by default?
What I did was Boot into TWRP, And used ADB through it
Then Through ADB, Pushed the IAF.img of the original download mode, ( I Wiped it accidentally, thinking I had to.) and then wrote the IAF to the Download mode to restore the Download Modes Official Function, To restore the phone to factory.
Then I Just used the LG Software Update Tool to re-flash to stock, and then uh oh, the encryption screen again.
This is the stupid part, So Apparently LG Stock Recovery was able to remove the encryption through a wipe and like magic took me to the setup screen. (No Encryption password request).
Then I Proceeded to root using LG root-script and used TWRP Manager to reinstall TWRP 3.0.2.0 Bam!
Then as a test (I Didn't want to bother downloading CM13) Flashed it with Orion OS and Mini Gapps.
And like Magic, it was all new again.
Lots of threads were used to figure this out especially the re-writing of the IAF image (I had no idea how to write it to the original IAF partition.
Thanks who ever decided to post about how to reinstall the original IAF file.
So, If your (Insert relation here) decides to encrypt your phone and then proceeds to unencrypt it and then brick it, your not in trouble after all!

Jacobwitt said:
I Tried many methods, but the one that worked was this:
So, You know how the D415's boot loader is unlocked by default?
What I did was Boot into TWRP, And used ADB through it
Then Through ADB, Pushed the IAF.img of the original download mode, ( I Wiped it accidentally, thinking I had to.) and then wrote the IAF to the Download mode to restore the Download Modes Official Function, To restore the phone to factory.
Then I Just used the LG Software Update Tool to re-flash to stock, and then uh oh, the encryption screen again.
This is the stupid part, So Apparently LG Stock Recovery was able to remove the encryption through a wipe and like magic took me to the setup screen. (No Encryption password request).
Then I Proceeded to root using LG root-script and used TWRP Manager to reinstall TWRP 3.0.2.0 Bam!
Then as a test (I Didn't want to bother downloading CM13) Flashed it with Orion OS and Mini Gapps.
And like Magic, it was all new again.
Lots of threads were used to figure this out especially the re-writing of the IAF image (I had no idea how to write it to the original IAF partition.
Thanks who ever decided to post about how to reinstall the original IAF file.
So, If your (Insert relation here) decides to encrypt your phone and then proceeds to unencrypt it and then brick it, your not in trouble after all!
Click to expand...
Click to collapse
So, you recover Download mode and flash stock ROM in LG Software Update Tool over encrypted CM13, and this fix you problem if I good understand?

Vule991 said:
So, you recover Download mode and flash stock ROM in LG Software Update Tool over encrypted CM13, and this fix you problem if I good understand?
Click to expand...
Click to collapse
Yes, That is exactly What I did.