Related
I upgraded my p1000 from cm10.2 to cm11 few weeks ago but the latest cm11 seems to be a bit laggish on my device and I'd like to go back to cm10.2, first of all... is it possible? If so, which is the proper way to do it?
mrfree2ita said:
I upgraded my p1000 from cm10.2 to cm11 few weeks ago but the latest cm11 seems to be a bit laggish on my device and I'd like to go back to cm10.2, first of all... is it possible? If so, which is the proper way to do it?
Click to expand...
Click to collapse
I'd recommend you try OmniROM Its what I'm using on my "P1" and although it has its share of problems. Wired Headsets don't seem to be working. Its no more worse then CM10 was, and on that note why CM10.2 which like CM10.1 was broken beyond use? The only decent CM10 was CM10 from 2013 - 02 - 03. Which AFAIK was the last fully working CM10 Mod for the P1000. As the 10.1 and .2 had the Camera Bugs.
In any case Omni is pretty well supported with near nightly, or at the lest every other night updates. As long as you don't get crazy with it with Live Wallpapers, like my Old man was trying to run on it. (He too has a P1000), its pretty damned responsive. But. Again you ONLY have 512MB of RAM on the P1000. In some rear cases even less then this!
In my Fathers case the same sh-- that was causing his CM11 to lag like heck, was the same crap that was making the fresh install of his CM10 (version as dated above!), lag just as bad. So you might want to first clean up such resource hungry Apps as you have first.
But, on the Latest OmniROM for the P1 (Int't GSM version), as of 06.08.14 (Which is still the the most current at the time I wrote this), just running the Google Now Launcher, and a few widgets. The Tablet doesn't feel any considerably slower then it did back in CM10, and the Google Now Launcher is a KEEPER! I can't imagine wanting to roll back to CM10.
P.s. Did you remember to reset your Firmware + wiping the Cache Partition, and Dalvik Cache? This could also partially explain your problems. If you, had not done this.
P.p.s. Download your ROM, and appropriate GAPPs Package, then reboot your P1000 by pressing both the Volume Up, and Power Button till you see the Galaxy Tab / Samsung Bootloader Screen. Then release the Power Button, while continuint to hold the Volume Up till you fully enter the Recovery Mode.
Once in the Recovery Mode do the following Factory Reset, then Wipe Cache Partition and the Dalvik Cache (Advanced Settings). Then install your CM10.x ROM from where you stored it i.e. the /Download Folder? And when thats though. Your GAPPs Package as well. After which you then boot into your new ROM. Which might take a few moments longer, on the first boot as the Database(s)? have to built from scratch again.
Mmmhh I think I'll follow your suggestion and I'll try OmniROM. Have you used the CWM recovery or the TWRP suggested on their official wiki to flash the omnirom?
mrfree2ita said:
Mmmhh I think I'll follow your suggestion and I'll try OmniROM. Have you used the CWM recovery or the TWRP suggested on their official wiki to flash the omnirom?
Click to expand...
Click to collapse
The way I described it before was for CWM. OmniROM uses TWRP. The ideas the same, in fact its a bit simpler on TWRP, in as far as it simplifies the wipe progress. Just One TIP download and install SuperSU, and run it. Once your rooted, go into your System Settings and click on the SuperSu Setting, (near the bottom), and it should ask you if you want to use a backup script, to keep root! You should run this if you want to... Need to keep Root for say AdAway. As OmniRom does NOT ship out with Root... WHY?! I can't say.
Other then that the only other annoying things I dislike about this ROM is that I have to keep uninstalling the Apollo Player. as well as reinstalling the Xposed Installer reset the "ro.config.low_ram" from true, to false, to re-enable transparencies, as well as other Lock Screen Widgets. After each update. Which again averages about every other day. I use something called ROM Toolbox Lite to do this, as trying to do this manually I always seem to gimp my install to a point of bootlooping.
But, other then these little niggles I actually like this ROM! for the most part.
And we should discourage question thread in development forum.
Sent from my GT-N7100 using XDA Free mobile app
Hello XDA community, I am a 100% new noob who is interested in getting started with rooting. I am going to get right to the point with what I am working with, what I have done, and what I need some help with. May my journey with lovely pictures be a helpful guide for all those who follow me (I find it is easier to understand things with lots of images).
Used this thread to begin my journey on rooting an old Nook HD tablet.
Started with a factory reset but it automatically updated according to my settings page, so one of my question is; does it matter what software version my device is running before I root it?
Followed instructions in PeteInSequim guide and created an 8 GB Micro SD Card with all the files.
Green = CM-12.1_Installation_20150925 Instructions PDF
Light Blue = Files from NookHD-bootable-CWM-6046-for-emmc-BOOTFILES-rev0-(07.13.14)
Red = CyanogenMod 12.1 (No official release on their website)
Orange = ClockworkMod_Recovery (Couldn't find website for other versions)
Yellow = TWRP Recovery (They may have a newer version)
Purple = TK-GAPPS (Which I downloaded the STOCK package, and am not sure if that is compatible)
This is what I have done so far, and would like advise on what I should do before I advance, specifically around the TWRP VS. CWM with relation to the GAPPS packages. In the tutorial (PDF), I believe they use the CWM to install TWRP, I think TWRP is better and is the only of the two who will support my GAPPS package, but would like someone to help clarify so I don't make a permanent mistake. Also, should I use newer versions of anything? Should I even be attempting CM-12.1 if it is not officially supported? I don't want to have to keep making changes and not changing backgrounds or settings... should I go for the more stable CM-11, if so would I have to completely change my process?
Thanks for the help,
Buckaroo9
I'm a bit lazy when it comes to installing incremental releases, so I prefer to do simple "dirty installs". This means re-flashing without wiping the old installation, which can be done in seconds with no consequences.
But a dirty install will probably fail if you have made user-interface changes, even if you try to reverse out those changes before flashing. You can still install revisions any time you wish, but you must do the wipes first. This means you will have to go through the set-up procedure all over again, which takes a lot longer than a dirty install.
CM-12.1 for our Nooks should eventually be offered among the official nightly releases, and hopefully a milestone release now and then. I might consider UI tweaks after installing one of these, then settle down for a long quite period of no more updates.
If a stable CM-12.1 ever happens, we'll all be installing CM-13 by then.
Click to expand...
Click to collapse
PeteInSequim
Could you please explain this concept slightly more to me? How much would I be able to change and what would the consequences be? If I make changes would I always have to do a clean wipe, would that mean I would have to not make changes and constantly wait for updates? This uncertainty is kind of pushing me away from rooting...
Buckaroo9 said:
...
This is what I have done so far, and would like advise on what I should do before I advance, specifically around the TWRP VS. CWM with relation to the GAPPS packages. In the tutorial (PDF), I believe they use the CWM to install TWRP, I think TWRP is better and is the only of the two who will support my GAPPS package, but would like someone to help clarify so I don't make a permanent mistake.
Click to expand...
Click to collapse
The files you got look right, although I'd recommend using the smaller micro or even nano GApps packages as you can always add more apps later on.
Just use CWM to flash TWRP first, then boot to TWRP to wipe /data and flash CWM and GApps.
Also, should I use newer versions of anything? Should I even be attempting CM-12.1 if it is not officially supported? I don't want to have to keep making changes and not changing backgrounds or settings... should I go for the more stable CM-11, if so would I have to completely change my process?
...
Click to expand...
Click to collapse
CM12.1 for the HD/HD+ is not officially supported and, more importantly, is no longer enhanced/maintained (its original developer has recently moved onto CM13). I've been using CM12.1 for about a month now: the apps' performance can be noticeably more snappy but not consistently so, on the downside couple of apps/features that used to work on CM11 no longer work.
If you're looking for a reasonably newer but stable CM version, I'd suggest you try CM11 (either M12 snapshot or one of the recent "nightly" releases).
digixmax said:
Just use CWM to flash TWRP first, then boot to TWRP to wipe /data and flash CWM and GApps.
Click to expand...
Click to collapse
Is there any reason TWRP can't flash itself?
digixmax said:
I'd recommend using the smaller micro or even nano GApps packages as you can always add more apps later on.
Click to expand...
Click to collapse
Is there any downside to using a larger GApps, and if I can always add more, does that mean I can mix and match, are the essentially just packages of Apps that I am side-loading?
digixmax said:
If you're looking for a reasonably newer but stable CM version, I'd suggest you try CM11 (either M12 snapshot or one of the recent "nightly" releases).
Click to expand...
Click to collapse
I am definably leaning towards more stable, but in your opinion, what features would I loose from CM12 (Android 5.0 Lollipop)? Someone made a good point that, the most advanced, newest, and coolest software will always be unstable. You have to trade off the cutting edge for reliability and support.
As a new member to rooting, I think I may start with more stable things, and then work my way up.
Buckaroo9 said:
Is there any reason TWRP can't flash itself?
Click to expand...
Click to collapse
The TWRP flashable zip file you have contains a TWRP image that is compiled for internal EMMC. Once installed, it can be used to flash CM, GApps, or another version of CWM or TWRP to replace itself.
To flash from SD you need to find and use a TWRP recovery image that is compiled for SD.
Is there any downside to using a larger GApps, and if I can always add more, does that mean I can mix and match, are the essentially just packages of Apps that I am side-loading?
Click to expand...
Click to collapse
You can use a Zip archive program like 7-zip to open up and browse the content of these GApps zip packages to see and compare their particular mixes of apps.
I am definably leaning towards more stable, but in your opinion, what features would I loose from CM12 (Android 5.0 Lollipop)?
Click to expand...
Click to collapse
This depends on your particular use and choice of apps for the tablet, but as examples, the Hulu app and USB Host feature which work on CM11 don't work on CM12.1.
Has anyone managed to get it working? I just tried to install via FlashFire and wound up getting an animation loop on the SlimLP boot logo. I applied the 5.1.1 firmware through the "apply update through adb" option in the recovery, can anyone confirm Xposed even working on SlimLP?
I'd like to know this also. Have not tried it yet.
I think you have to use the slim-rom version from the 4th post. The original slim rom is not running with xposed beacause of some ART optimizations... Read the slim rom thread. There you can find something about it.
Thanks! Think I found an easier solution than installing Xposed for what zip needed though (just needed YouTube to play in the background). That will come in handy if I want it later for any reason though.
Yes, xposed works fine. Big thanks to csolanol!
You must use the xposed compatible SlimLP 0.13 build + the correct xposed version (see the howto xposed thread in Fire General forum).
Anybody had success with getting .013 build running successfully with eXposed.. I've tried the ' Slim-ford-5.1.1.beta.0.13-UNOFFICIAL-20151221-0949.zip ' build from root junkies tutorial i think in section 4 or something if i remember vaguely, but with no luck... The Flash just proceeds as expected then reboots while opening/loading .zip.. But the standard release 'non-eXposed' runs without any problems.
Need to include more information. You're flashing with twrp or flashfire? If you used flashfire, what are you coming from? Stock 5.1.1 or another rom.
Do you mean after flashing the rom your Fire will not boot / start up?
I flashed SlimLP 0.13 via twrp without a problem on two different Fires. Xposed runs fine.
thanks for your reply, I'm flashing with flashFire from a r00ted fresh clean stock fire-os 5.1.1 on Amazon Fire 7" 5th Gen. i execute flash after selecting wipe all partitions except sd and then load .zip via ota then push button to commence flash, it proceeds to blank screen and then flashing screen and begins to attempt rom install i see rom info and 'char pic' of rom then it self terminates and reboots to existing r00ted fire-os, i do this exact same process with the rom not currently supporting Xposed from rootjunkie download site, and everything completes successfully spending a slightly longer period at the rom install/upload stage completing successfully with slimlp running nice... minus a few almost irrelevant bugs i noticed...
Twrp via adb doesn't work with 5.1.1 right? only works on 5.0.1&2? .. unless im mistaken.. any ideas?
Yep, we can't use twrp on 5.1.1.
So you select to wipe, system data, 3rd party apps, dalvik cache, cache partition, correct? I'm afraid I have no suggestions.
exactly that's correct , then i select rom, then i select gapps. then press flash button and it halts on the next screen as it begins to flash rom and quits to a reboot .. everything still unchanged as it was.. i have tried this process installing from stock os fire 5.1.1 & slimlp 5.1.1 with unsuccessful results.. but hey at least i have a SlimLp non-Xposed edition installed that beats Fire-BS#"*t any day. guess I'll have to wait for a new build to be released. bummer.
---------- Post added at 12:32 ---------- Previous post was at 12:25 ----------
in the future i guess more concentration is needed on the 5.1.1 Xposed edition skimlp rom to be flashed from 5.1.1 stock, for the true android custom eXperience .. i have also seen a fw roll back to 5.0.1or5.0.2 is not possible from any 5.1.1 os. never mind.
What I find is odd is that you've selected to wipe first. Flashfire should be wiping before trying & failing to flash SlimLP 0.13, leaving your Fire wiped & unable to boot back into the stock FireOS (you would then need to restore FireOS 5.1.1 via adb sideload in the amazon recovery). FlashFire is in beta & I think it's currently a bit buggy.
Bib_x said:
I think you have to use the slim-rom version from the 4th post. The original slim rom is not running with xposed beacause of some ART optimizations... Read the slim rom thread. There you can find something about it.
Click to expand...
Click to collapse
Sorry, I feel I joined the conversation mid-way but, which SlimROM thread are you talking about?
There is only one SlimLP-Thread in android development section.
Newest SLim-Version for Fire is without Art-Optimizations, so you can use xposed now with the latest slimlp 0.14.
With the older SlimLP 2.3 there was Art-Optimization inside - so there no xposed was working.
Bib_x said:
There is only one SlimLP-Thread in android development section.
Newest SLim-Version for Fire is without Art-Optimizations, so you can use xposed now with the latest slimlp 0.14.
With the older SlimLP 2.3 there was Art-Optimization inside - so there no xposed was working.
Click to expand...
Click to collapse
Thanks for the reply. I actually don't have a Fire and came across this thread after a lot of googling. I'm running SlimLP 0.12 I think on a Note Edge. I absolutely love this ROM. Seriously, I was close to selling the phone for scraps until I flashed this ROM. Now I think I will never buy another phone unless there is SlimROM support already
Anyway, I've been looking everywhere for a solution to get Xposed running. I found people saying that SELinux needs to be set to Permissive which I have done but still no luck. Are you saying that it's impossible with SlimLP versions before 0.14? Somehow, I doubt that would come to the Note Edge
marcolorenzo said:
Thanks for the reply. I actually don't have a Fire and came across this thread after a lot of googling. I'm running SlimLP 0.12 I think on a Note Edge. I absolutely love this ROM. Seriously, I was close to selling the phone for scraps until I flashed this ROM. Now I think I will never buy another phone unless there is SlimROM support already
Anyway, I've been looking everywhere for a solution to get Xposed running. I found people saying that SELinux needs to be set to Permissive which I have done but still no luck. Are you saying that it's impossible with SlimLP versions before 0.14? Somehow, I doubt that would come to the Note Edge
Click to expand...
Click to collapse
Maybe try looking in the Note Edge forum not the Amazon Fire one?
Pond-life said:
Maybe try looking in the Note Edge forum not the Amazon Fire one?
Click to expand...
Click to collapse
Maybe you shouldn't presume, with no information, that people are imbeciles? Don't you think I would've have done that at the beginning? Anyway, I may be wrong but I presumed that whether or not Xposed worked was more dependent on the ROM and not the phone? So if people here, who are discussing Xposed on SlimROM can help me, why not ask?
Bib_x is correct, i confirm Xposed working on slimlp build 0.14 beautifully for Fire 7 5th Gen.. be wary of modules you install other wise you'll have to start everything from scratch when you reach a boot hang because of a not yet compatible module.. you have no custom recovery remember so no quick fix, can always fresh install everything lol., which is good training lol.
Hello .... I'm finding whatever OS I'm trying becoming unstable to use . So, I'm asking if there is any OS that is actually stable enough to use . I don't care whether it's an old version or what . I'm not using the tablet for games, just something I can browser the internet with . TIA
The one that has given me the fewest issues is https://forum.xda-developers.com/showthread.php?t=2712680 [ROM] [4.4.4] [CyanogenMod 11 by Jcsullins] [DM] [06/12/15]
everything works extremely well except the DSP manager when adjusting audio settings for the built in speakers where changes beyond the defaults do not have any effect on the audio.
Sadly many of the links are dead for things like gapps.
The ROM I use is cm-11-20151116-SNAPSHOT-jcsullins-tenderloin.zip
The gapps I use is: gapps-444-base-20160802-1-signed.zip
If needed, I can upload the gapps that I use though I am unsure if the forum has any rules surrounding it if I were to upload them to something like dropbox.
I try the others from time to time (easier for me since I really only use BSplayer and chrome in order to watch videos in a hover window while surfing the web (occasionally using my Bluetooth speakers or headphones).
Anyway, the main reason why I keep coming back to it, is the memory management. For many newer ROMs, you have issues such as the google calendar widget not working,or chrome not working properly, or when it is working, frequeny memory issues, especially if you want to upload an image to a site where it switches to the gallery app. by the time you select an image, it would fail to attach it because it will complain that the previous action could not be completed due to low memory.
With android 4.4, I do not have that issue. I don't know why it keeps happening for me since there are times when there will be over 100MB of free RAM, and chrome will still fail to do things with that error message.
Beyond that, the home screen under android 7.1.1 does not hold as many icons or widgets, even if you set the screen size to small, or adjust the dpi to 120. the home screen holds fewer icons and fewer widgets.
Overall, while it si great that newer versions of android are being supported, I feel that from a hardware standpoint then tablet has reached its limit with android 4.4
While there is also an evervolve version of android 4.4, for some reason it does not perform as well, even with more kernel features such as being able to overclock past 1.78GHz. it takes longer to boot, and some widgets do not work, along with issues with chrome.
https://forum.xda-developers.com/showpost.php?p=71176374&postcount=937
Check out the Nougat Evervolv thread. I've been using it, and it's fantastic.
Thanks for your input Razor512 .... And crazyates : Has this been updated since its first release, because when I gave it a go it was very unstable
Dude905 said:
Thanks for your input Razor512 .... And crazyates : Has this been updated since its first release, because when I gave it a go it was very unstable
Click to expand...
Click to collapse
Yes it has, but you need to download the nightly from their website. The XDA thread has an older version.
http://evervolv.com/devices/tenderloin
Ok, great news there crazyates. I installed evervolv from the YouTube guide, Do you know whether it still will work with those methods in the guide just as long I replace it with
ev_tenderloin-7.1.1-nightly-2017.03.03.zip and I believe you are using gapps-511-base-20161007-1-signed.zip , yes ? Thanks
YouTube >>> https://www.youtube.com/watch?v=ISWZ0c48gNA
Dude905 said:
Ok, great news there crazyates. I installed evervolv from the YouTube guide, Do you know whether it still will work with those methods in the guide just as long I replace it with
ev_tenderloin-7.1.1-nightly-2017.03.03.zip and I believe you are using gapps-511-base-20161007-1-signed.zip , yes ? Thanks
YouTube >>> https://www.youtube.com/watch?v=ISWZ0c48gNA
Click to expand...
Click to collapse
I'm not sure about the Youtube instructions, and I followed the written instructions on the forums.
Also, IIRC, if you're using a 7.1.1 ROM, you can't use a 5.1.1 Gapps. I would recommend downloading the newest 7.1.1 Gapps.
Here are the instructions I followed:
AlwaysLucky said:
If you end up having to start from scratch in TP Toolbox v0.42, follow these steps:
- Download a TP Toolbox Compatible ROM
- Download a TP Toolbox Compatible GApps
- Download a TP Toolbox Compatible TWRP
1. In the TP Toolbox v0.42 main menu, do a 'Complete Data Reset' to start from scratch
2. Select the 'Install Android' option from the main menu
3. Copy the 3 above files to the install folder after the TP is mounted
4. When given the option to adjust partition sizes, increase the System partition to at least 1312mb
5. Finish install, and reboot to TWRP
6. While in TWRP, flash the 9/6/16 TWRP 3.0.2.0 or the smaller 9/11/16 TWRP 3.0.2.0
7. Reboot into the new TWRP that you just flashed
8. In TWRP advanced wipe menu, wipe the System partition
9. While still in TWRP, flash the ROM from the OP along with some OpenGapps
10. Worship @jcsullins and @flintman, as they are your gods.
Click to expand...
Click to collapse
Here are the changes/differences I made/noticed:
crazyates said:
Step 3: While you're copying the older ROM/Gapps/TWRP into the "ttinstall" folder, I also copied everything you need for the new install into an "evervolv" folder. This way you can copy everything at once, and formatting a volume in TWRP doesn't destroy your install files.
Step 4: I have a 32GB TP, and don't use hardly any of it, so I increased the System to ~2GB, and the Cache to ~1GB. I figured going on the big side couldn't hurt.
Step 6: There's a newer version of Flintmans TWRP, 3.0.3.0(12/22/16).
Step 8: After you wipe the System, reformat the Data and Cache volumes as F2FS. Because your install files are on the External_SD instead of the Data, you can do this without recopying your install zips back again. I installed the system twice, once with Ext4 and once with F2FS. It feels snappier, and runs a lot better with F2FS.
Step 9: I used the Nightly build for the ROM, which is working great. Then the newest Gapps. Then I also flashed the SKZ overclock kernel at the same time.
Few other notes: Changing the Governor to LionHeart and Scheduler to Tripndroid made a noticeable difference for me. Also, because this doesn't have a lot of RAM, I gotta be careful with what I install, and how much I try to use it. Do NOT install Chrome from the app store. It will eat every bit of RAM available, and slow the whole thing down. I also use Greenify (with root permissions) to hibernate any app I can so it saves a lot of RAM that was as well. I'm using ~329MB (40%) for the system, with ~500MB (60%) available for apps.
Click to expand...
Click to collapse
@crazyates Did you try Evervolv 7.1 nightlies? I'm curious to read your experience feedback because I'm on it and getting tired of always having a non-responsive tablet. I might go back to 4.4 as I'll go mad otherwise.
bobcote said:
@crazyates Did you try Evervolv 7.1 nightlies? I'm curious to read your experience feedback because I'm on it and getting tired of always having a non-responsive tablet. I might go back to 4.4 as I'll go mad otherwise.
Click to expand...
Click to collapse
I am running the 7.1.1 nightlies. I haven't had any problems, and it's running very smooth. I'll randomly update it to the newest nightly, and haven't noticed any issues.
I do remember the time I first installed Evervolv 6.0 nightly last year. I installed it, and the touchscreen didn't work. At all. Looked into it, and it was a problem with that specific nightly build, so I went and reflashed everything with the one from the day before, and it worked great.
Anyways, all that to say it's working great, but it's still a nightly, so sometimes things go wonky.
I am still running a really old ICS build, and I noticed i can't update all my apps no more... what is the best Android version to run on the TP. Bluetooth is a must, but Camera isn't. Heard good things about 4.4.4 and 7.1.1, which one would you guys say runns smoother?
wprpalmeida said:
I am still running a really old ICS build, and I noticed i can't update all my apps no more... what is the best Android version to run on the TP. Bluetooth is a must, but Camera isn't. Heard good things about 4.4.4 and 7.1.1, which one would you guys say runns smoother?
Click to expand...
Click to collapse
Can't say much for 4.4.4, but I'm using 7.1.1 and it's great!
The only argument I could see making for 4.4.4 is if it runs a bit lighter than 7.1.1. These only have 1GB of RAM, so if 4.4.4 is capable of using less RAM for the android system, that means more RAM for apps. On the flip side, 7.1.1 uses such things as zRAM and KSM for better memory management, so it may be a wash.
crazyates said:
Can't say much for 4.4.4, but I'm using 7.1.1 and it's great!
The only argument I could see making for 4.4.4 is if it runs a bit lighter than 7.1.1. These only have 1GB of RAM, so if 4.4.4 is capable of using less RAM for the android system, that means more RAM for apps. On the flip side, 7.1.1 uses such things as zRAM and KSM for better memory management, so it may be a wash.
Click to expand...
Click to collapse
yeah, this is what I want to figure out. The developments in the Android codebase were quite extensive between these two releases, and the huge influx of budget phones in some markets (like mine for example) lead me to believe memory management would have been a key point in developing versions after 4.4.4. I'll give 7.1.1 a whirl and see how it goes.
Here are the instructions I followed:
...
Here are the changes/differences I made/noticed:
Click to expand...
Click to collapse
I tried to follow your instructions, but I get error messages like:
Error: unrecognized/unsopported zip 'FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.3.0-1-23-17.zip'
Error: Incompatible GAPPS/ROM versions None/7.0
I used the latest nightly (ev_tenderloin-7.1.1-nightly-2017.03.08.zip) and tried both open_gapps-arm-7.1-pico-20170312.zip and open_gapps-arm-7.1-pico-20170312, also I tried some of the TWRP-Versions you linked. I'm using TPToolbox v42 2015-01-08). So I wonder how you can figure out which versions fit together, I can remember this nagged me last time until I found a combination that worked...
AlwaysLucky said:
If you end up having to start from scratch in TP Toolbox v0.42, follow these steps:
- Download a TP Toolbox Compatible ROM
- Download a TP Toolbox Compatible GApps
- Download a TP Toolbox Compatible TWRP
1. In the TP Toolbox v0.42 main menu, do a 'Complete Data Reset' to start from scratch
2. Select the 'Install Android' option from the main menu
3. Copy the 3 above files to the install folder after the TP is mounted
Click to expand...
Click to collapse
Flexmaen said:
I tried to follow your instructions, but I get error messages like:
Error: unrecognized/unsopported zip 'FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.3.0-1-23-17.zip'
Error: Incompatible GAPPS/ROM versions None/7.0
Click to expand...
Click to collapse
Was that error message from TP Toolbox, or from TWRP? TP Toolbox won't recognize the newer TWRP images, nor will it recognize any 7.1 ROM/Gapps, so you need to use an older version to get things started. Once the older TWRP is installed, then you can use it to update to a newer version.
All in all, I had 8 ZIP files on my HP Touchpad to get a complete 7.1.1 install, but you can do it with as few as 6:
OLD ROM: CM 12.1
OLD Gapps: 5.1
OLD TWRP: 2.8.3.0
NEW ROM: Evervolv Nightly
NEW Gapps: 7.1
NEW TWRP: 3.0.3.0 F2FS
SKZ Kernel (Optional)
SuperSU (Optional)
Thank you! I installed the latest nightly, and it works fine so far.
The only thing I noticed that some apps now are blocking the device. This was also the case with the Android 4.4 Pac-Rom I used before. So it seems that some apps are using recources that aren't working well on the Touchpad at all, or that there is a general problem in several CM-versions.
For example the current version of Google Maps is so slow, you won't use it. I installend an older version (7.7.0), and this one works very fine. Also the new version of Maps lost the WiFi connection, which didn't cause any problem with the older version. So I wonder if there is some kind of incompatibility.
Another example: Fake GPS Location is much quicker than GPS-Emulator which also got stuck from time to time. Also the current Amazon App store was slooow.
Summary: Android 7.x runs fine so far, but you have to make sure that you get rid of the apps which block the device for some reason.
7.x is very slow some times.
Flexmaen said:
Thank you! I installed the latest nightly, and it works fine so far.
The only thing I noticed that some apps now are blocking the device. This was also the case with the Android 4.4 Pac-Rom I used before. So it seems that some apps are using recources that aren't working well on the Touchpad at all, or that there is a general problem in several CM-versions.
For example the current version of Google Maps is so slow, you won't use it. I installend an older version (7.7.0), and this one works very fine. Also the new version of Maps lost the WiFi connection, which didn't cause any problem with the older version. So I wonder if there is some kind of incompatibility.
Another example: Fake GPS Location is much quicker than GPS-Emulator which also got stuck from time to time. Also the current Amazon App store was slooow.
Summary: Android 7.x runs fine so far, but you have to make sure that you get rid of the apps which block the device for some reason.
Click to expand...
Click to collapse
When you say "blocking" you mean very slow? Since I uptaded from 4.4 to 7.x I've noticed that lots of apps are very slow. Some freezes for seconds and returns only when I block the device and turn on again. I dont know if its only on mine or its normal because of the old hardware. Is there any version that run real smooth? Or other system?
giolc90 said:
When you say "blocking" you mean very slow? Since I uptaded from 4.4 to 7.x I've noticed that lots of apps are very slow. Some freezes for seconds and returns only when I block the device and turn on again. I dont know if its only on mine or its normal because of the old hardware. Is there any version that run real smooth? Or other system?
Click to expand...
Click to collapse
Yes I mean very slow. Often so slow that it takes a minute until you can change to another app.
The Problem also existed on my 4.4 Pac Rom, so I guess it's rather caused by new apps who might expect some feature, like multicore, etc. Or it is some fault, that already existed in older custom roms. Not sure. However, I can recommend downgrading apps in this case, older versions often work like normal.
Flexmaen said:
Yes I mean very slow. Often so slow that it takes a minute until you can change to another app.
The Problem also existed on my 4.4 Pac Rom, so I guess it's rather caused by new apps who might expect some feature, like multicore, etc. Or it is some fault, that already existed in older custom roms. Not sure. However, I can recommend downgrading apps in this case, older versions often work like normal.
Click to expand...
Click to collapse
Perhaps using F2FS could help, if not currently using it?
crazyates said:
Was that error message from TP Toolbox, or from TWRP? TP Toolbox won't recognize the newer TWRP images, nor will it recognize any 7.1 ROM/Gapps, so you need to use an older version to get things started. Once the older TWRP is installed, then you can use it to update to a newer version.
All in all, I had 8 ZIP files on my HP Touchpad to get a complete 7.1.1 install, but you can do it with as few as 6:
OLD ROM: CM 12.1
OLD Gapps: 5.1
OLD TWRP: 2.8.3.0
NEW ROM: Evervolv Nightly
NEW Gapps: 7.1
NEW TWRP: 3.0.3.0 F2FS
SKZ Kernel (Optional)
SuperSU (Optional)
Click to expand...
Click to collapse
I guess there is a "new" method out there that can install Nougat 7.1.1 in as little as 3 zip files!!!
check it out, it comes with instructions and a new video...
I can name that tune in 3 zips!!
DoubleStuff said:
I guess there is a "new" method out there that can install Nougat 7.1.1 in as little as 3 zip files!!!
check it out, it comes with instructions and a new video...
I can name that tune in 3 zips!!
Click to expand...
Click to collapse
It doesn't work for me ... I'm having issues . First off I like to ask why he didn't use the latest Rom ? And the part with go to the PC Mounted Touchpad internal drive for the TWRP ? When I open the TWRP folder I don't see twrps file, why not ? There nothing in this folder, its empty . What I done was just placed those zip files in the TWRP folder . Afterwards once I do the final reboot to Evervolv it will just show those Evervolv lights flashing like its trying to load up but it doesn't, it just keeps continuously trying to load but it never does
Hi everyone:
I'm an ex IT tech. but don't know that much about smartphone tech. I say that because I'll follow along quickly if people can use metaphors that relate back to PCs. I've used Linux a bit but am not a Linux expert.
I have a Droid 4 with Jelly Bean on it. I'd like to upgrade it to whatever is the most stable later custom version of Android. Do people recommend CyanogenMod 12? Some LineageOS version? Stability and having everything work as much as possible is what's most important to me. Speed would be a bonus, but it not as important as stability/functionality.
I've done the following to prepare for this:
-Taken a screenshot and put it on my PC to keep track of which version of Android I have.
-Downloaded SafeStrap 3.75, but don't know if I have the right version for this phone. Somewhere I saw something about
a special version for the Droid 4.
-I'm not sure which gapps version to download. Will later versions have more apps but be more likely to
have compatibility issues with an older version of Android?
-I know how to get into developer mode
-I know how to get into Fastboot mode
Any help would be appreciated.
Shplad said:
Hi everyone:
I'm an ex IT tech. but don't know that much about smartphone tech. I say that because I'll follow along quickly if people can use metaphors that relate back to PCs. I've used Linux a bit but am not a Linux expert.
I have a Droid 4 with Jelly Bean on it. I'd like to upgrade it to whatever is the most stable later custom version of Android. Do people recommend CyanogenMod 12? Some LineageOS version? Stability and having everything work as much as possible is what's most important to me. Speed would be a bonus, but it not as important as stability/functionality.
I've done the following to prepare for this:
-Taken a screenshot and put it on my PC to keep track of which version of Android I have.
-Downloaded SafeStrap 3.75, but don't know if I have the right version for this phone. Somewhere I saw something about
a special version for the Droid 4.
-I'm not sure which gapps version to download. Will later versions have more apps but be more likely to
have compatibility issues with an older version of Android?
-I know how to get into developer mode
-I know how to get into Fastboot mode
Any help would be appreciated.
Click to expand...
Click to collapse
see the index for correct safestrap version, 3.75 is latest, but you need the Droid 4 one
[INDEX] Development Motorola Droid 4
GApps are android version specific, opengapps.org are good
I haven't used the Droid 4 much since cm11, it's likely still a good option
sd_shadow's How-To Videos for Droid 4
Sent from my XT1254 using XDA Labs
Thanks, however I was looking for something a little more newibe-friendly. There are literally dozens and dozens of pages to read. On top of that, the link to the SafeStrap is dead, and there are circular links, all of which appear to go that dead link. As well, the page to download the patch to enable the GSM on CDMA Global phones also has dead links.
Nothing simpler?
Shplad said:
Thanks, however I was looking for something a little more newibe-friendly. There are literally dozens and dozens of pages to read. On top of that, the link to the SafeStrap is dead, and there are circular links, all of which appear to go that dead link. As well, the page to download the patch to enable the GSM on CDMA Global phones also has dead links.
Nothing simpler?
Click to expand...
Click to collapse
The link for safe strap is not dead there are two versions. One from stargo and the other is a modified safe strap for unused partitions redone by some one else. You need to look in the correct posts and thread. Here is the download: http://www.internauta37.altervista....afestrap-maserati-v3.75-unused-partitions.apk
As far as for gsm keep looking you'll probully find something. I can't help you with that because I never needed to use but it shouldn't be to hard to do or figure out.
As far as wich rom you want to use just try a few different ones and see wich one you prefer to use as a daily driver.
Shplad said:
Thanks, however I was looking for something a little more newibe-friendly. There are literally dozens and dozens of pages to read. On top of that, the link to the SafeStrap is dead, and there are circular links, all of which appear to go that dead link. As well, the page to download the patch to enable the GSM on CDMA Global phones also has dead links.
Nothing simpler?
Click to expand...
Click to collapse
Hi Shplad,
It all seems a bit overwhelming at first, but there isn't that much to it really. So, if you've got some IT experience, I'm sure you'll be fine. I always use the latest version (out of curiosity), but from what I've read, CM11 is considered pretty stable, but 12 and 13 are good too. And you'll probably find you don't need the GSM patch as it'll just work automatically - I think it was required in CM12 at one point, but that might be fixed now.
You haven't mentioned rooting. If you haven't already done that, you may as well get that done first, and it's covered in the pages that sd_shadow linked to. And I had a quick look at the links to safestrap in the pages that sd_shadow linked to, and they all seemed ok to me (as OGdroidster has just said also). You just need to make sure you've got the one with 'maserati' in the filename.
So, (from memory - could be wrong), you just need to:
- root the phone
- download your chosen rom and gapps
- install safestrap
- in safestrap install file system then boot into recovery mode
- create yourself a slot in the boot options
- make sure your new slot is the active one (it tells you at the top)
- install your chosen rom and gapps in the install section
- reboot
And if you get stuck, you could just ask, and I'm sure someone will answer pretty quickly.
Good luck
So, which versions of Android are CM11 and CM12? Can anyone else chime in and let me know if CM12 is better or more stable than CM11?
It turns out I could not download the Safestrap because my firewall was blocking some advertising/metric site which was required to go that page. Got it now.
Not sure what the GSM code you refer to is for. Will the upgraded phone with CMxx not work by default on GSM networks, or is something different?
Thanks
moodroid said:
Hi Shplad,
It all seems a bit overwhelming at first, but there isn't that much to it really. So, if you've got some IT experience, I'm sure you'll be fine. I always use the latest version (out of curiosity), but from what I've read, CM11 is considered pretty stable, but 12 and 13 are good too. And you'll probably find you don't need the GSM patch as it'll just work automatically - I think it was required in CM12 at one point, but that might be fixed now.
You haven't mentioned rooting. If you haven't already done that, you may as well get that done first, and it's covered in the pages that sd_shadow linked to. And I had a quick look at the links to safestrap in the pages that sd_shadow linked to, and they all seemed ok to me (as OGdroidster has just said also). You just need to make sure you've got the one with 'maserati' in the filename.
So, (from memory - could be wrong), you just need to:
- root the phone
- download your chosen rom and gapps
- install safestrap
- in safestrap install file system then boot into recovery mode
- create yourself a slot in the boot options
- make sure your new slot is the active one (it tells you at the top)
- install your chosen rom and gapps in the install section
- reboot
And if you get stuck, you could just ask, and I'm sure someone will answer pretty quickly.
Good luck
Click to expand...
Click to collapse
Shplad said:
So, which versions of Android are CM11 and CM12? Can anyone else chime in and let me know if CM12 is better or more stable than CM11?
It turns out I could not download the Safestrap because my firewall was blocking some advertising/metric site which was required to go that page. Got it now.
Not sure what the GSM code you refer to is for. Will the upgraded phone with CMxx not work by default on GSM networks, or is something different?
Thanks
Click to expand...
Click to collapse
CM11 is KitKat (4.4), CM12 is Lollipop (5), CM13 is Marshmallow (6) and CM14 is Nougat (7).
I was referring to the GSM patch (that you queried above). What I was saying, was that in most versions of CM, GSM automatically works, so you won't need to apply the patch. But if you did have a problem, the links seem to work fine to me.
If I was you, I'd try out a few versions and find which version you prefer, as I don't think anyone will be able to tell you which is 'best'. I would have thought you'd be fine with 11, 12 or 13 though, and because you can have multiple roms installed with safestrap, you could install all 3 if you wanted!
Thanks. I guess I wasn't aware that you could use any CM. I thought only 11 or 12 could work properly on a Droid 4. So, any of those ROMs might work?
Also, at what stage do you install the GSM patch if it is necessary?
moodroid said:
CM11 is KitKat (4.4), CM12 is Lollipop (5), CM13 is Marshmallow (6) and CM14 is Nougat (7).
I was referring to the GSM patch (that you queried above). What I was saying, was that in most versions of CM, GSM automatically works, so you won't need to apply the patch. But if you did have a problem, the links seem to work fine to me.
If I was you, I'd try out a few versions and find which version you prefer, as I don't think anyone will be able to tell you which is 'best'. I would have thought you'd be fine with 11, 12 or 13 though, and because you can have multiple roms installed with safestrap, you could install all 3 if you wanted!
Click to expand...
Click to collapse
Shplad said:
Thanks. I guess I wasn't aware that you could use any CM. I thought only 11 or 12 could work properly on a Droid 4. So, any of those ROMs might work?
Also, at what stage do you install the GSM patch if it is necessary?
Click to expand...
Click to collapse
As far as I understand it (which could be totally wrong), 11 and 12 are no longer being developed and will only receive security updates, so from that point of view, I guess they will be more stable. But 13 and 14 will work, but there may be the odd issue here and there (particularly with 14 which is still quite new). You'd have to have a quick scan through the comments to see if there's anything that's like to be a problem for you.
With reagrds to GSM, I should just try it and see if it works to begin with. If it doesn't, then download the patch, reboot, go into safestrap, install the zip then reboot.
Hi,
If you are going to use a ROM with ART (Lollipop CM12x and above) Do not use CM12. It is old, outdated, and laggy. CM13 (LineageOS 13) provides a superior experience. Once LOS 14.1 becomes official for our devices, I would highly recommend upgrading to it, as it provides superior memory management.
Sent from my Motorola Droid RAZR using XDA Labs
Wow, this is a lot to take in. Thanks. So, I don't quite understand the repercussions. Once I root, does that mean any ROM OS that boots is somewhat more vulnerable, cause it's like being logged on as root in Linux, or does it depend which ROM I'm using or something else?
Bobcus Leper said:
Hi,
If you are going to use a ROM with ART (Lollipop CM12x and above) Do not use CM12. It is old, outdated, and laggy. CM13 (LineageOS 13) provides a superior experience. Once LOS 14.1 becomes official for our devices, I would highly recommend upgrading to it, as it provided superior memory management.
Sent from my Motorola Droid RAZR using XDA Labs
Click to expand...
Click to collapse
Okay, I figured out after my last post that root status depends on which ROM you are running, and of course installing a ROM without root status would put you back to unrooted status.
I downloaded Lineage OS 13 and verified the MD5SUM. I rooted the phone using Shadow's video.
Now I want to make an image of my NAND or have some other method of restoring the stock ROM before I install a new ROM. At what stage in the process do I do that and what is the safest tool / method to do that? RSDLite? Adding another ROM slot and using Nandroid backup?
Awaiting anxiously...
Alright, I learned from Googling that RSDLite can restore a ROM to the phone directly from your PC.
Does that wipe out any upgraded, more modern ROMS that I put on the phone, such as Lineage OS 13? Is it like having multiple partitions or hard drives on a PC?
How safe is the RSDLite procedure? Can someone explain the pros/cons of doing it that way versus (as I understand it) having 2 ROMs on the NAND available? I see a lot of HOWTOs, but very few explanations/diagrams/theory. If I could relate this back to PCs, I'd be able to understand better.
Shplad said:
Alright, I learned from Googling that RSDLite can restore a ROM to the phone directly from your PC.
Does that wipe out any upgraded, more modern ROMS that I put on the phone, such as Lineage OS 13? Is it like having multiple partitions or hard drives on a PC?
How safe is the RSDLite procedure? Can someone explain the pros/cons of doing it that way versus (as I understand it) having 2 ROMs on the NAND available? I see a lot of HOWTOs, but very few explanations/diagrams/theory. If I could relate this back to PCs, I'd be able to understand better.
Click to expand...
Click to collapse
As far as I understand it, and again, this could be wrong, using RSDLite is usually a last resort in the unlikely event that you've completely messed up your phone. You will lose everything, and your phone will back to how it was when you bought it. I've never needed to use RSDLite myself, but from what I've read, it's a pretty reliable way to get your phone working again. As long as you follow all the instructions, and install CM (LOS) 13 into another slot, it's very unlikely that you'll damage your original stock rom and you'll still be able to boot into if ever you need to. Hopefully, someone who knows more about it will comment also...
I got Safestrap 3.75 special version for unused partitions installed. I didn't realize it allows you to make TWRP ROM backups.
I made a backup of the stock ROM. The first time I did that, I got an error stating it couldn't find or access /boot.
Strangely, the second time I tried, it seemed to work fine.
I copied the folder with the stock ROM backup to my PC, just in case. I managed to flash with Lineage OS 13. It booted fine, but I forgot to select the Gapps zip as well. It does not appear to be rooted after bootup.
1. Do I need to reinstall Lineage 13 or is there way to install the apps without reinstalling Lineage?
2. What is the normal state of this ROM? I'm not sure if I have to root Lineage 13. If I don't enable root, will I be unable to run TWRP recovery and add the Gapps zip file and reinstall? I don't want to be stuck with a successful Lineage install and no apps. I'd find another way to install the apps, but I'm guessing you can't without the apps themselves, no?
Help!
Okay, I figured out how to install just gapps 5.1-2015-05-23-24 . However, during configuration, I cannot get the phone to connect to gmail via WiFi (I don't have a data plan).
"Validating Server Settings...
Couldn't open connection to server."
I see other people had this in other version of Android. Is this a particular problem in Lineage 13? Any solutions known?
...AAAANDDD Google Play Services has closed.
Hmm...this does not seem very stable at all. Has anyone actually tried Lineage 13 on this phone or was it just a guess that it might work?
EDIT:
I tried these suggestions, just in case.
https://productforums.google.com/forum/#!topic/gmail/ACSvDiQoufI
Now, I'm getting the error:
"Problem with account setup
Username or password is incorrect"
Google Play Services keeps closing. Should I uninstall the gapps and install a more compatible one? I think network connectivity is not stable.
Shplad said:
Hmm...this does not seem very stable at all. Has anyone actually tried Lineage 13 on this phone or was it just a guess that it might work?
Click to expand...
Click to collapse
Hi. I don't use gapps, and I'm uisng LOS 14 myself. But there's 57 pages of comments for LOS 13, so I think it's fair to say people have tried it! Now you've got it installed, you could post in the LOS 13 thread, and ask people which version of gapps they are using.
P.S. The first post in the Droid 4 LOS 13 thread appears to suggest using OpenGApps and has some details on how to install, or you could read through that thread for other tips.
moodroid:
Thanks, but on which website? There are quite a few Lineage OS forums.
moodroid said:
Hi. I don't use gapps, and I'm uisng LOS 14 myself. But there's 57 pages of comments for LOS 13, so I think it's fair to say people have tried it! Now you've got it installed, you could post in the LOS 13 thread, and ask people which version of gapps they are using.
P.S. The first post in the Droid 4 LOS 13 thread appears to suggest using OpenGApps and has some details on how to install, or you could read through that thread for other tips.
Click to expand...
Click to collapse
Shplad said:
moodroid:
Thanks, but on which website? There are quite a few Lineage OS forums.
Click to expand...
Click to collapse
I meant on this website. In the 'Droid 4 Android Development' section (https://forum.xda-developers.com/droid-4/development), there a thread for each of the roms. The one for CM (LOS) 13 is https://forum.xda-developers.com/droid-4/development/cm13-0-marshmallow-unofficial-builds-t3270938
moo:
Thanks for that. I didn't post there earlier because I thought it was only for developer reports of bugs, and my coding skills are exactly zero. Should I wait to see what happens in that other thread and not post back here until I hear something from there?