I am running Gigglebread 7.0.2 on my T-Mobile N1. I am getting ready to go to Italy for a few weeks and wanted to see what would happen to my phone with another carrier's SIM. So, I inserted the AT&T SIM from my work blackberry and had some issues, but got it working after the APN was sorted out.
When I swapped the T-Mobile SIM back, all of my Google accounts had forgotten their credentials. I rebooted once just to see and no change. So, I thought, easy, restore nandroid from earlier in the day. The restore went fine, no errors, no wipe of cache or dalvik only now I appear to have no gapps (no market, unable to add google accounts, shortcuts on desktop don't work). Again, no problem. I've seen this before so I wiped cache and dalvik from CW 2.5.x recovery and installed dta2sd (sometimes it helps) and then 20110307 gapps. Reboot and still no gapps functionality.
So, I brought out the bigger hammer (after a couple of tries at gapps install) and wiped data/factory, dalvik, cache partition, restored nandroid, reboot. Still no gapps. Repeated the same wipe, restore nandroid, install dta2sd, install gapps, reboot. Still no gapps.
Now I'm getting desperate. Less than 72 hours till plane leaves! I next changed to AmonRA recovery and wiped, various nandroid/gapps/dta2sd combinations and still no gapps functionality.
Switched to CW 3, yeah, I know... And wiped cache, dalvik, factory/data, and even formatted system. Various installations and it still refused to install gapps.
I next tried the CW 2.x factory/data wipe, dalvik, cache, and then installed Gigglebread 7.0.2, dta2sd beta4(like always), and gapps 20110307 and rebooted. As expected, sterile phone, touch android, and then I'm prompted for google account. I skip that and sure enough, market is back and I can add google accounts.
AUGH. Unless someone has a suggestion, I'm probably going to have to do a full reinstall tomorrow. I've been wanting to do it, but not this close to a trip.
On a side note, is it normal for a swap of the SIM card to wipe out my account settings? I will make sure from now on that my TI b/u is up to date.
Rick
Infuriating as it is, especially as you must have so much to do already, a re-install might be best at this point. Trying to troubleshoot and avoid doing this could just mean more wasted time in the long run.
DirkGently1 said:
Infuriating as it is, especially as you must have so much to do already, a re-install might be best at this point. Trying to troubleshoot and avoid doing this could just mean more wasted time in the long run.
Click to expand...
Click to collapse
Yup, already on that path. I fell asleep last night or I would have finished. I did manage to get a TI backup of many of my apps (gmail especially) so hopefully I won't have to set those back up again since I'm using two-factor auth on all of them (10 accounts) and don't want to go through the process of invalidating and recreating the app specific passwords again.
Rick
I am also facing the same problem now.
I was on Cyanogen Mod 7.0.3 when some application weirdly started building up data on system storage. There was only 16 KB of space left and it became un-responsive. So I restarted it, only to find the looping Cyan logo.
Fortunately I had a backup from 15 days back, which was CM 7.0.2. So, I flashed that and I thought I am back. But, I found Market was not working, in fact it was not even showing up in the app list. Also, Contacts data was wiped out and when I tried to check out the account and settings, google account option itself was not showing up.
I tried flashing 7.0.3 + latest gapps package using Rom manager, that did not work. I tried a clean wipe and flashed 7.0.2 from my backup, no effect. Then flashed latest gapps again, no change.
It is frustrating now. It looks as if google is not supporting my device anymore.
Any suggestion is welcome.
Did you check md5 from your gapps package?
You said you were using ROM manager so I suppose you are on cwm but are you on cwm 3.x or are you on cwm 2.5.1.4? If your on 3.x then downgrade if not then maybe try Amon-RA with temasek system wipe maybe just making a clean install of your recovery might fix it.
Also you might want to try flashing from recovery instead of ROM manager. Just for the fun of it.
Might also need to partition sd card again as CWM 3.0 probably fubar it.
Related
I rooted my Sprint Hero and have been able to successfully flash and operate Fresh 2.3.3 but CANNOT figure out how to get CM6 to boot. I wiped prior to attempting the flash but all that happens is a lockup on the HTC boot screen. I have attempted to flash it twice, and waited about 20 minutes the first time and 45 the second time with no progress, eventually having to pull the battery and reboot in recovery mode. I was only able to wipe the data but when I tried to wipe the delvik cache, it told me I needed to do it via ADB. I tried to partition my SD card but it ended up cutting the available memory in half, and erasing my backup, and I had to use an external card reader to reload Fresh so that I could actually use my phone (which IS fully functional now). Should I be wiping EVERYTHING on the phone (including the battery and rotate info)? What am I missing?
I have heard nothing but great things about CM6 and am very disappointed that I cannot get it to work. Can anyone help?
Sprint HTC Hero
Firmware version: 2.1-update 1
Software version: 2.27.651.6
try wiping your ext partition
I wiped everything that the recovery menu would allow me to prior to the first attempt at flashing and it wouldn't load. I pulled the battery and rebooted to the recovery menu then partitioned the SD card, wiped just prior to the second attempt at re-flashing, re-flashed and it still locked up at the HTC screen.
I like to think I'm pretty computer savvy but I just can't figure this out. Why would Fresh 2.3.3 load without a hitch, but CM6 not?
make sure you recovery is 1.6 or 1.7 to be able to wipe dalvik i had same prob
My recommendation would be flashing the recovery in this thread here.
This the recovery I used while I was using Fresh 2.3.3, and when I upgraded to the CM6 Nigtlies.
I say Flash The Custon Amon_RA 1.7 in Darchdroid thread->NANDROID!!!!->Wipe Data->Dalvik->sd-ext(if using apps2sd)->Flash RC1 or Latest Nightly (your choice)->Flash Optionally Google Apps->Optionally Flash Uncapped Kernel and/or Battery Tweak(I use the uncapped Kernel, and not the battery tweak, and I get 24 hours+ with average use)
Try that out.
Funny, im running into the same problem after flashing the wrong blackmod... wiped, reflashed cm and now it wont go past the htc white boot screen
It did boot before though which is odd
Edit: Wiped, wiped dalvik and ext part, flashed rom and gapps, working just fine now... will flash batt tweak, bm and round clock in a min, hopefully it doesn't break it
jUgGsY,
Thank you for being so thorough in your response, it all makes sense! My only issue now is trying to re-flash the recovery image. I downloaded the RA-Darchstar image but I'm not sure if it's correctly being pushed to the SD card (all I get is a long list of ADB commands, no particular confirmation) and when I try to flash the image, I get a message telling me that it can't find the partition. What does this mean? Is the recovery image really that important to the updated ROM? How come there is no specific recovery image recommended on the CM forum?
EDIT: I found directions from the Unlockr on the youtubes. Gonna give it a try and see how it goes after that...
So it was decadence#7 kernel that was screwing up my boot... removed it and using stock darchstar
Ok... this is getting ridiculous.
*I flashed the RA-Darchstar (1.7) recovery image
*NANDROIDed
*Wiped data, cache, Dalvik and sd-ext
*Flashed RC1
*Flashed the google addon
*Rebooted
Been waiting for the damn thing to boot for almost 30 minutes now, still stuck on the HTC screen. Can anyone tell me what is going on?
jordanjackthomas said:
Ok... this is getting ridiculous.
*I flashed the RA-Darchstar (1.7) recovery image
*NANDROIDed
*Wiped data, cache, Dalvik and sd-ext
*Flashed RC1
*Flashed the google addon
*Rebooted
Been waiting for the damn thing to boot for almost 30 minutes now, still stuck on the HTC screen. Can anyone tell me what is going on?
Click to expand...
Click to collapse
Are you flashing RC1 or one of the nightly ones? I had the same issue with RC1. I could not get it to boot past the HTC screen. However, the nightly ones flash just fine. I would suggest flashing a nightly. I now see you said RC1, lol. Try the latest nightly.
It looks like I will have to go with a nightly. Are there any that you recommend? The most recent or one from a few nights back?
jordanjackthomas said:
It looks like I will have to go with a nightly. Are there any that you recommend? The most recent or one from a few nights back?
Click to expand...
Click to collapse
The latest one seem to be very good. 8/22 but make sure you download the latest google apps for it also.
For some reason, I couldn't get any variation of CM to load on my phone (CM6 or the Vanilla variant). I went with Darch's LegendROM and it is excellent - much better than stock 2.1 for the Hero! Really fast and has some neat extra features. I noticed, though, that my reception is kind of bad now and I usually have excellent coverage at my house. I already downloaded the most up-to-date Sprint radio (2.42.01.04.27) but was just curious: do I need to wipe and re-flash the image FIRST or can I just flash the radio image over the already installed ROM?
AND: Please excuse my inexperience with all of this, but I'm about to ask two already answered questions: I'm not looking for long-winded answers but if someone could point me to a relevant thread, it would be GREATLY appreciated.
1) I keep getting a "process com.google.android.googleapps has stopped working" error when I try to sync with my gmail account. How do get this to work?
2) I remember reading that there was a known MMS issue with Darch's DroidROM, not any issue with the LegendRom, but I just received a "generic network failure" message when my wife tried to send me picturemail. Is there a workaround for this?
Thank you all for your patience!
My phone will currently not boot bast the CyanogenMod boot screen.
I flashed my phone several months ago to CM10.1 It was the update that patched the "masterkey" bug. I have been using it daily since then with no problems.
Today, I turn my phone on, and it just hangs at the boot animation.
There were no significant changes since the last time it was powered on. I think I installed McPixel from the humblebundle, and uninstalled a game from the playstore called Krog. No setting changes of any significance.
I've tried booting into safestrape and deleting both the cache and the dalvik cache, neither has helped. My stock rom still loads just fine, but i had factory reset it quite a while ago. I do have a backup of the rom from about 40 days ago i can try restoring, but i would love a more nondestructive way to fix this.
Try booting into safestrap, wiping system, cache, and dalvik, then reinstall the ROM and gapps.
Droid 4 - Avatar
kwyrt said:
Try booting into safestrap, wiping system, cache, and dalvik, then reinstall the ROM and gapps.
Droid 4 - Avatar
Click to expand...
Click to collapse
0.o wouldn't that be a LOT more destructive than just restoring the old backup?
pyro42 said:
0.o wouldn't that be a LOT more destructive than just restoring the old backup?
Click to expand...
Click to collapse
Nope. You are not wiping data so all your apps, setting, etc will still be there.
the data itself will remain if you just wipe the system, cache and dalvik cache but be sure to reinstall the latest stable build of CM and gapps for it
Sent from my XT894 using xda premium
kwyrt said:
Nope. You are not wiping data so all your apps, setting, etc will still be there.
Click to expand...
Click to collapse
ah gotcha gotcha...
unfortunately it didn't work.
for troubleshooting's sake, i went ahead and made a backup of the rom in it's non-working state.
i restored my old backup, it boots just fine.
restored borked backup (tested it, still won't boot), wiped cache/dcache, wiped system, installed cm-10.2-20130821-NIGHTLY-maserati.zip and gapps 20130812, wiped cache/dcache again for good measure, then reboot and waited 10 minutes, still won't pass boot logo.
so i figure someting's wrong with Data right? so i rebooted to safestrap and did a factory restore, then wiped cache/dcache, and still won't boot.
so now i'm going at it the opposite direction. restoring the working backup, restoring just the data from the nonworking backup, then upgrading CM/Gapps
rebooting.. and....
blank screen with full backlight. not so much as a CM logo.
i guess for now i am going to restore back to the old backup, update the rom, and go about reconfiguring, unless anyone has any more suggestions?
pyro42 said:
ah gotcha gotcha...
unfortunately it didn't work.
for troubleshooting's sake, i went ahead and made a backup of the rom in it's non-working state.
i restored my old backup, it boots just fine.
restored borked backup (tested it, still won't boot), wiped cache/dcache, wiped system, installed cm-10.2-20130821-NIGHTLY-maserati.zip and gapps 20130812, wiped cache/dcache again for good measure, then reboot and waited 10 minutes, still won't pass boot logo.
so i figure someting's wrong with Data right? so i rebooted to safestrap and did a factory restore, then wiped cache/dcache, and still won't boot.
so now i'm going at it the opposite direction. restoring the working backup, restoring just the data from the nonworking backup, then upgrading CM/Gapps
rebooting.. and....
blank screen with full backlight. not so much as a CM logo.
i guess for now i am going to restore back to the old backup, update the rom, and go about reconfiguring, unless anyone has any more suggestions?
Click to expand...
Click to collapse
Yeah, definitely sounds like something in /Data. Only other possible option I can think of would be to use Titanium Backup. It has an option to "Extract from Nandroid backup". It's under the "SPECIAL BACKUP/RESTORE" options. I've never used that option before so I have no idea how or if it would work but might be worth a shot.
kwyrt said:
Yeah, definitely sounds like something in /Data. Only other possible option I can think of would be to use Titanium Backup. It has an option to "Extract from Nandroid backup". It's under the "SPECIAL BACKUP/RESTORE" options. I've never used that option before so I have no idea how or if it would work but might be worth a shot.
Click to expand...
Click to collapse
wonderful idea, unfortunately TB crashes when i point it at either backup.
buuut i did find Nandroid Manager * ROOT which looks like it might be working.
if you really wanna see if it is the data or not have you tried to
flash 10.2 or whatever you started out with... then restore -just-
the data to the freshly flash system and then do a wipe of all
said caches... I do that sometimes to get a fresh start on my
os itself.. works pretty well. Just do not restore the cache just
the data part. Or restore with MD5 checking... if it doesn't check
out then you know for a fact that the data partition in that specific
nandroid isn't any good :/
Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?
isketch93 said:
Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?
Click to expand...
Click to collapse
I had 70% similar scenario ,but different error. i could boot into mokkee rom but crashed during initial setup ,below were the steps i used to fix it
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
got perfectly working Mokee ROM in MI3
bluethilak said:
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
Click to expand...
Click to collapse
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?
A nandroid backup is to be used in case of failure (and as a backup... but you should have backups anyway so data loss isn't the end of the world) - an app backup is so you can reinstall the apps with settings in Mokee.
isketch93 said:
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?
Click to expand...
Click to collapse
Nandroid backup is nothing but a complete backup of both Rom and Data.It will in a zip format ad gets saved in your internal memory
[Clockworkmod for CWM/TWRP for TWRP recovery]
http://www.makeuseof.com/tag/what-is-a-nandroid-backup-and-how-exactly-does-it-work/
Let me tell you How I handle my backup plans for my device because at least per week i will be changing the ROM.
1) I always save my contacts in Google contacts(So a normal sync will do)
2)I backup all app data and Message data using EasyBackup
:good::good:
I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?
bluethilak said:
...got perfectly working Mokee ROM in MI3
Click to expand...
Click to collapse
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps
isketch93 said:
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps
Click to expand...
Click to collapse
Dude banks gapps latest is for 5.1.0 lolipop ,mokkee is still in 5.0.x try other gapps ,PA or MInimal or get old Bank Gapps of correct lolipop version.:good:
---------- Post added at 10:06 AM ---------- Previous post was at 09:59 AM ----------
isketch93 said:
I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?
Click to expand...
Click to collapse
Clear some space at least 2gb temporarily in you Internal Memory ,Since you will be backing up your App Data,it definitely requires a lot of space .
I have a HTC ONE m7, rooted, I have been running CM11, flashing the nightlies with great success. When CM12 came out, it 'soft bricked' my phone, continuous reboots, failing android functions. was able to reinstall Titanium backup, then restore the phone to a previous point. back running, but not without bugs. after trying this 3 times, I have given up. but I read where people say, "do a wipe" then flash the ROM....... What, specifically does this mean?
yes I have rooted my phone, but I am just knowledgable to be dangerous. if It means back to factory specs, then how do I flash the rom? I think that my phone should run CM12, and maybe I need to wipe? wipe what? dalvic cache? is that a wipe?
Anybody have some ideas or can point me to some postings that may help me. Many Thanks, very tired of operating on the last build of CM11
blairan
Do a wipe typically means wipe the data, system, cache, and dalvik cache partitions. If you are using TWRP as your recovery (I do for this phone), boot into it and then press Wipe, then Advanced Wipe. Select those four (not internal storage or USB OTG) and then Swipe to Wipe. Of course, your phone won't boot at this point, so you'll need a new ROM waiting on internal storage to be flashed.
thankyou Coal, I have been trying to install a CM12 and/or a CM12.1 ROM I can get them to boot up, but play store is not present. I can access play store via themes, and it comes up as a web page rather than an app. (is this norm for CM12?)
once I sign in to play store, I try to install titanium backup to restore all my apps. it says it is installed, I press it anyway, and it says it will be installed soon, which never happens. CM12 and CM12.1 seem to be running fine, but I can't restore any of my old phone. I can recover to a CM11, but it is a little unstable, so I would like to upgrade the system and be flashing nightlies again. what do you think?
and after watching a few videos on you tube, I figured out that I was missing the Gapps file, and the supers file. enjoying lollipop success.
thanks coal!
blairan said:
and after watching a few videos on you tube, I figured out that I was missing the Gapps file, and the supers file. enjoying lollipop success.
thanks coal!
Click to expand...
Click to collapse
I was going to suggest GAPPS, but I wasn't sure if you needed it for CM. Glad you figured it out!
Apologies for duplicating this post but the original forum was apparently the wrong spot for this.
I need either some pointers or a reference to a how-to, if you please.
My Nexus 6 is currently running Pure Nexus 6.0.1-2060821-official, security patch 8/5/2016 with ElementalX kernel 3.10.40-ElementalX-N6-3-20.
I've updated Pure Nexus before through TWRP and all went well, but those efforts never involved updating the kernel too. I've attempted to flash the new kernel, the rom and the google apps, but the phone goes into a never ending boot effort and it's a tussle getting back to recovery mode as it tends to boot loop. The flashes are preceded by clearing Delvik and cache and cleared again after the flash.
Is the order of flashing off or perhaps not enough clearing of other items such as system? Or is a factory reset needed?
Kind of lost on this one and can't seem to string together enough search terms to find help specific to the problem.
Any help would be appreciated.
The kernel is most likely not updated to work with the rom. Each rom comes with its own kernel so you really don't have to flash a new one. I would flash the rom and gaps and see what happens. Leave the kernel out of it for now. You have to remember that not all kernels work on all roms. Many roms are making it so only their kernel works properly.
zelendel said:
The kernel is most likely not updated to work with the rom. Each rom comes with its own kernel so you really don't have to flash a new one. I would flash the rom and gaps and see what happens. Leave the kernel out of it for now. You have to remember that not all kernels work on all roms. Many roms are making it so only their kernel works properly.
Click to expand...
Click to collapse
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215, checked the MD5s, and flashed both after cache/Dalvik. Still got the same 4-color bouncing dots. Let it run like that for about 40 minutes before getting back into recovery.
Ran the same flash but this time also wiped system. Same result.
Is 40 minutes enough time? Impatience maybe?
Now back to original 6.0.1, PureNexus 6.0.1-20160821 and 3.10.40-ElementalX-N6-3.20 kernel.
Any ideas?
jlfesslerkc said:
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215, checked the MD5s, and flashed both after cache/Dalvik. Still got the same 4-color bouncing dots. Let it run like that for about 40 minutes before getting back into recovery.
Ran the same flash but this time also wiped system. Same result.
Is 40 minutes enough time? Impatience maybe?
Now back to original 6.0.1, PureNexus 6.0.1-20160821 and 3.10.40-ElementalX-N6-3.20 kernel.
Any ideas?
Click to expand...
Click to collapse
You are doing a full wipe right? Wiping system and data before flashing?
Also encryption could be an issue. If your device in encrypted or the kernel did not remove the force encryption flag. That could take awhile as well.
jlfesslerkc said:
Still no-go. Freshly downloaded purenexus_shamu-7.1.1-20170215-OFFICIAL and Full_Dynamic_GApps-7.1.x-20161215
Click to expand...
Click to collapse
Get the Feb 15 GApps too instead of the Dec 15 GApps. Don't use old GApps.
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Also make sure that the GApps are 7.1.x and not 7.x.x or you get a SDK mismatch. What does the recovery log show?
Pkt_Lnt said:
Get the Feb 15 GApps too instead of the Dec 15 GApps. Don't use old GApps.
https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Also make sure that the GApps are 7.1.x and not 7.x.x or you get a SDK mismatch. What does the recovery log show?
Click to expand...
Click to collapse
Got the Feb GApps, wiped Dalvik and cache... this time I let it run for a bit over an hour in case the encryption was an issue. There's a little over 19 GB in files. I figured an hour would be enough but no luck. Had to recover again from backup.
TWRP gives 5 items that can be wiped, Dalvik, System, data, Internal Storage and Cache. I was of the understanding that data pertained to user data (photos, notes, etc). Most all of that is backed up but I'm unclear on what needs wiping for this Nougat upgrade. When I wiped system, it didn't seem to help - although I was using the older GApps at that point. I've seen documentation that says to wipe these items at the outset and others that suggest after the flash is complete. Both? Which ones?
I don't want to resort to drastic measures if it's something simple that I've missed.
Needs Nougat bootloader and latest radio--flash in TWRP. This allows flashing N ROMs while will still work with all MM or even 5.1 ROMs
http://batakang.com/ftp/devs/mhous33/shamu/bootloaders/shamu_bootloader_moto-apq8084-72.01.zip
http://batakang.com/ftp/devs/mhous33/shamu/7.1.1/shamu_baseband_D4.01-9625-05.44+FSG-9625-02.115.zip
jlfesslerkc said:
Got the Feb GApps, wiped Dalvik and cache... this time I let it run for a bit over an hour in case the encryption was an issue. There's a little over 19 GB in files. I figured an hour would be enough but no luck. Had to recover again from backup.
TWRP gives 5 items that can be wiped, Dalvik, System, data, Internal Storage and Cache. I was of the understanding that data pertained to user data (photos, notes, etc). Most all of that is backed up but I'm unclear on what needs wiping for this Nougat upgrade. When I wiped system, it didn't seem to help - although I was using the older GApps at that point. I've seen documentation that says to wipe these items at the outset and others that suggest after the flash is complete. Both? Which ones?
I don't want to resort to drastic measures if it's something simple that I've missed.
Click to expand...
Click to collapse
What TWRP version? Old one cause problems on newer ROMS. Newest is 3.1.0, but 3.0.3 or 3.0.2 should be ok.
Wipe everything - /system, /data, /cache. /dalvik. Do NOT wipe Internal Storage (camera photos, downloads, etc.) before flashing. Data is usually app data, so make a nandroid first to save it, but app data can usually be restored with Titanium Backup or Google will restore it on setup. Just do not restore any system data.
Bootup on clean flash does take time, but normally no more than 20-25 minutes.
Try reverting to stock
Install stock firmware using adb
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
jlfessler said:
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
Click to expand...
Click to collapse
Hi... Save your internal storage before processing. Just in case... TWRP 2.8.5.0 is pre nougat and incompatible.
jlfessler said:
TWRP version might be the glitch.... Mine reports 2.8.5.0 in recovery mode. I'll update to the latest and retry after wiping all but internal storage. If that fails, I'll flash the boatloader and radio.
Once more into the breach.
Click to expand...
Click to collapse
You should really update the bootloader/radio to the latest once you update the TWRP. Updating the bootloader/radio will not affect your internal storage.
Pkt_Lnt said:
What TWRP version? Old one cause problems on newer ROMS. Newest is 3.1.0, but 3.0.3 or 3.0.2 should be ok.
Wipe everything - /system, /data, /cache. /dalvik. Do NOT wipe Internal Storage (camera photos, downloads, etc.) before flashing. Data is usually app data, so make a nandroid first to save it, but app data can usually be restored with Titanium Backup or Google will restore it on setup. Just do not restore any system data.
Bootup on clean flash does take time, but normally no more than 20-25 minutes.
Click to expand...
Click to collapse
Wiping system, data, cache and Dalvik seems to have gotten me to Nougat but apparently root did not come along for the ride. Wasn't expecting that. Is that par for the course?
jlfesslerkc said:
Wiping system, data, cache and Dalvik seems to have gotten me to Nougat but apparently root did not come along for the ride. Wasn't expecting that. Is that par for the course?
Click to expand...
Click to collapse
yup
Item 1.8 and 1.9 here
Pkt_Lnt said:
yup
Item 1.8 and 1.9 here
Click to expand...
Click to collapse
Thanks. 1.9 refers to SuperSU which is what I used earlier.
Also I take it reinstalling TitaniumBackup will then let me restore the apps. Still on track?
jlfesslerkc said:
Thanks. 1.9 refers to SuperSU which is what I used earlier.
Also I take it reinstalling TitaniumBackup will then let me restore the apps. Still on track?
Click to expand...
Click to collapse
That is what Titanium Backup (and Restore) does, yes.