Related
Just flashed my tf700 with CROMIX and it has made it into a new device. I've now started looking at my TF101 as well. It had pretty much ground to a halt, but I did a reset and it is now running as it was when new (running last stock asus rom). My TF700 was pretty much unusable so the new rom was a no brainer, but the tf101 is working fine, so not sure of the benefits?
Is it worth putting a rom like Katkis (4.3 or 4.4) on? What benefits/downsides will I see? Thanks in advance
In a word, Yes. Very much worth it.
KatKiss gives the TF101 a new lease of life, Im running KitKat 4.4.2 KatKiss #17 and it is a flying machine
I don't use my TF101 much at all, it only comes out when on holiday or ocassional lazy day at home. You don't exactly need a speed demon for music, movies, mahjong, book reading, email or web browsing.
That old saying of - "if it ain't broke don't fix it". But whilst I don't NEED the latest and greatest, the geek in me WANTS to stay at least semi up to date.
There are some dedicated and clever devs out there and I've been happily using KitKiss for just over a year.
Downsides? None that i can think of.
Benefits? A warm fuzzy feeling you've just put fresh life to an old forgotten child that was once your pride and joy.
Absolutely - Revolution HD 3.6 is a stable, fast albiet older 4.0.03ROM that performs excellently on the TF101. Y
Sent from my Transformer TF101 using XDA Premium HD app
gersen416 said:
Absolutely - Revolution HD 3.6 is a stable, fast albiet older 4.0.03ROM that performs excellently on the TF101. Y
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
You should try KatKiss, you'll not know what hit your TF if you're still rocking an ancient ICS ROM
I used megatron, revolution, eos, kk 4.2, 4.3 and 4.4
If you want lots of features/customization go with 4.2 as it has loads of that.
KK 4.3.1 is better than 4.2 IMO but has fewer customization and features.
KK 4.4.2 is the fastest of the three but lacks some customization because it's new.
It also lacks the Tablet UI (only Phatlet UI) that google ditched (I don't care cause I switched to Phablet long ago).
Thanks all for advice. I took the plunge and went with kk 4.4. It ran well, bug i had issues with sd card mounting (now fixed in r18) and also had wifi issues with the connection dropping out. I have now gone to kk 4.3 and am seeing how that runs. Have to say that it is very much a learning experience as previous versions of android have always been asus, even cromix is based on asus core. Never really sure if something is missing, asus specific or has been dropped by google (ie disk mounted icon in. status bar isn't in kk4.3, but is on cromix 4.3).
I will certainly persist to see what happens.
KatKiss 4.2.2 #226 is probably the most stable bug free version so far imo if you're looking for stability over new features, very fast and smooth, I don't remember having any issues with that ROM at all, and it comes with the Tablet UI option
Thanks Detection - I did just that. Got KK 4.4 running and after a few startup issues it seems to be working well. Will try a few other versions. Appreciate the recommendation.
tempted...
I'm on EOS 4.2.2 (whatever is in my sig I think) and it's been working really really well. I'm hesitant to try KK4.4 as things have never been better. I'll hold on a little longer until I feel that desire to tweak is too much to overcome.
If anyone has thoughts to persuade me, I'd like to hear it.
Cool! I was just going to ask for this myself after seeing there's not much activity on the TF101 branch for CM. Trying KatKiss now
Well if you are feeling adventurous, you could install Linux on it and transform it into a fully capable computer instead of just an Android tablet. Currently there is the rootbind kernel that allows you to dual boot
twrp 5.6 from play store
Hi all, (pardon my grammar, i am from the netherlands, aka Holland)
newbie here with tablet flashing.
I have been reading to long and thus to much i guess youtube showed a lot to, to people allready having a base on these things...
So i see many trees, so many, that i can not see the forrest through them.
I downloaded twrp form google play, thats not 2.6, but 5.6 (and called 'manager' this is not the same as the 2.6 version, thats not 'manager'?)
or so
Also i got goomanger , goo.im ? sounds like that.
Dragged (from windows) the downloaded KatKiss-4.4.2_019.zip and gapp something something
in to the root of allready rooted tf101 (that i learned and did in i guess 30 minutes)
started the app : twrp > install > the zip file... nothing. Stop, reboot, still on stock 4.0.3
goomanager, install rom, then appears direct the message "no goomanager folder", seeking for that i did not find where or how the goo manager should be or made, or named.
Also, and logical, much is dated in early 2012 for the asus transformer tf101. So broken links, other tool versions, time alwayss advances.
To bad, not many advanced 'end users' will get to a good start anywhere, all i found was texts from people with to much experience.
To make it short and simple, things like Starting how to's with : flash so you have root. Then download rom X, and flash it with (you name it) and oh yeah, set debugging ON."
I hope someone can direct me to a how to, with step 1 and many, not the ones i found, so for newbies, not for those knowing the base of these things.
I have root acces now.... yeeeee... i do not use these app's, well yes, 2 now, but they did not upgrade my tf101 to katkiss android 4.4.2..
twrp manager
all4allwin said:
Hi all, (pardon my grammar, i am from the netherlands, aka Holland)
newbie here with tablet flashing.
I have been reading to long and thus to much i guess youtube showed a lot to, to people allready having a base on these things...
So i see many trees, so many, that i can not see the forrest through them.
I downloaded twrp form google play, thats not 2.6, but 5.6 (and called 'manager' this is not the same as the 2.6 version, thats not 'manager'?)
or so
Also i got goomanger , goo.im ? sounds like that.
Dragged (from windows) the downloaded KatKiss-4.4.2_019.zip and gapp something something
in to the root of allready rooted tf101 (that i learned and did in i guess 30 minutes)
started the app : twrp > install > the zip file... nothing. Stop, reboot, still on stock 4.0.3
goomanager, install rom, then appears direct the message "no goomanager folder", seeking for that i did not find where or how the goo manager should be or made, or named.
Also, and logical, much is dated in early 2012 for the asus transformer tf101. So broken links, other tool versions, time alwayss advances.
To bad, not many advanced 'end users' will get to a good start anywhere, all i found was texts from people with to much experience.
To make it short and simple, things like Starting how to's with : flash so you have root. Then download rom X, and flash it with (you name it) and oh yeah, set debugging ON."
I hope someone can direct me to a how to, with step 1 and many, not the ones i found, so for newbies, not for those knowing the base of these things.
I have root acces now.... yeeeee... i do not use these app's, well yes, 2 now, but they did not upgrade my tf101 to katkiss android 4.4.2..
Click to expand...
Click to collapse
Hi, Twrp manager from playstore is a "manager" for TWRP Recovery using openrecoveryscript. Don't use it to flash katkiss android 4.4.2 coming form ICS 4.03 stock.
At fisrt you have to flash the TWRP Recovery. You can flash it with easyflasher or goomanager (if you're root) : Open GooManager > 3 dots menu button top right > "Install OpenRecoveryScript".
Once you have successfully flashed TWRP, you can flash any ROM you like from TWRP Recovery by booting into recovery
(Volume Down & Power until white text appears at the top of the screen, then release buttons and press volume up once)
Copy the ROM & Gapps to your extrenal SDCard
boot into recovery and, go to advanced wipe, wipe SYSTEM, CACHE & DALVIK CACHE, DATA, INTERNAL STORAGE (not external storage wich is SD card)
Go to the INSTALL menu and find your KatKiss ROM & Gapps (on your external sorage)
Flash ROM
Flash Gapps
WIPE menu and wipe only CACHE & DALVIK CACHE
reboot, You should be booting into Kat Kiss now. Enjoy
jh1969 said:
Hi, Twrp manager from playstore is a "manager" for TWRP Recovery using openrecoveryscript. Don't use it to flash katkiss android 4.4.2 coming form ICS 4.03 stock.
At fisrt you have to flash the TWRP Recovery. You can flash it with easyflasher or goomanager (if you're root) : Open GooManager > 3 dots menu button top right > "Install OpenRecoveryScript".
Once you have successfully flashed TWRP, you can flash any ROM you like from TWRP Recovery by booting into recovery
(Volume Down & Power until white text appears at the top of the screen, then release buttons and press volume up once)
Copy the ROM & Gapps to your extrenal SDCard
boot into recovery and, go to advanced wipe, wipe SYSTEM, CACHE & DALVIK CACHE, DATA, INTERNAL STORAGE (not external storage wich is SD card)
Go to the INSTALL menu and find your KatKiss ROM & Gapps (on your external sorage)
Flash ROM
Flash Gapps
WIPE menu and wipe only CACHE & DALVIK CACHE
reboot, You should be booting into Kat Kiss now. Enjoy
Click to expand...
Click to collapse
Wow, thanx for the walk through, i guess i will, if katkiss works, pay you a token of apreciation via PayPal.(if you have that)
Another question, since i do not have a small sd or 'normal size' sd card above 512 MB (and how formatted, fat? ntfs...?) can it be done by wired pc connection?
I have got the win 8 pc seeing the tf101's 'internal onboard sd memory' and offcourse on this pc the mentioned rom's.
all4allwin said:
Wow, thanx for the walk through, i guess i will, if katkiss works, pay you a token of apreciation via PayPal.(if you have that)
Another question, since i do not have a small sd or 'normal size' sd card above 512 MB (and how formatted, fat? ntfs...?) can it be done by wired pc connection?
I have got the win 8 pc seeing the tf101's 'internal onboard sd memory' and offcourse on this pc the mentioned rom's.
Click to expand...
Click to collapse
Hi, for sd card format to fat32,
If you don't have any sd card you can flash rom from tf101 internal storage, from windows copy kk rom & gapps to tf101 internal storage
reboot on twrp & wipe all except internal storage.
Please have a look here : http://www.transformerforums.com/fo...07-rom-jb-4-3-katkiss-multi-window-tf101.html everythings are explain (the installation for 4.3 & 4.4 is the same.
Good luck
thanx !!!
jh1969 said:
Hi, for sd card format to fat32,
If you don't have any sd card you can flash rom from tf101 internal storage, from windows copy kk rom & gapps to tf101 internal storage
reboot on twrp & wipe all except internal storage.
Please have a look here : [ link cut away since i can not post if there is a link...] everythings are explain (the installation for 4.3 & 4.4 is the same.
Good luck
Click to expand...
Click to collapse
Thanx! Finally i got it working!!, because of your directions and explenation!!!
I now have a tf101, clean as a whistle, with fresh 4.4.2. android rom.
(Some things are still not ok, but that's the rom, like ehhhh pictures library, when pressed the standard app on desktop, it mostley opens and stops, sometimes it works...)
And i want to put a little amount of practical thanx there, if you have PayPal.
Private message me your PayPal email adress and i shuffle some over.
kat kitt 4.4.2. netflix and video
Hee all, a newbie here, i can not replye in the thread itself.
What came into my mind was 2 things, also needed stock after some update of android.
nvidia tegra something...
and arm7. (drivers? codecs?)
perhaps these are missing/wrong ones in 4.4.2 and thus netflix and i.e. utopiatv.nl does not work.
all4allwin said:
Thanx! Finally i got it working!!, because of your directions and explenation!!!
I now have a tf101, clean as a whistle, with fresh 4.4.2. android rom.
(Some things are still not ok, but that's the rom, like ehhhh pictures library, when pressed the standard app on desktop, it mostley opens and stops, sometimes it works...)
And i want to put a little amount of practical thanx there, if you have PayPal.
Private message me your PayPal email adress and i shuffle some over.
Click to expand...
Click to collapse
Happy for you
I'm on kk4.4 and it's wonderful, but only thing is annoying me is that I can't put accents with the dock in, I mainly write in spanish, so this is certainly a big issue.
Any tip about how to fix it, I already have the dock layout set to Spanish,so this is not the problem.
Thanks in advance!
Hi guys,
for those of us who are waiting for at least the M1 of CM12 before switching lanes, I did a build of Carbon (and a few of CM11, previously) for our Photons.
This is an odexed ("user", not "userdbg") build, running on the cm-12.1 kernel branch and using the latest available f2fs_tools. It also features a modified init which can use either f2fs or ext4 for /cache and /data - so switching to f2fs is highly recommended, but not mandatory. Superuser is included.
This is esentially for those who switched to CM12 just for f2fs; it's miles faster than cm12, and a bit more responsive that the old official cm11 nightlies.
A word of warning. TWRP's "change filesystem" function formats the partition (PhilZ does too, but at least it makes that explicit).
So what you want to do when switching from an ext4 ROM is,
before you begin: copy everything in the internal sdcard somewhere on the external sdcard; this is needed, since the "internal sdcard" is actually a folder in /data;
in TWRP, begin by creating a backup of /data (that saves everything except the "internal sdcard" and /cache - that's why you need step #1);
do the FS change for both /data and /cache
restore the /data backup, on the freshly formatted /data partition; ignore the "different filesystem" warning, it's inconsequential;
install the ROM;
once you booted the phone, copy back the old contents of the internal sdcard
You only need to do this when you change filesystems, which will be exactly once if you like my ROMs And obviously, if you don't, you have to use the exact same procedure before flashing an ext4 ROM, if you don't want to lose data.
Though, in all fairness, I'd recommend flashing this cleanly - unless you're upgrading from an ext4 Carbon build.
A note on the radio
I have included a tool called radio-tool (of my own design) that allows people to enable/disable the US GSM lock and individual network bands;
if you're having the SIM mod, and are from, or have business in, the US, you can use it to kill the CDMA and Sprint LTE bands altogether, as well as to enable US GSM bands and disable the US GSM lock;
the source code is here
Use (as superuser)
Code:
radio-tool [dbg] [{+|-}opt [...]]
where opt is one of
uslock - US GSM lockout
cdma - CDMA bands (CDMA800 / CDMA1800 / CDMA2000 1xEV-DO)
usgsm - US GSM/HSPA bands (GSM850, GSM1900, WCDMA850, WCDMA1900)
eugsm - EU GSM/HSPA bands (GSM900, GSM1800, WCDMA900, WCDMA2100)
sprlte - Sprint LTE (LTE25, 1900)
vzwlte - Verizon LTE (LTE13, 700)
Download:
ROM: CARBON-KK-UNOFFICIAL_f2fs-20150526-moto_msm8960.zip
Recoveries: TWRP-2.8.6.0-20150526-f2fs-moto_msm8960_jbbl-xt897.img, PhilZ-6.59.0-20150520-crkk_f2fs-moto_msm8960_jbbl-xt897.
You do not need to use a su app with this; but if you want to, please use the latest SuperSU. Attempting to use a different, or older, su app could result in no radio.
Changes from stock Carbon:
alternative mount points support - this enables the ROM to work with either f2fs or ext4 for /data and /cache
tuned mount settings - kickass speed with both ext4 and f2fs
256MB of lz4-compressed swap space (zram0)
built on gcc-4.8-sabermod
build.prop tweaks - this defaults to GSM/WCDMA - plus a few radio and network tweaks;
added a few goodies that are present in CM builds (Term, Apollo, Calendar, CMWallpapers, VideoEditor, plus the cmdline utils);
removed the stats and the update apps (for obvious reasons)
added Romanian (programmers) keyboard support in Asanti Keypad
built with: twrp 2.8.6.0, cm12.1 kernel, cm12.1 f2fs-tools, cm12.1 e2fsprogs, cm12.1 exfat, cm12.1 fuse.
(this will allow me to pick up any improvements in kernel, file systems, and recovery, with great ease )
Quirks:
MTP doesn't start by default in TWRP, despite the fact that it claims to be enabled; disable and re-enable MTP, and it will work
in PhilZ' mount menu, entries for cache and data are duplicated; this is cosmetic - mounting and umounting works just fine, regarless which of the two entries for each partition you choose
.
Older, CM11 vanilla builds:
Download:
cm-11-20150427-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip - repo syncs, builds with TWRP, uses branch cm-12.1 of the kernel, uses latest available f2fs-tools
Use latest SuperSU with any of the CM ROMs - older, or different, su apps might make the radio not work.
NOTE. These ROMs are actually moto_msm8960_jbbl, so they should work on all devices for which official moto_msm8960_jbbl builds did, as long as they're still on the JB bootloader (jbbl) and you have a device-specific recovery that supports f2fs. A suitable PhilZ touch for non-xt897's can be found on the AtrixHD thread, courtesy of @palmbeach05, or you could use PhilZ-6.59.0-20150506-crkk_f2fs-moto_msm8960_jbbl-mb866 (note, despite the -mb866 suffix, it should work on any moto_msm8960_jbbl device except xt897).
The current repo is available here. To use,
repo init -u https://github.com/mionica/android.git -b cr_kk_gcc-4.8
repo sync
. build/envsetup.sh
breakfast carbon_moto_msm8960_jbbl
edit the .repo/local_manifests/roomservice.xml, changing the device project for android_device_motorola_moto_msm8960_jbbl to
Code:
<project path="android" name="mionica/android_device_motorola_moto_msm8960_jbbl" remote="mionica" revision="cr_kk_xt897" />
repo sync again
finally, (cd vendor/carbon && ./get-prebuilts).
After you do that, you're good to go - (optional) configure ccache (if it's your first build), (optional) enable ccache, choosecombo, then mka carbon 2>&1 | tee BUILD.LOG.
If you're not sure how to do any of these, either just use the provided ROM, or search on youtube for "building CyanogenMod" - that should help, I know it helped me Anyway, this thread is not the right place for learning how to build Android.
Mirrored for archival purposes.
This server WILL BE SLOW. You've been warned.
http://lionspaws.net/cm-11-20150401-UNOFFICIAL_f2fs-moto_msm8960_jbbl/
98e652a97965ba5d88cb9068fe7d4dbe *cm-11-20150401-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip
Using it for the last few days, seems good so far. Thanks
taking a break
Quick one. I'll take a break from this for now - my little sister's phone broke down, so she got my Photon. I just ordered one from the States today, but between that arriving and cornholiogsm doing the SIM mod, it might take a while (US to Ireland to Czech Republic to Ireland - and Tomas is pretty busy in my experience).
Thanks much for building this!
Forgive my ignorance, I've been using CM11 a while but other than the initial installation in which I followed wiki instructions, have only ever updated thru the phone. But since there hasn't been an update in a couple months, I'm considering installing this, particularly to solve the google service problems. If it makes the phone faster with better file system and ram stuff, that's a bonus, although concerned that might cause problems in the future. I don't fully understand what you mean by messed up build and odexed user stuff means. Basically I wonder can I just install this on top of the latest CM11 nightly without issues ("dirty flash")? My "recovery" is recovery-clockwork-6.0.4.4-xt926 clock but I only used that cuz that was what the wiki said, I've never used it since the initial install.
If the answer is yes, and I understand your post right, these are the install steps:
1. Download cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip
2. Download & install TWRP-2.8.6.0-20150408-cm11_f2fs-moto_msm8960_jbbl.img
3. Change filesystem of /cache and /data to f2fs using TWRP
4. Install cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip using TWRP
You said something about flash SuperSU alongside this. I don't recall having to do that before, can you provide a little more info?
Do I need to reinstall gapps, and if so, is it the same as I used before, gapps-kk-20140606-signed.zip?
And a couple more easy questions I could probably find by searching... how do I install that twrp....img file, can I do that thru clockwork... and how do I get into clockwork anyway, I remember it was holding some volume key during power or something but last time I tried to guess weird things happened with robots getting operations and such so if you happen to know the right keys/etc that would be convenient... will twrp replace clockwork and have the same keys to get boot to it, if not, what keys?
And last but not least... when CM11 M13 finally comes out, will I be able to upgrade to that from this, or perhaps because of the stuff you've taken from CM12 (f2fs/zram/etc) maybe I can't, or maybe I can if I set the filesystem back to default with TWRP first? How bout if one day I decide to use Lollipop (which I may never do anyway as I understand it's only recommended for phones with more than 1GB memory), will I be able to upgrade to CM12 the same way as regular CM11 user? I'd always used official stuff so this unofficial is making me nervous, but I really want my google stuff working right again and my battery to last all day like it used to...
Wait what wiki told you to use CWM for xt926!? CM's wiki?
enigma9o7 said:
Thanks much for building this!
Forgive my ignorance, I've been using CM11 a while but other than the initial installation in which I followed wiki instructions, have only ever updated thru the phone. But since there hasn't been an update in a couple months, I'm considering installing this, particularly to solve the google service problems. If it makes the phone faster with better file system and ram stuff, that's a bonus, although concerned that might cause problems in the future. I don't fully understand what you mean by messed up build and odexed user stuff means. Basically I wonder can I just install this on top of the latest CM11 nightly without issues ("dirty flash")? My "recovery" is recovery-clockwork-6.0.4.4-xt926 clock but I only used that cuz that was what the wiki said, I've never used it since the initial install.
If the answer is yes, and I understand your post right, these are the install steps:
1. Download cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip
2. Download & install TWRP-2.8.6.0-20150408-cm11_f2fs-moto_msm8960_jbbl.img
3. Change filesystem of /cache and /data to f2fs using TWRP
4. Install cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip using TWRP
You said something about flash SuperSU alongside this. I don't recall having to do that before, can you provide a little more info?
Do I need to reinstall gapps, and if so, is it the same as I used before, gapps-kk-20140606-signed.zip?
And a couple more easy questions I could probably find by searching... how do I install that twrp....img file, can I do that thru clockwork... and how do I get into clockwork anyway, I remember it was holding some volume key during power or something but last time I tried to guess weird things happened with robots getting operations and such so if you happen to know the right keys/etc that would be convenient... will twrp replace clockwork and have the same keys to get boot to it, if not, what keys?
And last but not least... when CM11 M13 finally comes out, will I be able to upgrade to that from this, or perhaps because of the stuff you've taken from CM12 (f2fs/zram/etc) maybe I can't, or maybe I can if I set the filesystem back to default with TWRP first? How bout if one day I decide to use Lollipop (which I may never do anyway as I understand it's only recommended for phones with more than 1GB memory), will I be able to upgrade to CM12 the same way as regular CM11 user? I'd always used official stuff so this unofficial is making me nervous, but I really want my google stuff working right again and my battery to last all day like it used to...
Click to expand...
Click to collapse
I agree with @arrrghhh you should use what your device maintainers recommend you use. I would also recommend you looking at what bootloader you have before trying this as there are KKBL builds in a different thread on I believe the RHD section. Odexed is like what you get from the manufacturer. It has .apk and odex files in it. odex assist the apk files. 6.0.4.4 is outdated, as 6.0.5.1 is the most recent. The install method you just recited is exactly what the OP just said. Per the OP, SU was not built into the 4/8 ROM, so you need to flash it as well. Yes you should be able to flash that Gapps, you just have to update your Gapps after finishing setup via playstore. Lollipop is able to be used on your device, as it currently has official builds. 5.0 had issues, 5.1 just got its official release yesterday. As far as unofficial builds go, I refer you to epinter and krystianp who both took an older device and provided unofficial updates that were very stable, despite the neverending work on a custom kernel. Furthermore, you can go talk to Quarx about unofficial builds, since his builds has been running the Defy for years. So being nervous about an unofficial build is like saying you're nervous about using a generic brand of something vs the more publicized item. Battery life will always be an issue if you have a bad setup (wifi and bt on all the time, max bright screen, hrs of listening to music or streaming, etc.)
@enigma9o7 Personally, I can't wait to do an unofficial cm11 build based on the cm11 m13 code base - with f2fs, and I expect, by then, zram (if it proves useful on cm11 at all - this thing works unreasonably well to begin with ). So I wouldn't worry about m13, as I'm pretty sure to release a parallel build on its side.
Now, I'm a bit impaired re. testing equipment atm but I have a mind to keep building this weekly or so anyway, while I judge the commits to be low-risk, and resume the riskier stuff once I get the new toy. Was away from Dublin this week, hence from my home PC , but that gets fixed tonight...
mionica said:
@enigma9o7 Personally, I can't wait to do an unofficial cm11 build based on the cm11 m13 code base - with f2fs, and I expect, by then, zram (if it proves useful on cm11 at all - this thing works unreasonably well to begin with ). So I wouldn't worry about m13, as I'm pretty sure to release a parallel build on its side.
Now, I'm a bit impaired re. testing equipment atm but I have a mind to keep building this weekly or so anyway, while I judge the commits to be low-risk, and resume the riskier stuff once I get the new toy. Was away from Dublin this week, hence from my home PC , but that gets fixed tonight...
Click to expand...
Click to collapse
One question i did have that i was wondering, when you built the kernel, did you set it up for GSM, CDMA, or both? I know we've talked via pm about things, but i've gotten it to boot up with your kernel, but no signal and baseband unknown
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
One question i did have that i was wondering, when you built the kernel, did you set it up for GSM, CDMA, or both? I know we've talked via pm about things, but i've gotten it to boot up with your kernel, but no signal and baseband unknown
Click to expand...
Click to collapse
Mmm will have to check. For me it's working in the EU using GSM/HSPA on the xt897 with the SIM mod.
I used the stock config from the cm12.1 xt897 kernel - I'll have to diff that with the cm11 one.
Another possibility is that it wouldn't work because of SElinux mismatches between kernel and userland. The following has to be in the fstab:
Code:
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,nosuid,nodev,noatime,nodiratime,barrier=1,[b]context=u:object_r:radio_efs_file:s0[/b] wait,check
If it doesn't, on the xt897 you get no WiFi, but I expect results might vary by device
All I'm saying is, it might or might not be a kernel config, would have to check when I get to my PC.
mionica said:
I used the stock config from the cm12.1 xt897 kernel - I'll have to diff that with the cm11 one.
Click to expand...
Click to collapse
I reviewed the entire changelog from cm-11.0 to HEAD, and couldn't find anything that looked even remotely radio-related, so I reckon it's most likely the SElinux thing. And now that I built a TWRP that has a chance of running on AHD, I guess you could tell me whether that's the case
arrrghhh said:
Wait what wiki told you to use CWM for xt926!? CM's wiki?
Click to expand...
Click to collapse
Yep, pretty sure. All started a year ago when I was looking for an android smartphone with a keyboard, this one was rated best, wikipedia itself said CM was required for kitkat, so looked into CM, found their installation wiki http://wiki.cyanogenmod.org/w/Install_CM_for_xt897 which step #2 is install clockworkmod recovery. Right now if I follow the link it leads to recovery-clockwork-6.0.1.3-asanti.img, but I'm pretty sure at the time I originally installed it lead to that version I used, which did work fine for installing CM as I do have it installed. But it's possible something else lead me to that version, I can't really remember for 100% sure, but I definitely started from CMs wiki.
---------- Post added at 10:17 AM ---------- Previous post was at 10:04 AM ----------
palmbeach05 said:
I would also recommend you looking at what bootloader you have before trying this as there are KKBL builds in a different thread on I believe the RHD section
....
The install method you just recited is exactly what the OP just said. Per the OP, SU was not built into the 4/8 ROM, so you need to flash it as well.
...
Yes you should be able to flash that Gapps, you just have to update your Gapps after finishing setup via playstore.
...
So being nervous about an unofficial build is like saying you're nervous about using a generic brand of something vs the more publicized item.
Click to expand...
Click to collapse
Thanks. My understanding is there is no KKBL for Photon Q anyway, but anyways I've always used the msm...jbbl roms.
Okay, will add installing SU to install steps.
Since I already have that version of gapps, my question is do I need to reinstall it then update everything. Shouldn't it already be good? I didn't have to reinstall gapps with the official nightlies, so want to know if I really need to for this.
My concern with unofficial is not that I dont trust it or think it's less stable, just that it may make it more difficult in future to upgrade or get back onto official path as I may not be able to follow the same steps as everyone else.
I'm still unsure if it's okay to dirty flash over CM11 nightly. I do actually use my phone for work so don't want to mess it up... but really want google stuff working again and can't keep waiting forever for official cm11.
enigma9o7 said:
Yep, pretty sure. All started a year ago when I was looking for an android smartphone with a keyboard, this one was rated best, wikipedia itself said CM was required for kitkat, so looked into CM, found their installation wiki http://wiki.cyanogenmod.org/w/Install_CM_for_xt897 which step #2 is install clockworkmod recovery. Right now if I follow the link it leads to recovery-clockwork-6.0.1.3-asanti.img, but I'm pretty sure at the time I originally installed it lead to that version I used, which did work fine for installing CM as I do have it installed. But it's possible something else lead me to that version, I can't really remember for 100% sure, but I definitely started from CMs wiki.
---------- Post added at 10:17 AM ---------- Previous post was at 10:04 AM ----------
Thanks. My understanding is there is no KKBL for Photon Q anyway, but anyways I've always used the msm...jbbl roms.
Okay, will add installing SU to install steps.
Since I already have that version of gapps, my question is do I need to reinstall it then update everything. Shouldn't it already be good? I didn't have to reinstall gapps with the official nightlies, so want to know if I really need to for this.
My concern with unofficial is not that I dont trust it or think it's less stable, just that it may make it more difficult in future to upgrade or get back onto official path as I may not be able to follow the same steps as everyone else.
I'm still unsure if it's okay to dirty flash over CM11 nightly. I do actually use my phone for work so don't want to mess it up... but really want google stuff working again and can't keep waiting forever for official cm11.
Click to expand...
Click to collapse
Yes, you can dirty flash this ontop of an existing CM11 after switching /data and /cache from ext4 to f2fs. Gapps will be fine since they install on the /system partition.
Sent from my ATRIX HD using XDA Free mobile app
Switched to Carbon, but preserved most of the goodies from CM; links in the first post.
Also added a note on how to hack your radio to disable CDMA/LTE - so you could go with this phone in the US and never register on Sprint's network (unless they have a GSM/WCDMA network in place too, which should be fine).
I decided to give it a try with your latest CM11. I installed the TWRP from your first post, was able to backup fine, but don't see how to reformat as f2fs....
enigma9o7 said:
I decided to give it a try with your latest CM11. I installed the TWRP from your first post, was able to backup fine, but don't see how to reformat as f2fs....
Click to expand...
Click to collapse
There should be an option to wipe things, go there
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
There should be an option to wipe things, go there
Click to expand...
Click to collapse
Thanks, found it.
And now I'm stuck. But I bet it's an easy solution.
I changed filesystems, restored data & cache, installed cm (04/27), installed superuser (wasnt sure if needed, but figured it couldnt hurt), and I booted.
No wifi or phone service but I'm hoping the last step will fix that, restoring sdcard0. However, I can't figure out how to copy that back. I used ES File Explorer to copy it to a folder in sdcard1 before I started. But now I can't paste it back to /storage, always told copy fails. There is a 0 byte file called sdcard0 there, if I delete it, it comes back. Since it's not a directory I can't change to it and copy the contents of my previous save into it... I tried deleting it and making a folder called sdcard0 before it recreated the 0 byte file but that failed too.
I thought maybe I'd try command line, but I'm no expert there... I su'd and tried similar things as in EX but similar results.
I thought I'd try to copy it back with TWRPs file manager, but I couldn't figure out where to put it, there was no /storage directory, so I tried putting it in / and that started copying for a while but before it was done it rebooted and just hung at the TeamWin screen until I powered off...
So yeah. Dunno how to restore sdcard0. Help please....
edit: maybe superuser doesn't work? I tried to use default "file manager" and it wont let me switch to root mode. Then I noticed that while trying ES File Manager again I didnt see the popup about "root granted" or something like that that I normally see. But superuser is installed, its in the apps menu and runs and a quick look thru the settings seems okay to me, but I don't recall ever setting anything before.
edit2: I'm giving up and going to try to go back to last cm11 nightly and hope my phone starts working again. I tried reflashing multiple times, eventually tried supersu instead of superuser and that worked to get root explorer working, but I still couldn't copy over sdcard0 using ES anyway, but using default filemanager I could start (although I hate that filemanager cuz I dont know how to change directories, usually have to tap about 15 times before it opens a folder), but it would always start then reboot before it finished. So I still dunno how to copy that back.
enigma9o7 said:
No wifi or phone service but I'm hoping the last step will fix that, restoring sdcard0. However, I can't figure out how to copy that back. I used ES File Explorer to copy it to a folder in sdcard1 before I started. But now I can't paste it back to /storage, always told copy fails. There is a 0 byte file called sdcard0 there, if I delete it, it comes back. Since it's not a directory I can't change to it and copy the contents of my previous save into it... I tried deleting it and making a folder called sdcard0 before it recreated the 0 byte file but that failed too.
Click to expand...
Click to collapse
Superuser is probably not a smart choice on KK. Use SuperSU instead.
The very first boot is somehow handled differently - I discovered this when I worked on integrating SuperSU into a catch-all zip of mine (alongside Windows Mobile ringtones, Midnight Commander, patched hosts, and a few other goodies). I got no radio with my package, but if I flased SuperSU instead, it worked.
It took me a coupe of tries to find the culprit - a flag file in /etc that SuperSU created after the first boot (and I attempted to create that from my zip). Made my zip not create that, and bang! everything worked just fine. Btw, removing that file after the first boot had no effect, the phone'd be screwed until you wiped /data.
Now, the fact that SuperSU handles the first boot differently kinda makes me think that older su's might very well not work (properly) on KK - and what you're reporting seems to confirm that.
I would strongly suggest going Carbon instead; that includes a working su. It's essentially CM with a different boot logo and a good few extra customization options (which you can safely ignore if you're not into that sort of thing).
So if you didn't go back yet, try either
flashing carbon and being done with it, everything will work;
flash the cm rom alongside supersu, not any other root app,
Either way, root will work, phone will work, and you'll be able to copy stuff around to your heart's desire.
As for a FM, I strongly suggest an app called Total Commander. The UI is atrocious as of late (the author is obviously better at coding than designing icons ), but it' probably the most complete FM solution for Android, bar none. And it's free, without adds; wait til you try it in landscape
I'm sorry for you inconvenience, but I also somehow feel it's earned - the OP said SuperSU back before Carbon replaced CM; because that's what I was using, and it worked for me - no guarantees if you went your own way. I've re-added the limitation and made it bold+orange in the CM part of the post (Carbon has its own, fully working, su).
Added the 2015.05.03 build of Carbon; links to 2015.04.30 removed.
At this stage, CM users should have everything they liked about CM, already compiled in (except for WhisperPush, the point of which I don't quite see).
Changelog from 2015.04.30:
added Calendar (!!!) - why on earth would the Carbon guys build an ROM without this?!
built on gcc-4.8.x-sabermod-20150429
added CMWallpapers, Video Editor
added the previously-missed vim, unrar, zip and gdbserver
synced with upstream; in particular, there was a noteworthy GPU memory allocation improvement in the kernel
Todo:
add an app for messing with the NV settings (enable/disable bands, enable/disable US GSM lockdown)
enable zram.
Added the 2015.05.05 build of Carbon; links to 2015.05.03/04 removed.
Changelog from 2015.05.04:
set default governor to msm-dcvs - better out-of-box performance
imported the cm-12.1 init support (including swap enabling)
Changelog from 2015.05.03:
support for fstab alternatives, cm12-style (my own code in fs_mgr); now you can use the ROM with either f2fs or ext4 for /cache and /data
massively improved FS performance for both ext4 and f2fs - tuned the fstab settings for best performance;
added radio-tool to enable/disable US GSM lock and groups of radio bands (CDMAs, US GSM/HSPA, EU GSM/HSPA, Sprint LTE, Verizon LTE) - see spoiler in first post
Todo:
figure out why swapping doesn't want to start, despite the device being there and mkswap succeeding (error -16).
Updating the recovery to a 20150505 build is highly recommended.
This is the link to the guide for flashing cm 12.1 on our Honor 3C - H30-U10. I don't own any of these builds or fixes, i just wanted to make this thread so that these things are easily available to people who CRAVE for Cyanogenmod on their honor 3c devices like me and ask for some help regarding the installation of apks. http://www.carbontesla.com/2015/08/install-honor-3c-cyanogenmod-12-1-lollipop-custom-rom-unofficial/
this is the link to the various builds of cm 12.1 https://cloud.mail.ru/public/3SBd/vVnPaUJ4C/ , however the one which has 20150923 in its name doesn't seem to boot up after flashing so i have flashed the one with 20150309 in its name which boots up fine and works pretty well.
Flash the Gapps also for the play store and google play services to work. Here is the link for it - http://www.carbontesla.com/download-google-apps-gapps/
Now, i tried PA Gapps mini and cyanogen 12.1 Gapps but they didnt work for me but AFH Gapps did work. You guys can try the former ones as there might have been some issue at my side.
The IMEI lost problem is there which can be solved by either restoring IMEI numbers using MTK or this zip http://1drv.ms/1FNtZUj. This may not be a permanent fix and the SIM not detected error may start showing up after a reboot but, it can be fixed by re-flashing this zip at recovery OR another rather stupid looking workound XD XD by turning on the airplane mode before rebooting and then switching it off after the boot up has finished.
I couldn't find the "Select default storage option" in the storage settings nor could i find the select preferred app installation location option in the Apps settings, so i found a workaround for linking the /sdcard in the root folder to /storage/sdcard1. Here is the script for it which has to be run everytime after booting the device in the terminal emulator:
1. first gain root privileges by entering su int the terminal.
2. type: mount -o bind /storage/sdcard1 /sdcard
That's it!! Now the default storage is your external sd card, one drawback of this is that you can't access the internal storage. If you want to access it, reboot your device and everything will revert back. if you want to set the default storage to the ext sd card, follow the above steps again.
THE PROBLEM: Apparently apks dont get installed most of the times even after enabling Unknown sources in the developer options, i don't know if this is the problem of google services or something, i would like someone to help out with this issue.
EDIT 1: The one which has 20150923 in its name boots up just fine, it needs more than one time dalvik cache deletion and factory resets.
Thanks for sharing ... some upgrade or new information in the last days...
This rom has several bugs. The only one version i still prefer to use is 151129 version
The latest 151202 doesn't booting after flash. Seems there's something wrong with boot.img
Anyway, i wish the developers will keep research and improve this rom to fix the bugs
Nothing new has happened mate
internauta2000 said:
Thanks for sharing ... some upgrade or new information in the last days...
Click to expand...
Click to collapse
No new updates have been release
I'll check the builds again and report back if i find any fixes for the bugs ASAP
Thanks for notifying!
Rayquaza said:
This rom has several bugs. The only one version i still prefer to use is 151129 version
The latest 151202 doesn't booting after flash. Seems there's something wrong with boot.img
Anyway, i wish the developers will keep research and improve this rom to fix the bugs
Click to expand...
Click to collapse
could you please provide the link for these builds? these couldn't be found on cloud.ru site
CM 12.1 ROM Development:
http://forum.xda-developers.com/android/development/rom-cyanogenmod-12-1-port-huawei-honor-t3307520
Great WORK!!
kernel.killer said:
CM 12.1 ROM Development:
http://forum.xda-developers.com/android/development/rom-cyanogenmod-12-1-port-huawei-honor-t3307520
Click to expand...
Click to collapse
Your Thread is amazing! Great work @kernel.killer !! Love your work! The ROM worked perfectly on my phone after flashing the modemFix zip
These are stock-based recovery flashable ROMs I've cooked up for the Cube iWork 10 Flagship (aka iWork 10 Ultimate), device i15-T(D).
They are all based on the stock build i15-T_V1.0_20160302, kernel version 3.14.37-x86_64-L1-R429 Wed Mar 2 18:22:46 CST 2016
I have tested these on my stock i15TD purchased directly from cube-tablet.com
If you are stock, unrooted with stock recovery you will need to go here first before you can use these.
WARNING: Flash at your own risk!!!
Make a full backup before flashing!
I would recommend wiping dalvik, cache, data & system before flashing.
For the Odexed versions a factory reset (dalvik, cache & data) will probably work. You might even be able to get away with a dirty flash if you're coming from the same stock build & kernel version, let me know
OTA: Will probably not work with the Stock Odexed version (I wouldn't try it anyhow) and definitely not work with any of the others as I've removed all the OTA stuff in them.
Descriptions
Stock Odexed NoRoot 552.4 MB
-Nothing has been touched here except for changing default location/language, so it boots up in English
Stock Odexed Debloated NoRoot 484.7 MB
-Same as above except debloated
Stock Odexed Debloated Root 489.0 MB
-Same as above and rooted
Stock Deodexed Debloated Root 417.03 MB
-Fully deodexed, debloated and rooted
Stock Deodexed Debloated Root NoGoogle 368.06 MB
-All the stock google stuff has been removed so you can flash a real gapps of your choice. (I have tested opengapps pico and recommend)
Instructions (remember, make a full backup first!)
Boot into TWRP, wipe dalvik, cache, data & system
Flash ROM
If you didn't wipe system in step 1 then go back to main screen, "Mount", select "system"
(if you're flashing the NoGoogle version, then flash gapps now)
Reboot
Enjoy
Thanks
@SuperR. -for the great kitchen
@vampirefo -for TWRP
Downloads
Stock Odexed NoRoot: Android FileHost or BasketBuild
Stock Odexed Debloated NoRoot: Android FileHost or BasketBuild
Stock Odexed Debloated Root: Android FileHost or BasketBuild
Stock Deodexed Debloated Root: Android FileHost or BasketBuild
Stock Deodexed Debloated Root NoGoogle: Android FileHost or BasketBuild
Gapps: Open GApps (select Platform x86, Android 5.1 & the variant of your choice. Note: x86_64 platfom gapps will NOT work.)
If this thread was helpful for you then please hit the "Thanks!" button!
reserved for additional resources
new fw version
chinagadgetsreviews.com/download-latest-android-lollipop-5-1-1-stock-firmware-cube-iwork-10-flagship-tablet.html
stefan_danut said:
chinagadgetsreviews.com/download-latest-android-lollipop-5-1-1-stock-firmware-cube-iwork-10-flagship-tablet.html
Click to expand...
Click to collapse
Thanks for the heads-up man -going to get started tomorrow on cooking up some ROMs for this version...
Sent from my OnePlus2 using XDA Labs
Turns out that build (20160412) is NOT lollipop 5.1.1, still 5.1. No big differences I can tell so far except for lack of play store/services and a bit less bloat. The boot animation is different (not Chinese cube one but text "TOPWING" ???). The device ID is also different.
I think I'll be holding off on making additional zips for this until there's a more serious and official update...
Sent from my OnePlus2 using XDA Labs
Hi jet, thanks for the tutorials!
I tried to install gapps but I get the error that there's insufficient storage available in system.
Did you get the same error? I'd like to use the stock installer.
According to the logs I have NO free system space.
Edit: I fixed it, might want to mention that you shouldn't forget to mount system!
UsernameNotRecognized said:
Hi jet, thanks for the tutorials!
I tried to install gapps but I get the error that there's insufficient storage available in system.
Did you get the same error? I'd like to use the stock installer.
According to the logs I have NO free system space.
Edit: I fixed it, might want to mention that you shouldn't forget to mount system!
Click to expand...
Click to collapse
Yeah, I didn't add it initially because if one wipes system before flashing then it's already mounted. It's the weird location of system partition on this tablet, opengapps (and supersu) install scripts can't mount it.
But, yeah it should be there as you pointed out, so I added it.
Thanks, and enjoy!
jetfin said:
Yeah, I didn't add it initially because if one wipes system before flashing then it's already mounted. It's the weird location of system partition on this tablet, opengapps (and supersu) install scripts can't mount it.
But, yeah it should be there as you pointed out, so I added it.
Thanks, and enjoy!
Click to expand...
Click to collapse
Ow, yeah, I had to because TWRP has issues remounting an otg mounted storage device, that might explain why it failed for me.
I just tried installing xposed and it got stuck in a bootloop, not a big issue as I've backed it up and haven't done much so far, but do you know if it's possible to install it?
And, heck, because I'm asking anyway, have you tried reinstalling windows? I'd like to install windows 10 enterprise on this tablet. Might save me the trouble from going to techtablets.
UsernameNotRecognized said:
I just tried installing xposed and it got stuck in a bootloop, not a big issue as I've backed it up and haven't done much so far, but do you know if it's possible to install it?
And, heck, because I'm asking anyway, have you tried reinstalling windows? I'd like to install windows 10 enterprise on this tablet. Might save me the trouble from going to techtablets.
Click to expand...
Click to collapse
I haven't tried xposed yet myself on this tab, but one guy over on my howto thread mentioned he tried and also ended up in a bootloop. Too much other stuff going on now but when I get around to xposed, if i get it working, I'll post here.
Sorry, can't help you on the windows side at all, in fact this iWork 10 is the first windows machine I've had in years, just android & ubuntu for me these days...
The people at techtablets are more keyed into the windows side of this tab, especially Laura. I'd recommend asking there.
It's the same tablet this and mine that have a Dual Boot (Windows 10 + Android 5.1.1).
And guys, any web page to follow curiosity of this tablet? mods, ROMS, etc...
What I *really* dislike about this tablet:
NO XPOSED... always destroys the bootup of android...
sdk22 x86 is the correct version, but not supported by this tablet... meh
jetfin said:
These are stock-based recovery flashable ROMs I've cooked up for the Cube iWork 10 Flagship (aka iWork 10 Ultimate), device i15-T(D).
They are all based on the stock build i15-T_V1.0_20160302, kernel version 3.14.37-x86_64-L1-R429 Wed Mar 2 18:22:46 CST 2016
Click to expand...
Click to collapse
Are these images for "Cube iWork 10 Flagship (i15-TC)" ?
Guys i need someone to tell me the network adapter name, because i installed new windows 10 and now i cannot find the network adapter driver.
Pls help, how to root td version? Need video tutorial
Hello everyone.
What is the available space of Android and Windows partition at the beginning?
No-one can answer this simply question??
Sent from my m1 note using Tapatalk
Help pls
Hi jet,
I flashed i15-T_Stock_Deodexed_Debloated_Root_NoGoogle.zip and open_gapps-x86-5.1-pico-20160917.zip,everything went okay except when I try to download apps from play store it shows downloading then it says can't download,what can be the reason for that? Or what can I do ?
demanik said:
Are these images for "Cube iWork 10 Flagship (i15-TC)" ?
Click to expand...
Click to collapse
No
Sent from my ONE A2003 using XDA Labs
abu laving said:
Hi jet,
I flashed i15-T_Stock_Deodexed_Debloated_Root_NoGoogle.zip and open_gapps-x86-5.1-pico-20160917.zip,everything went okay except when I try to download apps from play store it shows downloading then it says can't download,what can be the reason for that? Or what can I do ?
Click to expand...
Click to collapse
I've had similar before on other devices, flashing a different opengapps (like nano instead of Pico) or older opengapps or even other gapps package has usually worked... Note that you would want to reflash the rom and immediately following flash the gapps
Sent from my ONE A2003 using XDA Labs
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Download Links
LineageOS:
Downloads: https://download.lineageos.org/d2vzw
Google apps addon:
OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM platform, Android version 7.1)
HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.
Firmware:
Your best bet is to be on the MF1 bootstack/NE1 modem combo. Here's a flashable zip (this only needs to be done once): http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
Misc Links
Changelog:
Link: https://download.lineageos.org/d2vzw/changes/
Learn to build yourself:
Link: https://wiki.lineageos.org/devices/d2vzw/build
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] LineageOS 14.1 Nightlies for the Verizon Samsung Galaxy S3 (d2vzw), ROM for the Verizon Samsung Galaxy S III
Contributors
invisiblek
Source Code: http://github.com/LineageOS
ROM OS Version: 7.x Nougat
Version Information
Status: Nightly
Created 2016-12-05
Last Updated 2016-12-05
reserved
Hallelujah!
Is this the eighth or ninth life of this great phone?
@invisiblek, are there plans for the release of a Snapshot of CM13.0 for the d2vzw?
Congratulations on the "official" release!! Thank you for such an excellent and stable ROM for our ooooold, but no longer irrelevant, s3!
Nice job! Wich partitions can I mount as f2fs?
Just out of curiosity regarding the CM14.1...
Anyone having issue with internet connectivity specifically with the Play Store only (downloaded from Open GApps)?
Also, is anyone having issues with their external MicroSD. Though the external MicroSD can be viewed and can browse it, I'm Specifically stating the inability to execute, open, write to, etc...?
I had already sent the issues I'm having along with all my log files to @invisiblek and was curious as to any others experiencing the same/similar issues I experienced.
Thank you all for your time and understanding!
Thank you @invisiblek and other contributors. This is a great rom for this old phone. My DD is a LG G4, again, I went back to that after three Note 7's and all that drama. It's sad when a years old Galaxy S3 is running the latest and greatest but my LG G4 is still on last years Android! Yikes
I'm only using the SGS3 as a Wifi device so I can't comment on Cell radio functions but it's very smooth and seems markedly faster than when I was last using it as a DD. The only issue I've had and it may not even be related to this rom... I wanted to use Chainfire's PryFi to stick it to Kohls and Walmart that use WiFi Mac trackers, but when I launch PryFi and turn it on, it almost immediately crashes no matter what I do. Wipe cache, dalvik, reset and I get the same thing.
Thanks for the great work. Much appreciated!
@invisiblek, I'm reading elsewhere that the CM14.x should be installed first, then after the setup is accomplished, reboot back in to the recovery, then flash the GApps package.
Is this correct?
I just wanted to be sure in regards to the unconventional method of flashing the CM and the GApps together then reboot.
But, as you may know, after installing the 2 conventionally, I'm having trouble with the Play Store as well as the External MicroSD after setup.
I'd really appreciate your confirmation.
Thanks a Bunch!
Sent from my d2vzw using XDA Labs
Ibuprophen said:
@invisiblek, I'm reading elsewhere that the CM14.x should be installed first, then after the setup is accomplished, reboot back in to the recovery, then flash the GApps package.
Is this correct?
I just wanted to be sure in regards to the unconventional method of flashing the CM and the GApps together then reboot.
But, as you may know, after installing the 2 conventionally, I'm having trouble with the Play Store as well as the External MicroSD after setup.
I'd really appreciate your confirmation.
Thanks a Bunch!
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I had a problem installing the first time - I put build+Open GApps Aroma in the que and when the Aroma install was supposed to come up everything went black but the phone was still on. I flashed one and then the other without booting and it booted into initial setup normally.
But, I created a Nandroid with TWRP 2.8.7.0 and tried to restore the last Unofficial 14.1 build nandroid that worked normally but I couldn't get the sim card to work. Same when I tried to restore the new official. I tried numerous different ways to hold my mouth but it would never mount the SIM and settings was crapped out. I was able to restore my last MM nandroid and have it work normally. I've just switched to the latest TWRP 3.x.x.x. Don't know if that has anything to do with it....
I'm clean installing the new official again! It got stuck on boot (wrong boot animation, too) but pulling the batt and restarting, it went normally. (My Tibu settings were in the /data wipe. Gotta mount one and pull them )
Master Cylinder said:
I had a problem installing the first time - I put build+Open GApps Aroma in the que and when the Aroma install was supposed to come up everything went black but the phone was still on. I flashed one and then the other without booting and it booted into initial setup normally.
But, I created a Nandroid with TWRP 2.8.7.0 and tried to restore the last Unofficial 14.1 build nandroid that worked normally but I couldn't get the sim card to work. Same when I tried to restore the new official. I tried numerous different ways to hold my mouth but it would never mount the SIM and settings was crapped out. I was able to restore my last MM nandroid and have it work normally. I've just switched to the latest TWRP 3.x.x.x. Don't know if that has anything to do with it....
I'm clean installing the new official again! It got stuck on boot (wrong boot animation, too) but pulling the batt and restarting, it went normally. (My Tibu settings were in the /data wipe. Gotta mount one and pull them )
Click to expand...
Click to collapse
Thank you for your response!
I always had the latest TWRP 3.0.2-0 installed.
I flashed the CM14.1 20161207, Open GApps Pico 20161207 and, at first, SuperSU 2.78 Stable then when I retried a fresh install, i used SuperSU 2.78 SR5.
The same issues occurred (primarily) with the Play Store not being able to access the Internet the Internet and being able to see everything on my External MicroSD but, still not being able to read, write, move copy, install, etc...
I did see, during the initial bootup where you have the initial setup of CM & Google, the Google setup went fine but, I did notice that the carrier name reflected "no service" or "unknown" or something similar. I had ventured in to the network settings and did see everything needed in there so I didn't give it another thought.
To be honest, my opinion is that i really don't think that the release of the OFFICIAL CM14.1 Nightly was not ready yet.
I had to E-mailed @invisiblek the list of issues along with the installation log files from both the CM14.1 and the GApps but, I haven't even received an acknowledgement of at least a thank you.
@invisiblek is listed as the primary point of contact for Cyanogenmod and other than e-mailing him along with posting the issue here to his attention, I'm not sure how else to report any issues/feedback to Cyanogenmod... Cyanogenmod doesn't really pay attention to their own forums that has resulted in most individuals not even bothering with posting anything there anymore.
I'm personally going to put CM14.1 on hold till there's either some indication of improvement or finding some information reflecting my issues with some fixes, tryouts, solutions, etc...
I'm real disappointed with this...
Sent from my d2vzw using XDA Labs
Ibuprophen said:
Thank you for your response!
I always had the latest TWRP 3.0.2-0 installed.
I flashed the CM14.1 20161207, Open GApps Pico 20161207 and, at first, SuperSU 2.78 Stable then when I retried a fresh install, i used SuperSU 2.78 SR5.
The same issues occurred (primarily) with the Play Store not being able to access the Internet the Internet and being able to see everything on my External MicroSD but, still not being able to read, write, move copy, install, etc...
I did see, during the initial bootup where you have the initial setup of CM & Google, the Google setup went fine but, I did notice that the carrier name reflected "no service" or "unknown" or something similar. I had ventured in to the network settings and did see everything needed in there so I didn't give it another thought.
To be honest, my opinion is that i really don't think that the release of the OFFICIAL CM14.1 Nightly was not ready yet.
I had to E-mailed @invisiblek the list of issues along with the installation log files from both the CM14.1 and the GApps but, I haven't even received an acknowledgement of at least a thank you.
@invisiblek is listed as the primary point of contact for Cyanogenmod and other than e-mailing him along with posting the issue here to his attention, I'm not sure how else to report any issues/feedback to Cyanogenmod... Cyanogenmod doesn't really pay attention to their own forums that has resulted in most individuals not even bothering with posting anything there anymore.
I'm personally going to put CM14.1 on hold till there's either some indication of improvement or finding some information reflecting my issues with some fixes, tryouts, solutions, etc...
I'm real disappointed with this...
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I'll attempt to try to help with some of the issues here, as I have direct contact with invisiblek pretty much daily. First I will start off with a few questions, NOT poking, just asking, this also may address some previous posts as well... You have a verizon SCH-I535 correct, and not another variant? Just making sure. And to start you wiped data in TWRP (wipe to install new ROM option basically). Told it to flash your 12/07 build? Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps? After it rebooted, it sometimes takes a while to get the setup to actually start and display, sometimes it goes to a black screen for minutes, but be patient, it will come.. At that point in time, it will initialize sim card and be connected, as this was my experience on all 3 of my S3 phones in my household. Then proceed through setup...
Is your external card formatted as "portable storage", or is it formatted as "Adopted storage". Also what type of filesystem do you have the card formatted with? What file manager are you using to try to access your card with? There was some expected changes that might have to be worked out as the "unofficial" roms were running Selinux in permissive mode, and the "official" roms are running it in Enforcing mode. That is bound to cause some small differences in the way the 2 roms behave. Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom? There might be some issues being caused by that in itself.
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials. Also, I have had limited luck with the built in file manager. I have used ES File Explorer forever, and it continues to behave well on this rom. Also, even if you are going to nandroid back and forth between official and unofficial, it is best to do a wipe of DATA before the nandroid... As far as the play store goes, I haven't experienced any lack of connectivity. I do get very small intermittent blips where it seems like it isn't connected for a second or 2, but it is very rare, and it has always been like that as far as I can remember.. Part of the reason that is for me is because I use a network extender, and it has always been the achilles heel with CM.
Try going into TWRP, do the "wipe to install new rom", add the cm zip, and ALSO add the latest "Opengapps arm 7.1 pico or micro" (your choice) build into the zip queue so that they are flashed in succession. Let it rip, and see if that offers you any different results. After you get it initially setup, go into developer options and enable root as needed. Give it a run and see what issue are still present, if any. I am surprised to hear some of these issues, as between myself, my kids, and a handful of friends, everyone is super stoked at how well these early builds are running... I myself have less than 3 reported issues from friends that we are looking into, and they are all just cosmetic bugs so far... I will be glad to try to help in any way possible..
P.S. There have been quite a few things resolved/changed between TWRP 2.8.7.0 and 3.0.2-0, I would highly suggest not only upgrading to the latest TWRP version, but also making sure you are on the firmware versions that are mentioned in the OP.
Stealth111
Stealth111 said:
I'll attempt to try to help with some of the issues here, as I have direct contact with invisiblek pretty much daily. First I will start off with a few questions, NOT poking, just asking, this also may address some previous posts as well... You have a verizon SCH-I535 correct, and not another variant? Just making sure. And to start you wiped data in TWRP (wipe to install new ROM option basically). Told it to flash your 12/07 build? Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps? After it rebooted, it sometimes takes a while to get the setup to actually start and display, sometimes it goes to a black screen for minutes, but be patient, it will come.. At that point in time, it will initialize sim card and be connected, as this was my experience on all 3 of my S3 phones in my household. Then proceed through setup...
Is your external card formatted as "portable storage", or is it formatted as "Adopted storage". Also what type of filesystem do you have the card formatted with? What file manager are you using to try to access your card with? There was some expected changes that might have to be worked out as the "unofficial" roms were running Selinux in permissive mode, and the "official" roms are running it in Enforcing mode. That is bound to cause some small differences in the way the 2 roms behave. Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom? There might be some issues being caused by that in itself.
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials. Also, I have had limited luck with the built in file manager. I have used ES File Explorer forever, and it continues to behave well on this rom. Also, even if you are going to nandroid back and forth between official and unofficial, it is best to do a wipe of DATA before the nandroid... As far as the play store goes, I haven't experienced any lack of connectivity. I do get very small intermittent blips where it seems like it isn't connected for a second or 2, but it is very rare, and it has always been like that as far as I can remember.. Part of the reason that is for me is because I use a network extender, and it has always been the achilles heel with CM.
Try going into TWRP, do the "wipe to install new rom", add the cm zip, and ALSO add the latest "Opengapps arm 7.1 pico or micro" (your choice) build into the zip queue so that they are flashed in succession. Let it rip, and see if that offers you any different results. After you get it initially setup, go into developer options and enable root as needed. Give it a run and see what issue are still present, if any. I am surprised to hear some of these issues, as between myself, my kids, and a handful of friends, everyone is super stoked at how well these early builds are running... I myself have less than 3 reported issues from friends that we are looking into, and they are all just cosmetic bugs so far... I will be glad to try to help in any way possible..
P.S. There have been quite a few things resolved/changed between TWRP 2.8.7.0 and 3.0.2-0, I would highly suggest not only upgrading to the latest TWRP version, but also making sure you are on the firmware versions that are mentioned in the OP.
Stealth111
Click to expand...
Click to collapse
Okay... I tried to sort out and answer all the questions the best i could.
I also attached the log files. They are dated according to the Nightly releases.
Q: You have a verizon SCH-I535 correct, and not another variant?
A: Yes. I have an SCH-I535.
Q: And to start you wiped data in TWRP (wipe to install new ROM option basically).
A: 1) Factory Reset. 2) Wipe Dalvik, Data, Internal Storage, Cache and System. 3) Format Data. Then Restart Recovery back to TWRP.
Q: Told it to flash your 12/07 build?
Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps?
A: Install and select CM14.1 12/07 build then the Open GApps 7.1 ARM Pico. To add... I tried flashing the 2 above only, then tried the same 2 above with SuperSU 2.78 Stable, lastly the 2 above with SuperSU 2.78 SR5. All resulted with the same issues.
Q: Is your external card formatted as "portable storage", or is it formatted as "Adopted storage".
A: Portable Storage.
Q: Also what type of filesystem do you have the card formatted with?
A: VFAT
Q: What file manager are you using to try to access your card with?
A: Stock & ES File Explorer Pro
Q: Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom?
A: I'm aware of the stock root manager but, i've always preferred SuperSU's root management.
I really appreciate your assistance and please don't hesitate to defer to @invisiblek if necessary.
Also, please keep in mind that I'm not in a race. Take your time because patience is a virtue...
Thank you very much!!!
I wonder if the GApps issue is the underlying issue. I hope @MastahF & @Rapper_skull is aware of and working on it?
Sent from my d2vzw using XDA Labs
Stealth111 said:
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials.
Stealth111
Click to expand...
Click to collapse
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
Ibuprophen said:
Okay... I tried to sort out and answer all the questions the best i could.
I also attached the log files. They are dated according to the Nightly releases.
Q: You have a verizon SCH-I535 correct, and not another variant?
A: Yes. I have an SCH-I535.
Q: And to start you wiped data in TWRP (wipe to install new ROM option basically).
A: 1) Factory Reset. 2) Wipe Dalvik, Data, Internal Storage, Cache and System. 3) Format Data. Then Restart Recovery back to TWRP.
Q: Told it to flash your 12/07 build?
Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps?
A: Install and select CM14.1 12/07 build then the Open GApps 7.1 ARM Pico. To add... I tried flashing the 2 above only, then tried the same 2 above with SuperSU 2.78 Stable, lastly the 2 above with SuperSU 2.78 SR5. All resulted with the same issues.
Click to expand...
Click to collapse
I know this may sound funny but I've had this EXACT response from clean installs using the tiny GApps packages. Try one of the larger ones or the Aroma installer. (I know it's annoying if you want to keep all that crap off your phone ...)
As I said, I installed without using the qeue. I also wiped Dalvik/cache AFTER the installations, as per the OpenGApps instructions.
Oh, and my phone is purring like a kitten with 12/7 on it! XD
PS - Except for that dang restore issue. Scared to try it again but I gotta try it again eventually.
Master Cylinder said:
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
Click to expand...
Click to collapse
I have the same version as well. I go to the store, click install on the Pro version. It installs just fine... I then go in and open the program, it immediately asks for the needed root permissions, which I promptly give it, then I close the welcome message. When I actually then click install from within the program, it then tries to install for about 2 seconds and then says "oops, it looks like the installation was unsuccessful, maybe try a different location"....
Who knows.... :laugh:
Other than that, I agree, purring like a kitten!
Stealth111
Master Cylinder said:
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
I know this may sound funny but I've had this EXACT response from clean installs using the tiny GApps packages. Try one of the larger ones or the Aroma installer. (I know it's annoying if you want to keep all that crap off your phone ...)
As I said, I installed without using the qeue. I also wiped Dalvik/cache AFTER the installations, as per the OpenGApps instructions.
Oh, and my phone is purring like a kitten with 12/7 on it! XD
PS - Except for that dang restore issue. Scared to try it again but I gotta try it again eventually.
Click to expand...
Click to collapse
I tried the nano on one attempt thinking that pico was the culprit but, the same issue...
Sent from my d2vzw using XDA Labs
Sorry to ask this again but wich partitions should be remounted as f2fs for better performance?
Sent from my Pixel using XDA Forums Pro.
Ibuprophen said:
I tried the nano on one attempt thinking that pico was the culprit but, the same issue...
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I had the same problem with Nano. If you're gonna spend the time to do it, go big. Bigger rather than smaller.
Pierre2324 said:
Sorry to ask this again but wich partitions should be remounted as f2fs for better performance?
Click to expand...
Click to collapse
Here's a link that, i believe, will answer your question:
http://forum.xda-developers.com/showthread.php?t=2537119
Good Luck!
Sent from my d2vzw using XDA Labs
---------- Post added at 02:14 AM ---------- Previous post was at 01:54 AM ----------
Master Cylinder said:
I had the same problem with Nano. If you're gonna spend the time to do it, go big. Bigger rather than smaller.
Click to expand...
Click to collapse
There was a member in the GApps thread who had mentioned that he had a similar issue.
He stated that what worked for him was flashing a GApps Pico package on from about 30 days ago.
I believe that others had to flash their GApps packages from about 30 days ago had worked for them.
I know that this is an issue for many others who also reported it to the Dev(s).
I can't think of what in the world is going on...
Sent from my d2vzw using XDA Labs
Running smooth as ice.......only issue I've had was a single browser hicup. Incredible work, makes me smile knowing I have a newer version on my ancient phone than most of the $700+ flagship phones. Invisablek you sir are the man:good: