My device not getting into recovery. - LG Optimus 4X HD

My device not getting into recovery. Harwarically I can get into recovery, but I can not use adb reboot recovery or any rebooting app, it just normal reboots. Need urgent help. My buttons are almost finished cant stand more pressure.

Subhajitdas298 said:
Harwarically I can get into recovery
Click to expand...
Click to collapse
harwarically?
try changing recovery, if that doesn't solve it it's a rom problem

Rudjgaard said:
harwarically?
try changing recovery, if that doesn't solve it it's a rom problem
Click to expand...
Click to collapse
stock rom. i can get into recovery using hardware buttons and pa rom's power button menu. but can not get into using other apps.

Subhajitdas298 said:
stock rom. i can get into recovery using hardware buttons and pa rom's power button menu. but can not get into using other apps.
Click to expand...
Click to collapse
What other apps? Like some reboot app? Maybe they send the wrong argument to the bootloader. Might not be compatible with our device.
If you can get in using hardware buttons, then its mostly a problem with the other apps you are trying.

Download terminal emulator, run:
Code:
su
reboot recovery
and you're in recovery. If that doesn't work for some unknown reason, you need to switch roms.
EDIT: disregard this, per adams post below.

It doesn't work on stock rom unless you manually write recovery boot command to misc partition.
Sent from my OmniROM-powered LG Optimus 4X HD

Download from playstore rom manager and go in, in the app theres a option : *boot my device into recovery*
Sent from my LG-P880 using xda app-developers app

GalaxyVolvoZ said:
Download from playstore rom manager and go in, in the app theres a option : *boot my device into recovery*
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
As Adam posted above, none of these apps/ commands will work if it isn't defined in the misc partition. I wasnt aware of this before Adam pointed it out, ill look into the easiest way for this to be done.

JoinTheRealms said:
As Adam posted above, none of these apps/ commands will work if it isn't defined in the misc partition. I wasnt aware of this before Adam pointed it out, ill look into the easiest way for this to be done.
Click to expand...
Click to collapse
IIRC now that @GalaxyVolvoZ posted ROM Manager works, because it writes the needed command.
Otherwise this is the command needed in shell:
Code:
echo "boot-recovery" | /system/bin/dd of=/dev/block/mmcblk0p5 bs=1 count=13

Adam77Root said:
IIRC now that @GalaxyVolvoZ posted ROM Manager works, because it writes the needed command.
Otherwise this is the command needed in shell:
Code:
echo "boot-recovery" | /system/bin/dd of=/dev/block/mmcblk0p5 bs=1 count=13
Click to expand...
Click to collapse
Thanks! slightly off topic, but do you know what format the misc partition is?

JoinTheRealms said:
Thanks! slightly off topic, but do you know what format the misc partition is?
Click to expand...
Click to collapse
It's probably not formatted, just raw data.
Sent from my OmniROM-powered LG Optimus 4X HD

JoinTheRealms said:
Download terminal emulator, run:
Code:
su
reboot recovery
and you're in recovery. If that doesn't work for some unknown reason, you need to switch roms.
EDIT: disregard this, per adams post below.
Click to expand...
Click to collapse
does not work for me

i cant enter recovery on my phone. getting this everytime reboot int recovery. tried physical keys, or rom manager, even system reset also cannot do because of this. any idea how to solve this?
currently on stock rom

cruelboy86 said:
i cant enter recovery on my phone. getting this everytime reboot int recovery. tried physical keys, or rom manager, even system reset also cannot do because of this. any idea how to solve this?
currently on stock rom
Click to expand...
Click to collapse
Did you try to flash a recovery without unlocking bootloader?
Use LG mobile support tool.

Related

[Q] sprint hero recovery mode

hey guys right now im using darchstar's godspeed recovery.. but whats the most recommended recovery mode that everyone uses?
My personal favorite is Clockwork Mod Recovery. You can find the latest for our phone in the Andorid Development section, on the first page of the aospGBmod thread. Should be easy to find as it is right on top 99% of the time due to popularity.
DARCH All the way if your running GB then clockwork because I've read people have had problems with Darch's recovery with GB but if your running CM6 then stick with Darch
Root-Hack-Mod-Always™
laie1472 said:
DARCH All the way if your running GB then clockwork because I've read people have had problems with Darch's recovery with GB but if your running CM6 then stick with Darch
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
Anyone Have The Apk. Or Zip File For Darch's Recovery?
Sent from my HERO200 using XDA App
PMGRANDS said:
Anyone Have The Apk. Or Zip File For Darch's Recovery?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I got it off of darch's website but it's been down as far as I know for a little while now.. Luckily I backed it up on my dropbox when I first downloaded it
I attached it so it'll be on XDA for everyone
Download the Darchstar_ra.zip and extract it onto the root of your sdcard.
Boot up into your rom
Open up terminal emulator and enter the following:
Code:
su
flash_image recovery /sdcard/darchdroid_ra.img
reboot
2 questions will this restore previous RA nandroids and also can this do the complete wipe like clockwork?
kyouko said:
I got it off of darch's website but it's been down as far as I know for a little while now.. Luckily I backed it up on my dropbox when I first downloaded it
I attached it so it'll be on XDA for everyone
Download the Darchstar_ra.zip and extract it onto the root of your sdcard.
Boot up into your rom
Open up terminal emulator and enter the following:
Code:
su
flash_image recovery /sdcard/RA-Darchstar.img
reboot
Click to expand...
Click to collapse
sent from my twopointtwo themed hero
thoughtlesskyle said:
2 questions will this restore previous RA nandroids and also can this do the complete wipe like clockwork?
sent from my twopointtwo themed hero
Click to expand...
Click to collapse
I don't see why it would have problems restoring older nandroids, I've never had problems after updating.
And yes, you can wipe data/cache, cache, davlik-cache, battery stats, and rotation settings in the wipe menu.
I currently use ClockworkMod Recovery 2.5.0.1 for recovery mode.
Specs of my Sprint HTC Hero/APA6277 are...
Android version: AOSP
Baseband version 2.42.02.10.29,
Kernel version 2.6.29.6-aospMD [email protected] #1
Mode version: aospMOD-0.9.9.2
Build number: FRG83
I plan on flashing the AOSP GB Mod to my device as soon as a stable version of it becomes available.
kyouko said:
I don't see why it would have problems restoring older nandroids, I've never had problems after updating.
And yes, you can wipe data/cache, cache, davlik-cache, battery stats, and rotation settings in the wipe menu.
Click to expand...
Click to collapse
have you had any issues with wiping and flashing gingerbread because i didnt at first but lately it seems like its not a full wipe, then again im using a really old version of RA
kyouko said:
I got it off of darch's website but it's been down as far as I know for a little while now.. Luckily I backed it up on my dropbox when I first downloaded it
I attached it so it'll be on XDA for everyone
Download the Darchstar_ra.zip and extract it onto the root of your sdcard.
Boot up into your rom
Open up terminal emulator and enter the following:
Code:
su
flash_image recovery /sdcard/RA-Darchstar.img
reboot
Click to expand...
Click to collapse
Thanx A lot Kyouko!!
I Downloaded It....
But I Wanted To Pick Your Brain A Bit, Before I Flashed It.... Lol!
As I'm Sure You Know,
*Rom Manager* Has The Option "Flash Alternate Recovery" Which Switches The Users Recovery From Clockwork, To Amon_Ra, Right?
So I Guess My Question To You Is, What's The Difference Between This Recovery & The Other Two?
Is There More Features??
Oh, One More Thing.... Sorry!!
I Have A **** Load Of Backups From *Rom Manager* Will The Still Be Compatible, Since I Made'em With Clockwork?
Sent from my HERO200 using XDA App
thoughtlesskyle said:
have you had any issues with wiping and flashing gingerbread because i didnt at first but lately it seems like its not a full wipe, then again im using a really old version of RA
Click to expand...
Click to collapse
That issue was fixed in the newer RA versions (which includes this one and godspeed)
There was a problem wiping with the older RA after the cache location got moved in newer rom versions or something along those lines
PMGRANDS said:
As I'm Sure You Know,
*Rom Manager* Has The Option "Flash Alternate Recovery" Which Switches The Users Recovery From Clockwork, To Amon_Ra, Right?
So I Guess My Question To You Is, What's The Difference Between This Recovery & The Other Two?
Is There More Features??
Oh, One More Thing.... Sorry!!
I Have A **** Load Of Backups From *Rom Manager* Will The Still Be Compatible, Since I Made'em With Clockwork?
Click to expand...
Click to collapse
I'm not sure what the "flash alternate recovery" does because I only tried clockwork once and flashed over the recovery using terminal
As for features I took screens of each menu on the recovery
And I don't know what kind of backups rom manager does. If they're structured like nandroids it might work You may have to create a folder named "nandroid" and inside that folder create another and throw the backups in there. It'd be structured something like this:
/sdcard/nandroid/oldbackups/*folders go here*
And worst case scenario if they don't work but you really want all of them back you can just flash clockwork back to restore them.
kyouko said:
That issue was fixed in the newer RA versions (which includes this one and godspeed)
There was a problem wiping with the older RA after the cache location got moved in newer rom versions or something along those lines
I'm not sure what the "flash alternate recovery" does because I only tried clockwork once and flashed over the recovery using terminal
As for features I took screens of each menu on the recovery
And I don't know what kind of backups rom manager does. If they're structured like nandroids it might work You may have to create a folder named "nandroid" and inside that folder create another and throw the backups in there. It'd be structured something like this:
/sdcard/nandroid/oldbackups/*folders go here*
And worst case scenario if they don't work but you really want all of them back you can just flash clockwork back to restore them.
Click to expand...
Click to collapse
Darch's Recovery is an overclocked version of AmonRa with EXT4 Support. See here for more info
kyouko said:
That issue was fixed in the newer RA versions (which includes this one and godspeed)
There was a problem wiping with the older RA after the cache location got moved in newer rom versions or something along those lines
I'm not sure what the "flash alternate recovery" does because I only tried clockwork once and flashed over the recovery using terminal
As for features I took screens of each menu on the recovery
And I don't know what kind of backups rom manager does. If they're structured like nandroids it might work You may have to create a folder named "nandroid" and inside that folder create another and throw the backups in there. It'd be structured something like this:
/sdcard/nandroid/oldbackups/*folders go here*
And worst case scenario if they don't work but you really want all of them back you can just flash clockwork back to restore them.
Click to expand...
Click to collapse
Thanx For The Screenshots,
Now I'm Curious! And I Already Like The Way It Looks Better Than Clockwork! But To Be Honest Im A Little Nervous About Using ADB. Or Terminal Emulator!
Is It Easy/Hard?
I Heard You Can Brick Your Phone If You Enter A Command Wrong, Is That True?
Sent from my HERO200 using XDA App
PMGRANDS said:
Thanx For The Screenshots,
Now I'm Curious! And I Already Like The Way It Looks Better Than Clockwork! But To Be Honest Im A Little Nervous About Using ADB. Or Terminal Emulator!
Is It Easy/Hard?
I Heard You Can Brick Your Phone If You Enter A Command Wrong, Is That True?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
As long as you don't put "flash_image (BOOT or any other partition here)" you should be fine.
If you input it incorrectly it won't flash,
example: flashimage recovery /sdcard/darchdroid_ra.img
How to flash it via ADB:
Code:
adb shell
su
flash_image recovery /sdcard/darchdroid_ra.img
reboot
kyouko said:
As long as you don't put "flash_image (BOOT or any other partition here)" you should be fine.
If you input it incorrectly it won't flash,
example: flashimage recovery /sdcard/darchdroid_ra.img
How to flash it via ADB:
Code:
adb shell
su
flash_image recovery /sdcard/darchdroid_ra.img
reboot
Click to expand...
Click to collapse
followed the code lines for terminal emu and adb both times got Flash_img: not found even tried entering Darchstar_ra.img same error
thoughtlesskyle said:
followed the code lines for terminal emu and adb both times got Flash_img: not found even tried entering Darchstar_ra.img same error
Click to expand...
Click to collapse
Weird.. Do this for me, open up terminal emulator and type:
Code:
su
flash_image
you should get a return line saying:
Code:
usage: flash_image partition file.img
*see attached picture for example*
Make sure you're inputing it exactly the way I had it in the previous post - underscores and all. If the recovery.img name is different make sure whatever you type is exactly what the img is called.
If it's not in the /sdcard/ directory enter the correct one.
Example) /sdcard/downloads/oldrecovery.img
On my second attached picture you can see that the command worked, but since I already have that recovery flashed it aborts.
thoughtlesskyle said:
have you had any issues with wiping and flashing gingerbread because i didnt at first but lately it seems like its not a full wipe, then again im using a really old version of RA
Click to expand...
Click to collapse
I'd just use CW for Gingerbread, RA doesn't wipe boot or system I believe.
Does anyone know if you are able to Wipe Data/cache/dalvik from adb shell?
just making a script to automate the process.
anyone know the commands?
thanks

[Q] nandroid via adb or fastboot

hi to all!! i have a doubt....
can i do a nandroid backup of my current rom using adb or fastboot parameters??
anyone can write or leave it here?
thank´s in advance!!
No. Custom recover does it. You can issue the adb reboot recover command to get into it etc....
Sent from my Nexus One using XDA App
Yea...maybe its the reason that i dont know this parameter lol
sent from my amstrad CPC powered by LOL..(premium xda)
You sure can do it from adb. I had to find this out when I cracked my AMOLED screen and had to try and back everything up without being able to use the screen of my phone.
You need to be in recovery for it (you might be able to backup with fastboot as well, but I didn't have my bootloader unlocked at the time), so if you are full booted up, reboot into recovery and follow these commands.
Code:
adb reboot recovery
adb shell
nandroid backup
Nice and simple, right?
bassmadrigal said:
You sure can do it from adb. I had to find this out when I cracked my AMOLED screen and had to try and back everything up without being able to use the screen of my phone.
You need to be in recovery for it (you might be able to backup with fastboot as well, but I didn't have my bootloader unlocked at the time), so if you are full booted up, reboot into recovery and follow these commands.
Code:
adb reboot recovery
adb shell
nandroid backup
Nice and simple, right?
Click to expand...
Click to collapse
all rigth buddy... thank´s!!! i´ve a adb fastboot command list and this does not stay in the list...
bassmadrigal said:
You sure can do it from adb. I had to find this out when I cracked my AMOLED screen and had to try and back everything up without being able to use the screen of my phone.
You need to be in recovery for it (you might be able to backup with fastboot as well, but I didn't have my bootloader unlocked at the time), so if you are full booted up, reboot into recovery and follow these commands.
Code:
adb reboot recovery
adb shell
nandroid backup
Nice and simple, right?
Click to expand...
Click to collapse
ok i did it with the commands that you gave to me... and i obtain it when i try...
E:UNKNOWN VOLUME FOR PATH [/SDCARD]
CAN´T MOUNT SD CARD
#.
any advise????? please.......
some one can help-me please?? thanks in advance for your advises!!
SERGI.3210 said:
ok i did it with the commands that you gave to me... and i obtain it when i try...
E:UNKNOWN VOLUME FOR PATH [/SDCARD]
CAN´T MOUNT SD CARD
#.
any advise????? please.......
Click to expand...
Click to collapse
Sorry, I was out of town all day...
At what point is this failing? I assume you actually have an sdcard loaded in the phone?
bassmadrigal said:
Sorry, I was out of town all day...
At what point is this failing? I assume you actually have an sdcard loaded in the phone?
Click to expand...
Click to collapse
thanks for your continuity in this thread!!
shell shows me this when i put my device into recovery and enter the code that was provided to my above...sd card is in my device... but i think that the problem is that i don´t know what´s exactly the status that the phone need to stay.. into recovery with sd card usb mounted?(i think that not)
with the phone booted and in usb debugging mode & only chargue?
If you are booted into the phone (ie. fully loaded and able to use your phone), you need to issue the adb reboot recovery command. If the phone is off, hold down the volume down button as you are booting up. This will load the bootloader. From there, it will do a little check, and then you can use the volume keys to go to Recovery. Hit the Power button to select it. The phone will load the 'X' screen and eventually be in recovery (the text should be green or orange).
Once you are in recovery, you don't need to do anything else on the phone. Just issue
Code:
adb shell
nandroid backup
(You might have to issue the 'su' command if it shows a $ instead of a # before you run the backup.)
bassmadrigal said:
If you are booted into the phone (ie. fully loaded and able to use your phone), you need to issue the adb reboot recovery command. If the phone is off, hold down the volume down button as you are booting up. This will load the bootloader. From there, it will do a little check, and then you can use the volume keys to go to Recovery. Hit the Power button to select it. The phone will load the 'X' screen and eventually be in recovery (the text should be green or orange).
Once you are in recovery, you don't need to do anything else on the phone. Just issue
Code:
adb shell
nandroid backup
(You might have to issue the 'su' command if it shows a $ instead of a # before you run the backup.)
Click to expand...
Click to collapse
when i did it i obtained:
Code:
~#nandroid backup
E:unknown volume for path [/sdcard]
can´t mount sdcard
and if i write su i obtain it:
Code:
~#su
/sbin/sh: su: not found
~#
sorry for my ignorance mate i´m open for your help
also i know that the device is in the correct mode thank´s to you... and confirmated with command:
Code:
adb status-window
-[2j-[2hANDROID debug bridge (adb mode)
status:unknown
Which recovery do you use?
What happens when you type
Code:
adb devices
?
bassmadrigal said:
What happens when you type
Code:
adb devices
?
Click to expand...
Click to collapse
shows me that the device its connected and a big number... this part its correct
danger-rat said:
Which recovery do you use?
Click to expand...
Click to collapse
CWM recovery
SERGI.3210 said:
CWM recovery
Click to expand...
Click to collapse
CWM 3.x, or 2.x?
same problem
danger-rat said:
CWM 3.x, or 2.x?
Click to expand...
Click to collapse
I'm having the same problem with my HeroC. If you have any idea what to do I would really appreciate it! I'm running AOSP 2.3.4, Firerats MTD, and CWmod 3xxx
Don't use CWM 3.x, stick to the latest 2.x
danger-rat said:
Don't use CWM 3.x, stick to the latest 2.x
Click to expand...
Click to collapse
Should I just flash the CW2xxx over the CW3xxx and then proceed with the nandroid backup? I can't use my screen at all, so will that be a problem?

[Q] Flashing Custom Recovery

I'm having hard time flash custom recovery. I installed ROM Manager, when I tried to go to recovery I got stuck at android logo with EXCLAMATORY POINT. I already followed this instructions http://forum.xda-developers.com/showpost.php?p=10467058&postcount=1638 (deleted these files /system/etc/install-recovery.sh and /system/recovery-from-boot.p)
Followed these instructions:
via fastboot
Code:
Copy recovery-RA-passion-v2.2.1.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Click to expand...
Click to collapse
via terminal app
Code:
Copy recovery-RA-passion-v2.2.1.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-passion-v2.2.1.img(press enter)
reboot recovery(press enter)
Click to expand...
Click to collapse
I also installed 4Ext Touch Recovery, but I think it need a wifi to connect to server, but I can't access a wife connection as of now.
What am I missing? I'm about to flash a ROM, my problem is just the recovery.. Anyone can help me with this? :crying:
i dont think you are missing anything just boot into recovery and flash your rom.
dont use rom manager to flash recovery, dont use 4ext recovery control app.
if you used one of the two methods you mentioned above (terminal or fastboot) and it was successful
then you have a recovery on your phone, boot into it and install your rom of choice, of course some roms will need custom mtd partitions whcih can be managed through blackrose, but for now just flash one within your parameters so you can begin
happy flashing!
demkantor said:
i dont think you are missing anything just boot into recovery and flash your rom.
dont use rom manager to flash recovery, dont use 4ext recovery control app.
if you used one of the two methods you mentioned above (terminal or fastboot) and it was successful
then you have a recovery on your phone, boot into it and install your rom of choice, of course some roms will need custom mtd partitions whcih can be managed through blackrose, but for now just flash one within your parameters so you can begin
happy flashing!
Click to expand...
Click to collapse
I really dont know what is happening. Still I can't go to recovery. Btw, does locking/unlocking bootloader affects in flashing custom recovery. But I think I already unlock mine, how would I know if unlock or lock my bootloader?
... Yea very much so, and I believe I misread you first post, I take it you didn't root your phone properly. First of all check what boot loader you have by booting into your hboot. There are a few ways to get there but for now just power off and then power back on holding your volume down key, here will be a screen with some words and androids skateboarding, write down everything from that screen here.
Sent from my Nexus 7 using xda premium
demkantor said:
... Yea very much so, and I believe I misread you first post, I take it you didn't root your phone properly. First of all check what boot loader you have by booting into your hboot. There are a few ways to get there but for now just power off and then power back on holding your volume down key, here will be a screen with some words and androids skateboarding, write down everything from that screen here.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
*BlackRose - Made by Lecabel(dla5244) *
jb-260/10/166
NEXUSONE PVT ENG S-OFF
HBOOT-7.35.5017 (PB9911000)
MICROP-0b15
TOUCH PANEL-SYNT0103
RADIO-5.08.00.04
Apr 21 2012, 04:53:16
HBOOT
VOL UP
VOL DOWN
TRACKBALL
FASTBOOT
RECOVERY - when I select this, I will be stuck at android logo with !
REBOOT
POWERDOWN
Well you are better off than just an unlocked bootloader, you have black rose installed which essentially is an engineering bootloader that allows custom mtd partitions.
Right now you have 260 for system, 10 cache and 166 for data, this should be fine for any chance ROM but may consider changing later on depending on ROM you want to run
For now you need these things
ROM of choice and anything else the dev thinks you need (gapps etc)
Put that on root of sdcard, make sure it is partitioned to fat32 and not in any folder
Also need to have fastboot working, I'm assuming you are using windows.
You will need fastboot.exe usually found in the android SDK and elsewhere.
Proper drivers installed, and although not necessary its nice to add fastboot and adb into path in environmental variables.
If all this is done great. If not go do it now.
Now get recovery, let's say amonra. Open cmd in the same directory as the recovery image, make sure you name it recovery.img (if you don't change command to fit)
Boot into hboot, and put phone into fastboot mode and connect to computer
In cmd type
fastboot devices
If you see your serial # good, if not then you missed something earlier
Now type
fastboot flash recovery recovery.img
If the output say done then you are good, select recovery from within hboot menu and reboot there, once in recovery do a nandrpoid backup (good practice) then do a full wipe, (yes wipe everything you possibly can - side note fastboot -w is cleaner for future reference) then flash ROM, gapps, whatever you need
Let me know if you get stuck
Sent from my Nexus 7 using xda premium
demkantor said:
Well you are better off than just an unlocked bootloader, you have black rose installed which essentially is an engineering bootloader that allows custom mtd partitions.
Right now you have 260 for system, 10 cache and 166 for data, this should be fine for any chance ROM but may consider changing later on depending on ROM you want to run
For now you need these things
ROM of choice and anything else the dev thinks you need (gapps etc)
Put that on root of sdcard, make sure it is partitioned to fat32 and not in any folder
Also need to have fastboot working, I'm assuming you are using windows.
You will need fastboot.exe usually found in the android SDK and elsewhere.
Proper drivers installed, and although not necessary its nice to add fastboot and adb into path in environmental variables.
If all this is done great. If not go do it now.
Now get recovery, let's say amonra. Open cmd in the same directory as the recovery image, make sure you name it recovery.img (if you don't change command to fit)
Boot into hboot, and put phone into fastboot mode and connect to computer
In cmd type
fastboot devices
If you see your serial # good, if not then you missed something earlier
Now type
fastboot flash recovery recovery.img
If the output say done then you are good, select recovery from within hboot menu and reboot there, once in recovery do a nandrpoid backup (good practice) then do a full wipe, (yes wipe everything you possibly can - side note fastboot -w is cleaner for future reference) then flash ROM, gapps, whatever you need
Let me know if you get stuck
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Finally.. Thank you so much.. I can now go to custom recovery.. Now I will backup and wipe then flash.. :good::good: Will press THANK button now, maybe a million times.. hehe
No problem, fastboot is a key skill to learn with any android device that supports it
Here is a guide I made a while back
http://forum.xda-developers.com/showthread.php?p=27796375
Its meant for a different phone but the basics are the same, I would suggest to read up on it a bit and you will have a much easier android experience
Happy flashing!
Sent from my Nexus 7 using xda premium
demkantor said:
No problem, fastboot is a key skill to learn with any android device that supports it
Here is a guide I made a while back
http://forum.xda-developers.com/showthread.php?p=27796375
Its meant for a different phone but the basics are the same, I would suggest to read up on it a bit and you will have a much easier android experience
Happy flashing!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Okay. I will try to read my left time for this day. Thanks a lot..
demkantor said:
No problem, fastboot is a key skill to learn with any android device that supports it
Here is a guide I made a while back
http://forum.xda-developers.com/showthread.php?p=27796375
Its meant for a different phone but the basics are the same, I would suggest to read up on it a bit and you will have a much easier android experience
Happy flashing!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hi, I have a follow up question regarding sd partition, I will just raise my question here than making another thread. I have 4GB SD card but I forgot how much ext partition I made before but my total space in my SD card is 3.21GB. I want to partition my sd card again and increase it maybe to 1gb. If I will increase my partition should I flash again my ROM (VJ CM10.1 | Jelly Bean 4.2.2 - v6.0) and execute a2sd command in terminal emulator? or it's okay to partition my sd card without flashing the ROM again?
You can partition SD without fllashing rom again
On this phone the easiest way to check what you have is in 4ext recovery under info, or if you have a Linux distro run gparted
You could also run df through adb shell or if not by a computer, open a terminal and type
such
df
But being it sounds like you want too repartition I would just flash 4ext recovery and do everything from there
Sent from my Nexus One using xda app-developers app
demkantor said:
You can partition SD without fllashing rom again
On this phone the easiest way to check what you have is in 4ext recovery under info, or if you have a Linux distro run gparted
You could also run df through adb shell or if not by a computer, open a terminal and type
such
df
But being it sounds like you want too repartition I would just flash 4ext recovery and do everything from there
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
I think a2sd is not working in my device. When I tried to install a2sd or reinstall it there was a line written in termenal emulator (/dev/block/mmcblkop2) I think that the reason why I easily having internal memory full, even I already partition my sd card, with 1024 ext partition using 4ext touch recovery. Check my screenshot in titanium backup showing my memory status..
Sent from my Nexus One using xda app-developers app
It looks like its working, just need to move what you want from data to ext partition shown by titanium as a2sd. What ROM are you running? It does support having apps on ext correct?
Sent from my Nexus 7 using xda premium
demkantor said:
It looks like its working, just need to move what you want from data to ext partition shown by titanium as a2sd. What ROM are you running? It does support having apps on ext correct?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. Im using VJ CM10.1 | JB 4.2.2 V 6.0. How to move data to ext partition? I will post screenshot in my internal storage too.
Sent from my Nexus One using xda app-developers app
if the rom doesnt have the feature built in then use an app from the market to do it, ive never used this rom so i dont know what options it has
also if you want an easy to see graph style layout of you partitions download Disk Usage from the market, you can easily see what is stored in which partition
demkantor said:
if the rom doesnt have the feature built in then use an app from the market to do it, ive never used this rom so i dont know what options it has
also if you want an easy to see graph style layout of you partitions download Disk Usage from the market, you can easily see what is stored in which partition
Click to expand...
Click to collapse
Thanks. Btw what rom are you using?
Sent from my Nexus One using xda app-developers app
Cyanmobile
Yes it has apps2ext built in, go into settings to activate
Sent from my Nexus One using xda app-developers app
demkantor said:
Cyanmobile
Yes it has apps2ext built in, go into settings to activate
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
Thanks, Btw, what if I wanted to change my ROM, what procedure should I follow? Should I go back to Stock ROM before flashing a new ROM?
Nope, boot to recovery, do a nandroid backup, wipe everything, wipe twice even, hell fastboot wipe (most issues people have when flashing a new ROM is not clean wiping)
Then flash ROM like you did first time, and being you have a huge partition for system right now I would suggest to shrink it a bit first, maybe around 170 if your going to use cyan mobile. If you do this you propably should be prepared to flash recovery again as well
Sent from my Nexus 7 using xda premium
demkantor said:
Nope, boot to recovery, do a nandroid backup, wipe everything, wipe twice even, hell fastboot wipe (most issues people have when flashing a new ROM is not clean wiping)
Then flash ROM like you did first time, and being you have a huge partition for system right now I would suggest to shrink it a bit first, maybe around 170 if your going to use cyan mobile. If you do this you propably should be prepared to flash recovery again as well
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the quick reply. So, you're saying that I should partition my system first and flash recovery just like what you taught me in our previous posts? Just to be sure and making all things clear to my self.

Reboot in recovery.

Hi. I have a stock based rom, deodexed. I cant' reboot in recovery with the shoutdown menù. I tried also with apps like rom manager, recovery boot does not works, every time goes in normal reboot. Anyone can give me some suggestions?
Although the power button + vol- button work as normal, but i want to set the "recovery reboot" in the menù, also reboot in fastboot and bootloader boot
I have cwm 6.0.4.5...
It happens to me too!
I have deodexed Stock ROM 4.1.2 and I wanted to add advanced power menu with 4 -Way Reboot: Reboot, Hot Boot, Bootloader and Recovery.
I have followed many guides and in particular this (here my post)
Now all reboots work, except Recovery Reboot:
when I select "Recovery" the phone restart normally!!
After several tests, I tried to use some scripts to reboot into Recovery!
First Script:
Code:
#!/system/bin/sh
echo "boot-recovery" | /system/bin/dd of=/dev/block/mmcblk0p5 bs=1 count=13
When I run this script, the phone reboot into Recovery only the first time and any option I selected, the phone always restarts in Recovery! Why?
Second Script:
Code:
#!/system/bin/sh
rm /cache/recovery/command ; echo 'boot-recovery' | dd of=/dev/block/mmcblk0p5 bs=1 count=13 ; reboot ;
When I run this script, the phone reboot into Recovery immediately!
Now I would like know how I can fix this Problem!
And those scripts serve to reboot the phone into recovery via Advanced Power Menu?
I tried everything and I do not know where I'm wrong!
Are you both running cwm? Could that be the issue?
Sent from my Nexus 5 using Tapatalk
Install "Xposed Framework" and "Advanced Power Menu" to get your wanted options...
Ben36 said:
Are you both running cwm? Could that be the issue?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have tried many Recovery: TWRP 2.3.6.0, CWM 6.0.3.1 and 6.0.4.5, PhilZ Touch.
What do you suggest?
Fladder72 said:
Install "Xposed Framework" and "Advanced Power Menu" to get your wanted options...
Click to expand...
Click to collapse
I dont want "Xposed Framework", I want to fix my problem
glfsd said:
I have tried many Recovery: TWRP 2.3.6.0, CWM 6.0.3.1 and 6.0.4.5, PhilZ Touch.
What do you suggest?
I dont want "Xposed Framework", I want to fix my problem
Click to expand...
Click to collapse
Me too
paolotheking said:
Hi. I have a stock based rom, deodexed. I cant' reboot in recovery with the shoutdown menù. I tried also with apps like rom manager, recovery boot does not works, every time goes in normal reboot. Anyone can give me some suggestions?
Although the power button + vol- button work as normal, but i want to set the "recovery reboot" in the menù, also reboot in fastboot and bootloader boot
I have cwm 6.0.4.5...
Click to expand...
Click to collapse
You have to edit the frameworks to add the option, you'll need the android kitchen for that.
The fastboot reboot won't work, the fastboot boot option will work somewhat if you add "-c "androidboot.mode=normal"" as in fastboot boot [kernel.img] -c "androidboot.mode=normal"
It will have some problems but it'll work.
IcanhasLG said:
You have to edit the frameworks to add the option, you'll need the android kitchen for that.
The fastboot reboot won't work, the fastboot boot option will work somewhat if you add "-c "androidboot.mode=normal"" as in fastboot boot [kernel.img] -c "androidboot.mode=normal"
It will have some problems but it'll work.
Click to expand...
Click to collapse
I think he means that he isn't able to reboot to recovery with the option from the shutdown menu, not that there isn't one.
As he wrote he can't boot to recovery with ROM Manager either.
I had such problems back in the beginning of 4.3 development but and on stock too.
Maybe try to grab a log from boot if you tried to reboot to recovery.
Sent from my LG-P880 using XDA Premium 4 mobile app
Omario-242 said:
I think he means that he isn't able to reboot to recovery with the option from the shutdown menu, not that there isn't one.
As he wrote he can't boot to recovery with ROM Manager either.
I had such problems back in the beginning of 4.3 development but and on stock too.
Maybe try to grab a log from boot if you tried to reboot to recovery.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Rom Manager Free does not reboot in recovery, like other app, but Rom Manager Premium works...
Omario-242 said:
I think he means that he isn't able to reboot to recovery with the option from the shutdown menu, not that there isn't one.
Click to expand...
Click to collapse
exactly
Omario-242 said:
...Maybe try to grab a log from boot if you tried to reboot to recovery.
Click to expand...
Click to collapse
how to do it? I tried with adb
Code:
adb logcat > log.txt
or
Code:
adb logcat -v long > logcat.txt
but there are too much informations and I can not find the problem
I attach also "last_log" found in /cache/recovery/
..I do not know ..... but i think the problem is due to cwm
sorry for my poor english
glfsd said:
exactly
how to do it? I tried with adb
Code:
adb logcat > log.txt
or
Code:
adb logcat -v long > logcat.txt
but there are too much informations and I can not find the problem
I attach also "last_log" found in /cache/recovery/
..I do not know ..... but i think the problem is due to cwm
sorry for my poor english
Click to expand...
Click to collapse
maybe is a cwm problem, anyone can help us?

[dev] [wip] More Data on lg optimus l90

so ive messed with this before and have hard bricked devices doing so but those devices diddnt have custom recovery but i was able to increase the data partition size by approximately 500MB (see screenshot below) im working on a recovery zip that wll do it and seeing wherelse i can pull stuff from lol. i plan to future update it so that the system is 1GB which is about all you really need and shrink partitiojnns that have more space then they ned down to like 5MB to keep the number scheme the same
Beta 1 zip is bad i am just goinmg to make a windows bat file that will do it lol
instructions.
if you want to keep your rom and data you will need and external sd card that is big nough to hold a backup of system and data.
okay i made a bat script that **SHOULD** work i havent been able to test one part of it so if youd like to test ill attach the zip to the bottom of the post
DISCLAIMER
i am not resposible if you brick your device doing this i can only confirm it will work on D415 if your onj a variant and want to know if itll work PM me the output put either from adb or a terminal emulator ls -l /dev/block/platform/msm_sdcc.1/by-num
now there are instructions on screen to follow so make sure you fread them or you could screw something uyp lol
demonslayer12349 said:
so ive messed with this before and have hard bricked devices doing so but those devices diddnt have custom recovery but i was able to increase the data partition size by approximately 500MB (see screenshot below) im working on a recovery zip that wll do it and seeing wherelse i can pull stuff from lol. i plan to future update it so that the system is 1GB which is about all you really need and shrink partitiojnns that have more space then they ned down to like 5MB to keep the number scheme the same
Click to expand...
Click to collapse
so how do u increased it.....???
using sd card ext partitions or shrinking of other partitions..???
kprsnt said:
so how do u increased it.....???
using sd card ext partitions or shrinking of other partitions..???
Click to expand...
Click to collapse
shrinking of others. my final shrinking puts the total at 5.65GB
Hey guys! Is there any update for this project.
Sent from my LG-D410 using XDA Free mobile app
sorabh.v6 said:
Hey guys! Is there any update for this project.
Sent from my LG-D410 using XDA Free mobile app
Click to expand...
Click to collapse
Update..???
This works (because i tried this kind of method in p500)..
But I didnt tested it because my device is new ..
If u wanna try PM him
sorabh.v6 said:
Hey guys! Is there any update for this project.
Sent from my LG-D410 using XDA Free mobile app
Click to expand...
Click to collapse
just posted the first beta
I'm going to try this then give feed back
Sent from my LG-D410 using Tapatalk
---------- Post added at 05:26 AM ---------- Previous post was at 05:25 AM ----------
Just curious if this will work with stock rom
Sent from my LG-D410 using Tapatalk
I got an error flashing the .zip on TWRP, something related to binary. My model is the 410hn. Thanks for the support to L90.
Using cwm, got and error 6 during flash. D410. Stock ROM
Sent from my LG-D410 using Tapatalk
goldfinv said:
Using cwm, got and error 6 during flash. D410. Stock ROM
Sent from my LG-D410 using Tapatalk
Click to expand...
Click to collapse
InfinitusDesigner said:
I got an error flashing the .zip on TWRP, something related to binary. My model is the 410hn. Thanks for the support to L90.
Click to expand...
Click to collapse
working on a windows script right now to do it or to restore it to defazult
demonslayer12349 said:
so ive messed with this before and have hard bricked devices doing so but those devices diddnt have custom recovery but i was able to increase the data partition size by approximately 500MB (see screenshot below) im working on a recovery zip that wll do it and seeing wherelse i can pull stuff from lol. i plan to future update it so that the system is 1GB which is about all you really need and shrink partitiojnns that have more space then they ned down to like 5MB to keep the number scheme the same
Beta 1 zip is bad i am just goinmg to make a windows bat file that will do it lol
instructions.
if you want to keep your rom and data you will need and external sd card that is big nough to hold a backup of system and data.
okay i made a bat script that **SHOULD** work i havent been able to test one part of it so if youd like to test ill attach the zip to the bottom of the post
DISCLAIMER
i am not resposible if you brick your device doing this i can only confirm it will work on D415 if your onj a variant and want to know if itll work PM me the output put either from adb or a terminal emulator ls -l /dev/block/platform/msm_sdcc.1/by-num
now there are instructions on screen to follow so make sure you fread them or you could screw something uyp lol
Click to expand...
Click to collapse
I tried using this and it at first didn't find adb. I moved the .bat into the tools folder, and it ran and booted to recovery. When it booted to recovery it sat there saying "waiting for device to enter recovery"
Sent from my LG-D415 using Tapatalk
blondgod said:
I tried using this and it at first didn't find adb. I moved the .bat into the tools folder, and it ran and booted to recovery. When it booted to recovery it sat there saying "waiting for device to enter recovery"
Sent from my LG-D415 using Tapatalk
Click to expand...
Click to collapse
Okay. I need to refresh my bat scripting obviously XD and do you have twro installed? I should have mentioned that and if nothing else just unplug plug back in.
demonslayer12349 said:
Okay. I need to refresh my bat scripting obviously XD and do you have twro installed? I should have mentioned that and if nothing else just unplug plug back in.
Click to expand...
Click to collapse
Um no, I have Philz-Touch installed, Is there any way to turn this into a flashable zip? I don't want to loose my CWM format backups, so if I must switch to TWR then I might pass for now.
Awesome work none-the-less.
blondgod said:
Um no, I have Philz-Touch installed, Is there any way to turn this into a flashable zip? I don't want to loose my CWM format backups, so if I must switch to TWR then I might pass for now.
Awesome work none-the-less.
Click to expand...
Click to collapse
I've tried making a flashable zip but with no success. Right now twrp is the only way this works
blondgod said:
Um no, I have Philz-Touch installed, Is there any way to turn this into a flashable zip? I don't want to loose my CWM format backups, so if I must switch to TWR then I might pass for now.
Awesome work none-the-less.
Click to expand...
Click to collapse
Sorry should have mentioned you needed twrp. I've tried flashable zips but can't seem to get a working one
demonslayer12349 said:
Sorry should have mentioned you needed twrp. I've tried flashable zips but can't seem to get a working one
Click to expand...
Click to collapse
Its no problem at all. I've got enough space for now. Thanks for the work!
Sent from my LG-D415 using Tapatalk
blondgod said:
Its no problem at all. I've got enough space for now. Thanks for the work!
Sent from my LG-D415 using Tapatalk
Click to expand...
Click to collapse
No problem.
What about restoring original partition scheme? Is this possible via kdz tools (or what's called)? Is kdz reparitioning device?
Or it has to be done manually (then we have repart making it EXACTLY the same, every single byte?
@demonslayer12349, your script is a little strange.
Code:
@adb shell su -c "mount -o remopunt rw, /"
It should be:
Code:
@adb shell su -c "mount -o remount rw, /"
isn't it?
Then another thing. You delete 4 partitions and create only three.
For D410 partition 31 is "eksst". It is 0.5mb only. What is the reason to delete it?
Or the script is device-specific?
judas1977 said:
What about restoring original partition scheme? Is this possible via kdz tools (or what's called)? Is kdz reparitioning device?
Or it has to be done manually (then we have repart making it EXACTLY the same, every single byte?
Click to expand...
Click to collapse
As I know LG software doesn't recreate partitions, so you have to do it manually.
@up
Thx for the answer. Spoony bards they are

Categories

Resources