Develop Bugs

Error when restoring Nandroid

Hi
I'm getting this error when I try to restore:
Code:
Error : run 'nandroid-mobile.sh restore' via adb!
So I tried to restore it through adb.
But then I get this error message:
Code:
"error: unable to mount /system, aborting
/sdcard/nandroid/SH0CJPL05354/BCDAS-20110610-1442"
The thing is it worked the first time I tried it but it won't work anymore and since I've wiped, I can't boot up at all. I can only access Recovery and the Bootloader
I always wipe before restoring and for what it's worth, I had to restore in the first place because I flashed the Bravo Sense hboot.
I'm AmonRa 2.0.1
Alpharev S-Off

Seems like /system is not mounted? Try
Code:
adb remount
then have another go?

stringer7 said:
Seems like /system is not mounted? Try
Code:
adb remount
then have another go?
Click to expand...
Click to collapse
Is that right after I load the adb shell?
If so I'm getting this when I do adb remount:
Code:
/sbin/sh: adb: not found
I think I'm doing it wrong.

Ok, try to get your PC to recognise your device using
Code:
adb devices
There is s good guide on installation and use here:
http://forum.xda-developers.com/showthread.php?t=879701

stringer7 said:
Ok, try to get your PC to recognise your device using
Code:
adb devices
There is s good guide on installation and use here:
http://forum.xda-developers.com/showthread.php?t=879701
Click to expand...
Click to collapse
The phone is listed under adb devices and I have successfully located the nandroid on my sdcard using adb, it's just the restore fails as above. (Interestingly, it lists the phone under adb devices when I'm in Recovery but it won't do so when I'm in the bootloader screen.)
Anyway, this is what I'm getting with adb remount:
Code:
C:\>adb remount
remount failed: invalid argument
What would suggest from here?
Thanks for helping out, btw. It's very very much appreciated

Ok so you currently have s-off, RA recovery, access to bootloader and recovery, but no working rom and a nandroid backup that won't restore - that right?

stringer7 said:
Ok so you currently have s-off, RA recovery, access to bootloader and recovery, but no working rom and a nandroid backup that won't restore - that right?
Click to expand...
Click to collapse
If it was me I would wipe everything (I know you did already but just to be sure) download fresh version of the rom to your sd via PC, insert in phone and flash it through recovery. That gets you a functioning phone at least!
Then work on the restore issue. The backup was made with the same version of RA that you are currently using I assume? I'm not sure where to go with it really, and hope someone with more knowledge will pitch in...!

Something like that has already happened to me twice. First, I was running low on sd space. Second, my recovery was corrupted somewhat: fixed by reflashing the same recovery. Hope this helps you in troubleshooting.

stringer7 said:
If it was me I would wipe everything (I know you did already but just to be sure) download fresh version of the rom to your sd via PC, insert in phone and flash it through recovery. That gets you a functioning phone at least!
Then work on the restore issue. The backup was made with the same version of RA that you are currently using I assume? I'm not sure where to go with it really, and hope someone with more knowledge will pitch in...!
Click to expand...
Click to collapse
I managed to get it sorted. A guy on another forum mentioned this exact same solution. Which means props to you too.
Thanks for the help.

You are welcome!
Remember to pass it on and help where you can...

sak01 said:
I managed to get it sorted. A guy on another forum mentioned this exact same solution. Which means props to you too.
Thanks for the help.
Click to expand...
Click to collapse
Post the solution here to help other people.

^^sorry I missed your post.
It's this solution posted by stringer7 earlier
stringer7 said:
If it was me I would wipe everything (I know you did already but just to be sure) download fresh version of the rom to your sd via PC, insert in phone and flash it through recovery. That gets you a functioning phone at least!
Click to expand...
Click to collapse
Or as Rastaman over at AF put it:
if youve wiped, try and flash a new rom without restoring nand and see if it rebuilds the system partition
once done see if a nand restore will work (although it was done without ext :/)
Click to expand...
Click to collapse
So basically, flashing a new rom rebuilds the system partition and then the nand restore works.

if so, would be usefull to restore without the boot.img from nandbackup.
never used nandbackup, i have ridden that was availaible through some advanced features from nand restore on amonRA
this is a point already raised early by someone named Brandall

[Q] CWM Bootloop w/ v5.8.2.0

Long story short im a newb, im sorry for creating a new thread but ive exhausted my efforts looking for a solution to the problem im having. When the problem occured i had restored my original cwm backup that i created when first rooting my phone. I then did a factory wipe and reinstalled cwm and flashed my recovery. I went to install cm9 4-4-12 and i got a pop up that firmware update was available i clicked update system now and got sent to cwm recovery. Every time since then i cannot reboot into the android os, pulling battery. It doesnt matter what i do, ive tried to use a flash recovery zip i found in another thread to exit boot loop. Ive also tried restoring my original back ups and my recent back ups. I have the android sdk installed but having trouble getting adb to work not sure if i should go about trying to fix the recovery or trying to restore phone to its original state either way i think i need to get adb working before i can do either one. Any help is appreciated and im sorry if im wasting your time.

Did you try wipe cache, wipe dalvik cache, factory reset before flashing CM9?

Yes. The order i took was Wipe data/factory reset> Wipe cache partition> wipe dalvic cache> installed cm9 zip> installed gaps zip. still nothing got adb to work not doing much with it i know it has root access and when i got the state of the device it came up as unknown although im pretty sure im in recovery mode.

ok a few question and maybe a step by step to help you since i had a same promblem with a bad flash of CM9
1A. Can you boot into Recovery ? if not i can help you reflash your phone with the Kdz files took me forever to get it to work but i finilly found all the files needed.
1B. if it does boot into recovery run adb devices ... does it show the phone in recovery mode ? in the list.
If so then you can Download the following 6 files Dropbox Down link its not mine but was posted in another Nitro Recovery topic i will give credits once i re go threw the topic to see the poster
- recovery.img
- system.img
- baseband.img
- boot.img
- firmware.img
- pushall.bat
in your CWM recovery go to mounts or it may be under advanced and turn on usb mass storage and as long as all of those files are in your adb folder you can run the pushall.bat and it will place them on your sdcard.
After that turn off usb mass storage and run adb devices again to make sure you phone is still showing up. If so run these commands
Adb shell
****** notice the SU command isnt used here**** cant get super user in recovery but it will still let you run the commands and i can confirm it does work
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
You won't be able to issue a reboot command, so just hold power down on your phone til it's off and hold the volume down button so that it comes back up in factory data reset mode. You will want to pull your sdcard at this time if you don't want your data erased.
Hit power twice and your phone should go through its reset process and (hopefully!) come back up in a working (and rooted) AT&T "stock" rom
if not then try to follow this for the CM9 Adb Drivers Wiki for CM adb drivers i know its a little work but it dose the trick then go back up to the previous step and try that to get to stock rooted
i dont think i left anything out but i can help with anything else i know if that doesnt get you back up and running.
Credits to ???? for the drop box link with the godly files for our nitro
and to Malnilion for his guide on unbricking the nitro

edit: re-ran superoneclick for run and it worked! I should be good from here

Got everything to work. Wait spoke to soon tried to reinstall firmware update again got the same problem. oh well guess i should done fw update before installing cwm. Thanks for the help i should be able to repete this problem in the case of another brick... which just occured.

So after going through the process of unbricking my phone a second time my phone was rebooted into software update screen. Updating firmware then software and did not have to go through factory reset. Strange...

I pushed all images to my device via adb,but ota update gets an error when trying to install. At least its not bricked. Anyone know of another method?
Sent from my LG-P930 using XDA

lg nitro in recovery loop
toki, I tried your fix, but, it comes up /sdcard/boot.img is not found. any suggestions?

Tokie the dropbox links are not working

reverendyummypants said:
toki, I tried your fix, but, it comes up /sdcard/boot.img is not found. any suggestions?
Click to expand...
Click to collapse
re push the img file back to the sdcard
adb push boot.img /sdcard/ make sure that he boot.img file is in the same folder as your adb and then try the dd command for it it happened to me once
EdwinXVS said:
Tokie the dropbox links are not working
Click to expand...
Click to collapse
im uploading to my own dropbox bare with me ill posyt a live link as soon as it ready guys

cwm recovery loop
_Tokie, retried. still dd command cannot be done. file not found. The files ARE IN the adb folder. Not sure what else to do.

when you type adb push boot.img /sdcard/ what does it say ? i dont see why it will do the rest and not that one

dd: can't open sdcard\boot.img : no such file or directory

i was asking about when you pushed the boot.img to teh sdcard... if yyou want i can look at it threw teamviewer total up to you ... if you deside that pm me then info for it

Just take the SD card out and into your computer (assuming you have a card reader) and copy the files to it manually.

drumist said:
Just take the SD card out and into your computer (assuming you have a card reader) and copy the files to it manually.
Click to expand...
Click to collapse
im going to assume that he is booting into CWM its thats the case with teh usb cable hooked to the computer he can turn on mass storage from the CWM and just tranfer it that way .. if he doesnt have a reader .. i just dont see why its not copying the boot image

I'm sorry. The files are on the sdcard. When it comes time for the dd command, i get that error which i recently posted.

If you're in CWM you have to ensure your sdcard is mounted. I have got caught up on this step as well lol

Thank you to all that helped! XDA is awesome! Everything is back to normal. It also helps to have the right / or \ lol

[Q] No recovery anymore, Phone OK

In the process of trying to flash a new firmware to a GIO I somehow managed not to be able to acess the recovery menu anymore. Right now the Phone is rooted, booting fine into stock ROM, download mode is working but no recovery menu. While trying to boot with power and home button it just shows the Samsong logo for ages.
I tried to flash a new recovery several times due to the fact that the stock recovery is only able to apply update.zip and not able to select any custom filename. So I installed su and a new recovery this way. After realizing that there is no recovery anymore I did it using ODIN and download mode. I tried several recovery images from cwm to stock, but everytime the same.
What did I miss?
How to do a dalvik/cache reset outide revovery menu and not doing a full hard reset?
Would a hard reset help?
TiA,
longInt

Guess their are commands to do it with ADB, phone can still go on so thats fine
Download adb
Connect phone to pc
Open command prompt , cmd.bat
Type
Adb
Su
Reboot recovery
Try if it works...
You can also flash recovery with ODIN, cwm v5 can be flashed with odin
Sent from my GT-S5660 using xda premium

I did already
Flashed cwm-5.0.2.7-ext4+rfs-odin.tar.md5 using ODIN without problems, but as I said, no recovery menu available/accessible. BTW: Do I've todo anything after ODIN triggered the reboot? I just remove the phone and try to access recovery menu...
I do not have adb available at the moment, Sorry. Will try tommorow, but I guess this will not show something different!?
Thx!

Terminal emulator?
Code:
su
Reboot recovery
Sent from my HTC Sensation

OK; will try the Terminal emulation soon. But also when trying "Reboot to recovery" from inside ROM Manager it just hangs showing the SAMSUNG Logo. Did I flash the right recovery in terms of the ext4 thing?
TiA

voetbalremco said:
Adb
Su
Reboot recovery
Click to expand...
Click to collapse
This results in a black screen and the phone not booting anymore (just showing the Samsung logo). I'm pretty sure the stock rom is booting again after flashing cwm again (had this before). Doing this now...
Any other ideas, tipps?
TiA

OK, guys, time for new proposals. Whichever way I try to get into recovery it fails. Reflashing recovery brings the phone back, but how to go into recovery!? I even tried to boot recovery using my GS3 Toolkit with the same negative result just to prove there is no way to reach recovery.
Isn't there a need to flash cache and dalvik or something else after flashing recovery!? How?
TiA

Try flashing a full stock rom with odin, so everything is gone, kernel, su etc...
If still not, live with it or bring it to a service center
Sent from my GT-S5660 using xda premium

OK, thx. If someone is having additional hints/ideas please let me know . Phone is still working but still no recovery...

exact same problem
longint2 said:
OK, thx. If someone is having additional hints/ideas please let me know . Phone is still working but still no recovery...
Click to expand...
Click to collapse
I have the exact same problem as you. Same phone as you, phone rooted fine, tried installing CWM now can't get to recovery with the same symptoms as you. Holding Power+Home results in a hanging Samsung logo and no longer being able to boot at all. Removing the battery doesn't help. Reflashing allows me to boot normally but still not recovery mode (download mode accessible all the time). Rebooting from ROM manager usually results in "RAMDUMP mode arm9" instead of recovery (wtf).
Tried different CWM versions recommended for Gio, some older some newer, some with different filesystems.
Tried different methods for installing recoveries (from SD card in the original recovery mode the first time, and from ODIN)
Tried different methods of reaching recovery mode (key combination on boot, reboot from terminal, reboot from ROM manager).
Tried doing "firmware update" with (lol) Kies
Seriously no idea how to solve it, it's exactly the same as the problems in this thread. Advice from friends and these forums has so far not helped, but hopefully someone will discover an answer soon?
Things I don't think are related:
I have hardly any space left on the phone
My battery life has now been reduced to 2 hours average (woohoo!)

Have you tried installing stock rom via Odin? It installs stock recovery itself, and then you would be able to see what happens when you are trying to acces recovery

Very simple, it happened to me sometime ago. The problem was that my pc was blocking Odin to flash correctly, so I figured out the solution. The solution is to try flashing it from someone else's computer. Give it a try and tell me.
---------- Post added at 08:23 AM ---------- Previous post was at 08:17 AM ----------
Follow step by step:
Make sure you do it from a PC on which you haven't already installed Samsung USB drivers or KIES.
1. Install Samsung usb drivers.
2. Open Odin and boot phone into downloading mode.
3. Browse Gio.ops and xxxxxxxx.tar file and start flashing.
Sent from my GT-S5660 using Tapatalk 2

nope…
pakistanish said:
Very simple, it happened to me sometime ago. The problem was that my pc was blocking Odin to flash correctly, so I figured out the solution. The solution is to try flashing it from someone else's computer. Give it a try and tell me.
Click to expand...
Click to collapse
I doubt this is the problem because the first time I tried flashing CWM was not with Odin (I'm not a Windows user) but from the stock recovery as shown in the video tutorial on this forum. I think I'll try wojtek267's suggestions and reflash the stock rom when I get my USB cable back.

Tried a lot more things, none of them worked
Sorry for double-posting, but this is long.
Update:
I got a USB cable. I tried a lot of stuff that also doesn't work. That's what's covered in this post:
This doesn't work. Naturally the first part doesn't work because it says boot into recovery and I can't do that. Ignoring that and continuing from step 5 does just as little. At the bottom of this post I've written what Odin does.
This also doesn't work, it's basically the same thing.
Tried reinstalling stock ROM as suggested. No difference in results. List of ROMs I've tried at bottom of post.
Tried using Odin from a different PC, as suggested. More on this at bottom of post.
Tried flashing using flash_image in adb. More about that at bottom of the thread.
Tried to get fastboot to work. I get an infinite < waiting for device >. More on that at bottom of the post.
Tried to factory reset the phone using both the menu option in settings, and the dial code, both result in the phone turning off and then starting up with a blank black screen that stays there forever.
Tried taking the battery out a thousand times, seriously why is this suggested so often?
List of Recovery ROMs I've tried:
signed_cwm-5.0.2.7-flashablezip-ext4only.zip
cwm-5.0.2.7-ext4only-odin.tar.md5
cwm-5.0.2.7-ext4+rfs-odin.tar.md5
stockrecovery-DXKT4-odin.tar.md5
All coming from this thread.
Also one or two others from blog about clockworkmod etc.
The point is it has no effect because as far as I can tell it isn't even flashed anyway.
Flashing from fresh PC failed
What I mean by this is:
I took a different PC
did a fresh install of windows on it
installed the Samsung drivers using the Kies CD
put the phone in download mode (VolDown+Home+Power)
start Odin, select OPS and tar.md5 file
connect phone
run Odin
nothing special happens…
What Odin does:
copy image to phone → success
disconnect from COM port and wait for reboot
start countdown timer
at this point phone reboots normally (not recovery or anything) and nothing special happens, the Odin timer eventually time's out and the operation is finished
Update: added actual output from odin as an attachment.
I'm not sure but I don't think the above is what Odin is typically supposed to do.
The odin I'm using is 4.42 for Gio and comes from the threads linked to in the first 2 bullet points linked above.
How flash_image fails
I have tried using both adb and terminal emulator on phone. Root access is given to the emulator via superuser app. This is what I do:
Code:
su
cd system
flash_image recovery recovery.img
This is what I get:
Code:
error scanning partitions: No such file or directory
recovery.img is located in /system/recovery.img
flash_image is located in /system/bin/flash_image with proper chmod setting of 755.
It makes no difference if I mount the system as read/writeable or not.
The flash_image I'm using comes from CyanogenMod wiki, here.
My best guess here is that the reason flash_image finds no recovery partition is that there isn't one. I certainly don't see one. And this would also explain why the phone does nothing (black screen or samsung logo) when you try to boot to recovery.
Please dear God somebody tell me that one of you has seen this before and knows a solution for this?
According to this thread the partition where recovery.img resides is /dev/block/bml9, but how do I get my CWM recovery.img on that partition? Do I cat? dd? What? Is there any partition (e.g. that one, or /system or anything) that I should format to something strange before this will work?
Issues with fastboot
2 problems with this. First one is, how exactly do you get into "fastboot" mode on the phone? I don't even know if it can. I have uncovered the following startup key-combos:
recovery mode (Home+Power) does not work, so now just a blank screen
download mode (VolDown+Home+Power)
ramdump arm9 mode (VolUp+Home+Power)
emergency download mode (VolDown+VolUp+Home+Power)
LK Little Kernel Mode (VolUp+VolDown+Power)
blank screen (VolUp+Power)
blank screen (VolDown+Power)
regular boot (Power) doesn't work after attempting hard reset, only results in samsung logo and inability to boot
None of these seem to be fastboot mode, so I guess it's more complicated than that.
Other problem is I'm using Linux and I've read I'll need to configure Udev to detect the phone ID used when in fastboot mode.
I've read that some people who couldn't flash with flash_image in adb were able to flash using fastboot so I'm hoping for that.
Summary
As you guys can see I've really tried a lot of things. Everything I can think of, and everything I could find on XDA and the rest of the web. I have had no success. Like OP's topic title says, I still have a working phone. When Hard Reset fails and the phone becomes unbootable I can make it bootable again by using Odin to fail at flashing a recovery.
So the phone actually works fine. The problem is I can't get to recovery mode and therefore can not flash CyanogenMod (all CyanogenMod threads say to flash ClockworkMod Recovery before CyanogenMod).
Please can somebody help me with this, I don't know what else to try.
Edit: hey pakistanish, thanks for the suggestions, if I don't install the USB drivers from the Kies CD then where am I supposed to get them from?

Bump?
Nobody able to help with this?
Am I in the wrong sub-forum or something?

One more option you could try: the dd command. Provided you're rooted, copy the recovery.img file you want to flash over to your SD card.
then from a shell: dd if=/sdcard/recovery.img of=/dev/block/bml9 bs=4096
Also, did you try using ddms or logcat while your phone was stuck at the Samsung logo? There might have been clues as to what the issue was.
Good luck,
Darkshado

very nice try, still no cigarre
Darkshado said:
One more option you could try: the dd command. Provided you're rooted, copy the recovery.img file you want to flash over to your SD card.
then from a shell: dd if=/sdcard/recovery.img of=/dev/block/bml9 bs=4096
Also, did you try using ddms or logcat while your phone was stuck at the Samsung logo? There might have been clues as to what the issue was.
Click to expand...
Click to collapse
Hi thanks for the helpful advice! I tried that now. Backed up the current bml9 to sdcard with dd and then dd'd my recovery.img over it; it seemed successful. I restarted the phone to recovery mode and it just hangs at the Samsung logo like normal. This thread confirms that /dev/block/bml9 is indeed the recovery partition, however replacing it seems to have no effect.
I have never heard of ddms or logcat, what do they do and do you have download links?

I still have the same issue, thx for any advices.

LG E980 PhilZ Touch Recovery BootLoop Fix (HOW TO GET DEVICE BACK TO USABLE STATE)

Download the zip from this link http://s000.tinyupload.com/index.php?file_id=70581848454313738691 . After that mount USB in PhilZ and copy over the zip file to your phone. Then flash the zip file and your boot loop should be fixed. The fix is originally by @fosunite and was posted on the PhilZ page.

Why is the file size so big?

arifqur said:
Why is the file size so big?
Click to expand...
Click to collapse
I put several ROMs in it that I modified to work with the old recovery which I also modded...all is in the zip make sure to read the readme

or you could just keep a twrp recovery zip on your sdcard and flash it like i did when philz recover kept booting into recovery.

rob219 said:
or you could just keep a twrp recovery zip on your sdcard and flash it like i did when philz recover kept booting into recovery.
Click to expand...
Click to collapse
That's basically what the tutorial says but it also has modified CM11 zips that will be flashable in twrp 2.6.1.0

This is a simpler guide for those who have trouble with terminal based solutions
Sent from my LG-E980 using Tapatalk

philz bootloop
rob219 said:
or you could just keep a twrp recovery zip on your sdcard and flash it like i did when philz recover kept booting into recovery.
Click to expand...
Click to collapse
I am having this same issue. everything was going fine with it when I booted into recovery from rom toolbox, but the first time I booted into philz with the power vol up and home it looped and I cant get out of it. This TWRP method that you mention what version of TWRP should I dl and please someone help soon my phone is out of commission.

rjmxtech said:
Hi all,
I recently figured out how to get an LG E980 back to a usable state after being stuck in a recovery loop due to a user or random system error from the PhilZ Touch Recovery (CWM/TWRP combo) and put CyanogenMod on it instead of having to flash back to stock.....the following link is directed to a zip file with a read me inside of it along with some files that have been modified to work with the recovery I have included in the zip file.
------HERE IS THE ZIP FOLLOW THE README INSIDE IT OR RISK BRICKING YOUR DEVICE------
******I am not responsible for anything that may happen to your device while following this guide, before following it, and after following it.......by downloading the zip file and following the steps you take all responsibility for anything that may possibly happen to your device at any time before, after, or while following this guide!!!!!!!!!!!!!!!!!!!!!!******
Click to expand...
Click to collapse
I successfully installed TWRP 2.6.1.0. Not sure oif it is related but when I try to flash the cm11 zip file it says "no MD5 file found". It still says the flashing was successful. I then flash the pa-gapps file and it says "successful".
so I reboot to system and i get the "secure booting error. Cause: Device Unlock, so Boot Successful" then it boots right back into TWRP.
Please help.

droidbrain said:
I successfully installed TWRP 2.6.1.0. Not sure oif it is related but when I try to flash the cm11 zip file it says "no MD5 file found". It still says the flashing was successful. I then flash the pa-gapps file and it says "successful".
so I reboot to system and i get the "secure booting error. Cause: Device Unlock, so Boot Successful" then it boots right back into TWRP.
Please help.
Click to expand...
Click to collapse
did the flashing take a few seconds? are the files you are flashing on the SD card? if the answer is yes to both, you need to move the files you want to flash to the internal storage, then flash them. Personally i prefer CWM to flash and go back to TWRP if i ever get stuck on a recovery bootloop(reboot to system, fix root when prompted).

I did fix that issue without his files.
droidbrain said:
so I reboot to system and i get the "secure booting error. Cause: Device Unlock, so Boot Successful" then it boots right back into TWRP.
Please help.
Click to expand...
Click to collapse
What you guys might need is a command which should put your phone on usable state.
In this case of a bootloop into recovery you just need 6 steps.
1. Download the aroma file manager. It has a build in terminal console. Get this one here:
http://forum.xda-developers.com/attachment.php?attachmentid=2231581&d=1378202418
2. Place the zip file on anywhere you like. On external sd it s easier to find. Let s put it on the root of external sd.
3. In the recovery please flash that zip file from step 1
4. After aromafm has started, press menu->open console .
5. A console appeared. Type this command all at once:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 count=1088
6. Confirm this command by pressing enter. You see something displayed about copied with 1,1 kb or something. That was its process. To reboot your phone type in the console:
Code:
reboot
And confirm this by pressing enter again.
Info1: be sure that you didnt cause this boot loop by applying the OTA update from LG software update. If u did, the only way is to flash back with kdz!
Info2: Also if you flashed something what has caused an error loki ifying it and then bootloop, dont panic, use the command and flash something else working.
This command is handy, so write it down on paper or memorize it:.
Info3: If you enter the recovery by using POWER+volume up , ofc u need to enter the mentioned command in step 5 afterwards:::. Else you ll get a bootloop to recovery again.
Info4: If you are using philz touch recovery and have the aromafm zip file: Rename this file to "aromafm.zip" and place this into your external SD card into the clockworkmod/aromafm/aromafm.zip This way you can doubletap your recovery screen in philz touch and start your aromafm in a faster way.
Sent from my LG-E986 using XDA Free mobile app

fosunite said:
What you guys might need is a command which should put your phone on usable state.
In this case of a bootloop into recovery you just need 6 steps.
1. Download the aroma file manager. It has a build in terminal console. Get this one here:
http://forum.xda-developers.com/attachment.php?attachmentid=2231581&d=1378202418
2. Place the zip file on anywhere you like. On external sd it s easier to find. Let s put it on the root of external sd.
3. In the recovery please flash that zip file from step 1
4. After aromafm has started, press menu->open console .
5. A console appeared. Type this command all at once:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 count=1088
6. Confirm this command by pressing enter. You see something displayed about copied with 1,1 kb or something. That was its process. To reboot your phone type in the console:
Code:
reboot
And confirm this by pressing enter again.
Info1: be sure that you didnt cause this boot loop by applying the OTA update from LG software update. If u did, the only way is to flash back with kdz!
Info2: Also if you flashed something what has caused an error loki ifying it and then bootloop, dont panic, use the command and flash something else working.
This command is handy, so write it down on paper or memorize it:.
Info3: If you enter the recovery by using POWER+volume up , ofc u need to enter the mentioned command in step 5 afterwards:::. Else you ll get a bootloop to recovery again.
Info4: If you are using philz touch recovery and have the aromafm zip file: Rename this file to "aromafm.zip" and place this into your external SD card into the clockworkmod/aromafm/aromafm.zip This way you can doubletap your recovery screen in philz touch and start your aromafm in a faster way.
Sent from my LG-E986 using XDA Free mobile app
Click to expand...
Click to collapse
When I flashed zip it went into file manager and I had to acess the terminal from the menu. After the command string was entered I did get the 1,1 kb file message. When I tried to enter reboot, I got sh: reboot: not found. I exited console and closed file manager. It put me back into twrp. I then reboot back to system but I got the same secure boot message and back into twrp.

droidbrain said:
When I flashed zip it went into file manager and I had to acess the terminal from the menu. After the command string was entered I did get the 1,1 kb file message. When I tried to enter reboot, I got sh: reboot: not found. I exited console and closed file manager. It put me back into twrp. I then reboot back to system but I got the same secure boot message and back into twrp.
Click to expand...
Click to collapse
What did u do before u got in a bootloop?
Sent from my LG-E988 using XDA Free mobile app

droidbrain said:
When I flashed zip it went into file manager and I had to acess the terminal from the menu. After the command string was entered I did get the 1,1 kb file message. When I tried to enter reboot, I got sh: reboot: not found. I exited console and closed file manager. It put me back into twrp. I then reboot back to system but I got the same secure boot message and back into twrp.
Click to expand...
Click to collapse
You don't reboot from the console, you exit the console and also exit Aroma file manager back to CWM and then you just reboot system from Philz CWM and that should end your bootloop. Done it a bunch of times and always gets me out of the bootloop.
Erik

fosunite said:
What did u do before u got in a bootloop?
Sent from my LG-E988 using XDA Free mobile app
Click to expand...
Click to collapse
I was installing the OTA ATT update. When the phone restarted it booted into twrp been stuck there since. I can get into download mode but thats about it.
---------- Post added at 05:28 PM ---------- Previous post was at 05:19 PM ----------
ricco333 said:
You don't reboot from the console, you exit the console and also exit Aroma file manager back to CWM and then you just reboot system from Philz CWM and that should end your bootloop. Done it a bunch of times and always gets me out of the bootloop.
Erik
Click to expand...
Click to collapse
That is exactly what I did. Only boots into twrp.

droidbrain said:
I was installing the OTA ATT update. When the phone restarted it booted into twrp been stuck there since. I can get into download mode but thats about it.
---------- Post added at 05:28 PM ---------- Previous post was at 05:19 PM ----------
That is exactly what I did. Only boots into twrp.
Click to expand...
Click to collapse
Then your problem is not the recovery, your phone is booting to recovery only because your ROM fails to boot. Try installing another ROM using TWRP to see if it fixes your problem.
Erik

ricco333 said:
Then your problem is not the recovery, your phone is booting to recovery only because your ROM fails to boot. Try installing another ROM using TWRP to see if it fixes your problem.
Erik
Click to expand...
Click to collapse
I have tried multiple roms and have had the same problem. The only rom that seemed to be successful is the one attached to the link in the beginning of the thread. Except it still gave me the secure boot message and booted into twrp.

droidbrain said:
I have tried multiple roms and have had the same problem. The only rom that seemed to be successful is the one attached to the link in the beginning of the thread. Except it still gave me the secure boot message and booted into twrp.
Click to expand...
Click to collapse
What I would do in your case is restore back to stock using LG Flash Tools and then start over with FreeGee and install the recovery from there and see if your trouble clears.
Erik

Read info1 from my post.
U aplied the update and then u cannot boot. So u must flash kdz back to stock.
Sent from my LG-E988 using XDA Free mobile app

fosunite said:
Read info1 from my post.
U aplied the update and then u cannot boot. So u must flash kdz back to stock.
Sent from my LG-E988 using XDA Free mobile app
Click to expand...
Click to collapse
How do I do that?

droidbrain said:
How do I do that?
Click to expand...
Click to collapse
Better is that u should read this topic on the OP in the following link:
http://forum.xda-developers.com/showthread.php?p=44983841
[Guide][Stock Roms] Return Back To Stock AT&T & International
Sent from my LG-E988 using XDA Free mobile app

X800 rusch rom stuck on twrp after forced update

I accidentally permitted ota update to 18s. Now the phone is stuck on twrp screen and does not boot any system. Tried to install back rusch rom from twrp but still get to twrp only... any help would be very appreciated..

vladkon1 said:
I accidentally permitted ota update to 18s. Now the phone is stuck on twrp screen and does not boot any system. Tried to install back rusch rom from twrp but still get to twrp only... any help would be very appreciated..
Click to expand...
Click to collapse
Maybe you could fix this by using TWRP terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Click to expand...
Click to collapse
Reboot.
Good luck

Thank you for your reply!
tried to do it but after
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota i got error :
can't open /dev/block/platform/msm_sdcc.1/by-name/fota no such file or directory
any ideas?

Checked in file manager - under /dev/block/platform i have only /f9824900.sdhci and not /msm_sdcc.1 . Also under mount - system partition is not checked, when I check it and reboot it is still get unchecked. Any advise?

vladkon1 said:
Checked in file manager - under /dev/block/platform i have only /f9824900.sdhci and not /msm_sdcc.1 . Also under mount - system partition is not checked, when I check it and reboot it is still get unchecked. Any advise?
Click to expand...
Click to collapse
Copy Stock Rom (older release is better)to the phone's root, then Wipe Dalvik/Cache. Return to Stock recovery and try to flash it, maybe it will fix the boot issue.

nsmsdz said:
Copy Stock Rom (older release is better)to the phone's root, then Wipe Dalvik/Cache. Return to Stock recovery and try to flash it, maybe it will fix the boot issue.
Click to expand...
Click to collapse
Already tried 13s official. Also tried to restore from system backup... still twrp bootloops...