Most stable Custom ROM upgrade and HOWTO for Droid 4 - Motorola Droid 4

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?

Related

Help and Advice for First Time Attempt at Rooting

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.

Is there any OS that works ?

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

Zenfone Go Oreo help

Hi someone with an account on 4dpa with 30 posts could please download this rom and share it here? I don't know Russian so it's impossible for me to write 30 posts.
I have a Zenfone Go (Z00VD) and the stock ROM it's terrible (crash in the camera, 1 Gigabyte of app space already full....)
In case you can't, could you provide an alternative ROM with as less bugs as possible?
Thank you
Original Thread 4pda
Translated Google
Guess we're on the same boat buddy. Have you tried the other ROMs on their forum like the nougat ones? They seem nice.
I personally prefer to use the RR 5.5.9 lollipop rom provided by 4pda since for some reason the nougat and marshmallow roms on their site just give me bootloops. It may be different for you though.
JustAnormalGuy said:
Guess we're on the same boat buddy. Have you tried the other ROMs on their forum like the nougat ones? They seem nice.
I personally prefer to use the RR 5.5.9 lollipop rom provided by 4pda since for some reason the nougat and marshmallow roms on their site just give me bootloops. It may be different for you though.
Click to expand...
Click to collapse
Hi, not yet, it's not my phone so I'm searching a stable ROM. I saw the nougat thread here but it's not very clear what works and what not, there seems to be a nougat rom on 4dpa which should work well except the videocamera with the stock app, but the Oreo one seems almost bug free although more complex to install. Unfortunately I can't access it.
Hello,
From what I can tell, both Oreo and Nougat ROMs were unstable and/or sluggish for me, so I'd recommend to stick to Marshmallow based ROMs(for now). My personal preference is ResRemix 5.7.4, but if you decide to try any of them, keep in mind that ROMs with kernel 3.18.19(as far as I've seen most of ROMs in that thread) all have these two issues that I was able to find so far:
Notification LED doesn't work
Bluetooth audio doesn't work either
Other than that, the ROM is super-stable and somehow better than 5.1.1 ROMs from official dev thread there.
And for JustAnormalGuy, bootloops in later ROMs seem to happen because of unwiped internal storage(basicly needs entire /data partition wiped somewhy). Try marking the 'Internal SD' option when wiping partitions for ROM installing.
Good luck!
aurismat said:
Hello,
From what I can tell, both Oreo and Nougat ROMs were unstable and/or sluggish for me, so I'd recommend to stick to Marshmallow based ROMs(for now). My personal preference is ResRemix 5.7.4, but if you decide to try any of them, keep in mind that ROMs with kernel 3.18.19(as far as I've seen most of ROMs in that thread) all have these two issues that I was able to find so far:
Notification LED doesn't work
Bluetooth audio doesn't work either
Other than that, the ROM is super-stable and somehow better than 5.1.1 ROMs from official dev thread there.
And for JustAnormalGuy, bootloops in later ROMs seem to happen because of unwiped internal storage(basicly needs entire /data partition wiped somewhy). Try marking the 'Internal SD' option when wiping partitions for ROM installing.
Good luck!
Click to expand...
Click to collapse
Those 2 bugs are not a deal breaker for me, would you mind linking to the ResRemix 5.7.4 rom that you used?
Sure, buut since I can't post links(thanks XDA for 10 post restriction, love ya!), I'll have to send one another way.
PM me your Discord handle(if you have one) or something else. I should be able to send you the link there.
aurismat, and what version of twrp do you use ?
I use TWRP 3.0 by Jemmini. It's been a *long* time since I installed it though, so if you have something different, I'm afraid I won't be of much help unless I'll be able to pull my recovery .img file.
Actually, i use the same version. Problem is most probably my method of root. The common method of rooting for our device didn't include any flashing with sp flash tool. But for my situation, my bootloader is locked even after downgrading. So i did the other method (also found on the forum) in which includes flashing.
Hmm, it *may* be the root method, may be also the locked bootloader.
If I recall right(and this might be THE common way), I used the fastboot method from XDA, and I knew it'd work cause I rooted more phones that way. I remember downgrading the stock ROM down to version 39(i think that one still had the bootloader check in dev options) and then trying to unlock the bootloader and obviously go through flashing the recovery image.
Dunno what might be the issue with your way of flashing, though. AFAIK might be anything from leftover files to bootloader giving the finger.
@aurismat i think the problem might be that i used the "format all + download" option on sp flash tool. Does that affect the phone in any way that deprives my phone from using 6.0 - 7.0 roms? (Besides the "null" imei effect)
@JustAnormalGuy I don't think it should be a problem, because the ROM .zips install their own stuff to the partitions AFAIK, so even if Flashtool wipes everything, it should still be fine. Try doing one of them ROMs(previously said ResRemix worked for me), but remember to wipe the Internal Storage partition if you can.
Oh and remember to take a backup of your current ROM, should it bootloop again at least you won't have to do the hassle of reinstalling everything back(learned that the hard eay haha).
EDIT: was it just Nougat ROMs that you were trying or was it both Nougat and Marshmallow? Not sure what might be the cause, but the ROMs developed under the same kernel from ska-vova in 4PDA worked for me. Just a thought.
well actually i already tried various roms from Marshmallow to Nougat all of which gave me bootloops. I've already followed the steps of installation as written. However, i tried once installing a Marshmallow rom from the facebook group named "ASUS Zenfone Go Indonesia" and it surpisingly worked for me (numerous bugs present however), as well as most of the marshmallow (and only marshamallow roms) on their group.
The thing is I also might think one of the reasons why i get the bootloops in the roms from the 4pda forum is the kernel used in them. (just speculation) Should it be correct to assume that ?
As I recall:
Working rom shows "kernel version > [email protected]"
Not working rom - "kernel version > [email protected]"
Hmm, I'm using [email protected] kernel version 3.18.19.
All the ROMs there seem to be by mosly nik-kst's kernel. ska-vova seems to just build ROMs with the kernel.
Besides, take note from the working ROM - it's also from 4PDA.
Only thing I can speculate is that your device is somewhat different(maybe different hardware, not sure) and hence why it gives you BLs.
Dunno, this case is a tough cookie to be honest - only thing I can recommend at this point is to flash literally EVERYTHING back to stock and try using fastboot method to get recovery and root back.
Hey @Darkorn,
Over the span of a few days, I've tried installing 4PDA's Oreo ROM.
It took me a good couple of headaches to make out what translated Russian meant in the instructions, but I've managed to repartition the entire device to the guide.
Seems to work properly so far, hell even Bluetooth and Notification LED issues from older ROMs seem to be fixed!
Though one thing that annoys me *personally* is that it's impossible to install SuperSU, so you're stuck with Magisk. It's not the end of the world, though, as long as you don't care about SafetyNet's BS.
Oh and @JustAnormalGuy, try repartitioning your device according to the Oreo instructions in 4PDA, that might be the solution for ya.
If I ever get up to 10 posts I'll ask those guys permission to let me post the tutorial here with all the links(hopefully).
Until then, good luck to both of ya!
aurismat said:
Hey @Darkorn,
Over the span of a few days, I've tried installing 4PDA's Oreo ROM.
It took me a good couple of headaches to make out what translated Russian meant in the instructions, but I've managed to repartition the entire device to the guide.
Seems to work properly so far, hell even Bluetooth and Notification LED issues from older ROMs seem to be fixed!
Though one thing that annoys me *personally* is that it's impossible to install SuperSU, so you're stuck with Magisk. It's not the end of the world, though, as long as you don't care about SafetyNet's BS.
Oh and @JustAnormalGuy, try repartitioning your device according to the Oreo instructions in 4PDA, that might be the solution for ya.
If I ever get up to 10 posts I'll ask those guys permission to let me post the tutorial here with all the links(hopefully).
Until then, good luck to both of ya!
Click to expand...
Click to collapse
Nice! Resurrection Remix is working too well to bother, but who knows in a few months!
That would be great man, thanks !!

[Help] Unable to use custom ROMs on brand new 3T (touch non responsive once woken)

So about 3 weeks ago my 2 year old 3T just stopped working out of nowhere. I debated on whether to upgrade for over a week, but eventually decided to replace it with the same, just to have the familiar ROM, & not to have to learn anything new or mess with anything else, since I'm going through a lot of personal stuff right now. Anyway, I got the phone over a week ago and I've tried everything since then to get it running something beside OOS to no avail. Every single time it goes to sleep in another ROM, once I wake it up, touch is no longer responsive. I can't for the life of me figure out why. I have tried so many different things, in so many different ways. I know it might sound ridiculous but at this point I'm just in tears... I really need a functional phone, and I never would have bought another OP3T if I knew I'd be stuck with OOS....
The process I went through as soon as I got it:
Unfortunately I don't remember the version of OOS that it came with
- Unlock bootloader
- Flash TWRP (twrp-3.0.4-1 due to a thread I came across and was confused by)
- Wipe everything
- Flash recommended firmware for my ROM (posted in the ROM's thread)
- Flash my favorite ROM (Unofficial RR)
- Flash Magisk
- Boot, everything seems fine, screen goes off, turn it back on, unable to use touchscreen anymore.
I then used the unbrick tool, and tried again. Same problem. Used unbrick tool, unlocked bootloader, this time tried to flash this unofficial Lineage . Booted. It went to sleep. Woke up. Touchscreen nonfunctional.
I shut it down. Unbrick tool. This time I let it update itself all the way up to the very latest version of OOS. I go through the entire process again, this time flashing TWRP 3.2.1.0, it's the same thing. I've tried going up to open beta and then flashing my roms. I've tried flashing the rom without firmware, without magisk. With gapps. Without gapps. I always format and wipe everything. I also tried this on the off chance it might work.... I have seriously done the process every way imaginable, over twenty times since I got the phone last week.... nothing ever works. I also just tried Cyanogenmod, but it wouldn't flash at all.
I don't know what to do anymore. I just want to have a phone that I don't hate. At this point, I am too tired and I've got too much going on to figure this out on my own anymore. I would be grateful to pay someone at this point just to help me get this working honestly.... so if there's anyone out there who knows how to fix this, please let me know
Did you buy a new unit from somewhere or did you get a second hand unit ? In the latter case, the person who owned the device before you might have replaced the display for whatever reason, replaced displays often run into these kind of issues.
Also, does this happen on all the ROMs ? It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess). Try flashing a newer, latest updated pie rom and see how that works out.
Mizart said:
It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess).
Click to expand...
Click to collapse
What does that even mean? Sounds like you are just making stuff up.
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
SpaceOctopus said:
I shut it down. Unbrick tool. This time I let it update itself all the way up to the very latest version of OOS.
Click to expand...
Click to collapse
At any point, did you flash a full OOS zip (over 1 GB) and not just update patches? That is where I would start, to make sure it's one a completely stock baseline (including firmware, etc.).
You can get the latest full update zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
@SpaceOctopus
I would try a newer firmware like the
Stable5.0.8 Firmware+Modem_OnePlus3T.zip
I would also recommend the latest TWRP = twrp-3.3.0-1-oneplus3.img
if still not working definitely flash the flash a full OOS zip from the post above which is 5.0.8
else you should try making the jump to a 9.0 PIE ROM, I see an official and unofficial RR if that is your goto ROM, easy to locate in the [INDEX] ROMs, Kernels & Misc. for 3/3T thread
.
Mizart said:
Did you buy a new unit from somewhere or did you get a second hand unit ? In the latter case, the person who owned the device before you might have replaced the display for whatever reason, replaced displays often run into these kind of issues.
Also, does this happen on all the ROMs ? It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess). Try flashing a newer, latest updated pie rom and see how that works out.
Click to expand...
Click to collapse
Brand new from ebay. Sealed in the box.
I did try flashing a more recent version of resurrection remix, but it failed. Any recommendations?
redpoint73 said:
What does that even mean? Sounds like you are just making stuff up.
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
At any point, did you flash a full OOS zip (over 1 GB) and not just update patches? That is where I would start, to make sure it's one a completely stock baseline (including firmware, etc.).
You can get the latest full update zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Click to expand...
Click to collapse
I mean, does using the unbrick tool count? I think it completely flashes everything back to stock. Granted it's a very old version of OOS, but either way I will try that next just in case. Thank you.
hhp_211 said:
@SpaceOctopus
I would try a newer firmware like the
Stable5.0.8 Firmware+Modem_OnePlus3T.zip
I would also recommend the latest TWRP = twrp-3.3.0-1-oneplus3.img
if still not working definitely flash the flash a full OOS zip from the post above which is 5.0.8
else you should try making the jump to a 9.0 PIE ROM, I see an official and unofficial RR if that is your goto ROM, easy to locate in the [INDEX] ROMs, Kernels & Misc. for 3/3T thread
.
Click to expand...
Click to collapse
I did try that TWRP eventually. No change. I would probably have switched to pie a while ago, except one small thing. There's an xposed module I'm really attached to, and as far as I'm aware, xposed isn't available on pie? Or at least that's what I've heard/read. It's the xprivacy lua module that lets you control every type of data an app has access to. I think I've tried looking for an alternative and there aren't any, either. :'( You know, sometimes it's just that one small thing... lol
However, I did try to install the most recent version of RR yesterday, and it failed flashing. Don't know why. I'm going to try again after flashing the firmware. Maybe it'll work this time.
Anyway, I'm also going to try what you all have recommended and see what happens. Hopefully something happens. Thank you much for your help
Ok, well, this time it let me install Resurrection Remix latest version. It may not be exactly what I wanted, but it's pretty goddamn close, and it sure as hell isn't OOS! lol
Thanks for your help everyone! I really appreciate it. I do still really wish I knew wtf was happening honestly with it not properly running nougat ROM's, but hey, this works for me. It won't make me want to toss it in a dumpster and set it on fire every time I pick it up. :laugh: :laugh: :laugh:
Maybe I can get someone to figure it out in the future or something, I don't know. I sure wish someone would convert that xprivacy module to work with Magisk though! I'm surprised nobody has even made an alternative or an app or anything like it really.
SpaceOctopus said:
I mean, does using the unbrick tool count? I think it completely flashes everything back to stock. Granted it's a very old version of OOS, but either way I will try that next just in case.
Click to expand...
Click to collapse
I think the unbrick tool does flash the full OOS. But honestly not 100% sure, as I have never actually had to use the unbrick tool (knock on wood!). Which is one reason I decided to pose that as a question.
In any case, if the unbrick did flash an old OOS, best to replace with newer version (or at least the firmware). Updated firmware typically plays better with the current custom ROMs. And old firmware is often a culprit when random bugs occur after flashing a custom ROM. So again, flashing firmware and/or the full update zip (which also flashes the firmware) is best practice in such cases. And if you are in any doubt about the OOS version or corresponding firmware that was installed, it probably doesn't hurt to flash again.

[Discussion] Resurrection Remix 7 for Hammerhead (Android 9 Pie)

Hello everyone. I am opening this thread for the sake of convenience of us users of this ROM so that we stop hijacking the Oreo version thread and have a "clean" place where we can discuss about our experience with this great ROM. So I suggest anything regarding this ROM to be posted here!
You can find the official builds here: https://get.resurrectionremix.com/?dir=hammerhead
DISCLAIMER: I am by no means a developer or maintainer of this ROM, so this cannot be considered an official support thread, just conversation, plain and simple! Moderators can close this thread as soon as an official support thread opens.
Cheers!
I just installed the rom,came from stock. My first impressions are:
-It took 2 reboots to get the camera working. Installed google camera app since the integrated one doesnt show up on app drawer(you can access it from lockscreen though) and it seems to work kinda bad(picture goes black on it sometimes).
-It runs a bit hotter than stock rom. It might be just me though,I have opened the phone a few times to fix the power button which seems to get stuck for me once in a while.
-The default DPI doesn't seem right,everything looks a little bit smaller than it does on stock rom. There is an option to change it though, I set mine to 380 and it looks about right.
I haven't found any other issues yet.
Another note,I think the rom fixed my notification led lol. It didn't work for me on stock rom for some reason.
Pretty good rom overall,I haven't faced any stability issues yet.
edit: Is there any way to lower the resolution?
I upgraded from RR's Oreo build. Before flashing I repartitioned the phone using the method described here and the even more detailed instructions posted by douguluskaien on page 12 of that thread. The flash went very smoothly and although the phone initially ran hot it cooled back to normal after a few hours of what was probably background processing. With the 1.5G system partition I was able to install the micro version of GAPPS. I've had that experience after flashing new ROMs on other phones as well. I also discovered the bundled camera doesn't work and installed Google Camera. After starting up Google Camera, the original camera worked also. I tried connecting bluetooth headphones, and even though I could pair the headset I couldn't get the phone to send audio - it just kept playing through the phone speaker. I also found the default font size a little small, but changing it to Large in the Font Size menu got it back to what seems like normal.
I have one major issue which I realize is not directly related to the ROM. A custom version of TWRP is required to support the non-standard partitions, and that version is based on TWRP 3.2.3 and doesn't support device encryption. Does anyone know if an updated TWRP will be available that will allow me to encrypt the phone and still do recovery-related stuff?
In summary, this is impressively well along for a build that's only been live for a couple of weeks. This isn't my daily driver so I don't need absolute stability, so this is plenty for me for now. I just won't leave the house with it until I can encrypt.
I've been using this ROM for about a month now as a daily driver, so here's my feedback:
ROM is very nice and smooth and feature rich (as expected for RR). I installed it with Opengapps nano, rooted with Magisk. It works very well with the Pixel launcher I grabbed from here.
Some drawbacks I noticed:
Battery life is rather bad. I get 1h30m SOT at best with very mild usage (mostly site browsing and a little bit of social apps and YT video watching) . Then again I am still using the 5yr old battery that came with the phone...
The phone runs very hot (too hot to hold!) after using it for some time. It cools down rather fast if you let it be for a while, though.
Sometimes the camera is crashing (the notorious "can't connect to camera" error). usually a reboot fixes this.
Sometimes it takes a while for the device to wake up after pressing the power button.
I got some soft reboots under device heavy load. Mostly I get them when using the Rocket player music app, and it tries to load a large music folder. Phone freezes, then soft reboots.
SElinux is set to permissive and the build is signed with test keys. Maybe the first thing is caused by the latter, I don't know really....
Overall, it is a good ROM with room for improvement. However, I am concerned about its maintenance status. No update since May 14, so I keep my fingers crossed.
New build (28/07) uploaded!
hammerheadache said:
New build (28/07) uploaded!
Click to expand...
Click to collapse
I am not able to install it giving me ERROR 7
hammerheadache said:
New build (28/07) uploaded!
Click to expand...
Click to collapse
Do you know about change log??
What features added?
I want to update it tonight
As I state at the first post, I am not a developer, neither I have any involvement in this project and the people behind it. So I can't provide any support apart from my experience as a user.
sacmat said:
I am not able to install it giving me ERROR 7
Click to expand...
Click to collapse
I didn't flash this build so I don't know if it works or not. I have switched to a different ROM. However, could you elaborate? Do you come from another ROM? Did you dirty flash? Is your device repartitioned? Usually error 7 in TWRP means there's not enough system space...
m.morcielago said:
Do you know about change log??
What features added?
I want to update it tonight
Click to expand...
Click to collapse
I do not see any changelog file on the download page. Unfortunately with no official support thread, there are no official answers as well...
I flashed this build this morning by dirty way
Unfortunately Bluetooth is not working
It can find the other devices but can not connect to them
1- How can I fix it?
2-How can I downgrade to previous build?
hammerheadache said:
As I state at the first post, I am not a developer, neither I have any involvement in this project and the people behind it. So I can't provide any support apart from my experience as a user.
I didn't flash this build so I don't know if it works or not. I have switched to a different ROM. However, could you elaborate? Do you come from another ROM? Did you dirty flash? Is your device repartitioned? Usually error 7 in TWRP means there's not enough system space...
I do not see any changelog file on the download page. Unfortunately with no official support thread, there are no official answers as well...
Click to expand...
Click to collapse
Thanks for the idea, I had just repartitioned, so I had format my entire phone, (before that i had taken the backup ), and I had successfully installed the rom, I got an strange issue of WIFI connectivity, as I am not able to connect to my wifi which is having Hidden SSID, but i am successfully connected with the hotspot from my another primary phone. i haven't tested the bluetooth yet.
I dirty flashed the new build this morning. Haven't tried bluetooth or camera yet, but Wifi is working fine. As usual, the phone heated up for about a half hour after the flash and then the temp dropped and stabilized. Battery life is not great, like the May build, and there is often a long delay responding to the power button, especially shortly after power-up, but the build seems pretty solid.
Casting isn't finding anything to cast to in the most recent build. Camera worked fine.
New build available (Aug 4) as seen at ROM's dl page.
Bluetooth pairing now working for me on last release
Hi installed this ROM in clean maner but i got intermitent issue with sim card. Not sure if it is only sim issue or reboot but phone ask my pin code.
Looks like @voidz777 is the maintainer for RR Pie as well:
https://github.com/ResurrectionRemix-Devices/api/commit/8388c5df5069cf04df04facbdc22a2bfd8890185
New build (09/08) in case someone missed it... Link in OP
sacmat said:
I am not able to install it giving me ERROR 7
Click to expand...
Click to collapse
okay so to fix this you will have to repartition your system.
This thread will help you. https://forum.xda-developers.com/go...ment/repartition-nexus-5-repartition-t3844395
Repartitioning is the fix to error 70 while flashing gapps as well as error 7.
New build (Sep 16) available! Link in OP.
princeknockouts said:
okay so to fix this you will have to repartition your system.
This thread will help you. https://forum.xda-developers.com/go...ment/repartition-nexus-5-repartition-t3844395
Repartitioning is the fix to error 70 while flashing gapps as well as error 7.
Click to expand...
Click to collapse
Thank you for the tip, I followed the thread and was able to install RR 7 without any trouble. This might not be the right place to ask, but would you have any info on how to install SuperSU on RR 7, or is there perhaps another root method that we must use? Thanks in advance, I can't seem to find information on it anywhere and rather than continuing to bang my head against the wall I thought I'd ask.

Categories

Resources