Dear Member,
I'm new to rooring and flashing custom ROMS...
i have a folio 100 and after a lot of googling and hardwork i finally managed to root my device on windows XP.. then i tried to install Jelly Bean / CM10 (4.1.1) Alpha 2 - 27.09.2012 from http://forum.xda-developers.com/showthread.php?t=1864774 and followed the instructions.
initially when i typed fastboot devices i was getting "? fastboot" and rest of the commands returned 0x2 error.
then i treid
fastboot -i 0x955 erase userdata
fastboot -i 0x955 erase system
fastboot -i 0x955 erase cache
fastboot -i 0x955 erase linux
fastboot -i 0x955 erase recovery
till now everything worked like a charm but when i tried to run the last command
fastboot -i 0x955 flash recovery recovery-cwm-6.0.1.4.img
i'm getting error message "unable to load recoveryxxxx.img"
now i treid to reboot the device and its saying "magic value mismatch" please help me out..
Nonlxpe Menteur
leaderrocks said:
Dear Member,
I'm new to rooring and flashing custom ROMS...
i have a folio 100 and after a lot of googling and hardwork i finally managed to root my device on windows XP.. then i tried to install Jelly Bean / CM10 (4.1.1) Alpha 2 - 27.09.2012 from http://forum.xda-developers.com/showthread.php?t=1864774 and followed the instructions.
initially when i typed fastboot devices i was getting "? fastboot" and rest of the commands returned 0x2 error.
then i treid
fastboot -i 0x955 erase userdata
fastboot -i 0x955 erase system
fastboot -i 0x955 erase cache
fastboot -i 0x955 erase linux
fastboot -i 0x955 erase recovery
till now everything worked like a charm but when i tried to run the last command
fastboot -i 0x955 flash recovery recovery-cwm-6.0.1.4.img
i'm getting error message "unable to load recoveryxxxx.img"
now i treid to reboot the device and its saying "magic value mismatch" please help me out..
Click to expand...
Click to collapse
First, download the latest & most stable ROM (at the moment), including the ROM, GAPPS, recovery-cwm-CM10-A3.img & formatsd.zip
http://forum.xda-developers.com/showthread.php?t=1864774
Actually, you just need to flash the recovery through fastboot, other else can done in the recovery.
1. Copy all the ROM, GAPPS & formatsd.zip into your memory card. Then insert it into your Folio.
2. Run command prompt, make sure your tablet is connected with your PC in fastboot mode.
To erase existing/stock recovery. In command prompt, go into the fastboot program folder and type the following commands
Code:
fastboot erase recovery
3. Copy the CWM Recovery into your fastboot adb folder.
To flash CWM Recovery
Code:
fastboot flash recovery recovery-cwm-CM10-A3.img
fastboot reboot
4. Enter Recovery. Before you begin, wipe everything (except external_sd) in the CWM Recovery, after wiped, you can install the 3 zip files one by one. After finish, just reboot system.
Full procedure also stated in the link I provided, please scroll down.
Hope that helps you.
So did above solution help? I had a similar issue, and I resolved it by just booting the recovery image from fastboot, i.e.
Code:
fastboot boot recovery.img
Once you get into recovery you can flash an image which will in most cases flash a recovery image along with it. If not, you can try to flash the recovery image again once you've done a full wipe from the booted recovery.
I flashed TWRP to my tablet using the ADB/dd commands mentioned in the TWRP website. Now I wanna use the CWM that is included in the boot.img of cyanogenmod.
How do I do it? Do I just boot into fastboot and run fastboot to flash CWM?
Here's the adb commands use to flash TWRP
Code:
Download the above file. Copy the file to /sdcard/fotakernel.img and run the following commands using terminal emulator or in adb shell:
su
dd if=/sdcard/fotakernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Here's the fastboot commands use to flash CWM according to cyanogenmod.
Code:
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
thanks!
anyone? thanks
I'M NOT RESPONSIBLE FOR PEOPLE NOT FOLLOWING INSTRUCTIONS OR HARD BRICKED PHONES.
To follow this guide you must at least be able to access TWRP or Download mode or Fastboot at least.
(This guide applies too if your phone boots but with the Secure Boot error 1003 <- this error doesnt let your phone charge powered off)
1. Download Unbrick.zip
2. Download LG root zvb method zip from HERE (thanks to AUTOPRIME & Team CODEFIRE)
2a. Extract unbrick zip and root zvb zip in the same location
2b. right click "open command prompt" inside the folder of extraction.
3. Have LG drivers installed (you can find them in the forums)
4. If you have access to download mode and no TWRP installed you must first nuke LAF
4a. use the command prompt window we opened on 2b. and nuke laf using dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
4b. type LEAVE (this will leave your G3 on fastboot)
5. On the same window we must flash TWRP. using fastboot flash recovery twrp.img
5a. then fastboot flash boot boot.img, fastboot flash aboot aboot.img, fastboot flash laf laf.img
5b. fastboot reboot should take you to twrp where you can flash any rom (I suggest FULMICS)
5c. If the rom you flash fails to boot or you keep getting secure boot error keep on with this guide.
6. Enter twrp and copy the boot, aboot and laf imgs to your internal storage
6a. open a cmd prompt and enter adb shell
6b. use dd command as follows:
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
7. Reboot to recovery and flash any custom rom this should fix your Secure Boot error Sprint LG G3. :highfive:
Thanks to all devs who worked on root and roms for this amazing phone!
Thanks! I had a working phone but still got the boot error. I copied the unbrick.zip to my phone and used the terminal in TWRP to run the dd commands in step 6b and it fixed the error! Reinstalled a fresh fulmics and everything is working fine.
I was using a guide, https://forum.xda-developers.com/android/help/guide-how-to-lg-d-631-att-fastboot-t3130955, in hopes to use a custom recovery to restore my phone, it didn't take. Which lead to this problem.
During the process, I used ADB and inputed this command:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
(I also ran this command to zero out the actual block partition)
dd if=/dev/zero of=/dev/block/mmcblk0p15
So I found this guide, after finding out that a tot file is the only way to restore.
https://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
I did well until the final part of step, which requires the phone to be in download mode. I realize the problem is that the phone is in fast boot instead of download/driver mode, and I have no idea how to switch it back.
Also, The fastboot reboot command does nothing, and it flatout rejects the reboot into bootloader command.
Hello everyone, a year ago a I had installed a custom recovery on my Lenovo S5000-F and it caused a bootloop and I lost the recovery, fastboot is working fine but it only allow me flash boot, system, userdata and cache partitions. I already tried do:
1-Unpack boot.img
2-Edit default.prop to allow adb debugging and then create a custom OTA update to install by adb sideload.
But when I boot the system I get device offline. So looking through system.img I found an interesting thing, a flash recovery script: install-recovery.sh
Bash:
#!/system/bin/sh
echo 1 > /sys/module/sec/parameters/recovery_done #tony
if ! applypatch -c EMMC:recovery:6156288:b1d3582729e0f954b16931a7a87d4c09b6854396; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:boot:5781504:94079a17dc0e061e417363e4d44d7d8d0e609f16 EMMC:recovery b1d3582729e0f954b16931a7a87d4c09b6854396 6156288 94079a17dc0e061e417363e4d44d7d8d0e609f16:/system/recovery-from-boot.p
if applypatch -c EMMC:recovery:6156288:b1d3582729e0f954b16931a7a87d4c09b6854396; then #tony
echo 0 > /sys/module/sec/parameters/recovery_done #tony
log -t recovery "Install new recovery image completed"
else
echo 2 > /sys/module/sec/parameters/recovery_done #tony
log -t recovery "Install new recovery image not completed"
fi
else
echo 0 > /sys/module/sec/parameters/recovery_done #tony
log -t recovery "Recovery image already installed"
fi
This script means to replace any recovery installed by the user to the original one, but for some reason its not working.
So I would like to know if there is any way to flash a recovery partition through a script, so I can write this script to init.rc to install the stock recovery and fix bootloop.
EDIT: The install-recovery.sh had installed the stock recovery but I didn't noticed lol, the cause of bootloop is because the recovery and logo partitions its in the same file so when I flashed TWRP with a size bigger than my recovery partition it wrote to logo partition too.
Solved by creating a custom script using the same "applypatch" binary to flash the logo partition and worked fine
I know you want init rc... but...
Flashing stock bootloader SHOULD restore your ability to RESTORE recovery, which in turn will be used to get you to flash an update or restore.
You also need to re-enable fastboot keys ((fastboot) device offline, need to grant adb keys in gui )
And then again, I've seen in my phone that with adb keys set in gui of fone, does not mean fastboot keys were registered, only seen this since android 10, never seen it in 9, or less...?
I dont help with custom roms because there is too many, but flashing
Pachacouti said:
I know you want init rc... but...
Flashing stock bootloader SHOULD restore your ability to RESTORE recovery, which in turn will be used to get you to flash an update or restore.
You also need to re-enable fastboot keys ((fastboot) device offline, need to grant adb keys in gui )
And then again, I've seen in my phone that with adb keys set in gui of fone, does not mean fastboot keys were registered, only seen this since android 10, never seen it in 9, or less...?
I dont help with custom roms because there is too many, but flashing
Click to expand...
Click to collapse
But I can't flash stock booloader, fastboot only flash boot, system, userdata and cache partitions, since I can flash boot I can make a modified init.rc script to flash the stock recovery during boot time, but I don't know how to do this :/
Me neither, I dont think init.rc (the app.apk) is going to be much use soon either.
You say:
But I can't flash stock booloader,
fastboot only flash boot, system, userdata and cache partitions, ...
So I'm kinda confused, because where you say 'But I cant flash stock bootloader' then say 'fastboot only flash boot' tells me you SHOULD be able to flash stock bootloader with this:
fastboot reboot bootloader
( lets me know your actually in the bootloader's fastboot, and not custom recovery (twrp style, mb with no twrp gui,) fastboot, which can be confusing, because your then using the recovery's fastboot, and not the bootloader that loads BEFORE the recovery VERSION of fastboot, which MAY be out of date..)
fastboot erase/format bootoader ( erase/format=whichever works, do not reboot )
fastboot -w
fastboot flash boot YOUR_STOCK_BOOTLOADER.img
fastboot -w
fastboot reboot
Then do:
fastboot -w
fastboot erase/format recovery ( again, whichever wipes recovery)
fastboot -w
then
fastboot flash recovery YOUR_STOCK_RECOVERY.img
Fastboot -w (so many huh? but makes sure things get wiped that may contain any hidden cache)
fastboot reboot
That should be it lol, apart from the fact I dont know if you are a/b partition in which case, try booting fone with
fastboot boot slot_a OR slot_b
After this, I cant add, cause I cant speak for custom roms, but the above would work for me.
Pachacouti said:
Me neither, I dont think init.rc (the app.apk) is going to be much use soon either.
You say:
But I can't flash stock booloader,
fastboot only flash boot, system, userdata and cache partitions, ...
So I'm kinda confused, because where you say 'But I cant flash stock bootloader' then say 'fastboot only flash boot' tells me you SHOULD be able to flash stock bootloader with this:
fastboot reboot bootloader
( lets me know your actually in the bootloader's fastboot, and not custom recovery (twrp style, mb with no twrp gui,) fastboot, which can be confusing, because your then using the recovery's fastboot, and not the bootloader that loads BEFORE the recovery VERSION of fastboot, which MAY be out of date..)
fastboot erase/format bootoader ( erase/format=whichever works, do not reboot )
fastboot -w
fastboot flash boot YOUR_STOCK_BOOTLOADER.img
fastboot -w
fastboot reboot
Then do:
fastboot -w
fastboot erase/format recovery ( again, whichever wipes recovery)
fastboot -w
then
fastboot flash recovery YOUR_STOCK_RECOVERY.img
Fastboot -w (so many huh? but makes sure things get wiped that may contain any hidden cache)
fastboot reboot
That should be it lol, apart from the fact I dont know if you are a/b partition in which case, try booting fone with
fastboot boot slot_a OR slot_b
After this, I cant add, cause I cant speak for custom roms, but the above would work for me.
Click to expand...
Click to collapse
Oh I got it now, you mean flashing stock bootloader into boot partition so when I turn on the device it will be on bootloader, I can try it but there's another problem, I don't have the stock bootloader lol
GO get it then lol...
Pachacouti said:
GO get it then lol...
Click to expand...
Click to collapse
Unfortunately I didn't found the bootloader, but I tried flash the stock recovery into boot partition, but when I reboot the device boots into grey screen and then shutdown. I have no idea why this not worked :/ I already tried boot the recovery through fastboot but its just transfer the recovery.img and not boot.