Database Users

I can't update to ANY rom...

I wanted to update to CM7, once it rebooted into recovery mode it gives me an error. I got the official Sprint update and the same thing happens. Once it verifies the file, something happened and it says there was an error and does not update. I did a factory reset on the phone, got the official sprint update and the same thing happened. The error is always "signature verification failed" on both roms.
What can I do?
Thanks.

When flashing a rom, are you selecting 'install from SD" then find where you saved the zip, etc?
It sounds like you're trying it thru the update.zip option (don't do that). Also, when you reboot into recovery, you should be seeing orange type clockwork 3.0.0.6 (not blue or green).
Ask if you have any other questions.
Sent from my SPH-D700 using Tapatalk

Are you using cwm 3?

Thanks for the replies guys.
I am using clockword mod 3, with their option on updates.
I don't know how to do the "update from sd", haven't seen that. I'm not sure if I am seeing the orange you mention...I just go to restart in recovery mod from CM3.

capt_peo said:
Thanks for the replies guys.
I am using clockword mod 3, with their option on updates.
I don't know how to do the "update from sd", haven't seen that. I'm not sure if I am seeing the orange you mention...I just go to restart in recovery mod from CM3.
Click to expand...
Click to collapse
If you don't see orange text you're not on CWM3, you are either on CWM 2.5 or stock recovery and neither of those would be used for what you want to do.

Ya, check out the development section on getting the latest clockwork, if you don't have it already. And just in case, first, try powering off your phone, then hold camera button, volume down and power (after device is completely shut off). If you don't see orange text, you should update to the latest clockwork.
Sent from my SPH-D700 using Tapatalk

I turned off the phone, turned it on with the vol down/camera button and it automatically booted on CM recovery 3.0.0.5. Doing a rom backup. Then I see the orange text with several options but I can't pick any of them...I'm hitting the "home" button but nothing.
The phonr wont respond...I can toggle between the options but thats it.

I turned off the phone, turned it on with the vol down/camera button and it automatically booted on CM recovery 3.0.0.5. Doing a rom backup. Then I see the orange text with several options but I don't know where the hell CWM downloaded the file!!! I cant find it, or the official 2.2 one...
And now the phone is stuck in the SAMSUNG screen...

Bricked...tried factory reset and nothing. Tried restore through CWM and nothing...

If you are able to get into CWM or download mode then your phone is not bricked. It sounds like you will have to use ODIN to restore your phone back to stock.

capt_peo said:
Bricked...tried factory reset and nothing. Tried restore through CWM and nothing...
Click to expand...
Click to collapse
ClockworkMod 3 automatically converts your phone's filesystem from RFS to EXT4. You need a ROM that supports EXT4 or else it won't boot.
You wanted CM7 so go ahead and flash that if it's on the sd card. If you don't have it on the card it's easy to fix. Just turn off your phone and plug your memory card into a computer and copy a ROM that supports CWM3.
Once you flash a ROM your phone should boot normally.

Bro, when u boot into clockwork (orange) are u opening the slider and using the arrows and enter key. ? You shouldn't be using the home key.
Don't be so quick to "I'm bricked" .. cuz that's rarely the case. And annoying when ppl are trying to help.
Sent from my SPH-D700 using Tapatalk

K, thx for being patient. I did Odin and its again working.
Now the phone updated to 2.2.1
For future reference, can this Odin method be used o update to a non official rom (like CM7)?
Thanks for all the help.

I wouldn't rely odin for that, and as far as I know, no. For frame of reference, I've probably flashed epic roms over 100 times, and have only odin'd 5-- Used mostly to return to stock/update a modem. So, odining probably wasn't necessary for you. Do what arashed says a few posts up.

I'm using SRF 1.1.0/Twilight Zone and its amazing. Battery lasts a lot longer too.
Thanks again.

capt_peo said:
I'm using SRF 1.1.0/Twilight Zone and its amazing. Battery lasts a lot longer too.
Thanks again.
Click to expand...
Click to collapse
Thanks for your support!

[Q] Weird things happening with my DZ

My DZ has been doing some weird things lately and I'm at a bit of a loss as to what could be causing them.
It's rooted, S-OFF, running MIUI with ClockworkMod 5.0.2.0 installed but the recovery image won't do anything at all any more.
I click on an option and it just goes to the top-hat, circular arrow 'thinking' screen and stays there. It's the same with everything I select; it won't reboot, power off, wipe..nothing.
The problems started with the previous version of ClockworkMod, but are still present with the update.
It worked fine before, I was able to flash ROM's and do all the other usual tinkering, but then it literally just stopped with no instigation.
I've tried wiping the recovery and manually installing a new one via FastBoot but it won't work in FastBoot any more either. I just get the FAILED (remote: not allowed) message for everything I try and do.
I'm baffled.
Any ideas?
TIA

Tone-Fu said:
My DZ has been doing some weird things lately and I'm at a bit of a loss as to what could be causing them.
It's rooted, S-OFF, running MIUI with ClockworkMod 5.0.2.0 installed but the recovery image won't do anything at all any more.
I click on an option and it just goes to the top-hat, circular arrow 'thinking' screen and stays there. It's the same with everything I select; it won't reboot, power off, wipe..nothing.
The problems started with the previous version of ClockworkMod, but are still present with the update.
It worked fine before, I was able to flash ROM's and do all the other usual tinkering, but then it literally just stopped with no instigation.
I've tried wiping the recovery and manually installing a new one via FastBoot but it won't work in FastBoot any more either. I just get the FAILED (remote: not allowed) message for everything I try and do.
I'm baffled.
Any ideas?
TIA
Click to expand...
Click to collapse
The new clockwork 5 has alot of issues. You should try to reflash clockwork mod 3 or 4
Sent from my HTC Vision using XDA Premium App

Thanks for the reply, mate.
The problem is that I can't reflash to any other recovery.
The issues started when I was using the previous version, which was 4.X or something, so I updated to the latest iteration hoping it would fix the problem, but it didn't.

Don't use the power button to select stuff in clockwork, that's like a sleep mode.
Use either trackpad or camera button.
-Nipqer

Nipqer said:
Don't use the power button to select stuff in clockwork, that's like a sleep mode.
Use either trackpad or camera button.
-Nipqer
Click to expand...
Click to collapse
This. I think he's using the power button or volume buttons to move and select, which is incorrect.
You have to use the trackpad to scroll and select items.
So why are you trying to flash the new recovery through fastboot? Just pull your battery and boot into MIUI normally, then go to ROM manager and flash CWM 3.0.2.4, it will work. If it doesn't flash properly, go into the settings and select "wipe recovery before flash".

Tone-Fu said:
Thanks for the reply, mate.
The problem is that I can't reflash to any other recovery.
The issues started when I was using the previous version, which was 4.X or something, so I updated to the latest iteration hoping it would fix the problem, but it didn't.
Click to expand...
Click to collapse
I have met the similar problems too.
and I solved it via reflashing the recovery using the ROM manager.
So you can reflash your clockworkmod recovery 5.0.2.0 by ROM Manager, I guess that will work.

Cheers for the replies Nipqer & martonikaj.
The trackpad thing might be the issue but I can't tell because my wife's gone out with the phone! I'm used to using the recovery on my GS2 and DS2, which doesn't have the trackpad etc. so I may well have been using the volume rocker and power key on muscle memory.
Though it is interesting that that method obviously worked in previous iterations of the recovery.
Oh and in answer to your question I was trying to use FastBoot because I perceived the problem to be due to the flash via ROM manager.
@Sunkins - Yeah, I think ROM manager was working just fine. The problem seems to be down to the man in the loop! Cheers for the advice, mate.

I would recommend recovery 3.0.2.4 as it is rock solid, and seems to be the most reliable.

Please.

Guys please I know this is the wrong forum but no one is answering help. At all. Alright, I went to flash the ICS Sense alpha, and needed to restore a backup. I went into hboot, and restored the PD98IMG.zip. Afterwards it said "Press power to reboot" so i did. The phone turned off, and now nothing. After a LONG time the phone turned on to the White HTC Splash and vibrated CONSTANTLY, until the battery was pulled. I tried volume down + power but nothing. Except for the occasional white screen, nothing. Please, anyone/.

You're bricked
Sent from my Desire HD using telepathy...

I think your phone had a bootloop. Did you already installed custom recovery? Can you enter it through fastboot menu (vol down + power)?

I doubt he's bricked,why are you restoring that zip? You restore your back up....from clockwork?
Sent from my Desire HD using XDA Premium App

It won't enter into fastboot. Occasionally the white HTC screen comes on with a constant vibrate and the only way to stop that is to pull the battery. No fastboot, no recovery, nothing.
It wouldnt enter into recovery so I had to take the long way, by using the PD98IMG

HTC_Phone said:
It won't enter into fastboot. Occasionally the white HTC screen comes on with a constant vibrate and the only way to stop that is to pull the battery. No fastboot, no recovery, nothing.
It wouldnt enter into recovery so I had to take the long way, by using the PD98IMG
Click to expand...
Click to collapse
I am confused. So what exactly happens when doing this:
remove or rename the PD98IMG on the sd card
pull the battery from the DHD
re-enter it and hold volume down and power until the hboot starts
navigate by volume down/up to Recovery and press POWER

If you had to restore back to factory, why bother flashing ICS?
You should get away by installing one of the RUU using PC. here is a guide on how to install RUU and you'll have to search this section to find a RUU or google it.
Though firstly i would ask you if you can go into the recovery mode anyhow since you're saying that your phone can get the HTC logo. For that, hold down POWER + volume DOWN key to get you into hboot (IF YOU CAN) and choose recovery from there, once in recovery, go to option where you wipe your data + cache, wipe both of em and try restarting again...If you can't even get into recovery then do the RUU way of getting the rom working.

EDIT:
I'm not sure what in the world happened, but it booted into the ATT stock ROM. After 30 minutes of vibration and idk what else, it finally booted.

Lol least its on
Sent from my Desire HD using XDA Premium App

HTC_Phone said:
EDIT:
I'm not sure what in the world happened, but it booted into the ATT stock ROM. After 30 minutes of vibration and idk what else, it finally booted.
Click to expand...
Click to collapse
Gratz, suppose this thread's unnecessary now?
Anyway take care of what you do: always do a nandroid backup prior to flashing everything. Better spend 5min for backup than 5 days without a phone.

I think know what happens. If I remember correctly you had your phone replaced. And it came with gb. The pd98 you flashed was the froyo one. Hence the crazy vibration and long boot time. If Im right thisvwill happen each time you reboot Until you get the gb bootloader back on
Also spamming the threads is a pretty good way of getting banned. Maybe zel or Andy will be nice about it

marsdta said:
I think know what happens. If I remember correctly you had your phone replaced. And it came with gb. The pd98 you flashed was the froyo one. Hence the crazy vibration and long boot time. If Im right thisvwill happen each time you reboot Until you get the gb bootloader back on
Click to expand...
Click to collapse
That sounds somewhat correct. I DID get it replaced, but had a GB PD98 on the SD card. Anyway, it vibrated for quite some time, and eventually the vibration stopped. So I let the phone sit as I figured out some way to salvage the phone. And the the next HTC splash booted, and the phone proceeded into the stock ROM. Idk what happened, but I'm not complaining.

Dear Lord, it just turned off and is doing it again. But, I'm praying for the best again. Thanks guys.

HTC_Phone said:
Dear Lord, it just turned off and is doing it again. But, I'm praying for the best again. Thanks guys.
Click to expand...
Click to collapse
When you succesfuly back in your phone, just root it with AAHK and install some custom ROM and you should be fine.

motherninja said:
When you succesfuly back in your phone, just root it with AAHK and install some custom ROM and you should be fine.
Click to expand...
Click to collapse
The phone itself is already rooted, but I tried booting into CWM, and it did the same thing as it did before. So I have to run the RUU, and then S on the phone, and run the hack kit again. I already ran the RUU once, and nothing.

Probably best just to start over and do everything again,even if you've already done it,maybe the root didnt work?
Your phones a nightmare mate
Sent from my Desire HD using XDA Premium App

So you intentionally created a thread in the wrong section?
I guess the rules don't apply to you then.

Motorola bravo help

I have rooted my phone and flashed custom firmware b4... when i installed 2int to flash again.... it won't boot up the OS instead it keeps booting 2int... how do i boot into my os again... thx in advance
I am running android 4.1.1 jellybean

hotshot545 said:
I have rooted my phone and flashed custom firmware b4... when i installed 2int to flash again.... it won't boot up the OS instead it keeps booting 2int... how do i boot into my os again... thx in advance
I am running android 4.1.1 jellybean
Click to expand...
Click to collapse
Unfortunately, you cannot flash 2ndinit if you've already installed cyanogenmod, since it already has a bootloader. Goes for all versions of CM. I made the same mistake and had to flash the sbf.
I'm assuming that when you reboot normally you get stuck at the "red M" screen and your capacitive touch buttons might flicker. If that's the case, you will have to flash the sbf, because your bravo is boot looping. Go to this post here and follow the tutorial to the letter.
http://forum.xda-developers.com/showthread.php?t=1559109
If you are having further trouble, post it there.
And don't forget to say thank you to josuearisty

dr. Orange said:
unfortunately, you cannot flash 2ndinit if you've already installed cyanogenmod, since it already has a bootloader. Goes for all versions of cm. I made the same mistake and had to flash the sbf.
I'm assuming that when you reboot normally you get stuck at the "red m" screen and your capacitive touch buttons might flicker. If that's the case, you will have to flash the sbf, because your bravo is boot looping. Go to this post here and follow the tutorial to the letter.
http://forum.xda-developers.com/showthread.php?t=1559109
if you are having further trouble, post it there.
And don't forget to say thank you to josuearisty
Click to expand...
Click to collapse
thank u sooo much

hotshot545 said:
thank u sooo much
Click to expand...
Click to collapse
ok i just wanted to know is there a way to charge phone b4 doing this

hotshot545 said:
ok so if i flash it using sbf lite... will it run stock android 2.2 or will it's still run 4.1.1 and also will it still be rooted or will i have to restore root. and btw b4 i do this can i charge my phone in this "boot loop mode"... srry i am not the best at this kind of stuff... so I would greatly appriciate if you assisted me step by step if you could... thx in advance again..
**don't wanna brick my bravo xD
Click to expand...
Click to collapse
It will run stock 2.2.1 yes. If you follow the instructions from the tutorial, and you have at least a little battery left you should be fine, since you will have your phone plugged into your computer. You will have to re-root as well. When you sbf, you have to start all over, including rooting. Just make sure you follow the tutorial step by step. It does a much better job explaining how to fix everything.

Dr. Orange said:
It will run stock 2.2.1 yes. If you follow the instructions from the tutorial, and you have at least a little battery left you should be fine, since you will have your phone plugged into your computer. You will have to re-root as well. When you sbf, you have to start all over, including rooting. Just make sure you follow the tutorial step by step. It does a much better job explaining how to fix everything.
Click to expand...
Click to collapse
ok thx sooooo much.. approximatly how long will this take

hotshot545 said:
ok thx sooooo much.. approximatly how long will this take
Click to expand...
Click to collapse
Maybe an hour to get you back to jelly bean. It's worth it to take your time before each step so you don't mess anything up.

Dr. Orange said:
Maybe an hour to get you back to jelly bean. It's worth it to take your time before each step so you don't mess anything up.
Click to expand...
Click to collapse
Dude thx a bunch... i'm up and running jelly bean again using 2nd init btw next time i flash how would i do it without 2nd init

hotshot545 said:
Dude thx a bunch... i'm up and running jelly bean again using 2nd init btw next time i flash how would i do it without 2nd init
Click to expand...
Click to collapse
To reboot into recovery, hold the power/hold button down til that menu pops up, then select reboot, then select recovery. It was my pleasure helping. If you have any other questions just ask in the bravo general section and eventuality someone will help. Everyone with bravo is very supportive.
Edit: in recovery you will have options like reboot, wipe cache, wipe data, flash zip, backup/restore, that sort of thing. Usually I backup first just as a precaution, before wiping data and cache and then flashing a new rom. For other zips like gapps, cpu governors, or anything else you can just flash the zip without wiping.

Dr. Orange said:
To reboot into recovery, hold the power/hold button down til that menu pops up, then select reboot, then select recovery. It was my pleasure helping. If you have any other questions just ask in the bravo general section and eventuality someone will help. Everyone with bravo is very supportive.
Edit: in recovery you will have options like reboot, wipe cache, wipe data, flash zip, backup/restore, that sort of thing. Usually I backup first just as a precaution, before wiping data and cache and then flashing a new rom. For other zips like gapps, cpu governors, or anything else you can just flash the zip without wiping.
Click to expand...
Click to collapse
I'm gonna add, since the recovery option in the power button menu doesn't always access 2nd-init recovery (depends on the rom), nor is that option available in all roms, you just need to push the volume up button when the led light turns green when booting up to access the bootmenu. I've had cases where reboot menu recovery went to stock recovery instead of 2nd-init.
Its also a good idea to wipe cache\dalvik cache when flashing things like lockring mods, framework themes, and most theme related mods in general.

skeevy420 said:
I'm gonna add, since the recovery option in the power button menu doesn't always access 2nd-init recovery (depends on the rom), nor is that option available in all roms, you just need to push the volume up button when the led light turns green when booting up to access the bootmenu. I've had cases where reboot menu recovery went to stock recovery instead of 2nd-init.
Its also a good idea to wipe cache\dalvik cache when flashing things like lockring mods, framework themes, and most theme related mods in general.
Click to expand...
Click to collapse
When i start the phone up the led turns blue a few seconds before the boot animation appears... its that when i want to press the volume up key

hotshot545 said:
When i start the phone up the led turns blue a few seconds before the boot animation appears... its that when i want to press the volume up key
Click to expand...
Click to collapse
My fault, its Volume Down, and yes, the green blink before the blue is when you push it.
I got it confused with Stock Recovery, which is Power Button+Volume Up while turning on the phone.

Stuck in infinite CM spinner on Verizon LG G2

I'm a bit of a newbie with rooting and flashing but have been pretty successful up until now. I installed TWRP 2.3.6.2 and CM 10.2 on my Verizon LG G2 about a month ago.
Since then I've been updating with nightlies with much success.
When the 11.0 build showed up in the CM updates list I downloaded it and installed. It failed and I had to flash an older 10.2 nightly. My device became pretty unstable after this. Most GApps were gone or somehow corrupted. I re-installed a number of them but Google Play still didn't work.
I tried updating again to an 11.0 nightly today and again it failed. I then flashed a recent 10.2 nightly that had worked for me and now my phone is stuck an infinite spinning Cyanogenmod boot screen.
I have tried every combination of holding power and volume down to try to get into TWRP to try flashing another nightly but my device just continues to reboot to LG then Cyanogenmod spinner over and over.
I decided maybe I needed to reinstall TWRP (looks like there's a new version from today). I tried to access my device with it plugged into my computer using fastboot and adb push loki_flash and it returned "device not found."
I'm totally stuck now... no idea what to do next. Would be so grateful for some guidance on how to get my device functional again.
Thanks.

One additional comment: I've tried doing Power + Volume Down during LG logo but it doesn't do anything.
I managed to get into a Hardware Key Control Mode screen by holding Power + Volume Up + Volume Down which had some options about answering calls or turning off alarm using hardware keys.
Cannot seem to do anything to get to TWRP.

To get to TWRP:
* Hold Power until the phone shuts off
* Hold Power+Volume Down until the LG logo appears
* Release Power+Volume Down then immediately hold them both down again
You'll get a message to the effect of 'Press Power to permanently erase all user settings.' Do that (if you have a custom recovery installed, it'll just boot into that).
Also keep in mind that the first install of a custom rom like CM will sit on that logo screen for a couple of minutes.

I somehow just managed to get to a screen that says "Factory hard reset. Permanently Erase User Data & Reset Settings? Press Power key to confirm, and any other key to cancel." It says "Rooted" in the upper left corner.
The screen doesn't respond to Volume Up or Volume Down and I just let it sit there for a few minutes. It reverted back to the infinite CM spinner.
At this point I'm pretty much at a loss for what to do -- and afraid to do anything to mess things up even more.
Should I be trying to go back to stock? http://forum.xda-developers.com/showthread.php?t=2432476

antinorm said:
To get to TWRP:
* Hold Power until the phone shuts off
* Hold Power+Volume Down until the LG logo appears
* Release Power+Volume Down then immediately hold them both down again
You'll get a message to the effect of 'Press Power to permanently erase all user settings.' Do that (if you have a custom recovery installed, it'll just boot into that).
Also keep in mind that the first install of a custom rom like CM will sit on that logo screen for a couple of minutes.
Click to expand...
Click to collapse
Thanks for this suggestion -- I'll try to get back to that screen and do this. Also the CM spinner was stuck for 8 hours last night... so definitely not a function of bit of a delay for first install of a custom ROM.

tophy0 said:
I somehow just managed to get to a screen that says "Factory hard reset. Permanently Erase User Data & Reset Settings? Press Power key to confirm, and any other key to cancel." It says "Rooted" in the upper left corner.
The screen doesn't respond to Volume Up or Volume Down and I just let it sit there for a few minutes. It reverted back to the infinite CM spinner.
At this point I'm pretty much at a loss for what to do -- and afraid to do anything to mess things up even more.
Should I be trying to go back to stock? http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
This screen is what you want to see. Push Power a couple of times. It won't erase your settings. It'll boot into TWRP.

tophy0 said:
Thanks for this suggestion -- I'll try to get back to that screen and do this. Also the CM spinner was stuck for 8 hours last night... so definitely not a function of bit of a delay for first install of a custom ROM.
Click to expand...
Click to collapse
Phew, that worked! Back into TWRP.
Any additional guidance on what I should be doing to try to get back into a stable version of CM? I have many builds of CM 10.2 in internal storage that I could pick from. But before I try another one of those should I attempt to clean things up at all? Seems like my current configuration must have some sort of conflict that's leading to all the instability. I do have Titanium Pro installed so I believe I should be able to get my apps + data back as long as I don't completely clean out everything.
Thanks again for the help.

Also mods: just realized that I should have posted this thread in Q&A not General. Sorry about that! I don't think I can move it over myself or I would.

I think what I would like to do now is update TWRP to 2.6.3.3 and then install 11.0 using this build: http://www.droidforums.net/forum/lg-g2-development/258385-rom-wip-cyanogenmod-11-g2-vzw.html
Not sure how to update TWRP from 2.6.3.2 to 2.6.3.3 though. When I originally set up TWRP I used adb / loki-push but it's a bit of a blur how that worked since I was just following step 1-2-3 instructions.
Sorry for being such a noob with this stuff. Any additional guidance would be awesome.

As I suspected, flashing any CM ROM now leads to an infinite CM spinner so I think I need a plan B to get my device working again. At least I can now get to TWRP thanks to the help above.
Not sure where to go from here.

Did you try to wipe data, cache, dalvik cache and system? Then install cm. I think this is why you got a bootloop :/
Sent from my GOOPHONE i5C using XDA Premium 4 mobile app

Makrilli said:
Did you try to wipe data, cache, dalvik cache and system? Then install cm. I think this is why you got a bootloop :/
Sent from my GOOPHONE i5C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yup, when I finally got into TWRP I did this and was able to install a version of CM 10.2 that actually loaded.
All my apps and settings are obviously gone now so it's a good time to make the leap to TWRP 2.6.3.3 and CM 11.0. Trying to figure out how to do that now (in the proper forum!):
http://forum.xda-developers.com/showthread.php?t=2563982
Thanks for the help.

tophy0 said:
Yup, when I finally got into TWRP I did this and was able to install a version of CM 10.2 that actually loaded.
All my apps and settings are obviously gone now so it's a good time to make the leap to TWRP 2.6.3.3 and CM 11.0. Trying to figure out how to do that now (in the proper forum!):
http://forum.xda-developers.com/showthread.php?t=2563982
Thanks for the help.
Click to expand...
Click to collapse
I htink the wipe would have helped from the beg. Any time you jump roms I suggest doing a wipe. Also one thing you may want to look at is a backup of all your settings and everything, I use titanium and it has helped me out in situations like this in the past.

madisonjar said:
I htink the wipe would have helped from the beg. Any time you jump roms I suggest doing a wipe. Also one thing you may want to look at is a backup of all your settings and everything, I use titanium and it has helped me out in situations like this in the past.
Click to expand...
Click to collapse
Thanks, makes a ton of sense.
I also use Titanium to backup. When I do a fresh install of TWRP and CM 11.0 can I restore my system data in addition to apps + app data? I'm not sure to what restoring extent system data could create conflicts with the CM 11.0 build. For example will all the Google Mobile Services system data from my CM 10.2 build create conflicts?
What I really want is to easily bring back ~150 apps + all of my SMS messages, Contacts, Email settings, Homescreen layout and settings, etc. Not exactly sure what's achievable.

tophy0 said:
What I really want is to easily bring back ~150 apps + all of my SMS messages, Contacts, Email settings, Homescreen layout and settings, etc. Not exactly sure what's achievable.
Click to expand...
Click to collapse
You can safely use TB to restore user apps, their data and trebutchets data if you use that. Backing up sms and contacts with TB, I'm not sure about that as I used other app "super sms backup". And about emails I have no idea. Also it's not a good idea to restore settings, better to set them again
Sent from my GOOPHONE i5C using XDA Premium 4 mobile app

antinorm said:
To get to TWRP:
* Hold Power until the phone shuts off
* Hold Power+Volume Down until the LG logo appears
* Release Power+Volume Down then immediately hold them both down again
You'll get a message to the effect of 'Press Power to permanently erase all user settings.' Do that (if you have a custom recovery installed, it'll just boot into that).
Also keep in mind that the first install of a custom rom like CM will sit on that logo screen for a couple of minutes.
Click to expand...
Click to collapse
I owe you man! Saw the erase data screen and almost freaked out. Pressed power and it booted to TWRP.
Thanks again!
Mike

WCM3 said:
I owe you man! Saw the erase data screen and almost freaked out. Pressed power and it booted to TWRP.
Thanks again!
Mike
Click to expand...
Click to collapse
You know, I was wondering as well of how to get to TWRP if a rom didn't boot. I got to that screen too and thought it would erase the phone. This is good to know and should be a sticky somewhere.