I'm CyanogenMOD BakedGoods 1.0.1
I themed it using Nextheme
I also added TrackballWake [v0.1] and TrackballSkip [v0.1]
Now..I wanted to do a fresh reinstall...and wiped everything from Recovery. After I flash BakedGoods again...and reboot. I still have the Nextheme and TrackballWake [v0.1] and TrackballSkip [v0.1] installed. Why is that?
Now I'm having problems logging into Google. It won't log In. Even when I switch to the regular CyanMod...I remember that his ROM didn't come with the Google Apps...but when I reboot...the Google Apps is still there.
I'm really confused! Why is my phone not being wiped properly?
Wipe data, wipe dalvik, reflash.
Yeah...I do that...but when I reflash...I still have the theme and addons.
Yeah I also have a feeling that wiping in recovery doesnt actually wipe everything.
As for getting the login to work, flash the gapps zip which is on the cyonogen page with his rom. Dont do any wipes just flash the gapps zip which is file gapps-passion-ERE36B-2-signed.zip to be exact and it will let you login with google. I had the same problem after flashing cynogen rom coming from Desire rom.
hypersonicx said:
Yeah I also have a feeling that wiping in recovery doesnt actually wipe everything.
As for getting the login to work, flash the gapps zip which is on the cyonogen page with his rom. Dont do any wipes just flash the gapps zip which is file gapps-passion-ERE36B-2-signed.zip to be exact and it will let you login with google. I had the same problem after flashing cynogen rom coming from Desire rom.
Click to expand...
Click to collapse
O...I...C. Thanks! I thought that my N1 was starting to break...because I've been like flashing like crazy this past 2 weeks.
So anybody else have any ideas as to why the N1 is remembering what addons I've flashed? I've even done a Factory Reset from Settings...then went straight into HBOOT and use the Clear Storage before going into Recovery.
I would then wipe again in Recovery and then flash. Doing so actually got me a little further. It got rid of the theme colors but the theme icons were still showing up and also the trackball mod.
I **think** that some of the "themes" out there are basically modded ROMs as opposed to small theme files -- that may be completely wrong. Anyway, if they are modded roms, then wiping will not delete the ROM files (system files, inlcuding any icons).
Now, maybe this baked goods had those apps you mentioned in them.
If you really want to WIPE, and make it a definite that all the roms you've flashed are GONE, then WIPE --> flash stock rom --> reboot --> flash any custom rom
This may be the long approach, as you probably only need to wipe then flash any custom rom
Related
intalled AOSP Paradise and gapps on my defy(green lense) and everything seems to be working great except:
1. everytime i turn my phone off when i turn it back on the Mokee logo comes up 1st and then it loads AOSP fine but i have to re-enter all my google info
2. it doesn't save any of my settings.
3. it wont let me download any apps...they start downloading but just sit there downloading and if they do finish, it says cant install, not enough memory but i reformatted the sd partition in recovery before installing AOSP because i knew it didnt have enough memory to even install it.
4. Why does that Mokee screen come on still?
i had the Mokee ROM before but shouldnt that have gone away when i wiped data and cache?
Did i do something wrong on install? i did wipe data/factory reset, wipe cache, flashed ROM, flashed gapps, wipe dalvik cache and rebooted twice. it loads fine and everything seems to be working but i dont like having to start from scratch everytime i turn my phone on.
Help pls...frustrating
Try clean install as said in this thread.
forum.xda-developers.com/showthread.php?p=32093770#post32093770
Make sure you flash new rom before rebooting
Flash SBF and then Flash new ROM
[Q]AOSP Paradise
Euro_Rules said:
Flash SBF and then Flash new ROM
Click to expand...
Click to collapse
ok that fixed boot screen but not the redoing of google, downloading apps or saving settings...any other suggestions?:fingers-crossed:
i figured it out! i was missing the firmware from when i bricked it...so, i found a firmware file, flashed it and now it works like a charm!! yay
Moved to Q&A. Please ask all questions there.
I know it has been asked before, and I have searched the threads. reverting to stock is not a problem.
nexus 7 grouper when installing a custom rom (liquid smooth v2.9 specifically) I get stuck on the liquid boot image.
I have successfully installed v2.7 and am able to revert back to stock or custom.
after a data format, factory reset, and wiping all caches, installing the zip file from abd sideload, or directly from the device the new rom that has flashed will not get past the boot image. am I doing something wrong, or could I do something differently so that the new v2.9 boots up correctly?
I know it has been asked, but the most common answer is to go back to stock. okay, I get that. but I know this rom will run (it is flawless on my s3,) but I cant seem to get it working on the nexus.
thank you.
aircooledbusses said:
I know it has been asked, but the most common answer is to go back to stock. okay, I get that. but I know this rom will run (it is flawless on my s3,) but I cant seem to get it working on the nexus.
Click to expand...
Click to collapse
There have been numerous reports of bootup problems with "clean" LiquidSmooth ROMs in v2.7, 2.8 and 2.9.
Some possible solutions are:
Dirty flash on top of a LS ROM that boots (for instance dirty flash 2.9 on top of 2.7). When doing this you DON'T clear data and cache, but flashes new rom directly, along with gapps and kernel, and boots up. This has worked for some.
Another option when you get stuck on boot screen is to boot into recovery, and do factory reset and clear caches one more time, and try to reboot. It might take several times booting into recovery, and clear data/caches before it boots up, but again this has worked for some.
Finally you could also try the order in which you flash stuff. For instance try ONLY flashing rom, then reboot. If it works, then flash gapps. If it gets stuck, try flashing both rom and gapps in recovery, then reboot etc.
Hope that gives you something to play with! And I'm pretty sure that if you're insistent enough, you will eventually get it to boot! :good:
ameinild said:
There have been numerous reports of bootup problems with "clean" LiquidSmooth ROMs in v2.7, 2.8 and 2.9.
Some possible solutions are:
Dirty flash on top of a LS ROM that boots (for instance dirty flash 2.9 on top of 2.7). When doing this you DON'T clear data and cache, but flashes new rom directly, along with gapps and kernel, and boots up. This has worked for some.
Another option when you get stuck on boot screen is to boot into recovery, and do factory reset and clear caches one more time, and try to reboot. It might take several times booting into recovery, and clear data/caches before it boots up, but again this has worked for some.
Finally you could also try the order in which you flash stuff. For instance try ONLY flashing rom, then reboot. If it works, then flash gapps. If it gets stuck, try flashing both rom and gapps in recovery, then reboot etc.
Hope that gives you something to play with! And I'm pretty sure that if you're insistent enough, you will eventually get it to boot! :good:
Click to expand...
Click to collapse
I will keep trying. getting liquid to run on the fascinate was curious as well, but after a few flashes it took. I'll keep trying on the nexus.
Update: yes, persistence is the key. thanks
What I did was from v2.8 a factory reset, wipe cache and dalvik and flash from sideload
as expected it boot looped. manually booted into fastboot and flashed v2.9 again with only a cache and dalvik wipe.
this time it booted and I flashed gapps.
at the reboot I set up the rom to my liking and it seems to boot normally now.
aircooledbusses said:
at the reboot I set up the rom to my liking and it seems to boot normally now.
Click to expand...
Click to collapse
Yes, after it boots through the first time, I've only seen it boot normal from that point on.
Hey guys,
I'm not a total scrub at flashing roms and there's still a bunch of things that I don't understand. I'm pretty positive that I flashed Slimrom correctly but here's the situation.
Started on 4.2.2 Slimrom
Reboot to TWRP recovery
Format factory reset/format data, system, cache, dalvik cache
Flash Slimrom 4.3 stable build 1
Successfully reboots into 4.3
Okay now here's the weird part.
The first time I rebooted back into recovery to flash gapps. After I flashed gapps and tried to reboot into the rom, the phone freezes at the screen with "google" and the unlock sign on the bottom. The only way I can get it to boot into the rom again is if I reformat/reset EVERYTHING (including format data) and reflash 4.3. After a few tries of messing around with not wiping dalvik/cache and stuff I realized that even if I don't flash gapps it still freezes on the google screen. So here's my main problem
After flashing 4.3 slimrom, the phone boots into the rom only once. If I try restarting my phone it freezes on the "google" screen.
Anyone know what I'm doing wrong?
Just to clarify it's a LG Google Nexus 4 mako.
Sorry if I'm being redundant. I just want to give as much detail as possible. If you need anymore info let me know!
Thanks
ms3195 said:
Hey guys,
I'm not a total scrub at flashing roms and there's still a bunch of things that I don't understand. I'm pretty positive that I flashed Slimrom correctly but here's the situation.
Started on 4.2.2 Slimrom
Reboot to TWRP recovery
Format factory reset/format data, system, cache, dalvik cache
Flash Slimrom 4.3 stable build 1
Successfully reboots into 4.3
Okay now here's the weird part.
The first time I rebooted back into recovery to flash gapps. After I flashed gapps and tried to reboot into the rom, the phone freezes at the screen with "google" and the unlock sign on the bottom. The only way I can get it to boot into the rom again is if I reformat/reset EVERYTHING (including format data) and reflash 4.3. After a few tries of messing around with not wiping dalvik/cache and stuff I realized that even if I don't flash gapps it still freezes on the google screen. So here's my main problem
After flashing 4.3 slimrom, the phone boots into the rom only once. If I try restarting my phone it freezes on the "google" screen.
Anyone know what I'm doing wrong?
Just to clarify it's a LG Google Nexus 4 mako.
Sorry if I'm being redundant. I just want to give as much detail as possible. If you need anymore info let me know!
Thanks
Click to expand...
Click to collapse
Are you flashing the right Gapps package? Be sure you are flashing the latest 4.3 one.
abaaaabbbb63 said:
Are you flashing the right Gapps package? Be sure you are flashing the latest 4.3 one.
Click to expand...
Click to collapse
Yep I'm positive. I redownloaded both the 4.3 rom and gapps package multiple times just to make sure. Also it doesn't reboot even if I don't flash gapps. Doesn't boot at all if I flash both the rom then gapps at the same time.
bump
then, wipe data/factory reser and flash the stock rom. the rom might be the problem
davinnwilliam said:
then, wipe data/factory reser and flash the stock rom. the rom might be the problem
Click to expand...
Click to collapse
It works for everyone else though. It's Slimrom 4.3 stable build 1.
Rom isn't the problem.Slim rom beta 1(4.3) is super stable. Use any version of twrp recovery other than 2.6.1.0 and wipe system+data,flash slim rom,flash slim gapps,reboot.
Note: if you flashed franco kernel then this may be the issue for your bootloop also you may want to upgrade your bootloader and radio to 4.3 versions(bootloader more important)
Just flashed OmniRom beta 2 build together with gapps linked in the OmniRom thread and I get fc on first boot on both NFC service and one more android service something something - can't get passed the pop ups and a reboot into recovery is all I can do.
Wiped system using TWRP 2.6.3.2 and cleared cache after install - did another wipe after reboot just to be sure. I have seen this on other roms that I try to flash?
am I doing something wrong during the flash process?
Wipe (default twrp)
install rom and gapps
clear cache/dalvik
reboot
Tried different gapps with no success..
I tried to flash the first OmniRom (build 1) with the same problems and I also got CM start tutorial when I had flashed OmniRom?? So it feels like the wipe is not working as it should?
TheErk said:
Just flashed OmniRom beta 2 build together with gapps linked in the OmniRom thread and I get fc on first boot on both NFC service and one more android service something something - can't get passed the pop ups and a reboot into recovery is all I can do.
Wiped system using TWRP 2.6.3.2 and cleared cache after install - did another wipe after reboot just to be sure. I have seen this on other roms that I try to flash?
am I doing something wrong during the flash process?
Wipe (default twrp)
install rom and gapps
clear cache/dalvik
reboot
Tried different gapps with no success..
I tried to flash the first OmniRom (build 1) with the same problems and I also got CM start tutorial when I had flashed OmniRom?? So it feels like the wipe is not working as it should?
Click to expand...
Click to collapse
Where did you get the build? If you got a CM start tutorial then you definitely didn't wipe, and i wonder what exactly you're flashing? This would be anything official Omni
jerdog said:
Where did you get the build? If you got a CM start tutorial then you definitely didn't wipe, and i wonder what exactly you're flashing? This would be anything official Omni
Click to expand...
Click to collapse
Got the Omni from
http://forum.xda-developers.com/showthread.php?t=2517309
and the twrp from
http://forum.xda-developers.com/showthread.php?t=2469995
Others have succeeded using this so no clue what I'm doing wrong? I have flashed other roms, recovery works. Sometimes it seems like it is not wiping it all?
TheErk said:
Got the Omni from
http://forum.xda-developers.com/showthread.php?t=2517309
and the twrp from
http://forum.xda-developers.com/showthread.php?t=2469995
Others have succeeded using this so no clue what I'm doing wrong? I have flashed other roms, recovery works. Sometimes it seems like it is not wiping it all?
Click to expand...
Click to collapse
As this is far from an official build, you will want to direct your issues to the porter/builder of the ROM in that thread you linked.
jerdog said:
As this is far from an official build, you will want to direct your issues to the porter/builder of the ROM in that thread you linked.
Click to expand...
Click to collapse
That would be awesome, thanks
jerdog said:
As this is far from an official build, you will want to direct your issues to the porter/builder of the ROM in that thread you linked.
Click to expand...
Click to collapse
Think I found the problem - a "default" wipe in twrp won't do it - I had to go in to advanced and choose "cache,dalvik,data and system" now it works like a charm! Good to know for the future..
Hi!
I use Google edition s4 ROM, and i really like it. But when it receives an update do i have to factory reset everytime? Im on 20150614, with CWM 6,0,4,7.
Id really really appreciate a fast answer
Also, if i wish to switch Kernel from Alucard to Googy-Max, is it ok to Wipe dalvik cache, and then flash kernel?
EDIT: the rom: http://forum.xda-developers.com/showthread.php?t=2557353
bump?
Dirty flashes should be OK, however the ROM thread you linked to should have provided the answer. Regardless, you really should change that recovery to TWRP. Clockworkmod is no longer being supported and people are having difficulty installing some custom ROMs with it.
Wiping cache is fine when changing kernels.
Thanks for the help
Btw. I dont know how to change recoveries? XD. Is it Just using Odin like with cwm? And do i have to remove cwm first / wipe device?
No, u can just flash ur new recovery through cwm
Okay. What is the preferred TWRP? Do you possibly have a link ?
Asking because i cannot find the S4 i9505 on their site?
EDIT: I managed to install it via the App they've made. It is much nicer than CWM. Thanks for the help both of you
Ok ive tried to flash 2 different kernels multiple times now.
Tried Googy-Max, and the phone wont boot android ?
Tried Hulk, and it took forever to boot, then rebooted immediately etc.
Am i flashing kernels wrong?, i did dalvik/cache wipe after the flash