Database Users

[NIGHTLY][ROM] CyanogenMod 7 for Samsung Captivate (captivatemtd)

This thread is reserved for nightly builds of CyanogenMod Rom for Samsung Captivate.
All Samsung Roms run on top of BML/RFS, CyanogenMod 7 does NOT.
It runs on MTD/yaffs2 (like Nexus One) which means you'll not able to flash just any kernel or run just any other filesystem you want. Use it as it is if possible, otherwise confirm with the kernel developer that you are trying to install whether it would work with CM. We do not support other kernels and know nothing about their capabilities or compatibility. Only the data partition, which is on movinand, is ext4 like on speedmod or voodoo ("lagfix"). No "lagfix" is necessary because this does not use any Samsung proprietary file systems.
CyanogenMod is a free, community built distribution of Android 2.3 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
What are Nightly builds? Auto compiled build of the latest CyanogenMod source from github. This version changes each night and aren't officially supported.
If you find bugs/issues you can/must discuss here (do not submit nightlies bugs on CyanogenMod issue tracker).
Warning : Not for new users, flash this build only if you know what you are doing !!! Make SURE you can get into Download mode using only buttons (no other method, Download mode from just buttons is essential).
INSTRUCTIONS:
Latest version: http://download.cyanogenmod.com/?device=captivatemtd
Check the md5sum if you want to be sure that the download worked (different OSes have different programs that do md5, on ubuntu it is md5sum that you run against the zip you download and compare to the md5sum number shown on the download website). ROMManager does this automatically for ROMs you download via ROMManager.
- First time flashing CM 7 to your Captivate (or coming from another ROM)?
Easy way:
Start with a rooted Eclair/Froyo running Eclair/Froyo Bootloaders (do not ask us how to do this).
Install ROMManager Premium.
Flash ClockworkMod Recovery. Pick Captivate (MTD) (ignore the warning about not having an official, pick ClockworkMod 2.x).
Make sure you can reboot into ClockworkMod recovery from ROMManager. Reboot and get back into ROMManager Premium.
Choose download ROMs.
Pick the CyanogenMod Nightlies.
Check the Google Apps addon.
Check Backup current ROM!
Check wipe data, cache, dalvik cache.
Let ROMManager finish the installation.
Harder way:
Make sure you're running a Eclair/Froyo Firmware (2.1 or 2.2) and Eclair/Froyo Bootloaders!
Root your device and install ClockworkMod Recovery.
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon (through ROMManager is easiest)
- Upgrading from earlier CM7?
ROM Manager method:
Install ROMManager Premium.
Flash ClockworkMod Recovery. Pick Captivate (MTD) (ignore the warning about not having an official, pick ClockworkMod 3.x).
Choose Download ROMs.
Pick the CyanogenMod Nightlies.
Check the Google Apps addon.
Check Backup current ROM!
Check wipe cache, dalvik cache.
Let ROMManager finish the installation.
Clockwork Mod method:
Download and push the ROM zip file to the sdcard.
Reboot into recovery.
Do a Nandroid Backup!
Install the ROM zip from sdcard (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps. After flashing the rom, don't forget to flash Google Addon package if you want it. ROM Manager will allow you to flash it if you just go into it and after flashing the ClockworkMod recovery for MTD devices, choose Download ROMs, and pick Google Apps.
Additional Information:
Maintainers:
atin - http://twitter.com/atinm
codeworkx - http://twitter.com/codeworkx
coolya - http://twitter.com/dumdidum
guiperpt - http://twitter.com/guiperpt
unhelpful - http://twitter.com/unhelpfulone
Irc:
Host: irc.freenode.net:6667
Channels: #cyanogenmod, #cyanogenmod-dev, #cmsgs
Changelog:
Generic Changelog CMSRC Twitter
Device specific Changelog by igor.tonky
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy![/QUOTE]

SWEET thanks! Gonna try this out and test it.
Sent from my GT-I9000 using XDA App

Oh snap!
di11i 6.0 w/ Suckerpunch #53
Underclocked to 600mhz
Undervolted to -100mV

Very nice! definitely going to flash it
Is camera working fine now?

Wow
Wow you mean I can actually use Gingerbread on my cappy. I was getting bored of playing with ginger on my HTC dream which is slowwwwer then slow.
Thanks to every dev working on this.

atinm said:
your kitties, doggies and maybe even goldfish are no longer safe.
Click to expand...
Click to collapse
hahaha!
That is the funneyest thing i have herd.

Just want to make sure my understanding is correct
- Don't use "reboot recovery" command or other shiny things to do this!
Flash cm7-captivate-initial-kernel.tar as pda using odin without auto-reboot
So after flash of efs pull battery, get to dl mode, flash initial kernel with auto reboot off. Pull bay after flash go back to recovery?
Do a wipe
Factory restore in clockwork?
Install the Nexus S USB-Drivers from SDK-Manager if you're using windows.
Are these drivers needed to use odin our just files transfers
To revert to a samsung rom, simply use odin with repartition option enabled.
Does odin one click qualify here or use full version?
Just making sure I understand instructions fully, thanks

thx for your hard work man

DAGr8 said:
thx for your hard work man
Click to expand...
Click to collapse
Can't wait to see what you do with this.

Thank you very much but because this is a test release, I will keep my eye very close to see how everyone else does on this ROM. Actually, I'm scared to flash this until it's stable enough for a daily driver .

Can I reserve a post this late? Lol
Sent from my Captivate using XDA App

CM7 getting awfully close!

mcord11758 said:
So after flash of efs pull battery, get to dl mode, flash initial kernel with auto reboot off. Pull bay after flash go back to recovery?
Click to expand...
Click to collapse
No, please read the instructions fifty-thousand times before you do anything. It clearly says to use the three button combo to reboot, directly underneath that. If you do a battery pull while in Download mode, you risk destroying your phone.
mcord11758 said:
Factory restore in clockwork?
Click to expand...
Click to collapse
Yes.
mcord11758 said:
Are these drivers needed to use odin our just files transfers
Click to expand...
Click to collapse
These are drivers to use your phone (incorrect, but avoiding the question). Just install the drivers, because the instructions say so. If you don't, you can't plug your phone into your computer.
mcord11758 said:
Does odin one click qualify here or use full version?
Click to expand...
Click to collapse
Odin One Click. Or Odin3. It doesn't matter. Just reboot into Download mode using the button combo and use Odin.

I must be dumb but, There is no efs-backup for initial kernel to even download, Or I'm unable to find it. On that page, all I see is Initial package, update, and google-addon. No kernel, no efs package.
EDIT: k. I just fail. It was inside the initial package. .-.

Thank you for the response. The initial kernel to be flashed via odin is the z image inside the initial package?

This is why I love Android and XDA! Sweet! Even before Samsung releases it to the I9000 (granted it's still under development).

Are the modem links dead for anyone else?

Yeah I have no idea where the "initial kernel" is. It's not ANYWHERE on the site, nor in the initial package.

Konner920 said:
Yeah I have no idea where the "initial kernel" is. It's not ANYWHERE on the site, nor in the initial package.
Click to expand...
Click to collapse
Yeah, couldn't find that either.

Great job guys. I want to try this as I will flash almost anything once. I will give it some thought. I feel I am one step above noob. Any noobs out there might want to wait some more. Then again if you are a flasher...
Awesome work/progress.
Edit: I made the plunge. Worth every minute.

[GUIDE] [SOLVED] HOW TO FLASH CM11 ON BRAVO (Previously "Cm11 Issue, Status 0 Error")

[GUIDE] [SOLVED] HOW TO FLASH CM11 ON BRAVO (Previously "Cm11 Issue, Status 0 Error")
So, I tried to flash CM11 for the MB520 Bravo, found in this post:
http://forum.xda-developers.com/showthread.php?t=2515036
So I copy the ROM .zip to the SD card in my Bravo, and I reboot into CWM Recovery version 5.0.3.9, with the name "CyanogenDefy Recovery v5.0.3.9-jordan" on the top of the screen. This version of recovery came from josuearisty's one click tool for rooting and putting a recovery on the MB520 Bravo, which can be found here:
http://forum.xda-developers.com/showthread.php?t=1559109
I factory reset/clear cache like I know I am supposed to when flashing a custom ROM, but when I select the "Install zip from sd card" option and select the CM11 MB520 Nightly to flash, it gives me this:
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/cm-11-20140407-NIGHTLY-mb520.zip
(Status 0)
Installation aborted.
So then as I read on further in the CM11 install page, it says this: "For CM10,10.1,10.2 < 07.11.13 users: To install KitKat, need update recovery. Do not forget reboot, after install recovery. http://defy.bytekiste.de/cm11-nightl...e-recovery.zip". The thread is for the DEFY+ according to the title, but since I see there's also a Bravo download link, I assume that this means that I should install this updated recovery as well, since I am running the stock rooted 2.2.1, which is in fact "less than" 10.x or 4.x. I select the same "Install zip from sd card" option, and the same Status 0 is presented to me.
Then I go and try putting on CM10.x first, because then according to the thread's instructions I won't have to install this updated recovery if I am running that currently. I find a link for CM10.2 for the Bravo here:
http://forum.xda-developers.com/showthread.php?t=1779324
I download it, do the same install method, and I STILL GET A STATUS 0 saying it is unable to flash the zip!
Now I've done some research, and I THINK the status 0 means the zip is not compatible with my phone. I could see that with the updated-recovery.zip, but I don't see why that is showing up for the ROM's themselves because they are in fact made for the mb520.
Can someone please tell me what I am doing wrong, and if possible post a set of step-by-step instructions as to how I can go installing CM11 on my MB520 Bravo? Thanks.

*BUMP*
UPDATE: I seemed to get around the Status 0 issue in CM10.2 so far. First, I went from 2.2.1 to CM9 4.0.4. Then, I went from CM9 to CM10.1 in quarx2k's "archive" folder on his website. This updated my recovery to TWRP 2.6.0.0. From this new TWRP, I was able to flash the latest 10.2 nightly CM rom. I will keep this posted on how things go, in case anyone out there is actually following this

*BUMP AGAIN, PROBLEM SOLVED*
I got CM11 finally running on the Bravo. Here's the steps I took to get it on there. Some of these steps may be unnecessary, but I'm just going to list EXACTLY what I did in case all of these steps really are necessary:
1) I started out with stock 2.2.1. I rooted it, and used josuearisty's tool for one click root and recovery just to put recovery on it.
2) I flashed a build of CM9 from quarx2k's website. Here is a direct link to download it. Flashing this ROM also updated my cwm recovery. HOWEVER, this new version of recovery had scrolling issues with the volume rocker, so I just rebooted and pressed the vol. down button at the blue flashing LED light to boot into the boot menu. From there, I select to go to recovery, but instead of selecting "Custom Recovery" I select "Stable Recovery". This takes me back to the older recovery I got with the one click tool.
3) I flashed one of quarx2k's builds of CM10.1, which you can get for yourself here. Doing this updated my recovery again. It went from CWM 5 to TWRP 2 (I believe it was 2.6.0.0).
4) I flashed a CM10.2 build for the bravo from quarx2k, which I got from here. This updated my recovery YET AGAIN, to TWRP 2.6.3.0.
5) From here, I was able to flash the update-recvery.zip that is mentioned in the CM11 topic. I don't think this was necessary, because when I then booted into recovery again after flashing the update-recovery.zip, the version number for TWRP still read 2.6.3.0, the exact same as last time. But I just did it anyway to be safe. Here is a direct download link to the update-recovery ZIP mentioned on quarx's CM11 thread.
6) FINALLY, I flash the CM11 nightly zip from quarx2k's website. I get an error, but this time it's not a status 0 error, this tells me that the ZIP is not compatible with my device.
7) I give myself a facepalm, and take 3 deep breaths. "All hope is lost..." I think to myself.
7.5) A GOOGLE SEARCH TELLS ME THAT ALL HOPE IS NOT LOST!!! (that's supposed to signal you to keep reading)
8) Turns out, there is a way to disable the device compatibility check. So what I did was copy the CM11 zip to my pc, and unzip all of its contents. I go to META-INF\com\google\android\, and add a .txt ending to the "updater-script" file, which allows me to open it with Notepad++. It is possible to edit this with plain old Notepad in Windows, but it doesn't format the code very neatly like Notepad++ does. If you open the file in Notepad and Notepad++ and compare them you will see what I mean. Anyway, the line of code that reads...
assert(getprop("ro.product.device") == "mb520" || getprop("ro.build.product") == "mb520" || abort("This package is for \"mb520\" devices; this is a \"" + getprop("ro.product.device") + "\"."); (ignore that winking face in the line of code, that is supposed to be a "; )" but without the space between them.)
... was the one I deleted from the updater-script file. This should be the first line of code. I save, exit Notepad++, and remove the .txt ending from the updater-script so that it returns to an unknown filetype. Now, I take the META-INF, system, and file_contexts files that came from the original CM11 ROM zip and I create a NEW ZIP with all of the NEW files and folders.
9) I reboot to TWRP with the ROM zip copied to my phone's SD card, and I flash the new, fixed ROM zip. "Installation completed."
10) My Bravo is rebooted, it boots up, and i get a "Welcome!" bubble in my brand-new homescreen in KitKat
11) I nearly cried. Seriously.
So looking back I think it was really the recovery that was the issue for the Status 0 problem, and the only real way to update the recovery and solve the Status 0 problem is by flashing all these ROMs in the order I mentioned, but that's as far as I know, there may be a better and quicker way to do this that I just don't know about.
So basically this thread turned into a how-to. I wanted to post the instructions here because on the CM11-for-the-Defy-and-Bravo topic did NOT have any instructions whatsoever for flashing the Bravo CM11 build on the Bravo. If anyone has questions about what I wrote, then you can certainly post them below and I'll respond to them as soon as I can, and I'll answer them to the best of my abilities.

Thanks for the Guide
I just wanted to thank you for this well-written, step-by-step guide. I haven't tried it since I'm a beginner and need some more reading to do. I'm glad you overcame those issues, though.
Anyway, I wanted to ask you how smooth it ran and if it was worth it. Also I'm starting with Android 2.1, would that make a difference?

Gastnow said:
I just wanted to thank you for this well-written, step-by-step guide. I haven't tried it since I'm a beginner and need some more reading to do. I'm glad you overcame those issues, though.
Anyway, I wanted to ask you how smooth it ran and if it was worth it. Also I'm starting with Android 2.1, would that make a difference?
Click to expand...
Click to collapse
I think you should upgrade to 2.2.1 to make sure the one-click tool works with it because I do not know if the one click root and recovery works with 2.1. Upgrade to 2.2.1 just to be safe.
Sent from my SAMSUNG-SGH-I847

Thanks for the guide
Appreciate the work. What gapps are you using.

Doesn't have much support
I tried it. A lot slower then CM7.2 and very difficult to get my most important apps working (and I don't use many).
I would not recommend it for a daily (as mentioned on the Defy link). But, has potential if a developer takes up the task.

ilikepcs said:
Appreciate the work. What gapps are you using.
Click to expand...
Click to collapse
ilikepcs said:
I tried it. A lot slower then CM7.2 and very difficult to get my most important apps working (and I don't use many).
I would not recommend it for a daily (as mentioned on the Defy link). But, has potential if a developer takes up the task.
Click to expand...
Click to collapse
The gapps for this KitKat ROM can be found here. This came from the 4.4 thread:
QUARX2K'S KITKAT GAPPS
I used this as a daily driver for a little bit, until an update (I believe was from April 10th) with the Android 3.0 kernel broke the Camera. Whenever you would try to open the camera it would say "Can't connect to Camera". I'm not sure if this issue was fixed since then, and I know the versions before this had the 2.x kernel which was fine with the camera. I lent my Bravo to a family member because their phone broke, so I can't really do anything with the phone because it is not in my possession.
Anyway, check back at this thread and the link that it gives to the Bravo version of 4.4 to keep up with the latest version. This thread does not give a change log for the BRAVO version, but I assume that it's basically the same as the main version that the majority of the thread is talking about:
ANDROID KITKAT FOR DEFY AND DEFY PLUS (ALSO FOR THE MOTOROLA BRAVO)

Help please
The procedure to install cm11 after October 1 is the same? Or did it change? @jasonmerc
Quarx on their website does not mention cm10 and cm10.1
Sent from my mb520 using XDA Free mobile app

@jasonmerc
You are not using CM11 anymore? Do you know if the camera problem has been solved (I assume that with the 2.6.x kernel the original motorola camera drivers were used which most likely do not work with a 3.x kernel)? What was your general experience (especially regarding performance) with CM11 on the Bravo?
Thanks,
Markus

oldschool63 said:
@jasonmerc
You are not using CM11 anymore? Do you know if the camera problem has been solved (I assume that with the 2.6.x kernel the original motorola camera drivers were used which most likely do not work with a 3.x kernel)? What was your general experience (especially regarding performance) with CM11 on the Bravo?
Thanks,
Markus
Click to expand...
Click to collapse
Its been forever since I've used my Bravo let alone CM11. From what I can remember the new CM11 was EXTREMELY FAST compared to other ROMs. The only issue was the camera.
Sent from my LG-D415 using XDA Free mobile app

can you create a backup of it because some of the downloads don't work i got cm 9 4.0.4 im 12 and i ran into
a problem on cm 10.1 i cannot download it or flash it thx

[Q&A] [Rom & Kernel] [4.4.4] Freak-Slim (GCC 4.8 & 4.9, JustArchi Optimazition)

[Q&A] [Rom & Kernel] [4.4.4] Freak-Slim (GCC 4.8 & 4.9, JustArchi Optimazition)
Q&A for [Rom & Kernel] [4.4.4] Freak-Slim (GCC 4.8 & 4.9, JustArchi Optimazition)
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 & Kernel] [4.4.4] Freak-Slim (GCC 4.8 & 4.9, JustArchi Optimazition). 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!

Awesome Rom
But would like to see cm theme engine integration

What are the steps to get F2FS and this ROM running? I'm currently running stock everything (stock lollipop, stock bootloader and stock kernel).
Is this guide still relevant and can I just follow it but use your rom instead? Also do I need to flash a F2FS supported kernel as well, or is the kernel already in your ROM?
Thank you for your help and great work!

LucidElectron said:
What are the steps to get F2FS and this ROM running? I'm currently running stock everything (stock lollipop, stock bootloader and stock kernel).
Is this guide still relevant and can I just follow it but use your rom instead? Also do I need to flash a F2FS supported kernel as well, or is the kernel already in your ROM?
Thank you for your help and great work!
Click to expand...
Click to collapse
Just install the latest twrp and go to wipe, then select data, cache and system and Format then to f2fs.A f2fs kernel is already include

Could you add support for syncing the Calendar?
Other than that this ROM is awesome! My N7 was barely usable and now with F2FS and this ROM it's really smooth again!

It should work he add it back in the last build

Quick question, I've experienced this with this and a few other lp Roms. Can't duplicate on purpose just happens sometimes. I'll get doing something either browsing, viewing the forums in Tapatalk, twitter, game, nothing specific. But the system freezes. Only way out is to power reboot.
Everything is a clean install.
Sent from my LG-LS980 using Tapatalk

hsv_forever said:
It should work he add it back in the last build
Click to expand...
Click to collapse
I am using the latest build but it doesn't work for me. I don't even have Calendar in Settings -> Accounts -> Google -> *Mail address*. I have sync for Chrome, Contacts, Gmail and People details. Calendar should be there as well but it's not. I do believe this is a problem in the ROM since it works on my other Android devices.

Amazing fast ROM
Amazing !!! I did not want an official stock ROM from Google pace, but after reading and seeing videos with F2FS I tried it and do not regret it. Just great. Alpha version surprisingly no bugs. I support a further and test together with a classmate who has the same tablet.
Tablet is much faster. When Times music player plus firefox and something else, so he does not lag like 2-5 seconds before, up to 0.5s pauses the music and not so much.
But I had some questions about the initial problems.
What works - information for others:
Battery Percent Enabler for 4+ android
Battery Percentage from edavid93
Battery Percent for KitKat / L from kroegerama
Nexus Battery Percent Enabler from Artit Kiuwilai
I flash ROM as follows from ubuntu 14.04 with fastboot and TWRP 2.8.2.
Boot into new TWRP and I chose option for format /system, /data and /cache to f2fs:
wipe -> advaced wipe -> chose gradually system, cache and data -> repair or change file system -> change file system -> f2fs
I go home screen in TWRP and flash SlimLp (Slim-grouper-5.0.alpha.0.4-F2FS-20141126-1947.zip), gaps (pa_gapps-micro-5.0-ALPHA1-20141117a-signed.zip) and supersu (to test the ROM as a clean new installation of all, version 2.36, today update to 2.37 via TWRP).
Well, this worked great. The problem occurred when updating.
I download Slim-grouper-5.0.alpha.0.5-UNOFFICIAL-20141130-1042.zip
According to the instructions, we did wipe /system via TWRP and flash zip.
After boot all gaps crashed and supersu missed (Logically, it was installed in /system). I repaired flash actual SLimLp ROM, gaps and supersu at once.
Then they walked on again, it was only needed once again set a backup gmail account, apply privacy google play and gmail app.
Finally questions:
This will do after every update, or you can now use the System Update option in the setup? Or I'll have to update every time you do a wipe / system and then to flash SlimLP, gaps and Super su?
Is there a way to format the internal memory to F2FS?
Do not plan to include the option percent chance the battery as this allows the applications listed above?
What is the difference between alpha versions 0.4 and 0.5? UNOFFICIAL, what? I suppose that ended 0.4 development stage and is more or less stable.
Some detailed information about the plans for alterations to clean AOSP?
And the last question, which is off topic.
Nexus 5: In stock ROM option is missing in the list of close all applications. It is not the possibility of somehow turn to stock ROM on some google nexus with loplipop.

I can not get this Rom to work good for the life of me. I flash the rom then lp gapps, boot up and have no root. Boot into recovery and flash the super su zip, when I boot back in no apps will open and I can't download from the market, plus i still have no root. I need this Rom because stock lp is terrible on my device, almost un usable. Any suggestions? Using nexus 7 2012
.=(.stryker.originals.)=.

sTl2yk3l2 said:
I can not get this Rom to work good for the life of me. I flash the rom then lp gapps, boot up and have no root. Boot into recovery and flash the super su zip, when I boot back in no apps will open and I can't download from the market, plus i still have no root. I need this Rom because stock lp is terrible on my device, almost un usable. Any suggestions? Using nexus 7 2012
.=(.stryker.originals.)=.
Click to expand...
Click to collapse
Try to process what I've tried in the post above.
I flash ROM as follows from ubuntu 14.04 with fastboot and TWRP 2.8.2.
Boot into new TWRP and I chose option for format /system, /data and /cache to f2fs:
wipe -> advaced wipe -> chose gradually system, cache and data -> repair or change file system -> change file system -> f2fs
I go home screen in TWRP and flash SlimLp (Slim-grouper-5.0.alpha.0.4-F2FS-20141126-1947.zip), gaps (pa_gapps-micro-5.0-ALPHA1-20141117a-signed.zip) and supersu (to test the ROM as a clean new installation of all, version 2.36, today update to 2.37 via TWRP).
.
Click to expand...
Click to collapse
Or in stock ROM (/data, /system and /cache format to ext4 and TRIM only use in ext4, no F2FS) use TRIM (request root)
From any terminal:
Code:
su
fstrim -v /system
fstrim -v /data
fstrim -v /cache
or use app Lag Fixer (ROOT) from SimoneDev at google play

matlala said:
Try to process what I've tried in the post above.
Or in stock ROM (/data, /system and /cache format to ext4 and TRIM only use in ext4, no F2FS) use TRIM (request root)
From any terminal:
Code:
su
fstrim -v /system
fstrim -v /data
fstrim -v /cache
or use app Lag Fixer (ROOT) from SimoneDev at google play
Click to expand...
Click to collapse
I finally got things to work. I re downloaded the rom and lp gapps, and the most recent super su zip. Problem was I was using an outdated supersu. Zip. Now my tablet is running now like it should be running on stock. Like I said stock lp is terrible on the 2012 nexus 7, I bet gingerbread would work better haha.
.=(.stryker.originals.)=.

sTl2yk3l2 said:
I finally got things to work. I re downloaded the rom and lp gapps, and the most recent super su zip. Problem was I was using an outdated supersu. Zip. Now my tablet is running now like it should be running on stock. Like I said stock lp is terrible on the 2012 nexus 7, I bet gingerbread would work better haha.
.=(.stryker.originals.)=.
Click to expand...
Click to collapse
Factory image lollipop used as all ROM from Google ext4 and it is slow on this tablet.
SSD also have problems.
Just watch the main difference is that F2FS soon as you used to write random empty cells, not those to TRIM. Conversely ext4 to be ignored and writes gradually into the cells where there have been TRIM.
When complete filling of memory may occur again slowing down as if it ran on ext4.
LS: Lollipop needs supers 2.35+. And stock rom rooted own via CF autoroot that patched and boot section. Slim ROM already has a different kernel and this treatment, so you just have to flash the zip SuperSu.

installed this last night with F2FS.
holy **** it's fast. thanks so much!

Thanks
Thanks for your excellent work.
I sent you grant $ 2 and perhaps even sent it, but I'm just a poor student.
Otherwise also, I wonder whether today's alpha 7 will be on 5.0.1, although for grouper is not yet opficiálne factory image or source codes.

matlala said:
Thanks for your excellent work.
I sent you grant $ 2 and perhaps even sent it, but I'm just a poor student.
Otherwise also, I wonder whether today's alpha 7 will be on 5.0.1, although for grouper is not yet opficiálne factory image or source codes.
Click to expand...
Click to collapse
I never though I will get any donation so I am happy about every single donation.
Thank you [emoji4]
New build will be based on 5.0.1

freak_97 said:
I never though I will get any donation so I am happy about every single donation.
Thank you [emoji4]
New build will be based on 5.0.1
Click to expand...
Click to collapse
Wow, I look forward to a small child

freak_97 said:
I never though I will get any donation so I am happy about every single donation.
Thank you [emoji4]
New build will be based on 5.0.1
Click to expand...
Click to collapse
I've flashed this rom yesterday and I'm impressed! Thank you very much for your effort.
I just can't remove the location icon from the status bar (I read it's a lollipop bug, doesn't really bother) and can't install Google search (I haven't tried the solution someone posted in the original thread, though it seems to work).
Will I have to wipe everything in order to flash the new build?
One noob question, as I'm new when it comes to flashing my nexus: once I change to f2fs I don't have to repeat the process again if I want to change rom, right? (I'm not really planning on doing so as I'm so happy with my device right now).
Thanks again, keep it up!

AOSP browser
And what AOSP browser? Can I use a GAPS L which is contained? When you install it manually from 4.4.4 does not work.

Google Search now installs - no more Error 505
I was about to use the method mentioned of replacing lib files to get Google search to install, then I just tried the latest APK that came out 12/3/14. It works with no issues!
---------- Post added at 05:33 PM ---------- Previous post was at 05:14 PM ----------
I was about to use the method mentioned of replacing lib files to get Google search to install, then I just tried the latest APK that came out 12/3/14. It works with no issues!

[Help] I can't root or install cm

Hi.
I bought the nvidia shield android tv pro (500GB model). the built-in OS is... well you probably know it`s bad...
so I installed the custom rom from here http://forum.xda-developers.com/android/development/rom-t3138575
the custom rom works fine and I just wanted to install cm and supersu. however, when I boot TWRP (2.8.6.0) and try to install, it fails (can`t mount storage).
I tried it a few times and couldn't get it to work.
the only solution I can think of is installing TWRP (instead of just booting to it). should I do that? I thought it`s best to keep the original recovery.
Thanks!
Images attached.

I'm not an expert, but I had trouble rooting too. With my 16 GB model I had to manually mount the relevant partitions in TWRP (fill in the checkboxes in "Mount") before I flashed SuperSU. Also, it appears that you're using teletype's TWRP? I think that's for the 16 GB model only. Make sure you're using Steel01's latest version here: http://forum.xda-developers.com/and...very-twrp-2-8-6-0-shield-tv-variants-t3140926
Also, what do you mean by "install cm"? Because there's not yet any working build of CyanogenMod that I know of for this device.

BenjiHansell said:
I'm not an expert, but I had trouble rooting too. With my 16 GB model I had to manually mount the relevant partitions in TWRP (fill in the checkboxes in "Mount") before I flashed SuperSU. Also, it appears that you're using teletype's TWRP? I think that's for the 16 GB model only. Make sure you're using Steel01's latest version here: http://forum.xda-developers.com/and...very-twrp-2-8-6-0-shield-tv-variants-t3140926
Also, what do you mean by "install cm"? Because there's not yet any working build of CyanogenMod that I know of for this device.
Click to expand...
Click to collapse
I tried manualy mounting... it doesn't mark the checkbox, only logs 'can`t mount /...' .
I used the TWRP posted in this forum (all varients) - the same one you sent.
by "install cm" I meant "install google`s stuff":
Gapps for CM 12.1 arm64 version: http://wiki.cyanogenmod.org/w/Google_Apps
(from here http://forum.xda-developers.com/android/development/rom-t3138575)
basicaly I don't have to root. it's just a bonus. however, I do HAVE to install somehow google`s apps (mainly the play store). how do I do that?

i installed the default supersu that come with the twrp and the update supersu trough the play store and issues was fixed, it was the easier thing to do, goo luck

aniel300 said:
i installed the default supersu that come with the twrp and the update supersu trough the play store and issues was fixed, it was the easier thing to do, goo luck
Click to expand...
Click to collapse
how do I do that? and I don't have a play store, I installed that custom rom.

ohh im sorry i did not read your post but you should ask the developer of the rom and/or install latest trwp available, best luck

Problems installing Gapps on GSI Roms

So currently I'm running AOSP Extended V6 on my 002. The rom itself runs great BUT I can't get Gapps to stick. Unlocked bootloader with TWRP 3.1.0. After I resize system Gapps will install and say Successful but when I clear cache and reboot I have no nothing installed. I'm new to this device so be easy if i'm missing something obvious.
EDIT: I've tried multiple version of Gapps from a few different places.

I have yet to have any GSI rom work, so I stopped trying and just ran a debloat script I wrote

It's weird how hit and miss GSI is on the exact same model. I may end up reverting back to stock and unlock/root and use your script and then just call it a day if I can't figure this out. I SO wanted AOSP Ext to work but kinda useless to me without Gapps.

razredge said:
It's weird how hit and miss GSI is on the exact same model. I may end up reverting back to stock and unlock/root and use your script and then just call it a day if I can't figure this out. I SO wanted AOSP Ext to work but kinda useless to me without Gapps.
Click to expand...
Click to collapse
I honestly even uninstalled gapps on my 10 inch because its one purpose is gonna be an in-car OBD II monitoring tablet with Torque Pro for my car.
GSI roms are so strange. I have 3 G7 Play's. 2 of them took the same GSI just fine, then the third just bricked and boot looped. I had to change the boot animation in TWRP to get it to boot. Even then, camera and bluetooth didn't work, but the other 2 were 100% functional. Reflashed quite a few times

razredge said:
It's weird how hit and miss GSI is on the exact same model. I may end up reverting back to stock and unlock/root and use your script and then just call it a day if I can't figure this out. I SO wanted AOSP Ext to work but kinda useless to me without Gapps.
Click to expand...
Click to collapse
I believe the hit and miss comes from the gsi's being developed on specific devices by different developers. They are supposed to work on any project treble enabled devices but it's just not so. This is just my thought from trying almost all available and a lot of time reading. The whole idea has slowly began a full circle movement to custom gsi's. The oxymoron of that last sentence kind of sums it up from my experience. Custom generics are what are being produced for the most part. If one looks at the different maintainers threads they will see what device it is supposed to work on. A.O.S.P should work a little better than most and the builds I have tried from ci.android.com have worked really well. Personally didn't see much point in the stock android gsi over debloated stock in this case. Much simpler to maintain device integrity by debloating the very few unwanted apps. All that said I am still running Beast ROM as I actually like it, the only issue I know of is device theme(takes forever+know-how) and I don't use gapps. So it works great on my tablet and I am not sure what options I will have in the future. All the changes have me sitting with a tablet that if flashed back to stock will not take ota's and a serial# of 0123456789ABCDEF. Happy Modding.
Don't know if you've seen them but there are a couple gsi's that have gapps installed with no other options, can't remember which they were, but may work better.

I appreciate the info and insight you always give. My 002 I actually went back to stock and just rooted and debloated it. I wanted it to be stable since it's my couch tablet lol. I picked up a 007 on Black Friday just for the hell of it. I'm gonna play with it and experience some different roms. BTW, they changed the model numbers on them. It's not with me right now but the model number is all numbers now. Looks more like the serial number.
Sent from my Pixel 2 using Tapatalk

razredge said:
I appreciate the info and insight you always give. My 002 I actually went back to stock and just rooted and debloated it. I wanted it to be stable since it's my couch tablet lol. I picked up a 007 on Black Friday just for the hell of it. I'm gonna play with it and experience some different roms. BTW, they changed the model numbers on them. It's not with me right now but the model number is all numbers now. Looks more like the serial number.
Click to expand...
Click to collapse
The model number I remember for the 8" was ONA19TB002 and 10" was ONA19TB003 and 007 was kboard model. Did they change to something other than that ? I remember a different number when looking at fccid page but it seemed shorter. When it's nearby give update if you don't mind, I'm curious it may help in search for firmware.

The new model number is 100005209. I took the back off of the new one and my old one and they are identical with the same part numbers. They're also all branded Surf now.
Sent from my Pixel 2 using Tapatalk

I am venturing to flash ohh aosp -10 v107.
Needed to flash the vanilla version, because the gapps version was too big.
All I get is stuck at the onn splash screen.
Do I need to flash anything to vbmeta to get this to boot a gsi?
Update:
Self test result
Yes. Even after unlocking bootloader, still need to flash vbmeta with --disable-verification before you can boot gsi.
Then there is a setprop that is needed to get the gsi to boot
While device is stuck on the"Android" logo bootanimation from aosp. Enter commands into ad shell.
Code:
adb shell setprop debug.stagefright.ccodec 0
This will get tablet to boot. But the setprop (which should become persistent) does not remain after a reboot. So the line needs to be added to the boot script built into phh gsi. "rw-sysyem.sh"
Code:
adb shell
su
mount -o rw,remount /
echo "setprop debug.stagefright.ccodec 0" >> /system/bin/rw-system.sh
These steps worked for me. And should work for you. But as with any modifications to your device , by you , are your responsibility to confirm are done correctly.

The main problem I've been having has not been with the ROM itself. I had a few vanillas that after resizing and installing GAPPS the actual apps don't show up. I'd go back into TWRP and reflash the GAPPS and it would respond with a success after seeing all the apps install but after a reboot none was there.

razredge said:
The main problem I've been having has not been with the ROM itself. I had a few vanillas that after resizing and installing GAPPS the actual apps don't show up. I'd go back into TWRP and reflash the GAPPS and it would respond with a success after seeing all the apps install but after a reboot none was there.
Click to expand...
Click to collapse
I just had that with gapps install I was trying. And in recovery after the gapps flash, before reboot I looked around with twrp file manager. I see all the apps installed. But they are not in the correct location.
They are getting installed in the /system-root/app folder rather than the /system-root/system/app folder.
I don't know the fix yet. I mentioned it in the twrp thread and diplomatic has said he does not know why it didn't go as it was supposed to .

mrmazak said:
I just had that with gapps install I was trying. And in recovery after the gapps flash, before reboot I looked around with twrp file manager. I see all the apps installed. But they are not in the correct location.
They are getting installed in the /system-root/app folder rather than the /system-root/system/app folder.
I don't know the fix yet. I mentioned it in the twrp thread and diplomatic has said he does not know why it didn't go as it was supposed to .
Click to expand...
Click to collapse
Interesting.... I'll have to keep an eye on that. I didn't even pay attention where they installed to. Thanks for the heads up!

mrmazak said:
I just had that with gapps install I was trying. And in recovery after the gapps flash, before reboot I looked around with twrp file manager. I see all the apps installed. But they are not in the correct location.
They are getting installed in the /system-root/app folder rather than the /system-root/system/app folder.
I don't know the fix yet. I mentioned it in the twrp thread and diplomatic has said he does not know why it didn't go as it was supposed to .
Click to expand...
Click to collapse
Are you sure that is not correct? Because I just checked on my Onn 8 with the stock rom and they are in /system/app/.
There system privileged apps in: /system/priv-app. Updates are in /data/app, I believe.

Has anyone had success in installing opengapps on one of these tablets? Also, has anyone tried installing it with System mounted in TWRP? Even if it doesn't work in TWRP, I believe the install script supports running on Android too.

How has anyone been able to flash a gsi. Ive even tried disabling avb but cant get it to boot. After reboot twrp dosent even recognize an os installed
Sent from my SM-G975U1 using XDA Labs

diplomatic said:
Has anyone had success in installing opengapps on one of these tablets? Also, has anyone tried installing it with System mounted in TWRP? Even if it doesn't work in TWRP, I believe the install script supports running on Android too.
Click to expand...
Click to collapse
I haven't so far. I'll try with mounting system and post the results.

razredge said:
I haven't so far. I'll try with mounting system and post the results.
Click to expand...
Click to collapse
Fast forward 20 days... any progress?

diplomatic said:
Fast forward 20 days... any progress?
Click to expand...
Click to collapse
Woops.... No it still doesn't work. Actually it made one of my 8's bootloop after.

I found this solution in another thread:
- Format data partition and reboot recovery.
- Open terminal in twrp without system, data, and cache mounted.
- Enter the following commands:
e2fsck -y /dev/block/by-name/system
e2fsck -f /dev/block/by-name/system
resize2fs /dev/block/by-name/system
- Then reboot twrp
- Flash system img reboot recovery
- After that flash pico gapps without system mounted
Thats how i was able to successfully flash gapps on aosp phh 10. You may need to try a couple times but it should work.
Sent from my SM-G975U1 using XDA Labs

jwarrior319 said:
I found this solution in another thread:
- Format data partition and reboot recovery.
- Open terminal in twrp without system, data, and cache mounted.
- Enter the following commands:
e2fsck -y /dev/block/by-name/system
e2fsck -f /dev/block/by-name/system
resize2fs /dev/block/by-name/system
- Then reboot twrp
- Flash system img reboot recovery
- After that flash pico gapps without system mounted
Thats how i was able to successfully flash gapps on aosp phh 10. You may need to try a couple times but it should work.
Click to expand...
Click to collapse
So you got phh 10 to boot? How does it run any major bugs? Thanks