Database Users

Huge problem to restore nandroid backup - "can't mount SDCARD:/nandroid/"

Hello, when I tried to update my Magic to a new radio something went wrong. Start-up screen freezes. Only fastboot and recovery are available.
Now, when I trie to restore my nandroid backup in recovery I get the message:
E: Can't mount /dev/block/mmcblk0
p1 (or /dev/block/mmcblk0)
(No such file or directory)
E: Can't mount SDCARD:/nandroid/
And it's not the SDcard that's malfunctioning...
When I trie it with fastboot I get:
C:\AndroidSDK\tools>fastboot flash system system.img
sending 'system' (80002 KB)... OKAY
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\AndroidSDK\tools>fastboot flash boot boot.img
sending 'boot' (2560 KB)... OKAY
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\AndroidSDK\tools>fastboot flash userdata data.img
sending 'userdata' (132301 KB)... OKAY
writing 'userdata'... INFOsignature checking...
FAILED (remote: signature verify fail)
I've searched everywhere for a solution for this problem, and tried everything but nothing helped. So I hope someone can help me here...
These are the specifications of my phone:
SAPPHIRE PVT 32A ENG S-ON H
HBOOT-1.33.2010 (SAP10000)
RADIO-6.35.10.18
The original radio was 3.22.20.17
I had recovery-RA-sapphire-v1.6.2H, but after my failed radio update, it rebootet after 2 seconds...so now I use recovery-RA-hero-v1.6.2 to enter my recovery. This one works, doesn't reboot, but I don't have acces to my SDcard.
Thanks for you're help!

How long are you waiting after booting to Recovery before trying the restore? I think there's an issue with the amount of time it takes to mount the SDCard. Try waiting for a bit. It does work for me, but not if I immediately try to backup/restore after entering Recovery. I usually wait a couple of minutes.

well...I've waited 10 minutes...but still the same response...
If I see your specifications, I see that your phone is OFF and mine ON, in another tread someone said that the "ON"-sign was the reason for not having acces to the Sdcard... :s But I'm not sure this is true...
Even...everything I trie to flash with fastboot (so I don't need acces to my SDcard I guess...) doesn't work...due to that signature verify failure... Maybe there is a solution for that problem...?

Hey it seems you really have a problem.
The hboot version is not right for your radio version. You obviously did not follow the very clear howto by cursordroid, easily found in the android development section. I'm not sure how to solve this, but you must first look for some way to upgrade the SPL to the version that works correct with new radio.

Hi...yes... I updated the radio on a wrong way...
I already thought that this new radio and 'old' SPL were the reason why this doesn't function anymore...
I already tried to update the SPL on different ways... With recovery I don't have acces to my SD card and with fastboot I get the same response as above... I don't think there is another way... :s
I really screwed up this time...I hope someone can help me out... This is the first time this happens to me but it will be the last

Woww you're so lucky you didn't brick. Love it when people fail to follow simple instructions! And how would a nandroid restore help? Since when does that restore radio/spl. Also how did you manage to get the hero recovery on there? Did you flash the recovery then radio?
Since you're using the hero recovery, it takes some time to mount the sd card. SO wait a bit when you try this
Try this,
1) fastboot oem enableqxdm 0
2) If that doesn't work, you're sort of screwed. I'm not sure if it will work since youre s-on
3) If it works, flash the old radio in recovery.
4) I'd try goldcard if none of the above works

Hi...thanks for the help!
Well, I read somewhere that I could use that hero recovery... So I use fastboot to boot the recovery on my Magic, that's the only way to enter the recovery.
I first flashed recovery sapphire 1.6.2H, made a back-up and then I flashed the radio...
I tried what you asked and I got this:
C:\AndroidSDK\tools>fastboot oem enableqxdm 0
... INFO[ERR] Command error !!!
OKAY
So...I guess I'm screwed...?

Re: Huge problem to restore nandroid backup - "can't mount SDCARD:/nandroid/"
If your phone really fails to mount the sdcard in recovery, even after waiting a while, you might still be able to flash a correct engineering spl if your recovery allows you to connect by adb. The idea would be to push the img to /cache and flash it from there, using the adb command line. I have never tried that though so no guarantees.
Sent from my HTC Magic using the XDA mobile application powered by Tapatalk

Hi, yes, I waited 30minutes...still no result... should I wait longer?
I found the correct engineering spl and I can connect by adb...
Could you tell me which commands I have to type in cmd to push the engineering spl (.zip) with adb?
Thanks!

PM me if you haven't solved the problem yet.

I haven't solved the problem yet.. Could you tell me which commands I have to type for adb in command prompt? This is the name of the .zip file "update.Engineering-SPL-HBOOT-1.33.2009-signed"

Thanks for the help man... But I didn't succeed yet...I didn't get an error message but something went wrong... This is until where I got:
C:\AndroidSDK\tools>adb shell
/ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98492 0 98492 0% /dev
/dev/block/mtdblock4 81920 1192 80728 1% /cache
/ # exit
exit
C:\AndroidSDK\tools>adb push hboot-1.76.2007.img
Android Debug Bridge version 1.0.25
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
envivornment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP disconnect <host
>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB adb
tcpip <port> - restarts the adbd daemon listening on TCP on the spec
ified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
I didn't know for sure what you ment with '(the hboot file must be present in the current folder of course)' so pasted the SPL "hboot-1.76.2007" on my SDcard and in AndroidSDK/tools
Then I did this:
C:\AndroidSDK\tools>adb shell
/ # flash_image hboot /cache/hboot-1.76.2007.img
flash_image hboot /cache/hboot-1.76.2007.img
can't find hboot partition
It could be that you did forget a 'space' between boot and cache so I tried this:
/ # flash_image hboot /cache /hboot-1.76.2007.img
flash_image hboot /cache /hboot-1.76.2007.img
usage: flash_image partition file.img
/ # reboot bootloader
reboot bootloader
When I rebooted in bootloader everything was still the same... Did I do something wrong?
Already thanks for the great help!

janximan said:
Thanks for the help man... But I didn't succeed yet...I didn't get an error message but something went wrong... This is until where I got:
C:\AndroidSDK\tools>adb shell
/ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98492 0 98492 0% /dev
/dev/block/mtdblock4 81920 1192 80728 1% /cache
/ # exit
exit
C:\AndroidSDK\tools>adb push hboot-1.76.2007.img
Click to expand...
Click to collapse
this should be
Code:
C:\AndroidSDK\tools>adb push hboot-1.76.2007.img /cache
when the hboot file is in your tools folder. You got a usage message from the command, that means the command was malformed. So the rest couldn't work either. And no I did not miss any space in the flash_image command.

Damn, sorry to disappoint but I did some more research and I think my idea won't work after all

the Sign is on, and you have to turn it off. Use the goldcard method and use:
http://rapidshare.com/files/267446145/2.53.707.2_-_sappimg.zip
to turn it off, and start the flasshing process again for safe keeping.
Instructions:
http://translate.google.pt/translat...ss.C3.A1rio_para_fazer_o_processo&sl=pt&tl=en
If you want try flash using HTC Magic oficial update and start the process all over again for safe keeping.
Hope it helps

i was reading things better. Have you tried to download a oficially signed from HTC Hboot and in fastboot flashing it ? If you sucessed you could reverse the process
PS: does anyone know to explain me why did this exacly happened?

Jup...still no difference...
Thanks drbobb for all the effort and time! If there really is no other way to make it work than the goldcard method... I should try this one...but read it first a few times...
Jgcaap... Thanks for the help.. I explained on the first page how I get this far... Updated my radio on a wrong way :s

how did you update the radio ? Sorry to ask again but in the first page isnt expressed if you done by flashing procedure (USB) or by other method (Recovery).

Well...i don't know for sure but I think I just flashed a new radio (.zip) file in recovery... Without using fastboot...

Well according to the studies the most safe is in fastboot, in recovery you can also flash but there is always a risk since the recovery might not be 100% safe to flash. But you still havent done anything else? Please try remember because there must be a way of exploiting to make the phone work again.

Rooting HTC magic

Hello,
I've problems to install Cyanogen 4.2 on my HTC Magic.
My setup:
HTC Magic (Vodafone)
Sapphire PVT 32B ENG S-OFF H
HBOOT-1.33.2005 (SAPP10000)
CPLD10
RADIO-2.22.19.26i
Apr 20 2009,15:30:43
- Android SDK installed on PC.
- USB driver installed.
- started "CMD" and give command:
fastboot boot cm-recovery-1.4.img
- Now I've maked a nandroid backup.
- Connected to USB and copy nandroid map to my PC.
- Formatted sdcard.
- Placed cm-recovery-1.4.img and update.zip to my SDcard.
- Started fastboot on my Magic.
- fastboot boot cm-recovery-1.4.img
- Wipe/reset factory.
- Apply update.zip.
Now my phone is doing the update and says everything is OK. When the update finisched I press restart. On startup only the Vodafone logo displayed. After 30 minutes only logo.
Whats going wrong?
I've read something about wrong spl package? Someone know this issue?
Also when I do the command adb devices there are no device found. When I check my Device manager on the PC I see an Android Phone and the drivers where installed correctly.
adblogcat command :
Code:
* daemon not running. starting it now *
* daemon started successfully *
- waiting for device -
I//system/xbin/busybox( 48): +++ "This is your world, these are your people. Y
ou can live for yourself today, or help build tomorrow for everyone."
I//system/xbin/busybox( 48): +++ Welcome to Android 1.6 / CyanogenMod-4.2
I//system/xbin/busybox( 48): [: 1: unknown operand
I/logwrapper( 48): /system/xbin/busybox terminated by exit(0)
I/DEBUG ( 73): debuggerd: Oct 23 2009 18:52:50
E/flash_image( 79): error opening /data/recovery.img: No such file or director
y
I/vold ( 72): Android Volume Daemon version 2.0
I/vold ( 72): New MMC card 'USD ' (serial 103819993) added @ /devices/plat
form/msm_sdcc.2/mmc_host/mmc1/mmc1:b368
I/vold ( 72): Disk (blkdev 179:0), 15659008 secs (7646 MB) 1 partitions
I/vold ( 72): New blkdev 179.0 on media USD , media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:b368, Dpp 1
I/vold ( 72): Partition (blkdev 179:1), 15650816 secs (7642 MB) type 0xb
I/vold ( 72): New blkdev 179.1 on media USD , media path /devices/platform
/msm_sdcc.2/mmc_host/mmc1/mmc1:b368, Dpp 0
I/vold ( 72): Evaluating dev '/devices/platform/msm_sdcc.2/mmc_host/mmc1/mm
c1:b368/block/mmcblk0' for mountable filesystems for '/sdcard'
I/vold ( 72): Aborting start of /sdcard (bootstrap = 1)
I/vold ( 72): Volmgr not ready to handle device
D/vold ( 72): Bootstrapping complete

Mod edit: not dev related, moved to general

Rooting HTC Magic on OSX
I am so confused. I'm using Mac OSX and I think I followed everything that needs to be done based on the guide found on Full Update Guide - G1/Dream/Magic32A Firmware to CyanogenMod. But when I get to step 5 under Installation, I'm "command not found" error on Terminal. I hope there's a step-by-step or screen-by-screen tutorial on this, starting from installing the SDK. Sigh

Did you flash the DRC83_defanged.zip first? You need that for CM4 ROMs.

saferoot protocol failure error

I'm trying to use the saferoot rooting method for my att galaxy s4 on MK2 but keep getting this error:
Waiting for your phone to appear
Your phone is detected and ready for rooting.
Sending files to your device...
protocol failure
rm failed for /data/local/tmp/Superuser.apk, No such file or directory
protocol failure
protocol failure
protocol failure
protocol failure
protocol failure
Unable to chmod /data/local/tmp/getroot: No such file or directory
Unable to chmod /data/local/tmp/busybox: No such file or directory
Starting rooting program.
/system/bin/sh: /data/local/tmp/getroot: not found
Removing temporary files...
rm failed for /data/local/tmp/getroot, No such file or directory
rm failed for /data/local/tmp/selinuxoff, No such file or directory
rm failed for /data/local/tmp/su, No such file or directory
rm failed for /data/local/tmp/busybox, No such file or directory
rm failed for /data/local/tmp/install-recovery.sh, No such file or directory
Rebooting... Please wait.
Waiting for device to re-appear...
I've updated the drivers, toggled usb debugging, toggled camera and media mode, but nothing seems to work...

just download a new version of saferoot, but am getting this error now:
--- Samsung Galaxy S4 Android 4.3 Root ---
--- Based on the CVE-2013-6282 exploit by cubeundcube ---
[*] Testing adb usability
Plug in your phone and Press any key to continue . . .
[*] Waiting for your phone to appear
[*] Your phone is detected and ready for rooting.
[*] Sending files to your device...
Unable to chmod /data/local/tmp/getroot: No such file or directory
Unable to chmod /data/local/tmp/busybox: No such file or directory
[*] Starting rooting program.
/system/bin/sh: /data/local/tmp/getroot: not found
[*] Removing temporary files...
rm failed for /data/local/tmp/getroot, No such file or directory
rm failed for /data/local/tmp/su, No such file or directory
rm failed for /data/local/tmp/busybox, No such file or directory
rm failed for /data/local/tmp/install-recovery.sh, No such file or directory
[*] Rebooting... Please wait.
[*] Waiting for device to re-appear...
[*] Checking if su is still there
Something has deleted su - looking for the backup copy
The backup is gone too - can't recover!
Press any key to continue . . .

Unsuccessfull root on lg g2 f320k20f

Hi,
2nd time trying to root but still some message about can't reate, start and failed to copy. Full results below also. I've use the files and methods heree:
http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
http://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=45693809&nocache=1
Mounting system, pushing su binary and installing SuperSu...
2244 KB/s (1085140 bytes in 0.472s)
cp: can't create '/system/xbin/busybox': Read-only file system
failed to copy 'su' to '/system/xbin/daemonsu': Read-only file system
cp: can't stat '/system/xbin/daemonsu': No such file or directory
failed to copy 'install-recovery.sh' to '/system/etc/install-recovery.sh': Read-
only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to open /system/xbin/su: No such file or directory
Rebooting Phone.
***************************************************
***************************************************
You should hopefully now be fully rooted!!
Wait for your device to reboot and continue
with ioroot script to backup EFS...
***************************************************
***************************************************
/sdcard/modemst1.img: cannot open for write: Read-only file system
/sdcard/modemst2.img: cannot open for write: Read-only file system
remote object '/sdcard/modemst1.img' does not exist
remote object '/sdcard/modemst2.img' does not exist
++++++++++++++++++++++++++++++++++++++++FULL RESULT START+++++++++++++++++++++++++++
======adbd is already running as root
uid=0(root) gid=0(root) context=u:r:shell:s0
If you do NOT see uid=0(root) gid=0(root) above then
it is likely your device firmware is not supported or
USB mode was not toggled properly. You can try to
run the script again.
Press CTRL+c to stop this script...
If you DO see uid=0(root) gid=0(root) mentioned above...
CONGRATS.. Rooted ADB is now confirmed.
You will have a rooted ADB shell but no apps on the
phone will
'be' is not recognized as an internal or external command,
operable program or batch file.
PRESS ENTER to continue with full root.
PLEASE NOTE!
Continuing with full root can trip LG's rootchecker.
This means your phone will show ROOTED in Download mode.
You can remove root flag by flashing stock firmware...
.bin .tot or .kdz
If you do not want to possibly invalidate your warranty
press CTRL+c to stop this script...
*******************************************************
Press any key to continue . . .
Mounting system, pushing su binary and installing SuperSu...
2244 KB/s (1085140 bytes in 0.472s)
cp: can't create '/system/xbin/busybox': Read-only file system
failed to copy 'su' to '/system/xbin/daemonsu': Read-only file system
cp: can't stat '/system/xbin/daemonsu': No such file or directory
failed to copy 'install-recovery.sh' to '/system/etc/install-recovery.sh': Read-
only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to open /system/xbin/su: No such file or directory
Rebooting Phone.
***************************************************
***************************************************
You should hopefully now be fully rooted!!
Wait for your device to reboot and continue
with ioroot script to backup EFS...
***************************************************
***************************************************
/sdcard/modemst1.img: cannot open for write: Read-only file system
/sdcard/modemst2.img: cannot open for write: Read-only file system
remote object '/sdcard/modemst1.img' does not exist
remote object '/sdcard/modemst2.img' does not exist
***************************************************
***************************************************
EFS partitions now in ioroot folder on computer...
They are named modemst1.img and modemst2.img
They will come in handy in case of an emergency.
Store them somewhere you won't lose them.
IOroot is now complete.
***************************************************
***************************************************
Press any key to continue . . .
++++++++++++++++++++++FULL RESULT END++++++++++++++++++++

Same problem here, no solution yet.

LG G2 root
Hello guys,
is there any solution for this? I have same issue
Thank you

[FIX] No Run Download Mode

Hi all, hopefully today I bring good news, for you guys had the same as my previous loss
directly to the problem, I'm having problems with the download mode on the g2 d802, how to I get normal as before, help me anybody I say thank you. :crying:
Click to expand...
Click to collapse
I tried various methods suggested and finally I can get back to the normal mode and can download flashing stock rom.
and these are the steps I did to get back to normal download mode works fine now, hope this works for you too
Download the laf.img file from here
http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions
Code:
You need an OTG cable for this
Copy the file from the otg storage to your sdcard
Open twrp terminal and select the sdcard folder
Type this dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
This will surely fix your download mode
Worked for me...
turn off the device after you make that step, vol up, connect the device to the PC after entering download mode as in the picture my case before him, press the power button a few times
and taraaaaa the device back to normal mode download
Please return your stock rom http://forum.xda-developers.com/showthread.php?t=2432476
Thanks to @warlock94 http://forum.xda-developers.com/showpost.php?p=51633331&postcount=282

prabu33 said:
directly to the problem, I'm having problems with the download mode on the g2 d802, how to I get normal as before, help me anybody I say thank you. :crying:
Click to expand...
Click to collapse
I'm in a similar situation, no download mode.
D802 that works fine (tried both CM11 based and Stock based roms), I have recovery (TWRP), but I want to go back to 100% stock, and download mode is stuck in the splash screen, like in yours.
Now I could flash some of the zipped stock roms packed for recovery, but if for some reason my phone wouldn't boot, I wouldn't have download mode...
So I will stay in CM11 for now, because flashing something else is simply not safe.
Thanks

CaraMuuu said:
I'm in a similar situation, no download mode.
D802 that works fine (tried both CM11 based and Stock based roms), I have recovery (TWRP), but I want to go back to 100% stock, and download mode is stuck in the splash screen, like in yours.
Now I could flash some of the zipped stock roms packed for recovery, but if for some reason my phone wouldn't boot, I wouldn't have download mode...
So I will stay in CM11 for now, because flashing something else is simply not safe.
Thanks
Click to expand...
Click to collapse
Please try my way, I hope you are lucky

the issue is complete, a sunny day :fingers-crossed:

CaraMuuu said:
I'm in a similar situation, no download mode.
D802 that works fine (tried both CM11 based and Stock based roms), I have recovery (TWRP), but I want to go back to 100% stock, and download mode is stuck in the splash screen, like in yours.
Now I could flash some of the zipped stock roms packed for recovery, but if for some reason my phone wouldn't boot, I wouldn't have download mode...
So I will stay in CM11 for now, because flashing something else is simply not safe.
Thanks
Click to expand...
Click to collapse
I was in the same condition.
I wanted to flash my stock KDZ but it was getting stuck at the initial logo of Download mode
You can fix your download mode by this method as the laf.img is the "Download mode" partition image
Since you are on CM11, you don't need an OTG cable, just copy it to your sdcard and run the command from your TWRP terminal
You will be able to flash KDZs and return back to stock...

same problem but I can not enter to recovery .hahaha bring it to lg service to change m/b.
---------- Post added at 09:12 PM ---------- Previous post was at 09:09 PM ----------
CaraMuuu said:
I'm in a similar situation, no download mode.
D802 that works fine (tried both CM11 based and Stock based roms), I have recovery (TWRP), but I want to go back to 100% stock, and download mode is stuck in the splash screen, like in yours.
Now I could flash some of the zipped stock roms packed for recovery, but if for some reason my phone wouldn't boot, I wouldn't have download mode...
So I will stay in CM11 for now, because flashing something else is simply not safe.
Thanks
Click to expand...
Click to collapse
You have recovery mode .you can flash back to stock via dd command everything of g2 partition like me.
My case via fastboot .You case can do via recovery.
https://www.facebook.com/notes/droi...ware-ไม่ได้-เข้าหน้า-fastboot/548095431975810

ever say and do are stuck at twrp, successfully performs ADB sideload, its demographic is still stuck download mode does not work as in the picture, doing way OP and succeeded

prabu33 said:
Hi all, hopefully today I bring good news, for you guys had the same as my previous loss
I tried various methods suggested and finally I can get back to the normal mode and can download flashing stock rom.
and these are the steps I did to get back to normal download mode works fine now, hope this works for you too
Download the laf.img file from here
http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions
Code:
You need an OTG cable for this
Copy the file from the otg storage to your sdcard
Open twrp terminal and select the sdcard folder
Type this dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
This will surely fix your download mode
Worked for me...
turn off the device after you make that step, vol up, connect the device to the PC after entering download mode as in the picture my case before him, press the power button a few times
and taraaaaa the device back to normal mode download
Please return your stock rom http://forum.xda-developers.com/showthread.php?t=2432476
Thanks to @warlock94 http://forum.xda-developers.com/showpost.php?p=51633331&postcount=282
Click to expand...
Click to collapse
I got stuck in the first step of download mode and now it works ! Goog job, thank you :good:

Sangoku91 said:
I got stuck in the first step of download mode and now it works ! Goog job, thank you :good:
Click to expand...
Click to collapse
the same problem may be able to help much with this.

Worked for me! Thanks!!

CaraMuuu said:
Worked for me! Thanks!!
Click to expand...
Click to collapse
may your days fun day with the new device :laugh:

prabu33 said:
may your days fun day with the new device :laugh:
Click to expand...
Click to collapse
I'm unfortunately again in a similar situation, and the proposed resolution won't be applicable.
So.. I went stock, but I wanted to try some other AOSP based roms again. I downloaded FreeGee, and with this new version, it didn't only mess my laf partition as expected, but it also didn't install any recovery (tried TWRP and CWM, of course; ending with some weird error message). So now I'm in rooted stock, with no download mode and no custom recovery mode (stock recovery works just fine).
Any ideas? I tried to run the command in OP from terminal emulator with SU permissions, and even tough i saw a success message at the end, it seems it doesn't really do the job.

Logcat, in case somebody can help here:
Code:
2014-04-13 19:03:52
FreeGee version: 1.9.23
FreeGee paid: true
FreeGee dir is: /storage/emulated/legacy/freegee/
/system/bin/cp
constants.CP_COMMAND is /system/bin/cp
/data/local/tmp/edifier
/data/local/tmp/busybox
/data/local/tmp/busybox
/data/local/tmp/mkbootimg
/data/local/tmp/unpackbootimg
Download id from start is: 233
Download id from completition is: 233
Downloaded file path is: /storage/emulated/0/freegee/devices2_beta.xml
DeviceXML is: /storage/emulated/0/freegee/devices2_beta.xml
Device Name: LG G2
Device Model: LG-D802
Software Version: D80220c
Checking for loki support
Current actions are: loki_check,
Calculated digest: 24ca4d079b533dc2c96e8b05ee210aeb
Provided digest: 24ca4d079b533dc2c96e8b05ee210aeb
Using predownloaded loki_check
Running check for loki support through zip
about to run program [/system/bin/sh] with 2 args
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.039 secs (26886564 bytes/sec)
[-] Unsupported aboot image.
run_program: child exited with status 1
script aborted: assert failed: run_program("/system/bin/sh","/data/local/tmp/loki_check.sh") == 0
path is /storage/emulated/legacy/freegee//loki_check.zip
Path was /storage/emulated/legacy/freegee//loki_check.zip
Finding update package...
I:Update location: /storage/emulated/legacy/freegee//loki_check.zip
Opening update package...
I:1 key(s) loaded from /data/local/tmp/keys
Verifying update package...
I:comment is 1738 bytes; signature 1720 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
path is: /storage/emulated/legacy/freegee//loki_check.zip
Installing update...
E: unknown command [%s]
E: unknown command [%s]
E: Error in %s
(Status %d)
Exit code is: 1
2014-04-13 19:08:33
FreeGee version: 1.9.23
FreeGee paid: true
FreeGee dir is: /storage/emulated/legacy/freegee/
/system/bin/cp
constants.CP_COMMAND is /system/bin/cp
/data/local/tmp/edifier
/data/local/tmp/busybox
/data/local/tmp/busybox
/data/local/tmp/mkbootimg
/data/local/tmp/unpackbootimg
Download id from start is: 240
Download id from completition is: 240
Downloaded file path is: /storage/emulated/0/freegee/devices2_beta.xml
DeviceXML is: /storage/emulated/0/freegee/devices2_beta.xml
Device Name: LG G2
Device Model: LG-D802
Software Version: D80220c
Checking for loki support
Current actions are: loki_check,
Calculated digest: 24ca4d079b533dc2c96e8b05ee210aeb
Provided digest: 24ca4d079b533dc2c96e8b05ee210aeb
Using predownloaded loki_check
Running check for loki support through zip
about to run program [/system/bin/sh] with 2 args
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.047 secs (22310127 bytes/sec)
[-] Unsupported aboot image.
run_program: child exited with status 1
script aborted: assert failed: run_program("/system/bin/sh","/data/local/tmp/loki_check.sh") == 0
path is /storage/emulated/legacy/freegee//loki_check.zip
Path was /storage/emulated/legacy/freegee//loki_check.zip
Finding update package...
I:Update location: /storage/emulated/legacy/freegee//loki_check.zip
Opening update package...
I:1 key(s) loaded from /data/local/tmp/keys
Verifying update package...
I:comment is 1738 bytes; signature 1720 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
path is: /storage/emulated/legacy/freegee//loki_check.zip
Installing update...
E: unknown command [%s]
E: unknown command [%s]
E: Error in %s
(Status %d)
Exit code is: 1
2014-04-13 19:16:09
FreeGee version: 1.9.23
FreeGee paid: true
FreeGee dir is: /storage/emulated/legacy/freegee/
/system/bin/cp
constants.CP_COMMAND is /system/bin/cp
/data/local/tmp/edifier
/data/local/tmp/busybox
/data/local/tmp/busybox
/data/local/tmp/mkbootimg
/data/local/tmp/unpackbootimg
Download id from start is: 241
Download id from completition is: 241
Downloaded file path is: /storage/emulated/0/freegee/devices2_beta.xml
DeviceXML is: /storage/emulated/0/freegee/devices2_beta.xml
Device Name: LG G2
Device Model: LG-D802
Software Version: D80220c
Checking for loki support
Current actions are: loki_check,
Calculated digest: 24ca4d079b533dc2c96e8b05ee210aeb
Provided digest: 24ca4d079b533dc2c96e8b05ee210aeb
Using predownloaded loki_check
Running check for loki support through zip
about to run program [/system/bin/sh] with 2 args
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.042 secs (24966095 bytes/sec)
[-] Unsupported aboot image.
run_program: child exited with status 1
script aborted: assert failed: run_program("/system/bin/sh","/data/local/tmp/loki_check.sh") == 0
path is /storage/emulated/legacy/freegee//loki_check.zip
Path was /storage/emulated/legacy/freegee//loki_check.zip
Finding update package...
I:Update location: /storage/emulated/legacy/freegee//loki_check.zip
Opening update package...
I:1 key(s) loaded from /data/local/tmp/keys
Verifying update package...
I:comment is 1738 bytes; signature 1720 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
path is: /storage/emulated/legacy/freegee//loki_check.zip
Installing update...
E: unknown command [%s]
E: unknown command [%s]
E: Error in %s
(Status %d)
Exit code is: 1
2014-04-13 19:23:21
FreeGee version: 1.9.23
FreeGee paid: true
FreeGee dir is: /storage/emulated/legacy/freegee/
/system/bin/cp
constants.CP_COMMAND is /system/bin/cp
/data/local/tmp/edifier
/data/local/tmp/busybox
/data/local/tmp/busybox
/data/local/tmp/mkbootimg
/data/local/tmp/unpackbootimg
Download id from start is: 242
Download id from completition is: 242
Downloaded file path is: /storage/emulated/0/freegee/devices2_beta.xml
DeviceXML is: /storage/emulated/0/freegee/devices2_beta.xml
Device Name: LG G2
Device Model: LG-D802
Software Version: D80220c
Checking for loki support
Current actions are: loki_check,
Calculated digest: 24ca4d079b533dc2c96e8b05ee210aeb
Provided digest: 24ca4d079b533dc2c96e8b05ee210aeb
Using predownloaded loki_check
Running check for loki support through zip
about to run program [/system/bin/sh] with 2 args
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.041 secs (25575024 bytes/sec)
[-] Unsupported aboot image.
run_program: child exited with status 1
script aborted: assert failed: run_program("/system/bin/sh","/data/local/tmp/loki_check.sh") == 0
path is /storage/emulated/legacy/freegee//loki_check.zip
Path was /storage/emulated/legacy/freegee//loki_check.zip
Finding update package...
I:Update location: /storage/emulated/legacy/freegee//loki_check.zip
Opening update package...
I:1 key(s) loaded from /data/local/tmp/keys
Verifying update package...
I:comment is 1738 bytes; signature 1720 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
path is: /storage/emulated/legacy/freegee//loki_check.zip
Installing update...
E: unknown command [%s]
E: unknown command [%s]
E: Error in %s
(Status %d)
Exit code is: 1
Current actions are: loki_recovery,
Calculated digest: fb1b35bf05f1200e7f508962939296aa
Provided digest: fb1b35bf05f1200e7f508962939296aa
Using predownloaded loki_recovery
Current actions are: Revert D802 Aboot, loki_recovery,
Calculated digest: 2837dd9517350f6e0dbaa497107fa307
Provided digest: 2837dd9517350f6e0dbaa497107fa307
Using predownloaded Revert D802 Aboot
Current actions are: Revert D802 Aboot, TWRP-2.6.3.3, loki_recovery,
Calculated digest: 0a4f4eed6290f5d0101498281f5c8f94
Provided digest: 0a4f4eed6290f5d0101498281f5c8f94
Using predownloaded TWRP-2.6.3.3
actionDownloads size: 3
actionOrder size: 3
actionsleft: 3
allActionsDownloads is: true
Performing action: Revert D802 Aboot
about to run program [/system/bin/sh] with 2 args
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.166 secs (6316722 bytes/sec)
31744+0 records in
31744+0 records out
16252928 bytes transferred in 2.539 secs (6401310 bytes/sec)
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.031 secs (33825032 bytes/sec)
65536+0 records in
65536+0 records out
33554432 bytes transferred in 2.421 secs (13859740 bytes/sec)
1339c25f9052634eaf372ae9f70447d8 /data/local/tmp/aboot-after.img
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.603 secs (1738932 bytes/sec)
run_program: child exited with status 4
script aborted: assert failed: run_program("/system/bin/sh","/data/local/tmp/revert_aboot.sh") == 0
path is /storage/emulated/legacy/freegee//revert_aboot_d802.zip
Path was /storage/emulated/legacy/freegee//revert_aboot_d802.zip
Finding update package...
I:Update location: /storage/emulated/legacy/freegee//revert_aboot_d802.zip
Opening update package...
I:1 key(s) loaded from /data/local/tmp/keys
Verifying update package...
I:comment is 1738 bytes; signature 1720 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
path is: /storage/emulated/legacy/freegee//revert_aboot_d802.zip
Installing update...
E: unknown command [%s]
E: unknown command [%s]
E: Error in %s
(Status %d)
Exit code is: 1

CaraMuuu said:
I'm unfortunately again in a similar situation, and the proposed resolution won't be applicable.
So.. I went stock, but I wanted to try some other AOSP based roms again. I downloaded FreeGee, and with this new version, it didn't only mess my laf partition as expected, but it also didn't install any recovery (tried TWRP and CWM, of course; ending with some weird error message). So now I'm in rooted stock, with no download mode and no custom recovery mode (stock recovery works just fine).
Any ideas? I tried to run the command in OP from terminal emulator with SU permissions, and even tough i saw a success message at the end, it seems it doesn't really do the job.
Click to expand...
Click to collapse
Install flashify from playstore and flash a custom recovery
Then go in recovery and push the laf image through terminal
Sent from my LG-D802 using xda app-developers app

prabu33 said:
Hi all, hopefully today I bring good news, for you guys had the same as my previous loss
I tried various methods suggested and finally I can get back to the normal mode and can download flashing stock rom.
and these are the steps I did to get back to normal download mode works fine now, hope this works for you too
Download the laf.img file from here
http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions
Code:
You need an OTG cable for this
Copy the file from the otg storage to your sdcard
Open twrp terminal and select the sdcard folder
Type this dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
This will surely fix your download mode
Worked for me...
turn off the device after you make that step, vol up, connect the device to the PC after entering download mode as in the picture my case before him, press the power button a few times
and taraaaaa the device back to normal mode download
Please return your stock rom http://forum.xda-developers.com/showthread.php?t=2432476
Thanks to @warlock94 http://forum.xda-developers.com/showpost.php?p=51633331&postcount=282
Click to expand...
Click to collapse
Will this work for vs980? Do I use the same files?

vs980
can someone help with the vs980? There is no 24A 4.4.2 kitkat partitions in the main vs980 files even with that the laf file seems to be a .bin file and thus non flashable.. :/ help pleaseeee

Hi I have similiar problem, i Have custom rom and TWRP, but my download mode shows only splash and I cant flash kdz. I try your command, but TWRP terminal shows me: can't open dev/block/platform/msm-sddc.1/by-name/laf No such file or directory. What can i do?

Download Mode Fixed
prabu33 said:
Hi all, hopefully today I bring good news, for you guys had the same as my previous loss
I tried various methods suggested and finally I can get back to the normal mode and can download flashing stock rom.
and these are the steps I did to get back to normal download mode works fine now, hope this works for you too
Download the laf.img file from here
http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions
Code:
You need an OTG cable for this
Copy the file from the otg storage to your sdcard
Open twrp terminal and select the sdcard folder
Type this dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
This will surely fix your download mode
Worked for me...
turn off the device after you make that step, vol up, connect the device to the PC after entering download mode as in the picture my case before him, press the power button a few times
and taraaaaa the device back to normal mode download
Please return your stock rom http://forum.xda-developers.com/showthread.php?t=2432476
Thanks to @warlock94 http://forum.xda-developers.com/showpost.php?p=51633331&postcount=282
Click to expand...
Click to collapse
Thank you so much for posting this great solution :good::good::good: i just cant tell how i am feeling thank you once again Bro :good:

this laf.img worked for any G2 rom? for example d802 32GB?

how about 32G
Hello, same problem but with LG G2 32Go , help me plz.