I was running the HD rom, but got tired of the old battery life, so I used Rom Manager to flash CWM recovery 3.0.0.5, then flashed my old backup of build from 2/5/11.
Whenever I try to install a newer build, my Gmail won't install, Google Voice won't install, etc. I've tried using Titanium backup to restore, I've tried downloading from the market...nothing seems to work.
Could this be related to using the new recovery ? I've tried different builds and cleared the downloads to let it download fresh again, but nothing works
You're referring to cm7 correct?
You can update to the newest build through rom manager, and select the gapps option. No need to wipe, just install latest and you should be fine.
option94 said:
You're referring to cm7 correct?
You can update to the newest build through rom manager, and select the gapps option. No need to wipe, just install latest and you should be fine.
Click to expand...
Click to collapse
that's what I'm doing (and yeah, CM7, sorry)
but every time it finishes downloading and installing (and I do check the GAPPS option) Market's there, but everything else seems borked with no ability to install the GAPPS
just tried it manually by flashing everything, going to try going back to the experimental recoveries
EDIT: after going back, wiping everything, then installing over, I was able to install the Gapps, fix permissions, reboot, and they finally worked
thanks
Related
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
So I have the Razr M Retail, and I was rooted with Safestrap and running Hashcode0f's CM10, completely stable. Yesterday I decided to move to TWRP with the bootloader unlock, so I backed up my ROM to an external SD, and also separately used TiBu to backup my apps, and then used mattlgroff's Razr M Utility to unlock the BL and flash TWRP, which all went fine. Then I wiped internal storage and restored my backup from TWRP. It restored and booted fine, but the Wi-Fi and camera didn't work. The Wi-Fi is stuck to a toggled off position in the settings, and it's greyed out so I can't change it. If I click to see networks, it gets stuck in "Turning Wi-Fi on..." and I never see anything. The camera force closes with "Can't connect to camera." Since I hadn't been sure from the start that a restore would work, I was expecting trouble at this point, so I flashed a fresh version of CM10 from Hashcode's goo.im with the intention of restoring my apps with TiBu. It booted, but it seemed like it was running slow and the Wi-Fi didn't work, with the same issue as before. I didn't try the camera. I messed around with a few things trying to get it to work, and although nothing worked, I tried doing all of these separately and then reflashing:
a) Flash stock Moto 4.1.2 with the utility
b) Restore my stock rooted Moto 4.1.1 with safestrap (Just sayin, this gets weird, I end up with both TWRP and Safestrap)
c) Restore to b) and then restore my CM10 backup as a Safestrap ROM-slot 1
d) Dial *#*#526#*#* to reset Wi-Fi driver (did nothing afaik)
ALSO, I charged the phone last night and this morning at 8:30 it was at 100% battery. 3 hours later, with wi-fi, data, and GPS all off, and using the phone very very lightly, it was at 46%, so there is significant battery drain coming from somewhere.
Any help or suggestions would be greatly appreciated.
First off, you need to fastboot back to stock and start over. TWRP didn't break your phone, restoring a backup from SS did. If you flash a fresh CM10 build, not a backup, you should be okay and you should only get the bugs that are associated with CM10.
Ok, now you're going to ask why the backup didn't work. SS is designed to work on top of the stock boot.img, but CM10 has its own boot.img and that's the reason that CM10 builds were so buggy when used with SS. When you saved CM10 with SS, it probably saved the stock boot.img with it and the stock boot.img is not going to make CM10 happy. If you had saved a stock based ROM and tried to restore it, you probably would have been okay.
Now, with all that being said, if you fastboot back to 4.1.2, then you'll need to use a 4.1.2 based ROM or a CM build. If you want to use a 4.1.1 based ROM, you'll need to flash the 4.1.1 boot.img, prior to flashing the ROM. You battery is probably dying so quickly because CM10 is trying to fight with the stock kernel. You need to fastboot and flash clean.
Tmfle from
Thanks for the info, but it didn't work
I used the utility to fastboot flash stock Recovery and System, then root with Motochopper, and flash TWRP. I then used TWRP to wipe system and flash a fresh version of CM10, and when it booted there was noticeable graphics lag, and Wi-Fi and Camera didn't work.
I'll flash back to stock for tonight, hope you have another idea =\
VoraciousGhost said:
Thanks for the info, but it didn't work
I used the utility to fastboot flash stock Recovery and System, then root with Motochopper, and flash TWRP. I then used TWRP to wipe system and flash a fresh version of CM10, and when it booted there was noticeable graphics lag, and Wi-Fi and Camera didn't work.
I'll flash back to stock for tonight, hope you have another idea =\
Click to expand...
Click to collapse
Yeah, stop using CM builds. The camera and WiFi are known issues on those builds. What I told you solved the issue with your backed up CM build. This is the reason I don't use CM, they are all buggy right now. There was new one released with a different camera. See how that works for you.
What were your steps for install?
-Boot into recovery
-Wipe cache/dalvik, FDR
-Reboot recovery
-Mount system
-Flash ROM
-Wipe cache/dalvik
-Reboot system
FYI, I never wipe system, only cache/dalvik and FDR. Some people swear by wiping system, I don't do it.
RikRong said:
Yeah, stop using CM builds. The camera and WiFi are known issues on those builds. What I told you solved the issue with your backed up CM build. This is the reason I don't use CM, they are all buggy right now. There was new one released with a different camera. See how that works for you.
What were your steps for install?
-Boot into recovery
-Wipe cache/dalvik, FDR
-Reboot recovery
-Mount system
-Flash ROM
-Wipe cache/dalvik
-Reboot system
FYI, I never wipe system, only cache/dalvik and FDR. Some people swear by wiping system, I don't do it.
Click to expand...
Click to collapse
Hmm, I think I figured it out, or at least part of it, I'll make sure in the morning. Back in December-ish, before the bootloader unlock, Hashcode was releasing new CM10 builds every few days. Only the latest, dated 12/05, had working Wi-Fi, and that's what my backup should be. Now that I look at goo.im again, the only build on there is dated 11/14, and that's the one that I thought was 'fresh' but it never had working Wi-Fi or camera to begin with. Now I read through the CM10 thread here on XDA and I see that mic213 is building more current CM10 releases with more features working, and Hashcode has removed all of his builds except one (no idea why it's this particular one instead of the latest).
As for my install steps, they were actually:
-Boot into recovery
-Format Data (I said wipe system earlier, but I meant format data, as system gets wiped as part of it)
-I didn't reboot recovery, usually do but I got lazy
-Flash ROM (system was already mounted for me? )
-Wipe caches
-Reboot
So yeah, in the morning I'll download and flash mic213's build from here and I'm pretty sure that should work.
VoraciousGhost said:
Hmm, I think I figured it out, or at least part of it, I'll make sure in the morning. Back in December-ish, before the bootloader unlock, Hashcode was releasing new CM10 builds every few days. Only the latest, dated 12/05, had working Wi-Fi, and that's what my backup should be. Now that I look at goo.im again, the only build on there is dated 11/14, and that's the one that I thought was 'fresh' but it never had working Wi-Fi or camera to begin with. Now I read through the CM10 thread here on XDA and I see that mic213 is building more current CM10 releases with more features working, and Hashcode has removed all of his builds except one (no idea why it's this particular one instead of the latest).
As for my install steps, they were actually:
-Boot into recovery
-Format Data (I said wipe system earlier, but I meant format data, as system gets wiped as part of it)
-I didn't reboot recovery, usually do but I got lazy
-Flash ROM (system was already mounted for me? )
-Wipe caches
-Reboot
So yeah, in the morning I'll download and flash mic213's build from here and I'm pretty sure that should work.
Click to expand...
Click to collapse
Yeah, definitely use Mic's builds, they are more current. TWRP shows that the sytem is mounted, but it is fact not. That's why you need to reboot recovery. When you reboot, you'll see that it's not mounted.
Mic's CM10 is very, very stable. Very good build.
10.1 is a little more buggy but still a good build.
Sounds like you're either using one of Hash's old builds or new, buggy ones. Mic is the way to go for now
Sent from my Nexus 7 using Tapatalk HD
Hello, I've recently installed Temasek's CM 13 nightly marshmallow build to my bootloader unlock note 3. I'm having a difficult time acquiring root after the install. I've flashed SuperSu to no avail. I've even tried the Aramaic tool method with no luck. Is there anything I can do to get root back on this phone or am I screwed?
Look for SuperSU in the settings menu.
Not sure if you need to turn on developer options for it to appear there or not.
[Edit]Did you install CM with a custom recovery, or with flashfire?
Your post doesn't say one way or another, but if you have an unlocked bootloader you can flash a custom recovery using Odin... meaning that you always have root, so long as you preserve the unlocked bootloader.
Having only a single root (locked bootloader and no custom recovery) and using FlashFire to install a ROM puts you at constant risk of root loss.
.
Thanks for your reply. I have TWRP 3.0.2 installed. I didn't check to see if it was installed under settings but I have since restored back to my stock rooted ROM. I will reinstall CM again and let you know if SuperSu shows up in settings.
cblendz said:
Thanks for your reply. I have TWRP 3.0.2 installed. I didn't check to see if it was installed under settings but I have since restored back to my stock rooted ROM. I will reinstall CM again and let you know if SuperSu shows up in settings.
Click to expand...
Click to collapse
Hey.
Just to make sure I'm being clear - you do have to flash SuperSU along with the ROM flash - root is not "baked in" to CM.
For some reason CM "hides" the SuperSU app so that it only shows up in the Settings menu and not in the app drawer.
It wasn't clear from the way you described things if that's what was going on, but I remember having the same (?) experience ... I thought the install of SuperSU was somehow missing due to the fact it didn't show up in the app drawer.
.
bftb0 said:
Hey.
Just to make sure I'm being clear - you do have to flash SuperSU along with the ROM flash - root is not "baked in" to CM.
For some reason CM "hides" the SuperSU app so that it only shows up in the Settings menu and not in the app drawer.
It wasn't clear from the way you described things if that's what was going on, but I remember having the same (?) experience ... I thought the install of SuperSU was somehow missing due to the fact it didn't show up in the app drawer.
.
Click to expand...
Click to collapse
I've just tried reinstalling the cm13 ROM again and this time I checked to see if SuperSu was installed in settings. It didn't show up there either. I don't know what's going on with it. I wipe everything then flashed the ROM then wiped dalvik and cache. Then flashed open Gapps. Wiped dalvik and cache and flashed 2.78 SuperSu and reboot to system.
cblendz said:
I've just tried reinstalling the cm13 ROM again and this time I checked to see if SuperSu was installed in settings. It didn't show up there either. I don't know what's going on with it. I wipe everything then flashed the ROM then wiped dalvik and cache. Then flashed open Gapps. Wiped dalvik and cache and flashed 2.78 SuperSu and reboot to system.
Click to expand...
Click to collapse
I don't know if this would make a difference, but somewhere in that thread trader418 mentioned that you had to flash the ROM after the Gapps to take care of an issue with some init.d scripts. As in the sequence: wipe - ROM - gapps - ROM - supersu - first_boot.
I'm not sure if that's related or not. It's been long enough ago that I can't remember the exact details, but I remember thinking "hey, where did it go, I know I flashed it!".
Maybe it would be best to ask this question in that thread.
.
bftb0 said:
I don't know if this would make a difference, but somewhere in that thread trader418 mentioned that you had to flash the ROM after the Gapps to take care of an issue with some init.d scripts. As in the sequence: wipe - ROM - gapps - ROM - supersu - first_boot.
I'm not sure if that's related or not. It's been long enough ago that I can't remember the exact details, but I remember thinking "hey, where did it go, I know I flashed it!".
Maybe it would be best to ask this question in that thread.
.
Click to expand...
Click to collapse
Thanks a lot that was it. Finally got root. I wish CM would bake root in their Roms but all is good now. Thanks.
Hello and thanks for reading.
Well, I installed the TWRP on my Letv 1S X500 to flash the gapps and can use play services but as I had the recovery installed I wanted to test some customs rom. The problem is that I can go back to my stock rom or even other rom. Actually I could installed other rom but I can not do it more. (First I installed RR, after some hours many apps stop so I have to make wipes (Cache, dalvik, System and data) three times and I could installed lineage OS, but I can not use Snapchat so I wanted to install the S26 again so I tried to use the backup but the TWRP does not find it, it just does not appear. I did two backups, one when I had the S26 and other when I had RR and any of both appear when I press restore. I also tried to install the rom, not make a restore but, it says This package is for "X3" devices; this is a "x3". error 7. I already did the trick of deleting the semicolon or all the lines with the "assert" word but it is the same.
I have thought on installing the stock recovery and rename the s26 to "update.zip" but I do not know if it is just like that.
What could I do to fix this problem?
I want to have the stock rom, but if the problem with snapchat has a solution I could keep using LineageOS.
I have this recovery 3.1.0-0
The first backup was with TWRP 3.0.1 and the second one with my current TWRP 3.1.0-0
I am downloading other stock rom to prove, the 17S. I hope this work.
I just know, I am not a root user, I have not installed superSU. Is it important?
diosshu said:
I just know, I am not a root user, I have not installed superSU. Is it important?
Click to expand...
Click to collapse
No, it is not important.
Seems like you changed twrp, to restore the backup created by one version of twrp you need the same twrp to restore.
Hello,
Did you solve a problem?
I have same problem.
Hi,I've just installed:
lineage-14.1-20190713-UNOFFICIAL-clark
from androidfilehost. I am stuck In a bootloop but have been able to restore a backup. I'm using hashbang's moddedrecovery TWRP which is the only one I've ever had any luck booting a ROM with.
I've wiped data/system and tried installing it with and without gapps but still only get bootloop.
I notice this latest nightly has magisk 19.3 built-in and wonder if this may be the culprit? I'd really like to update for security updates as my stable build is quite outdated now.
Many thanks if anyone can help
captain sideways said:
Hi,I've just installed:
lineage-14.1-20190713-UNOFFICIAL-clark
from androidfilehost. I am stuck In a bootloop but have been able to restore a backup. I'm using hashbang's moddedrecovery TWRP which is the only one I've ever had any luck booting a ROM with.
I've wiped data/system and tried installing it with and without gapps but still only get bootloop.
I notice this latest nightly has magisk 19.3 built-in and wonder if this may be the culprit? I'd really like to update for security updates as my stable build is quite outdated now.
Many thanks if anyone can help
Click to expand...
Click to collapse
Did you check the md5 checksum?
Sent from my perry_f using XDA Labs
hello, thanks for replying.
checked original and matched. re-downloaded and checked that one as well just in case, also matched. same result
** Edit - Problem Solved - My Fault/Strange Glitch
Soooo, I tried a few more times to install the latest nightly and whenever the rom was finished installing, Magisk 19.3 was also attempting to install. this is not because magisk is included in the rom, because it's not. even after advanced wipe > everything apart from microSD card and clearing my zip queue several times, magisk was still trying to install after the rom.
I went back to stock 7 install using fastboot and the necessary files then reflashed modded TWRP via fastboot, rebooted, and installed the latest nightly and gapps together and rebooted. so far so good thanks again for replying.