Database Users

[ROM] Sero 7 Pro (US/UK/AU/DE) - AOSP 4.4.4_r2 DoPa v2.7

** DoPa6 (AOSP - Marshmallow) ** is now available - see this post for details and downloads
Click to expand...
Click to collapse
** DoPa5 (AOSP - Kitkat) ** is now available - see this post for details and downloads
Click to expand...
Click to collapse
DoPa v2.7 is a ROM for Sero 7 Pro owners everywhere. Whether bought in the US, Britain, Australia, Germany, or elsewhere, your tablet is supported.
The ROM starts with well-tested AOSP code and adds core functions where needed but skips the frills that are easy to add on - and remove when they cause problems. It's aimed at people who want to choose their own features and not have them imposed by the developer.
New / Improved
International Support - a single ROM for all Sero 7 Pros sold worldwide
New in v2.7 - support for the German model of the Sero 7 Pro (m470bsg)
Speed Control - a unified kernel provides speed when you need it and stock performance when you don't.
Use the new Performance page in the Settings app to control it
exFAT - support has been moved into the kernel for improved performance
Boot Animation - a handsome new DoPa animation thanks to @mikembley, our first-ever UK user
To get you started customizing your ROM, v2.7 offers these add-ons:
built-in: SuperSU, Xposed Installer GravityBox, Phab7
optional: have your tablet claim it's a Nexus7 to get more apps in PlayStore
The package does not include any Google apps (e.g. Playstore). See this thread for links to the latest GApps packages.
Installation
UK / AU / DE / First-time Users
If you're upgrading from a stock ROM (any variety), please click the "show content" button and read the instructions very carefully - they're long but your tablet's continued good health may depend on it!
STEP 1: Install Philz Touch Recovery
Users outside the US must use this version of Philz to install the ROM - neither the stock recovery nor other versions of CWM or Philz will work. Users in the US should use it just to avoid problems.
Stock Recovery
If you still have the stock recovery program you'll have to use the 'fastboot' program to install Philz. On Windows, this requires installation of the 'ADB' USB drivers while in fastboot mode (see below). A package containing the drivers, fastboot, adb and other files can be found in the 2nd posting on the DoPa Stock ROM thread. Note: there are several batch files (*.bat) in the package - do NOT run them.
put fastboot.exe in a convenient directory, then unzip sero7pro-philz6.58.0-dopa-v2.7.zip and put the file philz.img in the same directory (you won't need the other files)
unplug any USB cable, then press and hold Power+VolumeUp; the word "fastboot" should appear on the screen (nothing further will appear)
plug the USB cable from your PC into the tablet, then install the driver (open Device Manager, right click on "Other Devices->Fastboot", then select "Update Driver Software")
after installing the driver, open a command prompt ("DOS window") and change to the directory containing the files
enter fastboot flash recovery philz.img
when done, force the tablet off, remove the USB cable, then reboot into recovery: Power+VolumeDown - you should see the word "recovery", then the Philz menu
CWM
If you have CWM installed, copy sero7pro-philz6.58.0-dopa-v2.7.zip to an SD card, insert it in the tablet, then:
remove any USB cable, then boot into recovery: Power+VolumeDown
select "Install Zip", then "Choose zip from /storage/sdcard1"
select the file, then OK the selection
when done, back out to the main menu, select "Advanced options", then "Reboot recovery"
after the initial "recovery" screen, you should see the Philz menu
Regardless of how you install Philz, the result should be the same. If it boots OK, compatibility is assured
STEP 2: Backup
I can't emphasize this enough: you must make a backup of your existing ROM. If something goes wrong, there's no way to get your device working again other than to restore it using the backup you've made. There's also another reason to do a backup: before installing the new ROM, you will have to reformat your /data partition. This will wipe out your apps, your settings, and most importantly, all the music/photos/etc stored on your "internal SDcard". These last items can be restored if you follow the instructions below:
ROM
You must do your backup onto a real SD card that you can remove because your "internal SDcard" will be erased in the next step. In fact, it wouldn't be a bad idea to do two backups (preferably to different cards) just in case one is faulty.
on Philz main menu, select "Backup and Restore"
next, select "Backup to /storage/sdcard1" (the 6th item on that menu)
if there's enough space on the card, the backup will start without any further prompt; it could take anywhere from 3 to 15+ minutes depending on the amount of data and the speed of your card
if needed, you can enable compression to create a smaller backup: select "Misc Nandroid Settings -> Default Backup Format -> tar + gzip", then on the previous menu, tap on "Compression" to set the appropriate level
Internal SD card
This is optional but worthwhile if you have files you value stored on the tablet:
on Philz main menu, select "Backup and Restore"
next, select "Custom Backup to /storage/sdcard1" (the 9th item on that menu)
on the next screen, deselect everything, then select "Backup /data/media" (the next-to-last item)
finally, select "Start Custom Backup Job"
STEP 3: Install the DoPa ROM
Before you begin, you may want to download a Google Apps ("Gapps") package that you can install after the ROM. See this thread for a selection of packages. To avoid complications, I'd suggest choosing the "Nano Modular Package" to get just the basics - you can always upgrade later. Put your Gapps package along with the ROM zip on an SD card and insert it into the tablet - you can use the same card you're using for your backups.
on Philz main menu, select "Wipe and Format Options", then "Custom Format Options"
select "format /data and /data/media (/sdcard)" (the 8th item), then OK your choice
back on the main menu, select "Install Zip -> Choose zip from /storage/sdcard1"
select sero7pro-aosp444-dopa-v2.7.zip, then OK your choice - the install process should take about 40 seconds
next, install your Gapps package
return to the main menu, select "Reboot System Now", then hold your breath for the next 3-4 minutes
the Hisense screen should be up for less than a minute, followed by the DoPa boot animation for another 2-3 minutes
when the Google setup screen appears, you'll probably get a warning that "Bluetooth Sharing" has stopped - after you clear it, you'll never see it again
If the boot animation is still running after 5+ minutes, force the tablet off, then reboot. If that doesn't fix it, try formatting /data again. If it still doesn't work, restore your tablet from your backup ("Backup and Restore -> Restore from /storage/sdcard1"), then post a message here. If everything works out as hoped for, re-read the first posting in this thread for details on some of the features (and problems) of this ROM.
Upgrades
While any SELinux-enabled version of CWM or TWRP can be used to install the ROM, the companion Philz Touch CWM-based recovery is highly recommended if you use exFAT-formatted SD cards.
from DoPa AOSP Kitkat ROMs (v1.0-v2.6) - no need to wipe or format anything!
from pre-Kitkat (v4.4.x) or any CM-based ROMs - wipe your /data partition before installing to avoid unnecessary problems.
install sero7pro-aosp444-dopa-v2.7.zip
- the installer will wipe (but NOT format) /cache and dalvik-cache for you
install your preferred Gapps package
- upgraders: this is required to prevent your downloaded Google apps from crashing
optionally, install the Nexus7 spoof (sero7pro-nexus7spoof-dopa-v2.7.zip)
reboot (ignore any "fix root" prompt - it's incorrect)
f2fs / ext4 Migration
This DoPa ROM gives you the flexibility to format any of your built-in partitions using either the f2fs or ext4 file systems.
As part of your install - or at any time - you can switch formats without losing any data. Click "show content" for instructions.
If you haven't already installed Philz Touch Recovery, please do so first. Philz has gotten complicated, so read this carefully!
make a nandroid backup to your external SD card
select Wipe and Format Options, then Custom Format Options
select toggle f2fs <-> ext4 migration
- be sure there's a confirmation message at the bottom of the screen
select each partition you want to convert or wipe, then select the format and OK your choice
Important: to convert your /data partition, you must select format /data and /data/media (/sdcard)!!!
use Custom Restore from /storage/sdcard1 to restore the contents of the partitions you reformatted
Notes
Speed Control - this version uses a redesigned kernel that caps processor speeds at stock levels during start-up, then adjusts them once the tablet is up and running. Go to Settings->Performance to enable this feature, and to set the top speeds for the CPU (1.0-1.5ghz) and GPU (448-520mhz). When disabled,the processor will remain at stock speeds (1.2ghz/448mhz) unless changed by a 3rd-party app.
Encryption - the first time you formatted your /data partition, you lost the ability to encrypt your tablet's data. Using the companion Philz Touch Recovery to reformat /data (using either filesystem) will restore that ability. To preserve your existing data, do a backup first, then restore just /data when done. Note: you must select "format /data and /data/media (/sdcard)" when reformatting.
OTG Charging Support - this kernel supports charging the tablet while an external device (flash drive, keyboard, etc.) is attached to the USB port. This feature requires either an OTG 'Y' cable or an OTG USB hub, and the AC adapter that came with the tablet. For this to work, power must be connected to the cable or hub before plugging it into your tablet. The OTG device(s) can be attached/detached at any time.
WiFi Display (a.k.a. Miracast) - video works but its performance may depend upon your TV; audio does not work.
Bluetooth Sharing - on the initial boot, this service will FC due to a timing issue. The system will restart it and you should never see this error again.
Added/Changed in v2.6
International Support - added support to the kernel for the British and Australian models of the Sero 7 Pro
Overclocking - replaced separate standard and overclocked kernels with a unified kernel that uses less power when overclocked; added a new Performance page to the Settings app to control it
exFAT Support - moved exFAT support to the kernel for improved performance
Boot Animation - added a custom boot animation created by @mikembley
Added/Changed in v2.51
Flexible Formatting - added F2FS support for the /thirdparty and /mnt/modem partitions
Bug Fix - enabled Philz Touch Recovery to format the /thirdparty and /mnt/modem partitions using EXT4
Added/Changed in v2.5
Flexible Formatting - enabled use of either F2FS or EXT4 for any of the built-in partitions
External Storage - added support for F2FS, and for devices formatted without a partition table (i.e. Windows-style "super-floppies")
Android version - upgraded from AOSP 4.4.4_r2 to AOSP 4.4.4_r2.0.1
Recovery - added a DoPa version of Philz Touch Recovery
Added/Changed in v2.1
SD Cards - added support for SD cards formatted with the NTFS or exFAT filesystems
Android version - upgraded from AOSP 4.4.4_r1 to AOSP 4.4.4_r2
Added/Changed in v2.0
Google Now - voice activation (i.e "OK Google") now works in the Google Now launcher
kernel - added OTG charging support.
Credits
ziddey
randomblame
davepmer
the CM team
Downloads
sero7pro-aosp444-dopa-v2.7.zip the full ROM
sero7pro-nexus7spoof-dopa-v2.7.zip identify tablet as a Nexus7 to (possibly) show more apps in PlayStore
sero7pro-philz6.58.0-dopa-v2.7.zip a customized version of Philz Touch CWM-based Recovery v6.58.0
sero7pro-format-thirdparty.zip - only needed if you are downgrading from DoPa6 (Marshmallow) to previous versions (i.e. this one)
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.

Thanks man been running it since day one no problems and very stable.

Can We call these the Semi OFFICIAL ROM ?

I installed v1 after it booted up play store wasn't installed. Did any one else experience this? I did a dirty flash and a full wipe.
Sent from my Sero 7 Pro using xda app-developers app

How much free space should there be on a system after a fresh install?

datboy143 said:
I installed v1 after it booted up play store wasn't installed. Did any one else experience this? I did a dirty flash and a full wipe.
Sent from my Sero 7 Pro using xda app-developers app
Click to expand...
Click to collapse
I followed the instructions and noticed the same thing and gmail kept crashing. Flashing the latest gapps will fix all of that. I still have some testing to do and will report back later.

Gazoo119 said:
I followed the instructions and noticed the same thing and gmail kept crashing. Flashing the latest gapps will fix all of that. I still have some testing to do and will report back later.
Click to expand...
Click to collapse
Ok will do thanks
Sent from my SGH-I777 using xda app-developers app

GPS and Google music
I noticed on version 0 that GPS could take awhile to lock on, and if you turned it off and back on that sometimes it wouldn't lock on at all. I also noticed an issue when running Google music where it would freeze and cause the tablet to reboot. Anyone having these issues on the new build? Otherwise, this is one of the cleanest KitKat builds I've used

gotshores said:
I noticed on version 0 that GPS could take awhile to lock on, and if you turned it off and back on that sometimes it wouldn't lock on at all. I also noticed an issue when running Google music where it would freeze and cause the tablet to reboot. Anyone having these issues on the new build? Otherwise, this is one of the cleanest KitKat builds I've used
Click to expand...
Click to collapse
Don't use Google music but I do use scanner radio and whenever I switched streams the tablet would freeze and I would have to hold the power button to turn the tablet off.
Now its working like it should. So this latest build might fix Google music.
Another issue I was having is when I opened the calendar it would not close hitting the back button. Its closes fine now.
The GPS doesn't seem to load any slower for me than it did with the stock ROM but I don't use it much.
Anyway I would recommend trying this latest build. Just make sure you wipe cache and dalvik cache and flash the latest gapps. Everything should still be the same as before when you boot with the new ROM and hopefully you will notice some improvements.
---------- Post added at 07:31 PM ---------- Previous post was at 07:22 PM ----------
dolorespark said:
This is a plain-vanilla build of KitKat for those who prefer their enhancements added on rather than built in.
Click to expand...
Click to collapse
Just want to thank you for fixing the sound bug. V4A is working perfectly and as far as I can tell so is everything else. I will keep testing and if I run across anything strange I will post here. Your work on this is very much appreciated

dolorespark said:
This is a plain-vanilla build of KitKat for those who prefer their enhancements added on rather than built in. The only changes to the AOSP and kernel code are those needed to ensure compatibility or to enable standard features Hisense omitted (e.g. USB-OTG support). Because it relies on well-tested AOSP code, it is likely the most stable KitKat ROM available for this tablet. For the same reasons, it is almost certainly not the fastest KitKat ROM either.
To make it more functional, the package includes a handful of apps most people find useful: SuperSU, ES File Explorer, Xposed Installer, GravityBox, and my Phab7 UI switcher. To avoid the wrath of Google, it does not include any GApps; see this thread for links to the latest packages.
Installation
Having an SELinux-enabled version of CWM or TWRP installed is a prerequisite. You can find versions built by randomblame here or by davepmer here.
If you're upgrading from v0 of this ROM, clearing cache and dalvik-cache should suffice. Otherwise, do a full wipe of both your data and cache partitions. As always, a backup of your existing setup is recommended.
Notes
All features should be present and work as expected with these exceptions:
WiFi Display (a.k.a. Miracast) - video is enabled but very slow; audio is disabled because it doesn't work and generates 45 error messages per second when enabled
SELinux - the kernel runs in permissive mode due to missing entries in its configuration.
As these issues are resolved, the ROM will be updated accordingly.
Credits
randomblame
davepmer
the CM team
Download
sero7pro-aosp442-dopa-v1.zip
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.
DoPa
Click to expand...
Click to collapse
Thanks for the rom. After flashing the rom I rebooted, powered down and installed gapps. On reboot I got a message about root access possibly being lost and offering to fix it, I said yes. First time I get that, is it ok? (It seems to be working ok)

chopin_k said:
Thanks for the rom. After flashing the rom I rebooted, powered down and installed gapps. On reboot I got a message about root access possibly being lost and offering to fix it, I said yes. First time I get that, is it ok? (It seems to be working ok)
Click to expand...
Click to collapse
This is normal..
Sent from my Sero 7 Pro using XDA Premium 4 mobile app

enfermo said:
Can We call these the Semi OFFICIAL ROM ?
Click to expand...
Click to collapse
Generic, yes - (semi-)Official, no.
datboy143 said:
I installed v1 after it booted up play store wasn't installed.
Click to expand...
Click to collapse
Gazoo119 said:
I followed the instructions and noticed the same thing and gmail kept crashing. Flashing the latest gapps will fix all of that.
Click to expand...
Click to collapse
As noted in the OP, none of the GApps (e.g. Playstore) were included in this ROM. I have updated its verbiage to be even more explicit. As to GMail crashing, I'm a little puzzled how that could happen if it wasn't included - did you mean the generic Email app?
gotshores said:
I noticed on version 0 [...] an issue when running Google music where it would freeze and cause the tablet to reboot. Anyone having these issues on the new build?
Click to expand...
Click to collapse
I hope not: v1 wouldn't have been released if that bug were still present. The problems you encountered were caused by enabling sound effects, either built-in or 3rd-party - the notes for v0 said as much. Perhaps Google Music enabled them automatically.
chopin_k said:
Thanks for the rom. After flashing the rom I rebooted, powered down and installed gapps. On reboot I got a message about root access possibly being lost and offering to fix it, I said yes. First time I get that, is it ok? (It seems to be working ok)
Click to expand...
Click to collapse
I ran into that too - and something even odder. SuperSU's su and daemonsu program files should have a flag that marks them as authorized to give root access. That flag is now missing but I can still get root whenever needed. I don't know if this is to be expected with SELinux in place or just something specific to SuperSU. I'll investigate...
tinybeetle said:
How much free space should there be on a system after a fresh install?
Click to expand...
Click to collapse
After installing the ROM, the "Gapps Standard" package, and Antutu, Settings->Storage says I have 5.48gb available. This is the free space on your /data partition and includes the space used by your emulated SD Card (which is actually just a subdirectory of /data).

"Smart ass alert"
Not only was playstore not installed, it doesn't give me the winning lottery numbers for next week! What gives?
Ok, being serious, Thank you for your time and effort. This weekend I am going to finally give this a try.

Dolorespark,
I haven't messed with any sound effect settings, so it must be Google Music messing with things. Have you noticed any issues with GPS? I can run any of the other rom's, including CM11, and it locks on immediately, but it seems random with AOSP. Sometimes I'll wait a coupled of minutes and it'll get a lock, and other times it won't lock on at all. Anyway, thanks for all you do. I'll keep testing, and keep my trusty backup of DOPA v2.

Working brilliantly so far. V0 to V1 smooth after adding gapps back to the mix. Sounds like time to reinstall V4A and sync some commute podcasts!
Thanks Dolorespark!

envygreen said:
Working brilliantly so far. V0 to V1 smooth after adding gapps back to the mix. Sounds like time to reinstall V4A and sync some commute podcasts!
Thanks Dolorespark!
Click to expand...
Click to collapse
intermittently get google services has stopped.... only that but everything looks good so far.... anything to fix google services stopping? also had a root fix need after rebooting, did yes and everything is ok... thanks DOPA....

dolorespark said:
I hope not: v1 wouldn't have been released if that bug were still present. The problems you encountered were caused by enabling sound effects, either built-in or 3rd-party - the notes for v0 said as much. Perhaps Google Music enabled them automatically.
Click to expand...
Click to collapse
I had this issue on v0 as well and it seems that it's not gone yet. I only wiped dalvik & cache coming from v0 so I'm not sure if that's part of the problem, but I'm still experiencing the Google Play Music crash. It only seems to crash when playing content that hasn't already been cached locally. Attached is a logcat.

dolorespark said:
As noted in the OP, none of the GApps (e.g. Playstore) were included in this ROM. I have updated its verbiage to be even more explicit. As to GMail crashing, I'm a little puzzled how that could happen if it wasn't included - did you mean the generic Email app?
Click to expand...
Click to collapse
No it was gmail. It would close followed by the message "unfortunately this application has closed" or something like that. It wasn't really crashing but rather would not stay open. Anyway flashing the latest gapps fixed that and all is good for me so far.
I played with the tablet extensively last night and did not experience any problems. Even movies, streaming or local using XBMC play using a bluetooth headset. There is no stuttering as there was in all of the previous Jelly Bean roms, stock....DoPa1 and DoPa2. I don't know if that was a KitKat fix or what but I am very happy with the stability of this rom and the fact the XBMC bluetooth bug was fixed is icing on the cake. Of course V4A makes it even better.
I will continue to run the rom and will post if I find any bugs. Thanks again.:good:

Been running since v1 was posted. Have to say the music bug is no more! Listening to lucky mixes all day today and email, g+, and everything my wife and kids have done on it. No problems! Thanks You have really taken your time to make this rom perfect!!!!

Gazoo119 said:
[gmail] would close followed by the message "unfortunately this application has closed" or something like that. It wasn't really crashing but rather would not stay open. Anyway flashing the latest gapps fixed that and all is good for me so far.
Click to expand...
Click to collapse
nccruz said:
intermittently get google services has stopped.... only that but everything looks good so far.... anything to fix google services stopping?
Click to expand...
Click to collapse
Did you use the latest GApps package? As Gazoo119 noted, that fixed a problem with another app that uses Google Play Services. If the problem persists, you may want to go to Apps->Google Play Services, then tap the "Manage space" button. On the next screen it lets you clear all data.
gotshores said:
Have you noticed any issues with GPS? I can run any of the other rom's, including CM11, and it locks on immediately, but it seems random with AOSP. Sometimes I'll wait a coupled of minutes and it'll get a lock, and other times it won't lock on at all.
Click to expand...
Click to collapse
I hadn't tried GPS at all until you mentioned it. I installed Google Maps but couldn't get a lock at all. It's raining here, so I couldn't get fully in the clear. Instead I sat in my car and it still did nothing. Finally, I forced-stopped the app, cleared data and cache, then retried. This time it only took a few seconds to find me. I then turned off GPS, rebooted, and moved to my semi-covered patio. After getting everything going again, it took 10-15 seconds to get a rough fix (off about 70 feet) and it continued to hold it even after I went inside. You may want to try clearing Maps' data (if that's what you're using) to see if that helps.
unomar said:
I had this issue on v0 as well and it seems that it's not gone yet. I only wiped dalvik & cache coming from v0 so I'm not sure if that's part of the problem, but I'm still experiencing the Google Play Music crash. It only seems to crash when playing content that hasn't already been cached locally. Attached is a logcat.
Click to expand...
Click to collapse
Whatever crash you're seeing isn't the one that I fixed. That one was produced a full-blown hardware crash with a register dump. Your logcat doesn't show a register dump or even a Java runtime exception dump. There were two errors that caught my eye but I don't know if either would cause an "Unfortunately..." popup.
Code:
04-08 09:40:24.213 E/DownloadTaskImpl( 3156): Download failed because of IO Error: Socket closed
04-08 09:40:24.213 W/DownloadTaskImpl( 3156): Experienced error when trying to download: [mId=[7871, DEFAULT] mTrackTitle="Le onde" mRemoteId=9ea5817b-9753-348e-af52-ea7c0947c6cb mSourceAccount=1954430662 mPriority=3 mOwner=MUSIC_PLAYBACK mSeekMs=0 mRetryAllowed=true mFileLocation=[mFullPath=/data/data/com.google.android.music/files/music/mplayback_7871.tmp mStorageType=INTERNAL mCacheType=2] mExplicit=false]
Here, the (software) communication link being used to download "Le onde" was broken. Later on, you got this error:
Code:
04-08 09:40:57.133 I/wpa_supplicant( 618): wlan0: CTRL-EVENT-DISCONNECTED bssid=00:1a:30:e4:64:00 reason=0
[...]
04-08 09:40:59.803 E/DownloadTaskImpl( 3156): Download failed because of IO Error: recvfrom failed: ETIMEDOUT (Connection timed out)
04-08 09:40:59.803 W/DownloadTaskImpl( 3156): Experienced error when trying to download: [mId=[363, DEFAULT] mTrackTitle="Black Hole Sun" mRemoteId=8076a782-8454-3fd8-899d-213bb23836ac mSourceAccount=1954430662 mPriority=0 mOwner=MUSIC_PLAYBACK mSeekMs=0 mRetryAllowed=true mFileLocation=[mFullPath=/data/data/com.google.android.music/files/music/mplayback_363.tmp mStorageType=INTERNAL mCacheType=2] mExplicit=true]
This download failure is a lot easier to understand: your WiFi connection had dropped. I don't know that either of these is something I can fix. As above, you may want to try the obvious fixes if you haven't done so already: use the most recent GApps package, clear the app's cache and data, and play with the app's caching options.

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S GT-I9000 Any version to Android 6

[GUIDE/TUTORIAL] Samsung Galaxy S GT-i9000 Any version to Android 6
[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S (GT-I9000 galaxysmtd) stock to Android 6 Marshmallow
This detailed step-by-step guide helps you transform your Samsung Galaxy S I9000 to a more recent one with Android 6.
Make sure your phone is i9000 before going further: when you Power on phone, it is written Galaxy S.
and Go to Settings > About phone > Model number is GT-I9000.
### If Model number is not GT-I9000, quit this tutorial.
Check Android version: right below Model number, you have Firmware version.
If Android is 2.2 or below, follow this tutorial entirely.
If Android is 2.3.x, you can skip step 3)
Back to top of the same About phone menu: tap on System updates to check for an official update.
CHANGELOG OF TUTORIAL
v2. Minor improvements. Bought another i9000 to try whole tutorial again.
v1. Initial release
1) DOWNLOAD
### All you need to upgrade to Android 6 is in my pack. However, Android versions above 4.4 are very slow on Galaxy S (unusable for calls and messages)
### You can easily try Android 5.1.1 and 6.0.1 and come back to 4.4 though.
- djibe Galaxy S i9000 pack (803 MB) v1 : https://bit.ly/djibe-galaxys-pack
(contains Samsung USB drivers + Odin 1.83 + Pit file 512 + Android 2.3.6 GT_I9000_XWJW5_XXJW4_OXXJVC_Sbl + Root CF-Root-XX_OXA_JW4-v4.4-CWM3RFS
+ lineage-11-20170406-UNOFFICIAL-galaxysmtd + omni-5.1.1-20160414-galaxysmtd-HOMEMADE + Full+Advance-6.0.1-20160919-galaxysmtd-Final).
Official LineageOS 11 thread: https://forum.xda-developers.com/t/rom-4-4-4-lineageos.3589037/
- ROM. Full Advance 6.0.1 for galaxysmtd (build 20160919). Included in my pack.
Recommended: Unofficial Lineage OS 11 for galaxysmtd (build 20170406). Included in my pack.
- OpenGApps ARM 6 pico: https://opengapps.org/?arch=arm&api=6.0&variant=pico
Recommended - OpenGApps ARM 4.4 pico: https://opengapps.org/?arch=arm&api=4.4&variant=pico
- Charge phone to 100%
2) DESIMLOCK/DEBRAND/UNLOCK i9000
First, we want to make sure phone is not locked.
On your phone, open the dialer (as if you wanted to call a phone number) and type these keys:
Code:
*#7465625#
Phone returns this message:
Network Lock
[ON]
Follow my tutorial here before going further: https://forum.xda-developers.com/galaxy-s-i9000/general/guide-tutorial-howto-unlock-debrand-t4053109
If Network Lock is [OFF]. Go to next chapter.
3) BACKUP DATA
Install Samsung drivers (you unzipped earlier).
Then plug phone to PC in File transfer mode.
Collect all .jpg or .mp4 (particularly in DCIM folder).
Make sure your Google Account is synchronised.
Use an app like Backupyourmobile or SMS Backup & Restore to backup texts, contacts, etc.
Check that backup is located on microSD card.
Then copy the backup on your PC.
4) FLASH LATEST STOCK ANDROID 2.3.6 GINGERBREAD
### This step is only required if your phone is blocked on Android 2.1 Eclair or 2.2 Froyo (no more recent official update).
If you are already on 2.3.x Gingerbread, move on to next chapter.
You will lose all the data stored on phone.
Shutdown phone.
Boot phone in Download mode: Hold buttons Power + Menu + Volume down until Droid logi is shown and release the buttons.
You see a Droid logo with "Downloading... Do not turn off Target!!!" message (video here if my explanation isn't clear:
)
On PC, launch Odin with Administrator privileges (you unziped it from my pack, in the Flash folder). Select Odin.exe > right click > Run as administrator
In Odin's main window, check all 3 checkboxes: Re-Partition, Auto Reboot, F. Reset Time. Leave other checkboxes unchecked.
### Select PDA, PHONE and CSC files from the GT_I9000_XWJW5_XXJW4_OXXJVC_Sbl folder of my pack.
In PIT > select s1_odin_20100512.pit file
PDA > select PDA_XWJW5_Sbl.tar.md5
PHONE > select PHONE_XXJW4.tar.md5
CSC > select CSC_OXXJVC.tar.md5
Connect phone to USB.
ID:COM state becomes yellow.
Click Start
### ID:COM is not yellow: Try another USB port and/or another USB cable. Or another PC.
### Let flash proceed, don't touch anything, flash will last for 2min30.
Let phone autorestart.
Skip Android setup.
###### At any time, if your phone isn't working properly (bricked, bootloop), you can start fresh from this step.
5) FLASH NEW KERNEL + CWM RECOVERY
### Join us here if you your phone was already Android 2.3.x Gingerbread
Go to Settings > Applications > Development > Switch USB debugging ON.
Power off phone. Unplug phone from USB (if it was).
Run Odin as Administrator.
In Odin main window, check ONLY F. Reset Time checkbox. All other checkboxes must be unchecked.
In PDA > select CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.tar
Boot phone in Download mode: Hold buttons Power + Menu + Volume- until Droid logo is shown.
Connect phone to USB.
When ID:COM is yellow, click Start.
Wait until PASS! message shows up in Odin.
Disconnect phone.
We now want to enter in ClockWorkMod Recovery v3:
Hold buttons Power + Menu + Volume down until phone is shut...
THEN immediately move finger from Volume down to Volume up while holding Power + Home until Samsung logo shows up and release 3 buttons.
### If Android starts to load, just keep pressed on Power + Home + Volume+ until phone restarts and Samsung logo starts showing again.
6) FORMAT PARTITIONS AND INSTALL ANDROID 4.4 KITKAT / LINEAGEOS 11
Navigation within CWM recovery:
- Volume up: move up selection
- Volume down: move down selection
- Home: confirm selection
- Power: back to previous menu
Use Volume down to select wipe data/factory reset and confirm with Home.
On next screen, use volume- to select Yes -- delete all user data. Confirm with Home
Then repeat the operation to wipe cache partition.
Finally, go to mounts and storage and format /system.
Now select "mount USB storage" (still in mounts and storage).
Connect to PC, Galaxy S is detected as USB drive.
From Windows explorer, copy all files from my ROMs folder + Google Apps zip on phone's internal memory.
Once finished, safely remove device from Windows, then unmount from phone and unplug phone from USB.
Go back to CWM home menu and navigate to > install zip from sdcard > choose zip from sdcard > lineage-11*.zip and confirm install
Phone flashes and reboots in CWM recovery 6.0.5.1
### You now use Power to confirm actions within CWM 6 recovery.
Chose Install zip and confirm with Power this time.
choose zip from /storage/sdcard0 and confirm with Power
Select lineage-11*.zip and confirm flash. Wait
When finished, go back to CWM main menu.
Install zip of OpenGapps Pico 4.4 as described above.
Then reboot system now, Cyanogenmod 11/Android 4.4 loads.
Skip Android setup (if you want Android > 4.4, even though not recommended for performance reasons).
7) INSTALL ANDROID 5.1 LOLLIPOP
Shutdown phone.
Restart to recovery
Repeat same steps to install omni-5.1.1*.zip (wipe data/factory reset + Install zip)
Wait during boot.
Power off phone again, back to recovery.
8) INSTALL ANDROID 6 MARSHMALLOW
Recovery is now TWRP 2.8.7.0.
Check Never show this screen during boot again and Swipe to Allow Modifications.
Go to Wipe > Advanced wipe and select Dalvik, Cache, Data and System partitions. Swipe to Wipe.
Now go to Install > select Full+Advance-6.0.1-20160919*.zip and Swipe to Confirm Flash.
It is very long. When finished, tap on Back icon (bottom right of screen).
Tap on open_gapps-arm-6.0-pico*.zip and Swipe to Confirm Flash
Wipe cache/dalvik > Reboot system
Setup Android 6.
Enjoy.
djibe
TODO:
LOS 14.1 https://forum.xda-developers.com/t/rom-final-7-1-2-unofficial-lineageos-14-1.3703447/
### Want to go back to Android 4.4 for fluid usage ?
Restart in Recovery mode.
Go to Wipe > Advanced Wipe.
Select Dalvik, cache, data and systems partitions. Swipe to wipe.
Go to Install > lineage-11*.zip and confirm flash. Wait. Reboot.
Thanks: Authors of LineageOS 11, OpenGApps, Omni ROM, Full Advance ROM, @Katayew

Hi, does it work? Am I the first here, where are the others?
---------- Post added at 07:27 PM ---------- Previous post was at 07:20 PM ----------
Why is it necessary to install Android 5 bevor Android 6 ?

Hi,
seems clear enough to have 0 reactions
Yes you have to move forward slowly and install versions on top.
I would stick to 4.4 though (for fluidity)

I tried this way, and it seems to work. What do You think about?
Basis
S1 Gingerbread 2.3.6 + CF-Root
on internal SDCard CM 13.zip
https://forum.xda-developers.com/galaxy-s-i9000/i9000-development/rombeta-cyanogenmod-13-0-t3343471
Installation
CWM Recovery 3.0.0.5
• 1. install zip from sd card – don´t reboot
• 2. again install zip from sd card
=> TWRP 3.0.2-0 appears
Status Quo:
SDCard = vfat
Data = auto
Cache = yaffs2
System = ext4
....................................................................................the following steps maybe were wrong or unnecessary?
• Reboot to system
=> Installation starts
=> TWRP Menue appears
• Mount SDCard
• Installation CM 13
=> Failed to mount data
• wipe data ext2
=> stopped
• Reboot in Recovery
...............................................................................................................................................................................
• wipe data → Ext2 → failed
• wipe data → Repair file system => OK
• wipe data → Ext2 => OK
• wipe date → Ext4 => OK
....................................................................................the following steps maybe were wrong or unnecessary?
• wipe data → f2fs => OK
• Dalvik + cache WIPE
• Reboot System
=> TWRP Menue
• wipe format System f2fs => OK (ROM probably can´t install on f2fs)
.....................................................................................................................................................
• Mount SDCard, Data, Cache
• Instal CM 13.zip - without Verficiation and without Reboot => DONE - don´t wipe
• Install CM 13.zip => now SU is installing => DONE
• Reboot System
=> CM 13 starts ..................................................................... Antutu 5.7.1 7760
Reboot to TWRP
Status Quo:
data = f2fs
system = ext4
sdcard = vfat
cache = yaffs2
• wipe sdcard to f2fs = > OK
• cache to ext3 (unnecessary because changes automatically back to yaffs2)
• reboot to system
=> CM 13 starts ........................................................................................ Antutu 5.7.1 9500
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
i´m now trying Your Way. However would You like to give some Feedback? I have no experience in Android and i´am just trying like a monkey.
Thanks. Chris

Hi @k2-18b
k2-18b said:
I tried this way, and it seems to work. What do You think about?
Basis
S1 Gingerbread 2.3.6 + CF-Root
on internal SDCard CM 13.zip
https://forum.xda-developers.com/galaxy-s-i9000/i9000-development/rombeta-cyanogenmod-13-0-t3343471
Installation
CWM Recovery 3.0.0.5
• 1. install zip from sd card – don´t reboot
• 2. again install zip from sd card
=> TWRP 3.0.2-0 appears
Status Quo:
SDCard = vfat
Data = auto
Cache = yaffs2
System = ext4
....................................................................................the following steps maybe were wrong or unnecessary?
• Reboot to system
=> Installation starts
=> TWRP Menue appears
• Mount SDCard
• Installation CM 13
=> Failed to mount data
• wipe data ext2
=> stopped
• Reboot in Recovery
...............................................................................................................................................................................
• wipe data → Ext2 → failed
• wipe data → Repair file system => OK
• wipe data → Ext2 => OK
• wipe date → Ext4 => OK
....................................................................................the following steps maybe were wrong or unnecessary?
• wipe data → f2fs => OK
• Dalvik + cache WIPE
• Reboot System
=> TWRP Menue
• wipe format System f2fs => OK (ROM probably can´t install on f2fs)
.....................................................................................................................................................
• Mount SDCard, Data, Cache
• Instal CM 13.zip - without Verficiation and without Reboot => DONE - don´t wipe
• Install CM 13.zip => now SU is installing => DONE
• Reboot System
=> CM 13 starts ..................................................................... Antutu 5.7.1 7760
Reboot to TWRP
Status Quo:
data = f2fs
system = ext4
sdcard = vfat
cache = yaffs2
• wipe sdcard to f2fs = > OK
• cache to ext3 (unnecessary because changes automatically back to yaffs2)
• reboot to system
=> CM 13 starts ........................................................................................ Antutu 5.7.1 9500
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
i´m now trying Your Way. However would You like to give some Feedback? I have no experience in Android and i´am just trying like a monkey.
Thanks. Chris
Click to expand...
Click to collapse
Hi Chris,
I bought another stock and simlocked SGS to test again.
Whole tutorial went on very easily.
Especially when you know that going above Android 4.4 is crazy.

Wonderful tutorial! Pulled out my old phone and it’s happily running 4.4!! Now if I could get Magisk to figure out how to work with this, then I would be overjoyed.

EirikrHinnRauthi said:
Wonderful tutorial! Pulled out my old phone and it’s happily running 4.4!! Now if I could get Magisk to figure out how to work with this, then I would be overjoyed.
Click to expand...
Click to collapse
Hi,
You may try to
Download Magisk https://github.com/topjohnwu/Magisk/releases
Rename .apk to .zip
Reboot to Recovery
Flash zip
Tell us if it worked

djibe89 said:
Hi,
You may try to
Download Magisk https://github.com/topjohnwu/Magisk/releases
Rename .apk to .zip
Reboot to Recovery
Flash zip
Tell us if it worked
Click to expand...
Click to collapse
djibe89 said:
Hi,
You may try to
Download Magisk https://github.com/topjohnwu/Magisk/releases
Rename .apk to .zip
Reboot to Recovery
Flash zip
Tell us if it worked
Click to expand...
Click to collapse
I already have the flushable .zip — here is the message I am getting (ignore the /data thing - that was resolved - message happens anyway)
Also here is a picture of what I get with SuperSU flushable from ChainFire in case that helps anyone figure out what’s up.

Yes I think the phone has a weird boot sequence and cannot be flashed like this. Sorry I don't have time to look into it.
Somewhere on XDA ?

That is actually very well explained. If, like me, you only have Linux and can't use Odin, you can extract zimage from CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.tar and use heimdall to flash:
heimdall flash --KERNEL ./zImage --no-reboot

can we install any newer custom ROM above android 7?

AlphaBravo said:
can we install any newer custom ROM above android 7?
Click to expand...
Click to collapse
You won't be able.
This is the end.
Farewell i9000

[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

[GUIDE] HavocOS 4.1 With GApps and Root (magisk)

I got bored so I made a HavocOS guide. Enjoy!
I am not responsible for any bad things happening to your device/angry parents because YOU messed your phone up. If it somehow broke after you did this, it's not my problem.
oh yea also I didnt make the OS. this is just a guide.
Downloads in video description.
I wanted to make this quick and simple so here's a video:
----------------------------------------------------------
Written guide:
-
Pt. 0: quick prerequisites that i forgor to write before
-
consider reading through the guide before you do it
make sure oem unlocking is enabled on your phone. if you dont know how to do that uhh here's how:
1. go to settings
2. scroll down to about
3. tap the build number until it asks for your screen lock
4. go to system
5. go to developer options
6. enable oem unlocking.
7. if its grayed out its because your phone is cringe, sorry.
-
Pt. 1: Downloads
-
Download all of these files
Google USB driver Extract with 7z or WinRar.
Platform Tools Click "Download for Windows" and extract with 7z or WinRar.
Stock Firmware Extract with 7z or WinRar.
TWRP/Kernel Don't extract this.
HavocOS Don't extract this.
-
Pt. 2: Drivers
-
How to install Android drivers:
1. Put your phone in fastboot mode (turn off your phone and turn it back on with power button and vol down.)
2. Open Device Manager on your PC.
3. Click on the dropdown for "Other Devices"
4. Find "Android"
5. Double click on "Android"
6. Click on "Update Driver"
7. Click on "Browse my computer for drivers"
8. Click on "Let me pick from a list of available drivers on my computer"
9. Double click on "Show all devices"
10. Click on "Have Disk"
11. Click on "Browse"
12. Find the usb_driver folder that you extracted earlier and in that folder, select android_winusb.inf and hit "Open"
13. Select "Android Bootloader Interface" and it "Next"
14. If there are any warnings, just press "Yes"
Drivers have been installed.
-
Pt. 3: Installing command line tools
-
How to install platform-tools systemwide.
1. Find your platform-tools folder and move it to somewhere where it can stay there forever, E.g. the root folder in your C drive (C:\). I don't recommend putting it on your desktop because that will add useless clutter.
2. Go to your start menu and look up "Environment Variables"
3. Click on "Environment Variables"
4. Scroll down on the bottom; "System Variables" section, find "Path", and double click on it
5. Click on "New"
6. Click on "Browse"
7. Navigate to your "platform-tools" folder
8. Click on platform-tools
9. Click "Ok."
10. Click "Ok."
11. Click "Ok."
12. Click "Ok."
(lol)
oh also i forgot to mention, unlock your bootloader now
steps to do that here:
1. open cmd
2. enter fastboot flashing unlock
3. hit yes on the prompt that appears on your phone
4. you might need to enter fastboot flashing unlock_critical (if cmd gives you an error saying it doesn't exist or something just kinda ignore it, i'm only putting it here just in case)
5. you should be good to continue
-
Pt. 4: The Installation.
-
Installing HavocOS
1. MAKE SURE THAT YOUR PHONE IS IN FASTBOOT MODE.
2. Open aura-p-release-3201
3. Run flash_all.bat (double click on it)
4. Wait until it finishes running.
5. As soon as it closes and your phone screen turns black, immediately hold the power and volume down buttons and enter fastboot mode.
6. Open Command Prompt (CMD)
7. Flash the Kernel by typing fastboot flash boot <boot.img> and replace <boot.img> with the file path to your boot.img file. (Tip: you can drag the file into CMD to put in the file path.)
8. Flash HavocOS by typing fastboot flash system <HavocOS PHH.img> and replace <HavocOS PHH.img> with the file path to the HavocOS PHH.img file. Ignore the errors.
9. Wait until everything finishes and unplug your phone (if you want to)
10. Use volume buttons to go down to "Recovery Mode"
11. Select "Recovery Mode" with your power button. (Tip: double tap the power button to get past the bootloader unlocked warning screen)
12. Swipe to allow modifications
13. Tap on wipe > format data > type "yes" > press "OK"
14. Press back until you get to the TWRP home screen
15. Tap "Reboot" > tap "Recovery" > then tap "Do not install"
16. Wait until it reboots back into recovery.
17. Follow steps 12-14, then hit "Reboot" > then hit "System"
If it doesn't boot into the setup screen, open fastboot mode and format the data once more, then reboot into system.
----------------------------------------------------------
and here are the easiest and also some of the dumbest GSI root instructions ever:
Download Magisk-v21.4.zip
1. Open TWRP and mount everything. (except for USB storage. micro sd card is optional.)
2. Put Magisk-v21.4.zip on your phone (in file explorer)
3. Open the TWRP file manager (advanced > file manager)
4. Navigate to /system/system/bin
5. Find resetprop and tap on it
6. Rename resetprop to phh-resetprop
7. tap on install
8. install Magisk-v21.4.zip
9. Boot up your phone, open magisk, and update everything.
10. Turn on MagiskHide in the settings of magisk manager.
11. Profit$ (lol)
SafetyNet should pass if you did it properly (I would find it kinda funny if you managed to mess up those easy instructions)
Alright guys, have a nice day!
p.s: I might begin work on a user-friendly auto-installer soon.

Thank you OP, finally got Android 11 fully working including SafetyNet, camera/flashlight, Bluetooth and SD card. The only tricky part was the Bluetooth - got help from this comment - needed to delete both APKs before first boot.

pigjr said:
Thank you OP, finally got Android 11 fully working including SafetyNet, camera/flashlight, Bluetooth and SD card. The only tricky part was the Bluetooth - got help from this comment - needed to delete both APKs before first boot.
Click to expand...
Click to collapse
yea i forgot to include that part. I thought you didn't need to do that before boot tho. I managed to get BT working by deleting BluetoothResCommon.apk and renaming RazerAuraBluetoothRes.apk to BluetoothResCommon.apk.

all the links for 4.1 are dead you got any bro?

Cylow333 said:
all the links for 4.1 are dead you got any bro?
Click to expand...
Click to collapse
There is a mirror in the description of the video.

Dude you are a different type of god thank you so much I can finally sleep now.

Quick question: is this version of Havoc have no issues with receiving SMS? Previous versions of it cause this annoying issue that after few minutes from restart SMS stop arriving to phone and the only fix at that time was just to restart it. Tried some patches from telegram but basically end up with no fix.

drumiec said:
Quick question: is this version of Havoc have no issues with receiving SMS? Previous versions of it cause this annoying issue that after few minutes from restart SMS stop arriving to phone and the only fix at that time was just to restart it. Tried some patches from telegram but basically end up with no fix.
Click to expand...
Click to collapse
not that i know of

Uhh is there anyway to edit the buildprop without getting a bootloop? I tried with buildprop editor and i vant see any of the info if i change something and when i restart it goes in a loop.

Cylow333 said:
Uhh is there anyway to edit the buildprop without getting a bootloop? I tried with buildprop editor and i vant see any of the info if i change something and when i restart it goes in a loop.
Click to expand...
Click to collapse
I have never tried editing the buildprop so I don't know, sorry.

Marcos8760 said:
yea i forgot to include that part. I thought you didn't need to do that before boot tho. I managed to get BT working by deleting BluetoothResCommon.apk and renaming RazerAuraBluetoothRes.apk to BluetoothResCommon.apk.
Click to expand...
Click to collapse
So do I have to reflash in order to fix Bluetooth?
Sadly my main reason for losing is that I'm running into a mako issue with HavocOS. systenUI keeps crashing whenever the on-screen keyboard is displayed. This happens with the default installed gBoard and SwiftKey beta. It also crashes when the screen goes to sleep. I followed all the steps from the video. Only thing I did besides that was restore a backup from Google Drive so I didn't have to manually install everything. I'm sadly out of ideas and might have to switch to normal GSI or back to LineageOS so the device is stable enough to use.

gumbyx84 said:
So do I have to reflash in order to fix Bluetooth?
Sadly my main reason for losing is that I'm running into a mako issue with HavocOS. systenUI keeps crashing whenever the on-screen keyboard is displayed. This happens with the default installed gBoard and SwiftKey beta. It also crashes when the screen goes to sleep. I followed all the steps from the video. Only thing I did besides that was restore a backup from Google Drive so I didn't have to manually install everything. I'm sadly out of ideas and might have to switch to normal GSI or back to LineageOS so the device is stable enough to use.
Click to expand...
Click to collapse
I have never had to fix BT before first boot.
And also, that's kinda weird. I've never had any systemUI crashes with the keyboard, although i have had a weird bug where the entire OS crashes and it reboots into a state where its impossible to use. however, to fix that, i just reflashed and i never encountered the bug again. your install might have been a lemon. maybe install again?

Marcos8760 said:
I have never had to fix BT before first boot.
And also, that's kinda weird. I've never had any systemUI crashes with the keyboard, although i have had a weird bug where the entire OS crashes and it reboots into a state where its impossible to use. however, to fix that, i just reflashed and i never encountered the bug again. your install might have been a lemon. maybe install again?
Click to expand...
Click to collapse
Do I need to flash back to stock or can I do a "dirty" reflash?

gumbyx84 said:
Do I need to flash back to stock or can I do a "dirty" reflash?
Click to expand...
Click to collapse
Eh. I think flashing back to stock might be better.

Marcos8760 said:
Eh. I think flashing back to stock might be better.
Click to expand...
Click to collapse
Trying out now. I'm at work so I don't have my laptop with me. Trying it work a live CD image lol
Update: It's been sitting on the "Powered by Android" screen for 20+ minutes. I already tried a data wipe from the bootloader. I can get into TWRP. I'm going to give it another 10 minutes then try flashing HavocOS again.
Update 2: I've made progress. Now it's stick on the HavocOS loading screen. It's been like that for 20+ minutes. Tried the bootloader data format.
Update 3: I was finally able to flash HavocOS at home without issue. I flashed Magisk before even booting into the OS and it seems to be working ok. After it rebooted to complete the setup/install, the issue came back. I'm just flashing HavocOS without Magisk for now.

Hello,
Thank you for the guide, i have installed the android 11 successfully, but i got a startup loup when i tried to restart the phone (in a normal way ), the havoc logo started up then the password, but it just louping between them..
Please help

Hello I did exactly what you said for magisk I updated everything but the problem is that I don't have access to superuser and nor to the module in magisk in my razer phone 2 with havocOS.
Do you have a solution to this problem thank you ?

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy Tab 2 (7 or 10") from Stock to Android 8.1

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy Tab 2 (7 or 10") from Stock to Android 8.1
[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy Tab 2 Unified (7 or 10", espressowifi/3g) Stock to Android 8.1 Oreo / Unlegacy Android
This detailed step-by-step guide helps you transform your Samsung Galaxy Tab 2 to a newer one with Android 8.1.
Make sure your tablet is fine before going further: in Android, go to Settings > About device > Model number is listed below.
- espressowifi
- GT-P3110 (7", Wi-Fi)
- GT-P3113 (7", Wi-Fi)
- GT-P5110 (10.1", Wi-Fi)
- GT-P5113 (10.1", Wi-Fi)
- espresso3g
- GT-P3100 (7", 3G)
- GT-P5100 (10.1", 3G)
If not, quit this tutorial.
Disney+ and Netflix are working.
CHANGELOG
v1. Initial release for Android 8.1
1) DOWNLOAD
- djibe Galaxy Tab 2 pack: https://bit.ly/djibe-galaxytab2-pack
(contains Samsung tweaked Odin 3.13.1 + Samsung USB drivers + TWRP 3.4.0-0 official recovery + Magisk Root + Aurora Store). Unzip files.
+ ROM Android 8.1 Unlegacy Android: https://forum.xda-developers.com/t/rom-aosp-8-1-oreo-unlegacy-android-unofficial.4323203/
Download latest Wi-Fi build here: https://forum.xda-developers.com/attachments/ua_espresso-8-1-0-20211021-surefixed-zip.5438769/
Download latest 3G build here: https://androidfilehost.com/?fid=7161016148664826463
### GPS and Camera don't work. Use an Android 7.1 ROM if you need these
+ BitGApps Package ARM 8.1 (R44+): https://forum.xda-developers.com/t/custom-gapps-bitgapps-for-android.4012165/post-81060605
Download latest build: https://github.com/BiTGApps/BiTGApps-Release/releases
+ a microSD card. Copy ROM, Gapps, Magisk root and Aurora Store on microSD card (FAT32 format) and insert it in phone.
+ Charge phone to 100%
2) BACKUP DATA
Install Samsung drivers (you unzipped earlier).
Then plug phone to PC in File transfer mode.
Collect all .jpg or .mp4
Use app like Backupyourmobile and SMS backup & Restore to backup contacts, etc.
Check that backup is located on microSD card.
Then copy the backup on your PC.
Now connect to Wi-Fi, Settings > About device > Software update. Check you already have the latest.
3) FLASH TWRP 3.4 RECOVERY
Shut down tablet.
Boot in Download Mode: hold Power + Volume- until you see Warning's screen and release all buttons.
Confirm access to Download mode by pressing Volume+.
Connect tablet in USB, wait during bootloader drivers installation.
Then launch Odin.exe (included in my archive) and wait for Odin indicator ID:COM to become blue.
In options: Verify re-partition and Auto Reboot are NOT ticked while F. Reset Time is ticked.
In Files > PDA > select twrp-3.4.0-0-espressowifi.img.tar
### or twrp-3.4.0-0-espresso3g.img.tar for 3G model.
### Warranty will be Void after next click ###
Click Start.
When Success green message appears, unplug USB.
Now hold Power + Volume+ until Samsung logo shows up and release buttons.
### If tablet reboots normally, recovery will be reset. You can flash TWRP with Odin again.
4) BACKUP SYSTEM (Nandroid backup)
Wait a few seconds for TWRP recovery to boot.
Recovery asks for Keep System Read Only ? > Swipe to Allow Modifications.
Go to Backup > you can select the partitions you want to save.
I prefer to backup System, EFS and Boot.
Now type Select Storage > Select Micro SD card and confirm with OK
Now Swipe to Backup and wait during process.
Go to Home screen and continue with next chapter.
5) FORMAT PARTITIONS
Go to Wipe > Format Data
Type yes and confirm with bottom right icon.
Go to Home > Reboot > Recovery > Do not install app.
Back to TWRP, go to Wipe > Advanced wipe,
select Dalvik, System, Data, Internal Storage (if you really made a backup from step 2), Cache, then Swipe to Wipe,
then back.
### Don't select microSD or you will lose your backup
Go to Home > Reboot > Recovery > Do not install app.
6) FLASH ROM, GAPPS
Go to Install > choose ua_expresso*.zip,
(if you don't see the files, tap on Select Storage and make sure Micro SDCard is active).
then Add more Zips > bitgapps*.zip
then Swipe to confirm Flash.
Wait for operation to end.
Then tap Wipe cache/dalvik, swipe to confirm,
then Reboot System.
Wait for the phone to boot during 5 minutes.
### Don't connect to your Google account before setting up root.
7) IMPROVE
Go to Settings > System > About tablet
### Wi-Fi users, don't be scared, Galaxy Tab 2 3G is written, not a big deal.
Tap on the "Build number" entry seven times. You are notified that developer settings are now active.
Go to Settings > System > Developer options,
Set Windows animation to 0, Transition animation and transition scales to x 0,5.
If Netflix or Disney+ are not accessible from the Play Store, use Aurora Store.
8) STORE YOUR BACKUP IN A SAFE PLACE
Connect phone or microSD to PC.
Open microSD folder and backup TWRP folder to a safe place.
Enjoy,
djibe
Thanks: @Mighty, @LR7875, LOS Team, TWRP Team, BitGapps team, topjohnwu

Hi, there doesn't seem to be anything named Magisk Root within the download zip. Is it missing or am I missing something?

iCasseus said:
Hi, there doesn't seem to be anything named Magisk Root within the download zip. Is it missing or am I missing something?
Click to expand...
Click to collapse
Hi,true and sorry for that
You can download it here: https://github.com/topjohnwu/Magisk/releases

djibe89 said:
Hi,true and sorry for that
You can download it here: https://github.com/topjohnwu/Magisk/releases
Click to expand...
Click to collapse
Thanks. What do you do with Magisk after copying it to the external memory as it isn't mentioned in any other steps?
I have managed to follow all other steps and have it running with android 8.1 however Disney+ and Netflix do not work as I believe they see the tablet as rooted and don't like it. I have tried a few Disney+ install work arounds but still doesn't work. Do you have any ideas? Cheers

djibe89 said:
[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy Tab 2 (7 or 10") from Stock to Android 8.1
[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy Tab 2 Unified (7 or 10", espressowifi/3g) Stock to Android 8.1 Oreo / Unlegacy Android
This detailed step-by-step guide helps you transform your Samsung Galaxy Tab 2 to a newer one with Android 8.1.
Make sure your tablet is fine before going further: in Android, go to Settings > About device > Model number is listed below.
- espressowifi
- GT-P3110 (7", Wi-Fi)
- GT-P3113 (7", Wi-Fi)
- GT-P5110 (10.1", Wi-Fi)
- GT-P5113 (10.1", Wi-Fi)
- espresso3g
- GT-P3100 (7", 3G)
- GT-P5100 (10.1", 3G)
If not, quit this tutorial.
Disney+ and Netflix are working.
CHANGELOG
v1. Initial release for Android 8.1
1) DOWNLOAD
- djibe Galaxy Tab 2 pack: https://bit.ly/djibe-galaxytab2-pack
(contains Samsung tweaked Odin 3.13.1 + Samsung USB drivers + TWRP 3.4.0-0 official recovery + Magisk Root + Aurora Store). Unzip files.
+ ROM Android 8.1 Unlegacy Android: https://forum.xda-developers.com/t/rom-aosp-8-1-oreo-unlegacy-android-unofficial.4323203/
Download latest Wi-Fi build here: https://forum.xda-developers.com/attachments/ua_espresso-8-1-0-20211021-surefixed-zip.5438769/
Download latest 3G build here: https://androidfilehost.com/?fid=7161016148664826463
### GPS and Camera don't work. Use an Android 7.1 ROM if you need these
+ BitGApps Package ARM 8.1 (R44+): https://forum.xda-developers.com/t/custom-gapps-bitgapps-for-android.4012165/post-81060605
Download latest build: https://github.com/BiTGApps/BiTGApps-Release/releases
+ a microSD card. Copy ROM, Gapps, Magisk root and Aurora Store on microSD card (FAT32 format) and insert it in phone.
+ Charge phone to 100%
2) BACKUP DATA
Install Samsung drivers (you unzipped earlier).
Then plug phone to PC in File transfer mode.
Collect all .jpg or .mp4
Use app like Backupyourmobile and SMS backup & Restore to backup contacts, etc.
Check that backup is located on microSD card.
Then copy the backup on your PC.
Now connect to Wi-Fi, Settings > About device > Software update. Check you already have the latest.
3) FLASH TWRP 3.4 RECOVERY
Shut down tablet.
Boot in Download Mode: hold Power + Volume- until you see Warning's screen and release all buttons.
Confirm access to Download mode by pressing Volume+.
Connect tablet in USB, wait during bootloader drivers installation.
Then launch Odin.exe (included in my archive) and wait for Odin indicator ID:COM to become blue.
In options: Verify re-partition and Auto Reboot are NOT ticked while F. Reset Time is ticked.
In Files > PDA > select twrp-3.4.0-0-espressowifi.img.tar
### or twrp-3.4.0-0-espresso3g.img.tar for 3G model.
### Warranty will be Void after next click ###
Click Start.
When Success green message appears, unplug USB.
Now hold Power + Volume+ until Samsung logo shows up and release buttons.
### If tablet reboots normally, recovery will be reset. You can flash TWRP with Odin again.
4) BACKUP SYSTEM (Nandroid backup)
Wait a few seconds for TWRP recovery to boot.
Recovery asks for Keep System Read Only ? > Swipe to Allow Modifications.
Go to Backup > you can select the partitions you want to save.
I prefer to backup System, EFS and Boot.
Now type Select Storage > Select Micro SD card and confirm with OK
Now Swipe to Backup and wait during process.
Go to Home screen and continue with next chapter.
5) FORMAT PARTITIONS
Go to Wipe > Format Data
Type yes and confirm with bottom right icon.
Go to Home > Reboot > Recovery > Do not install app.
Back to TWRP, go to Wipe > Advanced wipe,
select Dalvik, System, Data, Internal Storage (if you really made a backup from step 2), Cache, then Swipe to Wipe,
then back.
### Don't select microSD or you will lose your backup
Go to Home > Reboot > Recovery > Do not install app.
6) FLASH ROM, GAPPS
Go to Install > choose ua_expresso*.zip,
(if you don't see the files, tap on Select Storage and make sure Micro SDCard is active).
then Add more Zips > bitgapps*.zip
then Swipe to confirm Flash.
Wait for operation to end.
Then tap Wipe cache/dalvik, swipe to confirm,
then Reboot System.
Wait for the phone to boot during 5 minutes.
### Don't connect to your Google account before setting up root.
7) IMPROVE
Go to Settings > System > About tablet
### Wi-Fi users, don't be scared, Galaxy Tab 2 3G is written, not a big deal.
Tap on the "Build number" entry seven times. You are notified that developer settings are now active.
Go to Settings > System > Developer options,
Set Windows animation to 0, Transition animation and transition scales to x 0,5.
If Netflix or Disney+ are not accessible from the Play Store, use Aurora Store.
8) STORE YOUR BACKUP IN A SAFE PLACE
Connect phone or microSD to PC.
Open microSD folder and backup TWRP folder to a safe place.
Enjoy,
djibe
Thanks: @Mighty, @LR7875, LOS Team, TWRP Team, BitGapps team, topjohnwu
Click to expand...
Click to collapse
Hi, may I ask where I can get the 7.1 ROM for my P3100?
Thank you very much! (my dad loves using old stuffs, but he wants GPS for some reasons)

Hi All,
Thanks for the tuto.
During the process, at point 6 for the zip files.
ua_expresso*.zip has been selected but i added BiTGApp 12 instead of 8.1.
ua_expresso*.zip installed but not BiTGApp.
The tablets works fine but without browser etc.
i tried to install again from Odin but it doens't come to TRW. The tablet restarts with ANDROID.
Thanks for any help,
Cheers,

bilame said:
Hi All,
Thanks for the tuto.
During the process, at point 6 for the zip files.
ua_expresso*.zip has been selected but i added BiTGApp 12 instead of 8.1.
ua_expresso*.zip installed but not BiTGApp.
The tablets works fine but without browser etc.
i tried to install again from Odin but it doens't come to TRW. The tablet restarts with ANDROID.
Thanks for any help,
Cheers,
Click to expand...
Click to collapse
Hi, can you boot with Power + Volume+ and release when Samsung logo is displayed ?

Hi djibe89,
Thanks for the quick reply.
Yes, i started with power + volume+ and it leaded to TRW.
so i installed the BiTGApp 8.1, then wiped cache/dalvik then reboot.
it didn't take 5 min but no apps has been installed unfortunately

bilame said:
Hi djibe89,
Thanks for the quick reply.
Yes, i started with power + volume+ and it leaded to TRW.
so i installed the BiTGApp 8.1, then wiped cache/dalvik then reboot.
it didn't take 5 min but no apps has been installed unfortunately
Click to expand...
Click to collapse
You can try OpenGApps then

bilame said:
Hi djibe89,
Thanks for the quick reply.
Yes, i started with power + volume+ and it leaded to TRW.
so i installed the BiTGApp 8.1, then wiped cache/dalvik then reboot.
it didn't take 5 min but no apps has been installed unfortunately
Click to expand...
Click to collapse
djibe89 said:
You can try OpenGApps then
Click to expand...
Click to collapse
or deltadroid : http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

aqt169 said:
Hi, may I ask where I can get the 7.1 ROM for my P3100?
Thank you very much! (my dad loves using old stuffs, but he wants GPS for some reasons)
Click to expand...
Click to collapse
GPS works in 8.1 rom tho

Hi,
Thanks Djibe89 and TheDoctor46.
I am wondering if files put on the sdcard from the first install could avoid right install of BiTGApp 8.1 ?
it's quite weird, i have no sound.
i could install a browser from playstore.
well, i'll try both OpenGapps and deltadroid.

bilame said:
Hi,
Thanks Djibe89 and TheDoctor46.
I am wondering if files put on the sdcard from the first install could avoid right install of BiTGApp 8.1 ?
Click to expand...
Click to collapse
Not it should not affect installation as thats what everyone does. Maybe a problem of BiTGapps?? (I have never tried them)

Hi members,
question everything works fine but i dont see playstore ore browser what did i wrong?

mp3catcher said:
Hi members,
question everything works fine but i dont see playstore ore browser what did i wrong?
Click to expand...
Click to collapse
Hi, which GApps did you flash ?

djibe89 said:
Hi, which GApps did you flash ?
Click to expand...
Click to collapse
Gapps base arm64-9.0.0 20180918 signed and bitgapps arm64-12.0.0-r45 both not working

mp3catcher said:
Gapps base arm64-9.0.0 20180918 signed and bitgapps arm64-12.0.0-r45 both not working
Click to expand...
Click to collapse

IMG-20220519-160206
Image IMG-20220519-160206 hosted in ImgBB
ibb.co

Well, Oreo is Android 8.1 so you have to download 8.1 GApps: https://github.com/BiTGApps/BiTGApp...wnload/v1.7/BiTGApps-arm-8.1.0-R45_signed.zip
Clean wipe and flash ROM + GAPPS

mp3catcher said:
Gapps base arm64-9.0.0 20180918 signed and bitgapps arm64-12.0.0-r45 both not working
Click to expand...
Click to collapse
You can't flash arm64 gapps on arm (v7) device and expect it to work.