Can't Full Format Phone? - HTC One V

Okay all the sudden on CFX 4.2.2 I am having weird issues, I converted google search to a user app, then back to a system app, and it would constantly crash, I now try and format the phone ie: wipe date/cache/dalvik and reboot into the ROM, I no longer get a prompt about a gmail account or anything like that and the ROM boots right up with no gmail notifications or anything, and google search still isn't working, why can I not format my phone lol?
I even tried re-flashing the ROM after a full wipe/format and it still is all beyond messed up?
WTH, even after a fresh ROM install with no flash over with GAPPS, it's still on the device like it was never formatted -.- im using CWM 6.0.1.5, i've never had issues with this recovery or anything, now all the sudden it's like GAPPS will not delete from the ROM.
Okay, a different attempt at flashing a completely different ROM then reflashing CFX, reflashing a different ROM got rid of GAPPS, so now im in the process of reflashing CFX to see if that fixed my problem, if it did idk why wiping the ROM itself wouldnt get rid of GAPPS.
Okay that fixed it =S.
I take that back, nope i guess im just screwed lol.
Okay i've come to the conclusion that something is just wrong with the ROM

Did you wipe the System partition before installing the new ROM? When you flash the GApps zip file in recovery, it writes those to System. Therefore, if you just wipe Data, they will still be there. Also, always do a full wipe (system, data, cache, dalvik) when switching to a different ROM.

Related

[Q] need some help

so imma newbie and i tryed to flash the destroyer rom onto my evo when i reboot run the rom it keep showing destroyer animation over and over does anyone else know why ?
Wait 10 mins, if nothing, try reboot, still nothing? Flash again.
Make you sure you follow directions when flashing a custom rom. Wipe data/cache/dalvik cache.
hTC Evo CM7-n17
You didn't flash it correctly and you got what is called bootlooping. Just wipe factory/data, cache, and dalvik and then try again.
It will bootloop if you flash the ROM and gapps in the same recovery session. You have to flash ROM, reboot, then go back into recovery, wipe dalvik and flash gapps. If you want the extras, flash larger gapps first, then reboot again and wipe dalvik and flash smaller gapps.
so i reflashed it worked just one problem my visual voicemail doesn't work at all
blakrepublic said:
so i reflashed it worked just one problem my visual voicemail doesn't work at all
Click to expand...
Click to collapse
You need to either flash back to a sense rom, verify that it works, like have someone call you and leave a message, then use titanium to backup the app and data, flash back to The Destroyer rom, restore the app and data, NOT system settings, or use google voice or a third party carrier.

cm9 and gapps?

so i loaded cm9 ics on my fire and everything worked great. then i flashed the gapps zip and when i turn on the fire the prompt screen comes on that comes on everytime you buy a new device, the one where you are prompted to touch the android and then you will enter your info and stuff. well, everytime i touch the android, it says "unfortunately the setup wizard has stopped" with a force close button. any ideas how to get gapps on?
May not have wiped everything properly, or flashed a corrupt gapps zip.
Either way, you can get around the issue from TWRP by deleting the file /system/app/SetupWizard.apk using the built-in file manager or ADB.
Dasanko said:
May not have wiped everything properly, or flashed a corrupt gapps zip.
Either way, you can get around the issue from TWRP by deleting the file /system/app/SetupWizard.apk using the built-in file manager or ADB.
Click to expand...
Click to collapse
Agreed, first try to wipe again. Factory reset (2x) for good measure, wipe cache, wipe Dalvik, Flash ROM, flash Gapps, boot. May even wipe cache/dalvik again after flashing. Not usually needed, but sometimes KF can get stubborn.
chemo1191 said:
Agreed, first try to wipe again. Factory reset (2x) for good measure, wipe cache, wipe Dalvik, Flash ROM, flash Gapps, boot. May even wipe cache/dalvik again after flashing. Not usually needed, but sometimes KF can get stubborn.
Click to expand...
Click to collapse
Question...I am too having this issue. Only difference is something happened to my USB and my computer can't install the device files anymore so I'm flashing the ROMs thru ROM manager now since I can't connect my phone to the computer. I know I'm using the right gapps but if I delete the apk for the setup wizard how will i be able to sign into my google account?

cant flash rom

Currently running Lifeless 14. I'm wanting to try the optimus 4.3
I do a backup, download the new rom. I wipe 3 times (cache, system, data, and dalvik). and even do a factory reset. Then flash the new rom.
Upon doing so I try to boot up but sits at the LG logo screen.
I tried redownloading the rom thinking there was an error. Same result
I also tried not wiping data for the hell. The flash was unsuccessful.
My only thought was a long time ago I tried AOSP but switched back to stock. Does this affect my issue possibly? IF so, how can i fix it without doing a complete wipe (including internal storage).

[Q] "gapps stopped" loop after CWM restore

Hi,
I was frustrated with the delay in T-Mobile's release of KitKat for the GSIII, so I decided to root my phone last night in order to try flashing CM11 on it. Rooted my phone with Towelroot, installed ROM Manager and CWM, and created backups on Kies and through CWM. Then I proceeded to do data wipe/factory reset, cache wipe, and /system format. Tried to flash CM11, but got a status 7 error.
I freaked out, so I decided to restore everything from the backup I'd created. Restoration seemed like a success, but now I get the error "Unfortunately, the process com.google.process.gapps has stopped" in an endless loop, and it prevents me and any apps from doing anything. I tried clearing dalvik cache in recovery, but the problem still persists. Read on a few threads that I should flash to stock firmware via Odin, but I'm currently on a macbook, so I can't install it.
tl;dr - Prepped to flash CM11, reached status 7 error, got freaked out, and did restore via CWM, only to get infinite loop of gapp crashes. No access to Odin or PC. Not hard bricked or soft bricked, but essentially useless phone. Help? );
if you can still get to recovery, download latest gapps and flash that
Did you factory reset before or after you restored your back up?
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Try to factory reset again
vvnn said:
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Click to expand...
Click to collapse
If I'm not mistaken, there is some device ID that will change each time you flash a new rom. It may be something to do with this ID not matching the one in the restored data. Purely a guess but seems logical to me.
Anyway, factory resetting will most likely solve this for you, but I wanted to add that except in certain circumstances, you shouldn't ever manually format /system. (and one format on any partition is sufficient. There shouldn't be any need to format multiple times). If you format /system, you are wiping the O/S off of your device. Then what happens if you have problems flashing a rom, or firmware? I've seen it happen many times and I often end up spending a couple of days working with them just to get the thing to boot up again!
When you flash a rom, the first thing it does is format /system. So there is just no need to do this manually. At least if the rom fails to flash (such as failing the assert checks), youll still have something to boot into. Hope this helps in the future!
I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.

Issues flashing ROM

I'm having some issues flashing any ROM. TWRP will not wipe data, or internal SD
For some reason, when I go to wipe data and factory reset, TWRP will say it was successful, but nothing ever gets wiped. It will only wipe system if I choose to. I've gotten a ROM to flash but when it boots up, all of the old apps and user data are still there and it makes everything crash. I've gotten into settings to do a reset, it reboots into recovery, runs the script, and still nothing wipes.
What I have tried:
Old TWRP, newest TWRP
CWM (seems to wipe but it won't get past the note 2 screen after flashing anything)
Wiping with CWM, flashing TWRP, then flashing a ROM (still loops after the note 2 screen)
Is there a terminal command I can use in TWRP to manually wipe things?
Thanks for any help I can get, I've flashed so many phones I can't remember but I've never had this issue
Maybe flash back to a stock ROM, factory wipe using stock recovery, then flash TWRP?
audit13 said:
Maybe flash back to a stock ROM, factory wipe using stock recovery, then flash TWRP?
Click to expand...
Click to collapse
Well when it bootloops t the Note 2 screen, I have to flash a ROM with Odin to get it working again. I've flashed a stock ROM with Odin, flashed TWRP with Odin, tried the wipes and it never wipes anything... I'm lost...
Isn't there a format function in TWRP that is seperate from the factory reset or advanced wipes? I was also trying to find a terminal command to type in the terminal in TWRP... I'm a little stumped...
I'm sorry, I read that too fast... That may actually work, wipe it in the stock recovery, and just don't let it boot into the system before flashing other stuff... I'm gonna try that out... Thanks man, I'll post back about it...
Since you are flashing the phone with Odin, is it a stock 4.1.1 ROM you're flashing? Which custom ROM are you flashing to the phone?
audit13 said:
Since you are flashing the phone with Odin, is it a stock 4.1.1 ROM you're flashing? Which custom ROM are you flashing to the phone?
Click to expand...
Click to collapse
The stock ROM I used is I317-ODIN-UCUCNJ1-Stock without the booloader packaged in, I'm still on the old bootloader. It's 4.4.2
The ROMS I've tried to flash was
Cyanide (Error 7, says incompatible data, please wipe the phone)
Resurrection Remix (Error 7, says incompatible data, please wipe the phone)
Latest CM10 Nightly
I got CM10 and Resurrection Remix to flash a couple times, but the phone boots and all the old apps and data, including the AT&T ones are still there, and the system keeps crashing. Then I change the recovery to CWM because it seems to wipe, change back to TWRP, flash the ROM and gapps again, but it bootloops at the Note 2 screen.
Should I try the 4.1.1 ROM and CWM? Whenever I'm going from a stock TW to non-TW I like to format everything, data, cache, system, and internal SD, but of course TWRP won't wipe the data or the internal SD.
It's probably because the bootloader and modem are too old for the roms. Recent roms will need updated bootloaders.
Ok, I had some more time to mess around with this today and figured it out. I feel kind of dumb but oh well, I got it.
TWRP was already loaded on, so I went to messing with it again. The 'Swipe to factory reset' was not wiping the data, and there was the 'Format Data' button right there in front of me. I did the factory reset, format data, rebooted recovery, wiped dalvik, cache, and system, then flashed the ROM and everything booted up just fine.
Thanks for all of the help!

Categories

Resources