I've been rummaging through all of XDA, YouTube and other independent sites to find a simple and comprehensive method to flash Cyanogenmod 10 and CWM Recovery 6.xx.xx on my old Nexus S I9023 but none of the walk-throughs are comprehensive enough. I'm pretty new when it comes to the flashing bit and the horror stories out there about people bricking their devices is quite dissuading.
Can someone point me in the right direction because there is conflicting data out there where some people just format data and cache while others mount drive and format system, data, cache, etc in addition to the previous step. Please help cause I really want to give CM10 a try.
Format system, data, cache, and dalvic cache. Flash the zip and gapps in that order. Enjoy.
Sent from my Nexus S 4G using xda premium
hey, just a quick question on the gapps. What is included with the zipped package? Can I not just d/l them from the market?? I flashed the gapps, but it didnt have gmail, maps and all that, I had to get them from the market.. (forgive the noob question, this was the first time I had ever flashed a rom)
Thanks, and sorry for derailing..
123go! said:
hey, just a quick question on the gapps. What is included with the zipped package? Can I not just d/l them from the market?? I flashed the gapps, but it didnt have gmail, maps and all that, I had to get them from the market.. (forgive the noob question, this was the first time I had ever flashed a rom)
Thanks, and sorry for derailing..
Click to expand...
Click to collapse
gapps let you have all Google services(like Play Store indeed)! For Gmail and Maps you install them from Play Store.
aladin6 said:
gapps let you have all Google services(like Play Store indeed)! For Gmail and Maps you install them from Play Store.
Click to expand...
Click to collapse
ok, so if I flashed the gapps, and on boot I had google play installed, then it worked? I guess I was expecting there to be all the google apps, but the majority of them are on the market now anyways....
---------- Post added at 09:30 PM ---------- Previous post was at 09:28 PM ----------
wessonster said:
I've been rummaging through all of XDA, YouTube and other independent sites to find a simple and comprehensive method to flash Cyanogenmod 10 and CWM Recovery 6.xx.xx on my old Nexus S I9023 but none of the walk-throughs are comprehensive enough. I'm pretty new when it comes to the flashing bit and the horror stories out there about people bricking their devices is quite dissuading.
Can someone point me in the right direction because there is conflicting data out there where some people just format data and cache while others mount drive and format system, data, cache, etc in addition to the previous step. Please help cause I really want to give CM10 a try.
Click to expand...
Click to collapse
Here OP, this is the guide i used to flash it (I am a noob as well, first rom I have flashed)
http://wiki.cyanogenmod.org/wiki/Nexus_S:_Full_Update_Guide
123go! said:
ok, so if I flashed the gapps, and on boot I had google play installed, then it worked?
Click to expand...
Click to collapse
Yes. Most flashable gapps are just those that are built-in and cannot be downloaded via play store.
I have already posted a few guides regarding rooting and flashing for devices like Gnex, Note etc on DroidViews. Tomorrow when I have my NS, I will surely try to write up for this, most probably a screenshot guide with proper step-by-step instructions.
wessonster said:
I've been rummaging through all of XDA, YouTube and other independent sites to find a simple and comprehensive method to flash Cyanogenmod 10 and CWM Recovery 6.xx.xx on my old Nexus S I9023 but none of the walk-throughs are comprehensive enough. I'm pretty new when it comes to the flashing bit and the horror stories out there about people bricking their devices is quite dissuading.
Can someone point me in the right direction because there is conflicting data out there where some people just format data and cache while others mount drive and format system, data, cache, etc in addition to the previous step. Please help cause I really want to give CM10 a try.
Click to expand...
Click to collapse
Hi, if you want a simple tool that help you to install driver, unlock, flash a custom recovery, root, backup and later flash a custom rom (remember to do a complete nandroid backup immediately after root!) use wugfresh tool here:
http://forum.xda-developers.com/showthread.php?t=1766475
If you want to learn how to flash a custom rom, the procedure is the same for all rom, once you learn one, you can flash all you want, read here:
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
I just wish to share this app that I discovered in the Play Store. Unlike the CM updater that still would download 100mb+ zip files whenever you're updating, this app will download only the essential parts that were updated from the previous version. For example, in the last few nightlies, it only needed to download around 4mb worth of data from the CM website thus saving me data, time, and hassle. The link to app here: CyanDelta Updater
Posted using xda mobile app
Related
First off all, credit for this guide goes to steal25 and lowetaxes for the original guide
It was just revised for the Shift
A special thanks also goes to strapped365 for his help revising this guide
READ ALL THE INSTRUCTIONS ALL THE WAY THROUGH FIRST BEFORE DOING ANYTHING
I do not reccomend "just flashing over a ROM"
1. REREAD THE INSTRUCTIONS (If your seeing this for the second time, proceed)
2. Make a Nandroid backup of your present set up.
3. Boot into Recovery
4. WIPE EVERYTHING!!! I CANNOT STRESS THIS ENOUGH
•Wipe in this order:
DALVIK CACHE
CACHE PARTITION
FORMAT SYSTEM
FORMAT SD:EXT
FORMAT DATA
FORMAT CACHE
THEN WIPE ALL USER DATA/FACTORY RESET
Do all of these 3Xs . Some do it only once. Some do it as much as 4Xs . 3Xs is Recommended
WIPE EVERYTHING EXCEPT THE SD CARD
5. Flash ROM (of your choosing)
6. Reboot (first Boot may take a while ) this is NOT a Bootloop.
7. Before you do anything, let the ROM settle in for about 10 mins. After about 10 mins, unlock the lockscreen.
8. Skip through Initial set up. DO NOT set up any accounts yet. Check and make sure everything installed.
9. IF NOT ON A SENSE ROM go ahead and install google apps
10. Now go ahead and sign into all your accounts. Set up Google and all that good stuff.
11. Open market, and install apps. If you use Titanium Backup DO NOT RESTORE System Apps or Data. Try not to restore Data for any app. If you restore an app like games and such, just restore the app.
THESE ARE THE SAME INSTRUCTIONS I FOLLOW. THE RESULT IS A BETTER FLASH THAN JUST DOING A REGULAR WIPE.
THIS PROCESS WILL ENSURE THE SYSTEM IS WIPED PROPERLY. RESULT, LESS OF A CHANCE FOR ISSUES TO ARISE!
The Original THREAD for the Guide
***I am not responsible for any damage that may occur to your device. If it BLOWS UP - MELTS - STEALS YOUR CAR - OR EATS YOUR GOLDFIISH IT'S ON YOU. This is only a recommendation of what you should do to Properly Wipe your device. If you cannot follow instructions that is on you.
You forgot google apps and google apps new talk which should be flashed right after the rom.
He's a sense guy probably why.
Sent from my Rooted Thrive
VICODAN said:
You forgot google apps and google apps new talk which should be flashed right after the rom.
Click to expand...
Click to collapse
Yea these instructions were orignally posted (by him) on themikmik.com which is soley a sense rom development site, and he just reposted them on XDA because there are alot of people who don't read themikmik (i hardly do) lol.
Btw nice idea posting it here too Prboy1969
Sent from my Epicly Blue Shift!
VICODAN said:
You forgot google apps and google apps new talk which should be flashed right after the rom.
Click to expand...
Click to collapse
Didn't forget . But just for you, updated OP .
prboy1969 said:
Didn't forget . But just for you, updated OP .
Click to expand...
Click to collapse
I'd give you a thanks but I'm limited to 5 per day.
Thanks very much for the detailed step-by-step instructions. Great tips... and I've successfully flashed MikShifted G Executive Edition onto my Evo Shift. It's *gorgeous*!!
Your very welcome. Glad I could help .
9. Boot into recovery, and wipe CACHE and DALVIK-CACHE. Then Reboot phone.
is wipe cache the same as format cache ?
Yes and no. It's a deeper clean allegedly.
This is the one I meant
Here we go again . I meant this one .
Can we get this stickied please?
is there anyway to write a script that can be run from recovery to do all that stuff automatically?
I'm sure it can be accomplished. I just don't know how :'(
TEAM MiK
Mik Roms Since 3/13/11
prboy1969 said:
Can we get this stickied please?
Click to expand...
Click to collapse
I'd second that but I don't agree with the instructions regarding Titanium. Of course, one should only restore system data at their own risk with the expectation that it'll mess things up but I've never had any trouble restoring data for nonsystem apps. For me being able to restore an app's data after a wipe or reset is one of the main benefits of having root access. I would never flash different ROMs if I thought I was gonna lose all my app data.
raydawg said:
is there anyway to write a script that can be run from recovery to do all that stuff automatically?
Click to expand...
Click to collapse
Yes. My Linuxfu is weak though, so I'm not gonna be writing it but I think it's a fairly easy task. Maybe check the Evo forums, I've seen a lot of them mention a full wipe zip. I wanna say it's Myn's but wouldn't place money on it.
jesusice said:
I'd second that but I don't agree with the instructions regarding Titanium. Of course, one should only restore system data at their own risk with the expectation that it'll mess things up but I've never had any trouble restoring data for nonsystem apps. For me being able to restore an app's data after a wipe or reset is one of the main benefits of having root access. I would never flash different ROMs if I thought I was gonna lose all my app data.
Yes. My Linuxfu is weak though, so I'm not gonna be writing it but I think it's a fairly easy task. Maybe check the Evo forums, I've seen a lot of them mention a full wipe zip. I wanna say it's Myn's but wouldn't place money on it.
Click to expand...
Click to collapse
There is a " Format ALL " for the OG EVO made by Calkulin. It's on his thread HERE. But it's only for 2.1 / 2.2 . As for my opinion on TB, well it comes from a LOT of Flahing ( read FLASHAHOLIC ). That's why I'm always flashing devices for other people. Just so I can get that rush of installing a new Rom on a device . Yes I know it's a sickness . But I figure it's safer to instruct people not to restore any data. Because we are who we are, and if you say some is ok. Then what is likely to happen is it will almost all be restored . Most always causing all kinds of weird issues. Yes you can restore some app data, but you have to use common sense ( no pun intended ) .
Mod can you please sticky this for us. Thank you
good guide noticed a big improvment! thanks. +1 for sticky!
No problem. Glad it helped you .
I'm not able to get any Google Apps to work (Market, Gmail, etc.) to work on CM 7.1 Port. However, Google Voice works fine..strange.
Any suggestions?
syllogyking said:
I'm not able to get any Google Apps to work (Market, Gmail, etc.) to work on CM 7.1 Port. However, Google Voice works fine..strange.
Any suggestions?
Click to expand...
Click to collapse
I would try wiping cache and dalvic and reflash gapps.
Sent from my PG86100 using XDA App
No gapps showing
I've a similar problem, in my case I can't find Google Play, google maps of youtube in my applications list, only google search and google talk. I'm using CM7 by Quarx and I've tried two different versions of gapps, gapps-gb-20110828-signed.zip and later gapps-gb-20120404-updated.zip (last one found in this post http://forum.xda-developers.com/showthread.php?t=1595963), both installed in recovery mode with clockworkmod.
Any help will be welcome.
Thanks.
raul1113 said:
I've a similar problem, in my case I can't find Google Play, google maps of youtube in my applications list, only google search and google talk. I'm using CM7 by Quarx and I've tried two different versions of gapps, gapps-gb-20110828-signed.zip and later gapps-gb-20120404-updated.zip (last one found in this post http://forum.xda-developers.com/showthread.php?t=1595963), both installed in recovery mode with clockworkmod.
Any help will be welcome.
Thanks.
Click to expand...
Click to collapse
Are you reflashing the rom along each time you try flashing gapps again?
There's a possibility that there's multiple installs of Market\Play conflicting with each other if all you're doing is wiping cache, wiping dalvik, and flashing gapps -- especially if you're flashing different versions of gapps.
What I recommend is backing up all your important apps data and reinstalling the rom. There's a chance that doing a factory reset then flashing gapps will work, but a fresh install is a better way to go.
skeevy420 said:
Are you reflashing the rom along each time you try flashing gapps again?
There's a possibility that there's multiple installs of Market\Play conflicting with each other if all you're doing is wiping cache, wiping dalvik, and flashing gapps -- especially if you're flashing different versions of gapps.
What I recommend is backing up all your important apps data and reinstalling the rom. There's a chance that doing a factory reset then flashing gapps will work, but a fresh install is a better way to go.
Click to expand...
Click to collapse
Finally worked!!!! I just did what skeevy420 suggested and after I added my google account "voilà" google play was there.
Thanks for your help.
PD: I made a clean backup of my stock rom (AT&T), do you think that could be useful to somebody?
raul1113 said:
Finally worked!!!! I just did what skeevy420 suggested and after I added my google account "voilà" google play was there.
Thanks for your help.
PD: I made a clean backup of my stock rom (AT&T), do you think that could be useful to somebody?
Click to expand...
Click to collapse
Nah, not unless you did something real cool with it that's hard to duplicate. We can just flash the sbf and get the same thing.
//Off to figure out that clock issue...again...and start on Paranoid Android:fingers-crossed:
Hi guys,
The question is as above. How do I update my paranoid android rom through goo manager?
I downloaded the new rom files but I ain't sure what to do under the flahs rom section. Do i have to do a factory reset or do i have to wipe the cache?
I tried updating once without any of these options. In the end, i lost my google apps. When I reinstore it, the expanded desktop function went missing. So I am hoping that someone can tell me the proper way of flashing it to avoid this problem in the future. Thank you!
Go read the first post of the paranoid android rom under android original development. Don't flash things until you read the instructions. Cache is wiped by the rom, and you need gapps with a new install.
Sent from my Nexus 7 using xda app-developers app
delonicdevil said:
Hi guys,
The question is as above. How do I update my paranoid android rom through goo manager?
I downloaded the new rom files but I ain't sure what to do under the flahs rom section. Do i have to do a factory reset or do i have to wipe the cache?
I tried updating once without any of these options. In the end, i lost my google apps. When I reinstore it, the expanded desktop function went missing. So I am hoping that someone can tell me the proper way of flashing it to avoid this problem in the future. Thank you!
Click to expand...
Click to collapse
as mentioned, you should always read the ROM thread completely before you flash.
the correct procedure is to download the updated zip, optionally check the md5 sum to make sure it did not get corrupted in transit [but if it got corrupted, I think CWM will tell you, and fail to even try to flash the zip], then flash the rom, and then flash gapps before rebooting. [if you reboot before flashing gapps, you will have to re-login, and re-authenticate apps like Google Voice, etc].
mvmacd said:
as mentioned, you should always read the ROM thread completely before you flash.
the correct procedure is to download the updated zip, optionally check the md5 sum to make sure it did not get corrupted in transit [but if it got corrupted, I think CWM will tell you, and fail to even try to flash the zip], then flash the rom, and then flash gapps before rebooting. [if you reboot before flashing gapps, you will have to re-login, and re-authenticate apps like Google Voice, etc].
Click to expand...
Click to collapse
and one more thing, flash a new kernel ONLY after the first reboot.
Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
thanks alot!
Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
OH..I didn't knew it. Thanks!
I am not getting on how to do that
Hi,
Can any one post link to forum?
I am using paranoid android and in goomanager its showing new update available..!
after downloading zip what to do next?
If any one can put screenshot or list step it would be much helpful..
Thanks in advance...
Balaji_NEXUS said:
OH..I didn't knew it. Thanks!
Click to expand...
Click to collapse
Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
This actually makes no difference, aside from making the process more time consuming. The few and far between anecdotes that led to this practice are a cum hoc ergo propter hoc fallacy. Without a doubt, it does not hurt anything, but it also yields no real benefit over flashing in the same recovery session.
Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
This doesn't really matter, apart from making you have to "Android is Upgrading" 2x.
The process I follow which never fails me is (there may be a quicker way, but I know this will always work):
1 - Download ROM / Kernel / GAPPS etc
2 - Move all downloaded files to a single folder named "Flashing" or something
3 - Reboot to Recovery
4 - Wipe Cache and Dalvik Cache
5 - Flash ROM
6 - Flash GAPPS
7 - Flash Kernel
8 - Wipe Cache / Dalvik
That is the process for updating Paranoid android
Updating to a completely different ROM would require a Factory reset and Format
Wilks3y said:
This doesn't really matter, apart from making you have to "Android is Upgrading" 2x.
The process I follow which never fails me is (there may be a quicker way, but I know this will always work):
1 - Download ROM / Kernel / GAPPS etc
2 - Move all downloaded files to a single folder named "Flashing" or something
3 - Reboot to Recovery
4 - Wipe Cache and Dalvik Cache
5 - Flash ROM
6 - Flash GAPPS
7 - Flash Kernel
8 - Wipe Cache / Dalvik
That is the process for updating Paranoid android
Updating to a completely different ROM would require a Factory reset and Format
Click to expand...
Click to collapse
You can safely leave off steps 2, 4, & 8
Anything you download using goo goes into a folder called goo manager. Just flash from there.
Wiping cache and dalvik is an old wives tale so to speak. You aren't doing a damn bit of good doing that. You can skip it
Sent from my Galaxy Nexus
Pirateghost said:
You can safely leave off steps 2, 4, & 8
Anything you download using goo goes into a folder called goo manager. Just flash from there.
Wiping cache and dalvik is an old wives tale so to speak. You aren't doing a damn bit of good doing that. You can skip it
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I know about the Goo Folder, however I like to keep all my stuff in the same place, and I download my Kernels from browser so I made my own for Flashing
Why is it a wives tale?
Thanks
Wilks3y said:
I know about the Goo Folder, however I like to keep all my stuff in the same place, and I download my Kernels from browser so I made my own for Flashing
Why is it a wives tale?
Thanks
Click to expand...
Click to collapse
Because when you flash a new ROM to /system, it has to rebuild the dalvik for the signature on the new ROM. Android handles this on its own. I haven't checked but I bet the updater-script wipes cache for you also. I have never manually wiped cache and dalvik for a ROM update on my nexus devices.
Sent from my Galaxy Nexus
Pirateghost said:
Because when you flash a new ROM to /system, it has to rebuild the dalvik for the signature on the new ROM. Android handles this on its own. I haven't checked but I bet the updater-script wipes cache for you also. I have never manually wiped cache and dalvik for a ROM update on my nexus devices.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Thanks for the advice bud
I'm guessing its still necessary if going to a whole new ROM?
Wilks3y said:
Thanks for the advice bud
I'm guessing its still necessary if going to a whole new ROM?
Click to expand...
Click to collapse
When going from one rom to another the only thing that you should do is run factory reset in recovery
Sent from my Galaxy Nexus
Pirateghost said:
When going from one rom to another the only thing that you should do is run factory reset in recovery
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Ok great.
Appreciate that
Hi there,
I'm kinda embarassed to ask, cause I think this MUST have been answered already - but seriously, I can't find it >.<
the latest nightlies (3/25) caused my find5 to be unable connect to any Wifi networks (it found the networks, but wasn't able connect..),
so i wanted to check if I messed sth up, or if it was just the nightly and decided to revert to an older version. However in doing so
I think i messed up a lot since some apps were displayed at beeing not installed, the play store didnt display any apps, not even the ones
installed ect... (wifi was working again btw.)
What I did was wiping cache, dalvik, system and flashing the older version downloaded from the omni rom website and wiping dalvik/cache again.
The uninstalled apps (which were still displayed) and the weird play store persisted when i went back to 3/25.
Where did I mess up? .. Sorry to bother.
chuSmu
Hi!
chuSmu said:
What I did was wiping cache, dalvik, system and flashing the older version downloaded from the omni rom website and wiping dalvik/cache again.
The uninstalled apps (which were still displayed) and the weird play store persisted when i went back to 3/25.
Click to expand...
Click to collapse
Did you wipe your data partition? That is where your apps are located. If you have corrupted apps, that's where I would look.
But, of course, before doing anything, don't forget to make a backup in your recovery!
Alexandre-P said:
Hi!
Did you wipe your data partition? That is where your apps are located. If you have corrupted apps, that's where I would look.
But, of course, before doing anything, don't forget to make a backup in your recovery!
Click to expand...
Click to collapse
Hi Alexandre-P,
thanks for your reply! I didn't wipe the data cause i usually don't have to do it when flashing a new version of the rom
of the same android version. Unfortunately i didn't do a backup pre flashing, but I will before tinkering around more ^^
But can you confirm that the flashing process in general was correct, or in case it was incorrect, where did i mess up?
Hey hi. I am a newbie. i am using samsung gs3 and i am on jb 4.3, i want to install custom rom. so pleas help me with how to install custom roms and and what are the this i should be needed
hellboyxxx said:
Hey hi. I am a newbie. i am using samsung gs3 and i am on jb 4.3, i want to install custom rom. so pleas help me with how to install custom roms and and what are the this i should be needed
Click to expand...
Click to collapse
There is a difference in installing a custom rom for the first time and flashing new versions - in this aspect the question doesn't exactly relate.
Since the installing a custom rom for the first time (I assume that's what u want) includes steps that differ from device to device you should
check your device's forum. You should find all the answers there.
Just an advice - no offense intended, really: Try to avoid posting things that don't relate in other threads. Use the search function in the forum/google before asking a question. If you can't find anything post a new thread!
kind regards chuSmu
back to the topic: can anyone confirm the way i flashed when reverting to a previous version?
You wiped /system but not /data? That's where things went wrong. Your fresh and newly installed /system apps are looking at the same funky /data from your previous install.
Generally, if you want to revert, simply dirty-flash the nightly you're looking for. It works.
If you're looking for a clean installation to troubleshoot a problem, TiBu your apps, wipe /system /data /cache & dalvik and start completely clean.
chuSmu said:
Hi there,
I'm kinda embarassed to ask, cause I think this MUST have been answered already - but seriously, I can't find it >.<
the latest nightlies (3/25) caused my find5 to be unable connect to any Wifi networks (it found the networks, but wasn't able connect..),
so i wanted to check if I messed sth up, or if it was just the nightly and decided to revert to an older version. However in doing so
I think i messed up a lot since some apps were displayed at beeing not installed, the play store didnt display any apps, not even the ones
installed ect... (wifi was working again btw.)
What I did was wiping cache, dalvik, system and flashing the older version downloaded from the omni rom website and wiping dalvik/cache again.
The uninstalled apps (which were still displayed) and the weird play store persisted when i went back to 3/25.
Where did I mess up? .. Sorry to bother.
chuSmu
Click to expand...
Click to collapse
chuSmu said:
Hi Alexandre-P,
thanks for your reply! I didn't wipe the data cause i usually don't have to do it when flashing a new version of the rom
of the same android version. Unfortunately i didn't do a backup pre flashing, but I will before tinkering around more ^^
But can you confirm that the flashing process in general was correct, or in case it was incorrect, where did i mess up?
Click to expand...
Click to collapse
cyril279 said:
You wiped /system but not /data? That's where things went wrong. Your fresh and newly installed /system apps are looking at the same funky /data from your previous install.
Generally, if you want to revert, simply dirty-flash the nightly you're looking for. It works.
If you're looking for a clean installation to troubleshoot a problem, TiBu your apps, wipe /system /data /cache & dalvik and start completely clean.
Click to expand...
Click to collapse
Thanks ..that was my mistake >.<.
Hi again!
chuSmu said:
I didn't wipe the data cause i usually don't have to do it when flashing a new version of the rom
of the same android version.
Click to expand...
Click to collapse
You generally don't have to wipe /data if you want to update your ROM version.
But if you want to downgrade your actual ROM's version, or switch to another ROM, I think you should format /data, as it might contain updated or incompatible new apps, frameworks or setting files.
Thanks again. I'll keep that in mind!
Sent from my Find 5 using XDA Premium 4 mobile app
Q&A for [ROM][AOSP][5.0.0_r2 LRX21M][BSZAospLP v1.0][SuperSU|BusyBox][06/11/14]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][AOSP][5.0.0_r2 LRX21M][BSZAospLP v1.0][SuperSU|BusyBox][06/11/14]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
keith.valdez said:
If I'm flashing from an All F2Fs Ext4 rom, are there any special preparations I need to perform to ensure I don't brick? I would like to flash it but I want to ensure that there are few caveats first. Thanks.
Click to expand...
Click to collapse
Make sure you change the partitions filesystem in TWRP to ext3 or it will not work!
NUMB401 said:
Make sure you change the partitions filesystem in TWRP to ext3 or it will not work!
Click to expand...
Click to collapse
Exactly - if coming from All-F2FS in recovery put cache and data back to ext4 otherwise when you boot it will think your tablet is encrypted and ask for a password!
Thanks for the ROM. However a tilapia(3g) version would be greatly appreciated!
Click to expand...
Click to collapse
I have built Lolipop from source for it but 3G does not seem to be working with radio from KitKat (and I don't know where to get another radio.img)
failing Google+ apk
Trying to install google+ and it keeps failing any ideas? I've tried the past 3 versions and it won't work.
irishman13 said:
Trying to install google+ and it keeps failing any ideas? I've tried the past 3 versions and it won't work.
Click to expand...
Click to collapse
Known incompatible for now. Rest assured it'll be fixed by the ota ?
For those of you still having issues -- make absolutely sure that you've wiped And repaired the cache, data, and system partitions, under TWRP's advanced menu (you have to select each 1 at at time). It takes like 1-2 secs per partition. Without the repair option, you're gonna be stuck on the Google logo forvever.
THEN restart once repaired wiped repaired, and flashed, and don't bother to let TWRP install SuperSU, as the ROM already has it.
---------------
Admin Note: this thread has a dedicated questions and answers section which you can access here -->.
@nickmv is that if you're coming from a f2fs Rom or for everyone?
gsmyth said:
For those of you still having issues -- make absolutely sure that you've wiped And repaired the cache, data, and system partitions, under TWRP's advanced menu (you have to select each 1 at at time). It takes like 1-2 secs per partition. Without the repair option, you're gonna be stuck on the Google logo forvever.
THEN restart once repaired wiped repaired, and flashed, and don't bother to let TWRP install SuperSU, as the ROM already has it.
---------------
Admin Note: this thread has a dedicated questions and answers section which you can access here -->.
@nickmv is that if you're coming from a f2fs Rom or for everyone?
Click to expand...
Click to collapse
Just F2FS
---------- Post added at 12:42 PM ---------- Previous post was at 12:42 PM ----------
irishman13 said:
Trying to install google+ and it keeps failing any ideas? I've tried the past 3 versions and it won't work.
Click to expand...
Click to collapse
Latest GApps newly linked in OP has a working Google+
There is broken "Ok Google" hotword as well as voice search. It just won't listen to me
First off let me say this is awesome and really breathed new life into my old N7! Secondly I used the Tap & Go setup method from an GPE One M8 and it didn't really work all the way but whatever.
The issue is there is now an undismissable notification on my M8 saying setup completed. Any ideas how to get rid of this?
Oh and also has Face Unlock ever been present on the Nexus? Wanted to try it out but wasn't listed as an option. Thanks a ton!
TitBkp
Hi
I have supersu installed but titanium backup doesn't recognise the device is rooted! Any ideas? Other root apps work on android 5 but this one doesn't.
I cannot log into play store since upgrading to lollipop. How can I fix this?
Sent from my AOSP on Grouper using XDA Free mobile app
Successfully installed via multirom, however play store crashes when opened.
am2012 said:
Hi
I have supersu installed but titanium backup doesn't recognise the device is rooted! Any ideas? Other root apps work on android 5 but this one doesn't.
Click to expand...
Click to collapse
Try this beta one:
http://forum.xda-developers.com/showpost.php?p=56629869&postcount=196
When installing the GApps package I get this error: E:Error executing updater binary in zip '/data/media/0/sideload.zip'
I originally got a different one but I remembered I was on the "buggy" 2.7.1.1 version so I updated to latest 2.8.1.1 version and well...this. I've wiped my data/cache/system/all of it and repaired the data n cache and then did this all and still a no go. What am I doing wrong? Am I missing something? The only issue I noticed listed for this was the recovery I used.
S1L3nTShaDoWz said:
When installing the GApps package I get this error: E:Error executing updater binary in zip '/data/media/0/sideload.zip'
I originally got a different one but I remembered I was on the "buggy" 2.7.1.1 version so I updated to latest 2.8.1.1 version and well...this. I've wiped my data/cache/system/all of it and repaired the data n cache and then did this all and still a no go. What am I doing wrong? Am I missing something? The only issue I noticed listed for this was the recovery I used.
Click to expand...
Click to collapse
So issue is just with the GApps zip file? Try flashing the ROM then rebooting recovery I had read in my main thread... Also be sure MD5 matches.
bshiznit said:
So issue is just with the GApps zip file? Try flashing the ROM then rebooting recovery I had read in my main thread... Also be sure MD5 matches.
Click to expand...
Click to collapse
Yes originally it was but I managed to fix it by re-doing it all over again w system repair too, though I believe it was doing it over again that fixed it the system repair could've helped. Anyways new issues now, TWRP claims I have no OS....yet here I am....booted in 5.0 w GApps. Oh well nothing to be upset by I guess, least I fixed it.
S1L3nTShaDoWz said:
Yes originally it was but I managed to fix it by re-doing it all over again w system repair too, though I believe it was doing it over again that fixed it the system repair could've helped. Anyways new issues now, TWRP claims I have no OS....yet here I am....booted in 5.0 w GApps. Oh well nothing to be upset by I guess, least I fixed it.
Click to expand...
Click to collapse
Glad to hear it! Sometimes /system remains mounted so TWRP will incorrectly report missing OS
I guess the mic doesn't work, Shazam doesn't work?
Works great so far! Only issue appears to be the volume buttons (when used for notification volume) results in crashing.