Database Users

[ROM][CM10.2][RECOVERY][KERNEL][DEV][SGH-I757M]UNOFFICIAL CM10.2 For Bell SGH-I757M

CM10.2 for Canadian Samsung Galaxy S2 HD LTE (SGH-I757M)
Code:
[COLOR="red"][B][SIZE="4"]*** Disclamer ***[/SIZE][/B]
THIS ROM IS FOR THE CANADIAN SGH-I757M ONLY... DO NOT FLASH IT ON ANOTHER DEVICE!
By flashing this ROM, you are voiding your phones warranty (Unless you return it
to complete stock which is possible, but beyond the scope of this thread). You
also agree that I will in no way be held responsible in the event that your
device becomes bricked (Not likely to happen). In addition, you are responsible
to take the necessary backups of your apps, data, sms, contacts, calendar events, etc.
If you agree, then please continue on ;)[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RECOVERY REQUIRED ***[/SIZE][/B]
Due to the addition of user control in CM10.1/CM10.2, you are required to update
your recovery to a supported recovery. As of this writing, the latest available
version is CWM6.0.3.9/Philz5.18.4 for the SGH-I757M.
If you flash the new ROM with the old incompatible recovery, you risk loosing
your sdcard under a bunch of subfolders.[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RADIO FIRMWARE REQUIRED ***[/SIZE][/B]
As of CM10.1, ICS radios (I757MUGLH2) are no longer supported. You must download the new JB radios (I757MUGMC5).[/COLOR]
Introduction
It's finally here :-D CM10.2 (Android4.3.x) for the Bell Canada Samsung Galaxy S2 HD LTE (SGH-I757M). Among the most notable new features are new adreno graphics drivers with triple buffering (this is project butter). More desired may be the new privacy manager features that allow you to control, on a per app basis, which information you wish to share. Other improvements include an improved lockscreen cLock and a new integrated Superuser.
Click to expand...
Click to collapse
Images
SEE SCREENSHOTS TAB AT THE TOP OF THIS PAGE.
Click to expand...
Click to collapse
What Works
* Phone
* Wi-Fi
* Mobile
* GPS
* Bluetooth
* SMS/MMS
* Data Usage
* Camera/Camcorder
* BLN Notification (Enabled in Advanced Device Settings)
* VM Notification
* Youtube Overlays
* init.d is fully supported
Click to expand...
Click to collapse
What Doesn't Work
* I experienced an incompatibility with some of my existing mp4 media files and when gallery tries to load them they cause a soft reboot. Loading these videos into the gallery media player using a 3rd party file manager seems to work without issue, it is the loading of the preview in gallery that causes the phone to crash.
Solution: The solution is to use a file manager to move the mp4 files to a new directory and add a ".nomedia" file to that directory so that when browsing photos in the gallery, it does not try to load the offending mp4 files.
* When unlocking the screen, sometimes only the capacitative buttons light up, and the screen doesn't come on. This seems to happen about 80% of the time.
Solution: This can be fixed by locking the screen, then unlocking it again. In about 5% of these cases the screen does not come on again. Just repeat the steps again until it does.
This has been fixed as of build 20131029
* You may notice a screen flicker when you first flash this ROM. This is due to a bug where the system can't decide whether to render the graphics with the cpu or the gpu, thus the flicker.
Solution: This is fixed by turning on Settings -> Developer Options -> Disable HW Overlays (You must first enable Developer Options by pressing 7 times on Settings -> About Phone -> Build Number). This will be reset on every boot. if you install Universal Init.d, my 91fixoverlays script will run on each boot and fix this automatically.
This has been fixed as of build 20131029
Click to expand...
Click to collapse
Pre-Installation instructions
1) Download to your sdcard, the new CWM6.0.3.9 flashable zip which is compatible with CM10.1/CM10.2
2) Enter your existing CWM Recovery
3) Install Zip From sdcard
4) Select the CWM_RECOVERY_6.0.3.9_I757M_20131005.zip that you downloaded to your sdcard
5) Flash the new Recovery
6) Go back to the main recovery menu and go Advanced -> Reboot Recovery (This might not actually reboot you into recovery, you may have to do that manually by turning off phone and using 3-button combo)
Click to expand...
Click to collapse
Now that you have the new recovery flashed to your device, you can continue to install this ROM.
Please be aware that the new recovery detects your sdcards (internal/external) in a different way. Your internal sdcard is recognized as /storage/sdcard0 and your external sdcard is recognized as /storage/sdcard1.
Installation instructions
1) Download the Rom and Gapps (Use only the Gapps downloded from this thread. It is customized due to our small cache partition)
2) Enter CWM
3) TAKE A NANDROID BACKUP
4) Wipe Data/Factory Reset
5) Format Cache
6) Advanced -> Format Dalvik Cache
7) Mounts and Storage -> Format /data,/cache and /system (Required for a clean flash)
8) Flash the Radios
9) Flash the ROM
10) Flash the Gapps
11) Reboot Phone
Click to expand...
Click to collapse
NOTE: If you are using Philz Touch/Advanced Recovery, you can replace steps 5 - 7 by selecting the "Clean to install a new ROM" option.
Download
ROM Downloads
Build: 20140224 (Latest)
ROM: cm-10.2-20140224-UNOFFICIAL-celoxhd.zip (185.4MB)
GAPPS: gapps-jb-20140224-signed.zip (106.5MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
NOTE: A dirty flash should work for upgrading , but a clean flash is highly recommended
Build: 20140120
ROM: cm-10.2-20140120-UNOFFICIAL-celoxhd.zip (185.4MB)
GAPPS: gapps-jb-20131231-signed.zip (103.8MB)
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Recovery Downloads
NEW CWM6.0.3.9 compatible with CM10.1/CM10.2
CWM_RECOVERY_6.0.3.9_I757M_20131005.zip (7.6MB)
NEW Philz Advanced Recovery 5.18.4 (CWM 6.0.4.4) compatible with CM10.1/CM10.2
PhilzAdvancedRecovery5.18.4-CWM6.0.4.4-SGH-I757M.zip (9.5MB)
NEW *** RECOMMENDED *** Philz Touch Recovery 6 (CWM 6.0.4.5) compatible with CM10.1/CM10.2/CM11.0
[celoxhd][SGH-I757M][CWM Advanced Edition] PhilZ Touch
* The downloads can also be found here on XDA. Use the "Download" tab at the top of the page to access both direct download or torrent download of this ROM.
Click to expand...
Click to collapse
Tips and Tricks
Checkout the second post for some tips and tricks on setting up the ROM.
Click to expand...
Click to collapse
Changelog
Code:
[B]December 23, 2013 - Build 20131223[/B]
* Revert build.prop to use dyn instead of gpu (less problems)
* Added back 91fixoverlays to /system/etc/init.d to disable hw overlays and fix screen flicker on boot
* Re-worked 91fixoverlays script so that it now runs in it's own shell to stop it from blocking other startup scripts and causing a laggy boot
* Fixed up device tree code including adding the correct definitions for boot animation size and update to the build fingerprint
* Synced latest changes from CyanogenMod
[B]December 1, 2013 - Build 20131201[/B]
* Force gpu rendering in build.prop
* Improve fix for screen on delay
* Synced latest changes from CyanogenMod
* Updated GAPPS
[B]October 29, 2013 - Build 20131029[/B]
* Tweaked build.prop to fix screen flicker and notification drawer lockup
* Fixed screen unlock bug - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/5e163ff0c5d90a4518cbc9e14c86dceec095c70a"]Commit 5e163ff0c5d90a4518cbc9e14c86dceec095c70a[/URL]
* Added SmartAssV2 Governor - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/511e45206bb9a1454a0c43b3d626749c1fa2c241"]Commit 511e45206bb9a1454a0c43b3d626749c1fa2c241[/URL]
* Added Adaptive Governor - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/7f40cc5808bad6dafc6b351b93b3d0ccbd0777a6"]Commit 7f40cc5808bad6dafc6b351b93b3d0ccbd0777a6[/URL]
* Added Lagfree Governor - [URL="https://github.com/titanic-fanatic/android_kernel_samsung_msm8660-common/commit/d1392017601d27303fbce9da18d2af718e7e1a65"]Commit d1392017601d27303fbce9da18d2af718e7e1a65[/URL]
* Restore Advanced Device Settings - [URL="https://github.com/titanic-fanatic/android_device_samsung_msm8660-common/commit/3126c17c6165c7d96abde4cd7459769e165aa195"]Commit 3126c17c6165c7d96abde4cd7459769e165aa195[/URL] / [URL="https://github.com/titanic-fanatic/android_packages_apps_Settings/commit/9031ffb1f4e4185f397724a27e3d75afe7fd67e4"]Commit 9031ffb1f4e4185f397724a27e3d75afe7fd67e4[/URL]
[B]October 5, 2013 - Build 20131003[/B]
* Initial release
Click to expand...
Click to collapse
FAQ
Q. How do I install SuperSu?
A. Install the latest version from the market, and also make sure you have Universal Init.d installed and active. Then open SuperSU and when it asks you to update the superuser binary, answer yes and make sure you select the "TWRP/CWM" method. This will reboot your phone into receovery where the superuser binary will be updated and the su daemon script added. When your phone reboots, recovery will warn you that your device may possibly be unrooted. This is because of the install-recovery.sh script that is required to start the superuser daemon which allows SuperSu to manage superuser permissions. You are not unrooted ;-)
If your having difficulties getting SuperSu installed, try downloading the flashable zip and manually flashing it to your phone.
UPDATE-SuperSU-v1.65.zip
* Thanks to @formercontra for this tip *
* Make sure this is the way in which you want to manage superuser permissions as I have not yet found a way to revert to the integrated superuser without having to re-flash the rom
Q. How do I access Developer Options?
A. Go to Settings -> About Phone and scroll to the bottom. Press the Build number 7 times to activate the Developer Options.
Q. Why is my screen flickering?
A. There is a bug in this ROM where the board can't decide whether to display the frames with the cpu or the gpu, thus the flickering while it resolves the issue. To fix it, disable HW Overlays in Developer Options. This needs to be set on every boot unless you are running Universal Init.d and my 91fixoverlays script is present in the /system/etc/init.d folder.
Q. When I unlock my screen, my menu/home/back/search buttons come on but the screen is black?
A. This is a known bug in this ROM and is on the list of things that need to be fixed. For now, when this happens, just lock the screen, then unlock it again and the display should come back. If it does not, repeat until it does (the most number of times i had to do that was 3).
Q. I was browsing my pictures/videos in the gallery and my phone rebooted?
A. This seems to be caused by the gallery trying to generate a preview from the first frame of an mp4 created on older versions. Simply move the mp4's to a different directory with a file manager and add a ".nomedia" file to the folder to stop the gallery from trying to scan them. To open them, open with a filemanager and then select the gallery media player and it will play without issue.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* CyanogenMod Team - ROM Base
Without all of the hard work and efforts of the CyanogenMod team, this ROM would not be possible, so we owe them our thanks for providing us with such excellent ROMs.
In addition, I have received a lot of help on my journey to understand and be able to develop for the android platform, so I owe the following people my thanks for helping me to make this ROM possible.
* [user=673068]@dsixda[/user] - Initial port of CM9/CM10 for SGH-I757M
* [user=4974935]@Strange Peer[/user] - Continued development of CM10
* [user=3478918]@rukusx7[/user] - Contributor
* [user=4435341]@bijon440[/user] - Contributor
* [user=4036181]@kj2112[/user] - Contributor
* [user=5077807]@Tronith[/user] - Contributor
* [user=3651088]@Zippy Dufus[/user] - Contributor
* @formercontra - Contributor
Thanks guys you've all been so awesome to work with ;)
One last group of people to thank. It's YOU! Without all of you guys and girls who come to download our creations, there would be no reward for doing this. Thank you for downloading, providing feedback and being part of this small family. You are all appreciated ;)
XDA:DevDB Information
UNOFFICIAL CM10.2 For Bell SGH-I757M, a ROM for the Samsung Galaxy S II
Contributors
titanic_fanatic
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.0.x
ROM Firmware Required: SGH-I757M
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2013-10-05
Last Updated 2014-02-23

Reserved
Tips and Tricks
Use the Bell Flex APN. You can select it by going to:
Settings -> Wireless & Networks -> More -> Mobile Networks -> Access Point Names
This helps fix some issues with VPN and some other system services.
Logcat what is it and how do I get one?
A logcat is the system log of events that occur on your device. This log provides the developers with some useful information pertaining to crashes and other bugs you may encounter while using the ROM and/or apps running on the ROM. Getting a logcat is generally a very simple thing. Just open your terminal emulator on your phone and type the following commands without typing the $ as it denotes a command on the command line:
$ su
$ logcat -v long > /sdcard/logcat.txt
Click to expand...
Click to collapse
The first command above will ask you to grant superuser permission to the terminal emulator which you must accept. The second command will create a file at the root of your sdcard called logcat.txt and then start writing the logs to this file. Since the logcat is a continuous function, your terminal emulator will not return you to the command prompt after the second command as it will continue to write logs until you stop it by pressing the x to close the emulator.
If you are experiencing an issue with an app, then you need to do the steps above to get the logcat recording, then press your home button so that you don't close the emulator, but put it in the background. Then you do the action that causes the bug to occur and then open the emulator and terminate it to stop the log from writing. this ensures that the error is located somewhere around the end of the log and makes it easier for us to spot
What is dalvik-cache and why do I need it?
To explain dalvik cache, you must understand how an app is pieced together. An apk (android app) is like a zip file and contains a bunch of files inside. Two important files to note are the resources.arsc and the classes.dex files. They are compiled versions of the resources (images, sounds, xml files) and classes (source code files) of the app. When android boots into a ROM for the first time, and everytime you install an app, the system performs an optimization called dex optimization which means that is pulls the dex file out of the app and places it into what is called your dalvik cache. The system can then pre-load these dex files and allow the app to start quickly.
Dalvik cache is stored in two locations, at /data/dalvik-cache for user apps and at /cache/dalvik-cache for system apps. We unfortunately have a very small partition for /cache, only 100MB and this sometimes causes a side effect on first boot where it fills up to much with apps that only ever run on the first boot to setup the system and then other dex files cannot be written to the /cache partition which causes them to Force Close (FC). The trick in this situation, is to bear through the FC messages to get the system to the home screen, then reboot into recovery and Wipe Dalvik Cache from the Advanced sub-menu. This will delete all the dex files in both locations I mentioned above and will force the system to regenerate them upon reboot, and this time, those 1-time running apps don't start up and don't end up being optimized which allows the necessary dex files to be created for the apps that were FC'ing.
I have moved what I could from the system partition to the data partition to spare some extra space on /cache but this still sometimes happens, especially as the ROM's get slightly bigger every new major version.

Wow! Thanks so much. Downloading now.

iDynamics said:
Wow! Thanks so much. Downloading now.
Click to expand...
Click to collapse
Wow, you already found it and I wasn't even finished putting everything up... make sure you use the new CWM, very very very important!

Followed the instructions ( to the best of my ability ) but I'm getting a random red border flicker every so often. I'm also not seeing the 91fixoverlays script in my init.d folder.
Smooth rom so far!

iDynamics said:
Followed the instructions but I'm getting a random red border flicker every so often. I'm also not seeing the 91fixoverlays script in my init.d folder.
Smooth rom so far!
Click to expand...
Click to collapse
I totally forgot to update the build.prop with the build type, it is responsible for the red border. Either use a build.prop editor or open the /system/build.prop with a text editor and change the following line:
ro.build.type=eng
Click to expand...
Click to collapse
Change it to:
ro.build.type=user
Click to expand...
Click to collapse
You will need to reboot after making this change.
In regards to the 91fixoverlays script, I do appologize. I forgot to include it in the zip... Please download the attached 91fixoverlays.txt file and rename it to 91fixoverlays and move it to /system/etc/init.d and change it's permissions to match the other files in that directory.
Sorry for missing these two things. I will update the packages ASAP and will post a note when it's done so you know that there is no need to follow the steps in this post.

Much appreciated! No more red flickering. Thanks!

Wow! Thank you!
Sent from my SGH-I757M using xda app-developers app

This. Is. Amazing!!!!!
Downloading now, will install and report back in a bit with findings.
Thanks so much!!

Awesome. Downloading. Will report back. Thanks!
Sent from my SGH-I757M using xda premium

I'm first!! (to post, anyway).
Installed the ROM. Did a clean flash (factory reset).
Upon the boot I got "Unfortunately Bluetooth Share has stopped" but appears to be no ramifications.
ROM looks great! Feels smooth.
Will do more testing.
Thanks

Zippy Dufus said:
I'm first!! (to post, anyway).
Installed the ROM. Did a clean flash (factory reset).
Upon the boot I got "Unfortunately Bluetooth Share has stopped" but appears to be no ramifications.
ROM looks great! Feels smooth.
Will so more testing.
Thanks
Click to expand...
Click to collapse
I think this is due to our oddly small cache partition. Only 100MB as compared to the skyrocket at 300MB. Currently, I only moved four apps in the gapps package to the data partition do that their dex files don't end up in the /cache/dalvik-cache dir and instead end up in /data/dalvik-cache. I think I need to move others. I also think that it happens only on first boot without side effects because a couple of the installed apps only run on first boot, then their dex files can be deleted (I think this happens automatically).
Sent from my SGH-I757M using XDA Premium 4 mobile app

Thanks titanic_fanatic, you've breathed new life into an old phone
Sent from my SGH-I757M using Tapatalk 2

Only issue I've run into so far is that auto rotate doesn't seem to work :-/
Sent from my SGH-I757M using XDA Premium 4 mobile app

I enabled kernel same page merging under performance and no lock screen issues.
Sent from my SGH-I757M using xda app-developers app

rukusx7 said:
I enabled kernel same page merging under performance and no lock screen issues.
Sent from my SGH-I757M using xda app-developers app
Click to expand...
Click to collapse
Cool, I'll give that a try. Anyone else having auto-rotation issues?
Sent from my SGH-I757M using XDA Premium 4 mobile app

Rotation is not working for me, though I always keep it on portrait anyway so I am not complaining.

Rotation doesn't work here, and every so often I run into spells where the only button that works is the home button and haptic feedback stops working all around. A reboot fixes it and it seems random. Other than those few things this is soooooo smooth. I'm happy. Thanks so much!
Sent from my SGH-I757M using xda premium

Fix for Sensors
Hey guys, to fix the sensors, download this attachment sensors.default.so.txt and rename it to sensors.default.so, move it to /system/lib/hw and give it the same permissions as the other files in that directory, then reboot and your sensors should be working

Works now! Thanks ya muchly.
Sent from my SGH-I757M using xda premium

[ROM][DEV][CM11.0][KERNEL][SGH-I757M]UNOFFICIAL CM11.0 For Bell SGH-I757M

CM11.0 for Canadian Samsung Galaxy S2 HD LTE (SGH-I757M)
Code:
[COLOR="red"][B][SIZE="4"]*** Disclamer ***[/SIZE][/B]
THIS ROM IS FOR THE CANADIAN SGH-I757M ONLY... DO NOT FLASH IT ON ANOTHER DEVICE!
By flashing this ROM, you are voiding your phones warranty (Unless you return it
to complete stock which is possible, but beyond the scope of this thread). You
also agree that I will in no way be held responsible in the event that your
device becomes bricked (Not likely to happen). In addition, you are responsible
to take the necessary backups of your apps, data, sms, contacts, calendar events, etc.
If you agree, then please continue on ;)[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RECOVERY REQUIRED ***[/SIZE][/B]
Due to the addition of user control in CM10.1/CM10.2/CM11.0, you are required to update
your recovery to a supported recovery with a version greater than 6.0.39. As of this writing, the latest available
version is Philz Touch Recovery 6.57.9 (based on CWM 6.0.51) for the SGH-I757M. There is currently not a
version of regular CWM for this device that will flash Kit Kat ROMs.
If you flash the new ROM with the old incompatible recovery, you risk loosing
your sdcard under a bunch of subfolders.[/COLOR]
Code:
[COLOR="red"][B][SIZE="4"]*** NEW RADIO FIRMWARE REQUIRED ***[/SIZE][/B]
As of CM10.1, ICS radios (I757MUGLH2) are no longer supported. You must download the new JB radios (I757MUGMC5).[/COLOR]
Introduction
It's finally here :-D CM11.0 (Android4.4.x) for the Bell Canada Samsung Galaxy S2 HD LTE (SGH-I757M). There is a lot to be said about Kit Kat with it's clean white icons and new launcher. The focus with Kit Kat was to make the device use less RAM and imrove performance, and so far it's running great.
Click to expand...
Click to collapse
Images
SEE SCREENSHOTS TAB AT THE TOP OF THIS PAGE.
Click to expand...
Click to collapse
What Works
* Phone
* Wi-Fi
* Mobile
* GPS
* Bluetooth
* SMS/MMS
* Data Usage
* Camera (Camcorder doesn't work on 1080, swith it to 720 for recording)
* BLN Notification (Enabled in Advanced Device Settings)
* VM Notification
* Youtube Overlays
* init.d is fully supported
* USB Mass Storage (UMS)/MTP
Click to expand...
Click to collapse
What Doesn't Work
* I experienced an incompatibility with some of my existing mp4 media files and when gallery tries to load them they cause a soft reboot. Loading these videos into the gallery media player using a 3rd party file manager seems to work without issue, it is the loading of the preview in gallery that causes the phone to crash.
Solution: The solution is to use a file manager to move the mp4 files to a new directory and add a ".nomedia" file to that directory so that when browsing photos in the gallery, it does not try to load the offending mp4 files.
Click to expand...
Click to collapse
Pre-Installation instructions
1) Download to your sdcard, the new Philz Touch Recovery 6.57.9 flashable zip which is compatible with CM10.1/CM10.2/CM11.0
2) Enter your existing CWM Recovery
3) Install Zip From sdcard
4) Select the philz_touch_6.12.8-celoxhd.zip that you downloaded to your sdcard
5) Flash the new Recovery
6) Go back to the main recovery menu and go Advanced -> Reboot Recovery (This might not actually reboot you into recovery, you may have to do that manually by turning off phone and using 3-button combo)
Click to expand...
Click to collapse
Now that you have the new recovery flashed to your device, you can continue to install this ROM.
Please be aware that the new recovery detects your sdcards (internal/external) in a different way. Your internal sdcard is recognized as /storage/sdcard0 and your external sdcard is recognized as /storage/sdcard1.
Installation instructions
1) Download the Rom and Gapps (Use only the Gapps downloded from this thread. It is customized due to our small cache partition)
2) Enter CWM
3) TAKE A NANDROID BACKUP
4) Wipe Data/Factory Reset
5) Format Cache
6) Advanced -> Format Dalvik Cache
7) Mounts and Storage -> Format /data,/cache and /system (Required for a clean flash)
8) Flash the Radios (Required before you flash the ROM, unless you already have the new JB radios flashed)
9) Flash the ROM
10) Flash the Gapps
11) Reboot Phone
Click to expand...
Click to collapse
NOTE: Using Philz Touch Recovery, you can replace steps 5 - 7 by selecting the "Clean to install a new ROM" option.
Download
ROM Downloads
Build: 20141122 (Latest)
ROM: cm-11-20141122-UNOFFICIAL-celoxhd.zip (213.2MB)
PA Mini GAPPS: PA Mini Modular GAPPS
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
NOTE: A clean flash is REQUIRED if upgrading from a previous version of android such as CM10.2
Build: 20140910
ROM: cm-11-20140910-UNOFFICIAL-celoxhd.zip (211.3MB)
PA Mini GAPPS: PA Mini Modular GAPPS
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
DADOES ROM:
Build: 20140424
ROM: cm-11-20140424-DADOES-UNOFFICIAL-celoxhd.zip (469.18MB)
GAPPS: INCLUDED
JB Radios: JB_modem_I757MUGMC5-flash_this_in_CWM.zip (21.3MB)
Recovery Downloads
*** REQUIRED *** Philz Touch Recovery 6.12.8 (CWM 6.0.4.7) compatible with CM10.1/CM10.2/CM11.0
[celoxhd][SGH-I757M][CWM Advanced Edition] PhilZ Touch
* I no longer upload files to XDA because it takes way to long to manage, so I only use androidfilehost.com. All files can be found under my profile: https://www.androidfilehost.com/?w=files&flid=7547
Click to expand...
Click to collapse
Tips and Tricks
Checkout the second post for some tips and tricks on setting up the ROM.
Click to expand...
Click to collapse
Changelog
Code:
[B]November 22, 2014 - Build 20141122[/B]
* Increased kernel version to Titanium 1.1.1
* Added cpu input boost framework - credit: sultanxda
* Added cpu OC (The scale goes up to 1890MHz, but you should only put it as high as 1836MHz since I was getting random reboots with 1890MHz. 1674MHz is the default OC and 1512MHz is the default CM OC) - credit: TeamFahQ/sultanxda/titanic-fanatic
* Added low power flash mode which will use a low powered flash when the battery is equal to or below 35%. This should help with the camera causing the phone to shut down when trying to take pictures using the flash. This threshold may need to be tweaked, so please let me know if you still experience shut downs related to using the camera. - credit: sultanxda
* Added sgs2hdbell as a device name to the updater-script to allow all bell i757m devices to flash the ROM without the need to edit the updater-script.
* Added panel undervolt interface. - credit: sultanxda
* More memory optimizations. Some of the extra RAM that the previous optimization gave us has been allocated to other things such as the surface flinger. Available RAM is now around ~760MB.
* Removed vbus_present wakelock for good (it worked it's way back in somehow)
* Added fast charge. Phone will now charge at 1200mA until 95% regardless of your charging source (AC/USB)
* Added exFAT driver to kernel. It's a filesystem like ext4 but is based on Windows FAT filesystem. You can format your sdcard as exFAT as it's supposed to be faster than vFAT which is what our sdcards are formatted as. Make sure you backup your sdcard contents before formatting it as exFAT and keep the backup until your sure you want to stick with exFAT.
* Removed NFC since I don't think anyone uses it and can't figure out how to have it disabled by default so it is removed completely. If someone is using NFC, let me know and I'll add it back but for now, I just see it as a battery drain.
[B]September 10, 2014 - Build 20140910[/B]
* Kernel now has a custom version number in addition to my kernel name of Titanium
* Optimized kernel memory mapping to increase our physical RAM from ~730MB to ~800MB (a whole 70 extra MB... whoa!)- credit: sultanxda
* Removed mDNIe (it's not supported/working)
* Removed 91fixoverlays script (no longer needed)
* Removed persist.hwc.mdpcomp.enabled from build.prop (hack to fix the hwoverlays because fb drivers are broken somehow) - credit: sultanxda
* Added GPU overclock from 266MHz to 320MHz (helps a lot with the UI lag) - credit: sultanxda
* Added code for 2 phase OnDemand governor - credit: sultanxda
* Added opensource frandom module to help speed up the UI (also helps with the lag) - credit: bryan2894
* Added mdp Color Enhancements (better display color) - credit: sultanxda
* Added color/gamma controls in place of mDNIe (see the tips and tricks section for my already tweaked favorite settings) - credit: bryan2894/titanic_fanatic (I had to integrate it into our display drivers)
* Added Swipe 2 Wake (S2W) support in the kernel (it's actually tap once on each key from left to right). - credit: bryan2894
* Added audio.r_submix.default.so to the build to enable screencasting - credit: [URL="http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193"]THIS POST[/URL]
* Added the necessary audio channels in the audio_policy.conf for screencasting - credit: [URL="http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193"]THIS POST[/URL]
* Added the necessary settings in Advanced Device Settings for screencasting and color/gamma control - credit: bryan2894/titanic_fanatic (I added the screencasting settings)
* Fixed the annoying BLN sticking (I think... Please confirm this for me) - credit: bryan2894
* Fixed the sampling rates for A2DP, input and r_submix channels - credit: bryan2894
* Changed both scaling governors to OnDemand - credit: bryan2894
[B]August 15, 2014 - Build 20140815[/B]
* Sync with sources
* Added sysfs interfaces for vibrator intensity
* Added Settings in Advanced Device Settings for vibrator intensity
[B]July 11, 2014 - Build 20140708[/B]
* Sync with sources (Update to Android 4.4.4)
* Vibrator module now built into kernel
* Added sysfs for vibrator intensity to allow user control of the vibrator intensity
[B]May 21, 2014 - Build 20140321[/B]
* Sync with sources
* Switched to using media-caf
* Updated kernel with sources for media-caf
* Fixed issue with Google Camera resolution preferences FC
* Added back 91fixoverlays script due to graphics glitches with the new kernel
[B]April 10, 2014 - Build 20140410[/B]
* Synced with sources
* Added USB Mass Storage Mode (UMS)
* Fixed network type selection menu. It now includes LTE as an option.
[B]March 29, 2014 - Build 20140329[/B]
* Synced with sources
* Added overlay items to enable homescreen/lockscreen rotation
* Set Camera as default Scene Mode to partially fix camcorder recording
* cherry-pick display-caf commits to fix some of the graphical glitches
[B]March 21, 2014 - Build 20140321[/B]
* Sync with sources
* Remove 91fixoverlays script
[B]February 6, 2014 - Build 20140206[/B]
* Initial release
Click to expand...
Click to collapse
FAQ
Q. How do I install SuperSu?
A. Install the latest version from the market. Then open SuperSU and when it asks you to update the superuser binary, answer yes and make sure you select the "TWRP/CWM" method. This will reboot your phone into receovery where the superuser binary will be updated and the su daemon script added. Reboot your phone and you should be rooted.
If your having difficulties getting SuperSu installed, try downloading the flashable zip and manually flashing it to your phone.
UPDATE-SuperSU-v1.65.zip
* Thanks to @formercontra for this tip *
* Make sure this is the way in which you want to manage superuser permissions as I have not yet found a way to revert to the integrated superuser without having to re-flash the rom
Q. How do I access Developer Options?
A. Go to Settings -> About Phone and scroll to the bottom. Press the Build number 7 times to activate the Developer Options.
Q. I was browsing my pictures/videos in the gallery and my phone rebooted?
A. This seems to be caused by the gallery trying to generate a preview from the first frame of an mp4 created on older versions. Simply move the mp4's to a different directory with a file manager and add a ".nomedia" file to the folder to stop the gallery from trying to scan them. To open them, open with a filemanager and then select the gallery media player and it will play without issue.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* CyanogenMod Team - ROM Base
Without all of the hard work and efforts of the CyanogenMod team, this ROM would not be possible, so we owe them our thanks for providing us with such excellent ROMs.
In addition, I have received a lot of help on my journey to understand and be able to develop for the android platform, so I owe the following people my thanks for helping me to make this ROM possible.
* [user=673068]@dsixda[/user] - Initial port of CM9/CM10 for SGH-I757M
* [user=4974935]@Strange Peer[/user] - Continued development of CM10
* [user=3478918]@rukusx7[/user] - Contributor
* [user=4435341]@bijon440[/user] - Contributor
* [user=4036181]@kj2112[/user] - Contributor
* [user=5077807]@Tronith[/user] - Contributor
* [user=3651088]@Zippy Dufus[/user] - Contributor
* @Socim - Thanks to Socim for pointing me in the right direction a few times ;-)
* @formercontra - Contributor
* @Sultanxda - Many bug fixes and improvements for the msm8660 kernel
Thanks guys you've all been so awesome to work with ;)
One last group of people to thank. It's YOU! Without all of you guys and girls who come to download our creations, there would be no reward for doing this. Thank you for downloading, providing feedback and being part of this small family. You are all appreciated ;)
XDA:DevDB Information
UNOFFICIAL CM11.0 For Bell SGH-I757M, ROM for the Samsung Galaxy S II
Contributors
titanic_fanatic
Source Code: https://github.com/titanic-fanatic
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: SGH-I757M
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2014-02-06
Last Updated 2014-11-24

Tips & Tricks
Tips and Tricks
Here are my settings for the color/gamma controls!
Color:
Red -> 60%
Green -> 45%
Blue -> 45%
Gamma:
Red -> 0
Green -> -5
Blue -> 5
Why does the color/gamma controls get set to a value other than what I've set?
This is something I have not yet resolved, but I have noticed that it seems to jump up by 5. So if you want 50% for example, try setting it to 45%.
Logcat what is it and how do I get one?
A logcat is the system log of events that occur on your device. This log provides the developers with some useful information pertaining to crashes and other bugs you may encounter while using the ROM and/or apps running on the ROM. Getting a logcat is generally a very simple thing. Just open your terminal emulator on your phone and type the following commands without typing the $ as it denotes a command on the command line:
$ su
$ logcat -v long > /sdcard/logcat.txt
Click to expand...
Click to collapse
The first command above will ask you to grant superuser permission to the terminal emulator which you must accept. The second command will create a file at the root of your sdcard called logcat.txt and then start writing the logs to this file. Since the logcat is a continuous function, your terminal emulator will not return you to the command prompt after the second command as it will continue to write logs until you stop it by pressing the x to close the emulator.
If you are experiencing an issue with an app, then you need to do the steps above to get the logcat recording, then press your home button so that you don't close the emulator, but put it in the background. Then you do the action that causes the bug to occur and then open the emulator and terminate it to stop the log from writing. this ensures that the error is located somewhere around the end of the log and makes it easier for us to spot
How do I take a dmesg (kernel log)?
It's fairly simple, open up your terminal then type the following:
$ su
$ dmesg > /storage/sdcard0/dmesg.txt
Click to expand...
Click to collapse
This will save the log to the root of your sdcard as dmesg.txt. Just post that or send it to [email protected] if it's to large to post here
What is dalvik-cache and why do I need it?
To explain dalvik cache, you must understand how an app is pieced together. An apk (android app) is like a zip file and contains a bunch of files inside. Two important files to note are the resources.arsc and the classes.dex files. They are compiled versions of the resources (images, sounds, xml files) and classes (source code files) of the app. When android boots into a ROM for the first time, and everytime you install an app, the system performs an optimization called dex optimization which means that is pulls the dex file out of the app and places it into what is called your dalvik cache. The system can then pre-load these dex files and allow the app to start quickly.
Dalvik cache is stored in two locations, at /data/dalvik-cache for user apps and at /cache/dalvik-cache for system apps. We unfortunately have a very small partition for /cache, only 100MB and this sometimes causes a side effect on first boot where it fills up to much with apps that only ever run on the first boot to setup the system and then other dex files cannot be written to the /cache partition which causes them to Force Close (FC). The trick in this situation, is to bear through the FC messages to get the system to the home screen, then reboot into recovery and Wipe Dalvik Cache from the Advanced sub-menu. This will delete all the dex files in both locations I mentioned above and will force the system to regenerate them upon reboot, and this time, those 1-time running apps don't start up and don't end up being optimized which allows the necessary dex files to be created for the apps that were FC'ing.
I have moved what I could from the system partition to the data partition to spare some extra space on /cache but this still sometimes happens, especially as the ROM's get slightly bigger every new major version.

Flashing Recovery for the First Time
Flashing CWM for the First Time
This is a pretty simple step once you get past the install recovery script which I'll explain how to accomplish. Make sure you follow the instructions closely because Odin, the program the we use to bypass the security, can do some serious damage to your phone if your not careful.
1) Download the latest CWM tar.md5 to your computer from my androidfilehost.com repo here:
http://www.androidfilehost.com/user/?w=settings-dev-files&flid=12461
2) Download Odin 1.8.5 zip and extract all the files to a folder on your computer (i use my desktop):
http://www.androidfilehost.com/?fid=23501681358544719
3) The drivers are very touchy on windows computers, so I recommend that you install Samsung Kies which will ensure that the drivers are installed and setup correctly. You can download kies from here:
http://www.samsung.com/ca/support/usefulsoftware/KIES/JSP
4) Be careful now that you have kies installed, it does not play nicely with Odin, so whenever you use Odin, you should ensure that kies is completely closed and not open in the system tray by opening your Task Manager and "End Task" to any kies process such as "Kies.exe" and "KiesTrayAgent.exe"
5) Now, with kies closed, open Odin and do not change any settings. It should look like this:
6) Now click on the Bootloader button and search for the CWM tar.md5 you downloaded from my androidfilehost.
7) Now turn off your phone, and when it's powered off, press and hold the volume down and power buttons at the same time until you see the warning message about Download mode. Press volume up to enter download mode.
8) With Kies closed on your computer and Odin open cwm tar.md5 loaded into the bootloader section and your phone in Download mode, plug your phone into the computer with your micro usb cord and wait for odin to display a "Device Added" message which tells you that odin sees your phone.
9) This is the tricky part and is all based on timing, so pay close attention.
10) You will now press the "Start" button in odin and wait for it to complete. It will display a green "Pass" message in the first box when it's done. At this time, the phone will reboot and will start with a slight vibration to notify you that it's booting up. It's exactly at the time that the phone vibrates that you need to immediately remove the micro usb cord and press and hold the volume up and volume down buttons simultaneously until cwm loads. If you miss this mark, android will boot, the install_recovery.sh script will run and overwrite the cwm you just flashed with the old stock 3e recovery (arghhh) and you will have to go through this process again.
If CWM complains about the install_recovery script, let it fix/remove it.
Once you have CWM flashed, you can use it to backup/restore your system, flash custom ROMs and you can even flash our CWM upgrades through CWM itself.

First Wood Woot !! And many thankyous.
Update-
This Rom is flawless so far. I have no issues that existed for me in CM10.2JB . Status Bar doesn't freeze. Apps aren't killed mid use. Calender sync was fixed by installing Google calendar from play store and then removing it. (I use Cal app). There's almost no lag in multi tasking. I'm very happy.?? kit Kat!
Let's all hit TFs donate button with a few bucks, eh?

Much appreciated. Downloading now.

Sweet, a thread here instead of g+!
Sent from my SGH-I757M using xda premium

For me the gallery issue was gone after switched to the next branch.

Crossbreeder won't install (it did on the earlier 4.4 builds).. but Adaway works just fine and everything's working smoothly. Love the music in the lockscreen! also noticed there's even more governor parameters to tweak, which is always a good thing

formercontra said:
Crossbreeder won't install (it did on the earlier 4.4 builds).. but Adaway works just fine and everything's working smoothly. Love the music in the lockscreen! also noticed there's even more governor parameters to tweak, which is always a good thing
Click to expand...
Click to collapse
That's due to the new recovery. If your on a Windows system, download 7zip if you don't have it already.
Here's what you do, open this roms zip file and extract only the update-binary from META-INF/com/google/android to a location on your computer. Then you can close the ROM zip. Now open the crossbreeder zip with 7zip and browse to META-INF/com/google/android and simply drag the extracted update-binary into the crossbreeder zip file replacing it's update-binary with the one from cm-11. Then close the zip and upload to your phone and flash away
Sent from my SGH-I757M using XDA Premium 4 mobile app

After running ROM for a few hours, I'm quite impressed. No issues so far. I will continue using it and report any findings. Thanks titanic for all your time and effort.
Sent from my SGH-I757M using Xparent Cyan Tapatalk 2

Phone won't boot
I flashed the rom and the gapps but I get no boot screen. I waited about five minutes and nothing happened. Any ideas on what went wrong??

Amazing
It's is so smooth, I am ecstatic to see how it'll be when ART becomes functional!
Thanks again!

omar.kassam97 said:
I flashed the rom and the gapps but I get no boot screen. I waited about five minutes and nothing happened. Any ideas on what went wrong??
Click to expand...
Click to collapse
Did you wipe and factory reset? Did you use the wipe to install new rom option?
This ROM must be flashed clean. No dirty flashing unless you already had cm-11 flashed.
Sent from my SGH-I757M using XDA Premium 4 mobile app

I am curious, in your 10.2 thread you said the calendar could not be assigned a gmail account in cm 11.
Was this resolved? For me it's a deal breaker (loving your cm10.2 anyways).
If it hasn't been fixed could we add it to the OP in the what doesn't work section?
Sent from my SGH-I757M using xda app-developers app

slushee said:
I am curious, in your 10.2 thread you said the calendar could not be assigned a gmail account in cm 11.
Was this resolved? For me it's a deal breaker (loving your cm10.2 anyways).
If it hasn't been fixed could we add it to the OP in the what doesn't work section?
Sent from my SGH-I757M using xda app-developers app
Click to expand...
Click to collapse
No, it's unfortunately not fixed and will definitely add that to the op
Sent from my SGH-I757M using XDA Premium 4 mobile app

Way to go Titanic! I will flash tomorow and try this one out.
Sent from my SGH-I757M using xda app-developers app

Philz touch cwm was just updated and now uses a new exfat module for mounting the sdcards. It's supposed to be faster than the fuse alternative. This version also fixes the resolution of the background image, the software buttons and the vibration.
http://forum.xda-developers.com/showthread.php?t=2552634
Sent from my SGH-I757M using XDA Premium 4 mobile app

The calendar works in slim. I think the calendar sync adapter is missing in cm-11. Can I get someone to add this apk to your /system/app dir give it the same permissions as the others, then reboot and try connecting the calendar to your Google account. I'm out of the house right now so can't test it myself.

titanic_fanatic said:
The calendar works in slim. I think the calendar sync adapter is missing in cm-11. Can I get someone to add this apk to your /system/app dir give it the same permissions as the others, then reboot and try connecting the calendar to your Google account. I'm out of the house right now so can't test it myself.
Click to expand...
Click to collapse
Yep, that worked. My Google account syncs now and i can create events. Thanks TF!
Sent from my SGH-I757M using xda premium

bijon440 said:
Yep, that worked. My Google account syncs now and i can create events. Thanks TF!
Sent from my SGH-I757M using xda premium
Click to expand...
Click to collapse
Excellent, I'll update the gapps package when I get home thanks for testing
Sent from my SGH-I757M using XDA Premium 4 mobile app

Perfect Android P setup for our device.

This is the perfect setup for android p, I use this as my daily driver and it has NO issues as of now. I have gone through almost a whole week of testing each rom before I chose this combination and this is super stable IMO.
Steps Followed:
1) Take backup of whole device (Including internal storage)
2) a) If you are on a Non-Treble rom:
- Install factorytovendor.zip (https://androidfilehost.com/?fid=962187416754475515)
- Install treble TWRP recovery img (https://www.androidfilehost.com/?fid=5862345805528044154)
- Reboot to new recovery
- Proceed to step 3
b) If you are already using a Treble rom:
- Proceed to step 3
3) Completely wipe your phone (Including internal storage, I found that this gives the best result)
4) Reboot to recovery (you will get no OS installed screen, slide the icon and do not worry you will reboot to TWRP)
5) Connect your phone to your PC and transfer the following files to the internal storage:
a) CR droid treble ROM (I used this: https://androidfilehost.com/?fid=5862345805528059385)
b) Img file extracted from P-DP5-sGSI-Aonly.zip (you can find it here: https://androidfilehost.com/?fid=5862345805528058112)
c) POST-sGSI_1_v0.14.zip (https://androidfilehost.com/?fid=5862345805528063582)
d) POST-sGSI_2_v0.17.zip (https://androidfilehost.com/?fid=5862345805528063581)
e) POST-sGSI_3_v0.2.zip (https://androidfilehost.com/?fid=5862345805528058103)
f) dp5-lag-fix.zip (https://drive.google.com/drive/folders/1_UOASaZTlclwANdfVPxZVqLoqStOJ2wE)
g) New GPU drivers (https://drive.google.com/drive/folders/1_UOASaZTlclwANdfVPxZVqLoqStOJ2wE)
h) Voltefixforz2.zip (https://drive.google.com/drive/folders/1_UOASaZTlclwANdfVPxZVqLoqStOJ2wE)
i) Gcam (https://drive.google.com/drive/folders/1_UOASaZTlclwANdfVPxZVqLoqStOJ2wE)
j) google play services apk (https://drive.google.com/drive/folders/1_UOASaZTlclwANdfVPxZVqLoqStOJ2wE)
k) AKT profiles apk (https://drive.google.com/drive/folders/1_UOASaZTlclwANdfVPxZVqLoqStOJ2wE)
l) Magisk (https://drive.google.com/drive/folders/1_UOASaZTlclwANdfVPxZVqLoqStOJ2wE)
6) Install crdroid treble rom
7) Install latest GPU drivers
8) flash P-DP5-sGSI-Aonly.img on System partition (choose install image from TWRP and choose img file and choose system image)
9) Mount System and Vendor on TWRP
10) Flash POST-sGSI_1
11) Flash POST-sGSI_2
12) Flash POST-sGSI_3
13) Flash Magisk
14) Mount System and Vendor on TWRP
15) Flash dp5-lag-fix.zip
16) Mount Vendor on TWRP
17) (To prevent reboots to twrp) Go to TWRP Advanced->Terminal, type the following and press enter
echo persist.sys.disable_rescue=true >> /vendor/build.prop
18) Reboot to System
19) let phone rest for 10 minutes (cool down)
20) Install Google Play Services Apk,
21) reboot to recovery
22) Install voltefix.zip
23) reboot to system
24) let phone rest for 10 minutes
25) click on setup from notification tray
26) signin to your google account
27) choose setup fingerprint and choose a pattern
28) on the screen where it asks you to place finger on sensor, leave the screen as it is for about 10 minutes (DO NOT TOUCH THE FINGERPRINT SENSOR RIGHT AWAY)
29) after 10 minutes, try registering your finger print:
a) if it passes, YAY!
b) if it goes back to previous screen, click on continue and try registering (no need to wait for 10 minutes)
c) if it goes to register screen and fails, YAY! you can set it up after the setup is complete (don't worry, it will work)
30) If you are restoring a backup from the cloud, the restore app will stop responding, dont worry. Click on app info and grant all permissions to the app, go back to previous screen and try again, It will work.
31) complete setup and let phone rest for 10-20 minutes.
32) open magisk and let it install updates (it will update twice) and check for safety net
33) install AKT profile apk
34) use balances xana for smooth performance, use xana battery to save some battery
35) install Gcam if any app crashes while accessing camera
ENJOY!!!

girish17m said:
This is the perfect setup for android p, I use this as my daily driver and it has NO issues as of now. I have gone through almost a whole week of testing each rom before I chose this combination and this is super stable IMO.
Steps Followed:
1) Take backup of whole device (Including internal storage)
2) a) If you are on a Non-Treble rom:
- Install factorytovendor.zip (https://androidfilehost.com/?fid=962187416754475515)
- Install treble TWRP recovery img (https://www.androidfilehost.com/?fid=5862345805528044154)
- Reboot to new recovery
- Proceed to step 3
b) If you are already using a Treble rom:
- Proceed to step 3
3) Completely wipe your phone (Including internal storage, I found that this gives the best result)
4) Reboot to recovery (you will get no OS installed screen, slide the icon and do not worry you will reboot to TWRP)
5) Connect your phone to your PC and transfer the following files to the internal storage:
a) CR droid treble ROM (I used this: https://androidfilehost.com/?fid=5862345805528059385)
b) Img file extracted from P-DP5-sGSI-Aonly.zip (you can find it here: https://androidfilehost.com/?fid=5862345805528058112)
c) POST-sGSI_1_v0.14.zip (https://androidfilehost.com/?fid=5862345805528063582)
d) POST-sGSI_2_v0.17.zip (https://androidfilehost.com/?fid=5862345805528063581)
e) POST-sGSI_3_v0.2.zip (https://androidfilehost.com/?fid=5862345805528058103)
f) dp5-lag-fix.zip (https://drive.google.com/drive/folders/1_UOASaZTlclwANdfVPxZVqLoqStOJ2wE)
g) New GPU drivers (https://drive.google.com/drive/folders/1_UOASaZTlclwANdfVPxZVqLoqStOJ2wE)
h) Voltefixforz2.zip (https://drive.google.com/drive/folders/1_UOASaZTlclwANdfVPxZVqLoqStOJ2wE)
i) Gcam (https://drive.google.com/drive/folders/1_UOASaZTlclwANdfVPxZVqLoqStOJ2wE)
j) google play services apk (https://drive.google.com/drive/folders/1_UOASaZTlclwANdfVPxZVqLoqStOJ2wE)
k) AKT profiles apk (https://drive.google.com/drive/folders/1_UOASaZTlclwANdfVPxZVqLoqStOJ2wE)
l) Magisk (https://drive.google.com/drive/folders/1_UOASaZTlclwANdfVPxZVqLoqStOJ2wE)
6) Install crdroid treble rom
7) Install latest GPU drivers
8) flash P-DP5-sGSI-Aonly.img on System partition (choose install image from TWRP and choose img file and choose system)
9) Mount System and Vendor on TWRP
10) Flash POST-sGSI_1
11) Flash POST-sGSI_2
12) Flash POST-sGSI_3
13) Flash Magisk
14) Mount System and Vendor on TWRP
15) Flash dp5-lag-fix.zip
16) Mount Vendor on TWRP
17) (To prevent reboots to twrp) Go to TWRP Advanced->Terminal, type the following and press enter
echo persist.sys.disable_rescue=true >> /vendor/build.prop
18) Reboot to System
19) let phone rest for 10 minutes (cool down)
20) Install Google Play Services Apk,
21) reboot to recovery
22) Install voltefix.zip
23) reboot to system
24) let phone rest for 10 minutes
25) click on setup from notification tray
26) signin to your google account
27) choose setup fingerprint and choose a pattern
28) on the screen where it asks you to place finger on sensor, leave the screen as it is for about 10 minutes (DO NOT TOUCH THE FINGERPRINT SENSOR RIGHT AWAY)
29) after 10 minutes, try registering your finger print:
a) if it passes, YAY!
b) if it goes back to previous screen, click on continue and try registering (no need to wait for 10 minutes)
c) if it goes to register screen and fails, YAY! you can set it up after the setup is complete (don't worry, it will work)
30) If you are restoring a backup from the cloud, the restore app will stop responding, dont worry. Click on app info and grant all permissions to the app, go back to previous screen and try again, It will work.
31) complete setup and let phone rest for 10-20 minutes.
32) open magisk and let it install updates (it will update twice) and check for safety net
33) install AKT profile apk
34) use balances xana for smooth performance, use xana battery to save some battery
35) install Gcam if any app crashes while accessing camera
ENJOY!!!
Click to expand...
Click to collapse
Can I use this new you drivers on nougat, oreo ROM or it is only for P?
Sent from my Zuk Z2 using Tapatalk

cichowlasp said:
Can I use this new you drivers on nougat, oreo ROM or it is only for P?
Sent from my Zuk Z2 using Tapatalk
Click to expand...
Click to collapse
You can use it for any version of android

girish17m said:
6) Install crdroid treble rom
7) Install latest GPU drivers
Click to expand...
Click to collapse
I have flashed latest Havoc os as base ROM and everything except fingerprint is working.
I have not done Step 7. Is it required for casual usage, zero gaming scenario?
Do I need to start again from crdroid now for flashing GPU drivers?

anjath said:
I have flashed latest Havoc os as base ROM and everything except fingerprint is working.
I have not done Step 7. Is it required for casual usage, zero gaming scenario?
Do I need to start again from crdroid now for flashing GPU drivers?
Click to expand...
Click to collapse
I have heard from many people that the latest drivers improves performance significantly, for me I saw a huge boost in smoothness of UI. (I dont game so can't comment on game performance)

What's advantage of new GPU driver?
Can I flash them after setting up the ROM?

Can you please attach benchmark scores in this thread @girish17m

sanketp60 said:
What's advantage of new GPU driver?
Can I flash them after setting up the ROM?
Click to expand...
Click to collapse
You can flash GPU drivers after setting up rom too. Shouldn't break anything (but backup everything just in case).. I have told my take on the advantages already

vvijayk1999 said:
Can you please attach benchmark scores in this thread @girish17m
Click to expand...
Click to collapse
I haven't checked benchmarks(and don't plan to) because this is a port of a developer preview and I don't expect this to break any benchmarks till stable android p is released. You are welcome to try though!

Thank you man for such a detailed and informative post. It is really helpful.
I want to ask how is the battery backup you are getting ?? Is it good / comparable to other oreo ROMs?

DivyanshuJ said:
Thank you man for such a detailed and informative post. It is really helpful.
I want to ask how is the battery backup you are getting ?? Is it good / comparable to other oreo ROMs?
Click to expand...
Click to collapse
Following the exact same steps I mentioned, I'm getting 5-6 hours of SOT (I'm on my 3rd charge cycle) with day to day usage. The phone feels as cool as bootleggers oreo and performs a little better than it (IMO). If you want all the advantages of the AI behind android P (the battery backup only gets better with time due to adaptive battery) and an amazing UI, then go for it.

Unable to Mount system after Step 8....plz help

Nishant Nimbster said:
Unable to Mount system after Step 8....plz help
Click to expand...
Click to collapse
were you on a treble rom before? and are you flashing the IMG file or the zip file?

girish17m said:
were you on a treble rom before? and are you flashing the IMG file or the zip file?
Click to expand...
Click to collapse
Yes I was on treble....and I am flashing the img file.

Nishant Nimbster said:
Yes I was on treble....and I am flashing the img file.
Click to expand...
Click to collapse
what is the error you are getting? you have flashed the gsi img to system, but after that you cant mount system from mount options?

girish17m said:
what is the error you are getting? you have flashed the gsi img to system, but after that you cant mount system from mount options?
Click to expand...
Click to collapse
Exactly!!...Unable to Tick the system option in mount.

Nishant Nimbster said:
Exactly!!...Unable to Tick the system option in mount.
Click to expand...
Click to collapse
that is weird. try wiping everything again, flash the twrp image I have attached in the first page and then follow the guide again. maybe its because you're using a different twrp

girish17m said:
that is weird. try wiping everything again, flash the twrp image I have attached in the first page and then follow the guide again. maybe its because you're using a different twrp
Click to expand...
Click to collapse
I have already flashed that Twrp 2 times....But l will start the process once again.

Nishant Nimbster said:
Exactly!!...Unable to Tick the system option in mount.
Click to expand...
Click to collapse
Try to change filesystem of system to any then wipe system then again change the system to ext4 and wipe

Nishant Nimbster said:
Unable to Mount system after Step 8....plz help
Click to expand...
Click to collapse
Moreover I have seen in guides everywhere, the image is to be flashed to "system image". Can the OP confirm?
Reboot to recovery. That might fix.
Sent from my z2_plus using XDA Labs

A Noobs Guide to Verizon Galaxy Note 4 Hardware Repair,Root,Bootloader,Twrp,ROM's

A Noobs guide to Galaxy Note 4 Verizon Motherboard Hardware repair and replacement
and Other Samsung Galaxy Note 4 repair ( Att, Tmobile etc ) starting in thread 2 ( user input welcome ) ​
My Overheat Heat and flash problem issues leading to
OEM Motherboard replacement and acquiring ROOT again​
OP Note : read the whole guide or for that matter any OP​
Thanks to many XDA-Developers forums, if you are not quoted or mentioned here I will add you !!
Device : Samsung Galaxy Note 4 Verizon SM-910V this OP ONLY !!!
Code:
[COLOR=Red][B]Your warranty is now void.[/B][/COLOR]
*most likely you don't have a warranty because you broke it, ROM'd it, its old and past warranty anyway !**
So, There is no warranty anyway, not even if you did anything in this thread to it
We are not responsible for bricked devices, dead SD cards,
thermonuclear war, or your getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this guide
before flashing it! (thanks @hsbadr)
YOU are choosing to make these modifications, and if
you point the finger at anyone for messing up your device, we will laugh at you
Symptoms : ROMs not flashing/installing , crashing, High heat, low battery life on new battery hardware note working specifically fingerprint.
Problems : digging through many forums 2 years later to root and unlock the bootloader, it took DAYS
Solution: keep track of my progress and make a useful step by step NOOB guide for Everything !
Section 1: Repairs
Then the rest of the sections are for Rooting, Installing TWRP custom recovery, fixing bootloader , and installing ROMS
Section 2: Flashing via ODIN and the correct rootable OEM rom 5.1.1 on a windows PC
section 2a: Flashing via Heimdall on a Linux device --need comments
Section 3: Achieve temporary root to install bootloader fix
Section 4: Use of ADB to (windows and linux ) to copy over bootloader fix
Section 5: install TWRP custom recovery and your first rom
Section 1: Repairs
If you have to replace the motherboard, and you have any other futzy component, might as well order it at this point, your going through pretty much the same process. I am only doing the motherboard, but the cameras and USB board are right there as well on this repair
I have been running a rooted Verizon Galaxy note 4 since Cynogenmod crashed and switched to Lineageos 14 and then 15.
Here is the forum
https://forum.xda-developers.com/no...eo-8-1-0-unofficial-lineage-15-1-rom-t3760969​
After several suggestions and searches, many users hinted I may be getting a Bad internal memory,
which refuses to write anymore.
So I had to go to Walmart and buy a LG Straight talk phone to use as my daily driver,
Then I ordered a new motherboard from China, 29.00 on Aliexpress.
See OP thread #2 below!! It was not fun searching for it, but I saved $20 to $40 from buying on ebay
What I bought may not be available from this seller, but here is the link. Use a desktop browser, it will show "suggested" other devices...
Code:
[URL]https://www.aliexpress.com/item/with-Android-System-Original-unlocked-for-Samsung-Galaxy-Note-4-N910V-Motherboard-Good-Working-Free-Shipping/32802513232.html?spm=a2g0s.9042311.0.0.66e04c4dpohrQm[/URL]
When I received it , it was time to look for a repair procedure on YouTube.
Hardware needed: thin shim and 00 size phillips, AND a blank cheap SD card you don't mind losing. It may be unusable after we are done
Cell Phone repair tool kit really helps save your fingernails !
Complete note 4 teardown video:
Code:
[media=youtube]ZND9Q73wjr8[/media]
Just the Motherboard video
Code:
[media=youtube]5KpT755hNpM[/media]
In the second video, you can see the phone booting up as a test to see if you have all the connections correct.
Because it came from china, its a good idea to setup your user and
download the app CPUz before you put all the screws back in,
and check to see if you have a real or fake chipset.
Yaayyyy mine was real . Thanks Aliexpress.
Button it up and do a factory reset (it booted up set up as a no user) so I wanted a fresh install oem with my user.
Section 2: Installing the Correct rootable OEM rom so we can install Anything else.
FIRST check to see if you have the emmc brickbug or you will BRICK it !!
1. Google play store install eMMC Brickbug
If your long number starts with 15xxxxxxxxxxxxxxxxx, YOU are Golden ! if not STOP, get another board ! or you are going to waste time , and get another board !
The Galaxy Note 4 Verizon had a special custom locked bootloader installed after the 4.4.4 release to 5.0.1 and made it very difficult to get
root access to your device.
I saw the notice
DON'T UPDATE YOUR BOOTLOADER TO ANYTHING AFTER THE LATEST BUILD AS OF 4/19/16
warning about a week to late. So I finished out my 2 year contract and watched the forums.
Seriously noobs, don't update your new motherboard ...
The rom pre-installed on my replacement motherboard was already setup booted to a running 5.0.1 oem rom, I could not root it.. with any method I remember downgrading my 6.x.x to 5.1.1 in one of the many forums listed here at XDA
This one was the one I used back then, and It turned out that is where I started..
Only a Verizon Samsung Galaxy note 4 Developer Edition has the ability to install custom roms, and most likely the motherboard you bought or have is NOT a developer edition
IF you have a eMMC that starts with 15 we can reprogram it a developer edition
Thanks to @hsbadr
Here are most of the downloads we need:
Code:
[URL]https://forum.xda-developers.com/devdb/project/?id=15720#downloads[/URL]
2. Download Odin, Download TWRP, and Samsung_unlock_n4-fix
3. On your windows PC, create a folder c:/Odin and extract the Odin zip file there, and copy the TWRP image there
4. Download the following OEM root able ROM to your c:/Odin folder
Code:
[URL]https://forum.xda-developers.com/devdb/project/dl/?id=18880[/URL]
5. Plug your phone into a USB port on your Windows PC
6. Install the necessary drivers if they don't automatically install from Samsung
Code:
[URL]https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows[/URL]
7. Set up your phone for flashing ROM and communicating
Settings - Security - Unknown sources- : check allow
settings - system -about phone - build number : click several times until you activate developer options
settings - system -about phone - developer options : Android Debugging : enable android debug bridge
settings - security - reactivation lock : Turn OFF or you will brick your device ( may vary where this is at . Important to turn off )
Power Off phone
Enter Download Mode - press and hold in this order <down arrow> <home> <power> until screen comes on. release buttons.
press up arrow to enter download mode
8. Open windows explorer and go to your c:/Odin folder. You should have an odin exe file, and the twrp file, and the large rom file.
a. right click odin exe and open as administrator
b. check to see if your connected to your phone. you should see a blue box in upper left with a com under it.
If you unplug your phone, you should hear the disconnect notice and the com and blue bar will go off, and when you connect, the com and blue bar and reconnect noise should appear.
9. click the AP button box, select the ROM file that you downloaded above.
NOTE : this ROM will disable WIFI so you wont be able to use the play store unless you have cellular connection.
you will have to transfer other files via usb cable !
Click start, do not unplug! until it stops.
10. Device will reboot. Remove cable, and battery before boot completes
11. Enter recovery mode . Press in order ,<volume up><home><power>
wait for the little android dude to do his thing, then there will be a menu. select factory reset, and reset and let it reboot
Set up minimal user or as a new phone with no user and check the settings in step 7
Set up your phone for flashing roms and communicating
Settings - Security - Unknown sources- : check allow
settings - system -about phone - build number : click several times until you activate developer options
settings - system -about phone - developer options : Android Debugging : enable android debug bridge
settings - security - reactivation lock : Turn OFF or you will brick your device ( may vary where this is at . Important to turn off )
Yayy, you now have a rootable device
Section 3 Achieve temporary root to install bootloader fix
In my try to obtain temporary root, I tried every method in all the forums ( go ahead and look and try )
The only 2 programs that reported to work is Kingroot, and Kingoroot. These are APK's that are NOT in the play store
you will have to download them and install them as unknown sources. I was only able to install kingroot . Kingoroot apk would not install
in both my 5.0.1 original on my motherboard, as well as what we just installed 5.1.1 I was unsucessful at obtaining root with these programs
Then I remembered Kingoroot has a windows version that installs on the PC <dangerous dont install yet>
On your PC you will need AVG antivirus to catch the malware ( other antivirus may work but this is what I had ) my PC is windows 7 ultimate
Advanced Users only :Recommend running a virtual machine with windows so as to keep your PC completely malware free. just delete the VM after this process !
This section you will need on your Note 4 from the Play Store : root checker
You will need a throw away SD card
You will need read through section 4 and 5 and get all files and programs there ready to install use and or transfer
0.5 update your AVG
1. With AVG installed on my PC, and my phone connected as a mtp with usb I downloaded and installed Kingoroot for windows.
https://www.kingoapp.com/
NOTE after not being able to install forum recommended kingoroot apk's i dint want wast time install the newest kingoroot apk from the website. Maybe it will work for you. If you do get kingoroot apk to work on your Note 4 let me know.
2. In the install process for kingoroot windows version AVG will quarantine a file.
there will be a couple popups .. close them
when its installed it will open and start talking to your phone.
3. press the root button.
It will take 30 sec to a minute to install some files on your phone and achieve root, there will be a new floating toolbar on the phone. root will disappear after a reboot, but not the resident programs this root is pretty stable, but i was not able to install SuperSUME (paid version ) as recommended in a XDA guide to obtain permanent root for this 5.1.1 rom. If your successful with super SUme with this let me know.
4. Open root checker to verify ! yayy.
5. Cleanup instructions when finished with this guide below
Section 4: Use of ADB to (windows and Linux ) to copy over bootloader fix
1. Your Note4 phone should be running with root, make sure phone is connected
Explanation : ADB is a Google provided tool for the android platform. It communicates with your phones operating system , transfers files , and actuates programs remotely in the background. totally necessary for development of ROM's, TWRP, and programs for every android device
You may or may not know that your android device is running a Linux kernel, with some Linux programs, with custom folders and custom files and settings, and the touch screen is the GUI graphical user interface touch input.
ADB is a command line user interface, when you turned this on in Developer settings, the kernel is listening constantly on the USB com port and some times on the WiFi com port for commands. if you don't need it turn it off, it could be a security hole, but we need it on.
It works great on windows, mac, or Linux varieties
2. Install on your computer
Code:
[URL]https://developer.android.com/studio/releases/platform-tools[/URL]
If you have linux, your distribution may have a package you can install from your distribution. Then it will be in your path as a command
3. Windows users , extract or install into c:/ADB and add that to your PATH variable if you want to use it all the time as a command
4. Open a command prompt window (search command or cmd , right click open as administrator)
5. If you have ADB folder in your path or are running Linux change directories to the folder where you downloaded the Samsung n4 fix file
6. You should still have root
type
Code:
adb devices
The ADB daemon ( little server program ) will start and return some information.
your phone will have a popup screen and should ask for permission, click allow
again type
Code:
adb devices
7. You should see something like this
Code:
List of devices attached
123a12ab device
The 123a12ab is made up. Yours will be specific to your device.
If you see something listed like the above adb is working. Now on to the next command to move the Samsung_unlock_n4-fix to the phone.
type dir ( or ls -al for Linux users ) to verify Samsung_unlock_n4-fix is in your directory
8. Send Unlocker to Phone with adb
Type or copy and paste the following command:
Code:
adb push samsung_unlock_n4-fix /data/local/tmp/
You should see successful output .
If you don't, check your PATH, check if your in the right folder, or make sure samsung_unlock_n4-fix is in your adb folder
9. Activate the unlocker. This requires root and a reboot. After the reboot you have to go and reactivate root in Section 3.3 above
type the following
Code:
adb shell
Congratulations you are now looking at the linux command line interface on your phone . the $ prompt means you are in the shell
10. activate superuser mode ( kind of like administrator in windows but more powerful )
type
Code:
su
then press enter key
YOU SHOUD NOW SEE a # prompt
This means you succeed in root. If you dont see a # you missed a step above somewhere , or your root was unstable and took too long to get to this point,that is why I said read thru this section and get ready..
Ok at this point we have the file we needed transfered, we have root, now we need to upgrade the permissions on the file so #root level of the operating system can use it !
The next command does all that then executes the command to upgrade your phone to developer edition !
Copy and paste the following command series and press enter.the && joins each command
Code:
cd /data/local/tmp/ && chmod 777 samsung_unlock_n4-fix && chown root.root samsung_unlock_n4-fix && ./samsung_unlock_n4-fix
The device will reboot and flash the developer code.
You should see some sort of progress in the window.
When done ,unplug the cable and pull the battery to shut down phone.
11. Make sure you have a cheap throwaway SD card installed !
One More Time to unlock the boot loader !! section 3 and 4 short version
Put the battery and cable back in and turn the phone back on and make sure its plugged in your PC.
Now repeat the kingoroot PC to gain temp root
open a command prompt or shell
type or copy paste the following to verify its connected
Code:
adb devices
transfer the fix
Code:
adb push samsung_unlock_n4-fix /data/local/tmp/ && a
open the shell on your phone
Code:
adb shell
gain super user rights
Code:
su
unlock the boot loader
same command series
Code:
cd /data/local/tmp/ && chmod 777 samsung_unlock_n4-fix && chown root.root samsung_unlock_n4-fix && ./samsung_unlock_n4-fix
You will see your phone do a series of outputs then reboot. when it reboots, disconnect the cable.
If this step is sucessful your phone will keep rebooting. This is NORMAL . after the first or second reboot, pull the battery and pull the sd card, and set the sdcard aside. It will need to be thrown out or repartititioned to be usable. or you can keep it as a memento on your charm bracelet.
Your bootloader is NOW UNLOCKED . keep phone off until you read the next section
Section 5a: install TWRP custom recovery
Currently right now you have 5.1.1 installed with some Chinese malware on your phone and PC,
A custom developer edition and an unlocked boot loader. Lets fix them all.
Turn on phone download mode . <down volume><home><power> then volume up to enter download mode
Open Odin again ( see above )
Connect phone ( look for com and blue bar )
Select AP button, and browse to TWRP file
Press start. when finished phone will restart.
Don't let it boot all the way back up! , pull battery, and install good SD card, and if you read this section you downloaded what you needed for a new ROM onto your sdcard
Turn off the automatic rebooting in the custom tab, DO NOT select the PIT tab
Press start
Once it finishes it will say Success or FAILED
IF it says FAILED start the whole process over! you didn't unlock the bootloader !
If success, Power off the phone with the pull battery method and disconnect your cable
Press and hold these buttons immediately to enter TWRP ,
<volume up> <home> <power>.
Swipe to allow changes in TWRP.
Select backup , change to SD card, You can also plug in a memory device into the USB port. If it sees it you will be able to use that for backup space
BACKUP everything . You now have a custom recovery installed, a unlocked bootloader, and a rootable ROM Backed UP !
If you feel you want to do this all over again if you flash the OEM Samsung ROM via Odin by accident like I did, ha ha skip the next steps
Select the backup button, select all the partitions, select the source, where you want to store it.
Name the backup rooted-backup-everything-5.1.1
Select start and go make some coffee or a sandwich. its about 4 gigabytes compression, so it may take about 5 to 10 minutes
Clean up -
uninstall windows kingoroot PC and do a virus check
check for hidden folders and registry entries
Section 5b. Install your first ROM
Cleanup : After your backup WIPE your phone twice
THIS IS TO guarantee, no Kingoroot or kingroot stuff is in the phone !!!
WIPE IT TWICE !!!
Some guides (listed below ) say to adb sideload over a root file , then install an older rom. I haven tried this. Let me know if you did and are successful.
Whatever ROM you use, please post a success story in the reply's. I am interested in how you all do.
I have tried every note 4 ROM and this is the most succesful for me and most stable
I have been using this ROM for a while, and the lineageos 14 version too
Code:
[URL]https://forum.xda-developers.com/note-4/snapdragon-dev/oreo-8-1-0-unofficial-lineage-15-1-rom-t3760969[/URL]
In most all ROMS, you can update the bootloader (TWRP) by TWRP app if rooted
you can update the modem ( a partition that contains original Samsung code to run the cell and wireless ) via ODIN
Roms and patches and other goodies can be installed via TWRP by downloading to your device or transfering them to your sd card
Oem ROMS must be installed via ODIN, and will WIPE all you just accomplished. so unless your selling your device, or giving it to grandma DONT.
If you copied the rom ( usually a zip file ) and the necessary files, and have upgraded your bootloader and modem to the newest,
Now install your ROM, and after your initial setup, come back to TWRP and do a full backup !
every time you try a new rom, and get it set up, do a backup. that way you can switch and test to your hearts desire till you run out of SD memory.
The cool thing is you can backup to an external memory device ! more room !
Follow the directions in the OP of your ROM to install. Enjoy
All the above info was gleaned from the following pages
Thanks to @beaups for discovering exploit !!!
Thanks to @hsbadr [HOWTO] Bootloader Unlock and Upgrade to Marshmallow [N910VVRU2CQL1]
Code:
[URL]https://forum.xda-developers.com/note-4-verizon/development/howto-bootloader-unlock-upgrade-to-t3398144[/URL]
and his files
Code:
[URL]https://forum.xda-developers.com/devdb/project/?id=15720#downloads[/URL]
Thanks to @ryanbg [Official] Note 4 Verizon Bootloader Unlock
Code:
[URL]https://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913[/URL]
and @urgodfather
Code:
[URL]https://forum.xda-developers.com/showpost.php?p=66381707&postcount=342[/URL]
Thanks to @chriskader [HOWTO] Converting your Retail Note 4 to a Developer Edition Note 4
and @Mickey387 for discovering how to compile the note 4 32bit hardware drivers into Oreo !!
and @_mone @ripee
for maintaining and working hard on
[ROM][UNOFFICIAL][8.1.0] LineageOS 15.1 [trlte][trlteduos]
Code:
[URL]https://forum.xda-developers.com/note-4/snapdragon-dev/oreo-8-1-0-unofficial-lineage-15-1-rom-t3760969[/URL]
Information Sources: felixtaf, ryanbg, kingroot, twrp, emotion, ibowtoandroid, shimp208, & urgodfather
some of this was also posted on reddit. https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked

Update:
Looking for a motherboard for a 910 that's not a v?
Thanks to user @maralexbar I need to update some info
Method 1 use eBay. Find your correct motherboard easily.
Method 2. Save some money use Ali Express ( China )
If you use Ali, and don't find your motherboard on a direct search, keep digging.
I forgot to mention this.
Looking for my Verizon motherboard, I found lots of parts like the USB internal connector etc. But no mobo. I had to go thru the store listing of the seller of the USB connector to find a vendor that had a mobo. Then I tried comparing different vendors. So do some digging. There is a billion people on Ali express selling stuff. Don't give up.
Plus Ali wants happy international buyers. So if you get a bogus item, you get your money back.

reserved #2
reserved #2

reserved #3
Reserved #3

reserved #4
Reserved #4

Thank you very much for this!!! The phone is running beautifully, smooth and fast. I ended up installing this ROM:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-resurrection-remix-6-0-0-t3768963
BJ

b1ggjoe said:
Thank you very much for this!!! The phone is running beautifully, smooth and fast. I ended up installing this ROM:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-resurrection-remix-6-0-0-t3768963
BJ
Click to expand...
Click to collapse
Your more than welcome

Announcement:
Thanks to @ripee
The lineage-17.1 thread is up!
[ROM][UNOFFICIAL][10] LineageOS 17.1 [tblte][trlte][trlteduos]
If you don't mind not having a working fingerprint sensor, or audio through the headphone jack, then Q is stable enough for daily use. As always when coming from an older rom version, it is highly recommended not to waste your time dirty flashing and just clean flash.
Q is still a work in progress, so I will still be releasing Pie builds, though maybe not as often. As in years past, once the Q bugs have been fixed up to the current Pie level, I will post about when my last Pie build will be. I will upload it to the Downloads tab located at the top of each page of this thread, and link it in the OP.

[GUIDE/TUTORIAL/HOWTO] Google Nexus 7 2013 Stock to Android 13

[GUIDE/TUTORIAL/HOWTO] Google Nexus 7 2013 Stock to Android 13
[GUIDE/TUTORIAL/HOWTO] Google Nexus 7 2013 LTE/deb or Wi-Fi-only/flo to Android 13 / LineageOS 20 with Netflix/Disney+ working
This detailed step-by-step guide helps you transform your Google Nexus 7 (4G or wifi) with Android 6 to a fresher one with Android 13.
### I'll make a few notes using this style: PLEASE READ THEM.
Before going further, make sure you have the correct model.
Go to Settings > About tablet > Model number: Nexus 7
And on tablet's back cover: Nexus is written vertically (horizontally on 2012 model)
### See here if not clear: https://android.stackexchange.com/questions/58273/how-to-distinguish-nexus-7-2012-and-nexus-7-2013
If you have a SIM card slot on the side, it is a LTE model (codename deb), if not, Wi-Fi only alias flo.
Make sure you have latest official updates.
Connect tab to Wi-Fi network.
Go to Settings > About tablet > System updates. Download if update is available.
### WARNING. I'm not sure banking apps will work. Office Lens and Adobe Scan don't work.
### See all my tutorials at https://github.com/djibe/Android-tutorials
### Buy me a coffee: https://ko-fi.com/djibe
CHANGELOG
v10. BitGApps v2, Lanchon repit cited
v9. Android 13, TWRP 3.7 (both by @followmsi)
v8. Back to BitGApps
v7. Hack GApps for Android 12.1/12L (thx to @JamesTanner)
v6. Android 12.1/LOS 19.1
v5. Stick to 12/19 (not 12L/19.1) to wait for compatible BitGApps
v4. Move to Android 12, improve fastboot errors, update Magisk to 24.3 + Netflix access
v3. Move to BitGApps, TWRP 3.6 by @followmsi, repartition script 1380/20 by @k23m
v2. Netflix and Disney+ with Magisk 23 + updated pack, improve readability
v1. Initial release
1) DOWNLOAD
- djibe Nexus 7 2013 pack: https://drive.google.com/file/d/1gPo8YGO-5b6mqugCDyi7T3k94uecwbfZ/view?usp=sharing
(contains USB drivers r13 + fastboot & adb + TWRP recovery 3.7.0_9-0 flo & deb by followmsi + Magisk root + repartition zip sysrepart_1380_20 by @k23m).
### Use Incognito web browser mode if needed to download pack.
Unzip pack on Windows desktop.
For both LTE model/deb & Wi-Fi model re-partitionned/flox
- ROM LineageOS 20 Unofficial by @followmsi (Android 13): https://forum.xda-developers.com/t/rom-flo-deb-unofficial-lineageos-20-0.3569067/
Download latest build: See top link in thread above
### You may also want LineageOS 18.1 Official (Android 11): https://download.lineageos.org/flox (download according BitGApps version)
+ BitGApps ARM 13 v2+ CORE: https://github.com/BiTGApps/BiTGApps-Release/releases/
+ Tablet must be fully charged.
2) INSTALL WINDOWS DRIVERS AND BACKUP
Go to the folder you unzipped earlier.
navigate to usb_driver_r13-windows > usb_driver.
Right click on android_winusb.inf and select Install. Confirm with OK.
Restart Windows.
Make sure Google/provider account is synchronized.
Backup photos, documents, contacts before going any further (ex: use the backupyourmobile app).
Connect tab to PC and retrieve data.
3) UNLOCK BOOTLOADER OF GOOGLE NEXUS 7 2013
In Android, go to Settings > About tablet.
Tap 7 times on "Build number", a notification confirms Developer menu is unlocked.
Go to Settings > Developer options and switch USB debugging ON.
Go to my /djibe folder you unziped earlier. In Windows address bar (ie E:\root\Google Nexus 7 2013\djibe\flash), type cmd and hit Enter
to open a Windows Command.
Connect tablet to PC.
Enter command
Code:
adb devices
Command starts adb and returns
Code:
077955f1 unauthorized
ADB (Android Debug Bridge) has started but tab is waiting for authorization.
On tablet, authorize adb commands from Allow USB debugging dialog: tap on OK.
Then enter command
Code:
adb reboot bootloader
Tab restarts and displays a droid, lowest message is: LOCK STATE - locked
Enter command
Code:
fastboot oem unlock
Using Volume+, select Yes - Unlock bootloader, confirm by pressing Power.
Lowest message is now: LOCK STATE - unlocked
### Unable to run fastboot commands: < waiting for device > ? Go to Windows Device Manager
### While in ADB, driver for Android Device should be named Android Composite ADB Interface. In Fastboot: Android Bootloader Interface
### Click on View > Display hidden devices, right click on Nexus 7 > Uninstall. Reinstall drivers. No success ? Try from another computer
Use Volume keys to select Start and Power to confirm.
Tablet is unlocked.
Configure Android quickly, reactivate Developer options and USB debugging.
Then restart tablet to bootloader using once again
Code:
adb reboot bootloader
4) FLASH TWRP 3.7 RECOVERY
Tablet displays the droid logo.
From Windows command, enter:
Code:
fastboot flash recovery twrp-3.7.0_9-0-flo_followmsi.img
### Or for LTE model:
Code:
fastboot flash recovery twrp-3.7.0_9-0-deb_followmsi.img
Command returns Finished. Total time: 0.995s
Back to tablet, use Volume keys to select Recovery mode, confirm with Power.
### You may experience lagginess within the Recovery.
Welcome to TWRP recovery.
Check Never show this screen during boot again and Swip to Allow Modifications.
Go straight to Backup > select Boot, System, Data partitions.
Swipe to Backup and wait during backup.
Back to home screen > Mount (tablet still connected to PC).
You can access tablet's storage folders from Windows Explorer if Data partition is checked and bottom right button show Disable MTP (within TWRP Mount menu).
From Windows Explorer, navigate to Nexus 7 > Internal Storage.
Copy TWRP folder and paste it somewhere safe on PC.
This is a perfect backup in case of crash.
5) FORMAT PARTITIONS
On tablet, now go to Wipe > Format data.
Type yes and confirm with bottom right check icon.
Now go to Wipe > Advanced Wipe. Select Dalvik / ART Cache, System, Data, Internal Storage, Cache and Swipe to Wipe.
We cannot flash on wiped partitions. Go to Reboot > Recovery and Swipe to Reboot.
Back to Mount menu.
From Windows Explorer, now copy sysrepart_1380_20.zip on Internal Storage.
Disconnect tab.
Back to tablet, go to Install > tap on sysrepart_1380_20.zip and Swipe to flash.
Go to Reboot > Recovery and Swipe to Reboot.
### Repartitioned Wi-Fi model is called flox (instead of flo)
### If you lack space, you should go there: https://forum.xda-developers.com/t/tool-unofficial-port-repit-for-nexus-7-2013-deb-flo.4237183/
6) FLASH ANDROID + GAPPS (+ MAGISK)
On restart, check Never show this screen during boot again and Swipe to Allow Modifications.
Connect tab to PC.
Back to Mount menu.
Copy ROM + GAPPS (+ Magisk) to Internal storage with Windows Explorer.
Go to TWRP Home > Install.
Select lineage-*.zip,
then Add more zips: bitgapps*.zip and Swipe to Install
(for root, needed for Netflix : and Add More Zips, then Magisk.zip)
### If you get Error 70, don't be scared. Tablet doesn't know the System partition was increased.
### Go to Wipe > Advanced Wipe > Resize File System > Swipe to Resize and flash GApps.
(Repeat Reboot to Recovery with Magisk v25.2 if you need root).
Android 13 is installed !
When done message prompts, tap on Wipe Cache/Dalvik and Swipe to Wipe.
Disconnect tab from PC.
Then Reboot System.
Let the tab start (a few minutes).
7) ROOT WITH MAGISK (OPTIONAL)
### Only if you flashed Magisk via TWRP recovery
Do not connect to Android account.
Magisk root starts with Android.
You can manage permissions and extra modules with Magisk Manager app.
Open Files app > Install Magisk.apk.
Then in Magisk goto Settings > Hide magisk app and give it a name, switch Zygisk option ON.
Go to Modules Tab > Install from Storage: MagiskHidePropsConfig and safetynet.
Go to Developer options to disable Android debugging (ADB).
Reboot phone.
You can use yasnac app to check Safetynet passes.
Then with Files App: install netflix and disney+ if needed.
10) OTHER APPS
- You can use GPS Status & Toolbox for faster GPS fix.
- Developer options
Settings > About tablet.
Tap 7 times on build number.
Back to Settings > Developer options
Select USB Configuration > set MTP
Set Windows animation scale, Transition animation scale and Animator duration scale to .5x (or disabled)
Tablet not seen by Windows or Can't access tablet from Windows Explorer ?
Activate Developer options.
Go to Settings > System > Developer options > Default USB configuration > File transfer
11) NETFLIX AND DISNEY+
You may try both apps without more manipulations.
If they don't work, go back to recovery and flash Magisk.
That's it.
Enjoy ;-)
Thanks: @followmsi, @k23m, @nbehary, @DevSwift1, @flex1911, @yattodettaman, @emmett.tsai, TopJohnWu, TWRP team, LineageOS team, BitGApps team
------------------------------------------------------------------------------------------
BOOT TO RECOVERY
Hold Power + Volume- until Droid logo appears and release buttons, this is Bootloader.
Press Volume- twice to show Recovery mode and confirm with Power

Amazing guide. Start to finish in just under an hour. Zero issues.

DefconZero said:
Amazing guide. Start to finish in just under an hour. Zero issues.
Click to expand...
Click to collapse
Hi, glad you like it !
This tab is awesome.

djibe89 said:
Hi, glad you like it !
This tab is awesome.
Click to expand...
Click to collapse
Indeed!
Forgot to add - THANKS to you and all the contributors you mentioned for all the support in keeping this device and the android community alive!

Easy guide, everything seems working just fine except gps not working how do I fix that?
Thanks to you and all the contributors you mentioned for all the support in keeping this device alive

After many unsuccessful attempts (Win64, Linux) I followed these instructions to the letter and it was successful. Thanks!

amem said:
Easy guide, everything seems working just fine except gps not working how do I fix that?
Thanks to you and all the contributors you mentioned for all the support in keeping this device alive
Click to expand...
Click to collapse
Hi,
I don't remember to have GPS failing.
I'm sorry I can't help on this.
I'll try to buy a new tab one day to test it again.

djibe89 said:
Hi,
I don't remember to have GPS failing.
I'm sorry I can't help on this.
I'll try to buy a new tab one day to test it again.
Click to expand...
Click to collapse
Hi
Thanks for taking the time to read my post after reboot It is working fine thanks again

Finally there is a guide which I can refer to as a newbie. Thank you so much!
Not sure why can't boot to recovery mode though...but resolved by manual long hold vol up + power button

andycyc said:
Finally there is a guide which I can refer to as a newbie. Thank you so much!
Not sure why can't boot to recovery mode though...but resolved by manual long hold vol up + power button
Click to expand...
Click to collapse
Hi,
thx for your post.
I'm glad it's useful.

Hi, been running my Nexus 7 rooted and on custom Android 6 based ROM and kernal for probably the last 6 years. Admittedly used very little, but still runs like a champ, if not a little sluggish. So I just decided to check back in to XDA and so happy to find this and try it out. However, GApps link not working for me. "File requested does not exist" Any possibility to fix link?
Thanks very much to OP!!
Edit: wow, pardon the banner, haven't been on XDA like I said for maybe six years, or more!
Edit 2: I believe I found the same GApps from another link djibe89 posted in LG G3 tutorial for the same process. Here:
[GUIDE/TUTORIAL/HOWTO] LG G3 D855 Stock to Android 11
[GUIDE/TUTORIAL/HOWTO] LG G3 D855 Stock to Android 11 [GUIDE/TUTORIAL/HOWTO] LG G3 LG-D855 (Unlocked/Europe) Stock to Android 11 R/LineageOS 18.1 with all files included, Netflix and Disney+ working This detailed step-by-step guide helps you...
forum.xda-developers.com

mookdawg7 said:
Hi, been running my Nexus 7 rooted and on custom Android 6 based ROM and kernal for probably the last 6 years. Admittedly used very little, but still runs like a champ, if not a little sluggish. So I just decided to check back in to XDA and so happy to find this and try it out. However, GApps link not working for me. "File requested does not exist" Any possibility to fix link?
Thanks very much to OP!!
Edit: wow, pardon the banner, haven't been on XDA like I said for maybe six years, or more!
Edit 2: I believe I found the same GApps from another link djibe89 posted in LG G3 tutorial for the same process. Here:
[GUIDE/TUTORIAL/HOWTO] LG G3 D855 Stock to Android 11
[GUIDE/TUTORIAL/HOWTO] LG G3 D855 Stock to Android 11 [GUIDE/TUTORIAL/HOWTO] LG G3 LG-D855 (Unlocked/Europe) Stock to Android 11 R/LineageOS 18.1 with all files included, Netflix and Disney+ working This detailed step-by-step guide helps you...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi, you can use Bitgapps:
BiTGApps Package ARM 11: https://github.com/BiTGApps/BiTGApps-Release/releases
Clean Flash ROM > restart recovery > flash Gapps > reboot
I'm updating tutorial

djibe89 said:
Hi, you can use Bitgapps:
BiTGApps Package ARM 11: https://github.com/BiTGApps/BiTGApps-Release/releases
Clean Flash ROM > restart recovery > flash Gapps > reboot
I'm updating tutorial
Click to expand...
Click to collapse
Fantastic! Everything was going smoothly. But the GApps kept failing on install (Unsupported SDK version, and Install config not found). Thought it might be the version I downloaded, but I came back here and found your reply, so rebooted recovery after Lineage 19 install, installed GApps package, wiped Dalvik/Cache, installed Magisk, wiped dalvik/cache, and rebooted system. Joy! Now appears to be up and running. Seems as though reboot>recovery after ROM flash made the difference. Haven't rooted yet, but I am having a lot of fun. Huge gratitude to you for this tutorial and development work, as well as quick reply. Thank you!
Edit: Ahh, I'm pretty rusty. Realized now Lineage 19 is based off of Android 12, instead of 11. So I installed GApps for 11, not 12. Maybe something to do with it...?

mookdawg7 said:
Fantastic! Everything was going smoothly. But the GApps kept failing on install (Unsupported SDK version, and Install config not found). Thought it might be the version I downloaded, but I came back here and found your reply, so rebooted recovery after Lineage 19 install, installed GApps package, wiped Dalvik/Cache, installed Magisk, wiped dalvik/cache, and rebooted system. Joy! Now appears to be up and running. Seems as though reboot>recovery after ROM flash made the difference. Haven't rooted yet, but I am having a lot of fun. Huge gratitude to you for this tutorial and development work, as well as quick reply. Thank you!
Edit: Ahh, I'm pretty rusty. Realized now Lineage 19 is based off of Android 12, instead of 11. So I installed GApps for 11, not 12. Maybe something to do with it...?
Click to expand...
Click to collapse
Well, I updated tuto for 12.
Choose GApps package accordingly
I'm looking to buy a new one to try 12
And test flashing errors after repartition

djibe89 said:
Well, I updated tuto for 12.
Choose GApps package accordingly
I'm looking to buy a new one to try 12
And test flashing errors after repartition
Click to expand...
Click to collapse
Thanks, worked great for me running unofficial Lineage 19/Android 12! I wasn't able to install official Lineage 18.1. TWRP rejected install because it did not recognize my device as flox. I thought that the repartition package renamed it to this, but anyway that is what I ran into.

mookdawg7 said:
Thanks, worked great for me running unofficial Lineage 19/Android 12! I wasn't able to install official Lineage 18.1. TWRP rejected install because it did not recognize my device as flox. I thought that the repartition package renamed it to this, but anyway that is what I ran into.
Click to expand...
Click to collapse
If you need to force flash one day, you can edit updater-script in ROM archive

djibe89 said:
[GUIDE/TUTORIAL/HOWTO] Google Nexus 7 2013 stock to Android 11 or 12
[GUIDE/TUTORIAL/HOWTO] Google Nexus 7 2013 LTE/deb or Wi-Fi-only/flo to Android 11 or 12 / LineageOS 18.1 or 19 with Netflix/Disney+ working
This detailed step-by-step guide helps you transform your Google Nexus 7 (4G or wifi) with Android 6 to a powerful one with Android 11 R.
### I'll make a few notes using this style: PLEASE READ THEM.
Before going further, make sure you have the correct model.
Go to Settings > About tablet > Model number: Nexus 7
And on tablet's back cover: Nexus is written vertically (horizontally on 2012 model)
### See here if not clear: https://android.stackexchange.com/questions/58273/how-to-distinguish-nexus-7-2012-and-nexus-7-2013
If you have a SIM card slot on the side, it is a LTE model (codename deb), if not, Wi-Fi only alias flo.
Make sure you have latest official updates.
Connect tab to Wi-Fi network.
Go to Settings > About tablet > System updates. Download if update is available.
### WARNING. I'm not sure banking apps will work.
CHANGELOG
v3. Move to BitGApps, TWRP 3.6 by @followmsi, repartition script 1380/20 by @k23m
v2. Netflix and Disney+ with Magisk 23 + updated pack, improve readability
v1. Initial release
1) DOWNLOAD
- djibe Nexus 7 2013 pack: https://drive.google.com/file/d/1gPo8YGO-5b6mqugCDyi7T3k94uecwbfZ/view?usp=sharing
(contains USB drivers r13 + fastboot & adb + TWRP recovery 3.6.0_9-1 flo & deb by followmsi + Magisk root + repartition zip sysrepart_1380_20 by @k23m).
### Use Incognito web browser mode if needed to download pack.
Unzip pack on Windows desktop.
For both LTE model/deb & Wi-Fi model re-partitionned/flox
- ROM LineageOS 18.1 Unofficial: https://forum.xda-developers.com/t/rom-flo-deb-unofficial-lineageos-18-1-2021-05-06.3569067/
Download latest build: See top link in thread above
### You may also use LineageOS 18.1 Official: https://download.lineageos.org/flox
### Want Android 12 (maybe not yet fully stable) ? Enjoy https://forum.xda-developers.com/t/rom-flo-deb-unofficial-lineageos-19-0-2022-01-07.3569067/
+ BiTGApps Package ARM 11: https://github.com/BiTGApps/BiTGApps-Release/releases
+ Tablet must be fully charged to 100%.
2) INSTALL WINDOWS DRIVERS AND BACKUP
Go to the folder you unzipped earlier.
navigate to usb_driver_r13-windows > usb_driver.
Right click on android_winusb.inf and select Install. Confirm with OK.
Restart Windows.
Make sure Google/provider account is synchronized.
Backup photos, documents, contacts before going any further (ex: use the backupyourmobile app).
Connect tab to PC and retrieve data.
3) UNLOCK BOOTLOADER OF GOOGLE NEXUS 7 2013
In Android, go to Settings > About tablet.
Tap 7 times on "Build number", a notification confirms Developer menu is unlocked.
Go to Settings > Developer options and switch USB debugging ON.
Open a Windows command prompt on the /djibe pack folder you unziped earlier:
select folder with left click, right click while holding SHIFT on keyboard > Open command windows here
Connect tablet to PC.
Enter command
Code:
adb devices
Command starts adb and returns
Code:
077955f1 unauthorized
ADB (Android Debug Bridge) has started but tab is waiting for authorization.
On tablet, authorize adb commands from Allow USB debugging dialog: tap on OK.
Then enter command
Code:
adb reboot bootloader
Tab restarts and displays a droid, lowest message is: LOCK STATE - locked
Enter command
Code:
fastboot oem unlock
Using Volume+, select Yes - Unlock bootloader, confirm by pressing Power.
Lowest message is now: LOCK STATE - unlocked
Use Volume keys to select Start and Power to confirm.
Tablet is unlocked.
Configure Android fast, reactivate Developer options and USB debugging.
Then restart tablet to bootloader using once again
Code:
adb reboot bootloader
4) FLASH TWRP 3.5/3.6 RECOVERY
Tablet displays the droid logo.
Enter this command
Code:
fastboot flash recovery twrp-3.6.0_9-1-flo_followmsi.img
### Or for LTE model:
Code:
fastboot flash recovery twrp-3.6.0_9-1-deb_followmsi.img
Command returns Finished. Total time: 0.995s
Use Volume keys to select Recovery mode, confirm with Power.
### You may experience lagginess within the Recovery.
Welcome to TWRP recovery.
Check Never show this screen during boot again and Swip to Allow Modifications.
Go straight to Backup > select Boot, System, Data partitions.
Swipe to Backup and wait during backup.
Back to home screen > Mount.
You can access folders from PC if Data partition is checked and bottom right button show Disable MTP.
From Windows Explorer, navigate to Nexus 7 > Internal Storage.
Copy TWRP folder and paste it somewhere safe on PC.
This is a perfect backup in case of crash.
5) FORMAT PARTITIONS
Now go to Wipe > Format data.
Type yes and confirm with bottom right check icon.
Now go to Wipe > Advanced Wipe, select Dalvik / ART Cache, System, Data, Internal Storage, Cache and Swipe to Wipe.
We cannot flash on wiped partitions. Go to Reboot > Recovery and Swipe to Reboot.
Back to Mount.
Copy sysrepart_1280_120.zip on Internal Storage.
Disconnect tab.
Go to Install > tap on sysrepart_1380_20.zip and Swipe to flash.
Go to Reboot > Recovery and Swipe to Reboot.
### Repartitioned Wi-Fi model is called flox (instead of flo)
6) FLASH ANDROID + BITGAPPS (+ MAGISK)
On restart, check Never show this screen during boot again and Swipe to Allow Modifications.
Connect tab to PC.
Back to Mount menu.
Copy ROM + GAPPS (+ Magisk) to Internal storage with Windows Explorer.
Go to TWRP Home > then Install.
Select lineage-*.zip,
(for root: and Add More Zips, then Magisk.zip)
and Swipe to force install.
After flash, go to Reboot > Recovery
After TWRP reboot, go to Install > BiTGApps*.zip and Swipe to Install.
### If you get Error 70, don't be scared. Tablet doesn't know the System partition was increased.
### Go to Wipe > Advanced Wipe > Resize File System > Swipe to Resize and flash BitGApps.
Android 11 (or 12) is installed !
When done message prompts, tap on Wipe Cache/Dalvik and Swipe to Wipe.
Disconnect tab from PC.
Then Reboot System.
Let the tab start (a few minutes).
7) ROOT WITH MAGISK (OPTIONAL)
### Only if you flashed Magish via TWRP recovery.
Configure Android as you like.
Magisk root starts with Android.
You can manage permissions and extra modules with Magisk Manager app.
If Magisk Manager doesn't download apk. Download official apk here: https://github.com/topjohnwu/Magisk/releases
10) OTHER APPS
- You can use GPS Status & Toolbox for faster GPS fix.
- Developer options
Settings > About tablet.
Tap 7 times on build number.
Back to Settings > Developer options
Select USB Configuration > set MTP
Set Windows animation scale, Transition animation scale and Animator duration scale to .5x
11) NETFLIX AND DISNEY+
You may try both apps without more manipulations.
If they don't work, go back to recovery anf flash Magisk.
Open Magisk app (v23+).
Go to Settings > go to App Rename app to Godmode to hide hide.
Below, switch MagiskHide ON.
Now go to Magisk Modules tab > install liboemcrypto disabler and MagiskHide Props Config.
Connect to your Google account, download from Play Store Netflix and Disney+.
### If you are already connected to Google account.
Clear cache (Settings > Apps > All apps > Google Play Store > Storage > Clear storage) and restart tab.
Relaunch Play Store, Netflix and Disney+ will be available in SD.
That's it.
Enjoy ;-)
Thanks: @followmsi, @k23m, @nbehary, @DevSwift1, @flex1911, @yattodettaman, @emmett.tsai, TopJohnWu, TWRP team, LineageOS team, BitGApps team
Click to expand...
Click to collapse
I followed the instructions and successfully installed the OS. It was working fine, but after some time touchscreen became unresponsive and now I can't do anything. I tried restarting using the power button and got into recovery, even in recovery, the touch screen is not responding. Someone, Please help.

moneyrockers said:
I followed the instructions and successfully installed the OS. It was working fine, but after some time touchscreen became unresponsive and now I can't do anything. I tried restarting using the power button and got into recovery, even in recovery, the touch screen is not responding. Someone, Please help.
Click to expand...
Click to collapse
Hi, is ADB active ?

djibe89 said:
[GUIDE/TUTORIAL/HOWTO] Google Nexus 7 2013 stock to Android 11 or 12
[GUIDE/TUTORIAL/HOWTO] Google Nexus 7 2013 LTE/deb or Wi-Fi-only/flo to Android 11 or 12 / LineageOS 18.1 or 19 with Netflix/Disney+ working
This detailed step-by-step guide helps you transform your Google Nexus 7 (4G or wifi) with Android 6 to a powerful one with Android 11 R.
### I'll make a few notes using this style: PLEASE READ THEM.
Before going further, make sure you have the correct model.
Go to Settings > About tablet > Model number: Nexus 7
And on tablet's back cover: Nexus is written vertically (horizontally on 2012 model)
### See here if not clear: https://android.stackexchange.com/questions/58273/how-to-distinguish-nexus-7-2012-and-nexus-7-2013
If you have a SIM card slot on the side, it is a LTE model (codename deb), if not, Wi-Fi only alias flo.
Make sure you have latest official updates.
Connect tab to Wi-Fi network.
Go to Settings > About tablet > System updates. Download if update is available.
### WARNING. I'm not sure banking apps will work.
CHANGELOG
v3. Move to BitGApps, TWRP 3.6 by @followmsi, repartition script 1380/20 by @k23m
v2. Netflix and Disney+ with Magisk 23 + updated pack, improve readability
v1. Initial release
1) DOWNLOAD
- djibe Nexus 7 2013 pack: https://drive.google.com/file/d/1gPo8YGO-5b6mqugCDyi7T3k94uecwbfZ/view?usp=sharing
(contains USB drivers r13 + fastboot & adb + TWRP recovery 3.6.0_9-1 flo & deb by followmsi + Magisk root + repartition zip sysrepart_1380_20 by @k23m).
### Use Incognito web browser mode if needed to download pack.
Unzip pack on Windows desktop.
For both LTE model/deb & Wi-Fi model re-partitionned/flox
- ROM LineageOS 18.1 Unofficial: https://forum.xda-developers.com/t/rom-flo-deb-unofficial-lineageos-18-1-2021-05-06.3569067/
Download latest build: See top link in thread above
### You may also use LineageOS 18.1 Official: https://download.lineageos.org/flox
### Want Android 12 (maybe not yet fully stable) ? Enjoy https://forum.xda-developers.com/t/rom-flo-deb-unofficial-lineageos-19-0-2022-01-07.3569067/
+ BiTGApps Package ARM 11: https://github.com/BiTGApps/BiTGApps-Release/releases
+ Tablet must be fully charged to 100%.
2) INSTALL WINDOWS DRIVERS AND BACKUP
Go to the folder you unzipped earlier.
navigate to usb_driver_r13-windows > usb_driver.
Right click on android_winusb.inf and select Install. Confirm with OK.
Restart Windows.
Make sure Google/provider account is synchronized.
Backup photos, documents, contacts before going any further (ex: use the backupyourmobile app).
Connect tab to PC and retrieve data.
3) UNLOCK BOOTLOADER OF GOOGLE NEXUS 7 2013
In Android, go to Settings > About tablet.
Tap 7 times on "Build number", a notification confirms Developer menu is unlocked.
Go to Settings > Developer options and switch USB debugging ON.
Open a Windows command prompt on the /djibe pack folder you unziped earlier:
select folder with left click, right click while holding SHIFT on keyboard > Open command windows here
Connect tablet to PC.
Enter command
Code:
adb devices
Command starts adb and returns
Code:
077955f1 unauthorized
ADB (Android Debug Bridge) has started but tab is waiting for authorization.
On tablet, authorize adb commands from Allow USB debugging dialog: tap on OK.
Then enter command
Code:
adb reboot bootloader
Tab restarts and displays a droid, lowest message is: LOCK STATE - locked
Enter command
Code:
fastboot oem unlock
Using Volume+, select Yes - Unlock bootloader, confirm by pressing Power.
Lowest message is now: LOCK STATE - unlocked
Use Volume keys to select Start and Power to confirm.
Tablet is unlocked.
Configure Android fast, reactivate Developer options and USB debugging.
Then restart tablet to bootloader using once again
Code:
adb reboot bootloader
4) FLASH TWRP 3.5/3.6 RECOVERY
Tablet displays the droid logo.
Enter this command
Code:
fastboot flash recovery twrp-3.6.0_9-1-flo_followmsi.img
### Or for LTE model:
Code:
fastboot flash recovery twrp-3.6.0_9-1-deb_followmsi.img
Command returns Finished. Total time: 0.995s
Use Volume keys to select Recovery mode, confirm with Power.
### You may experience lagginess within the Recovery.
Welcome to TWRP recovery.
Check Never show this screen during boot again and Swip to Allow Modifications.
Go straight to Backup > select Boot, System, Data partitions.
Swipe to Backup and wait during backup.
Back to home screen > Mount.
You can access folders from PC if Data partition is checked and bottom right button show Disable MTP.
From Windows Explorer, navigate to Nexus 7 > Internal Storage.
Copy TWRP folder and paste it somewhere safe on PC.
This is a perfect backup in case of crash.
5) FORMAT PARTITIONS
Now go to Wipe > Format data.
Type yes and confirm with bottom right check icon.
Now go to Wipe > Advanced Wipe, select Dalvik / ART Cache, System, Data, Internal Storage, Cache and Swipe to Wipe.
We cannot flash on wiped partitions. Go to Reboot > Recovery and Swipe to Reboot.
Back to Mount.
Copy sysrepart_1280_120.zip on Internal Storage.
Disconnect tab.
Go to Install > tap on sysrepart_1380_20.zip and Swipe to flash.
Go to Reboot > Recovery and Swipe to Reboot.
### Repartitioned Wi-Fi model is called flox (instead of flo)
6) FLASH ANDROID + BITGAPPS (+ MAGISK)
On restart, check Never show this screen during boot again and Swipe to Allow Modifications.
Connect tab to PC.
Back to Mount menu.
Copy ROM + GAPPS (+ Magisk) to Internal storage with Windows Explorer.
Go to TWRP Home > then Install.
Select lineage-*.zip,
(for root: and Add More Zips, then Magisk.zip)
and Swipe to force install.
After flash, go to Reboot > Recovery
After TWRP reboot, go to Install > BiTGApps*.zip and Swipe to Install.
### If you get Error 70, don't be scared. Tablet doesn't know the System partition was increased.
### Go to Wipe > Advanced Wipe > Resize File System > Swipe to Resize and flash BitGApps.
Android 11 (or 12) is installed !
When done message prompts, tap on Wipe Cache/Dalvik and Swipe to Wipe.
Disconnect tab from PC.
Then Reboot System.
Let the tab start (a few minutes).
7) ROOT WITH MAGISK (OPTIONAL)
### Only if you flashed Magish via TWRP recovery.
Configure Android as you like.
Magisk root starts with Android.
You can manage permissions and extra modules with Magisk Manager app.
If Magisk Manager doesn't download apk. Download official apk here: https://github.com/topjohnwu/Magisk/releases
10) OTHER APPS
- You can use GPS Status & Toolbox for faster GPS fix.
- Developer options
Settings > About tablet.
Tap 7 times on build number.
Back to Settings > Developer options
Select USB Configuration > set MTP
Set Windows animation scale, Transition animation scale and Animator duration scale to .5x
11) NETFLIX AND DISNEY+
You may try both apps without more manipulations.
If they don't work, go back to recovery anf flash Magisk.
Open Magisk app (v23+).
Go to Settings > go to App Rename app to Godmode to hide hide.
Below, switch MagiskHide ON.
Now go to Magisk Modules tab > install liboemcrypto disabler and MagiskHide Props Config.
Connect to your Google account, download from Play Store Netflix and Disney+.
### If you are already connected to Google account.
Clear cache (Settings > Apps > All apps > Google Play Store > Storage > Clear storage) and restart tab.
Relaunch Play Store, Netflix and Disney+ will be available in SD.
That's it.
Enjoy ;-)
Thanks: @followmsi, @k23m, @nbehary, @DevSwift1, @flex1911, @yattodettaman, @emmett.tsai, TopJohnWu, TWRP team, LineageOS team, BitGApps team
Click to expand...
Click to collapse
hi i followed the tutorial but when i flash twrp recovery then the touch is not working inside the recovery.its really annoying, can you please help me with this im using nexus 7 2013 LTE version

ShivaRK666 said:
hi i followed the tutorial but when i flash twrp recovery then the touch is not working inside the recovery.its really annoying, can you please help me with this im using nexus 7 2013 LTE version
Click to expand...
Click to collapse
Hi, can you try with suitable 3.5 TWRP ?
[ROM][flo|deb][UNOFFICIAL][LineageOS 20.0]
LineageOS 20.0 lineage-20.0-20230507-UNOFFICIAL-flo.zip lineage-20.0-20230507-UNOFFICIAL-deb.zip Known issues: - We are still Permissive (SELinux) - Encryption is not working .. Pls do NOT encrypt your /data partition! - Camera is not fully...
forum.xda-developers.com