EVO 4g looping after overclocking Netarchy kernel to 1.2 ghz - EVO 4G General

I've been using Mikfroyo 4.5 for a few weeks now and finally decided to flash a kernel. I chose this one here
http://forum.xda-developers.com/showthread.php?t=719763&highlight=rebooting
I think I am using clockworkmod recovery and I've been using rom manager to flash my roms and Mikfroyo had a built in reboot to recovery feature that I used to reboot my phone into recovery to flash the new kernel. I did not delete dalvik cache or anything I think. I'm not entirely sure. So when i tried to set the cpu to the max that it would allow it froze twice. and i rebooted each time and chose a different setting. I also saw a setting that said "set at boot" and i chose yes for that option. After a random reboot it seems to freeze just after the lockscreen shows up and it starts setting up the sd card. I have held down the power and raise volume button and nothing happens. And I have also tried the hold down power and lower volume button and nothing happens. Am I supposed to do both volume buttons at the same time? How can I fix my phone? It is completely unusable right now. Please help!!

sent17inel said:
I've been using Mikfroyo 4.5 for a few weeks now and finally decided to flash a kernel. I chose this one here
http://forum.xda-developers.com/showthread.php?t=719763&highlight=rebooting
I think I am using clockworkmod recovery and I've been using rom manager to flash my roms and Mikfroyo had a built in reboot to recovery feature that I used to reboot my phone into recovery to flash the new kernel. I did not delete dalvik cache or anything I think. I'm not entirely sure. So when i tried to set the cpu to the max that it would allow it froze twice. and i rebooted each time and chose a different setting. I also saw a setting that said "set at boot" and i chose yes for that option. After a random reboot it seems to freeze just after the lockscreen shows up and it starts setting up the sd card. I have held down the power and raise volume button and nothing happens. And I have also tried the hold down power and lower volume button and nothing happens. Am I supposed to do both volume buttons at the same time? How can I fix my phone? It is completely unusable right now. Please help!!
Click to expand...
Click to collapse
You can try reflashing Mikfroyo 4.5 without wiping and see if you can recover, or just flash another kernel over what is currently installed to reset setcpu. It's not wise to enable "set at boot" until you are sure that your settings are stable.

How can I flash a new rom or kernel if I can't get it to fully boot? It gets to the lock screen and then reboots. I have tried the holding down power button and volume and nothing happens. It still continues to boot up.

nandroid backup or full data wipe. Other than that fast fingers and you gotta hurry to the app and turn of start at boot before it starts loopin

chandlerw88 said:
nandroid backup or full data wipe. Other than that fast fingers and you gotta hurry to the app and turn of start at boot before it starts loopin
Click to expand...
Click to collapse
No way it would let me get that far. I've tried.
Soo nandroid backup or full data wipe. Either sound fine with me. How do I do that though?

Pull out battery, wait a couple seconds to put it back in, and press power and volume down until white screen shows up. You should know the rest.
It sounds like your messing around with a lot of things you don't know about. Before you do anything like majorly over clocking CPU Research it first
Sent from my Superphone. (Evo)

chandlerw88 said:
nandroid backup or full data wipe. Other than that fast fingers and you gotta hurry to the app and turn of start at boot before it starts loopin
Click to expand...
Click to collapse
Ha, had to do that a few times myself. Gotta be very quick lol.
Sounds like you aren't holding down the volume button if its starting up normally. Set CPU wouldn't have messed up your recovery. Hold down the volume button before pressing the power button and don't let go untilled the white screen pops up. Then you can reflash mikfroyo.

That was all I needed. I looked up a couple ways on how to get into recovery and they were all very vague. I didn't know that you needed to initially hold down power button and volume. I was initially tapping the power button and then holding power and volume. But I should be able to take it from here. Thank you everyone for you speedy responses!!!

When you flash a kernel you are supposed to clear cache and dalvik or else you will get the issues you described.also running set cpu at max can cause instability and random reboots.

Most 1gHz devices will only support overclocking around 1.9 before coming unstable. do as the thread says FULL WIPE, reflash rom, flash kernel, boot, then when adjusting set cpu dont "set on boot" until you have tried it out first.

pureEVO91 said:
Most 1gHz devices will only support overclocking around 1.9 before coming unstable. do as the thread says FULL WIPE, reflash rom, flash kernel, boot, then when adjusting set cpu dont "set on boot" until you have tried it out first.
Click to expand...
Click to collapse
A 1Ghz device at nearly 2Ghz! That's an awesome overclock!!! How stable?

Its completle stable in a powered off state!!!
Sent from my PC36100 using XDA App

^^^ yeah... lol
1.19 is best I can do on my evo.. before lockup/reboot.
i wish we can do 1.9
OP.. sounds like you got it handled...
and was able to get into recovery. I hate ROM manager... because of this kind of issues.. you did not really know how to do it manually.
to a nandroid restore or flash the ROM again (only wipe cache and dalvik) should fix it.
I did the same thing when i first tryed to overclock my last phone and checked "set on bootup". Learned.. never do that till I am 100% sure it is stable.
I was a noob back then.. and what I did was put my phone in the freezer.. then raced the clock before the cpu overheated and locked up. LOL silly.. but it worked.

hah. Our evos don't have enough of a heat sink to reach 1.9ghz

Wow. Sry guys didn't mean to miss post. 1.19gHz

Oh ok 1.19 sounds alot better. I was lookin like 1.9 WOOOOOOOOW!!!! I wish mine would go that fast.
I had the same problem as you b4. Netarchy's kernel doesnt like overclocking. Looks like your good tho....

Related

Cyanogem Mod - stuck on boot screen

Hi:
Really need some assistance here.
I am currently trying to install CM 7.0 RC1. From my ROM manager I selected the CM MOD and it went to reboot and install. Now it is just stuck on a screen with a little green Android Logo and Exclamation.
What can I do here? I am afraid to pull the battery but it doesn't seem to be moving past this point.
Do you have a custom recovery like Amon_RA or ClockWorkMod installed?
cyrus_mc said:
Hi:
Really need some assistance here.
I am currently trying to install CM 7.0 RC1. From my ROM manager I selected the CM MOD and it went to reboot and install. Now it is just stuck on a screen with a little green Android Logo and Exclamation.
What can I do here? I am afraid to pull the battery but it doesn't seem to be moving past this point.
Click to expand...
Click to collapse
You'll be fine pulling the battery since you're only flashing a ROM... it's a NO NO when flashing Radio though. That being said... the CORRECT way to restart when you're in a bootloop or stuck on that particular screen is to use the three finger salute and reboot by holding down the power button, volume down button, and pressing the trackball. From there, I'd immediately hold down the volume down button, which will force the phone into the bootloader and you can enter Recovery from there. Do a FULL wipe of data and cache, as well as dalvik-cache from the Advanced menu, then flash the ROM.
uansari1 said:
You'll be fine pulling the battery since you're only flashing a ROM... it's a NO NO when flashing Radio though. That being said... the CORRECT way to restart when you're in a bootloop or stuck on that particular screen is to use the three finger salute and reboot by holding down the power button, volume down button, and pressing the trackball. From there, I'd immediately hold down the volume down button, which will force the phone into the bootloader and you can enter Recovery from there. Do a FULL wipe of data and cache, as well as dalvik-cache from the Advanced menu, then flash the ROM.
Click to expand...
Click to collapse
Yup this is what to do. Quick bit of info; You can get to the boot loader by simply holding the volume button down and pressing the power button, just a little easier to do
That's what I had to do. Mine also got stuck.
Sent from my Nexus One using XDA App
Hollow.Droid said:
Yup this is what to do. Quick bit of info; You can get to the boot loader by simply holding the volume button down and pressing the power button, just a little easier to do
Click to expand...
Click to collapse
Agreed. I was just referring to what to do if you're stuck on the X or in a boot loop. ;-)
Sent from my Nexus One using Tapatalk
You're stuck with stock recovery. Reboot back to ROM, install recovery, only then reboot to install ROM.
Hey guys I'm having a similar problem, however my phone gets stuck on the initial nexus screen. I've been working on the phone problem for the better half of the day and this is what i've done, what works, and what doesn't.
WHAT I'VE DONE:
Full wipe, including Devik
Played around with installing different radios.
Download CM7-RC1 from CWM and the computer
WHAT WORKS:
MIUI Roms
Stock Gingerbread Rom
MY Back-up, which has CM7 Nightlie #45
WHAT DOESN'T:
All Cyanogen Mods
I even tried the CM6.0
So I'm a little stump on how to get my phone to run the latest Cyanogen or matter of fact, any CM Roms. Maybe my phone wants something different in her life
Any help will be great guys...thx
How much time did you wait?
Did you try erasing /system?
Well I just waited for 5 hours leaving it on the initial Nexus screen, in hopes it might do something, but it was to no success.
/system? not quite sure where that is... I am assuming it's in the roots... I can only do what I can from the recovery.
Try to install LeoGingerbread, for example. Does it work?
If yes - right after it installs, try to flash CM7.
cyrus_mc said:
Hi:
Really need some assistance here.
I am currently trying to install CM 7.0 RC1. From my ROM manager I selected the CM MOD and it went to reboot and install. Now it is just stuck on a screen with a little green Android Logo and Exclamation.
What can I do here? I am afraid to pull the battery but it doesn't seem to be moving past this point.
Click to expand...
Click to collapse
Whenever you see "little green Android Logo and Exclamation", you can press volume up and power button together to get into the bootloader menu and reboot your N1. It seems like your custom recovery did not work. Try to flash Clockworkmod recovery 2.5.1.4 (not 3.0.0.5) or RA recovery again. It may help.
Jack_R1 said:
Try to install LeoGingerbread, for example. Does it work?
If yes - right after it installs, try to flash CM7.
Click to expand...
Click to collapse
Wow that actually worked, thanks... can you explain why this is needs to be done to get it to work?
LeoGingerbread executes "format /system", that actually works and cleans the remains of the old OSes. Some other ROMs do, too.
armyshawkeye said:
Wow that actually worked, thanks... can you explain why this is needs to be done to get it to work?
Click to expand...
Click to collapse
Because you still have the stock recovery installed, that is how you access the menu for it.
Here's a flashable script that does the same thing. It was put together by temasek - I'm just sharing...
http://db.tt/wdeoIMI
Sent from my Nexus One using XDA App
danger-rat said:
Here's a flashable script that does the same thing. It was put together by temasek - I'm just sharing...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
How I flash this? As a update.zip?
Yes. I believe it executes "FORMAT SYSTEM:" command, maybe more than once.
Yes, it formats system, boot, data, and cache, each twice...
It's quicker than flashing a full ROM to achieve the same results...
Sent from my Nexus One using XDA App
danger-rat said:
Yes, it formats system, boot, data, and cache, each twice...
It's quicker than flashing a full ROM to achieve the same results...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
CW Recovery has options to format system, and other partitions, under Mounts and Storage.
Sent from my Nexus One using Tapatalk

droid pro, 902, cm7

I have a pro rooted, running gingerbread, flashed cm7 902 build.
it works great, having nothing to compare it too as this is my first custom rom flash (long story if you would like to hear it to learn from my mistakes just ask), one minor issue i have seen is if you choose to let battery die till it suts down when you power back up you will not have data. Easy fix is just restoring to stock rooted and re flashing 902 and voila data is back, and oh yeah dont let battery die completely
thanks to dutchbastard, CrackMonkey91, jackpotclavin (for the build), and motorolaoneclick root method Pete Souza (spelling)
any question just ask i am an open book
when i installed newest 9-02 update the phone gets stuck in bootloop whats up with that
aymanfoa said:
when i installed newest 9-02 update the phone gets stuck in bootloop whats up with that
Click to expand...
Click to collapse
I had the same issue with a bootloop, just in a different situation. Go to recovery (Take out battery, hold Power+R+M, wait for the green Android and the ! in a triangle, then let go, then press both volume keys at once(Gingerbread) or the @ key(Froyo), use volume buttons to scroll up and down) and wipe the phone. It should say something like wipe, factory reset, restore, you get the point. Wait for it to finist, then reboot. If it shows an error, dont mind that. Mine did too but its fine.

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.

Cannot iniate reboot or shutdown

Hello,
I have tried searching but haven't been able to find a similar issue for any android devices (amazing right?). My nexus 7 will not respond to any soft reboot. From power menus to terminal to factory reset (yes including from ROM recovery and the like). It will reboot from the 10second press, but as we know that is pretty ineffective considering the nexus 7 has that bug where you can't access recovery from boot loader. I have tried connecting to a PC to force recovery, Nada.
So now I am out of idea. Also, for the next 2 weeks I don't have a PC, only a gnex and nexus 7...
Any help appreciated.
update your bootloader and recovery, that bug has been fixed. what rom are you running, every single reboot/power off option works here.
I can't update it without being able to reboot. And I know its not a common issue.. hense why I ask for help... I am not reporting a issue, I am asking for ideas... thanks for the tremendous comprehension though
Oh, I forgot an important bit of info. It started happening after a kernel update (to fauxs latest) and now most programs that require root will be laggy or crash. And every 10sec reboot I do, apps "optimize" every time and every action, including downloaded files are missing since the last boot. (ie, I am always at the exact same point of the first boot after the kernel flash)
MatAuc12 said:
I can't update it without being able to reboot.
Click to expand...
Click to collapse
Are you saying that you can't get into fastboot by long-hold power and then hold vol down as soon as the device restarts?
Sent from my HTC Desire S
MatAuc12 said:
Oh, I forgot an important bit of info. It started happening after a kernel update (to fauxs latest) and now most programs that require root will be laggy or crash. And every 10sec reboot I do, apps "optimize" every time and every action, including downloaded files are missing since the last boot. (ie, I am always at the exact same point of the first boot after the kernel flash)
Click to expand...
Click to collapse
let the battery die and power itself off, then charge it. flash another kernel for sure.
simms22 said:
let the battery die and power itself off, then charge it. flash another kernel for sure.
Click to expand...
Click to collapse
I did let it die for cold boot and again, understanding my problem means since I can't initiate a reboot or get into recovery I cannot flash anything
BillGoss said:
Are you saying that you can't get into fastboot by long-hold power and then hold vol down as soon as the device restarts?
Sent from my HTC Desire S
Click to expand...
Click to collapse
Exactly. That is extremely strange behavior and complexes me even more than a soft brick even though the device works
MatAuc12 said:
Exactly. That is extremely strange behavior and complexes me even more than a soft brick even though the device works
Click to expand...
Click to collapse
boot pressing volume down while pressing the power button into the bootloader, flash a different kernel via fastboot. you can flash franco kernel in fastboot, since it is in boot.img form, or extract the stock boot.img from a stock rom and fastboot flash that. ive had similar behaviors with test kernels, faux forgot something in the kernel. then download and flash the newest bootloadee to fix your recovery from bootloader bug.
Try simms22 approach first.But if you can't get into fastboot and you can boot into the ROM- then you could try rewriting the boot.img. Get the boot.img/kernel you want and use the dd command to write it.
Warning: you can do serious damage with the dd command.
If you need some help with this, let me know. But I accept no responsibility if things go terribly wrong.
Sent from my Nexus 7

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.

Categories

Resources