Stuck in infinite CM spinner on Verizon LG G2 - G2 Q&A, Help & Troubleshooting

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.

Related

[Q] Already rooted but Qs about Custom ROMs

I'm rooted but have never ran anything but stock on my phone. Only having experience with flashing WinMo devices, what exactly do I need to know before flashing a custom ROM?
If I flash, do I lose the data on my phone now (does it do a factory wipe)?
Most times toy will need to do a wipe of the data and cache to get a full rom working correctly.
Sent from my DROIDX using XDA App
Yeah, thanks.. Just downloaded ROM manager and Clockworkmod Recovery ($2), kinda following the instructions from Gummys post.
How long does this process take? I installed from SD and did the reboot.. I must of waited a good fifteen minutes before pulling the battery assuming it was stuck. Now it's sitting on the Gummy Screen with the 4 rotating colored android pics.
Got into recovery but it's not allowing me to apply the update.zip (e:can't open/cache/recovery/command)?
Dang it! I was in the middle of posting the following instructions when I got interrupted (at work)
Code:
Flashing will wipe your phone. The nice thing with android is -anything you have purchased or installed from the market will automatically be restored to your phone after you log in using your gmail account.
Let me qualify my statement though - I have flashed a few roms and my free apps were not automatically installed for whatever reason. My purchased apps were not installed either - but they were available for installation at no charge.
Here is another important thing to remember - this will only happen if you chose the correct settings in -uh well- settings. There are some options in there to back up your data to google. If you did that then 95% chance it will all be good.
I recently switched from the DX to the D1 (gave my wife the DX bc I wanted to try some D1 roms) and all my apps were installed and somehow google even migrated my current wallpaper over! I was blown away by that.
Also -make sure your contacts are set up to sync with google. if they are just being added to your phone and not in sync with your google account you are going to loose them all.
Flashing roms:
1. You need to get the droidx bootstrapper app from the market (or I think you can get it for free if you search clockwork mod on google and go to Koush's website. I just bought it to help the developer.).
2. Open the app.
3. Press the "Bootstrap recovery button"
4. You should get a dialog box saying success (or something and then press ok).
5. Press "reboot recovery".
6. Your phone will reboot into clockwork recovery (not the stock phone recovery). It will be a black screen with old school green letters and a menu.
a. In recovery you do not have a touch screen.
b. The volume rocker is up/down.
c. The camera button is "Enter".
d. The physical back button will take you back one menu (also I believe the power button but I always used the power button.
7. The first thing you want to do before you do anything is make a nandroid (backup) of your phone.
8. The opening screen of recovery has the option to create a nandroid. do that.
9. It takes around 5 minutes then choose to reboot your phone when it says, ""complete".
10. To flash a rom put ti...
Wish I would have just posted what I had. Maybe you would have had a nandroid to revert to.
Dang.
Yea. It shouldn't take that long. Sounds like something got hosed. I am getting interrupter again. I will try and get back with some info.
Awesome info, thanks for this. Did a factory wipe and now it's booting up normally (or so it appears into Gummy), will definitely bookmark that info though, thanks again man!
Were you installing Gummy. And did you follow the instructions exactly?
****EDIT****
looks like you got it. glad to hear that.

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

[Q] Can't boot... have been meticulous... Help please?

This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic
syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??
Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App
syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.
last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.
Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App
OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!

[Q] TWRP 2.6.3.2 getting stuck wiping cache on D801

Just installed newest version of TWRP with Loki pre-installed. When I boot to recovery and try to do a full wipe, it gets stuck while wiping the cache partition. The progress bar below the script window is still animated, but I left it sitting for a good solid 10 minutes to nno avail. I can hold the power button and it will reboot and everything is normal once it boots up. Anyone have this problem or have any ideas? Thanks y'all.
nicktheqwik82 said:
Just installed newest version of TWRP with Loki pre-installed. When I boot to recovery and try to do a full wipe, it gets stuck while wiping the cache partition. The progress bar below the script window is still animated, but I left it sitting for a good solid 10 minutes to nno avail. I can hold the power button and it will reboot and everything is normal once it boots up. Anyone have this problem or have any ideas? Thanks y'all.
Click to expand...
Click to collapse
Yeah, it has a problem with clearing partitions, you would want to pick "Use -rm rf method" in settings. It works though, it just takes a long time, >10min is certainly not unthinkable.
Running the same version of twrp here.. for some reason it takes quite a long time, as long as you see those gray bars moving just let it do its thing... it could possibly be the version of twrp that makes this take so long but it does this with a full factory reset to id suggest letting it sit for alittle longer and see what happens!
It will eventually go through. Like others have said, it takes a really, really long time. 10+ minutes for sure.
The answer is in the second post. Change that setting and you're golden.
Sent from my LG-G2 using Tapatalk

Unable to upgrade to 4.4.4

Hello,
I have been trying to upgrade my nexus 4 to 4.4.4 or 4.4.3. I currently run the rom below and keep getting system update notifications. its downloading the update over and over and failing and killed my data plan lastnight.
When I flash a rom for 443 right now it looks to install fine. With some roms i get halfway through the config, Just after giving your name if im right. You can scroll down on the page, the arrow at the bottom of the screen that you are to click to go to the next screen turns from a down arrow to a right arrow but it never lets you click it to continue. im stuck. ive tried unclicking everything. My only safety is having the backup from 4.4.2 and i restore it back.
Some roms let me go all the way through the config but when its at the home screen and is giving you the quick tutorial, you click on the screen to continue and you can hear it click so it knows you touched the screen but it never goes further. again cant get to my homescreen to do anything. have to restore.
Ive been in this loop for a while now and just looking for any suggestions to why i cant put 4.4.3 or 4.4.4 on? Wouldnt call myself a noob with all of this but im kinda feelin like it now.
Nexus 4, Android Version 4.4.2
Kernel Version 3.4.76-NexusExperience-CAF
Nexus 5 Experience Release 3.1 CAF Kernel
Build Jan 23 2014
Build No KOT49H
Any suggestions would be appreciated. Thx
blacktuxnc said:
Hello,
I have been trying to upgrade my nexus 4 to 4.4.4 or 4.4.3. I currently run the rom below and keep getting system update notifications. its downloading the update over and over and failing and killed my data plan lastnight.
When I flash a rom for 443 right now it looks to install fine. With some roms i get halfway through the config, Just after giving your name if im right. You can scroll down on the page, the arrow at the bottom of the screen that you are to click to go to the next screen turns from a down arrow to a right arrow but it never lets you click it to continue. im stuck. ive tried unclicking everything. My only safety is having the backup from 4.4.2 and i restore it back.
Some roms let me go all the way through the config but when its at the home screen and is giving you the quick tutorial, you click on the screen to continue and you can hear it click so it knows you touched the screen but it never goes further. again cant get to my homescreen to do anything. have to restore.
Ive been in this loop for a while now and just looking for any suggestions to why i cant put 4.4.3 or 4.4.4 on? Wouldnt call myself a noob with all of this but im kinda feelin like it now.
Nexus 4, Android Version 4.4.2
Kernel Version 3.4.76-NexusExperience-CAF
Nexus 5 Experience Release 3.1 CAF Kernel
Build Jan 23 2014
Build No KOT49H
Any suggestions would be appreciated. Thx
Click to expand...
Click to collapse
im assuming that you you wiped data? you are flashing over a CAF based rom and kernel(cm), and general android is not CAF based. how and what are you flashing as well, stock 443/444?
simms22 said:
im assuming that you you wiped data? you are flashing over a CAF based rom and kernel(cm), and general android is not CAF based. how and what are you flashing as well, stock 443/444?
Click to expand...
Click to collapse
Wipe data/cache, dalvik wipe
I installed - [ROM+KERNEL][CM11][KTU84M][CAF&AOSP] Nexus 5 Experience - CM11 Based [R8.2 - 12Jun
im sure im missing a step here. its user error. in the past i flashed a rom and that was all i needed to do. Im trying to do this upgrade without connecting to a pc, its been in the closet for a while. thought of using the raspberry pi if i needed to.
blacktuxnc said:
Wipe data/cache, dalvik wipe
I installed - [ROM+KERNEL][CM11][KTU84M][CAF&AOSP] Nexus 5 Experience - CM11 Based [R8.2 - 12Jun
im sure im missing a step here. its user error. in the past i flashed a rom and that was all i needed to do. Im trying to do this upgrade without connecting to a pc, its been in the closet for a while. thought of using the raspberry pi if i needed to.
Click to expand...
Click to collapse
ok..
did you make a backup in recovery? if you did, try this, as a wipe isnt required to upgrade. restore your backup, boot up, then go back and dirty flash that rom over what you have. dirty flash means dont wipe a single thing. btw, when you flash a rom, it automatically wipes dalvik and cache, so you never actually have to do that when rom flashing(and never have to wipe anything for kernel flashing).
when i did that i can see icons on the homescreen which is different but i still get stuck at the same spot. the screen is faded with a blue circle in the center that says welcome make your self at home. it has a create more screens for apps and folders wording at the bottom with an arrow, and a OK button.
I click OK and hear it click but nothing happens. i try to scroll for the arrow and hear actions but nothing happens. I can pull down the menu at the top and goto my email. but when i go back to home, that screen is still there. ive rebooted the device. tried clicking back to get past it. run task killer. it always comes back to this intro screen on the home screen
blacktuxnc said:
when i did that i can see icons on the homescreen which is different but i still get stuck at the same spot. the screen is faded with a blue circle in the center that says welcome make your self at home. it has a create more screens for apps and folders wording at the bottom with an arrow, and a OK button.
I click OK and hear it click but nothing happens. i try to scroll for the arrow and hear actions but nothing happens. I can pull down the menu at the top and goto my email. but when i go back to home, that screen is still there. ive rebooted the device. tried clicking back to get past it. run task killer. it always comes back to this intro screen on the home screen
Click to expand...
Click to collapse
weird. it happens after dirty flashing? the reason i said dirty flash is because those menus wont appear. it might be wise to flash the stock image, then reroot.
simms22 said:
weird. it happens after dirty flashing? the reason i said dirty flash is because those menus wont appear. it might be wise to flash the stock image, then reroot.
Click to expand...
Click to collapse
Can you point me in the right direction of the right stock image? i was downloading from googles developer site "Factory Images "occam" for Nexus 4" but i think that might be the wrong thing? wouldnt extract properly. several download attempts and methods
it was the right thing you were downloading probably, as it is a google site.
nexus factory images https://developers.google.com/android/nexus/images
how to flash the factory image http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Ive got adb working on my raspberry pi now and im able to send commands but im getting an error towards the end
error failed to load 'image-occam--ktu84p.zip' : Cannot allocate memory
what folder is it trying to copy it to? /system?
i couldnt delete aps from system/app
i removed some stuff from /android/data but that didnt help. same error.

Categories

Resources