Database Users

Fastboot mode - no boot or recovery img **help**

Hi
I've searched for a solution but didn't find one for my problem so...
I was trying to flash an updated kernel through Kernel Manager application and then it said it cannot complete task and asked me to reboot system.
I then entered into the recovery and flashed the kernel manually.
When rebooted system I got the message "FASTBOOT MODE - NO BOOT OR RECOVERY IMG" in red at the top of the bootloader.
So naturally I thought maybe it lost the recovery so I went and flashed CWM recovery 3.0.2.5 (had 3.0.2.4 when all this happened) through fastboot and that went OK.
I then entered the recovery to make sure the recovery flashing went OK and pressed Restart system now.
But then it started the bootloader and the same message appeared "FASTBOOT MODE - NO BOOT OR RECOVERY IMG" in red at the top of the bootloader.
I repeated that process few times and same thing.
The strange thing is when I select "REBOOT BOOTLOADER" and it boots into bootloader I see "FASTBOOT MODE" in red at the top. But when I try to reboot the phose I see the message to the top again.
How can I get out of this?

Hi guys,
I've got the same problem, although I don't know if it IS a problem.
I'm running v7.0.0-NS and I'm going to upgrade to v7.0.3 ... just searching for instructions!!!
~AndrewGoldy

since I am able to enter the recovery Im trying to restore an earlier backup. Not sure it this will do anything since my problem is in the bootloader area.
If this makes my phone to start up normally then I really dont understand this.

*** I think that I've just fixed it ***
I opened up "Rom Manager v4.2.0.2", and then selected the option to "Flash ClockworkMod Recovery"
Once it had downloaded "ClockworkMod Recovery v3.0.2.4", I selected the option to "Reboot into Recovery".
That worked.
It now says "Fastboot Mode" when I boot into the Bootloader.
Success!!!! (I think)

Well it just finished restoring the backup.
It seems it solved the problem on mine to since it passed the bootloader and the boot animation is on.
I really cant understand this.

I've done the same but the Recovery Stil nor Bootloader works. However it does say Fast boot mode now instead of no boot or recovery img. But still can't flash or back up a rom!
Correction i got it work after flashing to oldest recovery that was an option

I fixed this problem (Nexus S) by reverting to an older (3.0.2.4) CMRecovery, just go down to the last option "All ClockworkMod Recoveries" and Flash an older version (mine was not working with 5.0.2.0).

Hi! Anyoane can help me ?
I disconnected by accidently the USB cable while the phone was at the ClockWorkMod Recovery v5.0.2.0/-mounts and storage/-mount USB storage, and after that ( adb , fastboot and usb died).
I installed Stock OTA 2.3.6 I9023 for my Nexus S I9023. During the day phone closed and no longer wanted to open (even replace the battery). After more hours the phone is open , adb and usb works not for a long time after several attempts ( during this time I managed it to root and install CWM 5.0.2.0 back)
I flashed ICS Kwiboo v3 . After reboot the phone began to froze , and shortaly closed.
Because the phone will no longer open I tried in CWM all ( wipe data:fact, wipe cache, wipe dalvik, format/all ) .
Now if reboot system on CWM I have Fastboot Mode - No Boot or Recovery IMG
but if I reboot bootloader or power off when is opened is just Fastboot Mode .
Adb , fastboot and mount USB still no work. ( I have SDK 14 on windows7 installed, all the driver for Nexus S was updated).
Because the PC not recognized my phon I can't install another ROM or CWM.
( When USB cable connecting on the phone it's charge the battery only!).
Thanks for your advice!

No recovery img & fastboot devices -> nothing
Hi all,
When I try to access the recovery mode on my NS, I have the same "no boot or recovery img". I change my CWM version from last to 3.0.2.4 and another version too. Still, I can't access the recovery mode.
I installed the SDK to restore a stock recovery image I found, hoping to use fastboot (from the sdk + a standalone version I found before). But it won't recognize my phone (fastboot devices -> nothing). I installed the PdaNet for the Android 1.0 driver, and the Android 4.0 driver from the SDK. Still nothing, although "adb devices" apparently sees my phone.
I've spent my whole night on this. Without recovery I can't backup, and I can't switch rom (heard of this ICS rolling-out ? I'd like to have some flavour of it), I can't wipe or whatever.
Please can someone point me to a solution for fastboot to see the phone, or even better, to reinstall a recovery tool ?
Thanks a huge lot
S

saychand said:
Hi all,
When I try to access the recovery mode on my NS, I have the same "no boot or recovery img". I change my CWM version from last to 3.0.2.4 and another version too. Still, I can't access the recovery mode.
I installed the SDK to restore a stock recovery image I found, hoping to use fastboot (from the sdk + a standalone version I found before). But it won't recognize my phone (fastboot devices -> nothing). I installed the PdaNet for the Android 1.0 driver, and the Android 4.0 driver from the SDK. Still nothing, although "adb devices" apparently sees my phone.
I've spent my whole night on this. Without recovery I can't backup, and I can't switch rom (heard of this ICS rolling-out ? I'd like to have some flavour of it), I can't wipe or whatever.
Please can someone point me to a solution for fastboot to see the phone, or even better, to reinstall a recovery tool ?
Thanks a huge lot
S
Click to expand...
Click to collapse
I can help you but....
1. In bootloader mod ADB working ? (if not try back off battery for 10 min or more) and try again..
2. Your device is rooted ?

I was going to suggest trying to reflash the latest recovery again in CWM, but I think you guys said that hasn't worked.
Every now and then when I flash a new ROM this happens to me. I usually just flash an older version, then reflash the newest version and the Recovery works just fine.
Maybe try using a different recovery program?

it does work, many have done it already, see all the duplicated topics
Sent from my SGH-T989 using xda premium

Thank you guys for your replys.
surdu_petru said:
I can help you but....
1. In bootloader mod ADB working ? (if not try back off battery for 10 min or more) and try again..
2. Your device is rooted ?
Click to expand...
Click to collapse
1. I removed the battery for 10mn. When I come back to the bootloader "ADB devices" doesn't return a device, so it doesn't see my phone. But when switched on, it can see it.
2. Yes, it is. There is the SuperUser app, and when apps ask for root, I can allow or deny. And the lock state is 'unlocked'
akabadnews said:
I was going to suggest trying to reflash the latest recovery again in CWM, but I think you guys said that hasn't worked.
Every now and then when I flash a new ROM this happens to me. I usually just flash an older version, then reflash the newest version and the Recovery works just fine.
Maybe try using a different recovery program?
Click to expand...
Click to collapse
I tried the latest, the oldest, the versions inbetween... nothing. I have the latest version of CWM and I reflashed the last Recovery from the app.
I can't flash another ROM, because I need recovery mode for that ; and my problem is that I can't access recovery indeed... :/ I feel like I need A to do B, and B to do A.
"No boot or recovery img": doesn't it mean that I should put some file somewhere ? I hope it would be that simple.
Do you have other ideas ?
---------- Post added at 01:33 PM ---------- Previous post was at 01:24 PM ----------
AllGamer said:
it does work, many have done it already, see all the duplicated topics
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I've tried several time, flashing different versions of CWM recovery. I've returned to bootloader -> recovery dozens of time and I still have the "no boot no recovery img". I'll try again.
All the threads which speak about it and mention to flash another rom -> yeah thanks, but I can't access recovery
Threads mentioning fastboot -> I tried with different drivers (including 1.0 and 4.0), but fastboot won't see/talk to my device
Do you see something else that I didn't try ?
---------- Post added at 02:16 PM ---------- Previous post was at 01:33 PM ----------
I also tried this which seems to be a good step
http://forum.xda-developers.com/showthread.php?t=1356319
Basically it says
adb shell
SU
flash_image recovery /sdcard/filename.img
But like the guy in thread, I have memory errors "mtd: read error at 0x00000000 (out of memory)" then write errors, then "failed with error: -1" and "error writing recovery"

It's ok now.
In case other it can help other people:
I tried again the PDAnet installation to get the android 1.0 drivers. (actually there is a binary called "install legacy usb drivers" which apparently worked well.)
Fastboot would detect my phone in bootloader mode.
So I could "fastboot flash recovery xxx.img" I first failed with a stock recovery, but for which I didn't know the exact reference and origins (I was stuck with the exclamation point in white triangle). As I couldn't find another stock recovery for Nexus S, I downloaded the CWM recovery from the website (not from the app), last version (5.0.2.0) and flashed it with fastboot.
It seems to work properly now, so i'm doing a rom backup, just in case for later, and I'll flash stock ICS
FYI: rom manager only caused me issues ; I don't know why Cyanogen uses it. Just use the recovery directly from recovery... Even CWM. just not Rom Manager.
Cheers and thanks to those who tried to help.
++

saychand said:
It's ok now.
In case other it can help other people:
I tried again the PDAnet installation to get the android 1.0 drivers. (actually there is a binary called "install legacy usb drivers" which apparently worked well.)
Fastboot would detect my phone in bootloader mode.
So I could "fastboot flash recovery xxx.img" I first failed with a stock recovery, but for which I didn't know the exact reference and origins (I was stuck with the exclamation point in white triangle). As I couldn't find another stock recovery for Nexus S, I downloaded the CWM recovery from the website (not from the app), last version (5.0.2.0) and flashed it with fastboot.
It seems to work properly now, so i'm doing a rom backup, just in case for later, and I'll flash stock ICS
FYI: rom manager only caused me issues ; I don't know why Cyanogen uses it. Just use the recovery directly from recovery... Even CWM. just not Rom Manager.
Cheers and thanks to those who tried to help.
++
Click to expand...
Click to collapse
THANKS! This helped A TON!
I did the PDA installation again, and for some reason this seemed to fix my inability to access recovery.
Agreed on Rom manager, I updated CWM through rom manager and I believe that's what buggered up my recovery, as I have never had trouble accessing it before I did that.
But again, a big THANKS for that suggestion!

[Q] N4 Soft-Bricked - NRT Not Helping

So I wanted to try Cataclysm, but was having issues switching to it from PA. It always kept booting into PA so I decided to do a full wipe. I did a full app backup and a nandroid backup using NRT. I first tried a regular factory reset, but eventually decided to wipe everything, even /system (a mistake, I now see). After I did that, I tried using NRT to flash stock + unroot. The NRT script gets through everything fine until it gets to the terminal part and says there's no 'boot.sig', 'recovery.sig', or 'system.sig'. It also fails the baseband version check. Don't know if it's even relevant, but it says something failed so I thought I'd include it. After that it tells me it will look like it's boot looping, but it just sticks in fastboot mode. If I wait 20 minutes nothing happens. If I push START it hangs on the Google screen but never gets any further, even 30 minutes later. I've tried pushing a custom zip and install in in TWRP. I've tried flashing a new kernel. Whatever I try I cannot seem to get any further than the boot screen. At this point I'd be happy with stock. I just want my phone back. What do I do?

I'm assuming NRT is a toolkit?
From here on, don't use a toolkit if you know how things work. Manual is the way to go.
Boot into fastboot, choose recovery, go into TWRP, advanced, ADB SIDELOAD.
Now use command prompt or terminal on your computer (depending on your OS), navigate to where you installed your toolkit, there should be a .exe or .sh called adb and fastboot.
Download your preferred rom and gapps, transfer it to this folder.
Now simply do a command "adb sideload *zipname*.zip " and it should transfer and flash your phone.
Don't flash a kernel yet, wait till you finish your first boot, then only you flash it.

I tried exactly what you said to flash the stock image. The terminal said it had transferred 100%, but TWRP said the sideload failed.

Hamalot said:
I tried exactly what you said to flash the stock image. The terminal said it had transferred 100%, but TWRP said the sideload failed.
Click to expand...
Click to collapse
that's because you can't flash the stock image like that.
Download CM and try.

It worked! Thank you so much!

[Q]LG G2 re-flashing or rooting stock 4.4.2 bad rom

Hi all,
First off I've tried now for a two days to solve this, reading as much as I could find on here and the rest of the internet.
I decided to root my LG D802 running 4.2 and install CWM recovery no problem. Next I flashed a stock 4.4.2 vodaphone img. All went well untill i tried to use the touch screen, which shows that when i press on one point on the screen it selects multiple points basically its unusable and unable to do almost anything with it, however i have managed to turn on ADB and connect to the phone. So now i have a stock recovery and an unusable ROM.
So next up I tried to rooting it since I had ADB shell working ok, using the IOROOT25. This appears to work as when it reboots and installs the kkroot.zip in the recovery it's saying it worked. Now when I reboot and open ADB shell then type SU to get root I can't press ok when superuser pops up to asking me to give it permission, because of the touch screen problem.
If i can get root in ADB then remount the files system then i will be able to DD a new recovery img??
After getting this far and loosing, I then found this: http://forum.xda-developers.com/showthread.php?t=2432476 on flashing to stock, but the program crashes every time it's about to flash, so i tried doing a fresh install of windows 7 and then tried windows 8 however the program still crashes every time and yes I have followed the instructions and tried the manual method and checking the 127.0.0.0. lgblahblah is there
So no I am turning to you guys for help.
phone details;
Model: D802 32GB
Firmware operator: VDF
sw version: D80220a
ro.build.fingerprint: lge/g2_vdf_com/g2:4.4.2/KOT49I.D80220a/D80220a.1392133741:user/release-keys
Recovery: <3e> KOT49I.D80220a test-keys

UPADATE: I have root but getting this error when trying to flash the recovery:
+] loki_flash v2.0
[-] Loki aboot version does not match device.
any ideas?
Ok so i found a different aboot img pushed to the phone and flashed that using dd
Code:
dd if=/data/local/tmp/about.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
this solved the problem above and a allowed me to flash cwm recovery. This then broke the installed rom so it wouldn't boot. now I had a custom recovery i flashed a EUR open 16gb stock zip this all went well and now i have a working phone What i should of done is remove the stock recovery.img from the zip and the line to flash it in the update script so it didn't flash the stock recovery.
This now leaves me with the loki flash problem above when trying to flash a custom recovery i could flash a different aboot.img but i don't want to break the current rom.
Any one else found a way to solve this problem?

need help
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB

Mustafa1 said:
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB
Click to expand...
Click to collapse
Have you tried running IO root to again root on your device? Also do you know much about linux, command line and android tools like ADB? Or do I need to explain the commands step by step?

twon23 said:
Have you tried running IO root to again root on your device? Also do you know much about linux, command line and android tools like ADB? Or do I need to explain the commands step by step?
Click to expand...
Click to collapse
i downloaded ioroot25 and extracted it and ran root.bat
Looking for device...
Make sure drivers are installed. Check Windows Device Manager.
Make sure proper USB Debugging mode is enabled.
Verizon users make sure ethernet mode is selected.
Did you check phone screen for Yes/No prompt?
(select checkbox to always remember then hit yes)
...sometimes you need to unplug the USB cable then re-plug.
Determining device model...
Rebooting into stock recovery...
When recovery loads, select: *apply update from adb* with power button...
then press Enter/Return on your keyboard.
Press any key to continue . . .
(here the phone restarts and LG logo appears with (secure booting error)message in the upper left corner, and when i press any key)
Reboot back into System after flash in recovery finishes.
Press any key to continue . . .
and when pressing any key the cmd closes and the phone stays on with black screen and the back light on
in the pc i get many windows about formating drives (from H to S)
and i dont know anything about linux or command line
would you explain it to me??

Ok so your phone not longer boots, correct? Do you know what build/version plus any other details of the rom you flashed? or even a link so i can have a look at the rom you have installed. Can you get into recovery mode and is it still a stock recovery image? also what is your phone d802? 16gb 32gb?

Mustafa1 said:
i downloaded ioroot25 and extracted it and ran root.bat
Looking for device...
Make sure drivers are installed. Check Windows Device Manager.
Make sure proper USB Debugging mode is enabled.
Verizon users make sure ethernet mode is selected.
Did you check phone screen for Yes/No prompt?
(select checkbox to always remember then hit yes)
...sometimes you need to unplug the USB cable then re-plug.
Determining device model...
Rebooting into stock recovery...
When recovery loads, select: *apply update from adb* with power button...
then press Enter/Return on your keyboard.
Press any key to continue . . .
(here the phone restarts and LG logo appears with (secure booting error)message in the upper left corner, and when i press any key)
Reboot back into System after flash in recovery finishes.
Press any key to continue . . .
and when pressing any key the cmd closes and the phone stays on with black screen and the back light on
in the pc i get many windows about formating drives (from H to S)
and i dont know anything about linux or command line
would you explain it to me??
Click to expand...
Click to collapse
If you're running root.bat as an admin, try executing it without admin privileges. Dunno why, but it seemed to work for me.

Mustafa1 said:
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB
Click to expand...
Click to collapse
Did you try to flash CWM recovery? http://forum.xda-developers.com/showthread.php?t=2582142 This thread has What you need to do .. After then you can nandroid backup after then wipe everything except EFS on twrp after that you can stock_kitkat.zip on the xda forum. Efter that restore data via twrp.
I think that It will be correct without deleting your current rom ...
---------- Post added at 06:18 PM ---------- Previous post was at 06:12 PM ----------
makgun said:
Did you try to flash CWM recovery? http://forum.xda-developers.com/showthread.php?t=2582142 This thread has What you need to do .. After then you can nandroid backup after then wipe everything except EFS on twrp after that you can stock_kitkat.zip on the xda forum. Efter that restore data via twrp.
I think that It will be correct without deleting your current rom ...
Click to expand...
Click to collapse
NOT CWM , it is TWRP
Are you from turkey?

twon23 said:
UPADATE: I have root but getting this error when trying to flash the recovery:
+] loki_flash v2.0
[-] Loki aboot version does not match device.
any ideas?
Ok so i found a different aboot img pushed to the phone and flashed that using dd
Code:
dd if=/data/local/tmp/about.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
this solved the problem above and a allowed me to flash cwm recovery. This then broke the installed rom so it wouldn't boot. now I had a custom recovery i flashed a EUR open 16gb stock zip this all went well and now i have a working phone What i should of done is remove the stock recovery.img from the zip and the line to flash it in the update script so it didn't flash the stock recovery.
This now leaves me with the loki flash problem above when trying to flash a custom recovery i could flash a different aboot.img but i don't want to break the current rom.
Any one else found a way to solve this problem?
Click to expand...
Click to collapse
Hi! I've recently flashed an updated stock ROM and have the same Touchscreen issue as yourself! Can you tell me the steps you have done to fix it? I'm using windows 8.1 to flash etc, and using a stock ROM I can't seem to get it to work again

[Q] Bricked?

Hopefully someone can help me here.
I have the N10 and it is rooted. I flashed the stock recovery and flashed the stock kernel.
So I should have been pretty much stock cause I had the 4.4.4 factory image on it except it was unlocked.
So then I let it do the OTA for lollipop.
When it rebooted into recovery it got about 1/3 and then hit an error (just said error).
Now I can only get it to the recovery screen and the reboot Mode Flag is 'Recovery'
The only thing I can do at that point is hit the power button and it reboots to recovery with a "No Command" error.
Help please!
EDIT: The thing finally booted up on it's own. Should I leave it alone or try to take the OTA update again?

sl2222 said:
Hopefully someone can help me here.
I have the N10 and it is rooted. I flashed the stock recovery and flashed the stock kernel.
So I should have been pretty much stock cause I had the 4.4.4 factory image on it except it was unlocked.
So then I let it do the OTA for lollipop.
When it rebooted into recovery it got about 1/3 and then hit an error (just said error).
Now I can only get it to the recovery screen and the reboot Mode Flag is 'Recovery'
The only thing I can do at that point is hit the power button and it reboots to recovery with a "No Command" error.
Help please!
EDIT: The thing finally booted up on it's own. Should I leave it alone or try to take the OTA update again?
Click to expand...
Click to collapse
Same for me. I'm trying to even manually flash the factory image, but it will not detect fastboot. I'm trying to research this now. The device just keeps restarting itself over and over into No Command.

IT Rider said:
Same for me. I'm trying to even manually flash the factory image, but it will not detect fastboot. I'm trying to research this now. The device just keeps restarting itself over and over into No Command.
Click to expand...
Click to collapse
Hi, I have exactly the same problem after installing Android 5.0 OTA. Please post a solution here if you find it. Thanks!

I didn't try the OTA again. I installed Lollipopalooza from this thread...
http://forum.xda-developers.com/showthread.php?t=1998585
No problem with it so far

sl2222 said:
I didn't try the OTA again. I installed Lollipopalooza from this thread...
http://forum.xda-developers.com/showthread.php?t=1998585
No problem with it so far
Click to expand...
Click to collapse
But I cannot flash any rom as none of ADB commands can be run (device is not connected, though I connected it with OEM cable). I tried factory reset but it didn't help.

Just wanted to share what worked for me after the OTA update failed and flashing stock images didn't work. Put the tablet in fastboot. Installed stock image, tablet wouldn't boot. Restarted went into recovery got the android on its back with the red x coming out of it (did not say bad command at thia point). I presses volume up and power at the same time on this screen. Cleared cache and rebooted then the tablet booted up.

I cannot believe companies still get away with this inadequate device "killing" type of software. Did no-one at the company do any testing before release?????
Rant over, onto solution - for me anyway.
The issue I had was that I could not get ADB to be of any use so switched to fastboot. Should have used fastboot from the getgo. Hohum.
So, into recovery with android on it's back with red triangle and reboot into fastboot.
Connect N10 to PC with USB cable.
Downloaded "Minimal ADB and Fastboot"(MAF)
Downloaded Lollipop for Nexus 10 - image-mantaray-lrx21p.zip and saved to c: drive (this saves loads of typing at command prompt)
File path for update is c:\image-mantaray-lrx21p.zip
Open MAF and ensure folder path points to your MAF install folder..
At command prompt type fastboot update c:\image-mantaray-lrx21p.zip
If you want to wipe device prior to update then type fastboot -w update c:\image-mantaray-lrx21p.zip
This may take a while so go make a drink - or something.
If all goes well, mine did, you should eventually be presented with the lollipop opening screen and a working device.

Just finally got it working!
ROM updates from ADB Sideload or Fastboot failed every time for different reasons.
What I had to do is to flash custom recovery (latest TWRP) with "fastboot flash recovery <recovery.img>" command.
From TWRP flashing the official ROMs also failed. But flashing Lollipopalooza as sl2222 suggested finally succeeded.
Thanks for all the help!

Download Mode Recovery on H918

After installing twrp using the one click root method, it restarted my V20 and I ended up in recovery mode (TWRP) and unable to boot into the OS. It seems I only have access to fastboot, download mode, and TWRP at this moment. I tried flashing the partitions with twrp, but twrp isn't realing my SD card for some odd reason, and I don't believe theres another way to move the file directly to the phone. I've been trying to work with "LG FlashTool" for hours, and keep getting the same error. Is there a reliable way to flash the OS through download mode? Thanks!

There is currently no way to flash those .tot images. What happens when you try to boot, where does it get stuck?
In TWRP you can connect to a PC and access the storage. Did you try moving the files that way?

slayerh4x said:
There is currently no way to flash those .tot images. What happens when you try to boot, where does it get stuck?
In TWRP you can connect to a PC and access the storage. Did you try moving the files that way?
Click to expand...
Click to collapse
I apologize for not checking my XDA notifications frequently enough.
I was able to copy over the .img system, boot, and recovery files to my internal storage when I was booted into TWRP then flashed them in TWRP.
Thanks for the help!

KingofPineCones said:
I apologize for not checking my XDA notifications frequently enough.
I was able to copy over the .img system, boot, and recovery files to my internal storage when I was booted into TWRP then flashed them in TWRP.
Thanks for the help!
Click to expand...
Click to collapse
I tried doing this and my system rebooted back into TWRP. Where did you get the files? Also did you ever get the encryption unsuccessful error? Whenever I install a system image or nandroid backup my phone reboots into TWRP.

crazyc78 said:
I tried doing this and my system rebooted back into TWRP. Where did you get the files? Also did you ever get the encryption unsuccessful error? Whenever I install a system image or nandroid backup my phone reboots into TWRP.
Click to expand...
Click to collapse
The encryption unsuccessful error was mentioned in the original TWRP form, you're just supposed to tap cancel and ignore it. It seems to happen every time you boot into TWRP. As for the .IMG files, I forgot where I got these but as soon as I find the post I'll be sure to give the creator credit. These worked perfectly for my H918.
Link to .zip file with the .img file-
https://drive.google.com/file/d/0B53iMlcsyyiKenAtT2k5STl0Umc/view?usp=drivesdk
(On mobile app or else I would've embedded it)
Boot into TWRP and push them through ADB into your device, then flash with TWRP. Make sure to flash system and recovery together, THEN REBOOT. If you flash system or recovery apart then reboot it might not work. I pushed them to /data/ and it worked for me. system.img is about 4GB if I remember correctly, so that one took a long time to push through ADB, about an hour and a half, just be prepared to wait a bit. Good luck!

KingofPineCones said:
The encryption unsuccessful error was mentioned in the original TWRP form, you're just supposed to tap cancel and ignore it. It seems to happen every time you boot into TWRP. As for the .IMG files, I forgot where I got these but as soon as I find the post I'll be sure to give the creator credit. These worked perfectly for my H918.
Link to .zip file with the .img file-
https://drive.google.com/file/d/0B53iMlcsyyiKenAtT2k5STl0Umc/view?usp=drivesdk
(On mobile app or else I would've embedded it)
Boot into TWRP and push them through ADB into your device, then flash with TWRP. Make sure to flash system and recovery together, THEN REBOOT. If you flash system or recovery apart then reboot it might not work. I pushed them to /data/ and it worked for me. system.img is about 4GB if I remember correctly, so that one took a long time to push through ADB, about an hour and a half, just be prepared to wait a bit. Good luck!
Click to expand...
Click to collapse
Thanks I appreciate the response, I was able to get my phone up and running by flashing a deodexed rom.

What are the commands to flash the stock system, boot image and recovery through fastboot? Is that what you used?

KingofPineCones said:
The encryption unsuccessful error was mentioned in the original TWRP form, you're just supposed to tap cancel and ignore it. It seems to happen every time you boot into TWRP. As for the .IMG files, I forgot where I got these but as soon as I find the post I'll be sure to give the creator credit. These worked perfectly for my H918.
Link to .zip file with the .img file-
https://drive.google.com/file/d/0B53iMlcsyyiKenAtT2k5STl0Umc/view?usp=drivesdk
(On mobile app or else I would've embedded it)
Boot into TWRP and push them through ADB into your device, then flash with TWRP. Make sure to flash system and recovery together, THEN REBOOT. If you flash system or recovery apart then reboot it might not work. I pushed them to /data/ and it worked for me. system.img is about 4GB if I remember correctly, so that one took a long time to push through ADB, about an hour and a half, just be prepared to wait a bit. Good luck!
Click to expand...
Click to collapse
So I downloaded this file you have in the reply... How can I flash the files in the zip through Fastboot? This currently is the only thing I can boot into to modify the system. The phone boots fine, but I cannot use ADB because it won't authorize the device. I have repeatedly tried killing the ADB server and restarting it, changed the USB ports to no avail... At this point, I cannot boot into TWRP even though it should be operational still.

andrewjt19 said:
So I downloaded this file you have in the reply... How can I flash the files in the zip through Fastboot? This currently is the only thing I can boot into to modify the system. The phone boots fine, but I cannot use ADB because it won't authorize the device. I have repeatedly tried killing the ADB server and restarting it, changed the USB ports to no avail... At this point, I cannot boot into TWRP even though it should be operational still.
Click to expand...
Click to collapse
Which TWRP version do you have? Is it RC8 or above? If its not then you are stuck until the TOT files can be used in LG UP or if we get a KDZ (Havent checked recently if a KDZ is available).
If you do there is a fail safe in TWRP (RC8 and above) that you boot to the LG factory reset and go through with it, TWRP does not execute the command and just boots to TWRP.

DarkestSpawn said:
Which TWRP version do you have? Is it RC8 or above? If its not then you are stuck until the TOT files can be used in LG UP or if we get a KDZ (Havent checked recently if a KDZ is available).
If you do there is a fail safe in TWRP (RC8 and above) that you boot to the LG factory reset and go through with it, TWRP does not execute the command and just boots to TWRP.
Click to expand...
Click to collapse
I'm running the latest version of TWRP not the RC8.

andrewjt19 said:
I'm running the latest version of TWRP not the RC8.
Click to expand...
Click to collapse
ONLY USE THIS METHOD IF YOU HAVE TWRP RC8 OR ABOVE INSTALLED!!!!! OTHERWISE YOU WILL ACTUALLY FACTORY RESET YOUR DEVICE!!!!!
While the device is powered off, press and hold Vol - and Power button. When you see the LG logo quickly release only the power button and re-press and hold the power button (Never let go of the Vol - button) This will boot you into the LG Factory reset screen. ONLY USE THIS METHOD IF YOU HAVE TWRP RC8 OR ABOVE INSTALLED!!!!! OTHERWISE YOU WILL ACTUALLY FACTORY RESET YOUR DEVICE!!!!! Choose yes to both options and you will be rebooted into TWRP. TWRP intercepts this command and ignores the factory reset part.

Will definitely give a shot. Thanks. I'll report back when I get to do it...

what are commands to flash the sys files